Thanks Kurt Q. for your assistance. I'm not a systems programmer (even though, for requirements of my job I've been granted RACF authority to use the dreadfully dangerous SMP/E -- that *really* ought to be fixed), so I don't know how things got out of sync, nor where to find matching instances. I can ask.
And, on further review, I note that GIM69217I is followed by a Serious error for RECEIVE FROMNETWORK, but only Informational for RECEIVE FROMNTS. On Thu, 9 Jan 2014 10:01:13 -0600, Mark Zelden wrote: >"Happens all the time" ?? This should never happen unless you are testing a >new >level of SMP/E via STEPLIB and don't also point to the maintenance z/OS root >file system. It most likely indicates that either maintenance was a applied >to >the live system or cloning the z/OS root file system wasn't done along with the >rest of "classic" data sets for the sysres set or visa versa - maintenance >applied to the live root, but maintenance version of "classic" MVS data sets. > Is this "cloning", sometimes called "deployment" to a live system? It seems there's a flaw in the process if the live system is not updated by a process identical to that used on the maintenance system. Either the maintenance system should be cloned to a test system and tests performed there, or (most safely), once tests have been performed on the maintenance system, maintenance should be applied to the production sytem by SMP/E APPLY identically as it was done on the maintenance/test system. None of which would have protected me: I'm nearly the only person doing what I tried; it probably wouldn't have been tested. >On Wed, 8 Jan 2014 22:52:40 -0600, Alan Field wrote: > >>This happens to me all the time. After applying maintenance to SMP/E >>you've updated the SMPCPATH dataset which has now got out of synch with >>the rest of SMPE. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
