Either way works. It's more about what you are comfortable with (even if you are OCD/anal). I always felt the trick was to pick one and stick with it and not mix the two.
Personally I prefer a unique HLQ for ISV datasets in the mastercat (e.g. SYSX.prodver.*) and non mastercat entries as MVS.prodver.* (for example). Alan, you run with 9 character qualifiers? -----Original Message----- Starr, Alan IEASYM00 defines &MVRVIEW as 'V01R11M00' SYSV.CAVIEW.V01R11M00.CAILINK is catalogued in a UCAT to VOL(&SYSL2) SYSV.CAVIEW.CAILINK is catalogued in a UCAT as an ALIAS SYMBOLICRELATE(SYSV.CAVIEW.&MVRVIEW..CAILINK) Regards, Alan -----Original Message----- Gibney, Dave I prefer to have the ISV datasets in LINKLST statements in PROGxx cataloged in the master catalog and not use volume references. My co-worker doesn't think it as a big deal and usually uses a load library cataloged in the ISV usercat and a volume reference. Am I just being anal (I really don't like volume references in parm members anywhere I can avoid them), or is the a legitimate concern that would support either position? We place such datasets on Non-SMS volumes shared between the four LPARS. We do not share master catalogs or in most cases user catalogs. Dave Gibney Information Technology Services Washington State University ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
