The output shows this: IN LMOD CEEPLPKA IN THE SCEERUN LIBRARY. THE RETURN CODE (04) EXCEEDED THE ALLOWABLE VALUE. DATE 14.247 - TIME 02:35:37
It's not at all uncommon for the binder to return code 04 for various reasons that are not actually 'problems'. In this case we see messages about conflicting module attributes. This happens. Life goes on. It's way less dangerous than, say, global warming. The real problem here is that SMPE is being too prissy. If 04 'exceeded the allowable value', then the allowable value is set too low. 04 is only a warning after all. Go into the SMPE dialog and examine the GLOBAL UTILITY options for entry LKED. If it says 'RETURN CODE: 0', you will incur never ending grief now and in the future. Because of your LKED entry, SMPE turns 04 into 08. Our 2.1 SMPE environment has already been tailored for us, so I can't tell how it came out of the box. Now it's set to 'RETURN CODE: 4', which we've used for as long as I can remember. This way we get 08 only for real problems. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Lizette Koehler <stars...@mindspring.com> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 09/04/2014 07:16 AM Subject: Re: RSU APPLY ISSUE GIM23911E Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> For this type of error I look at the following 1) JOBLOB of the SMP/E Job a. Are there any issues for the Datasets in the messages? b. Are there any IGD messages or Space issues 2) SMPRPT a. What messages are there for the PTF b. UI18451 does it have any PTFs with it that did not go on? 3) What other error messages are found in and about that PTF? That Library? That Load Module a. If there are no supporting messages that make sense on why it Failed b. Look through IBM Link (SR/ETR) and see if there has been an issue reported for the PTF during SMP/E Processing c. Open a CASE with IBM for that product to determine why it failed Unless you post your entire JOB LOG and SMPRPT and LINK output, hard to say why it failed. I might also like to see the DDDEF report to make sure the files are on the correct DD Statement. The reason to open a CASE to Language Environment is because it is their SMPE process. SMPE probably did exactly what it was supposed to do. However, something failed in the process. You may need to ask Language Environment if they have any issues with this PTF. Why do LKED process fail? Many reasons, Space, Incorrect dataset type (PDSE vs PDS), missing data set in SYSLMOD, and probably others. There should be messages in the SMPE JOB output that can clarify for you what is not quite correct. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Kurt Quackenbush > Sent: Thursday, September 04, 2014 5:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: RSU APPLY ISSUE GIM23911E > > > GIM23911E ** LINK-EDIT PROCESSING FOR SYSMOD UI18451 FAILED > FOR MODULE > > CEEZIDT > > IN LMOD CEEPLPKA IN THE SCEERUN LIBRARY. THE RETURN > CODE (04) > > EXCEEDED THE ALLOWABLE VALUE. DATE 14.247 - TIME 02:35:37 > - > > SEQUENCE NUMBER 000092 - SYSPRINT FILE SMP00040. > > > > when I checked SMP00040, I didnt find much info except > > > > IEW2322I 1220 1 INCLUDE SMPWRK3(CEEHDSP) UI18451 > > IEW2322I 1220 2 IDENTIFY CEEHDSP('UI18451') > > IEW2322I 1220 3 SETSSI 01118451 > <snip> > > The SMP/E messages are telling you there was a problem linking load module > CEEPLPKA. Find the binder output for that link edit operation (literally, Find > CEEPLPKA) and you should see something more meaningful than you've pasted > here. > > Kurt Quackenbush -- IBM, SMP/E Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
