When I run your JCL, I get: IEFC620I UNIDENTIFIABLE CHARACTER ; ON THE DD STATEMENT
Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roland Kinsman Sent: Friday, July 17, 2015 4:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: HISTORIC RETURN CODE IS 196 DIAGNOSTIC INFORMATION IS 0C060090 This JCL... //STEP01 EXEC PGM=IEFBR14 //ALC DD DSN=&&XX00500, // DISP=(NEW,CATLG,DELETE), // DSNTYPE=LIBRARY, // UNIT=VIO, // DCB=(RECFM=U,LRECL=0,BLKSIZE=27998,DSORG=PO), // SPACE=(CYL,(25,5,200)) works fine on one LPAR. On another LPAR, which happens to be a zPDT, it fails with the following error messages: IGD17040I ERROR IN DADSM PROCESSING ON VOLUME UNKNWN FOR DATA SET SYS15198.T160706.RA000.HCHRJK0A.XX00500.H01 HISTORIC RETURN CODE IS 196 DIAGNOSTIC INFORMATION IS 0C060090 IGD306I UNEXPECTED ERROR DURING IGGDAC02 PROCESSING RETURN CODE 12 REASON CODE 144 THE MODULE THAT DETECTED THE ERROR IS IGDVTSDA SMS MODULE TRACE BACK - VTSDA VTSCR SSIRT SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00000 It seems the key message is... HISTORIC RETURN CODE IS 196 DIAGNOSTIC INFORMATION IS 0C060090 Which seems to suggest that PDSE cannot be allocated on VIO. So why does it work on one LPAR but not the other? It's making me a little crazy. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
