Alas, all sysres packs all have the same name. Either mirrored for remote DR or the same physical volumes for local DR. Different Load Profile names on the HMC for a small measure of sanity, but same VOLSERs. So we're in the same (life)boat as you.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile jo.skip.robin...@att.net > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Jerry Whitteridge > Sent: Saturday, January 30, 2016 11:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Manipulating system symbols > > Can you derive the value from your IPL Packs ? Something like: > > SYSDEF SYMDEF(&MVSR1='&SYSR1(1:5).1') > SYSDEF SYMDEF(&MVSR2='&SYSR1(1:5).2') > SYSDEF SYMDEF(&SYSR2='&SYSR1(1:5).1') > SYSDEF SYMDEF(&SYSR3='&SYSR1(1:5).2') > > > Otherwise we have been forced to keep multiple sets of SYSDEF based on the > LPARNAME like : > > SYSDEF LPARNAME(SY01) SYSCLONE(T1) > LPARNAME(SY01) SYMDEF(&PAXC1IN1.='CCA4') > LPARNAME(SY01) SYMDEF(&PAXC1IN2.='CCA5') > LPARNAME(SY01) SYMDEF(&PAXC1IN3.='CCA6') > > And yes - When building new LPARS we have to ensure all the new Symbolics > are setup > > > > > Jerry Whitteridge > Manager Mainframe Systems & Storage > Albertsons - Safeway Inc. > 925 738 9443 > Corporate Tieline - 89443 > > If you feel in control > you just aren't going fast enough. > > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Skip Robinson > Sent: Saturday, January 30, 2016 11:05 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Manipulating system symbols > > I have LPAR-derived symbols--all set via the same clumsy tests I showed > earlier. I created that schema 20 years ago and would like to simplify and > sleeken (is that a word?) it. Here's why I need the function. > > I run system SYSKIP on three different CECs for business reasons. The > underlying LPAR names are different based on CEC--LPSKIP1, LPSKIP2, and > LPSKIP3. All three systems are internally &SYSNAME SYSKIP and look nearly > identical as necessary for 99% of user function. But some resources like > TCP/IP > and VTAM values need to be unique because I cannot have duplicates in the > network. I would like to be able to set symbols like &USRTCP and &USRVTAM > by simply extracting SKIP1/SKIP2/SKIP3 from the LPAR name. Unfortunately > the 'variable' LPARNAME provided for filtering is not actually a system symbol > and cannot parsed into substrings. > > This would be so easy in even a rudimentary programming language. I've > considered doing it in a Rexx that would set symbols via the new z/OS V2 > mechanism, but all this needs to happen very early in a serialized, primal > state > such as IEASYMxx before anything else kicks off. For the record, the LPARs on > the various CECs are used for production or some flavor of disaster recovery. > That's why each system needs to 'look the same' in each LPAR. > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > jo.skip.robin...@att.net > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Steve Horein > > Sent: Saturday, January 30, 2016 10:16 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: [Bulk] Re: Manipulating system symbols > > > > Are your LPARs related to other things such that you could then take > > advantage of Symbol substring? > > http://www- > > > 01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieae2 > > 00/usesubs.htm > > > > > > On Sat, Jan 30, 2016 at 10:47 AM, Skip Robinson > > <jo.skip.robin...@att.net> > > wrote: > > > > > For the first time in ages we are in the process of enhancing our > > > inventory of user defined system symbols (IEASYMxx). I jumped out > > > half-cocked and attempted to set a symbol equal to the name of the > > > current LPAR. That sounds easy, but I cannot find an simple way to > > > do it. Even pored over the V2R1 doc, which looks much as I remember > > > it from 1995. > > > > > > > > > > > > There are three names that can be used in SYSDEF statements: HWNAME, > > > LPARNAME, and VMUSERID. However, these are available only for > 'filtering'. > > > That is, I can do something like > > > > > > > > > > > > SYSDEF LPARNAME(LPARSKIP) /* If LPAR name is this */ > > > > > > SYMDEF(&USRLPARN='LPARSKIP') /* Then set user symbol to this */ > > > > > > > > > > > > The problem is that I have to have a separate pair of statements for > > > every LPAR in the Enterprise. If a new LPAR gets created, I have to > > > clone a new pair of statements. > > > > > > > > > > > > What I would like is to be able to set &USRLPARN directly to the > > > name of the current LPAR whatever it is. One statement that would > > > serve everywhere and never need cloning. Am I missing something > obvious? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
