Guys,
That explains most of my issues. We have some fairly large LRECL FB
sequential work files and were finding them unblocked, which increased our
I/O quite a bit. So SDB always blocks for maximum capacity, regardless of
performance implications. I guess we have to manually block these files
via JCL. Or is there a way to tell SDB that you want to favor performance
over capacity for a particular dataset?
I have another issue. Here is an example of some allocation JCL.
//STEP1 EXEC PGM=IEFBR14,REGION=4M
//SYSPRINT DD SYSOUT=*
//DD1 DD DSN=OSBSYS.RM.TEST.SEQVB,
// SPACE=(TRK,(5,1)),
// DCB=(RECFM=VB,LRECL=80),
// DISP=(,CATLG,DELETE),UNIT=3390
//DD2 DD DSN=OSBSYS.RM.TEST.PDSVB,
// SPACE=(TRK,(5,1,1)),
// DCB=(RECFM=VB,LRECL=80),
// DISP=(,CATLG,DELETE),UNIT=3390
//DD3 DD DSN=OSBSYS.RM.TEST.SEQFB,
// SPACE=(TRK,(5,1)),
// DCB=(RECFM=FB,LRECL=80),
// DISP=(,CATLG,DELETE),UNIT=3390
//DD4 DD DSN=OSBSYS.RM.TEST.PDSFB,
// SPACE=(TRK,(5,1,1)),
// DCB=(RECFM=FB,LRECL=80),
// DISP=(,CATLG,DELETE),UNIT=3390
The 2 PDSs end up half track blocked but both sequential files end up
blocksize=0 and so the files cannot be edited. Allocating the same
sequential files via ISPF 3.2 creates them half track blocked.
What other information does SDB need to block the sequential files
correctly in batch?
----------------------------------------------------------------------
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
