HP NonStop TS/MP 2.5 System Management Manual HP Part Number: 679664-002 Published: February 2012 Edition: Edition: J06.03 and all subsequent J-series RVUs and H06.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notice 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.
Contents About This Manual........................................................................................8 Product Version........................................................................................................................8 Supported Release Version Updates (RVUs)..................................................................................8 Intended Audience....................................................................................................................
3 Configuring Objects in a PATHMON Environment.........................................51 Configuration Overview...........................................................................................................51 Configuring a PATHMON Environment......................................................................................53 Specifying Limits................................................................................................................53 Specifying Node Independence........
Keep Development and Production Separate............................................................................105 Maintaining Associative Server Processes................................................................................105 Migrating Your Environment to a Different System......................................................................106 6 Managing the Pathsend Environment.........................................................109 The Pathsend Environment.........................
LOG1 and LOG2 Commands................................................................................................156 PRIMARY PATHMON Command.............................................................................................157 SET PATHMON Command.....................................................................................................158 SET PATHWAY Command......................................................................................................159 Example..............
ACS Subsystem Identifiers......................................................................................................275 Event-Message SPI Format......................................................................................................275 Listed Tokens...................................................................................................................276 Unlisted Tokens........................................................................................................
About This Manual This manual provides guidelines and examples for configuring and managing the J06.11 and subsequent RVUs, and H06.22 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.
Related Manuals 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. The Pathway/iTS objects are those that operate under the run-time portions of Pathway/iTS (the terminal control process (TCP) and SCREEN COBOL runtime environment).
Manual Description Pathway/iTS, and related products such as TMF and the NonStop TUXEDO transaction processing system. Guardian User’s Guide Provides basic information about the programs and utilities that are used most often by general system or application users. The guide addresses beginning users of NonStop systems. Other Manuals in the Manual Set Manuals Description TS/MP 2.
• Added a new attribute UMASK in the server-keyword attribute for the “ALTER SERVER Command” (page 178). • Added a new attribute UMASK in the “Display Format” (page 182) for the INFO SERVER command. • Added a new attribute UMASK to “RESET SERVER Command” (page 183). • Added a new attribute UMASK to “SET SERVER Command” (page 185). • Added a new attribute UMASK in the Example 30 (page 200) for the SHOW SERVER command.
Section Description Section 11, “PATHMON Environment Control Commands” Describes the PATHCOM commands that control the (page 150) PATHMON process and the PATHMON environment as a whole. Section 12, “SERVER Commands” (page 177) Gives the PATHCOM commands for configuring and controlling server objects.
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.
M address [ , new-value ]… [ - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
!o:i In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum !I , [ filename:maxlen ] ) ; !o:i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal.
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK | Failed } % Percent Sign A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
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 must perform to manage a PATHMON environment, as well as applicable tools and commands.
• Application Cluster Services (ACS) Subsystem Processes— These processes use Pathsend requestors to provide link management functions for applications. (Pathsend requestors are user applications that use Pathsend procedure calls to send requests to server classes.) In TS/MP, ACS subsystem core processes replace the TS/MP 2.0 LINKMON process. (Although TS/MP has a ROUT process with $ZLnn names, similar to what TS/MP 2.0 uses, the TS/MP ROUT is a redirector process that is part of the ACS subsystem.
Figure 1 A NonStop TS/MP Application With Pathway/iTS Pathway Environment Configurations 19
Figure 2 NonStop TS/MP Application With Guardian and OSS Servers 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.
Figure 3 PATHMON-Controlled Objects Distributed Over Two CPUs Pathway Environment Configurations 21
Figure 4 NonStop TS/MP Application Distributed Over Two Nodes 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.5 has updated PATHMON, PATHCOM and PDMCOM processes. For more information, see the TS/MP 2.5 Release Supplement. PATHMON Object The PATHMON object represents the PATHMON process.
The PATHMON process enforces global limits you set for the environment and monitors the operation of the objects under its control by performing these: • Keeping a record of the object definitions in the PATHMON configuration file. • Starting SERVER processes (available only if you are running the NonStop TS/MP product). • Starting TCPs, TERM objects, and PROGRAM objects (available only if you are running the Pathway/iTS product).
ACS Subsystem Processes An ACS subsystem process is a multitasking process that handles the interface to server processes from requestors other than SCREEN COBOL and TUXEDO requestors. Such requestors include Pathsend requestors; workstation clients that use RSC and, optionally, POET. Each processor in a system has one ACS subsystem process, which starts when the processor starts. The ACS subsystem process is shared by all Pathsend requestors running in a given processor.
Figure 5 Transaction Sources Personal Computers and Workstations Personal computers (PCs) and workstations can access the PATHMON environment using the RSC product. RSC allows client-server computing by supporting a variety of hardware and software configurations and communications protocols for PCs and workstations.
Intelligent Devices Intelligent devices—such as automated teller machines (ATMs), workstations, and barcode readers—can access server classes through SCREEN COBOL requestor programs and the TCP, a process supported under the Pathway/iTS product. This access route is possible when the intelligent device support (IDS) facility, which is part of the TCP, is used.
Figure 6 Requestor Access to Server Classes System Management Tasks The specific tasks to set up and manage PATHMON-controlled objects in a PATHMON environment depend on your applications, but generally include tasks shown in Figure 7 (page 28). You can perform the required tasks using PATHCOM or by writing a management application. For details, see “System Management Tools” (page 29). NOTE: System Management tasks can be performed using PDMCOM or PATHCOM. When using TS/MP 2.
Figure 7 System Management Tasks 1. Start the Pathway environment. This task consists of starting the PATHMON and PATHCOM processes. The PATHCOM process provides the interactive command interface to the PATHMON process. 2. 3. 28 Configure and start the PATHMON environment. • Configure the PATHMON process. You can specify a backup processor and request error dumping. • Specify global limits and settings with the SET PATHWAY command.
4. 5. 6. • Define configuration parameters for SCREEN COBOL program templates with the SET PROGRAM command and then add the program templates with the ADD PROGRAM command. • Define configuration parameters for server classes with the SET SERVER command and then add the server classes with the ADD SERVER command. Start the PATHMON-controlled objects. • Start all the TCP, TERM, and SERVER objects using the appropriate START command.
Figure 8 System Management Interfaces PATHCOM is an interactive, text-based interface; for example, an operator using PATHCOM can easily start and stop objects or obtain status information about objects. A management programming interface is command-driven and more toward logical processes. A management programming interface can simplify the automation of tasks associated with starting, maintaining, and stopping an environment or maintaining a state.
the command by gathering and returning statistical information about their links to the specified server class. PATHCOM allows you to enter commands interactively through a terminal or from a command file or TACL script. For more information about using command files and TACL scripts, see “Starting and Stopping a PATHMON Environment” (page 34).
an event log. An EMS distributor process reads the log and distributes the events to all appropriate management applications. • Subsystem environment The subsystem environment includes the PATHMON process and objects. The Transaction Management Facility (TMF), which provides transaction processing protection, also resides in this environment. For more information about the Distributed Systems Management set of products, see the Introduction to Distributed Systems Management.
an integrated NonStop system, including many products, from one location. For more details about the ViewPoint application, see the ViewPoint Manual. • The EMS FastStart product enhances development of applications under DSM. EMS FastStart provides a simple, cost-effective way for programmers to develop and test event messages. For more information, see the EMS FastStart Manual.
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.
ERROR *1017* PATHCTL FILE (file-error-num) The PATHMON process saves the configuration values you specify in memory, as shown in Figure 10 (page 35). At startup, these values are written to the PATHMON configuration file. (For more information, see “Configuring the PATHMON Process” (page 41).) Figure 10 Configuring the PATHMON Process Starting a PATHMON Environment Starting a PATHMON environment consists of these steps, which are summarized in this list and explained in detail throughout this section: 1.
You can enter this command from your terminal, as shown in the example. Alternatively, you can create a command file that contains this command (as well as others) and then request execution of the commands in that file. In either case, the operating system responds to your command by creating and starting the primary PATHMON process, as shown in Figure 11 (page 36). Figure 11 Starting the PATHMON Process Always provide a name for your PATHMON process.
If you do not specify these RUN options, the operating system assigns default values for them. For instance, the operating system assigns your terminal as the default log file device. For more information about these and other RUN options, see the TACL Reference Manual. Starting and Using PATHCOM After a PATHMON process is started, you can start a PATHCOM process to communicate with the PATHMON process by issuing an implicit RUN command to TACL.
and send messages to user terminal operators about changing conditions. It is generally easier and faster, however, to set up lengthy configurations non-interactively. PATHCOM RUN Options The command to run PATHCOM, like the command to run the PATHMON process, allows you to select several RUN options. For instance, you can select the processor in which PATHCOM runs or specifies a device other than your terminal as the destination of output from PATHCOM.
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.#LP, CPU 1, NOWAIT/ $PMX When PATHCOM runs, it reads the commands and runs them in sequence. When it encounters an end of file or an EXIT command, PATHCOM terminates. OBEY Command You specify the OBEY command from within PATHCOM.
paragraphs. For more information, see “Configuring Objects in a PATHMON Environment” (page 51). Specifying Limits Limits are global values that determine the maximum number of objects of each type that you can define when you are ready to configure individual objects.
To take full advantage of the node-independent feature, you must invoke it by using the SET PATHWAY NODEINDEPENDENT command prior to using the SET PATHMON commands that specify a backup processor and dump file. For more details on how the NODEINDEPENDENT attribute works, see “Configuring Objects in a PATHMON Environment” (page 51). Note that setting the Pathway NODEINDEPENDENT attribute to ON overrides and disables the node field of the CMDVOL command. For more details, see “CMDVOL Command” (page 138).
There are two START command options: COLD and COOL. Which one you choose depends on the task you want to perform: • Starting a new PATHMON environment (cold start) When you start a PATHMON environment for the first time, you must specify the COLD start option. The COLD start option tells the PATHMON process to create the configuration file, PATHCTL, that will store configuration information.
In response to this command, the PATHMON process: • Starts the PATHMON backup process if one is specified. • Uses the existing configuration file as a basis for creating the operating environment. The existing configuration file represents the PATHMON configuration at the time the system stopped (due to shutdown or failure). • Prompts you, if the PATHMON process name is different from the name stored in the PATHCTL file, that the PATHMON name is changed in the PATHCTL file.
NOTE: For shutting down the PATHMON environment in TS/MP 2.5, PDMCOM or PATHCOM can be used. However, 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 2.5 Release Supplement.
The ABORT option allows send statements to a server class to complete, but the TERM might be aborted before the server class can reply. Work does not necessarily stop on transaction boundaries, so the status of the transaction is unknown. If completing outstanding transactions is important to your application, use the ORDERLY option. The ORDERLY option opens and closes unlinked server processes, permitting the performance of any epilog processing.
Monitoring Shutdown Status You can monitor the status of the shutdown in one of two ways: • Include the STATUS AGGREGATE option in your SHUTDOWN2 command, as shown in this example: = SHUTDOWN2, MODE ORDERLY, STATUS AGGREGATE, UNTIL TIMEOUT 5 MINS The STATUS AGGREGATE option tells PATHCOM to display shutdown status every 20 seconds until shutdown completes or until the TIMEOUT option (if specified) expires. • Specify the STATUS PATHWAY command from any PATHCOM process.
Example 1 SHUTDOWN2 Status Display PATHWAY -- STATE = SHUTTING DOWN (IN PROGRESS) - STARTED 2:11:39 RUNNING LINKMONS 0 PATHCOMS 1 SPI 0 RUNNING STOPPED THAWED FREEZE FROZEN PENDING 1 1 0 0 STOPPED PENDING SERVERPROCESSES 8 1 0 TCPS* 2 4 0 RUNNING STOPPED PENDING SUSPENDED 8 8 0 0 SERVERCLASSES 2 RUNNING * TERMS PATHWAY - STATE = SHUTTING DOWN (IN PROGRESS) - STARTED 2:11:39 RUNNING LINKMONS 0 PATHCOMS 1 SPI 0 RUNNING STOPPED THAWED FREEZE FROZEN PENDING 3 1 0 0
Stopping the PATHMON Process If shutdown cannot complete, you can stop the PATHMON primary and backup processes by issuing this PATHCOM command: = STOP PATHMON This command stops the PATHMON primary and backup processes and writes a termination message to the log file. NOTE: The STOP PATHMON command is valid only if you have already issued a SHUTDOWN2 command.
Example 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. As such it == is subject to Guardian security limitations about who can stop == which processes.
After the PATHCOM prompt returns, you can either initiate communication with another PATHMON process or terminate your interaction with PATHCOM. For example, to open communication with the PATHMON process named $PMY, enter: = OPEN $PMY To end your interaction with PATHCOM, enter: = EXIT After PATHCOM runs this command, the PATHCOM process ceases to exist and control returns to TACL.
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.
Figure 17 PATHMON Environment With Multiple Applications In some configurations, a single application spans multiple PATHMON environments that might be distributed over a network. In cases where more than one PATHMON environment is involved, each environment is monitored by the PATHMON process. For more information, see “Distributing a Pathway or PATHMON Environment” (page 20).
If your application generates a large number of Pathsend requests (like the application shown in Figure 17 (page 52)), you must consider distributing the request load by configuring your TDP processes across a number of CPUs. Such an arrangement avoids overwhelming any single ACS subsystem processes; each ACS subsystem process can handle only a certain number of Pathsend requests. (For descriptions of configuration limits, see “Configuration Limits and Defaults” (page 318).
For a complete description of all the SET PATHWAY attributes, see “SET PATHWAY Command” (page 159). Specifying limits always involves some guessing, with penalties if you estimate wrong. Begin with a thorough understanding of your business application environment. Then choose your global parameters very carefully. Once you start your PATHMON environment, you cannot alter these limits without shutting the environment down for complete reconfiguration.
unspecified, the node name always defaults to the node where the PATHMON process is running at any given time. Migration Considerations Designating your PATHMON application as node-independent simplifies, but does not eliminate, the tasks associated with migrating an application from one system to another. Migrating device names configured under Pathway/iTS, for example, is not useful unless physical devices with those names are connected to the new node.
NOTE: For configuring PATHMON-controlled objects in TS/MP 2.5 PATHMON environment, PDMCOM or PATHCOM can be used. However, it is recommended to use PDMCOM (instead of PATHCOM) because it can communicate with multiple PATHMONs simultaneously. For more information, see the TS/MP 2.5 Release Supplement. Using the SET and ADD Commands Whether you create objects for a new environment or add objects to a restarted environment, the technique is the same, as follows: 1.
= SET SERVER CPUS (3:2, 0:6) = SET SERVER PROGRAM \PARIS.$MARKT.UPDATE = SET SERVER SECURITY “N” 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 18 (page 57).
The working set of attribute values is initialized when you start PATHCOM. In this initial stage, each attribute entry in the working set specifies either of these: • The attribute and the default value, assigned by PATHCOM. If you do not specify another value for this attribute with the SET or ADD command, this default value is assigned when you add any object of this type. • The attribute alone, with no value specified. You must assign a value for this attribute with the SET or ADD command.
Each time you enter the ADD command to add an object, the PATHMON process assigns the working-set values last established for that object type (unless you override these values with new ones in the ADD command). This feature allows you to use the PATHCOM working set as a template for defining and adding multiple objects of the same type with identical or similar attribute values. For example, these commands add four SERVER objects to your PATHMON environment.
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.
Using Existing Object Attributes for New Objects You can use object definitions recorded in the PATHMON configuration file as the basis for defining values in the PATHCOM working set. For example, suppose that you want to add a new SERVER object named JACK, using the same attributes that applied to the SERVER named ANNA (except for the TMF attribute).
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. The time period is determined by the CREATEDELAY attribute for the server class.
• CREATEDELAY specifies the maximum amount of time, ACS subsystem processes or TCP process must wait to use an established link to a server class before the PATHMON process starts another server process. • DELETEDELAY specifies the maximum amount of time a link between ACS subsystem processes, or TCP process and a dynamic server process can remain idle before the ACS subsystem processes or TCP process automatically returns the link to the dynamic server.
= = = = SET SET SET ADD SERVER SERVER SERVER SERVER NUMSTATIC 3 PARAM SWITCH-1 “ON” PROGRAM \SYS.$DATA.SRVRS.ORDSRV ORDER-SRV The SET commands in the preceding example establish these characteristics for the SERVER: • This is a Guardian server. (PROCESSTYPE attribute.) • 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.
= = = = = = = = = = = SET SET SET SET SET SET SET SET SET SET ADD SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER DEFINE =PARTS, CLASS MAP, FILE $DATA.REG2.PRTFIL DEFINE =ORDERS,CLASS MAP, FILE $DATA.REG2.ORDFIL ENV DEBUGLOGFORMAT=TRUE ENV HANGAROUND=TRUE MAXSERVERS 4 NUMSTATIC 3 PROGRAM app/bin/ordsrv1 STDERR process/error STDIN process/orders/new STDOUT process/orders/out ORDER-SRV1 • This is an OSS process. (PROCESSTYPE attribute).
Configuring OSS Servers for Effective Space Allocation When you start the PATHMON environment, the PATHMON process allocates enough memory and disk space to support most configurations. If your environment uses all allocated memory and disk space, the PATHMON process attempts to get more.
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. As a best practice, when utilizing these formulas is that you will pay a small penalty—in unused resources—if you overconfigure your system.
MAXSERVERS The MAXSERVERS attribute specifies the maximum number of server processes in a server class that can run at the same time. To determine maximum number of links available in a server class, use the formula MAXSERVERS x MAXLINKS. MAXLINKS The MAXLINKS attribute specifies the maximum number of links to an individual server process from all link managers, such as a ACS subsystem process.
CREATEDELAY and DELETEDELAY CREATEDELAY is the length of time a send request queues before the link manager asks for another link, assuming the link manager has determined that no more static links are available (that is, only dynamic links are available). A link manager will always ask for a link immediately if the link manager has determined that static links are still available.
process is managing five requestor processes, and each process sends a request to this server class, four processes must wait for the one link 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 21 (page 70).
Step 1 Identify Number of Pathsend Requestors and Terminals Identify how many Pathsend requestors and, if your environment includes Pathway/iTS, how many terminals your application environment must support. Multiply these by a safety factor—for example, 1.5—to allow for future application growth. The formula for Pathsend requestors is: Pathsend requestors x constant = total Pathsend requestors The formula for terminals is: terminals x constant = total terminals For example: 2000 existing terminals x 1.
In this example, “45 tps” is the working average transaction volume from Step 3, and “2 seconds” is the server class response time as measured. 45 tps x 2 seconds = 90 The transaction type requires 90 active links to the server class. NOTE: A transaction type might access more than one server class to complete the transaction. The transaction might even access a given server class more than once. Be sure to account for all transaction accesses when making this calculation.
TCPS For TCPs, use this formula: no. of links required = constant x MAXSERVERS x no. of TCPs no. of TCPs 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.
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.
no. of TCPs ---> from Step 2 n=1 where all server classes refers to all the server classes in your configuration. no. of links required is the number of links required by the TCP for this server class (from Step 5). no. of TCPs is the total number of TCPs from 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 allows and TERM and PROGRAM objects, for information on starting and stopping these objects, see the Pathway/iTS System Management Manual.
In response to the START SERVER command, the PATHMON process performs these startup operations for each static server process in the server class: • Creates and starts the server process by running the program specified in the PROGRAM attribute of the SERVER definition, using all parameters previously indicated by the SET SERVER commands. • Sends a startup message to the server process, describing that process’ environment.
Link Requests If the PATHMON process gets a link request from a link manager to a server class, and the server class is not frozen but no server processes are started, then the PATHMON process starts only the server process that satisfies the link manager request; it does not start all of the static server processes in the server class.
1. 2. 3. 4. 5. 6. The PATHMON process notifies all link managers, such as ACS subsystem processes and TCPs as well as all external TCPs, to delink from the server class. The link managers close all server processes. The server processes respond by preparing for termination and then stopping themselves. For any server class that has never been linked to a ACS subsystem processes, or TCP, the PATHMON process calls the Guardian OPEN/CLOSE procedure to try and trigger the server class to terminate.
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.
A System Management Scenario You know that users are encountering difficulties with some of their workstation client applications. The applications will not come up. By asking a few questions, you determine that RSC is running. Investigation on the host side reveals no telecommunications outages, so the problems must be in the PATHMON environment. 1. You use the STATUS SERVER * command to determine which server classes are currently running. 2.
Example 3 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.
Example 4 INFO PATHMON Display PATHMON BACKUPCPU 4 DUMP ON (FILE \SYS.$VOL1.TESTING.MONDUMP) The display in Example 4 (page 83) indicates that the PATHMON backup process is running in processor 4 and that the PATHMON process, if it encounters an internal error, writes the data stack information to \SYS.$VOL1.TESTING.MONDUMP. The INFO SERVER Command The INFO SERVER command displays information about a single server class, multiple server classes, or all server classes controlled by the PATHMON process.
parameter). A maximum of four server processes can run concurrently (indicated by the MAXSERVERS parameter). Link managers, such as the ACS subsystem processes, can each have only one link to each server process within this class (indicated by the LINKDEPTH parameter). The maximum number of concurrent send operations to any server process in this class is one (indicated by the MAXLINKS parameter). This example displays information about a single OSS server class, TRANS-SRV1, using the OBEYFORM option.
For a complete description of all the SERVER attributes viewable through the INFO SERVER command, see “INFO SERVER Command” (page 181). Displaying Status Information You can display the status of an object, error messages pertaining to the object, and other associated information using the STATUS command. The STATUS command displays information about the PATHMON process, SERVER objects, ACS subsystem processes, and the PATHMON environment.
The STATUS PATHMON Command The STATUS PATHMON command displays status for the PATHMON process, the PATHMON configuration file, and the logging files: = STATUS PATHMON Example 8 (page 86) shows the information displayed in response to the command. Example 8 STATUS PATHMON Display PATHMON \COMM.$PMON -- STATE=RUNNING CPUS 8:0 PATHCTL LOG1 LOG2 (OPEN) (CLOSED) (CLOSED) $OPER.TRANCNFG.PATHCTL $0 REQNUM 1 13 14 15 16 42 FILE PATHCOM EXT TCP PATHCOM LINKMON PATHCOM SPI PID $Y565 \SYS2.$ZCMC \SYS.
Example 9 STATUS SERVER Display SERVER #RUNNING PROCESS-SERVER 4 ERROR INFO PROCESS-SERVER currently has four server processes running. For each server class, you can also view the status of the server processes within the server class by including the DETAIL option in your command, as shown in this example: = STATUS SERVER PROCESS-SERVER, DETAIL Example 10 (page 87) shows the status for PROCESS-SERVER, a Guardian server class, and all server processes associated with this class.
Example 11 STATUS SERVER With PROCESSES Option: Guardian Server SERVER #RUNNING PROCESS-SERVER 4 ERROR 3115 INFO 34 PROCESS $ZTP0 STATE RUNNING ERROR INFO #LINKS 5 WEIGHT 11 LINKER M6530-TCP2 M6530-TCP6 LINK COUNT 003 002 PROCESS $ZTP1 STATE RUNNING ERROR 3115 INFO 34 #LINKS 4 WEIGHT 10 LINKER M6530-TCP4 M6530-TCP5 LINK COUNT 002 002 PROCESS $ZTP2 STATE RUNNING INFO #LINKS 4 WEIGHT 9 LINKER M6530-TCP1 L\SYS.
Example 12 STATUS SERVER With PROCESSES Option: OSS Server SERVER TRAN-SRVR #RUNNING 4 ERROR INFO PROCESS $ZTX0 STATE RUNNING ERROR INFO #LINKS 5 WEIGHT 11 LINKER L\SYS.$ZL12 L\SYS.$ZL13 LINK COUNT 003 002 PROCESS $ZTX1 STATE RUNNING ERROR INFO #LINKS 3 WEIGHT 08 LINKER L\SYS.$ZL14 LINK COUNT 003 PROCESS $ZTX2 STATE RUNNING ERROR INFO #LINKS 2 WEIGHT 05 LINKER L\SYS.$ZL15 L\SYS.
= . . (5 minutes go by) . = STATS TERM ... . = STATS TCP ... . = CONTROL TCP TCP-A, STATS OFF Once you enter the CONTROL TCP STATS OFF parameter, all statistical counters are reset to 0. The STATS SERVER Command The STATS SERVER command displays statistics, including response time information, about server class operations for a single server class, multiple server classes, or all server classes defined for a PATHMON environment.
Example 13 STATS SERVER Display: Guardian Server SERVER PROCESS-SERVER IN TCP M6530-TCP1 09:47:00 QUEUE INFO: I/O INFO: SEND REPLY 07 APR 1994, REQ CNT 0 REQ CNT 99198 % WAIT 0.0 MAX TSIZE 418 MAX WAITS 0 AVG TSIZE 184 1744 AVG WAITS 0.00 I/O CNT 99198 228 % DYNAMIC 0.0 MAX RESP 20.05 MIN RESP 0.00 STAND DEV 0.26 RESPONSE TIME INFO (TIME VALUES IN SECS): SEND TO SERVERCLASS SUMMARY # MEAS 99195 AVG RESP 0.
SUMMARY # MEAS 65277 AVG RESP 0.45 MAX RESP 42.17 MIN RESP 0.03 IN LINKMON L\SYS.$ZL11 09:47:01 STAND DEV 0.54 07 APR 1994, QUEUE INFO: REQ CNT 1 % WAIT 0.0 MAX WAITS 0 AVG WAITS 0.00 I/O INFO: SEND REPLY REQ CNT 12 MAX TSIZE 606 126 AVG TSIZE 606 126 I/O CNT 12 % DYNAMIC 0.
Example 14 STATS SERVER Display: OSS Server SERVER TRAN-SRVR IN LINKMON L\SYS.$ZL11 04 MAR 1995, 08:42:06 QUEUE INFO: REQ CNT % WAIT MAX WAITS AVG WAITS 1 0.0 0 0.00 I/O INFO: REQ CNT MAX TSIZE AVG TSIZE I/O CNT SEND 102 600 600 13 119 120 REPLY IN LINKMON L\SYS.$ZL12 04 % DYNAMIC 0.0 MAR 1995, 08:42:06 QUEUE INFO: REQ CNT % WAIT MAX WAITS AVG WAITS 0 0.0 0 0.00 I/O INFO: REQ CNT MAX TSIZE AVG TSIZE I/O CNT SEND 87 55 50 25 226 215 REPLY IN LINKMON L\SYS.
IN LINKMON L\SYS.$ZL10 04 MAR 1995, 08:42:06 QUEUE INFO: REQ CNT % WAIT MAX WAITS AVG WAITS % DYNAMIC 1 0.0 0 0.00 0.0 I/O INFO: REQ CNT MAX TSIZE AVG TSIZE I/O CNT SEND 15 100 100 03 4235 4000 REPLY Reconfiguring a PATHMON Environment As your business needs change, requirements for your transaction processing configuration are likely to change.
= SET PATHWAY MAXPARAMS 30 = SET PATHWAY MAXSTARTUPS 40 = START PATHWAY COLD! For more information about shutting down and starting your configuration, see “Starting and Stopping a PATHMON Environment” (page 34). NOTE: When specifying limits, you must always allow space for system growth. If you specify sufficient limits initially, you can avoid the need to reconfigure and cold start your system to specify new limits. For more details, see “Configuring Objects in a PATHMON Environment” (page 51).
Before using the DELETE command for a SERVER, you must freeze and stop the SERVER by using the FREEZE and STOP commands, respectively. To delete the server class named SALES, you enter: = FREEZE SERVER SALES = STOP SERVER SALES = DELETE SERVER SALES Changing Backup CPUs and Dump Files Although you must stop most PATHMON-controlled objects before you change their attributes, you can change three attributes for the PATHMON process while it is running: • The backup processor for the process.
You cannot change the OWNER and SECURITY attributes while a PATHMON environment is running; you must first shut down the environment, as shown in this example. Recall that when you configure global limits after a shutdown, you must specify all limits, not just the ones you are changing. Once you have specified old and new limits, and changed the OWNER and SECURITY attributes, you must use the COLD! start option to restart the PATHMON environment: = = . . .
6> PURGE NEWCONF To rename the file named NEWCONF to OLDCONF, enter: 7> RENAME NEWCONF, OLDCONF 3. Produce the OBEYFORM file. To do this, enter a PATHCOM OBEY command, specifying as input the EDIT file described in Step 1. For example, if you had named the EDIT file INFOCOM, you would enter: = OBEY INFOCOM This OBEY command runs the INFO commands contained in the EDIT file.
Security Logging The TS/MP 2.5 PATHMON makes a log entry for the following commands when they are issued on the objects configured under PATHMON: • ABORT • ADD • ALTER • DELETE • FREEZE • STOP • THAW • START The audit logging is done when the STATUS messages are d. The message format is shown below: ddMMMyy,mm:ss : STATUS - *1166* , AUDIT MSG - - USER where: ddMMMyy,mm:ss Displays date and time.
= 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 must ensure that the file is large enough.) The PATHMON process records the log file names that you select in the PATHMON configuration file. After a cool start, the same log files specified in the configuration file are used again; records produced after the cool start are appended to these files.
between these objects and server processes can slow down the response time of PATHMON processes compared to other commands (from PATHCOM or SPI). • Creating and deleting links If the PATHMON process is configured so that it is constantly creating and deleting links, the server might wait for processor cycles, causing incoming transactions to be placed on the server-class wait queue.
Detecting Problems These factors might cause the PATHMON process to be busy at times other than startup and shutdown: • Poor configuration • Creating and deleting links • Gathering statistics and information • Logging errors • Failures Poor Configuration If a link manager, such as a ACS subsystem processes, or TCP, cannot establish communication with a server process, the link manager indicates this situation to the screen program or Pathsend requestor, and the PATHMON process writes an error mess
In certain network situations, communication delays between the PATHMON process and link manager that is the ACS subsystem 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.
If error dumping has not been specified and the PATHMON tables (showing, for example, server states) appear to be in error, your representative may ask that you force a dump by performing: >PATHCOM $ =CONTROL PATHMON, DUMPMEMORY (FILE ) =EXIT where pm is the name of your PATHMON process and pmdump is name of the dump file. Note that the DUMPMEMORY option is not a substitute for setting the DUMP option to ON.
3. 4. 5. or functions you were performing at the time of the failure. Collect this information to have available when you contact your HP representative for help. Bring the PATHMON environment down using Guardian STOP commands to stop all processes. For more information about the Guardian STOP command, see the Guardian User’s Guide. Start PATHMON again. Coolstart the PATHMON environment.
There is an interval when the PATHMON process can grant a link to an associative server process that is stopping itself. Although the stopped state allows you to use the ALTER SERVER command to specify changes for configuration attributes, the changes you specify do not take effect until the associative server is actually stopped and then restarted from the same the PATHMON process.
Table 3 Migration Considerations: Object Attribute Values (continued) Object or Process Attribute Considerations/ Recommendations SERVER CLASS CPUS cpu-list Ensure that CPUs on new system have same numbers or change manually. DEFINE define-spec Could include system name stored as buffer; check and change manually if required. HOMETERM termname Ensure that a terminal with same name exists on new system or change manually.
You must also consider whether Pathsend requestors or SCREEN COBOL applications —perhaps those controlled by remote systems—use hard-coded node names in requests to server processes that belong to the application you want to migrate. If Pathsend procedure calls and screen application requests have not been coded for node independence, the applicable code must be changed manually.
6 Managing the Pathsend Environment The Pathsend Environment This section discusses the Pathsend environment, which consists of Pathsend processes and ACS subsystem processes, and the tasks you perform to manage the Pathsend environment. For more information on ACS subsystem core processes, see the TS/MP 2.5 Release Supplement. Pathsend Processes Pathsend processes are user-written Guardian programs that use Pathsend procedure calls to communicate with server classes.
Each processor contains only one set of ACS core processes (Redirector (ROUT), PB, and configuration subscriber (CS) programs running as $ZLnn, $ZPnn, and $ZCSnn processes respectively, where nn is the processor number), which are responsible for all Pathsend requestors executing in that processor. ACS subsystem core processes acquire links from the PATHMON process that controls the server class. The ROUT process then shares the links among the Pathsend requestors executing in the processor.
Table 5 (page 111) lists the ACS core processes and their respective process names and object names. Table 5 ACS Core Processes ACS Core Process Process Name Object Name BC ($ZACS) $SYSTEM.SYSnn.BC PB ($ZPnn) $SYSTEM.SYSnn.PB CS ($ZCSnn) $SYSTEM.SYSnn.CS ROUT ($ZLnn) $SYSTEM.SYSnn.ROUT Initialization Unlike the TS/MP 2.0 LINKMON process, the ACS subsystem core processes are initialized as soon as they are started.
This example specifies that a maximum of 16 link manager (LINKMON/ACS subsystem) processes can access your PATHMON environment: = SET PATHWAY MAXLINKMONS 16 If you have Pathsend processes in other systems that need to access server classes in your PATHMON environment, setting the MAXLINKMONS attribute to the number of CPUs in your system might not be correct.
= 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. If you do not specify the SERVER OWNER parameter, the default user ID is the owner ID of the user who started the PATHMON process. SECURITY The SERVER SECURITY attribute specifies the users, relative to the SERVER OWNER, who can access a server class from a Pathsend process.
• STATUS PATHWAY • STATUS SERVER (For complete examples of display output for the STATUS PATHWAY, STATUS PATHMON, and STATUS SERVER commands, see “Maintaining a PATHMON Environment” (page 80).) STATUS LINKMON Command To get status information about the LINKMON processes communicating with your PATHMON environment, use the STATUS LINKMON command. This command displays status information about a particular LINKMON process running on a specific system: = STATUS LINKMON L\ABC.
Example 17 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 WAIT . . . 15 LINKMON $ZL11 30,1 . . . STATUS PATHWAY Command To determine the number of LINKMON processes communicating with your PATHMON environment, use the STATUS PATHWAY command: = STATUS PATHWAY Example 18 (page 115) shows that there is 1 LINKMON process communicating with this PATHMON environment.
Example 19 LINKMON Information in STATUS SERVER Display SERVER PROCESS-SERVER PROCESS $ZTP2 #RUNNING ERROR INFO 4 3115 34 . . . STATE ERROR INFO #LINKS WEIGHT RUNNING 4 9 LINKER M6530-TCP1 L\SYS.$ZL11 LINK COUNT 003 001 . . . STATS SERVER Command To display statistics collected by ACS subsystem 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” (page 202). This section is divided into two parts: • The first part describes server process performance statistics that the ACS subsystem processes, and the TCP collect. • The second part describes server process performance statistics collected only by the TCPs.
Example 20 Sample Server Statistics SERVER SERVME IN TCP TCP1 19 FEB 1996, 15:22:30 * QUEUE INFO*: REQ CNT % WAIT MAX WAITS AVG WAITS % DYNAMIC 33272 99.8 7 2.37 99.9 I/O INFO*: REQ CNT MAX TSIZE AVG TSIZE I/O CNT SEND 33304 2 2 33304 2 2 REPLY RESPONSE TIME INFO (TIME VALUES IN SECS)*: SEND TO SERVERCLASS SUMMARY # MEAS AVG RESP MAX RESP MIN RESP STAND DEV 33303 0.50 2.51 0.10 0.
Example 21 QUEUE INFO Section of Sample Server Statistics SERVER SERVME IN TCP TCP1 19 FEB 1996, 15:22:30 * QUEUE INFO REQ CNT % WAIT MAX WAITS AVG WAITS % DYNAMIC 33272 99.8 7 2.37 99.9 * : IN ACS subsystem 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.
In a well-tuned system (with no dynamic servers), the only delay occurs at startup time, when initial links are granted to servers in the server class. If statistics are reset after startup, then the server queue counts must be 0. If the server queue counts are not 0, then you must increase the number of static servers. % DYNAMIC The higher the number indicated for % DYNAMIC, then the greater the chance that a dynamic server will be required.
Table 7 Server Statistics for I/O Info Statistic For SEND, Indicates: For REPLY, Indicates: REQ CNT Total number of Pathsends to servers in a N.A. server class. Pathsends include any of the following APIs: SERVERCLASS_DIALOG_ BEGIN_, SERVERCLASS_DIALOG_ SEND_, SERVERCLASS_SEND_, and SERVERCLASS_SENDL_ . MAX TSIZE Size, in bytes, of the largest amount of data Size, in bytes, of the largest amount of data transferred in a send. transferred in a reply from the server class.
Example 23 RESPONSE TIME INFO Section of Sample Server Statistics SERVER SERVME? IN TCP TCP1 19 FEB 1996, 15:22:30 * . . . RESPONSE TIME INFO (TIME VALUES IN SECS) * : SEND TO SERVERCLASS SUMMARY # MEAS AVG RESP MAX RESP MIN RESP STAND DEV 33303 0.50 2.51 0.10 0.49 . . . * Collected only if you have the Pathway/iTS product and TCP STATS ON Table 8 (page 122) shows the response time statistics and what they indicate.
within a given time interval. These statistics are collected only if your environment includes the Pathway/iTS product. The supplemental information is contained in the frequency distribution table, as shown in Example 24 (page 124). A separate frequency distribution table is generated for each server class.
Example 24 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 9 REQ CNT MAX TSIZE AVG TSIZE I/O CNT 33740 2 2 33740 2 2 REQ CNT * : I/O INFO * : SEND RESPONSE TIME INFO (TIME VALUES IN SECS) * : SEND TO SERVERCLASS SUMMARY AVG RESP MAX RESP MIN RESP STAND DEV 0.50 2.51 0.01 0.49 TIME INTERVAL (0.05 SECS # MEAS CUM % TI01 <0.01 132 0.3 0.01 <= TI02 <0.
0.90 <= TI18 < 0.96 0 49.9 0.96 <= TI19 < 1.02 16472 98.8 1.02 <= TI20 398 100.0 * Collected only if you have the Pathway/iTS product and TCP STATS ON Table 9 (page 125) shows the server statistics for frequency distribution and what they indicate.
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” (page 17) through “Tuning Your System by Using Statistics” (page 117). NOTE: This manual provides information specific to commands dealing with objects managed through the NonStop TS/MP product.
Command List Table 10 (page 127) is a list of the commands you can run using PATHCOM. The table entries provide the name of the command, its description, and the names of the objects influenced by the command. NOTE: The commands in this table pertain only to objects managed through the NonStop TS/MP product. For commands for objects managed under the Pathway/iTS product, see Pathway/iTS System Management Manual.
Table 10 PATHCOM Commands (continued) PATHCOM Commands Description Valid Objects SHOW Displays current values for the object attributes CMDCWD, CMDVOL, SERVER and environmental settings for PATHCOM SHUTDOWN Stops all PATHMON-controlled objects except PATHMON process PATHCOM SHUTDOWN2 Stops all PATHMON-controlled objects except PATHMON process PATHCOM START Starts one or more objects PATHWAY process, SERVER STATS Displays resource usage and system performance statistics SERVER STATUS Displays
Table 11 Commands and Objects (continued) Objects PATHCOM Commands PATHWAY PATHMON SERVER LINKMON x STATS x x x STOP x x SWITCH x STATUS x x THAW Command Format When entering PATHCOM commands, consider: • In general, options within a command are position independent. That is, you can place the options in any order within the command-line. For example, this command: SET SERVER PROCESSTYPE GUARDIAN, AUTORESTART 1, PROGRAM $MKT.PR6 can also be entered as: SET SERVER PROGRAM $MKT.
NOTE: You cannot embed PATHCOM comments in TACL scripts. In TACL scripts, information enclosed in brackets is interpreted as a function, not as a comment. For information on including comments in TACL scripts, see the TACL Reference Manual. • A PATHCOM command-line spans input records if the last nonblank character is an ampersand (&). Multiple commands, separated by semicolons, can appear on the same line. If command parameters are repeated, PATHCOM uses the last value entered for a parameter.
Guardian File Names Each disk file in the Guardian file-system is identified by a unique, symbolic file name, described in these paragraphs.
Absolute Pathnames Absolute pathnames must begin with a forward slash (/) and can have a maximum length of 1023 characters; the last character (character 1024) is reserved for a null. When setting an OSS pathname using the SET SERVER CWD command or when setting a default directory using the CMDCWD command, you must specify an absolute pathname. Absolute pathnames specified for server process attributes are validated when the SET SERVER command is processed.
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.5, HP recommends that you use PDMCOM instead of PATHCOM because it can communicate with multiple PATHMONs simultaneously. For more information on PDMCOM, see the TS/MP 2.
INSPECT ON | SAVEABEND establishes default debugging conditions for the process. HP recommends the following values: ON directs the file system to use Inspect if a debug operation is required. SAVEABEND directs Inspect to create a copy of a process if it abends, and save it in a separate file for debugging purposes.
run-option is: IN command-file OUT list-file CPU number NAME $process-name NOWAIT PRI number 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. IN command-file specifies a file from which commands are read. The command file can contain the Pathway configuration (that is, the PATHCOM commands that establish characteristics for the Pathway environment, the terminals, the TCPs, and the server classes).
NOWAIT specifies that the TACL command interpreter is not to wait for PATHCOM, but is to return immediately with a command input prompt. This option is usually not included when PATHCOM is used interactively, but is useful when PATHCOM is used with a command file. 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.
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.5, HP recommends that you use PDMCOM instead of PATHCOM, because it can communicate with multiple PATHMONs simultaneously. For more information on PDMCOM, see the TS/MP 2.5 Release Supplement. CMDCWD Command Use the CMDCWD command to set a default OSS directory.
command. But PATHCOM uses values defined with the CMDCWD command to resolve relative pathnames when it processes ADD or ALTER commands. If a default absolute pathname /abc is defined with the CMDCWD command (assuming no value is set for the CWD attribute), all OSS relative path names in ADD or ALTER commands are resolved with the /abc absolute pathname. The resolved path names are sent to the PROCESS_SPAWN_ procedure.
command, all Guardian file names 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.
5> CMDVOL \FIELD.$SUPP Expanded filename is \FIELD.$SUPP..SYS2. filename 6> CMDVOL \*.$ADMIN.VAC Expanded filename is \ filename -PATHMONnode.$ ADMIN.VAC. filename where current-PATHCOM-user-node is the node of the user who started PATHCOM. This example shows a default set when the Pathway NODEINDEPENDENT attribute is set to ON: CMDVOL \* Expanded filename is \ current -PATHMONnode. current-PATHCOM- user-volume.currentPATHCOM-user-subvolume.
PATHCOM $PM1;ERRORS 10;OBEY PWCMD EXIT Command Use the EXIT command to terminate communication with PATHCOM. If PATHCOM is using a command file, this command terminates the command file. EXIT PATHCOM stops when it encounters the EXIT command in a command file (the IN file). FC Command Use the FC command to edit or repeat a command line. FC [ [-] number | string ] number is the command number of the command to be retrieved. If number is passed as -7, the 7th previous command is retrieved.
SET PATHWAY MAXXTERMS 45 d// r50 The corrected command is: SET PATHWAY MAXTERMS 50 • You can specify a string after the FC command. If the string matches the starting letters of any of the prior ten commands, the corresponding command appears. It also allows you to edit and execute the command. • The FC command is displayed only if the command length is greater than 2.
OUT list-file specifies the name of a file to which PATHCOM directs the HELP output. If you omit this option, the output goes to the PATHCOM list file; this is typically the home terminal. ALL lists the syntax for all PATHCOM commands. COMMANDS lists the names of all PATHCOM commands. specifies a particular PATHCOM command syntax to appear. When entering the name of the command, do not include the angle brackets.
In response, PATHCOM displays the syntax for a TERM parameter list as: ::= TERM * [ [ , ] ...
3>ALTER SRV1, DEBUG ON 4>ALTER SRV1, HOMETERM $ZTNT.#PTA2AK3 5>ALTER SRV1, PROCESS $PROC 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.
specifies the node name to be used. $volume specifies the volume to be used. subvolume specifies the subvolume to be used. Considerations • If the node, volume, and subvolume are omitted and the current command file is a disk file, this command sets the default settings to that of the current command file. • If the OBEYVOL command is not issued, the default setting is the node, volume, and subvolume in which PATHCOM is running.
Examples This command opens the PATHMON process named $PATH: OPEN $PATH This command opens the PATHMON process named $PATH3 running on node \SYS1: OPEN \SYS1.$PATH3 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.
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. OBEYVOL displays the default node, volume, and subvolume for expansion of command file names. Examples The command SHOW CMDVOL displays: CMDVOL \TNS.$DICS.
Example • 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.
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.
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 ) SPREBALANCECPU number BACKUPCPU number specifies the processor where the PATHMON backup process runs.
triggers PATHMON to start the rebalancing of the server processes on the specified processor. The PATHCOM rejects this command if the PATHMON processes are not configured to run in MANUAL mode. The number indicates the CPU number on which server processes are to be rebalanced. The command accepts processor number as a parameter. The server processes which used to run on the mentioned processor before processor failure, will be shifted back to the original processor.
This Message… Is Displayed When… processes cannot be started and the PATHMON process returns this error. *1093* BACKUP PROCESSOR DOWN For a multiprocessor system, you specified a backup processor that does not exist or is not operational. For a single processor system, you included the BACKUPCPU attribute. *1095* ILLEGAL CPU NUMBER You specified for the BACKUPCPU attribute, the same processor in which the PATHMON primary process is running.
Examples The INFO PATHMON command causes the PATHMON process to display: =INFO PATHMON PATHMON BACKUPCPU 4 DUMP ON (FILE \SY.$VOL1.TESTING.MONDUMP) This command: INFO PATHMON, OBEYFORM causes PATHMON to display the information in command form: SET PATHMON BACKUPCPU 4 SET PATHMON DUMP ON (FILE \SY.$VOL1.TESTING.
MAXSPI N MAXSTARTUPS N MAXTCPS N MAXTELLQUEUE N MAXTELLS N MAXTERMS N MAXTMFRESTARTS N OWNER \OCOOL.G,U SECURITY “N” SPREBALANCEMODE “AUTO” [CURRENTLY M] [CURRENTLY M] [CURRENTLY M] [CURRENTLY M] OUT list-file directs output to the named list file; this file can be a DEFINE name. If this option is omitted, the PATHMON process directs the output to the PATHCOM list file; this is typically the home terminal.
SET SET SET SET SET SET SET SET SET PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY PATHWAY MAXPATHCOMS 5 MAXSERVERCLASSES ? MAXSERVERPROCESSES ? MAXSPI 1 MAXSTARTUPS ? NODEINDEPENDENT OFF OWNER \TS.8,8 SECURITY "U" SPREBALANCEMODE “DISABLE” These commands direct the Pathway environment information to a file: INFO/OUT PWINFO/PATHWAY INFO/OUT PWINFO/PATHWAY, OBEYFORM Note that you must add the START PATHWAY command to the OUT file before using the file to start a Pathway environment.
specifies that messages must be formatted as event messages. If you omit EVENTFORMAT, text messages are generated. Considerations • The OUT file initially specified with the PATHMON RUN command becomes the initial LOG1 file until you specify otherwise by issuing a logging command. The file is opened when you specify the STATUS attribute • As a best practice, specify a disk file for logging than a terminal because log messages are lost after they scroll off the terminal screen.
If you omit this option, the PATHMON process resumes its primary process in the processor recorded in the PATHMON configuration file. If this processor is down, no error occurs. Considerations • After a series of SWITCH and CONTROL commands, the PATHMON primary process might be running in a processor other than the one you initially defined. Use the STATUS PATHMON command to display the CPUs where the primary and backup PATHMON processes are running.
NOTE: file-name specifies a file that already exists and the PATHMON process attempts to dump to this file, a dump is not performed and error *1123* PATHMON, MEMORY DUMP NOT TAKEN is generated. OFF directs the PATHMON process not to write data stack and PATHMON configuration file information to a file when it encounters an internal error.
MAXDEFINES number MAXEXTERNALTCPS number MAXLINKMONS number MAXPATHCOMS number MAXPROGRAMS number MAXSPI number MAXTELLQUEUE number MAXTELLS number MAXTMFRESTARTS number NODEINDEPENDENT [ON | OFF] OWNER ownerid SECURITY security-attribute SPREBALANCEMODE rbmodeval pw-attribute For information about configuration limits for environments, see “Configuration Limits and Defaults” (page 318).
MAXSTARTUPS number is the maximum number of server classes that can have STARTUP messages. number must be a value from 0 through 4095. To the PATHMON process to process an ALTER SERVER STARTUP command, specify a maximum of 4094 for this attribute. This attribute is required. It has no default. Because only one SET SERVER STARTUP definition for each server class counts toward this limit, the number for this attribute must not exceed the value for MAXSERVERCLASSES.
is the maximum number of Subsystem Programmatic Interface (SPI) processes that can run simultaneously within the Pathway environment. SPI is part of the HP Distributed Systems Management (DSM) facility. For more information on the SPI interface, see the NonStop TS/MP and Pathway Management Programming Commands Manual. number must be a value from 1 through 100. (Until a Pathway environment is started, only one SPI process or PATHCOM process at a time can open communication with the PATHMON process.
Object Associated File Name SERVERCLASS ASSIGN logical-unit assign-spec GUARDIAN-LIB file name IN file-name OUT file-name OWNER owner-id PROGRAM file-name VOLUME $volume nl nl nl nl nl nl SERVERPROCESS GUARDIAN-SWAP $volume HOMETERM termname nl 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 file-name nl nl nl nl nl nl nl TERM object* FILE file-name INSPECT file-name PRINTER file-name
The security attributes are the same as the Guardian 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. The default value is “O”.
When you issue the SHUTDOWN command, the PATHMON process: • Initiates the FREEZE and STOP for all server classes that PATHMON controls; stops the terminals and Pathway/iTS TCPs; writes the internal configuration and directory information to the PATHMON configuration file; and stops the PATHMON process itself. If a server process is engaged in a dialog at the time the SHUTDOWN command is issued, the shut down process waits until the dialog has completed.
[, STATUS { QU[IET] | AG[GREGATE] } ] [, UNTIL { DONE } { TIMEOUT number { HRS | MINS | SECS } } ] MODE specifies the amount of force to be used when shutting down the system. The default is ORDERLY. OR or ORDERLY s work in progress to complete before stopping. For example, a terminal that is waiting for the completion of an I/O to a server is not stopped until the I/O completes. The PATHCOM process is suspended until the shutdown request completes or until the Break key is pressed.
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. Returning the PATHCOM prompt allows you to investigate the state of the system (for example, issue a STATUS PATHWAY command), examine or stop any object, or escalate the shutdown process.
Examples This command causes PATHCOM to stop all processes controlled by the PATHMON process.
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 link manager (LINKMON/ACS subsystem) processes that have links to server processes. STATUS [ / OUT list-file / ] { [ LINKMON ] L\node.
Example 25 STATUS LINKMON Display Format LINKMON STATE ERROR INFO PROCESS CPU lm-name state pw-error info process-name cpu . . . . . . . . . . . . . . . . . . nl nl nl nl nl nl nl nl nl nl nl nl The fields in this display are as follows: Display Field Description LINKMON Full name of the LINKMON process, including the node name STATE Current state of the LINKMON process.
Example 26 STATUS PATHMON Display Format PATHMON \node.$process-name-- STATE=pmon-state CPUS PATHCTL (file-state) $pathctl-file-name [ ERROR LOG1 [S] [E] (file-state) $log1-file-name [ ERROR LOG2 [S] [E] (file-state) $log2-file-name [ ERROR REQNUM [A] reqnum . . . FILE type . . . PID pid . . . pri : = num = num = num backup ] ] ] PAID WAIT paid wait-cause . . . . . . The fields in this display are as follows: Display Field Description PATHMON - PATHMON process name and current state.
Display Field Description WAIT The reason a request is waiting. Possible values are: IO The request is waiting for an I/O operation to complete. LOCK The request is waiting for an object locked by another requestor. LOCK-QUEUE The requestor is waiting for space in the internal lock queue. BUF The request is waiting for internal buffer space to become available. LOG-QUEUE The request is waiting for an entry in the internal status logging message queue to become available.
Display Format—Running Example 27 (page 173) shows the format of the display returned by the STATUS PATHWAY command while the system is running.
Example 28 STATUS PATHWAY Display Format (After Shutdown Failure) PATHWAY --STATE = SHUTTING-DOWN (IN PROGRESS) - STARTED 2:02:39 STOPPED 4:08:44 RUNNING EXTERNALTCPS LINKMONS PATHCOMS SPI number number number number RUNNING SERVERCLASSES number STOPPED number THAWED number RUNNING SERVERPROCESSES number STOPPED number PENDING number RUNNING STOPPED PENDING TCPS number number number TERMS RUNNING number STOPPED number PENDING number FROZEN number FREEZE PENDING number SUSPENDED number
Example 29 STATUS PATHWAY Display Format (After Shutdown Failure) PATHWAY --STATE = SHUTTING-DOWN (FAILED) - STARTED 4:01:39 STOPPED 4:08:44 RUNNING EXTERNALTCPS LINKMONS PATHCOMS SPI number number number number RUNNING SERVERCLASSES number STOPPED number THAWED number RUNNING SERVERPROCESSES number STOPPED number PENDING number TCPS RUNNING number STOPPED number PENDING number TERMS RUNNING number STOPPED number PENDING number FROZEN number FREEZE PENDING number SUSPENDED number Calculat
To avoid orphaned processes, first use the STATUS PATHWAY command, before executing the STOP PATHMON command, to determine what type of processes are running. Use the STATUS command on each type of object to find the names of the active processes, then stop each process. After all processes are stopped, then run the STOP PATHMON command.
12 SERVER Commands This section describes the PATHCOM commands that define and control SERVER objects; the commands are listed in alphabetic order.
Consideration The ADD SERVER command does not affect values established with the SET SERVER or RESET SERVER commands. Use the RESET SERVER command to change all of the values to their defaults, or use the SET SERVER command to replace only specific values.
specifies a single server class attribute keyword or several keywords separated by commas and enclosed in parentheses.
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 ]... ) } Column Head server-class specifies the name of a SERVER object.
Considerations • If you are using Pathway/iTS, consider these: ◦ Unless ! is specified, the freeze does not take effect until all SCREEN COBOL STOP-MODE special registers have a value of zero and no server in the server class has incomplete or outstanding requests. In the interim, the server class is put into the FREEZE-PENDING state.
SERVER * displays attribute values of all server classes in the PATHMON configuration file. This command does not display information about servers controlled by a PATHMON process in a different PATHMON environment. OBEYFORM displays the information in the format you would use to set up a PATHMON configuration file; each attribute appears as a syntactically correct SET command. PATHCOM adds a RESET SERVER command before and an ADD SERVER command after each SERVER object description.
PATHWAY command at the end of the OUT file before using the file to start the PATHWAY object. Examples These command requests information for two server classes: INFO (CLASS-2,CLASS-3) This command: INFO SERVER CLASS-1, OBEYFORM returns the following 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.
this attribute and will not display the same if SHOW SERVER command is issued, see “Example 2” (page 184). RESET SERVER [ server-keyword [ , server-keyword ]... ] server-keyword is: ARGLIST GUARDIAN-SWAP PROCESS ASSIGN HOMETERM PROCESSTYPE AUTORESTART IN PROGRAM CPUS LINKDEPTH SECURITY CREATEDELAY MAXLINKS STARTUP CWD MAXSERVERS STDERR DEBUG NUMSTATIC STDIN DEFINE OUT STDOUT DELETEDELAY OWNER TMF ENV PARAM UMASK VOLUME server-keyword specifies one or more attributes to be reset.
The SHOW SERVER command after RESET SERVER does not display the new attribute. SERVER PROCESSTYPE GUARDIAN . . SECURITY “N” TMF OFF VOLUME \node.$volume.subvolume 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 [,...
create-spec is: { { { { { { { { { EXT [ ( ] pri-extent-size [ ) ] } EXT ( [ pri-extent-size ] , sec-extent-size ) } EXCLUSIVE } SHARED } PROTECTED } I/O } INPUT } OUTPUT } CODE file-code } process-attribute is: [ [ [ [ [ [ ASSOCIATIVE { ON | OFF} CPUS primary:backup | cpu DEBUG { ON | OFF } GUARDIAN-SWAP $volume HOMETERM file-name PRI number ] ] ] ] ] ] server-attribute Specifies one or more attributes of the SERVER object being defined. The PROGRAM attribute is the only required attribute.
CAUTION: Neither PATHCOM nor the PATHMON process check for escape sequences in an argument list. If escape sequences or other nonprintable characters are included in an argument list, they are passed as input to PATHMON and unexpected results might occur. HP recommends that all characters specified for the ARGLIST attribute be ASCII printable. To specify escape sequences in an argument list, HP recommends that you use the SPI management programming interface, see the TS/MP 2.5 Management Programming Manual.
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” (page 138) and “SET PATHWAY Command” (page 159). create-spec specifies one of these file creation attributes or open attributes: File-creation or Open Attribute Description EXT Specifies the size of the file extents allocated to the file. pri-extent-size and sec-extent-size can be integers from 1 through 65,535.
and processor 1 is down, the PATHMON process starts the next server in processor 3. 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.
DEBUG { ON | OFF } specifies whether the server processes in this server class enter debug mode when starting. If you omit this attribute, the default is OFF. ON directs the server processes to enter debug mode. If the PATHMON process was started with INSPECT ON or the server program was compiled or bound with the Inspect process defined, the servers enter Inspect mode for debugging. For more information about Inspect mode, see the Inspect Manual.
CAUTION: Neither PATHCOM nor the PATHMON process checks for escape sequences in an environment list. If escape sequences or other nonprintable characters are included in an environment list, they are passed as input to PATHCOM, and unexpected results might occur. HP recommends that all characters specified for the ENV attribute be ASCII printable. To specify escape sequences in an environment list, HP recommends that you use the SPI management programming interface; see the TS/MP 2.
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” (page 138) and “SET PATHWAY Command” (page 159). This attribute is valid for Guardian and OSS server processes. IN file-name specifies the name of the input file passed to the server process in the startup message; this can be a DEFINE name.
number must be a value from 0 through 4095. If you omit this attribute, the default is 1. If MAXSERVERS is greater than the number of server process names that you define with the PROCESS attribute, the operating system assigns process names in the form $Xnnn, $Ynnn, or $Znnn after the last predefined process name is used. The sum of all MAXSERVERS values for all server classes cannot exceed the number defined in the SET PATHWAY MAXSERVERPROCESSES attribute.
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. This string must be enclosed in quotation marks if you include blanks, commas, or quotation marks in the value. Embedded quotation marks must be doubled. The PATHMON process uses the information you supply for this parameter to send a PARAM message to each server that it starts.
If you omit this attribute, the PATHMON process assigns all CPUs. See the description of the CPUS attribute earlier in this command. DEBUG { ON | OFF } determines whether the server process enters debug mode upon startup. If you omit this attribute, the default is ON. ON directs the server process to enter debug mode. OFF directs the server process not to enter debug mode.
Quotation marks are required. If you omit this attribute, the default is “N”. This attribute is valid for Guardian and OSS server processes. STARTUP string specifies the character string that is sent to a Guardian server process in the startup message. Leading blanks are ignored. If you want embedded blanks to be read as part of the startup string, enclose string in quotation marks. If the string includes quotation marks, they must be doubled. This attribute is valid for Guardian server processes only.
If you omit this attribute, the default is OFF. ON s servers to lock and update audited files. The 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 ACS subsystem processes or TCP process opens the servers with a syncdepth of 1. The ACS subsystem processes do not perform checkpoint operations; it automatically retries I/O errors in the same way as the operating system retries them.
Server Class DEFINEs A server process context includes any DEFINEs that you specified using the DEFINE attribute of the SET SERVER command and a _DEFAULTS DEFINE automatically generated by the PATHMON process for values you did not specify. You can create DEFINEs to specify the default volume and subvolume for a server process and to specify files used by the server. For example, these PATHCOM commands form part of a Guardian server class definition: SET SERVER PROGRAM $DATA.PW.
Examples These commands define a subset of the server class attributes: RESET SERVER SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SET SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER SERVER PROCESSTYPE GUARDIAN ASSIGN DDL, \*.$DATA.DIC.DDL AUTORESTART 4 CPUS (0:1, 2:3) CREATEDELAY 10 SECS DELETEDELAY 5 MINS LINKDEPTH 1 MAXLINKS 5 MAXSERVERS 7 NUMSTATIC 2 OWNER \*.
SHOW SERVER Command Use the SHOW SERVER command to display a subset of the attribute values for a server class, in alphabetic order. Only attributes consistent with the process type (Guardian or OSS) are displayed. If a value has not been configured for an attribute, this command displays the current default value. SHOW [ / OUT list-file / ] SERVER OUT list-file directs output to the named list file; this can be a DEFINE name.
DEFINE PARAM GUARDIAN-LIB PROCESS IN STARTUP These OSS attributes are displayed only if they have values defined: ARGLIST CWD DEFINE ENV GUARDIAN-LIB PROCESS STDERR STDIN STDOUT The CWD attribute appears 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).
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. 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.
OUT list-file directs output to the named list file; this can be a DEFINE name. If this option is omitted, the PATHMON process directs the output to the PATHCOM list file; this is typically the home terminal. server-class specifies the name of a previously defined and added server class. Use either a single name or several names separated by commas and enclosed in parentheses. SERVER * displays statistics for all server classes in the PATHMON configuration file.
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 manager that is the ACS subsystem processes. STATUS [ / OUT list-file / ] { [ SERVER ] name [ , PROCESS $process-name ] } { [ SERVER ] name [ , PROCESSES ] } { [ SERVER ] name [ , DETAIL ] } { [ SERVER ] name [ , FREEZE ] } { [ SERVER ] ( name [ , name ]... ) [ , PROCESSES { [ SERVER ] ( name [ , name ]...
. . . . . . . . The fields in this display are as follows: Display Field Description SERVER Name of the server class. #RUNNING Number of server processes in the server class that are currently running. ERROR Pathway error number. This number includes any error that might occur when the PATHMON process attempts to create a dynamic server.
Display Field Description LINKS Number of the links from link managers to the server process. WEIGHT Indicates the use of the server process compared to the use of other server processes in the server class. For each link to a server class, the server process’s weight is incremented by 3 for the first link from a given link manager that is the ACS subsystem process, by 2 for the second link from that link manager, and by 1 for all subsequent links from that link manager.
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 in the following section: STATUS SERVER FREEZE Display Format SERVER STATE server-name . . . FREEZE STATE freeze-state . . . TERM FREEZE term-name freeze-state . . . . . .
STATUS SERVER *, DETAIL This commands display status information about the specified frozen server classes, and include various options: STATUS /OUT STATFLE/SERVER CLASS-1,FREEZE STATUS SERVER CLASS-2,FREEZE STATUS CLASS-3,FREEZE This command displays the names of terminals that have not yet accepted the freeze condition for all server classes: STATUS SERVER *, FREEZE This command displays the names of all server classes that are in a FROZEN or FREEZE-PENDING state: STATUS FREEZE STOP SERVER Command Use
is specified for never-linked, non associative servers that follow Guardian OPEN/CLOSE logic, the WAIT time allows the servers to do the cleanup. If WAIT time is 0 secs, all the servers stop immediately. In case of duplicate STOP SERVER commands specified for the same server class with a different WAIT time, the never-linked, non associative servers of the specified server-class, will stop at the earliest timeout among the specified WAIT values.
Considerations • After the PATHMON process thaws a server class, the PATHMON process allows Pathsend requestors access to the thawed server classes. For SCREEN COBOL requestors without an ON ERROR clause, the TCP resumes the operation by executing the send request. (When SCREEN COBOL requestors containing an ON ERROR clause encounter a frozen server class, they perform as directed by the ON ERROR code.
Example 32 Wild card support using * in the SERVER object name STATUS SERVER EXM* The above command displays the status of all server classes defined for the PATHWAY environment whose name starts with "EXM": SERVER #RUNNING EXMP1 1 EXMP2 1 EXMP3 1 EXMP4 1 EXMPA 1 EXMPB 1 ERROR INFO NOTE: Only one instance of the wildcard character ("*") is accepted. If two or more asterisks are used, "illegal syntax" error appears. Therefore, for example, A*BD, AB*D or ABD* is supported.
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.
*1049* TERM SUSPENDED Operating System Error Numbers Some PATHMON environment messages include an operating system error number. Although the error number is typically identified as a file-system error, it might also represent a sequential I/O (SIO) error or other specialized error. SCREEN COBOL Errors When an error originates in the SCREEN COBOL program, use the STATUS TERM, DETAIL command to obtain the name, version, and instruction address of the program unit being executed.
1006 *1006* PATHMON, ABENDED Cause. The PATHMON process aborted due to a fatal error. Effect. The PATHMON process cannot process requests or monitor or control the PATHMON environment. Recovery. Determine why the PATHMON process abended by checking the NonStop Kernel errors in messages logged just before this message, and then restart the PATHMON environment.
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. 1011 *1011* link manager-name, DELINK FAILURE : < nested-message > Cause. An error occurred while a TCP or LINKMON process was trying to return a link to a server class.
If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. 1014 *1014* ENTRY IN USE (LOCKED) Cause. The named object entry was locked (for example, during a state change) and the request timed out before the entry was unlocked. Effect. The request fails. Recovery. Reissue the request when the named object entry is no longer locked.
1019 *1019* link manager-name, PATHMON -> TCP FILE ERROR (errnum) Cause. A file-system error (errnum) occurred during an I/O operation to the specified TCP or LINKMON process. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 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.
1024 *1024* object-name, ILLEGAL FILE NAME (errnum) Cause. An invalid file name was detected in the definition of the specified object. The 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. Correct all invalid file names in the definition of object-name.
1027 *1027* PATHMON, LOG1 FILE CLOSED Cause. The LOG1 file is closed. Effect. None Recovery. Informational message only; no corrective action is needed. 1028 *1028* PATHMON, LOG1 FILE OPENED Cause. The LOG1 file is open. Effect. None Recovery. Informational message only; no corrective action is needed. 1029 *1029* PATHMON, LOG2 FILE CLOSED Cause. The LOG2 file is closed. Effect. None Recovery. Informational message only; no corrective action is needed. 1030 *1030* PATHMON, LOG2 FILE OPENED Cause.
Effect. Entries cannot be added until the configuration file is available. Recovery.
Recovery. Use an ALTER command to correct the system name in the object definition. 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.
Cause. An error occurred during request initiation. Effect. The request fails. Recovery. For additional information, see the description associated with the nested message. 1042 *1042* TERM term-name, RESUMED Cause. The indicated terminal has resumed processing. Effect. None Recovery. Informational message only; no corrective action is needed. 1043 *1043* object-name, STARTED Cause. The specified object has started. Effect. None Recovery. Informational message only; no corrective action is needed.
1048 *1048* TERM term-name, SUSPENDED : < nested-message > Cause. The specified terminal suspended processing due to an error in the program. The reason for the error is indicated in the nested message. Effect. The terminal remains suspended until it is aborted with the ABORT TERM command. Recovery. For additional information, see the description associated with the nested message. 1049 *1049* TERM term-name, SUSPENDED : < nested-message > Cause.
1053 *1053* TCP NOT RUNNING Cause. The TCP specified in a TERM definition is not running. Effect. The operation fails. Recovery. Determine why the TCP is not running. After correcting the problem, start the TCP with the START TCP command. 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.
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 is accepted and will complete when all link managers pass a message to the PATHMON process that the server class is frozen. Effect. None Recovery. Informational message only; no corrective action is needed. 1060 *1060* NOT FROZEN Cause.
Recovery. Reissue the command after the server class is thawed. 1064 *1064* SERVER server-name, FROZEN Cause. The specified server class is frozen. Effect. None Recovery. Informational message only; no corrective action is needed. 1065 *1065* SERVER server-name, THAWED Cause. The specified server class is thawed. Effect. None Recovery. Informational message only; no corrective action is needed. 1066 *1066* TERMINALS NOT CONFIGURED TO RECEIVE TELL MESSAGES Cause.
Cause. A PATHMON process dump was taken by operator request or because the PATHMON DUMP attribute was d at the time an internal error occurred. Effect. Memory is written to the named dump file. Recovery. If the dump was taken by operator request, this message is informational only; no corrective action is needed.
Effect. The PATHMON process stops the backup process, if it is running, and attempts to start a new backup process. 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 the backup process. The nested message indicates the reason. Effect. The PATHMON process runs without a backup. Recovery.
Cause. A PATHMON process internal-consistency check failed. This is an internal error. Effect. The PATHMON process terminates. If the DUMP attribute is d, the PATHMON process creates a dump file before terminating. Recovery.
1081 *1081* PATHCTL FILE IS INCOMPATIBLE (COLD START REQUIRED) Cause. During a cool start, the PATHMON configuration file was not compatible with the currently running PATHMON process. This incompatibility can result from these either the PATHMON configuration file is a pre-D30 version of the file (which is not compatible with D30 versions of the PATHMON process), or the PATHMON configuration file has an invalid file code (the valid file code is 310). Effect. The cool start fails. Recovery.
Cause. The terminal running the program was aborted by the ABORT TERM command. Effect. The terminal 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 operation is aborted. Recovery. Check the PATHMON process log file for the Pathway and Guardian error encountered.
Recovery.
Recovery. Increase the value of the MAXSERVERCLASSES attribute, and then reissue the ADD SERVER or ALTER SERVER command. 1103 *1103* SERVER server-class, TOO MANY SERVER PROCESS ENTRIES Cause. The number of server process definitions has reached the maximum value specified for the MAXSERVERPROCESSES attribute of the SET PATHWAY command. Effect. The ADD SERVER or ALTER SERVER command fails. Recovery. Increase the value of the MAXSERVERPROCESSES attribute and reissue the ADD SERVER or ALTER SERVER command.
Cause. The number of tell messages issued has reached the maximum specified for the MAXTELLS attribute of the SET PATHWAY command, or the value defined for the MAXTELLS attribute is too large. Effect. The tell message requests fail. 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.
Cause. The PATHMON process cannot send checkpoint information to the 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. The TCP has read the requested program unit code segment into memory after checking the SCREEN COBOL object directory file. Effect. The TCP uses the latest version of each program unit. Recovery.
Effect. The terminal abends. Recovery. Informational message only; no corrective action is needed. 1120 *1120* object-name, AUTORESTARTED Cause. After a failure, AUTORESTART restarted the specified object. Effect. None Recovery. Informational message only; no corrective action is needed. 1121 *1121* object-name, AUTORESTART DISABLED Cause. The specified object reached the AUTORESTART limit configured for it. Effect. The object is not restarted. Recovery.
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. 1124 *1124* PATHMON, ALLOCATESEGMENT ERROR (errnum) Cause. An error occurred, identified by the error number, on a call to the ALLOCATESEGMENT procedure. Effect. The PATHMON process is unable to allocate an extended data segment. The PATHMON process terminates. Recovery.
Cause. The Event Management Service (EMS) facility is not available. The PATHMON process cannot handle requests from processes calling EMS procedures. 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.
Cause. You started the PATHMON process specifying DEFINEs other than the _DEFAULTS DEFINE with the VOLUME attribute. Effect. PATHMON ignores any DEFINEs other than the _DEFAULTS DEFINE with the VOLUME attribute. Recovery. Specify a DEFINE message using the SET SERVER DEFINE command. 1141 *1141* SERVER server-name, DEFINE PROCEDURE ERROR (DEFINE-errnum) Cause. An error occurred, identified by the error number, in a procedure call to the DEFINE procedure library (for example, to DEFINERESTORE). Effect.
Effect. The processing of DEFINE statements is disabled, making it impossible to add a DEFINE definition to a server class. Recovery. Install a version of the NonStop operating system that supports DEFINESAVE and DEFINERESTORE—that is, version C10 or later. 1145 *1145* PROGRAM program-name, ILLEGAL TERM NAME term-name Cause. A RUN PROGRAM command specified an invalid name for a terminal (for example, a name with more than seven characters). Effect. The RUN PROGRAM command fails. Recovery.
and TERM objects cannot be configured. No server process can be started whose name is not configured by the user. Recovery.
1154 *1154* SHUTDOWN REQUEST TIMED OUT Cause. The shutdown operation has not completed, but the time specified by the TIMEOUT attribute has expired. Effect. None Recovery. Informational error message; no corrective action is needed. 1155 *1155* SHUTDOWN FAILED Cause. An object in the PATHMON environment, such as a server class, could not be stopped. Effect. The shutdown fails. Recovery. Stop the object using the TACL STOP command and retry the shutdown.
Effect. The PATHMON process cannot process requests or monitor or control the PATHMON environment. Recovery. Determine why the PATHMON process abended by checking the Guardian errors in messages logged just before this message, and then restart the PATHMON environment.
1162 *1162* RESIZESEGMENT ERROR (errnum) Cause. A error occurred during a call to the Guardian RESIZESEGEMENT or CHECKRESIZESEGMENT procedure. Effect. The command fails. 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.
Cause. The maximum number of ACS subsystem process, TCP, and external TCP processes has exceeded the total number of link managers allowed (currently 800). Effect. The bad value (MAXEXTERNALCPS, MAXLINKMONS or MAXTCPS) is rejected and the SET PATHWAY command fails. Recovery. Re-enter the values of MAXEXTERNALCPS, MAXLINKMONS and MAXTCPS, after ensuring that their sum does not exceed the value of the maximum link managers allowed (currently 800). 1166 *1166* AUDIT MSG Cause.
Recovery. As the SPREBALANCEMODE is not MANUAL, this command is not required. If the SPREBALANCEMODE is DISABLE, and then rebalancing cannot happen. If the SPREBALANCEMODE is AUTO, and then the rebalancing happens automatically. Manual intervention is not required.
14 PDMCOM Messages (Numbers 1500-1999) This section describes the messages generated by the PDMCOM process.
Cause. FC command was the first command to be issued at the PDMCOM prompt. Effect. The command fails. Recovery. Issue the FC command only if a previous command-line exists. 1503 *1503* Command String Not Found Cause. The string entered with the FC command does not match any prior command. Effect. The command fails. Recovery. Specify a valid string with the FC command and issue the command again. 1504 *1504* Invalid command number Cause. FC command was issued with an invalid command number. Effect.
Cause. The PDMHELP help file is not found at the location where PDMCOM resides Effect. HELP command, issued to receive help on the PDMCOM commands or the PDMCOM error numbers, fails. Recovery. Place the PDMHELP help file at the location where PDMCOM resides. If the file is missing from the system, then reinstall the product. 1508 *1508* No help available Cause. Help could not be made available at this time. Effect.
Effect. The command is aborted. Recovery. Determine the reason for failure and initiate the corrective action accordingly. If the error is displayed during execution of an ALTER-DOMAIN command, then check the configuration of the server throughout the domain. Any inconsistency must be corrected manually. 1513 *1513* INTERNAL ERROR - . Cause. Some unexpected error occurred. Effect. The command is aborted. Recovery. Take appropriate action depending on the error message.
Cause. The specified domain name does not exist. Effect. The domain is not opened. Recovery. Specify the correct domain name, and then 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. Internal request of the ALTER-DOMAIN command to execute the queued Pathsend requests failed.
1523 *1523* DOMAIN ALREADY PARTITIONED FOR SERVER. Cause. The CONTROL DOMAIN PARTITION command was issued for a domain-server combination, which was already partitioned. Effect. The command is rejected. Recovery. Issue the CONTROL DOMAIN UNDO PARTITION command, and then reissue the command. 1524 *1524* DOMAIN NOT PARTITIONED FOR SERVER. Cause. The CONTROL DOMAIN UNDO PARTITION command was issued for a domain-server combination, which was not partitioned. Effect. The command is rejected. Recovery.
Cause. PDMCOM failed to read an OBEY file. Effect. The command fails. Recovery. The OBEY file might be corrupt. Create a new OBEY file and reissue the command. If the problem persists, contact your HP NonStop representative. 1529 *1529* FC COMMAND IS INVALID IN AN OBEY FILE. Cause. The FC command is issued in an OBEY file. 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.
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.
2003 *2003* PATHMON NOT OPEN Cause. The PATHMON process is not open. Effect. The request to the PATHMON process fails. Recovery. Use the PATHCOM OPEN command with the PATHMON process name. 2007 *2007* SERVER server-name FROZEN Cause. The indicated server class is frozen. Effect. None Recovery. Informational message only; no corrective action is needed. 2008 *2008* ILLEGAL ATTRIBUTE VALUE Cause. The value specified for an attribute is not within the valid range. Effect. The command fails. Recovery.
Recovery. Enter a valid number. 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 syntax for the newly introduced or modified command is incorrect. Effect. The command fails. Recovery. Enter the input characters using the correct syntax. 2014 *2014* ILLEGAL TIME VALUE Cause. The time value entered cannot be represented in 16 bits. Effect.
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. • Running a program on terminals with non-network names. Terminal names used in a PATHMON environment cannot exceed seven characters including the $ symbol. Effect. The reply fails. Recovery.
Recovery. Enter a correct object name and resubmit the command. 2021 *2021* PATHCOM OPERATOR INPUT NEEDED IN NON-INTERACTIVE MODE Cause. A response is needed but PATHCOM is running noninteractively. This message is equivalent to the interactive DO YOU WISH TO CONTINUE? prompt. Effect. Because PATHCOM is in noninteractive mode, the process terminates. Recovery. Enter the required response. 2022 *2022* TERM term-name RESUMED Cause. The named terminal has resumed operation. Effect. None Recovery.
Cause. The named terminal is suspended. Effect. None 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.
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. The number of processor pairs exceeded the maximum number of 16. Effect. The command fails. Recovery. Specify 16 or less processor pairs. 2037 *2037* NUMBER OF PREDEFINED SERVERS WOULD EXCEED MAXSERVERS Cause.
Effect. PATHCOM fails. Recovery. Contact your Global Customer Support Center (GCSC). Before contacting the GCSC, have the following information available: • Log files and dump files • Your PATHMON configuration file and PATHMON process version • A description of the application task that was in progress when the error was encountered This information is invaluable for the support staff to be able to understand the problem and help fix the problem. 2041 *2041* PATHWAY MICROCODE NOT INSTALLED Cause.
Recovery. Enter a correct value for the LINKDEPTH attribute. 2047 *2047* RUN PERMITTED ONLY FOR IN = OUT = TERMINAL Cause. A RUN command is allowed in interactive mode only. Effect. The command fails. Recovery. Re-enter 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.
2054 *2054* TCP tcp-name PRIMARIED Cause. The primary process is running in the 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. A RUN PROGRAM command was issued with the NOWAIT option but the FILE attribute was not specified; or NOWAIT was specified, but the name of the PATHCOM command terminal was entered for the FILE attribute.
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. The operation fails. Recovery. For information concerning the specified DEFINE error, see the Guardian Procedure Errors and Messages Manual. 2060 *2060* SAVED DEFINE LENGTH EXCEEDS PATHCOM LIMIT Cause. The size of the DEFINE definition being added to a server class exceeds the PATHMON process internal limit. Effect.
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.
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. 2070 *2070* THE COMBINED LENGTH OF ARGLIST AND ENV IS GREATER THAN IS ALLOWED Cause. The combined length of the values defined for the server class attributes ARGLIST and ENV exceed the 24,000-character maximum. Effect. Whichever attribute was specified last, ARGLIST or ENV, is not set. Recovery.
2075 *2075* CMDVOL NODE VALUE CONFLICTS WITH PATHWAY NODEINDEPENDENT ON Cause. The SET PATHWAY NODEINDEPENDENT attribute is set to ON, but a value other than \* was specified by the CMDVOL command as the node name in the default settings for file name expansion. Effect. The \* node name specification conflicts with the NODEINDEPENDENT attribute setting. Recovery. Perform one of these: • SET PATHWAY NODEINDEPENDENT to OFF and cold start the PATHWAY object.
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.
3117 *3117* link manager-name, SERVER CLASS UNDEFINED Cause. The server class specified in a Pathsend statement is not defined for the PATHMON environment. Effect. The operation fails. Recovery. Isolate and correct the problem within the requestor program. See the TS/MP 2.5 Pathsend and Server Programming Manual. 3118 *3118* link manager-name, REQUEST INVALID FOR SERVER STATE Cause. The state of the specified server does not allow the requested operation to occur. This is an internal error. Effect.
3201 *3201* link manager-name, SYNCID VIOLATION IN MESSAGE RECEIVED BY TCP Cause. A LINKMON process (or TCP) received an invalid message synchronous ID (SYNCID). This is an internal error. Effect. The request cannot be processed. 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.
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).
Recovery. Informational message only; no corrective action is needed. LINKMON cannot be run Cause. You attempted to start a LINKMON process with a RUN command. Effect. The LINKMON process terminates processing. Recovery. There is no way to recover from this error condition; you cannot start a LINKMON process with a RUN command. SEGMENT_ALLOCATE_ error error-number [ (error detail error-detail) ] on swap file swap-file-name Cause.
SERVERCLASS_SEND_ call in this processor causes the LINKMON process to reattempt initialization; after the condition is corrected, the LINKMON process can complete initialization.
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. 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.
• Token descriptions • Effect and recovery information The syntax box contains the text version of the event message, which is available through the EMSTEXT procedure. When you use the EMSTEXT procedure to get the text version of an event message, you request either the display format or the console compatible format, as described in the EMS Manual. For the ACS subsystem event messages, both the versions are identical.
Definition ZACL-DDL-EVENT-LEVEL Type Enum Tacl Enum Begin 89 ZACL-VAL-EVENT-LEVEL-INFO Value 0 As "INFO". 89 ZACL-VAL-EVENT-LEVEL-STATUS Value 1 As "STATUS". 89 ZACL-VAL-EVENT-LEVEL-WARNING Value 2 As "WARNING". 89 ZACL-VAL-EVENT-LEVEL-ERROR Value 3 As "ERROR". 89 ZACL-VAL-EVENT-LEVEL-FATAL Value 4 As "FATAL". End Token -Type ZACL-TYP-EVENT-LEVEL Value is ZSPI-TDT-ENUM Def is ZACL-DDL-EVENT-LEVEL. nl ZACL-VAL-EVENT-LEVEL-INFO The ACS subsystem does not generate info events.
Event Message Text 1001 - Backup process created in CPU cpu-number Token Descriptions ZACL-TKN-EVENT-LEVEL has the value ZACL-VAL-EVENT-LEVEL-STATUS. ZACL-TKN-EVENT-CPU-NUMBER contains the number of the CPU on the local system in which the backup domain coordinator process was started. This token is the subject of the event message. Effect. The backup domain coordinator process runs in the indicated CPU. Recovery. This is an informational message only; no corrective action is needed.
1003: ZACL-EVT-BACKUP-ABENDED The backup domain coordinator process terminated unexpectedly. ] Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. Conditional Tokens ZACL-TKN-EVENT-TERM-STOPPER token-type ZSPI-TYP-PHANDLE. ZACL-TKN-EVENT-TERM-SSID token-type ZSPI-TYP-SSID. ZACL-TKN-EVENT-TERM-TEXT token-type ZSPI-TYP-STRING.
1004: ZACL-EVT-CP-LAUNCH-ERROR Either the domain coordinator process cannot create an ACS subsystem process in the specified CPU on the local system because the PROCESS_LAUNCH_() operation failed or the ACS subsystem process was created but the PROCESS_LAUNCH_() operation returned a warning.] Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-PROCESS-NAME ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT.
1005: ZACL-EVT-CP-ABENDED An ACS subsystem process terminated unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. ZACL-TKN-EVENT-ERROR-DETAIL token-type ZSPI-TYP-INT. Conditional Tokens ZACL-TKN-EVENT-TERM-STOPPER token-type ZSPI-TYP-SSID. ZACL-TKN-EVENT-TERM-SSID token-type ZSPI-TYP-PHANDLE.
Effect. The ACS subsystem process is not available in the indicated CPU; other ACS subsystem processes continue to run on the CPU. Recovery. Correct the condition that caused the file error, and retry the operation. 1006: ZACL-EVT-FILE-ERROR An ACS subsystem process invoked a Guardian file-system procedure on an open or named file and the operation failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING.
1007: ZACL-EVT-OSS-ERROR An ACS subsystem process invoked an OSS procedure and the operation failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-OSS-ERRNO token-type ZSPI-TYP-INT2. Conditional Token ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING.
Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-ERROR. ZACL-TKN-EVENT-PROCEDURE contains the name of the Guardian process management procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the ACS subsystem process associated with the failure. ZACL-TKN-EVENT-ERROR-CODE contains the name of the ACS subsystem process associated with the failure.
ZACL-TKN-EVENT-ERROR-CODE contains the Pathsend error code returned by the failed operation. ZACL-TKN-EVENT-ERROR-DETAIL contains the file-system error code returned by the failed operation. If the value of this token is zero in an event message, the token is null and is omitted from the message. ZACL-TKN-EVENT-SERVER-NAME contains the PATHMON process name and server class name supplied to the failed operation, separated by a period.
Effect. The process that invoked the failed operation terminates abnormally and produces a SaveAbend file. Recovery. If the failure was due to a file-system error or system-resource limit, correct the condition and use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the failure occurred. If this is an internal error; contact your HP analyst. 1011: ZACL-EVT-SEGMENT-CORRUPT An ACS subsystem process detected corruption in the ACS subsystem shared memory segment in the CPU.
ZACL-TKN-EVENT-PROCEDURE contains the name of the Guardian binary semaphore 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 protected by the semaphore that was being accessed by the failed operation. ZACL-TKN-EVENT-ERROR-CODE contains the Guardian or OSS error code returned by the failed operation. Effect.
Event-Message Text 1015 - Memory pool operation procedure() failed, segment segment-id, error errnum 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.
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. 1017: ZACL-EVT-UNAUTH-REQUESTOR An unauthorized process attempted to open an ACS subsystem process.
1018: ZACL-EVT-INVALID-RQST-MSG An ACS subsystem process received an invalid request message. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCESS-ID token-type ZSPI-TYP-PHANDLE. Event-Message Text 1018 - Invalid request message received from process process-id Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-ID contains the process handle of the requestor process that sent the invalid request message.
Effect. The request message is ignored. A reply containing an FEINVALOP (2) error is returned to the requestor process. Recovery. This event indicates that incompatible versions of ACS components are installed on different systems in the same domain. 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 token-type ZACL-TYP-EVENT-LEVEL.
ZACL-TKN-EVENT-PROCESS-ID contains the process handle of the process that committed the protocol error. This token is the subject of the event message. Effect. The operation in which the protocol error occurred is aborted. Recovery. Contact your HP support analyst. 1022: ZACL-EVT-PATHMON-IO-TIMEOUT An I/O operation from an ACS subsystem process to a PATHMON process timed out. ACS subsystem processes use a timeout value of 5 minutes for an I/O to a PATHMON process.
Token Descriptions ZACL-TKN-EVENT-LEVEL has either the value ZACL-VAL-EVENT-LEVEL-WARNING or ZACL-VAL-EVENTLEVEL- ERROR. 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 file-system error FEOK. Recovery. Retry the send operation. If the problem persists, check the PATHMON process. You must shut down and restart your application.
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. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the PATHMON process.
1027: ZACL-EVT-PATHMON-EXT-SHUTDOWN A PATHMON process sent a PATHMONSHUTDOWN request to the ACS subsystem. This condition typically occurs in response to a TS/MP SHUTDOWN command. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. Event-Message Text 1027 - PATHMON process-name was externally shut down Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
1029: ZACL-EVT-CPU-STARTED The ACS subsystem processes in the specified CPU were started in response to a START command or were restarted in response to a CONTROL command. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. Event-Message Text 1029 - Core processes started in CPU cpu-number Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-STATUS.
Recovery. Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU. 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 token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING.
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. This token is the subject of the event message. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 1033: ZACL-EVT-LOG1-CLOSED The LOG1 event log file was closed either in response to an operator command or because an error occurred while writing to the log file.
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. This token is the subject of the event message. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 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.
Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING. 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 requestor program or start the named PATHMON process.
ZACL-TKN-EVENT-PROCEDURE token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-PROCESS-ID token-type ZSPI-TYP-PHANDLE. ZACL-TKN-EVENT-FILE-NAME token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. Event-Message Text 1038 - Server pathmon-name.serverclass-name file operation procedure() failed, process process-id, file file-name, error errnum Token Descriptions ZACL-TKN-EVENT-LEVEL has one of the values ZACL-VAL-EVENT-LEVEL-WARNING or ZACL-VALEVENT- LEVEL-ERROR.
EMS Messages 1040 through 1049 1042: ZACL-EVT-SERVER-UNAUTH-MSG A Pathsend requestor process attempted to perform a Pathsend operation on a server class that the process is not authorized to communicate with. Authority to communicate with a Pathway server class is determined by the OWNER and SECURITY configuration attributes of the server class. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-SERVER-NAME token-type ZSPI-TYP-STRING.
Event-Message Text 1062 - ( process-name): No backup CPU available 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 domain coordinator process followed by the CPU and PIN enclosed in parentheses. This token is the subject of the event message. Effect. The domain coordinator process runs as a single process. Recovery.
Event-Message Text 1064 - ACS reserved process name process-name is in use. Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-ERROR. 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.
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 token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT. Event-Message Text 1066 - Invalid backup CPU cpu-number - CPU needs to be d Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
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. Contact HP support to install the ACS program files in $SYSTEM.SYSnn. 1068: ZACL-EVT-INVALID-HOMETERM The home terminal is no longer valid and cannot be used to create a backup domain coordinator process or other ACS subsystem process. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL.
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. Primary process terminates and the backup process takes over. Recovery. Informational message only; no corrective action is needed. EMS Messages 1070 through 1071 1070: ZACL-EVT-PROCESS-SWITCH-FAILED The process pair cannot switch because no backup process is running.
ZACL-TKN-EVENT-TERM-TEXT token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-ERROR-DETAIL token-type ZSPI-TYP-INT. Event-Message Text 1071 - Primary process in CPU cpu-number terminated abnormally, comp-code comp-code, stopper stopper-id, termssid term-ssid, term-info term-info, term-text term-text Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
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.5 follows the same syntax as PATHCOM commands. For more information on PDMCOM Commands, see the TS/MP 2.5 Release Supplement.
FREEZE { [ SERVER ] server-class } { [ SERVER ] (server-class [, server-class ]...) } { SERVER * } [ ! ] [ , WAIT ] HELP [ / OUT list-file / ] [ [ [ [ [ ALL COMMANDS command-name “detail-name” error-num ] ] ] ] ] HISTORY [ number ] INFO [ / OUT list-file / ] PATHMON [ , OBEYFORM ] INFO [ / OUT list-file / ] PATHWAY [ , OBEYFORM ] INFO [ / OUT list-file / ] { [ SERVER ] server-class } { [ SERVER ] ( server-class [ , server-class ] ...
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 ]...
MAXSPI number MAXTELLQUEUE number MAXTELLS number MAXTMFRESTARTS number NODEINDEPENDENT [ON | OFF] OWNER ownerid SECURITY security-attribute SPREBALANCEMODE rbmodeval NOTE: Among the attributes in the SET PATHWAY command are some attributes that apply only to the Pathway/iTS product: MAXTCPS, MAXTERMS, MAXEXTERNALTCPS, MAXPROGRAMS, MAXTELLQUEUE, MAXTELLS, and MAXTMFRESTARTS.
[ [ file-name ] , create-spec ...
STATUS [ / OUT list-file / ] { [ LINKMON ] L\node.$process-name } { LINKMON * } STATUS [ / OUT list-file / ] PATHMON STATUS [ / OUT list-file / ] PATHWAY [ , COUNT number ] [ , INTERVAL number { HRS | MINS | SECS } ] STATUS [ / OUT list-file / ] { [ SERVER ] name [ , PROCESS $process-name ] { [ SERVER ] name [ , PROCESSES ] { [ SERVER ] name [ , DETAIL ] { [ SERVER ] name [ , FREEZE ] { [ SERVER ] ( name [ , name ]... ) [ , PROCESSES ] { [ SERVER ] ( name [ , name ]...
B PATHCOM Reserved Words This appendix contains a list of words that are reserved and cannot 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.5 follow the same syntax as PATHCOM commands. For more information on PDMCOM Commands, see the TS/MP 2.5 Release Supplement.
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 OWNER MAXASSIGNS PARAM MAXDEFINES PARTITION 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 UMASK RESET UN
SHUTDOWN2 SPREBALANCECPU SPREBALANCEMODE START nl nl STARTUP STATS STATUS STDERR STDIN STDOUT STOP 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 MAXINPUT
C Configuration Limits and Defaults Table 13 (page 318) lists global limits for various items within each Pathway environment. NOTE: These limits are subject to change with product SPRs or with new software releases. For information on TS/MP 2.5 limits, see the TS/MP 2.5 Release Supplement. Table 13 Global Pathway Environment Limits Item Limits Per Pathway Environment ASSIGNs 8191 for all server classes.
alphabetically, by PATHCOM parameter. These limits and defaults are subject to change with product SPRs or with new software releases. SPI tokens and fields are used in the management programming interface to Pathway environments. For more information on this interface, see the TS/MP 2.5 Management Programming Manual.
Table 14 Limits and Defaults for Parameters (continued) PATHCOM Parameter* SPI Token/Field** ERRORS N.A Value Limits and Defaults Values: -1 Allow infinite number of errors. 0 Stop after encountering first error. 132,767 Number of errors and warnings to be ignored. EVENTFORMAT EXT FILE ZEVENTFORMAT ZEXTENTSIZE ZFILE GUARDIAN-SWAP HELP HIGHPIN N.A. ZHIGHPIN Default: 0 Values: EVENTFORMAT Default: Only text (console) messages are generated.
Table 14 Limits and Defaults for Parameters (continued) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXLINKS Values: ZMAXLINKS 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.
Table 14 Limits and Defaults for Parameters (continued) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults Recommended value if Pathway/iTS is not installed at your site: 0.
Table 14 Limits and Defaults for Parameters (continued) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults PRI Values: ZPRIORITY 1 through 199 Default (the The priority assigned by $CMON, or if $CMON is not PATHMON active, the priority of TACL minus 1. process): Default (SERVER): 10 less than the priority of the PATHMON process. Default 20 less than the priority of the PATHMON process.
Table 14 Limits and Defaults for Parameters (continued) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults Must not exceed 1024 bytes. TIMEOUT ZTIMEOUT Default: None Values: 0 through 16,383 SECS, or 0 through 1092 MINS, or 0 through 18 HRS Default The LINKMON process waits indefinitely for server I/O (LINKMON): operation to complete unless the send times out during the I/O because of the timeout value specified in the SERVERCLASS_SEND_ call.
D Migration Information This appendix covers migration and compatibility issues for the NonStop TS/MP product on C-series and D-series systems. These topics are discussed: • Interprocess communication issues • Application conversion For information on migration and compatibility issues relative to the Pathway/iTS product, see the Pathway/iTS System Management Manual. For more information about running applications on HP NonStop systems, see the Guardian Application Conversion Guide.
Table 15 NonStop TS/MP Process High-PIN and Low-PIN Support (continued) Operation PATHMON PATHCOM LINKMON Service high-PIN requestors Yes, when requestors are named N.A. Yes Open a high-PIN process Yes Yes Yes Create a high-PIN process Yes N.A. N.A. Can be created by a high-PIN process Yes Yes N.A. By default, PATHCOM runs at a high PIN. By default, the PATHMON process runs at a high PIN.
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 requestor that is communicating with s
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. $RECEIVE A special Guardian file name through which a process receives and optionally replies to messages from other processes by using Guardian procedure calls. This file is analogous to a request queue defined for a NonStop TUXEDO server.
availability The amount of time an application running on a Tandem system can be used effectively by a user of that application. backup process The member of a process pair that takes over the application work when the primary process fails. See also primary process, process pair, and checkpoint message. base screen In SCREEN COBOL, a screen that occupies the entire physical display area of a terminal and can be displayed independently of other screens.
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. See also reduced instruction-set computing (RISC).
DBCS See double-byte character set (DBCS). DDL See Data Definition Language (DDL). deadlock 1. 2. A situation in which two processes cannot proceed because each is waiting for a reply from the other. A situation in which two transactions cannot proceed because each is waiting for the other to release a lock.
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. dynamic server A server process that the PATHMON process creates after a TCP or ACS subsystem process has waited for a specified time period for a static server to become available. A dynamic server process exists only as long as it is needed. See also static server.
provide a connection between the opening process and the file. See also fully qualified file name, partially qualified file name, OSS filename, and OSS pathname. file system 1. 2. In the Guardian environment, the application program interface for communication between a process and a file. A file can be a disk file, a device other than a disk, or another process. In the OSS environment, a collection of files and file attributes.
intelligent device support (IDS) facility A feature of the TCP that supports access to Pathway server classes by intelligent devices. This facility allows SCREEN COBOL requestor programs to interact with external processes that, in turn, control devices such as personal computers, automated teller machines, and point-of-sale devices. intelligent mode An operating mode in which data and messages are sent between an intelligent device and the Pathway environment.
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 Section A section in the Data Division of a SCREEN COBOL source program that describes the data type, size, and relative position (sequence) of each field in a message template.
TM/MP that provides these features is the TMF subsystem. See also Transaction Management Facility (TMF) subsystem. NonStop Transaction Services/MP (NonStop TS/MP) A Tandem product that provides process management and link management functions for OLTP applications on Tandem NonStop systems. NonStop TS/MP consists of the PATHMON process, the ACS subsystem process, the PATHCOM process and interface, and the Pathsend procedures.
processing can be used for many different kinds of business tasks such as order processing, inventory control, accounting functions, and banking operations. See also batch processing. online transaction processing (OLTP) application A set of programs that perform online transaction processing (OLTP) tasks on behalf of the user. With an OLTP application, many terminal users can update data simultaneously, recording the changes in the database as they are entered.
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 ACS subsystem processes; and performs all process control (starting, monitoring, restarting, and stopping) of server processes and TCPs. PATHMON-controlled object An object defined and managed by a PATHMON process, through PATHCOM or the Pathway management programming interface.
Pathway server A server process or program in the Pathway transaction processing environment. See also NonStop TUXEDO server and PTP server. Pathway subsystem The PATHMON environment components to which SPI commands are sent under the Pathway subsystem ID and which generate EMS event messages with the Pathway subsystem ID. All SPI commands for the Pathway subsystem are sent to the PATHMON process, but the processsing for the command might involve other processes, such as a TCP.
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.
COBOL or Pathsend requestor. This header indicates whether the request was processed successfully and whether the reply contains data returned by the application service. See also request translation header. request message The part of an interprocess communication message that is formatted by a requestor 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.
are two types of screen: base screens and overlay screens. See also base screen, overlay screen, and screen description entry. SCREEN COBOL A procedural language developed by Tandem and based on COBOL that is used to define and control screen displays on terminals and other input/output devices. SCREEN COBOL allows programmers to write requestor programs that communicate with operator terminals and intelligent input/output devices, and that send data to server processes that manage application databases.
special register A data item defined by the SCREEN COBOL compiler, rather than explicitly in the program. Each special register has a particular purpose and must be used only as defined. The SCREEN COBOL language defines a different set of special registers from those defined by the standard COBOL language. SPI See Subsystem Programmatic Interface (SPI). static server A server process that the PATHMON process creates when a START SERVER command is issued.
Tandem NonStop Series/RISC (TNS/R) Tandem computers that support the Tandem NonStop Kernel and that are based on reduced instruction-set computing (RISC) technology. TNS/R processors implement the RISC instruction set and are upwardly compatible with the TNS system-level architecture. See also reduced instruction-set computing (RISC) and Tandem NonStop Series (TNS).
tokens in an SPI buffer by calling the SSPUT procedure and retrieve them from the buffer by using the SSGET procedure. transaction An operation or a series of operations that retrieves and updates information to reflect an exchange of goods or services. In the process of retrieving and updating information, a transaction transforms a database from one consistent state to another.
user conversion procedure A procedure that lets users make their own validation checks or conversions of data passed between a SCREEN COBOL program and a terminal screen or intelligent device. ViewPoint application An extensible interactive application for managing operations in the Guardian environment. It provides tools for interacting with multiple Tandem subsystems, including PATHCOM, allowing a system manager to easily control an integrated Tandem system from one location.
Index Symbols ! (Exclamation point) See Exclamation point, 43 ! parameter FREEZE SERVER command, 180 SHUTDOWN command, 165 START PATHWAY command, 168 $SYSTEM.SYSTEM.
Cancelling PATHCOM commands, 130 Characters inserting and deleting, 141 Client-server computing, 25 CLOSE message, 208 CMDCWD command, 56, 137 CMDCWD parameter, 147 CMDVOL command, 138 CMDVOL parameter, SHOW command, 147 COLD attribute, 168 COLD start option in command files, 98 starting PATHMON environment with, 42 Command files and TACL routines, 39 building a new cold start file, 155 creating with INFO, OBEYFORM, 97 expanding file names, 145 IN command for, 39 OBEY command for, 39 PATHMON startup command
DELETE SERVER command, 180 DELETEDELAY attribute, 62 for Server classes, 63, 69 relation to dynamic server processes, 62, 63 Deleting PROGRAM objects, 95 SERVER objects, 95 TCPs, 95 TERM objects, 95 Deleting characters, 141 DETAIL parameter STATUS SERVER command, 204 Devices, 26 Diagnosing problems, data to collect for, 103, 104 Disk file names, 131 Disk space for configuration file, 40 for PATHMON configuration information, 34 Displaying configuration information, 81, 84 object attributes, 60 statistics co
H HELP command, 38, 142, 144 HIGHPIN attribute SET SERVER command, 191 HISTORY command, 144 HOMETERM attribute SET SERVER command, 191, 195 I I/O operations, requested by Pathsend processes definition of, 109 server statistics for, 120 I/O operations, requested by TERM objects, 120 IDS facility, for intelligent device support, 26 IFPRICPU attribute PRIMARY PATHMON command, 157 Illegal CPU number (message 1095), 152, 159 IMMEDIATE option, SHUTDOWN2 command, 166 IN attribute, SET SERVER command, 192 IN comma
LOG1 and LOG2 commands, 156, 157 LOG1 command, 99 LOG2 command, 99 Logging errors and events See also Log messages, Log files, and EMS, 98 M Management applications, 31, 32 Management interfaces, 29, 32 Management tools DSM set of products, 31 EMS FastStart product, 33 Measure product, 32 PATHCOM, 30 Service Provider, 33 SPI, 31 Tandem Performance Data Collector (TPDC), 32 ViewPoint product, 32 MAXASSIGNS attribute, 40, 53, 160 MAXDEFINES attribute, 161 MAXLINKMONS attribute, 53, 112, 113, 161 MAXLINKS att
states, 126 ON ERROR clause, 181 OPEN command, 146 Open Systems Services (OSS) hardware required for, 61 operating environment, 17 See also Server classes, OSS, 64 server classes configuring, 61 defined, 17, 23 memory, disk space considerations, 66 servers defining OSS directory for, 56 Optional attributes Server classes, 62 ORDERLY option, SHUTDOWN2 command, 166 Orphan processes cause of, 79 stopping, 48 Orphaned processes, 176 OSS See Open Systems Services, 56 OSS pathnames description, 131, 132 setting d
STATS SERVER, 90 STATUS PATHMON, 86 STATUS PATHWAY, 85 STATUS SERVER, 86 STOP SERVER, 78 SWITCH, 96 THAW SERVER, 78 PATHCONF files, collecting for problem diagnosis, 103 PATHCTL display field, 171 PATHCTL file See Configuration file, 34 PATHMON server names, granting, 194 SERVER restart attempts, 188 PATHMON configuration file, 34, 35, 56 PATHMON environment applications, 51 attributes for, 53 configuration limits, 318, 324 configuring across CPUs, 20 configuring and managing objects in, 27, 33 consideratio
STATUS SERVER command, 204 Process pairs, 36 Process priority, setting, 66 Processes avoiding orphans, 176 maximum concurrent, 318 switching primary and backup, 176 PROCESSES attribute, 204 PROCESSTYPE attribute, 62, 83, 84 setting, 186 Production environment, ensuring availability of , 105 PROGRAM attribute SET SERVER command, 195 PROGRAM attribute, for Server classes, 62 PROGRAM objects altering, 95 defined, 18 deleting, 95 Q Question mark (?), to show attributes that require values, 58 Queues for server
setting maximum, 160 STARTUP messages, setting maximum, 161 stopping, 78 SERVER objects ADD command, 177, 178 ALTER command, 178, 179 altering, 95 altering security for Pathsend access, 113 and SCREEN COBOL requestors, 26 collecting data about for problem diagnosis, 104 configuration limits, 318 defined, 17, 23 definition of, 23 DELETE command, 180 deleting, 95 displaying information about, 83, 90 FREEZE command, 180, 181 freezing, 78 Guardian displaying information about, 83 displaying statistics for, 90 I
STARTUP messages, for server classes, 161 Startup, cool CONTROL PATHMON command, effect of, 152 STATE display field, 170, 205 Static links, 189 Static server processes NUMSTATIC attribute, 63, 76 relation to MAXSERVERS and NUMSTATIC attributes, 62 starting, 76 stopping, 78 Statistics collected by ACS subsystem processes, 116 TCPs, 89 displaying information about, 89, 92 for SERVER objects, 90, 116 STATS command SERVER, 90 STATS SERVER command, 202, 203 STATUS attribute, 156, 166 STATUS command PATHMON, 86 P
Transaction Management Facility(TMF) frozen server class, relation to, 181 Translation server, Pathway, 23, 61 U UMASK attribute SET SERVER command, 197 UMASK parameter ALTER SERVER command, 179 INFO SERVER command, 182 RESET SERVER command, 183 SHOW SERVER command, 200 Unable to purge… (LINKMON message), 273 Unable to secure swap file… (LINKMON message), 273 UNTIL attribute, 166 V ViewPoint product, 32 VOLUME attribute, SET SERVER command, 197 Volume names, 131 VPROC, for product version, 103, 104 W WAI
