Actually our naming conventions are
Production MVS.prod.*(.lpar) SYSX.prod.*(.lpar)
(.lpar) if I need LPAR specific datasets
Install/Test MVS.prodVnnn.*
SYSX.prodV99.* which is a linklisted copy of a
MVS.prodVnnn.* load although I could realistically
use SYSX.prod.*.lpar for the sandbox
Assuming the datasets are made large enough I never have to change
linklist/lpalist or JCL/PROCs for production and only occasionally
JCL/PROCs for testing
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Ted MacNEIL
Sent: Monday, June 14, 2010 4:56 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: [IBM-MAIN] Linklst; 6 of 1/half dozen of the other?
>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).
I don't like versions in LNKLST datasets.
I have no problem with them in maintenance or steplibs.
But, regardless of the HLQ, they should not have versioning in the
production environment, IMO.
-
Too busy driving to stop for gas!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
