The following process summarizes how user name access is handled by TPS:
When TPS is initiated, it checks for the presence of a NGEN28TP/USERS file. If one is present, TPS loads a maximum of 100 valid entries from the file, and sorts by user name. Entries are ignored and ODT error messages are sent if any of the following problems occur:
An entry has invalid syntax.
The file has more than 100 valid entries.
At any time TPS is running, you may force a reload of the NGEN28TP/USERS file by using the LOADUSERS command.
If the NGEN28TP/USERS file is loaded into TPS, then each user wishing to sign on to TPS must enter a valid user name and checkword combination, using a HELLO, USER, or LOGON command. If that user name / checkword combination has an associated CONTROL command level entry in the file, then that user is designated as a CONTROL user, with access to all TPS commands; otherwise they can only access USER commands.
If the NGEN28TP/USERS file is not visible to TPS, no sign-on entry is required, and all users have CONTROL status.
When Report output is received by TPS, the setting of GLB.USER is passed to TPS in a Report output header record (as are other System Data Item values).
The visibility of Report output to TPS users is summarized in the following table.
If … | Then Report Output Is Visible To… |
No NGEN28TP/USERS file is loaded | All users |
GLB.USER is spaces | All users |
GLB.USER or GLB.ALTUSER is not found in NGEN28TP/USER | CONTROL users only |
GLB.USER or GLB.ALTUSER is found in NGEN28TP/USERS | Only users signed on to TPS with either USERNAME |
Note: A TPS user cannot apply commands to TPS backup files unless those files are visible to that user.If the NGEN28TP/USERS file has not been declared or loaded, then GLB.USER is ignored.