Peter Ten Eyck wrote:
Confusion about model DSCBs...
z/OS V1R3.0 DFSMS: Using Data Sets states:
3.9.5.1.2 Creating a Model DSCB
You can create a model DSCB on the volume on which your index resides.
Restriction: You cannot use a model DSCB for system-managed generation data
sets.
...
At our shop we run something like this:
//TSGEN JOB CLASS=S
//STEP1 EXEC PGM=IEBGENER
//SYSUT1 DD DSN=TECH.TEST.INPUT(0),DISP=SHR
//SYSUT2 DD DSN=TECH.TEST.OUTPUT(+1),
// DISP=(NEW,CATLG,KEEP),UNIT=DISK,
// SPACE=(TRK,(1,1,)),DCB=(SYS2.DSCB)
//SYSOUT DD SYSOUT=Q
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=Q
//
Where both SYSUT1 and SYSUT2 are SMS managed datasets. This seems to
contradict the restriction above.
Does anyone have any comments on this restriction?
Yes.
Your DSCB model is not the same as "GDG DSCB model". The latter is
zero-track VTOC entry on the same volume when all the GDD datasets are
to be placed and its name is the same as GDG base. That's why it cannot
be cataloged, so cannot be SMS-ed as well. However it is prehistory.
In SMS environment you don't have to use any DSCB modelling at all.
The above DD without "DCB=" should work as well.
For non-SMS GDG datasets modeling is still required, I don't know why,
but it is. However it can be "regular, non-GDG" modeling, like yours, or
even DATACLAS= (still for non-SMS managed datasets).
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
