Filter
Top Products
readable, such as, a file called MASTER.PAYROLL.WEEKLY. This might be just
too tempting to your average system hacker. A better choice might be
MR.PY.WK.
C.2.4 User Name
This qualifier should allow the end creator to assign their own unique name to
identify the particular set of a certain type of data; for example, with a master
circuit file, there would be a distinction between MYPART and YOURPART, or
MYPART1 versus MYPART2. Some other examples of these are:
•
Part number (#0135678)
•
Print program (PRTPROGM)
•
New York Area (NEWYORK)
•
X15 Model (X15MODEL)
•
Geological site #458 (GEO#458)
•
Branch office #57 (BROFC057)
The intent of this level of qualification is to uniquely identify one piece of a type
of data from another piece of the same type of data. Examples of this show the
distinction between ″TELPHLOG.NEWYORK″ and ″TELPHLOG.CALIF″ or between
″PGMSRCE.MYPGM1″ and ″PGMSRCE.MYPGM2″. This should use the entire
qualifier (that is, all of the eight characters).
C.2.5 Data Set Level
Another level of qualification that is sometimes useful in application areas is the
level of the piece of data. Some examples of this are listed below:
•
Design level or version or release level (for example, for engineering,
programming, documentation)
•
Change number, an arbitrary number to indicate a constantly increasing
number for subsequent improvements on a piece of data
•
Cyclic level (for example, yearly, monthly, weekly, daily)
C.3 Things Not to Include in the Data Set Name
There are certain pieces of information that should never be part of the data set
name. The general category of this data is that information which is very likely
subject to change. This type of qualification usually doesn′t add anything
meaningful in terms of identifying the data for storage management reasons.
Some examples of this are shown in subsequent sections.
C.3.1 Department Number
This is a piece of information that is sure to change either due to
re-organization, or movement of projects or individuals.
Appendix C. DFSMS Naming Conventions 547