NonStop TS/MP System Management Manual Abstract This manual describes the interactive management interface to the HP NonStop™ TS/MP; it is intended for system managers and operators. It provides guidelines for configuring and controlling a TS/MP transaction processing system and its objects, and for monitoring the status and performance of objects controlled by PATHMON in a Pathway environment.
Document History Part Number Product Version Published 120039 NonStop TS/MP D42 August 1996 135027 NonStop TS/MP D42 July 1997 541819-001 NonStop TS/MP D42 February 2006
NonStop TS/MP System Management Manual Glossary Index What’s New in This Manual ix Manual Information ix New and Changed Information Examples Figures Tables ix About This Manual xiii Purpose of This Manual xiii Who Should Read This Manual xiii How This Manual Is Organized xiv Related Reading xv Other Manuals in the Manual Set xvii Other Manuals of Interest xvii Notation Conventions xviii 1.
1. Introduction to NonStop TS/MP System Management (continued) Contents 1. Introduction to NonStop TS/MP System Management (continued) System Management Tools 1-17 PATHCOM Interactive Interface 1-18 Management Programming Interface 1-18 Other System Management Tools 1-20 Summary of PATHCOM Commands 1-21 2.
3. Configuring Objects in a PATHMON Environment (continued) Contents 3. Configuring Objects in a PATHMON Environment (continued) Defining Attributes for Guardian and OSS Servers 3-17 Additional Considerations 3-22 Setting Process Priority 3-23 Configuring Links for Optimum Performance 3-23 Links and Link Attributes 3-24 Understanding the Effects of Link Configuration 3-26 Steps to Optimum Link Configuration 3-28 4.
5. Maintaining a PATHMON Environment (continued) Contents 5. Maintaining a PATHMON Environment (continued) PATHCOM-Specific Problems 5-30 Server-Specific Problems 5-30 Recovering from PATHMON Failure 5-31 Keep Development and Production Separate 5-31 Maintaining Associative Server Processes 5-32 Migrating Your Environment to a Different System 5-33 6.
9. PATHMON and PATHCOM Startup Commands Contents 9. PATHMON and PATHCOM Startup Commands Starting the PATHMON Process Starting PATHCOM 9-3 9-1 10. PATHCOM Operation Commands CMDCWD Command 10-2 CMDVOL Command 10-3 ERRORS Command 10-5 EXIT Command 10-6 FC Command 10-6 HELP Command 10-8 OBEY Command 10-10 OBEYVOL Command 10-11 OPEN Command 10-12 RESET CMDCWD Command SHOW Command 10-13 10-13 11.
12. SERVER Commands (continued) Contents 12. SERVER Commands (continued) FREEZE SERVER Command 12-5 INFO SERVER Command 12-7 RESET SERVER Command 12-10 SET SERVER Command 12-12 Server Class DEFINEs 12-31 SHOW SERVER Command 12-33 START SERVER Command 12-35 Examples 12-36 STATS SERVER Command 12-37 STATUS SERVER Command 12-39 STOP SERVER Command 12-45 THAW SERVER Command 12-46 13.
C. Configuration Limits and Defaults Contents C. Configuration Limits and Defaults D. Migration Information Interprocess Communication Issues D-1 Application Conversion Guidelines D-2 E. Setting TMF Parameters SET SERVER Command and TMF E-1 Precautions for Using TMF Parameters E-1 Glossary Index Examples Example 2-1. Example 2-2. Example 5-1. Example 5-2. Example 5-3. Example 5-4. Example 5-5. Example 5-6. Example 5-7. Example 5-8. Example 5-9. Example 5-10. Example 5-11. Example 5-12. Example 5-13.
Examples (continued) Contents Examples (continued) Example 7-5. Example 11-1. Example 11-2. Example 11-3. Example 11-4. Example 11-5. Example 12-1.
Tables (continued) Contents Tables (continued) Table 7-2. Table 7-3. Table 7-4. Table 8-1. Table 8-2. Table 10-1. Table C-1. Table C-2. Table D-1.
Contents NonStop TS/MP System Management Manual—541819-001 x
What’s New in This Manual Manual Information NonStop TS/MP System Management Manual Abstract This manual describes the interactive management interface to the HP NonStop™ TS/MP; it is intended for system managers and operators. It provides guidelines for configuring and controlling a TS/MP transaction processing system and its objects, and for monitoring the status and performance of objects controlled by PATHMON in a Pathway environment.
What’s New in This Manual ° Changes in the G06.27 Manual Changed the error message, 1051, on page 13-16 Changes in the G06.27 Manual This is the first edition of the TS/MP System Management Manual. This manual replaces the TS/MP portions of both the NonStop TS/MP and Pathway System Management Guide and the NonStop TS/MP and Pathway Management Reference Manual.
What’s New in This Manual Enhancements to the Manual PATHCOM configuration commands to specify the default node to be the node where the PATHMON process is currently running. Note. Some attributes in existing configurations might have names tied to specific nodes and might, therefore, require careful configuration or manual changes after switching nodes. • The INFO commands have been enhanced to display \* for node-independent attributes.
What’s New in This Manual Enhancements to the Manual NonStop TS/MP System Management Manual—541819-001 xii
About This Manual This manual provides guidelines and examples for configuring and managing the D42.00 RVU of TS/MP, which runs on HP NonStop K-series servers on D42.00 and all subsequent D-series RVUs. This manual is one of a set of manuals that describes the TS/MP and Pathway/iTS. The contents of these two products are as follows: • • NonStop TS/MP: This product consists of the PATHMON process, the LINKMON process, the PATHCOM process and interface, and the Pathsend procedure calls.
How This Manual Is Organized About This Manual The task-oriented parts of this manual are also intended for individuals writing programs to access server classes in a PATHMON environment programmatically. Such programmers also need the reference information in the TS/MP Management Programming Manual, and, if they are using Pathway/iTS, the Pathway/iTS Management Programming Manual. How This Manual Is Organized The first section of this manual is an overview of Pathway system management.
Related Reading About This Manual Section Description Section 10, PATHCOM Operation Commands Gives the commands for controlling and operating PATHCOM. Section 11, PATHMON Environment Control Commands Describes the PATHCOM commands that control the PATHMON process and the PATHMON environment as a whole. Section 12, SERVER Commands Gives the PATHCOM commands for configuring and controlling server objects.
Related Reading About This Manual Manual Description Pathway/iTS System Management Manual Provides instructions and guidelines for configuring and controlling the Pathway/iTS objects in a PATHMON environment and for monitoring the status and performance of those objects. The Pathway/iTS objects are those that operate under the run-time portions of Pathway/iTS (the terminal control process (TCP) and SCREEN COBOL runtime environment).
Other Manuals in the Manual Set About This Manual For information about other NonStop software products associated with Pathway transaction processing environments, see: Manual Description Introduction to NonStop Transaction Processing Describes the environment, components, and benefits of HP transaction processing products, including TS/MP, Pathway/iTS, and related products such as TMF and the NonStop TUXEDO transaction processing system.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
Notation for Management Programming Interfaces About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING.
1 Introduction to NonStop TS/MP System Management This section briefly describes the objects and processes in a Pathway online transaction processing (OLTP) environment. This section also introduces the tasks you perform to manage a PATHMON environment, as well as applicable tools and commands. Depending on your hardware and software configuration, a Pathway environment includes one of these: • • The NonStop TS/MP product Both the NonStop TS/MP and Pathway/iTS products Note.
Introduction to NonStop TS/MP System Management Objects and Processes Provided by Pathway/iTS Pathsend requesters. (Under Pathway/iTS, the TCP is the link manager for SCREEN COBOL requesters.) Objects and Processes Provided by Pathway/iTS These elements of a Pathway environment are provided by the Pathway/iTS product. Information about configuring and managing these items is covered in the Pathway/iTS System Management Manual.
Introduction to NonStop TS/MP System Management Pathway Environment Configurations Figure 1-1.
Introduction to NonStop TS/MP System Management Pathway Environment Configurations Figure 1-2. NonStop TS/MP Application With Guardian and OSS Servers OSS Operating Environment Client Workstations SERVER (Server Class) Server Processes Remote System Pathsend Requester Management Application Process Application Database LINKMON PATHMON Environment SERVER (Server Class) Command Terminal PATHCOM PATHMON Server Processes Guardian Operating Environment VST002.
Introduction to NonStop TS/MP System Management Distributing a Pathway or PATHMON Environment Distributing a Pathway or PATHMON Environment Depending on the requirements of your application, you might distribute a Pathway or PATHMON environment over several processor in a single NonStop system or among several NonStop systems. One way to optimize response time for your business transactions might be to distribute your application’s workload across more than one processor in a NonStop system.
Introduction to NonStop TS/MP System Management Distributing a Pathway or PATHMON Environment Figure 1-3. PATHMON-Controlled Objects Distributed Over Two CPUs Screen Program Library User Workstations User Workstations CPU 0 CPU 1 TCP TERMs TCP TERMs PATHMON Server Class A Server Processes Server Class B Server Class A Server Processes Server Processes Server Class B Server Processes PATHCOM Database Command Terminal VST003.
Introduction to NonStop TS/MP System Management Distributing a Pathway or PATHMON Environment Figure 1-4. NonStop TS/MP Application Distributed Over Two Nodes \NODE A PATHCOM Batch Pathsend Requests Command Terminal Batch Control File PATHCOM 1 Server Class LINKMON List of Accounts Server Processes \NODE B PATHCOM 2 Database Server Class Server Class Server Processes Server Processes VST004.
Introduction to NonStop TS/MP System Management NonStop TS/MP Objects and Processes NonStop TS/MP Objects and Processes This subsection contains additional detail on the transaction services objects and processes provided by the NonStop TS/MP product. Information on defining and managing these items is provided in this manual. PATHMON Object The PATHMON object represents the PATHMON process. The PATHMON process and the objects it controls make up the PATHMON environment.
Introduction to NonStop TS/MP System Management PATHCOM Processes affect the PATHWAY object, see Starting and Stopping a PATHMON Environment on page 2-1. PATHCOM Processes You can use PATHCOM at a command terminal to communicate interactively with the PATHMON process. Other users use PATHCOM at application terminals to start and run Pathway applications. Multiple PATHCOM processes can communicate with a single PATHMON process concurrently, each supporting a particular user.
Introduction to NonStop TS/MP System Management Transaction Sources management functions for Pathsend requesters in the way that the TCP and the PATHMON process provide those functions for SCREEN COBOL requesters. Note. Although LINKMON processes are visible to the PATHMON process, they are not entities controlled or managed by the PATHMON process. For more information about the LINKMON process and Pathsend requesters, see Section 6, Managing the Pathsend Environment.
Introduction to NonStop TS/MP System Management Transaction Sources Figure 1-5. Transaction Sources RSC Personal Computer LINKMON Pathsend Requesters Workstation GDSX Point-of-Sale Terminal PATHCOM PATHCOM Environment PATHMON Server Class Server Processes IDS TCP Automated Teller Machine GDSX Any I/O device Database Application Terminal VST005.
Introduction to NonStop TS/MP System Management Personal Computers and Workstations Personal Computers and Workstations Personal computers (PCs) and workstations can access the PATHMON environment using the RSC product. RSC enables client-server computing by supporting a variety of hardware and software configurations and communications protocols for PCs and workstations.
Introduction to NonStop TS/MP System Management Unsupported or Special-Function I/O Devices The application interface to SNAX/HLS requires little detailed knowledge of SNAX or SNA. For more information about the SNAX/HLS product, see the SNAX/HLS Configuration and Control Manual. Unsupported or Special-Function I/O Devices Requests from unsupported or special-function I/O devices can be handled by the HP Extended General Device Support (GDSX) product.
Introduction to NonStop TS/MP System Management System Management Tasks Figure 1-6. Requester Access to Server Classes Tandem System \LND PATHMON Controlled Objects Server Class X $PMB Server Pathsend Requesters Server Class Y Server Pathsend Requesters Database $L01 $L01 Database Server Class Z Server Database VST006.
Introduction to NonStop TS/MP System Management System Management Tasks Figure 1-7.
Introduction to NonStop TS/MP System Management • System Management Tasks Start the PATHMON environment by using the START PATHWAY command. Use the cold start option to start the environment for the first time. Use the cool start option to start the environment using an existing configuration. 3. Configure the PATHMON-controlled objects: that is, the set of objects controlled by the PATHMON process.
Introduction to NonStop TS/MP System Management System Management Tools For complete information about the PATHCOM commands that configure and control the PATHMON environment and PATHMON-controlled objects, including syntax, usage rules, and error messages, see Sections 8 through 16. For a summary of these commands, see Appendix A, Syntax Summary.
Introduction to NonStop TS/MP System Management PATHCOM Interactive Interface repetitive your system management tasks, the more advantageous it is to use a management programming interface. Your choice might also depend on the availability of resources to develop a management application, which is a sophisticated programming assignment, or on the availability of other products, such as NonStop NET/MASTER.
Introduction to NonStop TS/MP System Management Management Programming Interface As shown in Figure 1-9, a management application in the operations environment uses the management programming interface to monitor and control objects in the PATHMON environment. The management application sends commands and inquiries to processes in the PATHMON environment through the management programming interface. The processes send responses or event messages to the management application using the same interface.
Introduction to NonStop TS/MP System Management • Other System Management Tools Subsystem environment The subsystem environment includes the PATHMON process and its objects. The Transaction Management Facility (TMF), which provides transaction processing protection, also resides in this environment. For more information about the Distributed Systems Management set of products, see the Introduction to Distributed Systems Management.
Introduction to NonStop TS/MP System Management • Summary of PATHCOM Commands The Measure product enables you to balance and tune NonStop systems. Using the Measure product, you can configure measurements, collect performance data, display and plot data, and so on. For more information about using Measure, see the Measure User’s Guide and the Measure Reference Manual. • The HP Tandem Performance Data Collector (TPDC) is a host-based performance collection and relationship product.
Introduction to NonStop TS/MP System Management • • • • • Summary of PATHCOM Commands STATUS command displays the status of an object (whether it is running or stopped, for example). STATS command displays resource usage and system performance statistics. ALTER command changes the attributes of a previously defined object. STOP command stops individual objects, for example, SERVER objects. SHUTDOWN2 command stops all PATHMON-controlled objects.
2 Starting and Stopping a PATHMON Environment Steps to Starting and Configuring a PATHMON Environment This section describes how to start, restart, and shut down a PATHMON environment. Before you actually start a PATHMON environment, you start the PATHMON process. Multiple PATHMON environments can run on a given node; however, each PATHMON environment includes only one PATHMON process.
Starting a PATHMON Environment Starting and Stopping a PATHMON Environment system, the PATHMON process uses the information stored in this file to create its operating environment. Assigning the PATHMON Configuration File The PATHMON configuration file is always automatically created on the node where the PATHMON process is running. Also, unless you specify otherwise, the PATHMON process operates as if the PATHMON configuration file is located in its default volume and subvolume, under the name PATHCTL.
Starting and Stopping a PATHMON Environment Starting the PATHMON Process Assign a process name and start the PATHMON process that controls your PATHMON environment. 2. Start PATHCOM. Start a PATHCOM process that communicates with the PATHMON process. From this point on, all your interactions with the PATHMON environment take place through PATHCOM. 3. Configure the PATHMON environment. Use SET PATHWAY commands to specify global parameters and limits for the overall configuration.
Starting the PATHMON Process Starting and Stopping a PATHMON Environment Figure 2-2. Starting the PATHMON Process 1> PATHMON / NAME $PMX, CPU 3, NOWAIT/ Command Interpreter PATHMON $ PMX VST011.vsd You should always provide a name for your PATHMON process. You use this name to identify your the PATHMON process when you communicate with the PATHMON process through PATHCOM. (If you do not supply a name, the system gives the PATHMON process a default name, $X984.
Starting and Stopping a PATHMON Environment Starting and Using PATHCOM the PATHMON process runs as a background process. TACL regains control of the terminal as soon as the PATHMON process is created.
Starting and Using PATHCOM Starting and Stopping a PATHMON Environment Figure 2-3. Starting PATHCOM 2> PATHCOM $PMX Command Interpreter PATHCOM PATHMON $ PMX VST012.vsd When PATHCOM starts, it opens communication with your PATHMON process, displays the PATHCOM banner message on your screen, and presents an equal sign as a prompt for your first PATHCOM command.
Starting and Stopping a PATHMON Environment Starting and Using PATHCOM operating system supplies standard default values. For details about the default values for the TACL RUN options, see the TACL Reference Manual. Getting HELP for PATHCOM Syntax and Errors You can display a complete list of all PATHCOM commands available by entering this PATHCOM command: = HELP COMMANDS You can request syntax assistance from PATHCOM.
Starting and Stopping a PATHMON Environment Starting and Using PATHCOM that you want PATHCOM to read. A command file can be an IN file or an Command file: the only difference lies in how you execute the file. IN Command You specify the IN command when you start PATHCOM. For example, this command starts PATHCOM and directs PATHCOM to read commands from a file named PWCMD and list them on the device $S.#LP: 11> PATHCOM /IN PWCMD, OUT $S.
Starting and Stopping a PATHMON Environment Configuring Global Parameters In the preceding example, PATHCOM reads commands from the command file specified by the DEFINE =CMD-FILE ($DATA.PW.CONFIG) and lists them on the device specified by the DEFINE =OUT-FILE ($S). For detailed information about DEFINEs, see the TACL Reference Manual and the Guardian User’s Guide.
Configuring Global Parameters Starting and Stopping a PATHMON Environment Figure 2-5. Specifying PATHMON Environment Limits = SET PATHWAY MAXTCPS 2 PATHMON PATHCOM Total TCPs 2 . . . VST014vsd By specifying limits, you enable the PATHMON process to reserve the disk space that it needs for configuration information. Later, when you actually define and add your PATHMON-controlled objects (described in Section 3, Configuring Objects in a PATHMON Environment).
Starting and Stopping a PATHMON Environment Configuring the PATHMON Process For example, these commands indicate that the owner is the super ID and that only the owner can add, modify, or delete PATHMON-controlled objects: = SET PATHWAY OWNER 255,8 = SET PATHWAY SECURITY "O" Configuring the PATHMON Process Use PATHCOM commands to configure your PATHMON process. For example, you might want to specify a backup processor or request error dumping.
Starting and Stopping a PATHMON Environment Specifying the START Command Specifying the START Command After you have started the PATHMON process and PATHCOM and configured global parameters, you can start your PATHMON environment. There are two START command options: COLD and COOL. Which one you choose depends on the task you want to perform: • Starting a new PATHMON environment (cold start) When you start a PATHMON environment for the first time, you must specify the COLD start option.
Shutting Down a PATHMON Environment Starting and Stopping a PATHMON Environment Figure 2-6. Starting a New PATHMON Environment = START PATHWAY COLD PATHCOM PATHMON Back Process PATHMON PATHMON Configuration File VST015vsd Restarting a PATHMON Environment (COOL Start Option) To restart a PATHMON environment, use the COOL start option as follows: = START PATHWAY COOL In response to this command, the PATHMON process: • • • Starts the PATHMON backup process if one is specified.
Starting and Stopping a PATHMON Environment Shutting Down a PATHMON Environment You can choose from these three options: ORDERLY, ABORT, and IMMEDIATE. Each option provides a different level of shutdown, as described in Table 2-1 and in the subsections that follow. In an environment that includes the NonStop TS/MP product, the PATHMON process automatically stops SERVER processes under its control, and then the PATHMON process itself.
Specifying the ORDERLY Option Starting and Stopping a PATHMON Environment Table 2-1.
Starting and Stopping a PATHMON Environment Specifying the ABORT Option The ORDERLY option opens and closes unlinked server processes, permitting the performance of any epilog processing. Specifying the ABORT Option The ABORT option aborts all TERMS for a faster shutdown operation.
Escalating the Shutdown Operation Starting and Stopping a PATHMON Environment Escalating the Shutdown Operation If you choose the ORDERLY or ABORT option, you can escalate the shutdown operation by pressing the Break key and then specifying a faster option.
Monitoring Shutdown Status Starting and Stopping a PATHMON Environment • Specify the STATUS PATHWAY command from any PATHCOM process. (For details on using the PATHCOM that issued the SHUTDOWN2 command, see Using PATHCOM During Shutdown on page 2-21.
Starting and Stopping a PATHMON Environment Monitoring Shutdown Status This are examples of situations in which shutdown cannot complete: • • An external object (ASSOCIATIVE), such as a server process, cannot be stopped. The network goes down and a locally controlled TCP is running on a remote system in that network. To see if objects are still running, you should specify a STATUS PATHWAY command. If necessary, you can try to stop these objects by specifying a Guardian STOP command at your TACL prompt.
Starting and Stopping a PATHMON Environment Monitoring Shutdown Status Example 2-2. Sample TACL Routine to Stop Orphan Processes (Local System Only) ?SECTION stop_children ROUTINE == Stops all children of a given process id & then stops the process id == USAGE: == STOP_CHILDREN == EXAMPLE: == STOP_CHILDREN $CRPM == this would stop $CRPM and all children of $CRPM (if used by == appropriate user-id) == LIMITATION == This issues explicit stop commands against processes.
Starting and Stopping a PATHMON Environment Using PATHCOM During Shutdown Using PATHCOM During Shutdown When you issue a a SHUTDOWN2 command, the PATHCOM prompt is suspended until shutdown completes, or until you specifically request the prompt to return using one of these methods: • • Press the Break key during a SHUTDOWN2 command. This action returns the PATHCOM prompt to your terminal without affecting execution of the shutdown operation. Specify a TIMEOUT option with the SHUTDOWN2 command.
Starting and Stopping a PATHMON Environment Using PATHCOM During Shutdown NonStop TS/MP System Management Manual—541819-001 2- 22
3 Configuring Objects in a PATHMON Environment Configuration Overview To configure a PATHMON environment, you specify global limits that define the number of objects in the environment, and you configure the objects that run under the PATHMON process to support your application. (A PATHMON environment consists of objects and processes controlled by the PATHMON process.) Note.
Configuring Objects in a PATHMON Environment Configuration Overview In Figure 3-1 on page 3-1, a PC-based inventory application sends Pathsend requests through the Remote Server Call product (RSC) and Transaction Delivery Process (TDP) to the link manager, LINKMON, which forwards the requests to the appropriate server process. The dashed lines indicate control links, while solid lines indicate data links.
Configuration Overview Configuring Objects in a PATHMON Environment Figure 3-2.
Configuring Objects in a PATHMON Environment Configuring a PATHMON Environment operating environments, see Figure 1-2 on page 1-4. As a system manager for a PATHMON environment, you can configure and manage OSS server objects. How you configure a PATHMON environment depends on various management objectives: the size of your application or applications, the number of users, response-time requirements, whether the application is distributed over a network, and so on.
Configuring Objects in a PATHMON Environment • • • • Specifying Limits MAXPARAMS specifies the maximum number of server classes that can have PARAM messages. MAXSERVERCLASSES specifies the maximum number of server-class descriptions that you can add to the PATHMON configuration file. MAXSERVERPROCESSES specifies the maximum number of server processes that you can define for all server classes using the MAXSERVERS option of the SET SERVER COMMAND.
Configuring Objects in a PATHMON Environment Specifying Node Independence additional help, contact your HP representative for details about performance classes offered and for a description of services available from service provider. Specifying Node Independence You can avoid hard-coding node names for many Guardian file names and other variable names in your PATHMON environment by setting the NODEINDEPENDENT attribute of the SET PATHWAY command to ON.
Configuring Objects in a PATHMON Environment Specifying Security the PATHMON process records errors and object status changes. If you leave the node portion of a log file name unspecified, the node name always defaults to the node where the PATHMON process is running at any given time. Migration Considerations Designating your PATHMON application as node-independent simplifies, but does not eliminate, the tasks associated with migrating an application from one system to another.
Configuring Objects in a PATHMON Environment Configuring PATHMON-Controlled Objects Configuring PATHMON-Controlled Objects After specifying global limits and issuing the START command, you configure the SERVER objects that run under the PATHMON process to support your application. If your environment includes the Pathway/iTS product, you also configure TCP, TERM, and PROGRAM objects. For instruction on configuring these objects, see the Pathway/iTS System Management Manual.
Configuring Objects in a PATHMON Environment Using the SET and ADD Commands For more information on the NODEINDEPENDENT attribute, see the description of the SET PATHWAY command in Section 11, PATHMON Environment Control Commands. 2. Add the object with the ADD command. The PATHMON process writes the object’s name and definition to the PATHMON configuration file, inserting this information in the space allocated for it when the file was created.
Using the SET and ADD Commands Configuring Objects in a PATHMON Environment Figure 3-3. Defining and Adding a PATHMON-Controlled Object = SET SERVER PROCESSTYPE OSS = SET SERVER CREATEDELAY 1 MINS = SET SERVER MAXSERVERS 2 = SET SERVER CPUS (3:2, 0:6) = SET SERVER PROGRAM \PARIS.$MARKT.DEPT = SET SERVER SECURITY "N" = SET SERVER = ADD SERVER SRVR-X PATHCOM PATHMON PATHMON Configuration File $PMX Backup CPU Server SRV-1 . . . PROCESSORTYPE OSS . . . MAXSERVERS 2 CPU (3:2, 0:6) . . . PROGRAM \PARIS.
Configuring Objects in a PATHMON Environment Understanding the Working Set of Attribute Values Understanding the Working Set of Attribute Values PATHCOM maintains a working set of attribute values for objects you define in your PATHMON environment. These objects include SERVER objects and −if your environment includes the Pathway/iTS product−TCP, TERM, and PROGRAM objects. For information about managing Pathway/iTS objects, see the Pathway/iTS System Management Manual.
Configuring Objects in a PATHMON Environment Understanding the Working Set of Attribute Values In response to this command, PATHCOM displays: SERVER PROCESSTYPE GUARDIAN AUTORESTART 0 CREATEDELAY 1 MINS DEBUG OFF DELETEDELAY 10 MINS HOMETERM $term-name HIGHPIN OFF LINKDEPTH 1 MAXSERVERS 1 NUMSTATIC 0 OWNER owner PRI priority PROGRAM ? SECURITY "N" TMF OFF VOLUME \node.$volume.subvolume In this example, the working set is in its initial state.
Configuring Objects in a PATHMON Environment Understanding the Working Set of Attribute Values = ADD SERVER DON, PROGRAM \*.$MKT.SALES.ANAL = ADD SERVER MARY,PROGRAM \*.$MKT.SALES.ADMIN All these SERVER objects have the same PROCESSTYPE attribute (namely, Guardian). FRED and JOAN have a LINKDEPTH of 1, while DON and MARY have a LINKDEPTH of 2. Each SERVER object has a unique, node-independent, PROGRAM attribute.
Configuring Objects in a PATHMON Environment Displaying Object Attributes Overriding Working-Set Values When you add an object, you can temporarily override the current attribute values in the PATHCOM working set by specifying other values in the ADD command.
Configuring Objects in a PATHMON Environment Using Existing Object Attributes for New Objects The resulting display appears in this format: SERVER ANNA PROCESSTYPE GUARDIAN AUTORESTART 0 CPUS (2:1,3:2,0:1) CREATEDELAY 1 MINS DEBUG OFF DEFINE =EMP, CLASS MAP, FILE \SYS.$D.APPL.EMP DELETEDELAY 10 MINS HIGHPIN OFF HOMETERM \*.$TERM LINKDEPTH 1 MAXSERVERS 5 NUMSTATIC 2 OWNER \TS.8,8 PRI 134 PROGRAM \*.$BANK1.TEST.CHECK SECURITY "N" TMF ON VOLUME \*.$BANK1.
Configuring Objects in a PATHMON Environment Choosing Names for PATHMON-Controlled Objects Choosing Names for PATHMON-Controlled Objects 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 processes according to the functions they perform: ORDERS for a SERVER that processes orders or INV for one that updates inventory control records.
Configuring Objects in a PATHMON Environment Defining Attributes for Guardian and OSS Servers the server class. This type of server is not dependent on the START SERVER command. A dynamic server process runs as long as a link manager, such as the LINKMON process, communicates with it. Unused links to dynamic servers are returned to the PATHMON process by the link manager. The PATHMON process deletes unused links based on the time limit defined by the DELETEDELAY attribute for the server class.
Configuring Objects in a PATHMON Environment Defining Attributes for Guardian and OSS Servers processor specified as a backup. This parameter is passed to the server as part of the PARAM message. As it creates the server processes, the PATHMON process uses the primary CPUs in the order specified. If a processor is down, the PATHMON process uses the backup processor as an alternate processor and passes the primary processor number as the backup processor parameter.
Configuring Objects in a PATHMON Environment • • • • • Defining Attributes for Guardian and OSS Servers IN specifies the name of the input file passed to the server in the startup message. It can be a DEFINE name. If you omit this attribute, spaces are passed to the server. OUT specifies the name of the OUT file passed to the server in the startup message. It can be a DEFINE name. If you omit this attribute, spaces are passed to the server.
Configuring Objects in a PATHMON Environment Defining Attributes for Guardian and OSS Servers reuses the CPUs in the order specified: for example, a fourth server process would start in processor 2 if that processor were available. (CPUS attribute.) • • • The total number of all server processes in the server class that the PATHMON process can run simultaneously is five. (MAXSERVERS attribute.) The total number of static server processes allowed is three. (NUMSTATIC attribute.
Configuring Objects in a PATHMON Environment Defining Attributes for Guardian and OSS Servers These commands defines an example of an OSS SERVER object and then adds it under the server class name ORDER-SRV1: = = = = = = = = = = = = = = = = • • RESET SERVER SET SERVER PROCESSTYPE OSS SET SERVER ARGLIST -1, process/log, -t SET SERVER CPUS (2,3,0) SET SERVER CWD /centrl/inven/orders SET SERVER DEFINE =PARTS, CLASS MAP, FILE $DATA.REG2.PRTFIL SET SERVER DEFINE =ORDERS,CLASS MAP, FILE $DATA.REG2.
Configuring Objects in a PATHMON Environment • Additional Considerations A variable called DEBUGLOGFORMAT is defined. Its value is TRUE. (ENV attribute.) A variable called HANGAROUND is defined. Its values is TRUE. (ENV attribute.) • • • • • • The total number of all server processes in the server class that the PATHMON process can run simultaneously is four. (MAXSERVERS attribute.) The total number of static server processes allowed is three. (NUMSTATIC attribute.
Configuring Objects in a PATHMON Environment Setting Process Priority Configuring for the Use of High PINs If you have configured your system to allow the use of high PINs, you can define additional server classes without exhausting PINs that you might need for other processes. Additionally, you have more freedom to define server classes as static, thus reducing the overhead associated with process startup.
Configuring Objects in a PATHMON Environment Links and Link Attributes you overconfigure your system. On the other hand, you will pay a large penalty—in performance and operations problems and obscure system errors— if you underconfigure your system. Links and Link Attributes A link is a connection between a link manager, such as the LINKMON process, and a specific server process. The link is used to send a request to, and receive a reply from, a server.
Configuring Objects in a PATHMON Environment Links and Link Attributes The PATHMON process creates server processes to create links. Consequently, the value you specify for the SET PATHWAY MAXSERVERPROCESSES command also affects your link configuration. For more information, see Specifying Limits on page 3-4. MAXSERVERS The MAXSERVERS attribute specifies the maximum number of server processes in a server class that can run at the same time.
Configuring Objects in a PATHMON Environment Understanding the Effects of Link Configuration NUMSTATIC The NUMSTATIC attribute specifies the maximum number of static servers within a server class. Because it is recommended that you run your application with static servers only, you should specify the same value for NUMSTATIC that you specify for MAXSERVERS. This way, no dynamic servers should ever be required.
Understanding the Effects of Link Configuration Configuring Objects in a PATHMON Environment because the PATHMON process cannot create another server process to satisfy the link requests. This situation is illustrated in Figure 3-5, which shows a server class that allows only one server process to run at a time. The server process can handle only one request: Request 1 from TCP-1. Other requests, from TCP-1, TCP-2, and the LINKMON process, are waiting to be processed.
Steps to Optimum Link Configuration Configuring Objects in a PATHMON Environment Figure 3-6. Link Configuration With MAXSERVERS Set to 5 MAXLINKS = 1 LINKDEPTH = 1 MAXSERVERS = 5 PATHMON Server Class 5 processes running LINKMON Request 1 = proccessing Request 2 = proccessing Request 3 = proccessing Request 4 = proccessing Request 5 = proccessing VST021.
Configuring Objects in a PATHMON Environment Steps to Optimum Link Configuration 9. Adjust values based on the value in of the TABLE OCCURS clause in the RECEIVE-CONTROL paragraph of your COBOL server programs. 10. For Pathway/iTS environments, calculate additional TCP attributes. Note that this approach is geared to generate the correct configuration values for a single server class.
Configuring Objects in a PATHMON Environment Steps to Optimum Link Configuration The calculation must be done for each transaction; then the results are applied to each serve class. The formula is: avg. transaction vol. x constant = working avg. transaction vol. For example: 30 transactions per second x 1.5 = 45 transactions per second (tps) where “1.5” is the safety factor and the working average transaction volume is expressed in transactions per second. Note.
Steps to Optimum Link Configuration Configuring Objects in a PATHMON Environment For example, suppose transaction-1 requires 90 active links to the server class, transaction-2 requires 5 active links, transaction-3 requires 10 active links, and transaction-4 requires 15 active links. 90 + 5 + 10 + 15 = 120 total active links required The value you specify for MAXSERVERS should be 120. Note.
Configuring Objects in a PATHMON Environment Steps to Optimum Link Configuration where the constant is a safety factor, MAXSERVERS is the result of Step 6, and no. of TCPs is the total number of TCPs from Step 2. The result, no. of links required by TCPs, is the total potential TCP demand for links to the server class.
Steps to Optimum Link Configuration Configuring Objects in a PATHMON Environment Resolving the equation yields a MAXLINKS value of 1, which means that in this sample configuration, each server process can have just one link to a link manager at a given moment; and 120 server processes can run at any one time. Thus, the configuration provides for a maximum of 120 links, adequate to support the 120 links required.
Configuring Objects in a PATHMON Environment Steps to Optimum Link Configuration Step 10 Identify Additional TCP Attributes If your environment includes the Pathway/iTS product, you can perform this final step to identify additional key TCP attributes. Use the value for the PATHWAY MAXSERVERCLASSES attribute as the value for the TCP MAXSERVERCLASSES attribute. Use 50 as the value for TCP MAXTERMS (as in Step 2).
4 Starting and Stopping SERVER Objects After you configure and start your PATHMON environment and define and add SERVER objects, you issue the START command to activate each SERVER object or process. Note. If your PATHMON environment includes objects provided by the Pathway/iTS product, such as TCP s and TERM and PROGRAM objects, for information on starting and stopping these objects, see the Pathway/iTS System Management Manual.
Starting and Stopping SERVER Objects Starting SERVER Objects The next command starts all static server processes defined for all server classes, in alphabetic order: = START SERVER * You can, however, specify a single static server process, by including the PROCESS option in your command.
Starting and Stopping SERVER Objects Freezing and Thawing Server Classes The ASSIGN messages are constructed directly from the information you provided for the ASSIGN attribute to the SET SERVER command. The PARAM message contains one item for each attribute value you specified for the PARAM attribute of the SET SERVER command. The number of the processor not chosen as the primary processor is reported in the BACKUPCPU attribute, which the PATHMON process adds to the PARAM message.
Starting and Stopping SERVER Objects Stopping SERVER Objects If no server process in the server class has incomplete or outstanding requests, the PATHMON process freezes the server class immediately. If any server process in the server class has incomplete or outstanding requests, the PATHMON process does not freeze the server class until these requests are completed. While awaiting completion of such requests, the server class remains in the FREEZE-PENDING state and can accept no new requests.
Starting and Stopping SERVER Objects Stopping SERVER Objects 1. The PATHMON process notifies all link managers, such as LINKMON processes and TCPs as well as all external TCPs, to delink from the server class. 2. The link managers close all server processes. 3. The server processes respond by preparing for termination and then stopping themselves. 4.
Starting and Stopping SERVER Objects Stopping SERVER Objects NonStop TS/MP System Management Manual—541819-001 4 -6
5 Maintaining a PATHMON Environment System Maintenance Tasks This section describes operations you need to perform on a regular basis to maintain a PATHMON environment.
Maintaining a PATHMON Environment A System Management Scenario For all of these commands, you can direct the display output to a text file by including the OUT option in your command. For example, this command directs output to the text file named JUNE95: = INFO /OUT JUNE95/ PATHWAY With the INFO command, you can use the OBEYFORM option to capture a configuration for use in future start operations. (See Capturing a Configuration on page 5-21.
Maintaining a PATHMON Environment Displaying Configuration Information 7. You use the STATUS SERVER * command again to confirm that all server classes are stopped. Now B-NAME-SERVE and C-NAME-SERVE are stopped, as are all the other server classes. 8. You use the START SERVER command to start server class A-NAME-SERVE. 9. You use the THAW SERVER * command to thaw the other server classes, followed by another STATUS SERVER * command to confirm that all these server classes are thawed. 10.
Displaying Configuration Information Maintaining a PATHMON Environment Example 5-1. INFO PATHWAY Display PATHWAY MAXASSIGNS 200 MAXDEFINES 0 MAXEXTERNALTCPS 0 MAXLINKMONS 8 MAXPARAMS 50 MAXPATHCOMS 95 MAXPROGRAMS 0 MAXSERVERCLASSES 50 MAXSERVERPROCESSES 300 MAXSPI 10 MAXSTARTUPS 50 MAXTCPS 0 MAXTELLQUEUE 0 MAXTELLS 0 MAXTERMS 0 MAXTMFRESTARTS 0 NODEINDEPENDENT OFF OWNER \SYS.
Maintaining a PATHMON Environment Displaying Configuration Information Environment Control Commands. For syntax descriptions for Pathway/iTS attributes, see the Pathway/iTS System Management Manual. The INFO PATHMON Command The INFO PATHMON command displays information about the PATHMON process: = INFO PATHMON Example 5-2 shows an example of what might be displayed when you execute the INFO PATHMON command. Example 5-2. INFO PATHMON Display PATHMON BACKUPCPU 4 DUMP ON (FILE \SYS.$VOL1.TESTING.
Maintaining a PATHMON Environment Displaying Configuration Information Example 5-3. INFO SERVER Display for a Guardian Server SERVER TRECV PROCESSTYPE GUARDIAN ASSIGN TEXTSRV,\SYS.$ZTXT ASSIGN TRAFFICLOG,\SYS.$M9.TMAILDBA.TRAFLOG AUTORESTART 3 CPUS (11:4,10:5,9:6,8:7,7:8,8:9) CREATEDELAY 15 SECS DEBUG OFF DELETEDELAY 60 MINS HIGHPIN OFF HOMETERM $OSP LINKDEPTH 1 MAXLINKS 1 MAXSERVERS 4 NUMSTATIC 2 OUT \SYS.$TLOG OWNER \SYS.
Maintaining a PATHMON Environment Displaying Configuration Information This example displays information about a single OSS server class, TRANS-SRV1, using the OBEYFORM option. OBEYFORM causes the information to be displayed in the format used to configure the server class: = INFO SERVER TRANS-SRV1, OBEYFORM Example 5-4 shows the information displayed in response to the command. Note that PATHCOM includes the RESET SERVER command before and the ADD SERVER command after the server class description.
Displaying Status Information Maintaining a PATHMON Environment A TCP or LINKMON process can have only one link to each server process within this class (indicated by the LINKDEPTH parameter). For a complete description of all the SERVER attributes viewable through the INFO SERVER command, see INFO SERVER Command on page 12-7. Displaying Status Information You can display the status of an object, error messages pertaining to the object, and other associated information using the STATUS command.
Displaying Status Information Maintaining a PATHMON Environment The display shows that there are eight LINKMON processes, 10 PATHCOM processes, and one SPI process currently running. (There are no external TCPs communicating with this PATHMON environment.) The display also shows the state of all server classes and server processes, and, if your environment includes Pathway/iTS, TCPs and TERM objects.
Displaying Status Information Maintaining a PATHMON Environment Example 5-7 shows the information displayed in response to the command. Example 5-7. STATUS SERVER Display SERVER PROCESS-SERVER #RUNNING 4 ERROR INFO PROCESS-SERVER currently has four server processes running.
Displaying Status Information Maintaining a PATHMON Environment one link with the LINKMON process named L\SYS.$ZL11. Server process $ZTP3 has only one link, with the TCP named M6530-TCP. Example 5-9.
Displaying Status Information Maintaining a PATHMON Environment Example 5-10 shows links for an OSS server class TRAN-SRVR. Notice that process $ZTX2 has two links: one link with the LINKMON process named L\SYS.$ZL15 and one link with LINKMON process L\SYS.$ZL10. For a complete description of the information available through the STATUS SERVER command, see STATUS SERVER Command on page 12-39. Example 5-10.
Maintaining a PATHMON Environment Displaying Statistics Information Displaying Statistics Information Server statistics are collected by LINKMON processes or TCPs that have links to the server class. The LINKMON process collects these statistics on an ongoing basis. A TCP collects them only if you use one of these commands to direct the system to collect them: • • SET TCP STATS CONTROL TCP STATS Note that TCPs are configured in your environment only if you are running the Pathway/iTS product.
Displaying Statistics Information Maintaining a PATHMON Environment Example 5-11 shows the information collected by four TCPs and one LINKMON process and displayed in response to the command. Note. Your environment includes TCPs only if you have the Pathway/iTS product. Example 5-11. STATS SERVER Display: Guardian Server SERVER PROCESS-SERVER IN TCP M6530-TCP1 09:47:00 QUEUE INFO: 07 APR 1994, REQ CNT 0 REQ CNT 99198 % WAIT MAX WAITS 0.
Maintaining a PATHMON Environment Displaying Statistics Information If you include the FREQTABLE option, as shown in this command example, the STATS SERVER command generates a frequency distribution table containing statistics for the specified server class: = STATS SERVER PROCESS-SERVER, FREQTABLE For more information about server statistics and the FREQTABLE option, see Section 7, Tuning Your System by Using Statistics. Note.
Displaying Statistics Information Maintaining a PATHMON Environment Example 5-12. STATS SERVER Display: OSS Server SERVER TRAN-SRVR IN LINKMON L\SYS.$ZL11 08:42:06 QUEUE INFO: REQ CNT 1 I/O INFO: REQ CNT SEND 102 REPLY IN LINKMON L\SYS.$ZL12 08:42:06 QUEUE INFO: REQ CNT 0 I/O INFO: REQ CNT SEND 87 REPLY IN LINKMON L\SYS.$ZL13 08:42:06 QUEUE INFO: REQ CNT 0 I/O INFO: REQ CNT SEND 42 REPLY IN LINKMON L\SYS.$ZL14 08:42:06 QUEUE INFO: REQ CNT 0 I/O INFO: REQ CNT SEND 12 REPLY IN LINKMON L\SYS.
Maintaining a PATHMON Environment Reconfiguring a PATHMON Environment Reconfiguring a PATHMON Environment As your business needs change, requirements for your transaction processing configuration are likely to change. Adjustments are sometimes necessary to satisfy your transaction throughput and response time requirements and to update or expand the system to provide needed resources.
Maintaining a PATHMON Environment Adding, Altering, and Deleting Objects > PATHMON /NAME $PM, NOWAIT/ > PATHCOM $PM . .(specify old limits) . = SET PATHWAY MAXPARAMS 30 = SET PATHWAY MAXSTARTUPS 40 = START PATHWAY COLD! For more information about shutting down and starting your configuration, see Section 2, Starting and Stopping a PATHMON Environment Note. When specifying limits, you should always allow space for system growth.
Maintaining a PATHMON Environment Changing Backup CPUs and Dump Files Altering Objects You can alter SERVER, TCP, TERM, and PROGRAM objects by entering the ALTER command for the specified object type. Before using the ALTER command for a SERVER object, you must freeze and stop the SERVER with the FREEZE and STOP commands, respectively.
Maintaining a PATHMON Environment Exchanging Primary and Backup CPUs To direct the memory dump for the PATHMON process to a file named PMDUMP, enter: = CONTROL PATHMON, DUMP ON (FILE PMDUMP) The PATHMON configuration file is updated to reflect these changes. To change the file for logging output, use the PATHCOM commands LOG1 and LOG2.
Maintaining a PATHMON Environment Capturing a Configuration . = SET PATHWAY OWNER 8,60 = SET PATHWAY SECURITY "O" = START PATHWAY COLD! For more information about the OWNER and SECURITY attributes, see Section 3, Configuring Objects in a PATHMON Environment. Capturing a Configuration You can use the INFO command with the OBEYFORM option to capture a configuration for use in future start operations.
Maintaining a PATHMON Environment Capturing a Configuration named NEWCONF. Notice that an asterisk (*) is used in the last four commands to indicate all SERVER objects in the set. INFO /OUT NEWCONF/ PATHMON , OBEYFORM INFO /OUT NEWCONF/ PATHWAY , OBEYFORM INFO /OUT NEWCONF/ SERVER *, OBEYFORM 2. Purge any existing file of the same name as your destination command file, or rename that file, by entering the PURGE or RENAME TACL commands.
Maintaining a PATHMON Environment Logging Status and Error Information configures and cold starts the PATHMON environment. As an example, to use the command file named NEWCONF to configure and start your system, enter: = OBEY NEWCONF This step completes your configuration and start operations. If you frequently alter your global configuration, using the OBEYFORM option to create a command file can be helpful. Note. OBEYFORM presents certain limitations.
Maintaining a PATHMON Environment Logging Information to a Disk File Logging Information to a Disk File To select a destination other than your terminal for logging information, you can enter a run option with the implicit RUN PATHMON command, as follows: 5> PATHMON / NAME $PMX, CPU 3, NOWAIT, OUT LOGPMON/ Alternatively, you can specify the file for logging output by using the PATHCOM commands LOG1 and LOG2.
Maintaining a PATHMON Environment Links and PATHMON Performance messages and text messages to $0 because although the LOG2 command did not specify the EVENTFORMAT parameter, the LOG1 command did. Note. If the log file is running but is temporarily unavailable or overloaded, the PATHMON environment may slow down. Links and PATHMON Performance A link is managed and owned by the the PATHMON process that controls the server process.
Maintaining a PATHMON Environment Managing PATHMON Process Performance A link manager will return a link to a server process when any of these situations occur: Cause Action A “DELETEDELAY” timer expires for a dynamic link. Returns the dynamic link. An OPEN error occurs on a link. Returns the link. An I/O error occurs on a link. (I/O errors include timeouts caused by the SET SERVER TIMEOUT value. Timeouts caused by the SERVERCLASS_SEND_ timeout value are not considered to be link errors.
Maintaining a PATHMON Environment Detecting Problems These sections describe factors that can cause poor performance and steps you can take to improve performance.
Maintaining a PATHMON Environment Improving Performance Logging Errors The PATHMON process is responsible for all error logging. Delays in logging errors or status messages can adversely affect the performance of the PATHMON environment. You should examine the log file and understand what causes each of the errors. In a well-designed, well-configured PATHMON environment, the log should be empty or nearly so. Occasional errors do not exact a large penalty.
Maintaining a PATHMON Environment Information to Include When Reporting Problems Information to Include When Reporting Problems When requesting your HP representative’s help in resolving a problem with NonStop TS/MP, you can greatly enhance the representative’s ability to help you by providing this information, where applicable. PATHMON Environment These files and information apply to the PATHMON environment as a whole.
Maintaining a PATHMON Environment PATHCOM-Specific Problems If error dumping has not been specified and the PATHMON tables (showing, for example, server states) appear to be in error, your representative may ask that you force a dump by performing: >PATHCOM $ =CONTROL PATHMON, DUMPMEMORY (FILE ) =EXIT where pm is the name of your PATHMON process and pmdump is name of the dump file. Note that the DUMPMEMORY option is not a substitute for setting the DUMP option to ON.
Maintaining a PATHMON Environment • Recovering from PATHMON Failure Status information; at the system prompt, perform: STATUS /OUT / *, PROG , DETAIL where statfile is the listing file that captures the status display in an edit file, and prog filename is the server program’s file name. Recovering from PATHMON Failure If PATHMON fails, perform these steps to capture data about the failure and restart the PATHMON process. 1.
Maintaining a PATHMON Environment Maintaining Associative Server Processes recommended that you maintain separate sets of development and production server classes. It is also desirable to define separate TCPs for development and production. Certain types of errors, such as timeout errors, can also occur when you are debugging servers in a Pathway application. For further information about these errors, see the section on servers in the TS/MP Pathsend and Server Programming Manual.
Maintaining a PATHMON Environment Migrating Your Environment to a Different System attributes do not take effect until the PATHMON process receives a START SERVER command for an associative server that has actually stopped: ASSIGN OUT PRI DEFINE OWNER PROGRAM GUARDIAN-LIB VOLUME SECURITY HOMETERM PARAM STARTUP IN Associative Servers as Subtype 30 Processes An associative server can be a subtype 30 process, which simulates a terminal or communication device.
Migrating Your Environment to a Different System Maintaining a PATHMON Environment The table includes objects supported by the NonStop TS/MP product and, as noted, the Pathway/iTS product. Table 5-1. Migration Considerations: Object Attribute Values (page 1 of 3) Considerations/ Recommendations Object or Process Attribute PATHMON process BACKUPCPU cpu-num Ensure that CPUs on new system have same numbers or change manually.
Migrating Your Environment to a Different System Maintaining a PATHMON Environment Table 5-1. Migration Considerations: Object Attribute Values (page 2 of 3) Object or Process Attribute Considerations/ Recommendations SERVER PROCESS CPUS pricpu:backupcpu or cpu-num Ensure that CPUs on new system have same numbers or change manually. GUARDIAN-SWAP $volume Ensure that a disk attached to new system has same name or change manually.
Migrating Your Environment to a Different System Maintaining a PATHMON Environment Table 5-1. Migration Considerations: Object Attribute Values (page 3 of 3) Object or Process Attribute Considerations/ Recommendations PRINTER filename Ensure that a device with same name exists on new system or change manually. TCL PROG Ensure that volume portion of the file name is known to new system or change manually. *Objects configured under Pathway/iTS only Note.
6 Managing the Pathsend Environment The Pathsend Environment This section discusses the Pathsend environment, which consists of Pathsend processes and LINKMON processes, and the tasks you perform to manage the Pathsend environment. Pathsend Processes Pathsend processes are user-written Guardian programs that use Pathsend procedure calls to communicate with server classes. The Pathsend procedure calls are part of the operating system library.
LINKMON Processes Managing the Pathsend Environment NonStop TUXEDO clients and servers. NonStop TUXEDO servers are created and managed within the NonStop TUXEDO environment, but within the PATHMON environment these servers appear as OSS processes. The LINKMON process gathers statistics for servers. For more information, see Tuning Your System by Using Statistics on page 7-1.
LINKMON Processes Managing the Pathsend Environment Table 6-1.
Managing the Pathsend Environment • • • LINKMON Processes Returns an error to the application (Pathsend error 947, file-system error 43). Logs one or more messages to the system log. Returns to its original state and waits 10 seconds before processing additional Pathsend procedure calls, so that subsequent sends to the uninitialized LINKMON process do not flood $0. When the LINKMON process receives the next SEND call, it tries again to initialize itself.
Managing the Pathsend Environment Pathsend Management Tasks Pathsend Management Tasks To enable communication between Pathsend processes and server processes, you must configure your PATHMON environment to specify: • • The number of LINKMON processes that your PATHMON environment can support at one time The appropriate security to control access to server classes You cannot configure or control LINKMON processes with PATHCOM commands in the same way that you control and configure PATHMON-controlled obj
Managing the Pathsend Environment • Specifying Security The PATHMON process must be able to open the server processes (to send startup messages). All of these opens are performed using the PATHMON process’s user ID.
Monitoring LINKMON Processes Managing the Pathsend Environment You set the SERVER SECURITY parameter using the Guardian security values A, G, O, -, N, C, and U. For example, this command enables only those Pathsend processes running under the process ID and on the same system as the user specified by the SERVER OWNER attribute to access the server class: = SET SERVER SECURITY "O" “N” is the default security for the SERVER SECURITY attribute.
Monitoring LINKMON Processes Managing the Pathsend Environment Displaying Information About LINKMON Processes You can also display information about LINKMON processes using these STATUS commands: • • • • STATUS LINKMON STATUS PATHMON STATUS PATHWAY STATUS SERVER (For complete examples of display output for the STATUS PATHWAY, STATUS PATHMON, and STATUS SERVER commands, see Section 5, Maintaining a PATHMON Environment.
Monitoring LINKMON Processes Managing the Pathsend Environment The STATUS PATHMON display shows the Guardian process ID of the LINKMON processes and their process-accessor IDs, as shown in Example 6-2. Example 6-2. LINKMON Information in STATUS PATHMON Display PATHMON \CHI.$PM32 -- STATE=RUNNING CPUS 8:0 PATHCTL (OPEN) $OPER.TRANCNFG.PATHCTL LOG1 (CLOSED) $0 LOG2 (CLOSED) REQNUM FILE PID PAID 15 . . . LINKMON . . .
Monitoring LINKMON Processes Managing the Pathsend Environment Example 6-4. LINKMON Information in STATUS SERVER Display SERVER PROCESS-SERVER PROCESS $ZTP2 LINKER M6530-TCP1 L\SYS.$ZL11 #RUNNING 4 . . . STATE RUNNING ERROR 3115 ERROR INFO 34 INFO #LINKS 4 WEIGHT 9 LINK COUNT 003 001 . . . STATS SERVER Command To display statistics collected by LINKMON processes, use the STATS SERVER command.
7 Tuning Your System by Using Statistics This section describes statistics collected for server processes. These statistics are collected when you execute the STATS SERVER command. See the description of the STATS SERVER Command on page 12-37. This section is divided into two parts: • • The first part describes server process performance statistics that both the LINKMON process and the TCP collect. The second part describes server process performance statistics collected only by the TCPs.
Tuning Your System by Using Statistics • • Queue Info Server-class wait queue (QUEUE INFO) Input and output operations (I/OþINFO) Example 7-1 shows a sample set of server statistics gathered by a TCP (TCP1) and a LINKMON process (LM1). Example 7-1. Sample Server Statistics SERVER SERVME IN TCP TCP1* QUEUE INFO*: 19 FEB 1996, 15:22:30 % WAIT MAX WAITS AVG WAITS % DYNAMIC 99.8 7 2.37 99.
Tuning Your System by Using Statistics Queue Info Example 7-2. QUEUE INFO Section of Sample Server Statistics SERVER SERVME IN TCP TCP1* QUEUE INFO*: 19 FEB 1996, 15:22:30 % WAIT MAX WAITS AVG WAITS % DYNAMIC 99.8 7 2.37 99.9 . . . IN LINKMON LM1 INTERVAL 10 MINS COUNT 1/5 25 SEP 1984, 11:50:25 QUEUE INFO: REQ CNT % WAIT MAX WAITS AVG WAITS % DYNAMIC 19 0.0 0 0.00 94.
I/O Info Tuning Your System by Using Statistics % DYNAMIC The higher the number indicated for % DYNAMIC, the greater the chance that a dynamic server will be required. It is important to realize that this number does not indicate: • • That dynamic servers were in fact started. It does indicate, however, that some requests were delayed anywhere from not at all to the time specified with the SET SERVER CREATEDELAY command. The number of dynamic links granted by the PATHMON process.
Tuning Your System by Using Statistics Server Statistics Collected Only By the TCP Table 7-2. Server Statistics for I/O Info Statistic For SEND, Indicates: For REPLY, Indicates: REQ CNT Total number of sends to servers in this server class N.A.
Response Time Info Tuning Your System by Using Statistics the moment after it issues a SEND statement and stopping the clock the moment after it receives a reply from the server process. The captured measurements represent server response time. Example 7-4 shows only the RESPONSE TIME INFO section of the sample server statistics. See this example as you read this section. Example 7-4. RESPONSE TIME INFO Section of Sample Server Statistics SERVER SERVME? IN TCP TCP1* 19 FEB 1996, 15:22:30 . . .
Tuning Your System by Using Statistics Frequency Distribution Frequency Distribution When you specify the FREQTABLE option of the STATS SERVER command, the PATHMON process displays supplemental statistics on the completion of SCREEN COBOL SEND statements within a given time interval. These statistics are collected only if your environment includes the Pathway/iTS product. The supplemental information is contained in the frequency distribution table, as shown in Example 7-5.
Frequency Distribution Tuning Your System by Using Statistics Table 7-4. Server Statistics for Frequency Distribution Statistic Indicates TIME INTERVAL Value of the time increment from one interval to the next # MEAS Total number of measurements collected during the given time interval CUM % Cumulative percentage of the total number of measurements the line item represents You can use the statistics for frequency distribution to determine the times of peak load for your system.
8 Overview of PATHCOM This section contains overview information to help you get started using PATHCOM to manage your PATHMON environment. For more detailed information on how PATHCOM works and how to manage your Pathway environment, see Introduction to NonStop TS/MP System Management on page 1-1 through Section 7, Tuning Your System by Using Statistics. Note. Note. This manual provides information specific to commands dealing with objects managed through the NonStop TS/MP product.
Command List Overview of PATHCOM only the PATHMON process and the FREEZE SERVER command affects only server classes. Note. The PATHMON process reports only destination object states; it does not report transitional states. To determine the current state of an object, use the appropriate STATUS command. Command List Table 8-1 is a list of the commands you can execute using PATHCOM. The table entries provide the name of the command, its description, and the names of the objects influenced by the command.
Command List Overview of PATHCOM Table 8-1.
Command and Object Relationships Overview of PATHCOM Table 8-1.
Command Format Overview of PATHCOM Command Format When entering PATHCOM commands, consider: • In general, options within a command are position independent. That is, you can place the options in any order within the command line. For example, this command: SET SERVER PROCESSTYPE GUARDIAN, AUTORESTART 1, PROGRAM $MKT.PR6 could also be entered as: SET SERVER PROGRAM $MKT.
Interactive Mode Overview of PATHCOM Note. You cannot embed PATHCOM comments in TACL scripts. In TACL scripts, information enclosed in brackets is interpreted as a function, not as a comment. For information on including comments in TACL scripts, see the TACL Reference Manual. • A PATHCOM command line spans input records if the last nonblank character is an ampersand (&). Multiple commands, separated by semicolons, can appear on the same line.
Noninteractive Mode Overview of PATHCOM Noninteractive Mode PATHCOM functions in noninteractive mode when it reads commands from a command file. In this example, PATHCOM reads commands from a file named CMDFILE and lists them on the device $S.#LP. When it encounters an end-of-file command or an EXIT command, PATHCOM terminates. 3> PATHCOM/IN CMDFILE,OUT $S.#LP, CPU 1, NOWAIT/$PM2 You can use DEFINEs to specify names for the files that PATHCOM uses directly as IN, OUT, and OBEY command files.
File Name Expansion Overview of PATHCOM Each process and each device, such as a tape drive or printer, is identified the same way a disk file is identified. For example: \TSB.$TAPE1 specifies a particular tape drive on the system named \TSB. If a Pathway environment is running on this system, only $TAPE1 is required for the file name. File Name Expansion File name expansion is accomplished through the use of default names.
Relative Pathnames Overview of PATHCOM When setting an OSS pathname using the SET SERVER CWD command or when setting a default directory using the CMDCWD command, you must specify an absolute pathname. Absolute pathnames specified for server process attributes are validated when the SET SERVER command is processed. Relative Pathnames At process time, PATHCOM treats any OSS pathname that does not begin with a forward slash (/) as a relative pathname and expands it to create an absolute pathname.
Relative Pathnames Overview of PATHCOM NonStop TS/MP System Management Manual—541819-001 8- 10
9 PATHMON and PATHCOM Startup Commands This section describes the TACL commands for starting the PATHMON process and PATHCOM. Before starting PATHCOM, you must start the PATHMON process, the central control process of a Pathway environment. The default name of the PATHMON object file is $SYSTEM.SYSTEM.PATHMON. Starting the PATHMON Process You start the PATHMON process by entering the PATHMON command through the TACL command interpreter. PATHMON / NAME $process-name [ , run-option ]...
PATHMON and PATHCOM Startup Commands Starting the PATHMON Process CPU number specifies the processor where the primary PATHMON process executes. This number can be the number of any processor on your system from 0 through 15. The backup processor is specified with the SET PATHMON command and the BACKUPCPU parameter. If you omit this parameter, the default is the processor used by the TACL command interpreter.
PATHMON and PATHCOM Startup Commands Starting PATHCOM PRI number specifies the execution priority of the PATHMON process. number can be a value from 1 through 199. If you omit this parameter, the default is one less than the priority of the TACL command interpreter. If there is an active $CMON on the system, the default is the priority $CMON assigns.
PATHMON and PATHCOM Startup Commands Starting PATHCOM If you omit this parameter, input is taken from the current TACL input file; this file is typically the home terminal. OUT list-file specifies a file to which all PATHCOM command responses are written. The file must be either an EDIT file or an unstructured format file. If responses are written to a key-sequenced, relative, or entry-sequenced file, the Pathway configuration fails and the PATHCOM process eventually abends.
Starting PATHCOM PATHMON and PATHCOM Startup Commands number can be a value from 1 through 199. If you omit this parameter, the default is a priority slightly greater than the priority of the PATHMON process. pathmon-name specifies the name of the PATHMON process with which PATHCOM is to establish communication. The format is: [ \node.]$process-name If node is omitted, PATHCOM opens the PATHMON process with the same system name as the name of the TACL command interpreter.
PATHMON and PATHCOM Startup Commands NonStop TS/MP System Management Manual—541819-001 9 -6 Starting PATHCOM
10 PATHCOM Operation Commands The commands for controlling and operating PATHCOM are: CMDCWD CMDVOL ERRORS EXIT FC HELP OBEY OBEYVOL OPEN RESET SHOW NonStop TS/MP System Management Manual—541819-001 10- 1
PATHCOM Operation Commands CMDCWD Command CMDCWD Command Use the CMDCWD command to set a default OSS directory. When processing ADD or ALTER commands, the PATHMON process uses this default directory to resolve OSS relative file names only if no value has been defined for the CWD attribute. CMDCWD oss-pathname oss-pathname specifies an absolute OSS directory name. For more information on OSS pathnames, see the subsection OSS Pathnames on page 8-8.
PATHCOM Operation Commands CMDVOL Command CMDVOL Command Use the CMDVOL command to set the default node, volume, or subvolume for the expansion of any Guardian file names associated with objects supported under NonStop TS/MP or Pathway/iTS, 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 CMDVOL command. CMDVOL { { { { [ \node. | \*.] $volume.subvolume } [ \node. | \*.] $volume } [ \node. | \*.
CMDVOL Command PATHCOM Operation Commands subsequently defined without specified node name are expanded with the \MARS node name. If you issue the CMDVOL command again to assign the node \DALLAS, all subsequent Guardian file names defined without specified node names are expanded, and stored in the PATHMON configuration file, with the \DALLAS node name. Previous file names resolved with the \MARS node are not changed.
ERRORS Command PATHCOM Operation Commands 1> CMDVOL $ENGR.SYS1 Expanded filename is \current-PATHCOMuser-node.$ENGR.SYS1.filename 2> CMDVOL \HQ.$MKT.SALES Expanded filename is \HQ.$MKT.SALES.filename 3> CMDVOL $ADMIN Expanded filename is \HQ.$ADMIN.SALES.filename 4> CMDVOL SYS2 Expanded filename is \HQ.$ADMIN..SYS2.filename 5> CMDVOL \FIELD.$SUPP Expanded filename is \FIELD.$SUPP..SYS2.filename 6> CMDVOL \*.$ADMIN.VAC Expanded filename is \filename-PATHMONnode.$ADMIN.VAC.
EXIT Command PATHCOM Operation Commands Considerations • • The ERRORS command must appear in the command line before any OBEY command; otherwise, PATHCOM ignores the ERRORS command and stops after the first error or warning. You can enter the ERRORS command in the command file that you use for the IN file option of the PATHCOM startup command; however, if you enter ERRORS on the same command line with the IN file option, PATHCOM ignores the IN command file to execute the ERRORS command.
FC Command PATHCOM Operation Commands Considerations • You enter subcommands and their associated strings beneath the display command line and terminate these commands with a carriage return. Begin replacement, insertion, and deletion commands with the character positioned directly above the subcommand (R,I,D). Subcommand R replaces characters in the command line with replacementstring on a one-for-one basis.
HELP Command PATHCOM Operation Commands HELP Command Use the HELP command to display or list to a file the command syntax for all PATHCOM commands. HELP [ / OUT list-file / ] [ [ [ [ [ ALL COMMANDS <“detail-name”> ] ] ] ] ] OUT list-file specifies the name of a file to which PATHCOM directs the HELP output. If you omit this option, the output goes to the PATHCOM list file; this is typically the home terminal. ALL lists the syntax for all PATHCOM commands.
HELP Command PATHCOM Operation Commands [ <“detail-name”> [ ] ] command-name ::= ABORT CONTROL FREEZE LOG2 PRIMARY SET STATS TELL ADD DELETE HELP O REFRESH-CODE SHOW STATUS THAW ALTER ERRORS INFO OBEY RESET SHUTDOWN STOP CMDCWD EXIT INSPECT OBEYVOL RESUME SHUTDOWN2 SUSPEND CMDVOL FC LOG1 OPEN RUN START SWITCH Examples The command HELP SUSPEND, PATHCOM displays the SUSPEND command syntax as: SUSPEND [ ! ] To next obtain syntax for the parameter of the SUSP
PATHCOM Operation Commands OBEY Command OBEY Command Use the OBEY command to cause commands to be read from a specified command file. { OBEY } file-name { O } file-name specifies a HP file name. The file can be a disk file, terminal, or process from which PATHCOM reads commands. file-name can also be the name of a DEFINE. Considerations • • PATHCOM reads and executes commands from the named file until it encounters an EXIT command or the end of the file.
PATHCOM Operation Commands OBEYVOL Command OBEYVOL Command Use the OBEYVOL command to set the default node, volume, and subvolume for expansion of OBEY command file names. OBEYVOL [ [ [ [ [ \node.] $volume.subvolume ] [ \node.] $volume ] [ \node.] subvolume ] \node ] \node specifies the node name to be used. $volume specifies the volume to be used. subvolume specifies the subvolume to be used.
OPEN Command PATHCOM Operation Commands OPEN Command Use the OPEN command to specify the name of the PATHMON processand therefore the Pathway environmentto which PATHCOM directs subsequent commands. This command is useful when more than one Pathway environment is running on the same NonStop system. You can direct commands to multiple PATHMON processes during a single PATHCOM session. OPEN [ \node.]$pm-process \node specifies the HP node name or node number on which a PATHMON process can be opened.
RESET CMDCWD Command PATHCOM Operation Commands RESET CMDCWD Command Use the RESET CMDCWD command to change to blanks the default OSS directory name you defined with the CMDCWD command. RESET CMDCWD Consideration This command does not change the OSS directory name for SERVER objects already added to the PATHMON configuration file.
PATHCOM Operation Commands SHOW Command ERRORS displays the number of errors PATHCOM ignores when reading a command file. This number is set by the ERRORS command, described previously in this section. If PATHCOM has not yet read the OBEY command file, this option displays the number of errors to be ignored. If PATHCOM has read the file, this option displays the number of errors remaining of the number you specified for PATHCOM to ignore.
11 PATHMON Environment Control Commands This section describes the PATHCOM commands that control the PATHMON process and the PATHMON environment as a whole; the commands are listed in alphabetic order.
PATHMON Environment Control Commands CONTROL PATHMON Command CONTROL PATHMON Command Use the CONTROL PATHMON command to change specific attributes of the PATHMON process while it is running and to record the changes in the PATHMON configuration file. CONTROL PATHMON , pathmon-attribute [ , pathmon-attribute ]... pathmon-attribute is: BACKUPCPU number DUMP { ON [ ( FILE file-name ) ] | OFF } DUMPMEMORY (FILE file-name ) BACKUPCPU number specifies the processor where the PATHMON backup process runs.
PATHMON Environment Control Commands CONTROL PATHMON Command If you do not specify the volume and subvolume portions of file-name, the PATHMON process creates a dump file on the same subvolume as the PATHMON configuration file. The format of the file name is ZZPMnnn, where nnn is a 3-digit number. The file code is 130. Note.
CONTROL PATHMON Command PATHMON Environment Control Commands 11 times, 2 minutes if stopped 12 times, and so forth. However, the PATHMON process does not delay creating a backup process if any of these occur: ° The processor in which the PATHMON primary or backup process is executing fails. ° ° A PATHCOM SWITCH command is executed. A CONTROL PATHMON BACKUPCPU command is executed.
PATHMON Environment Control Commands INFO PATHMON Command This command creates a backup PATHMON process in processor 4, and creates a dump file named PMDUMP if an internal error occurs: CONTROL PATHMON, BACKUPCPU 4, DUMP ON (FILE PMDUMP) INFO PATHMON Command Use the INFO PATHMON command to display the attribute values currently defined for the PATHMON process. INFO [ / OUT list-file / ] PATHMON [ , OBEYFORM ] OUT list-file directs output to the named list file; this could be a DEFINE name.
PATHMON Environment Control Commands INFO PATHWAY Command This command directs the information to a file: INFO/OUT PMINFO/PATHMON, OBEYFORM These commands create a DEFINE at PATHCOM startup and direct the information to the file specified in the DEFINE: 12> ADD DEFINE =OUT-LOG, CLASS SPOOL, LOC $S, REPORT "INFO" 12> PATHCOM $PM1 =INFO/ OUT =OUT-LOG/SERVER * This sequence of commands captures a configuration for a Pathway environment (minus the START PATHWAY command) in the command file called NEWCONFG: =I
INFO PATHWAY Command PATHMON Environment Control Commands START PATHWAY command at the end of the OUT file before using the file to start a Pathway environment. Examples After you define the attribute values with the SET PATHWAY command, you can use the INFO PATHWAY command to display those values.
PATHMON Environment Control Commands LOG1 and LOG2 Commands LOG1 and LOG2 Commands Use the LOG1 and LOG2 commands to name the files that the PATHMON process and the Pathway/iTS TCPs use for reporting errors and changes in object status. The PATHMON process generates either text or event messages for each log file; you specify which type of message the PATHMON process generates.
PATHMON Environment Control Commands LOG1 and LOG2 Commands STATUS sends status change messages and error messages to the file you specify with file-name. If the STATUS option is not specified, only error messages are written to the log file. EVENTFORMAT specifies that messages should be formatted as event messages. If you omit EVENTFORMAT, text messages are generated.
PATHMON Environment Control Commands PRIMARY PATHMON Command This command closes the LOG2 file: LOG2 PRIMARY PATHMON Command Use the PRIMARY PATHMON command to resume operation of the PATHMON primary process in the processor defined for this process in the PATHMON configuration file. Use this command after an individual process or processor failure, or after a SWITCH command has moved the PATHMON primary process from one processor to another.
SET PATHMON Command PATHMON Environment Control Commands This command resumes the operation of the PATHMON primary process in processor 2 only if processor 2 is the processor recorded in the PATHMON configuration file for the PATHMON process. PRIMARY PATHMON, IFPRICPU 2 SET PATHMON Command Use the SET PATHMON command to establish the values for the PATHMON attributes. Use this command before cold starting a Pathway environment. SET PATHMON pathmon-attribute [ , pathmon-attribute ]...
SET PATHWAY Command PATHMON Environment Control Commands OFF directs the PATHMON process not to write data stack and PATHMON configuration file information to a file when it encounters an internal error. Errors This table lists the most common errors that can occur during the processing of the SET PATHMON command: This Message… Is Displayed When… *1093* BACKUP PROCESSOR DOWN For a multiprocessor system, you specified a backup processor but only one processor is operational.
PATHMON Environment Control Commands SET PATHWAY Command SET PATHWAY pw-attribute [ , pw-attribute ]...
PATHMON Environment Control Commands SET PATHWAY Command PARAM messages for a server class count as one toward this limit, the number for this attribute should not exceed the value of MAXSERVERCLASSES. MAXSERVERCLASSES number is the maximum number of server class descriptions that you can add to the PATHMON configuration file. number must be a value from 0 through 4095. To enable the PATHMON process to process an ALTER SERVER command, specify a maximum of 4094 for this attribute.
PATHMON Environment Control Commands SET PATHWAY Command MAXTERMS number This attribute is specific to the Pathway/iTS product. A complete description of this attribute is given in the Pathway/iTS System Management Manual. This attribute is required. It has no default. If your environment does not support Pathway/iTS, it is recommended you specify 0 for the value. MAXDEFINES number is the maximum number of DEFINE definitions that you can specify for all server classes in a Pathway environment.
PATHMON Environment Control Commands SET PATHWAY Command MAXPROGRAMS number This attribute is specific to the Pathway/iTS product. A complete description of this attribute is given in the Pathway/iTS System Management Manual. If your environment does not support Pathway/iTS, it is recommended you specify 0 for the value. If you omit this attribute, the default is 0.
PATHMON Environment Control Commands SET PATHWAY Command NODEINDEPENDENT [ON | OFF] designates whether unspecified node names in Guardian file names resolve to the node name \*, a generic name that designates whatever node the PATHMON process is running on after cool start. If you omit this attribute, the default is OFF. ON specifies \* as the default node name when the node name is left unspecified in Guardian file names defined during the current PATHCOM session and all subsequent PATHCOM sessions.
PATHMON Environment Control Commands SET PATHWAY Command Object Associated File Name PATHMON process DUMP FILE file-name Pathway object OWNER owner-id SERVERCLASS ASSIGN logical-unit assign-spec GUARDIAN-LIB file name IN file-name OUT file-name OWNER owner-id PROGRAM file-name VOLUME $volume SERVERPROCESS GUARDIAN-SWAP $volume HOMETERM termname TCP object* DUMP FILE file-name GUARDIAN-LIB file-name GUARDIAN-SWAP $volume HOMETERM term-name INSPECT file-name PROGRAM file-name SWAP $volume TCLPROG
PATHMON Environment Control Commands SET PATHWAY Command OWNER ownerid is the user ID allowed to issue PATHCOM commands that directly alter the state of the PATHMON-controlled objects. The user ID must be known to the system in which PATHCOM is running. Use this attribute in conjunction with the SECURITY attribute. The value of ownerid is one of these: [ \system-number | \*.] group-number, user-number [ \node | \* .] group-name .
PATHMON Environment Control Commands Example “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 “U”. Caution. If the owner of this system is the super ID, allowing the security to default to “N” results in a security risk for your system.
PATHMON Environment Control Commands • SHUTDOWN Command (Old) Initiates the FREEZE and STOP for all server classes that PATHMON controls; stops the terminals and Pathway/iTS TCPs; writes the internal configuration and directory information to the PATHMON configuration file; and stops the PATHMON process itself. If a server process is engaged in a dialog at the time the SHUTDOWN command is issued, the shut down process waits until the dialog has completed.
PATHMON Environment Control Commands SHUTDOWN2 Command SHUTDOWN2 Command The SHUTDOWN2 command stops the PATHMON-controlled objects. Use the SHUTDOWN2 command to stop the Pathway environment in one of three ways. The three ways are progressively more forceful. The SHUTDOWN2 command cannot be reversed; in other words, once you have initiated the shutdown process, you cannot stop that process. Note. In previous releases of Pathway, the only shutdown command available was the SHUTDOWN command.
PATHMON Environment Control Commands SHUTDOWN2 Command STATUS specifies whether status information is to be displayed during a shutdown. If you omit this attribute, the default is QUIET. QU or QUIET causes PATHCOM not to display any messages until the shutdown request completes. After the shutdown request is completed, PATHCOM displays the results of the shutdown. AG or AGGREGATE causes PATHCOM to display the Pathway environment status every 20 seconds while shutdown is executing.
SHUTDOWN2 Command PATHMON Environment Control Commands Escalating the Shutdown Process Once you have issued a SHUTDOWN2 command with MODE ORDERLY or MODE ABORT, you can escalate the shutdown process by pressing the Break key and entering a more forceful SHUTDOWN2 option.
PATHMON Environment Control Commands • • START PATHWAY Command Upon successful completion of the shutdown process, the PATHMON process is stopped. For more information on strategies for shutting down a Pathway environment, see Starting and Stopping a PATHMON Environment on page 2-1. Examples This command causes PATHCOM to stop all processes controlled by the PATHMON process.
PATHMON Environment Control Commands STATUS LINKMON Command If a configuration file already exists, the PATHCOM process notifies the operator. The operator can either continue the START PATHWAY COLD command or abort it in preparation for cool starting the environment. ! specifies that the command is to be executed without any warnings or prompts. When used with COLD, the PATHMON process writes over the existing PATHMON configuration file with the current configuration information.
STATUS LINKMON Command PATHMON Environment Control Commands OUT list-file directs output to the file that you specify; this could be a DEFINE name. If you omit this option, the PATHMON process writes the output to the PATHCOM list file; this is typically the home terminal. L\node.$process-name specifies the name of the LINKMON process. L identifies the process as a LINKMON process. \node specifies the name of the NonStop system on which the LINKMON process is running.
PATHMON Environment Control Commands STATUS PATHMON Command Display Field Description INFO Additional information regarding the error number. See the error messages listed in Section 13, PATHMON Messages (Numbers 1000-1999) through Section 16, LINKMON Log Messages.
STATUS PATHMON Command PATHMON Environment Control Commands Example 11-2. STATUS PATHMON Display Format PATHMON \node.$process-name-- STATE=pmon-state CPUS pri : PATHCTL (file-state) $pathctl-file-name [ ERROR = num LOG1 [S] [E] (file-state) $log1-file-name [ ERROR = num LOG2 [S] [E] (file-state) $log2-file-name [ ERROR = num REQNUM [A] reqnum . . . FILE type . . . PID pid . . . PAID paid . . . backup ] ] ] WAIT wait-cause . . .
STATUS PATHMON Command PATHMON Environment Control Commands Display Field Description FILE Requester type. Possible values are: LINKMON LOG waiting. PATHCOM TCP EXT TCP SYS The requester is a LINKMON process. The task that writes log messages to the log file. This is always reqnum = 0 and is displayed only if the task is The requester is a PATHCOM process. The requester is a TCP running in this Pathway environment. The requester is a TCP running in another Pathway environment.
PATHMON Environment Control Commands STATUS PATHWAY Command STATUS PATHWAY Command Use the STATUS PATHWAY command to display the number of PATHMON-controlled objects that are in each possible state. This command provides an overview of the Pathway environment. You can also use the STATUS PATHWAY command with the SHUTDOWN2 command to monitor the progress of a Pathway environment shutdown. STATUS [ / OUT list-file /] PATHWAY , option [ , option] ...
STATUS PATHWAY Command PATHMON Environment Control Commands Example 11-3.
Example PATHMON Environment Control Commands Example 11-5.
SWITCH PATHMON Command PATHMON Environment Control Commands Consideration All processes started by the PATHMON process and still running when the STOP PATHMON command completes successfully are orphaned. To avoid orphaned processes, first use the STATUS PATHWAY command, before executing the STOP PATHMON command, to determine what type of processes are running. Use the STATUS command on each type of object to find the names of the active processes, then stop each process.
PATHMON Environment Control Commands SWITCH PATHMON Command ° The processor in which the PATHMON primary or backup process is executing fails. ° ° A PATHCOM SWITCH command is executed. A CONTROL PATHMON BACKUPCPU command is executed. When the PATHMON process does not delay the creation of a backup process, it resets its internal counter. Consequently, creation of a backup process has to fail ten more times before the PATHMON process delays creating the backup process.
PATHMON Environment Control Commands SWITCH PATHMON Command NonStop TS/MP System Management Manual—541819-001 11 -36
12 SERVER Commands This section describes the PATHCOM commands that define and control SERVER objects; the commands are listed in alphabetic order.
ALTER SERVER Command SERVER Commands server-attribute specifies an attribute describing a server class. A server class attribute consists of a keyword and a value. The value you enter overrides the value previously established with the SET SERVER command. Use any of the attributes listed for the SET SERVER command. All attributes specified must be consistent with the process type defined for the server class.
ALTER SERVER Command SERVER Commands server-class specifies the name of a previously defined and added server class. server-attribute specifies an attribute describing a server class. A server class attribute consists of a keyword and a value. The value you enter overrides the value previously established with the SET SERVER command. Use any of the attributes listed for the SET SERVER command. All attributes specified must be consistent with the process type defined for the server class.
ALTER SERVER Command SERVER Commands Consideration For information on altering associative servers, see the discussion of associative servers in Section 5, Maintaining a PATHMON Environment.
DELETE SERVER Command SERVER Commands DELETE SERVER Command Use the DELETE SERVER command to remove a server class description from the PATHMON configuration file. All servers in the server class must be stopped before the PATHMON process can delete a SERVER object. DELETE [SERVER] { server-class } { ( server-class [ , server-class ]... ) } server-class specifies the name of a SERVER object.
FREEZE SERVER Command SERVER Commands ! prohibits all link managers from sending requests to a server class; the SCREEN COBOL STOP-MODE special register value is ignored. WAIT directs the PATHMON process to complete this command pending acceptance by the link managers of the communication freeze on the server class. This option allows you to monitor the freeze operation as it takes place. The PATHMON process attempts to freeze each server class and reports on each one as frozen or pending freeze.
INFO SERVER Command SERVER Commands This command immediately freezes all the server classes in the Pathway environment: FREEZE SERVER * ! This command freezes all the server classes in the system and waits until all terminals are frozen to complete the command: FREEZE SERVER *, WAIT INFO SERVER Command Use the INFO SERVER command to display the attribute values defined in the PATHMON configuration file for a server class.
INFO SERVER Command SERVER Commands These attributes are displayed for all server classes: PROCESSTYPE HIGHPIN OWNER AUTORESTART HOMETERM PRI CREATEDELAY LINKDEPTH PROGRAM DEBUG MAXSERVERS SECURITY DELETEDELAY NUMSTATIC TMF VOLUME If PROCESSTYPE is GUARDIAN, these attributes are displayed only if they have values defined: ASSIGN IN PROCESS DEFINE OUT STARTUP GUARDIAN-LIB PARAM If PROCESSTYPE is OSS, these attributes are displayed only if they have values defined: ARGLIST ENV STDER
INFO SERVER Command SERVER Commands This command: INFO SERVER CLASS-1, OBEYFORM returns these screen display: RESET SERVER SET SERVER PROCESSTYPE GUARDIAN SET SERVER AUTORESTART 0 SET SERVER CPUS (2:1,3:2,0:1) SET SERVER CREATEDELAY 1 MINS SET SERVER DEBUG OFF SET SERVER DEFINE =EMP, CLASS MAP, FILE \SYS.$D.APPL.EMP SET SERVER DELETEDELAY 10 MINS SET SERVER HIGHPIN OFF SET SERVER HOMETERM \*.$TERM SET SERVER LINKDEPTH 1 SET SERVER MAXSERVERS 5 SET SERVER NUMSTATIC 2 SET SERVER OWNER \TS.
RESET SERVER Command SERVER Commands RESET SERVER Command Use the RESET SERVER command to change the values for server class attributes from the ones you defined with the SET SERVER command to the default values. This command does not change the attributes of a server class already added to the PATHMON configuration file. RESET SERVER [ server-keyword [ , server-keyword ]...
RESET SERVER Command SERVER Commands This command deletes all of the file assignments for the server class: RESET SERVER ASSIGN This command resets a specific DEFINE definition: RESET SERVER DEFINE =employee This command resets the values for the specified attributes: RESET SERVER CREATEDELAY,MAXSERVERS NonStop TS/MP System Management Manual—541819-001 12 -11
SET SERVER Command SERVER Commands SET SERVER Command Use the SET SERVER command to define values for server class attributes. Use this command before using the ADD SERVER command. SET SERVER server-attribute [ , server-attribute ]... server-attribute is: PROCESSTYPE { GUARDIAN | OSS } ARGLIST argument [,...] ASSIGN logical-unit , assign-spec AUTORESTART number CPUS { ( primary:backup [, primary:backup ]...) | ( cpu [ , cpu ]...
SET SERVER Command SERVER Commands logical-unit is: { [ program-unit . ] } logical-file-name { * . } assign-spec is: [ file-name ] [ [ file-name ] , create-spec ...
SET SERVER Command SERVER Commands All other SERVER object attributes describe both Guardian and OSS server processes. For information about configuration limits, also see Appendix C, Configuration Limits and Defaults. PROCESSTYPE GUARDIAN | OSS specifies the type of servers in the server class. GUARDIAN All servers in this server class are Guardian processes. OSS All servers in this server class are OSS processes. If you omit this attribute, the default is GUARDIAN.
SET SERVER Command SERVER Commands you enter the command as follows: SET SERVER ARGLIST "arg 1", """Argument2""", argument3, "argument ""4""" & Note. Due to the extra characters required by PATHCOM to embed blanks, quotes, commas, and semicolons, it is possible for the input buffer to be larger than the 24,000-character maximum. In such cases, PATHCOM allows 500 additional bytes in the input buffer.
SET SERVER Command SERVER Commands * replaces program-unit for the server with the file name specified in the PROGRAM attribute. 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.
SET SERVER Command SERVER Commands AUTORESTART number specifies the number of times that the PATHMON process attempts to restart a server process within a fixed 10-minute interval after an abnormal termination, such as a call to the Guardian ABEND procedure. number can be a value from 0 through 32,767. If you omit this attribute, the default is 0.
SET SERVER Command SERVER Commands Only Guardian server processes can be run as NonStop processes. Therefore, for Guardian server processes only, the PATHMON process passes to the server process a PARAM message containing BACKUPCPU filled in with a 3-byte ASCII representation of the processor number of the backup processor. Use the GETBACKUPCPU procedure to retrieve the backup processor number from the PARAM message. (For more information on the GETBACKUPCPU procedure, see the COBOL Reference Manual.
SET SERVER Command SERVER Commands If you omit this attribute in the SET command, relative OSS pathnames are resolved using the default directory specified by the CMDCWD command. If no value is set for this attribute via either command, there is no default. This attribute is valid for OSS server processes only. Use the OSS getcwd() function to obtain the name of the current working directory. DEBUG { ON | OFF } specifies whether the server processes in this server class enter debug mode when starting.
SET SERVER Command SERVER Commands DELETEDELAY number { HRS | MINS | SECS } specifies the maximum amount of time a link between a link manager, such as a LINKMON process or TCP, and a dynamic server process in a server class can remain idle before the link manager automatically returns the link to the dynamic server. number must be a value within one of these ranges: 0 through 16,383 SECS 0 through 1092 MINS 0 through 18 HRS If you omit this attribute, the default is 10 MINS.
SET SERVER Command SERVER Commands In addition, environment variable names (name) cannot contain an equal sign (=). (The first equal sign PATHCOM encounters is used as the delimiter for the environment variable name.) However, an equal sign can be included in the value. For example, to specify an environment variable named env1 having a value of abc=cba, enter the command as follows: SET SERVER ENV env1=abc=cba For a discussion of when to use parentheses, see the subsection Command Format on page 8-5.
SET SERVER Command SERVER Commands HIGHPIN { ON | OFF } specifies whether the server process runs at a high PIN or a low PIN: ON The server process runs at a high PIN. OFF The server process runs at a low PIN. If you omit this attribute, the default is OFF. To run a server at a high PIN, you must also set the ?HIGHPIN compiler directive in your server source code file. For more information about the ?HIGHPIN compiler directive, see the appropriate programming language reference manual.
SET SERVER Command SERVER Commands LINKDEPTH number specifies the maximum number of concurrent links that any one link manager, such as the LINKMON process or a TCP, can have to a given server process before the PATHMON process directs that link manager's link requests to another server within the server class. The value of LINKDEPTH should not exceed the value of MAXLINKS and cannot exceed 255. In the unlikely event that if MAXLINKS is set to 0, the value of LINKDEPTH should be set to 1.
SET SERVER Command SERVER Commands This attribute is valid for Guardian and OSS server processes. MAXSERVERS number specifies the maximum number of server processes in this server class that can run at the same time. number must be a value from 0 through 4095. If you omit this attribute, the default is 1.
SET SERVER Command SERVER Commands command descriptions in CMDVOL Command on page 10-3 and SET PATHWAY Command on page 11-12. If you omit this attribute, spaces are passed to the servers for the file name. This attribute is valid for Guardian server processes only. OWNER ownerid specifies the user ID that controls access from a Pathsend process to a server class. (The TCPs ignore this server attribute.) The user ID must be known to the system in which PATHCOM is running.
SET SERVER Command SERVER Commands may be less because all individual PARAMs for a server are collected into a single PARAM message, limited in length to 1028 bytes. For more information about PARAM messages, see the Guardian User’s Guide. For more information about this parameter, see the COBOL Reference Manual. This attribute is valid for Guardian server processes only. PRI priority specifies the priority at which the servers of this server class run. priority can be a value from 1 through 199.
SET SERVER Command SERVER Commands If you omit this attribute, the default is OFF. ON allows the PATHMON process to grant links to the server process, even if a server by the same name already exists. A START SERVER command is successful. OFF does not allow the PATHMON process to grant links to the server process if a server by the same name already exists. A START SERVER command fails.
SET SERVER Command SERVER Commands PRI number specifies the priority at which the server process runs. See the description of the PRI attribute earlier in this command. PROGRAM file-name | oss-pathname specifies the name of the object file to be used by the servers in this server class. For Guardian processes, specify a Guardian file name. PATHCOM validates the file name when the SET SERVER command is issued.
SET SERVER Command SERVER Commands 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. This attribute is valid for Guardian server processes only.
SET SERVER Command SERVER Commands TIMEOUT number { HRS | MINS | SECS } specifies the timeout value that a link manager such as a LINKMON process or TCP uses for the I/O operation to the server process. TIMEOUT must be a value from 0 through 18 HRS, 0 through 1092 MINS, or 0 through 16,383 SECS. If you omit this attribute, there is no timeout on the server I/O operation. That is, the link manager waits indefinitely for the server I/O operation to complete.
Server Class DEFINEs SERVER Commands Defaults for file name expansion are based on values you specify for the CMDVOL command and the SET PATHWAY NODEINDEPENDENT attribute. See the command descriptions in CMDVOL Command on page 10-3 and SET PATHWAY Command on page 11-12. This attribute is valid for both Guardian and OSS server processes. For more information on _DEFAULTS DEFINE, see Server Class DEFINEs on page 12-31.
Server Class DEFINEs SERVER Commands When resolving relative OSS pathnames, the value defined by the SET SERVER CWD command takes precedence. The RESET SERVER command resets this value to null. The value defined by the CMDCWD command is used to resolve relative OSS pathnames only if no value has been set using the SET SERVER CWD command. It is a default absolute pathname that you can define for a server class. The RESET SERVER command has no effect on this value.
SHOW SERVER Command SERVER Commands SET SERVER OUT \*.$RM123 ADD SERVER SERV-ABC Note that in the above example, the generic node name \* is specified for the node names for the ASSIGN, OWNER, IN, and OUT file names. The \* name designates the node where the PATHMON process is currently running. In this example, the OWNER, IN, and OUT file names are stored in the PATHMON configuration file using \* as the node name, making these attributes node-independent.
SHOW SERVER Command SERVER Commands OUT list-file directs output to the named list file; this could be a DEFINE name. If this option is omitted, the PATHMON process directs the output to the PATHCOM list file; this is typically the home terminal. Display Formats When PATHCOM first starts or after a RESET SERVER command is issued, the SHOW SERVER command displays only the required SET SERVER command attributes and the server class default values.
START SERVER Command SERVER Commands Additional Attributes Displayed These Guardian attributes are displayed only if they have values defined: ASSIGN OUT DEFINE PARAM GUARDIAN-LIB PROCESS IN STARTUP These OSS attributes are displayed only if they have values defined: ARGLIST GUARDIAN-LIB CWD PROCESS DEFINE STDERR ENV STDIN STDOUT The CWD attribute is displayed when a value is set either by the CMDCWD command or by the SET SERVER CWD command.
Examples SERVER Commands PROCESS $process-name specifies the name of a single server in the server class. SERVER * starts all server classes in the PATHMON configuration file and in the correct state. Considerations • • The START SERVER command starts the number of servers defined by the SET SERVER NUMSTATIC attribute for the server class. For information on starting associative servers, see “Associative Servers” under SET SERVER Command earlier in this section.
STATS SERVER Command SERVER Commands This command starts only the static server processes defined for the named server classes: START SERVER (IMF-CLASS, ORD-SRV, MFG-SRV) This command starts a single process named $SLIB in the server class IMF-CLASS: START IMF-CLASS, PROCESS $SLIB STATS SERVER Command Use the STATS SERVER command to display resource usage and performance statistics, including response time information.
STATS SERVER Command SERVER Commands server-class specifies the name of a previously defined and added server class. Use either a single name or several names separated by commas and enclosed in parentheses. SERVER * displays statistics for all server classes in the PATHMON configuration file. COUNT number specifies the number of times that the STATS command repeats. You can stop the command from repeating by pressing the Break key.
STATUS SERVER Command SERVER Commands Examples This command displays statistical information gathered about the specified server class, eight times, at one-hour intervals: STATS CLASS-1, COUNT 8, INTERVAL 1 HRS This command collects statistical information about all of the server classes for four times, at 15-minute intervals, and directs the information to a specified file: STATS /OUT STATFLE/ SERVER *, RESET, INTERVAL 15 MINS, COUNT 4 STATUS SERVER Command Use the STATUS SERVER command to display the c
STATUS SERVER Command SERVER Commands DETAIL includes status information on the servers processes associated with the specified server class. FREEZE displays the names of the server classes in the FROZEN or FREEZEPENDING state. For each server class that is in the FREEZEPENDING state, the names of the terminals that have not yet accepted the freeze of the server class are also listed. The PATHMON process does not report FREEZE information about external link managers such as LINKMON processes.
STATUS SERVER Command SERVER Commands Display Field Description INFO For additional information regarding the error number, see the error messages listed in Section 13, PATHMON Messages (Numbers 1000-1999) through Section 16, LINKMON Log Messages. The freeze-state may also be displayed. Possible values are: FREEZE-PENDING The server class received a FREEZE command, but the state of one or more terminals delays the freeze from completing.
STATUS SERVER Command SERVER 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 processes. RUNNING The server process is running. PENDING The last link was returned but the server process has not yet stopped.
STATUS SERVER Command SERVER Commands The additional fields returned in this display are as follows: Display Field Description LINKER Name of a link manager, such as a LINKMON process, that is currently linked to the server. LINKMON process names have the format: L\node.$process-name LINK COUNT L Identifies the process as a LINKMON process. \node Name of the NonStop systemNonStop system on which the LINKMON process is running. $processname LINKMON process name.
STATUS SERVER Command SERVER Commands Display Field Description FREEZE STATE State of the server class. Possible values are: FREEZE-PENDING The server class received a FREEZE command, but the state of one or more terminals delays the freeze from completing. FROZEN The server class is frozen. No communication can take place with any server of the server class until the class receives a THAW command. TERM Name of a terminal that prevents the server class from becoming frozen.
STOP SERVER Command SERVER Commands This commands display status information about the specified frozen server classes, and include various options: STATUS /OUT STATFLE/SERVER CLASS-1,FREEZE STATUS SERVER CLASS-2,FREEZE STATUS CLASS-3,FREEZE This command displays the names of terminals that have not yet accepted the freeze condition for all server classes: STATUS SERVER *, FREEZE This command displays the names of all server classes that are in a FROZEN or FREEZE-PENDING state: STATUS FREEZE STOP SERVER
THAW SERVER Command SERVER Commands PATHMON process stops the OSS server class, the executed process may become an orphan process. • For information on stopping associative servers, see Maintaining Associative Server Processes on page 5-32.
THAW SERVER Command SERVER Commands Considerations • • After the PATHMON process thaws a server class, the PATHMON process allows Pathsend requesters access to the thawed server classes. For SCREEN COBOL requesters without an ON ERROR clause, the TCP resumes the operation by executing the send request. (When SCREEN COBOL requesters containing an ON ERROR clause encounter a frozen server class, they perform as directed by the ON ERROR code.
SERVER Commands THAW SERVER Command NonStop TS/MP System Management Manual—541819-001 12 -48
13 PATHMON Messages (Numbers 1000-1999) This section describes the messages generated by the PATHMON process. General Information All messages returned by the PATHMON environment are logged by the PATHMON process; however, messages in some number ranges represent errors reported to the PATHMON process by other processes.
PATHMON Messages (Numbers 1000-1999) Operating System Error Numbers For example: ERROR - *1048* TERM TERM-1, SUSPENDED: *3117* SERVER CLASS UNDEFINED --- INST CODE: SEND AT OFFSET %37 IN PROGRAM UNIT PROG-X(1) IN TCLPROG \SYS.$VOL.SUBVOL.POBJ Note. The additional information on terminal errors, which is appended to the standard error message text, significantly increases the size of messages sent to a log file.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. None Recovery. Informational message only; no corrective action is needed. 1004 *1004* ALREADY STOPPED Cause. The named entity is already stopped. Effect. None Recovery. Informational message only; no corrective action is needed. 1005 *1005* PATHMON, SHUTDOWN Cause. The PATHMON environment has been successfully shut down. Effect. None Recovery. Informational message only; no corrective action is needed. 1006 *1006* PATHMON, ABENDED Cause.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 1007 *1007* link manager-name, CAN'T GRANT LINK : < nested-message > Cause. A server class link cannot be granted to a LINKMON process or a TCP . Effect. The Pathsend statement or SEND operation fails. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. Configure the PATHMON environment. 1011 *1011* link manager-name, DELINK FAILURE : < nested-message > Cause. An error occurred while a TCP or LINKMON process was trying to return a link to a server class. The nested message indicates the reason for the failure. Effect. The effect depends on the reason for the failure. Recovery. For additional information, see the description associated with the nested message.
PATHMON Messages (Numbers 1000-1999) • • PATHMON Messages 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 Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 1014 *1014* ENTRY IN USE (LOCKED) Cause.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 1018 *1018* SERVER server-name, SERVER FILE ERROR (errnum) Cause. A file-system error (errnum) occurred during an I/O operation to the specified server class. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 1022 *1022* PATHMON, RECEIVE FILE ERROR (errnum) Cause. A file-system error (errnum) occurred during an I/O operation to $RECEIVE. Effect. The effect depends on the file-system error that occurred. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1027 *1027* PATHMON, LOG1 FILE CLOSED Cause. The LOG1 file is closed. Effect. None Recovery. Informational message only; no corrective action is needed. 1028 *1028* PATHMON, LOG1 FILE OPENED Cause. The LOG1 file is open. Effect. None Recovery. Informational message only; no corrective action is needed. 1029 *1029* PATHMON, LOG2 FILE CLOSED Cause. The LOG2 file is closed. Effect. None Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. Define the required attribute. For details about the required attributes for those commands, see the SET PATHMON and the SET PATHWAY commands. 1032 *1032* PATHCTL FILE IS FULL Cause. An entry cannot be added because the PATHMON configuration file is full. This is an internal error. Effect. Entries cannot be added until the configuration file is available. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The requesting TCP or LINKMON process is not linked to the server class. Recovery. Increase the value of the MAXSERVERS, MAXLINKS, or LINKDEPTH attribute in the server class definition. (It is not recommended that you set LINKDEPTH higher than 1 for servers other than communications-based servers, such as HLS servers.) 1035 *1035* object-name, NO SUCH ENTRY Cause. The specified entry does not exist.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1038 *1038* {SERVER server-name | TCP tcp-name} PROCESS CREATION FAILURE: err-text Cause. An error occurred during the creation of a new process for the indicated server or TCP. err-text identifies a process-creation error and provides detail concerning the problem. Effect. The new process is not created. Recovery. For additional information, see the description of the PROCESS_CREATE_ procedure in the Guardian Procedure Calls Reference Manual.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1042 *1042* TERM term-name, RESUMED Cause. The indicated terminal has resumed processing. Effect. None Recovery. Informational message only; no corrective action is needed. 1043 *1043* object-name, STARTED Cause. The specified object has started. Effect. None Recovery. Informational message only; no corrective action is needed. 1045 *1045* REQUEST NOT VALID FOR CURRENT STATE Cause.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The effect depends on the application and what type of object stopped. Recovery. For additional information, see the description associated with the nested message. 1048 *1048* TERM term-name, SUSPENDED : < nested-message > Cause. The specified terminal suspended processing due to an error in the program. The reason for the error is indicated in the nested message. Effect.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1051 *1051* TCP tcp-name, EXCEEDS THE LIMIT ON PATHMON OPENERS. Cause. The internal limit on the total number of concurrent openers of the PATHMON process would be exceeded by opening this TCP for communication with the PATHMON process at this time. Effect. The PATHMON process cannot communicate with the TCP or LINKMON process. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages After correcting the cause of the failure, restart the TCP (this step is not needed if AUTORESTART is specified for the TCP). A LINKMON process failure requires you to reload the processor.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. None Recovery. Informational message only; no corrective action is needed. 1059 *1059* FREEZE PENDING Cause. A freeze request has been accepted and will complete when all link managers pass a message to the PATHMON process that the server class is frozen. Effect. None Recovery. Informational message only; no corrective action is needed. 1060 *1060* NOT FROZEN Cause.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1063 *1063* MUST BE THAWED Cause. A START SERVER command was issued before the server class was thawed. Effect. The command fails. Recovery. Reissue the command after the server class is thawed. 1064 *1064* SERVER server-name, FROZEN Cause. The specified server class is frozen. Effect. None Recovery. Informational message only; no corrective action is needed. 1065 *1065* SERVER server-name, THAWED Cause. The specified server class is thawed. Effect.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The effect depends on the error. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The PATHMON process runs without a backup. Recovery. For additional information, see the description associated with the nested message. 1073 *1073* PATHMON, CHECKOPEN FAILURE (%errnum) Cause. An error occurred during an operating system CHECKOPEN operation. The error number identifies the CHECKOPEN error code. Effect. The primary file is closed. Any additional effect depends on the file that was being opened. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The PATHMON process terminates. If the DUMP attribute is enabled, the PATHMON process creates a dump file before terminating. Recovery.
PATHMON Messages (Numbers 1000-1999) %p-reg is the program counter register %e-reg is the environment register %l-reg is the local register PATHMON Messages Effect. The PATHMON process terminates. If possible, it creates a dump file. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1085 *1085* PATHMON MUST NOT RUN WITH HIGHPIN SET Cause. You attempted to set the HIGHPIN attribute to ON for the PATHMON process. Effect. The PATHMON process cannot run. Recovery. Reset the HIGHPIN attribute to OFF and reissue the START command. 1086 *1086* TERM TYPE NOT DEFINED FOR PROGRAM Cause. The TYPE parameter of the RUN PROGRAM command is undefined or mismatched, or the PROGRAM definition has not been added. Effect. The operation fails.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The terminal’s operation is aborted. Recovery. Check the PATHMON process log file for the Pathway and Guardian error encountered. 1090 *1090* SECURITY VIOLATION Cause. The requesting user failed the security check for the operation on the PATHMON-controlled object. Effect. The user is prohibited from performing unauthorized actions on the object. Recovery. Informational only; no corrective action is required.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The PATHMON process creates a backup process, if possible. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1101 *1101* TERM term-name, TOO MANY TERM ENTRIES Cause. The number of terminal descriptions has reached the maximum value specified for the MAXTERMS attribute or the MAXPROGRAMS attribute of the SET PATHWAY command. Effect. The ADD TERM or RUN PROGRAM command fails. Recovery. Increase the value of the MAXTERMS attribute and reissue the ADD TERM command; or, increase the value of the MAXPROGRAMS attribute and reissue the RUN PROGRAM command.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. Increase the value of the MAXSTARTUPS attribute and reissue the ADD SERVER or ALTER SERVER command. 1105 *1105* SERVER server-class, TOO MANY ASSIGN ENTRIES Cause. The number of ASSIGN definitions has reached the maximum value specified for the MAXASSIGNS attribute of the SET PATHWAY command. Effect. The ADD SERVER or ALTER SERVER command fails. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. Increase the value of the MAXPROGRAMS attribute and reissue the ADD PROGRAM command. 1109 *1109* TOO MANY DEFINE ENTRIES Cause. An attempt was made to add a DEFINE definition to a server class, but the total number of DEFINEs for all server classes has reached the maximum value specified for the MAXDEFINES attribute. Effect. The ADD SERVER or ALTER SERVER command fails. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1115 *1115* TCP tcp-name, TCP REFRESHED Cause. The TCP has read the requested program unit code segment into memory after checking the SCREEN COBOL object directory file. Effect. The TCP uses the latest version of each program unit. Recovery. Informational message only; no corrective action is needed. 1116 *1116* CHECK-DIRECTORY ON FOR TCP; REFRESH-CODE IGNORED Cause.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1119 *1119* TERM term-name, AUTO ABORTED Cause. The specified suspended terminal automatically aborted before being restarted with AUTORESTART. Effect. The terminal abends. Recovery. Informational message only; no corrective action is needed. 1120 *1120* object-name, AUTORESTARTED Cause. After a failure, AUTORESTART restarted the specified object. Effect. None Recovery. Informational message only; no corrective action is needed.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1123 *1123* PATHMON, MEMORY DUMP NOT TAKEN (internal-condition) Cause. An attempt to perform a PATHMON memory dump failed; generally, a dump file already exists. This is an internal error. Effect. No dump file is created. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. For information concerning the specified USESEGMENT error, see the Guardian Procedure Errors and Messages Manual. 1126 *1126* PATHMON CANNOT EXECUTE ON THIS RELEASE OF THE NONSTOP KERNEL Cause. The PATHMON process uses the extended memory feature of the NonStop operating system. In addition, the PATHMON process uses features available in release C20 of the HP NonStop operating system.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. Any PATHMON logs open with EVENTFORMAT are closed as a result of this error. Recovery. For information concerning the EMSINIT error, see the Guardian Procedure Calls Reference Manual. 1137 *1137* EMSADDSUBJECT ERROR (%errnum) Cause. An error occurred, identified by the error number, on a call to the EMSADDSUBJECT procedure. Effect. Any PATHMON logs open with EVENTFORMAT are closed as a result of this error. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1140 *1140* DEFINES SPECIFIED AT PATHMON CREATION ARE IGNORED Cause. You started the PATHMON process specifying DEFINEs other than the _DEFAULTS DEFINE with the VOLUME attribute. Effect. PATHMON ignores any DEFINEs other than the _DEFAULTS DEFINE with the VOLUME attribute. Recovery. Specify a DEFINE message using the SET SERVER DEFINE command. 1141 *1141* SERVER server-name, DEFINE PROCEDURE ERROR (DEFINE-errnum) Cause.
PATHMON Messages (Numbers 1000-1999) • • • • PATHMON Messages Details from the message(s) generated Your PATHMON configuration file and the PATHMON process version 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 Global Customer Support Center (GCSC), supply your system number and the numbers an
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1147 *1147* BACKUP IS INITIALIZED AND RUNNING Cause. The PATHMON backup process is initialized, running, and ready to take over for the primary process, if necessary. Effect. None Recovery. Informational message only; no corrective action is needed. 1148 *1148* MAXIMUM NUMBER OF WAITED RUN PROGRAM REQUESTS EXCEEDED Cause. An attempt was made to initiate more than 100 waited RUN PROGRAM requests from PATHCOM and from SPI programs. Effect.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 1150 *1150* STARTING SHUTDOWN - Cause. The shutdown process has started in the indicated mode. Effect. None Recovery. Informational message only; no corrective action is needed. 1151 *1151* PATHMON STOPPED Cause. The STOP PATHMON command was issued. Effect.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages 1154 *1154* SHUTDOWN REQUEST TIMED OUT Cause. The shutdown operation has not completed, but the time specified by the TIMEOUT attribute has expired. Effect. None Recovery. Informational error message; no corrective action is needed. 1155 *1155* SHUTDOWN FAILED Cause. An object in the PATHMON environment, such as a server class, could not be stopped. Effect. The shutdown fails. Recovery.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Effect. The command fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. Cool or cold start the PATHMON objects to make the PATHMON configuration file accessible again. 1158 *1158* PATHMON UNINITIALIZED - DOUBLE FAILURE Cause. The primary PATHMON process has failed and the backup PATHMON process has not been fully initialized. Effect.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages about PROCESS_SPAWN_ codes, see the Guardian Procedure Errors and Messages Manual. 1160 *1160* OSS NOT AVAILABLE ON THIS SYSTEM Cause. This PATHMON environment does not support OSS server processes. Effect. The configured OSS server processes cannot be started. Recovery. Call your HP representative to inquire about installing OSS support features on your system. 1161 *1161* SERVER CLASS DOES NOT MATCH REQUESTED PROCESSTYPE Cause.
PATHMON Messages (Numbers 1000-1999) PATHMON Messages Recovery. Either the NonStop TS/MP product or the Pathway/iTS product must be licensed before the PATHMON process can start an application. If you believe you have secured a license for the NonStop TS/MP or Pathway/iTS product, perform: 1. Confirm that one or both licensing files–ZLICA58 (NonStop TS/MP) or ZLICSA59 (Pathway/iTS) are located in the $SYSTEM.ZPATHWAY subvolume. 2. Confirm that the files located in $SYSTEM.
PATHMON Messages (Numbers 1000-1999) NonStop TS/MP System Management Manual—541819-001 13 -44 PATHMON Messages
14 PATHCOM Messages (Numbers 2000-2999) This section lists the messages generated by PATHCOM.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages PATHCOM Messages These messages are returned by PATHCOM: 2001 *2001* TERM term-name, ABORTED Cause. The specified terminal was aborted. Effect. None Recovery. Informational message only; no corrective action is needed. 2002 *2002* ABORT FAILURE Cause. An abort request failed. Effect. None Recovery. Determine the cause for the failure and reissue the abort request. 2003 *2003* PATHMON NOT OPEN Cause. The PATHMON process is not open. Effect.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2008 *2008* ILLEGAL CONFIGURATION VALUE Cause. The value specified for an attribute is not within the valid range for that attribute. Effect. The command fails. Recovery. Respecify the unacceptable attribute value using a value in the valid range for that attribute. 2009 *2009* ILLEGAL CPU NUMBER Cause. The processor number is not in the range 0-15, or the same processor number is defined for the object’s primary and backup processes. Effect.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2012 *2012* ILLEGAL PRIORITY VALUE {0:255} Cause. The priority value entered is not in the 0-255 range. Effect. The command fails. Recovery. Enter a valid priority value. 2013 *2013* ILLEGAL SYNTAX Cause. The sequence of input characters did not conform to the language syntax. Effect. The command fails. Recovery. Reenter the input characters using the correct syntax. 2014 *2014* ILLEGAL TIME VALUE Cause.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages This information is invaluable for the support staff to be able to understand the problem and help fix the problem. 2016 *2016* INVALID REPLY FROM PATHMON Cause. A reply was received that does not comply with the NonStop TS/MP internal interprocess message protocol. This error can be caused by: • • • Running incompatible versions of PATHCOM and the PATHMON process. PATHCOM attempting communication with a process that is not a PATHMON process.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2019 *2019* NO INTERNAL FREESPACE AVAILABLE Cause. No free space is available in the PATHCOM internal data area. Effect. The operation fails. Recovery. Contact your Global Customer Support Center (GCSC).
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2022 *2022* TERM term-name RESUMED Cause. The named terminal has resumed operation. Effect. None Recovery. Informational message only; no corrective action is needed. Note. You will receive this message only if you are using the Pathway/iTS product. 2024 *2024* object-name STARTED Cause. The named object is running. Effect. None Recovery. Informational message only; no corrective action is needed. 2027 *2027* object-name STOPPED Cause.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages Recovery. Informational message only; no corrective action is needed. 2031 *2031* TCP tcp-name SWITCHED Cause. The primary and backup processes of the named TCP exchanged operation in response to a TCP SWITCH command. Effect. The command completed successfully. Recovery. Informational message only; no corrective action is needed. Note. You will receive this message only if you are using the Pathway/iTS product. 2032 *2032* TABLE OVERFLOW Cause.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2034 *2034* SERVER server-name THAWED Cause. The named server class is thawed. Effect. None Recovery. Informational message only; no corrective action is needed. 2035 *2035* TOO MANY NESTED OBEY FILES (MAX=4) Cause. The number of nested command files exceeded the maximum depth of 4. Effect. The command fails. Recovery. Rewrite the command files with 4 or less nested files. 2036 *2036* TOO MANY CPU PAIRS SPECIFIED (MAX=16) Cause.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages Recovery. Reduce the number of PARAM messages. 2040 *2040* PATHCOM TRAP T = %trap S = %s-reg P = %p-reg E = %e-reg L = %l-reg Cause. PATHCOM is trapped because of a hardware or software failure. These values reflect the process environment at the time PATHCOM failed: %trap is the number of the trap. %s-reg is the stack register. %p-reg is the program counter register. %e-reg is the environment register. %l-reg is the local register. Effect.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2042 *2042* THIS FORM OF PROCESS NAME NOT ALLOWED Cause. The process name contained more than five characters including the dollar sign ($). Effect. The command fails. Recovery. Reenter the process name with the correct amount of characters. 2043 *2043* ILLEGAL SECURITY ATTRIBUTE Cause. The value specified for a security attribute was invalid. Effect. The command fails. Recovery. Enter the correct security attribute.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages Recovery. Reenter the command in interactive mode. 2048 *2048* ILLEGAL TERM TYPE SPECIFICATION Cause. The value specified for TERM TYPE is invalid. Effect. The command fails. Recovery. Enter a correct value for TERM TYPE. Note. You will receive this message only if you are using the Pathway/iTS product. 2049 *2049* NUMSTATIC EXCEEDS MAXSERVERS Cause.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2054 *2054* TCP tcp-name PRIMARIED Cause. The primary process is running in its configured processor. Effect. The PRIMARY TCP command completed successfully. Recovery. Informational message only; no corrective action is needed. 2056 *2056* IN FILE CANNOT RUN NOWAIT Cause.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2058 *2058* RESET NOT ALLOWED FOR THIS PARAMETER Cause. An ALTER command was issued that attempted to reset a required attribute. Effect. The command fails. Recovery. Stop the PATHMON environment, redefine the attribute using the SET command, and restart the PATHMON environment. 2059 *2059* DEFINE PROCEDURE ERROR (DEFINE-errnum) Cause. An error occurred, identified by the error number, in a procedure call to the DEFINE procedure library. Effect.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2061 *2061* DEFINE PARSING AND DISPLAY DISABLED Cause. PATHCOM is not able to parse or display the DEFINE definitions. This error can occur, for example, if one or more of the required DEFINE procedures, such as DEFINESAVE and DEFINERESTORE, are not available. Effect. The DEFINE operation fails. Recovery. Contact your Global Customer Support Center (GCSC).
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2064 *2064* CURRENT PATHMON NAME IS DIFFERENT FROM PATHMON NAME IN PATHCTL FILE. DO YOU WISH TO CONTINUE? Cause. The START COLD command (without the ! option) was issued. Although the PATHCTL file exists and the stored configuration is valid, the PATHMON process name specified in the START command is different from the PATHMON process name stored in the PATHCTL file. Effect.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages Effect. The SET, ADD, or ALTER command fails. Recovery. Define a value for the attribute within the valid range. 2069 *2069* OSS PATHNAME IS INVALID Cause. An OSS pathname in the command is invalid due to a disallowed forward slash (/) or null character. Effect. The attribute value for the OSS server process is not set. Recovery.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2072 *2072* OSS PATHNAME NOT ABSOLUTE OR DOESN’T RESOLVE TO ABSOLUTE PATHNAME: attribute-name Cause. The value specified for the CWD attribute was not an absolute pathname. If no pathname has been defined for the CWD attribute, then the pathname entered for the specified OSS attribute is not an absolute pathname. Effect. If you attempted to set the CWD attribute, the pathname is rejected and the attribute is not set.
15 Link Manager Messages (Numbers 3000-3999) This section describes the messages logged by the PATHMON process on behalf of link managers—the LINKMON process or TCPs. General Information All messages returned by the PATHMON environment are logged by the PATHMON process; however, messages in some number ranges represent errors reported to the PATHMON process by other processes.
Link Manager Messages (Numbers 3000-3999) LINKMON Messages Effect. The operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3116 *3116* link manager-name, ERROR DURING SERVER I/O (errnum) Cause. A file-system error occurred during I/O to a server process. Effect. The I/O operation fails. The link manager unlinks from the server class. Recovery.
Link Manager Messages (Numbers 3000-3999) LINKMON Messages If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 3200 *3200* link manager-name, INVALID FORMAT MESSAGE RECEIVED BY TCP Cause. A LINKMON process or terminal control process (TCP) received an invalid request from the PATHMON process.
Link Manager Messages (Numbers 3000-3999) LINKMON Messages 3226 *3226* link manager-name, REQUESTED FUNCTION NOT SUPPORTED IN THIS RELEASE Cause. The PATHMON process requested a function that is not supported in this version of the LINKMON process. Effect. The operation fails. Recovery. Use a newer version of the LINKMON process. 3233 *3233* link manager-name, SERVER PROCESS UNKNOWN Cause.
16 LINKMON Log Messages This section describes, in alphabetic order, the log messages that a LINKMON process can write to the system log, $0, during LINKMON initialization. General Information The LINKMON process in a processor does not begin initialization until it receives a SERVERCLASS_SEND_ call from a Pathsend process executing in its processor. If an error occurs during LINKMON initialization, the LINKMON process: • • • Returns an error to the application (Pathsend error 947, file-system error).
LINKMON Log Messages LINKMON Log Messages Effect. The LINKMON process is unable to process SERVERCLASS_SEND_ calls. This message is always followed by an EMS message that describes why the LINKMON process could not obtain enough memory. Recovery. Recovery depends on the error that occurs. For example, if the next message is “SEGMENT_ALLOCATE_ error 1 (error detail 43) on swap file $SYSTEM.ZLINKMON.ZZLM04,” you must make additional disk space available before the LINKMON process can initialize itself.
LINKMON Log Messages LINKMON Log Messages Terminating Cause. The LINKMON process has terminated. Effect. The LINKMON process is no longer able to support SERVERCLASS_SEND_ calls in its processor. Recovery. This message is not expected during normal operation. If you receive this message, contact your HP representative. Unable to purge existing swap file swap-file-name (file purge error error-number) Cause.
LINKMON Log Messages LINKMON Log Messages NonStop TS/MP System Management Manual—541819-001 16- 4
A Syntax Summary This appendix contains summaries of the PATHCOM commands described in this manual. All commands are listed in alphabetic order. Note that PATHCOM commands that create or manage Pathway/iTS objects such as TCP, TERM, and PROGRAM objects, are described in Pathway/iTS System Management Manual. ADD SERVER server-class [ , server-attribute ]... ALTER [ SERVER ] server-class { { { { , , , , server-attribute DELETE delete-option RESET server-keyword RESET (server-keyword [ , server-keyword ].
Syntax Summary DELETE [SERVER] { server-class } { ( server-class [ , server-class ]... ) } ERRORS [ number ] EXIT FC FREEZE { [ SERVER ] server-class } { [ SERVER ] (server-class [, server-class ]...
Syntax Summary LOG1 [ file-name [ , logparam [ , logparam ] ] ] LOG2 [ file-name [ , logparam [ , logparam ] ] ] logparam is: STATUS EVENTFORMAT { OBEY } file-name { O } OBEYVOL [ [ [ [ [ \node.] $volume.subvolume ] [ \node.] $volume ] [ \node.] subvolume ] \node ] OPEN [ \node.]$pm-process PATHCOM [ / run-option [ , run-option ]... / ] [ pathmon-name [ ; command [ ; command ]...
Syntax Summary PRIMARY PATHMON [ , IFPRICPU number ] RESET CMDCWD RESET SERVER [ server-keyword [ , server-keyword ]... ] server-keyword is: ARGLIST ASSIGN AUTORESTART CPUS CREATEDELAY CWD DEBUG DEFINE DELETEDELAY ENV GUARDIAN-LIB GUARDIAN-SWAP HIGHPIN HOMETERM IN LINKDEPTH MAXLINKS MAXSERVERS NUMSTATIC OUT OWNER PARAM PRI PROCESS PROCESSTYPE PROGRAM SECURITY STARTUP STDERR STDIN STDOUT TMF VOLUME SET PATHMON , pathmon-attribute [ , pathmon-attribute ]...
Syntax Summary SET PATHWAY pw-attribute [ , pw-attribute ]... pw-attribute is: MAXASSIGNS number MAXPARAMS number MAXSERVERCLASSES number MAXSERVERPROCESSES number MAXSTARTUPS number MAXTCPS number MAXTERMS number MAXDEFINES number MAXEXTERNALTCPS number MAXLINKMONS number MAXPATHCOMS number MAXPROGRAMS number MAXSPI number MAXTELLQUEUE number MAXTELLS number MAXTMFRESTARTS number NODEINDEPENDENT [ON | OFF] OWNER ownerid SECURITY security-attribute Note.
Syntax Summary SET SERVER server-attribute [ , server-attribute ]... server-attribute is: PROCESSTYPE { GUARDIAN | OSS } ARGLIST argument [,...] ASSIGN logical-unit , assign-spec AUTORESTART number CPUS { ( primary:backup [, primary:backup ]...) | ( cpu [ , cpu ]... } CREATEDELAY number { HRS | MINS | SECS } CWD oss-pathname DEBUG { ON | OFF } ( DEFINE define-name , define-attribute-spec [, define-attribute-spec ] ... ) DELETEDELAY number { HRS | MINS | SECS } ENV name=value [ ,...
Syntax Summary SET SERVER (continued) logical-unit is: { [ program-unit . ] } logical-file-name { * . } assign-spec is: [ file-name ] [ [ file-name ] , create-spec ...
Syntax Summary SHUTDOWN2 [, MODE { OR[DERLY] | AB[ORT] | IM[MEDIATE] } ] [, STATUS { QU[IET] | AG[GREGATE] } ] [, UNTIL { DONE } { TIMEOUT number { HRS | MINS | SECS }} ] START PATHWAY { COOL } [!] { COLD } START { [ SERVER ] server-class [ , PROCESS $process-name ] } { [ SERVER ] ( server-class [ , server-class ]... ) } { SERVER * } STATS [ / OUT list-file / ] { [ SERVER ] server-class } { [ SERVER ] ( server-class [ , server-class ]... ) } { SERVER * } [ , server-attribute [ , server-attribute ]...
Syntax Summary STATUS [ / OUT list-file / ] { { { { { { { { { [ SERVER [ SERVER [ SERVER [ SERVER [ SERVER [ SERVER [ SERVER SERVER * FREEZE ] ] ] ] ] ] ] [ name [ , PROCESS $process-name ] name [ , PROCESSES ] name [ , DETAIL ] name [ , FREEZE ] ( name [ , name ]... ) [ , PROCESSES ] ( name [ , name ]... ) [ , DETAIL ] ( name [ , name ]...
Syntax Summary NonStop TS/MP System Management Manual—541819-001 A -10
B PATHCOM Reserved Words This appendix contains a list of words that are reserved and should not be used for variable names in PATHCOM commands. Although it might be possible in some contexts to use words on this list, HP strongly recommends that these words not be used in any user-assigned names.
NonStop TS/MP Environment PATHCOM Reserved Words CWD HELP MAXSERVERS HIGHPIN MAXSPI HOMETERM MAXSTARTUPS HRS MAXTCPS MAXTELLQUEUE I-O MAXTELLS IBM-3270 MAXTERMS IFPRICPU MAXTMFRESTARTS IN MINS INFO MODE INPUT INTELLIGENT NUMSTATIC INTERVAL NODEINDEPENDENT OBEY LIKE OBEYFORM LINKDEPTH OBEYVOL LINKMON OFF LOG1 ON LOG2 OPEN OUT MAXASSIGNS OUTPUT MAXDEFINES OWNER MAXEXTERNALTCPS MAXLINKS PARAM MAXLINKMONS PATHMON MAXPARAMS PATHWAY MAXPATHCOMS POWERONRECOVERY MAXPRO
NonStop TS/MP Environment PATHCOM Reserved Words PROCESSES PROCESS PROCESSTYPE PROGRAM T16-6510 PROTECTED T16-6520 T16-6530 REC T16-6530WP RESET T16-6540 THAW SECS TIMEOUT SECURITY TMF SEL SERVER UNTIL SET SHARED VOLUME SHOW SHUTDOWN WAIT SHUTDOWN2 START WARM STARTUP STATS STATUS STDERR STDIN STDOUT STOP SWITCH NonStop TS/MP System Management Manual—541819-001 B- 3
Pathway/iTS Environment PATHCOM Reserved Words Pathway/iTS Environment Reserved words exclusive to the Pathway/iTS environment appear in the following table: ABORT OSS BREAK PRINTER CHECK-DIRECTORY REFRESH-CODE CODEAREALEN RESUME CURRENT RUN DIAGNOSTIC SERVERPOOL DISPLAY-PAGES STATE SUSPEND ECHO SWAP ERROR-ABORT TCLPROG INITIAL TCP INSPECT TELL IOPROTOCAL TERM IS-ATTACHED TERMBUFF TERMPOOL MAXINPUTMSGLEN TRAILINGBLANKS MAXINPUTMSGS TYPE MAXPATHWAYS MAXREPLY MAXSERVERPROCESSES M
C Configuration Limits and Defaults Table C-1 lists global limits for various items within each Pathway environment. Note. These limits are subject to change with product SPRs or with new software releases. Table C-1. Global Pathway Environment Limits (page 1 of 2) Item Limits Per Pathway Environment ASSIGNs Maximum total of 4095 for all server classes.
Configuration Limits and Defaults Table C-1. Global Pathway Environment Limits (page 2 of 2) Item Limits Per Pathway Environment PATHWAY object One (or one process pair) per Pathway environment. Requesters Maximum number of concurrently running processes (LINKMON, PATHCOM, SPI, and Pathway/iTS TCP and external TCP,) must not exceed 800. (Although more than 150 can be configured, no more than 800 can run concurrently.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 1 of 10) PATHCOM Parameter* ARGLIST SPI Token/Field** Value Limits and Defaults ZPWY-TKN-DEFSCARGLIST Values: OSS process startup argument list; from 2 to 24,000 characters. ZPWY-TKN-DEF-SCENV + ZPWY-TKN-DEF-SCARGLIST cannot exceed 24,000 bytes. Default: Empty argument list ASSOCIATIVE ZASSOCIATIVE Values: ON | OFF Default: OFF AUTORESTART ZAUTORESTART Values: 0 through 32,767 Value should be greater than 0.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 2 of 10) PATHCOM Parameter* CWD SPI Token/Field** Value Limits and Defaults ZPWY-TKN-DEFSCCWD Values: Absolute OSS pathname of the current working directory.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 3 of 10) PATHCOM Parameter* SPI Token/Field** GUARDIAN-SWAP Value Limits and Defaults Values: Maximum of 10 disk volumes for SERVER objects. Default: Selected by operating system (from _DEFAULTS DEFINE statement, if available). HELP N.A. Values: 1000 through 3999 Default: N.A. HIGHPIN ZHIGHPIN Values: ON | OFF Suggested value is ON for new applications written for HP NonStop(tm) systems.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 4 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXEXTERNALTCPS ZMAXEXTERNALTCPS Values: Total of values for MAXTCPS, MAXEXTERNALTCPS, and MAXLINKMONS must not exceed 800. Maximum number of concurrently running processes (TCP, external TCP, LINKMON, PATHCOM, and SPI) must not exceed 800.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 5 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXPATHCOMS ZMAXPATHCOMS Values: 1 through 100 Maximum number of concurrent openers of the PATHMON process (TCP, external TCP, LINKMON, PATHCOM, and SPI) must not exceed 800. For production, the value for this parameter should be large enough to allow for parallel interfaces (multiple PATHCOM and SPI processes).
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 6 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXSPI ZMAXSPI Values: 1 through 100 Maximum number of concurrent openers of the PATHMON process (TCP, external TCP, LINKMON, PATHCOM, and SPI) must not exceed 800. For production, the value for this parameter should be large enough to allow for parallel interfaces (multiple PATHCOM and SPI processes).
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 7 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXTMFRESTARTS ZMAXTMFRESTARTS Values: -1 Unlimited restarts 0 No restarts 1 through 32,767 Number of restarts Default: 5 MODE ZMODE Values: ORDERLY | ABORTTERM | IMMEDIATE Default: ORDERLY N.A. ZACCESS Values: I/O | INPUT | OUTPUT Default: No value is passed. N.A.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 8 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults OUT ZOUT Values: Name of output file. Default (SERVER): Spaces are passed for file name. Default (PATHCOM): Output directed to PATHCOM list file (typically the home terminal). OWNERID ZOWNERID Values: [system-number.] group-number, user-number or [nodename.] groupname.user-name Default: Owner ID of user who started the PATHMON process.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 9 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults SECURITY ZSECURITY Values: “A” “G” “O” “-” “N” “C” “U” Any local user A group member or owner Owner only Local super ID Any local or remote user Any member of owner’s community Any member of owner’s user class The owner should not be a supergroup user with “N” or “A” for a security value; this combination causes a security breach.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 10 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults TIMEOUT ZTIMEOUT Values: 0 through 16,383 SECS, or 0 through 1092 MINS, or 0 through 18 HRS Default (LINKMON): The LINKMON process waits indefinitely for server I/O operation to complete unless the send times out during the I/O because of the timeout value specified in the SERVERCLASS_SEND_ call.
D Migration Information This appendix covers migration and compatibility issues for the NonStop TS/MP product on C-series and D-series systems. These topics are discussed: • • Interprocess communication issues Application conversion For information on migration and compatibility issues relative to the Pathway/iTS product, see the Pathway/iTS System Management Manual. For more information about running applications on HP NonStop systems, see the Guardian Application Conversion Guide. Note.
Application Conversion Guidelines Migration Information D-series processes and associated application processes can run in many combinations of high and low PINs. Table D-1 lists the possible communication paths for D-series Pathway processes. If a process runs at a high PIN, all processes that communicate with that process must be able to communicate with a high-PIN process. The characters “N.A.” indicate that an option is not available. Table D-1.
Migration Information Application Conversion Guidelines Additional considerations specific to the PATHMON environment include the following: • • • Process names for servers must follow the C-series representation of a dollar sign ($) followed by one to four alphanumeric characters. Process names for PATHCOM and the PATHMON process must follow the Cseries representation as follows: ° If the name will be used across a network, a dollar sign ($) followed by one to four alphanumeric characters.
Migration Information Application Conversion Guidelines NonStop TS/MP System Management Manual—541819-001 D- 4
E Setting TMF Parameters When you are configuring and controlling a PATHMON application that uses the Transaction Management Facility (TMF) subsystem of the TMF, consider these basic questions: • • How do the settings you specify for the TMF parameter of the SET SERVER command affect Pathsend procedure calls and SCREEN COBOL SEND statements? What problems are caused by using the TMF OFF option of the SET TERM or SET PROGRAM commands as a switch to turn TMF off for a requester that is communicating with
Setting TMF Parameters Precautions for Using TMF Parameters NonStop TS/MP System Management Manual—541819-001 E- 2
Glossary Note. This glossary does not include terms for elements of the SCREEN COBOL language that are also found in standard COBOL. For definitions of such terms, refer to standard COBOL texts or to the text of the Pathway/TS SCREEN COBOL Reference Manual. absolute pathname. An OSS pathname that begins with a slash (/) character and is resolved beginning with the root directory. See also OSS pathname, relative pathname, and root directory. accept operation.
attributes Glossary attributes. Those characteristics of an object that influence the operation of that object and establish its capabilities. audited file. A database file that is flagged for auditing by the TMF subsystem; auditing is the monitoring of transactions in preparation for recovery efforts. audit trail. A record of database changes that can be used by the TMF subsystem to rebuild a database in the event of a hardware or software failure.
client/server model Glossary client/server model. A model for distributing applications. In general, but not always, in this model the client process resides on a workstation and the server process resides on a second workstation, minicomputer, or mainframe system. Communication takes the form of request and reply pairs, which are initiated by the client and serviced by the server. (A server can make requests of another server, thus acting as a client.
configuration Glossary configuration. The definition or alteration of characteristics of an object. See also object. configured TERM object. A TERM object that is explicitly configured with an ADD TERM command. Such a TERM object exists until it is explicitly deleted. Names of configured TERM objects begin with a letter. See also temporary TERM object and TERM object. consistency. See database consistency. context.
database management system (DBMS) Glossary application, which establishes the values and relationships of database fields and records. database management system (DBMS). A product, such as NonStop SQL/MP or Enscribe, that serves as the interface between a user or program (for example, a Pathway server) and the database. Among its many functions, the DBMS controls access to and organization of data within the database. Data Definition Language (DDL).
descriptor Glossary descriptor. For each elementary data item, the SCREEN COBOL compiler builds a data structure that describes the size, type, usage, and dependencies of the item. All of the information that pertains to a given item makes up the descriptor for that item. For example, the PICTURE specification is included in the descriptor. The descriptors are passed to the TCP in the pseudocode and provide a dictionary of information for interpreting and handling incoming data.
EDIT file Glossary available. A dynamic server process exists only as long as it is needed. See also static server. EDIT file. A source text file that can be augmented and modified by the user through a Tandem text editor program such as TEDIT (PS Text Edit). EMS. See Event Management Service (EMS). EMS log file. See event log file. Enable product. A tool provided by Tandem that allows users to develop simple data management applications without using a conventional programming language.
external process Glossary external process. A process in a different PATHMON environment from the process with which it is communicating. For example, suppose a TCP managed by PATHMON process $PMB requests a link to a server process in a server class that is managed by PATHMON process $PMA. Both the TCP and PATHMON process $PMB are external processes with respect to PATHMON process $PMA and the server class managed by $PMA. external server. See external process. external TCP. See external process.
fully qualified file name Glossary fully qualified file name. The complete name of a file in the Guardian environment. For a permanent disk file, this consists of a node name (system name), volume name, subvolume name, and file identifier (file ID). In interactive interfaces such as PATHCOM and TACL, the parts of a file name are separated by periods. See also partially qualified file name. gateway process.
intelligent mode Glossary intelligent mode. An operating mode in which data and messages are sent between an intelligent device and the Pathway environment. See also conversational mode (definition 1), intelligent device, and message-oriented requester. interactive mode. An operating mode in which commands are entered from a terminal keyboard. interoperability. The ability to communicate, execute programs, or transfer data between dissimilar environments. interoperate.
link management Glossary link management. The act of coordinating the sharing of links between requester or client processes and server processes. link manager. A process that requests links to server processes and provides link access after the link is granted. TCPs and LINKMON processes are the link managers in the Pathway environment. See also link access and link granting. LINKMON process. A Guardian process that supports access to servers in the Pathway, NonStop TUXEDO, and PTP environments.
mixed data item Glossary mixed data item. A data item that contains both single-byte and double-byte characters; in a COBOL or SCREEN COBOL program, these data items are declared as PIC X. modified data tag (MDT). In SCREEN COBOL, a bit that is set or reset to indicate whether data in an associated field is to be sent to the computer from the terminal. multithreaded. A programming model that provides more than one thread of control within a program.
NonStop SQL/MP Glossary NonStop SQL/MP. The Tandem relational database management system that promotes efficient online access to large distributed databases. See also Structured Query Language (SQL) and Enscribe database record manager. NonStop Transaction Manager/MP (NonStop TM/MP). A Tandem software product that provides transaction management, transaction protection, and database consistency in online transaction processing (OLTP) environments.
OBEY command Glossary Tandem NonStop Kernel, NonStop Transaction Services/MP, and NonStop Transaction Manager/MP. See also Pathway transaction processing environment. OBEY command. A command in a Tandem interactive interface, such as PATHCOM or the SCREEN COBOL Utility Program (SCUP), that allows users to execute the commands in a command file. See also command file. object. An entity that is subject to independent reference or control by one or more subsystems.
online transaction processing (OLTP) application Glossary online transaction processing (OLTP) application. A set of programs that perform online transaction processing (OLTP) tasks on behalf of the user. With an OLTP application, many terminal users can update data simultaneously, recording the changes in the database as they are entered. OLTP applications generally display, check, and accept input data; manipulate the input data; and perform some type of data-output activity. Open System Services (OSS).
PATHCOM command file Glossary PATHCOM command file. A file of PATHCOM commands that define and add the PATHMON-controlled objects required to execute an application. This file can contain all of the commands needed to start a PATHMON environment. PATHCOM command terminal. See command terminal. PATHCTL. See PATHMON configuration file. Pathmaker product. A menu-driven application generator, provided by Tandem, that increases the productivity of programmers developing Pathway applications.
Pathsend program Glossary Pathsend program. A Guardian program, written in C, C++, COBOL, Pascal, pTAL, or TAL, that makes calls to Pathsend procedures to request services from a Pathway server. A running Pathsend program is called a Pathsend process. See also Pathsend process. Pathsend requester. See Pathsend process. PATHTCP2. The TCP object file, usually identified by the file name $SYSTEM.SYSTEM.PATHTCP2. PATHTCPL. The TCP user library object file. Pathway application.
Pathway server Glossary Remote Server Call (RSC) product. The programming tools provided by POET include a simplified programming interface, name mapping, and conversion mapping. Pathway server. A server process or program in the Pathway transaction processing environment. See also NonStop TUXEDO server and PTP server. Pathway subsystem. The PATHMON environment components to which SPI commands are sent under the Pathway subsystem ID and which generate EMS event messages with the Pathway subsystem ID.
POET Glossary compiler, the compiler produces a code file named POBJCOD, a directory file named POBJDIR, and (if the SYMBOLS option is enabled) a symbols file named POBJSYM. POET. See Pathway Open Environment Toolkit (POET). primary process. The currently active process of a process pair in the Guardian environment. See also backup process and process pair. process. (1) A unique execution of a program in the Guardian environment.
PTP application Glossary PTP application. A collection of software components that perform transaction processing for CICS applications in the Guardian environment on Tandem NonStop systems. See also Customer Information Control System (CICS) and Parallel Transaction Processing (PTP) Services for the CICS API product. PTP Services product. See Parallel Transaction Processing (PTP) Services for the CICS API product. PTP server. A server in the PTP transaction processing environment.
requester Glossary indicates whether the request was processed successfully and whether the reply contains data returned by the application service. See also request translation header. requester. A process or program that runs in the Guardian environment on a Tandem NonStop system and requests services from a server process. For example, a SCREEN COBOL program is a requester program that is interpreted by the terminal control process (TCP), which provides link access to Pathway server classes.
RISC Glossary RISC. See reduced instruction-set computing (RISC). root directory. An OSS directory associated with a process that the system uses for pathname resolution when a pathname begins with a slash (/) character. See also OSS pathname. RSC. See Remote Server Call (RSC). scalability.
Screen Section Glossary Screen Section. A section in the Data Division of a SCREEN COBOL source program that describes the types and locations of fields in screens that can be displayed on a terminal. SCUP. See SCREEN COBOL Utility Program (SCUP). SEND operation. In SCREEN COBOL, an operation in which a transaction request message is sent to a server process and a reply is received back from the server process. See also server-class send operation. server.
special register Glossary special register. A data item defined by the SCREEN COBOL compiler, rather than explicitly in the program. Each special register has a particular purpose and should be used only as defined. The SCREEN COBOL language defines a different set of special registers from those defined by the standard COBOL language. SPI. See Subsystem Programmatic Interface (SPI). static server. A server process that the PATHMON process creates when a START SERVER command is issued.
system name Glossary backup process from repeating I/O operations that have already been completed by the primary process. system name. (1) The first of the four parts of a Guardian file name; also called a node name. (2) A name that identifies the Tandem system on which a PATHMON process is running. In SCREEN COBOL programs, this name is given in SEND statements.
TEDIT Glossary TEDIT. A Tandem text editor used to create or modify a source text file. Also called PS Text Edit. tell message. An informational message sent by PATHCOM or a management application to one or more terminals controlled by a SCREEN COBOL program, to be displayed for the terminal operators. TELL object. A temporary object used in PATHCOM and SPI commands to define a tell message. temporary TERM object.
throughput Glossary throughput. The number of transactions a system can process in a given period, such as one second. TMF. See Transaction Management Facility (TMF) subsystem. TMF level recovery. Recovery of the database to a consistent state through the use of the TMF subsystem. When a failure occurs, the TMF subsystem allows the application to back out the entire transaction, returning the contents of the database to the values it held when the transaction was started.
Glossary Transaction Management Facility (TMF) subsystem Transaction Management Facility (TMF) subsystem. The major component of the NonStop TM/MP product, which protects databases in online transaction processing environments. To furnish this service, the TMF subsystem manages database transactions, keeps track of database activity through audit trails, and provides database recovery methods. See also NonStop Transaction Manager/MP (NonStop TM/MP) and transaction. transaction mode.
Glossary user conversion procedure user conversion procedure. A procedure that lets users make their own validation checks or conversions of data passed between a SCREEN COBOL program and a terminal screen or intelligent device. ViewPoint application. An extensible interactive application for managing operations in the Guardian environment.
$RECEIVE Glossary NonStop TS/MP System Management Manual—541819-001 Glossary -30
Index A ABORT option, SHUTDOWN2 command 11-22 Absolute OSS pathnames 8-8 ADD command guidelines for 3-8 relationship with SET command 3-9 SERVER 3-16 ADD SERVER command 12-1/12-2 Adding Server classes 3-16 AGGREGATE option, SHUTDOWN2 command 11-23 ALL parameter, HELP command 10-8 ALTER command 5-19 ALTER SERVER command 12-2/12-4 Altering objects See individual objects PATHMON environment 5-17 server class security for Pathsend access 6-7 Angle brackets 10-8 Applications configuring in a PATHMON environment
C Index BACKUPCPU attribute CONTROL PATHMON command 11-2 primary CPU, relation to 12-36 SET PATHMON command 11-11 SET SERVER command 12-18 Banner, PATHCOM 2-6 BEGIN-TRANSACTION statement 12-47 Binder program 12-21 Brackets, angle 10-8 BREAK attribute, for TERM objects 3-12 Break function key PATHCOM commands 8-6 SHUTDOWN2 command 11-23 C Cancelling PATHCOM commands 8-6 Characters inserting and deleting 10-7 Client-server computing 1-12 CLOSE message 12-45 CMDCWD command 3-8, 10-2 CMDCWD parameter 10-13 C
D Index Configuration file (continued) recording changes to PATHMON 11-2/11-5 saving contents of 5-21 startup types 11-25/11-26 status of 11-28/11-30 using attributes defined in 3-15 Configuration limits and defaults C-1/C-3 Configuring See also Reconfiguring PATHMON environments applications in a PATHMON environment 3-1 limits for PATHMON environment 5-17 limits for PATHMON environments 2-9, 3-4 multiple PATHMON environments 3-3 object attributes for maximum performance 3-26/3-34 PATHMON-controlled objec
E Index DELETEDELAY attribute (continued) relation to dynamic server processes 3-16, 3-18 Deleting PROGRAM objects 5-19 SERVER objects 5-19 TCPs 5-19 TERM objects 5-19 Deleting characters 10-7 DETAIL parameter STATUS SERVER command 12-40 Devices 1-12 Diagnosing problems, data to collect for 5-29/5-31 Disk file names 8-7 Disk space for configuration file 2-10 for PATHMON configuration information 2-1 Displaying configuration information 5-3/5-7 object attributes 3-14 statistics collected by LINKMON process
F Index External objects and processes LINKMON process 1-9 PATHCOM 1-9 Pathsend 1-13 TCPs 1-12 External TCPs shutting down 11-21 F Failed to get… (LINKMON message) 16-1 FastStart product 1-21 FC command 10-6/10-7 FECONTINUE (startup message 70) 4-2, 12-36 FESCSERVERLINKCONNECT (error 904) 12-30 File names Guardian 8-7 OSS pathnames 8-8/8-9 setting Guardian defaults 10-3 setting OSS defaults 10-2 File open error 9-5, 10-12 File-creation attributes 12-16 File-identifier names 8-7 FREEZE attribute 12-40 Fre
K Index INFO display field 11-27, 12-40 INFO SERVER command 12-7/12-9 INITIAL attribute, for TERM objects 3-13 Initialized and running (LINKMON message) 16-2 Initializiation files D-2 Inserting characters 10-7 INSPECT parameter PATHMON startup command 9-2 Intelligent devices 1-12 Interactive mode (PATHCOM) 2-6, 8-6 Interfaces PATHCOM interactive 1-17/1-18 SPI programmatic 1-18 INTERVAL parameter STATS SERVER command 12-38 STATUS PATHWAY command 11-31 I/O operations, requested by Pathsend processes definit
M Index LINKMON processes (continued) monitoring of 6-7/6-10 name format 12-43 names for 6-3 naming 11-27 relation to Pathsend processes 6-1 server access 12-25 sharing links 3-24 shutting down 11-21 starting 6-3 statistics collected by 6-10 STATUS command 11-26/11-28 status of 11-29 tasks performed by 6-1 thawing server requests 12-46/12-47 TMF, relation to 12-6 Links associative servers 12-26 attributes affecting DELETEDELAY 3-26 LINKDEPTH 3-25 MAXLINKS 3-25 MAXSERVERS 3-25 NUMSTATIC 3-26 configuration
N Index MAXLINKS attribute 3-18, 3-25, 12-23, 12-44 MAXPARAMS attribute 2-9, 3-5, 11-13 MAXPATHCOMS attribute 3-5, 11-15 MAXSERVERCLASSES attribute for PATHMON environments 2-9, 3-5 SET PATHWAY command 11-14 MAXSERVERPROCESSES attribute for PATHMON environments 2-9, 3-5 SET PATHWAY command 11-14 MAXSERVERS attribute 3-18, 3-25, 12-24 MAXSPI attribute 11-16 MAXSTARTUPS attribute 2-9, 3-5, 11-14 MAXTCPS attribute, for PATHMON environments 2-9 MAXTERMS attribute for PATHMON environments 2-9 Measure product 1
O Index NUMSTATIC attribute 12-24 for Server classes 3-18, 3-26 relation to MAXSERVERS attribute 3-18 relation to static server processes 3-18 O OBEY command, TACL 2-8 OBEY (or O) command 10-10 OBEYFORM parameter INFO PATHMON command 11-5 INFO PATHWAY command 11-6 INFO SERVER command 12-7 OBEYVOL command 10-11 OBEYVOL parameter, SHOW command 10-14 Objects altering definitions of 5-19 and attributes 3-8 and working set values 3-11 controlling and maintaining, overview 5-1 defined PATHMON process 1-8 SERVE
P Index OWNER attribute for PATHMON environment 5-20 for PATHMON environments 3-7 for Pathsend access to servers 6-6 SET PATHWAY command 11-19 SET SERVER command 12-25 P PAID display field 11-29 PARAM attribute, for Guardian Server classes 3-19 PARAM parameter 12-25 Parameters configuration limits for C-1/C-3 displaying settings 10-13/10-14 PATHCOM advantages of 1-18 as interactive interface tool 1-17/1-18 banner message for 2-6 collecting data about for problem diagnosis 5-30 command and object summary
P Index PATHCOM commands (continued) STATUS PATHWAY 5-8 STATUS SERVER 5-9 STOP SERVER 4-4 SWITCH 5-20 THAW SERVER 4-4 PATHCONF files, collecting for problem diagnosis 5-29 PATHCTL display field 11-29 PATHCTL file See Configuration file PATHMON server names, granting 12-26 SERVER restart attempts 12-17 PATHMON configuration file 2-1/2-2, 3-9 PATHMON environment applications 3-1 attributes for 3-4 configuration limits C-1/C-3 configuring across CPUs 1-5 configuring and managing objects in 1-14/1-21 consider
Q Index PATHMON process and object (continued) STATUS command 11-28/11-30 STOP command 11-33/11-34 SWITCH command 11-34/11-35 TACL command for starting 9-1/9-3 Pathsend environment See also Pathsend processes description of environment 6-1 procedure calls 6-1 Pathsend facility, server access, specifying 12-25 Pathsend processes as external objects 1-13 as requesters 1-13 communication w ith server classes 6-1 defined 1-13 relation to LINKMON processes 6-1 security requirements for network 6-5 SERVER objec
R Index Queues for server class waits 7-2 QUIET option, SHUTDOWN2 command 11-23 R Reconfiguring Pathway applications a scenario 5-2 adding, altering, and deleting objects 5-17 changing owner and security 5-20 specifying new limits 5-17 Relative OSS pathnames 8-9 Remote access, to PATHMON 2-5 Remote Server Call (RSC) product for client-server computing 1-12 Repeating the command line 10-6/10-7 REQNUM display field 11-29 Request not valid… (message 1045) 11-34, 12-44 REQUEST PENDING, and STOP SERVER comman
S Index Server classes attributes for 3-17/3-22 ARGLIST 3-20 ASSIGN 3-18 CPUS 3-17 CREATEDELAY 3-18 CWD 3-20 DEFINE 3-18 DELETEDELAY 3-18 ENV 3-20 MAXLINKS 3-18 MAXSERVERS 3-18 NUMSTATIC 3-18 optional 3-17 PARAM 3-19 PROCESSTYPE 3-17 PROGRAM 3-17 required 3-17 STDERR 3-20 STDIN 3-20 STDOUT 3-20 configuring 3-16/3-23 defined 3-16 defining and adding 3-16/3-23 example of a Guardian 3-19 example of an OSS 3-21 Guardian attributes for 3-18 displaying link status for 5-10 OSS configuring attributes for 3-20 Se
S Index Server processes (continued) associative 12-26 CREATEDELAY attribute 3-16 defined 3-16 DELETEDELAY attribute 3-16 displaying information about configuration 5-5 dynamic 12-20 freezing 4-4 home terminal, specifying 12-22 input file, naming 12-22 links to 3-24, 4-3 multithreaded 12-23 object programs for 3-17 relationship to server class 3-16 restart attempts, specifying 12-17 setting maximum 11-14 starting dynamic 4-1 static 4-1 static 12-17 static, specifying maximum 12-24 stopping 4-4 Server prog
T Index Startup files, creating with INFO, OBEYFORM 5-21 STARTUP messages, for server classes 11-14 Startup, cool CONTROL PATHMON command, effect of 11-3 STATE display field 11-27, 12-41 Static links 12-18 Static server processes NUMSTATIC attribute 3-18, 4-1 relation to MAXSERVERS and NUMSTATIC attributes 3-17 starting 4-1 stopping 4-4 Statistics collected by LINKMON processes 6-2, 6-10 TCPs 5-13 displaying information about 5-13/5-15 for SERVER objects 5-13, 6-10 STATS command SERVER 5-13 STATS SERVER c
U Index TCP statistics CONTROL TCP STATS command 5-13 SET TCP STATS command 5-13 TCPs altering 5-19 and associative servers 5-32 and links 4-3 as external objects 1-12 attributes for DUMP 5-20 defined 1-2 deleting 5-19 external, shutting down 11-21 freezing server requests 12-5 frozen server class, sending to 12-6 links, idle 12-20 links, requesting new 12-18 switching primary and backup CPUs for 5-20 thawing server requests 12-46 user library object file 5-29 TCP/SERVER communication 4-3 Templates for PA
W Index W WAIT display field 11-29 WAIT parameter FREEZE SERVER command 12-6 SHUTDOWN command 11-21 WEIGHT display field 12-41 Working set values, for PATHMONcontrolled objects 3-11/3-14 Special Characters ! parameter FREEZE SERVER command 12-6 SHUTDOWN command 11-21 START PATHWAY command 11-26 ! (Exclamation point) See Exclamation point $SYSTEM.SYSTEM.
