There is a pretty good description of Symbols, rules, substrings etc in Chapter 2 of MVS Init and Tuning Reference. Section titled "Using system symbols in parmlib" ... <joke alert> otherwise know as USSiP </joke alert>
Rob Schramm Senior Systems Consultant Imperium Group On Sun, Apr 8, 2012 at 8:29 AM, Jake anderson <[email protected]> wrote: > Thanks a lot for your precise explanation. > > On Sun, Apr 8, 2012 at 7:46 AM, retired mainframer <[email protected] >> wrote: > >> :>: -----Original Message----- >> :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On >> :>: Behalf Of Jake anderson >> :>: Sent: Saturday, April 07, 2012 6:58 PM >> :>: To: [email protected] >> :>: Subject: Coding IEASYMxx >> :>: >> :>: Hello All, >> :>: >> :>: First of all apology for asking a very basic question and being >> :>: ignorant.In >> :>: our shop we have two sysres volumes MTSRS1, MTSRS2,MSTRS3 so during >> :>: SYSRES >> :>: cloning we adopt indirect cataloging. Also it is important to specify >> :>: the >> :>: symbolic parameter at IEASYMxx member. My only basic question is that >> :>: will >> :>: it be wise enough to code like below : >> :>: >> :>: SYMDEF(&SYSR2='MTSRS2') >> :>: SYMDEF(&SYSR3='MTSRS3'). >> >> If you code it like this, then when you have a second set of SYSRES >> volumes, >> say TSTRS1, TSTRS2, TSTRS3, &SYSR1 will resolve to TSTRS1 as you want but >> &SYSR2 will still resolve to the MTSRS2, not TSTRS2. >> >> :>: >> :>: I have referred the link >> :>: >> http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fco >> :>: m.ibm.zos.r12.ieae200%2Fplnsym.htm >> :>: but I am not really able to understand the below coding when we more >> :>: than >> :>: 1 sysres volumes : >> :>: >> :>: :SYSDEF . >> :>: >> :>: . >> :>: SYMDEF(&SYSR2='&SYSR1(1:3).RS2') /* second SYSRES logical >> :>: extension */ >> >> This code says set the value of &SYSR2 to the first three characters of >> &SYSR1 followed by the characters RS2. When you IPL from MTSRS1, the first >> three characters of &SYSRS1 are MTS so &SYSRS2 resolves to MTSRS2. And >> when >> you IPL from TSTRS1, the first three characters are TST so &SYSR2 will >> resolve to TSTRS2. This insures that &SYSRS1, &SYSRS2, and &SYSRS3 always >> resolve to the three volumes that are part of a matched set. >> >> :>: SYMDEF(&SYSR3='&SYSR1(1:3).RS3') /* third SYSRES logical >> :>: extension */" >> :>: >> :>: >> :>: Could anyone please explain me about the above syntax. How to make use >> :>: the of the above syntax reasonably. >> >> The only change you need to make to the above is to decide how many volumes >> are involved. My last system (1.11) had only two 3390-9s so I didn't >> bother >> with &SYSRS3. >> >> ---------------------------------------------------------------------- >> 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
