Use the PROGRUN command to run local or remote block-mode applications such as DSM/PM, T/Mail, OMF, and ViewPoint. The PROGRUN command suspends your terminal output as long as the process is running. You can communicate interactively with the application and receive the result of commands, but NonStop NET/MASTER MS cannot intercept the exchanges with the process, and there is no record of the responses to commands issued when you return to NonStop NET/MASTER MS. The PROGRUN command can also be used to run conversational applications, but you should restrict its use to block-mode applications (see the caution, below).
The Console Extras facility provides a user interface that facilitates your use of the PROGRUN command. See “The Console Extras Facility,” later in this section. When you start a program using PROGRUN, you must exit the program to return to NonStop NET/MASTER MS. When NonStop NET/MASTER MS regains control of the terminal, it returns you to the environment from which the PROGRUN command was entered.
Caution You can run conversational utilities using the PROGRUN command. However, because applications and utilities started using PROGRUN take complete control of the terminal and consequently suspend use of the terminal by NonStop NET/MASTER MS, you are not aware of incoming messages destined for your OCS window when you are interacting with a PROGRUN-initiated application. This impairs the integral monitoring capability that NonStop NET/MASTER MS provides. OPSYS, therefore, is the preferred way of starting and terminating interactive sessions with conversational Guardian utilities. For block-mode applications, there is no choice but to use the PROGRUN command.
If you start a TACL process by using the PROGRUN command and then log on to TACL, you must press CTRL-Y or use the EXIT command to return to NonStop NET/MASTER MS.
Be aware also that, if you start a TACL process by using PROGRUN and you do not have a valid Guardian user ID and password, you will be unable to log on to, and stop, the TACL process to return to NonStop NET/MASTER MS. In this case, you must ask your system manager to stop the TACL process for you.
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, messages may be lost. Such messages are still logged to the activity log.
If a terminal timeout occurs while a process has control of a terminal, the timeout action is initiated when NonStop NET/MASTER MS regains control of the terminal.
The Two Forms of the PROGRUN Command
106379 Tandem Computers Incorporated 7–21
The Two Forms of the PROGRUN Command
There are two forms of the PROGRUN command—format 1 (restricted) and format 2 (unrestricted):
Format 1 gives you access to block-mode (or conversational) applications that have been predefined to your NonStop NET/MASTER MS system by your system manager (through the UMS facility). You can use your Console Extras utility list to access these predefined applications. Ask your system manager to customize your Console Extras utility list for you.
PROGRUN utility
Each application that you can interact with using this format of the PROGRUN command has a command authority level associated with it. You may not have access to all the applications that you are able to use outside of NonStop NET/MASTER MS.
Format 2 allows you to access any Guardian object file, including conversational Guardian utilities: PROGRUN FILE=file-spec [ CPU=cpu-number ] [ DEFAULT=$volume.subvolume ] [ NAME=process-name ] [ PRI=process-priority ] [ PARAMS="startup-string" ]
Depending on how your NonStop NET/MASTER MS system is configured and your command authority level, you may have access to format 1, format 2, or both formats of the PROGRUN command.
Refer to the NonStop NET/MASTER MS Command Reference Manual for a complete description of the PROGRUN command.
The Two Forms of the PROGRUN Command
Example
Enter the following PROGRUN command to start a session with the Remote Console Process (RCP):
PROGRUN RCP
The following RCP main screen takes over your terminal:
S Y S T E M S T A T U S
CPU Fz Status CPU Fz Status 00 E Executing GUARDIAN 90 01 E Executing GUARDIAN 90 02 E Executing GUARDIAN 90 03 E Executing GUARDIAN 90 04 No response 05 No response 06 No response 07 No response 08 No response 09 No response 10 No response 11 No response 12 No response 13 No response 14 No response 15 No response R C P M A I N M E N U LOGGED ON T9996C30 - 25AUG92
SF1: GUARDIAN 90 MODE SF9: LOBUG
SF3: ALARM STATUS AND CONTROL SF10: SYSTEM LOAD CONFIGURATION SF4: PROCESSOR DUMP SF11: REMOTE STATUS AND CONTROL SF5: PROCESSOR LOAD SF12: RCP LOGON/LOGOFF
SF6: SYSTEM LOAD SF13: IPC STATUS SF7: PROCESSOR BUSY SF14: I/O CONFIGURATION SF8: RMI STATUS SF15: POWER/ENVIRONMENT STATUS SF16: EXIT
F1: Help F14: Display locators COPYRIGHT TANDEM COMPUTERS INC. 1989 - 1992
After you exit from RCP, the results from the PROGRUN command are displayed:
(11:40) --- OPERATOR CONTROL SERVICES --- START PROGRUN RCP
NNM1459 PROCESS $X095 CREATED FOR $SYSTEM.SYSTEM.RCP NNM1460 PROCESS $X095 FOR $SYSTEM.SYSTEM.RCP STOPPED
Running NetStatus
106379 Tandem Computers Incorporated 7–23
Running NetStatus
NetStatus is an object-oriented, full-screen user interface that provides a central operations environment from which you can:Monitor the current state of objects in a network.
Control and display information about subsystem objects either through function keys or by invoking DSNM subsystem commands.
Note The NetStatus application is supported for Tandem 6530 or compatible terminals only.
If the NetStatus product is available on your system and your system manager has started the NetStatus Pathway process, you can access it. If you have access to Console Extras, you can ask your system manager to add the NetStatus utility to your Console Extras utility list to enable you to access NetStatus through Console Extras. Otherwise, you have to access NetStatus from either the OCS command line, the Command Entry command line, or the Activity Log Browse facility command line, by starting the NETSTAT NCL procedure using the following syntax.
NETSTAT [ NOCOLOR ] [ DISPLAY filename ]
NOCOLOR
specifies that your terminal does not support color.
DISPLAY filename
specifies the file to be used as the startup NetStatus display set. The display set identifies the objects in your network that you can monitor and control from the NetStatus Network Status screen. Display sets are described in detail in the
NetStatus User’s Guide. If your system manager has defined a file in your user ID
definition record (Installation Attribute 1), you need not explicitly specify this file. NetStatus uses the file defined in your Installation Attribute 1 field as the display set.
Note The NETSTAT NCL procedure suspends your terminal output (in the same way as the PROGRUN command) as long as you are in NetStatus.
If you frequently enter and exit from the NetStatus application and usually use the same display set, you may find it convenient to set up an equate to access the
NetStatus application. The next example shows how to use the EQUATE command to abbreviate a long NETSTAT command string to just three characters—NET:
Running NetStatus
If you have several display sets defined, you may want to define a PREF attribute function key that allows you to enter the name of a particular display set. For example:
FK SF14 PREF,-NETSTAT NOCOLOR DISPLAY+
Now, to display the status of the objects defined in the display set named SNAXSET, located in your default library, you could simply enter the following string in the OCS command line and press the SF14 function keys:
SNAXSET
When you first enter NetStatus, it tries to retrieve one of the following display sets: The DISPLAY file name, if included when you invoke NetStatus
The file name configured in the Installation Attribute 1 field of your user ID definition record
A display set called ZDISPSET, if available (see your system manager for details about ZDISPSET on your system)
A NetStatus Configuration screen is displayed if NetStatus cannot retrieve a display set:
Page 1 NetStatus Configuration Display Set File Name
SUBSYS OBJTYPE NAME MANAGER OPTION --- --- ---- --- ---
Valid hierarchy options are: A = All (default), S = Subonly, O = Only.
F1--Execute Monitor F2--Retrieve Display Set
F4--Return, No Change F12-Help SF2-First Page SF3-Last Page SF15-Clear Display Set SF16-Exit
Running NetStatus
106379 Tandem Computers Incorporated 7–25
A Network Status screen is displayed if NetStatus can retrieve a display set. The screen provides a status summary for each object in your display set file.
Page 1 Network Status Level 1 Select state: Parent:
\SYS1.0 \SYS1.1 \SYS1.$SYSTEM 1 0 0 1 0 0 4 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 << LINK-SUMMARY 1 0 0 >> ==>
F1--Execute F2--Text F3--Down F4--Up F5--Status F6--Info
F7--Inquire F8--Expand F9--Cancel F11-Conf F12-Help SF2-First SF3--Last SF4-TopLvl SF5-Detail SF6-Stats SF7-Start SF8-Rsvd SF9-Abort SF10-Update SF1-CLEAR SF16-EXIT
Using the NetStatus application to perform network management tasks is described in the NetStatus User’s Guide.
Note When you are working in NetStatus, standard NetStatus function keys and commands apply.
To return to NonStop NET/MASTER MS from NetStatus, press the SF16 function key from any NetStatus screen.
Entering Commands From Within NetStatus
Entering Commands From Within NetStatus
All NetStatus screens (except the NetStatus Configuration screen) have a command line on which you can enter commands. You can issue any DSNM command (using OPSYS) for which you have a high enough authority level from any NetStatus command line.
For example, to display information about all servers under a PATHMON named $ADPN, enter the following command in the command input line and press the F1 function key to execute the command:
OPSYS INFO SERVER * UNDER $ADPN
The first three lines of the command response appear on the Network Status screen:
Page 1 Network Status Level 1 Select state: Parent:
\SYS1.0 \SYS1.1 \SYS1.$SYSTEM 1 0 0 1 0 0 7 0 0
MORE TEXT << LINK-SUMMARY 1 0 0 >> ==> OPSYS INFO SERVER * UNDER $ADPN
PATHWAY SERVER NETSTATUS-SVR01 UNDER \SYS1.$ADPN Autorestart: 3
Processes: 1
Viewing Command Responses in NetStatus
106379 Tandem Computers Incorporated 7–27
Press the F2 function key to view the complete response:
Page 1 MORE TEXT NetStatus Text Display PATHWAY SERVER NETSTATUS-SVR01 UNDER \SYS1.$ADPN Autorestart: 3 Processes: 1 Primary Cpu: 0 Backup Cpu: 1 Createdelay: 1:00.0 Debug: off Deletedelay: 1.0 Guardianlib: Hometerm: In: Linkdepth: 1 Maxlinks: 1 Maxservers: 1 Numstatic: 1 Out: Priority: 155 Program: \SYS1.$DATA.ZDSMS.NSTAT Sendtimeout: 0.0
==> OPSYS INFO SERVER * UNDER $ADPN
F1--Execute F4--Return F9--Cancel
F12-Help SF2-First SF3-Last SF16-Exit
Viewing Command Responses in NetStatus
You can use the function keys in Table 7-3 to view command responses on the NetStatus Text Display screen.
Table 7-3. Viewing Command Responses in NetStatus
6530 Function Key Description PAGEDOWN/
NEXTPAGE
Displays next screenful of response messages.
PAGEUP/ PREVPAGE
Displays previous screenful of response messages.
F4 Returns to the screen from which command was issued.
F12 Displays help.
SF2 Displays first screenful of response messages. SF3 Displays last screenful of response messages.
SF16 Exits from the NetStatus application and returns to the NonStop NET/MASTER MS window from which you invoked NetStatus.
Issuing DSNM commands from within the NetStatus application is discussed in more detail in the NetStatus User’s Guide.
Sending a Problem to DSM/PM