It's a major hot button of mine that components sometimes make incompatible changes such that the parms *required* for one release are *unacceptable* to another release. This means that a common member cannot be shared concurrently and also complicates going forward or backward. One workaround that I've had some success with it to use parmlibs associated with specific releases to contain the otherwise incompatible versions. In our case, SYS1.PARMLIB lives away from sysres and is intended to be shared by all members a sysplex. But each sysres volume contains the IBM-supplied library CPAC.PARMLIB. This library comes with ServerPac but--unlike IBM.PARMLIB--is never updated by PTF. Hence any updates you make in CPAC are permanent for the life of that release. So you can effectively create two versions of BPXPRMxx, one in each CPAC library, that are appropriate for the release being IPLed. You could even use version-specific system symbol definitions in IEASYSxx, but I would avoid too much cleverness.
This workaround is sucky on many grounds, the worst of which is that eventually you want to mainstream the 'new' version(s) back into the shared parmlib. Who remembers to do that and when? It's a long-term parmlib management issue, but especially if you're better organized than I am, not an insurmountable one. The key to making this work is to concatenate CPAC.PARMLIB in LOADxx. We put our own parmlib first in order to pick up customized members. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office jesse1.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Field, Alan Sent: Wednesday, February 24, 2016 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Parsing IEASYS00 entries I want to specify a different BPXPRMnn concatenation depending on whether I'm IPLing z/OS 2.1 or z/OS 2.2. The second member has the filesystem mounts and they are different depending on which level of z/OS is IPLing. In SYS1.PARMLIB(IEASYS00) I specify OMVS=(00,&OSLEVEL(2:1)&OSLEVEL(4:1)), However at IPL get BPXI030I THE OMVS= PARAMETER WAS FOUND TO HAVE A SYNTAX ERROR. IEA341A RESPECIFY OMVS PARM OR PRESS ENTER IEE600I REPLY TO 00 IS;OMVS=00 IEE252I MEMBER BPXPRM00 FOUND IN SYS1.PARMLIB Entering the command SET OMVS=(00,&OSLEVEL(2:1)&OSLEVEL(4:1)) I get IEE295I COMMAND CHANGED BY SYMBOLIC SUBSTITUTION ORIGINAL: SET OMVS=(00,&OSLEVEL(2:1)&OSLEVEL(4:1)) MODIFIED: SET OMVS=(00,21) SET OMVS=(00,21) so I put OMVS=00, back in IEASYS00 and I created an MPF exit triggering off the BPXI004I OMVS INITIALIZATION COMPLETE message to issue the SET OMVS=&OSLEVEL(2:1)&OSLEVEL(4:1) as an interim solution. It appears the OMVS= parameter does not like system symbols. Is this correct or have I somehow messed up my coding? Thanks Alan Field Systems Engineer Principal Blue Cross Blue Shield of MN 651.662.3546 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
