Work Management Standards › User Profile and Security Standards › User Profiles › Naming Convention for User Profiles
Naming Convention for User Profiles
The user profile name will appear on reports, dumps, and logs. For this reason, it is helpful for both operations and problem shooting if, as well as uniquely identifying the individual user, it can indicate what the user’s role is, i.e. some operational grouping. For end users the most significant grouping tends to be by department, or for developers by the project on which they are working. A two-part convention is therefore recommended for user profile names:
Prefix—Prefix one to four characters long indicating a department or project (see the section, End-user Profiles and Development profiles in this chapter).
- Each prefix will generally correspond to a group profile.
- The prefix ‘Q’ should be reserved for IBM shipped files, for example, QSYS, QPGMR.
- A three-character mnemonic created according to the normal CL conventions is preferable; for example, ‘ACC - Accounts’, ‘SLS -Sales’. However, this is not always practical if there are a large number of profiles or if it is useful to encode additional information in the prefix.
Identifier—One to six character unique identifiers of users.
- Ideally, such an identifier should be short, simple, extendable, and unique. Initials are more likely to succeed than names or surnames.
- A null identifier is used on group profiles (for example, blank).
- Identifiers representing roles, for instance the group security officer, can be named using standard three character CL mnemonics.
Examples:
- ACC\-—Accounts department
- ACC_ES—Accounts - Ernest Saunders
- ACC_RC—Accounts - R.Calvi
- ACC_IB—Accounts - Ivan Boesky
- ACCUSRPRF—Accounts - Profile to copy for new users
- ACCSECOFR—Accounts - Security officer/administrator
- YBOTHER—Panacea product
