System Software Library User’s Guide to DSNM Commands Abstract This manual provides information for using DSNM commands to monitor and control a network of Tandem nodes. Part Number 098571 Edition Second Published Product Version Release ID Supported Releases September 1993 C31/D20 D20.00 This manual supports C30.09 and D20.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Edition Part Number Product Version Earliest Supported Release Published First Update 1 Second 069310 089928 098571 C31 C31 C31/D20 N/A N/A C30.09/D20.00 August 1992 March 1993 September 1993 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
New and Changed Information This manual has been updated to use the D-series nomenclature. The operating system for Tandem NonStop systems, formerly called the Guardian operating system, is now called the Tandem NonStop Kernel. This change reflects Tandem’s current and future operating system enhancements that further enable open systems and application portability.
New and Changed Information 098571 Tandem Computers Incorporated iv
Contents About This Manual xiii Notation Conventions Section 1 xvii Introduction What Is in This Section 1-1 Basic Information About DSNM 1-1 Subsystems 1-2 Object States Reported by DSNM NonStop NET/MASTER MS NetCommand Section 2 1-4 1-5 1-6 DSNM Commands What Is in This Section 2-1 DSNM Commands by Function 2-1 DSNM Command Support by Subsystem 2-2 Command-Line Syntax 2-3 Commands 2-3 Object Specification 2-3 Modifiers 2-5 Parameters 2-6 Considerations 2-7 Canceling Commands ABORT Command
Contents Section 3 Object Specifications What Is in This Section 3-1 Objects in DSNM Commands 3-1 Object Specification 3-1 Effect of Qualifiers on Names 3-2 Specifying Objects 3-5 Specifying Individual Objects 3-5 Specifying Lists of Names With the Same Qualifiers 3-7 Specifying Lists of Names With Different Qualifiers 3-7 Nesting Object Specifications 3-8 DNS Groups 3-8 All Members of Groups 3-9 Selected Members of Groups 3-9 DNS Composites 3-10 All Components of a Composite 3-10 Selected Components
Contents Section 5 Subsystems What Is in This Section 5-1 AM3270 5-2 Object Types 5-2 States 5-2 Effects of the Hierarchy Modifier Control Commands 5-3 The INFO Command 5-3 The STATISTICS Command 5-3 5-3 Expand 5-4 Object Types 5-4 States 5-4 Effects of the Hierarchy Modifier 5-5 Control Commands 5-5 The INFO Command 5-5 The STATISTICS Command 5-5 Guardian 5-6 Object Types 5-6 States 5-6 Effects of the Hierarchy Modifier Commands 5-7 5-6 Pathway 5-8 Object Types 5-8 States 5-9 Effects of the Hierarc
Contents Effects of the Hierarchy Modifier 5-15 Control Commands 5-16 The INFO Command 5-16 The STATISTICS Command 5-16 Spooler 5-17 Object Types 5-17 States 5-17 Effects of the Hierarchy Modifier Commands 5-17 5-17 TR3271 5-18 Object Types 5-18 States 5-18 Effects of the Hierarchy Modifier 5-19 Control Commands 5-19 The INFO Command 5-19 The STATISTICS Command 5-19 X25AM 5-20 Object Types 5-20 States 5-20 Effects of the Hierarchy Modifier Control Commands 5-21 The INFO Command 5-21 The STATISTICS Comman
Contents Applying Security Restrictions 6-7 Standard NetCommand Command Set OBEY Command 6-8 Applications and Utilities 6-9 Define Process Commands Section 7 6-8 6-10 NonStop NET/MASTER MS Interface What Is in This Section 7-1 How to use Online Help 7-1 How to Issue DSNM Commands Supported Subsystems 7-1 7-1 DSNM Command Set in NonStop NET/MASTER MS Accessing Utilities 7-3 ANSWER Command BREAK Command 7-4 7-5 CLEANUP Command EOF Command KILL Command SEND Command 7-2 7-6 7-7 7-8 7-9
Contents Figures Figure 5-1. Subsystem Object Hierarchy in the AM3270 Subsystem 5-2 Figure 5-2. Subsystem Object Hierarchy in the Expand Subsystem Figure 5-3. Subsystem Object Hierarchy for GUARDIAN Figure 5-4. Subsystem Object Hierarchy in the Pathway Subsystem Figure 5-5. Subsystem Object Hierarchy in the SNAX/CDF Subsystem 5-11 Figure 5-6. Subsystem Object Hierarchy in the SNAX/XF Subsystem Figure 5-7. Subsystem Object Hierarchy in the TR3271 Subsystem 5-18 Figure 5-8.
Contents Table 5-19. Data Communication Subsystem Object Type Abbreviations For DSNM Commands 5-22 Table 5-20.
Contents xii 098571 Tandem Computers Incorporated
About This Manual Distributed Systems Network Management (DSNM) provides a single, consistent command set that can be used to control and monitor objects belonging to certain Tandem subsystems and user applications. This manual introduces the DSNM command set, gives the syntax for each DSNM command, and discusses different parts of the DSNM command syntax.
About This Manual Where to Go For More Information Where to Go For More The following manuals are prerequisite reading for system managers and Information recommended reading for operators: Introduction to NonStop System Operations gives a general overview of Tandem NonStop systems. Distributed Systems Management Solutions (DSMS) System Management Guide contains installation and configuration information for DSNM, NetStatus, and NetCommand in a DSMS and a NonStop NET/MASTER MS environment.
About This Manual Where to Go For More Information If the system configuration includes any of the following subsystems or products, the indicated manuals are appropriate references: For NetStatus: NetStatus User’s Guide For AM3270: Device-Specific Access Methods-AM3270/TR3271 andSCF Reference Manual for AM3270 and TR3271 For Expand: Expand Network Management Guide and SCF Reference Manual for EXPAND For Guardian: Guardian User’s Guide For Pathway: Pathway PATHCOM Reference Manual For SNAX/CDF: SNAX/CDF Co
About This Manual Where to Go For More Information xvi 098571 Tandem Computers Incorporated
Notation Conventions General Syntax Notation UPPERCASE LETTERS The following list summarizes the notation conventions for syntax presentation in this manual. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation Conventions General Syntax Notation Ellipsis ... An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char...
Notation Conventions Notation for Messages Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned.
1 Introduction What Is in This Section This section introduces the Distributed Systems Network Management (DSNM) product and its command set.
Introduction Basic Information about DSNM Logical names in commands. The user may specify operations on object aliases or object groups, as well as the objects themselves. Routing and transport for commands, responses, and monitoring operations to objects located anywhere in the network. The communication components of DSNM enable management applications to monitor and control resources on remote nodes as well.
Introduction Basic Information about DSNM Table 1-1.
Introduction Basic Information about DSNM As listed in Table 1-2, within the set of Tandem subsystems supported by DSNM, some can be : Controlled, queried for information, and monitored (AM3270, EXPAND, PATHWAY, SNAX, SNAXCDF, TR3271, X25AM) Monitored only (GUARDIAN, SPOOLER) Controlled and queried for information (limited support for Tandem data communications subsystems is available as an extension to DSNM in a NonStop NET/MASTER MS operations environment.
Introduction NonStop NET/MASTER MS UP means that the object is ready, available, or in use. DOWN means that the object is unavailable or that operator intervention is required to bring it up. PENDING means that the object is not up or down. Many subsystems use more than one object state to indicate that an object is not ready for use, but that it is not totally deactivated: for example, the object is currently stopping or starting.
Introduction NetCommand NetCommand NetCommand is the command-line interface to DSNM for users of DSMS and the Integrated Operations Console (IOC). Section 6, “NetCommand Interface,” contains information on the NetCommand interface, including instructions for logging on and off, obtaining help, and accessing NonStop tools. DSNM commands can also be issued from the command line in NetStatus, if that product is available at your site; refer to the NetStatus User’s Guide for details.
2 DSNM Commands What Is in This Section This section introduces the DSNM command set and identifies and gives command syntax for each of the commands. Section 3, “Object Specifications,” and Section 4, “Modifiers,” give additional information on specific aspects of the DSNM command syntax. DSNM Commands by DSNM commands can be categorized by function as follows: Function Information retrieval commands—return various types of information about objects.
DSNM Commands DSNM Commands by Function DSNM Command Support by Subsystem Table 2-1 shows the commands supported by each subsystem. Table 2-1.
DSNM Commands Command-Line Syntax Command-Line Syntax All DSNM commands, except AGGREGATE, have the same general syntax, which includes the following information: Command Object specification Modifiers Parameters The DSNM command syntax is shown below: command objectspec [, objectspec ][, modifier ][, parameter ] Commands The command can be any one of the following: ABORT INFO INQUIRE START STATISTICS STATUS STOP UPDATE Object Specification An object specification gives information DSNM uses to ident
DSNM Commands Command-Line Syntax The syntax of the object specification is shown in the following box: [subsys] [type] [\node.]name [[\node.]name] ... [UNDER [\node.]$manager] [hierarchy-modifier] subsys is a qualifier that identifies the name of the subsystem that controls the objects you are specifying. If you do not specify a subsystem, DSNM attempts to determine the objects’ subsystems from the operating system, Distributed Name Service (DNS), and the rest of the object specification.
DSNM Commands Command-Line Syntax Note You can specify the node as part of the name or as part of the manager. If it appears in both places, the manager node takes precedence. You must specify the node if it is not the local node and any of the following are true: The name is a wild card (*) The name begins with a dollar sign ($) The name includes a manager The name is not in the DNS database If the name is an alias, a group, or a composite, you can omit the node.
DSNM Commands Command-Line Syntax State modifier—restricts the scope of the command to a subset of the specified objects on the basis of their states. The state modifier values are: UP NOT-UP DOWN NOT-DOWN Response modifier—controls the type of information generated in response to an INQUIRE or STATUS command.
DSNM Commands Canceling Commands Considerations The following considerations, which apply to all commands except AGGREGATE, are discussed in detail in Section 3, “Object Specifications,” and Section 4, “Modifiers.” You can use parentheses to nest object specifications. Modifiers can appear in any order as long as there is only one of each type. The hierarchy modifier is the only exception; it can occur as part of the object specification or as part of the command as a whole, or both.
DSNM Commands ABORT Command ABORT Command The ABORT command causes DSNM to issue the subsystem-specific command(s) that stops each object. When an object is stopped, its state changes to the subsystem state that corresponds to the DSNM DOWN state. The ABORT command stops objects without waiting for any outstanding operations to be completed. This command is more emergency-oriented than the STOP command, which stops objects only after outstanding operations are finished.
DSNM Commands ABORT Command error-modifier determines how much information is reported when the command is correct but the objects against which the command is being executed produce errors. The error modifier does not affect the command response for errors that result when a command is entered incorrectly or when a name cannot be resolved. ERROR-BRIEF returns a one-line response for each object producing an error; the response identifies the object and briefly describes the error.
DSNM Commands ABORT Command Examples The following command stops the Expand lines in the group ALL-EXPAND. The default hierarchy modifier is ALL, but because the group consists only of lines that have no subordinate objects, there are no subordinate objects to stop. ABORT ALL-EXPAND The following command aborts the objects that are pending among the SNAX line \BERLIN.$SATM, its PUs and LUs, and the Expand lines \BERLIN.$LHF and \BERLIN.$LHUK.
DSNM Commands AGGREGATE Command AGGREGATE Use the AGGREGATE command to obtain the status of each object under the specified Command manager process or subsystem. The response message comprises information that is collated into a summary of the number of objects of each type that are UP, PENDING, DOWN, UNDEFINED and IN ERROR. AGGREGATE [subsys] [\node]... [[UNDER [\node.]$manager]] [,[subsys] [\node]... [[UNDER [\node.]$manager]]]... subsys is the subsystem for which you want the aggregate status.
DSNM Commands AGGREGATE Command The following command returns the aggregate status of all the Pathway objects under the manager process $PMUK. DSNM determines that the subsystem is Pathway from the manager process $PMUK, provided that $PMUK is a running Pathway monitor process. DSNM also assumes that $PMUK is defined on the local node. AGGREGATE UNDER $PMUK A sample response to the command is: PATHWAY 8 Up, PATHWAY 1 Up, PATHWAY 0 Up, TERM UNDER \LONDON.
DSNM Commands INFO Command INFO Command Use the INFO command to obtain configuration information on objects. INFO objectspec [, objectspec ]... [, hierarchy-modifier ] [, error-modifier ] objectspec is the object specification. The syntax for the object specification is provided at the beginning of this section, under “Command-Line Syntax.” Detailed discussion of the object specification is provided in Section 3, “Object Specifications.
DSNM Commands INFO Command ERROR-SUPPRESS suppresses any response from objects that produce errors. This option is normally used when it is known in advance that objects will produce errors and the response is not desired. If you do not specify a value for the error modifier, it defaults to ERROR-BRIEF. Considerations Examples The INFO command is not appropriate for all object types. See Section 5, “Subsystems,” for information on how the command is interpreted by each subsystem.
DSNM Commands INFO Command The following command returns the configuration for the SNAX line \LONDON.$SATM: INFO $SATM ONLY Because the ONLY modifier is specified, the command does not return any information for the PUs and LUs under $SATM. A sample response to the command is: SNAX LINE \LONDON.$SATM DUX: Full Duplex Interface: RS232 Max Pus: 8 Max Lus: 250 Poll Interval: 0:00:00.25 Record Size: 268 Speed: 9600 Station Mode: Primary Switched: Off Windowed: 7 Xmit Timeout: 0:00:00.
DSNM Commands INQUIRE Command INQUIRE Command Use the INQUIRE command to obtain the current status of objects as recorded in the DSNM object database. Response time to the INQUIRE command can be faster than that of the STATUS command, but the response to the STATUS command can be more up-to-date than that of the INQUIRE command. See “Considerations” for details. INQUIRE objectspec [, [, [, [, [, [, [, objectspec ]...
DSNM Commands INQUIRE Command ERROR-DETAIL returns the same information as ERROR-BRIEF, along with additional details about the errors. If additional information is not available, ERROR-BRIEF and ERROR-DETAIL result in the same response. ERROR-SUPPRESS suppresses any response from objects that produce errors. This option is normally used when it is known in advance that objects will produce errors and the response is not desired.
DSNM Commands INQUIRE Command highlight-modifier determines the scope of the command, based on information in the DSNM object database: DEFINED limits the scope of the command to objects that are defined in the DSNM object database. UNDEFINED limits the scope of the command to objects that are not defined in the DSNM object database. MONITORED limits the scope of the command to objects that are recorded in the DSNM object database as being monitored.
DSNM Commands INQUIRE Command Some subsystems generate EMS events for some object state changes but not for others. See Section 5, "Subsystems," for details on possible discrepancies between INQUIRE and STATUS. Because the SUMMARY, SUMMARY-BYTYPE, and SUMMARY-BYOBJECT response modifiers return the number of objects in each state, the state modifier is ineffective with them. DSNM ignores the state modifier if it is combined with any of these response modifiers.
DSNM Commands INQUIRE Command The following command returns a short status line for each member of the group JAXSNAX, and the total number of subordinate objects in each state by object type: INQUIRE JAX-SNAX, SUMMARY-BYOBJECT A sample response to the command is: SNAX LINE SNAX PU 1 Up, 0 SNAX LU 0 Up, 5 SNAX LINE SNAX PU 1 Up, 0 SNAX LU 4 Up, 0 \BERLIN.$SATM Up \BERLIN.$SATM Pending, 0 Down, 0 \BERLIN.$SATM Pending, 0 Down, 0 \BERLIN.$STLR Up \BERLIN.$STLR Pending, 0 Down, 0 \BERLIN.
DSNM Commands START Command START Command The START command causes DSNM to issue the subsystem-specific command(s) that change each object to the subsystem state that corresponds to the DSNM UP state. If all objects specified in the command are started, there is no command response. If the command fails to start any of the objects, there is a response listing the objects that were not started. If the command line contains a syntax error, an error message is returned.
DSNM Commands START Command ERROR-DETAIL returns the same information as ERROR-BRIEF, along with additional details about the errors. If additional information is not available, ERROR-BRIEF and ERROR-DETAIL result in the same response. ERROR-SUPPRESS suppresses any response from objects that produce errors. This option is normally used when it is known in advance that objects will produce errors and the response is not desired.
DSNM Commands START Command Examples The following command starts the SNAX lines identified by the aliases BERLIN-ATMLINE and PARIS-ATM-LINE but does not start any subordinate PUs or LUs: START BERLIN-ATM-LINE PARIS-ATM-LINE, ONLY The following command starts all the Pathway terminals under the manager process \BERLIN.$PMD. If a subsystem error occurs while DSNM is executing the command, the error information is not returned. START TERM * UNDER \BERLIN.
DSNM Commands STATISTICS Command STATISTICS Command Use the STATISTICS command to obtain operational statistics about objects. STATISTICS objectspec [, [, [, [, [, objectspec ]... hierarchy-modifier ] error-modifier ] state-modifier ] RESET ] objectspec is the object specification. The syntax for the object specification is provided at the beginning of this section under “Command-Line Syntax.” Detailed discussion of the object specification is provided in Section 3, "Object Specifications.
DSNM Commands STATISTICS Command that objects will produce errors and the response is not desired. If you do not specify a value for the error modifier, it defaults to ERROR-BRIEF. state-modifier restricts the scope of the command to a subset of the specified objects, depending on their states: UP restricts the command to the specified objects that are up. NOT-UP restricts the command to the specified objects that are either down or pending.
DSNM Commands STATISTICS Command L2 I Frames Sent: 17 L2 I Frames Rcvd: 8 L2 I Frames Sent P: 0 L2 I Frames Rcvd P: 0 L2 RR Frames Sent: 25 L2 RR Frames Rcvd: 39 L2 RNR Frames Sent: 0 L2 RNR Frames Rcvd: 0 L2 REJ Frames Sent: 0 L2 REJ Frames Rcvd: 0 L2 SABM Frames Sent: 0 L2 SABM Frames Rcvd: 0 L2 DISC Frames Sent: 0 L2 DISC Frames Rcvd: 0 L2 CMDR Frames Sent: 0 L2 CMDR Frames Rcvd: 0 L2 UA Frames Sent: 0 L2 UA Frames Rcvd: 0 L2 DM Frames Sent: 0 L2 DM Frames Rcvd: 0 L2 SREJ Frames Sent: 0 L2 SREJ Frames R
DSNM Commands STATISTICS Command A sample response to the command is: SNAX PU \PARIS.$SATM.#ATMCC Sample Time: 06 Mar 1992, 11:07:03.456 Reset Time: 03 Mar 1992, 14:29:45.
DSNM Commands STATUS Command STATUS Command Use the STATUS command to obtain the current subsystem status of objects, as obtained from the subsystem. The STATUS command generates more up-to-date information than the INQUIRE command, but the response time can be slower. See “Considerations” for details. STATUS objectspec [, [, [, [, [, objectspec ]... hierarchy-modifier ] error-modifier ] state-modifier ] response-modifier ] objectspec is the object specification.
DSNM Commands STATUS Command is not available, ERROR-BRIEF and ERROR-DETAIL result in the same response. ERROR-SUPPRESS suppresses any response from objects that produce errors. This option is normally used when it is known in advance that objects will produce errors and the response is not desired. If you do not specify a value for the error modifier, it defaults to ERROR-BRIEF.
DSNM Commands STATUS Command See “Considerations” in the INQUIRE command discussion for additional information on how status information is obtained directly from the DSNM object database. See Section 5, “Subsystems,” for details on possible discrepancies between INQUIRE and STATUS. The state modifier is ignored if the response modifier has the value of SUMMARY, SUMMARY-BYTYPE, or SUMMARY-BYOBJECT, because these values return totals by subsystem state.
DSNM Commands STATUS Command SNAX LU \BERLIN.$STLR.#TLR2 Pending, Stopping Lu State: Daclu Request Pending, Not in Session Session State: Not in Session Open State: Opens Forbidden Session Id: 3 SNAX LU \BERLIN.$STLR.#TLR3 Pending, Stopping Lu State: Daclu Request Pending, Not in Session Session State: Not in Session Open State: Opens Forbidden Session Id: 4 SNAX LU \BERLIN.$STLR.
DSNM Commands STATUS Command A sample response to the command is: PATHWAY SERVER \LONDON 2 Up, 0 Pending, 0 Down, PATHWAY TCP \LONDON 1 Up, 0 Pending, 0 Down, PATHWAY TERM \LONDON 10 Up, 0 Pending, 0 Down, PATHWAY SERVER \BERLIN 1 Up, 1 Pending, 0 Down, PATHWAY TCP \BERLIN 0 Up, 1 Pending, 0 Down, PATHWAY TERM \BERLIN 0 Up, 10 Pending, 0 Down, 2–32 098571 Tandem Computers Incorporated 0 Undefined, 0 In Error 0 Undefined, 0 In Error 0 Undefined, 0 In Error 0 Undefined, 0 In Error 0 Undefined, 0 In Error
DSNM Commands STOP Command STOP Command Use the STOP command to stop objects after they complete all current and outstanding operations. The command causes DSNM to issue the appropriate subsystem commands to bring each object down after all current and outstanding operations have been completed. If all objects specified in the command are successfully stopped, there is no command response. If the command fails to stop any object, there is a response listing the objects that were not stopped.
DSNM Commands STOP Command error-modifier determines how much information is reported when the command is correct but the objects against which the command is being executed produce errors. The error modifier does not affect the command response for errors that result when a command is entered incorrectly or when a name cannot be resolved. ERROR-BRIEF returns a one-line response for each object producing an error; the response identifies the object and briefly describes the error.
DSNM Commands STOP Command Because each subsystem must stop its objects in a predetermined order, the ONLY hierarchy modifier is ineffective with certain object types if their subordinate objects are still up; that is, stopping certain object types forces their subordinates to be stopped as well. The STOP command is not appropriate for all object types; see Section 5, “Subsystems,” for details. Examples The group T-TERMS consists of composites of type TELLER-TERM.
DSNM Commands UPDATE Command UPDATE Command Use the UPDATE command to modify object attributes in the DSNM object database that control: Whether or not an object is monitored when it appears on the NetStatus display What states cause an object to be highlighted on the NetStatus display The UPDATE command returns a response for only those objects that are not successfully updated. UPDATE objectspec [, [, [, [, [, [, [, [, objectspec ]...
DSNM Commands UPDATE Command ERROR-BRIEF returns a one-line response for each object producing an error; the response identifies the object and briefly describes the error. ERROR-DETAIL returns the same information as ERROR-BRIEF, along with additional details about the errors. If additional information is not available, ERROR-BRIEF and ERROR-DETAIL result in the same response. ERROR-SUPPRESS suppresses any response from objects that produce errors.
DSNM Commands UPDATE Command ACCEPTABLE limits the scope of the command to objects that are recorded in the DSNM object database as being monitored and currently in one of their acceptable states. UNACCEPTABLE limits the scope of the command to objects that are recorded in the DSNM object database as being monitored and not currently in one of their acceptable states. For detailed information on the highlight modifier, see Section 4, “Modifiers.
DSNM Commands UPDATE Command Considerations The UPDATE command line must include one of the following: MONITOR, NOMONITOR, or an ACCEPT clause. If you specify ACCEPT with no parameters, DSNM replaces the values in the acceptable states field of the object entry with only the current state of the object. If you specify more than one subsystem object when you issue the UPDATE command, DSNM replaces the acceptable states for each object with that object’s current state.
3 Object Specifications What Is in This Section This section gives detailed information on supplying object specifications within DSNM commands. Object specifications are used to identify the objects against which a DSNM command is being issued. Objects in DSNM All DSNM commands, except the AGGREGATE command, require that you specify at Commands least one object on which the command is to act.
Object Specifications Objects in DSNM Commands A wild card (*)—specifies all the objects of the specified type in the specified subsystem under the specified manager. The optional qualifiers that can be included in an object specification are: Subsystem Object type Node Manager The hierarchy modifier determines which objects are to be included, based on the subsystem object hierarchy. See Section 4, “Modifiers,” for detailed information on the hierarchy modifier.
Object Specifications Objects in DSNM Commands You can supply additional qualifiers to make the name resolvable by issuing the following command: STATUS SERVER SERVER-X UNDER $PM2 The subsystem can be omitted because DSNM can determine it from the manager. The object type is required because DSNM assumes it is TERM, if it is not specified. Now suppose the DNS database contains the names of two Pathway servers with the name SERVER-X, with one under $PM1 and one under $PM2.
Object Specifications Objects in DSNM Commands Wild Cards Some subsystems support the use of a wild card (*) in object names. If you use a wild card, it is resolved by the subsystem and not from DNS. Therefore, any object specification that contains a wild card must be accompanied by qualifiers that enable DSNM to determine the subsystem, object type, manager (if any), and node. This does not always mean that all qualifiers must be entered.
Object Specifications Specifying Objects Specifying Objects There are a number of ways you can create object specifications in a DSNM command. You can: Specify individual objects Specify lists of names with the same qualifiers Specify lists of names with different qualifiers Nest object specifications Following is information on each of these approaches.
Object Specifications Specifying Objects Specifying Objects by Alias An alias is a name that can be used as a synonym for the object’s fully qualified subsystem object name. An alias is defined in the DNS database. For example, assume BERLIN-ATM-CLSTR is an alias for the SNAX PU whose object name is \BERLIN.$SATM.#ATMCC. You could start the PU by specifying: START PU \BERLIN.$SATM.
Object Specifications Specifying Objects Specifying Lists of Names With the Same Qualifiers A single object specification can consist of a space-separated list of names with qualifiers that apply to all the names. The syntax is shown in the following box: [subsys] [type] [\node.]name [[\node.]name] . . . [UNDER [\node.]$manager] [hierarchy-modifier] DSNM applies the modifiers to all names on the list.
Object Specifications DNS Groups Nesting Object Specifications You can force the same qualifiers to apply to every object specification in a commadelimited list. To do so, enclose the entire list of object specifications in parentheses and place the qualifiers outside the parentheses. Within the parentheses, qualifiers apply only to the object specifications of which they are a part. Any qualifiers outside the parentheses apply to the entire list within the parentheses.
Object Specifications DNS Groups All Members of Groups To specify all members of the group, specify the group name. For example, if PARIS is the name of a group that consists of all SNAX and Expand lines connected to the Paris office, you can stop them with the following command: STOP PARIS Selected Members of Groups To restrict the command to selected members of the group, use the group name with the appropriate qualifiers. Following is the syntax for applying qualifiers to a group name.
Object Specifications DNS Composites DNS Composites A composite is a strictly defined set of subsystem objects that must match the specifications of a composite type that has previously been defined to DNS. For example, if a composite type consists of one SNAX LU and one Pathway terminal, all composites of that type must contain exactly one SNAX LU and one Pathway terminal. The components of a composite must belong to subsystems that DSNM supports and must be a type that is supported by DSNM.
Object Specifications Wild Cards Wild Cards DSNM allows you to use a wild card to specify all objects of the same type, if the subsystem supports this feature. A wild-card (*) is used in an object specification in place of the object name. The syntax is shown in the following box. [subsys] [type] [\node.]* [UNDER [\node.
4 Modifiers What Is in This Section When you issue DSNM commands, you can specify modifiers to affect the scope or output of the command. For some commands, you can also specify parameters, which affect the action of the command. This section discusses the types of modifiers and parameters used in DSNM commands. Modifiers Following are the types of modifiers used in DSNM commands: Hierarchy modifier—indicates which objects are to be affected by the command based on the subsystem object hierarchy.
Modifiers Hierarchy Modifier If you specify a hierarchy modifier and a state or highlight modifier, DSNM applies the hierarchy modifier before it applies the state or highlight modifier. (This permits you to apply a command to the subordinates of an object that does not satisfy the other modifiers.) Some DSNM commands do not allow for the use of all modifiers. See detailed information on each DSNM command in Section 2, “DSNM Commands,” for specific information.
Modifiers State Modifier In the following command, ONLY modifies both LONDON and TCP2, so the command starts LONDON SNAX lines and TCP2, but not their subordinate objects. Because TCP1 has its own hierarchy modifier, which is ALL, TCP1 and all its subordinate objects are started.
Modifiers State Modifier Examples If TCP1 is a Pathway TCP and $PMUK is its Pathway manager process, the following command aborts the Pathway terminals under $PMUK that are pending. The command does not stop TCP1. (NOT-UP also includes terminals that are down, but the ABORT command does not affect objects that are already down.) ABORT TCP1 UNDER $PMUK, SUBONLY, NOT-UP The following command starts any of the SNAX lines \PARIS.$SATM, \BERLIN.$SATM, and $SATM (on the local node) that are down.
Modifiers Highlight Modifier Highlight Modifier The highlight modifier can be used only with the UPDATE or INQUIRE commands. It limits the scope of the command to a subset of the objects, based on their attributes in the DSNM object database. None of the values of the highlight modifier is the default. If you do not specify a highlight modifier, DSNM applies the command, regardless of their attributes in the DSNM object database. You can specify state and highlight modifiers in the same command.
Modifiers Error Modifier Note An object is considered monitored if its monitor attribute is set in the DSNM object database. Two values of the highlight modifier are similar in name to two parameters of the UPDATE command: MONITORED and NOT-MONITORED are values of the highlight modifier that limit the scope of the command either to objects that are currently being monitored or to objects that are not currently being monitored.
Modifiers Response Modifier Response Modifier The response modifier is applicable only to the STATUS and INQUIRE commands. It is applied to the objects determined by the value of the hierarchy modifier. Following are the possible values of the response modifier: Note BRIEF DSNM returns one line of status information for each object. DETAIL DSNM returns one line of information for each object, plus detailed information from each object’s subsystem.
Modifiers Response Modifier Because no hierarchy modifier is specified, the response also includes the status of all the pending or down terminals controlled by the TCP. The default response modifier BRIEF is applied and the command returns one line of information per object: PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY TCP TERM TERM TERM TERM TERM TERM TERM TERM TERM TERM TCP1 UNDER \LONDON.$PMUK Down UKPWT1 UNDER \LONDON.$PMUK Down UKPWT2 UNDER \LONDON.
Modifiers Response Modifier Under each group member, the response displays one line for each subordinate object type, showing the number of subordinate objects in each state: SNAX SNAX 1 SNAX 0 SNAX SNAX 1 SNAX 4 LINE PU Up, 0 LU Up, 5 LINE PU Up, 0 LU Up, 0 \BERLIN.$SATM Up \BERLIN.$SATM Pending, 0 Down, 0 \BERLIN.$SATM Pending, 0 Down, 0 \BERLIN.$STLR Up \BERLIN.$STLR Pending, 0 Down, 0 \BERLIN.
Modifiers Parameters Parameters The UPDATE, INQUIRE and the STATISTICS commands enable you to specify parameters, which change the action of the command. The parameters are: ACCEPT FROM-DISPLAY MONITOR | NOMONITOR RESET ACCEPT ACCEPT is used with the DSNM UPDATE command. It is used to change the acceptable state of a specified object to the state or states indicated.
5 Subsystems What Is in This Section This section contains information that is specific to the subsystems that can be controlled by Distributed Systems Network Management (DSNM) in your installation. You must use the appropriate keyword when identifying the subsystems in DSNM commands.
Subsystems AM3270 AM3270 If you use DSNM to control the AM3270 subsystem, you will find the following information helpful. While it covers what you need to know about AM3270 from the viewpoint of operating DSNM, it is not exhaustive. For more details on the AM3270 subsystem, refer to the SCF Reference Manual for AM3270 and TR3271. Object Types The AM3270 subsystem contains two object types, LINE and SU, which correspond to AM3270 lines and subdevices.
Subsystems AM3270 Effects of the Hierarchy Modifier Table 5-2 shows the effects of the hierarchy modifier when it is applied to the various object types in this subsystem. The default value is ALL. Table 5-2.
Subsystems Expand Expand Object Types If you use DSNM to control the Expand subsystem, you will find the following information helpful. While it covers what you need to know about Expand from the viewpoint of operating DSNM, it is not exhaustive. For more details on the Expand subsystem, refer to the Expand Network Management Guide. The Expand subsystem contains two object types, PATH and LINE. If you issue a command for this subsystem without specifying the object type, the object type defaults to LINE.
Subsystems Expand Effects of the Hierarchy Modifier Table 5-4 shows the effects of the hierarchy modifier when it is applied to the object types in this subsystem. The default value is ALL. Table 5-4.
Subsystems Guardian Guardian The DSNM keyword, GUARDIAN, refers to a number of entities in the operating system, which are treated as though they were objects in a single subsystem. If you use DSNM to monitor these operating system objects, you will find the following information helpful. While it covers what you need to know about entities in the operating system from the viewpoint of operating DSNM, it is not exhaustive. For more details, refer to the Guardian User’s Guide.
Subsystems Guardian Table 5-6.
Subsystems Pathway Pathway If you use DSNM to control the Pathway subsystem, you will find the following information helpful. While it covers what you need to know about Pathway from the viewpoint of operating DSNM, it is not exhaustive. For more details on the Pathway subsystem, refer to the Pathway PATHCOM Reference Manual. Object Types The Pathway subsystem contains three object types, TCP, TERM, and SERVER, which correspond to terminal control processes, terminals, and server classes.
Subsystems Pathway States Table 5-7 shows how DSNM reports Pathway subsystem states. Table 5-7.
Subsystems Pathway Control Commands The DSNM START, STOP, and ABORT commands are equivalent to the following PATHCOM commands: DSNM Command TCP PATHCOM command TERM SERVER STOP ABORT START STOP STOP START STOP ABORT START FREEZE, then STOP FREEZE, then STOP THAW, then START The INFO Command When the INFO command is issued against a Pathway object, it uses fields that are also used in the responses to the SET TCP, SET TERM, and SET SERVER commands in Pathway.
Subsystems SNAX/CDF SNAX/CDF If you use DSNM to control the SNAX/CDF subsystem, you will find the following information helpful. While it covers what you need to know about SNAX/CDF from the viewpoint of operating DSNM, it is not exhaustive. For more details on the SNAX/CDF subsystem, refer to the SNAX/CDF Configuration and Control Manual. On the command line, SNAX/CDF is specified as SNAXCDF.
Subsystems SNAX/CDF States Table 5-9 shows how DSNM reports SNAX/CDF subsystem states. Table 5-9. How DSNM Reports SNAX/CDF Subsystem States DSNM Object State SNAX/CDF Subsystem State UP PENDING STARTED STARTING STOPPING ABORTING DEFINED STOPPED DOWN Note Table 5-9 is valid for the DSNM STATUS command. Because of the way that subsystems are implemented, the NetStatus product and the DSNM INQUIRE command can report objects as either up or down, which the DSNM STATUS command reports as pending.
Subsystems SNAX/CDF Control Commands The DSNM START, STOP, and ABORT commands are similar to the SCF START, STOP, and ABORT commands. The INFO Command When the INFO command is issued against a SNAX/CDF object, it produces information similar to the information produced by the SCF INFO DETAIL command. Refer to the SCF Reference Manual for SNAX/CDF for more information.
Subsystems SNAX/XF SNAX/XF If you use DSNM to control the SNAX/XF subsystem, you will find the following information helpful. While it covers what you need to know about SNAX/XF from the viewpoint of operating DSNM, it is not exhaustive. For more details on the SNAX subsystem, refer to the SNAX/XF Configuration and Control Manual. The DSNM keyword for SNAX/XF is SNAX.
Subsystems SNAX/XF States Table 5-11 shows how DSNM reports SNAX/XF subsystem states. Table 5-11. How DSNM Reports SNAX/XF Subsystem States DSNM Object State SNAX/XF Subsystem State UP STARTED ACTIVE STARTING STOPPING (all other states) ADDED DEFINED SUSPENDED STOPPED PENDING DOWN Note Table 5-11 is valid for the DSNM STATUS command.
Subsystems SNAX/XF Control Commands The DSNM START, STOP, and ABORT commands are similar to the SCF START, STOP, and ABORT commands. The INFO Command When the INFO command is issued against a SNAX/XF object, it produces a subset of the information produced by the SCF INFO DETAIL command. Refer to the SCF Reference Manual for SNAX/XF for more information.
Subsystems Spooler Spooler Object Types States If you use DSNM to monitor the Spooler subsystem, you will find the following information helpful. While it covers what you need to know about Spooler from the viewpoint of operating DSNM, it is not exhaustive. For more details on the Spooler subsystem, refer to the Spooler Utilities Reference Manual. The Spooler subsystem contains only one object type, DEV, which corresponds to devices.
Subsystems TR3271 TR3271 If you use DSNM to control the TR3271 subsystem, you will find the following information helpful. While it covers what you need to know about TR3271 from the viewpoint of operating DSNM, it is not exhaustive. For more details on the AM3270 subsystem, refer to the Device-Specific Access Methods-AM3270/TR3271. Object Types The TR3271 subsystem contains two object types, LINE and SU, which correspond to lines and subdevices.
Subsystems TR3271 Effects of the Hierarchy Modifier Table 5-16 shows the effects of the hierarchy modifier when it is applied to the various object types in this subsystem. The default value is ALL. Table 5-16.
Subsystems X25AM X25AM Object Types If you use DSNM to control the X25AM subsystem, you will find the following information helpful. While it covers what you need to know about X25AM from the viewpoint of operating DSNM, it is not exhaustive. For more details on the X25AM subsystem, refer to the X25AM Management Programming Manual. The X25AM subsystem contains two object types, LINE and SU, which correspond to lines and subdevices.
Subsystems X25AM Effects of the Hierarchy Modifier Table 5-18 shows the effects of the hierarchy modifier when it is applied to the various object types in this subsystem. The default value is ALL. Table 5-18.
Subsystems Other Supported Tandem Data Communication Subsystems Other Supported Tandem Data Communications Subsystems Note When used with NonStop NET/MASTER MS, DSNM includes a process known as the automation I process. The process enables DSNM to provide control and limited information retrieval capabilities for some data communications subsystems that DSNM does not ordinarily manage. Section 1, “Introduction,” discusses the support for these subsystems.
Subsystems Other Supported Tandem Data Communication Subsystems States Table 5-20 shows how DSNM reports Tandem data communications subsystem states. Table 5-20.
6 NetCommand Interface What Is in This Section This section tells you how to issue DSNM commands from NetCommand. NetCommand is the command-line interface to DSNM and is used in a DSMS environment, with or without the Integrated Operations Console (IOC).
NetCommand Interface Using NetCommand Logging On Use the LOGON command at the TACL prompt to log on. LOGON user-group.user-ID [, password] user-group is the name of the user group to which you belong. user-ID is your user ID. password is your password. Considerations TACL first checks that your user group and user ID are valid, then it checks the password. If you omit the password, TACL prompts you for it.
NetCommand Interface Using NetCommand The TACL prompt (TACL 1>) appears if you are not a NetCommand operator and the terminal is not a NetCommand terminal. To obtain the NetCommand prompt, from the TACL prompt, execute the NETCMD utility by issuing the command shown in the following box. [RUN] [$volume.subvol.]NETCMD [DSNM name] $volume.subvol is the location of the NETCMD utility. name is the name of a DSNM configuration.
NetCommand Interface Using NetCommand Getting Help in NetCommand During your NetCommand session, you can use the HELP command to display the syntax of a specific command, or to display a list of the commands that you are authorized to use. HELP [ word [word]... | /OTHER/ ] word is any command that you are authorized to use or any word for which NetCommand help text exists. OTHER causes NetCommand to show you a list of words that are not commands, but for which help text is available.
NetCommand Interface Using NetCommand Defaults Your default node, volume, and subvolume. (This is the default for utilities and applications, and for file name specifications.) Prompt The current setting for the NetCommand prompt. Log The name of the current log file. Command server The fully qualified name of the DSNM command server process. (The node portion of the “Command server” field is the default node for objects in DSNM commands.) NetServer The name of the NetCommand server process.
NetCommand Interface Using NetCommand Changing the NetCommand Prompt Use the SETPROMPT command to change the NetCommand prompt so that it displays any combination of the current node, volume, and subvolume, or any text string that you specify. SETPROMPT { [NODE] [VOL] [SUBVOL] | TEXT string } NODE causes the prompt to include the name of the current node. VOL causes the prompt to include the name of the current volume. SUBVOL causes the prompt to include the name of the current subvolume.
NetCommand Interface Using NetCommand Directing Comand Output to a Printer NetCommand enables you to redirect the output of a command from your terminal to a device or file. The command syntax is shown in the following box: command [/OUT location/] [remainder of command syntax] command is any DSNM command; for example, INFO, ABORT, and STATUS. See Section 2, “DSNM Commands,” for information on DSNM commands. location is the name of a spooler, terminal, or disk file.
NetCommand Interface Standard NetCommand Command Set Standard The NetCommand command set can be customized for individual network operators NetCommand and for specified systems. To find out which commands you can use, enter HELP at Command Set the NetCommand prompt, or ask your system manager. The standard NetCommand command set, however, includes the following commands: DSNM commands—described in Section 2, “Using DSNM Commands.” LOGOFF—ends the NetCommand session. LOGON—begins the NetCommand session.
NetCommand Interface Applications and Utilities file-ID is the name of the command file. Considerations A command file is often called an OBEY file. NetCommand displays all the commands in the command file as they are executed; it also displays any responses. Commands and responses are recorded in a log. You must have the authority to issue each individual command contained in the command file. NetCommand issues an error message and skips any commands in the command file that you are not authorized to use.
NetCommand Interface Define Process Commands Define Process The Tandem VIEWPOINT product includes the Define Process command library, Commands which is a set of commands used to define, start, stop, and undefine processes in any node to which the user has access. If VIEWPOINT is installed on your node, the commands are also available within NetCommand. Refer to the VIEWPOINT Manual for detailed instructions on using the Define Process commands.
7 NonStop NET/MASTER MS Interface What Is in This Section This section tells you how to issue DSNM commands from NonStop NET/MASTER Management Services (MS).
NonStop NET/MASTER MS Interface DSNM Command Set in NonStop NET/MASTER MS DSNM Command Set The standard set of DSNM commands available to NonStop NET/MASTER MS users in NonStop includes all of the commands described in Section 2, “DSNM Commands.” NET/MASTER MS Additionally, NonStop NET/MASTER MS gives you access to six more DSNM commands. The commands enable you to establish sessions with utility programs or TACL commands. These DSNM commands are referred to as DSNM “utility access commands”.
NonStop NET/MASTER MS Interface Accessing Utilities Accessing Utilities The DSNM utility access commands enable you to start and terminate utility sessions. You start utility sessions with the SEND command. You can only start sessions with utilities that you are authorized to run by the NonStop NET/MASTER MS security features. You send text, which normally consists of commands, to your utility sessions with the SEND command.
NonStop NET/MASTER MS Interface ANSWER Command ANSWER Command Use the ANSWER command to respond to confirmation prompts generated by a utility. The following command sends text to the utility session for immediate processing. OPSYS ANSWER session text session specifies the name of an existing utility session whose prompt is being answered. The session name was created with the SEND command that established the utility session.
NonStop NET/MASTER MS Interface BREAK Command BREAK Command Use the BREAK command to send a BREAK message for immediate processing by the utility session. The following command is equivalent to pressing the BREAK key if you were running the utility yourself. Many conversational utilities interpret the BREAK message as a request to abandon current operations. OPSYS BREAK session session is the name of an existing utility session to which a BREAK message is sent.
NonStop NET/MASTER MS Interface CLEANUP Command CLEANUP Command Use the CLEANUP command to terminate all of your utility sessions. OPSYS CLEANUP [ STOP | DOWN ] STOP causes all of your sessions and their utilities to be stopped. STOP is the default. DOWN causes all outstanding text sent to your utility sessions to be discarded and all of your sessions to be terminated. The utilities themselves continue with the current command, if any.
NonStop NET/MASTER MS Interface EOF Command EOF Command Use the EOF command to send end-of-file to a utility session. The following command is equivalent to entering end-of-file from the keyboard when the utility is running normally on a terminal. The effect of end-of-file depends on the utility. OPSYS EOF session session is the name of an existing utility session to which end-of-file is sent. The session name was created with the SEND command that established the utility session.
NonStop NET/MASTER MS Interface KILL Command KILL Command Use the KILL command to immediately terminate a utility session. OPSYS KILL session session is the name of an existing utility session that is to be terminated. The session name was created with the SEND command that established the session. See “SEND Command” later in this section for information on utility and session names. Considerations The KILL command affects the utility immediately regardless of any outstanding operations.
NonStop NET/MASTER MS Interface SEND Command SEND Command Use the SEND command to establish a new utility session with a utility and to send text to it, or to send text to an existing utility session. OPSYS [ SEND ] session[=utility ] [ text ] session is a valid session name. SEND is optional. If SEND is specified and the session does not already exist, the session is created. A valid session name begins with an alphabetic character, followed by up to 19 letters, numbers, or underscores.
NonStop NET/MASTER MS Interface SEND Command Examples The following command creates a utility session called FUP with the utility by the same name: OPSYS SEND FUP The next command sends the text INFO * to the FUP session created in the previous example. If the utility session did not already exist, this command would create the utility session and send the text to it.
Appendix A Messages What Is in This This appendix explains the messages that are generated by DSNM. The error Appendix messages are listed in order by message number. DSNM Messages - nnn A number of the following error messages result from internal errors in the software. These errors are caused by factors that are not under your control. If they occur, write down the error message along with a description of the circumstances, and contact a Tandem representative for assistance.
Messages DSNM Messages - 44 Invalid Token or Operand Value Cause. Your command included something invalid in the position where a keyword or operand was expected. Effect. Your command was not executed. Recovery. Refer to Section 2, "DSNM Commands," for the correct syntax of the command and reissue it. - 45 Required Token or Operand Missing Cause. Your command omitted something that was syntactically required. Effect. Your command was not executed. Recovery.
Messages DSNM Messages - 60 Out of Memory Cause. There is insufficient memory to execute your command. Effect. Your command might have been partially executed. Use the information commands to determine to what extent the command was executed. Recovery. Configure a larger segment size or break the command up into several smaller commands. For information on configuring a larger segment size, see the Distributed Systems Management Solutions (DSMS) System Management Guide. - 64 File System Error Cause.
Messages DSNM Messages - 71 Segment Allocation Error Cause. There was a segment allocation error during the execution of your command. Effect. Your command was not executed. Recovery. If there was not enough disk space, configure the SWAPVOL disk for more space for the segment swap file. Refer to the Distributed Systems Management Solutions (DSMS) System Management Guide for information. - 75 DNS Failure Cause. DNS returned an error. Effect. Your command might have been partially executed.
Messages DSNM Messages -81 Missing Object Type Cause. You issued a command without specifying the object type, and the object type could not be determined from the information on the command line. Effect. Your command is not executed on the affected objects. Recovery. Reissue the command, specifying the object type explicitly. -82 Invalid Object Type Cause. You issued a command, specifying an object type that is not valid for the subsystem. Effect. Your command is not executed on the affected objects.
Messages DSNM Messages -105 Interface Error Cause. A DSNM subsystem interface responded with an error while it was executing the command. Effect. Your command was not executed. Recovery. If the interface is not running, start it. Check the interface’s configuration and correct it as needed. If neither of these measures solves the problem, it is probably an internal error in the interface; contact a Tandem representative. -106 Object Monitor Error Cause.
Messages DSNM Messages -195 * Not Supported by Subsystem Cause. You attempted to use a wild card with a subsystem that does not support the use of wild cards. Effect. Objects represented by * are ignored. Recovery. Retype the command without a wild card. -196 Invalid Subsystem Cause. Your command includes a subsystem that is either misspelled or not part of your DSNM installation. Effect. Your command was not executed. Recovery. Reissue the command with a valid subsystem name.
Messages DSNM Messages -202 Object Name too Long Cause. You typed an object name that is longer than the maximum legal length. Effect. Your command was not executed. Recovery. Reissue the command with a correct name. -204 Missing or Invalid Library Argument Cause. There is an internal problem in the software that issued the message. Effect. The effects of this problem will vary, depending on the individual situation. Recovery. Contact a Tandem representative. -212 Invalid Syntax Cause.
Messages DSNM Messages -400 Missing or Invalid Utility Name Cause. You omitted the utility name or you attempted to use the SEND command to establish a session, giving it an unusable name. This error can also occur if you use the full session=utility syntax and utility does not match the utility passed in the SEND command that established the session. Effect. The command is not processed. Recovery. Correct and reissue the command. -401 Missing or Invalid Session Name Cause.
Messages DSNM Messages -404 Command Pre-empted Cause. The command was discarded because of a BREAK, CLEANUP, or KILL command. Effect. The command may have been partially processed. Recovery. None. -405 Utility Process Deleted Cause. The utility process associated with a session was stopped, abended, or its CPU failed. More specific information is usually supplied by additional error text in the message. Effect. The command may have been partially processed. Recovery. None.
Messages Messages From the DSNM Parser -408 Invalid username or password Cause. NonStop NET/MASTER has supplied invalid logon information. Effect. The command is not processed. Recovery. Notify your system manager, or see the NonStop NET/MASTER Management Services (MS) System Management Guide for information on specifying user names. Messages From the The following errors might be generated by the DSNM parser, which interprets your DSNM Parser commands before they are executed.
Messages Messages From the DSNM Parser Invalid Error Number: error Cause. An error that DSNM does not recognize occurred during the processing of your command. This is the mechanism by which file system errors associated with Tandem data communications subsystems other than AM3270, EXPAND, SNAX/CDF, SNAX/XF, TR3271 or X25AM are reported. Effect. The effects of this problem will vary, depending on the individual situation. Recovery.
Messages Messages From the DSNM Parser Recovery. Correct and reissue the command. Name too long Cause. You entered a name that is longer than the maximum legal length. Effect. Your command was not executed. Recovery. Correct the name and reissue the command. No operands Cause. You issued a command that requires operands, but did not specify any. Effect. Your command was not executed. Recovery. Correct and reissue the command. Reserved word misplaced Cause.
Messages Messages From the DSNM Parser Unexpected end Cause. The command did not include all required and expected information. Effect. Your command was not executed. Recovery. Correct and reissue the command. Unexpected error: text Cause. There is an internal problem in the software that issued the message. Effect. The effects of this problem will vary, depending on the individual situation. Recovery. Note the error text and contact a Tandem representative.
Index A ABORT command 2-8, 2-9, 2-10, 5-5, 5-10, 5-13, 5-16, 5-19, 5-21 contrasted with STOP command 2-33 ACCEPT parameter 4-10 AGGREGATE command 2-11, 2-12 Aliases examples 3-6 specifying 3-6 ALL value 4-2 AM3270 5-2 control commands 5-3 hierarchy modifier 5-3 object types 5-2 states 5-2 ANSWER command 7-2, 7-4 Automation I process 5-1, 5-22 B BREAK command 7-5 key 7-5 message 7-5 BREAK command 7-2 BREAK key 2-7 BRIEF modifier 4-7 BRIEF value 4-7 C Canceling commands 2-7 CLEANUP command 7-2, 7-6 Command se
Index D Define Process commands, from NetCommand 6-10 DEFINED modifier 4-5 DEFINED value 4-5 DETAIL modifier 4-7 DETAIL value 4-7 DOWN object state induced by use of the ABORT command 2-9 induced by use of the STOP command 2-33 DOWN value 4-3 DSNM error messages A-1 functions of 1-1 parser messages A-11 DSNM Commands ABORT 2-8, 2-9, 2-10 AGGREGATE 2-11, 2-12 functions 2-1 INFO 2-13, 2-14, 2-15 INQUIRE 2-16, 2-17, 2-18, 2-19, 2-20 list of 2-3 specifying objects within 2-3, 2-4, 2-5 START 2-21, 2-22, 2-23 ST
Index E ENV command 6-4, 6-8 EOF command 7-2, 7-6, 7-7 Error messages A-1 Error modifier 4-6 ERROR-BRIEF 4-6 ERROR-DETAIL 4-6 ERROR-SUPPRESS 4-6 ERROR-BRIEF value 4-6 ERROR-DETAIL value 4-6 ERROR-SUPPRESS value 4-6 Expand 5-4 control commands 5-5 hierarchy modifier 5-5 object types 5-4 states 5-4 F FC (fix command) 6-8 FC (fix command), from NetCommand 6-8 FROM-DISPLAY parameter 4-10 G Groups specifying 3-8, 3-9 specifying members 3-9 Guardian hierarchy modifier 5-6 object types 5-6 states 5-6 Guardian as
Index Highlight modifier 4-5, 4-6 ACCEPTABLE 4-5 DEFINED 4-5 MONITORED 4-5 NOT-MONITORED 4-5 UNACCEPTABLE 4-5 UNDEFINED 4-5 HISTORY command 6-8 HISTORY command, from NetCommand 6-8 I INFO command 2-13, 2-14, 2-15, 5-3, 5-5, 5-10, 5-13, 5-16, 5-19, 5-21 Information retrieval commands 2-1 INQUIRE command 2-16, 2-17, 2-18, 2-19, 2-20, 5-7, 5-17 K Keywords 5-1 KILL command 7-2, 7-8 L Lists of nested object specifications 3-5, 3-8 LOGON command 6-2 M Modifiers 4-1 BRIEF 4-7 description of 2-5 DETAIL 4-7 error 2
Index N NetCommand 6-1 command output to printer 6-7 Define Process commands 6-10 ENV command 6-4, 6-8 EXIT command 6-3 exiting 6-3 getting help 6-4 HELP command 6-4, 6-8 logging off 6-3 LOGOFF command 6-3, 6-8 LOGON command 6-8 running applications 6-9 running utilities 6-9 security 6-7 SETPROMPT command 6-6, 6-8 standard command set 6-8 starting 6-2 terminal 6-2 NetStatus 2-38, 6-1 NETSTATUS command, from NetCommand 6-8 NOMONITOR parameter 4-10 NonStop NET/MASTER MS additional DSNM commands within 7-2 is
Index DOWN 1-5 IN ERROR 1-5 UNDEFINED 1-5 UNKNOWN 1-5 UP 1-5 Objects examples of names 3-6 specifying 3-5, 3-8 ONLY value 4-2 P Parameters 2-6 ACCEPT 2-6, 4-10 FROM DISPLAY 2-6 FROM-DISPLAY 4-10 MONITOR 4-10 MONITOR and NOMONITOR 2-6, 4-10 NOMONITOR 4-10 RESET 2-6 Reset 4-10 Pathway 5-8 control commands 5-10 hierarchy modifier 5-9 object types 5-8 states 5-9 Pathway groups specifying 3-11 Q Qualifiers specifying 3-9, 3-10 R RESET parameter 4-10 Response modifier 4-7, 4-8, 4-9 BRIEF value 4-7 DETAIL 4-7 SUM
Index S SEND command 7-2, 7-4, 7-5, 7-6, 7-7, 7-8, 7-9, 7-10 SETPROMPT command 6-6, 6-8 SNAX/CDF 5-11 control commands 5-13 hierarchy modifier 5-12 object types 5-11 states 5-12 SNAX/XF 5-14 control commands 5-16 hierarchy modifier 5-15 object types 5-14 states 5-15 Specifying aliases 3-6 composite components 3-10 composites 3-10 Group members 3-9 Groups 3-8 objects 3-5, 3-8 Pathway groups 3-11 qualifiers 3-10 Specifying objects 2-3, 2-4, 2-5 Spooler 5-17 hierarchy modifier 5-17 object types 5-17 states 5-
Index STOP command 2-33, 2-34, 2-35, 5-5, 5-10, 5-13, 5-16, 5-19, 5-21 contrasted with ABORT command 2-8 SUBONLY value 4-2 Subsystems See entries under each subsystem name commands supported by 2-1 definition of 1-2 object states 1-4 supported by DSNM 1-2 SUMMARY value 4-7 SUMMARY-BYOBJECT value 4-7 SUMMARY-BYTYPE value 4-7 T TR3271 5-18 hierarchy modifier 5-19 object types 5-18 states 5-18 U UNACCEPTABLE value 4-5 UNDEFINED value 4-5 UP object state induced by use of the START command 2-21 UP value 4-3 UP
