Wow, I love this kind of problem. I ran the following JCL with IEFBR14:
//NEWGUY1 DD DISP=(NEW,DELETE),SPACE=(TRK,1),DSN=TED066.TEST
//NEWGUY2 DD DISP=(NEW,DELETE),SPACE=(TRK,1),DSN=&&TEST
//NEWGUY3 DD DISP=(NEW,DELETE),SPACE=(TRK,1)
The resulting allocations shown below differ in two ways: real DASD vs.
VIO, and short vs. long (near max) data set name. I've seen cases where a
program would not work with VIO data sets; usually an ISV product that was
(or should have been!) documented as such. The length of the data set name
may be significant if the application for some reason obtains the data set
and stores it somewhere: the longer *generated* name may overlay some
buffer or work area.
IGD101I SMS ALLOCATED TO DDNAME (NEWGUY1 )
DSN (TED066.TEST )
STORCLAS (STANDARD) MGMTCLAS (STANDARD) DATACLAS (STAND1)
VOL SER NOS= ARN030
IGD101I SMS ALLOCATED TO DDNAME (NEWGUY2 )
DSN (SYS06054.T203308.RA000.TESTALLO.TEST.H01 )
STORCLAS (STANDARD) MGMTCLAS ( ) DATACLAS (STAND1)
VOL SER NOS= VIO
IGD101I SMS ALLOCATED TO DDNAME (NEWGUY3 )
DSN (SYS06054.T203308.RA000.TESTALLO.R0170562 )
STORCLAS (STANDARD) MGMTCLAS ( ) DATACLAS (STAND1)
VOL SER NOS= VIO
.
.
JO.Skip Robinson
Southern California Edison Company
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
IBM Mainframe Discussion List <[email protected]> wrote on 02/23/2006
09:26:39 AM:
> Hi All. Once again I look to the group for help. I am at a total
> loss and have test extensively. This is the issue:
>
> If I use the following && JCL the job fails consistently with an 0C4:
> //WORK01 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(4300,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK01
> //WORK02 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(4300,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK02
> //WORK03 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(900,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK03
> //WORK04 DD DISP=NEW,UNIT=SYSDA,SPACE=(CYL,(900,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=&&WORK04
> I have 4 PUBLIC volumes.
>
> If I use this JCL which uses permanent datasets the job works everytime:
> //WORK01 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK1,
> // VOL=SER=BACK09
> //WORK02 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK2,
> // VOL=SER=BACK09
> //WORK03 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK3,
> // VOL=SER=BACK09
> //WORK04 DD DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(5,5)),
> // LRECL=8192,BLKSIZE=0,RECFM=VB,DSN=TRAM1.WORK4,
> // VOL=SER=BACK09
>
> Can anyone offer suggestions as to why &&work is not working. We are
> OS390 V2R10 and the program is written LE. I do not have the source
> because it was given to us by the agency we feed the data too. In
> advance thanks all.
----------------------------------------------------------------------
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
