Compaq NonStop™ Pathway/XM System Management Manual Abstract This manual describes the interactive management interface to the Compaq NonStop™ Pathway/XM product, which provides enhanced, simplified system management; increased system capacity; automatic load balancing; and other features for managing Pathway applications. Product Version Pathway/XM 1.
Document History Part Number Product Version Published 136665 Pathway/XM 1.0 December 1997 426761-001 Pathway/XM 1.5 October 2000 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
Compaq NonStop™ Pathway/XM System Management Manual Index Examples Figures Tables What’s New in This Manual vii About This Manual ix 1. What Chapters Do You Need? 2.
5. Configuring Clients and Requesters Contents Keeping Development and Production Separate Using the PXMCFG Utility 4-4 4-4 Writing a PXMCFG Source File 4-7 Configuring Global Parameters 4-14 Configuring Global Resources and Defaults 4-15 Configuring the PATHMON Processes 4-21 Rolling Configurations 4-23 5. Configuring Clients and Requesters Configuring TCP Templates 5-1 Configuring ROUTER Objects 5-7 Configuring TERM and PROGRAM Objects 5-9 6.
9. Managing Servers Contents Displaying Information About Client and Requester Objects Sending Messages to Terminal Users 8-7 8-12 Managing Exception Conditions 8-13 9. Managing Servers Starting Server Classes 9-1 Freezing and Thawing Server Classes 9-4 Reconfiguring Distributed Server Classes Online 9-5 Displaying Information About Servers 9-6 Stopping Server Classes 9-10 Queue-Management Algorithm Used by the LCS Processes 9-11 10. PXMCFG Statements and PXMCHK Utility 11. PXMCOM Commands 12.
B. Pathway/XM Reserved Words Contents B. Pathway/XM Reserved Words C. Configuration Limits and Defaults D. Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment E. Migrating Pathway Applications to the Pathway/XM Environment F.
Tables Contents Figure 7-2. Using PXMCOM Commands to Manage a Pathway/XM Environment 7-5 Tables Table i. Related NonStop™ TS/MP and Pathway/iTS Manuals by Software Release xvii Table ii. Related NonStop TM/MP Manuals by Software Release xix Table 1-1. Management Tasks and Manual Sections Table 2-1. Supported Releases 2-4 Table 4-1. Migration Considerations: Object Attribute Values Table 5-1. Storage Capacity of T16-6520 Terminal 5-22 Table 5-2.
Contents Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 vi
What’s New in This Manual Manual Information Pathway/XM System Management Manual Abstract This manual describes the interactive management interface to the Compaq NonStop™ Pathway/iTS product, which provides enhanced, simplified system management; increased system capacity; automatic load balancing; and other features for managing Pathway applications. Product Version Pathway/XM 1.
New Objects What’s New in This Manual New Objects The following objects have been added: PLAN, ROUTER, SERVICE New PXMCFG Commands ADD ROUTER ENABLE ROUTER RESET ROUTER SET ROUTER ADD SERVICE RESET SERVICE SET SERVICE EXPORT INVENTORY PXMCFG Statement Changes The following SET PATHWAY attributes are automatically set to the maximum value and are no longer valid in statements: MAXASSIGNS MAXPARAMS MAXDEFINES MAXSTARTUPS New PXMCOM Commands INFO GROUP INFO PLAN INFO ROUTER START PLAN START ROUTER STA
About This Manual This manual is both a task-oriented and a reference manual. It gives instructions and guidelines for configuring and managing objects in the Compaq NonStop™ Pathway/XM environment using the PXMCFG, PXMCHK, and PXMCOM utilities. It also provides syntax and complete descriptions of all PXMCFG statements and PXMCOM commands and gives cause, effect, and recovery information for all messages returned by these utilities.
Related Documentation About This Manual Table i. Related NonStop™ TS/MP and Pathway/iTS Manuals by Software Release NonStop™ Kernel Release D36.
Related Documentation About This Manual Table ii. Related NonStop TM/MP Manuals by Software Release NonStopTM Kernel OS Release Product Version G02.00 and later G-series releases; D46.00 and later D4x releases D40 and later D36.
About This Manual Your Comments Invited Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the Compaq User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
About This Manual Notation Conventions Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. 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.
About This Manual Notation for Messages An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
About This Manual Notation for Messages [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
About This Manual Notation for Messages Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 xvi
1 What Chapters Do You Need? Which Sections Do You Need? This manual is organized into logical groups of information for easy reference. Table 1-1 is a descriptive map showing which sections of this manual are relevant to particular system management tasks. For each listed task, the “You Need...” column provides the page numbers of one or more manual sections or subsections that pertain to that task. Table 1-1.
What Chapters Do You Need? Which Sections Do You Need? Table 1-1.
2 Pathway/XM Benefits and Features Compaq NonStop™ Pathway/XM simplifies the management of Pathway applications by means of several features. It provides a centralized configuration and management interface with automatic load balancing, online reconfiguration and replacement of servers, simplified object naming, and an increased overall system capacity.
Pathway/XM Benefits and Features Automatic Load Balancing of Requester and Server Processes external TCPs, external PATHMON processes, or associative servers. If separate management is required for multiple applications, multiple Pathway/XM environments can run on the same set of Compaq NonStop™ Himalaya systems. In addition, the abstraction provided by logical configurations allows your application to grow easily.
Pathway/XM Benefits and Features Predefined Configuration Files Predefined Configuration Files With Pathway/XM, you perform configuration offline, in advance. Thus you can generate multiple predefined configurations and manage your configurations as you manage versions of your application software. Even if you make temporary changes while managing a running application, your initial configuration is always saved, and you do not need to generate OBEYFORM output.
Use of Existing NonStop™ TS/MP and Pathway Software Pathway/XM Benefits and Features In addition to distributed server classes for dynamic load balancing, Pathway/XM also provides direct and replicated server classes for backward compatibility with existing applications. Use of Existing NonStop™ TS/MP and Pathway Software Pathway/XM is layered on top of the PATHMON/PATHCOM management interface provided by the NonStop™ TS/MP and Compaq NonStop™ Pathway/iTS products.
Pathway/XM Benefits and Features Supported Releases NonStop™ TM/MP product (including the IPMs applicable to the NonStop™ Kernel release being used). The NonStop™ TS/MP product is required. For most applications for which the Pathway/XM environment is designed (all applications including SCREEN COBOL requesters), Pathway/iTS is also required. The NonStop™ TM/MP product is also required if you are using distributed server classes.
Pathway/XM Benefits and Features Supported Releases Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 2 -6
3 Overview of Configuring and Managing Pathway/XM This section describes the processes and basic operation of a Compaq NonStop™ Pathway/XM environment and introduces the tasks you perform to manage a Pathway/XM environment.
Building a Pathway/XM Configuration Overview of Configuring and Managing Pathway/XM Then you run the PXMCFG utility, specifying your configuration source file as input. The PXMCFG utility creates a SuperCTL file using the statements in the configuration source file. Figure 3-1 illustrates a configuration for a Pathway/XM environment. Figure 3-1.
Overview of Configuring and Managing Pathway/XM Managing a Pathway/XM Environment PXMCFG then configures multiple instances of the components as required by your specified configuration parameters. Later, at run time, PXMCOM and other Pathway/XM components create instances of some components, such as screen programs and server processes, as needed by your running application.
Managing a Pathway/XM Environment Overview of Configuring and Managing Pathway/XM Figure 3-2.
Components of the Pathway/XM Environment Overview of Configuring and Managing Pathway/XM Components of the Pathway/XM Environment Figure 3-3 shows the major components of a Pathway/XM environment and how they interrelate. This figure includes some components that are created automatically by Pathway/XM without your needing to configure them, such as process broker (PB) processes and link control service (LCS) processes. Figure 3-3.
Overview of Configuring and Managing Pathway/XM PXMCFG Utility PXMCFG Utility The PXMCFG utility generates the initial configuration of a Pathway/XM environment. PXMCFG uses the statements in the configuration source file to build the SuperCTL file. You run the PXMCFG utility offline (in batch mode) before starting the Pathway/XM environment.
Overview of Configuring and Managing Pathway/XM PATHMON Processes and PATHCTL Files Logical nodes are configured objects that specify available processor resources to be used for requesters or servers. One PB process, running as a process pair, is provided for each logical node in the Pathway/XM environment. PATHMON Processes and PATHCTL Files The PATHMON object represents a PATHMON process, which controls a set of requester-related and server-related objects in a Pathway/XM environment.
Overview of Configuring and Managing Pathway/XM Terminal Control Processes (TCPs) Terminal Control Processes (TCPs) Terminal control processes (TCPs) provide terminal management and transaction control. A TCP is a multithreaded process that interprets compiled SCREEN COBOL requester programs (screen programs) in the user’s application, executing the appropriate program instructions for each I/O device or process the TCP is configured to handle.
Overview of Configuring and Managing Pathway/XM Server Classes and Server Processes Server Classes and Server Processes A server class is a group of processes that provide services to requesters, such as SCREEN COBOL requester programs (running as terminal tasks) or Pathsend requesters. Processes in a server class typically perform a specific type of application work (for example, adding customer names and addresses, calculating invoice totals, or checking inventory).
Overview of Configuring and Managing Pathway/XM How Pathway/XM Balances the Transaction Workload Pathsend requesters are either user-written or provided as part of Compaq or third-party products. For example, workstation clients that use Compaq NonStop™ Remote Server Call/MP (RSC/MP) communicate with Pathway servers indirectly by means of Pathsend requesters created by RSC on behalf of the clients.
Overview of Configuring and Managing Pathway/XM Load Balancing Requests from Pathsend processes for distributed server classes are handled in the same way as other transaction requests, with one difference. Pathsend requests are always directed to the one PATHMON process in the Pathway/XM environment that has an external name, and are serviced by the server processes controlled by that PATHMON process.
Overview of Configuring and Managing Pathway/XM Pathway/XM Analyst Configuration Tool When a processor is reloaded, the LCS rebalances the server processes in the system to take advantage of the additional processor. This is done gradually over time, in parallel with the servicing of the queue by existing server processes.
4 Configuring the Pathway/XM Environment This section describes how to get started in configuring a Compaq NonStop™ Pathway/XM environment. It provides general information about the configuration process, and also describes how to configure global parameters and objects for the Pathway/XM environment.
Two Approaches to Configuring Objects Configuring the Pathway/XM Environment Two Approaches to Configuring Objects You can configure your Pathway/XM environment in either of two ways: • • Create a configuration source file by manually keying in all the statements. Then use the PXMCFG utility to create a SuperCTL file. This is a batch-type approach. Use the Pathway/XM Analyst tool, which provides an interactive approach.
Configuring the Pathway/XM Environment PATHMON Object PATHMON Object The PATHMON object is a template for configuring PATHMON processes, each of which controls a set of requester-related and server-related objects in a Pathway/XM environment. The objects controlled by a PATHMON process include terminal control processes (TCPs), TERM objects, PROGRAM objects, and SERVER objects. A Pathway/XM environment includes one or more PATHMON processes, all of which have the same configuration attributes.
Configuring the Pathway/XM Environment SERVER Objects SERVER Objects A SERVER object represents a server class, which is a set of duplicate copies of a single server process. All server processes in a server class use the same object program. The TYPE attribute of a server class determines whether it is managed as a distributed, direct, or replicated server class.
Configuring the Pathway/XM Environment Input to PXMCFG Then you run PXMCFG, specifying your configuration source file as the input file and giving a file name to be used for the SuperCTL file. For detailed syntax of the command you use to run PXMCFG, refer to Starting PXMCFG on page 10-2. The PXMCFG utility creates a new SuperCTL file, builds the initial configuration of the Pathway/XM environment as specified in your source file, and places that configuration in the SuperCTL file.
Configuring the Pathway/XM Environment Checking Process Capacity For cause, effect, and recovery information about the individual error and warning messages that can appear in your PXMCFG listing, refer to Section 12, PXMCFG Messages. Example 4-1.
Configuring the Pathway/XM Environment Writing a PXMCFG Source File Therefore, after you run PXMCFG, it is recommended that you review the last page (summary page) of your PXMCFG output and compare it with the SYSGEN configuration for your application system. If the number of processes per CPU in your SYSGEN configuration is inadequate, increase the parameter value in SYSGEN.
Configuring the Pathway/XM Environment Using the SET and ADD Statements 1. Define the attributes for the object, using a SET statement parameter for each attribute. PXMCFG scans your attribute definitions in order, checking them for syntax errors. PXMCFG saves the attributes as a working set, pending your request to add the objects to your configuration. In many cases, you can choose to accept default values supplied by PXMCFG. 2. Add the object to your configuration with the ADD statement.
Using the SET and ADD Statements Configuring the Pathway/XM Environment Figure 4-1. Defining and Adding a Pathway/XM Object SET SERVER TYPE DISTRIBUTED SET SERVER MAXSERVERS 2 SET SERVER PROGRAM \PARIS.$MARKT.DEPT SET SERVER SECURITY “N” ADD SERVER SRVR-X PXMCFG SuperCTL File SERVER • • • TYPE DISTRIBUTED • • • MAXSERVERS 2 • • • PROGRAM \PARIS.$MARKT.DEPT • • • SERVER SRVR-X CDT 018.
Configuring the Pathway/XM Environment Understanding the Working Set of Attribute Values Understanding the Working Set of Attribute Values PXMCFG maintains a working set of attribute values for objects you define in your Pathway/XM environment. These objects include NODE, SERVER, TCP, TERM, PROGRAM, ROUTER, and SERVICE objects. The working set of attribute values is initialized when you start PXMCFG.
Configuring the Pathway/XM Environment Understanding the Working Set of Attribute Values All of these SERVER objects have the same TYPE attribute (namely, DISTRIBUTED). FRED and JOAN have a NUMSTATIC value of 1, while DON and MARY have a NUMSTATIC value of 2. In addition, MARY has an AUTORESTART value of 1. Each SERVER object has a unique PROGRAM attribute. Figure 4-2 shows the attribute values for the SERVER object named MARY being added to the SuperCTL file. Figure 4-2.
Configuring the Pathway/XM Environment Using Existing Object Attributes for New Objects Overriding Working-Set Values When you add an object, you can temporarily override the current attribute values in the PXMCFG working set by specifying other values in the ADD statement.
Configuring the Pathway/XM Environment Choosing Object Names Choosing Object Names When adding multiple objects of any one kind, you should name them in a logical way that makes them easy to identify and manage later. For example, you might name SERVER objects according to the functions they perform: ORDERS for a server class that processes orders or INV for one that updates inventory control records.
Configuring the Pathway/XM Environment Configuring Global Parameters Configuring Global Parameters The SET PATHWAY statement enables you to define global limits for your configuration and to specify node-independent, owner, and security attributes. These tasks are described in the following paragraphs. For the complete syntax of the SET PATHWAY statement, including descriptions of all the attributes you can set for the PATHWAY object, refer to SET PATHWAY on page 10-32.
Configuring the Pathway/XM Environment Configuring Global Resources and Defaults The next example specifies that only the super ID user can modify the Pathway/XM environment: SET PATHWAY OWNER 255,8 SET PATHWAY SECURITY "O" Before the START PATHWAY statement is processed, the owner ID is always the process accessor ID of the PXMCOM process and the security value is “O” (owner). Note.
Configuring the Pathway/XM Environment Specifying the System (Physical Node) Specifying the System (Physical Node) The SYSTEM attribute specifies the name of the NonStop™ Himalaya system to which the NODE object applies. All processes to which this NODE object applies will be started in the specified CPUs (given in the CPUS attribute) on the specified Compaq system. If this attribute is not defined, PXMCFG uses the name of the system on which it is running.
Configuring the Pathway/XM Environment Specifying the Default Volume and Subvolume will run, on the average, only one-fourth as many processes (for this NODE object) as run in CPUs 3 and 5. More than one NODE object can specify the same set of CPUs. In this case, the processes assigned to both NODE objects will run in those CPUs. Assigning a weight of 0 to a CPU, specifies that the CPU is available to be used only after another CPU has failed.
Specifying the Default Home Terminal Configuring the Pathway/XM Environment runs with the specified priority value minus an offset value associated with the type of process, as follows: Process Type Default Priority Value PATHMON NODE object priority minus 0 Process broker (PB) NODE object priority minus 1 Link control service (LCS) NODE object priority minus 3 TCP NODE object priority minus 5 Server Process NODE object priority minus 10 For example, suppose you issue the following SET NODE st
Configuring the Pathway/XM Environment Configuring Object Attributes for Future Migration Configuring Object Attributes for Future Migration In the future, you might need to migrate your Pathway/XM environment to a different set of NonStopTM Himalaya systems (physical nodes), either because of a system failure or as part of a planned migration (for example, in a configuration that includes Nomadic Disk technology).
Configuring the Pathway/XM Environment Configuring Object Attributes for Future Migration Table 4-1. Migration Considerations: Object Attribute Values (page 2 of 2) Object or Process Attribute Considerations/ Recommendations PARAM param-string Could include system name stored as buffer; check and change manually if required. STARTUP startupstring Could include system name stored as buffer; check and change manually if required.
Configuring the Pathway/XM Environment Adding a NODE Object Adding a NODE Object After you have set all the attributes for a NODE object, you add the NODE object with an ADD statement.
Configuring the Pathway/XM Environment Defining the Well-Known Named PATHMON Process Expand node (SYSTEM value) defined in the set of client NODE objects in your configuration. The client NODE objects used for PATHMON processes can be the same as those used for TCPs or can be a separate client NODE object used just for PATHMON processes.
Configuring the Pathway/XM Environment Rolling Configurations Rolling Configurations Rolling configurations allow you to update your Pathway/XM configuration online. In other words, you do not have to stop and then restart your Pathway/XM environment when migrating to a new configuration. To prepare for a migration, you use PXMCFG or the Pathway/XM Analyst tool to create a new SuperCTL file.
Configuring the Pathway/XM Environment Rolling Configurations Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 4- 24
5 Configuring Clients and Requesters This section describes how to define objects related to terminal (SCREEN COBOL) requesters and add these objects to your Compaq NonStop™ Pathway/XM configuration. You define and add requester-related objects after you have configured your global Pathway/XM environment as described in Section 4, Configuring the Pathway/XM Environment.
Configuring Clients and Requesters • • • Defining TCP Attributes Servicing SCREEN COBOL SEND requests by sending request messages to server processes and receiving reply messages back Gathering statistics about TERM objects, the server processes, and the TCP itself Reporting operating errors and status information to the PATHMON process Defining TCP Attributes You use the SET TCP and ADD TCP statements to define the TCP attributes for a TCP template, name the TCP template, and add it to your Pathway/XM
Defining TCP Attributes Configuring Clients and Requesters MAXSERVERPROCESSES Specifies the maximum number of server processes, distributed among all server classes, with which each TCP can communicate simultaneously. MAXWEIGHTS Specifies the maximum total terminal weight value allowed for any TCP based on this TCP template. MAXINPUTMSGS Specifies the maximum number of unsolicited messages that each TCP queues at any one time for any TERM object under its control.
Configuring Clients and Requesters Setting Process Priority Setting Process Priority As described in Section 2, the PRI attribute of the NODE object allows you to set a default base process priority value for the various types of processes in your Pathway/XM environment, including TCPs. However, for TCPs created with a specific TCP template, you can override the PRI setting in the associated client NODE object by specifying the PRI attribute in the SET TCP statement.
Configuring Clients and Requesters Configuring High or Low PINs Configuring High or Low PINs The setting of the HIGHPIN attribute for the TCP template affects whether the TCP processes can run at high process identification numbers (PINs). TCPs can be created at high PINs if the following conditions are met: • • The HIGHPIN option is set to ON for the TCP template. (The default value is OFF.) There is a high PIN available.
Configuring Clients and Requesters Specifying Maximum Server Classes and Server Processes per TCP Specifying Maximum Server Classes and Server Processes per TCP The MAXSERVERCLASSES and MAXSERVERPROCESSES attributes specify the maximum number of server classes and server processes, respectively, with which each TCP can communicate simultaneously.
Configuring Clients and Requesters Configuring TCPs for Pathway/iTS You have two choices for naming the library object file: • • You can name the customized library $SYSTEM.SYSTEM.PATHTCPL. You can name the customized library file something other than $SYSTEM.SYSTEM.PATHTCPL, such as $SKY.KING.USERTCPL. If you keep the name $SYSTEM.SYSTEM.PATHTCPL for your customized library file, you need not explicitly configure the library file name.
Support for ROUTER Objects Configuring Clients and Requesters Support for ROUTER Objects Before you define and add a ROUTER object, you must enable the router feature. Check the following table; if your Pathway/XM environment is running on an operating system release for which the router default is DISABLED, you must specify an ENABLE ROUTER statement before the SET ROUTER statement. NonStopTM Kernel OS* Pathway/XM Product Version 1.0 D32 1.0 D42 1.5 D38 1.
Configuring Clients and Requesters • • • Configuring TERM and PROGRAM Objects NONSTOP specifies whether the router process runs as a process pair. INSPECT specifies whether you can use the Inspect program to examine the SCREEN COBOL programs running on the terminals handled by the router process. The SET TCP INSPECT attribute also must be set to ON. PRINTER specifies the name of the print device for each temporary TERM object associated with this ROUTER object.
Configuring Clients and Requesters Configuring TERM Objects 10 to 15 operator terminals monitor the system using several different informationgathering Pathway applications. A Pathway application can support up to 4095 configured TERM objects. Thus, it is often appropriate to use TERM objects for large networks of terminals dedicated to a single application.
Configuring Clients and Requesters Configuring TERM Objects names, you can perform management operations on an entire group of terminals with a single PXMCOM command. • • • BREAK specifies whether the TCP accepts the Break key function for its terminals running in conversational mode. DIAGNOSTIC specifies whether diagnostic screens are displayed to inform the terminal operator when an error condition or termination occurs. TYPE specifies the type of device on which the TERM object runs.
Configuring Clients and Requesters Configuring TERM Objects number of transactions per hour or the number of I/O operations per hour that the terminal generates. You can use the following formula to define initial WEIGHT values for your TERM objects based on collected TERM object statistics and configuration information.
Configuring Clients and Requesters Configuring PROGRAM Objects You can define a terminal to belong to more than one group. You do this by using multiple SET statements, as in the following example: SET SET SET SET ADD TERM TERM TERM TERM TERM GROUP INQUIRY GROUP MONDAY GROUP WEDNESDAY GROUP FRIDAY TERM-17, FILE $T017 Configuring PROGRAM Objects PROGRAM objects are templates used by the PATHMON process when creating and starting temporary TERM objects.
Configuring Clients and Requesters Configuring PROGRAM Objects type. (In a SCREEN COBOL program, the program name is the name specified in the PROGRAM-ID paragraph of the Identification Division.) Because your screen programs can run on many different types of devices or processes, you can also use the TYPE attribute to specify the different options that these devices or processes require.
Configuring Clients and Requesters Configuring PROGRAM Objects For example, you could issue the following statements to define all temporary TERM objects based on the PROGRAM object SALES as members of a group called TELEMKT: SET SET SET ADD PROGRAM PROGRAM PROGRAM PROGRAM GROUP TELEMKT TCP TCP-PRIME TYPE IBM-3270 (INITIAL MENU-3270) SALES After your Pathway/XM environment and its objects are configured and started and the SALES program is running on a number of terminals, you can then issue a single S
Configuring Clients and Requesters Setting TMF Parameters Setting TMF Parameters The SET TERM and SET PROGRAM statements each include a TMF parameter with an ON or OFF option: • • TMF ON: The TCP invokes the corresponding operating system procedure for any TMF statement issued from a SCREEN COBOL program. ON is the default setting whether or not the TMF software is running.
Setting TMF Parameters Configuring Clients and Requesters affect the action of a SCREEN COBOL SEND statement when the TMF subsystem is running. Figure 5-1.
Setting TMF Parameters Configuring Clients and Requesters Figure 5-2.
Configuring Clients and Requesters Setting TMF Parameters When you include a TIMEOUT clause in the SET SERVER statement, all SEND operations to that server class are timed by the TCP. If the specified number of seconds elapses after a SEND operation is initiated and before a reply is received, the TCP issues a Guardian CANCEL procedure call against the outstanding I/O to the server.
Configuring Clients and Requesters Setting the DISPLAY-PAGES Parameter for Terminal Devices retry the write operations, so there is no need to back out the write. In contrast, a key-sequenced file requires a transaction backout; otherwise, the transaction will fail when the second write is attempted at the same location. TMF Parameters and TMF Errors If a TMF error occurs and makes normal operations impossible, do not attempt to continue normal operations by setting the TMF parameter options to OFF.
Configuring Clients and Requesters Setting the DISPLAY-PAGES Parameter for Terminal Devices terminal maintains to record field characteristics (for example, brightness or blinking versus non-blinking). The DISPLAY-PAGES parameter determines how much terminal memory is used for the screen-image area compared to how much is used for the field-attribute entries area. The more memory assigned to one, the less available to the other.
Setting the DISPLAY-PAGES Parameter for Terminal Devices Configuring Clients and Requesters information in the following paragraph helps you estimate the number of field-attribute entries. The tables in the remainder of this section help you match terminal type to the average number of field-attribute entries to determine the appropriate DISPLAYPAGES value. Using the appropriate DISPLAY-PAGES value allows a terminal to achieve its highest performance level without exceeding its fixed amount of RAM.
Setting the DISPLAY-PAGES Parameter for Terminal Devices Configuring Clients and Requesters Table 5-3 lists the average number of field-attribute entries a T16-6530 terminal can store. Table 5-3. Storage Capacity of T16-6530 Terminal DISPLAY-PAGES Value Average Number of Field-Attribute Entries per Screen 1 4095 2 2510 3 1488 4 976 5 670 6 465 7 319 8 209 Table 5-4 lists the average number of field-attribute entries a TS530 terminal can store.
Configuring Clients and Requesters Configuring Dummy Terminals for Future Expansion Configuring Dummy Terminals for Future Expansion If desired, you can configure dummy TERM objects so that you can add new terminals later without rerunning PXMCFG. You define such TERM objects by omitting the FILE attribute (which specifies the terminal device or process name) in the SET TERM statement. The resulting TERM objects cannot be operated on by any PXMCOM commands except INFO TERM and CONTROL TERM.
6 Configuring Servers This section describes how to define server-related objects (server classes and SERVICE objects) and add them to your Compaq NonStop™ Pathway/XM configuration. You define and add server classes after you have configured your global Pathway/XM environment as described in Section 4, Configuring the Pathway/XM Environment. You can define your server classes either before or after you define requester-related objects as described in Section 5, Configuring Clients and Requesters.
Configuring Servers Required and Optional Attributes In addition, you can specify a number of optional attributes for server classes or accept default values for them. Among the optional attributes are the following: TYPE Specifies the way Pathway/XM manages the server processes in the server class, and has three options: DISTRIBUTED, REPLICATED, and DIRECT.
Configuring Servers Example Example For example, the following sequence of PXMCFG statements defines a SERVER object and then adds it under the server-class name ORDER-SRV: RESET SERVER SET SERVER NODE SERVER-1 SET SERVER PROGRAM $DATA.SRVRS.ORDSRV SET SERVER GROUP ORDERS SET SERVER GROUP THURSDAY SET SERVER CMON ON SET SERVER HIGHPIN ON SET SERVER MAXSERVERS 5 SET SERVER NUMSTATIC 3 SET SERVER NONSTOP 0 SET SERVER TMF ON SET SERVER ASSIGN ORDERS, $DATA.REG1.ORDFILE SET SERVER ASSIGN PARTS, $DATA.REG2.
Configuring Servers • • Defining the Server-Class Type The files that your server program recognizes by the names ORDERS and PARTS are the files $DATA.REG1.ORDFILE and $DATA.REG2.PARTFILE, respectively. When the PATHMON process starts a server process, it transmits the following PARAM message: SWITCH-1 “ON” Defining the Server-Class Type The TYPE attribute determines the way in which Pathway/XM manages the server processes within the server class.
Configuring Servers Defining Server Groups Direct and Replicated Server Classes Direct and replicated server classes allow you to use existing servers that were coded to depend on the process-management and link-management mechanisms used by NonStop™ TS/MP and Compaq NonStop™ Pathway/iTS without Pathway/XM. These server-class types allow you to migrate your applications more gradually to the Pathway/XM environment. Direct server classes are comparable to the server classes defined by NonStop™ TS/MP.
Interfacing to a $CMON Process Configuring Servers later operate on or display information about an entire group of server classes with a single PXMCOM command by specifying the group name instead of the object name. For example, you could issue the following statements to define three server classes as members of a group called ORDERS (assuming the NODE attribute has already been defined): SET ADD ADD ADD SERVER SERVER SERVER SERVER GROUP ORDERS GROCERY, PROGRAM $PGM.GROC HEALTH, PROGRAM $PGM.
Configuring Servers Configuring the MAXSERVERS and NUMSTATIC Attributes To ensure that Pathway/XM can create as many processes as needed, you should compile your server programs with the ?HIGHPIN attribute set to ON, and you should set the HIGHPIN attribute to ON for all server classes in your configuration.
Configuring Servers Setting the NONSTOP Attribute It is recommended that for a direct server class, you set these two attributes to the same value, so that all server processes in the direct server class are static (that is, are created when the server class is started). For replicated server classes, the NUMSTATIC attribute defines the number of static server processes under each PATHMON process for the server class.
Configuring Servers Setting the TMF Parameter Setting the TMF Parameter The SET SERVER statement includes a TMF parameter with an ON or OFF option: • • TMF ON: The TCP allows a SCREEN COBOL SEND operation, or the LINKMON process allows a Pathsend server-class send operation, to members of this server class whether or not the SCREEN COBOL or Pathsend requester program is in transaction mode.
Configuring Servers Specifying Process Names for Direct Server Processes Among the file attributes that you can specify with ASSIGN are disk extent size, access exclusion mode, file code, and record and block size. PARAM PARAM assigns a string value to a parameter name, which the PATHMON process then sends in a PARAM message to each server process as it starts. You can include multiple PARAM specifications for a server class, just as you can include multiple ASSIGN specifications.
Configuring Servers Configuring Dummy Distributed Server Classes for Future Expansion example, you might later want to define a new server class to perform new services on behalf of terminal requesters. To define a dummy server class, you configure a SERVER object with the TYPE attribute set to DISTRIBUTED and with required attributes assigned, but without defining optional attributes (such as the PROGRAM attribute) that can be assigned later.
Configuring Servers Configuring Server Classes for Import (SERVICE objects) When you configure a dummy server class, you must specify the NODE and NONSTOP attributes, because they are required for distributed server classes. (For a distributed server class, you must set the NONSTOP attribute to 0.
Configuring Servers Required and Optional Attributes Required and Optional Attributes The following SERVICE object attributes are required: • • FILE specifies the SuperCTL file that contains the server definitions to be imported. NODE specifies the NODE object to which the imported servers are to be linked When you add a SERVICE object, you must specify an object name.
Configuring Servers Configuring SERVICE Objects Note that the following items must match before PXMCFG overwrites the name, otherwise an error is returned: 1. In the export statement, the variable type (PROCESS) must be the same as the attribute type, which in this example is a process. 2. In the import statement, the variable type (PROCESS) must match the type in the export statement. 3. In the import statement, the variable name (PRNAME) must match the name in the export statement.
Configuring Servers Specifying server groups Specifying server groups The GROUP attribute allows you to assign one or more group names to the set of server classes being imported. The name is then automatically added to the configuration of each SERVER object when it is imported; group names originally defined for the server classes remain unchanged.
Configuring Servers Exporting Nested Server Class Definitions Exporting Nested Server Class Definitions When preparing a set of server class configurations for export, you can nest configuration statements by including SERVICE object definitions that import server class configurations from elsewhere.
7 Managing a Pathway/XM Environment This section describes how to manage and maintain your global Compaq NonStop™ Pathway/XM environment.
Managing a Pathway/XM Environment NODE Objects shut down the Pathway/XM environment, and to obtain status information about the entire environment. NODE Objects A logical node, or NODE object, defines a set of processor (CPU) resources on a particular Compaq system and, optionally, default object attributes used for either requesters (clients) or servers in the Pathway/XM environment. One process broker (PB) process is created for each NODE object in the Pathway/XM environment.
Managing a Pathway/XM Environment TERM and PROGRAM Objects TERM and PROGRAM Objects TERM objects represent tasks controlling the input-output devices and processes that allow users to interact directly or programmatically with a Pathway application. Each task runs as a thread within a TCP; a TCP can handle many such threads concurrently. There are two types of these objects: configured TERM objects and temporary TERM objects.
Managing a Pathway/XM Environment Starting PXMCOM all the online mananagement functions needed in the Pathway/XM environment. (PATHCOM commands are not needed and should not be used.) Caution. Using PATHCOM commands to change the configuration or to change the state of objects can interfere with Pathway/XM operations and produce unpredictable results; it can cause the Pathway/XM environment to be unbalanced and uncontrollable from PXMCOM.
Starting PXMCOM Managing a Pathway/XM Environment Figure 7-1. Starting PXMCOM and Opening the SuperCTL file 2> PXMCOM 1>> OPEN SCTL1 Command Interpreter SCTL1 CDT 013.CDD You can open a remote SuperCTL file if, for example, you need to configure a Pathway/XM environment on a remote system. If you want to open a SuperCTL file on another node in your Expand network, be sure to use a fully qualified Guardian file name in your command, for example: >> OPEN \NYC.$RMT.
Managing a Pathway/XM Environment Using PXMCOM in Noninteractive Mode Using PXMCOM in Noninteractive Mode If you are specifying lengthy configurations, you probably want to create a command file or a TACL routine that contains your PXMCOM commands. This method permits PXMCOM to read and act upon the commands very quickly. You enter your PXMCOM commands into the command file before starting PXMCOM. When you are ready to start PXMCOM, you specify the name of the file that you want PXMCOM to read.
Managing a Pathway/XM Environment Using the TRACELOG Command to Record Commands and Output PXMCOM session. Several PXMCOM commands are available to select what information is logged and where it is kept. Using the TRACELOG Command to Record Commands and Output The TRACELOG command directs PXMCOM to log all commands you enter, and all output displayed by PXMCOM, to a disk file. This command thus keeps a full record of your PXMCOM session.
Status and Error Messages Managing a Pathway/XM Environment To disable the display of information about PATHCOM commands, you issue the following command: >> VERBOSE OFF The initial setting of the VERBOSE option is OFF. The VERBOSE command displays a large amount of information that can be useful in troubleshooting. For the syntax of the VERBOSE command, refer to VERBOSE on page 11-108.
Managing a Pathway/XM Environment Specifying the Location for Message Logging PXMCOM messages and PATHCOM messages are logged to the OUT file you specify when you start PXMCOM with a TACL RUN command. If you do not specify the OUT parameter in the RUN command, these messages are sent to the current TACL output file; this is typically the home terminal for the TACL process.
Managing a Pathway/XM Environment Specifying the Location for Message Logging once they scroll off the terminal screen; also, performance is generally better to a process on a disk file than to a terminal. Caution. If you log information to a terminal, Compaq recommends restricting activity on that terminal. If the terminal is busy it can cause the Pathway/XM environment to become suspended while waiting to log messages.
Managing a Pathway/XM Environment Displaying Current PXMCOM Operational Settings $DATA.PM.LOGFILE as LOG2 $0, STATUS. The process next sends both error information and status information to $0 because although the LOG1 command did not specify the STATUS parameter, the LOG2 command did. Additionally, the process sends both event messages and text messages to $0 because although the LOG2 command did not specify the EVENTFORMAT parameter, the LOG1 command did.
Managing a Pathway/XM Environment Information in the Control Files Information in the Control Files After you have used PXMCFG to build the SuperCTL file, it contains all of the process and other object definitions needed to start your Pathway/XM environment. However, no processes or objects are created until you run PXMCOM, open the SuperCTL file, and issue the necessary START commands.
Managing a Pathway/XM Environment Cold Starting a Pathway/XM Environment To restart a Pathway/XM environment with a previously started configuration, saving many changes made during previous PXMCOM operation but using new PATHMON configuration (PATHCTL) files, you specify the COOL start option. If an error condition occurs after a warm start, you can often correct the error by doing a cool start.
Managing a Pathway/XM Environment Cool Starting a PATHMON Environment Cool Starting a PATHMON Environment To cool start a Pathway/XM environment, use the COOL start option as follows: >> START PATHWAY COOL In response to this command, PXMCOM performs the following steps, using the current configuration information in the SuperCTL file: 1. Creates the process broker (PB) processes: one PB process pair for each NODE object specified in the configuration. 2.
Managing a Pathway/XM Environment Starting TCP, TERM, and SERVER Objects object is already running when you issue the START command, the PATHMON process displays an error message and makes no attempt to start the object. Starting TCPs Before you start the configured TERM objects, you must start the TCPs associated with them by using one or more START TCP commands. The START TCP command causes the specified TCP processes to be created.
Managing a Pathway/XM Environment Displaying Information About a Pathway/XM Environment The following command starts the server class named QUERIES: >> START SERVER QUERIES The following command starts all server classes in the Pathway/XM environment: >> START SERVER * When the START SERVER command is issued, the processes created for each server class depend on the server-class type.
Managing a Pathway/XM Environment Displaying Configuration Information Displaying Configuration Information The INFO command displays configuration information. You can display configuration information about your overall Pathway/XM environment or about specific objects− PATHMON processes, NODE objects, TCPs, TERM objects, PROGRAM objects, and SERVER objects. You can also display information about specific messages sent to user terminals through the TELL command.
Managing a Pathway/XM Environment Displaying Status Information Various levels of detail can be reported by the STATUS command. For instance, the STATUS SERVER command features an option for reporting the status of each server process in the server class. STATUS PATHWAY Command The STATUS PATHWAY command displays status information about your overall Pathway/XM environment. This command is useful for getting an overview of processes currently running.
Managing a Pathway/XM Environment Displaying Statistics STATUS PATHMON Command The STATUS PATHMON command displays status information for all PATHMON processes in the Pathway/XM environment. For each PATHMON process, the display includes the PATHMON process name, the state (open or closed) of the PATHCTL and log files, and a list of the processes (such as LINKMON processes, TCPs, and PXMCOM processes) currently communicating with this PATHMON process.
Managing a Pathway/XM Environment Migrating Configurations Online currently active configuration to the new configuration. You can execute the migration plan online whenever you are ready. This allows you to create a new configuration on a development system, move the new SuperCTL file to the production system, and then migrate to the new configuration. For example, you might need to add more terminals to your configuration, or you might want to reorganize which servers or terminals are in various groups.
Managing a Pathway/XM Environment Making Temporary Online Adjustments to a Pathway/XM Environment 7. Pathway/XM is successfully migrated to the new configuration when all the PLAN objects are successfully completed. If not all the plans are successful, use STATUS PLAN to diagnose the problem. Fix any error and reissue the START PLAN * command. 8. Start the TCP, TERM, and SERVER CLASS objects.
Redefining CPU Resources Managing a Pathway/XM Environment Table 7-1.
Managing a Pathway/XM Environment Enabling or Disabling Error Dumping for the PATHMON Processes In this example, new server processes in distributed server classes associated with the NODE object SERVER1 will continue to be distributed among CPUs 1, 3, 5, 6, and 9, but the relative distribution of servers among the first four of these CPUs will change.
Managing a Pathway/XM Environment Pathsend Requesters Pathsend Requesters Pathsend requesters are self-contained, user-written Guardian processes that use Pathsend procedure calls, rather than SCREEN COBOL programs and the TCP, to communicate with server classes. Workstation clients that use the Compaq NonStop™ Remote Server Call/MP (RSC/MP), for example, communicate with Pathway servers indirectly by means of Pathsend requesters created by RSC on behalf of the clients. Note.
LINKMON Processes Managing a Pathway/XM Environment Table 7-2 lists the effects of PXMCFG commands on LINKMON processes. Table 7-3 lists the effects of PXMCOM commands on LINKMON processes. Table 7-2.
Managing a Pathway/XM Environment LINKMON Processes For all systems that have the NonStopTM TS/MP product installed, a LINKMON process is included by default in the system image for each CPU. A LINKMON process starts in each CPU as the CPU is loaded. Process Names LINKMON process names appear in PXMCOM displays in the form L\system.$ZLnn, where nn is the number of the CPU on which the LINKMON process resides.
Managing a Pathway/XM Environment Configuration Tasks Extended Memory LINKMON extended memory is supported by a disk swap file named $SYSTEM.ZLINKMON.ZZLMnn, where nn is the CPU number of the LINKMON process. For example, the LINKMON process $ZL01 in CPU 1 uses the swap file $SYSTEM.ZLINKMON.ZZLM01. These swap files, created by the LINKMON processes, are owned by the super user and secured with four dashes (“----”) so that they can be accessed only by the super user.
Managing a Pathway/XM Environment Configuration Tasks Specifying Security For Pathsend processes, there are two levels of security to consider: network-level security and server-class security. Network-Level Security For Pathsend processes to access server processes, the following network conditions must be met: • • • The LINKMON process must be able to open the well-known named PATHMON process (to make link requests).
Monitoring LINKMON Processes Managing a Pathway/XM Environment For example, the following commands set the SERVER OWNER attribute to the user ID of the super user on the system 222 or \ABC, respectively: SET SERVER OWNER 222.255,255 SET SERVER OWNER \ABC.SUPER.SUPER If the user ID’s system is the same as the system in which the well-known named PATHMON process is running, you need not specify the system number or name.
Managing a Pathway/XM Environment Monitoring LINKMON Processes In a Pathway/XM environment, the well-known named PATHMON process handles all requests from LINKMON processes. Therefore, there should never be more than one LINKMON process with links to server classes in a Pathway/XM environment.
Managing a Pathway/XM Environment Recovering from PATHMON Process Failures STATS SERVER Command LINKMON processes automatically gather statistics for servers. They continually collect statistics about each server class with which they have links, unless the server class stops for any reason—in which case, the statistics are lost. To display these statistics, use the STATS SERVER command.
Shutting Down a Pathway/XM Environment Managing a Pathway/XM Environment Shutting Down a Pathway/XM Environment You can shut down your Pathway/XM environment by stopping all Pathway/XM objects collectively with the STOP PATHWAY command. You can choose from the following three options: ORDERLY, ABORT, and IMMEDIATE. Each option provides a different level of shutdown, as described in Table 7-4 and in the subsections that follow.
Shutting Down a Pathway/XM Environment Managing a Pathway/XM Environment Table 7-4. Effects of STOP PATHWAY Options (page 2 of 2) ORDERLY ABORT IMMEDIATE PB processes Closed Closed Stopped Outstanding work All outstanding work (I/O and dialog activity) is completed For TCPs and server classes, outstanding work (I/O and dialog activity) is completed. For transactions involving an aborted TERM, unknown.4 Unknown New work Not allowed Not allowed Not allowed 1.
Managing a Pathway/XM Environment Specifying the ORDERLY Option Specifying the ORDERLY Option The ORDERLY option enables work in progress to complete before shutting down. The following command specifies an orderly shutdown: >> STOP PATHWAY, MODE ORDERLY The ORDERLY option requires the most time to complete the shutdown operation, because all transactions in progress are allowed to complete before objects (TCPs, TERM objects, SERVER objects, and PATHMON process) involved in the transaction are stopped.
Managing a Pathway/XM Environment Escalating the Shutdown Operation The IMMEDIATE option is the quickest way to shut down a Pathway/XM environment, but you must consider the following consequences before specifying this option: • • • If completed successfully, the IMMEDIATE option stops processes immediately, regardless of the presence of pending requests and incomplete operations. Unlinked server processes are not able to perform any epilog processing.
Managing a Pathway/XM Environment • • If Shutdown Cannot Complete The time shutdown began Status of all entities defined in the Pathway/XM environment If Shutdown Cannot Complete If PXMCOM encounters an error while shutting down, it terminates the shutdown operation. PXMCOM returns the reason for the failure. In some cases, you may need to examine the log file to determine why shutdown did not complete, correct the problem, and reissue the STOP PATHWAY command.
Managing a Pathway/XM Environment Information to Include When Reporting Problems Information to Include When Reporting Problems When requesting help from your Compaq representative in resolving a problem with your Pathway/XM environment, you can greatly enhance the representative’s ability to help you by providing certain information about your environment. Pathway/XM Environment The following files and information apply to the Pathway/XM environment as a whole.
Managing a Pathway/XM Environment PXMCFG- or PXMCOM-Specific Problems VERBOSE ON command to collect information about the PATHCOM commands that were issued on behalf of PXMCOM. If you are able to reproduce the problem, give the Compaq representative a simple test case illustrating the problem along with a description of how to reproduce it.
Managing a Pathway/XM Environment Terminal-Specific Problems PATHMON Configuration and TCP Object Information Make the SuperCTL file available to your Compaq representative. Also, use PXMCOM commands to display information about the TCP at the time of the problem, as follows: >PXMCOM >>OPEN superctl-file >>INFO TCP * >>EXIT where superctl-file is the name of your SuperCTL file.
Managing a Pathway/XM Environment • • • SCUP-Specific Problems All copy libraries referenced in the source file or files. If applicable, a compiler listing showing the problem. Error messages written to the terminal but not included in the compiler listing. SCUP-Specific Problems If you detect a problem with the SCREEN COBOL Utility Program (SCUP), collect the relevant object code (POBJ) files for review.
8 Managing Clients and Requesters This section describes operations you need to perform to manage and maintain requester-related objects in a Compaq NonStop™ Pathway/XM environment. Most of the information in this section pertains to terminal requesters (SCREEN COBOL requesters, which run as threads within TCPs). Only limited management is available for Pathsend requesters. You can monitor information about them, and some global management objects (such as PATHMON processes) affect their operation.
Managing Clients and Requesters Starting ROUTER Objects To start each TCP, the associated PATHMON process creates the TCP process by running the program file indicated by the PROGRAM attribute of the TCP object, as recorded in the SuperCTL file. This attribute specifies the name of the file that contains the TCP’s object code. The PATHMON process then passes the TCP definition to the TCP process. The TCP uses the information in the TCP definition to initialize itself and start its backup process.
Managing Clients and Requesters Starting PROGRAM Objects The next command starts all TERM objects configured in the SuperCTL file: >> START TERM * After reading the TERM definition from the SuperCTL file, PXMCOM passes the TERM definition to the TCP process assigned to it by Pathway/XM. When the TCP receives this information, it: • • • • Checks the specified library file for the program indicated by the INITIAL attribute.
Managing Clients and Requesters Stopping TCPs You can run a PROGRAM object with or without the NOWAIT option. The NOWAIT option enables a maximum of 4,095 PROGRAM objects to run at the same time. If you do not specify NOWAIT, the maximum number of PROGRAM objects that can run at the same time drops to approximately 100. The NOWAIT option causes the PROGRAM object to execute concurrently with PXMCOM, so that the PXMCOM prompt returns immediately to your screen.
Managing Clients and Requesters Stopping ROUTER Objects Stopping ROUTER Objects To stop a ROUTER object, you use the STOP ROUTER command. This command stops the socket listener process; TERM objects that still have the listener process open are closed and then stopped with an error condition.
Managing Clients and Requesters Enabling and Disabling TCP Dumping and Statistics Collection Enabling and Disabling TCP Dumping and Statistics Collection You can use the CONTROL TCP command to enable or disable error dumping or statistics collection for selected TCPs in a running Pathway/XM environment.
Managing Clients and Requesters Displaying Information About Client and Requester Objects Displaying Information About Client and Requester Objects The SuperCTL file and the individual PATHCTL files associated with the PATHMON processes maintain information about object configurations, object status, and operation statistics.
Managing Clients and Requesters Displaying Status Information The INFO TERM Command The INFO TERM command displays the configured attribute values for a single TERM object, multiple TERM objects, or all TERM objects in the Pathway/XM environment. It can display information about both configured and temporary TERM objects.
Managing Clients and Requesters Displaying Status Information The STATUS TCP Command The STATUS TCP command displays status for a single TCP, multiple TCPs, or all TCPs defined in a PATHMON environment. The following example displays status for all TCPs in the Pathway/XM environment: >> STATUS TCP * You can also include state information (running, stopped, or suspended) in your command. The STATE option is very useful for problem detection and management.
Managing Clients and Requesters Displaying Statistics Displaying Statistics You can display statistics for ROUTER, TCP, and TERM objects by using the STATS command. Statistics for TCP and TERM objects are available for display only if you use one of the following commands to direct the system to collect them: • • SET TCP STATS ON CONTROL TCP STATS ON If you have used one of these commands, you can display requester statistics by using the STATS TCP and STATS TERM commands.
Managing Clients and Requesters Displaying Statistics Once you enter the CONTROL TCP STATS OFF parameter, all statistical counters are reset to 0. The STATS TCP Command The STATS TCP command displays statistics about TCP operations and data-space allocation for a single TCP, multiple TCPs, or all TCPs in a Pathway/XM environment. (This command does not display information about external TCPs that might have links to local servers.
Managing Clients and Requesters Sending Messages to Terminal Users If you include the FREQTABLE option, the STATS TERM command generates a frequency distribution table that contains statistics for the specified TERM object (or objects): >> STATS TERM TFRONT1, FREQTABLE For the syntax of the STATS TERM command, refer to STATS TERM on page 11-71. Sending Messages to Terminal Users You can send messages to application terminal users using the TELL TERM command.
Managing Clients and Requesters Managing Exception Conditions For the syntax of the TELL TERM command, refer to TELL TERM on page 11-104. For the syntax of the INFO TELL command, refer to INFO TELL on page 11-36. For the syntax of the DELETE TELL command, refer to DELETE TELL on page 11-22. Managing Exception Conditions Sometimes you need to change parameter values in your Pathway/XM environment because an exception or error condition has occurred for an object, such as a TERM object or a TCP.
Managing Clients and Requesters Managing Exception Conditions Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 8- 14
9 Managing Servers This section describes operations you need to perform to manage and maintain serverrelated objects in a Compaq NonStop™ Pathway/XM environment.
Managing Servers Distributed Server Classes In the Pathway/XM environment, you manage SERVER objects by server class only; Pathway/XM manages the individual server processes automatically on your behalf. Note. To start a server process that has been frozen (with the FREEZE command) and then stopped, you must first issue the THAW command. For more information, see Freezing and Thawing Server Classes on page 9-4.
Managing Servers Direct and Replicated Server Classes The LCS process starts new server processes in parallel with the servicing of the transaction queue by existing server processes. As a result, the overhead associated with starting a new process is outside the path of the transaction.
Managing Servers Freezing and Thawing Server Classes queued for the time period specified by the CREATEDELAY attribute for the server class. A link manager always tries to satisfy a send request with a static link if one is available. If a dynamic server process sits idle for the time limit defined by the DELETEDELAY attribute for the server class, the link manager returns the link to the PATHMON process.
Managing Servers Reconfiguring Distributed Server Classes Online A distributed server class can be frozen automatically. This occurs if the distributed server class is suspended for more than the maximum time specified in the SUSPEND SERVER command. To allow LINKMON processes and TCPs to resume communication with a server class, use the THAW command. For example, to thaw the SERVER named SALES, enter: >> THAW SERVER SALES The THAW command works only for server classes that are frozen.
Displaying Information About Servers Managing Servers 4.
Managing Servers Displaying Configuration Information for Servers Displaying Configuration Information for Servers The INFO SERVER command displays configuration information about a single server class, multiple server classes, or all server classes in the Pathway/XM environment. The following example displays configuration information about a single server class named TRECV: >> INFO SERVER TRECV For the syntax of the INFO SERVER command, refer to INFO SERVER on page 11-33.
Managing Servers Displaying Statistics for Servers The SET TCP STATS Statement The SET TCP STATS ON statement, a PXMCFG statement used when you configure a TCP template, tells all TCPs associated with the specified TCP template to gather statistics until you specify a CONTROL TCP STATS OFF command. The CONTROL TCP STATS Command The CONTROL TCP STATS command enables you to gather statistics only when you need them. You specify this command after your Pathway/XM environment is running.
Managing Servers A System Management Scenario For the syntax of the STATS SERVER command, refer to STATS SERVER on page 11-67. Note. LINKMON processes do not report response-time information or frequency-distribution information. Only TCPs collect this data. A System Management Scenario The following scenario illustrates how to use the information provided by the STATUS SERVER command to detect problems within your server environment and to determine how to rectify these problems.
Managing Servers Stopping Server Classes Stopping Server Classes Before you can stop a server class with the STOP SERVER command, you must disable all communication from LINKMON processes and TCPs to the server by using the FREEZE SERVER command. For example, the following command freezes all server processes in the server class CLASS-1: >> FREEZE SERVER CLASS-1 After the server class is frozen, you can stop the server process by stopping the server class to which it belongs.
Managing Servers Queue-Management Algorithm Used by the LCS Processes To restart a stopped server process, you must first thaw the server process, then issue the START SERVER command, as shown in the following example: >> THAW SERVER * >> START SERVER * For the syntax of the commands used in stopping a server class, refer to the following: FREEZE SERVER on page 11-24 STOP SERVER on page 11-96 THAW SERVER on page 11-106 START SERVER on page 11-59 Queue-Management Algorithm Used by the LCS Processes Each
Managing Servers Queue-Management Algorithm Used by the LCS Processes Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 9- 12
10 PXMCFG Statements and PXMCHK Utility This section describes the Compaq NonStop™ Pathway/XM configuration utility (PXMCFG) statements that define the Pathway/XM environment and Pathway/XM object configurations. It also gives the syntax of the TACL RUN command to start the PXMCFG process. For more information about using the PXMCFG utility, refer to Using the PXMCFG Utility on page 4-4.
PXMCFG Statements and PXMCHK Utility Starting PXMCFG Starting PXMCFG PXMCFG is the batch process that processes configuration statements and generates the Pathway/XM environment configuration used by the PXMCOM process. The name of the PXMCFG object file is $volume.subvolume.PXMCFG. Start a PXMCFG process by entering the PXMCFG RUN command through the TACL command interpreter and specifying a SuperCTL configuration file name. PXMCFG [ / run-option [ , run-option ]...
PXMCFG Statements and PXMCHK Utility Starting PXMCFG CPU number specifies the processor in which PXMCFG runs. Possible values are any CPU on your system, from 0 through 15. If you omit this parameter, the default is the processor used by the TACL command interpreter. NAME $process-name specifies the name of the PXMCFG process. $process-name begins with a $ (dollar sign), followed by one to five alphanumeric characters; maximum of six characters including the $.
PXMCFG Statements and PXMCHK Utility Starting PXMCFG Configuration Summary Format At the end of a successful completion of PXMCFG, it lists a summary of the configuration. The summary includes both the objects you have configured (for example, SERVER and NODE objects) and the objects PXMCFG has automatically calculated (PATHMON processes and TCP processes).
PXMCFG Statements and PXMCHK Utility Starting PXMCFG The overall summary includes the following fields: Total Systems The total number of physical (Expand) nodes on which resources are defined in the configuration. Total NODE Objects The total number of NODE objects defined in the configuration. Total PATHMON Objects The total number of PATHMON processes that will be included in this Pathway/XM environment.
PXMCFG Statements and PXMCHK Utility Starting PXMCHK Information about each TCP process under this PATHMON process, as follows: The internally assigned process name Information about the associated TCP template Names of the associated PROGRAM object or TERM objects • • For each server NODE object, the following information is included: ° The name of the NODE object ° The CPU resource assignments for the NODE object ° Names of the associated server classes (SERVER objects) For each PLAN object, the fol
PXMCFG Statements and PXMCHK Utility ADD NODE ADD NODE This statement adds CPU resources to the Pathway/XM environment by entering the NODE object name into the SuperCTL configuration file. The named NODE object is used as a reference when defining TCP and SERVER objects. Use this statement after defining a NODE object with the SET NODE statement. ADD NODE node-name [ , node-attribute ] ... node-name specifies the name of a logical processing node in a network of machines.
PXMCFG Statements and PXMCHK Utility ADD PROGRAM ADD PROGRAM This statement enters the name and the description of a PROGRAM object into the SuperCTL configuration file. Use this statement after defining a PROGRAM object with the SET PROGRAM statement. ADD PROGRAM program-name [ , program-attribute ]... program-name specifies the PROGRAM object name.
PXMCFG Statements and PXMCHK Utility ADD ROUTER ADD ROUTER This statement adds support for Pathway/iTS web clients by entering the name and description of a ROUTER object into the SuperCTL configuration file. Use this statement after defining a ROUTER object with the SET ROUTER statement. ADD ROUTER router-name [ , node-attribute ] ... router-name specifies the ROUTER object name.
PXMCFG Statements and PXMCHK Utility ADD SERVER ADD SERVER This statement enters the name and description of a server class into the SuperCTL configuration file. Use this statement after defining a server class with the SET SERVER statement. ADD SERVER server-class [ , server-attribute ]... server-class specifies the name of a server class.
PXMCFG Statements and PXMCHK Utility ADD SERVICE ADD SERVICE This statement enters the name and description of a SERVICE object into the SuperCTL configuration file. Use this statement after defining a SERVICE object with the SET SERVICE statement. ADD SERVICE server-group-name [ , service-attribute ] ... server-group-name specifies the name of the SERVICE object, which is also used as a group name for the set of SERVER objects to be imported or exported.
PXMCFG Statements and PXMCHK Utility ADD TCP ADD TCP This statement establishes the name and description of a TCP template. Each defined and added TCP template is used by PXMCFG as a template from which to generate the TCP processes that manage TERM and PROGRAM objects. TCP processes generated by PXMCFG are entered into the SuperCTL configuration file. Use this statement after defining a TCP template with the SET TCP statement. ADD TCP tcp-template [ , tcp-attribute ]...
PXMCFG Statements and PXMCHK Utility ADD TERM ADD TERM This statement enters the name and description of a TERM object into the SuperCTL configuration file. Use this statement after defining a TERM object with the SET TERM statement. This statement can be issued only for configured TERM objects. ADD TERM term-name [ , term-attribute ]... term-name specifies the name of a TERM object.
PXMCFG Statements and PXMCHK Utility COMMENT COMMENT This statement allows comment text to be included in PXMCFG source files. COMMENT text text consists of comment text for documentation purposes. This text is ignored by PXMCFG. text can be from 1 through 243 alphanumeric characters. There must be at least one space between the statement name and the text. Consideration This statement is useful for documenting source files.
PXMCFG Statements and PXMCHK Utility ENABLE ROUTER ENABLE ROUTER This statement enables support for ROUTER objects in systems running operating system version D46.0 or higher. Use this statement before defining a ROUTER object with the SET ROUTER statement. ENABLE ROUTER Although the D38 version of Pathway/XM supports both the D38 (and higher) and D46 (and higher) versions of the operating system, router processes are only supported in D46 and higher versions.
PXMCFG Statements and PXMCHK Utility EXPORT EXPORT This statement exports node-independent SERVER object definitions to a SuperCTL file. The file can later be imported into another Pathway/XM configuration; node relationships are automatically resolved when the file is imported. Use this statement before using any SERVER object statements. EXPORT { ON | OFF } ON directs PXMCFG to generate an export SuperCTL file that contains only SERVER object definitions.
PXMCFG Statements and PXMCHK Utility INCLUDE INCLUDE This statement directs PXMCFG to process the specified nested statement file. PXMCFG processes all nested statements in the named file before returning to the original statement file to continue processing. INCLUDE file-name file-name specifies the name of a source file containing PXMCFG statements. Consideration This statement is useful for simplifying a very large configuration source file.
PXMCFG Statements and PXMCHK Utility INVENTORY INVENTORY This statement directs PXMCFG to take an inventory of the currently executing SuperCTL file and then build an automated migration plan. Use this statement before executing the PXMCOM START PLAN statement. INVENTORY { active-superctl-file-name } active-superctl-file-name specifies the name of the SuperCTL file that is currently controlling the Pathway/XM environment.
RESET NODE PXMCFG Statements and PXMCHK Utility RESET NODE This statement changes the values for the NODE object attributes from the values that you defined with the SET NODE statement to the Pathway/XM standard defaults. This statement does not change the attributes of a NODE object already added to the SuperCTL configuration file. RESET NODE [ node-keyword [ , node-keyword ]...
RESET PROGRAM PXMCFG Statements and PXMCHK Utility RESET PROGRAM This statement changes the values for the PROGRAM object attributes from the values that you defined with the SET PROGRAM statement to the defaults. This statement does not change the attributes of a PROGRAM object already added to the SuperCTL configuration file. RESET PROGRAM [ program-keyword [ , program-keyword ]...
RESET ROUTER PXMCFG Statements and PXMCHK Utility RESET ROUTER This statement changes the values for the ROUTER object attributes from the values that you defined with the SET ROUTER statement to the Pathway/XM standard defaults. This statement does not change the attributes of a ROUTER object already added to the SuperCTL configuration file. RESET ROUTER [ router-keyword [ , router-keyword ]...
RESET SERVER PXMCFG Statements and PXMCHK Utility RESET SERVER This statement changes the values for server class attributes from the ones you defined with the SET SERVER statement to the default values. This statement does not change the attributes of a server class already added to the SuperCTL configuration file. RESET SERVER [ server-keyword [ , server-keyword ]...
PXMCFG Statements and PXMCHK Utility RESET SERVICE RESET SERVICE This statement changes the values for the SERVICE object attributes from the values that you defined with the SET SERVICE statement to the Pathway/XM standard defaults. This statement does not change the attributes of a SERVICE object already added to the SuperCTL configuration file. RESET SERVICE [ service-keyword [ , service-keyword ]...
RESET TCP PXMCFG Statements and PXMCHK Utility RESET TCP This statement changes the values for the TCP attributes from the values you defined with the SET TCP statement to the default values. This statement does not change the attributes of a TCP already added to the SuperCTL configuration file. RESET TCP [ tcp-keyword [ , tcp-keyword ]...
RESET TERM PXMCFG Statements and PXMCHK Utility RESET TERM This statement changes the values for TERM object attributes from the ones you defined with the SET TERM statement to the defaults. This statement does not change the attributes of a TERM object already added to the SuperCTL configuration file. RESET TERM [ term-keyword [ , term-keyword ]...
PXMCFG Statements and PXMCHK Utility SET NODE SET NODE This statement defines a logical set of resources to be used by either requester (client) processes or server processes. Attributes set by this statement for a given NODE object are used as default settings for all SERVER and TCP processes associated with that NODE object. Use this statement before using the ADD NODE statement. SET NODE node-attribute [ , node-attribute ] ... node-attribute is: CPUS (cpu[:weight] [ , cpu[:weight] ]...
SET NODE PXMCFG Statements and PXMCHK Utility DEFAULT $volume.subvolume specifies the Guardian name of the disk volume and subvolume to be used as a file name expansion default by all SERVER or TERM objects associated with this NODE object. If you set this attribute, both the volume and the subvolume must be specified. If you omit this attribute, names default to the volume and the subvolume on which the PXMCFG process is running.
SET NODE PXMCFG Statements and PXMCHK Utility Process Type Default Priority Value Link Control Service (LCS) NODE object priority minus 3 TCP NODE object priority minus 5 Server Process NODE object priority minus 10 You can override the execution priority of processes by using the SET SERVER PRI and SET TCP PRI statements. If you omit this attribute, the base priority value of the logical node is the priority at which the PXMCFG process ran when it created the SuperCTL file.
PXMCFG Statements and PXMCHK Utility SET NODE Example The following statements define a NODE object that acts in the SERVER role, uses resources on the physical system named \CHICAGO, and distributes server processes evenly across four CPUs (25 percent of the processes in each named CPU): SET NODE CPUS (2:25, 3:25, 4:25, 5:25) SET NODE ROLE SERVER SET NODE SYSTEM \CHICAGO Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 10 -29
PXMCFG Statements and PXMCHK Utility SET PATHMON SET PATHMON This statement establishes the values for the PATHMON process attributes. All PATHMON processes generated in this Pathway/XM environment use the values set by this statement; in other words, all PATHMON processes in a given Pathway/XM environment are exactly alike, with the exception of the process name. SET PATHMON { NODES node-name } { NODES ( node-name [ , node-name ]...
PXMCFG Statements and PXMCHK Utility SET PATHMON DUMP {ON | OFF} specifies whether the PATHMON process writes its data stack information and the contents of its configuration file to a dump file if the PATHMON process encounters an internal error. If you omit this attribute, the default is OFF. ON directs the PATHMON process to write the information in its data stack and the contents of its configuration file to a dump file and then to set this option to OFF.
PXMCFG Statements and PXMCHK Utility SET PATHWAY SET PATHWAY This statement establishes attribute values for the PATHWAY object and defines values for the PATHMON processes that are created in this Pathway/XM environment. The attribute values can be changed only at configuration time. SET PATHWAY pw-attribute [ , pw-attribute ]...
PXMCFG Statements and PXMCHK Utility SET PATHWAY and LINKMON processes within a Pathway/XM environment are allowed to hold links concurrently to a single server process. number must be a value from 0 through 800. If you omit this attribute, the default value is 0; any attempt by a LINKMON process to access a server process within the Pathway/XM environment fails. If your environment uses Pathsend processes, you must set this attribute to a value greater than 0.
SET PATHWAY PXMCFG Statements and PXMCHK Utility MAXTELLS number specifies the maximum number of tell messages that can exist concurrently per PATHMON process within a Pathway/XM environment. number must be a value from 0 through 4095. If you omit this attribute, the default is 32. If your environment does not support Pathway/iTS, it is recommended you specify 0 for the value.
PXMCFG Statements and PXMCHK Utility SET PATHWAY SECURITY security-attribute specifies the users who can issue PXMCOM commands that directly alter the state of the Pathway/XM objects. Before you issue the PXMCOM START PATHWAY command, the owner ID is the process-accessor ID of the PXMCOM process and the security attribute is “O”. This security setting prevents alteration of the Pathway/XM configuration attributes. The security attributes are the same as the Guardian security attributes.
PXMCFG Statements and PXMCHK Utility SET PROGRAM SET PROGRAM This statement establishes the values for the PROGRAM object attributes. Use this statement before using the ADD PROGRAM statement. SET PROGRAM program-attribute [ , program-attribute ]... program-attribute is: TCP template-name TYPE terminal-type ( type-attribute [ , type-attribute ]...
SET PROGRAM PXMCFG Statements and PXMCHK Utility terminal-type specifies the type of device on which the program is to run.
SET PROGRAM PXMCFG Statements and PXMCHK Utility TCP stops accepting terminal input and terminates the ACCEPT statement without changes to the working storage section. Pressing the Break key has no effect on the TCP when the ACCEPT statement is coded without an ESCAPE ON ABORT clause. If the TCP is not executing either of the preceding statements, pressing the Break key has no effect on the TCP process. OFF directs the TCP to ignore the Break key function.
PXMCFG Statements and PXMCHK Utility SET PROGRAM ECHO { ON | OFF | CURRENT } overrides the terminal echo mode (that is, the mode configured for a terminal at system generation time) so that character input appears correctly on the terminal. The ECHO attribute supports terminals running in conversational or intelligent mode. If you omit this attribute, the default is ON. ON Directs input to appear on the terminal screen.
PXMCFG Statements and PXMCHK Utility SET PROGRAM TRAILINGBLANKS { ON | OFF } specifies whether the TCP suppresses the display of trailing ASCII blank characters in output lines sent to terminals by the SCREEN COBOL DISPLAY and SEND MESSAGE verbs. If you omit this attribute, the default is ON. ON Directs the TCP not to suppress trailing ASCII blanks. OFF Directs the TCP to suppress trailing ASCII blanks.
PXMCFG Statements and PXMCHK Utility SET PROGRAM If you omit system-number or physical-node, the name is resolved with the SYSTEM value set for the associated NODE object. If no value is specified for the NODE object SYSTEM attribute, the physical node name defaults to the physical system on which the PXMCFG utility ran during the configuration process. The group-name and user-name values default to the user ID of the user who started PXMCOM.
PXMCFG Statements and PXMCHK Utility SET PROGRAM SECURITY security-attribute specifies the PXMCOM users who can issue a PXMCOM RUN PROGRAM command for this PROGRAM object. This attribute controls only who can execute a RUN PROGRAM command; it does not control who can execute a CALL statement from another SCREEN COBOL program unit. The security attributes are the same as the operating system security attributes.
PXMCFG Statements and PXMCHK Utility SET PROGRAM Examples The following statements define a subset of the PROGRAM object attributes: SET SET SET SET PROGRAM PROGRAM PROGRAM PROGRAM TCP TCP-1 TYPE 4 (INITIAL MAINMENU) OWNER 8,9 SECURITY "G" The following statement defines multiple terminal options: SET PROGRAM TYPE 5 (INITIAL LOGON, BREAK ON, ECHO ON) Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 10 -43
PXMCFG Statements and PXMCHK Utility SET ROUTER SET ROUTER This statement defines values for the router process which listens for web-client connection requests and distributes connections to the TCP processes and terminals. Use this statement before using the ADD ROUTER statement. SET ROUTER router-attribute [ , router-attribute ] ...
PXMCFG Statements and PXMCHK Utility SET ROUTER CONNECTIONS number specifies the number of TERM objects to be used to process socket connections. Each TERM object can process one concurrent socket connection. The ROUTER object may have a maximum of five connection requests waiting for a TERM object to become available. When all TERM objects are busy, the sixth connection request waiting is rejected. number is from 1 through 32767; the default is 1.
SET ROUTER PXMCFG Statements and PXMCHK Utility If you omit this attribute, the default is OFF. ON starts the Inspect process when the SCREEN COBOL program begins and breaks execution of the program before the first program instruction executes. FILE file-name specifies the name of the Inspect command terminal. Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object. If you omit file-name, the default is the home terminal of the TCP.
PXMCFG Statements and PXMCHK Utility SET SERVER SET SERVER This statement defines values for server class attributes. Use this statement before using the ADD SERVER statement. SET SERVER server-attribute [ , server-attribute ]... server-attribute is: ( ASSIGN logical-unit , assign-spec ) AUTORESTART number CMON { ON | OFF } CREATEDELAY number { HRS | MINS | SECS } DEBUG { ON | OFF } ( DEFINE define-name , define-attribute-spec [, define-attribute-spec ] ...
PXMCFG Statements and PXMCHK Utility SET SERVER create-spec is: { { { { { { { { { EXT [ ( ] pri-extent-size [ ) ] } EXT ( [ pri-extent-size ] , sec-extent-size ) } EXCLUSIVE } SHARED } PROTECTED } I/O } INPUT } OUTPUT } CODE file-code } server-attribute Specifies one or more attributes of the SERVER object being defined. The PROGRAM attribute is the only required attribute. ASSIGN logical-unit , assign-spec assigns a logical file name to a physical Guardian file and specifies attributes of the file.
SET SERVER PXMCFG Statements and PXMCHK Utility assign-spec specifies values for the physical file. file-name specifies the name of the Guardian file, which represents the physical file assigned to the server program; this name could be a DEFINE name. If you omit this option, no value is passed for this field of the ASSIGN message. Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object.
PXMCFG Statements and PXMCHK Utility SET SERVER CMON { ON | OFF } specifies whether the LCS process allows a user-supplied $CMON process, if one exists, to approve or modify the values of server-process startup parameters (such as CPU numbers and process priorities). This attribute is valid only for distributed server classes. If you omit this attribute, the default is OFF.
PXMCFG Statements and PXMCHK Utility SET SERVER If you omit this attribute, the default is OFF. ON Directs the server processes to enter debug mode. If the PATHMON process was started with ON or the server program was compiled or bound with the Inspect process defined, the servers enter Inspect mode for debugging. OFF Directs the server processes not to enter debug mode. DEFINE define-name , define-attribute-spec assigns a DEFINE definition as part of a server class definition.
SET SERVER PXMCFG Statements and PXMCHK Utility group. To do this, specify each group in a separate SET SERVER GROUP statement. This attribute is optional; if you omit this attribute, there is no default. GUARDIAN-LIB file-name specifies the name of the user library object file that contains additional server code space and procedures that can be shared among servers.
PXMCFG Statements and PXMCHK Utility SET SERVER HOMETERM device-name specifies the name of the home terminal for servers in the server class. If you omit this attribute, the default is the home terminal of the PATHMON process. Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object. IN file-name specifies the name of the input file passed to the server process in the startup message; this could be a DEFINE name.
PXMCFG Statements and PXMCHK Utility SET SERVER manager does not check how many links a server has with other TCP processes or LINKMON processes. If the value for this attribute is too large, it can cause the requests to the server process to be queued at the server for an unacceptable length of time. For example, if MAXLINKS is equal to 20, there could be 20 concurrent requests outstanding to a server. If the transaction service time is 1 second, a response time of more than 20 seconds can occur.
PXMCFG Statements and PXMCHK Utility SET SERVER NONSTOP { 0 | 1 } specifies whether server processes run with backup processes. 0 The server process does not run with a backup process. 1 The server process runs with a backup process. This value is valid for direct and replicated server classes only. If you omit this attribute, the default is 1. In a single processor environment, using the default generates an error. You can either ignore the error or set NONSTOP to 0.
SET SERVER PXMCFG Statements and PXMCHK Utility OWNER ownerid specifies the user ID that controls access from a Pathsend process to a server class. (The TCP processes ignore this server attribute.) The user ID must be known to the system in which PXMCOM is running. Use this attribute in conjunction with the SECURITY attribute. The value of owner-id is one of the following: [ \system-number. ] group-number, user-number [ \physical-node. ] group-name.
PXMCFG Statements and PXMCHK Utility SET SERVER PROCESS $process-name assigns server names, which allows Pathway/XM to use direct server processes as associative servers. The PATHMON process gives the process names to the servers when it creates them. It assigns the names in the order that you define them in the server class description. This attribute is required; you must define the exact same number of process names as is defined for MAXSERVERS.
PXMCFG Statements and PXMCHK Utility SET SERVER “N” Any local or remote user “C” Any member of owner's community (local or remote user having same group ID as owner) “U” Any member of owner's user class (local or remote user having same group ID and user ID as owner) Quotation marks are required. If you omit this attribute, the default is “N”. STARTUP string specifies the character string that is sent to a Guardian server process in the startup message. Leading blanks are ignored.
PXMCFG Statements and PXMCHK Utility SET SERVER performs checkpoint operations, but does not automatically retry I/O errors; this is done by the operating system. TYPE { DISTRIBUTED | REPLICATED | DIRECT } specifies the way the server processes in the server class are managed.
PXMCFG Statements and PXMCHK Utility SET SERVER Examples The following statements define a subset of the server class attributes: RESET SERVER SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER ASSIGN DDL, $DATA.DIC.
PXMCFG Statements and PXMCHK Utility SET SERVICE SET SERVICE This statement defines values for a set of pre-defined, node-independent SERVER objects that can be imported by third-party applications. Use this statement before using the ADD SERVICE statement. SET SERVICE service-attribute [ , service-attribute ]...
PXMCFG Statements and PXMCHK Utility SET SERVICE type identifies how the variable is used when SERVER objects are used. The following types are valid: FILE DISK DEVICE PROCESS VOLUME SUBVOL Any valid DISK, DEVICE, or PROCESS name. A disk file name. A Guardian device name. A Guardian process name. A disk volume name. A disk subvolume name. name specifies a name for the variable.
PXMCFG Statements and PXMCHK Utility SET TCP SET TCP This statement defines values for a TCP template from which PXMCFG configures TCP processes. Use this statement before using the ADD TCP statement. SET TCP tcp-attribute [ , tcp-attribute ]...
PXMCFG Statements and PXMCHK Utility SET TCP NODE node-name specifies the name of a previously defined and added NODE object that defines the resources to be used by TCP processes configured from this TCP template. The NODE object must have the ROLE attribute set to CLIENT. This attribute is required and must be specified before you specify the TCLPROG attribute. TCLPROG file-name specifies the name of the SCREEN COBOL object library file that a TCP uses to locate the screen programs for its terminals.
PXMCFG Statements and PXMCHK Utility SET TCP OFF directs a TCP configured from this TCP template to check its memory for a version of the called program unit. If the program is already in the TCP code area and the TCP checked the directory file after the latest REFRESH-CODE command, the TCP uses that version of the program and does not read the directory file. Note. This option does not ensure that the TCP uses the latest accessible version of the called program unit.
SET TCP PXMCFG Statements and PXMCHK Utility DEBUG { ON | OFF } specifies whether a TCP enters debug mode on startup. If you omit this attribute, the default is OFF. ON Directs the TCP to enter debug mode. If the PATHMON process is configured with INSPECT, the TCP enters the Inspect program instead of the DEBUG program. OFF Directs the TCP not to enter debug mode.
PXMCFG Statements and PXMCHK Utility SET TCP After starting a TCP, the operating system modifies the TCP object file to point to the user library file that you define with this attribute. To change the user library file name, you must stop the TCP and alter this attribute value. Stopping the TCP does not change the user library pointer in the TCP object file. All TCP processes running simultaneously and using the same object code must also use the same user library object file.
PXMCFG Statements and PXMCHK Utility SET TCP HOMETERM device-name specifies the name of the terminal that receives TCP debugging information. Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object. If you omit this attribute, the default is the value you specify for SET NODE HOMETERM. INSPECT {ON | OFF} specifies whether you can use the Inspect program to examine the SCREEN COBOL programs running on the terminals controlled by a TCP.
PXMCFG Statements and PXMCHK Utility SET TCP MAXINPUTMSGLEN number specifies the maximum length in bytes of any unsolicited message that a TCP accepts. This does not include the header length. number can be a value from 0 through 6000 bytes. If you omit this attribute, the default is 133 bytes. (Note that any bytes you specify in excess of the default are taken from the terminal pool area.) TCP processes reject messages received that exceed MAXINPUTMSGLEN.
PXMCFG Statements and PXMCHK Utility SET TCP If you omit this attribute, the default is 2000 bytes. A TCP uses this number and the value for the MAXTERMDATA attribute to allocate the size of the context areas (Slot 0 and Slot 1) for its terminals. For a TCP that runs the gateway requester program to support Pathway/iTS web clients, specify a value of 32000. MAXSERVERCLASSES number specifies the maximum number of server classes with which a TCP can communicate simultaneously.
PXMCFG Statements and PXMCHK Utility SET TCP MAXWEIGHTS number specifies the total of the SET TERM WEIGHT values allowed for a TCP. The PXMCFG process uses this value to calculate the number of TERM objects to assign to the TCP. For example, if you specify a value of 100 and SET TERM WEIGHT is 10, then the maximum number of TERM objects that can be assigned to the TCP is 10. number must be a value from 1 through 32768. If you omit this attribute, the default is 32768.
PXMCFG Statements and PXMCHK Utility SET TCP PRI priority specifies the execution priority at which a TCP runs. priority can be a value from 1 through 199. If you omit this attribute, the default is the priority set for the NODE object to which this TCP is associated. PROGRAM file-name specifies a TCP object file name (usually $SYSTEM.SYSTEM.PATHTCP2). Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object.
PXMCFG Statements and PXMCHK Utility SET TCP SWAP $volume specifies the Guardian name of the disk volume for the temporary file used for swapping the TCP extended data segment. Defaults for file name expansion are based on the value of the DEFAULT attribute of the associated NODE object. TERMBUF bytes specifies the maximum number of bytes that a TCP allocates from the TERMPOOL area for its terminal output buffers. (This allocation has no effect on terminal input operations.
PXMCFG Statements and PXMCHK Utility SET TCP greater than the SET TCP TERMBUF value; the TCP requires the additional 25 bytes for pool management. Note. The pool space value allocated for TERMPOOL is the value you configure rounded up to the next highest multiple of 4. For a TCP that runs the gateway requester program to support Pathway/iTS web clients, specify a value of 200000.
PXMCFG Statements and PXMCHK Utility SET TERM SET TERM This statement defines values for the configured TERM object attributes. Use this statement before using the ADD TERM statement. SET TERM term-attribute [ , term-attribute ]...
PXMCFG Statements and PXMCHK Utility SET TERM AUTORESTART number specifies the number of times that the PATHMON process attempts to restart the TERM object within a fixed 10-minute interval after an abnormal termination causes the TCP to place the TERM object in the SUSPEND-ABORT or a SUSPEND-RESUME state. This state does not result from a normal ABORT, STOP, or SUSPEND command. number can be a value from 0 through 32,767. If you omit this attribute, the default is 0.
SET TERM PXMCFG Statements and PXMCHK Utility DIAGNOSTIC { ON | OFF } specifies whether diagnostic screens are displayed to inform the terminal operator when an error condition or termination occurs. The SCREEN COBOL special register DIAGNOSTIC-ALLOWED is initialized to YES or NO according to the value of this attribute. Screen recovery is invoked following the display of a diagnostic screen. If you omit this attribute, the default is ON. ON Displays diagnostic screens.
PXMCFG Statements and PXMCHK Utility SET TERM ECHO { ON | OFF | CURRENT } overrides the terminal echo mode (that is, the mode configured for a terminal at system generation time) so that character input appears correctly on the terminal. The ECHO attribute supports terminals running in conversational or intelligent mode. If you omit this attribute, the default is ON. ON Directs input to appear on the terminal screen.
PXMCFG Statements and PXMCHK Utility SET TERM This attribute is optional; if you omit this attribute, there is no default and the terminal or device process acts as a dummy terminal. See Section 3 for a discussion of dummy terminals. GROUP group-name specifies the name of a set of TERM objects; all temporary and configured TERM objects defined with this group-name are members of the same set.
PXMCFG Statements and PXMCHK Utility SET TERM IOPROTOCOL { 0 | 1 } specifies the protocol the TCP follows when a SCREEN COBOL SEND MESSAGE statement completes with a timeout or an unsolicited message. If you omit this attribute, the default is 0. 0 Directs a TCP to issue a CANCEL procedure to cancel a SEND MESSAGE I/O. The I/O is cancelled because an unsolicited message arrives or a SEND MESSAGE TIMEOUT occurs. 1 Directs a TCP to use a CONTROL-26 protocol to cancel a SEND MESSAGE I/O.
PXMCFG Statements and PXMCHK Utility SET TERM IS-ATTACHED directs the copy of the screen image to a printer that is either physically attached to the terminal or on the same line controller as the terminal on which the program runs. IS-ATTACHED is one of the following: T16-6530 Directs copy to a printer attached directly to the terminal. T16-6520 Directs copy to a printer attached directly to the terminal. IBM-3270 Directs copy to the device that is attached to the same control unit as the terminal.
SET TERM PXMCFG Statements and PXMCHK Utility TYPE term-class specifies the type of device on which the TERM object runs. Specify term-class in the format term-type:term-subtype .
PXMCFG Statements and PXMCHK Utility SET TERM attribute is used. If the TERMINAL IS clause is not present and this attribute does not specify a term-subtype value, the TCP determines the device type from a call to the file system DEVICEINFO procedure.
PXMCFG Statements and PXMCHK Utility Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 10 -84 SET TERM
11 PXMCOM Commands This section describes the Compaq NonStop™ Pathway/XM Command Interpreter (PXMCOM) commands that manage the Pathway/XM environment and Pathway/XM objects, providing a single point of control for all Pathway systems being managed. The PXMCOM commands use the information in the SuperCTL configuration file generated by the PXMCFG utility. The commands in this section are described in alphabetical order.
PXMCOM Commands Table 11-1. PXMCOM Commands and Object Types (page 2 of 2) Commands Object Types X X X X X X X X X X X X X X Null TCP X TERM SERVER X TELL ROUTER PROGRAM PLAN PATWAY PATMON NODE RUN X START X STATS X STATUS* X STOP X X X SUSPEND X X X TELL X X THAW X TRACELOG X VERBOSE X VOLUME X * STATUS FREEZE and STATUS LINKMON are also valid. INFO GROUP is a valid command although GROUP is not a formal object type.
PXMCOM Commands Starting PXMCOM Starting PXMCOM PXMCOM is the process that provides the interactive management command interface to the Pathway/XM environment. The name of the PXMCOM object file is $volume.subvolume.PXMCOM. Start a PXMCOM process by entering the PXMCOM command through the TACL command interpreter. PXMCOM [ / run-option [ , run-option ]... / ] [ command [ ; command ]...
PXMCOM Commands Starting PXMCOM If you omit this parameter, output is directed to the current TACL output file; this is typically the home terminal. CPU number specifies the processor in which PXMCOM runs. Possible values are any CPU on your system, from 0 through 15. If you omit this parameter, the default is the processor used by the TACL command interpreter. NAME $process-name specifies the name of the PXMCOM process.
PXMCOM Commands Starting PXMCOM Example The following example starts a PXMCOM process named $COM1 in CPU4, sends output to the file COMMSG, and opens the SuperCTL file named SALESCFG (previously created by the PXMCFG statement): PXMCOM /OUT COMMSG, CPU 4, NAME $COM1/ OPEN SALESCFG Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 11- 5
PXMCOM Commands ABORT TERM ABORT TERM This command aborts a suspended or running TERM object or a defined or selected group of TERM objects. This command can be issued to configured and temporary TERM objects. ABORT TERM { term-name } { GROUP group-name } { * } term-name specifies the name of a TERM object. GROUP group-name specifies the name of a set of TERM objects, each configured as a member of the specified group. The ABORT TERM command is issued to each TERM associated with this group.
PXMCOM Commands ABORT TERM Considerations • • • When TERM objects are aborted with an ABORT TERM command, no replies from outstanding SEND operations are received. This differs from the STOP TERM command, which does not complete until replies are received from all outstanding SEND operations. If a TERM object is in TMF transaction mode when this command is executed, the transaction is backed out before the TERM aborts.
PXMCOM Commands COMMENT COMMENT This command allows comment text to be included in PXMCOM command files or interactively in log files. COMMENT text text consists of comment text for documentation purposes. This text is ignored by PXMCOM. text can be from 1 through 243 alphanumeric characters. There must be at least one space between the command name and the text. Consideration This command is useful for documenting log files during troubleshooting while using the TRACELOG command.
CONTROL NODE PXMCOM Commands CONTROL NODE This command changes CPU definitions for a NODE object while the Pathway/XM environment is running. The new CPU attribute definitions are used when new processes are started; the new values do not effect currently running requester or server processes. Processes currently running in CPUs no longer available to the NODE object are stopped at the end of their reservation period.
PXMCOM Commands CONTROL NODE Example The following command, in effect, removes CPU 5 from use by the NODE named SALES by changing the relative percentage of processes that can be executed in that CPU to zero, and changes the distribution of processes in CPUs 6 and 10: CONTROL NODE SALES, CPUS (5:0, 6:75, 10:25) Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 11 -10
PXMCOM Commands CONTROL PATHMON CONTROL PATHMON This command changes the DUMP attribute of the PATHMON process while it is running. CONTROL PATHMON DUMP { ON | OFF } DUMP { ON | OFF } specifies whether the PATHMON process writes the data stack information to a file if it encounters an internal error. ON directs the PATHMON process to write the information in its data stack and the contents of its configuration file to a dump file and then to set this option to OFF.
PXMCOM Commands CONTROL SERVER CONTROL SERVER This command changes specific SERVER attributes while server processes are running. After this command completes successfully, the server processes are restarted and run with the new attribute changes specified. Before you execute this command, a distributed server class must be in the SUSPENDED or the STOPPED state; direct or replicated server classes must be in the STOPPED state.
PXMCOM Commands CONTROL SERVER create-spec is: { { { { { { { { { EXT [ ( ] pri-extent-size [ ) ] } EXT ( [ pri-extent-size ] , sec-extent-size ) } EXCLUSIVE } SHARED } PROTECTED } I/O } INPUT } OUTPUT } CODE file-code } server-class specifies the name of a previously defined and added distributed SERVER object. GROUP group-name specifies the name of a set of SERVER objects, each configured as a member of the specified group.
CONTROL SERVER PXMCOM Commands name for the source code or for the run unit. If the server is a subprogram, this name is used in the CALL statement. logical-file-name specifies the name of the file in the server program. logical-filename is associated with a physical file. For example, in a COBOL program logical-file-name is the file description name in a SELECT clause. * replaces program-unit for the server with the file name specified in the PROGRAM attribute.
CONTROL SERVER PXMCOM Commands File-creation or Open Attribute Description CODE filecode Assigns a file code to logical-unit. file-code can be an integer 0 through 65535. If you omit filecode, the value is 0. REC recordsize Specifies the length of the records in logical-unit. record-size can be an integer from 1 through 4072. BLOCK blocksize Sets the size of the data blocks for logical-unit. block-size can be an integer from 1 through 4096.
PXMCOM Commands CONTROL SERVER Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object. IN file-name specifies the name of the IN file in the startup message; this could be a DEFINE name. Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object.
CONTROL SERVER PXMCOM Commands The number for MAXSERVERS minus the number for NUMSTATIC is the number of dynamic servers for the server class. Links to dynamic servers are granted to a link manager by the PATHMON process when a link request cannot be satisfied by a static server. Dynamic server processes are started by the PATHMON process only as the result of a link request; they are not started by the START SERVER command. The value of NUMSTATIC cannot exceed the value of MAXSERVERS.
PXMCOM Commands CONTROL SERVER Defaults for file name expansion are based on the values of the SYSTEM and DEFAULT attributes of the associated NODE object. STARTUP string specifies the character string that is sent to a Guardian server process in the startup message. Leading blanks are ignored. If you want embedded blanks to be read as part of the startup string, enclose string in quotation marks. If the string includes quotation marks, they must be doubled.
PXMCOM Commands CONTROL TCP CONTROL TCP This command changes specific TCP process attributes while the TCP is running. If the TCP process is not running when you issue this command, the PATHMON process returns an error. CONTROL TCP { term-name } { GROUP group-name } { * } tcp-attribute [ , tcp-attribute ]... tcp-attribute is: DUMP { ON | OFF } STATS { ON | OFF } term-name specifies the name of a TERM object. The CONTROL TCP command is issued to the TCP process that manages this TERM object.
CONTROL TCP PXMCOM Commands After creating 10 primary process and 10 backup process dump files, the TCP process stops performing memory dumps. This prevents writing over existing dump files that may indicate the original cause of a problem, and prevents filling a disk with dump files. OFF directs the TCP process not to write data stack information to a file when it encounters an internal or fatal error.
PXMCOM Commands CONTROL TERM CONTROL TERM This command changes the file name for a TERM object while the device is running and permanently records the change in the SuperCTL. If the device is not running when you issue this command, the PATHMON process returns an error. CONTROL TERM term-name, FILE file-name term-name specifies the name of a TERM object. file-name specifies the new file name for the TERM object.
PXMCOM Commands DELETE TELL DELETE TELL This command deletes a pending tell message. DELETE TELL number number specifies the number of the pending tell message. Consideration Tell message numbers are globally assigned; each tell message has a unique number within a Pathway/XM environment.
PXMCOM Commands ENV This command displays the current operational settings for the Pathway/XM environment.
PXMCOM Commands FREEZE SERVER FREEZE SERVER This command prohibits all link managers, such as LINKMON processes, TCP processes, and LCS processes, from sending requests to a server class. If a server process has incomplete requests (requests for which links have not yet been granted) or outstanding requests (such as an active dialog), the PATHMON process cannot freeze the server class until after these requests complete.
PXMCOM Commands FREEZE SERVER Considerations • • Unless ! is specified, the freeze does not take effect until all SCREEN COBOL STOP-MODE special registers have a value of zero and no server in the server class has incomplete or outstanding requests. In the interim, the server class is put into the FREEZE-PENDING state.
PXMCOM Commands INFO GROUP INFO GROUP This command displays the names of currently configured groups and their members.. Note. GROUP is not a configurable object; it is a pseudo-object used in this command for the purposes of obtaining important information. INFO GROUP { group-name } { * [ , { SERVERS | TERMS } ] } group-name specifies the name of a previously defined group. * displays the names and members of all groups in the SuperCTL configuration file.
PXMCOM Commands INFO NODE INFO NODE This command displays the current configuration of a NODE object. INFO NODE { node-name | * } node-name specifies the name of a previously defined and added NODE object. * displays the configuration information for all NODE objects in the SuperCTL configuration file. Considerations • • • You can execute this command whenever the SuperCTL file is open, even before the Pathway/XM environment is started.
PXMCOM Commands INFO PATHMON INFO PATHMON This command displays the current configuration of the PATHMON processes in your Pathway/XM environment, including the attributes you set by using the PXMCFG SET PATHMON statement. INFO PATHMON Consideration You can direct the output of this command to a file by using the OUT command before executing the INFO command.
PXMCOM Commands INFO PATHWAY INFO PATHWAY This command displays both the PATHMON-controlled object attribute values you defined by using the PXMCFG SET PATHWAY statement, and the values currently in effect. For object attributes not yet defined, this command displays the default value or a question mark character. INFO PATHWAY Consideration You can direct the output of this command to a file by using the OUT command before executing the INFO command.
PXMCOM Commands INFO PLAN INFO PLAN This command displays information about the SuperCTL configuration migration PLAN objects generated by the INVENTORY command. The SuperCTL file containing the new configuration must be open. INFO PLAN { plan-name | * [ , DETAIL ] } plan-name specifies the name of a PLAN object. * displays the migration information in all PLAN objects in the SuperCTL configuration file.
PXMCOM Commands INFO PROGRAM INFO PROGRAM This command displays the attribute values defined in the PATHMON configuration file for a PROGRAM object. INFO PROGRAM program-name program-name specifies the name of a previously defined and added PROGRAM object. Considerations • • INFO PROGRAM displays all of the PXMCFG SET PROGRAM attribute values that you explicitly defined for the PROGRAM object.
PXMCOM Commands INFO ROUTER INFO ROUTER This command displays the current configuration of a ROUTER object. INFO ROUTER { router-name | * } router-name specifies the name of a previously defined and added ROUTER object. * displays the configuration information for all ROUTER objects in the SuperCTL configuration file. Considerations • • INFO NODE displays all of the PXMCFG SET ROUTER attribute values that you explicitly defined for the NODE object.
PXMCOM Commands INFO SERVER INFO SERVER This command displays the attribute values defined in the PATHMON configuration file for a server class. INFO SERVER { server-class } { GROUP group-name } { * } server-class specifies the name of a previously defined and added SERVER object. GROUP group-name specifies the name of a set of SERVER objects, each configured as a member of the specified group. The INFO SERVER command is issued to each SERVER object associated with this group.
INFO TCP PXMCOM Commands INFO TCP This command displays the attribute values defined in the PATHMON configuration file for a TCP process. This command does not display information about external TCPs (TCPs that are controlled by another Pathway/XM environment). INFO TCP { term-name } { GROUP group-name } { * , option } option is: { SEL [ NOT ] { PENDING | RUNNING | STOPPED } } { STATE [ NOT ] { PENDING | RUNNING | STOPPED } } term-name specifies the name of a TERM object.
PXMCOM Commands INFO TCP Considerations • • • • INFO TCP displays both the TCP process attribute values you explicitly defined in the PXMCFG SET TCP statements for the TCP template and default values for the attributes you did not explicitly define. The attributes are displayed in alphabetic order. You can direct the output of this command to a file by using the OUT command before executing the INFO command.
PXMCOM Commands INFO TELL INFO TELL This command displays the text of a pending tell message. INFO TELL { number | * } number specifies an integer that identifies the message whose text is to be displayed. * displays the text of all pending tell messages.
INFO TERM PXMCOM Commands INFO TERM This command displays the attribute values defined in the PATHMON configuration file for a TERM object. This command can be issued for configured and temporary TERM objects. INFO TERM { [ pathmon-object.
PXMCOM Commands INFO TERM Considerations • • INFO TERM displays only the PXMCFG SET TERM attribute values that you explicitly defined for a TERM object. The attributes are displayed in alphabetic order. You can direct the output of this command to a file by using the OUT command before executing the INFO command.
PXMCOM Commands INSPECT TERM INSPECT TERM This command invokes the Inspect process to debug a SCREEN COBOL program running on a TERM object. This command establishes a breakpoint at the next program instruction; the program waits for commands from the Inspect process. Before you use the INSPECT TERM command, the PXMCFG SET TCP INSPECT attribute must be set to ON. This command can be issued for configured and temporary TERM objects. INSPECT TERM { [ pathmon-object.
PXMCOM Commands INSPECT TERM Examples The following commands invoke the INSPECT process to debug a program running on the specified TERM objects: INSPECT TERM TERM-1 INSPECT TERM-2, FILE $TERM6 Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 11 -40
PXMCOM Commands LOG1 and LOG2 LOG1 and LOG2 These commands name the files that are used globally by all PATHMON processes and TCP processes in the Pathway/XM environment for reporting errors and changes in object status. The PATHMON processes generate messages in the specified format. Event messages are used for reporting to an operator or application program through the Event Management Service (EMS), a part of Distributed Systems Management (DSM). LOG1 [ file-name [ , { EVENTFORMAT | STATUS } ]...
PXMCOM Commands LOG1 and LOG2 Considerations • • • Before the LOG1 and LOG2 commands are used to specify a log file, all log messages are sent to the system default file, $0. If two or more Pathway/XM environments are running on the same physical system, both default to the same $0. LOG1 and LOG2 command settings are stored in the current configuration portion of the SuperCTL configuration file and are preserved during a cool and warm start, but not during a cold start.
PXMCOM Commands OBEY OBEY This command causes commands to be read from a specified command file. OBEY file-name file-name specifies a file name. The file can be a disk file, terminal, or process from which PXMCOM or PXMCFG reads commands or statements. file-name can also be the name of a DEFINE. Considerations • • PXMCOM reads and executes commands from the named file until it encounters an EXIT command or the end of the file.
PXMCOM Commands OPEN OPEN This command opens the SuperCTL configuration file. OPEN superctl-file superctl-file specifies the name of the SuperCTL configuration file for the currently running Pathway/XM environment. Consideration If you attempt to open a file which supersedes another, already open SuperCTL file, the rolling configuration migration automatically starts and the PLAN objects are automatically executed in the correct order. This can take a noticeable period of time.
PXMCOM Commands OUT OUT This command determines the output device or file for all information returned to users by Pathway/XM processes. When executed with a file name, the OUT command causes the PXMCOM process to write all screen activity to the specified output file. When executed again with no file name, the PXMCOM process directs all information to the screen, OUT file-name file-name specifies the name of an output file into which all activity on the screen is written.
REFRESH-CODE TCP PXMCOM Commands REFRESH-CODE TCP This command directs the TCP process to read the SCREEN COBOL directory file to check for the latest version of a called program. This command is effective only if the TCP process is running and the CHECK-DIRECTORY attribute is set to OFF. Use this command when a new version of a SCREEN COBOL program (in the TCLPROG file) becomes available to the TCP.
PXMCOM Commands REFRESH-CODE TCP Considerations • • In production systems, use the REFRESH–CODE TCP command to add a new version of a SCREEN COBOL program to the application. The REFRESH-CODE TCP command operates in conjunction with the TCP CHECK-DIRECTORY attribute. When the attribute is set to OFF, the TCP process reads the TCLPROG directory file during a SCREEN COBOL CALL statement only if one of the following conditions exists: • • The called program is not in the TCP process code area.
PXMCOM Commands RESUME SERVER RESUME SERVER This command releases the suspension of a distributed server class and resumes the processing of transactions queued for the class. RESUME SERVER { server-class } { GROUP group-name } { * } server-class specifies the name of a previously suspended distributed server class. Note. This command does not apply to direct or replicated server classes. GROUP group-name specifies the name of a set of SERVER objects, each configured as a member of the specified group.
RESUME TERM PXMCOM Commands RESUME TERM This command restarts a screen program that has been suspended with the SUSPEND TERM command. The RESUME TERM command changes the TERM state to RUNNING. This command can be issued to configured and temporary TERM objects. RESUME TERM { [ pathmon-object.
PXMCOM Commands RESUME TERM Considerations • • • After you enter a RESUME TERM command, the SCREEN COBOL program starts executing at the point where the TERM object was suspended. Screen recovery is performed before the program resumes normal execution. If a TERM object in TMF transaction mode was suspended for a programmatic reason and is in a restartable state, the RESUME TERM command initiates TERM activity by restarting the logical transaction at the BEGIN-TRANSACTION verb.
PXMCOM Commands RUN PROGRAM RUN PROGRAM This command initiates the execution of a SCREEN COBOL program on a device interoperating with your Pathway/XM environment. When this command is issued, the PATHMON process performs the following: 1. Creates a temporary TERM object based on the configuration information in the PROGRAM object template. (This is similar to the PXMCFG ADD TERM statement.) Assigns an object name beginning with a number to distinguish it from configured TERM objects. 2.
PXMCOM Commands RUN PROGRAM PRINTER specifies the printer to be used for the SCREEN COBOL PRINT SCREEN verb. An attached printer either physically plugs into the terminal (for example, a T16-6520 or T16-6530 terminal) or connects to the same line controller (for example, an IBM 3270 compatible terminal using AM3270) as the terminal on which the SCREEN COBOL program runs. file-name specifies the file name for the print device.
RUN PROGRAM PXMCOM Commands The file-name parameter must be represented in network form. It must begin with a $ (dollar sign) followed by one to six alphanumeric characters; maximum of seven characters including the $. The first character must be alphabetic. Specifying a terminal name as the file allows you to run PXMCOM on one terminal and the SCREEN COBOL program on another terminal.
PXMCOM Commands RUN PROGRAM NOWAIT causes the program to execute concurrently with PXMCOM, so that the PXMCOM prompt returns immediately to your screen. To use the NOWAIT option, you must specify a terminal that is different from the terminal on which you give the RUN PROGRAM command. If you do not specify this option, the PXMCOM prompt does not return to your screen until after the program has completed running.
PXMCOM Commands START PATHWAY 11 PXMCOM Commands START PATHWAY This command starts a Pathway/XM environment. See Starting a Pathway/XM Environment on page 7-11 for a more detailed discussion of the steps performed by the START PATHWAY command. START PATHWAY { COLD | COOL | WARM } COLD creates a new Pathway/XM environment using the initial configuration information stored in the SuperCTL file to build new PATHMON configuration files.
PXMCOM Commands START PATHWAY Considerations • • • This command is executed without any warnings or prompts (which is the same as the former PATHCOM ! option in underlying products). To increase performance, TERM object configurations are written to the appropriate PATHMON configuration files only when a START TERM command is issued. During the startup process, the subvolume name of the PXMCOM object file is stored in the SuperCTL file.
PXMCOM Commands START PLAN START PLAN This command starts one or more migration plans. START PLAN { plan-name | * } plan-name specifies the name of a PLAN object generated by the INVENTORY command. * issues the START PLAN command to all PLAN objects in the PSuperCTL configuration file. CONSIDERATIONS • • • You must start migration plans in the sequence listed by the INVENTORY command. When a plan is started it cannot be stopped.
PXMCOM Commands START ROUTER START ROUTER This command initiates operation of a router. You must issue this command before you issue the START TERM command for the terminals associated with the router.. START ROUTER { router-name | * } router-name specifies the name of a previously defined and added ROUTER object. * issues the START ROUTER command to all ROUTER objects in the Pathway/XM environment.
PXMCOM Commands START SERVER START SERVER This command initiates operation of the static servers in a server class. The number of static servers started is determined by the value set for the NUMSTATIC attribute. This command does not affect server classes in the FROZEN state. START SERVER { server-class } { GROUP group-name } { * } server-class specifies the name of a previously defined and added SERVER object.
START TCP PXMCOM Commands START TCP This command initiates operation of TCP processes. This command cannot initiate external TCPs (TCPs that are controlled by another Pathway/XM environment). If the primary processor defined for a TCP is unavailable, the PATHMON process starts the TCP in the backup processor defined for that TCP.
PXMCOM Commands START TCP Examples The following command starts only the TCP that manages the terminal PARTS1: START TCP PARTS1 The following command starts all of the TCP processes in a given Pathway/XM environment: START TCP * The following command starts all TCP processes in the STOPPED state: START TCP *, STATE STOPPED Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 11 -61
START TERM PXMCOM Commands START TERM This command directs the TCP to begin executing a SCREEN COBOL program on one or more designated TERM objects. The TCP that controls the TERM objects and the ROUTER object associated with the TERM objects must be running before you issue this command. This command can be issued only to configured TERM objects. START TERM { [ pathmon-object.
START TERM PXMCOM Commands SEL or STATE issues the START TERM command only to TERM objects in the specified state. You can substitute SEL for STATE. Possible states are: RUNNING STOPPED SUSPENDED NOT RUNNING NOT STOPPED NOT SUSPENDED This command affects only those TERM objects in the STOPPED state. If you specify any other state, the system displays the command prompt again; it does not display any output or generate an error message.
STATS NODE PXMCOM Commands STATS NODE This command displays the following resource usage and performance statistics for the resources in a NODE object: • • For each CPU, the maximum and current number of process reservations (including reservations for all types of processes, not just distributed server processes) The percentage of reservation requests denied and reservation extension requests STATS NODE { node-name | * } [ RESET ] node-name specifies the name of a previously defined and added NODE ob
PXMCOM Commands STATS NODE Example The following command displays statistical information gathered about the node NODE-A: STATS NODE NODE-A Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 11 -65
STATS ROUTER PXMCOM Commands STATS ROUTER This command displays the following resource usage and performance statistics for the resources in a ROUTER object: • • • The number of connection requests waiting service The number of connection requests received per hour The number of connection timeouts STATS ROUTER { router-name | * [ , RESET ] } router-name specifies the name of a previously defined and added ROUTER object.
PXMCOM Commands STATS SERVER STATS SERVER This command displays resource usage and performance statistics, including response time information. These statistics provide information about server class operations; they are tracked by link managers such as LINKMON processes, TCP processes, and LCS processes that have links to a server class. LINKMON processes collect these statistics continuously; you cannot set an attribute that controls whether LINKMON processes track statistics.
PXMCOM Commands STATS SERVER DETAIL for distributed server classes, directs the PXMCOM process to return the following additional information on the LCS process: queue length, average arrival time, and average service time. This option is not valid for direct and replicated server classes. Considerations • • The STATS SERVER command displays statistics for link managers, such as LINKMON processes, TCP processes, and LCS processes. The link managers store the statistics for a server class.
PXMCOM Commands STATS TCP STATS TCP This command displays resource usage and performance statistics collected by the TCP. These statistics provide information about TCP operations and data space allocations. This command does not display statistics for any external TCP processes (TCP processes that are controlled by another Pathway/XM environment) that might be linked to local server processes.
STATS TCP PXMCOM Commands SEL or STATE issues the STATS TCP command only to TCP processes in the specified state. You can substitute SEL for STATE. Possible states are: PENDING RUNNING STOPPED NOT PENDING NOT RUNNING NOT STOPPED This command affects only those TCP processes in the RUNNING or PENDING state. If you specify any other state, the system displays the command prompt again; it does not display any output or generate an error message.
STATS TERM PXMCOM Commands STATS TERM This command displays resource-usage and performance statistics, including response time information, collected by the TCP. These statistics provide information about TERM object operations. The STATS attribute in the CONTROL TCP command and the PXMCFG SET TCP statement controls whether a TCP tracks its statistics. This command can be issued for configured and temporary TERM objects. STATS TERM { [ pathmon-object. ]term-name } [{ FREQTABLE | RESET }] ...
STATS TERM PXMCOM Commands RESET sets back to zero the counters used for the statistics measurements. SEL or STATE issues the STATS TERM command only to TERM objects in the specified state. Possible states are: RUNNING STOPPED SUSPENDED NOT RUNNING NOT STOPPED NOT SUSPENDED This command affects only those TERM objects in the RUNNING or SUSPENDED state. If you specify any other state, the system displays the command prompt again; it does not display any output or generate an error message.
STATUS LINKMON PXMCOM Commands STATUS LINKMON This command displays information about LINKMON processes that have links to server processes or to LCS processes. Note. This command is included in this version of Pathway/XM only for purposes of compatibility with older versions of NonStopTM TS/MP. STATUS LINKMON { L\node.$process-name | * } L\node.$process-name specifies the name of the LINKMON process. L Identifies the process as a LINKMON process.
PXMCOM Commands STATUS LINKMON Examples The following command displays status information for all LINKMON processes: STATUS LINKMON * The following commands display status information for a specific LINKMON process running on a specific physical (Expand) node: STATUS LINKMON L\NWREG.$ZL05 The following commands direct the LINKMON status information to the file named STATFLE: OUT STATFILE STATUS LINKMON L\CPTNO.
STATUS NODE PXMCOM Commands STATUS NODE This command displays general status information for a NODE object, including the name of the associated PB process, CPU weight and process workload information, and (optionally) counts of process reservations for distributed server classes. STATUS NODE { node-name | * } [ , DETAIL ] node-name specifies the name of a previously defined and added NODE object. * displays status information for all NODE objects in the SuperCTL configuration file.
STATUS PATHMON PXMCOM Commands STATUS PATHMON This command displays the status of each PATHMON process and its configuration file and the Pathway/XM environment logging files. This command also displays a list of the processes currently communicating with each PATHMON process. STATUS PATHMON Consideration You can direct the output of this command to a file by using the OUT command before executing the STATUS command.
STATUS PATHMON PXMCOM Commands Display Field Description PATHMON STATE PATHMON process name and current state. Possible state values are: STARTING A PATHWAY START command has not completed. RUNNING A PATHWAY START command has completed. SHUTTINGDOWN A shutdown request has not completed. PID Process ID of the requester process (PATHMON, TCP, or LINKMON process) PAID Process-accessor ID of the requester process REQNUM The PATHMON process internal identifier of a requester.
STATUS PATHWAY PXMCOM Commands STATUS PATHWAY This command displays status information about the Pathway/XM environment.
PXMCOM Commands STATUS PLAN STATUS PLAN This command displays the execution status of a migration plan. If the migration plan is in progress, it displays the objects in the plan that are scheduled next to be migrated. STATUS PLAN { plan-name | * } plan-name specifies the name of a PLAN object previously generated by the INVENTORY command. * displays status information for all PLAN objects in the SuperCTL configuration file.
STATUS ROUTER PXMCOM Commands STATUS ROUTER This command displays general status information for a ROUTER object. Information displayed includes current state, process name used by associated handler processes, and the number of active connections currently being processed by TERM objects. STATUS ROUTER { router-name | * } [ , DETAIL ] node-name specifies the name of a previously defined and added ROUTER object. * displays status information for all ROUTER objects in the SuperCTL configuration file.
STATUS SERVER PXMCOM Commands STATUS SERVER This command displays the current status of a server class. For distributed server classes, the STATUS SERVER command returns status information on the associated LCS process and, optionally, on the individual server processes in the server class. For direct and replicated server classes, STATUS SERVER command returns only status information on the individual server processes in the server class.
STATUS SERVER PXMCOM Commands DETAIL for distributed server classes, requests status information on the individual server processes associated with the specified server class. This option does not apply to direct and replicated server classes. Considerations • • You can direct the output of this command to a file by using the OUT command before executing the STATUS command. To support all versions of the underlying PATHCOM process, from D32.
STATUS SERVER PXMCOM Commands Display Field Description INFO Additional information regarding the error number. The freeze-state may also be displayed. Possible values are: LINK COUNT LINKER FREEZE-PENDING The server class received a FREEZE command, but the state of one or more terminals delays the freeze from completing. The STATUS SERVER FREEZE command can be used to display the names of these terminals. FROZEN The server class is frozen.
STATUS SERVER PXMCOM Commands Display Field Description STATE Current state of the server process. Possible values are: STOPPED The server process is stopped and has no links to link managers, such as LINKMON or LCS processes. RUNNING The server process is running. PENDING The last link was returned but the server process has not yet stopped.
STATUS TCP PXMCOM Commands STATUS TCP This command displays the status of one or more TCPs and, optionally, the status of the terminals they control. STATUS TCP { term-name } [ , DETAIL ] { GROUP group-name } { * , option } option is: { SEL [ NOT ] { PENDING | RUNNING | STOPPED } } { STATE [ NOT ] { PENDING | RUNNING | STOPPED } } term-name specifies the name of a TERM object. The STATUS TCP command is issued to the TCP that manages this TERM object.
STATUS TCP PXMCOM Commands Consideration You can direct the output of this command to a file by using the OUT command before executing the STATUS command. Display Fields The fields in the displays returned by this command are as follows: Display Field Description ACCEPT Possible values are: YES Terminal execution is at an ACCEPT statement. YES-RESTART The terminal is in transaction mode; the transaction has been restarted.
STATUS TCP PXMCOM Commands Display Field Description TRANSMODE Whether or not the terminal is in transaction mode. Possible value is: YES WAIT The terminal is in transaction mode and the data is protected by TMF auditing. If the terminal is not in transaction mode, this field is left blank. Reason the terminal is waiting. The possible values are listed separately below. The possible values for the WAIT field are as follows: wait-cause Description READY The terminal is ready.
STATUS TCP PXMCOM Commands wait-cause Description BKPT-HOLD The terminal task is at an Inspect breakpoint. CHECKPOINT The terminal is waiting for completion of a checkpoint. END-TRANS The terminal is waiting for the TMF subsystem to complete an ENDTRANSACTION operation. INSPECT-FILE The terminal task is waiting to communicate with the Inspect process to perform some Inspect operation. IMON-I/O The terminal task is doing an I/O operation to the IMON process.
STATUS TERM PXMCOM Commands STATUS TERM This command displays the current status of one or more TERM objects. This command can be issued for configured and temporary TERM objects. STATUS TERM { [ pathmon-object. ]term-name } [ , DETAIL ] { GROUP group-name } { * , option } option is: { SEL { STATE [ NOT ] { RUNNING | STOPPED | SUSPENDED } } [ NOT ] { RUNNING | STOPPED | SUSPENDED } } pathmon-object specifies the internal PATHMON object name that is displayed in the header of a STATUS TERM command.
STATUS TERM PXMCOM Commands Considerations • • • You can direct the output of this command to a file by using the OUT command before executing the STATUS command. In a production environment with a large number of terminals, it is better not to use the TERM * option to return status information on all TERM objects in the PATHMON environment.
STATUS TERM PXMCOM Commands Display Field Description SERVER Name of the server class the terminal is communicating with or waiting for STATE Current state of the TERM object.
PXMCOM Commands STOP PATHWAY STOP PATHWAY This command stops a Pathway/XM environment. The STOP PATHWAY command cannot be reversed; in other words, once you have initiated the shutdown process, you cannot stop that process. Note. The STOP PATHWAY command replaces the PATHCOM SHUTDOWN2 command. In effect, the STOP PATHWAY command issues a PATHCOM SHUTDOWN2 command to all Pathway environments managed by this Pathway/XM environment.
PXMCOM Commands STOP PATHWAY STATUS specifies whether status information is to be displayed during a shutdown. If you omit this attribute, the default is QUIET. QU or QUIET directs PXMCOM not to display any messages until the stop request completes. After the stop request is completed, PXMCOM displays the results of the shutdown. AG or AGGREGATE directs PXMCOM to display the Pathway environment status every 20 seconds while shutdown is executing.
STOP PATHWAY PXMCOM Commands Considerations • • • • • The STOP PATHWAY command stops all objects managed by the Pathway/XM environment.
STOP ROUTER PXMCOM Commands STOP ROUTER This command stops the listener process associated with the ROUTER object. TERM objects that still have the listener process open are closed and then stopped with an error condition.. STOP ROUTER { router-name | * } router-name specifies the name of a previously defined and added ROUTER object. * issues the STOP ROUTER command to all ROUTER objects in the SuperCTL configuration file..
PXMCOM Commands STOP SERVER STOP SERVER This command directs all link managers, such as LINKMON processes, TCP processes, and LCS processes to return their links to a server class. The server class must be in the FROZEN state before you issue this command. STOP SERVER { server-class } { GROUP group-name } { * } server-class specifies the name of a previously defined and added SERVER object.
STOP TCP PXMCOM Commands STOP TCP This command stops TCP processes. This command cannot stop external TCPs (TCPs controlled by another Pathway/XM environment) that are linked to local server processes. STOP TCP { term-name } [ , WAIT ] { GROUP group-name } { * , option } option is: { SEL [ NOT ] { PENDING | RUNNING | STOPPED } } { STATE [ NOT ] { PENDING | RUNNING | STOPPED } } term-name specifies the name of a TERM object. The STOP TCP command is issued to the TCP that manages this TERM object.
PXMCOM Commands STOP TCP WAIT directs the PXMCOM process to retry the command every second if the STOP command is rejected with an invalid TCP-state error. If you omit this option, the STOP command aborts on any error. Considerations • • The PATHMON process stops all TCP processes in the order that you specify. It cannot stop a TCP until all of the terminals controlled by the TCP are stopped.
STOP TERM PXMCOM Commands STOP TERM This command stops a TERM object. The TCP stops a TERM object as soon as the TERM object reaches a qualified state. A qualified state exists when the following three conditions are met: • • • The TERM object has reached a SCREEN COBOL ACCEPT statement. The SCREEN COBOL special register STOP-MODE is set to zero. The TERM object (if running under TMF auditing) is not in TMF transaction mode. This command can be issued to configured and temporary TERM objects.
STOP TERM PXMCOM Commands RUNNING STOPPED SUSPENDED NOT RUNNING NOT STOPPED NOT SUSPENDED This command affects only those TERM objects in the RUNNING or SUSPENDED state. If you specify any other state, the system displays the command prompt again; it does not display any output or generate an error message.
PXMCOM Commands SUSPEND SERVER SUSPEND SERVER This command temporarily stops the processing of transactions queued for a distributed server class in the LCS process. Send operations from TCP requesters and client processes are queued until the suspension is released. The RESUME SERVER command releases the suspension. SUSPEND SERVER { server-class } { GROUP group-name } { * } server-class specifies the name of a previously defined and added distributed server class. Note.
SUSPEND TERM PXMCOM Commands SUSPEND TERM This command directs the TCP to temporarily suspend execution of the SCREEN COBOL program. This command can be used for debugging when it is important to preserve the TERM object in its most recent state. The RESUME TERM command releases the suspension. A TERM object is suspended as soon as it reaches a qualified state, which exists when the following three conditions are met: • • • The TERM has reached a SCREEN COBOL ACCEPT statement.
SUSPEND TERM PXMCOM Commands SEL or STATE issues the SUSPEND TERM command only to TERM objects in the specified state. You can substitute SEL for STATE. Possible states are: RUNNING STOPPED SUSPENDED NOT RUNNING NOT STOPPED NOT SUSPENDED This command affects only those TERM objects in the RUNNING state. If you specify any other state, the system displays the command prompt again; it does not display any output or generate an error message.
TELL TERM PXMCOM Commands TELL TERM This command displays a message on a terminal or set of terminals. The TCP waits for the terminal operator to complete the current screen before displaying the message, so normal operation is not disrupted. TELL TERM { [ pathmon-object.
PXMCOM Commands TELL TERM Considerations • • • Each terminal has a circular queue for tell messages. If the queue is full when a new tell message is sent, the oldest tell message in the queue is overwritten by the new message. When you issue a TELL command, the tell message is assigned a number between zero and the value of MAXTELLS. The PATHMON process deletes a tell message automatically when all destination terminals acknowledge receiving the message.
PXMCOM Commands THAW SERVER THAW SERVER This command allows link managers such as LINKMON processes, TCP processes, and LCS processes to resume sending requests to server processes in a frozen server class. THAW SERVER { server-class } { GROUP group-name } { * } server-class specifies the name of a previously defined and added SERVER object. GROUP group-name specifies the name of a set of SERVER objects, each configured as a member of the specified group.
PXMCOM Commands TRACELOG TRACELOG This command directs PXMCOM to send all commands and all displayed output to a trace-log file. This command remains in effect for the duration of the PXMCOM session or until it is executed again. TRACELOG [ file-name ] file-name specifies the name of the file in which PXMCOM is to record commands and displayed output and begins the TRACELOG function. If you omit this attribute, the TRACELOG function terminates.
PXMCOM Commands VERBOSE VERBOSE This command specifies whether PXMCOM displays information about all underlying PATHCOM commands it sends to the PATHMON processes. It records information that can be used later, if needed, in troubleshooting. The VERBOSE command remains in effect for the duration of the PXMCOM session or until it is explicitly turned off. VERBOSE { ON | OFF } ON | OFF specifies whether PXMCOM displays information about underlying commands it sends to the PATHMON processes.
VOLUME PXMCOM Commands VOLUME This command temporarily defines a default physical node, volume, and/or subvolume for the expansion of any Guardian file names associated with objects in the Pathway/XM environment, except command-file names used with the OBEY command. Guardian file names specified in SET commands are expanded with the current value defined by the VOLUME command. VOLUME [ [ [ [ { { { { \node \node \node \node . . . . } $volume.
PXMCOM Commands Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 11- 110 VOLUME
12 PXMCFG Messages This section describes the messages generated by the PXMCFG process. These messages are included in the output of the PXMCFG process, inserted in the listing below the relevant PXMCFG statement. Message numbers for PXMCFG messages are in the range from 6800-6999. 6800 *6800* ENTRY ALREADY EXISTS Cause. An ADD statement specified an object that has already been added. Effect. The object is not added. Recovery. Check the name of the specified object and change it, if needed.
PXMCFG Messages 6804 *6804* ILLEGAL LINKDEPTH VALUE (1:255) Cause. The value specified for the LINKDEPTH attribute was either 0 or greater than 255. Effect. No SuperCTL file is created. Recovery. Specify a valid value for the attribute. 6805 *6805* ILLEGAL NUMBER Cause. The number format entered is not valid. Effect. No SuperCTL file is created. Recovery. Specify a valid number for the attribute. 6806 *6806* ILLEGAL PRIORITY VALUE Cause. The value specified for the PRI attribute is not valid. Effect.
PXMCFG Messages 6808 *6808* ILLEGAL SYNTAX Cause. The sequence of input characters does not conform to the syntax for the statement. Effect. No SuperCTL file is created. Recovery. Reenter the statement with the correct syntax. 6809 *6809* ILLEGAL TIME VALUE Cause. The time value entered cannot be represented in 16 bits. Effect. No SuperCTL file is created. Recovery. Enter an acceptable time value. 6810 *6810* INVALID CPU WEIGHT Cause.
PXMCFG Messages 6812 *6812* INVALID SYSTEM NAME Cause. The physical node specified cannot be found. Effect. No SuperCTL file is created. Recovery. Specify the name of an existing physical node. 6813 *6813* INVALID VALUE FOR WEIGHT Cause. The value specified for the WEIGHT attribute for a TERM object exceeds the value specified for the MAXWEIGHTS attribute for the TCP associated with the TERM object. Effect. No SuperCTL file is created. Recovery.
PXMCFG Messages 6816 *6816* NO SUCH ENTRY Cause. The object name specified does not exist. Effect. No SuperCTL file is created. Recovery. Either enter the correct object name or make sure the specified object is defined and added earlier in the PXMCFG source file. 6817 *6817* NODE IS NOT DEFINED AS A CLIENT NODE Cause. The NODE object specified for a TCP is defined as a server node. Effect. No SuperCTL file is created. Recovery. TCPs must be configured for client nodes.
PXMCFG Messages 6820 *6820* NUMSTATIC EXCEEDS MAXSERVERS Cause. The value specified for the NUMSTATIC attribute for a SERVER object exceeds the value specified for the MAXSERVERS attribute. Effect. No SuperCTL file is created. Recovery. Either decrease the value for the NUMSTATIC attribute or increase the value for the MAXSERVERS attribute. 6821 *6821* PATHMON NODE NOT FOUND FOR A TANDEM SYSTEM Cause.
PXMCFG Messages 6824 *6824* SERVER ATTRIBUTE AND TYPE DO NOT MATCH Cause. The value specified for a server class TYPE attribute conflicts with one or more attribute values defined for the server class. Effect. No SuperCTL file is created. Recovery. Change the conflicting attribute value. 6825 *6825* STRING TOO LONG Cause. An input string exceeds the maximum length allowed. Effect. No SuperCTL file is created. Recovery. Specify an input string with a valid length.
PXMCFG Messages 6828 *6828* TOO MANY NESTED INCLUDE FILES (MAX=15) Cause. The number of nested INCLUDE files exceeds the maximum depth of 15. Effect. No SuperCTL file is created. Recovery. Rewrite the OBEY or INCLUDE files with fewer nested files. 6829 *6829* TOO MANY NODES Cause. The number of NODE objects defined for the Pathway/XM environment exceeds the maximum of 256. Effect. No SuperCTL file is created. Recovery. Decrease the number of NODE objects defined.
PXMCFG Messages 6832 *6832* TOO MANY TCP TEMPLATES Cause. The number of TCP templates defined exceeds the maximum of 204800. Effect. No SuperCTL file is created. Recovery. Decrease the number of TCP templates defined. 6833 *6833* TOO MANY TERMS Cause. The number of TERM objects defined exceeds the maximum of 1048064. Effect. No SuperCTL file is created. Recovery. Decrease the number of TERM objects defined. 6834 *6834* DISTRIBUTION ERROR Cause. This is an internal error. Effect.
PXMCFG Messages 6836 *6836* NUMBER OF PREDEFINED SERVERS WOULD EXCEED MAXSERVERS Cause. The number of names specified for a direct server class is greater than the value assigned to the MAXSERVERS attribute. Effect. The PXMCFG process does not generate a SuperCTL file. Recovery. Either change the number of process names given or the value of the MAXSERVERS attribute; these two values must be the same. 6837 *6837* NUMBER OF PREDEFINED SERVERS IS LESS THAN MAXSERVERS Cause.
PXMCFG Messages 6840 *6840* TOO MANY ASSIGN ENTRIES Cause. The total number of SET SERVER ASSIGN statements exceeds 4094. Effect. The PXMCFG process does not generate a SuperCTL file. Recovery. Either reduce the number of SET SERVER ASSIGN statements or divide the Pathway/XM environment into two Pathway/XM environments. 6841 *6841* TOO MANY DEFINES ENTRIES Cause. The total number of SET SERVER DEFINE statements exceeds 4094. Effect. The PXMCFG process does not generate a SuperCTL file. Recovery.
PXMCFG Messages 6844 *6844* THE CLIENT NODE ATTRIBUTE MUST BE DEFINED BEFORE THE CLIENT ATTRIBUTE CAN BE PROCESSED Cause. The SET TCP NODE statement was not specified. The NODE attribute is required to evaluate swap file-name references. Effect. The PXMCFG process does not generate a SuperCTL file. Recovery. Enter a SET TCP NODE statement. 6845 *6845* ENTRY ALREADY EXISTS object name Cause. The object name has already been defined in the configuration. Effect.
PXMCFG Messages 6848 *6848* NUMSTATIC IN server-name ADJUSTED TO number-assigned TO BE A MULTIPLE OF THE NUMBER OF PATHMONS Cause. The number of PATHMON processes required (as calculated by PXMCFG) does not divide evenly into NUMSTATIC. Effect. The value of NUMSTATIC is adjusted to be a multiple of the number of PATHMON processes. Recovery. No recovery is required; this is an informational message only. 6849 *6849* MAXSERVERS IN server-name ADJUSTED TO number-assigned TO BE EQUAL TO NUMSTATIC Cause.
PXMCFG Messages 6852 *6852* NUMBER OF TERMS PER TCP (number-tcps) CALCULATED FOR tcp-name IS LOW Effect. The PXMCFG process has determined that less than 11 TERM objects are associated with a TCP process. Compaq experience indicates that assigning a small number of TERM objects to a TCP has an undesirable effect on performance. Cause. No effect; this is an informational message only. Recovery. No recovery required. To increase the ratio of TERM objects per TCP, modify the TCP weights.
PXMCFG Messages 6855 *6855* SUPERCTL ENTITY INSERT FAILED, ERROR=error-number Cause. The PXMCFG process failed to insert an object into the SuperCTL file; the reason is indicated by the error number. Effect. The PXMCFG process does not generate a SuperCTL file. Recovery. Use the error information to determine the problem, then correct the problem and retry building the SuperCTL file. 6856 *6856* SUPERCTL INVENTORY FAILED, ERROR=error-number Cause.
PXMCFG Messages 6859 *6859* SUPERCTL CLOSE FAILED, ERROR=error-number Cause. ThePXMCFG process received an error while trying to close the processing on the newly created SuperCTL file. Effect. The PXMCFG process may or may not generate a valid SuperCTL file. Recovery. Use the error information to determine the problem, then correct the problem and retry building the SuperCTL file. 6860 *6860* SAME GROUP NAME (name) USED FOR BOTH TERM AND SERVER ENTITIES Cause.
13 PXMCOM, PB, and LCS Messages This section describes the messages generated by the PXMCOM, process broker (PB), and link control service (LCS) processes. Log messages are written to the log files specified by the LOG1 and LOG2 commands. Error, warning, and informational messages are returned to the output device or file currently defined for the Compaq NonStop™ Pathway/XM environment. Messages in this section are described in numerical order.
PXMCOM, PB, and LCS Messages General Information Log messages have a maximum length of 132 characters; messages exceeding that limit are truncated. All messages described in this section have the following format: date, time, process-name: msg-level - *msg-number* process-type: msg-text date the date the message was generated. time the time the message was generated. process-name the name of the process that returned the event. msg-level the importance level of the message.
LCS Messages (Messages 6000-6199) PXMCOM, PB, and LCS Messages LCS Messages (Messages 6000-6199) The following messages are generated by LCS processes. 6000 *6000* LCS termination c: error-class, f: function, ID: error-condition, Detail: error-detail Cause. The LCS process stopped or terminated abnormally due to the condition specified in the message. If the LCS process terminated abnormally (abended), the most likely cause is an internal program error.
LCS Messages (Messages 6000-6199) PXMCOM, PB, and LCS Messages When the Values of error-class and function are… And the value of errorcondition is… The Error is Caused by… c: LB f: reserve or f: extend 1 Lost communication with PB c: LB f: connect 1 Error in opening the file to the PB c: ReceiveFile f: reply(msgtag) or f: reply(request) 1 Error in resetting transaction to null c: ProcCfig f: updateFromConfig, program-name 1 or 2 Error in program name c: ProcCfig f: updateFromConfig 2 3 4 5
PXMCOM, PB, and LCS Messages LCS Messages (Messages 6000-6199) 6001 *6001* Error parsing ASSIGN. Class: class Token: token ID: field-type Position: position class the function that was parsing the ASSIGN statement when the error occurred token the token in the error that may be displayed field-type the type of field being parsed when the error occurred.
PXMCOM, PB, and LCS Messages LCS Messages (Messages 6000-6199) 6003 *6003* Cannot communicate with $CMON. Bypassing $CMON processing. Cause. The LCS process encountered an error when trying to communicate with the $CMON process. This is a warning message. Effect. The LCS process stops trying to communicate with the $CMON process and continues processing. Recovery. This message indicates a problem with the application. Check the application to determine the problem.
PXMCOM, PB, and LCS Messages LCS Messages (Messages 6000-6199) 6006 *6006* Server restarting FileErr: file-system-error, retries: retries Cause. The LCS process encountered the specified file-system I/O error after attempting to restart the server process the specified number of times. Effect. If the reservation for the server process has not expired, the LCS makes another attempt to restart the server. Recovery. Determine the problem from the file-system error information included in the message.
PXMCOM, PB, and LCS Messages LCS Messages (Messages 6000-6199) 6009 *6009* File number: file-number, returned error: error-number Cause. The LCS process encountered an unexpected file-system error on the specified file. Effect. The LCS process stops. Recovery. Determine the problem from the file-system error information included in the message. Refer to the Guardian Procedure Errors and Messages Manual for more detailed information on the error.
PXMCOM, PB, and LCS Messages PB Messages (Messages 6200-6399) PB Messages (Messages 6200-6399) The following messages are generated by PB processes. 6201 *6201* Failed to configure, SuperCTL = filename, Error = error-number, error-class Cause. During its initialization phase, the PB process encountered an error while reading the specified SuperCTL configuration file. Effect. The PB process stops. Recovery.
PXMCOM, PB, and LCS Messages • • PB Messages (Messages 6200-6399) A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the Compaq Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6205 *6205* Backup process failed. Cause. The backup PB process failed. Effect. The backup PB process stops. Recovery. Informational message only; no corrective action is needed. 6206 *6206* Starting backup process in CPU cpu-number Cause. A backup PB process was started in the specified CPU. Effect. PB processing continues normally. Recovery. Informational message only; no corrective action is needed.
PXMCOM, PB, and LCS Messages • • PXMCOM Messages (Messages 6500-6799) A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the Compaq Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6504 *6504* Read error on OBEY file Cause. An error was returned when PXMCOM attempted to read an OBEY file. Effect. The commands in the OBEY file are not executed. Recovery. Check the OBEY file to determine the problem. 6505 *6505* Cannot read PXCCSTM Cause. An error was returned when PXMCOM attempted to read the PXCCSTM file. Effect. The PXMCOM process runs normally, but custom commands are not executed when PXMCOM is started.
PXMCOM, PB, and LCS Messages • PXMCOM Messages (Messages 6500-6799) Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the Compaq Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 6508 *6508* Send to object (object-name) failed, Error = error-number Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6511 *6511* PROCESS_GETINFO_ returned error-number Cause. The command interpreter was unable to locate the subvolume for an object file. PXMCOM, PATHMON, PATHCOM, TCP, PB, and LCS object files are assumed to be on the installation subvolume. Effect. The process fails. Recovery. Determine the problem from the error information in the message. 6512 *6512* Pathway/XM is not running Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Effect. The command fails. Recovery. Determine the problem from the error information in the message, correct it, and retry the command. 6517 *6517* Unable to assign node-name to PATHMON name Cause. The PXMCOM process was unable to assign the physical node specified in the SuperCTL file for a well-known, named PATHMON process. This message is usually preceded by message 6519 and may indicated a corrupted SuperCTL file. Effect.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Recovery. Determine the problem from the error information in the message, correct it, and retry the command. 6521 *6521* Failure reading PATHMON entity from SuperCTL file. Error=error-number Cause. The PXMCOM process encountered an error when attempting to read the PATHMON object’s configuration information stored in the SuperCTL file. Effect. The command fails. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Recovery. Determine the problem from the error information in the message, correct it, and retry the command. 6525 *6525* Failure reading TERM entity from SuperCTL file. Error=error-number Cause. The PXMCOM process encountered an error when attempting to read the TERM object’s configuration information stored in the SuperCTL file. Effect. The command fails. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Recovery. Determine the problem from the error information in the message, correct it, and retry the command. 6529 *6529* Failure updating TCP entity in SuperCTL file. Error=error-number Cause. The PXMCOM process encountered an error when attempting to update the TCP object’s configuration information stored in the SuperCTL file. Effect. The command fails. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6532 *6532* Cannot open SuperCTL file; status status-number Cause. The PXMCOM process encountered an error when attempting to open the SuperCTL file. Effect. The command fails. Recovery. Determine the problem from the error information in the message. 6541 *6541* SERVER does not exist or not in the correct state Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6552 *6552* NODE object does not exist Cause. A command specified a NODE object that is not defined in the SuperCTL configuration file. Effect. The command fails. Recovery. Reissue the command with the correct NODE object name. 6554 *6554* Unable to obtain CPU numbers from the PB for START SERVER Cause. The PXMCOM process was unable to obtain CPU numbers from the PB. Effect. The START SERVER command fails. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6557 *6557* Pathway must be completely shut down. PATHWAY first Issue STOP Cause. A problem has occured that requires the Pathway/XM environment to be shut down. Effect. The effect of any PXMCOM command, except the STOP PATHWAY command, is unpredictable. Recovery. Issue the STOP PATHWAY command. 6558 *6558* Pathway was not shut down properly. Issue STOP PATHWAY first Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6562 *6562* The server class server-class-name is in a state state Cause. The specified server class is in the indicated state, where state is one of the following: STOPPED, LOCKED, SUSPENDED, UNKNOWN. Effect. The command fails. Recovery. Change the state of the server class, then reissue the command. 6566 *6566* Server Class (server-class-name ) not SUSPENDED Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6569 *6569* Unable to SUSPEND Server Class (server-class-name ), Error error-number Cause. A SUSPEND SERVER command was issued to the specified server class but the LCS process controlling the server class rejected the request Effect. The command fails. The server class is left in an unknown state. Recovery. Determine the problem from the error information in the message. When the error is corrected, stop the server class then restart it.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) If your local operating procedures require contacting the Compaq Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 6580 *6580* Node (node-name ) has no assigned CPUs available Cause. Among the CPUs assigned to the specified NODE object, none are available. Effect. The command fails. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6585 *6585* Failure posting a READUPDATE, c: error-class, f: function, ID: field-identifier, Detail: error-detail Cause. The PXMCOM process was unable to read $RECEIVE messages because an internal error occurred. Effect. The PXMCOM process terminates abnormally. Recovery. Restart the PXMCOM process, and reissue the command.
PXMCOM, PB, and LCS Messages • • PXMCOM Messages (Messages 6500-6799) A description of the application task that was in progress when the error was encountered Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the Compaq Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6593 *6593* Error from PATHMON startup sending assigns: error-number Cause. The PXMCOM process encountered an I/O error when attempting to initialize a PATHMON process. Effect. The START PATHWAY command fails. Recovery. Determine the problem from the error information in the message, correct it, and retry the command. 6597 *6597* Error from PATHCOM open: error-number Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6601 *6601* No log file is open Cause. The PXMCOM process encountered an internal error while attempting to open a new trace log file. Effect. The PXMCOM process continues to run but the TRACELOG command fails. Recovery. Stop and then restart the PXMCOM process; reissue the TRACELOG command. 6602 *6602* LOG file has been opened Cause. The trace log file defined for the Pathway/XM environment was opened in response to a TRACELOG command.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6605 *6605* OUT file has been opened Cause. A file for output has been opened in response to an OUT command. This message is returned only if VERBOSE is set to ON. Effect. All information returned by subsequent commands is written to the file specified in the OUT command instead of to the screen. Recovery. Informational message only; no corrective action is needed. 6606 *6606* OUT file has been closed Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6609 *6609* Failed to open object object-name, error = error-number Cause. The PXMCOM process was not able to open the process associated with the object named in the message. The error number is the file-system error returned on this operation. Effect. If the message names a NODE object, the Pathway/XM environment is no longer running. If the messages names a server class, the LCS process associated with the server class has failed.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6621 *6621* No help available for that topic Cause. The topic requested in the HELP command was not found in the PXCHELP text file. Effect. The command fails. Recovery. Reissue the command with the correct help topic or enter different text to find the topic. 6622 *6622* No help available Cause. The PXMCOM process was not able to locate the specified HELP text file. Effect. The command fails. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6625 *6625* FC string is too long Cause. The resulting command line is longer than the maximum command length. Effect. The command fails. Recovery. If the command line contains multiple commands, enter each command on a separate command line. 6626 *6626* FC command is invalid in PXMCSTM Cause. The FC command was found in the PXMCSTM customization file during PXMCOM process startup. Effect.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6629 *6629* Redisplay command invalid in PXMCSTM Cause. The “?” command was encountered in the PXMCSTM customization file during PXMCOM process startup. Effect. The “?” command is not executed and processing continues to the next command in the PXMCSTM file. Recovery. Remove the “?” command from the PXMCSTM file. 6630 *6630* Redisplay command invalid in OBEY file Cause. The PXMCOM process encountered the “?” command in the obey file.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6633 *6633* Re-execute command invalid in OBEY file Cause. The PXMCOM process encountered the “!” command in the obey file. Effect. The “!” command is not executed and processing continues to the next command in the obey file. Recovery. Remove the “!” command from the obey file. 6634 *6634* Re-execute command invalid in run-line arguments Cause. The “!” command was entered on the PXMCOM command line. Effect.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Effect. The command fails. Recovery. Check the file-name syntax in the command and check the current environment settings using the ENV command. 6638 *6638* Unable to obtain CPU numbers from PB for START TCP. Defaulting. Cause. The PXMCOM process was unable to obtain CPU resources from the PB process associated with its node. Effect. The CPU defaults to the CPU used by the PATHMON process associated with the TCP.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Effect. The PXMCOM process continues to run but the ROUTER process, if it is present, does not function. Recovery. Determine the problem from the error information in the message. Stop and restart the ROUTER object. 6644 *6644* Failure updating ROUTER (router-name) in SuperCTL file, Error=error-number Cause.
PXMCOM, PB, and LCS Messages • PXMCOM Messages (Messages 6500-6799) Supporting documentation such as Event Management Service (EMS) logs, trace files, and dump files, if applicable If your local operating procedures require contacting the Compaq Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 6648 *6648* ROUTER (router-name) has already been started Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Effect. Until all of the modification plans are completed, some commands may generate errors when accessing new or removed objects. Recovery. Informational message only; no corrective action is needed. 6654 *6654* Modification PLANs activated, Linking SuperCTL files Cause. The PXMCOM process is opening a new SuperCTL file that is to supersede the active SuperCTL file currently being used by the Pathway/XM environment. Effect.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Recovery. Determine the problem from the error information in the message, correct it, and then retry the command. 6660 *6660* Error error-number , Can’t obsolete entity in SuperCTL Cause. The PXMCOM process encountered an error when attempting to update an object’s status during the execution of a modification plan. Effect. The modification plan is not completed; the SuperCTL file may be in a invalid state. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Effect. The PXMCOM command is not executed. Recovery. Informational message only; no corrective action is needed. 6665 *6665* Can’t retrieve status of modification PLAN Cause. The PXMCOM process encountered an error when attempting to read the status of an object in either the old or new SuperCTL file. Effect. The modification plan is not completed; the SuperCTL may be in a invalid state. Recovery.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6668 *6668* Failed to activate SuperCTL, Error=error-number Cause. The PXMCOM process encountered an error when attempting to update the SuperCTL file status. Effect. The SuperCTL is in an invalid state. Recovery. Issue a STOP PATHWAY command, then restart Pathway/XM specifying the new SuperCTL file. 6669 *6669* Unable to activate configuration. START PATHWAY cannot complete. Error=error-number Cause.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) Recovery. Check that the parameter name was entered correctly and, if not, reissue the command. If the parameter name was correct, then the parameter must be added through a new Pathway/XM configuration. 6672 *6672* Invalid ‘CONTROL SERVER DEFINE’, previously not declared Cause. The define name specified is not associated with the identified server class.
PXMCOM, PB, and LCS Messages PXMCOM Messages (Messages 6500-6799) 6675 *6675* Failure opening output file (file-name) Cause. The PXMCOM process encountered an error when attempting to open an output file. Effect. The command fails. Recovery. Make sure the specified file name is valid and that you have write access to the file. 6676 *6676* Corrected, NUMSTATIC adjusted to be a multiple of the number of PATHMONs Cause.
A Syntax Summary This appendix contains summaries of the PXMCFG statements and PXMCOM commands described in this manual. All statements and commands are listed in alphabetical order. Starting PXMCFG PXMCFG [ / run-option [ , run-option ]... / ] superctl-file run-option is: IN command-file OUT list-file CPU number NAME $process-name NOWAIT PRI number Starting PXMCHK PXMCHK superctl-file Starting PXMCOM PXMCOM [ / run-option [ , run-option ]... / ] [ command [ , command ]...
PXMCFG Statements Syntax Summary ADD PROGRAM program-name [ , program-attribute ]... ADD ROUTER router-name [ , node-attribute ] ... ADD SERVER server-class [ , server-attribute ]... ADD SERVICE server-group-name [ , service-attribute ] ... ADD TCP tcp-template [ , tcp-attribute ]... ADD TERM term-name [ , term-attribute ]... COMMENT text ENABLE ROUTER EXPORT { ON | OFF } INCLUDE file-name INVENTORY { active-supercontrol-file-name } RESET NODE [ node-keyword [ , node-keyword ]...
PXMCFG Statements Syntax Summary RESET PROGRAM [ program-keyword [ , program-keyword ]... ] program-keyword is: ERROR-ABORT GROUP OWNER PRINTER SECURITY TCP TMF TYPE terminal-type RESET ROUTER [ router-keyword [ , router-keyword ]... ] node-keyword is: PROTOCOL TCP HANDLER PORT CONNECTIONS GROUP WEIGHT INITIAL NONSTOP INSPECT PRINTER RESET SERVER [ server-keyword [ , server-keyword ]...
PXMCFG Statements Syntax Summary RESET TCP [ tcp-keyword [ , tcp-keyword ]... ] tcp-keyword is: AUTORESTART CHECK-DIRECTORY CODEAREALEN DEBUG DUMP GUARDIAN-LIB GUARDIAN-SWAP HIGHPIN HOMETERM RESET TERM INSPECT MAXINPUTMSGLEN MAXINPUTMSGS MAXPATHWAYS MAXREPLY MAXSERVERCLASSES MAXSERVERPROCESSES MAXTERMDATA NODE NONSTOP POWERONRECOVERY PRI PROGRAM SERVERPOOL STATS SWAP TCLPROG TERMBUF TERMPOOL [ term-keyword [ , term-keyword ]...
Syntax Summary PXMCFG Statements SET PATHWAY pw-attribute [ , pw-attribute ]... pw-attribute is: MAXEXTERNALTCPS number MAXLINKMONS number MAXPXMCOMS number MAXSPI number MAXTELLQUEUE number MAXTELLS number MAXTMFRESTARTS number OWNER ownerid SECURITY security-attribute SET PROGRAM program-attribute [ , program-attribute ]... program-attribute is: TCP template-name TYPE terminal-type ( type-attribute [ , type-attribute ]...
Syntax Summary PXMCFG Statements SET ROUTER router-attribute [ , router-attribute ] ... router-attribute is: PROTOCOL { SOCKET | HTTP } TCP template-name HANDLER TCP/IP-process-name PORT port-number CONNECTIONS number GROUP group-name WEIGHT weight-number INITIAL program-unit-name NONSTOP { ON | OFF } INSPECT { ON [ ( FILE file-name ) ] | OFF } PRINTER file-name SET SERVER server-attribute [ , server-attribute ]...
PXMCFG Statements Syntax Summary SET SERVER (continued) TIMEOUT number { HRS | MINS | SECS } TMF { ON | OFF } TYPE { DISTRIBUTED | REPLICATED | DIRECT } VOLUME volume-spec logical-unit is: { [ program-unit . ] } logical-file-name { * . } assign-spec is: [ file-name ] [ [ file-name ] , create-spec ...
Syntax Summary PXMCFG Statements SET TCP tcp-attribute [ , tcp-attribute ]...
Syntax Summary PXMCOM Commands SET TERM term-attribute [ , term-attribute ]...
PXMCOM Commands Syntax Summary CONTROL SERVER { server-class } { GROUP group-name } { * } , server-attribute server-attribute is: ASSIGN logical-unit , assign-spec DEFINE define-name , define-attribute-spec [ , define-attribute-spec ] ... GUARDIAN-LIB file-name HOMETERM device-name IN file-name MAXSERVERS number NUMSTATIC number OUT file-name PARAM parameter-name parameter-value [ , parameter-name parameter-value ] ... PRI priority PROGRAM file-name STARTUP string logical-unit is: { [ program-unit .
Syntax Summary PXMCOM Commands CONTROL TCP { term-name } { GROUP group-name } { * } tcp-attribute [ , tcp-attribute ]...
PXMCOM Commands Syntax Summary INFO PROGRAM program-name INFO ROUTER { router-name | * } INFO SERVER { server-class } { GROUP group-name } { * } INFO TCP { term-name } { GROUP group-name } { * , option } option is: { SEL [ NOT ] { PENDING | RUNNING | STOPPED } } { STATE [ NOT ] { PENDING | RUNNING | STOPPED } } INFO TELL { number | * } INFO TERM { [ pathmon-object.
PXMCOM Commands Syntax Summary OBEY file-name OPEN superctl-file OUT file-name REFRESH-CODE TCP { term-name } { GROUP group-name } { * , option } option is: { SEL [ NOT ] { PENDING | RUNNING | STOPPED } } { STATE [ NOT ] { PENDING | RUNNING | STOPPED } } RESUME SERVER { server-class } { GROUP group-name } { * } RESUME TERM { [ pathmon-object.
Syntax Summary PXMCOM Commands RUN PROGRAM program-name [ , run-parameter [ , run-parameter ]...
PXMCOM Commands Syntax Summary START TERM { [ pathmon-object. ]term-name } [,INITIAL program-unit-name ] { GROUP group-name } { * , option } option is: { SEL { STATE [ NOT ] { RUNNING | STOPPED | SUSPENDED } } [ NOT ] { RUNNING | STOPPED | SUSPENDED } } STATS NODE { node-name | * } [ RESET ] STATS ROUTER { router-name | * [ , RESET ] } STATS SERVER { server-class } [{ FREQTABLE | RESET }] ... { GROUP group-name } { * } [ , DETAIL ] STATS TCP { term-name } [{ FREQTABLE | RESET }] ...
PXMCOM Commands Syntax Summary STATUS LINKMON { L\node.
PXMCOM Commands Syntax Summary STATUS TERM { [ pathmon-object.
PXMCOM Commands Syntax Summary SUSPEND SERVER { server-class } { GROUP group-name } { * } SUSPEND TERM { [ pathmon-object. ]term-name } [ ! ] { GROUP group-name } { * , option } option is: { SEL { STATE [ NOT ] { RUNNING | STOPPED | SUSPENDED } } [ NOT ] { RUNNING | STOPPED | SUSPENDED } } TELL TERM { [ pathmon-object.
B Pathway/XM Reserved Words The following words are reserved for use as PXMCFG and PXMCOM keywords. They cannot be used as names of objects in a Compaq NonStop™ Pathway/XM environment.
Pathway/XM Reserved Words PARAM PATHMON PATHWAY PLAN PXMCFG PXMCHK PXMCOM PORT POWERONRECOVERY PRI PRINTER PROCESS PROCESSES PROGRAM PROTECTED PROTOCOL QU QUIET REFRESH-CODE REPLICATED RESET RESUME ROLE ROUTER RUN RUNNING SECS SECURITY SEL SERVER SERVERPOOL SERVICE SET SHARED SOCKET START STARTUP STATE STATS STATUS STOP STOPPED SUSPEND SUSPENDED SWAP SYSTEM T16-6510 T16-6520 T16-6530 T16-6530WP T16-6540 TCLPROG TCP TELL TERM TERMBUF TERMPOOL THAW TIMEOUT TMF TRAILINGBLANKS TYPE UNTIL VARIABLE VOLUME WAIT
C Configuration Limits and Defaults Table C-1 lists global limits for various items within a Compaq NonStop™ Pathway/XM environment. Table C-1. Global Pathway/XM Environment Limits Item Limits Per Pathway/XM environment ASSIGNs Maximum total of 4095 for all server classes.
Configuration Limits and Defaults Table C-1. Global Pathway/XM Environment Limits Item Limits Per Pathway/XM environment Requesters Maximum number of concurrent link requests from all TCP processes in a Pathway/XM enviroment to a server class is 38400 or the value of LINKDEPTH, whichever is smaller. Maximum of 256 concurrent link requests per TCP to a server class. Maximum of 256 concurrent PathSend requesters in a CPU.
Configuration Limits and Defaults Table C-2. Configuration Limits and Defaults (page 2 of 8) PXMCFG or PXMCOM Parameter Valid Values and Limits Default Value CHECK-DIRECTORY ON | OFF Suggested value is OFF for production, ON for development. ON CMON ON | OFF OFF CODE 0 through 65535 0 CODEAREALEN 0 through 2147483647 bytes Use SCUP (SCREEN COBOL Utility Program) or STATS TCP to determine this value.
Configuration Limits and Defaults Table C-2. Configuration Limits and Defaults (page 3 of 8) PXMCFG or PXMCOM Parameter Valid Values and Limits Default Value DUMP ON | OFF Suggested value is ON. OFF ECHO ON | OFF | CURRENT ON ERROR-ABORT ON | OFF ON EVENTFORMAT EVENTFORMAT Only text messages are generated. EXCLUSIVE ON | OFF OFF EXT 1 through 65535 No value is passed.
Configuration Limits and Defaults Table C-2. Configuration Limits and Defaults (page 4 of 8) PXMCFG or PXMCOM Parameter Valid Values and Limits Default Value LINKDEPTH 1 through 255 The value should be less than or equal to the value of MAXLINKS. If MAXLINKS is 0, use the LINKDEPTH default.
Configuration Limits and Defaults Table C-2. Configuration Limits and Defaults (page 5 of 8) PXMCFG or PXMCOM Parameter Valid Values and Limits Default Value MAXTERMDATA If NONSTOP set to 0: 0 through 2147483647 bytes If NONSTOP set to 1: 2804 through 2147483647 bytes 8000 MAXTMFRESTARTS -1 through 32767 5 MAXWEIGHTS 1 through 32768 32768 MODE ORDERLY | ABORT | IMMEDIATE ORDERLY NODE One through 15 alphanumeric and hyphen characters; the first character must be alphabetic.
Configuration Limits and Defaults Table C-2. Configuration Limits and Defaults (page 6 of 8) PXMCFG or PXMCOM Parameter Valid Values and Limits Default Value PROCESS For PATHMON name, a dollar sign ($) followed by one through five alphanumeric characters; the first character after the $ must be alphabetic.
Configuration Limits and Defaults Table C-2.
Configuration Limits and Defaults Table C-2.
Configuration Limits and Defaults Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 C -10
D Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment The following basic characteristics of a Compaq NonStop™ Pathway/XM environment make it different from a PATHMON environment: • • • • • • • • • • You configure a Pathway/XM environment offline, by preparing a source file and running the PXMCFG utility, before any PATHMON processes are started. This feature allows you to maintain and manage multiple configurations.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment • Because of Pathway/XM’s automatic load-balancing features, some object attributes have different meanings in the Pathway/XM environment. For example, in the Pathway/XM environment the TCP attribute MAXINPUTMSGS specifies the maximum number of unsolicited messages that can be queued per TERM object rather than per TCP.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-1 maps the underlying NonStopTM TS/MP and Compaq NonStop™ Pathway/iTS objects and object attributes to Pathway/XM objects and object attributes; a long dash (—) means the item does not apply. Table D-1.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-1.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-2 maps the PATHCOM commands to the corresponding PXMCOM and PXMCFG commands; a long dash (—) means the item does not apply. Table D-2.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-2.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-2.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-2. PATHCOM Commands Versus PXMCFG and PXMCOM Commands (page 4 of 6) PATHCOM Command Corresponding PXMCFG Statement Corresponding PXMCOM Command RESET TERM RESET TERM — — — RESUME SERVER RESUME TERM — RESUME TERM RUN PROGRAM — RUN PROGRAM — SET NODE — New statement SET PATHMON SET PATHMON — DUMP file-name not supported.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-2. PATHCOM Commands Versus PXMCFG and PXMCOM Commands (page 5 of 6) PATHCOM Command Corresponding PXMCFG Statement Corresponding PXMCOM Command STATS SERVER — STATS SERVER OUT parameter replaced by OUT command. COUNT and INTERVAL, parameters not supported. STATS TCP — STATS TCP OUT parameter replaced by OUT command. COUNT and INTERVAL parameters not supported.
Summary of Differences Between the Pathway/XM Environment and the PATHMON Environment Table D-2. PATHCOM Commands Versus PXMCFG and PXMCOM Commands (page 6 of 6) PATHCOM Command Corresponding PXMCFG Statement Corresponding PXMCOM Command — — SUSPEND SERVER New command SUSPEND TERM — SUSPEND TERM TCP parameter not supported. SWITCH PATHMON — — Command not supported SWITCH TCP — — Command not supported TELL TERM — TELL TERM TCP parameter not supported.
E Migrating Pathway Applications to the Pathway/XM Environment To migrate existing Pathway applications (managed by a PATHMON process, using the NonStopTM TS/MP and Compaq NonStop™ Pathway/iTS products without Compaq NonStop™ Pathway/XM) to the Pathway/XM environment, the Pathway/XM product includes an intelligent migration utility program called PXMCNVRT. This utility allows you to migrate your applications gradually, step by step.
Migrating Pathway Applications to the Pathway/XM Environment 5. Run the PXMCNVRT utility, using as input the output from BUILDCFG: RUN PXMCNVRT /IN PCFGSRC, OUT out-file/ where out-file is the disk file where you want your initial Pathway/XM configuration file to be placed. The output file from PXMCNVRT is a PXMCFG source file. In subsequent steps, you can use a text editor such as PS Text Edit (TEDIT) to edit the statements in this file. 6.
Migrating Pathway Applications to the Pathway/XM Environment 11. If desired, identify additional sets of system and CPU resources to fine-tune your application performance. Create additional NODE objects as follows: • • Edit your PXMCFG source file to define additional client and server NODE objects and to re-specify the NODE objects used by your PATHMON processes, TCPs, and server classes.
Migrating Pathway Applications to the Pathway/XM Environment Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 E- 4
F Example Configuration Source Files Configuration Example Overview This appendix contains three example configuration source files and an output file. The examples are for a vendor who provides a bank fraud detection service application and a customer who is a bank that is installing the vendor’s application: Vendor Source File This example configuration source file is prepared by the vendor.
Example Configuration Source Files Vendor Source File Example 4. Run PXMCFG on the customer’s new SuperCTL file to migrate online to the new configuration: pxmcfg /in cursfig, out egpxmout/ cursctl Vendor Source File Example This example configuration source file is prepared by the vendor (the Fraud Detection Service Company, in this example).
Vendor Source File Example Example Configuration Source Files comment RESET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET Define server class SC-FDS-HIST SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER comment TYPE DISTRIBUTED NONSTOP 0 NODE FDS-SERVER-NODE AUTORESTART 2 CMON OFF DEBUG OFF HIGHPIN ON PRI 130 MAXSERVERS 5 NUMSTATIC 1 OWNER 101,27 SECURITY "N" STARTUP "-S " TMF ON PARAM FIRST ON Need quotes because of the sem
Example Configuration Source Files SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER Vendor Source File Example STARTUP "PXMCTL FDS-SERVER-NODE" TMF ON NONSTOP 1 PARAM quo "quoted" PARAM unquo unquoted ADD SERVER SC-FDS-TRANS comment RESET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET Define server class SC-FDS-PATMAT SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER TYPE DISTRIBUTED NODE FDS-SERVE
Example Configuration Source Files Customer Source File (Import Example) Customer Source File (Import Example) This example configuration source file is prepared by the customer. It contains configuration statements for the customer’s Pathway/XM environment and includes statements for importing the server configurations from the vendor as part of the Fraud Detection Service application the customer is installing.
Customer Source File (Import Example) Example Configuration Source Files SET SET SET SET SET SET SET SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER NODE SERVER-NODE AUTORESTART 2 CMON ON HOMETERM $AHCO DEBUG OFF HIGHPIN ON PRI 199 MAXSERVERS 5 NUMSTATIC 1 OWNER 101,27 PROGRAM $DATAB.AHLCSV2.
Customer Source File (Import Example) Example Configuration Source Files set ADD ADD ADD ADD ADD ADD ADD term group g2029 TERM TERM TERM TERM TERM TERM TERM comment RESET ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD TERM-20 TERM-21 TERM-22 TERM-23 TERM-24 TERM-25 TERM-26 Specify no group TERM GROUP TERM TERM TERM TERM TERM TERM TERM TERM TERM TERM comment TERM-30 TERM-31 TERM-32 TERM-33 TERM-34 TERM-35 TERM-36 TERM-37 TERM-38 TERM-39 Add a TCP for the router to use RESET TCP SET TCP NODE SET TCP MAXWE
Example Configuration Source Files SET SERVER PARAM SET SERVER (PARAM Customer Source File (Import Example) FIRST ON LAST ON) comment Must enclose PARAM in quotes because of the comment semicolon. SET SERVER PARAM TIMEOFFSET "+0SC1;+"":00:00;" SET SERVER OUT $S.#S1PARAM SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER ASSIGN DD1, $DATA.DIC.DDL,SHARED ASSIGN DD2, $DATA2.XIC.DDL,BLOCK 243, CODE 27, EXT(2,22), SHARED HOMETERM $AHCO ASSIGN DD3.
Example Configuration Source Files Customer Source File (Import Example) comment Define server class SCDIR RESET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER TYPE DIRECT NODE SERVER-NODE AUTORESTART 0 HOMETERM $AHCO OUT =def DEBUG OFF HIGHPIN ON PRI 137 MAXSERVERS 5 NUMSTATIC 1 GROUP GRSCDIR PROCESS $AH
Customer New Source File (Online Migration Example) Example Configuration Source Files Customer New Source File (Online Migration Example) This example configuration source file is generated by the customer. It contains the new customer configuration (the configuration that contains the new fraud detection server configurations) to which the customer wants to migrate online from the currently existing configuration.
Customer New Source File (Online Migration Example) Example Configuration Source Files comment Define server class SC001 RESET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER TYPE DISTRIBUTED NONSTOP 0 NODE SERVER-NODE AUTORESTART 2 CMON ON HOMETERM $AHCO DEBUG OFF HIGHPIN ON PRI 130 MAXSERVERS 5 NUMSTATIC 1 OWNER 101,27 PROGRAM $DATA2.CODE.
Customer New Source File (Online Migration Example) Example Configuration Source Files ADD ADD ADD ADD set ADD ADD ADD ADD ADD ADD ADD TERM TERM TERM TERM term group g2029 TERM TERM TERM TERM TERM TERM TERM TERM-16 TERM-17 TERM-18 TERM-19 TERM-20 TERM-21 TERM-22 TERM-23 TERM-24 TERM-25 TERM-26 comment Specify no group RESET ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD TERM GROUP TERM TERM TERM TERM TERM TERM TERM TERM TERM TERM TERM-30 TERM-31 TERM-32 TERM-33 TERM-34 TERM-35 TERM-36 TERM-37 TERM-38 TERM-3
Customer New Source File (Online Migration Example) Example Configuration Source Files SET ROUTER CONNECTIONS 5 ADD ROUTER AHRTR SET SERVER PARAM SET SERVER (PARAM FIRST ON LAST ON) comment Must enclose PARAM in quotes because of the semicolon. SET SERVER PARAM TIMEOFFSET "+0SC1;+"":00:00;" SET SERVER OUT $S.#S2PARAM SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER ASSIGN DD1, $DATA.DIC.DDL,SHARED ASSIGN DD2, $DATA2.XIC.
Example Configuration Source Files SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER Output File Example OWNER 101,27 PROGRAM $DATAB.AHLCSV2.TRAVSERV SECURITY "N" STARTUP "-S" TMF OFF ADD SERVER SCREP comment Add service fdsSCTL RESET SERVICE SET SERVICE VARIABLE FILE:GOOD=goodnull SET SERVICE FILE fdssctl SET SERVICE NODE SERVER-NODE SET SERVICE GROUP cuGrp17 SET SERVICE VARIABLE FILE:AbC=$V.SV.FN SET SERVICE VARIABLE FILE:vnd1out=CU1OUT SET SERVICE VARIABLE FILE:NONE=SV.
Output from Vendor Source File Example Configuration Source Files 0 33 0 34 0 35 0 36 0 37 0 38 0 39 0 40 0 41 0 42 0 43 0 44 0 45 0 46 0 47 0 48 0 49 0 50 0 51 0 52 0 53 0 54 0 55 0 56 0 57 0 58 0 59 0 60 0 61 0 62 0 63 0 64 0 65 0 66 0 67 0 68 0 69 0 70 0 71 0 72 0 73 0 74 0 75 0 76 0 77 EXT(2,2) 0 78 0 79 0 80 0 81 0 82 0 83 0 84 0 85 0 86 0 87 0 88 0 89 0 90 0 91 0 92 0 93 0 94 0 95 0 96 0 97 0 98 0 99 0 100 0 101 ADD NODE FDS-SERVER-NODE SET NODE ROLE CLIENT ADD NODE CLIENT-NODE comment Even though
Output from Vendor Source File Example Configuration Source Files 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 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 SET SERVER PROGRAM
Output from Customer Source File (Import Example) Example Configuration Source Files Exported Server Classes: SC: SC-FDS-HIST SC: SC-FDS-TRANS SC: SC-FDS-PATMAT PATHWAY/XM CONFIGURATION SUMMARY Total Total Total Total Total Total Total Total Total Total Systems NODE Objects PATHMON Objects Server Classes TCP Templates TCP Objects PROGRAM Objects ROUTER Objects TERM Objects PLAN Objects = = = = = = = = = = 0 0 0 3 0 0 0 0 0 0 Output from Customer Source File (Import Example) PXMCFG - T0223D46 - (31MAR2
Example Configuration Source Files 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 0 0 0 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 SET SET SET ADD NODE NODE NODE NODE Output from Customer Source File (Import Example) HOMETERM $AHCX DEFAULT $TSERV2.
Example Configuration Source Files 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 0 0 0 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 SET SET SET SET ADD ADD ADD ADD ADD ADD ADD ADD ADD set ADD ADD ADD ADD ADD AD
Example Configuration Source Files Output from Customer Source File (Import Example) 0 175 0 176 0 177 comment =================== ROUTER ======================= 0 178 0 179 RESET ROUTER 0 180 0 181 comment Setthe four required attributes. 0 182 0 183 SET ROUTER PROTOCOL HTTP 0 184 SET ROUTER TCP GOODNAM 0 185 SET ROUTER PORT 42 0 186 SET ROUTER INITIAL myprog 0 187 0 188 0 189 comment Set other attributes..
Output from Customer Source File (Import Example) Example Configuration Source Files 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 0 0 0 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 ADD SERVER SC00198, PRI 198
Example Configuration Source Files 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 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 IMPORTING: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> IMPORTING: >> >> >> IMPORTING: >> >> >> Output from Customer Source File (Import Example) comment Define server class SCREP RESET SERVER SET SERVER TYPE REPLICATED SET SERVER NODE SE
Example Configuration Source Files 0 Output from Customer Source File (Import Example) 339 Processing configuration distribution assignments ConfigDB \SVLDEV.$BOOMER.AHPXMEG.CUSCTL generated.
Output from Customer Source File (Import Example) Example Configuration Source Files TERM: TERM-29 TCP: TCP0024 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: TERM-30 TCP: TCP0025 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-1 TCP: TCP0026 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-2 TCP: TCP0027 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-3 TCP: TCP0028 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-4 TCP: TCP0029 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZER
Output from New Customer Source File (Online Migration Example) Example Configuration Source Files Output from New Customer Source File (Online Migration Example) PXMCFG - T0223D46 - (31MAR2000) - 27 April 2000, 17:02:19 Copyright 2000 Compaq Computer Corporation 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 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
Output from New Customer Source File (Online Migration Example) Example Configuration Source Files 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 0 0 0 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 SET SET SET SET SET SET SET SET SET SET SET SET SET
Output from New Customer Source File (Online Migration Example) Example Configuration Source Files 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 0 0 0 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 ADD ADD ADD A
Output from New Customer Source File (Online Migration Example) Example Configuration Source Files 0 193 0 194 0 195 0 196 0 197 0 198 0 199 0 200 0 201 0 202 0 203 0 204 0 205 0 206 0 207 0 208 0 209 0 210 0 211 0 212 EXT(2,22), 0 213 0 214 0 215 0 216 0 217 0 218 0 219 0 220 0 221 0 222 0 223 0 224 0 225 0 226 0 227 0 228 0 229 0 230 0 231 0 232 0 233 0 234 0 235 0 236 0 237 0 238 0 239 0 240 0 241 0 242 0 243 0 244 0 245 0 246 0 247 0 248 0 249 0 250 0 251 0 252 0 253 0 254 0 255 0 256 0 257 SET SET S
Output from New Customer Source File (Online Migration Example) Example Configuration Source Files 0 258 0 259 0 260 0 261 0 262 0 263 0 264 0 265 0 266 0 267 0 268 0 269 0 270 0 271 0 272 0 273 0 274 0 275 0 276 0 277 0 278 0 279 0 280 0 281 0 282 0 283 0 284 0 285 0 286 0 287 0 288 0 289 0 290 IMPORTING: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> IMPORTING: >> >> >> IMPORTING: >> >> >> 0 291 SET SET SET SET SET SET SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER SE
Example Configuration Source Files Output from New Customer Source File (Online Migration Example) DETAILED PATHWAY/XM CONFIGURATION SUMMARY System: \WEST Client Node: CLIENT-NODE Cpus = (3:99, 4:1) PATHMON: PM0000 TCP: TCP0039 (TCP Template: TCP-1 on Node: PROGRAM: PROG-1 TCP: TCP0000 (TCP Template: TCP-1 on Node: TERM: TERM-7 TCP: TCP0001 (TCP Template: TCP-1 on Node: TERM: TERM-8 TCP: TCP0002 (TCP Template: TCP-1 on Node: TERM: TERM-9 TCP: TCP0003 (TCP Template: TCP-1 on Node: TERM: TERM-10 TCP: TCP000
Example Configuration Source Files Output from New Customer Source File (Online Migration Example) TERM: ZERM-4 TCP: TCP0028 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-5 TCP: TCP0029 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-6 TCP: TCP0030 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-7 TCP: TCP0031 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-8 TCP: TCP0032 (TCP Template: TCP-1 on Node: CLIENT-NODE) TERM: ZERM-9 TCP: TCP0033 (TCP Template: TCP-1 on Node: CLIENT-NOD
Example Configuration Source Files Output from New Customer Source File (Online Migration Example) Type: TCP Action: Update Objects: TCP0000 TCP0001 TCP0002 TCP0003 TCP0004 TCP0005 TCP0006 TCP0007 TCP0008 TCP0009 TCP0010 TCP0011 TCP0012 TCP0013 TCP0014 TCP0015 TCP0016 TCP0017 TCP0018 TCP0019 TCP0020 TCP0021 TCP0022 TCP0023 TCP0024 TCP0025 TCP0026 TCP0027 TCP0028 TCP0029 TCP0030 TCP0031 TCP0032 TCP0033 TCP0034 TCP0035 TCP0036 TCP0037 TCP0038 TCP0039 Plan: 25_UPDATE_PROGRAMS Type: PROG Action: Update Object
Output from New Customer Source File (Online Migration Example) Example Configuration Source Files SC00198 PATHWAY/XM CONFIGURATION SUMMARY Total Total Total Total Total Total Total Total Total Total Systems NODE Objects PATHMON Objects Server Classes TCP Templates TCP Objects PROGRAM Objects ROUTER Objects TERM Objects PLAN Objects = = = = = = = = = = 1 2 1 7 2 40 1 1 43 10 1 Warning while processing configuration file Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 F- 33
Example Configuration Source Files Output from New Customer Source File (Online Migration Example) Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 F- 34
Index A ABORT option, for MODE parameter 7-32, 7-34, 11-92 ABORT TERM command 8-5, 11-6/11-7 ACCEPT display field 11-86 ACCEPT statement 10-76 ADD command ADD NODE 4-15/4-21, 10-7 ADD PROGRAM 5-12/5-14, 10-8 ADD ROUTER 10-9 ADD SERVER 10-10 ADD SERVICE 10-11 ADD TCP 10-12 ADD TERM 10-13 comparison to PATHCOM ADD D-5 guidelines for 4-7 relationship to SET command 4-8 AGGREGATE option, for STATUS parameter 11-93 ALL FIELDS USED error 10-38, 10-77 ALTER command not supported D-5 Analyst configuration tool 3-12
C Index C Caching, screen 5-20 CANCEL procedure, Guardian 10-80 Cannot communicate with $CMON... (message 6003) 13-6 Cannot delete pb_crew_member (message 6578) 13-24 Cannot open SuperCTL file (message 6532) 13-20 Cannot read PXCCSTM (message 6505) 13-13 Cannot send startup message to PB... (message 6577) 13-24 CANNOT UPDATE ACTIVE PATHMONS...
D Index Configuration files (continued) status of 11-76/11-77 SuperCTL and PATHCTL 7-11/7-13 using attributes defined in 4-12 Configured terminal (TERM) objects See TERM objects Configuring automated 2-1 configured object types 4-2/4-4 global parameters 4-14/4-15 global parameters and objects 4-1/4-22 global resources 4-15/4-21 migrating online 7-19 multiple command files 4-7 new features D-2 object naming guidelines 4-13 overview of tasks 3-1/3-3 PATHMON processes 4-21/4-22 reconfiguring online 7-21/7-23
D Index Debugging INSPECT TERM command 11-39 specifying terminal for TCP 10-68 SUSPEND SERVER command 11-101 SUSPEND TERM command 11-102 DEFAULT attribute guidelines 4-17 SET NODE command 10-27 Default Guardian file names, VOLUME command 11-109 Default settings, ENV command 11-23 Default values for SERVER SECURITY attribute 7-29 DEFINE attribute CONTROL SERVER command 11-15 SET SERVER command 10-51 DEFINE definitions using for command file names 7-6 DEFINE PROCEDURE ERROR.
E Index DUMP attribute (continued) CONTROL TCP command 11-19 SET PATHMON command 10-31 SET TCP command 10-66 DUMPMEMORY attribute not supported D-3 Dumps enabling or disabling online 7-23 for PATHMON processes 4-22, 5-6 for TCPs 7-38 Dynamic server processes relationship to MAXSERVERS and NUMSTATIC 10-55 starting 9-3 using DELETEDELAY attribute 10-51 E ECHO attribute SET PROGRAM command 10-39 SET TERM command 10-78 ENABLE ROUTER command 10-15 Enabling TCP dumping 8-6 END-TRANS in WAIT display field 11-88
F Index External objects and processes LINKMON process 7-24 PATHMON processes 10-69, 10-71 TCPs, new features D-2 TCPs, specifying maximum 10-32 F Failed to configure (message 6201) 13-9 Failed to open $RECEIVE (message 6582) 13-25 Failure posting a READUPDATE... (message 6585) 13-26 Failure reading NODE... (message 6520) 13-16 Failure reading PATHMON... (message 6521) 13-17 Failure reading PROGRAM... (message 6522) 13-17 Failure reading SERVER... (message 6523) 13-17 Failure reading TCP...
H Index GROUP attribute (continued) SET ROUTER command 10-45 SET SERVER command 6-5, 10-51 SET SERVICE command 10-61 SET TERM command 5-12, 10-79 START SERVER command 11-59 START TCP command 11-60 START TERM command 11-62 STATS SERVER command 11-67 STATUS SERVER command 11-81 STATUS TCP command 11-85 STATUS TERM command 11-89 STOP SERVER command 11-96 STOP TCP command 11-97 STOP TERM command 11-99 SUSPEND SERVER command 11-101 SUSPEND TERM command 11-102 TELL TERM command 11-104 THAW SERVER command 11-106
L Index INCLUDE command 4-7, 10-17 INFO command comparison to PATHCOM INFO D-6 INFO GROUP 11-26 INFO NODE 7-17, 11-27 INFO PATHMON 7-17, 11-28 INFO PATHWAY 7-17, 7-29, 11-29 INFO PLAN 11-30 INFO PROGRAM 11-31 INFO ROUTER 11-32 INFO SERVER 9-7, 11-33 INFO TCP 11-34/11-35 INFO TELL 8-12, 11-36 INFO TERM 11-37/11-38 INFO display field 11-73, 11-82, 11-86, 11-90 INITIAL attribute SET PROGRAM command 5-13, 10-37 SET ROUTER command 10-45 SET TERM command 5-10, 10-75 START TERM command 11-62 INPUT file creation
M Index Link Control Service (LCS) processes (continued) queue-management algorithm 9-11 transaction queuing 3-10 LINK COUNT display field 11-84 Link requests when starting 9-4 LINKDEPTH attribute 10-53 LINKDEPTH EXCEEDS MAXLINKS (message 6814) 12-4 LINKER display field 11-84 LINKMON processes and CPU halts 7-27 authorization checks performed by 7-28 communicating with the PATHMON process 7-24 controlling Pathsend access to servers 7-28 definition of 3-9, 7-3, 7-24 displaying information about 7-29, 7-30/
M Index Managing displaying information 7-16/7-19, 8-7/8-10, ??/8-12, 9-6/9-8 exception conditions 8-13 monitoring Pathsend environment 7-23/7-31 overview 3-1/3-3 Pathway/XM environment 7-1/7-40 PXMCOM commands 11-1/11-109 queue-management algorithm 9-11 requesters 8-1/8-13 servers 9-1/9-11 servers, a scenario 9-9 shutting down Pathway/XM 7-32/7-36 stopping SERVER objects 9-10/9-11 MAXASSIGNS attribute, guidelines 4-14 MAXEXTERNALTCPS attribute 10-32 MAXINPUTMSGLEN attribute 10-69 MAXINPUTMSGS attribute g
N Index Messages, status and error 7-8/7-9, 13-1/13-2 Messages, tell deleting 11-22 displaying 11-104 managing 8-12 Messages, unsolicited length, setting (MAXINPUTMSGLEN attribute) 10-69 protocol, specifying (IOPROTOCOL attribute) 10-39, 10-80 queue, setting (MAXINPUTMSGS attribute) 5-5, 10-69 UMP I/O bytes allocated by TCP 10-72 Migrating to new configuration 2-3 Migration configuring for 4-19 example configuration source file F-10 utility (PXMCNVRT) 2-3 MISSING SUPERCTL FILE NAME (message 6815) 12-4 MOD
O Index NonStop servers 6-5 NonStop TS/MP, using existing 2-4 NOWAIT parameter PROGRAM objects 8-4 PXMCFG startup command 10-3 PXMCOM startup command 11-4 RUN PROGRAM command 11-54 NUMBER OF PREDEFINED SERVERS... (message 6836) 12-10 NUMBER OF PREDEFINED SERVERS... (message 6837) 12-10 NUMBER OF TCPS CALCULATED... (message 6846) 12-12 NUMBER OF TERMS PER TCP... (message 6852) 12-14 NUMBER OF TERMS...
P Index P PAID display field 11-76 PARAM parameter CONTROL SERVER command 11-17 guidelines 6-10 SET SERVER command 10-56 Parameters, limits for C-1/C-9 PATHCOM interface comparison to Pathway/XM commands D-5/D-10 displaying underlying commands to PATHMON 7-7 MAXPATHCOMS attribute 10-33 warning message 7-3 PATHCOM processes, functions of 3-7 PATHCONF files, collecting for problem diagnosis 7-38 PATHCTL configuration files 3-7, 7-12 PATHCTL display field 11-76 PATHMON configuration files See PATHCTL configu
P Index PATHWAY object (continued) INFO command 11-29 new features D-3 SET command 10-32/10-35 START command 11-55 STATUS command 11-78 STOP command 11-92/11-94 Pathway was not shut down properly...
P Index PROCESSES attribute 11-81 PROCESSHANDLE_TO_STRING_ returned error (message 6584) 13-25 Processor halts 7-27 PROCESSTYPE attribute not supported D-3 PROCESS_GETINFO_ returned (message 6511) 13-15 Product version, VPROC command 7-37 Production environment, ensuring availability of 4-4 PROGRAM attribute CONTROL SERVER command 11-17 SET SERVER command 10-57 SET TCP command 10-72 PROGRAM ID name, specifying 10-48 PROGRAM objects ADD command 10-8 as templates for device types 5-14 configuring 5-9, 5-13/
Q Index PXMCOM management process (continued) starting 7-4, 11-3/11-5 using interactively 7-5 using noninteractively mode 7-6 Q Q overflow (message 6012) 13-8 Q size full (message 6011) 13-8 Q size high (message 6010) 13-8 Queue-management algorithm 9-11 QUIET option, for STATUS parameter 11-93 R RAM organization for terminals 5-21 Read error on IN (message 6506) 13-13 Read error on OBEY file (message 6504) 13-13 READY in WAIT display field 11-87 REC file creation attribute 10-49 Received an error on $R
S Index Response time See also STATS command starting SERVER objects before TCPs 7-15 Restarting Pathway/XM environments 7-12/7-14 RESTART-COUNTER special register 11-25, 11-50, 11-106 RESUME command comparison to PATHCOM RESUME D-8 RESUME SERVER 11-48 RESUME TERM 11-49/11-50 ROLE attribute guidelines 4-15 SET NODE command 10-28 Rolling configurations 2-3, 4-23, 7-19 example source file F-10 ROUTER objects ADD command 10-9 configuring 5-7 definition of 4-3 displaying information 8-7 ENABLE command 10-15 e
S Index Security caution on security risk 10-35 network conditions for Pathsend access 7-28 Pathsend access to servers 7-28 SECURITY attribute guidelines 4-14 SET PATHWAY command 4-14, 10-35 SET PROGRAM command 5-15, 10-42 SET SERVER command 10-57 SEND message verb, specifying maximum 10-69 SEND operations and links 9-4 timeouts 10-58 SEND statements 5-19, 11-25 Send to object... (message 6508) 13-14 SERVBUF in WAIT display field 11-87 SERVER ATTRIBUTE AND TYPE...
S Index SERVER objects (continued) SUSPEND command 11-101 THAW command 11-106 types of classes 3-9 Server processes assigning names (PROCESS attribute) 6-10, 10-57 automatic load balancing 2-2, 3-10/3-12 displaying information about 9-7 displaying statistics 9-8 dynamic 10-51 global maximum C-2 home terminal (HOMETERM attribute) 10-27 input file (IN parameter) 10-53 links to 9-4 maximum TCP links (MAXSERVERPROCESSES attribute) 5-6, 10-70 multithreaded (LINKDEPTH attribute) 10-53 object file, specifying (P
S Index START command (continued) START SERVER 9-1, 11-59 START TCP 8-1, 11-60/11-61 START TERM 8-2, 11-62/11-63 START PATHWAY has failed...
T Index STOPMODE register 7-33 Stopping See also STOP command ROUTER objects 8-5 TCP and TERM objects 8-4 TERM objects 8-5 STOP-MODE special register 11-24 STRING TOO LONG (message 6825) 12-7 Subtype 30 processes 11-54 SUPERCTL CLOSE FAILED... (message 6859) 12-16 SuperCTL configuration file assigning file name 10-3 how built 4-5 information stored 7-12 opening 7-11 overview 3-1, 3-6, 4-5 SUPERCTL CREATE FAILED... (message 6857) 12-15 SUPERCTL ENTITY INSERT FAILED...
T Index TCP processes (continued) file name (PROGRAM attribute) 10-72 frozen server class, sending to 11-25 functions of 3-8 INFO command 11-34/11-35 links, idle (DELETEDELAY attribute) 10-51 links, new (CREATEDELAY attribute) 10-50 managing exception conditions 8-13 pool space, allocating (TERMPOOL attribute) 10-73 REFRESH-CODE command 11-46/11-47 START command 11-60/11-61 starting 7-15, 8-1 STATS command 11-69/11-70 STATUS command 11-85/11-88 STOP command 11-97/11-98 stopping 8-4 TMF restarts (MAXTMFRES
T Index TERM objects (continued) RESET command 10-25 restart attempts (AUTORESTART attribute) 10-76 RESUME command 11-49/11-50 SET command 10-75/10-83 setting and displaying statistics 8-10 START command 11-62/11-63 starting 7-15, 8-2 starting temporary objects 8-3 STATS command 11-71/11-72 STATUS command 11-89/11-91 STOP command 11-99/11-100 stopping 8-5 SUSPEND command 11-102/11-103 TELL command 11-104/11-105 TERMBUF attribute 10-73 TERMBUF in WAIT display field 11-87 TERMINAL IS clause 10-82 Terminals
U Index TMF attribute guidelines 5-16/5-20, 6-9 SET PROGRAM command 10-42 SET SERVER command 10-58 SET TERM command 10-81 TMF (Transaction Management Facility) error recovery 6-9 frozen server class, relation to 11-25 precautions for using parameters 5-20 restarting after freeze 11-106 specifying maximum TCP restarts 10-34 TERM activity, resuming 11-50 TOO MANY ASSIGN ENTRIES (message 6840) 12-11 TOO MANY DEFINE ENTRIES (message 6841) 12-11 TOO MANY NESTED...
W Index Variable file names configuring for export 6-15 specifying for import 6-13 VERBOSE command 7-7, 11-108 VOLUME attribute guidelines 6-10 SET SERVER command 10-59 VOLUME command 11-109 comparison to PATHCOM CMDVOL D-10 VPROC command, for product version 7-37 VPROC, for product version 7-31 $SYSTEM.SYSTEM.
Index Special Characters Compaq NonStop™ Pathway/XM System Management Manual— 426761-001 Index -26
