It is true that you cannot ask the catalog processing to resolve any symbol other than ******. But you can specify a volser either of ****** or &SYSR1 within the LOADxx definition.
This update was made in OS/390 R6. Andy H pointed to the documentation: "If '******' or '&SYSR1' is specified, IPL processing will attempt to locate the specified data set on the system residence volume. " This is correct. Mark Z pointed to The following cannot be catalogued with a system symbol: SYS1.PARMLIB Any parmlib data set listed in LOADxx without a volume name. More complete for the SYS1.PARMLIB line would be "SYS1.PARMLIB unless listed in LOADxx with a volume name". SYS1.PARMLIB is added for you by default *unless* you specify it. So if you allow it to be added by default, then you are asking the system to resolve the catalog entry's special symbol and that cannot be done. If you specify it, then the line about "any parmlib data set" applies. If you like that clarification, let me know and we can get that updated. >We stil have in PROGxx: >APF ADD DSNAME(SYS1.LINKLIB) VOLUME(******) >I am not sure if it is still necessary. APF ADD does not do catalog lookups. The choices are between specifying the volume (and here you could use ****** or &SYSR1) and indicating that the data set is SMS-managed (and thus is deemed APF-authorized regardless of on which data set it lives according to the catalog. So you need the volume specification. You could just use &SYSR1 if you chose (but I too would not bother changing, unless you have nothing better to do; ****** will always be supported). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
