I really don't think this is a packaging error; as noted by Tom Conley, those are exceedingly rare. If one occurs, there should be a lightning quick HOLD record that would show up in any APPLY attempt. The date on the 'offending' PTF is mid 2017; we're not looking at something hot off the press. I'm convinced that this is a user error, perhaps from long ago. Go ahead and open a case, but my money is on a past APPLY failure. This sysmod BTW is TCP/IP HIP6220, SUP in z/OS 2.3 by HIP6230.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: Monday, August 26, 2019 10:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: GIM38201E and GIM31901I It's been a while, but my default mode is to track down what's wrong with the packaging, contact the vendor and work with him to resolve it. Except in emergencies I don't develop my own workaround. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Lizette Koehler <stars...@mindspring.com> Sent: Sunday, August 25, 2019 9:56 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GIM38201E and GIM31901I When I have these types of issues, I go back to the vendor to find out what is needed to resolve the issue. This could be something in the way they coded the SMP/e fixes or in the way I am trying to apply maintenance. I do not do anything fancy with maintenance. If you could post your SMP/e control cards - there might be something we see in the way they are coded. I usually do a APPLY CHECK Bypass(HOLDSYS) S(x y z) . From what I have seen over the years, this usually will work. And I will tend to use the SMP/e panels in ISPF to build my JCL. Saves a lot of time in building the jobs. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Peter > Sent: Sunday, August 25, 2019 12:21 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: GIM38201E and GIM31901I > > Hi > > I am apply RSU for our zOS system. I am receiving a error message > > GIM38201E ** THERE IS A MODID ERROR FOR MOD ENTRY EZBTCRDF IN SYSMOD > UI34556 > > GIM31901I SYSMOD UI34556 DOES NOT SPECIFY UI46897 ON PRE OR SUP OPERAND. > UI46897 IS THE RMID FOR MOD EZBTCRDF THAT IS CURRENTLY INSTALLED. > > GIM22601I APPLY PROCESSING FAILED FOR SYSMOD UI34556. > > Does it mean the PTF UI46897 applied should be restored and modify its > MCS to add UI34556 as its PRE ? > > Is my understanding correct? > > Could someone please shed light on ? > > zOS 2.2 > > Peter > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
