Guardian Utilities
The NonStop NET/MASTER MS OPSYS command is your interface, through DSNM, to Guardian conversational utilities, and to TACL commands, macros, and routines (all of which are referred to as “utilities” in the following discussion).
Note You cannot issue commands to block-mode applications by using the OPSYS command. You must run block-mode applications and access them directly. To run block-mode applications, use the NonStop NET/MASTER MS command PROGRUN. If you have access to the Console Extras facility and the application is listed on your Console Extras utility list, you can also run the application from there. To run NETSTATUS, use the NETSTAT command.
The DSNM Utility Access Command Set
The DSNM utility access commands you can issue through OPSYS are listed in Table 7-2.
Table 7-2. The DSNM Utility Access Commands Available With OPSYS
DSNM Utility Access Command Function
SEND Establishes a utility session (if currently nonexistent) and sends text to an established session.
ANSWER Responds to a confirmation prompt generated by a utility. EOF Sends an end-of-file character to an existing session; it has the
same effect as pressing the CTRL and Y keys (externally to NonStop NET/MASTER MS).
BREAK Sends a break message to an existing session; it has the same effect as pressing the BREAK key (externally to NonStop NET/MASTER MS).
KILL Terminates a utility session immediately. CLEANUP Terminates all your utility sessions.
Utility Access Security
106379 Tandem Computers Incorporated 7–7
The format of the OPSYS command, when used to run Guardian conversational utilities, is as follows:
[ OPSYS ] dsnm-utility-command [ session[ =utility ] [ text ] ] dsnm-utility-command is one of:
ANSWER BREAK CLEANUP [ STOP | DOWN ]
EOF KILL [ SEND ]
session
is the name by which the utility session is identified.
utility
is the name of a Guardian utility or TACL macro defined through the NonStop NET/MASTER MS User ID Management Services (UMS) facility. Use only when a session is being created and if you want to assign a session name that is different from the utility name.
text
is the command or parameters to be sent to the session.
Refer to the User’s Guide to DSNM Commands for a complete description of DSNM utility access command syntax and the NonStop NET/MASTER MS Command Reference
Manual for a complete description of the OPSYS command.
When you issue an OPSYS command (either explicitly or implicitly; OPSYS is
sometimes optional as explained under “Starting a Session With a Utility,” later in this section) to communicate with a Guardian utility, NonStop NET/MASTER MS receives the results of interaction with the utility, and sends the results either to your terminal or to the NCL process from which the utility session was established.
Getting Help for DSNM Utility Access Commands
To display help for any of the DSNM utility access commands, enter the following in the command input line and press the F1 (PF01) function key:
OPSYS dsnm-utility-command
For example, enter the following string and then press the F1 (PF01) function key:
OPSYS SEND
Utility Access Security Each Guardian utility you can interact with through OPSYS must have been defined for your NonStop NET/MASTER MS system. This is considered a system
management task and is discussed in the NonStop NET/MASTER MS System
Management Guide. You may not have access to all of the Guardian utilities that you
Starting a Session With a Utility
If you try to establish a session with a utility that has not been defined for your NonStop NET/MASTER MS system, the following error message is displayed:
NNM2173 COMMAND AUTHORITY LEVEL NOT SPECIFIED FOR utility cmd
In addition, each Guardian utility that has been defined for your NonStop
NET/MASTER MS system has a command authority level associated with it. Within each utility definition, certain utility commands may have higher or lower authority levels. You may not have a high enough command authority level to access all of the Guardian utilities (or to access the entire command set associated with a particular utility) that you are able to use outside of NonStop NET/MASTER MS.
If you try to establish a session with a utility or to issue a command for which you do not have a sufficient authority level, the following error message is displayed:
NNM0228 INSUFFICIENT COMMAND AUTHORITY LEVEL Starting a Session With a
Utility
Start a session with a Guardian utility by using an OPSYS SEND command. You can give the session a unique name, as in the following example:
OPSYS SEND FUP1=FUP
or
OPSYS FUP1=FUP (remember, the DSNM SEND command is optional) The File Utility Program banner is displayed in the message display area, as shown here:
START OPSYS SEND FUP1=FUP
NNM1468 File Utility Program - T6553D20 - (01JUN93) System \SYS1 NNM1468 Copyright Tandem Computers Incorporated 1981, 1983, 1985-1993 NNM0999 *END*
If the utility does not have the same name as any NonStop NET/MASTER MS or DSNM commands, you can refer to the utility by its own name, and both the OPSYS command and the SEND keyword become optional: for example,
OPSYS SEND FUP
or
OPSYS FUP
or
Starting a Session With a Utility
106379 Tandem Computers Incorporated 7–9
If you refer to the utility by its own name, and if the utility is one that does not accept any commands (for example, DSAP), the utility is started immediately, and responses appear on your screen. If the utility does accept commands, and you have specified a utility command, the responses are displayed in the current window of the OCS screen. However, if the utility does accept commands (for example, FUP) and you have not specified a utility command, the Command Entry screen appears:
--- COMMAND ENTRY --- COMMAND :
:
SYSTEM : SYS1 ASYNC ON WRAP OFF CAPTURE 0 LINE 1 UTILITY : FUP SCROLL OFF F4 PRINT MAX CAP 1000 COLUMN 1 ---
You can then enter your FUP commands through the screen for this session. You can also access the Command Entry screen through the System Support Services Primary Menu screen. In either case, you can modify the UTILITY field to identify the utility to which you want commands to be sent. If you want to route the utility command to a remote system, you can modify the SYSTEM field to identify the link that connects the system.
If you want to give a session a name, you can start the session from the Command Entry screen by entering the OPSYS command, prefixed by a slash (/), in the COMMAND field, as follows:
/OPSYS SEND FUP1=FUP
(Using the slash means: do not send the command to the utility specified in the UTILITY field but send it as a NonStop NET/MASTER MS command. You do not need to use the slash if the UTILITY field is blank.)
Messages appear in the message display area of the Command Entry screen to advise you of the starting process. Once the session has started, you can use the session name in the UTILITY field to send commands to the utility.
You can create multiple concurrent sessions. Any sessions you create are valid only in the environment from which they are created. For example, if you establish a FUP session named FUP1 in OCS and then switch into the Command Entry facility or even
Sending Commands to a Utility
into a different OCS window, you will not be able to send commands in the new environment to that FUP1 session for processing. If you want to send commands to a session called FUP1 in the new environment, you must establish a new FUP1 session with FUP.
In addition, your current Guardian user ID (GUID) is attached to every utility session you establish. You can create multiple concurrent sessions using the same GUID or using different GUIDs. If you try to send a command to a session established under a different GUID or in a different environment, a new session is established for the utility.
Note In the Command Entry facility, you cannot use the PROFILE GUID command to change your GUID. Even though the profile is changed, you are still identified by the GUID that was in effect before the change.
Sending Commands to a Utility
When you are in the Command Entry facility, you can use the following three fields to send utility commands to any system:
The COMMAND field allows you to enter the name of the utility command. You can enter multiple commands if the utility allows it. However, if the command separator is a semicolon (;), you must use two semicolons (;;) instead.
Note You can use the COMMAND field to enter commands or text that you want to send to NonStop NET/MASTER MS, instead of to the utility, by using the slash (/): for example, /PROFILE.
The SYSTEM field allows you to enter the name of the link that connects the remote system to which you want to route the utility command. If you want to send the command to your own system, ensure that the field either is blank or contains the ID of your system.
The UTILITY field allows you to enter the name of the utility or utility session to which you want to send the command.
Sending Commands to a Utility
106379 Tandem Computers Incorporated 7–11
For example, if SYS1 is the name of a link, then when you press the ENTER key from the following screen, you send a SECURE command to the File Utility Program (FUP) on the system connected to SYS1.
--- COMMAND ENTRY --- COMMAND : SECURE $DATA.ZNCLPGN.MYFILE, "CCCC"
:
SYSTEM : SYS1 ASYNC ON WRAP OFF CAPTURE 0 LINE 1 UTILITY : FUP SCROLL OFF F4 PRINT MAX CAP 1000 COLUMN 1 ---
Messages appear in the message display area to advise you of the result. You can examine previous messages that were received during the session by examining the capture buffer.
If the value in the UTILITY field is FUP, the following three commands establish a session with the FUP utility, request that the security setting of a file be changed, and then display the new security setting:
INFO $DATA.ZNCLPGN.MYFILE
SECURE $DATA.ZNCLPGN.MYFILE, "NUNU" INFO $DATA.ZNCLPGN.MYFILE
Sending Commands to a Utility
The capture buffer contains the results of the commands:
--- COMMAND ENTRY --- COMMAND :
:
SYSTEM : SYS1 ASYNC ON WRAP OFF CAPTURE 14 LINE 1 UTILITY : FUP SCROLL OFF F4 PRINT MAX CAP 1000 COLUMN 1 --- INFO $DATA.ZNCLPGN.MYFILE
NNM1468 File Utility Program - T6553D20 - (01JUN93) System \SYS1 NNM1468 Copyright Tandem Computers Incorporated 1981, 1983, 1985-1993 NNM1456 CODE EOF LAST MODIF OWNER RWEP TYPE NNM1456 $DATA.ZNCLPGN NNM1456 MYFILE 101 0 8:34 100,21 NCNC NNM0999 *END* SECURE $DATA.ZNCLPGN.MYFILE,"NUNU" NNM0995 REQUEST COMPLETE INFO $DATA.ZNCLPGN.MYFILE
NNM1456 CODE EOF LAST MODIF OWNER RWEP TYPE NNM1456 $DATA.ZNCLPGN
NNM1456 MYFILE 101 0 8:34 100,21 NUNU NNM0999 *END*
** END OF DELIVERED MESSAGES **
The following example establishes a session with the Disk Space Analysis Program (DSAP) and asks for a summary analysis for a single user from the Command Entry facility. In this case, you have entered DSAP in the UTILITY field and the parameters $DATA, USER 100,21 in the COMMAND field.
--- COMMAND ENTRY --- COMMAND :
:
SYSTEM : SYS1 ASYNC ON WRAP OFF CAPTURE 25 LINE 6 UTILITY : DSAP SCROLL OFF F4 PRINT MAX CAP 1000 COLUMN 1 --- $DATA, USER 100,21
NNM1468 TACL (T9205D20 - 01JUN93), Operating System D20 NNM1468 COPYRIGHT TANDEM COMPUTERS INCORPORATED 1985,1987-1993 NNM1468 CPU 1, process has no backup
NNM1468 November 10, 1994 8:58:37 NNM1468 (Invoking $SYSTEM.SYSTEM.TACLLOCL) NNM1468 (Invoking $DATA2.JOHNN.TACLCSTM)
NNM1468 -- VLX -- Attaching segment $data2.sys1.publsegf NNM1468 -- VLX -- Attaching segment $data2.user.publsegf NNM1468 Loading TACLCMD
NNM1468 Hometerm is not pagemode 6530 NNM1468 Loaded from $DATA2.MAXFER.MAXFER: NNM1468 MTT TTM
NNM1468 Current volume is $DATA2.JOHNN NNM1456
NNM1456
NNM1456 PAGE 1 DSAP -- SYS1.JOHNN -- NNM1456
Responding to Prompts Generated by Utilities
106379 Tandem Computers Incorporated 7–13
Note Because DSAP does not have associated commands, you cannot enter the Command Entry facility by issuing DSAP from the OCS command input line. You must be in the facility already: for example, through option 6 on the System Support Services Primary Menu screen.
You can also send utility commands without using the Command Entry facility, by issuing OPSYS SEND commands. However, sending utility commands by this method requires you to include the utility name or the session name in the OPSYS command each time you send a command to the utility. In the Command Entry facility, you enter the utility name or the session name only once per session with the utility. The following example sends a SECURE command to the File Utility Program (FUP) through an established session named FUP1:
OPSYS SEND FUP1 SECURE $DATA.ZNCLPGN.MYFILE, "CCCC"
You can send a command to the utility in the same command string with which you establish the session. The following example establishes a session named FUP1 with the FUP utility and sends it a command:
OPSYS SEND FUP1=FUP SECURE $DATA.ZNCLPGN.MYFILE, "CCCC"
If you choose not to give the utility session a name that is different from the name of the utility, and if the name of the utility does not match the name of any of the other NonStop NET/MASTER MS or DSNM commands, then both the OPSYS command and the SEND keyword are optional when you send a command to the utility session: for example,
FUP SECURE $DATA.ZNCLPGN.MYFILE, "CCCC" Responding to Prompts
Generated by Utilities
Issue OPSYS ANSWER commands to respond to requests generated by a utility. These are generally in the form of confirmation prompts.
If you are in the Command Entry facility, you can type your response in the COMMAND field and press the F14 (PF14) function key to issue the command. If you are working in OCS, confirmation prompts are full NRD messages, which remain in the NRD message area even after you respond to them with an OPSYS ANSWER command. (Full NRD messages are discussed more fully in Section 4, “Operator Control Services (OCS).”) You can use the F14 (PF14) function key to answer and to remove the non-roll-delete attribute of a confirmation prompt at the same time as follows:
1. Type your answer at the OCS command input line. 2. Position the cursor to the left of the confirmation prompt.
3. Press F14 (PF14) to answer and to purge the confirmation prompt.
The first character of the prompt is replaced by the pipe symbol (|), and the prompt becomes a roll-delete message.
Responding to Prompts Generated by Utilities
Example
The following OCS example sends a request to FUP1 (a session that you have previously started with FUP) to purge all the files in $DATA.MYVOL:
OPSYS SEND FUP1 PURGE $DATA.MYVOL.*
FUP asks for confirmation, as shown in the following screen:
(09:30) --- OPERATOR CONTROL SERVICES --- START OPSYS SEND FUP1 PURGE $DATA.MYVOL.*
NNM1456 DO YOU WISH TO PURGE THE ENTIRE SUBVOLUME $DATA.MYVOL NNM1456 [100,021 FUP1] ( Y[ES], N[ONE], S[ELECT], F[ILES] )? NNM0999 *END*
_____________________________________________________________________________
--- --- NonStop NET/MASTER D30 --- --- M=>
You want to select a subset of the files in $DATA.MYVOL to be purged. You respond as follows:
1. Type S at the command input line.
2. Position the cursor to the left of the prompt:
Responding to Prompts Generated by Utilities
106379 Tandem Computers Incorporated 7–15
3. Press F14 (PF14). The following screen appears.
(09:31) --- OPERATOR CONTROL SERVICES --- START OPSYS SEND FUP1 PURGE $DATA.MYVOL.*
NNM1456 DO YOU WISH TO PURGE THE ENTIRE SUBVOLUME $DATA.MYVOL |NM1456 [100,021 FUP1] ( Y[ES], N[ONE], S[ELECT], F[ILES] )? NNM0999 *END*
NNM1456 CODE EOF LAST MODIF OWNER RWEP TYPE REC BLOCK NNM1456 $DATA.MYVOL NNM1456 AAAA 101 0 9:27 100,21 NCNC NNM1456 [100,021 FUP1] PURGE? NNM0999 *END* _____________________________________________________________________________ --- --- NonStop NET/MASTER D30 --- --- M=> S
(If you are in the Command Entry facility, type S in the COMMAND field and press F14 (PF14) to issue the command.)
You respond to each confirmation prompt as follows: 1. Type your response at the command input line. 2. Position the cursor to the left of the prompt:
Sending a BREAK Message to a Utility
3. Press F14 (PF14). The following screen appears.
(09:35) --- OPERATOR CONTROL SERVICES --- START OPSYS SEND FUP1 PURGE $DATA.MYVOL.*
NNM1456 DO YOU WISH TO PURGE THE ENTIRE SUBVOLUME $DATA.MYVOL |NM1456 [100,021 FUP1] ( Y[ES], N[ONE], S[ELECT], F[ILES] )? NNM0999 *END*
NNM1456 CODE EOF LAST MODIF OWNER RWEP TYPE REC BLOCK NNM1456 $DATA.MYVOL NNM1456 AAAA 101 0 9:27 100,21 NCNC |NM1456 [100,021 FUP1] PURGE? NNM0999 *END* NNM1456 NNM1456 $DATA.MYVOL.AAAA PURGED. NNM1456 MYFILE 101 0 9:21 100,21 NCNC NNM1456 [100,021 FUP1] PURGE? NNM0999 *END* _____________________________________________________________________________ --- --- NonStop NET/MASTER D30 --- --- M=> Y
Sending a BREAK Message to a Utility
Issue an OPSYS BREAK command to send a BREAK message to a utility. This is the equivalent of pressing the BREAK key when you are interacting with a utility running in the foreground. If you are in the Command Entry facility, you can use the SF13 function key to issue the command.
How the BREAK message affects the behavior of the utility depends on the particular utility.
Example
The following example sends a request to FUP1:
Ending a Session With a Utility
106379 Tandem Computers Incorporated 7–17
You decide that the command is returning more information than you need and issue a BREAK command to stop the output (if you are in the Command Entry facility, press SF13 to issue the command):
OPSYS BREAK FUP1
(10:10) --- OPERATOR CONTROL SERVICES --- NNM1456 ZEX0616N 101 2442 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0617N 101 2440 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0618N 101 2464 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0619N 101 2740 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0620N 101 2738 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0621N 101 2766 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0622N 101 2878 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0623N 101 2388 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0624N 101 2500 10NOV94 14:25 100,21 NCNC NNM1456 ZEX0625N 101 2532 10NOV94 14:25 100,21 NCNC NNM1456 ZEX0701N 101 2180 10NOV94 14:25 100,21 NCNC NNM1456 ZEX0702N 101 2232 10NOV94 14:25 100,21 NCNC NNM1456 ZEX0703N 101 2228 10NOV94 14:25 100,21 NCNC NNM1469 (-404) Command Pre-empted NNM0999 *END* NNM0995 REQUEST COMPLETE _____________________________________________________________________________ NNM1456 ZEX0612N 101 2332 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0613N 101 2330 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0614N 101 2512 10NOV94 14:24 100,21 NCNC NNM1456 ZEX0615N 101 2638 10NOV94 14:24 100,21 NCNC --- --- NonStop NET/MASTER D30 --- --- M=> OPSYS BREAK FUP1
Ending a Session With a Utility
When you exit the environment in which you are interacting with Guardian utilities, all utility sessions established within that environment are terminated.
You can also explicitly terminate Guardian utility sessions by using the OPSYS CLEANUP and KILL commands.
KILL The KILL command terminates an individual utility session immediately, without regard to any outstanding requests. You cannot KILL a session started under a different GUID. If you are in the Command Entry facility, you can use the SF14 function key to issue the command.
CLEANUP The CLEANUP command terminates all utility sessions associated with your current NonStop NET/MASTER MS environment, regardless of the GUIDs associated with the sessions. If you are in the Command Entry facility, either prefix the OPSYS CLEANUP command with a slash (/) or enter spaces in the UTILITY field. Refer to the User’s Guide to DSNM Commands for more information on the KILL and