Why not use DSORG=PS? My ADATA below.
Regards,
John K
>usage
DISP UNIT RECFM LRECL BLKSIZE ALLOCTRK FREETRK SECONDARY DSORG
SHR 3390 VB 32756 32760 5X 1350 1 10 CYL PS
>verify
END OF DATA SET
159 CHARACTERS PER AVERAGE VARIABLE LENGTH RECORD
25,052 CHARACTERS IN THE LARGEST VARIABLE LENGTH RECORD
276,479 LOGICAL RECORDS WERE INPUT
1,353 PHYSICAL BLOCKS WERE INPUT
32,760 CHARACTERS IN THE LARGEST PHYSICAL BLOCK
32,598 CHARACTERS PER AVERAGE PHYSICAL BLOCK
From: paul schuster <[email protected]>
To: [email protected]
Date: 08/31/2010 12:26 AM
Subject: ADATA size limitation ?
Hi:
Is there a limitation on how many ADATA records can be written? For
example, when I define the ADATA file as a PDSE, and the number of records
must exceed the 64K PDSE member limit, the assembly fails and I get this
message:
IEC036I 002-AC,IGC0005E,jobname,procname,ADATA,ucb@,volser,adatadsn,ADATA
IEA995I SYMPTOM DUMP OUTPUT 285
SYSTEM COMPLETION CODE=002 REASON CODE=000000AC
TIME=23.56.48 SEQ=15258 CPU=0000 ASID=0167
PSW AT TIME OF ERROR 075C1000 80DC0B56 ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=00DBF000 OFFSET=00001B56
NAME=IFG0199B
When I then define the ADATA file as a PDS,
asssembly works ok, but ADATA file always shows 64403 records, and the last
many (not sure how many, probably several hundred) records are all like
this:
****************************************** * * * I/O error detected, I/O
terminated * * * ******************************************
Is there some way around this limiitation? Probably an ADATA exit, but
which records should be filtered? I am trying to create an ADATA file for
use by the XDC MAP and DMAP commands.
This is HLASM RELEASE at PTF UK57150. Or is this already fixed at a higher
maintenance level for HLASM?
Thank you.
Paul
