Yea, I saw that same APAR. At this point we are all guessing, but it seems like maybe he tried to apply the native c/370 FMID ontop of serverpac. At this point, I think the best advice would be for the OP to open a PMR with IBM on how to proceed. I was honestly surprised that the C/370 compiler has not been sunsetted yet.
_________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Greg Shirey Sent: Tuesday, September 09, 2014 12:01 PM To: [email protected] Subject: Re: RSU APPLY ISSUE GIM23911E 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:[email protected]] On Behalf Of Mainframe Mainframe Sent: Tuesday, September 09, 2014 9:51 AM To: [email protected] 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 [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
