Good Catch! I didn't make the connection.
_________________________________________________________________ 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 Gibney, Dave Sent: Thursday, September 04, 2014 3:23 PM To: [email protected] Subject: Re: RSU APPLY ISSUE GIM23911E I could be way off base, but given that the OP just finished a thread where the solution was a mass/conditional zoneedit of his DDDEFs, I would look very closely at which libraries are actually being used and updated by this SMP/E running. An inadvertent mixing of LE levels is scary. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Skip Robinson > Sent: Thursday, September 04, 2014 11:22 AM > To: [email protected] > Subject: Re: RSU APPLY ISSUE GIM23911E > > Guilty as charged; I did not dwell on Doug's posts. Installing the > same PTF and getting a different result raise other questions to be pursued. > There may be a benign explanation that IBM could supply in an SR. I > applied > UI18451 in June and don't see any anomalies the sysout. > > . > . > 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 > [email protected] > > > > From: Doug Henry <[email protected]> > To: [email protected], > Date: 09/04/2014 09:30 AM > Subject: Re: RSU APPLY ISSUE GIM23911E > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > On Thu, 4 Sep 2014 07:32:54 -0700, Skip Robinson > <[email protected]> wrote: > > >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. > > Hi Skip, > If you read my previous reply's you will know that I sucessfully > applied > UI18451 just to test this for him this morning. However he is running > into some fundamental problem . The bind of CEEPLPKA should result in > a return code 0 (not 4). I also have my binder global option set to 4 > but that is irrelevent in this problem because it is being overridden > by the lmod Return Code subentry (it specifies 0). The problem seems > to be with the entries that are autoinclude by the binder don't seem > to have the proper rent reus flag set. As I said before an example is > the module STRXFRM that should be RENT, REUS, REFR . > > IEW2322I 1220 1272 NAME CEEPLPKA(R) MAX > ACCEPTABLE RC=00 > > Doug > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- 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
