Re: PDSE and HLASM together in z/OS 2.1

2014-02-28 Thread Sharuff Morsa3
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

Re: PDSE and HLASM together in z/OS 2.1

2014-02-28 Thread Miklos Szigetvari
- 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

Re: PDSE and HLASM together in z/OS 2.1

2014-02-27 Thread Sharuff Morsa3
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

Re: PDSE and HLASM together in z/OS 2.1

2014-02-27 Thread John Gilmore
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.

PDSE and HLASM together in z/OS 2.1

2014-02-26 Thread Miklos Szigetvari
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