NET/MASTER Management Services (MS) Command Reference Manual

LBANNER
PROGRUN
NonStop NET/MASTER MS Commands
115412 Tandem Computers Incorporated 2–289
Considerations
The default authority level of the PROGRUN command depends on whether your
installation permits the use of both Format 1 and Format 2, or Format 2 only.
If your installation permits the use of both Format 1 and Format 2, the default
authority level of Format 1 is 0. (The authority levels are set in the INIT NCL
procedure.)
The authority level of each Guardian utility that is available using Format 1 is
defined using the Maintain Utility Command Set Definitions option in UMS.
When you follow the PROGRUN command by a utility name, your authority
level is checked against the authority level of the individual utility to
determine whether you can access the utility.
If your installation permits the use of both Format 1 and Format 2, the default
authority level of Format 2 is 255. The authority level of Format 2 (the
unrestricted PROGRUN command) is defined in the Maintain Utility
Command Set Definitions option in UMS.
If your installation permits the use of Format 2 only, the default authority level
of Format 2 is 2.
You can enter this command from any NCL procedure, except the INIT NCL
procedure, by using either the CMD core statement or the INTCMD verb. If you
enter the command from an NCL procedure, you must execute it from an NCL
procedure that sends the results of the command to a terminal.
Guardian utilities available using Format 1 are defined using the Maintain Utility
Definitions option in UMS. The authority level of each Guardian utility that is
available using Format 1 is defined using the Maintain Utility Command Set
Definitions option in UMS. Default authority levels for Guardian utility
commands are listed in Appendix A, “Default Authority Levels for Guardian
Utility Commands.”
This command supports both conversational and block-mode Guardian utilities.
It is recommended that you use the OPSYS command rather than the PROGRUN
command to start and terminate interactive sessions with conversational Guardian
utilities.
If a terminal timeout period should occur while a process has control of a terminal,
the timeout action is initiated when NonStop NET/MASTER MS regains control of
the terminal.
NonStop NET/MASTER MS queues messages arriving for display at a suspended
terminal. If a process retains control of a terminal for a long time, then messages
may be lost. Messages lost from display at an OCS window are still logged in the
activity log. You can use Log Browse to examine them later when control returns
to NonStop NET/MASTER MS.