HP NonStop TS/MP Management Programming Manual Abstract This manual describes the management programming interface to the HP NonStop™ TS/MP product. It is intended for programmers writing applications that manage TS/MP.
Part Number Published 540082-005 November 2010 Document History Part Number Product Version Published 540082-001 NonStop TS/MP D42 November 2005 540082-002 NonStop TS/MP D42 October 2006 540082-003 NonStop TS/MP 2.3 May 2008 540082-004 NonStop TS/MP 2.4 July 2009 540082-005 NonStop TS/MP 2.0, 2.1, 2.3, and 2.
Legal Notices Copyright 2010 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop TS/MP Management Programming Manual Index Legal Notices Examples Figures Tables 1 What’s New in This Manual xi Manual Information xi New and Changed Information xi About This Manual xvii Purpose of This Manual xvii Who Should Read This Manual xviii What Is in This Manual xviii Related Documentation xix Notation Conventions xxii HP Encourages Your Comments xxv 1.
Contents 3. SPI Programming Considerations (continued) 3.
4. SPI and EMS Standard Definitions Contents 4. SPI and EMS Standard Definitions SPI Standard Definitions 4-1 Information Specific to the Pathway Subsystem EMS Standard Definitions 4-4 4-3 5.
5. ZPWY-DDL- Definitions (continued) Contents 5.
7. ZPWY-MAP- Definitions (continued) Contents 7.
8. Pathway Subsystem Control Commands (continued) Contents 8. Pathway Subsystem Control Commands (continued) STATUS LM 8-12 STATUS PATHWAY 8-13 STATUS PM 8-13 STATUS PMREQUESTER STOP PATHWAY 8-15 STOP PM 8-17 SWITCH PM 8-18 8-14 9.
9. Server Class Commands (continued) Contents 9. Server Class Commands (continued) STATUS SCPROCESS STOP SC 9-44 THAW SC 9-45 9-43 10.
11. PATHMON Event Messages (continued) Contents 11. PATHMON Event Messages (continued) Event-Message Text 11-3 Simple Tokens 11-3 Error Recovery 11-3 Event-Message Range 1000 Through 1999 11-4 12. PATHMON Error Messages Message Numbers 12-1 Error Presentation 12-1 Unlisted Tokens 12-2 Object Types in Error Lists 12-2 Error-Message Range 1000 Through 1999 12-2 13.
14. ACS Subsystem Messages (continued) Contents 14. ACS Subsystem Messages (continued) EMS Messages 1070 through 1072 14-44 15. SPI Error Messages Message Numbers 15-1 Error Presentation 15-2 Object Types in Error Lists 15-2 Error-Message Range 4000 Through 4999 15-3 16. Management Programming Examples Configuring Pathway 16-1 Adding or Altering a Server 16-30 Obtaining Subsystem Information 16-35 17.
Figures (continued) Contents Figures (continued) Figure 1-4. Figure 2-1. Figure 3-1. Management Programming Environment 1-8 Sending Commands and Receiving Responses Commands and Objects 3-8 2-6 Tables Table 1-1. Table 1-2. Table 2-1. Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table 3-5. Table 4-1. Table 4-2. Table 4-3. Table 4-4. Table 4-5. Table 4-6. Table 4-7. Table 4-8. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 6-1. Table 7-1. Table 7-2. Table 10-1. Table 10-2. Table 10-3.
Contents HP NonStop TS/MP Management Programming Manual—540082-005 xi
Contents HP NonStop TS/MP Management Programming Manual—540082-005 xii
What’s New in This Manual Manual Information HP NonStop TS/MP Management Programming Manual Abstract This manual describes the management programming interface to the HP NonStop™ TS/MP product. It is intended for programmers writing applications that manage TS/MP.
What’s New in This Manual ° ° Changes to the H06.19/J06.08 Manual ZREQCNT ZIOS Changes to the H06.19/J06.08 Manual • • • • Added ZPWY-DDL-CPUWT on page 5-2 and 5-10. Added ZCPUWTINFO on page 7-12 and 7-22. Updated the ZPWY-TKN-UNKNOWNNAME on page 10-10. Added the new ZPWY-EVT-PM-AUDITSTATUS audit status message on page 11-87. Changes to the H06.14/J06.03 Manual • • • • • • • • • Supported release statements have been updated to include J-series RVUs.
What’s New in This Manual • • • • Changes in the July 1996 Revision of the Manual Corrected code in Example 16-1. Changed the maximum number of concurrently running requester processes from 150 to 800 under Considerations on page 7-11 and in Appendix A, Configuration Limits and Defaults. Updated the event message 1051: ZPWY-EVT-PM-REQUESTTABLEFULL on page 11-45 and the error message 1051: ZPWY-ERR-PM-REQUESTTABLEFULL on page 12-33.
What’s New in This Manual Changes in the July 1996 Revision of the Manual Product Changes This manual edition documents these changes in the D42 product version: • • • The PATHMON configuration file (PATHCTL) can now be made node independent. To support this feature, these changes have been made to the management programming interface: ° A new value, \*, when used in place of a node name, assigns node independence to an attribute.
What’s New in This Manual • • Changes in the July 1996 Revision of the Manual Code in examples in Section 16, Management Programming Examples and Section 18, Error Handling Example Program has been corrected. Miscellaneous terminology changes and editorial corrections have been made.
What’s New in This Manual Changes in the July 1996 Revision of the Manual HP NonStop TS/MP Management Programming Manual—540082-005 xviii
About This Manual This preface describes the purpose and the contents of this manual and other manuals that are closely related to this manual. This manual is one of a set of manuals that describe the TS/MP and Pathway/iTS products. The contents of these two products are: • • TS/MP: This product consists of the PATHMON process, the LINKMON process or the application cluser services (ACS) subsystem processes, the PATHCOM process and interface, and the Pathsend procedure calls.
Who Should Read This Manual About This Manual Who Should Read This Manual This manual is intended for individuals writing applications that manage TS/MP objects in a Pathway subsystem. Such programmers also need the task-oriented information in the TS/MP System Management Manual. It is also assumed that readers have a general knowledge of HP NonStop system programming concepts. To use this manual effectively, you should be familiar with: • • • • • Basic NonStop system architecture.
Related Documentation About This Manual Sections Description Section 7, ZPWY-MAP- Definitions Provides definitions for TS/MP-specific extensible structured tokens used in commands and responses. Section 8, Pathway Subsystem Control Commands and Section 9, Server Class Commands Describe the SPI commands for configuring and controlling Pathway, PATHMON, and Server objects.
Related Documentation About This Manual Figure i.
Related Documentation About This Manual For information specific to managing a Pathway subsystem, read: • • Introduction to NonStop Transaction Processing. This manual describes the environment, components, and benefits of HP transaction processing products, including TS/MP, Pathway/iTS, and related products such as NonStop Transaction Management Facility (TMF) and the NonStop Tuxedo transaction processing system. TS/MP System Management Manual.
Notation Conventions About This Manual • EMS Manual. This manual describes how to write event-message filters to select messages of particular interest and how to distribute event messages to various destinations. Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required.
Notation for Messages About This Manual … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
Notation for Management Programming Interfaces About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
About This Manual HP Encourages Your Comments HP NonStop TS/MP Management Programming Manual—540082-005 xxviii
1 Introduction This manual describes the management programming interface to the Pathway subsystem provided by the NonStop Transaction Services (TS/MP) product. It describes how to use programmatic commands in a management application to configure TS/MP objects that support transaction-processing servers, how to monitor the status and performance of these objects, and how to handle error and event messages returned by the Pathway subsystem. Note.
Which Sections Do You Need? Introduction Which Sections Do You Need? This manual is organized into logical groups of information for easy reference. Table 1-2 is a descriptive map indicating which sections are relevant to particular operating environments. Table 1-2.
Introduction Architecture and Components Figure 1-1 on page 1-4 shows a simple TS/MP application that uses Pathway/iTS. This example shows the TCP and the PATHMON process managing communications between Guardian requesters and servers. Note. Although LINKMON processes or ACS subsystem processes are visible to the PATHMON process and are part of the Pathway subsystem, they are not controlled or managed by the PATHMON process.
Architecture and Components Introduction Figure 1-1.
Distributed Systems Management Introduction Distributed Systems Management Distributed Systems Management (DSM) is a group of software tools that enables you to construct an integrated view of a system or network. DSM tools allow you to: • • • • • • Manage your system from a single control point. Distribute control of transaction processing among systems. Retain a session with one subsystem (such as Pathway, TMF, or FUP) while interacting with another subsystem.
Management Interfaces Introduction Figure 1-2 illustrates a Pathway subsystem that uses the SPI and EMS procedures for subsystem control and event management. Figure 1-2. TS/MP and DSM PATHMON Command Message Event Collector Response Message GETEVENT Command Message Management Application Event Distributor GETEVENT Response Message Event Log VST003.
PATHCOM Interface Introduction Figure 1-3. TS/MP Management Interfaces Devices Management Interfaces Management Application Process PATHMON Process PATHCOM Command Terminal VST004.vsd PATHCOM Interface PATHCOM is a command language interpreter and interactive command interface to the PATHMON process, the central control process for your Pathway subsystem. By using PATHCOM, which consists of sets of object-related commands, you can interactively define and manage all PATHMON-controlled objects.
SPI Interface Introduction Figure 1-4 shows the management programming environment: Figure 1-4. Management Programming Environment Operations Environment Commands, Inquiries Management Programming Interface NonStop TS/MP Environment SPI Pathway Subsystem Management Application EMS Responses, Messages TMF Subsystem VST005.
2 TS/MP Management Programming This section summarizes the SPI interface to the Pathway subsystem and the commands and object types defined for the subsystem. This section also provides information about starting and opening the PATHMON process programmatically. Comparison of PATHCOM and SPI Commands Like PATHCOM, the SPI management programming interface to the Pathway subsystem uses commands that operate on objects.
Comparison of PATHCOM and SPI Commands TS/MP Management Programming Table 2-1.
Pathway Management Programming Interface TS/MP Management Programming Table 2-1.
TS/MP Management Programming • • Control and Inquiry A program that starts SERVER objects automatically at a specified time at the beginning of the day. (This program would communicate with the Pathway subsystem only.) A program that performs automatic recovery after an object failure. (This program would communicate with EMS and Pathway subsystem.) These paragraphs give an overview of the tasks involved in setting up and managing a Pathway subsystem.
TS/MP Management Programming Sending Commands and Receiving Replies Considerations When Opening PATHMON When opening the PATHMON process programmatically, consider: • • • • • The PATHMON process can be opened by multiple user processes. The field ZMAXSPI determines how many processes can request to use the SPI interface to open the PATHMON process at the same time. Both a primary process and its backup can open a PATHMON process simultaneously.
Design Considerations TS/MP Management Programming Figure 2-1 on page 2-6 illustrates the commands sent and the responses received when configuring a Pathway subsystem. Figure 2-1. Sending Commands and Receiving Responses Message Buffer SSINIT Management Application START PATHWAY DEF PATHWAY WRITEREAD SSPUT PATHMON SSGET RESPONSE PATHMON Config File VST006.vsd For a more detailed description of how to build command messages and decode responses, see Section 3, SPI Programming Considerations.
TS/MP Management Programming Design Considerations Use CANCEL or CANCELREQ only if it is unimportant for the application to monitor whether or not the command was performed. • • Pathway subsystems do not support the ALLOW-TYPE token or the RESPONSETYPE token.
TS/MP Management Programming Design Considerations HP NonStop TS/MP Management Programming Manual—540082-005 2 -8
3 SPI Programming Considerations After your subsystem and EMS processes are running and your management application has established communication with the Pathway subsystem, the main business of your management application is to format and send commands, decode responses and act on the results, and interpret event messages and act on their information. This section provides summary information about SPI programming and discusses SPI programming considerations specific to the Pathway subsystem.
SPI Programming Considerations Definition Files Definition Files The commands, responses, and event messages sent to and received from the Pathway subsystem are made up of items called tokens. Each token contains a particular piece of information, such as a command parameter or an item of information about an event. Tokens can be single values or structures consisting of several values. Some tokens, called header tokens, are present in every command and response and in every event message.
SPI Programming Considerations Contents Contents The Pathway definition files contain definitions: • • • • • • • • • • • • • • • • • • Object names for use in error tokens and object-selector tokens Error tokens Attribute (DEF-) tokens Command-modifier (PAR-) tokens Object-selector (SEL-) tokens Qualifier (QUAL-) tokens Commands Object types Token types, used in defining simple tokens Token numbers, which uniquely identify each token Token codes, used in defining simple tokens Predefined values Token ma
SPI Programming Considerations Message Elements for the Pathway Subsystem SPI (ZSPI) definition file PWY (ZPWY) definition file An application that retrieves event messages issued by the Pathway subsystem needs the definition files: SPI (ZSPI) definition file PWY (ZPWY) definition file EMS (ZEMS) definition file For example, a management application written in COBOL that sends commands to and retrieves event messages issued by the Pathway subsystem would copy or load the definition files: ZSPIDEF.
Commands SPI Programming Considerations The Pathway subsystem has its own set of command numbers, which are 16-bit integers represented in DDL by constants and in programs by TAL literals, COBOL level-01 variables, C pragmas, or TACL text variables. The command number is one of the tokens in the message header, which is a component of both command and response buffers. For TS/MP objects, the Pathway subsystem supports the programmatic commands listed in Table 3-1. Table 3-1.
Object Types SPI Programming Considerations Object Types All commands and responses contain an object-type token in the header. For the Pathway subsystem, object types are identified in programs by symbolic names of the form ZPWY-OBJ-name, where name identifies the object type. For example, the PM object type is represented by the name ZPWY-OBJ-PM. The object-type header token, ZSPI-TKN-OBJECT-TYPE, always has one of these names.
Object Types SPI Programming Considerations Table 3-2. TS/MP Object Types (page 2 of 2) Object Type Description ZPWY-OBJ-SCPARAM A PARAM associated with a server class. This object allows you to assign a string value to a server parameter name. This object type is the same as the PARAM parameter in the PATHCOM SERVER object commands. ZPWY-OBJ-SCPROCESS A process associated with a server class. This object type is the same as the PROCESS parameter in the PATHCOM SERVER object commands.
Object Names SPI Programming Considerations Figure 3-1.
SPI Programming Considerations Object-Selector Tokens Object-Selector Tokens Many Pathway commands and responses contain object-selector tokens that, when combined with object-type information, designate which objects are affected by the command. Object-selector tokens are represented by the name ZPWY-DDL-SELname, where name is the name of the specific object. Event Numbers All event messages contain a header token identifying the event by number.
Extensible Structured Tokens SPI Programming Considerations Extensible Structured Tokens This is a sample DDL definition for an extensible structured token that defines the attributes for a program. The TAL, COBOL, TACL, and C code generated follows the DDL definition. Note. The TAL, COBOL, TACL, and C codes redefine each character field (Z^C and Z-C in the examples) as an integer array and as an array of individual bytes to accommodate certain NonStop operating system procedures.
SPI Programming Considerations Extensible Structured Tokens Corresponding TAL structure for ZPWY-DDL-DEF-SCASSIGN: STRUCT ZPWY^DDL^DEF^SCASSIGN^DEF (*); BEGIN STRUCT ZGUARDIANFILE; BEGIN STRUCT Z^SYSNAME; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; STRUCT Z^S = Z^C; BEGIN INT Z^I[0:3]; END; STRING Z^B[0:7] = Z^C; END; STRUCT Z^LOCALNAME; BEGIN STRUCT Z^DISC; BEGIN STRUCT Z^VOLUME; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; STRUCT Z^S = Z^C; BEGIN INT Z^1[0:3]; END; ... ... ...
SPI Programming Considerations Extensible Structured Tokens Corresponding COBOL level-01 variable for ZPWY-DDL-DEF-SCASSIGN: 01 ZPWY-DDL-DEF-SCASSIGN. 02 ZGUARDIANFILE 03 Z-SYSNAME. 04 Z-C 04 Z-S REDEFINES Z-C. 05 Z-I 04 Z-B REDEFINES Z-C 03 Z-LOCALNAME. 04 Z-DISC. 05 Z-VOLUME. 06 Z-C 06 Z-S REDEFINES Z-C. 07 Z-I 06 Z-B REDEFINES Z-C PIC X(8). NATIVE-2 OCCURS 4 TIMES. PIC X OCCURS 8 TIMES. PIC X(8). NATIVE-2 OCCURS 4 TIMES. PIC X OCCURS 8 TIMES. ... ... ... 02 ZBLOCKSIZE NATIVE-2.
Types for Fields in Structured Tokens SPI Programming Considerations Corresponding C pragma for ZPWY-DDL-DEF-SCASSIGN: #pragma fieldalign shared2 __zpwy_ddl_def_scassign typedef struct __zpwy_ddl_def_scassign { zspi_ddl_fname32_def zguardianfile; struct { zspi_ddl_int2_def zprimary; zspi_ddl_int2_def zsecondary; } zextentsize; zspi_ddl_int2_def zfilecode; zspi_ddl_int_def zexclusion; zspi_ddl_int_def zaccess; zspi_ddl_int_def zrecordsize; zspi_ddl_int_def zblocksize; Types for Fields in Structured Tokens
SPI Programming Considerations Data Lists and Error Lists Previously in the ZSPIDDL file, ZSPI-DDL-CHAR8 is defined as eight ASCII characters. ZSPI-DDL-FNAME is defined as a Guardian internal format file name, including disk name, process name, and device name. Throughout this manual, the type of a field is indicated wherever the field is described.
SPI Programming Considerations Considerations for SSINIT 6. Send the command message using the mechanism appropriate to your programming language (for example, a WRITEREAD call in TAL, a READ WITH PROMPT verb in COBOL, or a #INPUTV or #OUTPUTV built-in function in TACL). Note. Always initialize an extensible structured token that is to appear in a command by using the SPI procedure SSNULL. This procedure ensures that every field of the token is initialized to its null value.
Considerations for SSPUT SPI Programming Considerations For TACL: #SET ZPWY^VAL^SSID & [ZSPI^VAL^TANDEM].[ZSPI^SSN^ZPWY].[ZPWY^VAL^VERSION] For C: zpwy_val_ssid_def zpwy_val_ssid ={ ZSPI_VAL_TANDEM, ZSPI_SSN_ZPWY ZPWY_VAL_VERSION }; or #string.h strcpy ( zpwy_val_ssid.z_owner, ZSPI_VAL_TANDEM }; strcpy ( zpwy_val_ssid.z_number = ZSPI_SSN_ZPWY }; strcpy ( zpwy_val_ssid.
SPI Programming Considerations Specifying Continuation Specifying Continuation Because the Pathway subsystem does not support multiple responses per response buffer, your management application must use continuation if you want to change or query a series of objects or subobjects with a single command. Continuation allows your management application to resubmit a command repeatedly until all objects or subobjects in a series have been accessed.
Required Object States for Continuation SPI Programming Considerations End of Continuation The Pathway subsystem management programming interface is designed to return a context token during continuation whenever there is a response in the response buffer. As a result, the Pathway subsystem always returns an empty response for the last record of a continuation. The value ZPWY-ERR-PM-NODATA denotes an empty response buffer, as well as the end of the response continuation dialog.
Continuation Example SPI Programming Considerations Table 3-3.
32-Byte File Names SPI Programming Considerations The Application… 6. 8. The PATHMON Process… Reissues the INFO SC command with the special selector and adds the context token from the previous response to the message. 7. Returns the name of CLASS-B and a context token. 9. Returns the name of CLASS-C and a context token. Reissues the INFO SC command with the special selector and adds the context token from the previous response to the message. 10.
Resetting Values in Fields SPI Programming Considerations Example 3-1. Format for 32-Byte File Names File Name 32-Byte Format Byte # 0....5....10...15...20...25....31 \A.$B "\A $B " \A.$B.#C "\A $B #C \A.$B.#C.D "\A $B #C D " \W.$X.Y.Z "\W $X Y Z " " These procedures are provided in the system library for handling file names in this format: • • • • FNAME32COLLAPSE, similar to the system procedure FNAMECOLLAPSE, converts 32-byte file names to external format.
Receiving and Decoding Response Messages SPI Programming Considerations Table 3-4.
SPI Programming Considerations Considerations The Pathway subsystem can return an empty response if an application returns a ZSPI-TKN-CONTEXT token and there are no more responses to be returned. The return token ZSPI-TKN-RETCODE in the returned response always has the value ZPWY-ERR-PM-EOF. 6. Take action appropriate to the information in the response. Considerations The response buffer always contains the return token, ZSPI-TKN-RETCODE.
Security SPI Programming Considerations The PATHMON process does not provide support for continuing—despite errors— through the use of the SPI standard token ZSPI-TKN-ALLOW-TYPE. The SPI standard token ZSPI-TKN-RETCODE contains a nonzero value if the PATHMON process detects an error in a command message or detects an error when attempting to perform a command. The Pathway subsystem can also return file-system errors.
Naming Guidelines for Applications SPI Programming Considerations Table 3-5. Restricted Commands and Objects for TS/MP To Control… Use These Restricted (Sensitive) Commands (ZPWY-CMD- ) and Object Types (ZPWY-OBJ- )… START SC SCPROCESS STOP SC THAW SC Any user can issue all of the other commands.
SPI Programming Considerations Server Objects 3. Use the SWITCH PM and CONTROL PM commands to move the primary PATHMON process back to the configured CPU. The last command in the sequence should be a CONTROL PM command so that the changes are recorded in the PATHCTL file. • • The PATHCOM LOG1 and LOG2 commands are implemented by issuing the ZPWY-CMD-CONTROL command with the ZPWY-OBJ-PM object.
SPI Programming Considerations Writing C Programs When the last link known to the PATHMON process is returned by a link manager (such as the LINKMON process) and the associative server is started by the PATHMON process, the PATHMON process leaves the server state as RUNNING (instead of changing it to PENDING). A RUNNING state allows the PATHMON process to continue to allocate links to the server during the period that other requesters continue to use the server.
SPI Programming Considerations Command Presentation Generating the ZPWYC Include File Under certain conditions, the DDL compiler introduces an extra level in the structure definitions in the ZPWYC file. If any C compiler errors indicate a problem with the structure fields, make sure the structure definition in the ZPWYC file matches the structure used in the program.
Unlisted Tokens SPI Programming Considerations The notation used for simple tokens in the syntax box is an abbreviated version of the essential information given in the DDL TOKEN-CODE statement. You define extensible structured tokens by using DDL DEFINITION statements. The order of the tokens in the syntax box is not necessarily the order in which they must occur in a command or response buffer—except for the ZSPI-TKN-ENDLIST token.
SPI Programming Considerations Required Tokens and Fields HP NonStop TS/MP Management Programming Manual—540082-005 3- 30
4 SPI and EMS Standard Definitions This section discusses SPI and EMS standard definitions used in the token-oriented management programming interface to TS/MP and Pathway/iTS. The information in this section is general information. Information about a definition specific to a particular command or response appears in the description of that command or response, later in this manual. Definitions in this section appear in Data Definition Language (DDL) format.
SPI Standard Definitions SPI and EMS Standard Definitions Table 4-1. SPI Standard Definitions for Header Tokens ZSPI-TKN-CHECKSUM ZSPI-TKN-COMMAND ZSPI-TKN-HDRTYPE ZSPI-TKN-LASTERR ZSPI-TKN-LASTERRCODE ZSPI-TKN-LASTPOSITION ZSPI-TKN-MAX-FIELD-VERSION ZSPI-TKN-MAXRESP ZSPI-TKN-OBJECT-TYPE ZSPI-TKN-POSITION ZSPI-TKN-SERVER-VERSION ZSPI-TKN-SSID ZSPI-TKN-USEDLEN Table 4-2.
SPI and EMS Standard Definitions Information Specific to the Pathway Subsystem Table 4-5. SPI Standard Definitions for Structures ZSPI-DDL-BOOLEAN ZSPI-DDL-BYTE ZSPI-DDL-CHAR-PAIR ZSPI-DDL-CHAR6 ZSPI-DDL-CHAR8 ZSPI-DDL-CRTPID ZSPI-DDL-DEVICE ZSPI-DDL-DISCNAME ZSPI-DDL-ENUM ZSPI-DDL-FNAME ZSPI-DDL-INT ZSPI-DDL-INT2 ZSPI-DDL-INT2-PAIR ZSPI-DDL-TIMESTAMP ZSPI-DDL-TRANSID ZSPI-DDL-UINT ZSPI-DDL-USERID Table 4-6.
EMS Standard Definitions SPI and EMS Standard Definitions ZSPI-TKN-SSID contains ZPWY-VAL-SSID, the subsystem ID of the Pathway subsystem with this structure: def ZPWY-VAL-SSID 02 Z-FILLER 02 Z-OWNER 02 Z-NUMBER 02 Z-VERSION Tacl SSID. token-type ZSPI-DDL-CHAR 8. value ZSPI-VAL-TANDEM. token-type ZSPI-DDL-CHAR 8. redefines Z-FILLER token-type ZSPI-DDL-INT. value ZSPI-SSN-ZPWY. token-type ZSPI-DDL-INT value ZPWY-VAL-VERSION. end. ZSPI-SSN-ZPWY is the subsystem number assigned to the Pathway subsystem.
5 ZPWY-DDL- Definitions This section discusses private tokens, field types, and predefined token and field values used in the token-oriented management programming interface to TS/MP. The information in this section is general information. Information about a definition specific to a particular command or response appears in the description of that command or response, later in this manual. Definitions in this section appear in Data Definition Language (DDL) format.
Pathway Subsystem Definitions ZPWY-DDL- Definitions Table 5-3.
Buffer Declarations ZPWY-DDL- Definitions Buffer Declarations TS/MP provides these buffer declarations for message buffers you can use with the SPI procedures. ZPWY-DDL-MSG-BUFFER is a message buffer of the appropriate size for use with the SPI procedures in applications that manage Guardian server processes. def ZPWY-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER token-type token-type token-type token-type occurs ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT.
Token Codes for Object Names ZPWY-DDL- Definitions The DDL definitions for object names are also used to define the error tokens ZPWY-TKN-REQobjecttypeNAME and ZPWY-TKN-objecttypeNAME and the subject tokens for event messages. Token Codes for Object Names The DDL definitions for object names describe token types that have the prefix ZPWY-TYP-. The token types are used to build token codes, which have the prefix ZPWY-TKN-.
ZPWY-DDL-SCASSIGNNAME ZPWY-DDL- Definitions ZSERVERCLASS is the name of the server class. ZVERSION is the internal format version; set this to the preset value ZPWY-VALSERVERCLASS2. The PATHMON process uses this value to ensure that the response buffer contains data compatible with the requester version. ZPWY-DDL-SCASSIGNNAME ZPWY-DDL-SCASSIGNNAME identifies an ASSIGN message and the server class with which it is associated. def ZPWY-DDL-SCASSIGNNAME. 02 ZSERVERCLASS 02 FILLER 02 ZLOGICALUNIT.
ZPWY-DDL-SCDEFINENAME ZPWY-DDL- Definitions ZPWY-DDL-SCDEFINENAME ZPWY-DDL-SCDEFINENAME identifies a DEFINE definition and the server class with which it is associated. def ZPWY-DDL-SCDEFINENAME. 02 ZSERVERCLASS 02 FILLER 02 ZDEFINE end. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. token-type ZPWY-DDL-DEFINE-NAME. ZSERVERCLASS is the server class with which this DEFINE name is associated. ZDEFINE is the name of the DEFINE.
ZPWY-DDL- Definitions ZPWY-DDL-SCPROCESSNAME ZSERVERCLASS is the name of the server class with which the PARAM is associated. ZPARAM is the name of a parameter to which you assign a string value. ZPWY-DDL-SCPROCESSNAME ZPWY-DDL-SCPROCESSNAME identifies a specific server process within a server class. def ZPWY-DDL-SCPROCESSNAME. 02 ZSERVERCLASS 02 FILLER 02 ZPROCESS 02 ZVERSION token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. token-type ZSPI-DDL-CHAR6. token-type ZPWY-DDL-SCPROCESS-VERSION.
ZPWY-DDL-UNKNOWNNAME ZPWY-DDL- Definitions ZSERVERCLASS is the name of the server class. ZPWY-DDL-UNKNOWNNAME ZPWY-DDL-UNKNOWNNAME is used in event management to identify the name of the subject when the object type (for example, SC) is unknown. It is also used for internal errors when the type of the subject is not known. def ZPWY-DDL-UNKNOWNNAME. 02 UNKNOWN 02 FILLER-1 end. token-type ZPWY-DDL-OBJECT-NAME.
ZPWY-DDL-CHAR24 ZPWY-DDL- Definitions ZPWY-DDL-CHAR24 ZPWY-DDL-CHAR24 designates 24 ASCII characters, addressable as a STRUCT, as bytes or as integers. def ZPWY-DDL-CHAR24. 02 Z-C 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C end. pic X(24). type BINARY 16 occurs 12 times. pic X occurs 24 times. ZPWY-DDL-CHAR31 ZPWY-DDL-CHAR31 designates 31 ASCII characters, addressable as a STRUCT, as bytes or as integers. def ZPWY-DDL-CHAR31. 02 Z-C 02 Z-S redefines Z-C. 03 Z-I 03 FILLER 02 Z-B redefines Z-C end.
ZPWY-DDL-CPU ZPWY-DDL- Definitions ZPWY-DDL-CPU ZPWY-DDL-CPU is the CPU number of a particular processor in a system. Valid values range from 0 through 15. def ZPWY-DDL-CPU token-type ZSPI-DDL-INT. ZPWY-DDL-CPUWT ZPWY-DDL-CPUWT is the weight of a defined processor (CPU). Valid values range from 1 through 100. def ZPWY-DDL-CPUWT token-type ZSPI-DDL-INT. Assigning a value for ZPWY-DDL-CPUWT is optional. Note. ZPWY-DDL-CPUWT is supported by TS/MP 2.4 and is available only on systems running J06.
ZPWY-DDL-DUMP-INFO ZPWY-DDL- Definitions A DEFINE name can be from 2 through 24 characters in length. The first character must be an equal sign (=) and the second must be a letter. The name can contain alphanumeric characters, hyphens (-), underscores (_), and circumflexes (^). For more information about DEFINEs, see the TACL Reference Manual and the Guardian User’s Guide.
ZPWY-DDL- Definitions ZPWY-DDL-DUMP-INFO If a file error interferes with creating a file that you specify, the PATHMON process creates the dump file on the same subvolume as its program object file and uses the form ZZPMnnn for the file name. If you do not specify a file name, the PATHMON process creates its dump file on the same volume and subvolume as the PATHMON configuration file.
ZPWY-DDL- Definitions ZPWY-DDL-ERRINFO2 For more information on PATHMON dump files, see the CONTROL PM command description in the TS/MP System Management Manual. For more information on TCP dump files, see the SET TCP command in the Pathway/iTS System Management Manual. Reset values for each field are predefined. These values are described in Section 3, SPI Programming Considerations. Use the #SETBYTES built-in function to reset the fields using the TACL program.
ZPWY-DDL-ERROR-INFO ZPWY-DDL- Definitions ZDETAIL2 contains additional error information. This example shows error information returned in ZERRORINFO and ZERRORINFO2: ZERRORINFO ZERROR ZINFO ZERRORINFO2 ZERROR2 ZINFO2 ZDETAIL2 1038 %001413 1038 1 11 ZPWY-DDL-ERROR-INFO ZPWY-DDL-ERROR-INFO provides error information. def ZPWY-DDL-ERROR-INFO. 02 ZERROR 02 ZINFO end. token-type ZPWY-DDL-INT. token-type ZSPI-DDL-INT. ZERROR contains a Pathway environment error number.
ZPWY-DDL-OBJECT-NAME ZPWY-DDL- Definitions ZPWY-DDL-OBJECT-NAME ZPWY-DDL-OBJECT-NAME designates a name given to an object in the PATHMON environment (such as a PM or SC object). The name can have from 1 through 15 alphanumeric or hyphen characters, must start with a letter, must be unique within the Pathway subsystem, and must not be a Pathway reserved word. The name must be left-justified and blank-filled. Pathway subsystem reserved words are listed in the TS/MP System Management Manual.
ZPWY-DDL-SC-VERSION ZPWY-DDL- Definitions ZGROUPNUMBER is a number from 0 through 255 that uniquely identifies a group of users on a system. This field is required. ZUSERNUMBER is a number from 0 through 255 that uniquely identifies a user within a group. This field is required. If you do not assign values to these fields, the default is the owner ID of the user who started the PATHMON process. ZPWY-DDL-SC-VERSION ZPWY-DDL-SC-VERSION is the internal format version of a requester.
ZPWY-DDL-0-100 ZPWY-DDL- Definitions Note. ZPWY-VAL-YES is equivalent to ZSPI-VAL-TRUE, and ZPWY-VAL-NO is equivalent to ZSPI-VAL-FALSE, neither of which is supported in COBOL. For information on working with Boolean values and COBOL coding suggestions, see the SPI Programming Manual. ZPWY-DDL-0-100 ZPWY-DDL-0-100 is a value from 0 through 100. def ZPWY-DDL-0-100 token-type ZSPI-DDL-INT. ZPWY-DDL-0-4095 ZPWY-DDL-0-4095 is a value from 0 through 4095. def ZPWY-DDL-0-4095 token-type ZSPI-DDL-INT.
ZPWY-DDL- Definitions Predefined Token and Field Values Predefined Token and Field Values A predefined token or field is given a symbolic name in the Pathway subsystem definitions file. The Pathway subsystem defines these token and field values: ZPWY-VAL-SSID is the subsystem ID of the Pathway subsystem. For information about the structure of this value, see ZSPI-TKN-SSID on page 4-4. ZPWY-VAL-BUFLEN is the length of the message buffer, in bytes.
ZPWY-DDL-CTLSTATE-VALUE ZPWY-DDL- Definitions ZPWY-DDL-CTLSTATE-VALUE ZPWY-DDL-CTLSTATE-VALUE contains information on the state of the PATHMON process in the PATHCTL file. Values are described with ZPWY-MAP-PAR-INFO on page 7-31. def ZPWY-DDL-CTLSTATE-VALUE token-type ZSPI-DDL-ENUM. ZPWY-DDL-FILESTATE-VALUE ZPWY-DDL-FILESTATE-VALUE specifies the state of a file. def ZPWY-DDL-FILESTATE-VALUE ENUM. token-type ZSPI-DDL- Valid values are ZPWY-VAL-CLOSED or ZPWY-VAL-OPEN.
ZPWY-DDL-PMSTATE-VALUE ZPWY-DDL- Definitions The valid values are: ZPWY-VAL-STOPPED The server process is stopped. ZPWY-VAL-PENDING The server process is stopping. ZPWY-VALSUSPENDED The server process is suspended. ZPWY-VAL-RUNNING The server process is running. ZPWY-DDL-PMSTATE-VALUE ZPWY-DDL-PMSTATE-VALUE provides the status of the PATHMON process. def ZPWY-DDL-PMSTATE-VALUE ENUM.
ZPWY-DDL-REQTYPE-VALUE ZPWY-DDL- Definitions ZPWY-DDL-REQTYPE-VALUE ZPWY-DDL-REQTYPE-VALUE identifies a process that is currently communicating with the PATHMON process. def ZPWY-DDL-REQTYPE-VALUE ENUM. token-type ZSPI-DDL- Values are described under ZPWY-MAP-STATUS-PMREQUESTER on page 7-51. ZPWY-DDL-REQWAIT-VALUE ZPWY-DDL-REQWAIT-VALUE identifies the reason a request to the PATHMON process is waiting in response to the STATUS PMREQUESTER command. def ZPWY-DDL-REQWAIT-VALUE ENUM.
ZPWY-DDL- Definitions Simple Tokens For more information on error and event tokens, see Section 7, ZPWY-MAPDefinitions. For more information on error and event tokens, see Section 10, Event Management.
6 ZPWY-TKN- Definitions This section discusses variable-length byte string tokens used in the token-oriented management programming interface to TS/MP. Each variable-length byte string token has a value consisting of a string of bytes of varying length. Table 6-1 lists the variablelength byte strings provided by the Pathway subsystem: Table 6-1.
ZPWY-TKN-DEF-SCCWD ZPWY-TKN- Definitions The length of the argument list can be from 2 through 24,000 bytes. The combined total length of ZPWY-TKN-DEF-SCENV and ZPWY-TKN-DEF-SCARGLIST must not exceed 24,000 bytes. The program name that is automatically passed as the first argument (argv[0]) does not need to be specified by the user, nor is it included in the 24,000 character maximum. If you do not assign a value for this token when adding a server class, the default is an empty argument list.
ZPWY-TKN-DEF-SCDEFINE ZPWY-TKN- Definitions ZPWY-TKN-DEF-SCDEFINE This token is a variable-length byte string that contains saved DEFINE attributes. A saved DEFINE is an internal file name representation created when you set DEFINE attributes, add a DEFINE name, or save a DEFINE using Guardian procedures. def ZPWY-TKN-DEF-SCDEFINE BYTESTRING. token-type ZSPI-TYP- The first two bytes of the string is the length of the saved DEFINE that follows, in bytes. The third byte is the start of the DEFINE.
ZPWY-TKN-DEF-SCPROGRAMOSS ZPWY-TKN- Definitions This token is returned in the response buffer of an INFO command only if a value has been defined. This field is valid for OSS server processes only. ZPWY-TKN-DEF-SCPROGRAMOSS This token is the name of the object file used by the servers in a OSS server class. def ZPWY-TKN-DEF-SCPROGRAMOSS BYTESTRING. token-type ZSPI-TYP- The first two bytes of the string is the length of the pathname that follows, in bytes. The third byte is the start of the pathname.
ZPWY-TKN-DEF-SCSTDIN ZPWY-TKN- Definitions To reset the value for this token in an ALTER command, specify a string length of 0 in the first two bytes of the string. If the token is not included in the command buffer, the current value is not changed. If the file specified does not exist, it is created. Output is appended to the end of the file. If you omit this attribute, a null string is sent to the server process.
ZPWY-TKN- Definitions ZPWY-TKN-DEF-SCSTDOUT The first two bytes of the string is the length of the pathname that follows, in bytes. The third byte is the start of the pathname. The length cannot exceed 1023 bytes; the last character (character 1024) is reserved for a null. If you do not assign a default directory to resolve relative OSS pathnames (using ZPWY-TKN-DEF-SCCWD), you must specify an absolute OSS pathname for the OSS stdout file. Case is significant.
7 ZPWY-MAP- Definitions This section discusses extensible structured tokens used in the token-oriented management programming interface to TS/MP. The information in this section is general information. Information about a definition specific to a particular command or response appears in the description of that command or response, later in this manual. Definitions in this section appear in Data Definition Language (DDL) format. Definitions of structures use DDL definition statements.
Extensible Structured Tokens ZPWY-MAP- Definitions Table 7-1. Categories of Extensible Structured Tokens (page 2 of 2) Category Token Format Description Selector tokens ZPWY-MAP-SEL- These tokens select specific objects by name. Statistics tokens ZPWY-MAP-STATS- These tokens contain status information returned from the PATHMON process. Status tokens ZPWY-MAP-STATUS- These tokens contain statistics and performance information returned from the PATHMON process.
ZPWY-MAP-DEF-PATHCTL ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHCTL This token contains information on the PATHMON configuration file returned by the INFO PATHCTL command. def ZPWY-DDL-DEF-PATHCTL. 02 ZPATHCTLSTATE VALUE. 02 ZCOLDSTARTTIME 02 ZCOOLSTARTTIME 02 ZPATHMONNAME end. token-type ZPWY-DDL-CTLSTATEtoken-type ZSPI-DDL-TIMESTAMP. token-type ZSPI-DDL-TIMESTAMP. token-type ZSPI-DDL-CRTPID. ZPATHCTLSTATE is the state of the PATHMON process in the PATHMON configuration file.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY ZPATHMONNAME is the PATHMON process name and process ID as recorded in the configuration file. ZPWY-MAP-DEF-PATHWAY This token defines all the attributes for the PATHMON process and for the Pathway subsystem. It contains the information you would specify with the SET PATHMON and SET PATHWAY commands in the PATHCOM interface. Note. Some of the ZPWY-MAP-DEF-PATHWAY fields apply only to the Pathway/iTS product.
ZPWY-MAP-DEF-PATHWAY ZPWY-MAP- Definitions def ZPWY-DDL-DEF-PATHWAY. 02 ZBACKUPCPU 02 ZDUMPINFO. 03 ZDUMP 03 ZDUMPFILE 02 ZMAXASSIGNS !r 02 ZMAXEXTERNALTCPS 02 ZMAXLINKMONS 02 ZMAXPARAMS !r 02 ZMAXPATHCOMS 02 ZMAXPROGRAMS 02 ZMAXSERVERCLASSES !r 02 ZMAXSERVERPROCESSES !r 02 ZMAXSPI 02 ZMAXSTARTUPS !r 02 ZMAXTCPS !r 02 ZMAXTELLQUEUE 02 ZMAXTELLS 02 ZMAXTERMS !r 02 ZMAXTMFRESTARTS 02 ZOWNER. 03 ZSYSTEMNUMBER 03 ZGROUPNUMBER 03 ZUSERNUMBER 02 ZSECURITY VALUE.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY ZBACKUPCPU specifies the CPU in which the PATHMON backup process runs. ZDUMPINFO specifies information about dump files. The fields are described under ZPWY-DDLDUMP-INFO on page 5-11. To reset this field using the TACL program, you must use the #SETBYTES built-in function. For more information, see the SPI Programming Manual. ZMAXASSIGNS is the maximum number of ADD SCASSIGN definitions that you can specify for all server classes in the PATHMON environment.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY ZMAXPARAMS is the maximum number of PARAM messages that you can specify across all server classes in the PATHMON environment. A single PARAM message exists for each server class that contains one or more individual PARAMs. This field has the same meaning as the MAXPARAMS parameter in the PATHCOM SET PATHWAY command. ZMAXPARAMS must be a number from 0 through 4095. This field is required; there is no default.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY The combined values for ZMAXSERVERS in ZPWY-MAP-DEF-SC (or MAXSERVERS in the PATHCOM SERVER definition) for all server classes is limited to the value of ZMAXSERVERPROCESSES. This field is required; there is no default. ZMAXSPI is the maximum number of SPI processes that can run simultaneously within the Pathway subsystem. The value must be a number from 1 through 100.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY ZMAXTERMS this field applies only to Pathway/iTS; a complete description is given in the Pathway/iTS Management Programming Manual. If you do not have Pathway/iTS installed, HP recommends setting this value to zero. This field is required; there is no default. ZMAXTMFRESTARTS this field applies only to Pathway/iTS; a complete description is given in the Pathway/iTS Management Programming Manual.
ZPWY-MAP-DEF-PATHWAY ZPWY-MAP- Definitions ZNODEINDEPENDENT specifies how node names are resolved when no node name is specified for a given field.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY The information-only fields described in the Pathway/iTS Management Programming Manual are: ZCUREXTERNALTCPS ZCURPROGRAMS ZCURTCPS ZCURTELLS ZCURTERMS Considerations • • If Pathway/iTS is used in conjunction with TS/MP, the total of the values for ZMAXLINKMONS and the Pathway/iTS fields ZMAXTCPS and ZMAXEXTERNALTCPS cannot exceed 800.
ZPWY-MAP-DEF-SC ZPWY-MAP- Definitions ZPWY-MAP-DEF-SC ZPWY-MAP-DEF-SC identifies an extensible structured token that defines the attributes for a server class. ZPWY-MAP-DEF-SC def ZPWY-DDL-DEF-SC. 02 ZAUTORESTART 02 ZCPUINFO. !r 03 ZCPUPAIRCOUNT 03 ZCPUPAIR.
ZPWY-MAP-DEF-SC ZPWY-MAP- Definitions ZAUTORESTART specifies the number of times that the PATHMON process attempts to restart a server process within a fixed 10-minute interval after an abnormal termination, such as a call to the Guardian ABEND procedure. The valid values are: 0 Specifies no automatic restart. 1 through 32,767 Directs the PATHMON process to allow this many automatic restarts in 10 minutes. Directs the PATHMON process to allow unlimited restarts in 10 minutes.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SC ZBACKUP when specifying primary and backup processor pairs, this field is the backup processor. Valid values are in the range from 0 through 15. It is recommeded that you specify a CPU number that is greater than plus or minus one from the primary CPU. When specifying a list of single CPUs, the only valid value is -1. Only Guardian server processes can be run as NonStop processes.
ZPWY-MAP-DEF-SC ZPWY-MAP- Definitions If you do not assign a value to this field, the default is 60,000,000 (1 minute). If the link manager has no established links or it calculates that a static link is available, the link manager immediately requests a link without waiting for ZCREATEDELAY to expire. While waiting for ZCREATEDELAY to expire, if an established or newly created link becomes available, the link manager immediately uses that link.
ZPWY-MAP-DEF-SC ZPWY-MAP- Definitions ZGUARDIANLIB specifies the name of the user library object file that contains additional server code space and procedures that can be shared among servers. If you supply a file name for this field, the operating system uses this file name and the file named in the ZPROGRAM field to access the server code. For example: ZPROGRAM $DATA.WORK.SRVOBJ ZGUARDIANLIB $DATA.WORK.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SC ZIN is the name of the input file passed to the server process in the startup message; this could be a DEFINE name. The node name can be either a specific node name or \*, a generic name representing the node on which the PATHMON process is currently running. If you do not specify a node name, the default node for the file-name expansion is determined by the value you specify for the ZNODEINDEPENDENT field of the START PATHWAY command.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SC If the value for this field is too large, it can cause the requests for the server to be queued at the server. For example, if ZMAXLINKS has a value of 20, there could be 20 concurrent requests outstanding to a server process. If the transaction service time is 1 second, a response time of more than 20 seconds can occur. Note. The value of ZMAXLINKS and the value of the TABLE OCCURS clause in the RECEIVE-CONTROL paragraph of your COBOL server programs must correspond.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SC If you do not assign a value to this field, the default is 0 (that is, all servers are dynamic). The PATHMON process does not create a server until it receives a link request from a link manager. When ZNUMSTATIC has a value of 0, the first link to a server class counts as a static link in the server statistics. For more information on configuring this field, see the TS/MP System Management Manual. The value of ZNUMSTATIC cannot exceed the value of ZMAXSERVERS.
ZPWY-MAP-DEF-SC ZPWY-MAP- Definitions ZSENDTIMEOUT specifies the timeout value that a link manager (such as a LINKMON process, ACS subsystem processes, or Pathway/iTS TCP) uses for the I/O operation to the server process. You must specify ZSENDTIMEOUT as a quadrupleword (64-bit) microsecond value; the value must be in the range of 0 through 18 hours or 0 through 1092 minutes, or 0 through 16,383 seconds.
ZPWY-MAP-DEF-SC ZPWY-MAP- Definitions ZDEFAULTVOLUME for Guardian processes, specifies the server class default volume and subvolume names to be passed to the server process in the startup message. This value is also used by the PATHMON process for the VOLUME attribute of _DEFAULTS DEFINE. For OSS processes, specifies the server class default Guardian volume and subvolume used by the PATHMON process for the VOLUME attribute of _DEFAULTS DEFINE.
ZPWY-MAP-DEF-SCASSIGN ZPWY-MAP- Definitions To run a server at a high PIN, you must also set the ?HIGHPIN compiler directive in your server source code file. For more information about the ?HIGHPIN compiler directive, see the appropriate programming language reference manual. ZPROCESSTYPE specifies the type of servers in the server class. The valid values are: ZPWY-VALGUARDIAN All servers in this server class are Guardian processes. ZPWY-VAL-OSS All servers in this server class are OSS processes.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SCASSIGN ZGUARDIANFILE is the name of a Guardian file in which the PATHMON process stores the ASSIGN values and sends those values to the server process using an ASSIGN message when the server process is opened. The node name can be either a specific node name or \*, a generic name representing the node on which the PATHMON process is currently running.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SCASSIGN ZRECORDSIZE sets the length of the records in the logical file indicated in ZPWY-MAP-SEL-SCASSIGN. Valid values range from 1 through 4072. If you do not assign a value to ZRECORDSIZE, no value is passed. ZBLOCKSIZE sets the size of the data blocks for the logical file indicated in ZPWY-MAP-SEL-SCASSIGN. Valid values range from 1 through 4096. If you do not assign a value to ZBLOCKSIZE, no value is passed.
ZPWY-MAP-DEF-SCPARAM ZPWY-MAP- Definitions ZPWY-MAP-DEF-SCPARAM This token defines an individual server PARAM. The PATHMON process bundles all the individual PARAMs for a specific server into a PARAM message according to a specified Guardian format. The PATHMON process sends the PARAM message to each server process that it starts. def ZPWY-DDL-DEF-SCPARAM. 02 ZLENGTH 02 ZAREA CHAR132. end. token-type ZSPI-DDL-INT. token-type ZPWY-DDL- ZLENGTH is the length, in bytes, of the parameter value.
ZPWY-MAP-DEF-SCPROCESS ZPWY-MAP- Definitions ZPWY-MAP-DEF-SCPROCESS This token defines attributes for a server process within a server class. def ZPWY-DDL-DEF-SCPROCESS. 02 ZASSOCIATIVE token-type 02 ZCPUPAIR. 03 ZPRIMARY token-type 03 ZBACKUP token-type 02 ZDEBUG token-type 02 ZGUARDIANSWAP token-type 02 ZHOMETERM token-type 02 ZPRIORITY token-type end. ZPWY-DDL-ON-OFF. ZPWY-DDL-CPU. ZPWY-DDL-CPU. ZPWY-DDL-ON-OFF. ZSPI-DDL-FNAME32. ZSPI-DDL-FNAME32. ZPWY-DDL-1-199.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-SCPROCESS When ZCPUPAIR is used with ZPWY-MAP-DEF-SCPROCESS, the PATHMON process uses the CPUs specified for the server process. The CPUs specified for the server process do not need to match the CPUs specified for the server class in ZPWY-MAP-DEF-SC. If you do not assign a value to the ZCPUPAIR fields, the system assigns the same value designated in the ZCPUPAIR field in ZPWY-DDL-DEF-SC.
ZPWY-MAP-DEF-SCSTARTUP ZPWY-MAP- Definitions ZPRIORITY is the priority at which the server process runs. Valid values range from 1 through 199. If you do not assign a value to this field, the default is the value specified for the same field in ZPWY-DDL-DEF-SC. ZPWY-MAP-DEF-SCSTARTUP This token defines the character string sent to a Guardian server process in the startup message. def ZPWY-DDL-DEF-SCSTARTUP. 02 ZLENGTH token-type ZSPI-DDL-INT. !r 02 ZAREA token-type ZPWY-DDL-CHAR132. !r end.
ZPWY-MAP-PAR-CONTROL-PM ZPWY-MAP- Definitions Note. Any field in this structure can be changed independently of any other field. If you change the value for a field and do not explicitly assign a value to other fields, the other fields retain their original values. ZBACKUPCPU specifies the CPU where the PATHMON backup process runs. PATHMON stops its existing backup process and creates a new backup process in the CPU you specify.
ZPWY-MAP- Definitions ZPWY-MAP-PAR-CONTROL-PM ZSTATUS indicates whether status change messages, along with the error messages, should be logged to the file you specify in the ZFILE field. The valid values are: ZPWY-VAL-OFF Specifies not to include status change messages ZPWY-VAL-ON Specifies to include status change messages If you do not assign a value to this field and no value was previously assigned, the default is ZPWY-VAL-OFF.
ZPWY-MAP-PAR-FREEZE-SC ZPWY-MAP- Definitions ZPWY-MAP-PAR-FREEZE-SC This token specifies whether to disregard the SCREEN COBOL special register STOPMODE, thereby freezing the server class immediately and ignoring incomplete and outstanding requests. def ZPWY-DDL-PAR-FREEZE-SC. 02 ZIGNORESTOPMODE end. token-type ZPWY-DDL-YES-NO. ZIGNORESTOPMODE specifies whether to ignore the STOP-MODE special register and freeze the server class immediately.
ZPWY-MAP-PAR-SHUTDOWN ZPWY-MAP- Definitions ZNODEINDEPENDENTFORMAT indicates the format in which node names are to be returned. The valid values are: ZPWY-VAL-YES Directs the PATHMON process to return only the node names explicitly supplied in previous commands. For fields of type ZSPI-DDL-FNAME32, \* is returned for node names not explicitly specified. For the ZOWNERID field, ZPWY-VALNODEINDOWNERSYS is returned.
ZPWY-MAP- Definitions ZPWY-MAP-PAR-START-PATHWAY2 ZMODE specifies the amount of force to be used when shutting down the Pathway subsystem. Each level is progressively more forceful, and faster, than the previous level. The valid values are: ZPWY-VAL-ORDERLY Allows all transactions currently in progress to complete before the subsystem is stopped. 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.
ZPWY-MAP-PAR-STATS-SCLM ZPWY-MAP- Definitions ZPWY-VAL-YES for a cold start, specifies to start the subsystem regardless of whether a PATHMON configuration file is present. The PATHMON process overwrites the existing PATHMON configuration file with the current configuration information. For a cool start, specifies to use the existing PATHMON configuration file to restart the subsystem. Any unexpected PATHMON process name in the PATHCTL file is ignored.
ZPWY-MAP-PAR-STATUS-SC ZPWY-MAP- Definitions ZPWY-MAP-PAR-STATUS-SC This token specifies the state of the server class whose status you are requesting. def ZPWY-DDL-PAR-STATUS-SC. 02 ZFREEZESTATE token-type ZPWY-DDL-FRZSTATESELVALUE. end. ZFREEZESTATE indicates for which state the status is requested. The valid values are: ZPWY-VAL-ANY Status is requested for any state. ZPWY-VAL-FROZEN Status is requested for server classes in the FROZEN state.
ZPWY-MAP-SEL-LM ZPWY-MAP- Definitions This token is optional. However, if you supply the token in a command buffer, you must assign a value. ZPWY-MAP-SEL-LM This token specifies the name of a LINKMON process. The token fields are described under ZPWY-DDL-LMNAME on page 5-4. def ZPWY-DDL-SEL-LM. 02 ZNAME 03 ZLINKMON 03 ZFILLER-1 end. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. When returned in a response buffer, this token specifies the LINKMON process that was acted upon.
ZPWY-MAP- Definitions ZPWY-MAP-SEL-SCASSIGN ZPWY-MAP-SEL-SCASSIGN This token specifies the associated server class and the name to which a file name and file attributes are assigned. The token fields are described under ZPWY-DDLSCASSIGNNAME on page 5-5. def ZPWY-DDL-SEL-SCASSIGN. 02 ZNAME. 03 ZSERVERCLASS token-type 03 FILLER token-type 03 ZLOGICALUNIT. 04 ZPROGRAMUNIT token-type 04 FILLER token-type 04 ZLOGICALFILE token-type 04 FILLER-1 token-type end. ZPWY-DDL-OBJECT-NAME. ZPWY-DDL-FILLER.
ZPWY-MAP-SEL-SCLM ZPWY-MAP- Definitions ZPWY-MAP-SEL-SCLM This token specifies the name of a server class and the name of the LINKMON process to which that server class is linked. The token fields are described under ZPWY-DDL-SCLMNAME on page 5-6. def ZPWY-DDL-SEL-SCLM. 02 ZNAME. 03 ZSERVERCLASS 03 FILLER-1 03 ZLINKMON 03 FILLER-1 end. token-type token-type token-type token-type ZPWY-DDL-OBJECT-NAME. !r ZPWY-DDL-FILLER. ZPWY-DDL-OBJECT-NAME. !r ZPWY-TYP-FILLER.
ZPWY-MAP- Definitions ZPWY-MAP-SEL-SCSTARTUP When returned in a response buffer, this token specifies the associated server class and the specific server process acted upon. ZPWY-MAP-SEL-SCSTARTUP This token specifies the name of a server startup string and the associated server class. The token fields are described under ZPWY-DDL-SCSTARTUPNAME on page 5-7. def ZPWY-DDL-SEL-SCSTARTUP. 02 ZNAME. 03 ZSERVERCLASS token-type ZPWY-DDL-OBJECT-NAME. !r 03 FILLER-1 token-type ZPWY-DDL-FILLER. end.
ZPWY-MAP-STATS-SC ZPWY-MAP- Definitions ZPWY-MAP-STATS-SC This token reports statistics on a server class. def ZPWY-DDL-STATS-SC. 02 ZSTATSTIME TIMESTAMP. 02 ZQUEUEINFO. 03 ZREQCNT 03 ZWAITS 03 ZMAXWAITS 03 ZAGGREGATEWAITS 03 ZDYNAMICLINKS 02 ZIOINFO. 03 ZSEND. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZREPLY. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 02 ZPERFINFO. 03 ZAGGREGATE. 04 ZTOTALMEASCOUNT 04 ZAVGRESP 04 ZMAXRESP 04 ZMINRESP 04 ZSUMOFSQUARES 03 ZFREQTABLE.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-SC ZREQCNT is the number of requests to the server class that could not be satisfied immediately. ZWAITS is the total number of send requests that the link manager queued when one or more other requests were already queued for the server class. To find the percentage of send requests that waited, multiply ZWAITS by 100 and divide the result by ZREQCNT.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-SC ZMAXSIZE is the size, in bytes, of the largest amount of data transferred in a send statement during the interval that the link manager reports these statistics. ZAGGREGATESIZE is the total size, in bytes, of the data transferred in a send statement during the interval that the link manager reports these statistics. To find the average size, divide ZAGGREGATESIZE by ZIOS. ZIOS is the number of I/O operations to the servers in this server class.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-SC captured by starting and stopping internal clocks at initiation and termination of SEND statements. The limits imposed on measurement collection are: • • • • Measurements will stop for any server upon the 99,999,999th measurement. Any measurement greater than 99,999,999.99 seconds is discarded. After a measurement counter reaches 99,999,999.99 seconds, measurementcollection for this server class stops. Response times are reported in microseconds.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-SC ZFREQTABLE reports supplemental statistics on the completion of SCREEN COBOL SEND statements within a given time interval. This field is relevant only if you are using the Pathway/iTS product. The supplemental information is contained in the frequency distribution table; a separate frequency distribution table is generated for each server class. This information is used to determine the times of peak load for your system.
ZPWY-MAP-STATUS-LM ZPWY-MAP- Definitions ZPWY-MAP-STATUS-LM This token reports status information on a LINKMON process linked to a Pathway subsystem server class. def ZPWY-DDL-STATUS-LM. 02 ZSTATUSTIME 02 ZSTATE VALUE. 02 ZERRORINFO. 03 ZERROR 03 ZINFO 02 ZPROCESS end. token-type ZSPI-DDL-TIMESTAMP. token-type ZPWY-DDL-OBJSTATEtoken-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-CRTPID. ZSTATUSTIME gives the time this status was collected, as a four-word GMT timestamp.
ZPWY-MAP-STATUS-PATHWAY ZPWY-MAP- Definitions ZPWY-MAP-STATUS-PATHWAY This token reports the number of objects in a Pathway subsystem in each class in each possible state. def ZPWY-DDL-STATUS-PATHWAY. 02 ZSTATUSTIME 02 ZEXTERNALTCPS. 03 ZRUNNING 02 ZLINKMONS. 03 ZRUNNING 02 ZPATHCOMS. 03 ZRUNNING 02 ZSERVERCLASSES. 03 ZRUNNING 03 ZSTOPPED 03 ZTHAWED 03 ZFROZEN 03 ZFREEZEPENDING 02 ZSERVERPROCESSES. 03 ZRUNNING 03 ZSTOPPED 03 ZPENDING 02 ZSPI. 03 ZRUNNING 02 ZTCPS.
ZPWY-MAP-STATUS-PATHWAY ZPWY-MAP- Definitions ZLINKMONS reports the number of LINKMON processes. It includes: ZRUNNING reports the number of LINKMON processes that are running. ZPATHCOMS reports the number of PATHCOM processes. It includes: ZRUNNING reports the number of PATHCOM processes that are running. ZSERVERCLASSES reports the number of server classes.
ZPWY-MAP-STATUS-PATHWAY ZPWY-MAP- Definitions ZTCPS reports the number of Pathway/iTS TCPs. It includes: ZRUNNING The number of Pathway/iTS TCPs that are running and capable of controlling Pathway/iTS TERM objects ZSTOPPED The number of Pathway/iTS TCPs that are stopped ZPENDING The number of Pathway/iTS TCPs that have received a STOP command and are stopping For more information about TCPs, see the TS/MP System Management Manual.
ZPWY-MAP-STATUS-PM ZPWY-MAP- Definitions ZSHUTDOWNFAILED indicates the date and time the PATHMON process encountered an error while trying to shut down. ZSHUTDOWNSTARTED indicates the date and time the PATHMON process started actively shutting down the Pathway subsystem. ZPWY-MAP-STATUS-PM This token reports status information on the PATHMON process, the PATHMON configuration file, and the logging files. def ZPWY-DDL-STATUS-PM. 02 ZSTATUSTIME 02 ZPATHMONSTATE 02 ZPATHCTL.
ZPWY-MAP-STATUS-PM ZPWY-MAP- Definitions ZSTATE indicates whether the configuration file is open. The valid values are: ZPWY-VAL-CLOSED The file is closed. ZPWY-VAL-OPEN The file is open. ZFILE contains the name of the PATHMON configuration file. ZERROR contains the number of the last error for the PATHMON configuration file. ZLOG1INFO reports information about the LOG1 file. It has: ZSTATE indicates the state of the log file. The valid values are: ZPWY-VAL-CLOSED The file is closed.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-PMREQUESTER ZPWY-MAP-STATUS-PMREQUESTER This token reports status information on a specific requester process. def ZPWY-DDL-STATUS-PMREQUESTER. 02 ZSTATUSTIME token-type ZSPI-DDL-TIMESTAMP. 02 ZABORTPENDING token-type ZPWY-DDL-YES-NO. 02 ZREQTYPE token-type ZPWY-DDL-REQTYPEVALUE. 02 ZGUARDIANPID token-type ZSPI-DDL-CRTPID. 02 ZGUARDIANPAID token-type ZSPI-DDL-BYTE-PAIR. 02 ZWAIT token-type ZPWY-DDL-REQWAIT-VALUE. 02 ZWAITOBJECT token-type ZPWY-DDL-CHAR35.
ZPWY-MAP-STATUS-PMREQUESTER ZPWY-MAP- Definitions ZGUARDIANPID gives the process ID of the requester. ZGUARDIANPAID gives the process-accessor ID of the requester. ZWAIT indicates the reason a request is waiting. The valid values are: ZPWY-VAL-NONE The request is not waiting. ZPWY-VAL-IODONE The request is waiting for an I/O operation to complete. ZPWY-VAL-LOCK The request is waiting for an object that is locked by another requester.
ZPWY-MAP-STATUS-SC ZPWY-MAP- Definitions ZPWY-MAP-STATUS-SC This token reports status information on a server class. def ZPWY-DDL-STATUS-SC. 02 ZSTATUSTIME 02 ZFREEZESTATE 02 ZERRORINFO 03 ZERROR 03 ZINFO 02 ZRUNNING 02 ZERRORINFO2 03 ZERROR2 03 ZINFO2 03 ZDETAIL2 end. token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-DDL-TIMESTAMP. ZPWY-DDL-FRZSTATE-VALUE. ZPWY-DDL-ERROR-INFO. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZPWY-DDL-ERRINFO2.
ZPWY-MAP-STATUS-SCPROCESS ZPWY-MAP- Definitions ZPWY-MAP-STATUS-SCPROCESS This token reports status information on a server process. def ZPWY-DDL-STATUS-SCPROCESS. 02 ZSTATUSTIME token-type 02 ZSTATE token-type 02 ZPROCESS token-type 02 ZERRORINFO. 03 ZERROR token-type 03 ZINFO token-type 02 ZLINKS token-type 02 ZWEIGHT token-type 02 ZERRORINFO2 token-type 03 ZERROR2 token-type 03 ZINFO2 token-type 03 ZDETAIL2 token-type end. ZSPI-DDL-TIMESTAMP. ZPWY-DDL-OBJSTATE-VALUE. ZSPI-DDL-CRTPID. ZSPI-DDL-INT.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-SCPROCESS ZLINKS is the number of the links to the server from link managers, such as LINKMON processes or ACS subsystem processes and Pathway/iTS TCPs. For more information about TCPs, see the Pathway/iTS System Management Manual and the Pathway/iTS Management Programming Manual. ZWEIGHT is the use of the server compared to the use of other servers in the server class.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-SCPROCESS HP NonStop TS/MP Management Programming Manual—540082-005 7- 56
8 Pathway Subsystem Control Commands This section describes the commands that enable you to define and control the PATHMON process and the Pathway subsystem: Commands Object Types ZPWY-CMD-CONTROL ZPWY-OBJ-PM ZPWY-CMD-GETVERSION ZSPI-VAL-NULL-OBJECT-TYPE ZPWY-OBJ-PM ZPWY-CMD-INFO ZPWY-OBJ-PATHCTL ZPWY-OBJ-PATHWAY ZPWY-CMD-SHUTDOWN2 ZPWY-OBJ-PATHWAY ZPWY-CMD-START ZPWY-OBJ-PATHWAY ZPWY-CMD-STATUS ZPWY-OBJ-LM ZPWY-OBJ-PATHWAY ZPWY-OBJ-PM ZPWY-OBJ-PMREQUESTER ZPWY-CMD-STOP ZPWY-OBJ-PATHWAY ZPWY-
CONTROL PM Pathway Subsystem Control Commands CONTROL PM Use the CONTROL PM command to change specific attributes of the PATHMON process while it is running and to record the changes in the PATHMON configuration file. Continuation You cannot use continuation with this command. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29.
Pathway Subsystem Control Commands CONTROL PM 3. Writes the information to $0. The PATHMON process writes error information, status information, or both to $0 depending on what was specified for the initial log file with the ZSTATUS field. Additionally, the PATHMON process writes the information to $0 in the same format (that is, event messages or text) specified for the initial log file with the ZEVENTFORMAT field.
Pathway Subsystem Control Commands • • CONTROL PM When you cool start a Pathway subsystem (that is, when you use a pre-existing configuration file to start a Pathway subsystem) after using the CONTROL PM command, the PATHMON process uses the values you changed with the CONTROL PM command. When the creation of a backup process fails more than ten times, the PATHMON process delays trying to create a backup process. The delay is 1 minute if stopped 11 times, 2 minutes if stopped 12 times, and so forth.
GETVERSION Pathway Subsystem Control Commands GETVERSION Use the GETVERSION command to return the version of the PATHMON process. Continuation You cannot use continuation with this command. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions.
INFO PATHCTL Pathway Subsystem Control Commands Object Type ZPWY-OBJ-PM Tokens in Response Buffer ZSPI-TKN-SERVER-BANNER token-type ZSPI-TYP-CHAR50. Consideration The value of ZSPI-TKN-SERVER-BANNER is intended only for display, not for programs to examine. Its format might change in future versions of the product. Therefore, application programs should not extract information from this token value.
INFO PATHWAY Pathway Subsystem Control Commands INFO PATHWAY Use the INFO PATHWAY command to return the attribute values currently in effect for the Pathway subsystem. For object attributes not yet defined, this command returns the default value (for optional fields) or a null value (for required fields). The values returned by INFO PATHWAY encompass both the PATHMON process and Pathway subsystem parameters (established by the SET PATHMON and SET PATHWAY commands in the PATHCOM interface).
SHUTDOWN2 PATHWAY Pathway Subsystem Control Commands SHUTDOWN2 PATHWAY Use the SHUTDOWN2 PATHWAY command to stop a Pathway subsystem. This command corresponds to the PATHCOM SHUTDOWN2 command. The SHUTDOWN2 command cannot be reversed; in other words, once you have initiated the shutdown process, you cannot stop that process. Continuation You cannot use continuation with this command.
SHUTDOWN2 PATHWAY Pathway Subsystem Control Commands • • • • • • These commands are disabled when the PATHMON process is in the ZPWY-VAL-SHUTDOWN state: Command Type Commands Disabled During SHUTDOWN State Control commands START SWITCH PM Server class commands ADD ALTER DELETE START TCP Commands (Pathway/iTS product only) ADD ALTER DELETE START SWITCH Program commands (Pathway/iTS product only) ADD ALTER DELETE START Terminal commands (Pathway/iTS product only) ADD ALTER DELETE INSPECT
START PATHWAY Pathway Subsystem Control Commands START PATHWAY Use the START PATHWAY command to start a Pathway subsystem, either by creating a new PATHMON configuration file (cold start), replacing an existing configuration file (cold start with ZIGNORE), or using the configuration in the existing configuration file (cool start).
Pathway Subsystem Control Commands START PATHWAY Tokens in Response Buffer For START PATHWAY, common error values for ZSPI-TKN-RETCODE are: 1003 (ZPWY-ERR-PM-ALREADYSTARTED) indicates that the PATHMON process has already been started. 1008 (ZPWY-WRN-PM-BADPATHCTL) indicates that the PATHMON configuration file is empty or does not contain a valid state. 1031 (ZPWY-ERR-PM-MISSINGPARAM) indicates that a required Pathway configuration parameter was not defined.
STATUS LM Pathway Subsystem Control Commands STATUS LM Use the STATUS LM command to display information about LINKMON processes or ACS subsystem processes that have links to server processes. Continuation To obtain the status of more than one LINKMON process or ACS subsystem processes, initialize the ZLM field in ZPWY-DDL-SEL-LM to ZPWY-VAL-ALLLM. Reissue the command continually by using the context token returned by the PATHMON process until no data is returned in the reply buffer.
STATUS PATHWAY Pathway Subsystem Control Commands STATUS PATHWAY Use the STATUS PATHWAY command to display the number of PATHMONenvironment objects that are in each possible state. This command provides an overview of the Pathway subsystem. Continuation You cannot use continuation with this command. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29.
STATUS PMREQUESTER Pathway Subsystem Control Commands Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions. Command ZPWY-CMD-STATUS Object Type ZPWY-OBJ-PM Tokens in Response Buffer ZPWY-MAP-STATUS-PM token-type ZPWY-DDL-STATUS-PM.
STOP PATHWAY Pathway Subsystem Control Commands Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions. Command ZPWY-CMD-STATUS Object Type ZPWY-OBJ-PMREQUESTER Tokens in Command Buffer ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-PMREQUESTER token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SELPMREQUESTER.
STOP PATHWAY Pathway Subsystem Control Commands Continuation You cannot use continuation with this command. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions. Command ZPWY-CMD-STOP Object Type ZPWY-OBJ-PATHWAY Tokens in Response Buffer ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT.
STOP PM Pathway Subsystem Control Commands For more information about continuation, see Specifying Continuation on page 3-17. For more information about Pathway/iTS commands, see the Pathway/iTS Management Programming Manual. • • To implement the equivalent of the PATHCOM SHUTDOWN ! command, add an ABORT TERM command for all TERMs (specifying continuation) after the STOP TERM command in the previous sequence.
Pathway Subsystem Control Commands SWITCH PM Consideration All processes started by the PATHMON process and still running when the STOP PM command completes successfully are orphaned. Orphaned processes are processes no longer recognized by the PATHMON process. To avoid orphaned processes, first use the STATUS PATHWAY command, before executing the STOP PM command, to determine what type of processes are running.
Pathway Subsystem Control Commands SWITCH PM Considerations • • • Use the Guardian LOOKUPPROCESS procedure to identify the CPUs in which the PATHMON primary and backup processes are actually running after you have repeatedly issued the SWITCH PM command. To record the CPU definitions in the PATHMON configuration file, use the CONTROL PM command. Whenever the PATHMON primary or backup process is stopped more than 10 times by a TACL STOP command, the PATHMON process delays creating a backup process.
Pathway Subsystem Control Commands HP NonStop TS/MP Management Programming Manual—540082-005 8- 20 SWITCH PM
9 Server Class Commands This section describes the SPI commands that define and control server classes and server processes within a Pathway subsystem; the commands are listed in alphabetical order.
ADD SC Server Class Commands ADD SC Use the ADD SC command to enter the name and description of a server class into the PATHMON configuration file. For guidelines on calculating appropriate configuration values for your site, see the TS/MP System Management Manual. Continuation You cannot use continuation with this command to add all server classes; you must explicitly add each server class by name.
ADD SC Server Class Commands For server classes having OSS processes, the following tokens and fields in ZPWY-MAP-DEF-SC are required: ZPROCESSTYPE and ZDEFAULTVOLUME. ZPWY-TKN-DEF-SCPROGRAMOSS is also required.
Server Class Commands ADD SC For descriptions of all error-token values and their associated error lists, see Section 10, Event Management.. For considerations regarding errors that can occur when a server process is in debug mode, see the TS/MP Pathsend and Server Programming Manual. Considerations • • • The tokens and fields included in the command buffer must be valid for the process type defined for the server class.
ADD SCASSIGN Server Class Commands • Here is an example of a partial configuration for a server: ZMAXLINKS 10 ZLINKDEPTH 2 ZMAXSERVERS 7 ZNUMSTATIC 2 ZCREATEDELAY 10,000,000 ZDELETEDELAY 300,000,000 (microsecond value for 10 seconds) (microsecond value for 5 minutes) Each server process in this configuration can have up to 10 links from Pathway subsystem or Pathsend requesters (ZMAXLINKS has a value of 10).
ADD SCASSIGN Server Class Commands Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions. Command ZPWY-CMD-ADD Object Type ZPWY-OBJ-SCASSIGN Tokens in Command Buffer ZPWY-MAP-SEL-SCASSIGN !r ZPWY-MAP-DEF-SCASSIGN !r token-type ZPWY-DDL-SEL-SCASSIGN. token-type ZPWY-DDL-DEF-SCASSIGN.
ADD SCDEFINE Server Class Commands • To specify node independence for server class attributes, specify \* for node names or omit node names and set ZNODEINDEPENDENT to ON in the START PATHWAY command. ADD SCDEFINE Use the ADD SCDEFINE command to add a DEFINE definition for a given server class to the PATHMON configuration file. The DEFINE specifies the default volume and subvolume and the files used by the server processes.
ADD SCPARAM Server Class Commands Tokens in Response Buffer For ADD SCDEFINE, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1012 ZPWY-ERR-PM-DUPNAME A DEFINE message that has the same name as the name assigned to ZDEFINE already exists. 1109 ZPWY-ERR-PMTOOMANYSCDEFINE The value specified for ZMAXDEFINES was reached. For descriptions of all error-token values and their associated error lists, see Section 10, Event Management.
ADD SCPARAM Server Class Commands Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions. Command ZPWY-CMD-ADD Object Type ZPWY-OBJ-SCPARAM Tokens in Command Buffer ZPWY-MAP-SEL-SCPARAM !r ZPWY-MAP-DEF-SCPARAM !r token-type ZPWY-DDL-SEL-SCPARAM. token-type ZPWY-DDL-DEF-SCPARAM.
ADD SCPROCESS Server Class Commands ADD SCPROCESS Use the ADD SCPROCESS command to add a process name for a given server process to the PATHMON configuration file. Continuation You cannot use continuation with this command to add all server process names; you must explicitly add each server process name. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29.
Server Class Commands ADD SCSTARTUP Considerations • An associative server is configured with the ZASSOCIATIVE field in ZPWY-DDLDEF-SCPROCESS set to ZPWY-VAL-ON. When changing the definition of an associative server, make sure you make the changes everywhere the associative server is defined. Otherwise, you cannot be assured that the new definition will be implemented or permanent. For more information on associative servers, see Server Objects on page 3-26.
ADD SCSTARTUP Server Class Commands Object Type ZPWY-OBJ-SCSTARTUP Tokens in Command Buffer ZPWY-MAP-SEL-SCSTARTUP !r ZPWY-MAP-DEF-SCSTARTUP !r token-type ZPWY-DDL-SEL-SCSTARTUP. token-type ZPWY-DDL-DEF-SCSTARTUP. Tokens in Response Buffer ZPWY-MAP-SEL-SCSTARTUP ZSPI-TKN-RETCODE token-type ZPWY-DDL-SEL-SCSTARTUP. token-type ZSPI-TYP-INT.
ALTER SC Server Class Commands ALTER SC Use the ALTER SC command to change the attribute values of a server class that was previously added to the PATHMON configuration file. All server processes in the server class must be in the STOPPED state before you issue this command. Continuation You cannot use continuation with this command to alter all server classes; you must explicitly alter each server class by name.
ALTER SC Server Class Commands For server classes having OSS processes, the following tokens and fields in ZPWY-MAP-DEF-SC are required: ZPROCESSTYPE and ZDEFAULTVOLUME. ZPWY-TKN-DEF-SCPROGRAMOSS is alo required.
ALTER SC Server Class Commands Considerations • For ALTER commands, the values for tokens and fields omitted from the command buffer remain unchanged. Reset values for each field are predefined. These values are described in Section 3, SPI Programming Considerations. To reset ZDEFAULTVOLUME, ZGUARDIANLIB, ZHOMETERM, ZIN, ZOUT, or ZPROGRAM with the TACL program, you must use the #SETBYTES built-in function. For more information, see the SPI Programming Manual.
ALTER SCASSIGN Server Class Commands ALTER SCASSIGN Use the ALTER SCASSIGN command to change the attributes of a server ASSIGN message. The attributes are the same as those for the ASSIGN parameter of the PATHCOM SET SERVER command. All server processes in the server class must be in the STOPPED state to use this command. Continuation You cannot use continuation with this command to alter all server ASSIGN messages; you must explicitly alter each ASSIGN message by name.
ALTER SCDEFINE Server Class Commands • To perform the equivalent of the PATHCOM ALTER SERVER, RESET ASSIGN command, use the DELETE SCASSIGN command. ALTER SCDEFINE Use the ALTER SCDEFINE command to change a server class DEFINE. Continuation You cannot use continuation with this command to alter either all DEFINE names or all associated server classes; you must individually alter each server DEFINE.
ALTER SCPARAM Server Class Commands ALTER SCPARAM Use the ALTER SCPARAM command to change the attributes of a server PARAM message. The attributes are the same as those specified for the PARAM parameter of the PATHCOM SET SERVER command. All server processes in the server class must be in the STOPPED state to use this command. Continuation You cannot use continuation with this command to alter all parameters; you must explicitly alter each parameter by name.
Server Class Commands ALTER SCPROCESS ALTER SCPROCESS Use the ALTER SCPROCESS command to change the attributes of a server process. The attributes are the same as those specified with PROCESS parameter of the PATHCOM SET SERVER command. All server processes in the server class must be in the STOPPED state to use this command. Continuation You cannot use continuation with this command to alter all server process names; you must explicitly alter each server process name.
Server Class Commands ALTER SCSTARTUP When changing the definition of an associative server, make sure you make the changes everywhere the associative server is defined. Otherwise, you cannot be sure that the new definition will be implemented or permanent. For more information on associative servers, see Server Objects on page 3-26. • • To specify node independence for server class attributes, specify \* for node names or omit node names and set ZNODEINDEPENDENT to ON in the START PATHWAY command.
DELETE SC Server Class Commands Considerations • • For ALTER commands, the values for tokens and fields omitted from the command buffer remain unchanged. To perform the equivalent of the PATHCOM ALTER SERVER, RESET STARTUP command, use the DELETE SCSTARTUP command.
Server Class Commands DELETE SCASSIGN Consideration Deleting an SC object also deletes all associated SCASSIGN, SCDEFINE, SCPARAM, SCPROCESS, and SCSTARTUP objects. DELETE SCASSIGN Use the DELETE SCASSIGN command to delete the definition for a server ASSIGN message from the PATHMON configuration file. All server processes in the server class must be frozen and then stopped to use this command.
Server Class Commands DELETE SCASSIGN Considerations • • Deleting an SC object causes all associated SCASSIGN objects to be deleted— you do not need to issue the DELETE SCASSIGN command. This command is equivalent to the PATHCOM ALTER SERVER, RESET ASSIGN command.
Server Class Commands DELETE SCDEFINE DELETE SCDEFINE Use the DELETE SCDEFINE command to delete a DEFINE definition from the PATHMON configuration file. All server processes in the server class must be frozen and then stopped to use this command. Continuation To delete all DEFINEs for a single server class, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SCDEFINE to the name of the server class, and initialize the ZDEFINE field to ZPWY-VAL-ALLSCDEFINE.
Server Class Commands DELETE SCPARAM DELETE SCPARAM Use the DELETE SCPARAM command to delete the definition of a server PARAM attribute from the PATHMON configuration file. All server processes in the server class must be frozen and then stopped to use this command. Continuation To delete all PARAM parameters for a single server class, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SCPARAM to the server class name and initialize the ZPARAM field to ZPWY-VAL-ALLSCPARAM.
DELETE SCPROCESS Server Class Commands DELETE SCPROCESS Use the DELETE SCPROCESS command to delete the attributes associated with a server process name from the PATHMON configuration file. The attributes are the same as those in the PROCESS parameter of the PATHCOM SET SERVER command. All server processes in the server class must be frozen and then stopped to use this command.
Server Class Commands • DELETE SCSTARTUP This command is equivalent to the PATHCOM ALTER SERVER, RESET PROCESS command. DELETE SCSTARTUP Use the DELETE SCSTARTUP command to delete the startup string from the server definition in the PATHMON configuration file. All server processes in the server class must be frozen and then stopped to use this command. Continuation You cannot use continuation with this command to delete all startup strings. There is only one SCSTARTUP per SC object.
FREEZE SC Server Class Commands FREEZE SC Use the FREEZE SC command to prohibit all link managers, such as LINKMON processes or ACS subsystem processes and Pathway/iTS TCPs, from sending requests to a server class. If a server has incomplete requests (requests for which links have not yet been granted) or outstanding requests (such as an active dialog), the PATHMON process cannot freeze the server class until after these requests complete.
FREEZE SC Server Class Commands Tokens in Response Buffer For FREEZE SC, a common error value for ZSPI-TKN-RETCODE is: Error Number Error Token Description 1057 ZPWY-ERR-PM-ALREADYFROZEN The server class is already frozen. For descriptions of all error-token values and their associated error lists, see Section 10, Event Management.
INFO SC Server Class Commands INFO SC Use the INFO SC command to obtain the attribute values defined in the PATHMON configuration file for a server class. Continuation To obtain information for all server classes, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SC to ZPWY-VAL-ALLSC. Reissue the command continually by using the context token returned by the PATHMON process until no data is returned in the reply buffer. For more information, see Specifying Continuation on page 3-17.
Server Class Commands INFO SC Considerations • • • • Information about ASSIGN messages, DEFINEs, PARAM messages, and the startup message string can be obtained with the INFO SCASSIGN, INFO SCDEFINE, INFO SCPARAM, and INFO SCSTARTUP commands, respectively. To obtain the default values for server class attributes, issue the INFO SC command and assign a null value to the ZSERVERCLASS field in ZPWY-DDLSEL-SC.
INFO SCASSIGN Server Class Commands INFO SCASSIGN Use the INFO SCASSIGN command to obtain the attribute values for a server ASSIGN message defined in the PATHMON configuration file. The attributes are the same as those for the ASSIGN parameter of the PATHCOM SET SERVER command.
INFO SCDEFINE Server Class Commands INFO SCDEFINE Use the INFO SCDEFINE command to obtain the attribute values for a DEFINE recorded in the PATHMON configuration file. The attributes are the same as those for the DEFINE parameter of the PATHCOM SET SERVER command. Continuation To obtain information for all DEFINEs for a single server class, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SCDEFINE to the name of the server class, and initialize the ZDEFINE field to ZPWY-VAL-ALLSCDEFINE.
INFO SCPARAM Server Class Commands INFO SCPARAM Use the INFO SCPARAM command to obtain the attribute value for a server PARAM parameter defined in the PATHMON configuration file. The attribute is the same as for the PARAM parameter of the PATHCOM SET SERVER command. Continuation All the individual PARAMs defined in an SCPARAM object for a specific server class are bundled into a single PARAM message.
INFO SCPROCESS Server Class Commands INFO SCPROCESS Use the INFO SCPROCESS command to obtain the attribute values for a server process defined in the PATHMON configuration file. The attributes are the same as those for the PROCESS parameter of the PATHCOM SET SERVER command. Continuation To obtain information for all server processes, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SCPROCESS to the server class name, and initialize the ZPROCESS field to ZPWY-VAL-ALLSCPROCESS.
Server Class Commands • INFO SCSTARTUP When ZPWY-MAP-PAR-INFO is present in the command buffer and the ZNODEINDEPENDENT field is set to ZPWY-VAL-YES, the INFO SCPROCESS command returns all explicitly defined node names for FNAME32 field types. \* is returned for all node names specified with \* and node names that have not been specified but which have defaulted to \* because ZNODEINDPEENDENT is set to ON. The ZOWNERID field is returned with the value ZPWY-VALNODEINDOWNERSYS.
START SC Server Class Commands Tokens in Command Buffer ZPWY-MAP-SEL-SCSTARTUP !r token-type ZPWY-DDL-SEL-SCSTARTUP. Tokens in Response Buffer ZPWY-MAP-SEL-SCSTARTUP ZPWY-MAP-DEF-SCSTARTUP token-type ZPWY-DDL-SEL-SCSTARTUP. token-type ZPWY-DDL-DEF-SCSTARTUP. Considerations • • There is only one startup string per server class. There are no defaults for startup strings. START SC Use the START SC command to initiate operation of the static servers in the server class.
START SC Server Class Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SC ZSPI-TKN-RETCODE token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SC. token-type ZSPI-TYP-INT. Tokens in Response Buffer For START SC, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1003 ZPWY-ERR-PMALREADYSTARTED The server class is already started.
Server Class Commands START SCPROCESS START SCPROCESS Use the START SCPROCESS command to start a single named server process in a given server class. Continuation To start all server processes for a server class, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SCPROCESS to the name of the server class, and initialize the ZPROCESS field to ZPWY-VAL-ALLSCPROCESS. Reissue the command continually by using the context token returned by the PATHMON process until no data is returned in the reply buffer.
STATS SCLM Server Class Commands Tokens in Response Buffer For START SCPROCESS, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1003 ZPWY-ERR-PMALREADYSTARTED The specified file cannot be used for a home terminal. 1038 ZPWY-ERR-PMNEWPROCESS An error occurred while the PATHMON process was attempting to create a new process. 1091 ZPWY-ERR-PMINVALIDHOMETERM An error occurred while the PATHMON process was attempting to create a new process for the server class.
STATS SCLM Server Class Commands Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-29. For descriptions of tokens and fields, see Section 4, SPI and EMS Standard Definitions through Section 7, ZPWY-MAPDefinitions. Command ZPWY-CMD-STATS Object Type ZPWY-OBJ-SCLM Tokens in Command Buffer ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SCLM !r ZPWY-MAP-PAR-STATS-SCLM SCLM. token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SCLM.
STATUS SC Server Class Commands STATUS SC Use the STATUS SC command to obtain the current status of a server class. Status information on an individual server process can be obtained with the STATUS SCPROCESS command (the equivalent of the PATHCOM STATUS SERVER, DETAIL command). The STATUS SC command returns status information for server classes linked to link managers, such as LINKMON processes or ACS subsystem processes and Pathway/iTS TCPs.
STATUS SCPROCESS Server Class Commands Considerations • • • To perform the equivalent of the PATHCOM STATUS SERVER command, use the STATUS SC command. To perform the equivalent of the PATHCOM STATUS SERVER, DETAIL command, use the STATUS SC command and the STATUS SCPROCESS command. To perform the equivalent of the PATHCOM STATUS SERVER, PROCESSES command, use the STATUS SC command (using the optional parameter, ZPWYPAR-STATUS-SC) and the STATUS TCPLINK command.
STOP SC Server Class Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-SCPROCESS token-type ZPWY-DDL-SEL-SCPROCESS. ZPWY-MAP-STATUS-SCPROCESS token-type ZPWY-DDL-STATUSSCPROCESS. Consideration Use this command with the STATUS SC command to perform the equivalent of the PATHCOM STATUS, DETAIL command. STOP SC Use the STOP SC command to stop all server processes in the server class.
THAW SC Server Class Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SC ZSPI-TKN-RETCODE token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SC. token-type ZSPI-TYP-INT. Tokens in Response Buffer For STOP SC, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1004 ZPWY-ERR-PMALREADYSTOPPED The server class is already stopped. 1062 ZPWY-ERR-PMMUSTBEFROZEN The server class must be frozen before you issue a STOP SC command.
THAW SC Server Class Commands Continuation To thaw all server classes, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SC to ZPWY-VAL-ALLSC. Reissue the command continually by using the context token returned by the PATHMON process until no data is returned in the reply buffer. When you specify continuation, responses are only returned for server classes that are frozen. For more information, see Specifying Continuation on page 3-17.
Server Class Commands • THAW SC For an application running under Pathway/iTS, the TCP performs these actions after the THAW command resumes the activity of a terminal that was in TMF transaction mode: 1. Directs the TMF software to restart the transaction at the BEGINTRANSACTION statement and to assign a new transaction identifier 2.
Server Class Commands HP NonStop TS/MP Management Programming Manual—540082-005 9- 48 THAW SC
10 Event Management This section describes the TS/MP interface to the Event Management Service (EMS) and describes the functions of the various event and error message tokens. Message Numbers All messages returned by the PATHMON environment are logged by the PATHMON process. However, some messages in some number ranges represent events and errors reported to the PATHMON process by other processes.
Event Management Event Management Programming for Pathway Subsystems For TS/MP, the PATHMON process logs event messages for itself and for LINKMON processes or ACS subsystem processes. For Pathway/iTS, the PATHMON process logs event messages for itself and for the TCPs. You configure event logging using either the PATHCOM LOG1 and LOG2 commands or the programmatic CONTROL PM command.
Console Messages versus Event Messages Event Management Console Messages versus Event Messages The PATHMON process generates error and status messages as console messages and event messages. The event messages produce display-format messages when operated on by the EMSTEXT procedure. Console messages and display-format messages are logically similar, but not identical to each other. Note. Message text can change from version to version.
Event Messages and the ViewPoint Application Event Management Event Messages and the ViewPoint Application Event messages logged to $0 result in a textual display on the ViewPoint screen. Console messages that are logged to $0 are normally also echoed to the ViewPoint application. To avoid duplication, console messages logged to $0 are only included on the ViewPoint display when neither the LOG1 nor the LOG2 command specifies the EVENTFORMAT parameter.
Error Lists and Error Recovery Event Management Error Lists and Error Recovery Pathway subsystem event messages do not contain error lists to describe errors reported by other subsystems. These errors are indicated by simple tokens. For example, when the PATHMON process reports a file system I/O error (such as ZPWYERR-PM-PATHCTLIO), the error value is reported in the token ZPWY-TKN-ERROR. If an error occurs while error or status information is being written to a log file, the PATHMON process: 1.
Additional Programming Considerations Event Management • • • • The Pathway subsystem that generated the event message is uniquely identified by the name of the PATHMON process. The token ZSPI-TKN-MANAGER contains this identification. Event messages are classified as error, status, or warning messages by using the token ZPWY-TKN-EVENTCLASS. The token ZEMS-TKN-EVENTNUMBER distinguishes PATHMON process event messages from link manager event messages.
Header Tokens Event Management • • • Standard Pathway tokens—appear in all Pathway subsystem event messages. Event-specific Pathway tokens—appear in some Pathway subsystem event messages. Nested messages—might appear in some Pathway subsystem event messages.
Standard EMS Token Event Management Table 10-1. Standard EMS Header Tokens (page 2 of 2) Token and Token Type Data Type Description ZEMS-TKN-LOGTIME 64-bit integer Contains the time the collector added the event message to the event log. 16-bit integer Identifies the primary process ID of the PATHMON process. 16-bit unsigned integer Identifies the system where the PATHMON process was running. 16-bit unsigned integer Contains the user ID of the PATHMON process.
Standard SPI Token Event Management Standard SPI Token Table 10-4 lists a standard SPI token that appears in all Pathway subsystem event messages but is not a message-header token; it is an unconditional token. Table 10-4. Standard SPI Token Token Description ZSPI-TKN-MANAGER Contains the process name of the PATHMON process. For more information about this token, see the SPI Programming Manual.
Event-SpecificTokens Event Management Subject Token ZEMS-TKN-SUBJECT-MARK indicates the subject token, which identifies the TS/MP object or file that is most directly involved in the event. The subject token indicates one of these tokens as present in the event-message buffer: TS/MPToken Description ZPWY-TKN-FNAME Event concerns a file. ZPWY-TKN-LMNAME Event concerns a LINKMON process or ACS subsystem processes. ZPWY-TKN-PMNAME Event concerns the PATHMON process.
Nested Messages Event Management Table 10-6.
Example Event Message Event Management Example Event Message Example 10-1 shows an example event message with all the event tokens and example values. The example indicates whether the tokens are unconditional (U), conditional (C), or HP internal (I). Example 10-1. Example Event Message EMSTEXT format of this event message: \SYS.$PM1: ERROR - *1007* LINKMON L\SYS.
Error Messages Event Management Error Messages Most Pathway subsystem errors reported to a management application are returned in the response buffer the application receives from the PATHMON process.
Example Error Lists Event Management Table 10-7. Error List Tokens (page 2 of 2) Token Description ZSPI-TKN-PARM-ERR This token contains the code of the token in error and the offset to the field in error. ZSPI-TKN-PARM-ERR is used for field validation and identifying required fields that are missing. Information about this token appears in the DSM Programming Manual. Tokens Sometimes Present (continued) ZPWY-TKN-ERRCOMMAND This token identifies the command that caused the error.
Example Error Lists Event Management • • • • • • • • • • • The message header, including the command (ZPWY-CMD-START), the object type (ZPWY-OBJ-SC), the version of the PATHMON process, and the subsystem ID ZSPI-TKN-RETCODE, containing the value ZPWY-ERR-PM-ALREADYSTARTED ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR, indicating the Pathway subsystem ID and the value ZPWY-ERR-PM-ALREADYSTARTED ZPWY-TKN-REQCOMMAND, containing ZPWY-CMD-START ZPWY-TKN-REQOBJECTTYPE, containing ZPWY-OBJ-SC ZPWY-TKN-REQSCNAME, containing "
Retrieving and Decoding Event Messages Event Management Retrieving and Decoding Event Messages When using the management programming interface to manage your Pathway subsystem, you can specify a subtype 30 process as an EMS collector. An EMS collector is a type of logging device (as is a log file). Subtype 30 processes, which are supported by the PATHMON process, are nonprivileged processes that simulate terminals and communication devices.
Event-Management Considerations Event Management f. Call EMSGET or EMSGETTKN twice to retrieve the subject of the event message. In the first call, retrieve the subject-mark token (ZEMS-TKNSUBJECT-MARK) to get the token code and index of the token identifying the subject. Then make another call to retrieve the subject token itself. g. Call EMSGET or EMSGETTKN to retrieve the values of other tokens from the event message. h.
Templates Event Management The EMS Manual provides information on how to code, compile, load, and replace filters. Templates Event-message templates are provided with TS/MP. These templates define the text used for displays of event messages by the ViewPoint console application and other console devices and applications. Both source and compiled templates are provided. You can modify the source templates and compile them again if you wish to customize your messages.
11 PATHMON Event Messages This section describes event messages reported by the PATHMON process. The descriptions are given in ascending order by event number; that is, in ascending order by the ZPWY-EVT- values. The PATHMON process logs messages pertaining to TS/MP and Pathway/iTS objects. Message Numbers All messages returned by the PATHMON environment are logged by the PATHMON process.
PATHMON Event Messages Event-Message Format Event-Message Format Each event message in this section includes: • • • • • The number and name of the event message A description of the event message cause A syntax box listing: ° The unconditional and conditional tokens that have specific values for that event message. For a description of each token, see Section 10, Event Management.
Subject Tokens PATHMON Event Messages Subject Tokens Subject tokens (for example, ZPWY-TKN-SCNAME) contain the name of the PATHMON-controlled object that is the subject of the event message. Within the syntax boxes in this section, subject tokens may be presented in the form ZPWY-TKNnnnNAME, where nnn represents any of these TS/MP object types: LM PMREQUESTER SC SCASSIGN SCDEFINE SCLM SCPARAM SCPROCESS SCSTARTUP For descriptions of these object types, see Object Types on page 3-6.
Event-Message Range 1000 Through 1999 PATHMON Event Messages Event-Message Range 1000 Through 1999 Event messages numbered from 1000 through 1999 describe events reported by the PATHMON process. Note that some Pathway subsystem event messages include a Guardian error number. Although the error number is typically identified as a filesystem error, it can also represent a sequential I/O (SIO) error or other specialized error.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1005: ZPWY-EVT-PM-SHUTDOWN The Pathway subsystem has been successfully shut down. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1006: ZPWY-EVT-PM-PMABENDED The PATHMON process aborted due to a fatal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1007: ZPWY-EVT-PM-LINKFAIL A server class link cannot be granted to a link manager. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1011: ZPWY-EVT-PM-DELINKFAIL An error occurred during while a link manager was trying to return a link to a server class. The nested message indicates the reason for the failure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1012: ZPWY-EVT-PM-DUPNAME Either the PATHMON process tried to add an object having a name that already exists, or the PATHMON process tried to start a Pathway/iTS TCP or server process using a process name that is already active within this Pathway subsystem. This message usually indicates that there was an attempt to use an object name or a process name twice.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1013: ZPWY-EVT-PM-EMPTYENTRY An entry that should contain the description of a Pathway object (for example, a server class) is empty. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1015: ZPWY-EVT-PM-ENTRYTYPEMISMATCH An object type does not match the type specified or implied by a request. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1016: ZPWY-EVT-PM-TCPFAIL A TCP stopped abnormally even though a stop command was not issued. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1017: ZPWY-EVT-PM-PATHCTLIO A file-system error (errnum) occurred during an I/O operation to the PATHMON configuration file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1018: ZPWY-EVT-PM-PMSCPROCESSIO A file-system error (errnum) occurred during an I/O operation to the specified server class. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1019: ZPWY-EVT-PM-PMTCPIO A file system error (errnum) occurred during an I/O operation to the specified link manager. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1020: ZPWY-EVT-PM-LOG1IO A file-system error (errnum) occurred during an I/O operation to the LOG1 file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1021: ZPWY-EVT-PM-LOG2IO A file-system error (errnum) occurred during an I/O operation to the LOG2 file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1022: ZPWY-EVT-PM-RECEIVEIO A file-system error (errnum) occurred during an I/O operation to $RECEIVE. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1023: ZPWY-EVT-PM-TCPPMIO A file-system error (errnum) occurred during an I/O operation to the specified link manager. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1024: ZPWY-EVT-PM-BADFILENAME An invalid file name was detected in the definition of the specified object. errnum identifies the file-system error number. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1025: ZPWY-EVT-PM-INTERNAL An internal consistency check failed in the PATHMON process. This error is not fatal. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1026: ZPWY-EVT-PM-BADMSG A message received does not conform to the PATHMON request protocol. This error can be caused by running incompatible versions of PATHCOM, PATHMON, or PATHTCP. The message was received from the process running under the specified user ID. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1027: ZPWY-EVT-PM-LOG1OFF The LOG1 file is closed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-PMNAME. ZSPI-TYP-ENUM.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1028: ZPWY-EVT-PM-LOG1ON The LOG1 file is open. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-PMNAME. ZSPI-TYP-ENUM.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1029: ZPWY-EVT-PM-LOG2OFF The LOG2 file is closed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-PMNAME. ZSPI-TYP-ENUM.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1030: ZPWY-EVT-PM-LOG2ON The LOG2 file is opened. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-PMNAME. ZSPI-TYP-ENUM.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1032: ZPWY-EVT-PM-NODISKSPACE An entry cannot be added because the PATHMON configuration file is full. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1033: ZPWY-EVT-PM-NOFREESPACE There is insufficient space in the PATHMON process’s free-space table. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1034: ZPWY-EVT-PM-NOSCPROCESS The PATHMON process cannot grant a link to a link manager because no server processes are available. Either the link manager is already linked to all server processes in the class, or all processes in the class currently have the maximum number of links defined for the ZMAXLINKS field.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1035: ZPWY-EVT-PM-NAMENOTDEFINED The specified entry does not exist. Either the wrong object name was used or the desired object does not exist. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1036: ZPWY-EVT-PM-SYSNOTDEFINED There is an invalid system name in the definition of the indicated object. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1037: ZPWY-EVT-PM-PARTIALENTRYDEL An extraneous entry, which was in an inconsistent state when PATHMON failed, was deleted from the PATHMON configuration file during a cool start. This message occurs only in response to a Pathway/iTS STATUS TCP or STATUS TERM command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Event Messages Event-Message Range 1000 Through 1999 Effect. These entry token types are deleted upon a cool start: • • • Old copies of entries that were made obsolete as a result of an ALTER command Temporary server process entries that were named by the system Temporary Pathway/iTS TERM objects created by a Pathway/iTS RUN PROGRAM request. This entry type only applies if you are running Pathway/iTS. Recovery. Informational message only; no corrective action is needed.
PATHMON Event Messages Event-Message Range 1000 Through 1999 For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS BOOLEAN. ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME nnnNAME. ZPWY-TKN-EVENTCLASS token-type ZSPI-TYPtoken-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYPtoken-type ZSPI-TYP-ENUM.
PATHMON Event Messages Event-Message Range 1000 Through 1999 UNABLE TO ALLOCATE A PRIV STACK FOR THE PROCESS UNABLE TO LOCK THE PRIV STACK FOR THE PROCESS UNABLE TO ALLOCATE A MAIN STACK FOR THE PROCESS UNABLE TO LOCK THE MAIN STACK OF A NATIVE I/O PROCESS THAT IS CREATED BY COUP format-file-type is one of the following: PROGRAM LIBRARY format-error is one of the following: FILE HAS UNDEFINED DATA BLOCKS FILE NOT FIXED-UP BY BINDER HEADER INITSEGS NOT CONSISTENT WITH SIZE INVALID PEP LIB FILE HAS MAIN PRO
PATHMON Event Messages Event-Message Range 1000 Through 1999 ZPWY-TKN-NEWPROCERROR contains the number of the process creation error. N indicates that this token can occur in a nested error message. ZPWY-TKN-NEWPROCRESULT, ZPWY-TKN-NEWPROCFORMATFILETYPE, ZPWY-TKN-NEWPROCFORMATERROR, and ZPWY-TKN-PROCCREATRESULT are reserved for HP internal use only. N indicates that these tokens can occur in a nested error message. Effect. The new process is not created. Recovery.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1041: ZPWY-EVT-PM-REQUESTHANDLER An error occurred during request initiation for the reason indicated in nestedmessage. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1042: ZPWY-EVT-PM-RESUMEDSTATUS The indicated terminal has resumed processing. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TERMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1043: ZPWY-EVT-PM-STARTEDSTATUS The specified object has started. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-nnnNAME.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1046: ZPWY-EVT-PM-FSERROR A file-system error (errnum) occurred. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-nnnNAME.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1047: ZPWY-EVT-PM-STOPPEDSTATUS The specified object has stopped for the reason indicated in nested-message. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1048: ZPWY-EVT-PM-SUSPENDEDERROR The specified terminal suspended processing due to an error in the program. The reason for the error is indicated in nested-message. This message occurs only in response to a Pathway/iTS STATUS TCP or STATUS TERM command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1049: ZPWY-EVT-PM-SUSPENDEDSTATUS The specified terminal has suspended processing due to a SUSPEND TERM command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TERMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1050: ZPWY-EVT-PM-SYSMSGHANDLER An error occurred while the PATHMON process was processing a system message. The error is indicated by nested-message. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1051: ZPWY-EVT-PM-REQUESTTABLEFULL There is not enough room in the requester table for the PATHMON process to communicate with the link manager. (A maximum of 800 of the sum of the attributes ZMAXEXTERNALTCPS, ZMAXLINKMONS, ZMAXPATHCOMS, ZMAXTCPS, and ZMAXSPI or a maximum of 800 TCPs can execute concurrently.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1054: ZPWY-EVT-PM-TCPREQUESTFAIL The link manager failed during a request. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1061: ZPWY-EVT-PM-SCFROZEN A link request from a link manager was rejected because the server class is frozen. The server class must be thawed before links can be granted. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1064: ZPWY-EVT-PM-FROZENSTATUS The specified server class is frozen. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-SCNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-SCNAME.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1065: ZPWY-EVT-PM-THAWEDSTATUS The specified server class is thawed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-SCNAME ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYP-SCNAME.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1067: ZPWY-EVT-PM-BADENTRYID A link request from a TCP specified an entity that is not known to the PATHMON process. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1068: ZPWY-EVT-PM-DUMPTAKEN A PATHMON process dump was performed at operator request or because the ZDUMP field was enabled at the time an internal error occurred. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1069: ZPWY-EVT-PM-SYSPROCERROR The operating system returned an error on a call to a Guardian procedure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1071: ZPWY-EVT-PM-CHECKPOINT An error occurred during an operating system CHECKPOINT procedure operation. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1072: ZPWY-EVT-PM-BUCREATEFAIL The PATHMON process was not able to create its backup for the reason indicated in nested-message. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1073: ZPWY-EVT-PM-CHECKOPEN An error occurred during an operating system CHECKOPEN operation. errnum is the CHECKOPEN error code. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1074: ZPWY-EVT-PM-CHECKCLOSE A error occurred during an operating system CHECKCLOSE operation. errnum is the CHECKCLOSE error number. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1077: ZPWY-EVT-PM-BUTAKEOVER The PATHMON backup process has taken over processing because the primary CPU failed or because a PRIMARY or SWITCH command was executed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1078: ZPWY-EVT-PM-INTERNALFATAL A PATHMON process internal-consistency check failed. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1080: ZPWY-EVT-PM-TRAPPED A software or hardware failure resulted in a trap. This is a Pathway subsystem internal error.
PATHMON Event Messages Event-Message Range 1000 Through 1999 ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-TRAP, ZPWY-TKN-SADDR, ZPWY-TKN-PADDR, ZPWY-TKN-EADDR, and ZPWY-TKN-LADDR are conditional tokens specific to this event message. N indicates these tokens can occur in a nested error message. For descriptions of these tokens, see Nested Messages on page 10-10. Effect. The PATHMON process terminates. If possible, it creates a dump file. Recovery.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1081: ZPWY-EVT-PM-PATHCTLVERSION During a cool start, the PATHMON configuration file was incompatible with the currently running PATHMON process. This incompatibility can result from: either the PATHMON configuration file being a version prior to D30 (which is not compatible with D30 versions of the PATHMON configuration file), or the PATHMON configuration file having an invalid code (the valid file code is 310).
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1083: ZPWY-EVT-PM-LINEDOWN The Expand communication link to the external PATHMON environment is down. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1093: ZPWY-EVT-PM-BUCPUDOWN The backup CPU for the PATHMON process or for the Pathway/iTS TCP is not running. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1094: ZPWY-EVT-PM-BUFAIL The PATHMON backup process abended or stopped unexpectedly. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1114: ZPWY-EVT-PM-CPTABLEFULL The PATHMON process cannot send checkpoint information to its backup process due to an internal condition. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1115: ZPWY-EVT-PM-REFRESHEDSTATUS The Pathway/iTS TCP has read the requested program unit code segment into memory after checking the SCREEN COBOL object directory file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1119: ZPWY-EVT-PM-AUTOABORTEDSTATUS The specified suspended terminal automatically aborted before being restarted with AUTORESTART. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1120: ZPWY-EVT-PM-AUTOSTARTEDSTATUS After a failure, the AUTORESTART feature restarted the specified object. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1121: ZPWY-EVT-PM-DISABLEAUTORESTART The specified object reached the AUTORESTART limit configured for it. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1122: ZPWY-EVT-PM-BUSTOPPED The PATHMON backup process was stopped by its primary process. This message normally occurs after the CONTROL PM command causes the backup process to change from one CPU to another. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1123: ZPWY-EVT-PM-DUMPNOTTAKEN An attempt to perform a PATHMON memory dump failed; generally, a dump file already exists. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1124: ZPWY-EVT-PM-ALLOCATESEGMENT A Guardian error (errnum) occurred on a call to the ALLOCATESEGMENT procedure. This error is fatal. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1125: ZPWY-EVT-PM-USESEGMENT A Guardian error (errnum) occurred on a call to the USESEGMENT procedure. This error is fatal. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1141: ZPWY-EVT-PM-DEFINEPROCEDURE A Guardian error occurred during a call to the DEFINE procedure library (for example, to the DEFINERESTORE procedure). errnum is the DEFINE procedure error number. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1144 : ZPWY-EVT-PM-DEFINEDISABLED The library procedure for a DEFINE (such as DEFINERESTORE) is unavailable. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1147: ZPWY-EVT-PM-BACKUPISUP The PATHMON backup process is initialized, running, and ready to take over for the primary process, if necessary. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1149: ZPWY-EVT-PM-INTERNALTABLE There is insufficient space for additional entries in one of the PATHMON internal tables. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1150: ZPWY-EVT-PM-SHUTDOWNSTARTED The shutdown process has started in the indicated mode. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1151: ZPWY-EVT-PM-STOPPED The PATHMON process stopped in response to a STOP PM command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1155: ZPWY-EVT-PM-SHUTDOWNFAILED An object in the Pathway subsystem, such as a server class, could not be stopped. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
PATHMON Event Messages Event-Message Range 1000 Through 1999 1159: ZPWY-EVT-PM-OSSPROCESSFAILURE An error occurred while the PATHMON process was trying to create the specified OSS server process. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Event Messages Event-Message Range 1000 Through 1999 error-detail is one of the following: EXTENDED SEGMENT INITIALIZATION ERROR (file-system error) FILE SYSTEM ERROR ON EXTENDED SWAP FILE (file-system error) FILE SYSTEM ERROR ON HOME TERMINAL (file-system error) FILE SYSTEM ERROR ON LIBRARY FILE (file-system error) FILE SYSTEM ERROR ON PROGRAM FILE (file-system error) FILE SYSTEM ERROR ON SWAP FILE (file-system error) ILLEGAL HOME TERMINAL (file-system error) ILLEGAL LIBRARY FILE FORMAT - (format
PATHMON Event Messages Event-Message Range 1000 Through 1999 format-error is one of the following: ACCELERATOR HEADER IN THE FILE IS INVALID AN INTERNAL STRUCTURE OF THE FILE CONTAINS ERROR TYPE (3039). SEE YOUR TANDEM REPRESENTATIVE FOR FURTHER INFORMATION.
PATHMON Event Messages Event-Message Range 1000 Through 1999 Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-OSSPROCESSFAILURE (1159). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-SCNAME, which contains the name of the server class that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-OSSERRNO contains the OSS error number returned by the PROCESS_SPAWN_ procedure.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1160: ZPWY-EVT-PM-OSSNOTAVAILABLE This PATHMON environment does not support the OSS server processes. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1162: ZPWY-EVT-PM-RESIZESEGMENT A error occurred during a call to the Guardian RESIZESEGEMENT or CHECKRESIZESEGMENT procedure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event-Message Range 1000 Through 1999 PATHMON Event Messages 1166: ZPWY-EVT-PM-AUDITSTATUS This is an audit status message. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-UNKNOWNNAME ZPWY-TKN-EVENTCLASS ZPWY-TKN-TEXT token-type token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
PATHMON Event Messages Event-Message Range 1000 Through 1999 command (for example, START) which generated this event. entity (for example, TCP) on which the command was issued. outcome of the command (failed or successful). user who issued the command. Effect. None. Recovery. Informational message only; no corrective action is needed.
12 PATHMON Error Messages This section describes error messages reported by the PATHMON process. The descriptions are given in ascending order by error number; that is, in ascending order by the ZPWY-ERR- values. The PATHMON process logs messages pertaining to TS/MP and Pathway/iTS objects. Message Numbers All messages returned by the PATHMON environment are logged by the PATHMON process.
Unlisted Tokens PATHMON Error Messages • • Token descriptions Effect and recovery information For more information., see Error Messages on page 10-13. Unlisted Tokens When a token is common to all event messages but is not specific to any one event message, it is not listed in the syntax boxes and token descriptions in this section. For a description of all tokens not listed in this section, see Tables 10-1 through 10-1 in Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1003: ZPWY-ERR-PM-ALREADYSTARTED The named entity is already running. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1004: ZPWY-ERR-PM-ALREADYSTOPPED The named entity is already stopped. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1008: ZPWY-ERR-PM-BADPATHCTL The PATHMON configuration file does not exist or you used the equivalent of the ! option when performing a cool start. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1009: ZPWY-ERR-PM-CONFIGDONE The START PATHWAY command (SET PATHWAY command in PATHCOM) cannot be executed while the PATHMON process is in the RUNNING state. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1010: ZPWY-ERR-PM-CONFIGNOTDONE An attempt was made to execute a command while the PATHMON process was not in the RUNNING state. Only the START PATHWAY (SET PATHMON and SET PATHWAY commands in PATHCOM) can be executed while the subsystem is unconfigured. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1012: ZPWY-ERR-PM-DUPNAME Either the PATHMON process tried to add an object having a name that already exists, or the PATHMON process tried to start a Pathway/iTS TCP or server process using a process name that is already active within this Pathway subsystem. This message usually indicates that there was an attempt to use an object name or a process name twice.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1013: ZPWY-ERR-PM-EMPTYENTRY An entry that should contain the description of a Pathway object (for example, a server class) is empty. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1014: ZPWY-ERR-PM-ENTRYLOCKED The named object’s entry was locked (for example, during a state change) and the request timed out before the entry was unlocked. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1015: ZPWY-ERR-PM-ENTRYTYPEMISMATCH An object type does not match the type specified or implied by a request. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1016: ZPWY-ERR-PM-TCPFAIL A TCP stopped abnormally even though a stop command was not issued. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1017: ZPWY-ERR-PM-PATHCTLIO A file-system error occurred during an I/O operation to the PATHMON configuration file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1018: ZPWY-ERR-PM-PMSCPROCESSIO A file-system error occurred during an I/O operation to the specified server class. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1019: ZPWY-ERR-PM-PMTCPIO A file-system error occurred during an I/O operation to the specified link manager. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1020: ZPWY-ERR-PM-LOG1IO A file-system error occurred during an I/O operation to the LOG1 file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1021: ZPWY-ERR-PM-LOG2IO A file-system error occurred during an I/O operation to the LOG2 file. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1022: ZPWY-ERR-PM-RECEIVEIO A file-system error occurred during an I/O operation to $RECEIVE. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1023: ZPWY-ERR-PM-TCPPMIO A file-system error occurred during an I/O operation to the specified link manager. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1024: ZPWY-ERR-PM-BADFILENAME An invalid file name was detected in the definition of the specified object. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1025: ZPWY-ERR-PM-INTERNAL An internal consistency check failed in the PATHMON process. This error is not fatal. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1026: ZPWY-ERR-PM-BADMSG A message received does not conform to the PATHMON request protocol. This error can be caused by running incompatible versions of PATHCOM, PATHMON, or PATHTCP. The message was received from the process running under the specified user ID. This error does not appear as an error list; it appears only in the RETCODE token in response to a command that is using continuation. Effect. The PATHMON process rejects the request.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1032: ZPWY-ERR-PM-NODISKSPACE An entry cannot be added because the PATHMON configuration file is full. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1033: ZPWY-ERR-PM-NOFREEPACE There is insufficient space in the PATHMON process’s freespace table. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1035: ZPWY-ERR-PM-NAMENOTDEFINED The specified entry does not exist. Either the wrong object name was used or the desired object does not exist. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1036: ZPWY-ERR-PM-SYSNOTDEFINED There is an invalid system name in the definition of the indicated object. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1038: ZPWY-ERR-PM-NEWPROCESS A Guardian error occurred while the operating system was attempting to create a new process for the indicated object by using the PROCESS_CREATE_ procedure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1039: ZPWY-ERR-PM-PMNOTNAMED A PATHMON process name was not supplied when the PATHMON process was started. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1041: ZPWY-ERR-PM-REQUESTHANDLER An error occurred during request initiation for the reason indicated in the nested message. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1045: ZPWY-ERR-PM-STATEMISMATCH The command cannot be executed because the object specified in the command or its controlling object (for example, the Pathway/iTS TCP for a terminal) is not in the appropriate state. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1046: ZPWY-ERR-PM-FSERROR A file-system error occurred. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1050: ZPWY-ERR-PM-SYSMSGHANDLER An error occurred while the PATHMON process was processing a system message. The error is indicated by the nested message. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1051: ZPWY-ERR-PM-REQUESTTABLEFULL There is not enough room in the requester table for the PATHMON process to communicate with the link manager. (A maximum of 800 of the sum of the attributes ZMAXEXTERNALTCPS, ZMAXLINKMONS, ZMAXPATHCOMS, ZMAXTCPS, and ZMAXSPI or a maximum of 800 TCPs can execute concurrently.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1052: ZPWY-ERR-PM-TCPNOTDEFINED The Pathway/iTS TCP specified in a termfinal or terminal template definition is not configured. The TCP must be configured and started before its associated TERM objects and PROG objects are started. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1053: ZPWY-ERR-PM-TCPNOTRUNNING The Pathway/iTS TCP specified in a terminal definition is not running. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1054: ZPWY-ERR-PM-TCPREQUESTFAIL The link manager failed during a request. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1055: ZPWY-ERR-PM-TOOMANYENTRIES The attempted request exceeds the number of concurrent executions allowed for the Pathway/iTS START PROG command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1057: ZPWY-ERR-PM-ALREADYFROZEN An attempt was made to freeze a server that is already frozen. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1058: ZPWY-ERR-PM-FREEZEINPROGRESS A freeze request for the server is already in progress. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1059: ZPWY-ERR-PM-FREEZEPENDING A freeze request has been accepted and will complete when all link managers pass a message to the PATHMON process that the server class is frozen. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1060: ZPWY-ERR-PM-ALREADYTHAWED An attempt was made to thaw a server that was not frozen or was already thawed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1061: ZPWY-ERR-PM-SCFROZEN A link request from a link manager was rejected because the server class is frozen. The server class must be thawed before links can be granted. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1062: ZPWY-ERR-PM-MUSTBEFROZEN A STOP SC command was issued before the server class was frozen. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1063: ZPWY-ERR-PM-MUSTBETHAWED A START SC command was issued before the server class was thawed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1066: ZPWY-ERR-PM-TELLNOTCONFIG You issued a Pathway/iTS TELL command but the ZMAXTELLQUEUE field in ZPWYDDL-DEF-PATHWAY has a value of 0. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1067: ZPWY-ERR-PM-BADENTRYID A link request from a link manager specified an entity that is not known to the PATHMON process. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1069: ZPWY-ERR-PM-SYSPROCERROR The operating system returned an error on a call to a Guardian procedure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1070: ZPWY-ERR-PM-BUDOWN The CONTROL or SWITCH command cannot complete because the PATHMON process or the Pathway/iTS TCP backup process is not running. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1071: ZPWY-ERR-PM-CHECKPOINT A Guardian error occurred during the execution of a CHECKPOINT procedure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1073: ZPWY-ERR-PM-CHECKOPEN A Guardian error occurred during the execution of a CHECKOPEN procedure. This error does not appear as an error list; it appears only in the RETCODE token in response to a command that is using continuation. Effect. The primary file is closed. Additional effects depend on the file being opened. Recovery. For information about the specified CHECKOPEN error, see the Guardian Procedure Calls Reference Manual.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1078: ZPWY-ERR-PM-INTERNALFATAL A PATHMON process internal consistency check failed. This is a Pathway subsystem internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1079: ZPWY-ERR-PM-NOSTATICSCPROCESS A START SC command failed because the ZNUMSTATIC field in ZPWY-DDL-DEF-SC is set to 0. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1080: ZPWY-ERR-PM-TRAPPED A software or hardware failure resulted in a trap. This is a Pathway subsystem internal error.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1081: ZPWY-ERR-PM-PATHCTLVERSION During a cool start, the PATHMON configuration file was incompatible with the currently running PATHMON process. This incompatibility can result from: either the PATHMON configuration file being a version prior to D30 (which is not compatible with D30 versions of the PATHMON configuration file), or the PATHMON configuraiton file having an invalid code (the valid file code is 310).
PATHMON Error Messages Error-Message Range 1000 Through 1999 1083: ZPWY-ERR-PM-LINEDOWN The Expand communication link to the external PATHMON environment is down. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1086: ZPWY-ERR-PM-CLASSNOTDEFINED Either the Pathway/iTS ZTERMTYPE field in ZPWY-DDL-PAR-START-PROG is undefined or mismatched, or the PROG object definition has not been added. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1087: ZPWY-ERR-PM-PROGSTOPPED The terminal running the program was stopped by the Pathway/iTS STOP TERM command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1088: ZPWY-ERR-PM-PROGABORTED The terminal running the program was stopped by the Pathway/iTS ABORT TERM command. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1089: ZPWY-ERR-PM-PROGABORTEDERROR The terminal running the program encountered an error that caused the terminal to suspend. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1090: ZPWY-ERR-PM-SECURITY The requesting user failed the security check for the operation on a PATHMONcontrolled object. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1092: ZPWY-ERR-PM-PROGSUSPENDERROR The terminal was suspended because of an error in the SCREEN COBOL program. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1093: ZPWY-ERR-PM-BUCPUDOWN The backup CPU for the PATHMON process or the Pathway/iTS TCP is not running. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1095: ZPWY-ERR-PM-BADCPUNUM The CPU number specified in a command was not in the range 0 through 15 or was not the number of a CPU on your system. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1100: ZPWY-ERR-PM-TOOMANYTCP The number of Pathway/iTS TCP descriptions has reached the maximum value specified for the ZMAXTCPS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1101: ZPWY-ERR-PM-TOOMANYTERM The number of terminal descriptions has reached the maximum value specified for the ZMAXTERMS or ZMAXPROGRAMS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1102: ZPWY-ERR-PM-TOOMANYSC The number of server class descriptions has reached the maximum value specified for the ZMAXSERVERCLASSES field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1103: ZPWY-ERR-PM-TOOMANYSCPROCESS The number of server process definitions has reached the maximum value specified for the ZMAXSERVERPROCESSES field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1104: ZPWY-ERR-PM-TOOMANYSCSTARTUP The number of startup message definitions has reached the maximum value specified for the ZMAXSTARTUPS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1105: ZPWY-ERR-PM-TOOMANYSCASSIGN The number of ASSIGN message definitions has reached the maximum value specified for the ZMAXASSIGNS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1106: ZPWY-ERR-PM-TOOMANYSCPARAM The number of PARAM message definitions has reached the maximum value specified for the ZMAXPARAMS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1107: ZPWY-ERR-PM-TOOMANYTELL The number of tell messages issued has reached the maximum value specified for the ZMAXTELLS field in ZPWY-DDL-DEF-PATHWAY, or the value defined for the ZMAXTELLS field is too large. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1108: ZPWY-ERR-PM-TOOMANYPROG The number of PROG descriptions has reached the maximum value specified for the ZMAXPROGRAMS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1112: ZPWY-ERR-PM-FNS The command issued is not supported by this version of the TS/MP. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1113: ZPWY-ERR-PM-NOTMYTCP The command issued is not valid for an Pathway/iTS external TCP. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1116: ZPWY-ERR-PM-ALREADYREFRESHED A REFRESHCODE command was issued, but the ZCHECKDIRECTORY field in ZPWY-DDL-DEF-TCP has a value of ZPWY-VAL-ON (that is, the TCP checks the SCREEN COBOL object program directory file at each CALL statement). For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1117: ZPWY-ERR-PM-ALREADYPRIMARIED The Pathway/iTS primary TCP process was already running in its configured CPU when the PRIMARY TCP command was issued. This error does not appear as an error list; it appears only in the RETCODE token in response to a command that is using continuation. Effect. None. Recovery. Informational message only; no corrective action is needed.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1125: ZPWY-ERR-PM-USESEGMENT A Guardian error occurred on a call to the USESEGMENT procedure. This error is fatal. This error does not appear as an error list; it appears only in the RETCODE token in response to a command that is using continuation. Effect. The PATHMON process is unable to select a particular extended data segment. The PATHMON process terminates. Recovery.
Error-Message Range 1000 Through 1999 PATHMON Error Messages Effect. The SPI requests fail. Recovery. Use a C00 or later version of the NonStop operating system and the PATHMON process. 1131: ZPWY-ERR-PM-TCPNOTLINKED ThePathway/iTS TCP specified in a STATUS TCPLINK command is not linked to the designated server class. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1135: ZPWY-ERR-PM-EMSDISABLED The Event Management Service (EMS) facility is not available. The PATHMON process cannot handle requests from processes calling EMS procedures. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1137: ZPWY-ERR-PM-EMSADDSUBJECT An error occurred, identified by the error number, on a call to the EMSADDSUBJECT procedure. This error does not appear as an error list; it appears only in the RETCODE token in response to a command that is using continuation. Effect. Any PATHMON logs open with EVENTFORMAT are closed as a result of this error. Recovery.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1148: ZPWY-ERR-PM-MAXWAITEDRUNPROGS An attempt was made in to initiate more than 100 waited START PROG (or PATHCOM RUN PROGRAM) requests from PATHCOM and SPI programs. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1152: ZPWY-ERR-PM-SHUTDOWN-ESCALATED The shutdown process has been escalated. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1153: ZPWY-ERR-PM-IN-SHUTDOWN The request just submitted cannot be serviced because a shutdown of the PATHMON environment is in progress. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1154: ZPWY-ERR-PM-SHUTDOWNTIMEOUT The shutdown operation has not completed, but the specified timeout value has expired. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1156: ZPWY-ERR-PM-PCTLINACCESSIBLE A file-system error occurred, identified by the error number, while the PATHMON process was trying to access the PATHMON configuration file. This message is entered into the log file, but is not returned to the user. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1158: ZPWY-ERR-PM-UNINITIALIZEDPMON The primary PATHMON process has failed and the backup PATHMON process has not been fully initialized. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1159: ZPWY-ERR-PM-OSSPROCESSFAILURE An error occurred while the PATHMON process was trying to create the specified OSS server process. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages Recovery. OSS server processes are created by calls to the Guardian PROCESS_SPAWN_ procedure. For additional information, see the detailed description in this message; the description of PATHMON event 1159 lists the possible messages returned. For information about the PROCESS_SPAWN_ procedure call, see the Guardian Procedure Calls Reference Manual.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1161: ZPWY-ERR-PM-PROCTYPEMISMATCH You have issued an INFO command specifying a server class that is not valid for the process type defined for that class. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 1000 Through 1999 PATHMON Error Messages 1162: ZPWY-ERR-PM-RESIZESEGMENT A error occurred during a call to the Guardian RESIZESEGEMENT or CHECKRESIZESEGMENT procedure. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 1164: ZPWY-ERR-PM-PRODUCTNOTLICENSED You have issued a command for an HP NonStop product that is not licensed for your site. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
PATHMON Error Messages Error-Message Range 1000 Through 1999 HP NonStop TS/MP Management Programming Manual—540082-005 12 -92
13 LINKMON Messages This section describes the event and error messages logged by the PATHMON process on behalf of the LINKMON process or the ACS subsystem processes. The descriptions are given in ascending order by message number. Note. These messages are a subset of the messages in the message-number range 3000 through 3999 that are reported by link managers (such as LINKMON and TCPs). Messages reported by TCPs are described in the Pathway/iTS Management Programming Manual.
LINKMON Messages Event-Message Format Event-Message Format Each event message in this section includes: • • • • • The number and name of the event message A description of the event message cause A syntax box listing: ° The unconditional and conditional tokens that have specific values for that event message. For a description of each token, see Section 10, Event Management.
Subject Tokens LINKMON Messages Subject Tokens Subject tokens (for example, ZPWY-TKN-SCNAME) contain the name of the PATHMON-controlled object that is the subject of the event message. Within the syntax boxes in this section, subject tokens may be presented in the form ZPWY-TKNnnnNAME, where nnn represents any of these TS/MP object types: LM PMREQUESTER SC SCASSIGN SCDEFINE SCLM SCPARAM SCPROCESS SCSTARTUP For descriptions of these object types, see Object Types on page 3-6.
LINKMON Messages Event Messages in the Range 3000 Through 3999 Event Messages in the Range 3000 Through 3999 Although Pathway/iTS TCPs can be the subject of all messages having numbers in the range 3000-3999, these messages can also have a LINKMON process or ACS subsystem processes as the subject. Note that some Pathway subsystem event messages include a Guardian error number.
LINKMON Messages Event Messages in the Range 3000 Through 3999 Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-TCP-SCPROCESSOPEN (3100). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-LMNAME or ZPWY-TKN-TCPNAME, which contains the name of the LINKMON process, the ACS Process Broker, or TCP that is the subject of this message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-ERROR contains the number of the file-system error.
LINKMON Messages Event Messages in the Range 3000 Through 3999 3116: ZPWY-EVT-TCP-SCPROCESSIO A file-system error (errnum) occurred during an I/O operation to a server process. This event can be reported by either the LINKMON process, the ACS subsystem processes, or the TCP. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
LINKMON Messages Event Messages in the Range 3000 Through 3999 ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. Effect. The I/O operation fails. The TCP, LINKMON process, or ACS subsystem processes unlinks from the server class. Recovery.
LINKMON Messages Event Messages in the Range 3000 Through 3999 ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-TCP-SCNOTDEFINED (3117). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-LMNAME, ZPWY-TKN-TERMNAME, or ZPWY-TKN-TCPNAME, which contains the name of the LINKMON process, the ACS Process Broker, Pathway/iTS TERM object, or TCP that is the subject of this event message.
LINKMON Messages Event Messages in the Range 3000 Through 3999 3118: ZPWY-EVT-TCP-BADSCSTATE The state of the specified server does not allow the requested operation to occur. This is a Pathway subsystem internal error. This event can be reported by either the LINKMON process, the ACS subsystem processes, or the TCP. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
LINKMON Messages Event Messages in the Range 3000 Through 3999 3200: ZPWY-EVT-TCP-BADPMTCPMSG The specified TCP, LINKMON process, or ACS subsystem processes received an invalid request from the PATHMON process. This error usually occurs when incompatible versions of the PATHMON process and the LINKMON process, ACS subsystem process, or TCP are running at the same time.
Event Messages in the Range 3000 Through 3999 LINKMON Messages 3201: ZPWY-EVT-TCP-BADSYNCID A LINKMON process or TCP received an invalid message synchronous ID (SYNCID). This is a LINKMON or TCP internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Event Messages in the Range 3000 Through 3999 LINKMON Messages 3226: ZPWY-EVT-TCP-PMTCPFNS The PATHMON process requested a function not supported in this version of the LINKMON process. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
LINKMON Messages Event Messages in the Range 3000 Through 3999 3233: ZPWY-EVT-TCP-SPUNKNOWN A LINKMON process or TCP received a message from the PATHMON process containing a reference to a server process that is unknown to the link manager. This is an internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
LINKMON Messages Error Messages in the Range 3000 Through 3999 Error Messages in the Range 3000 Through 3999 Although Pathway/iTS TCPs can be the subject of all messages having numbers in the range 3000-3999, these messages can also have a LINKMON process as the subject. 3100: ZPWY-ERR-TCP-SCPROCESSOPEN A file-system error occurred while a server process was being opened. This error can be reported by either the LINKMON process or the ACS Process Broker or the TCP.
LINKMON Messages Error Messages in the Range 3000 Through 3999 3118: ZPWY-ERR-TCP-BADSCSTATE The state of the specified server does not allow the requested operation to occur. This is a Pathway subsystem internal error. This error can be reported by either the LINKMON process or the ACS Process Broker or the TCP. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
LINKMON Messages Error Messages in the Range 3000 Through 3999 3200: ZPWY-ERR-TCP-BADPMTCPMSG The specified link manager received an invalid request from the PATHMON process. This error usually occurs when incompatible versions of the PATHMON process and the LINKMON process or the ACS Process Broker or TCP are running at the same time. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
3201: ZPWY-ERR-TCP-BADSYNCID LINKMON Messages 3201: ZPWY-ERR-TCP-BADSYNCID A LINKMON process or TCP received an invalid message synchronous ID (SYNCID). This is a LINKMON process or the ACS Process Broker or TCP internal error. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
3201: ZPWY-ERR-TCP-BADSYNCID LINKMON Messages 3226: ZPWY-ERR-TCP-PMTCPFNS The PATHMON process requested a function not supported in this version of the TCP or LINKMON process. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
LINKMON Messages 3201: ZPWY-ERR-TCP-BADSYNCID 3233: ZPWY-ERR-TCP-SPUNKNOWN The TCP or LINKMON process or the ACS Process Broker received a message from the PATHMON process containing a reference to a server process that is unknown to the link manager. This is a Pathway internal error. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The TCP or LINKMON process cannot process the request. Recovery.
LINKMON Messages 3201: ZPWY-ERR-TCP-BADSYNCID HP NonStop TS/MP Management Programming Manual—540082-005 13 -20
14 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.
ACS Subsystem Identifiers ACS Subsystem Messages ACS Subsystem Identifiers ACS subsystem number for NonStop OS SPI subsystems 252 ACS subsystem name in the NonStop OS APPCLSTR ACS subsystem name abbreviation ACL External ACS subsystem identifier for release TS/MP 2.1. This identifier occurs in event message text, which is typically produced by EMS event printing distributors for EMS formatted event messages logged by ACS subsystem processes. TANDEM.APPCLSTR.
Unlisted Tokens ACS Subsystem Messages Unlisted Tokens When a token is common to all event messages, it is not included in the message descriptions in this chapter. For a description of all tokens not listed in this chapter, see the TS/MP Management Programming Manual.
ACS Event Severity Levels ACS Subsystem Messages ACS Event Severity Levels Event severity levels indicate the impact (on ACS subsystem resources and processes) of an event occurrence detected by an ACS subsystem process. Every event occurrence logged by the ACS subsystem indicates the severity of that occurrence.
EMS Messages 1000 through 1009 ACS Subsystem Messages ZACL-VAL-EVENT-LEVEL-FATAL indicates that an ACS subsystem process encountered a condition that prevented it from performing any more operations. The process terminates immediately, which aborts any operations that it had in progress. If the condition was an internal error in the process logic or data, it produces a SaveAbend file. Typically, the process termination disables the CPU in which it was running.
EMS Messages 1000 through 1009 ACS Subsystem Messages 1002: ZACL-EVT-BACKUP-LAUNCH-ERROR The domain coordinator process cannot create a backup process in the specified CPU on the local system because the PROCESS_LAUNCH_() operation failed.l Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL token-type token-type token-type token-type ZACL-TYP-EVENT-LEVEL. ZSPI-TYP-INT. ZSPI-TYP-INT.
EMS Messages 1000 through 1009 ACS Subsystem Messages 1003: ZACL-EVT-BACKUP-ABENDED The backup domain coordinator process terminated unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-CPU-NUMBER token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT. Conditional Tokens ZACL-TKN-EVENT-TERM-STOPPER ZACL-TKN-EVENT-TERM-SSID ZACL-TKN-EVENT-TERM-TEXT token-type ZSPI-TYP-PHANDLE. token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-STRING.
EMS Messages 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-TERM-STOPPER contains the process handle of the process that initiated the termination. This token is included only if the process was stopped externally. ZACL-TKN-EVENT-TERM-SSID contains the SPI subsystem identifier associated with the process-termination operation. This token is omitted if no subsystem identifier was associated with the termination.
ACS Subsystem Messages EMS Messages 1000 through 1009 ZACL-TKN-EVENT-CPU-NUMBER contains the number of the CPU on the local system in which the process could not be started. This token is the subject of the event message. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the process that was not created. ZACL-TKN-EVENT-ERROR-CODE contains the process-creation error code returned by the PROCESS_LAUNCH_() procedure.
EMS Messages 1000 through 1009 ACS Subsystem Messages 1005: ZACL-EVT-CP-ABENDED An ACS subsystem process terminated unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-PROCESS-NAME ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL token-type token-type token-type token-type token-type ZACL-TYP-EVENT-LEVEL. ZSPI-TYP-INT. ZSPI-TYP-STRING. ZSPI-TYP-INT. ZSPI-TYP-INT.
EMS Messages 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-TERM-STOPPER contains the process handle of the process that caused the termination. This token is included only if the process was stopped externally. ZACL-TKN-EVENT-TERM-SSID contains the SPI subsystem identifier associated with the process-termination. This token is omitted if no subsystem identifier was associated with the termination. ZACL-TKN-EVENT-TERM-TEXT contains the termination text associated with the process-termination.
EMS Messages 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-PROCESS-NAME contains the name of the failed process. ZACL-TKN-EVENT-ERROR-CODE contains the file-system error code returned by the failed operation. ZACL-TKN-EVENT-FILE-NAME contains the name of the Guardian file, device, or process accessed by the failed operation. This token is omitted for Guardian procedures that do not operate on files but that, nevertheless, report failures using file-system error codes. Effect.
EMS Messages 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-FILE-NAME contains the path name of the OSS file or directory that was accessed by the failed operation. This token is omitted for OSS procedures that do not operate on files or directories. Effect. The operation associated with the OSS operation is aborted. Recovery. Correct the condition that caused the OSS error and try the operation again.
EMS Messages 1000 through 1009 ACS Subsystem Messages ZACL-TKN-EVENT-ERROR-DETAIL contains additional information about the error returned by the failed operation. If the value of this token is zero in an event message, the token is null and should be regarded as omitted from the message. Effect. The operation associated with the process-management operation is aborted. Recovery. Correct the condition that caused the error and try the operation again.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-ERROR-DETAIL contains the 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. This token is omitted for link manager procedures that do not operate on server classes. Effect.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-ERROR-CODE contains the memory management error code returned by the failed operation. ZACL-TKN-EVENT-ERROR-DETAIL contains the memory management error detail code returned by the failed operation. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message. Effect. The process that invoked the failed operation terminates abnormally and produces a SaveAbend file. Recovery.
EMS Messages 1010 through 1019 ACS Subsystem Messages 1012: ZACL-EVT-BINSEM-ERROR An ACS subsystem process invoked a Guardian semaphore-system procedure and the operation failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCEDURE ZACL-TKN-EVENT-SEGMENT-ID ZACL-TKN-EVENT-ERROR-CODE token-type token-type token-type token-type ZACL-TYP-EVENT-LEVEL. ZSPI-TYP-STRING. ZSPI-TYP-INT. ZSPI-TYP-INT.
EMS Messages 1010 through 1019 ACS Subsystem Messages 1014: ZACL-EVT-BINSEM-ABANDONED A process terminated while holding the lock on one of the ACS subsystem shared memory semaphores. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-SEGMENT-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. Event-Message Text 1014 - Process failed holding memory segment segment-id semaphore Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL.
EMS Messages 1010 through 1019 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-PROCEDURE contains the name of the Guardian memory-pool management procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-SEGMENT-ID contains the identifier of the memory segment containing the pool that was being accessed by the failed operation.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-SEGMENT-ID contains the identifier of the memory segment containing the pool from which space was to be allocated. This token is the subject of the event message. Effect. The process that failed to allocate space from the memory segment terminates immediately. Recovery. Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the problem occurred.
EMS Messages 1010 through 1019 ACS Subsystem Messages ZACL-TKN-EVENT-CREATOR-ID contains the process-creator user identifier of the unauthorized requester process. ZACL-TKN-EVENT-FILE-NAME contains the file name of the ACS subsystem process that the unauthorized process supplied to the OPEN or FILE_OPEN_ operation. ZACL-TKN-EVENT-PROCESS-NAME contains the named process descriptor of the process that sent the unauthorized OPEN request. This token is omitted if the unauthorized process is unnamed. Effect.
ACS Subsystem Messages EMS Messages 1010 through 1019 Recovery. Correct the requester program. 1019: ZACL-EVT-INCOMP-RQST-VER 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 1019 - Incompatible request version received from process process-id Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
EMS Messages 1020 through 1029 ACS Subsystem Messages EMS Messages 1020 through 1029 1020: ZACL-EVT-INVALID-RPLY-MSG An ACS subsystem process received an invalid reply message or a reply message that has an incompatible version. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-PHANDLE.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1021: ZACL-EVT-PROTOCOL-ERROR An ACS subsystem process detected a protocol (operation order) error by another system process. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-PHANDLE. Event-Message Text 1021 - Protocol error in communication with process processid Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-ERROR.
ACS Subsystem Messages EMS Messages 1020 through 1029 ZACL-TKN-EVENT-PROCESS-NAME contains the name of the PATHMON process. This token is the subject of the event message. Effect. If the I/O operation was initiated in response to a send operation, the send operation fails with Pathsend error FEScPathmonConnect and file-system error FETIMEDOUT. The ACS subsystem attempts to close communication to this PATHMON process.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1024: ZACL-EVT-PATHMON-IO-ERROR An I/O operation from the ACS subsystem to a PATHMON process failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-NAME ZACL-TKN-EVENT-ERROR-CODE token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INT.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1025: ZACL-EVT-PATHMON-OPEN-ERROR An attempt to open a PATHMON process failed. Unconditional Tokens ZACL-TKN-EVENT-LEVEL token-type ZACL-TYP-EVENT-LEVEL. ZACL-TKN-EVENT-PROCESS-NAME token-type ZSPI-TYP-STRING. ZACL-TKN-EVENT-ERROR-CODE token-type ZSPI-TYP-INT. Event-Message Text 1025 - PATHMON process-name OPEN operation failed, error errnum Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
EMS Messages 1020 through 1029 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the PATHMON process. This token is the subject of the event message. Effect. The send operation fails with Pathsend error FEScPathmonMessage and filesystem error FEOK. Recovery. Try the send operation again. If the problem persists, check the PATHMON process. You may need to shutdown and restart your application.
EMS Messages 1020 through 1029 ACS Subsystem Messages 1028: ZACL-EVT-PATHMON-INVALID-MAT An ACS subsystem process received an invalid message from a PATHMON process. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-NAME token-type ZACL-TYP-EVENT-LEVEL token-type ZSPI-TYP-STRING. Event-Message Text. 1028 - Invalid message received from PATHMON process-name Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-WARNING.
EMS Messages 1030 through 1039 ACS Subsystem Messages ZACL-TKN-EVENT-CPU-NUMBER contains the number of the physical CPU that was started on the system where the event message was generated. This token is the subject of the event message. Effect. Pathsend operations initiated in the CPU no longer fail with FESCLINKMONCONNECT errors. Recovery. This is an informational message only; no corrective action is needed.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1031: ZACL-EVT-LOG-FILE-ERROR An ACS subsystem process encountered an error while writing an event message to the configured LOG1 or LOG2 event log file. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCEDURE ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-FILE-NAME token-type token-type token-type token-type ZACL-TYP-EVENT-LEVEL. ZSPI-TYP-STRING. ZSPI-TYP-INT. ZSPI-TYP-STRING. Event-Message Text.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1032: ZACL-EVT-LOG1-OPENED The LOG1 event log file was opened successfully. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-FILE-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. Event-Message Text. 1032 - LOG1 opened on file file-name Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-STATUS. ZACL-TKN-EVENT-FILE-NAME contains the Guardian name of the event log file.
EMS Messages 1030 through 1039 ACS Subsystem Messages ZACL-TKN-EVENT-FILE-NAME contains the Guardian name of the event log file. This token is the subject of the event message. Effect. None. Recovery. If the event was due to an error on the log file, check the previously issued event message for a detailed description of the problem. If the event was issued in response to an operator command, this is an informational message only; no corrective action is needed.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1035: ZACL-EVT-LOG2-CLOSED The LOG2 event log file was closed either in response to an operator command or because an error occurred while writing to the log file. If this event was due to an error on the log file, a previously issued event message described the error. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-FILE-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING.
EMS Messages 1030 through 1039 ACS Subsystem Messages 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 requester program or start the named PATHMON process.
EMS Messages 1030 through 1039 ACS Subsystem Messages 1038: ZACL-EVT-SERVER-FILE-ERROR A Guardian file-system operation on a server process failed unexpectedly or completed with an unexpected error code. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-SERVER-NAME ZSPI-TKN-MANAGER ZACL-TKN-EVENT-PROCEDURE ZACL-TKN-EVENT-PROCESS-ID ZACL-TKN-EVENT-FILE-NAME ZACL-TKN-EVENT-ERROR-CODE token-type token-type token-type token-type token-type token-type token-type ZACL-TYP-EVENT-LEVEL. ZSPI-TYP-STRING.
EMS Messages 1040 through 1049 ACS Subsystem Messages ZACL-TKN-EVENT-FILE-NAME contains the process file name that identifies the server process and that was used by the failed operation. ZACL-TKN-EVENT-ERROR-CODE contains the file-system error code returned by the failed operation. Effect. The Pathsend operation associated with the file-system operation is aborted. Recovery. Correct the condition that caused the operation to fail.
ACS Subsystem Messages EMS Messages 1050 through 1059 ZACL-TKN-EVENT-ACCESS-ID contains the process access user identifier of the unauthorized requester process. Effect. The Pathsend operation fails with an FESERVERLINKCONNECT Pathsend error and FESECVIOL file-system error detail. Recovery. None. This event message indicates a possible attempt to breach the security of a Pathway application. EMS Messages 1050 through 1059 TS/MP 2.1 does not contain messages in this number range.
EMS Messages 1060 through 1069 ACS Subsystem Messages 1063: ZACL-EVT-INVALID-BACKUP-CPU An invalid CPU number was specified in the domain coordinator process startup string. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT. Event-Message Text 1063 - Invalid backup CPU specified: cpu-number Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-CPU-NUMBER token-type ZSPI-TYP-INT.
ACS Subsystem Messages EMS Messages 1060 through 1069 ZACL-TKN-EVENT-PROCESS-NAME contains the reserved process name that is currently being used. This token is the subject of the event message. Effect. If the domain coordinator process detects the problem during process startup, it terminates immediately. If it detects the condition during the START ACS command processing, the START operation fails and no ACS subsystem processes are started. Recovery.
ACS Subsystem Messages EMS Messages 1060 through 1069 1066: ZACL-EVT-BACKUP-CPU-DISABLED A primary domain coordinator process terminated unexpectedly in the indicated CPU and the ACS subsystem processes in that CPU have not been restarted. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT.
EMS Messages 1060 through 1069 ACS Subsystem Messages Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-FATAL. ZACL-TKN-EVENT-FILE-NAME contains the name of the Guardian subvolume where the domain coordinator program resides. This token is the subject of the event message. ZACL-TKN-EVENT-SYSNN contains the name of the Guardian subvolume that contains the OSIMAGE file used to load the system. Effect. The domain coordinator process terminates immediately. Recovery.
EMS Messages 1060 through 1069 ACS Subsystem Messages Effect. If the backup domain coordinator process fails, the primary domain coordinator process continues to run without a backup process. If one of the other ACS subsystem processes fails, the CPU where it was running is disabled. Recovery. Restart the home terminal if possible. Otherwise, stop and restart the ACS subsystem with a new home terminal. 1069: ZACL-EVT-PROCESS-SWITCH The primary process can no longer continue.
EMS Messages 1070 through 1072 ACS Subsystem Messages EMS Messages 1070 through 1072 1070: ZACL-EVT-PROCESS-SWITCH-FAILED The process pair cannot switch because no backup process is running. The backupprocess CPU may be down or the ACS subsystem processes have not been restarted in that CPU. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCESS-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING.
EMS Messages 1070 through 1072 ACS Subsystem Messages 1071: ZACL-EVT-PRIMARY-ABENDED The primary domain coordinator process terminated abnormally. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-CPU-NUMBER ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL token-type token-type token-type token-type ZACL-TYP-EVENT-LEVEL. ZSPI-TYP-INT. ZSPI-TYP-INT. ZSPI-TYP-INT.
ACS Subsystem Messages EMS Messages 1070 through 1072 ZACL-TKN-EVENT-TERM-STOPPER contains the process handle of the process that stopped the primary process. This token is included only if the process was stopped externally. ZACL-TKN-EVENT-TERM-SSID contains the SPI subsystem identifier associated with the primary process termination. This token is omitted if no subsystem identifier was associated with the process termination.
ACS Subsystem Messages EMS Messages 1070 through 1072 1072: ZACL-EVT-ACSCTL-SYNTAX-ERROR Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-ERROR-TEXT token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. Conditional Tokens ZACL-TKN-EVENT-FILE-NAME ZACL-TNM-EVENT-LINE-NUMBER token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INT. Event-Message Text.
ACS Subsystem Messages EMS Messages 1070 through 1072 HP NonStop TS/MP Management Programming Manual—540082-005 14 -48
15 SPI Error Messages This section describes the error messages reported by the Subsystem Programmatic Interface (SPI). The descriptions are given in ascending order by error number; that is, in ascending order by the ZPWY-ERR- values. Message Numbers 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.
Error Presentation SPI Error Messages Error Presentation Errors returned by a SPI requester appear in error lists. Each error list in this section includes: • • • • • The number and name of the error message A description of the error message cause A syntax box listing the tokens associated with the error message Token descriptions Effect and recovery information For more information, see Error Messages on page 10-13.
Error-Message Range 4000 Through 4999 SPI Error Messages Error-Message Range 4000 Through 4999 Error messages numbered from 4000 through 4999 describe error lists returned from SPI requesters. 4001: ZPWY-ERR-SPI-EXTRATOKEN An extra token is present in the message buffer sent to the PATHMON process. For example, this error is returned if there are two occurrences of ZPWY-DDL-SEL-SC for one ADD SC command.
Error-Message Range 4000 Through 4999 SPI Error Messages 4002: ZPWY-ERR-SPI-INVALIDTOKEN The PATHMON process does not recognize a token in the message buffer. For example, this error would be returned if token number 150 were present and there were only 136 token numbers defined for Pathway tokens. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4003: ZPWY-ERR-SPI-WRONGTOKEN An incorrect token is present in the message buffer sent to the PATHMON process. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-PARM-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST.
Error-Message Range 4000 Through 4999 SPI Error Messages 4004: ZPWY-ERR-SPI-MISSINGTOKEN A required token is missing from the message buffer sent to the PATHMON process. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-PARM-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST.
Error-Message Range 4000 Through 4999 SPI Error Messages 4005: ZPWY-ERR-SPI-INVALIDFIELD An extensible structured token contains an invalid field. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4006: ZPWY-ERR-SPI-MISSINGFIELD A required field in an extensible structured token is missing. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4007: ZPWY-ERR-SPI-NUMSTATICTOOBIG The value for the ZNUMSTATIC field in ZPWY-DDL-DEF-SC is larger than the value for the ZMAXSERVERS field in ZPWY-DDL-DEF-PATHWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4008: ZPWY-ERR-SPI-TOOMANYDEFSERVERS The number of predefined servers exceeds the value specified in the ZMAXSERVERS field in ZPWY-DDL-DEF-PATHWWAY. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4009: ZPWY-ERR-SPI-INVALIDBUFFER The SPI procedures report an invalid message buffer. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SSCTL.
Error-Message Range 4000 Through 4999 SPI Error Messages 4010: ZPWY-ERR-SPI-BADCHECKSUM The SPI procedures report a bad CHECKSUM operation on the message buffer. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
Error-Message Range 4000 Through 4999 SPI Error Messages 4011: ZPWY-ERR-SPI-SSPUT An error occurred on the call to SSPUT. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4012: ZPWY-ERR-SPI-SSGET An error occurred on the call to SSGET. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SSCTL.
Error-Message Range 4000 Through 4999 SPI Error Messages 4013: ZPWY-ERR-SPI-SSINIT An error occurred on the call to SSINIT. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SSCTL.
Error-Message Range 4000 Through 4999 SPI Error Messages 4014: ZPWY-ERR-SPI-SSNULL An error occurred on the call to SSNULL. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SSCTL.
Error-Message Range 4000 Through 4999 SPI Error Messages 4015: ZPWY-ERR-SPI-WRONGSUBSYS The subsystem ID specified in the request is not the Pathway subsystem ID. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT.
Error-Message Range 4000 Through 4999 SPI Error Messages 4016: ZPWY-ERR-SPI-RESERVEDWORD A field in an extensible structured token contains a Pathway subsystem reserved word. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4017: ZPWY-ERR-SPI-INVALIDCONTEXT A context token is invalid or corrupted. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4018: ZPWY-ERR-SPI-CTLPMNAMEMISMATCH The PATHMON process name or the system name in the PATHMON configuration file does not match the name given to the PATHMON process when it was started. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4019: ZPWY-ERR-SPI-CTLSTATEMISMATCH The requester attempted a cool start, but the PATHMON configuration file contains an object in the RUNNING state. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4021: ZPWY-ERR-SPI-CMDTOOBIG The used length of the SPI buffer is greater than the PATHMON process read count. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4022: ZPWY-ERR-SPI-ATLEASTONE No fields in an extensible structured token are specified; at least one field must be specified. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4023: ZPWY-ERR-SPI-CWDCANTBERESETNOW The current working directory specified for ZPWY-TKN-DEF-SCCWD cannot be changed because other OSS pathnames are defined as relative pathnames and require the current value of CWD to resolve them to absolute pathnames. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4024: ZPWY-ERR-SPI-GUARDIANATTRUSED A field defined for an OSS server process is valid only for Guardian server processes. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4025: ZPWY-ERR-SPI-OSSATTRUSED A field or token defined for a Guardian server process is valid only for OSS server processes. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4026: ZPWY-ERR-SPI-OSSATTRTOOBIG The value for an OSS server process exceeded the maximum length. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4027: ZPWY-ERR-SPI-INVALIDPATHNAME An OSS pathname is invalid due to a disallowed forward slash (/) or null character. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4028: ZPWY-ERR-SPI-ARGENVEXCEEDMAX The combined length of the values defined for the server class tokens ZPWY-TKNDEF-SCARGLIST and ZPWY-TKN-DEF-SCENV exceed the 24,000-character maximum. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4029: ZPWY-ERR-SPI-RESOLVEDTOOBIG A relative pathname is entered for an OSS attribute. When the relative pathname is resolved, by using the OSS directory specified in ZPWY-TKN-DEF-SCCWD, the resulting absolute pathname exceeds the maximum 1024 bytes allowed. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4030: ZPWY-ERR-SPI-NAMENOTABSOLUTE Either the OSS pathname specified is a relative pathname but no default directory has been specified to resolve it, or, if a default directory has been defined for ZPWY-TKNDEF-SCCWD, then the relative OSS pathname specified does not resolve to an absolute pathname. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management.
Error-Message Range 4000 Through 4999 SPI Error Messages 4031: ZPWY-ERR-SPI-BUFFEREXHAUSTION There are already five pending requests from this SPI requester; no new request can be processed now. For a description of tokens that are present in this event message but are not listed or described below, see Section 10, Event Management. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST.
16 Management Programming Examples This section contains these three management programming examples: • • • A Pathway subsystem configuration program, written in COBOL. A program that issues an ADD SERVER or ALTER SERVER command, written in TACL. A program that issues an INFO PATHWAY command, written in TACL. Configuring Pathway Example 16-1 presents a management program that configures a Pathway subsystem. The program, which is written in COBOL: 1. Starts the PATHMON process 2.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 1 of 28) * NB: Pathmon requires that SPI clients be low-pin or be named. Set the appropriate linker flag. * The source search path must include the ZSPIDEFS subvolume. * To compile from Guardian, add this define; it must name the subvolume of the SPI source files. * ADD DEFINE =_SOURCE_SEARCH, CLASS SEARCH, SUBVOL0 ($system.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 2 of 28) * * * * * * * * 05 WS-COBOL-VAL-TRUE-X NATIVE-2 VALUE -1. 05 WS-COBOL-VAL-TRUE REDEFINES WS-COBOL-VAL-TRUE-X PIC X(2). 05 WS-COBOL-VAL-ON REDEFINES WS-COBOL-VAL-TRUE-X PIC X(2). 05 WS-COBOL-VAL-YES REDEFINES WS-COBOL-VAL-TRUE-X PIC X(2). 05 WS-COBOL-VAL-FALSE-X NATIVE-2 VALUE 0. 05 WS-COBOL-VAL-FALSE REDEFINES WS-COBOL-VAL-FALSE-X PIC X(2).
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 3 of 28) 01 PRINT-LINES. 05 WS-BLANK-LINE PIC X(2) VALUE SPACES. 05 WS-STATUS-SC-HEADER PIC X(39) VALUE "SERVER #RUNNING ERROR INFO". 05 WS-STATUS-SCPROCESS-HEADER PIC X(60) VALUE " PROCESS STATE ERROR INFO #LINKS WEIGHT". 05 WS-DETAIL-LINE PIC X(80). 05 WS-STATUS-SC-DETAIL REDEFINES WS-DETAIL-LINE. 10 SC-NAME PIC X(15). 10 FILLER PIC X(02). 10 RUNNING PIC ZZZZ9. 10 FILLER PIC X(06). 10 LAST-ERROR PIC 9999.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 4 of 28) COPY ZPWY-DDL-SEL-SCPROCESS IN "ZPWYCOB" REPLACING ZPWY-DDL-SEL-SCPROCESS BY ==ZPWY-DDL-SEL-SCPROCESS REDEFINES SEL-AREA==. 01 DEF-AREA PIC X(02). COPY ZPWY-DDL-DEF-PATHWAY IN "ZPWYCOB" REPLACING ZPWY-DDL-DEF-PATHWAY BY ==ZPWY-DDL-DEF-PATHWAY REDEFINES DEF-AREA==. COPY ZPWY-DDL-DEF-SC IN "ZPWYCOB" REPLACING ZPWY-DDL-DEF-SC BY ==ZPWY-DDL-DEF-SC REDEFINES DEF-AREA==.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 5 of 28) * Get the default volume. MOVE SPACES TO WS-STARTUP-VOLUME ENTER "SMU_Startup_GetText_" USING WS-VOLUME-PORTION, WS-STARTUP-VOLUME GIVING WS-STARTUP-VOLUME-LEN IF WS-STARTUP-VOLUME-LEN IS NOT NEGATIVE THEN ADD 1 TO WS-STARTUP-VOLUME-LEN ELSE DISPLAY "SMU_Startup_GetText_ ERROR" SET NOT-OK-TO-CONTINUE TO TRUE END-IF . 300-START-PATHMON.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 6 of 28) MOVE SPACES TO WS-FILE-NAME STRING WS-PATHMON-PROCESS-NAME DELIMITED BY ":" ".#ZSPI" DELIMITED BY SIZE INTO WS-EXTERNAL-FILE-NAME ENTER "COBOL_ASSIGN_" USING PATHMON-FILE, WS-EXTERNAL-FILE-NAME GIVING WS-COBOL-RESULT MOVE "COBOL_ASSIGN_" TO WS-ERROR-TEXT PERFORM 3900-CHECK-COBOL-ERROR IF OK-TO-CONTINUE THEN OPEN I-O PATHMON-FILE END-IF . 500-MAINLINE.
Management Programming Examples Configuring Pathway Example 16-1.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 8 of 28) * Next, issue the INFO SC command. PERFORM 3800-ISSUE-PATHMON-COMMAND * Finally, obtain the default values for the * server class definition. ENTER TAL "SSGET" USING ZPWY-DDL-MSG-BUFFER, ZPWY-MAP-DEF-SC, ZPWY-DDL-DEF-SC, WS-FIRST-OCCURRENCE GIVING WS-SS-RESULT MOVE "SSGET of ZPWY-DDL-SEL-SC" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Construct the ADD SC command.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 9 of 28) IF WS-TEMPORARY-RESULT IS ZERO THEN DISPLAY "FNAMEEXPAND ERROR " SET NOT-OK-TO-CONTINUE TO TRUE END-IF MOVE VOLUME-NAME OF WS-FILE-NAME TO Z-VOLUME OF ZDEFAULTVOLUME OF ZPWY-DDL-DEF-SC MOVE SUBVOL-NAME OF WS-FILE-NAME TO Z-SUBVOLUME OF ZDEFAULTVOLUME OF ZPWY-DDL-DEFSC * Put the server class definition into the buffer.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 10 of 28) * * * * MOVE "SSNULL of ZPWY-DDL-DEF-SCASSIGN" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR Set appropriate server class ASSIGN definition values. Point the file name to the current subvolume. STRING WS-STARTUP-VOLUME DELIMITED BY SPACE ".
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 11 of 28) 1600-STATUS-SERVERCLASS-DETAIL. MOVE "SERVER-SPI" TO OBJECT-NAME OF WS-SPI-INPUT PERFORM 1700-STATUS-SERVERCLASS * Get the status for all server processes of the server class. DISPLAY WS-BLANK-LINE DISPLAY WS-STATUS-SCPROCESS-HEADER PERFORM 2200-BUILD-STATUS-SP-ALL PERFORM 3600-SAVE-INITIAL-REQUEST * Issue the STATUS SCPROCESS command.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 12 of 28) 2300-STATUS-SCPROCESS-CONTINUE. * Issue the STATUS SCPROCESS command for the first or * next server process. PERFORM 3800-ISSUE-PATHMON-COMMAND IF OK-TO-CONTINUE THEN PERFORM 2700-DISPLAY-STATUS-SCPROCESS END-IF * Merge returned context into original request, setting up the * continuation request. PERFORM 3700-SETUP-CONTINUATION . 2600-DISPLAY-STATUS-SC.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 13 of 28) 2700-DISPLAY-STATUS-SCPROCESS. MOVE "2700-DISPLAY-STATUS-SCPROCESS" TO WS-PARA-NAME * Get the object-selector token for the server process.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 14 of 28) 2800-SELECT-COMMAND-OBJECT. MOVE "2800-SELECT-COMMAND-OBJECT" TO WS-PARA-NAME ENTER TAL "SSINIT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-VAL-BUFLEN, ZPWY-VAL-SSID, ZSPI-VAL-CMDHDR, COMMAND OF WS-SPI-INPUT, OBJECT-TYPE OF WS-SPI-INPUT GIVING WS-SS-RESULT MOVE "SSINIT of ZPWY-DDL-MSG-BUFFER" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR . 3100-SELECT-SERVERCLASS.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 15 of 28) 3300-SELECT-SCPROCESS. MOVE "3300-SELECT-SCPROCESS" TO WS-PARA-NAME * Clear, build, and put the object-selector token for the * server process into the buffer.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 16 of 28) 3800-ISSUE-PATHMON-COMMAND. IF OK-TO-CONTINUE THEN READ PATHMON-FILE WITH PROMPT ZPWY-DDL-MSG-BUFFER IF OK-TO-CONTINUE THEN * Protect against a long buffer being returned by a server. MOVE ZPWY-VAL-BUFLEN TO Z-BUFLEN OF ZPWY-DDL-MSG-BUFFER * Get the RETCODE token.
Management Programming Examples Configuring Pathway Example 16-1.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 18 of 28) PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Build and put the Pathway definition into the buffer.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 19 of 28) * * * * * * * USING ZPWY-MAP-SEL-SC, ZPWY-DDL-SEL-SC GIVING WS-SS-RESULT MOVE "SSNULL of ZPWY-DDL-DEF-PATHWAY" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR ENTER TAL "SSPUT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-MAP-SEL-SC, ZPWY-DDL-SEL-SC GIVING WS-SS-RESULT MOVE "SSPUT of ZPWY-DDL-SEL-SC" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR Next, issue the INFO SC command.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 20 of 28) END-IF * Point the startup volume to the current subvolume. STRING WS-STARTUP-VOLUME DELIMITED BY SPACE ".X " DELIMITED BY SIZE INTO WS-EXTERNAL-FILE-NAME MOVE SPACES TO WS-TEMPORARY-AREA * Convert the file name to internal format.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 21 of 28) MOVE "FILE4" TO FILE-NAME OF WS-FILE-NAME PERFORM 1100-ADD-SERVERCLASS-ASSIGN . 1100-ADD-SERVERCLASS-ASSIGN. MOVE "1100-ADD-SERVERCLASS-ASSIGN" TO WS-PARA-NAME * Construct the ADD SCASSIGN command.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 22 of 28) * Issue the ADD SCASSIGN command. PERFORM 3800-ISSUE-PATHMON-COMMAND . / 1500-START-SERVERCLASS. MOVE "1500-START-SERVERCLASS" TO WS-PARA-NAME * Construct the START SC command. MOVE ZPWY-CMD-START TO COMMAND OF WS-SPI-INPUT MOVE ZPWY-OBJ-SC TO OBJECT-TYPE OF WS-SPI-INPUT PERFORM 2800-SELECT-COMMAND-OBJECT * Construct the object-selector token for the server class.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 23 of 28) * Issue the STATUS SC cmd (ZPWY-DDL-PAR-STATUS-SC is not needed). PERFORM 3800-ISSUE-PATHMON-COMMAND * Display the results of the STATUS SC command. PERFORM 2600-DISPLAY-STATUS-SC . / 1800-TERMINATE. SET OK-TO-CONTINUE TO TRUE PERFORM 1900-SHUTDOWN-PATHWAY CLOSE PATHMON-FILE . 1900-SHUTDOWN-PATHWAY. * Construct the STOP PATHWAY command.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 24 of 28) GIVING WS-SS-RESULT MOVE "SSGET of ZPWY-DDL-SEL-SC" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Get the server class STATUS definition.
Management Programming Examples Configuring Pathway Example 16-1.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 26 of 28) MOVE "SSINIT of ZPWY-DDL-MSG-BUFFER" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR . 3100-SELECT-SERVERCLASS. MOVE "3100-SELECT-SERVERCLASS" TO WS-PARA-NAME * Clear, build, and put the object-selector token for the * server class into the buffer.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 27 of 28) * Clear, build, and put the object-selector token for the * server process into the buffer.
Management Programming Examples Configuring Pathway Example 16-1. TS/MP Configuration Program (page 28 of 28) 3800-ISSUE-PATHMON-COMMAND. IF OK-TO-CONTINUE THEN READ PATHMON-FILE WITH PROMPT ZPWY-DDL-MSG-BUFFER IF OK-TO-CONTINUE THEN * Protect against a long buffer being returned by a server. MOVE ZPWY-VAL-BUFLEN TO Z-BUFLEN OF ZPWY-DDL-MSG-BUFFER * Get the RETCODE token.
Management Programming Examples Adding or Altering a Server Adding or Altering a Server Example 16-2 presents a management program that opens a Pathway subsystem and issues an ADD SERVER or ALTER SERVER command. The example is a TACL macro written as a SPI requester and: 1. Determines whether the PATHMON process name and server name are supplied and checks that the names, as well as the command, are in a valid format 2.
Adding or Altering a Server Management Programming Examples Example 16-2.
Management Programming Examples Adding or Altering a Server Example 16-2.
Management Programming Examples Adding or Altering a Server Example 16-2. Adding or Altering a Server (page 3 of 5) [#IF [#EMPTYV T^svr^name] |THEN| #RESULT 0 #OUTPUT You must supply a valid server name !!!! |ELSE| #RESULT 0 #OUTPUT Unexpected argument in [#ROUTINENAME]: [#REST] ] == end if [emptyv t^filename] ..... ] == case [argument /text T^svr^name/ ...... #UNFRAME ] == end def r_format_server_name ..... == == Enter call routines to ensure that the PMONNAME, server name, and command are correct.
Management Programming Examples Adding or Altering a Server Example 16-2. Adding or Altering a Server (page 4 of 5) == == == Load the buffer (spi^buf). First, set the server name then load it into the buffer using #SSPUTV. Then set the server attributes and load them into the buffer.
Management Programming Examples Obtaining Subsystem Information Example 16-2. Adding or Altering a Server (page 5 of 5) == == == If an error is encountered, open the error list in the response buffer for access, extract the command from the response buffer, and extract the object type from the response buffer.
Obtaining Subsystem Information Management Programming Examples 8. Displays the results by extracting ZPWY-DDL-DEF-PATHWAY from the response buffer and displaying its contents This example calls the source file ASCICONV, which contains a routine to convert integers to strings, used to display things like error numbers. This source file is shown in Example 16-4. Supply the Pathway subsystem name (that is, $PM) in this example. Example 16-3.
Management Programming Examples Obtaining Subsystem Information Example 16-3. Obtaining Subsystem Information Program Example (page 2 of 2) == == Initialize the buffer (spi^buf) with the SSID (subsystem ID) value and the command that is to be executed. SINK [#SSINIT /TYPE 0/ spi^buf [zpwy^val^ssid] [zpwy^cmd^info] & /OBJECT [zpwy^obj^pathway]/] == == == == Initialize the ZPWY^DDL^STATUS^PATHWAY token with null values using ZPWY^MAP^STATUS^PATHWAY to determine how each field is to be initialized.
Obtaining Subsystem Information Management Programming Examples Example 16-4. ASCICONV Source File INT PROC ASCII (V,RJUST,STG); INT V; INT RJUST; STRING .STG; BEGIN STRING INT INT INT ! INT VALUE TO CONVERT ! RIGHT-JUSTIFY FLAG ! TARGET STRING .
17 Server Class DEFINE Examples This section provides two examples related to server class DEFINEs. Both examples are written in the TACL programming language. Adding a Server Class DEFINE Example 17-1 presents a functioning SPI requester that adds a DEFINE to a server class. No error handling is performed in this example. To use this example in your own environment, you must supply all values enclosed in brackets (< >). For example, you would change: .#ZSPI to: $PM.
Server Class DEFINE Examples Adding a Server Class DEFINE Example 17-1. ADD SCDEFINE Programming Example (page 2 of 3) [#DEF saved^define STRUCT BEGIN INT S^Define( 0: 475 ); END; ] == end #def saved^define == The "define^buf" structure is used to pass the DEFINE info to PATHMON. [#DEF define^buf STRUCT BEGIN INT SDLength; INT S^Define( 0: 475 ); END; ] == end #def define^buf #SET define^buf == == Save the DEFINE and put it in saved^define buffer.
Obtaining Server Class DEFINE Information Server Class DEFINE Examples Example 17-1. ADD SCDEFINE Programming Example (page 3 of 3) #SSPUTV spi^request^buf zpwy^map^sel^scdefine zpwy^ddl^sel^scdefine #SSPUTV spi^request^buf zpwy^tkn^def^scdefine define^buf == Open PATHMON and send the request.
Server Class DEFINE Examples Obtaining Server Class DEFINE Information Example 17-2. INFO SCDEFINE Programming Example (page 1 of 2) ?TACL MACRO #FRAME == == First load the SPI token definition files "ZPWYTACL" and "ZSPITACL". These files are usually located on $DSV.ZSPIDEF. #PUSH X^ Y^ == variable to load definition files into. This prevents == TACL from running out of segment space.
Obtaining Server Class DEFINE Information Server Class DEFINE Examples Example 17-2. INFO SCDEFINE Programming Example (page 2 of 2) == Set the serverclass and definename in the selector token. #SET zpwy^ddl^sel^scdefine:zname:zserverclass #SET zpwy^ddl^sel^scdefine:zname:zdefine == == Load the selector token and DEFINE information into the SPI request buffer. #SSPUTV spi^request^buf zpwy^map^sel^scdefine zpwy^ddl^sel^scdefine == Open PATHMON and send the request.
Server Class DEFINE Examples Obtaining Server Class DEFINE Information HP NonStop TS/MP Management Programming Manual—540082-005 17- 6
18 Error Handling Example Program This example management program decodes a Pathway subsystem SPI error list. It is written in COBOL. The program: 1. Obtains and interprets the ZSPI-TKN-RETCODE token and selects a table based on the range of ZSPI-TKN-RETCODE. For information on the ZSPI-TKNRETCODE token, see the SPI Programming Manual. 2. Locates and displays the error message text. 3.
Error Handling Example Program Example 18-1. Handling Errors (page 2 of 26) 05 WS-ERROR. 10 OBJECT-TYPE 10 OBJECT-FLAG 88 OBJECT-HAS-NO-NAME 88 OBJECT-HAS-NAME 10 NAME-TKN 10 INFO 05 WS-DECODE. 10 PARAMETER 10 OBJECT-FLAG 88 OBJECT-HAS-NO-NAME 88 OBJECT-HAS-NAME 10 OBJECT-TYPE-NAME 10 OBJECT-NAME-COUNT 10 OBJECT-NAME-TABLE. 15 OBJECT-NAME-1 15 OBJECT-NUMBER NATIVE-2 VALUE -1. PIC S9(4) COMP VALUE 0. VALUE 0. VALUE 1. NATIVE-4. NATIVE-2 VALUE -1. NATIVE-2 VALUE -1. PIC S9(4) COMP VALUE 0. VALUE 0. VALUE 1.
Error Handling Example Program Example 18-1. Handling Errors (page 3 of 26) 01 WS-COMMAND-NAMES REDEFINES WS-COMMAND-NAME-TABLE. 05 COMMAND-ENTRY PIC X(15) OCCURS 21 TIMES. 01 WS-OBJECT-TYPE-NAME-TABLE.
Error Handling Example Program Example 18-1. Handling Errors (page 4 of 26) 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC X(12) PIC 9 NATIVE-4. NATIVE-4. PIC X(12) PIC 9 NATIVE-4. NATIVE-4. PIC X(12) PIC 9 NATIVE-4. NATIVE-4.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1. Handling Errors (page 7 of 26) 05 05 05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE "DEF-SCPROGRAMOSS". "DEF-SCCWD". "DEF-SCSTDERR". "DEF-SCSTDIN". "DEF-SCSTDOUT". "DEF-SCENV". "DEF-SCARGLIST".
Error Handling Example Program Example 18-1. Handling Errors (page 8 of 26) 05 05 05 05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC X(19) S9(4) X(19) S9(4) X(19) S9(4) X(19) S9(4) X(19) S9(4) S9(4) X(19) S9(4) VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE "OSSATTRUSED". 4025. "OSSATTRTOOBIG". 4026. "INVALIDPATHNAME". 4027. "ARGENVEXCEEDSMAX".
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1. Handling Errors (page 12 of 26) 05 05 05 05 05 05 05 05 01 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC X(20) VALUE "OSSNOTAVAILABLE". PIC S9(4) VALUE 1160. PIC X(20) VALUE "PROCTYPEMISMATCH". PIC S9(4) VALUE 1161. PIC X(20) VALUE "RESIZESEGMENT". PIC S9(4) VALUE 1162. PIC X(20) VALUE "PRODUCTNOTLICENSED". PIC S9(4) VALUE 1164. WS-PM-ERROR-NAMES REDEFINES WS-PM-ERROR-NAME-TABLE.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1. Handling Errors (page 18 of 26) COPY ZPWY-DDL-SCTERMNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-SCTERMNAME BY ==ZPWY-DDL-SCTERMNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-TCPLINKNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-TCPLINKNAME BY ==ZPWY-DDL-TCPLINKNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-TCPNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-TCPNAME BY ==ZPWY-DDL-TCPNAME REDEFINES OBJECT-NAME-AREA==.
Error Handling Example Program Example 18-1. Handling Errors (page 19 of 26) PERFORM 500-DISPLAY-REQUEST-CMD PERFORM 600-DISPLAY-REQUEST-OBJTYPE PERFORM 700-DISPLAY-REQUEST-OBJNAME PERFORM 800-DISPLAY-PARM-ERROR PERFORM 900-DISPLAY-ERROR-CMD PERFORM 1000-DISPLAY-ERROR-OBJTYPE PERFORM 1100-DISPLAY-ERROR-OBJNAME PERFORM 1200-DISPLAY-ERROR-INFO EXIT PROGRAM . / 100-INITIALIZATION.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1. Handling Errors (page 21 of 26) 400-DISPLAY-SPI-ERROR. SEARCH ALL ERROR-ENTRY OF WS-SPI-ERROR-NAMES AT END DISPLAY "PATHMON SPI ERROR: " WS-SPI-RESULT WHEN ERROR-NUMBER OF WS-SPI-ERROR-NAMES ( SPI-ERROR-INDEX ) = WS-SPI-RESULT DISPLAY "PATHMON SPI ERROR: " ERROR-NAME OF WS-SPI-ERROR-NAMES ( SPI-ERROR-INDEX ) . 500-DISPLAY-REQUEST-CMD.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1. Handling Errors (page 23 of 26) / 1000-DISPLAY-ERROR-OBJTYPE.
Error Handling Example Program Example 18-1. Handling Errors (page 24 of 26) MOVE SPACES TO IMAGE OF WS-PRINT STRING " " DELIMITED "(%" DELIMITED NAME OF WS-NUMOUT DELIMITED ")" DELIMITED INTO IMAGE OF WS-PRINT END-STRING DISPLAY IMAGE OF WS-PRINT END-IF END-IF BY BY BY BY SIZE SIZE SIZE SIZE . / 1300-CHECK-SUBSYSTEM-ERROR. IF WS-SS-RESULT IS NOT ZERO THEN DISPLAY "SS ERROR: " WS-SS-RESULT END-IF . 1400-DECODE-OBJECT-TYPE.
Error Handling Example Program Example 18-1.
Error Handling Example Program Example 18-1.
Error Handling Example Program HP NonStop TS/MP Management Programming Manual—540082-005 18 -27
Error Handling Example Program HP NonStop TS/MP Management Programming Manual—540082-005 18 -28
A Configuration Limits and Defaults Table A-1 lists global limits for various items within each PATHMON environment. Note. These limits are subject to change with product SPRs or with new software releases. Table A-1. Global Pathway Environment Limits Item Limits Per PATHMON Environment (page 1 of 2) ASSIGNs Maximum total of 4095 (for TS/MP 2.0 and 2.1) or 8191 (for TS/MP 2.3) for all server classes.
Configuration Limits and Defaults Table A-1. Global Pathway Environment Limits Item Limits Per PATHMON Environment (page 2 of 2) Links Only one SCREEN COBOL program at a time can use a link (by performing a SEND). Only one Pathsend process at a time can use a link. For Pathway limits with ACS subsystem processes, see the TS/MP System Management Manual.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 1 of 9) PATHCOM Parameter* ARGLIST SPI Token/Field** Value Limits and Defaults ZPWY-TKNDEFSCARGLIST Values: OSS process startup argument list; from 2 to 24,000 characters. ZPWY-TKN-DEF-SCENV + ZPWY-TKN-DEF-SCARGLIST cannot exceed 24,000 bytes. Default: Empty argument list ASSOCIATIVE ZASSOCIATIVE Values: ON | OFF Default: OFF AUTORESTART ZAUTORESTART Values: 0 through 32,767 Value should be greater than 0.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 2 of 9) PATHCOM Parameter* CWD SPI Token/Field** Value Limits and Defaults ZPWY-TKNDEFSCCWD Values: Absolute OSS pathname of the current working directory.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 3 of 9) PATHCOM Parameter* SPI Token/Field** GUARDIANSWAP Value Limits and Defaults Values: Maximum of 10 disk volumes for SERVER objects. Default: Selected by operating system (from _DEFAULTS DEFINE statement, if available). HELP N.A. Values: 1000 through 3999 Default: N.A. HIGHPIN ZHIGHPIN Values: ON | OFF Suggested value is ON for new applications written for D-series systems.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 4 of 9) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXEXTERNALT CPS ZMAXEXTERNALT CPS Values: Total of values for MAXTCPS, MAXEXTERNALTCPS, and MAXLINKMONS must not exceed 800. Maximum number of concurrently running processes (TCP, external TCP, LINKMON or ACS subsytem processes, PATHCOM, and SPI) must not exceed 800.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 5 of 9) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXPATHCOMS ZMAXPATHCOMS Values: 1 through 100 Maximum number of concurrent openers of PATHMON (TCP, external TCP, LINKMON or ACS subsystem processes, PATHCOM, and SPI) must not exceed 800. For production, the value for this parameter should be large enough to allow for parallel interfaces (multiple PATHCOM and SPI processes).
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 6 of 9) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults MAXTCPS ZMAXTCPS Values: Total of values for MAXTCPS, MAXEXTERNALTCPS, and MAXLINKMONS must not exceed 800. Maximum number of concurrent openers of PATHMON (TCP, external TCP, LINKMON or ACS subsystem processes, PATHCOM, and SPI) must not exceed 800.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 7 of 9) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults NODEINDEPEND ENT ZNODEINDEPEND ENT Values: ON | OFF Default: OFF N.A. ZNODEINDEPEND ENTFORMAT Values: YES | NO Default: NO NUMSTATIC ZNUMSTATIC Values: 0 through 4095; must not exceed value of MAXSERVERS. The number of dynamic servers for a server class is MAXSERVERS minus NUMSTATIC.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 8 of 9) PATHCOM Parameter* SPI Token/Field** Value Limits and Defaults PROCESSTYPE ZPROCESSTYPE Values: GUARDIAN | OSS Default: GUARDIAN PROGRAM ZPROGRAM ZPWY-TKNDEFSCPROGRAM OSS Values: For Guardian server processes, the name of the Guardian object file name; 1 through 15 alphanumeric or hyphen characters; first character must be alphabetic.
Configuration Limits and Defaults Table A-2. Limits and Defaults for Parameters (page 9 of 9) PATHCOM Parameter* STDERR SPI Token/Field** Value Limits and Defaults ZPWY-TKNDEFSCSTDERR Values: Name of the OSS stderr (standard error) file. Must not exceed 1024 bytes. Default: None STDIN ZPWY-TKNDEFSCSTDIN Values: Name of the OSS stdin (standard input) file. Must not exceed 1024 bytes. Default: None STDOUT ZPWY-TKNDEFSCSTDOUT Values: Name of the OSS stdout (standard output) file.
Configuration Limits and Defaults HP NonStop TS/MP Management Programming Manual—540082-005 A -12
Index Numbers 32-byte file names 3-20/3-21 A Action events not supported 10-6 ADD SC command 9-2 ADD SCASSIGN command 9-5 ADD SCDEFINE command 9-7, 17-1/17-3 ADD SCPARAM command 9-8 ADD SCPROCESS command 9-10 ADD SCSTARTUP command 9-11 ALLOW-TYPE token not supported 2-7 ALTER SC command 9-13 ALTER SCASSIGN command 9-16 ALTER SCDEFINE command 9-17 ALTER SCPARAM command 9-18 ALTER SCPROCESS command 9-19 ALTER SCSTARTUP command 9-20 Applications management 2-3 Applications, steps for event processing 10-2 Arc
D Index Commands See also individual commands asynchronous abort not supported 2-6 building and sending 3-14/3-22 cancelling 2-6 command list 2-1/2-3 command modifier tokens, list of 7-1, 7-2 continuation for multiple objects 3-9, 3-17/3-19 numbers and symbolic names for 3-4/3-5 presentation format 3-28/3-29 receiving and decoding responses 3-22/3-23 restricting use 3-24/3-25 sending 2-5/2-6 symbolic names 3-28 Comment token 3-9 Common definitions buffer declaration 5-3 EMS standard 4-4 extensible structu
E Index Definitions (continued) predefined token and field values 5-18 private field types for predefined values 5-18/5-21 private token and field types 5-8/5-17 simple tokens 5-21 SPI standard 4-1/4-4 variable-length byte strings 6-1/6-6 DELETE SC command 9-21 DELETE SCASSIGN command 9-22 DELETE SCDEFINE command 9-24 DELETE SCPARAM command 9-25 DELETE SCPROCESS command 9-26 DELETE SCSTARTUP command 9-27 DELETEDELAY timer 7-15 Destinations for messages 10-4 Disk file, logging events to 10-4 Display-format
F Index F I Field references 3-23 Field types private 5-8/5-17 private for predefined values 5-18/5-21 Field values predefined 5-18 resetting 3-21 File extents size 7-23 File names, 32-byte 3-20/3-21 Files See Definitions files, Log files Filters, EMS compiling 10-17 description of 10-5 when to use 10-16/10-18 FNAME32COLLAPSE procedure 3-21 FNAME32EXPAND procedure 3-21 FNAME32TOFNAME procedure 3-21 FNAMETOFNAME32 procedure 3-21 Formatting messages 10-3 FREEZE SC command 9-28 FROZEN object state 3-19 in
M Index LINKMON processes (continued) system shutdown, relation to 8-15 TMF procedures, calling 9-29 Links description of 9-4 unused 9-5 Lists, presentation format 3-29 LM objects description of 3-6 name, selecting 7-36 STATUS command 8-12 status information 7-45 Log files error recovery 8-2 initial 10-3 LOG1 and LOG2 command, PATHCOM 10-3 M Management tasks See System management tasks Managing a Pathway subsystem 1-1/1-2, 1-6/1-7 Messages See also SCASSIGN objects, SCDEFINE objects, SCPARAM objects comm
N Index N Names, objects 5-3 Names, symbolic 10-6 Naming conventions for definition files 3-2 Naming guidelines (Zxxx) 3-25 Nested event messages 10-10 NEWPROCESS procedure, Guardian 2-4 Node independence See ZNODEINDEPENDENT field, ZNODEINDEPENDENTFORMAT field Nonprivileged processes (subtype 30) 10-16 NOWAIT depth 2-5 NOWAIT I/O operations 2-6 Null values 3-16, 3-29 Number ranges for messages 10-1 O Object file, OSS processes 6-4 Object name token 5-15 Objects See also individual object types authoriza
Q Index Pathname See OSS processes Pathsend restricting access to server class 7-21 PATHWAY object description of 3-6 INFO command 8-7 programming considerations 3-25 SHUTDOWN2 command 8-8 START command 8-10 STATUS command 8-13 STOP command 8-15 Pathway subsystem architecture 1-2/1-3 defining attributes 7-4/7-10 extensible structured tokens 7-1/7-55 ID 3-15 management program design 2-6/2-7 management programming interface 2-3/2-6 managing 1-1, 1-6/1-7 predefined token and field values 5-18 private field
S Index Reply messages 2-5/2-6 Requesters selecting 7-36 status 7-51 types of 7-51 Requests, cancelling 2-6 Reset constants 3-21 Resetting statistics counters 7-34 Responses, receiving and decoding summary 3-22/3-23 Response-control token 3-15 RESPONSE-TYPE token not supported 2-7 Restarts, specifying number allowed 7-13 Retrieving messages 2-5/2-6 Return token 3-23 Run priority 7-19, 7-28 RUNNING 3-19 RUNNING object state 3-19 S SC objects ADD command 9-2 ALTER command 9-13 authorization to access 7-21
S Index SCPROCESS objects (continued) defining attributes 7-26/7-28 DELETE command 9-26 description of 3-6 INFO command 9-35 name, selecting 7-38 programming considerations 3-26/3-27 START command 9-39 STATUS command 9-43 status information 7-54/7-55 SCREEN COBOL SEND call timeout 7-20 SEND statement statistics 7-42 STOP-MODE special register 9-29 SCSTARTUP objects ADD command 9-11 ALTER command 9-20 defining attributes 7-28 DELETE command 9-27 description of 3-6 INFO command 9-36 name, selecting 7-39 pro
T Index Statistics, collecting See ZSTATS field, STAT SCLM command STATS SCLM command 9-40 Status information See individual commands and object types STATUS LM command 8-12 STATUS PATHWAY command 8-13 STATUS PM command 8-13 STATUS PMREQUESTER command 8-14 STATUS SC command 9-42 STATUS SCPROCESS command 9-43 STOP PATHWAY command 8-15 STOP PM command 8-17 STOP SC command 9-44 STOPPED marker 3-27 STOPPED object state 3-19 Stopping See individual ABORT, SHUTDOWN2, and STOP commands STOP-MODE special register
U Index Terminals home, naming 7-16, 7-27 specifying maximum 7-9 Terminating See individual ABORT, SHUTDOWN2, and STOP commands THAW 2-3 THAW SC command 9-45 THAWED object state 3-19 TMF subsystem frozen server classes 9-29 invoking 7-20 response to thawing 9-47 TMFCOM 1-5 Token types fields in structured tokens 3-13/3-14 private 5-8/5-17 SPI standard 4-2 Token values, predefined 5-18 Tokens See also Attribute tokens, Comment token, Context token, Qualifier tokens arrays, unsupported 3-14 codes for object
Z Index ZBACKUP field ZPWY-DDL-CPU-PAIR 5-10 ZPWY-MAP-DEF-SC 7-14 ZPWY-MAP-DEF-SCPROCESS 7-26 ZBACKUPCPU field ZPWY-MAP-DEF-PATHWAY 7-6 ZPWY-MAP-PAR-CONTROL-PM 7-29 ZBLOCKSIZE field 7-24 ZCOLDSTARTTIME field 7-3 ZCOOLSTARTTIME field 7-3 ZCPUINFO field 7-13 ZCPUPAIR field ZPWY-MAP-DEF-SC 7-13 ZPWY-MAP-DEF-SCPROCESS 7-26 ZCPUPAIRCOUNT field 7-13 ZCPUWTINFO field 7-22 ZCREATEDELAY field ZPWY-DDL-DEF-SC 9-5 ZPWY-MAP-DEF-SC 7-14 ZCUR- fields, list of 7-10 ZDEBUG fieldC 7-15 ZDEFAULTVOLUME field 7-21 ZDEFINE fi
Z Index ZGUARDIANPAID field 7-52 ZGUARDIANPID field 7-52 ZHIGHPIN field 7-21 ZHOMETERM field 7-16, 7-27 ZIGNORE field 7-33 ZIGNORESTOPMODE field 7-31 ZIN field 7-17 ZINFO field 5-14 ZINFO2 field 5-13 ZIOINFO field 7-41 ZIOS field 7-42 ZLENGTH field ZPWY-MAP-DEF-SCPARAM 7-25 ZPWY-MAP-DEF-SCSTARTUP 7-28 ZLINKDEPTH field ZPWY-DDL-DEF-SC 9-4 ZPWY-MAP-DEF-SC 7-17 ZLINKMON field ZPWY-DDL-LMNAME 5-4 ZPWY-DDL-SCLMNAME 5-6 ZLINKMONS field ZPWY-MAP-STATUS-PATHWAY 7-47 ZLINKS field 7-55 ZLOCKED field 7-52 ZLOCKS fie
Z Index ZPWY-MAP-STATUS-LM 7-45 ZPWY-MAP-STATUSSCPROCESS 7-54 ZPROCESSTYPE field 7-22 ZPROGRAM field 7-19 ZPROGRAMUNIT field 5-5 ZPWYC file 3-28 ZPWYDDL file 5-1 ZPWYTMPL event object file 10-18 ZPWY-CMD- commands See also individual commands list of 3-4/3-5 ZPWY-DDL- definitions 0-100 5-17 0-4095 5-17 1-100 5-17 1-199 5-17 1-255 5-17 AUTO-RESTART 5-8 buffer declarations, list of 5-1 CHARnnn 5-8/5-9 CPU 5-10 CPU-PAIR 5-10 CTLSTATE-VALUE 5-19 DEFINE-NAME 5-10 DUMP-INFO 5-11 ERRINFO2 5-13 ERROR-INFO 5-14 FI
Z Index ZPWY-ERR-PM- errors (continued) CHECKCLOSE 12-50 CHECKOPEN 12-50 CHECKPOINT 12-49 CLASSNOTDEFINED 12-56 CONFIGDONE 12-6 CONFIGNOTDONE 12-7 CPTABLEFULL 12-74 DUMPNOTTAKEN 12-76 DUPNAME 12-8 EMPTYENTRY 12-9 EMSADDSUBJECT 12-80 EMSADDTOKENS 12-80 EMSBADDEVICETYPE 12-80 EMSDISABLED 12-79 EMSINIT 12-79 ENTRYLOCKED 12-10 ENTRYTYPEMISMATCH 12-11 EOF 3-23 FNS 12-73 FREEZEINPROGRESS 12-39 FREEZEPENDING 12-40 FSERROR 12-31 INTERNAL 12-21 INTERNALFATAL 12-51 INVALIDHOMETERM 12-60 IN-SHUTDOWN 12-83 LINEDOWN 1
Z Index ZPWY-ERR-PM- errors (continued) TCPPMIO 12-19 TCPREQUESTFAIL 12-36 TELLNOTCONFIG 12-45 TOOMANYENTRIES 12-37 TOOMANYPROG 12-72 TOOMANYSC 12-66 TOOMANYSCASSIGN 12-69 TOOMANYSCPARAM 12-70 TOOMANYSCPROCESS 12-67 TOOMANYSCSTARTUP 12-68 TOOMANYTCP 12-64 TOOMANYTELL 12-71 TOOMANYTERM 12-65 TRAPPED 12-53 UNINITIALIZEDPMON 12-86 USESEGMENT 12-77 ZPWY-ERR-SPI- errors ARGENVEXCEEDMAX 15-29 ATLEASTONE 15-23 BADCHECKSUM 15-12 BUFFEREXHAUSTION 15-32 CMDTOOBIG 15-22 CTLPMNAMEMISMATCH 15-20 CTLSTATEMISMATCH 15-21
Z Index ZPWY-EVT-PM- events (continued) DELINKFAIL 11-8 DISABLEAUTORESTART 11-69 DUMPNOTTAKEN 11-71 DUMPTAKEN 11-51 DUPNAME 11-9 EMPTYENTRY 11-10 ENTRYTYPEMISMATCH 11-11 FROZENSTATUS 11-48 FSERROR 11-40 INTERNAL 11-21 INTERNALFATAL 11-58 INTERNALTABLE 11-77 LINEDOWN 11-62 LINKFAIL 11-7 LOG1IO 11-16 LOG1OFF 11-23 LOG1ON 11-24 LOG2IO 11-17 LOG2OFF 11-25 LOG2ON 11-26 NAMENOTDEFINED 11-30 NEWPROCESS 11-33 NODISKSPACE 11-27 NOFREESPACE 11-28 NOSCPROCESS 11-29 OSSNOTAVAILABLE 11-85 OSSPROCESSFAILURE 11-81 PARTI
Z Index ZPWY-MAP-PAR- modifier tokens category description 7-1 CONTROL-PM 7-28 FREEZE-SC 7-31 INFO 7-31 SHUTDOWN 7-32 START-PATHWAY2 7-33 STATS-SCLM 7-34 STATUS-SC 7-35 ZPWY-MAP-QUAL- object qualifier tokens category description 7-1 SC 7-35 ZPWY-MAP-SEL- selection tokens category description 7-2 LM 7-36 PMREQUESTER 7-36 SC 7-36 SCASSIGN 7-37 SCDEFINE 7-37 SCLM 7-38 SCPARAM 7-38 SCPROCESS 7-38 SCSTARTUP 7-39 ZPWY-MAP-STATS-SC statistics token category description 7-2 field descriptions 7-40/7-44 ZPWY-MAP-S
Z Index ZPWY-TKN- nested message tokens (continued) TIMEOUTVALUE 10-11 TRAP 10-11 UNSOLCOUNT 10-11 UNSOLREJECTEDERROR 10-11 USERID 10-11 ZPWY-TKN- standard tokens EVENTCLASS 10-9 HASNESTED 10-9 HASPULOC 10-9 HASSUBJECT2 10-9 nnnNAME 10-9 ZPWY-TKN- subject tokens FNAME 10-10 LMNAME 10-10 PMNAME 10-10 PROGNAME 10-10 SCNAME 10-10 TCPNAME 10-10 TELLNAME 10-10 TERMNAME 10-10 UNKOWNNAME 10-10 ZPWY-TKN- tokens DEF-SCARGLIST 6-1 DEF-SCCWD 6-2 DEF-SCDEFINE 6-3 DEF-SCENV 6-3 DEF-SCPROGRAMOSS 6-4 DEF-SCSTDERR 6-4 DE
Z Index ZPWY-VAL- values (continued) OSSGUARDIAN 5-20, 7-35 OUTPUT 7-23 PATHCOM 7-51 PATHWAYTS 12-91 PENDING 5-20, 7-35, 7-53, 7-54 predefined values, list of 5-2 PROCCREATxxx 5-13 PROGDONE 7-52 REQBUF 7-52 RESETnnn, list of 3-21 RUNNING 5-20, 7-3, 7-48, 7-49, 7-54 SCPROCESS2 5-7, 5-16 SERVERCLASS2 5-5, 5-16 SHUTDOWN 7-48 SHUTDOWNFAILED 7-48 SHUTTINGDOWN 7-49 SPI 7-51 SSID 3-15, 5-18 STARTBACKUP 7-52 STARTING 7-48, 7-49 STATUSEVENT 10-9 STOPPED 5-20, 7-48, 7-49, 7-54 SUPER 5-21 SUSPENDED 5-20, 7-54 SYSMSG
Special Characters Index ZSPI-TKN- tokens ALLOW-TYPE not supported 3-24 COMMAND 4-3 COMMENT 3-9 CONTEXT 3-9, 3-22 DATALIST 3-22 ENDLIST 3-23 ERRLIST 3-22, 3-23 header, list of 4-1, 4-2 MANAGER 10-6, 10-9 MAXRESP 3-15 OBJECT-TYPE 4-3 RESPONSE-TYPE not supported 3-23 RETCODE 3-23 SERVER-BANNER 4-3 SERVER-VERSION 4-3 simple, list of 4-2 special, list of 4-2 SSID 4-4 USEDLEN token 10-4 ZSPI-TKN-ERRLIST nested message token 10-10 ZSPI-TYP-xxx token types, list of 4-2 ZSPI-VAL-xxx values, list of 4-3 ZSTART fie
Special Characters Index HP NonStop TS/MP Management Programming Manual—540082-005 Index -22
