IBM OS/390 User Manual
individuals keep a standard LOGON ID, and change the set of filters instead of
the IDs.
the IDs.
As an example of this set of conventions, consider a common problem of
constantly shifting workloads. If the Storage Administrator was always faced with
getting the data for a given application and moving it to another system, then it
would make good sense to have a naming convention for the HLQ that would
allow him to easily accomplish this via filtering techniques. Other reasons are for
data portability to other installations for disaster/recovery situations that would
cause an application to be brought up on an alien system.
constantly shifting workloads. If the Storage Administrator was always faced with
getting the data for a given application and moving it to another system, then it
would make good sense to have a naming convention for the HLQ that would
allow him to easily accomplish this via filtering techniques. Other reasons are for
data portability to other installations for disaster/recovery situations that would
cause an application to be brought up on an alien system.
One example of a naming convention for HLQs might be the following:
•
First Character:
−
A - Accounting Support
−
D - Documentation
−
E - Engineering
−
F - Field Support
−
M - Marketing Support
−
P - Programming
−
$ - TSO user ID
An alternative here is to use one of the characters above as the first
character of the TSO user ID to allow movement of all data within an
application (including the TSO data). This is not the way recommended
by the author -- the preference would be a standard code for TSO, such
as
character of the TSO user ID to allow movement of all data within an
application (including the TSO data). This is not the way recommended
by the author -- the preference would be a standard code for TSO, such
as
″
$
″.
The above list does not represent all of the possibilities. For example, a
bank might have separation of HLQs by major application such as
checking, savings, mortgage loans, investments or ATM. An insurance
company might have applications such as life, auto, personal insurance,
major medical and corporate accounts.
bank might have separation of HLQs by major application such as
checking, savings, mortgage loans, investments or ATM. An insurance
company might have applications such as life, auto, personal insurance,
major medical and corporate accounts.
−
Remaining Characters = Project Name or Code Number
Note:
This might have been chosen because a project code might exist
for programming, engineering, documentation, and accounting, but it
does not imply that one must do it that way. It has been the experience
of the author that similar project codes would not be common.
does not imply that one must do it that way. It has been the experience
of the author that similar project codes would not be common.
A more natural idea is to have the actual project name following the first
character. For example, the remaining portion of the
character. For example, the remaining portion of the
″
E
″
project could be the
code name of the machine being designed, while a
″
P
″
project could be the
name of the programming application or product name.
Some examples might be:
−
E3090M150
−
E3090M200
−
E3090M300
−
E3090M400
−
E3090M500
−
E3090M600
−
E3380K
−
E3380J
Appendix C. DFSMS Naming Conventions
545