HP 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 541819-003 NonStop TS/MP 2.3 May 2008 541819-004 NonStop TS/MP 2.3 December 2008 541819-005 NonStop TS/MP 2.3 and 2.4 May 2009 541819-006 NonStop TS/MP 2.0, 2.3, and 2.4 May 2010 541819-007 NonStop TS/MP 2.0, 2.1, 2.3, and 2.
Legal Notices Copyright 2010 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop TS/MP System Management Manual Glossary Index Examples Figures Tables Legal Notices What’s New in This Manual xi Manual Information xi New and Changed Information xi About This Manual xvii Purpose of This Manual xvii Who Should Read This Manual xviii How This Manual Is Organized xviii Related Reading xxi Other Manuals in the Manual Set xxiii Other Manuals of Interest xxiii Notation Conventions xxiii HP Encourages Your Comments xxviii 1.
1. Introduction to NonStop TS/MP System Management (continued) Contents 1. Introduction to NonStop TS/MP System Management (continued) Pathsend Processes 1-15 System Management Tasks 1-16 System Management Tools 1-19 PATHCOM Interactive Interface 1-20 Management Programming Interface 1-21 Other System Management Tools 1-23 Summary of PATHCOM Commands 1-23 2.
3. Configuring Objects in a PATHMON Environment (continued) Contents 3. Configuring Objects in a PATHMON Environment (continued) Configuring Server Classes 3-16 Configuring Static and Dynamic Server Processes 3-17 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) Information to Include When Reporting Problems 5-29 PATHMON Environment 5-29 PATHMON-Specific Problems 5-30 PATHCOM-Specific Problems 5-31 Server-Specific Problems 5-31 Recovering from PATHMON Failure 5-31 Keep Development and Production Separate 5-32 Maintaining Associative Server Processes 5-33 Migrating Your Environment to a Different System 5-34 6.
8. Overview of PATHCOM (continued) Contents 8. Overview of PATHCOM (continued) OSS Pathnames 8-9 Absolute Pathnames 8-9 Relative Pathnames 8-9 9. PATHMON and PATHCOM Startup Commands Starting the PATHMON Process Starting PATHCOM 9-3 9-1 10.
11. PATHMON Environment Control Commands (continued) Contents 11. PATHMON Environment Control Commands (continued) STOP PATHMON Command 11-36 SWITCH PATHMON Command 11-37 12.
16. Link Manager Messages (Numbers 3000-3999) Contents 16. Link Manager Messages (Numbers 3000-3999) General Information 16-1 LINKMON Messages 16-1 17. LINKMON Log Messages General Information 17-1 LINKMON Log Messages 17-1 18.
Glossary Contents 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. Example 6-1. Example 6-2. Example 6-3. Example 6-4. Example 7-1. Example 7-2. Example 7-3. Example 7-4. Example 7-5. Example 11-1. Example 11-2. Example 11-3. Example 11-4. Example 11-5. Example 12-1. Example 12-2. Example 12-3.
Figures Contents Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 1-7. Figure 1-8. Figure 1-9. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 8-1.
Tables (continued) Contents Tables (continued) Table 10-1. Table C-1. Table C-2. Table D-1.
What’s New in This Manual Manual Information HP 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 to the 541819-006 Manual Removed the following text from AVG TSIZE for REPLY on page 7-5: “This size can be used to fine tune the amount of server pool space required.” • • • • Updated the note on page 12-24. Added a note about the link selection when the LINKDEPTH is greater than 1 on page 12-43. Added a note about the lock failed error on page 14-5. Updated the description of SERVER objects on page C-2.
What’s New in This Manual • • • ° ° ° Changes to the 541819-004 Manual Section 14, PDMCOM Messages (Numbers 1500-1999) Section 15, PATHCOM Messages (Numbers 2000-2999) Section 16, Link Manager Messages (Numbers 3000-3999) Updated the syntax of SET SERVER command on page A-6. Added the following keywords under PATHCOM Reserved Words: ° ° ° ° ° ° CSECS COUPLE DECOUPLE DOMAIN PARTITION UNDO Updated value limits of CREATEDELAY on page C-4.
What’s New in This Manual • • • • • • • • Changes to the H06.14/J06.03 Manual Updated the note on MAXLINKS on page 12-24. Added a note on page 12-49 to specify limitation of wildcards. Updated Usage Considerations for SET SERVER TIMEOUT Attribute on page 12-50. Added a new section, Section 14, PDMCOM Messages (Numbers 1500-1999), listing all the messages generated by PDMCOM on page14-1. Added the following terms in the Glossary: ° ° ° ° ° ° ° Application Cluster Services domain on page -1.
What’s New in This Manual • • • • • • • Changes to the H06.14/J06.03 Manual Updated the description of $process-name on page 12-26 under SET SEVER Command. Added a reference to Usage Considerations for SET SERVER TIMEOUT Attribute in TIMEOUT number { HRS | MINS | SECS } on page 12-30. Added the description of scwait on page 12-45. Added the section Wild Card support in PATHCOM on page 12-48. Added the section Usage Considerations for SET SERVER TIMEOUT Attribute on page 12-50.
What’s New in This Manual Changes to the H06.14/J06.
About This Manual This manual provides guidelines and examples for configuring and managing the J06.03 and subsequent RVUs, and H06.05 and subsequent RVUs of TS/MP, which run on HP Integrity NonStop™ Servers and HP Integrity NonStop™ BladeSystem.This manual is one of the set of manuals that describes the TS/MP and Pathway/iTS.
Who Should Read This Manual About This Manual Who Should Read This Manual This manual is intended for those individuals responsible for starting, configuring, and managing a PATHMON environment, using the PATHCOM interactive interface. It is assumed that readers have a general knowledge of NonStop software programming concepts. The task-oriented section of this manual are also intended for individuals writing programs to manage server classes in a PATHMON environment programmatically.
How This Manual Is Organized About This Manual Section Description (page 2 of 3) Section 7, Tuning Your System by Using Statistics Describes statistics information provided by the LINKMON process or ACS subsystem processes and terminal control process (TCP) and how to use this information to monitor and maintain your PATHMON environment.
How This Manual Is Organized About This Manual Section Description (page 3 of 3) Appendix C, Configuration Limits and Defaults Summarizes Pathway/iTS configuration limits and defaults. Appendix D, Migration Information Describes migration and compatibility considerations. Appendix E, Setting TMF Parameters Provides guidelines on how to set parameters in various PATHCOM commands when you are using TMF to manage transactions in your PATHMON environment.
Related Reading About This Manual Related Reading For more information specific to managing a PATHMON environment, see: 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.
Related Reading 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.
Other Manuals in the Manual Set About This Manual Other Manuals in the Manual Set TS/MP Pathsend and Server Programming Manual: This manual describes the Pathsend procedure calls, included as part of TS/MP, and how to use those calls to write requester programs. It also describes how to design and code Pathway servers for use with all types of requesters and clients. TS/MP Release Supplement: This manual supplements the HP NonStop™ TS/MP manual set. It describes the new features provided by TS/MP 2.
General Syntax Notation About This Manual General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
Notation for Messages About This Manual !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i:i. !i,o In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Notation for Management Programming Interfaces About This Manual horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
Change Bar Notation About This Manual !o. The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information.
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 NonStop TS/MP The following table presents a comparative architecture of TS/MP versions, namely TS/MP 2.0, 2.1, and 2.3. Table 1-1. Comparative Architecture of TS/MP Versions TS/MP 2.3 and Later Versions TS/MP 2.1 TS/MP 2.0 TS/MP with NonStop Tuxedo Application TS/MP Application Environment TS/MP Application Environment TS/MP Application Environment TS/MP Application Environment Management and Control TS/MP 2.
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.) • • Application Cluster Services (ACS) Subsystem Processes—these processes use Pathsend requesters to provide link management functions for applications. (Pathsend requesters are user applications that use Pathsend procedure calls to send requests to server classes.) In TS/MP 2.
Introduction to NonStop TS/MP System Management Pathway Environment Configurations Figure 1-1 illustrates a Pathway environment that includes the NonStop TS/MP product and the Pathway/iTS product. In this example, a remote system uses Pathsend requesters to access the server processes, with link management provided by LINKMON or ACS subsystem processes. A set of Pathway/iTS application terminals makes requests through the TCP.
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.
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 PATHMON Server Class LINKMON List of Accounts Server Processes \NODE B PATHMON 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. TS/MP 2.3 has updated PATHMON, PATHCOM and new PDMCOM processes. For more information, see the TS/MP Release Supplement.
Introduction to NonStop TS/MP System Management PATHCOM Processes start up and shut down the PATHMON-controlled objects, and obtain status information about the PATHMON environment. For information on the attributes that 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.
Introduction to NonStop TS/MP System Management Transaction Sources in a given processor. LINKMON processes function as link managers, providing link 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.
Introduction to NonStop TS/MP System Management Transaction Sources Figure 1-5. Transaction Sources RSC LINKMON or ACS subsystem processes Personal Computer 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 HP NonStop System \LND PATHMON Controlled Objects Server Class X $PMB Server Pathsend Requesters $ZL01 Server Class Y Server Pathsend Requesters Database $ZL02 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 tasks associated with starting, maintaining, and stopping an environment or maintaining a state. Whether you use the PATHCOM interactive interface or the management programming interface to manage your PATHMON environment may depend on the complexity and frequency of your system management tasks. The more complex or repetitive your system management tasks, the more advantageous it is to use a management programming interface.
Introduction to NonStop TS/MP System Management Management Programming Interface Management Programming Interface A management programming interface is a token-oriented interface based on the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS)— part of HP’s Distributed System Management (DSM) product. (See Distributed Systems Management.
Introduction to NonStop TS/MP System Management Management Programming Interface The management programming interface provides the standard set of procedures, definitions, and message formats required to send messages between your management application in the operations environment and the PATHMON process in the Pathway environment. The management programming interface includes SPI and the Event Management Service (EMS), another DSM facility.
Introduction to NonStop TS/MP System Management Other System Management Tools management tasks, management applications can free operators to concentrate on more critical or creative system management activities. Other System Management Tools You get optimum performance from a well-balanced NonStop system. These tools enable you to analyze NonStop system performance. • The Measure product enables you to balance and tune NonStop systems.
Introduction to NonStop TS/MP System Management • • • • • • • • Summary of PATHCOM Commands SHOW command displays the current values for an object. ADD command adds a PATHMON-controlled object. INFO command displays values for an object as recorded in the PATHMON configuration file. 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.
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 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 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. Use SET PATHMON commands to specify a backup processor and request error dumping.
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 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 run 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 Using DEFINEs You can use DEFINEs to specify names for the files that PATHCOM uses directly as command files. For example: 12> ADD DEFINE =CMD-FILE, CLASS MAP, FILE $DATA.PW.CONFIG 13> ADD DEFINE =OUT-FILE, CLASS SPOOL,LOC $S, REPORT “CONFIG” 14> PATHCOM/IN =CMD-FILE, OUT =OUT-FILE/ $PMX In the preceding example, PATHCOM reads commands from the command file specified by the DEFINE =CMD-FILE ($DATA.PW.
Configuring Global Parameters Starting and Stopping a PATHMON Environment PATHMON process writes the values to the PATHMON configuration file. For the syntax of all SET PATHWAY commands, including descriptions of all required parameters, see Section 11, PATHMON Environment Control Commands. Figure 2-5. Specifying PATHMON Environment Limits = SET PATHWAY MAXTCPS 2 PATHMON PATHCOM Total TCPs 2 . . .
Starting and Stopping a PATHMON Environment Configuring the PATHMON Process Specifying the Owner and Security Attributes You specify security for your PATHMON environment by setting the OWNER and SECURITY attributes. These attributes determine who is allowed to alter the definitions and states of PATHMON-controlled objects.
Starting and Stopping a PATHMON Environment Specifying the START Command If you request your HP representative’s help in analyzing a problem, the representative will likely require a DUMP file. It is therefore recommended that DUMP be set to ON for production systems. 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.
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.
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 HP NonStop TS/MP System Management Manual—541819-007 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 or ACS subsystem processes, which forward 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. 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 The limits that you specify determine the maximum number of SERVER objects you can define for your system during subsequent configuration: • • • • • MAXASSIGNS specifies the number of ASSIGN definitions that you can specify for all server classes. MAXPARAMS specifies the maximum number of server classes that can have PARAM messages.
Configuring Objects in a PATHMON Environment Specifying Node Independence For more information about limits and default values for your PATHMON environment, see Appendix C, Configuration Limits and Defaults. Note that identifying a truly optimum configuration for your PATHMON environment can require a significant degree of calculation and tuning that is beyond the scope of this manual.
Configuring Objects in a PATHMON Environment Specifying Security Some Names Are Always Node-Independent Note that some object names are node-independent regardless of whether you use the NODEINDEPENDENT attribute or not. These include the names of log files in which 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.
Configuring Objects in a PATHMON Environment Configuring PATHMON-Controlled Objects Before you issue the START PATHWAY command, the owner ID is always the process accessor ID of the PATHMON process and the security attribute is O (owner). This setting prevents alteration of the global configuration parameters. Note. After you issue the START PATHWAY command, if you do not specify a value for the security attribute, it defaults to N (any local or remote user).
Configuring Objects in a PATHMON Environment Using the SET and ADD Commands CMDVOL command to set the default node, volume, and subvolume for the expansion of any file names. When creating OSS servers, use the CMDCWD command to record an OSS directory to be used to resolve relative file names specified for OSS server attributes. For more details on these commands, see CMDVOL Command and CMDCWD Command.
Using the SET and ADD Commands Configuring Objects in a PATHMON Environment Before adding the SERVER, you can check the values by using the SHOW command: = SHOW SERVER Then, you name and add the SERVER, using an ADD SERVER command: = ADD SERVER SERVER-X In response, the PATHMON process writes the name and definition for this SERVER into the PATHMON configuration file, as shown in Figure 3-3. Figure 3-3.
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 Configuring Static and Dynamic Server Processes Configuring Static and Dynamic Server Processes There are two types of server processes: static and dynamic. A static server is a server process that the PATHMON process creates when the START SERVER command is issued. A dynamic server is a server process that the PATHMON process creates after a link manager has waited for a specific time period for a static server to become available.
Configuring Objects in a PATHMON Environment Defining Attributes for Guardian and OSS Servers If the server process stops under normal circumstances, for example, in response to a STOP command, the PATHMON process does not attempt to restart it. • The CPUS attribute specifies the CPUs on which server processes of this server class will run. You can specify either a list of paired (primary and backup) CPUs or a list of single CPUS.
Configuring Objects in a PATHMON Environment Defining Attributes for Guardian and OSS Servers Attributes That Apply Only to Guardian Servers These attributes are valid only for Guardian servers: • ASSIGN assigns a logical file name to a physical file used by your server program and specifies the attributes of that file. You can include multiple ASSIGN specifications for a server class to cover as many files as necessary.
Configuring Objects in a PATHMON Environment • • Defining Attributes for Guardian and OSS Servers The files that your server program recognizes by the names ORDERS and PARTS are the files $DATA.REG1.ORDFILE and $DATA.REG2.PARTFILE, respectively. (ASSIGN attribute.) The PATHMON process starts the first server process in the server class in processor 2, the second server process in processor 3, and the third in processor 0.
Configuring Objects in a PATHMON Environment • • • Defining Attributes for Guardian and OSS Servers STDERR specifies an OSS filename or device name to which errors are sent. STDIN specifies an OSS filename or device name from which this server process accepts input. STDOUT specifies an OSS filename or device name to which this server process sends output.
Configuring Objects in a PATHMON Environment Additional Considerations and STDOUT attributes are resolved against this directory name to create an absolute pathname. (CWD attribute.) • • PARTS is defined as the logical filename for the physical file located at $DATA.REG2.PRTFIL. ORDERS is defined as the logical filename for the physical file located at $DATA.REG2.ORDFIL. (DEFINE attribute). A variable called DEBUGLOGFORMAT is defined. Its value is TRUE. (ENV attribute.
Configuring Objects in a PATHMON Environment Setting Process Priority the PATHMON process completes its attempt, a message is logged explaining that the PATHMON process was trying to resize its segment. If all preallocated extents for the PATHCTL file become full, the PATHMON process attempts to allocate another extent. If additional space is not available and a command is issued, the command fails and you get an allocation error.
Configuring Objects in a PATHMON Environment Links and Link Attributes steps for each server class in your application, then add the totals to determine global limits for such attributes as MAXSERVERPROCESSES. Note that although the calculations and formulas that follow are intended to assist you in arriving at an optimum configuration, they are necessarily generic. Only you know the specific characteristics of your system.
Configuring Objects in a PATHMON Environment • • • • • Links and Link Attributes MAXSERVERS MAXLINKS LINKDEPTH NUMSTATIC CREATEDELAY and DELETEDELAY 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.
Configuring Objects in a PATHMON Environment Understanding the Effects of Link Configuration manager makes the server open available for use by multiple SCREEN COBOL programs or Pathsend processes and user applications, respectively. Note. Normally, only server programs that are coded as NOWAIT I/O should have a LINKDEPTH value greater than 1. Setting the LINKDEPTH value greater than 1 for a WAITED server class can lead to queueing at the server process and increased response time.
Understanding the Effects of Link Configuration Configuring Objects in a PATHMON Environment Suppose, for example, that you set the server attribute LINKDEPTH equal to 20, which permits 20 concurrent requests to a server process. If transaction service time is 1 second and the server class handles requests serially, response time might be as much as 20 seconds. Thus, this LINKDEPTH setting can cause send requests to queue on the server class for unacceptable lengths of time.
Steps to Optimum Link Configuration Configuring Objects in a PATHMON Environment to become available. However, if the server configuration were changed to make MAXSERVERS = 5, each process’s send request can be handled by a separate server process. Processing under this configuration is shown in Figure 3-6. Figure 3-6.
Configuring Objects in a PATHMON Environment Steps to Optimum Link Configuration 7. Calculate the potential link manager demand for links to the server class. 8. Calculate the value you must specify for the server class MAXLINKS attribute. 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.
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 As an example, if the value for the NUMSTATIC attribute for the server class ORDERSRV is 5, this command starts five static server processes in the server class named ORDER-SRV: = START SERVER ORDER-SRV 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 Starting SERVER Objects The startup message has a header that is constructed from what you specified for the IN, OUT, and VOLUME attributes in the SET SERVER command. If you specified a character string for the STARTUP attribute, that is also included. 3. If the server replies with a value of 70 (FECONTINUE) to the startup message, the PATHMON process sends variables and parameter messages to the server.
Starting and Stopping SERVER Objects Freezing and Thawing Server Classes Freezing and Thawing Server Classes To disable communication between link managers and server processes without actually stopping the server class, use the FREEZE SERVER command. The FREEZE SERVER command prevents link managers from sending requests to the server processes.
Starting and Stopping SERVER Objects Stopping SERVER Objects server classes are in a FREEZE-PENDING state and the STOP command will not work.) This command stops all instances of a server in server class CLASS-1: = STOP SERVER CLASS-1 To stop all servers in your PATHMON configuration, first run: = FREEZE SERVER * Once the server classes are frozen, run this command: = STOP SERVER * After this, if the WAIT user option is specified, PATHMON waits until the WAIT time is over.
Starting and Stopping SERVER Objects Stopping SERVER Objects HP NonStop TS/MP System Management Manual—541819-007 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 controlled objects. You use the STATS command to check statistics for SERVER resources. Note. Information about TCPs that appears in this section applies to your environment only if you are using the Pathway/iTS product. For all of these commands, you can direct the display output to a text file by including the OUT option in your command.
Maintaining a PATHMON Environment Displaying Configuration Information 5. You use these two commands to attempt to freeze the two server classes: = FREEZE SERVER B-NAME-SERVER ! = FREEZE SERVER C-NAME-SERVER ! 6. You use a STOP SERVER * command to stop all server classes. 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.
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 run 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 or ACS subsystem processes 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.
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 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. Example 5-10.
Maintaining a PATHMON Environment Displaying Statistics Information Displaying Statistics Information Server statistics are collected by LINKMON processes, ACS subsystem processes, or TCPs that have links to the server class. The LINKMON process or the ACS subsystem processes collect these statistics on an ongoing basis.
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 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. First, it produces a highly restrictive record of your system configuration, one in which the default values recorded are those assigned by the current version of the PATHMON environment.
Maintaining a PATHMON Environment Logging Information to a Terminal The audit logging is done when the STATUS messages are enabled. The message format is shown below: ddMMMyy,mm:ss : STATUS - *1166* , AUDIT MSG - - USER where: ddMMMyy,mm:ss Displays date and time. Displays the PATHMON process name that sends the message. Displays the entity name.
Maintaining a PATHMON Environment Links and PATHMON Performance reported in tokenized event message format, and to specify the disk file LOGCOPY as a log file for both error and status change information in text format, enter: = LOG1 $0, EVENTFORMAT = LOG2 LOGCOPY, STATUS Before specifying a disk file for logging, you must first create that file, using the FUP CREATE command. (You should ensure that the file is large enough.
Maintaining a PATHMON Environment Understanding the Causes of Link Dissolution your environment includes the Pathway/iTS product, the PATHMON process also maintains status information for TCP and TERM objects. By understanding how PATHMON manages links and what causes dissolution of links, you can take steps to improve the performance of your system. This can adversely affect PATHMON performance under exception conditions such as network or processor failure: • Maintaining object status to manage links.
Maintaining a PATHMON Environment Managing PATHMON Process Performance Cause Action The PATHMON process sends an external shutdown notification Deletes all links owned by that PATHMON process, allowing current I/O to complete. Consequently, no links are returned to the PATHMON process. The PATHMON process returns an unexpected I/O error or close message, or the link manager detects a message protocol error. Deletes all links owned by that PATHMON process, allowing current I/O to complete.
Maintaining a PATHMON Environment • Detecting Problems Failures Poor Configuration If a link manager, such as a LINKMON process, ACS subsystem processes, or TCP, cannot establish communication with a server process, the link manager indicates this situation to the screen program or Pathsend requester, and the PATHMON process writes an error message to the log files. If you experience such a failure, you likely need to review your configuration.
Maintaining a PATHMON Environment • • • Improving Performance Network failures A TCP going down (Pathway/iTS environment only) Server process failure In certain network situations, communication delays between the PATHMON process and link managers, such as the LINKMON process, can reduce response time even further. Improving Performance You can improve PATHMON performance in some instances by reconfiguring your PATHMON environment. These subsections describe options that you might want to consider.
Maintaining a PATHMON Environment PATHMON-Specific Problems Version Procedure Use the VPROC procedure to get the product version for the applicable PATHMON components, as follows: >VPROC Enter filename: >$.PATHCOM >$.PATHMON where $vol.subvol is the system volume and subvolume on which the desired component resides. Event Log and CONFLIST Be sure to collect any PATHMON and EMS log files. Also include the $SYSTEM.SYSnn.CONFLIST file.
Maintaining a PATHMON Environment PATHCOM-Specific Problems particular time—before it encounters a fatal error. You should only force a dump if your HP representative specifically requests it. PATHMON Configuration and Object Information Make the PATHCTL file available to your HP representative.
Maintaining a PATHMON Environment Keep Development and Production Separate 1. Determine whether it is in your users’ best interests to bring the PATHMON environment down right away. A well-designed, well-tuned system may actually run for one or two days without the PATHMON process. Contact users and find out whether critical applications are running as expected. If they are, you may be able to wait before stopping the entire environment. 2. Capture data about the failure.
Maintaining Associative Server Processes Maintaining a PATHMON Environment Maintaining Associative Server Processes An associative server is a process within a server class that can be started outside of the PATHMON environment by a process other than the the PATHMON process that controls the server class.
Maintaining a PATHMON Environment Migrating Your Environment to a Different System Associative Servers as Subtype 30 Processes An associative server can be a subtype 30 process, which simulates a terminal or communication device. When an associative server is a subtype 30 process, the PATHMON process determines the server’s device type; you do not have to designate the device type with the TYPE option of the RUN PROGRAM command.
Migrating Your Environment to a Different System Maintaining a PATHMON Environment Table 5-1. Migration Considerations: Object Attribute Values (page 1 of 2) Considerations/ Recommendations Object or Process Attribute PATHMON process BACKUPCPU cpu-num Ensure that CPUs on new system have same numbers or change manually. DUMP ON | OFF Specify a new DUMP file name if the name was previously specified. PATHWAY object OWNER owner-id Ensure that user ID is known to new system 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 2) Object or Process TCP* TERM* PROGRAM* Attribute Considerations/ Recommendations GUARDIAN-SWAP $volume Ensure that a disk attached to new system has same name or change manually. HOMETERM termname Ensure that a terminal with same name exists on new system or change manually.
Maintaining a PATHMON Environment Migrating Your Environment to a Different System Note. The SWAP and GUARDIAN-SWAP attributes are not included in Table 5-1 because TCP swap space is now handled by the Kernel-Managed Swap Facility (KMSF) and the SWAP and GUARDIAN-SWAP values are no longer used. However, if you do specify device names for these attributes, you must ensure that the named devices exist; otherwise, an error occurs.
Maintaining a PATHMON Environment Migrating Your Environment to a Different System HP NonStop TS/MP System Management Manual—541819-007 5- 38
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. In TS/MP 2.3, ACS subsystem core processes have replaced the LINKMON process. For more information on ACS subsystem core processes, see the TS/MP Release Supplement.
LINKMON Processes Managing the Pathsend Environment include the Pathsend processes such as those created by RSC on behalf of its workstation clients. LINKMON processes also manage communication between 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.
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 ACS Subsystem Core Processes ACS Subsystem Core Processes In TS/MP 2.3, the ACS subsystem core processes replace the TS/MP 2.0 LINKMON process. Together with the PATHMON process, the ACS subsystem controls communication between Pathsend requester processes and server classes. In terms of benefits, the ACS Subsystem provides higher Pathsend limits and better link management over TS/MP 2.0 LINKMON process.
ACS Subsystem Core Processes Managing the Pathsend Environment $ZCSnn processes respectively, where nn is the processor number), which are responsible for all Pathsend requesters executing in that processor. ACS subsystem core processes acquire links from the PATHMON process that controls the server class. The ROUT process then shares its links among the Pathsend requesters executing in its processor. The ACS subsystem core processes are visible to a PATHMON process but are not controlled by it.
Managing the Pathsend Environment ACS Subsystem Core Processes For more information about the commands listed in Table 6-2, see Section 10, PATHCOM Operation Commands, Section 11, PATHMON Environment Control Commands and Section 12, SERVER Commands. If you have TS/MP 2.3 (or later version) installed on your system, you need to configure and bring up the ACS subsystem processes using SCF commands. You cannot start ACS subsystem processes with TACL RUN commands.
Managing the Pathsend Environment Pathsend Management Tasks ACS Subsystem Memory Dumps Unlike TS/MP 2.0, the ACS subsystem core processes no longer halt the processor in case of internal product errors. Instead, ACS core processes stop themselves after creating memory abend files. Note. If one of the ACS core processes on a processor goes down, the remaining core processes on the same processor also go down. Issuing the SCF CONTROL command can restart the stopped core process on the processor.
Managing the Pathsend Environment • Specifying Security Server-class-level security Network Level Security For Pathsend processes to access server processes, this network conditions must be met: • • • The LINKMON process must be able to open the PATHMON process (to make link requests). The LINKMON process must be able to open the server processes (to send user requests). The PATHMON process must be able to open the server processes (to send startup messages).
Managing the Pathsend Environment Monitoring LINKMON Processes For example, these commands set the SERVER OWNER attribute to the user ID of the super user on the system 222 or \ABC, respectively: = SET SERVER OWNER 222.255,255 = SET SERVER OWNER \ABC.SUPER.SUPER If the user ID’s system is the same as the system in which PATHCOM is running, you need not specify the system number or name.
Monitoring LINKMON Processes Managing the Pathsend Environment Checking the Value for MAXLINKMONS To check the value that you defined for MAXLINKMONS and to check the number of LINKMON processes currently accessing your PATHMON environment, use the INFO PATHWAY command, as shown in this example: = INFO PATHWAY If you set MAXLINKMONS equal to 16 and there are currently four LINKMON processes that have one or more links to server classes within your PATHMON environment, the INFO PATHWAY command returns this
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 run the STATS SERVER command. See the description of the STATS SERVER Command. This section is divided into two parts: • • The first part describes server process performance statistics that the LINKMON process or ACS subsystem processes, 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 statistics show the amount of link manager resources used to communicate with a server class. Server statistics collected by LINKMON processes or ACS subsystem processes, and TCPs provide information about: • • 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.
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.
Tuning Your System by Using Statistics I/O Info REQ CNT REQ CNT indicates the number of requests for a link to a server that could not be satisfied immediately because of the unavaialability of a link or when the link manager is in the process of requesting a link. You can compare this number with the REQ CNT number for I/O INFO (see I/O Info earlier in this section) to determine what percentage of the transactions requesting a link to a particular server experienced some delay.
I/O Info Tuning Your System by Using Statistics Example 7-3. I/O INFO Section of Sample Server Statistics SERVER SERVME IN TCP TCP1* I/O INFO*: SEND REPLY 19 FEB 1996, 15:22:30 REQ CNT 33304 .. MAX TSIZE 2 2 . . . AVG TSIZE 2 2 . . I/O CNT 33304 IN LINKMON LM1 INTERVAL 10 MINS COUNT 1/5 25 SEP 1984, 11:50:25 . . .
Tuning Your System by Using Statistics Server Statistics Collected Only By the TCP REQ CNT Statistics are not provided for REPLY statements because there are no explicit requests for REPLY. I/O CNT Statistics are not provided for REPLY statements because there are no explicit requests for REPLY. Server Statistics Collected Only By the TCP Server statistics show the amount of link manager resources used to communicate with a server class.
Tuning Your System by Using Statistics Frequency Distribution Table 7-3 shows the response time statistics and what they indicate. Table 7-3.
Tuning Your System by Using Statistics Frequency Distribution Example 7-5. Sample Server Statistics With Frequency Distribution Table SERVER SERVME IN TCP TCP1* QUEUE INFO*: 19 FEB 1996, 15:26:14 % WAIT MAX WAITS AVG WAITS % DYNAMIC 99.8 7 2.38 99.9 I/O INFO*: MAX TSIZE AVG TSIZE I/O CNT SEND 2 2 33740 REPLY 2 2 RESPONSE TIME INFO (TIME VALUES IN SECS)*: SEND TO SERVERCLASS SUMMARY # MEAS AVG RESP MAX RESP MIN RESP STAND DEV 33739 0.50 2.51 0.01 0.49 FREQUENCY DISTRIBUTION*: TIME INTERVAL (0.
Frequency Distribution Tuning Your System by Using Statistics • There are fewer than 50 sample measurements collected at the time of the STATS request. In this case, this text appears at the bottom of the STATS SERVER display: FREQUENCY DISTRIBUTION:? MEASUREMENTS TAKEN • NOT PRODUCED: LESS THAN 50 SAMPLE At the fiftieth measurement, the time increment calculated is less than 0.01 second. In this case, this appears at the bottom of the STATS SERVER display: FREQUENCY DISTRIBUTION:? LESS THAN .
Tuning Your System by Using Statistics HP NonStop TS/MP System Management Manual—541819-007 7- 10 Frequency Distribution
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 through Section 7, Tuning Your System by Using Statistics. Note. This manual provides information specific to commands dealing with objects managed through the NonStop TS/MP product.
Command List Overview of PATHCOM Note. The CONTROL TERMs command must be issued when TERM is in the STOPPED state for COUPLE request. The relationships illustrated in Figure 8-1 apply for all of the PATHCOM commands and the PATHMON-controlled objects. Some PATHCOM commands affect only certain objects and their operation. For example, the CONTROL command affects only the PATHMON process and the FREEZE SERVER command affects only server classes. Note.
Command List Overview of PATHCOM Table 8-1.
Command and Object Relationships Overview of PATHCOM Table 8-1. PATHCOM Commands (page 3 of 3) PATHCOM Commands STATUS Description Valid Objects Displays the current status of any PATHMON-controlled object or a LINKMON process linked to a server class LINKMON*, PATHMON process, PATHWAY, SERVER * Although LINKMON is listed here as a valid object, it is not like other NonStop TS/MP objects.
Command Format Overview of PATHCOM Table 8-2. Commands and Objects Objects PATHCOM Commands PATHWAY PATHMON SHUTDOWN x SHUTDOWN2 x START x SERVER LINKMON x STATS x STATUS x x x STOP x x SWITCH x THAW x x 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.
Overview of PATHCOM Interactive Mode parentheses. In the third example, both attributes must be enclosed in parentheses because neither is the last in the list. SET SERVER PARAM A a, B b SET SERVER ( PARAM A a, B b ), ASSIGN aaaaa, bbbbb SET SERVER ( PARAM A a, B b ), ( ASSIGN aaaaa, bbbbb ) , & PRI 141 • You can embed comments within a line of commands or you can enter comments on separate lines. Enclose the comments in brackets if a PATHCOM command is on the same line.
Overview of PATHCOM Noninteractive Mode or: = command-1 = command-2 Pressing the terminal Break key during the execution of a PATHCOM command (described in Section 10, PATHCOM Operation Commands) cancels the command; control remains with PATHCOM and you can reenter the command. Pressing the Break key in all other instances, including after the PATHCOM prompt appears, returns the terminal to the TACL command interpreter without terminating PATHCOM.
Overview of PATHCOM • • • File Name Expansion $volumeIdentifies a physical disk pack mounted on a disk unit subvolumeIdentifies a disk file as a member of a related set of files as defined by the user file–identifierIdentifies a particular file within the subvolume File names of disk files are represented to HP subsystem programs by these four parts concatenated into a contiguous string. Each part is separated from the other by a period as follows: \node.$volume.subvolume.
Overview of PATHCOM OSS Pathnames OSS Pathnames An OSS pathname in the OSS attributes PROGRAM, STDIN, STDERR, and STDOUT can be an absolute pathname or a relative pathname. Case is significant. When specifying an OSS pathname longer than one line, use the PATHCOM continuation character (&) at the end of the line to indicate continuous input. If the pathname includes an ampersand (&) as part of the name and the ampersand occurs at the end of an input line, enter two ampersands.
Overview of PATHCOM • Relative Pathnames An expanded pathname has a forward slash as the final character. Caution. NonStop TS/MP makes no changes to existing OSS pathnames. If escape sequences or other non-printable characters are included in a pathname, unexpected results might occur. It is recommended that all characters in OSS pathnames be ASCII characters.
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. Note. When using TS/MP 2.3 or later version, it is recommended to use PDMCOM instead of PATHCOM because it can communicate with multiple PATHMONs simultaneously.
PATHMON and PATHCOM Startup Commands Starting the PATHMON Process run-option is one of the TACL RUN [D] command run options. For details about the RUN [D] run options, see the TACL Reference Manual. CPU number specifies the processor where the primary PATHMON process runs. 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.
PATHMON and PATHCOM Startup Commands Starting PATHCOM If you omit this parameter, output is directed to the TACL list file; this is typically the home terminal. In a production environment, it is recommended you specify a log file. 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.
PATHMON and PATHCOM Startup Commands Starting PATHCOM server classes). PATHCOM reads 132-byte records from the specified file until an end-of-file character or an EXIT command is encountered. 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.
Starting PATHCOM PATHMON and PATHCOM Startup Commands PRI number is the execution priority of the PATHCOM process. 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.
PATHMON and PATHCOM Startup Commands HP NonStop TS/MP System Management Manual—541819-007 9 -6 Starting PATHCOM
10 PATHCOM Operation Commands The commands for controlling and operating PATHCOM are: CMDCWD CMDVOL ERRORS EXIT FC HELP HISTORY OBEY OBEYVOL OPEN RESET SHOW ! Note. When using TS/MP 2.3 or later version, it is recommended to use PDMCOM instead of PATHCOM because it can communicate with multiple PATHMONs simultaneously. For more information on PDMCOM, see the TS/MP Release Supplement.
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.
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.
PATHCOM Operation Commands EXIT Command 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 run the ERRORS command.
FC Command PATHCOM Operation Commands • • • R (replacement-string) Replaces one or more characters. I (insertion-string) Inserts one or more characters. D (deletion-character) Deletes one character. 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).
HELP Command PATHCOM Operation Commands • If the following commands are entered at the PATHCOM prompt: \NSSYS.$VOL.SUBVOL 11> PATHCOM $X30Q: PATHCOM - T0845H02 - (30APR09) (C)2008-2009 Hewlett Packard Development Company, L.P.
HELP Command PATHCOM Operation Commands COMMANDS lists the names of all PATHCOM commands. specifies a particular PATHCOM command syntax to be displayed. When entering the name of the command, do not include the angle brackets. <“detail-name”> specifies a particular parameter syntax to be displayed. When entering the name of the parameter, include the angle brackets; do not include the quotation marks.
HISTORY Command PATHCOM Operation Commands In response, PATHCOM displays the syntax for a TERM parameter list as: ::= TERM * [ [ , ] ...
PATHCOM Operation Commands HISTORY Command Examples • When five commands are entered at the PATHCOM prompt: \NSSYS.$VOL.SUBVOL 11> PATHCOM $X30Q: PATHCOM - T0845H02 - (30APR09) (C)2008-2009 Hewlett Packard Development Company, L.P. = [ SERVER SRV1 is configured in $PM1 = OPEN $PM1 = ALTER SRV1, NUMSTATIC 1 = ALTER SRV1, DEBUG ON = ALTER SRV1, HOMETERM $ZTNT.
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 runs 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.
PATHCOM Operation Commands ! Command ! Command Use the ! command to execute an existing command. ! [ [-]number | string ] number is the number of a command line. If number is passed as -7, the 7th previous command is executed. string is the first character or characters of a previous command. Note. The ! command is supported by TS/MP 2.4 and is available only on systems running J06.05 and later J-series RVUs and H06.16 and later H-series RVUs.
PATHCOM Operation Commands • To execute a command starting with “op”, enter: = !op The following command is executed: = OPEN $PM1 HP NonStop TS/MP System Management Manual—541819-007 10 -18 ! Command
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 PATHCOM For detailed information about LINKMON processes and their use with Pathsend requesters, see the TS/MP Pathsend and Server Programming Manual. Note. When using TS/MP 2.3 or later version, it is recommended to use PDMCOM instead of PATHCOM because it can communicate with multiple PATHMONs simultaneously. For more information on PDMCOM, see the TS/MP Release Supplement.
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 run. A CONTROL PATHMON BACKUPCPU command is run.
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 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 MAXPARAMS number is the maximum number of PARAM messages that you can specify across all server classes in a given Pathway environment. number must be a value from 0 to 4095. The default is 0. This attribute sets the limit on the number of PARAM definitions that you can specify for Pathway server classes with the SET SERVER command.
PATHMON Environment Control Commands SET PATHWAY Command MAXTCPS 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. This attribute is mandatory. It has no default value. MAXTERMS number This attribute is specific to the Pathway/iTS product.
PATHMON Environment Control Commands SET PATHWAY Command This attribute is required. It has no default. If the value for MAXLINKMONS is 0, any attempt by a LINKMON process to access a server controlled by the PATHMON process fails. MAXPATHCOMS number is the maximum number of PATHCOM processes that can run simultaneously within Pathway. number must be a value from 1 through 100. The default value is 5. For other limits, see Configuration Limits and Defaults.
PATHMON Environment Control Commands SET PATHWAY Command If your environment does not support Pathway/iTS, it is recommended you specify 0 for the value. The default value is 32. MAXTMFRESTARTS 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. The default value is 5.
PATHMON Environment Control Commands SET PATHWAY Command Following are the file names that can be qualified by a node name when configuring a PATHMON environment. These names are designated as nodeindependent when the NODEINDEPENDENT attribute is set to ON.
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. The default is “N” (for TS/MP 2.0 and 2.1) and “O” (for TS/MP 2.3 and later versions). Note. For more information on TS/MP 2.4 and later versions, see the TS/MP Release Supplement Manual. Caution.
PATHMON Environment Control Commands SHUTDOWN Command (Old) SHUTDOWN Command (Old) The SHUTDOWN command stops the PATHMON-controlled objects. Note. The SHUTDOWN2 command replaces the SHUTDOWN command. It is recommended you use the SHUTDOWN2 command for a faster, more reliable means of stopping your Pathway environment. The SHUTDOWN command is still available to maintain backward compatibility.
PATHMON Environment Control Commands SHUTDOWN2 Command Examples This command stops all terminals, except those in a SUSPEND state, before stopping all server processes, Pathway/iTS TCPs, and the PATHMON process and notifying LINKMON processes or ACS subsystem processes: SHUTDOWN This command stops all PATHMON-controlled objects, including terminals in a SUSPEND state: SHUTDOWN!,WAIT The PATHMON process retries the SHUTDOWN!,WAIT command if a terminal, Pathway/iTS TCP, or other process, such as a LINKMON p
PATHMON Environment Control Commands SHUTDOWN2 Command AB or ABORT aborts all terminals and allows all other objects such as TCPs and server classes to complete outstanding work before stopping. The PATHCOM process is suspended until the shutdown request completes or until the Break key is pressed. After shutdown, the PATHCOM prompt is returned. IM or IMMEDIATE stops all server processes and Pathway/iTS TCPs immediately. The PATHCOM is suspended until the shutdown request completes.
SHUTDOWN2 Command PATHMON Environment Control Commands returned. If the timeout occurs and shutdown has not completed, the PATHCOM prompt returns without affecting the execution of the shutdown process. Using the Break Key During Shutdown You can use the Break key during shutdown to return the PATHCOM prompt without affecting the execution of the shutdown process.
SHUTDOWN2 Command PATHMON Environment Control Commands • • • • Command Type Commands Disabled During SHUTDOWN State Program commands (Pathway/iTS product only) ADD ALTER DELETE RUN Terminal commands (Pathway/iTS product only) ADD ALTER DELETE INSPECT RESUME START SUSPEND Tell commands (Pathway/iTS product only) DELETE TELL Use the ORDERLY option, for example, for epilogue processing (when the application requires the server process to write out totals before stopping).
PATHMON Environment Control Commands START PATHWAY Command START PATHWAY Command Use the START PATHWAY command to start a Pathway environment. START PATHWAY { COOL } [!] { COLD } [!] COOL starts the PATHMON-controlled objects using the configuration information contained in an existing PATHMON configuration file. All PATHWAY, PATHMON, and SERVER object definitions, as well as Pathway/iTS TCP, TERM, and PROGRAM object definitions, remain in the file.
PATHMON Environment Control Commands STATUS LINKMON Command Examples This command starts a Pathway environment and causes the PATHMON process to allocate a new PATHMON configuration file: START PATHWAY COLD! This command starts a Pathway environment but causes the PATHMON process to use the existing PATHMON configuration file: START PATHWAY COOL STATUS LINKMON Command Use the STATUS LINKMON command to display information about LINKMON processes that have links to server processes.
STATUS LINKMON Command PATHMON Environment Control Commands Display Format The format of the display returned by the STATUS LINKMON command is shown in Example 11-1. This format is similar to the one for the STATUS TCP command, except that the DETAIL option is not available with the STATUS LINKMON command. The fields are described below. Example 11-1. STATUS LINKMON Display Format LINKMON lm-name . . . STATE state . . . ERROR pw-error . . . INFO info . . . PROCESS process-name . . . CPU cpu . . .
STATUS PATHMON Command PATHMON Environment Control Commands STATUS PATHMON Command Use the STATUS PATHMON command to display the status of the PATHMON process, the PATHMON configuration file, and the logging files. This command also displays a list of the processes currently communicating with the PATHMON process. STATUS [ / OUT list-file / ] PATHMON OUT list-file directs output to the file that you specify; this could be a DEFINE name.
PATHMON Environment Control Commands STATUS PATHMON Command Explanation of the display fields (continued). Display Field Description LOG1 and LOG2 The type of logging defined, current state, and name of the indicated log file. Possible logging types are: S E The log file is open for status logging. The log file is open for event logging. Possible state values are: CLOSED OPEN The file is closed. The file is open.
STATUS PATHWAY Command PATHMON Environment Control Commands Display Field Description PID Process ID of the requester process (PATHMON, TCP, or LINKMON process) PAID Process-accessor ID of the requester process WAIT The reason a request is waiting. Possible values are: IO LOCK LOCK-QUEUE BUF LOG-QUEUE TIMEOUT PROG-DONE NEWPROCESS The request is waiting for an I/O operation to complete. The request is waiting for an object locked by another requester.
STATUS PATHWAY 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. COUNT number determines the number of times that the status screen is displayed until the Break key is used, or until the Pathway environment is shut downwhichever occurs first. The default count is 1.
STATUS PATHWAY Command PATHMON Environment Control Commands Example 11-4.
PATHMON Environment Control Commands Example Calculating Totals Totals for each object can be calculated from these displays as follows: Total… Is Calculated By Adding Together the Fields… Total server classes RUNNING + STOPPED OR THAWED + FROZEN+ FREEZE PENDING Total server processes RUNNING + STOPPED + PENDING Total TCPs (Pathway/iTS) RUNNING + STOPPED + PENDING Total terminals (Pathway/iTS) RUNNING + STOPPED + PENDING + SUSPENDED Example This command writes the status display to a file named
SWITCH PATHMON Command PATHMON Environment Control Commands Errors This table lists the most common error that can occur during the processing of the STOP PATHMON command: This Message… Is Displayed When… *1045* REQUEST NOT VALID FOR CURRENT STATE You have issued a STOP PATHMON command but the PATHMON process is not in the shuttingdown state. Issue a SHUTDOWN2 PATHWAY command before issuing the STOP PATHMON command.
PATHMON Environment Control Commands • SWITCH PATHMON Command After successfully executing a SWITCH PATHMON command, the PATHMON process logs this status message: STATUS - *1077* TAKEOVER BY BACKUP HP NonStop TS/MP System Management Manual—541819-007 11 -38
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 Examples These commands freeze the specified server classes: FREEZE SERVER CLASS-1 FREEZE (CLASS-2,CLASS-3) ! 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 configuratio
INFO SERVER Command SERVER Commands Display Format INFO SERVER displays both the server class attribute values you explicitly defined and default values for the attributes you did not explicitly define. The attributes are displayed in alphabetic order after PROCESSTYPE.
INFO SERVER Command SERVER Commands Examples These command requests information for two server classes: INFO (CLASS-2,CLASS-3) 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 \*.
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 HP NonStop TS/MP System Management Manual—541819-007 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 ]... ) | ( cpu (cpu-wt) [ , cpu (cpu-wt) ]...
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 cpu (cpu-wt) is the weight defined for the CPU. PATHMON stores the CPU weights in the PATHCTL file. It is used to create a new process. The processes are created on a CPU such that the percentage of processes running on a CPU to the total number of processes on all CPUs is almost equal to the defined weights. The CPU weight must be in the range of 1 through 100. The sum of all CPU weights must be 100. Note. Backup CPU cannot be specified when using CPU weights.
SET SERVER Command SERVER Commands available while the link manager is waiting for CREATEDELAY to expire, the link manager immediately uses that link. When the TCP calculates that no static link is available, it delays all future link requests to the PATHMON process by the value of CREATEDELAY. If CREATEDELAY is not specified, a default delay of 60 SECS is imposed. Note.
SET SERVER Command SERVER Commands This attribute is valid for Guardian and OSS server processes. DEFINE define-name , define-attribute-spec assigns a DEFINE definition as part of a server class definition. When a server process in the server class is created, the specified DEFINEs are included in the process context. define-name specifies a valid name to be assigned to the DEFINE. A DEFINE name can be from 2 through 24 characters in length.
SET SERVER Command SERVER Commands process, environment variables are available as an array of null-terminated strings, ending with a null pointer, pointed to by the external variable environ []. You can specify from 3 through 24,000 characters for the ENV attribute. (The length is calculated as the number of bytes of storage needed, in other words, the length after any quotes have been removed and a null byte added for each environment variable.
SET SERVER Command SERVER Commands In this example, whoever starts the PATHMON process must have WRITE and EXECUTE access to the server object file. If you omit this attribute, the operating system accesses all of the server code, including the user library object file, through the file that you define with the PROGRAM attribute. Defaults for file name expansion are based on values you specify for the CMDVOL command and the SET PATHWAY NODEINDEPENDENT attribute.
SET SERVER Command SERVER Commands System 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 and SET PATHWAY Command. If you omit this attribute, spaces are passed to the servers for the file name. This attribute is valid for Guardian server processes only. LIKE server-class sets the attribute values for the server class to those of the named server class.
SET SERVER Command SERVER Commands If you omit this attribute, the default is an unlimited number of links. It is strongly recommended that you set a value for MAXLINKS. Note. The value of MAXLINKS and the value of the TABLE OCCURS clause in the RECEIVE– CONTROL paragraph of your COBOL server programs must correspond with each other. The MAXLINKS value must be equal to or less than the TABLE OCCURS value.
SET SERVER Command SERVER Commands The number for MAXSERVERS minus the number for NUMSTATIC is the number of dynamic servers for the server class. Links to dynamic servers are granted to a TCP, LINKMON process, or ACS subsystem processes by the PATHMON process when a link request cannot be satisfied by a static server. Dynamic server processes are started by the PATHMON process only as the result of a link request; they are not started by the START SERVER command.
SET SERVER Command SERVER Commands PARAM parameter-name parameter-value assigns a string value to a parameter name. You can omit the parentheses if this parameter is the last one of the SET SERVER command. parameter-name specifies the name to which you assign parameter-value. The name must begin with an alphabetic character. parameter-value specifies a character string value that you assign to parameter-name.
SET SERVER Command SERVER Commands with a # (pound sign) and followed by one to seven alphanumeric characters. The first character must be a letter. If you omit this attribute, the default is a process name that the operating system assigns in the form $Xnnn, $Ynnn, or $Znnn. For better manageability, assign explicit server process names instead of letting the operating system assign the server process names.
SET SERVER Command SERVER Commands GUARDIAN-SWAP $volume specifies the Guardian name of the disk volume for the swap file formerly used by the operating system for memory swaps of the server data area. Allocation of this swap file is now handled by the Kernel Managed Swap Facility (KMSF) on behalf of the PATHMON process, and any value specified for this parameter is not used. However, if you specify a value for this parameter, it must represent an existing device, or an error occurs.
SET SERVER Command SERVER Commands The security attributes are the same as the Guardian file security attributes. The possible values are: “A” Any local user “G” A group member or owner “O” Owner only “-” Local super ID “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.
SET SERVER Command SERVER Commands If the file specified does not exist, it is created. If you omit this attribute, a null string is sent to the server process. This attribute is valid for OSS server processes only. STDOUT oss-pathname specifies the name of the OSS stdout (standard output) file to be used by the servers in this server class. This file is opened only for write operations.
Server Class DEFINEs SERVER Commands If you omit this attribute, the default is OFF. ON allows servers to lock and update audited files. The LINKMON, ACS subsystem processes, or TCP process opens the servers with a syncdepth of 0. OFF does not allow servers to lock and update audited files. The LINKMON, ACS subsystem processes, or TCP process opens the servers with a syncdepth of 1.
Server Class DEFINEs SERVER Commands You can specify the default volume and subvolume for a server class using the VOLUME attribute of the SET SERVER command or the VOLUME attribute of _DEFAULTS DEFINE. If you do not specify _DEFAULTS DEFINE, the PATHMON process uses the volume and subvolume you assigned with the VOLUME attribute. If you assign _DEFAULTS DEFINE and a VOLUME attribute, the PATHMON process ensures that these values correspond.
Server Class DEFINEs SERVER Commands • For information about configuring the NonStop Translation Server for NonStop TUXEDO, see the Pathway Translation Server for the NonStop TUXEDO System Manual.
SHOW SERVER Command SERVER Commands These SET SERVER commands show the use of parentheses to avoid ambiguity: SET SERVER ( PARAM SWITCH-1 ON , SWITCH-15 OFF ) , & MAXLINKS 10 SET SERVER (ARGLIST "arg 1", """Argument2"""), PRI 141, & (ENV env1="env1", env2="here is env2"), MAXLINKS 5 These command specifies a list of five arguments; the second and fourth argument are null strings: SET SERVER ARGLIST arg1,"",arg3,,arg5 These command specifies a list of five arguments; all arguments are null strings except f
SHOW SERVER Command SERVER Commands Example 12-1. SHOW SERVER Default and Guardian Display 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 When the PROCESSTYPE attribute is set to OSS but no other values have been defined, the same information is displayed.
START SERVER Command SERVER Commands The CWD attribute is displayed when a value is set either by the CMDCWD command or by the SET SERVER CWD command. All OSS pathnames, argument lists, and environment variables are displayed as quoted strings, regardless of whether there are embedded quotes (similar to the way PARAM values are displayed).
Examples SERVER Commands The startup protocol for servers consists of these steps: 1. The PATHMON process creates the server by calling the NEWPROCESS or PROCESS_CREATE_ procedure. The server process context includes all DEFINEs specified in the server class configuration (using the SET SERVER DEFINE command). 2. The PATHMON process sends the server a startup message.
STATS SERVER Command SERVER Commands ACS subsystem processes track statistics. The STATS attribute of the SET TCP command controls whether a TCP tracks its statistics. Note. LINKMON processes or ACS subsystem processes do not collect performance statistics. Performance statistics are collected only by the TCPs, which are configured in your environment only if you are running the Pathway/iTS product. For a discussion of statistics collections, see Section 7, Tuning Your System by Using Statistics.
STATS SERVER Command SERVER Commands The frequency distribution table is not generatedeven if you specify the FREQTABLE optionunder these conditions: • • There have been fewer than 50 response time measurements collected at the time of the STATS request. At the fiftieth measurement, the size of the time interval calculated is less than 0.01 second. INTERVAL number specifies the time period between the statistics displays, incremented in hours, minutes, or seconds.
STATUS SERVER Command SERVER Commands STATUS SERVER Command Use the STATUS SERVER command to display the current status of a server class. This command displays status information for server classes linked to link managers such as LINKMON processes. 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 ]...
STATUS SERVER Command SERVER Commands If the FREEZE option is specified with SERVER *, and no server classes are in the FREEZE-PENDING state, PATHCOM returns a prompt. SERVER * displays the status of all server classes defined for the Pathway environment. STATUS FREEZE displays the names of all server classes that are in the FROZEN or FREEZE-PENDING state. Display Format Without DETAIL Following is the format of the display returned by the STATUS SERVER command without the DETAIL option.
STATUS SERVER Command SERVER Commands Display Format With DETAIL Following is the format of the display returned by the STATUS SERVER command with the DETAIL option. The fields are described below. STATUS SERVER Display Format With DETAIL SERVER #RUNNING ERROR INFO server-name running pw-error info [freeze-state] . . . . . . . . . . . . PROCESS STATE ERROR INFO #LINKS WEIGHT process-name state pw-error info links weight . . . . . . . . . . . . . . . . . .
STATUS SERVER Command SERVER Commands Display Format, PROCESSES Attribute, Without DETAIL Following is the format of the display returned by the STATUS SERVER PROCESS or STATUS SERVER PROCESSES commands without the DETAIL option. The fields not already described are described below. STATUS SERVER PROCESS[ES] Display Format SERVER server-name . . . LINKER name . . . #RUNNING ERROR running pw-error . . . . . . LINK COUNT links . . . INFO info [freeze-state] . . .
STATUS SERVER Command SERVER Commands Display Format, FREEZE Attribute, Without DETAIL Following is the format of the display returned by the STATUS SERVER FREEZE command without the DETAIL option. The fields are described below. STATUS SERVER FREEZE Display Format SERVER STATE server-name . . . FREEZE STATE freeze-state . . . TERM term-name . . . FREEZE freeze-state . .
STOP SERVER Command SERVER Commands Errors This table lists the most common error that can occur during the processing of the STATUS SERVER command: This Message… Is Displayed When… ERROR - *1045* REQUEST NOT VALID FOR CURRENT STATE You have issued a STATUS SERVER command with the FREEZE option, but none of the server classes listed are in the FROZEN or FREEZEPENDING state.
STOP SERVER Command SERVER Commands permits you to obtain original functionality of the STOP command after attempting the new style OPEN/CLOSE method and waiting for the specified < scwait> time. Note. If the option from PATHCOM is specified with STOP SERVER command, it will try to stop the server even if the server is in hung state.PATHCOM will wait for the specified time and will return a command prompt after timeout.
THAW SERVER Command SERVER Commands Errors This table lists the most common error that can occur during the processing of the STOP SERVER command: This Message… Is Displayed When… *1059* FREEZE PENDING You have tried to issue a STOP SERVER command while a FREEZE SERVER command is still in progress; the STOP SERVER command fails. To stop the server, wait until the freeze has completed, then reissue the STOP SERVER command. Examples This command stops all the server classes in the Pathway environment.
Wild Card support in PATHCOM 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.
Wild Card support in PATHCOM SERVER Commands • THAW Note. 1. Wild card support using only * in the command is applicable to TS/MP PATHCOM. (Refer Example 12-2) 2. Wild card support by specifying "*" in the SERVER object name is applicable to TS/MP 2.3 PATHCOM and later versions.(Refer Example 12-3). For more information on TS/MP 2.3 and later versions, see the TS/MP Release Supplement. Example 12-2 shows the usage of wild card using only * in the command. Example 12-2.
SERVER Commands Usage Considerations for SET SERVER TIMEOUT Attribute Usage Considerations for SET SERVER TIMEOUT Attribute If a server process is delayed in its request processing (for example: when it is stuck behind a lock, is blocked by a higher priority process, or due to any performance pitfall), TS/MP may time out the request using the timeout value from either the SET SERVER TIMEOUT configuration parameter or the timeout argument of a SERVERCLASS_SEND_ call, SERVERCLASS_DIALOG_BEGIN_call or SERVER
13 PATHMON Messages (Numbers 1000-1499) 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.
Operating System Error Numbers PATHMON Messages (Numbers 1000-1499) from the STATUS TERM, DETAIL command. The additional information is placed at the end of the error-message text and starts with three dashes ( --- ): Additional Error Information Field Description INST CODE inst-code The instruction code of the program unit. AT OFFSET %inst-addr The instruction address of the program unit.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1002 *1002* TERM term-name, ABORTED Cause. The specified TERM object has been aborted. Effect. None Recovery. Informational message only; no corrective action is needed. 1003 *1003* object, ALREADY STARTED Cause. The named entity is already running. 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.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. Determine why the PATHMON process abended by checking the NonStop Kernel errors in messages logged just before this message, then restart the PATHMON environment.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Effect. The operation fails. Recovery. Stop the PATHMON environment before changing the configuration. 1010 *1010* PATHWAY NOT CONFIGURED Cause. An attempt was made to run a command while the PATHMON process was not in the RUNNING state. Only the SET PATHMON and SET PATHWAY commands can be run while the PATHMON process is not running. Effect. The command fails. Recovery. Configure the PATHMON environment.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1013 *1013* object-name, EMPTY ENTRY Cause. An entry that was supposed to contain the description of an object (for example, a server) is empty. This is an internal error. Effect. The operation that needed to use the entry cannot complete. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1016 *1016* TCP tcp-name, FAILED Cause. A TCP stopped abnormally even though a stop command was not issued. Effect. The TCP is unavailable. Recovery. Determine the cause of failure, then restart the TCP. 1017 *1017* PATHCTL FILE ERROR (errnum) Cause. A file-system error (errnum) occurred during an I/O operation to the PATHMON configuration file. Effect. The I/O operation fails. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1020 *1020* PATHMON, LOG1 FILE ERROR (errnum) Cause. A file-system error (errnum) occurred during an I/O operation to the LOG1 file. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 1021 *1021* PATHMON, LOG2 FILE ERROR (errnum) Cause. A file-system error (errnum) occurred during an I/O operation to the LOG2 file. Effect.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1024 *1024* object-name, ILLEGAL FILE NAME (errnum) Cause. An invalid file name was detected in the definition of the specified object. errnum identifies the file-system error number. Effect. The request that needed the object fails. Recovery. Make sure that all Open Systems Services (OSS) pathnames are on the same system node as the PATHMON process; OSS processes cannot be spawned on a remote system.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Effect. The PATHMON process rejects the request. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1030 *1030* PATHMON, LOG2 FILE OPENED Cause. The LOG2 file is open. Effect. None Recovery. Informational message only; no corrective action is needed. 1031 *1031* REQUIRED PATHWAY OR PATHMON CONFIGURATION PARAMETER NOT SET Cause. A required PATHMON or PATHWAY object attribute is not defined. Effect. The operation fails. Recovery. Define the required attribute.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1033 *1033* PATHMON, NO INTERNAL FREESPACE AVAILABLE Cause. There is insufficient space in the PATHMON process’s free-space table. Effect. The operation fails. Recovery. Contact your HP representative for assistance. 1034 *1034* link manager-name, NO SERVER AVAILABLE FOR REQUESTING TCP Cause. The PATHMON process cannot grant a link to a TCP or a LINKMON process because no server processes are available.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1037 *1037* object-name, PARTIAL ENTRY DELETED (%internal-id) Cause. An extraneous entry was deleted from the PATHMON configuration file during a cool start. These entry types are deleted: • • • Temporary TERM entries that were created for a RUN PROGRAM request. This entry type only applies is you are running the Pathway/iTS product.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Effect. The call to DEVICEINFO2 and the request fails. This error is not logged, but is simply returned to the operator. Recovery. For information regarding the specified error, see to the Guardian Procedure Errors and Messages Manual. 1041 *1041* PATHMON, REQUEST HANDLER : < nested-message > Cause. An error occurred during request initiation. Effect. The request fails. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1046 *1046* object-name, FILE-SYSTEM ERROR (errnum) Cause. A file-system error (errnum) occurred. 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. 1047 *1047* object-name, STOPPED : < nested-message > Cause. The specified object has stopped. Effect.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1050 *1050* PATHMON, SYSMSG HANDLER : < nested-message > Cause. An error occurred while the PATHMON process was processing a system message. The error is indicated by the nested-message. Effect. The effect depends on the particular error that occurred. Recovery. For additional information, see the description associated with the nested message. 1051 *1051* TCP tcp-name, EXCEEDS THE LIMIT ON PATHMON OPENERS. Cause.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1054 *1054* link manager-name, TCP FAILED DURING REQUEST Cause. The TCP or LINKMON process failed during a request. Effect. The request is not completed. Recovery. Determine the cause of the TCP or LINKMON process failure by checking the errors in messages logged just before this message. After correcting the cause of the failure, restart the TCP (this step is not needed if AUTORESTART is specified for the TCP).
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Effect. None Recovery. Informational message only; no corrective action is needed. 1058 *1058* FREEZE IN PROGRESS Cause. A freeze request for the server is already in progress. 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.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1062 *1062* MUST BE FROZEN Cause. A STOP SERVER command was issued before the server class was frozen. Effect. The command fails. Recovery. Reissue the command after the server class is frozen. 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.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1067 *1067* INVALID INTERNAL IDENTIFIER FROM TCP (%internal-identifier) Cause. A TCP or LINKMON process request specified an entity that is not known to the PATHMON process. This error is an internal error. Effect. The request fails. Recovery.
PATHMON Messages (Numbers 1000-1499) 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. 1069 *1069* ERROR FROM SYSTEM PROCEDURE Cause. The operating system returned an error on a call to a Guardian procedure. Effect. The effect depends on the error. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. For information concerning the CHECKPOINT error, see the Guardian Procedure Calls Reference Manual. 1072 *1072* PATHMON, CREATE BACKUP FAILURE : < nested-message > Cause. The PATHMON process could not create its backup process. The nested message indicates the reason. Effect. The PATHMON process runs without a backup. Recovery. For additional information, see the description associated with the nested message.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. If the primary processor failed, reload the processor so that the PATHMON process can create a backup process. If a PRIMARY or SWITCH command was run, this is an informational message only; no corrective action is needed. 1078 *1078* PATHMON, FATAL ERROR ( %P-register ) Cause. A PATHMON process internal-consistency check failed. This is an internal error. Effect. The PATHMON process terminates.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1080 *1080* PATHMON, TRAP: T=%trap S=%s-reg P=%p-reg E=%e-reg L=%l-reg Cause. A software or hardware failure resulted in a trap. This is an internal error. These values give the process environment at the time the PATHMON process failed: %trap-no is the number of the trap for use with DEBUG %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.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1083 *1083* link manager-name, LINE TO TCP IS DOWN Cause. The Expand link to the external PATHMON environment is down. Effect. The PATHMON process cannot access the specified LINKMON process or TCP. Recovery. Establish a link to the system in which the LINKMON process or TCP is running. 1085 *1085* PATHMON MUST NOT RUN WITH HIGHPIN SET Cause. You attempted to set the HIGHPIN attribute to ON for the PATHMON process. Effect.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1088 *1088* TERMINAL ABORTED BY OPERATOR Cause. The terminal running the program was aborted by the ABORT TERM command. Effect. The terminal’s operation terminates. Recovery. Informational message only; no corrective action is needed. 1089 *1089* TERMINAL ABORTED BECAUSE OF ERROR Cause. The terminal running the program encountered an error that caused the terminal to suspend. Effect. The terminal’s operation is aborted. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1093 *1093* object-name, BACKUP PROCESSOR DOWN Cause. The backup processor for the PATHMON process or for the TCP is not running. Effect. A backup process cannot be created. Recovery. Reload the processor. 1094 *1094* PATHMON, BACKUP PROCESS FAILED Cause. The PATHMON backup process abended or stopped unexpectedly. Effect. The PATHMON process creates a backup process, if possible. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1100 *1100* TCP tcp-name, TOO MANY TCP ENTRIES Cause. The number of TCP descriptions has reached the maximum value specified for the MAXTCPS attribute of the SET PATHWAY command. Effect. The ADD TCP command fails. Recovery. Shut down the PATHMON environment. Increase the value of the MAXTCPS attribute (assuming it is not at the maximum allowable value). Reissue the ADD TCP command. 1101 *1101* TERM term-name, TOO MANY TERM ENTRIES Cause.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. Increase the value of the MAXSERVERPROCESSES attribute and reissue the ADD SERVER or ALTER SERVER command. 1104 *1104* SERVER server-class, TOO MANY STARTUP ENTRIES Cause. The number of server startup definitions has reached the maximum value specified for the MAXSTARTUPS attribute of the SET PATHWAY command. Effect. The ADD SERVER or ALTER SERVER command fails. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. Increase or decrease the value of the MAXTELLS attribute, depending on the cause of the error. 1108 *1108* PROGRAM program-unit-name, TOO MANY PROGRAM ENTRIES Cause. The number of PROGRAM descriptions has reached the maximum value specified for the MAXPROGRAMS attribute of the SET PATHWAY command. Effect. The ADD PROGRAM command fails. Recovery. Increase the value of the MAXPROGRAMS attribute and reissue the ADD PROGRAM command.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1114 *1114* PATHMON, CP TABLE FULL - BACKUP BEING RE-INITIALIZED Cause. The PATHMON process cannot send checkpoint information to its backup process due to an internal condition. Effect. The backup is stopped and automatically recreated. Recovery. Informational message only; no corrective action is needed. 1115 *1115* TCP tcp-name, TCP REFRESHED Cause.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1118 *1118* SELECTION NOT APPLICABLE Cause. The selection criteria does not apply to the specified objects because there is no association between the objects. Effect. The command fails. Recovery. Reissue the command, specifying objects that have a relationship with each other. 1119 *1119* TERM term-name, AUTO ABORTED Cause. The specified suspended terminal automatically aborted before being restarted with AUTORESTART. Effect. The terminal abends.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1122 *1122* PATHMON, BACKUP PROCESS STOPPED Cause. The PATHMON backup process was stopped by its primary process. This message normally occurs after the CONTROL PATHMON, BACKUPCPU command causes the backup process to change from one processor to another. Effect. The PATHMON backup process is down. A new backup is created in the new processor as soon as possible. Recovery. Informational message only; no corrective action is needed.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. For information concerning the specified ALLOCATESEGMENT error, see the Guardian Procedure Errors and Messages Manual. 1125 *1125* PATHMON, USESEGMENT ERROR (errnum) Cause. An error occurred, identified by the error number, on a call to the USESEGMENT procedure. Effect. The PATHMON process is unable to select a particular extended data segment. The PATHMON process terminates. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Effect. The requests fail. Recovery. Use version C00 or later of the HP NonStop operating system and the PATHMON process. 1136 *1136* EMSINIT ERROR (%errnum) Cause. An error occurred, identified by the error number, on a call to the EMSINIT procedure. 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.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1039 *1139* EVENTFORMAT NOT SUPPORTED FOR THIS DEVICE Cause. An attempt was made to perform event message logging to a terminal, printer, or operator process created with a version of the HP NonStop operating system previous to the C00 version. Effect. The event message logging fails. Recovery. Send the event message to a device or process that supports event formatting. 1140 *1140* DEFINES SPECIFIED AT PATHMON CREATION ARE IGNORED Cause.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1143 *1143* DEFINE NAME IN SAVED DEFINE IS INCORRECT Cause. The name of the DEFINE definition being added to a server class caused an internal conflict within the PATHMON process. Effect. The DEFINE definition is not added. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1146 *1146* SERVER server-name, THAW NOT COMPLETED Cause. A THAW SERVER request is in progress. Effect. The request issued to the frozen server fails. Recovery. Reissue the command after the server has successfully thawed. 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.
PATHMON Messages (Numbers 1000-1499) • • • • 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-1499) PATHMON Messages Effect. None Recovery. Informational error message; no corrective action is needed. 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.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1157 *1157* PATHCTL FILE NOT ACCESSIBLE Cause. A command has been issued that accesses the PATHMON configuration file, but the file is not accessible due to a previously occurring file-system error. The cause of the file-system error is noted in message 1156 in the log. This message is not logged. Effect. The command fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1159 *1159* SERVER object-name, OSS PROCESS CREATION FAILURE: (process-creation-detail) Cause. An error occurred while the PATHMON process was trying to create the specified OSS server process. Effect. The server process is not created. Recovery. OSS server processes are created by calls to the Guardian PROCESS_SPAWN_ procedure. For additional information, see the detailed description in this message.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages Recovery. For additional information, see the descriptions of the RESIZESEGEMENT or CHECKRESIZESEGMENT procedures in the Guardian Procedure Calls Reference Manual. 1163 *1163* LICENSING ERROR: PATHWAY PRODUCTS MUST BE LICENSED Cause. PATHMON could not start up because it could not confirm that either the NonStop TS/MP product or the Pathway /TS product is licensed for your site. Effect. System startup fails. Recovery.
PATHMON Messages (Numbers 1000-1499) PATHMON Messages 1167 *1167* TERM , TERM SHOULD BE IN STOPPED STATE Cause. You have issued a CONTROL TERM COUPLE request when the TERM is not in the STOPPED state. Effect. The request is not completed successfully. Recovery. Ensure that the TERM is in the STOPPED state before issuing the COUPLE request.
14 PDMCOM Messages (Numbers 1500-1999) This section describes the messages generated by the PDMCOM process.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1501 *1501* Failure starting process-name process Cause. PDMCOM fails to launch the process indicated by process-name. The displayed error message will have more information about the syntax error. Effect. The command fails. Recovery. Correct the failure condition indicated in the error message and issue the command again. 1502 *1502* History buffer is empty Cause. FC command was the first command to be issued at the PDMCOM prompt. Effect.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages Effect. HELP command, issued to receive help on the PDMCOM commands or the PDMCOM error numbers, fails. Recovery. Change the file code to 101. If the file is not in a readable format, reinstall the product. 1506 *1506* No help available for that topic Cause. No help is available for the text entered after the help keyword.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1509 *1509* FC String too long Cause. The string entered with FC command is too long. Effect. The command fails. Recovery. This error is very unlikely. Contact your Global Mission Critical Support Center (GMCSC) with a description of the application task that was in progress when the error was encountered. 1510 *1510* Invalid command for object type. Cause. PDMCOM was not able to parse the command correctly. Effect. The command fails. Recovery.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1513 *1513* INTERNAL ERROR - . Cause. Some unexpected error occurred. Effect. The command is aborted. Recovery. Take appropriate action depending on the error message. 1514 *1514* LOCK FAILED FOR SERVER IN ENVIRONMENT . Cause. The server entry, for which a FREEZE, STOP, ALTER, THAW, START, or ALTER-DOMAIN command was issued, is already locked. Effect. The command is aborted.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1517 *1517* NONEXISTENT DOMAIN. Cause. The specified domain name does not exist. Effect. The domain is not opened. Recovery. Specify the correct domain name and reissue the command. 1518 *1518* NEW REQUEST QUEUING FAILED. Cause. Internal request of the ALTER-DOMAIN command to queue Pathsend requests failed. Effect. The command is aborted. Recovery. Reissue the ALTER-DOMAIN command. 1519 *1519* NEW REQUEST PROCESSING FAILED. Cause.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1521 *1521* PATHMON NOT PART OF DOMAIN . Cause. The PATHMON process specified with the PATHMON attribute of the ALTER-DOMAIN command is not a part of the domain opened by the earlier OPEN command. Effect. The command is aborted. Recovery. Specify the correct PATHMON name and reissue the command. 1522 *1522* SERVERCLASS NOT PART OF PATHMON . Cause.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1525 *1525* MAX LIMIT REACHED. Cause. The number of CONTROL DOMAIN PARTITON command reached its maximum value—128. Effect. The command is rejected. Recovery. Reduce the number of partition requests. 1526 *1526* ACS INFRASTRUCTURE IS SHUTTING DOWN. Cause. The command is issued when the ACS infrastructure is shutting down. Effect. The command is rejected. Recovery. Start the ACS Infrastructure and then reissue the command.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages Effect. The command fails. Recovery. Remove the FC command from the OBEY file and reissue the command. 1530 *1530* REDISPLAY COMMAND IS INVALID IN OBEY FILE. Cause. The Redisplay command is issued in an OBEY file. Effect. The command fails. Recovery. Remove the Redisplay command from the OBEY file and reissue the command. 1531 *1531* RE-EXECUTE COMMAND IS INVALID IN OBEY FILE. Cause. The Reexecute command is issued in an OBEY file. Effect.
PDMCOM Messages (Numbers 1500-1999) PDMCOM Messages 1534 *1534* OBEY FILENAME IS MISSING. Cause. The OBEY file name is not supplied. Effect. The command fails. Recovery. Specify an OBEY file name and reissue the command. 1535 *1535* NON-PRINTABLE CHARACTERS IN OBEY FILE. Cause. The OBEY file supplied contains non-printable characters. Effect. The command fails. Recovery. Check the OBEY file supplied. Remove any non-printable characters from the OBEY file and reissue the command.
15 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 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. Make sure that OSS pathnames (other than those specified for the CWD attribute or the CMDCWD command) do not have a forward slash (/) as the last character.
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.
PATHCOM Messages (Numbers 2000-2999) PATHCOM Messages 2079 *2079* ILLEGAL CPU WEIGHT Cause. The CPU weight is not in the range of 1 through 100. Or, summation of all the weights is not equal to 100. Effect. The command fails. Recovery. Redefine the CPU weight with a correct value.
PATHCOM Messages (Numbers 2000-2999) HP NonStop TS/MP System Management Manual—541819-007 15 -20 PATHCOM Messages
16 Link Manager Messages (Numbers 3000-3999) This section describes the messages logged by the PATHMON process on behalf of link managers—the LINKMON process, 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 3100 *3100* link manager-name, ERROR DURING SERVER OPEN (errnum) Cause. A file-system error occurred while a server process was being opened. 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.
Link Manager Messages (Numbers 3000-3999) • • LINKMON 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.
Link Manager Messages (Numbers 3000-3999) LINKMON Messages Recovery. Contact your Global Customer Support Center (GCSC). 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.
17 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 HP NonStop TS/MP System Management Manual—541819-007 17- 4
18 ACS Subsystem Messages Introduction Note. The messages described in the section are a subset of the messages in the messagenumber range 1000 through 1071 that are reported by ACS subsystem processes. The messages reported by TCPs are described in the Pathway/iTS Management Programming Manual.s All messages returned by the PATHMON environment are logged by the PATHMON process. However, some messages in some number ranges represent events and errors reported to the PATHMON process by other processes.
Event-Message SPI Format ACS Subsystem Messages ACS subsystem name in the NonStop OS APPCLSTR ACS subsystem name abbreviation ACL External ACS subsystem identifier for release TS/MP 2.1. This identifier occurs in event message text, which is typically produced by EMS event printing distributors for EMS formatted event messages logged by ACS subsystem processes. TANDEM.APPCLSTR.
Unlisted Tokens ACS Subsystem Messages ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN Contains the value ZSPI-VAL-FALSE if the value of ZACL-TKN-EVENT-LEVEL is less than ZACL-VAL-EVENT-LEVEL-WARNING. Contains the value ZSPI-VAL-TRUE if the value of ZACL-TKN-EVENT-LEVEL is greater than or equal to ZACL-VAL-EVENT-LEVEL-WARNING. ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT Contains the ACS subsystem event message number.
ACS Event Severity Levels ACS Subsystem Messages ACS Event Severity Levels Event severity levels indicate the impact (on ACS subsystem resources and processes) of an event occurrence detected by an ACS subsystem process. Every event occurrence logged by the ACS subsystem indicates the severity of that occurrence.
ACS Subsystem Messages EMS Message Range 1000 through 1009 generated the event message continues to accept requests and perform other operations. Typically, error events require correcting the error condition and trying the operation again. ZACL-VAL-EVENT-LEVEL-FATAL Indicates that an ACS subsystem process encountered a condition that prevented it from performing any more operations. The process terminates immediately, which aborts any operations that it had in progress.
ACS Subsystem Messages EMS Message Range 1000 through 1009 1002: ZACL-EVT-BACKUP-LAUNCH-ERROR The domain coordinator process cannot create a backup process in the specified CPU on the local system because the PROCESS_LAUNCH_() operation failed.l Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT.
ACS Subsystem Messages EMS Message Range 1000 through 1009 1003: ZACL-EVT-BACKUP-ABENDED The backup domain coordinator process terminated unexpectedly. ] Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-CPU-NUMBER token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT. Conditional Tokens ZACL-TKN-EVENT-TERM-STOPPER ZACL-TKN-EVENT-TERM-SSID ZACL-TKN-EVENT-TERM-TEXT token-type ZSPI-TYP-PHANDLE. token-type ZSPI-TYP-SSID.
ACS Subsystem Messages EMS Message Range 1000 through 1009 ZACL-TKN-EVENT-TERM-SSID contains the SPI subsystem identifier associated with the process-termination operation. This token is omitted if no subsystem identifier was associated with the termination. ZACL-TKN-EVENT-TERM-TEXT contains the termination text associated with the process-termination operation. This token is omitted if no termination text was associated with the termination. Effect.
ACS Subsystem Messages EMS Message Range 1000 through 1009 ZACL-TKN-EVENT-PROCESS-NAME contains the name of the process that was not created. ZACL-TKN-EVENT-ERROR-CODE contains the process-creation error code returned by the PROCESS_LAUNCH_() procedure. ZACL-TKN-EVENT-ERROR-DETAIL contains additional information about the process-creation error returned by the PROCESS_LAUNCH_() operation. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message.
EMS Message Range 1000 through 1009 ACS Subsystem Messages 1005: ZACL-EVT-CP-ABENDED An ACS subsystem process terminated unexpectedly.] Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-PROCESS-NAME ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT.
EMS Message Range 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-TERM-STOPPER contains the process handle of the process that caused the termination. This token is included only if the process was stopped externally. ZACL-TKN-EVENT-TERM-SSID contains the SPI subsystem identifier associated with the process-termination. This token is omitted if no subsystem identifier was associated with the termination.
EMS Message Range 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-PROCESS-NAME contains the name of the failed process. ZACL-TKN-EVENT-ERROR-CODE contains the file-system error code returned by the failed operation. ZACL-TKN-EVENT-FILE-NAME contains the name of the Guardian file, device, or process accessed by the failed operation. This token is omitted for Guardian procedures that do not operate on files but that, nevertheless, report failures using file-system error codes. Effect.
ACS Subsystem Messages EMS Message Range 1000 through 1009 ZACL-TKN-EVENT-FILE-NAME contains the path name of the OSS file or directory that was accessed by the failed operation. This token is omitted for OSS procedures that do not operate on files or directories. Effect. The operation associated with the OSS operation is aborted. Recovery. Correct the condition that caused the OSS error and try the operation again.
ACS Subsystem Messages EMS Message Range 1000 through 1009 Effect. The operation associated with the process-management operation is aborted. Recovery. Correct the condition that caused the error and try the operation again. 1009: ZACL-EVT-PATHSEND-ERROR An ACS subsystem process invoked an internal Pathsend or ACS subsystem link manager procedure and the operation failed unexpectedly.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-SERVER-NAME contains the PATHMON process name and server class name supplied to the failed operation, separated by a period. This token is omitted for link manager procedures that do not operate on server classes. Effect. The ACS subsystem operation associated with the failed operation is aborted. Recovery. Correct the condition that caused the error and try the operation again.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-ERROR-DETAIL contains the memory management error detail code returned by the failed operation. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message. Effect. The process that invoked the failed operation terminates abnormally and produces a SaveAbend file. Recovery.
EMS Messages 1010 through 1019 ACS Subsystem Messages 1012: ZACL-EVT-BINSEM-ERROR An ACS subsystem process invoked a Guardian semaphore-system procedure and the operation failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCEDURE ZACL-TKN-EVENT-SEGMENT-ID ZACL-TKN-EVENT-ERROR-CODE token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT.
EMS Messages 1010 through 1019 ACS Subsystem Messages 1014: ZACL-EVT-BINSEM-ABANDONED A process terminated while holding the lock on one of the ACS subsystem shared memory semaphores. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-SEGMENT-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. Event-Message Text 1014 - Process failed holding memory segment segment-id semaphore Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL.
EMS Messages 1010 through 1019 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-PROCEDURE contains the name of the Guardian memory-pool management procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-SEGMENT-ID contains the identifier of the memory segment containing the pool that was being accessed by the failed operation.
ACS Subsystem Messages EMS Messages 1010 through 1019 ZACL-TKN-EVENT-SEGMENT-ID contains the identifier of the memory segment containing the pool from which space was to be allocated. This token is the subject of the event message. Effect. The process that failed to allocate space from the memory segment terminates immediately. Recovery. Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the problem occurred.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-CREATOR-ID contains the process-creator user identifier of the unauthorized requester process. ZACL-TKN-EVENT-FILE-NAME contains the file name of the ACS subsystem process that the unauthorized process supplied to the OPEN or FILE_OPEN_ operation. ZACL-TKN-EVENT-PROCESS-NAME contains the named process descriptor of the process that sent the unauthorized OPEN request. This token is omitted if the unauthorized process is unnamed. Effect.
EMS Messages 1010 through 1019 ACS Subsystem Messages 1019: ZACL-EVT-INCOMP-RQST-VER Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-ID token-type ZACL-TYP-EVENT-LEVEL token-type ZSPI-TYP-PHANDLE Event-Message Text 1019 - Incompatible request version received from process process-id Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
EMS Messages 1020 through 1029 ACS Subsystem Messages EMS Messages 1020 through 1029 1020: ZACL-EVT-INVALID-RPLY-MSG An ACS subsystem process received an invalid reply message or a reply message that has an incompatible version. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-PHANDLE.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1021: ZACL-EVT-PROTOCOL-ERROR An ACS subsystem process detected a protocol (operation order) error by another system process. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-PHANDLE. Event-Message Text 1021 - Protocol error in communication with process processid Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-ERROR.
ACS Subsystem Messages EMS Messages 1020 through 1029 ZACL-TKN-EVENT-PROCESS-NAME contains the name of the PATHMON process. This token is the subject of the event message. Effect. If the I/O operation was initiated in response to a send operation, the send operation fails with Pathsend error FEScPathmonConnect and file-system error FETIMEDOUT. The ACS subsystem attempts to close communication to this PATHMON process.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1024: ZACL-EVT-PATHMON-IO-ERROR An I/O operation from the ACS subsystem to a PATHMON process failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-NAME ZACL-TKN-EVENT-ERROR-CODE token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INT.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1025: ZACL-EVT-PATHMON-OPEN-ERROR An attempt to open a PATHMON process failed. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. Event-Message Text 1025 - PATHMON process-name OPEN operation failed, error errnum Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
EMS Messages 1020 through 1029 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the PATHMON process. This token is the subject of the event message. Effect. The send operation fails with Pathsend error FEScPathmonMessage and filesystem error FEOK. Recovery. Try the send operation again. If the problem persists, check the PATHMON process. You may need to shutdown and restart your application.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1028: ZACL-EVT-PATHMON-INVALID-MAT An ACS subsystem process received an invalid message from a PATHMON process. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-NAME token-type ZACL-TYP-EVENT-LEVEL token-type ZSPI-TYP-STRING. Event-Message Text. 1028 - Invalid message received from PATHMON process-name Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
EMS Messages 1030 through 1039 ACS Subsystem Messages ZACL-TKN-EVENT-CPU-NUMBER contains the number of the physical CPU that was started on the system where the event message was generated. This token is the subject of the event message. Effect. Pathsend operations initiated in the CPU no longer fail with FESCLINKMONCONNECT errors. Recovery. This is an informational message only; no corrective action is needed.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1031: ZACL-EVT-LOG-FILE-ERROR An ACS subsystem process encountered an error while writing an event message to the configured LOG1 or LOG2 event log file. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCEDURE ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-FILE-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-STRING. Event-Message Text.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1032: ZACL-EVT-LOG1-OPENED The LOG1 event log file was opened successfully. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-FILE-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. Event-Message Text. 1032 - LOG1 opened on file file-name Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-STATUS. ZACL-TKN-EVENT-FILE-NAME contains the Guardian name of the event log file.
EMS Messages 1030 through 1039 ACS Subsystem Messages ZACL-TKN-EVENT-FILE-NAME contains the Guardian name of the event log file. This token is the subject of the event message. Effect. None. Recovery. If the event was due to an error on the log file, check the previously issued event message for a detailed description of the problem. If the event was issued in response to an operator command, this is an informational message only; no corrective action is needed.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1035: ZACL-EVT-LOG2-CLOSED The LOG2 event log file was closed either in response to an operator command or because an error occurred while writing to the log file. If this event was due to an error on the log file, a previously issued event message described the error. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-FILE-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING.
EMS Messages 1030 through 1039 ACS Subsystem Messages ZSPI-TKN-EVENT-ENV-NAME contains the PATHMON process name supplied to the Pathsend operation. This token is the subject of the event message. Effect. The Pathsend operation fails with an FESCPATHMONCONNECT error and a FENOSUCHDEV file-system error detail. Recovery. Correct the Pathsend requester program or start the named PATHMON process.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1038: ZACL-EVT-SERVER-FILE-ERROR A Guardian file-system operation on a server process failed unexpectedly or completed with an unexpected error code. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-SERVER-NAME ZSPI-TKN-MANAGER ZACL-TKN-EVENT-PROCEDURE ZACL-TKN-EVENT-PROCESS-ID ZACL-TKN-EVENT-FILE-NAME ZACL-TKN-EVENT-ERROR-CODE token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-FNAME32. token-type ZSPI-TYP-STRING.
EMS Messages 1040 through 1049 ACS Subsystem Messages ZACL-TKN-EVENT-FILE-NAME contains the process file name that identifies the server process and that was used by the failed operation. ZACL-TKN-EVENT-ERROR-CODE contains the file-system error code returned by the failed operation. Effect. The Pathsend operation associated with the file-system operation is aborted. Recovery. Correct the condition that caused the operation to fail.
ACS Subsystem Messages EMS Messages 1050 through 1059 Effect. The Pathsend operation fails with an FESERVERLINKCONNECT Pathsend error and FESECVIOL file-system error detail. Recovery. None. This event message indicates a possible attempt to breach the security of a Pathway application. EMS Messages 1050 through 1059 TS/MP 2.1 does not contain messages in this number range.
EMS Messages 1060 through 1069 ACS Subsystem Messages 1063: ZACL-EVT-INVALID-BACKUP-CPU An invalid CPU number was specified in the domain coordinator process startup string. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. Event-Message Text 1063 - Invalid backup CPU specified: cpu-number Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT.
ACS Subsystem Messages EMS Messages 1060 through 1069 ZACL-TKN-EVENT-PROCESS-NAME contains the reserved process name that is currently being used. This token is the subject of the event message. Effect. If the domain coordinator process detects the problem during process startup, it terminates immediately. If it detects the condition during the START ACS command processing, the START operation fails and no ACS subsystem processes are started. Recovery.
ACS Subsystem Messages EMS Messages 1060 through 1069 1066: ZACL-EVT-BACKUP-CPU-DISABLED A primary domain coordinator process terminated unexpectedly in the indicated CPU and the ACS subsystem processes in that CPU have not been restarted. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT.
EMS Messages 1060 through 1069 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-FILE-NAME contains the name of the Guardian subvolume where the domain coordinator program resides. This token is the subject of the event message. ZACL-TKN-EVENT-SYSNN contains the name of the Guardian subvolume that contains the OSIMAGE file used to load the system. Effect. The domain coordinator process terminates immediately. Recovery.
EMS Messages 1070 through 1071 ACS Subsystem Messages Effect. If the backup domain coordinator process fails, the primary domain coordinator process continues to run without a backup process. If one of the other ACS subsystem processes fails, the CPU where it was running is disabled. Recovery. Restart the home terminal if possible. Otherwise, stop and restart the ACS subsystem with a new home terminal. 1069: ZACL-EVT-PROCESS-SWITCH The primary process can no longer continue.
EMS Messages 1070 through 1071 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-INFO. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the process pair. Effect. The process pair cannot switch; ACS subsystem processes may not be available to handle requests. Recovery. If the backup-process CPU is down, reload it. If the backup-process CPU is up, use the CONTROL command to restart the ACS subsystem processes.
ACS Subsystem Messages EMS Messages 1070 through 1071 ZACL-TKN-EVENT-ERROR-CODE contains the completion code associated with the process-termination operation. A completion code of -4 indicates that only the primary process, not both members of the process pair, terminated. ZACL-TKN-EVENT-ERROR-DETAIL contains the termination information code associated with the process termination. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message.
ACS Subsystem Messages EMS Messages 1070 through 1071 HP NonStop TS/MP System Management Manual—541819-007 18 -46
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. Note. PDMCOM commands in TS/MP 2.3 and later versions follow the same syntax as PATHCOM commands. For more information on PDMCOM Commands, see the TS/MP Release Supplement.
Syntax Summary CONTROL PATHMON , pathmon-attribute [ , pathmon-attribute ]... pathmon-attribute is: BACKUPCPU number DUMP { ON [ ( FILE file-name ) ] | OFF } DUMPMEMORY (FILE file-name ) DELETE [SERVER] { server-class } { ( server-class [ , server-class ]... ) } ERRORS [ number ] EXIT FC [ [-] number | string ] FREEZE { [ SERVER ] server-class } { [ SERVER ] (server-class [, server-class ]...
Syntax Summary INFO [ / OUT list-file / ] PATHWAY [ , OBEYFORM ] INFO [ / OUT list-file / ] { [ SERVER ] server-class } { [ SERVER ] ( server-class [ , server-class ] ...) } { SERVER * } [ , OBEYFORM ] 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.
Syntax Summary PATHCOM [ / run-option [ , run-option ]... / ] [ pathmon-name [ ; command [ ; command ]... ] ] run-option is: IN command-file OUT list-file CPU number NAME $process-name NOWAIT PRI number PATHMON / NAME $process-name [ , run-option ]... / run-option is: CPU number INSPECT ON NOWAIT OUT log1-file PRI number PRIMARY PATHMON [ , IFPRICPU number ] RESET CMDCWD RESET SERVER [ server-keyword [ , server-keyword ]...
Syntax Summary SET PATHMON , pathmon-attribute [ , pathmon-attribute ]... pathmon-attribute is: BACKUPCPU number DUMP { ON [ ( FILE file-name ) ] | OFF } SET PATHWAY pw-attribute [ , pw-attribute ]...
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 ]... ) ( cpu (cpu-wt) [ , cpu (cpu-wt) ]... ) CREATEDELAY number { HRS | MINS | SECS | CSECS } CWD oss-pathname DEBUG { ON | OFF } ( DEFINE define-name , define-attribute-spec [, define-attribute-spec ] ...
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 HP NonStop TS/MP System Management Manual—541819-007 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. Note. PDMCOM commands in TS/MP 2.3 and later versions follow the same syntax as PATHCOM commands. For more information on PDMCOM Commands, see the TS/MP Release Supplement.
NonStop TS/MP Environment PATHCOM Reserved Words FC MAXEXTERNALTCPS FILE MAXLINKS FREEZE MAXLINKMONS FREQTABLE MAXPARAMS MAXPATHCOMS GUARDIAN MAXPROGRAMS GUARDIAN-LIB MAXSERVERCLASSES GUARDIAN-SWAP MAXSERVERS MAXSPI HELP MAXSTARTUPS HIGHPIN MAXTCPS HOMETERM MAXTELLQUEUE HRS MAXTELLS MAXTERMS I-O MAXTMFRESTARTS IBM-3270 IFPRICPU NUMSTATIC IN NODEINDEPENDENT INFO INPUT OBEY INTELLIGENT OBEYFORM INTERVAL OBEYVOL OFF LIKE ON LINKDEPTH OPEN LINKMON OUT LOG1 OUTPUT LOG2
NonStop TS/MP Environment PATHCOM Reserved Words PATHMON SWITCH PATHWAY POWERONRECOVERY T16-6510 PRI T16-6520 PRIMARY T16-6530 PROCESS T16-6530WP PROCESSES T16-6540 PROCESSTYPE PROGRAM THAW PROTECTED TIMEOUT TMF REC RESET UNDO UNTIL SECS SECURITY VOLUME SEL SERVER WAIT SET WARM SHARED SHOW SHUTDOWN SHUTDOWN2 START STARTUP STATS STATUS STDERR STDIN STDOUT STOP HP NonStop TS/MP System Management Manual—541819-007 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. These limits are applicable for TS.MP 2.0. Note. These limits are subject to change with product SPRs or with new software releases. For information on TS/MP 2.3 and 2.4 limits, see the TS/MP Release Supplement. Table C-1. Global Pathway Environment Limits (page 1 of 2) Item Limits Per Pathway Environment ASSIGNs Maximum total of 4095 (for TS/MP 2.0 and 2.1) or 8191 (for TS/MP 2.
Configuration Limits and Defaults Table C-1. Global Pathway Environment Limits (page 2 of 2) Item Limits Per Pathway Environment Links Only one SCREEN COBOL program at a time can use a link (by performing a SEND). Only one Pathsend process at a time can use a link. For a description of how to calculate the number of links a link manager may need for a given server class and the number of links a given server class is able to provide, see Configuring Links for Optimum Performance.
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* SPI Token/Field** Value Limits and Defaults CREATEDELAY ZCREATEDELAY Values: HRS | MINS | SECS | CSECS 0 through 16,383 CSECS, or 0 through 16,383 SECS, or 0 through 1092 MINS, or 0 through 18 HRS The time set for this parameter may be added to the response time for all transactions; therefore, the value should be small.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 3 of 10) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults EXT ZEXTENTSIZE Values: 1 through 65,535 Default: No value is passed. FILE ZFILE Values: One through seven alphanumeric characters, including the $; first character after the $ must be alphabetic. Default: N.A. GUARDIAN-SWAP Values: Maximum of 10 disk volumes for SERVER objects.
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 MAXASSIGNS ZMAXASSIGNS Values: 0 through 4095 (for TS/MP 2.0 and 2.1) Default: N.A. Values: 0 through 8191 (for TS/MP 2.3 and later versions) Default: N.A. MAXDEFINES ZMAXDEFINES Values: 0 through 4095 (for TS/MP 2.0 and 2.1) Default: N.A. Values: 0 through 8191 (for TS/MP 2.3 and later versions) Default: N.A.
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 MAXLINKS ZMAXLINKS Values: 0 through 4095 To help determine the appropriate value for this attribute, see the discussion on Links earlier in this appendix. In a COBOL server, the size of MAXLINKS size must be equal to or less than the value of RECEIVETABLE.
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 MAXSERVERCLASSES ZMAXSERVERCLASSES Values: 0 through 4095 Total of MAXSERVERS values for all server classes must not exceed value of MAXSERVERPROCESSES. Default: N.A. MAXSERVERPROCESSES ZMAXSERVERPROCESSES Values: 0 through 4095 MAXSERVERS ZMAXSERVERS Values: 0 through 4095 Default: N.A.
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 MAXTCPS ZMAXTCPS Values: Total of values for MAXTCPS, MAXEXTERNALTCPS, and MAXLINKMONS must not exceed 800. Maximum number of concurrent openers of the PATHMON process (TCP, external TCP, LINKMON, PATHCOM, and SPI) must not exceed 800. Recommended value if Pathway/iTS is not installed at your site: 0.
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 N.A. ZBLOCKSIZE Values: 1 through 4096 Default: No value is passed. NODEINDEPEN DENT ZNODEINDEPEN DENT Values: ON | OFF N.A. ZNODEINDEPEN DENTFORMAT Values: YES | NO ZNUMSTATIC Values: 0 through 4095; must not exceed value of MAXSERVERS.
Configuration Limits and Defaults Table C-2. Limits and Defaults for Parameters (page 9 of 10) PATHCOM Parameter* PROCESS SPI Token/Field** Value Limits and Defaults ZLINKMON ZPROCESS Values: One to six alphanumeric characters, including the $; first character after the $ must be alphabetic. Default: N.A.
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 STATUS N.A. Values: QUIET | AGGREGATE Default: QUIET STDERR ZPWY-TKN-DEFSCSTDERR Values: Name of the OSS stderr (standard error) file. Must not exceed 1024 bytes. Default: None STDIN ZPWY-TKN-DEFSCSTDIN Values: Name of the OSS stdin (standard input) file. Must not exceed 1024 bytes.
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 processes. Additionally, you have more freedom to define servers as static, thus reducing the overhead associated with process startup. 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.
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 HP NonStop TS/MP System Management Manual—541819-007 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 HP NonStop TS/MP System Management Manual—541819-007 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.
associative server Glossary name with a logical file of a program and, optionally, attributes characteristics to that file. associative server. A process within a server class that can be started outside the Pathway environment by a process other than the PATHMON process that controls the server class. ATMI. See Application-Transaction Monitor Interface (ATMI). attributes. Those characteristics of an object that influence the operation of that object and establish its capabilities. audited file.
CISC Glossary CISC. See complex instruction-set computing (CISC). client. An application program that requests services to be performed. In discussions of the Pathway environment, this term is used to refer to the part of an application that runs on some other vendor’s hardware, such as a personal computer, Macintosh computer, UNIX workstation, or mainframe computer system, and makes requests of a server process. See also requester, server, and client/server model. client/server model.
command terminal Glossary command terminal. A terminal at which a system manager or operator enters commands for configuration and management, such as the PATHCOM commands that configure and manage a PATHMON environment. See also application terminal. complex instruction-set computing (CISC). A processor architecture based on a large instruction set, characterized by numerous addressing modes, multicycle machine instructions, and many special-purpose instructions.
current working directory Glossary current working directory. The OSS directory from which relative pathnames are resolved. See also OSS pathname and relative pathname. Customer Information Control System (CICS). An IBM transaction management system that provides concurrent online access to data files by means of user-written application programs. CICS also includes facilities for building, using, and maintaining databases. database consistency.
DEFINE Glossary DEFINE. A named set of attributes and associated values. In a DEFINE (as with an ASSIGN command), users can specify information to be communicated to processes they start. definition files. A set of files containing data declarations for items related to SPI messages and their processing. The core definitions required to use SPI are provided in a DDL file and in several language-specific definition files, one for each programming language that supports SPI.
double-byte character Glossary database management systems (NonStop SQL/MP and Enscribe). DTP allows the coordination of multiple, autonomous actions as a single logical unit of work. double-byte character. A character represented in two bytes. See also double-byte character set. double-byte character set (DBCS). A character set, such as Tandem Kanji, that uses two bytes of data to represent a single character. DSM. See Distributed Systems Management (DSM). dumb terminal. See fixed-function terminal.
Expand networking software Glossary Expand networking software. Tandem software that can connect up to 255 Tandem NonStop systems into a single network. Extended General Device Support (GDSX). A Tandem product that facilitates communication between general I/O devices and a PATHMON environment by acting as a front-end or a back-end process. extensible structured token. In the Subsystem Programmatic Interface (SPI), a token with a value that can be extended by appending new fields in later releases.
File Utility Program (FUP) Glossary file attributes. A file system provides the namespace for the file serial numbers that uniquely identify its files. File Utility Program (FUP). A Tandem product that allows users to create, copy, purge, and otherwise manipulate disk files interactively. fixed-function terminal. A nonintelligent device (that is, a device without processing ability) capable of sending and receiving information over communications lines.
Inspect Glossary Inspect. The Tandem debugging tool that can be used interactively to examine and modify the execution of Guardian processes and SCREEN COBOL requester programs. Inspect command terminal. The terminal on which programmers enter commands to Inspect when debugging a SCREEN COBOL program or a Pathway server. intelligent device.
link Glossary link. (1) An open of a server process within a server class. When a link manager—that is, a TCP or a LINKMON process—sends a request to a PATHMON process for a link to a server in a specified server class, the PATHMON process selects a server process in that server class (possibly starting a new server process if necessary) and then returns the name of the server process to the requesting link manager. See also link granting and link manager.
Glossary message-oriented requester same kinds of services that system managers can request through the PATHCOM interface. A management application can also interact with subsystems other than the Pathway subsystem. Management applications use the Subsystem Programmatic Interface (SPI) to send commands to subsystems and the Event Management Service (EMS) to receive notification of significant events. message-oriented requester.
nondedicated device Glossary nondedicated device. A term formerly used for a terminal or other input/output device on which a Pathway application could be started from PATHCOM with a RUN PROGRAM command. The RUN PROGRAM command results in the creation of a temporary TERM object to control the terminal. (No new term replaces this term; instead, the manual text now refers to such devices as those associated with temporary TERM objects.) See also dedicated device and temporary TERM object.
NonStop TUXEDO native client Glossary NonStop TUXEDO native client. See native System/T client. NonStop TUXEDO server. A server process or program managed by the NonStop TUXEDO system administrative facilities. See also Pathway server. NonStop TUXEDO system. Tandem’s implementation of the Novell, Inc., TUXEDO enterprise transaction processing system.
OLTP Glossary names for some of these object types and defines additional object types; for example, PM, LM, PROGTERM, and TCPTERM are object types in the SPI interface. OLTP. See online transaction processing (OLTP). OLTP application. See online transaction processing (OLTP) application. online transaction processing (OLTP). A method of processing transactions in which entered transactions are immediately applied to the database.
overlay screen Glossary overlay screen. In SCREEN COBOL, a screen that is displayed in an overlay area of a base screen. A base screen can be used with various overlay screens. See also screen and base screen. Parallel Transaction Processing (PTP) Services for the CICS API product.
PATHMON process Glossary PATHMON process. The central controlling process in the Pathway environment. The PATHMON process maintains configuration-related data; grants links to server classes in response to requests from TCPs and LINKMON processes; and performs all process control (starting, monitoring, restarting, and stopping) of server processes and TCPs. pathname. See OSS pathname. Pathsend procedures.
Pathway environment Glossary Pathway environment. See Pathway transaction processing environment. Pathway management programming interface. A set of programmatic commands that allow users to write management application programs that communicate directly with the PATHMON process for configuration and management. This interface is based on the Subsystem Programmatic Interface (SPI) within the Distributed Systems Management (DSM) software.
Pathway translation server for the NonStop TUXEDO system Glossary Pathway translation server for the NonStop TUXEDO system. A server process, provided by Tandem as part of the NonStop TUXEDO product, that allows a Pathway (SCREEN COBOL or Pathsend) requester to use the services of a NonStop TUXEDO server. The translation server thus acts as a gateway process between the Pathway environment and the NonStop TUXEDO environment.
process pair Glossary process pair. A fault-tolerant arrangement of processes in the Guardian environment, whereby two processes in separate processors share the same name and execute identical code. One process functions as the primary process and the other functions as the backup process. The two processes are kept in sync through checkpoint messages sent from the primary to the backup process.
Glossary reduced instruction-set computing (RISC) reduced instruction-set computing (RISC). A processor architecture based on a relatively small and simple instruction set, a large number of general-purpose registers, and an optimized instruction pipeline that supports high-performance instruction execution. See also complex instruction-set computing (CISC). relative pathname. An OSS pathname that does not begin with a slash (/) character.
request message Glossary interprocess communication in the Guardian environment. See also requester and server. request message. The part of an interprocess communication message that is formatted by a requester and sent to a specific server. The message contains any data and instructions needed by the server to perform its processing. See also reply message. request/response server. See context-free server. request translation header.
SCOBOLX Glossary SCOBOLX. The object file for the SCREEN COBOL compiler program. This name is given in a TACL command to invoke the compiler. See also SCREEN COBOL. screen. A group of data fields that represent formatted data to be displayed on a terminal. A screen is defined by a screen description entry in the Screen Section of a SCREEN COBOL program. There are two types of screen: base screens and overlay screens. See also base screen, overlay screen, and screen description entry. SCREEN COBOL.
server class Glossary messages to the clients or requesters. A server process is a running instance of a server program. (2) A combination of hardware and software designed to provide services in response to requests received from clients across a network. For example, Tandem’s Himalaya servers provide transaction processing, database access, and other services.
Structured Query Language (SQL) Glossary Structured Query Language (SQL). A relational database language used to define, manipulate, and control databases. subsystem. In the context of the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS), a process or collection of processes that gives users access to a set of related resources or services. A subsystem typically controls a cohesive set of objects.
TAL Glossary TAL. See Transaction Application Language (TAL). Tandem Advanced Command Language (TACL). The user interface to the Tandem NonStop Kernel in the Guardian environment. The TACL product is both a command interpreter and a command language. Tandem Alliance. Tandem’s marketing and technical support program for third-party vendors, which encourages the development of application software for the Pathway environment.
terminal Glossary processing is completed or when a STOP TERM or ABORT TERM command is issued. Names of temporary TERM objects begin with a number. See also configured TERM object and TERM object. terminal. An I/O device capable of sending and receiving information over communications lines. terminal context. Data maintained by a TCP for each active terminal under its control. terminal control process (TCP).
token Glossary token. (1) An attribute control element in the CONTROLLED clause of a SCREEN COBOL program, which allows run-time control of display attributes. This token consists of an attribute identifier and an attribute value. (2) In the Subsystem Programmatic Interface (SPI), a distinguishable unit in a message. An SPI token consists of an identifier (token code or token map) and a token value.
TRANSFER delivery system Glossary TRANSFER delivery system. An information delivery system that enables organizations to move and manage information efficiently within a single Tandem system or across a network of systems. The TRANSFER delivery system supports communications between users, I/O devices, and processes in the Guardian environment. TSCODE. The object code for the part of a GDSX process that is supplied by Tandem.
$RECEIVE Glossary HP NonStop TS/MP System Management Manual—541819-007 Glossary -30
Index A ABORT option, SHUTDOWN2 command 11-25 Absolute OSS pathnames 8-9 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-25 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-10 Angle brackets 10-9 Applications configuring in a PATHMON environment
C Index BACKUPCPU attribute CONTROL PATHMON command 11-3 primary CPU, relation to 12-37 SET PATHMON command 11-12 SET SERVER command 12-18 Banner, PATHCOM 2-6 BEGIN-TRANSACTION statement 12-48 Binder program 12-22 Brackets, angle 10-9 BREAK attribute, for TERM objects 3-12 Break function key PATHCOM commands 8-7 SHUTDOWN2 command 11-26 C Cancelling PATHCOM commands 8-7 Characters inserting and deleting 10-7 Client-server computing 1-14 CLOSE message 12-46 CMDCWD command 3-8, 10-2 CMDCWD parameter 10-15 C
D Index Configuration file (continued) recording changes to PATHMON 11-3/11-6 saving contents of 5-21 startup types 11-28/11-29 status of 11-31/11-33 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-27/3-34 PATHMON-controlled objec
E Index DELETEDELAY attribute for Server classes 3-18, 3-26 relation to dynamic server processes 3-17, 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-14 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
F Index External objects and processes LINKMON process 1-11 PATHCOM 1-11 Pathsend 1-15 TCPs 1-14 External TCPs shutting down 11-23 F Failed to get… (LINKMON message) 17-1 FastStart product 1-23 FC command 10-6/10-7 FECONTINUE (startup message 70) 4-3, 12-37 FESCSERVERLINKCONNECT (error 904) 12-30 File names Guardian 8-7 OSS pathnames 8-9/8-10 setting Guardian defaults 10-3 setting OSS defaults 10-2 File open error 9-5, 10-14 File-creation attributes 12-16 File-identifier names 8-7 FREEZE attribute 12-40
K Index INFO command (continued) SERVER 5-5 INFO display field 11-30, 12-41 INFO SERVER command 12-7/12-9 INITIAL attribute, for TERM objects 3-13 Initialized and running (LINKMON message) 17-2 Initializiation files D-2 Inserting characters 10-7 INSPECT parameter PATHMON startup command 9-2 Intelligent devices 1-14 Interactive mode (PATHCOM) 2-6, 8-6 Interfaces PATHCOM interactive 1-19/1-20 SPI programmatic 1-21 INTERVAL parameter STATS SERVER command 12-39 STATUS PATHWAY command 11-34 I/O operations, req
M Index LINKMON processes (continued) monitoring of 6-10/6-14 name format 12-43 names for 6-3 naming 11-29 relation to Pathsend processes 6-1 server access 12-25 sharing links 3-24 shutting down 11-23 starting 6-3, 6-7 statistics collected by 6-14 STATUS command 11-29/11-30 status of 11-31 tasks performed by 6-1 thawing server requests 12-47/12-48 TMF, relation to 12-6 Links associative servers 12-27 attributes affecting DELETEDELAY 3-26 LINKDEPTH 3-25 MAXLINKS 3-25 MAXSERVERS 3-25 NUMSTATIC 3-26 configur
N Index MAXPATHCOMS attribute 3-5, 11-17 MAXSERVERCLASSES attribute for PATHMON environments 2-9, 3-5 SET PATHWAY command 11-15 MAXSERVERPROCESSES attribute for PATHMON environments 2-9, 3-5 SET PATHWAY command 11-15 MAXSERVERS attribute 3-18, 3-25, 12-24 MAXSPI attribute 11-17 MAXSTARTUPS attribute 2-9, 3-5, 11-15 MAXTCPS attribute, for PATHMON environments 2-9 MAXTERMS attribute for PATHMON environments 2-9 Measure product 1-23 Memory swap 12-28 Memory dumps for PATHMON process 2-11, 5-20 for TCP 5-20 M
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-12 OBEYFORM parameter INFO PATHMON command 11-6 INFO PATHWAY command 11-7 INFO SERVER command 12-7 OBEYVOL command 10-13 OBEYVOL parameter, SHOW command 10-16 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-10 SERV
P Index OWNER attribute for PATHMON environment 5-20 for PATHMON environments 3-7 for Pathsend access to servers 6-9 SET PATHWAY command 11-21 SET SERVER command 12-25 P PAID display field 11-32 PARAM attribute, for Guardian Server classes 3-19 PARAM parameter 12-26 Parameters configuration limits for C-1/C-3 displaying settings 10-15/10-16 PATHCOM advantages of 1-20 as interactive interface tool 1-19/1-20 banner message for 2-6 collecting data about for problem diagnosis 5-31 command and object summary
P Index PATHCOM (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-30 PATHCTL display field 11-31 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-5 configuration limits C-1/C-3 configuring across CPUs 1-7 configuring and managing objects in 1-16/1-23 considerations fo
Q Index PATHMON process and object (continued) STATUS command 11-31/11-33 STOP command 11-36/11-37 SWITCH command 11-37/11-38 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-15 as requesters 1-15 communication w ith server classes 6-1 defined 1-15 relation to LINKMON processes 6-1 security requirements for network 6-9 SERVER objec
R Index Queues for server class waits 7-2 QUIET option, SHUTDOWN2 command 11-25 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-14 Repeating the command line 10-6/10-7 REQNUM display field 11-32 Request not valid… (message 1045) 11-37, 12-45 REQUEST PENDING, and STOP SERVER comman
S Index Server classes attributes for 3-17/3-22 ARGLIST 3-20 ASSIGN 3-19 CPUS 3-18 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-21 STDIN 3-21 STDOUT 3-21 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-19 displaying link status for 5-10 OSS configuring attributes for 3-20 Se
S Index Server processes assigning names 12-26 associative 12-27 CREATEDELAY attribute 3-17 defined 3-16 DELETEDELAY attribute 3-17 displaying information about configuration 5-5 freezing 4-4 home terminal, specifying 12-22 input file, naming 12-22 links to 4-3 multithreaded 12-23 object programs for 3-17 relationship to server class 3-16 restart attempts, specifying 12-17 setting maximum 11-15 starting dynamic 4-1 static 4-1 static 12-17 static, specifying maximum 12-24 stopping 4-4 Server programs, defi
T Index STARTUP messages, for server classes 11-15 Startup, cool CONTROL PATHMON command, effect of 11-4 STATE display field 11-30, 12-42 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-14 TCPs 5-13 displaying information about 5-13/5-15 for SERVER objects 5-13, 6-14 STATS command SERVER 5-13 STATS SERVER command 12-37/12-39 STATUS attribute 11-10, 11-25
U Index TCPs (continued) as external objects 1-14 attributes for DUMP 5-20 defined 1-3 deleting 5-19 external, shutting down 11-23 freezing server requests 12-5 frozen server class, sending to 12-6 links, requesting new 12-18 switching primary and backup CPUs for 5-20 thawing server requests 12-47 user library object file 5-30 TCP/SERVER communication 4-4 Templates for PATHMON-controlled objects 3-12 TERM objects altering 5-19 defined 1-3 deleting 5-19 stopping 11-23 Terminals SEND to frozen servers 12-6
Special Characters Index Working set values, for PATHMONcontrolled objects 3-11/3-14 Special Characters ! parameter FREEZE SERVER command 12-6 SHUTDOWN command 11-23 START PATHWAY command 11-28 ! (Exclamation point) See Exclamation point $SYSTEM.SYSTEM.
