I think we need to 'see the work'. You mention 'copying' the dataset. But
allocation doesn't depend on the program being executed - only the SPACE
specification. So if you allocate something like:
//DG2 EXEC PGM=IEBDG
//SYSPRINT DD SYSOUT=*
//SEQOUT DD DSN=SJP.AVGR.DATA,DISP=(,CATLG),
// LRECL=80,BLKSIZE=27920,RECFM=FB,DSORG=PS,
// SPACE=(80,698),AVGREC=U
//SYSIN DD *
DSD OUTPUT=(SEQOUT)
FD NAME=FIELD1,STARTLOC=1,LENGTH=4,PICTURE=4,B'0001',INDEX=1
CREATE QUANTITY=698,NAME=FIELD1
And then run an IEHLIST against the resulting dataset, it should occupy one
track:
CONTENTS OF VTOC ON VOL SMS007 <THIS IS AN SMS MANAGED VOLUME>
---------------DATA SET NAME---------------- SER NO SEQNO DATE.CRE DATE.EXP
DATE.REF EXT DSORG RECFM OPTCD BLKSIZE
SJP.AVGR.DATA SMS007 1 2021.082 00.000
2021.082 1 PS FB 00 27920
SMS.IND LRECL KEYLEN INITIAL ALLOC 2ND ALLOC EXTEND LAST
BLK(T-R-L) DIR.REM F2 OR F3(C-H-R) DSCB(C-H-R)
S 80 TRKS 0 0BY 0 2
170 0 1 7
EATTR
NS
EXTENTS NO LOW(C-H) HIGH(C-H)
0 4 13 4 13
----ON THE ABOVE DATA SET,THERE ARE 0
EMPTY TRACK(S).
One possibility is that the Default Device Geometry in the your SMS
configuration is 47476 rather than 56664 (i.e., 3380 rather than 3390). If
you're copying the dataset with an application such as Sort or something
similar, the application may alter the output allocation or may automatically
taken another extent. Another possibility is a vendor product such ours (ACC)
or others (from BMC, CA, etc), that might automatically alter certain
allocations.
Steve
Steve Pryor
DTS Software LLC
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
