On Tue, 8 Oct 2013 08:14:44 -0700, Skip Robinson <[email protected]> wrote:
>The last couple of posts in this thread have overlooked Andy Higgins's >observation that &SYSR1--or any symbolic for that matter--cannot be used >to catalog a data set in the PARMLIB concatenation. The reason is that >symbolics are defined in PARMLIB members that themselves cannot be located >and processed until NIP knows how to find PARMLIB data sets. It's a >chicken-egg problem. > > &SYSR1 is a special case and is available to resolve the VOLSER, even in LOADxx. It can't be used to resolve a data set name however prior to symbol processing. For example, LOADxx can NOT use PARMLIB SYS1.PARMLIB.&SYSR1 So it can be used anywhere ****** is used in catalog entries. I disagree with Mr. Gilmore's assertion that it "should" be used. They are logically equivalent, so i wouldn't go recatalogging all my master catalog data sets "just because". Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] ITIL v3 Foundation Certified Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
