In reaction to the recent DUMMY and ISPLOG BLKSIZE=0 thread, I did a test
with the following:
//GENER EXEC PGM=IEBGENER
//SYSPRINT DD DISP=(NEW,CATLG),
// DSN=&SYSUID..IEBGENER.SYSPRINT,
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0),
// UNIT=SYSDA,SPACE=(TRK,1)
(Note this is SYSPRINT, not SYSUT2.) The characteristics of the created
data set are:
Data Set Name . . . : user.IEBGENER.SYSPRINT
General Data Current Allocation
Volume serial . . . : TSO002 Allocated tracks . : 1
Device type . . . . : 3390 Allocated extents . : 1
Organization . . . : PS
Record format . . . : FBA
Record length . . . : 121
Block size . . . . : 121 Current Utilization
1st extent tracks . : 1 Used tracks . . . . : 1
Secondary tracks . : 0 Used extents . . . : 1
This BLKSIZE does not appear to be the SDB supplied value (a similar test
with IDCAMS REPRO gives 27951). It has been my perception that it is IBM's
policy to allow SDB to operate on utility output rather than forcing a
BLKSIZE in the utility's code. Should this be reported to IBM? (And how
is Utilities Development likely to react in view of the recent waffle on
the IEBGENER PARM='SDB=YES' default waffle?)
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
