Some shops use ACS routines to convert UNIT=VIO to a "real" DASD allocation, preferring to use outboard DASD (with all their built-in memory-based cache) in preference to CEC memory.
Perhaps the first LPAR has that policy and your zPDT is configured to use memory for VIO? Not sure if there really is a restriction from allocating PDSE on VIO, but it would not surprise me. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Roland Kinsman Sent: Friday, July 17, 2015 5:42 PM To: [email protected] 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 [email protected] with the message: INFO IBM-MAIN This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
