I mis-wrote. My LPALSTxx and PROGxx do not utilized the &SYSR1 variable. Only on the APF statements is it used. Sorry for the confusion.
All the datasets except for the VSAM (ZFS) on my the volume I use for SMP/E target and IPL are cataloged with &SYSR1 for the volume name. Even SYS1.NUCLEUS, SYS1.LPALIB, and SYS1.LINKLIB, which must be on the IPL volume anyway. Except for SYS1.PARMLIB and SYS1.PROCLIB, which are cataloged using ****** for the volume name. I've had IPL issues when not using that convention. But usage of that special volume name implies they are on the IPL volume. On Thu, 29 Aug 2019 12:49:47 +0000, David Spiegel <dspiegel...@hotmail.com> wrote: >Hi Matthew, >That is not the same as CATALOGing Datasets to VOL(&SYSRx). > >Regards, >David > >On 2019-08-29 08444, Matthew Stitt wrote: >> On my systems, I use the volume parameter of the LPALSTxx, PROGxx, etc. >> Volume is set to &SYSR1 (or &SYSR2 (on mod-54, so not needed now) ). Have >> no issues with IPL using this method. >> >> Matthew >> >> On Thu, 29 Aug 2019 10:58:15 +0000, Richards, Robert B. >> <robert.richa...@opm.gov> wrote: >> >>>> So, has anyone IPL'd z/OS 2.2 or higher with the data sets on the sysres >>>> catalogued to volume &SYSR1. instead of volume ****** ??? >>> Not in my shop (z/OS 2.3). All my references to &SYSR1. are all contained >>> in IEASYM00 and are used to substring its first four characters for the >>> setting of &SYSR2., etc. >>> >>> Bob > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
