I've been working through some issues on a system that uses non-SMS datasets, which mostly works the way I expected.
But I have noticed that something that odd works on SMS managed datasets and volumes fails without SMS. For example: //GENER EXEC PGM=IEBGENER //SYSUT1 DD DSN=KIRK.TEST.MVOLIN,DISP=SHR 30 tracks of FB/80 data //SYSUT2 DD DSN=KIRK.TEST.MVOL, // DCB=(RECFM=FB,LRECL=80), // UNIT=(3390,2), // VOLUME=(,,,2,SER=(VPWRKE,VPWRKF)), // SPACE=(TRK,(1,1)), // should use 15 1-trk ext on 2 vols // DISP=(NEW,CATLG) //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //* On a system with SMS managed datasets and volumes, this works fine. But without SMS, it gets: IEC027I 737-04,IFG0194D,CRTMVOL,GENER,SYSUT2,0D35,VPWRKF,KIRK.TEST.MVOL So it can't find the F1 DSCB on VPWRKF - the second volume. I always figured that creating this was automatic, but maybe only with SMS managed? Other googles for ABEND737-04 point to issues with multi-volume IMS OSAM datasets, where IBM seems to prescribe that you must first allocate each volume (without cataloging) separately: https://www.ibm.com/support/knowledgecenter/en/SSEPH2_13.1.0/com.ibm.ims13.doc.sdg/ims_sag42.htm If this is just the way that it works, fine, but I was hoping that someone on list could shed some light on this darkness. Regards, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
