I don't know if this helps, but APAR OW36048 contains the following information:
If you found incorrect data set names for any DDDEFs in your primary target zone and have already installed maintenance on the new system, IBM recommends that you run the SMP/E REPORT CALLLIBS command against this zone now. Then run the CALLLINK job generated by SMP/E. This will ensure that load modules containing external references are link-edited correctly on your system. This APAR was closed in 1998, but may still be applicable. By the way, it specifically notes that if your serverpac order did not have C/370 that the DDDEF for SEDCBASE would be directed to CEE.SCEELKED. I've never run CALLLIBS or CALLLINK, so I don’t know what they do, so proceed with caution. Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mainframe Mainframe Sent: Tuesday, September 09, 2014 9:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: RSU APPLY ISSUE GIM23911E THanks .But my initial serverpac came without C/370 product and we installed like below REP DDDEF(SEDCBASE) DA(CEE.SCEELKED) VOLUME(RES001) UNIT(3390) WAITFORDSN SHR . But later when I received CBPDO from from IBM for C/370, it allocated SEDBASE dataset but as DDDEF was pointing to SCEELKED, so data related to this FMID went to SCEELKED and SEDBASE is empty for me . ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
