−E3380D
−E3380S
−E3990M3
−E3990M2
The above example would allow various filtering techniques the flexibility of
recognizing different sets of data easily. Some examples of this follow:
•HLQ = E* -- All of the Engineering Data
•HLQ = E3090* -- All of the 3090 CPU Family of Designs
•HLQ = E3380* -- All of the 3380 DASD Family of Designs
C.2.2 Relative Importance
This level of qualification might indicate things such as:
•Production Data
•Development Data
•Test Data
In general, it would be important to be able to recognize the distinction between
production data and test data. Other types of levels could be:
•Master Data
•Update Data
•Work Data
C.2.3 File Contents
This level of qualification should state what the data is. For example, an
application strips some information out of the master database and builds a work
file for subsequent processing. This file contains the employee id number and
his job code. One might then call this file the ″employee- job code file″. Other
examples might include such things as:
•Telephone call log (TELPHLOG)
•Parts inventory file (PRTINVEN)
•Parts unit cost file (PRTUCOST)
•Payroll file (PAYROLL)
•Checking account transaction file (CHKXACTN)
•CADAM circuit design file (CKTDESGN)
•Heat dissipation statistics file (HEATSTAT)
•Simulation result file (SIMRSLTS)
•Program source (PGMSRCE)
•Life insurance account file (LIFEACCT)
•User′s Manual script file (USMANUAL)
•Input manufacturing file (INPMANUF)
•Transportation bill of lading file (XPRTBILL)
All of the above examples describe what the data is. There should be a unique
character code for each data set type within a given application. This concept is
demonstrated with each of the examples above.
Note: Eight characters have been used as the standard for the data set type in
all of the above examples. This is probably a reasonable number of characters,
although not mandatory. It may not even be a good idea to make file names too
546 VSE to OS/390 Migration Workbook