Re: PDSE and HLASM together in z/OS 2.1
After a bit of (archaeological) digging, it appears our manuals are incorrect and that we've visited this issue before. When HLASM 1.4 development was in full flight, the CODEPAGE option was added. This appears to have fallen victim to the short-on-os-storage issue - and the coded 128k value was changed to a whopping 132K! - the books never caught up with this modification. I agree with Miklos, and we will look to change this value - Richard will be on the case when he returns from SHARE. Sharuff smo...@uk.ibm.com btw - anyone going to SHARE ? If so, go say hello to Richard Cebula - its his first SHARE conference! From:Miklos Szigetvari miklos.szigetv...@isis-papyrus.com Subject: Re: PDSE and HLASM together in z/OS 2.1 Hi Thank you Sharuff. We have closed the PMR76555.010.618, as with REGION=1000M it worked, I think it would be not bad if the SIZE default would be a little less. On 27.02.2014 13:38, Sharuff Morsa3 wrote: Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: PDSE and HLASM together in z/OS 2.1
Thank you very much On 28.02.2014 12:26, Sharuff Morsa3 wrote: After a bit of (archaeological) digging, it appears our manuals are incorrect and that we've visited this issue before. When HLASM 1.4 development was in full flight, the CODEPAGE option was added. This appears to have fallen victim to the short-on-os-storage issue - and the coded 128k value was changed to a whopping 132K! - the books never caught up with this modification. I agree with Miklos, and we will look to change this value - Richard will be on the case when he returns from SHARE. Sharuff smo...@uk.ibm.com btw - anyone going to SHARE ? If so, go say hello to Richard Cebula - its his first SHARE conference! From:Miklos Szigetvari miklos.szigetv...@isis-papyrus.com Subject: Re: PDSE and HLASM together in z/OS 2.1 Hi Thank you Sharuff. We have closed the PMR76555.010.618, as with REGION=1000M it worked, I think it would be not bad if the SIZE default would be a little less. On 27.02.2014 13:38, Sharuff Morsa3 wrote: Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Kind regards, / Mit freundlichen Grüßen Miklos Szigetvari Research Development ISIS Papyrus Europe AG Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria T: +43(2236) 27551 333, F: +43(2236)21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our brand new extended Website at www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS Papyrus accepts no responsibility for malicious or inappropriate content. ---
Re: PDSE and HLASM together in z/OS 2.1
Miklos Szigetvari wrote: Subject: PDSE and HLASM together in z/OS 2.1 ... After a PMR it turned out that the PDSE has not enough storage. We are using the default assembler OPTION SIZE(MAX) . In this case , according the book , the assembler gives back 128 K byte storage, but it is not big enough for PDSE. I will change the default SIZE, but maybe the assembler would gives back something more as 128K ? SIZE=MAX is the default. Reading the HLASM Install guide SC26-3494-05 http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/download/asmi1021.pdf page 170, note 4 says: '4. When you specify the MAX suboption, the assembler releases 128 K back to the user region (z/OS), virtual machine (CMS), or the partition GETVIS (z/VSE), for system usage. When you specify the MAX suboption, there might not be enough storage remaining in the user region (z/OS), virtual machine (CMS), or the partition GETVIS (z/VSE), to load any exits you specify, or any external functions you use in your assembly. I also found the HLASM V1.4 pdf (dated Sept 2000) - and it has the same words - and I'd put good money on the older versions saying the same. Richard (the HLASM developer) has asked whether this is the time to change the 128k value increase it a little rather than have everyone change their procedures. If an RFE or request appears - I'm sure an APAR will soon turn up. (An RFE would be a good place for all to suggest what value should be used in place of 128k) Sharuff smo...@uk.ibm.com Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: PDSE and HLASM together in z/OS 2.1
As John Ehrman very recently pointed out here, expressions, e.g., SIZE(MAX-2M) may be used is specifying SIZE values. It would, I think, be more appropriate to make this facility better known and encourage its use than it would be to change the traditional behavior of MAX under the covers. Making such a change will certainly produce more ABENDs than result from its current, occasionally greedy behavior. John Gilmore, Ashland, MA 01721 - USA
PDSE and HLASM together in z/OS 2.1
Hi Not so serious problem, in z/OS 1.13 we wrote our SYSADATA to PDSE and using 0M region size. In z/OS 2.1 all this jobs ended with an S0F4 reason x'24' and i/O error with SYSADATA After a PMR it turned out that the PDSE has not enough storage. We are using the default assembler OPTION SIZE(MAX) . In this case , according the book , the assembler gives back 128 K byte storage, but it is not big enough for PDSE. I will change the default SIZE, but maybe the assembler would gives back something more as 128K ? -- Kind regards, / Mit freundlichen Grüßen Miklos Szigetvari Research Development ISIS Papyrus Europe AG Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria T: +43(2236) 27551 333, F: +43(2236)21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our brand new extended Website at www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS Papyrus accepts no responsibility for malicious or inappropriate content. ---
