SYSADATA file quirk

2011-02-21 Thread Mike Shaw
Everyone: I have a PDSE defined as RECFM=VB, LRECL=300, BLKSIZE=23440. Several members exist in the data set. If I use HLASM 1.6 to assemble a module and point the SYSADATA DD for that assembly to that PDSE like this in the JCL: //C.SYSADATA DD DISP=SHR,DSN=x(memname) with the ADATA parm

Re: SYSADATA file quirk

2011-02-21 Thread Johanson, Adam
Mike Shaw wrote: If he's not happy 'cause the LRECL is too short, give me an error message, don't just change things without telling me! I don't know if this qualifies as HLASM telling you that it's changing things, but the Programmer's Guide says that the file attributes should be

Re: SYSADATA file quirk

2011-02-21 Thread Mike Shaw
Thank you Adam, I stand corrected. A warning message would have been nice though... -- Mike Shaw MVS/QuickRef Support Group Chicago-Soft, Ltd. On Mon, Feb 21, 2011 at 2:43 PM, Johanson, Adam adam.johan...@usaa.comwrote: Mike Shaw wrote: If he's not happy 'cause the LRECL is too short, give

Re: SYSADATA file quirk

2011-02-21 Thread Paul Gilmartin
On 2/21/2011 11:17 AM, Mike Shaw wrote: Shouldn't the assembler check the DCB attributes for an existing SYSADATA output file, particularly a PDS or PDSE, and use those attributes, rather than CHANGING the DCB attributes without a warning? If he's not happy 'cause the LRECL is too short, give me

Re: SYSADATA file quirk

2011-02-21 Thread Paul Gilmartin
On 2/21/2011 3:00 PM, Binyamin Dissen wrote: On Mon, 21 Feb 2011 14:20:04 -0700 Paul Gilmartinpaulgboul...@aim.com wrote: :On 2/21/2011 11:17 AM, Mike Shaw wrote: : Shouldn't the assembler check the DCB attributes for an existing SYSADATA : output file, particularly a PDS or PDSE, and use