TS/MP 2.5 Management Programming Manual

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series

HP NonStop TS/MP 2.5 Management

Programming Manual

HP Part Number: 679665-002

Published: May 2012

Edition: J06.03 and subsequent J-series RVUs and H06.05 and all subsequent H-series RVUs

Summary of content (393 pages)

PAGE 1
HP NonStop TS/MP 2.5 Management Programming Manual HP Part Number: 679665-002 Published: May 2012 Edition: J06.03 and subsequent J-series RVUs and H06.
PAGE 2
© Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
PAGE 3
Contents About This Manual........................................................................................9 Product Version........................................................................................................................9 Supported Release Version Updates (RVUs)..................................................................................9 Intended Audience....................................................................................................................
PAGE 4
Receiving and Decoding Response Messages.............................................................................44 Summary of Steps..............................................................................................................44 Considerations..................................................................................................................44 Error Handling......................................................................................................................
PAGE 5
ZPWY-DDL-0-100...............................................................................................................66 ZPWY-DDL-0-4095.............................................................................................................66 ZPWY-DDL-0-8191..............................................................................................................66 ZPWY-DDL-1-100................................................................................................................
PAGE 6
ZPWY-MAP-SEL-SCPROCESS..................................................................................................103 ZPWY-MAP-SEL-SCSTARTUP...................................................................................................103 ZPWY-MAP-SRVFORSP .........................................................................................................103 ZPWY-MAP-STATS-SC............................................................................................................
PAGE 7
STATS SCLM........................................................................................................................158 STATUS SC..........................................................................................................................159 STATUS SCPROCESS.............................................................................................................160 STOP SC...........................................................................................................
PAGE 8
Listed Tokens...................................................................................................................268 Unlisted Tokens................................................................................................................268 Subject Tokens.................................................................................................................269 Error Presentation....................................................................................................
PAGE 9
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 describes the TS/MP and Pathway/iTS products. The contents of these two products are: • TS/MP: This product consists of the PATHMON process, the application cluster services (ACS) subsystem processes, the PATHCOM process and interface, and the Pathsend procedure calls.
PAGE 10
Figure 1 Related Documentation For information specific to managing a Pathway subsystem, see: Table 1 Related Manuals Document Name Description 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.
PAGE 11
Table 1 Related Manuals (continued) Document Name Description Guardian Procedure Errors and Messages Manual This manual describes the Guardian messages for NonStop systems. The manual covers error codes and error lists associated with Guardian procedure calls, the interprocess messages sent to application programs by the operating system and the command interpreter. For information on other TS/MP interfaces, see: TS/MP 2.
PAGE 12
• Added a new token in the ZPWY-MAP- definitions, “ZPWY-MAP-SRVFORSP ” (page 103). • In section Log File Error Recovery, updated the list under “Considerations” (page 119). • In section GETVERSION, added limitations, “Limitations” (page 119). • Added a new SPI command, “SRVFORSP” (page 155). • Updated the 1166 EMS Message, “1166: ZPWY-EVT-PM-AUDITSTATUS” (page 222). • Merged LINKMON Messages and ACS Subsystem Messages in, “ACS Subsystem Messages” (page 267).
PAGE 13
Sections Description Section 16, “Server Class DEFINE Examples” (page 343) Provides examples of management applications that work with server class DEFINE information. The examples are written in the TACL programming language. Section 17, “Error Handling Example Program” (page 349) Provides an example of an error-handling program. Appendix A, “Configuration Limits and Defaults” (page 372) Summarizes TS/MP configuration limits and defaults.
PAGE 14
An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown.
PAGE 15
LDEV ldev [ CU %ccu | CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] { } Braces A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X | Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request.
PAGE 16
Include the document title, part number, and any comment, error found, or suggestion for improvement regarding this document.
PAGE 17
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.
PAGE 18
Table 3 Configuration and Manual Correspondences (continued) If Your Configuration Includes… Servers You Need… To Perform these actions… Section 17 See error-handling examples Section 9 Define and control SERVER objects Architecture and Components The Pathway subsystem includes a group of related software tools that enable your organization to develop, install, and manage online transaction processing applications.
PAGE 19
Figure 2 A TS/MP Application With Pathway/iTS 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.
PAGE 20
• Handle events (such as errors or changes in state) through a single mechanism, regardless of which subsystem originated the event. • Build an integrated and uniform approach to problem determination, including uniform reporting of events that call for operator action (for instance, a request that an operator mount a tape); ways to tailor event reporting to your own needs; and means for responding to events programmatically, without operator intervention.
PAGE 21
subsystem and directs activities. Figure 4 (page 21) illustrates these two interfaces and their relationship to a PATHMON process. Figure 4 TS/MP Management Interfaces PATHCOM Interface PATHCOM is a command language interpreter and an 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.
PAGE 22
Figure 5 Management Programming Environment 22 Introduction
PAGE 23
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. The 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.
PAGE 24
Table 4 PATHCOM and SPI Commands for TS/MP (continued) PATHCOM Commands and Object Types Equivalent SPI Commands (ZPWY-CMD- ) and Object Types (ZPWY-OBJ- ) No equivalent GETVERSION No equivalent GETVERSION PM PRIMARY PATHMON SWITCH PM SET PATHMON START PATHWAY SET PATHWAY START PATHWAY SHUTDOWN STOP (all objects) + ABORT TERM + FREEZE SC + STOP PATHWAY SHUTDOWN2 SHUTDOWN2 PATHWAY START PATHWAY INFO PATHCTL + START PATHWAY STATUS PATHMON STATUS PM STATUS PMREQUESTER STATUS PATHWAY STATUS
PAGE 25
Table 4 PATHCOM and SPI Commands for TS/MP (continued) PATHCOM Commands and Object Types STATUS SERVER, PROCESSES Equivalent SPI Commands (ZPWY-CMD- ) and Object Types (ZPWY-OBJ- ) STATUS SC + STATUS SCPROCESS + STATUS TCPLINK (STATUS TCPLINK is a Pathway/iTS command nl STOP SERVER STOP SC THAW SERVER THAW SC Pathway Management Programming Interface The Pathway Management Programming interface is a token-oriented interface based on the SPI message format, procedures, and definition files.
PAGE 26
across a network, a maximum of five characters is allowed—a dollar sign followed by four alphanumeric characters (for example, $abc2). #ZSPI identifies the application as using the SPI interface and directs the PATHMON process to process requests and replies using the SPI procedures. Considerations When Opening PATHMON When opening the PATHMON process programmatically, consider: • The PATHMON process can be opened by multiple user processes.
PAGE 27
Figure 6 Sending Commands and Receiving Responses For a detailed description of how to build command messages and decode responses, see “SPI Programming Considerations” (page 29). Details on the SPI procedures and their use with various languages are available in the SPI Programming Manual.
PAGE 28
• Security is implemented for specific groups of commands and is described under “Security” (page 45). For information about implementing security for access to the PATHMON process, see the Safeguard Reference Manual. • SPI and the NonStop subsystems that support it are designed such that, under most circumstances, you can install a new release of HP NonStop software on any one of your systems without changing your existing management applications.
PAGE 29
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 information about SPI programming and discusses SPI programming considerations specific to the Pathway subsystem.
PAGE 30
ZSPIDEF.ZsubsysTACL ZSPIDEF.ZsubsysTAL subsys is a three-character code identifying the subsystem or other software component to which these definitions belong. The code for the Pathway subsystem is PWY. The last characters of each file name denote the language in which the definitions in this file are coded.
PAGE 31
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.ZSPICOB ZSPIDEF.ZPWYCOB ZSPIDEF.ZEMSCOB If your application manages subsystems other than Pathway, it also needs the definition files required by those subsystems.
PAGE 32
Table 5 TS/MP Programmatic Commands (continued) Command Description ZPWY-CMD-FREEZE Prohibits all link managers (such as ACS subsystem process or Pathway/iTS TCPs) from sending requests to a server class if the object is not active ZPWY-CMD-GETVERSION Obtains the version of an object ZPWY-CMD-INFO Obtains the configuration of an object ZPWY-CMD-SHUTDOWN2 Stops a Pathway subsystem more quickly and easily than the STOP PATHWAY command ZPWY-CMD-START Initiates operation of an object ZPWY-CMD-STATS
PAGE 33
Table 6 TS/MP Object Types (continued) Object Type Description terminal control process (TCP), or other requesters described in the STATUS PMREQUESTER command. Server Class Objects ZPWY-OBJ-SC A server class, which is a group of server processes that perform a specific type of work. All processes within a server class run copies of the same server program. A server class can contain either Guardian processes or HP NonStop Open System Services (OSS) processes, but not both.
PAGE 34
Figure 7 Commands and Objects Object Names In the Management Programming interface to the Pathway subsystem, the form of an object name depends on the object type. “Token Codes for Object Names” (page 55) describes the name formats for objects of each type. 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.
PAGE 35
described in “SPI Error Messages” (page 305). Messages returned to servers from TCPs are described in the Pathway/iTS Management Programming Manual. Other Tokens Commands, responses, and event messages for the Pathway subsystem, like those for other subsystems, also include other tokens providing further information. Comment Token ZSPI-TKN-COMMENT is a token that a requester can use to include arbitrary information of its own in a command.
PAGE 36
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; ... ... ... INT END; ZBLOCKSIZE; 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.
PAGE 37
INT INT INT INT ZEXCLUSION; ZACCESS; ZRECORDSIZE; ZBLOCKSIZE; 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 Many
PAGE 38
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. Definitions for Pathway subsystem private token and field types are in “ZPWY-DDL- Definitions” (page 53), “ZPWY-TKN- Definitions” (page 71), and “ZPWY-MAP- Definitions” (page 75).
PAGE 39
Using ZSPI-TKN-MAXRESP ZSPI-TKN-MAXRESP is used by some subsystems to enable multiple responses in a single response buffer. Because the Pathway subsystem does not support multiple responses in a single response buffer, ZSPI-TKN-MAXRESP is only useful if your management application must handle all subsystems in a consistent manner; that is, if Pathway responses must be enclosed in data lists. To reference the Pathway subsystem alone, you do not have to specify ZSPI-TKN-MAXRESP.
PAGE 40
default values in each optional field. Consequently, the program does not have to determine either the PATHMON process null values or the defaults. Specifying Continuation As 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 sub-objects with a single command.
PAGE 41
Predefined Value Definition ZPWY-VAL-ALLSC Multiple server classes ZPWY-VAL-ALLSCASSIGNLF Multiple logical-file names in a server class ASSIGN message ZPWY-VAL-ALLSCASSIGNPU Multiple program-unit names in a server class ASSIGN message ZPWY-VAL-ALLSCDEFINE Multiple server class DEFINE definitions ZPWY-VAL-ALLSCPARAM Multiple server class PARAM messages ZPWY-VAL-ALLSCPROCESS Multiple server processes These values have the same meaning as the asterisk (*) used in the PATHCOM commands.
PAGE 42
Table 7 Required Object States for Continuation (continued) Command Object Type Required State STOP SC RUNNING, FROZEN THAW SC FROZEN Continuation Example These steps describe what occurs when a management application obtains information about the SC objects named CLASS-A, CLASS-B, and CLASS-C: The Application… The PATHMON Process… 1. Specifies ZPWY-CMD-INFO and ZPWY-OBJ-SC with the SSINIT call. 2. Assigns the constant ZPWY-VAL-ALLSC to the ZSERVERCLASS field in ZPWY-DDL-SEL-SC. 3.
PAGE 43
Example 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.
PAGE 44
Resetting Fields With the TACL Program To reset fields of type FNAME32, CRTPID, or SUBVOL with the TACL program, you must use the #SETBYTES built-in function. More information on resetting fields with the #SETBYTES built-in function is available in the SPI Programming Manual. Receiving and Decoding Response Messages These subsections summarize the steps required to receive and decode SPI command responses.
PAGE 45
perform the command. An error is a serious condition that prevents the command from being completed. If the command completes with no errors, the value of the return token is zero. If ZSPI-TKN-RETCODE has any nonzero value, it means an error has occurred. In this case, the PATHMON process includes an error list in the response, providing information about the error. A warning reports a condition less serious than that of an error.
PAGE 46
Table 9 Restricted Commands and Objects for TS/MP (continued) To Control… Use These Restricted (Sensitive) Commands (ZPWY-CMD- ) and Object Types (ZPWY-OBJ- )… SCASSIGN SCPARAM SCPROCESS ZSCSTARTUP FREEZE SC START SC SCPROCESS STOP SC THAW SC Any user can issue all of the other commands. Naming Guidelines for Applications By convention, HP uses names beginning with the letter Z (lowercase z in the C language) for all definitions and all component fields of structures in the definition files.
PAGE 47
Server Objects When developing a management application that defines and manages server classes, consider: • To add a full server class definition, issue an ADD SC command followed by ADD commands for each of the optional object types desired, namely SCPROCESS, SCASSIGN, SCPARAM, and SCSTARTUP. • When you delete an SC object, all associated objects for that SC are also deleted. • An associative server is a process within a server class.
PAGE 48
NOTE: 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 is implemented or permanent. Writing C Programs This subsection contains special considerations for writing C programs. Building the DDL Dictionary The DDL command ?CFIELDALIGN_MATCHED2 allows the DDL compiler to generate C data structures starting on byte boundaries.
PAGE 49
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 can 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.
PAGE 50
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.
PAGE 51
Table 12 SPI Standard Definitions for Special Tokens ZSPI-TKN-ADDR ZSPI-TKN-CLEARERR ZSPI-TKN-COUNT ZSPI-TKN-DATA-FLUSH ZSPI-TKN-DEFAULT-SSID ZSPI-TKN-DELETE ZSPI-TKN-INITIAL-POSITION ZSPI-TKN-LEN ZSPI-TKN-NEXTCODE ZSPI-TKN-NEXTTOKEN ZSPI-TKN-OFFSET ZSPI-TKN-RESET-BUFFER ZSPI-TKN-USEDLEN nl nl nl nl nl nl nl nl nl nl nl Table 13 SPI Standard Definitions for Token Types ZSPI-TYP-BOOLEAN ZSPI-TYP-BYTESTRING ZSPI-TYP-CHAR8 ZSPI-TYP-CRTPID ZSPI-TYP-DEVICE ZSPI-TYP-ENUM ZSPI-TYP-INT ZSPI-TYP-INT-PAI
PAGE 52
ZSPI-TKN-SSID contains ZPWY-VAL-SSID, the subsystem ID of the Pathway subsystem with this structure: def ZPWY-VAL-SSID 02 Z-FILLER Tacl SSID. token-type ZSPI-DDL-CHAR 8 value ZSPI-VAL-TANDEM. nl 02 Z-OWNER token-type ZSPI-DDL-CHAR 8. redefines Z-FILLER nl 02 Z-NUMBER token-type ZSPI-DDL-INT. value ZSPI-SSN-ZPWY. nl 02 Z-VERSION token-type ZSPI-DDL-INT value ZPWY-VAL-VERSION. nl end. ZSPI-SSN-ZPWY is the subsystem number assigned to the Pathway subsystem.
PAGE 53
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.
PAGE 54
Table 20 TS/MP Private Token and Field Types (continued) ZPWY-DDL-ERROR-INFO ZPWY-DDL-FILLER NOTE: The Pathway subsystem types listed in Table 20 (page 53) are used only as a basis for defining other types. These types indicate the structure parts of other types, but your programs not refer to them directly. Therefore, to save space, TS/MP does not produce programming-language declarations for them. A few type names are not described; instead they are expanded into their component fields.
PAGE 55
is a message buffer of the appropriate size for use with the SPI procedures in applications that manage Open System Services (OSS) server processes. def ZPWY-DDL-MAX-MSG-BUFFER. 02 Z-MSGCODE token-type ZSPI-DDL-INT. 02 Z-BUFLEN token-type ZSPI-DDL-INT. 02 Z-OCCURS token-type ZSPI-DDL-INT. 02 Z-FILLER token-type ZSPI-DDL-CHAR occurs 0 to ZPWY-VAL-MAX-BUFLEN times depending on Z-OCCURS. end. This buffer message declaration is also defined in the ZSPIDEF.
PAGE 56
ZPWY-DDL-PMREQUESTERNAME ZPWY-DDL-PMREQUESTERNAME identifies a requester of the PATHMON process. (For a complete list of possible requesters, see the description of the ZREQTYPE field under “ZPWY-DDL-PMREQUESTERNAME” (page 56).) def ZPWY-DDL-PMREQUESTERNAME. 02 ZNUMBER token-type ZSPI-DDL-CHAR-PAIR. end. ZNUMBER contains a number identifying the requester. ZPWY-DDL-SCNAME ZPWY-DDL-SCNAME identifies a server class. def ZPWY-DDL-SCNAME. 02 ZSERVERCLASS token-type ZPWY-DDL-OBJECT-NAME.
PAGE 57
ZLOGICALUNIT specifies the name assigned to a file and file attributes and contains these fields: ZPROGRAMUNIT specifies the name of the server process in the source program. In COBOL, the source program name for the server is the PROGRAM ID name. The program name can be different from the file name for the source code or for the run unit. If the server is a subprogram, this name is used in the CALL statement. ZLOGICALFILE specifies the name of the file in the server program.
PAGE 58
ZPWY-DDL-SCPARAMNAME ZPWY-DDL-SCPARAMNAME identifies a PARAM message and the server class with which it is associated. def ZPWY-DDL-SCPARAMNAME. 02 ZSERVERCLASS token-type ZPWY-DDL-OBJECT-NAME. 02 FILLER token-type ZPWY-DDL-FILLER. 02 ZPARAM token-type ZPWY-DDL-CHAR31. 02 FILLER-1 token-type ZPWY-DDL-FILLER. end. 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.
PAGE 59
ZPWY-DDL-SCSTARTUPNAME ZPWY-DDL-SCSTARTUPNAME identifies a startup message and the server class to be associated with that message. def ZPWY-DDL-SCSTARTUPNAME. 02 ZSERVERCLASS token-type ZPWY-DDL-OBJECT-NAME. 02 FILLER-1 token-type ZPWY-DDL-FILLER. end. 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.
PAGE 60
times. 03 FILLER 02 Z-B redefines Z-C pic X pic X occurs 15 times. end. 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 pic X(24). 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C type BINARY 16 pic X occurs 12 times occurs 24 times. end. 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 pic X(31).
PAGE 61
ZPWY-DDL-CHAR132 ZPWY-DDL-CHAR132 designates 132 ASCII characters, addressable as a STRUCT, as bytes or as integers. def ZPWY-DDL-CHAR132. 02 Z-C pic X(132). 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C type BINARY 16 pic X occurs 66 times. occurs 132 times. end. ZPWY-DDL-CPU ZPWY-DDL-CPU is the CPU number of a particular processor in a system. Valid values range from 0 to 15. def ZPWY-DDL-CPU token-type ZSPI-DDL-INT. ZPWY-DDL-CPUWT ZPWY-DDL-CPUWT is the weight of a defined processor (CPU).
PAGE 62
CHAR24. A DEFINE name can be from 2 to 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.
PAGE 63
If you do not specify a file name, then the PATHMON process creates the dump file on the same volume and subvolume as the PATHMON configuration file. The format of the file names are ZZPMnnP and ZZPMnnB, where nnis a number from 01 to 10, and P and B indicate the primary or the backup process, respectively, that the PATHMON process dumped. For more information on PATHMON dump files, see the CONTROL PM command description in the TS/MP System Management Manual.
PAGE 64
This example shows error information returned in ZERRORINFO and ZERRORINFO2: ZERRORINFO ZERROR ZINFO 1038 %001413 ZERRORINFO2 ZERROR2 ZINFO2 ZDETAIL2 1038 1 11 ZPWY-DDL-ERROR-INFO ZPWY-DDL-ERROR-INFO provides error information. def ZPWY-DDL-ERROR-INFO. 02 ZERROR token-type ZPWY-DDL-INT. 02 ZINFO token-type ZPWY-DDL-INT. end. ZERROR contains a Pathway environment error number. The error numbers are described by symbolic names in the TS/MP System Management Manual.
PAGE 65
ZPWY-DDL-ON-OFF ZPWY-DDL-ON-OFF specifies whether a feature or capability (such as using an Inspect process or TMF auditing) is enabled. def ZPWY-DDL-ON-OFF token-type ZSPI-DDL-BOOLEAN. Values can be ZPWY-VAL-ON or ZPWY-VAL-OFF; their meanings are further described in the fields in which they occur. NOTE: ZPWY-VAL-ON is equivalent to ZSPI-VAL-TRUE, and ZPWY-VAL-OFF is equivalent to ZSPI-VAL-FALSE, neither of which are supported in COBOL.
PAGE 66
ZPWY-VAL-SERVERCLASS2 ZPWY-DDL-SCPROCESS-VERSION ZPWY-DDL-SCPROCESS-VERSION is the version of a requester. This token, although supplied by requesters, is used only by TS/MP servers. def ZPWY-DDL-SCPROCESS-VERSION token-type ZSPI-DDL-ENUM. The valid value is: ZPWY-VAL-SCPROCESS2 ZPWY-DDL-TIME-TYPE ZPWY-DDL-TIME-TYPE is a 64-bit Julian timestamp or elapsed time in microseconds. def ZPWY-DDL-TIME-TYPE token-type ZSPI-DDL-TIMESTAMP. ZPWY-DDL-YES-NO ZPWY-DDL-YES-NO specifies a yes or no decision.
PAGE 67
ZPWY-DDL-1-199 ZPWY-DDL-1-199 is a value from 1 to 199. def ZPWY-DDL-1-199 token-type ZSPI-DDL-INT. ZPWY-DDL-1-255 ZPWY-DDL-1-255 is a value from 1 to 255. def ZPWY-DDL-1-255 token-type ZSPI-DDL-INT. 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.
PAGE 68
ZPWY-DDL-FILESTATE-VALUE ZPWY-DDL-FILESTATE-VALUE specifies the state of a file. def ZPWY-DDL-FILESTATE-VALUE token-type ZSPI-DDL-ENUM. Valid values are ZPWY-VAL-CLOSED or ZPWY-VAL-OPEN. ZPWY-DDL-FRZSTATE-VALUE ZPWY-DDL-FRZSTATE-VALUE specifies the freeze state of a server class as returned to a program making a status request. def ZPWY-DDL-FRZSTATE-VALUE token-type ZSPI-DDL-ENUM. Values are described with “ZPWY-MAP-PAR-STATUS-SC” (page 100).
PAGE 69
The valid values are: ZPWY-VAL-GUARDIAN Server processes are Guardian processes. ZPWY-VAL-OSS Server processes are OSS processes. ZPWY-VAL-OSSGUARDIAN Server processes can be either Guardian or OSS processes. ZPWY-DDL-PROCESSTYPE-VALUE ZPWY-DDL-PROCESSTYPE-VALUE specifies the type of server processes in a server class. def ZPWY-DDL-PROCESSTYPE-VALUE token-type ZSPI-DDL-ENUM. The valid values are: ZPWY-VAL-GUARDIAN Server processes are Guardian processes.
PAGE 70
ZPWY-DDL-RBMODE-VALUE ZPWY-DDL-RBMODE-VALUE identifies the value of pathway attribute SPREBALANCEMODE set by the user. def ZPWY-DDL-RBMODE-VALUE token-type ZSPI-DDL-ENUM. The valid values are: ZPWY-VAL-DISABLE SPREBALANCEMODE is set as DISABLE. ZPWY-VAL-AUTO SPREBALANCEMODE is set as AUTO. ZPWY-VAL-MANUAL SPREBALANCEMODE is set as MANUAL. Simple Tokens A simple token has a value consisting of a single field or a fixed structure.
PAGE 71
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.
PAGE 72
ZPWY-TKN-DEF-SCCWD This token is the absolute OSS pathname of the current working directory of an OSS server process. This value is used to resolve relative pathnames specified for other OSS server process attributes in the server class. def ZPWY-TKN-DEF-SCCWD token-type ZSPI-TYP-BYTESTRING. 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. Case is significant. The length cannot exceed 1024 bytes.
PAGE 73
If you do not assign a value for this field when adding a server class, then no environmental information is sent to the server processes in this server class. 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. This token is returned in the response buffer of an INFO command only if a value is defined. This field is valid for OSS server processes only.
PAGE 74
ZPWY-TKN-DEF-SCSTDIN This token is the name of the OSS stdin (standard input) file used by the OSS servers in a server class. This file is opened only for read operations. def ZPWY-TKN-DEF-SCSTDIN token-type ZSPI-TYP-BYTESTRING. 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.
PAGE 75
7 ZPWY-MAP- Definitions This section discusses the 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.
PAGE 76
Table 25 TS/MP Extensible Structured Tokens (continued) ZPWY-MAP-PAR-SHUTDOWN Qualifier tokens ZPWY-MAP-QUAL-SC Selector tokens ZPWY-MAP-SEL-LM ZPWY-MAP-SEL-PMREQUESTER ZPWY-MAP-SEL-SC ZPWY-MAP-SEL-SCASSIGN ZPWY-MAP-SEL-SCDEFINE nl nl nl ZPWY-MAP-SEL-SCLM ZPWY-MAP-SEL-SCPARAM ZPWY-MAP-SEL-SCPROCESS ZPWY-MAP-SEL-SCSTARTUP nl nl nl nl Statistics tokens ZPWY-MAP-STATS-SC Status tokens ZPWY-MAP-STATUS-LM ZPWY-MAP-STATUS-PATHWAY ZPWY-MAP-STATUS-PM ZPWY-MAP-STATUS-PMREQUESTER nl ZPWY-MAP-STATUS-SC Z
PAGE 77
ZCOLDSTARTTIME is the original cold start time as recorded in the PATHMON configuration file. ZCOOLSTARTTIME is the time the most recent cool start was done, as recorded in the PATHMON configuration file. If cool start was not done, then ZCOOLSTARTTIME has the same value as ZCOLDSTARTTIME. 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 the Pathway subsystem.
PAGE 78
02 ZCURPARAMS 02 ZCURPATHCOMS 02 ZCURPROGRAMS 02 ZCURSERVERCLASSES 02 ZCURSERVERPROCESSES 02 ZCURSPI 02 ZCURSTARTUPS 02 ZCURTCPS 02 ZCURTELLS 02 ZCURTERMS 02 ZMAXDEFINES 02 ZCURDEFINES 02 ZNODEINDEPENDENT 02 ZDUMASK 02 ZSPREBALANCEMODE end. token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZPWY-DDL-0-4095. ZPWY-DDL-0-4095. ZPWY-DDL-0-100. ZPWY-DDL-0-4095. ZPWY-DDL-0-4095.
PAGE 79
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 to 4095. This is a required field; no default.
PAGE 80
ZMAXSTARTUPS is the maximum number of server classes that can have STARTUP messages. The value must be a number from 0 to 4095. To enable PATHMON process to run the equivalent of the PATHCOM ALTER SERVER STARTUP command, specify a maximum of 4094 for this attribute. Because only one STARTUP definition for each server class counts toward this limit, the number for this field not exceed the value for ZMAXSERVERCLASSES. This is a required field; no default.
PAGE 81
If you do not assign a value to this field, then the default is ZPWY-VAL-N. ZMAXDEFINES is the maximum number of ADD SCDEFINE definitions that you can specify for all server classes in a PATHMON environment. This field has the same meaning as the MAXDEFINES parameter in the PATHCOM SET PATHWAY command. Each ADD SCDEFINE definition counts as one towards the value of this parameter. The value must be a number from 0 to 8191. The maximum number of DEFINEs allowed by Pathway for all server classes is 8191.
PAGE 82
ZCURnnn Fields Fields prefaced with ZCUR are information-only fields. The PATHMON process returns the values currently defined for each of these fields in response to the INFO command (these fields are not used for the START command).
PAGE 83
02 02 02 02 02 02 ZMAXLINKS ZMAXSERVERS ZNUMSTATIC ZOUT ZPRIORITY ZPROGRAM token-type token-type token-type token-type token-type token-type ZPWY-DDL-0-4095. ZPWY-DDL-0-4095. ZPWY-DDL-0-4095. ZSPI-DDL-FNAME32. ZPWY-DDL-1-199. ZSPI-DDL-FNAME32 !r 02 ZSENDTIMEOUT 02 ZTMF 02 ZDEFAULTVOLUME token-type ZPWY-DDL-TIME-TYPE. token-type ZPWY-DDL-ON-OFF. token-type ZSPI-DDL-SUBVOL. !r 02 ZOWNER.
PAGE 84
list of single CPUs; the two types cannot be mixed. ZCPUPAIR can occur from 1 to 16 times, depending on the value you specify for ZCPUPAIRCOUNT. ZPRIMARY when specifying CPU-pairs, this field indicates a primary processor in a CPU-pair. When specifying a list of single CPUs, this field is a single processor. Valid values range from 0 to 15. ZBACKUP when specifying primary and backup processor pairs, this field is the backup processor. Valid values are in the range from 0 to 15.
PAGE 85
to expire. While waiting for ZCREATEDELAY to expire, if an established or newly created link becomes available, the link manager immediately uses that link. If you are using the Pathway/iTS product, then note that when the TCP calculates that insufficient server resources are available, the TCP delays all future link requests from the PATHMON process by the value of CREATEDELAY or by 60 seconds, whichever is greater.
PAGE 86
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. After starting a server, the operating system modifies the server object file to point to the user library object file. You can set the server user library file using the TACL RUN command or by using the Binder program development tool. For more information, see the Binder Manual.
PAGE 87
is the maximum number of concurrent links permitted between all link managers (such as ACS subsystem processes and Pathway/iTS TCPs) and a server in a server class. This value must be from 0 to 4095. This attribute sets the maximum number of concurrent send operations to a single server process. The link manager does not check how many links a server has with other link managers. For more information on configuring this field, see the TS/MP 2.5 System Management Manual.
PAGE 88
to a server class counts as a static link in the server statistics. For more information on configuring this field, see the TS/MP 2.5 System Management Manual. The value of ZNUMSTATIC cannot exceed the value of ZMAXSERVERS. ZOUT is the name of the OUT file in the startup message that receives output from the server class; this is 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.
PAGE 89
SEND operation that times out has a server I/O error 12 reported in the SCREEN COBOL TERMINATION-STATUS special register. The ZSENDTIMEOUT attribute is not active until the first OPEN procedure is complete. The initial open of a server process by an ACS subsystem processes has an automatic 5-minute timeout period; the initial open of a server process by a TCP has an automatic 10-minute timeout period.
PAGE 90
If you do not assign a value to this parameter, the default is ZPWY-VAL-N. ZHIGHPIN is the default PIN (process identification number) range for all processes in the server class. The valid values are: ZPWY-VAL-ON The server processes in this class run at a high PIN, if other requirements are met. ZPWY-VAL-OFF The server processes in this class run at a low PIN. If you omit this field, the default is ZPWY-VAL-OFF.
PAGE 91
Octal Number Maximum Allowed Permissions Description 6 --x Execute 7 --- No permissions granted For example, if you specify a user mask of 027: • The OWNER has all permissions requested by the program creating the file (0). • The GROUP has READ permissions, but WRITE and EXECUTE permissions are not allowed (2). • The OTHERS do not have any permissions (7). NOTE: ZUMASK is supported by TS/MP 2.5 and is available only on systems running J06.11 or later J-series RVUs and H06.
PAGE 92
assigns a file code to the logical file name indicated in ZPWY-MAP-SEL-SCASSIGN. Valid values are integers ranging from 0 to 65535. If you do not assign a value to ZFILECODE, no value is passed. ZEXCLUSION is the exclusion mode for the logical file name indicated in ZPWY-MAP-SEL-SCASSIGN. The exclusion mode determines how other processes can access the file. The value of ZEXCLUSION can be ZPWY-VAL-SHARED, ZPWY-VAL-EXCLUSIVE, or ZPWY-VAL-PROTECTED.
PAGE 93
messages can be added to any one server class. In practice, the actual number can be less because all individual PARAMs for a server are collected into a single PARAM message, which is limited to 1028 bytes in length. For more information about PARAM messages, see the Guardian Programmer’s Guide. ZPWY-MAP-DEF-SCPROCESS This token defines attributes for a server process within a server class. nl def ZPWY-DDL-DEF-SCPROCESS. 02 ZASSOCIATIVE 02 ZCPUPAIR.
PAGE 94
Entering values for ZPRIMARY and ZBACKUP is optional in multiprocessor environments; the system assigns CPUs if you do not designate any. ZDEBUG determines whether the server enters debug mode on startup. The valid values are: ZPWY-VAL-OFF Directs the server process not to enter debug mode. ZPWY-VAL-ON Directs the server process to enter debug mode.
PAGE 95
ZAREA is the startup string value. ZPWY-MAP-PAR-CONTROL-PM This token defines PATHMON process attributes that can be changed by using the CONTROL PM command. def ZPWY-DDL-PAR-CONTROL-PM. 02 ZBACKUPCPU 02 ZDUMPINFO. 03 ZDUMP token-type ZPWY-DDL-CPU. token-type ZPWY-DDL-ON-OFF. token-type ZSPI-DDL-FNAME32. 03 ZDUMPFILE 02 ZLOG1INFO. 03 ZSTATE token-type ZPWY-DDL-FILESTATE-VALUE. 03 ZSTATUS token-type ZPWY-DDL-ON-OFF. 03 ZEVENTFORMAT token-type ZPWY-DDL-ON-OFF. 03 ZFILE token-type ZSPI-DDL-FNAME32.
PAGE 96
ZPWY-VAL-CLOSED Specifies not to open the log file; if the log file is already open, specifies to close it. ZPWY-VAL-OPEN Specifies to open the log file. If you do not assign a value to this field and no value was previously assigned, then the default is ZPWY-VAL-OPEN. Any value previously assigned continues in effect if you do not assign a new value. CAUTION: are lost.
PAGE 97
The command accepts processor number as a parameter. The server processes which used to run on the mentioned processor before processor failure, will be shifted back to the original processor. To validate this command the number must be between 0 -15 and PATHMON must be configured to run in MANUAL mode (SPREBALANCEMODE).
PAGE 98
commands, those specified as node-independent, and those defaulted. For the ZDEFAULTVOLUME field of ZPWY-DDL-DEF- SC, the node name is returned in network name format; it is returned with the node number. If you do not assign a value to this field, then the default is ZPWY-VAL-NO. ZPWY-MAP-PAR-SHUTDOWN This token specifies how a Pathway subsystem is to shut down. nl nl def ZPWY-DDL-PAR-SHUTDOWN. token-type ZPWY-DDL-INT. 02 ZMODE nl nl nl token-type ZPWY-DDL-TIME-TYPE. !r nl 02 ZTIMEOUT !r end.
PAGE 99
specifies whether to disregard the PATHMON configuration file. The valid values are: ZPWY-VAL-NO for a cold start, specifies not to cold start the subsystem if a PATHMON configuration file can be used to cool start. For a cool start, specifies to return an error if an unexpected PATHMON process name is encountered in the PATHCTL file. ZPWY-VAL-YES for a cold start, specifies to start the subsystem regardless of whether a PATHMON configuration file is present.
PAGE 100
ZPWY-MAP-PAR-STATUS-SC This token specifies the state of the server class whose status you are requesting. nl def ZPWY-DDL-PAR-STATUS-SC. token-type ZPWY-DDL-FRZSTATESEL-VALUE. 02 ZFREEZESTATE 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.
PAGE 101
end. When returned in a response buffer, this token specifies the LINKMON process that was acted upon. ZPWY-MAP-SEL-PMREQUESTER This token specifies the name of a specific requester process. The token fields are described under “ZPWY-DDL-PMREQUESTERNAME” (page 56). def ZPWY-DDL-SEL-PMREQUESTER. 02 ZNAME. nl nl nl nl token-type ZSPI-DDL-CHAR-PAIR. 03 ZNUMBER !r end. When returned in a response buffer, this token specifies the requester process for which information is being provided.
PAGE 102
All the fields in ZPWY-MAP-DEF-SCASSIGN are optional. However, at least one field must be assigned a value when adding a server class. ZPWY-MAP-SEL-SCDEFINE This token specifies the associated server class and the name to which a DEFINE is assigned. The token fields are described under “ZPWY-DDL-SCDEFINENAME” (page 57). def ZPWY-DDL-SEL-SCDEFINE 02 ZNAME. 03 ZSERVERCLASS nl nl token-type ZPWY-DDL-OBJECT-NAME. nl token-type ZPWY-DDL-FILLER. token-type ZPWY-DDL-DEFINE-NAME.
PAGE 103
ZPWY-MAP-SEL-SCPROCESS This token specifies the associated server class and the process name. The token fields are described under “ZPWY-DDL-SCPROCESSNAME” (page 58). def ZPWY-DDL-SEL-SCPROCESS. 02 ZNAME. 03 ZSERVERCLASS nl nl token-type ZPWY-DDL-OBJECT-NAME. nl token-type ZPWY-DDL-FILLER. token-type ZPWY-DDL-OBJECT-CHAR6. !r nl 03 FILLER token-type ZPWY-DDL-SCPROCESS-VERSION. 03 ZPROCESS !r 03 ZVERSION !r end.
PAGE 104
is the name of a server process within the server class. The name consists of a dollar sign ($) followed by one to five alphanumeric characters. The first character must be a letter. ZVERSION is the internal format version; set this to the preset value ZPWY-VAL-SCPROCESS2. The PATHMON process uses this value to ensure that the response buffer contains data compatible with the requestor version. NOTE: This attribute is not currently used. It is reserved for the future use.
PAGE 105
reports the time at which statistics were collected. ZQUEUEINFO reports statistics about the server class wait queue. This queue usually holds send operations that the link manager (such as ACS subsystem processes, or Pathway/iTS TCP) cannot execute immediately because a link to the server class is not available. Server class requests wait in the link manager until an existing link becomes available or until the PATHMON process grants a new link.
PAGE 106
ZIOS is the number of I/O operations to the servers in this server class. For sends, this value is always the same as the ZREQCNT value. ZREPLY reports information about REPLY statements from the server class. ZREPLY contains: ZREQCNT is when statistics are not provided for REPLY statements because there are no explicit requests for REPLY.
PAGE 107
ZTOTALMEASCOUNT is the total number of measurements collected. ZAVGRESP is the average response time calculated from the collected measurements. ZMAXRESP is the maximum response time recorded during the given time interval (since statistics counters were turned on or reset). ZMINRESP is the minimum response time recorded during the given time interval (since statistics counters were turned on or reset). ZSUMOFSQUARES is a statistic that can be used to calculate standard deviation and variance.
PAGE 108
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 02 ZERRORINFO. nl nl token-type ZSPI-DDL-TIMESTAMP. token-type ZPWY-DDL-OBJSTATE-VALUE nl token-type ZSPI-DDL-INT. 03 ZERROR token-type ZSPI-DDL-INT. 03 ZINFO token-type ZSPI-DDL-CRTPID. 02 ZPROCESS end. ZSTATUSTIME gives the time when this status was collected, as a four-word GMT timestamp.
PAGE 109
03 ZFREEZEPENDING token-type ZSPI-DDL-INT. nl 02 ZSERVERPROCESSES. token-type ZSPI-DDL-INT. 03 ZRUNNING token-type ZSPI-DDL-INT. 03 ZSTOPPED token-type ZSPI-DDL-INT. nl 03 ZPENDING 02 ZSPI. 03 ZRUNNING 02 ZTCPS. 03 ZRUNNING 03 ZSTOPPED 03 ZPENDING token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZPWY-DDL-PMSTATE-VALUE. token-type ZSPI-DDL-TIMESTAMP. token-type ZSPI-DDL-TIMESTAMP. 02 ZTERMS.
PAGE 110
ZSERVERPROCESSES reports the number of server processes. It includes: ZRUNNING The number of server processes that are running ZSTOPPED The number of server processes that are stopped ZPENDING The number of server processes that have received a STOP command and are stopping ZSPI The number of SPI requesters. It includes: ZRUNNING reports the number of SPI requesters that have this PATHMON process open ZTCPS reports the number of Pathway/iTS TCPs.
PAGE 111
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. nl def ZPWY-DDL-STATUS-PM. token-type ZSPI-DDL-TIMESTAMP. 02 ZSTATUSTIME token-type ZPWY-DDL-PMSTATE-VALUE. 02 ZPATHMONSTATE nl token-type ZPWY-DDL-FILESTATE-VALUE. 02 ZPATHCTL. token-type ZSPI-DDL-DISCNAME. 03 ZSTATE token-type ZSPI-DDL-INT.
PAGE 112
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-VAL-OPEN The file is open. ZSTATUS indicates whether the log file is open for status logging. The valid values are: ZPWY-VAL-OFF The log is open for error logging only. ZPWY-VAL-ON The log is open for error and status logging. ZEVENTFORMAT indicates whether messages are formatted as text or as event messages.
PAGE 113
indicates that the PATHMON process is completing a request for a requester process that has aborted. ZREQTYPE specifies the type of requester. The valid values are: ZPWY-VAL-EXTTCP The requester is a Pathway/iTS TCP running in another Pathway subsystem. ZPWY-VAL-LINKMON The requester is a LINKMON process. ZPWY-VAL-LOG The requester is a task that writes log messages to the log file. ZPWY-VAL-PATHCOM The requester is a PATHCOM process.
PAGE 114
ZWAITOBJECT identifies a file associated with the wait cause. ZLOCKS gives the number of files the requester has locked. ZLOCKED names the files locked by this requester. ZLOCKED can occur from zero to five times, depending on the value in ZLOCKS. ZPWY-MAP-STATUS-SC This token reports status information on a server class. nl def ZPWY-DDL-STATUS-SC. 02 ZSTATUSTIME 02 ZFREEZESTATE 02 ZERRORINFO 03 ZERROR 03 ZINFO 02 ZRUNNING 02 ZERRORINFO2 03 ZERROR2 03 ZINFO2 token-type ZSPI-DDL-TIMESTAMP.
PAGE 115
ZPWY-MAP-STATUS-SCPROCESS This token reports status information on a server process. nl def ZPWY-DDL-STATUS-SCPROCESS. 02 ZSTATUSTIME 02 ZSTATE 02 ZPROCESS 02 ZERRORINFO. 03 ZERROR 03 ZINFO 02 ZLINKS 02 ZWEIGHT 02 ZERRORINFO2 03 ZERROR2 03 ZINFO2 token-type ZSPI-DDL-TIMESTAMP. token-type ZPWY-DDL-OBJSTATE-VALUE. token-type ZSPI-DDL-CRTPID. nl token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. token-type ZPWY-DDL-ERRINFO2. token-type ZSPI-DDL-INT.
PAGE 116
For each link to a server class, a weight is incremented by 3 for the first link from a given link manager, by 2 for the second link from that link manager, and by 1 for all subsequent links from that link manager. Note that, whenever possible, a link manager uses older links before newer ones. ZERRORINFO2 contains additional error information. The field is described under “ZPWY-DDL-ERRINFO2” (page 63).
PAGE 117
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 nl ZPWY-OBJ-PATHCTL ZPWY-OBJ-PATHWAY ZPWY-CMD-INFO nl 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 nl nl nl ZPWY-OBJ-PATHWAY ZP
PAGE 118
Log File Error Recovery While your Pathway subsystem is running, the PATHMON process and the Pathway/iTS TCPs report errors and status information to a log file. Using the fields associated with ZLOG1INFO and ZLOG2INFO, you can direct the PATHMON process to report errors only, or errors and changes in object status as well. You can direct the PATHMON process to log information to only one file or to copy the information to two files.
PAGE 119
• 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 further attempts to create a backup process. The delay is 1 minute if stopped 11 times, 2 minutes if stopped 12 times, and so forth.
PAGE 120
Tokens in Command Buffer nl ZSPI-TKN-SERVER-BANNER token-type ZSPI-TYP-CHAR50. GETVERSION PM Use the GETVERSION PM command to obtain the release level of the PATHMON process returned in the header token ZSPI-TKN-SERVER-VERSION. 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” (page 49).
PAGE 121
Considerations • Use INFO PATHCTL to determine whether the Pathway subsystem was shut down (with the STOP PATHWAY command) or whether it is still in a RUNNING state. • Use INFO PATHCTL to determine whether the current PATHMON process name matches the PATHMON process name in the PATHCTL file. INFO PATHWAY Use the INFO PATHWAY command to return the attribute values currently in effect for the Pathway subsystem.
PAGE 122
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-SHUTDOWN2 Object Type nl ZPWY-OBJ-PATHWAY Tokens in Command Buffer nl ZPWY-MAP-PAR-SHUTDOWN Tokens in Response Buffer token-type ZPWY-DDL-PARSHUTDOWN. ZSPI-TKN-RETCODE token type ZSPI-TYP-INT.
PAGE 123
• When ZMODE is set to ORDERLY or ABORT mode, the PATHMON process sends a single shutdown request to each locally controlled Pathway/iTS TCP. The TCP acknowledges the request and begins the shutdown phase, denying all requests to start new work. This mode of operation allows all locally controlled TCPs to shut down in parallel, reducing the time required to shut down the Pathway subsystem.
PAGE 124
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. For descriptions of all error-token values and their associated error lists, see “Event Management” (page 163).
PAGE 125
Object Type nl ZPWY-OBJ-LM Tokens in Command Buffer nl ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-LM !r Tokens in Response Buffer token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-LM. ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-LM token-type ZPWY-DDL-SEL-LM. ZPWY-MAP-STATUS-LM token-type ZPWY-DDL-STATUS-LM. STATUS PATHWAY Use the STATUS PATHWAY command to display the number of PATHMON-environment objects that are in each possible state.
PAGE 126
Considerations • To implement the equivalent of the PATHCOM STATUS PATHMON command, issue the STATUS PM command and then issue the STATUS PMREQUESTER command with continuation. • During shutdown, the PATHMON process automatically stops logging status messages. • Unlike the file names that appear in the PATHCOM STATUS PATHMON display, the file names returned by the STATUS PM command do not include node names.
PAGE 127
STOP PATHWAY causes the PATHMON process to delete all servers that are not linked to a link manager. ACS subsystem processes are notified of the STOP PATHWAY command and prohibited from sending requests to Pathway subsystem server classes. If you are using Pathway/iTS, then note that this command is the same as the PATHCOM SHUTDOWN command, except that the TERM objects and TCP objects are not automatically stopped; you must stop all the TERM objects and TCP objects before issuing this command.
PAGE 128
STOP PM Use the STOP PM command to stop the PATHMON process pair; the Pathway subsystem must be currently in the process of shutting down (ZPATHWAYSTATE is set to ZPWY-VAL-SHUTDOWN). 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” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75).
PAGE 129
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75).
PAGE 130
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.
PAGE 131
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-ADD Object Type nl ZPWY-OBJ-SC Tokens in Command Buffer nl ZPWY-MAP-SEL-SC token-type ZPWY-DDL-SEL-SC. !r ZPWY-MAP-DEF-SC token-type ZPWY-DDL-DEF-SC. !r ZPWY-TKN-DEF-SCPROGRAMOSS token-type ZSPI-TYP-BYTESTRING.
PAGE 132
Error Number Error Token Description 4025 ZPWY-ERR-SPI-OSSATTRUSED An attribute valid only for OSS server processes was specified for a Guardian server process. 4026 ZPWY-ERR-SPI-OSSATTRTOOBIG The value specified for an OSS attribute exceeds the maximum length. 4027 ZPWY-ERR-SPI-INVALIDPATHNAME An OSS pathname in the command is invalid.
PAGE 133
• 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.
PAGE 134
ZPWY-MAP-DEF-SCASSIGN !r Tokens in Response Buffer token-type ZPWY-DDL-DEF-SCASSIGN. ZPWY-MAP-SEL-SCASSIGN ZSPI-TKN-RETCODE token-type ZPWY-DDL-SEL-SCASSIGN. token-type ZSPI-TYP-INT. Tokens in Response Buffer For ADD SCASSIGN, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1012 ZPWY-ERR-PM-DUPNAME An ASSIGN message that has the same name as the name assigned to ZLOGICALUNIT already exists.
PAGE 135
ZPWY-MAP-SEL-SCDEFINE !r ZPWY-TKN-DEF-SCDEFINE Tokens in Response Buffer token-type ZPWY-DDL-SEL-SCDEFINE. ZPWY-MAP-SEL-SCDEFINE ZSPI-TKN-RETCODE token-type ZPWY-DDL-SEL-SCDEFINE. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-BYTESTRING. 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.
PAGE 136
ZPWY-OBJ-SCPARAM Tokens in Command Buffer nl ZPWY-MAP-SEL-SCPARAM !r ZPWY-MAP-DEF-SCPARAM !r Tokens in Response Buffer token-type ZPWY-DDL-SEL-SCPARAM. ZPWY-MAP-SEL-SCPARAM ZSPI-TKN-RETCODE token-type ZPWY-DDL-SEL-SCPARAM. token-type ZSPI-TYP-INT. token-type ZPWY-DDL-DEF-SCPARAM. Tokens in Response Buffer For ADD SCPARAM, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1012 ZPWY-ERR-PM-DUPNAME A PARAM message by this name already exists for this server class.
PAGE 137
!r ZPWY-MAP-DEF-SCPROCESS !r Tokens in Response Buffer ZPWY-MAP-SEL-SCPROCESS ZSPI-TKN-RETCODE token-type ZPWY-DDL-DEF-SCPROCESS. token-type ZPWY-DDL-SEL-SCPROCESS. token-type ZSPI-TYP-INT. Tokens in Response Buffer For ADD SCPROCESS, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1012 ZPWY-ERR-PM-DUPNAME A server process by this name already exists for this server class. 1103 ZPWY-ERR-PM-TOOMANYSCPROCESS The value specified for ZMAXSERVERPROCESSES was reached.
PAGE 138
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-ADD Object Type nl ZPWY-OBJ-SCSTARTUP Tokens in Command Buffer nl ZPWY-MAP-SEL-SCSTARTUP !r ZPWY-MAP-DEF-SCSTARTUP !r Tokens in Response Buffer token-type ZPWY-DDL-SEL-SCSTARTUP.
PAGE 139
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.
PAGE 140
Tokens in Response Buffer For ALTER SC, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1103 ZPWY-ERR-PM-TOOMANYSCPROCESS The value specified in ZPWY-DDL-DEF-PATHWAY for ZMAXSERVERPROCESSES was reached. 4023 ZPWY-ERR-SPI-CWDCANTBERESETNOW The current working directory cannot be changed because other OSS pathnames were defined as relative pathnames.
PAGE 141
• 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 is implemented or permanent.
PAGE 142
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. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49).
PAGE 143
ZPWY-MAP-DEF-SCPARAM !r Tokens in Response Buffer token-type ZPWY-DDL-DEF-SCPARAM. ZPWY-MAP-SEL-SCPARAM token-type ZPWY-DDL-SEL-SCPARAM. 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 “SPI Programming Considerations” (page 29). • To perform the equivalent of the PATHCOM ALTER SERVER, RESET PARAM command, use the DELETE SCPARAM command.
PAGE 144
program, you must use the #SETBYTES built-in function. For more information, see the SPI Programming Manual. • An associative server is configured with the ZASSOCIATIVE field in ZPWY-DDL-DEF-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 sure that the new definition is implemented or permanent.
PAGE 145
DEFINEs, PARAM parameters, and STARTUP string (if any). All servers in the server class must be frozen and then stopped to use this command. Continuation To delete 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 and then stopped.
PAGE 146
ZPWY-CMD-DELETE Object Type nl ZPWY-OBJ-SCASSIGN Tokens in Command Buffer nl ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SCASSIGN !r Tokens in Response Buffer token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SCASSIGN. ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SCASSIGN token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SCASSIGN. Considerations • Deleting an SC object causes all associated SCASSIGN objects to be deleted— you need not issue the DELETE SCASSIGN command.
PAGE 147
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. (Continuation is not available using the ZSERVERCLASS field.
PAGE 148
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-DELETE Object Type nl ZPWY-OBJ-SCPROCESS Tokens in Command Buffer nl ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SCPROCESS !r Tokens in Response Buffer token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SCPROCESS.
PAGE 149
Considerations • Deleting an SC object deletes the associated SCSTARTUP objects—you need not issue the DELETE SCSTARTUP command. • This command is equivalent to the PATHCOM ALTER SERVER, RESET STARTUP command. FREEZE SC Use the FREEZE SC command to prohibit all link managers, such as ACS subsystem processes and Pathway/iTS TCPs, from sending requests to a server class.
PAGE 150
Considerations If you are using Pathway/iTS, consider: • If ZIGNORESTOPMODE is set to ZPWY-VAL-NO, the freeze does not take effect until all SCREEN COBOL STOP-MODE special registers have a value of zero and no server in the server class has incomplete or outstanding requests. In the interim, the server class is put into the FREE-PENDING state.
PAGE 151
ZPWY-MAP-DEF-SC token-type ZPWY-DDL-DEF-SC. ZPWY-TKN-DEF-SCPROGRAMOSS token-type ZSPI-TYP-BYTESTRING. ZPWY-TKN-DEF-SCCWD token-type ZSPI-TYP-BYTESTRING. ZPWY-TKN-DEF-SCSTDERR token-type ZSPI-TYP-BYTESTRING. ZPWY-TKN-DEF-SCSTDIN token-type ZSPI-TYP-BYTESTRING. ZPWY-TKN-DEF-SCSTDOUT token-type ZSPI-TYP-BYTESTRING. ZPWY-TKN-DEF-SCENV token-type ZSPI-TYP-BYTESTRING. ZPWY-TKN-DEF-SCARGLIST token-type ZSPI-TYP-BYTESTRING.
PAGE 152
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-INFO Object Type nl ZPWY-OBJ-SCASSIGN Tokens in Command Buffer nl ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SCASSIGN !r ZPWY-MAP-PAR-INFO Tokens in Response Buffer token-type ZSPI-TYP-BYTESTRING. token-type ZPWY-DDL-SEL-SCASSIGN.
PAGE 153
Considerations There is no default value for a server DEFINE. Consequently, if you issue the INFO SCDEFINE command and include ZPWY-MAP-SEL-SCDEFINE in the command buffer with null values, the PATHMON process returns ZPWY-MAP-DEF-SCDEFINE with a null string (that is, the length field is zero). INFO SCPARAM Use the INFO SCPARAM command to obtain the attribute value for a server PARAM parameter defined in the PATHMON configuration file.
PAGE 154
by the PATHMON process until no data is returned in the reply buffer. For more information, see “Specifying Continuation” (page 40). Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75).
PAGE 155
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-INFO Object Type nl ZPWY-OBJ-SCSTARTUP Tokens in Command Buffer nl ZPWY-MAP-SEL-SCSTARTUP !r Tokens in Response Buffer ZPWY-MAP-SEL-SCSTARTUP ZPWY-MAP-DEF-SCSTARTUP token-type ZPWY-DDL-SEL-SCSTARTUP.
PAGE 156
• For associative server processes, the command sets the associative flag ON in the reply buffer. If the associative process is linked to the multiple server classes, the command returns any one of the server classes. • For information about map definitions, see “ZPWY-MAP-SRVFORSP ” (page 103). START SC Use the START SC command to initiate operation of the static servers in the server class. This command does not affect server classes in the FROZEN state.
PAGE 157
Considerations • This command starts the number of server processes defined by the ZNUMSTATIC field in ZPWY-DDL-DEF-SC. • The ASSIGN messages are built directly from the information you provide in the ADD SCASSIGN command. The PARAM message contains one item for each parameter value you specify for the ZAREA field in ZPWY-DDL-DEF-SCPARAM (with the ADD SCPARAM command).
PAGE 158
Error Number Error Token Description 1091 ZPWY-ERR-PM-INVALIDHOMETERM An error occurred while the PATHMON process was attempting to create a new process for the server class. 1159 ZPWY-EVT-PM-OSSPROCESSFAILURE An error occurred while the PATHMON process was trying to create the specified OSS server process. For descriptions of all error-token values and their associated error lists, see “Event Management” (page 163).
PAGE 159
Considerations • Statistics for server classes are stored by the link managers. If the server class stops for any reason, its statistics are lost . As a result, when a server in that class is restarted, the link manager has no statistics for the server class. • Use this command in combination with the Pathway/iTS STATS SCTCP command to perform the equivalent of the PATHCOM STATS SERVER command. STATUS SC Use the STATUS SC command to obtain the current status of a server class.
PAGE 160
STATUS SCPROCESS Use the STATUS SCPROCESS command to obtain the current status of a server process. Status information on the server class can be obtained with the STATUS SC command (the equivalent of the PATHCOM STATUS SERVER command without the DETAIL option). Continuation To obtain status information for all server processes in a server class, initialize the ZPROCESS field in ZPWY-DDL-SEL-SCPROCESS to ZPWY-VAL-ALLSCPROCESS.
PAGE 161
Command Syntax For tokens that may be present in the command and response buffers but are not listed, see “Unlisted Tokens” (page 49). For descriptions of tokens and fields, see “SPI and EMS Standard Definitions” (page 50) through “ZPWY-MAP- Definitions” (page 75). Command nl ZPWY-CMD-STOP Object Type nl ZPWY-OBJ-SC Tokens in Command Buffer nl ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SC !r Tokens in Response Buffer ZSPI-TKN-CONTEXT ZPWY-MAP-SEL-SC ZSPI-TKN-RETCODE token-type ZSPI-TYP-BYTESTRING.
PAGE 162
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” (page 40).
PAGE 163
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 message numbers range represent events and errors reported to the PATHMON process by other processes.
PAGE 164
Event Management Programming for Pathway Subsystems To process an event message, a management application must: 1. Start a copy of the EMS event distributor (EMSDIST). 2. Issue appropriate distributor programmatic commands, selecting the collector or log file from which the events must be retrieved and specifying the filter to be used in selecting the events. 3. Issue a GETEVENT command to the EMS event distributor. 4.
PAGE 165
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.
PAGE 166
LOG1 $0, EVENTFORMAT LOG2 $DATA.PM.LOGFILE, STATUS If an error occurs on LOG1, the PATHMON process closes the log because the error occurred on $0; PATHMON process does not reopen LOG1. If an error occurs on LOG2, the PATHMON process reopens $DATA.PM.LOGFILE as LOG2 $0, STATUS. The PATHMON process then sends both error information and status information to $0 because LOG1 used the default value (ZPWY-VAL-OFF) for ZSTATUS and LOG2 specified ZPWY-VAL-ON for ZSTATUS.
PAGE 167
Event Messages Each Pathway subsystem event message is contained within an event-message buffer consisting of: • Message header token—contains the value ZSPI-VAL-EVTHDR, which identifies a message as an event message. The event-message header is built by the EMSINIT procedure. The header differs from the standard command header by omitting some command and response tokens and including some standard EMS tokens.
PAGE 168
Table 26 Standard EMS Header Tokens (continued) Token and Token Type Data Type Description ZEMS-TKN-LOGTIME ZSPI-TYP-TIMESTAMP 64-bit integer Contains the time the collector added the event message to the event log. ZEMS-TKN-PIN ZSPI-TYP-INT 16-bit integer Identifies the primary process ID of the PATHMON process. ZEMS-TKN-SYSTEM ZSPI-TYP-UINT 16-bit unsigned integer Identifies the system where the PATHMON process was running.
PAGE 169
Table 30 Subsystem-specific EMS Tokens Token and Token Type Description ZPWY-TKN-EVENTCLASS Indicates the type of event information. The valid values are: ZPWY-VAL-ERROREVENT The event describes error information. ZPWY-VAL-STATUSEVENT The event describes status information. ZPWY-VAL-WARNEVENT The event describes warning information.
PAGE 170
In the individual event descriptions in this manual, nested messages are identified as “Tokens for Nested Message.” The nested message tokens, which are fully described in the EMS Manual, are: • ZSPI-TKN-ERRLIST Marks the beginning of the nested error list • ZSPI-TKN-ENDLIST Terminates the nested error list • ZPWY-TKN-NESTEDMSGNUMBER The event number of the nested message One or more of the conditional tokens listed in Table 31 (page 170), which describe the nested message.
PAGE 171
Example 2 Example Event Message EMSTEXT format of this event message: \SYS.$PM1: ERROR - *1007* LINKMON L\SYS.
PAGE 172
Table 32 Error List Tokens Token Description Tokens Always Present ZSPI-TKN-ERRLIST This token marks the beginning of an error list. It identifies an error list containing additional information about an error reported in ZSPI-TKN-RETCODE. ZSPI-TKN-ENDLIST This token marks the end of an error list. ZSPI-TKN-ERROR This token contains the Pathway subsystem ID and an error number.
PAGE 173
• 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 "CLASS-A" • ZPWY-TKN-ERRCOMMAND, containing ZPWY-CMD-START • ZPWY-TKN-ERROBJECTTYPE, containing ZPWY-OBJ-SC • ZPWY-TKN-ERRSCNAME, containing "CLASS-A" • ZSPI-TKN-ENDLIST Scenario 2 Your management application issues the START SC command for CLASS-A, but the buffer is co
PAGE 174
c. d. e. f. g. h. i. Call SSMOVE or SSMOVETKN to move the context token from the response buffer into the GETEVENT command buffer. The context token is needed when your application resends the command to get the next event. Call SSGET or SSGETTKN to retrieve the token containing the event message (ZEMS-TKN-EVENT) from the response buffer. Call EMSGET or EMSGETTKN to retrieve the subsystem ID (ZSPI-TKN-SSID) and the event number (ZEMS-TKN-EVENTNUMBER) from the event message.
PAGE 175
Both source and compiled templates are provided. You can modify the source templates and compile them again if you wish to customize your messages. The name of the Pathway template object file is ZPWYTMPL; the source file is SPWYTMPL. For general information about DSM templates and instructions on how to use and modify them, see the DSM Template Services Manual.
PAGE 176
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. However, some message numbers range represent events and errors reported to the PATHMON process by other processes.
PAGE 177
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 Table 26 (page 167) in “Event Management” (page 163).
PAGE 178
Event-Message Range 1000 Through 1999 Event messages numbered from 1000 to 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. 1002: ZPWY-EVT-PM-ABORTEDSTATUS A specific Pathway/iTS TERM object is aborted.
PAGE 179
Recovery. Informational message only; no corrective action is needed. 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 “Event Management” (page 163). 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.
PAGE 180
ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. TOKENS FOR NESTED MESSAGE are described in “Nested Messages” (page 169). Effect. The Pathsend statement or SEND operation fails. Recovery. For additional information, see the description associated with the nested message. 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.
PAGE 181
Event-Message Text *1012* object-name, ENTRY ALREADY EXISTS Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-DUPNAME (1012). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-nnnNAME, which identifies the Pathway object name that is the subject of this event message. For possible object types, see “Subject Tokens” (page 177). ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. Effect.
PAGE 182
ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type ZPWY-TYP-nnnNAME. token-type ZSPI-TYP-ENUM. Event-Message Text *1015* object-name, ENTRY NOT DESIGNATED TYPE Token Descriptions ZEMS-TKN-EMPHASIS contains ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-ENTRYTYPEMISMATCH (1015). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-nnnNAME, which identifies the Pathway object name that is the subject of this event message. For possible object types, see “Subject Tokens” (page 177).
PAGE 183
ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type ZPWY-TYP-PMNAME. token-type ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-ERROR token-type ZSPI-TYP-INT. Event-Message Text *1017* PATHMON, PATHCTL FILE ERROR (errnum) Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-PATCHCTLIO (1017). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message.
PAGE 184
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 “Event Management” (page 163). Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYP-nnnNAME.
PAGE 185
ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-ERROR contains the number of the file system error that occurred. N indicates that this token can occur in a nested error message. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
PAGE 186
Event-Message Text *1022* PATHMON, RECEIVE FILE ERROR (errnum) Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-RECEIVEIO (1022). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-ERROR contains the number of the file-system error that occurred.
PAGE 187
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYP-nnnNAME. token-type ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-ERROR token-type ZSPI-TYP-INT.
PAGE 188
contains a P-register value. N indicates that this token can occur in a nested error message. ZPWY-TKN-PADDR Effect. The PATHMON process creates a memory dump if dumping is enabled. Recovery. Contact your HP support representative. 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.
PAGE 189
ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-LOG1OFF (1027). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-STATUSEVENT. Effect. None. Recovery. Informational message only; no corrective action is needed. 1028: ZPWY-EVT-PM-LOG1ON The LOG1 file is open.
PAGE 190
has a value of ZPWY-VAL-STATUSEVENT. ZPWY-TKN-EVENTCLASS Effect. None. Recovery. Informational message only; no corrective action is needed. 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 “Event Management” (page 163).
PAGE 191
Recovery. Contact your HP support representative. 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 “Event Management” (page 163). 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.
PAGE 192
Effect. The requesting link manager is not linked to the server class. Recovery. Increase the value for the ZMAXSERVERS, ZMAXLINKS, or ZLINKDEPTH field in ZPWY-DDL-DEF-SC. (HP recommends that you not set ZLINKDEPTH higher than 1 for servers other than communications-based servers, such as HLS servers.) 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.
PAGE 193
has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-EVENTCLASS Effect. The operation fails. Recovery. Use an ALTER command to correct the system name in the object definition. 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.
PAGE 194
ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYP-nnnNAME. token-type ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-ERROR N ZPWY-TKN-NEWPROCERROR token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT. HP Internal Tokens N N N N ZPWY-TKN-NEWPROCRESULT ZPWY-TKN-NEWPROCFORMATFILETYPE ZPWY-TKN-NEWPROCFORMATERROR ZPWY-TKN-PROCCREATRESULT token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM.
PAGE 195
ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-NEWPROCESS (1038). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-SCNAME or ZPWY-TKN-TCPNAME, which contains the name of the server class or the Pathway/iTS TCP that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-ERROR contains a file-system error number. N indicates that this token can occur in a nested error message. ZPWY-TKN-NEWPROCERROR contains the number of the process creation error.
PAGE 196
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). 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. ZPWY-TYP-TERMNAME. ZSPI-TYP-ENUM.
PAGE 197
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). Unconditional Tokens ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN. ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT. ZEMS-TKN-SUBJECT-MARK token-type ZSPI-TYP-SSCTL. ZPWY-TKN-nnnNAME token-type ZPWY-TYP-nnnNAME. ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-ERROR token-type ZSPI-TYP-INT.
PAGE 198
has a value of ZPWY-VAL-STATUSEVENT. ZPWY-TKN-EVENTCLASS TOKENS FOR A NESTED MESSAGE are described under “Nested Messages” (page 169). Effect. The effect depends on the application and what type of object stopped. Recovery. For additional information, see the description associated with the nested message. 1048: 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.
PAGE 199
ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-SUSPENDEDSTATUS (1049). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-TERMNAME, which contains the name of the TERM object that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-STATUSEVENT. Effect. The terminal remains suspended until you issue the Pathway/iTS RESUME TERM command. Recovery. For additional information, see the description associated with the nested message.
PAGE 200
Event-Message Text *1051* TCP tcp-name, REQUESTER TABLE OVERFLOW Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-TRUE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-REQUESTTABLEFULL (1051). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-TCPNAME, which contains the name of the TCP that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. Effect. The PATHMON process cannot communicate with the ACS subsystem processes, or the Pathway/iTS TCP.
PAGE 201
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). 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. ZSPI-TYP-ENUM.
PAGE 202
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). 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. ZSPI-TYP-ENUM.
PAGE 203
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 “Event Management” (page 163). 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.
PAGE 204
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 “Event Management” (page 163). 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.
PAGE 205
ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. TOKENS FOR A NESTED MESSAGE are described under “Nested Messages” (page 169). Effect. The PATHMON process runs without a backup. Recovery. For additional information, see the description associated with the nested message.
PAGE 206
N ZPWY-TKN-ERROR token-type ZSPI-TYP-INT. Event-Message Text *1074* PATHMON, CHECKCLOSE FAILURE (%errnum) Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-CHECKCLOSE (1074). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT.
PAGE 207
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. Conditional Tokens N ZPWY-TKN-PADDR token-type ZSPI-TYP-UINT. Event-Message Text *1078* PATHMON, FATAL ERROR (%p-register) Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-TRUE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-INTERNALFATAL (1078).
PAGE 208
Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-TRUE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-TRAPPED (1080). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. 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.
PAGE 209
ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN. ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT. ZEMS-TKN-SUBJECT-MARK token-type ZSPI-TYP-SSCTL. ZPWY-TKN-nnnNAME token-type ZPWY-TYP-nnnNAME. ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-ENUM. Event-Message Text *1083* link manager-name, LINE TO TCP IS DOWN Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-LINEDOWN (1083).
PAGE 210
ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYP-PMNAME. token-type ZSPI-TYP-ENUM. Event-Message Text *1094* PATHMON, BACKUP PROCESS FAILED Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-TRUE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-BUFAIL (1094). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message.
PAGE 211
ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type ZPWY-TYP-TCPNAME. token-type ZSPI-TYP-ENUM. Event-Message Text *1115* TCP tcp-name, TCP REFRESHED Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-REFRESHEDSTATUS (1115). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-TCPNAME, which contains the name of the TCP that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-STATUSEVENT. Effect.
PAGE 212
*1120* object-name, AUTORESTARTED Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-AUTOSTARTEDSTATUS (1120). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-nnnNAME, which contains the name of the object that is the subject of this event message. For possible object types, see “Subject Tokens” (page 177). ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-STATUSEVENT. Effect. None. Recovery. Informational message only; no corrective action is needed.
PAGE 213
ZPWY-TKN-PMNAME ZPWY-TKN-EVENTCLASS token-type ZPWY-TYP-PMNAME. token-type ZSPI-TYP-ENUM. Event-Message Text *1122* PATHMON, BACKUP PROCESS STOPPED Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-BUSTOPPED (1122). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-STATUSEVENT. Effect.
PAGE 214
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). Unconditional Tokens ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN. ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT. ZEMS-TKN-SUBJECT-MARK token-type ZSPI-TYP-SSCTL. ZPWY-TKN-PMNAME token-type ZPWY-TYP-PMNAME. ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-ERROR token-type ZSPI-TYP-INT.
PAGE 215
contains the number of the USESEGMENT error that occurred. N indicates that this token can occur in a nested error message. ZPWY-TKN-ERROR Effect. The PATHMON process is unable to select a particular extended data segment. The PATHMON process terminates. Recovery. For information about the specified USESEGMENT error, see the Guardian Procedure Errors and Messages Manual.
PAGE 216
Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-DEFINEDISABLED (1144). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-STATUSEVENT. Effect. The processing of DEFINE statements is disabled, making it impossible to add a DEFINE definition to a server class. Recovery.
PAGE 217
Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-INTERNALTABLE (1149). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. Effect. The SCASSIGN, SCDEFINE, SCPARAM, SCPROCESS, and SCSTARTUP objects cannot be configured for a server class.
PAGE 218
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). 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 Text *1151* PATHMON STOPPED Token Descriptions ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-FALSE.
PAGE 219
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-INT. token-type ZSPI-TYP-SSCTL. token-type ZPWY-TYP-nnnNAME. token-type ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-OSSERRNO N ZPWY-TKN-TPCERROR N ZPWY-TKN-TPCDETAIL token-type ZSPI-TYP-INT2.
PAGE 220
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.
PAGE 221
PROCESS_CREATE_ procedure. N indicates that this token can occur in a nested error message. ZPWY-TKN-ERROR,ZPWY-TKN-NEWPROCFORMATERROR, are reserved for HP internal use only. N indicates that these and tokens can occur in a nested error message. ZPWY-TKN-PROCCREATRESULT Effect. The server process is not created. Recovery. OSS server processes are created by calls to the Guardian PROCESS_SPAWN_ procedure. For additional information, see the detailed description in this message.
PAGE 222
Event-Message Text *1162* PATHMON, RESIZESEGMENT ERROR (errnum) Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-PM-RESIZESEGMENT (1162). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-PMNAME, which contains the name of the PATHMON process that is the subject of this event message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-ERROR contains the number of the RESIZESEGMENT error that occurred.
PAGE 223
Recovery. Informational message only; no corrective action is needed.
PAGE 224
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. However, some message numbers range represent events and errors reported to the PATHMON process by other processes.
PAGE 225
Object Types in Error Lists Within the syntax boxes in this section, nnn represents one of these TS/MP object types: LM SCASSIGN SCPARAM PMREQUESTER SCDEFINE SCPROCESS SC SCLM SCSTARTUP For descriptions of these object types, see “Object Types” (page 32). Object types not listed above are Pathway/iTS objects, described in the Pathway/iTS Management Programming Manual. Error-Message Range 1000 Through 1999 Error messages numbered from 1000 to 1999 describe errors reported by the PATHMON process.
PAGE 226
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT.
PAGE 227
ZSPI-TKN-ERROR contains ZPWY-ERR-PM-CONFIGDONE. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-START. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-PATHWAY. ZPWY-TKN-ERRCOMMAND contains ZPWY-CMD-START, which was executing when the error occurred. Effect. The command fails. Recovery. Stop the Pathway subsystem before changing the configuration. 1010: ZPWY-ERR-PM-CONFIGNOTDONE An attempt was made to execute a command while the PATHMON process was not in the RUNNING state.
PAGE 228
1013: ZPWY-ERR-PM-EMPTYENTRY An entry that 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 “Event Management” (page 163).
PAGE 229
Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-ENTRYTYPEMISMATCH. Effect. The request that specified the object fails. Recovery. Correct the object type specified or implied by the request and retry the request. 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 “Event Management” (page 163).
PAGE 230
ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQSCNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-SCNAME ZPWY-TKN-ERRINFO ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-SCNAME ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SCNAME. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-PMSCPROCESSIO. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-SC.
PAGE 231
Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-LOG1IO. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-CONTROL. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-PM. ZPWY-TKN-ERRCOMMAND contains ZPWY-CMD-CONTROL. ZPWY-TKN-ERROBJECTTYPE contains ZPWY-OBJ-PM. ZPWY-TKN-ERRINFO contains the file-system error that occurred on the LOG1 file. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
PAGE 232
ZPWY-TKN-ERRINFO contains the file-system error that occurred on the $RECEIVE file. Effect. The effect depends on the file-system error that occurred. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 1023: ZPWY-ERR-PM-TCPPMIO A file-system error occurred during an I/O operation to the specified link manager.
PAGE 233
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZPWY-TKN-ERRINFO ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
PAGE 234
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT.
PAGE 235
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
PAGE 236
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163).
PAGE 237
ZSPI-TKN-ERROR contains ZPWY-ERR-PM-REQUESTHANDLER. Effect. The request fails. Recovery. For additional information, see the description associated with the nested message. 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.
PAGE 238
Effect. The terminal remains suspended until it is aborted with the Pathway/iTS ABORT TERM command. Recovery. For additional information, see the description associated with the nested message. 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 “Event Management” (page 163).
PAGE 239
1052: ZPWY-ERR-PM-TCPNOTDEFINED The Pathway/iTS TCP specified in a terminal 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 “Event Management” (page 163).
PAGE 240
ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-TCPNAME. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-TCPREQUESTFAIL. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-LM or ZPWY-OBJ-TCP. Effect. The request is not completed.
PAGE 241
ZSPI-TKN-ERROR contains ZPWY-ERR-PM-ALREADYFROZEN. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-FREEZE from the request. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-SC. ZPWY-TKN-REQSCNAME contains the name of the server from the request. Effect. None. Recovery. Informational message only; no corrective action is needed. 1058: ZPWY-ERR-PM-FREEZEINPROGRESS A freeze request for the server is already in progress.
PAGE 242
Recovery. Informational message only; no corrective action is needed. 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 “Event Management” (page 163).
PAGE 243
ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-SCNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SCNAME. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-MUSTBEFROZEN. ZPWY-TKN-REQCOMMAND contains the value ZPWY-CMD-STOP from the request. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-SC. ZPWY-TKN-REQSCNAME contains the name of the server that is not frozen. Effect. The command fails. Recovery.
PAGE 244
ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-TERM. ZPWY-TKN-REQTELLNAME contains the number of the tell message. Effect. The tell message request fails. Recovery. Enter a value between 1 and 300 in the ZMAXTELLQUEUE field. 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.
PAGE 245
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZPWY-TKN-ERRINFO ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type Token Descriptions ZSPI-TKN-ERROR ZSPI-TYP-LIST. ZSPI-TYP-ERROR.
PAGE 246
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.
PAGE 247
ZSPI-TKN-ERROR contains ZPWY-ERR-PM-NOSTATICSCPROCESS. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-START from the request. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-SC. ZPWY-TKN-REQSCNAME contains the name of the server you attempted to start. Effect. The PATHMON process cannot start a server process until it receives a request from an ACS subsystem processes, or a Pathway/iTS TCP. Recovery. Define the ZNUMSTATIC field in ZPWY-DDL-DEF-SC with a value from 0 to 4095.
PAGE 248
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 Pathway subsystem cannot be run. Recovery. Load the Pathway subsystem microcode and restart the subsystem. 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 “Event Management” (page 163).
PAGE 249
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-TERMNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT.
PAGE 250
ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type ZSPI-TYP-nnnNAME. token-type ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-PROGABORTEDERROR. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-START. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-PROG or ZPWY-OBJ-TERM. ZPWY-TKN-REQnnnNAME contains either the name of the program or the name of the TERM for which a start was attempted. Effect. The terminal’s operation is aborted. Recovery.
PAGE 251
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQPROGNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-PROGNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-PROGNAME. ZSPI-TYP-INT.
PAGE 252
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
PAGE 253
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT.
PAGE 254
ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQSCPROCESSNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-SCPROCESSNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-SCPROCESSNAME. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SCPROCESSNAME. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-TOOMANYSCPROCESS.
PAGE 255
ZPWY-TKN-SCASSIGNNAME ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SCASSIGNNAME. token-type ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-TOOMANYSCASSIGN. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-ADD or ZPWY-CMD-ALTER. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-SCASSIGN. ZPWY-TKN-REQSCASSIGNNAME contains the name of the ASSIGN message that not be added. Effect. The ADD SCASSIGN or ALTER SCASSIGN command fails. Recovery.
PAGE 256
ZSPI-TKN-ERROR contains ZPWY-ERR-PM-TOOMANYTELL. ZPWY-TKN-REQCOMMAND contains ZPWY-CMD-ADD. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-TKN-TELL. ZPWY-TKN-REQTELLNAME contains the number of the tell message that not be added. Effect. The tell message requests fail. Recovery. Increase or decrease the value of the ZMAXTELLS field depending on the cause of the error.
PAGE 257
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
PAGE 258
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.
PAGE 259
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 abends after displaying this message. Recovery. Use a B40 or later version of the operating system. 1130: ZPWY-ERR-PM-SPIDISABLED The SPI facility is not available. The PATHMON process cannot handle requests from processes calling the SPI procedures.
PAGE 260
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
PAGE 261
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 “Event Management” (page 163).
PAGE 262
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). 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. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-SSCTL.
PAGE 263
Error-Message Text *1156* PATHCTL FILE NOW INACCESSIBLE DUE TO FILE SYSTEM ERROR Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-PCTLINACCESSIBLE. Effect. The command might or might not fail, depending upon when the file-system error occurred during the processing of the command. If the command fails, ZPWY-EVT-PM-PATHCTLIO (event 1017) is returned. In either case, the PATHMON configuration file cannot be accessed by subsequent commands. Recovery.
PAGE 264
*1159* object-type object-name, OSS PROCESS CREATION FAILURE: (oss-process-creation-detail) Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-PM-OSSPROCESSFAILURE. ZPWY-TKN-REQCOMMAND contains the ZPWY-CMD-START command from the request. ZPWY-TKN-REQOBJECTTYPE contains ZPWY-OBJ-SC from the request. ZPWY-TKN-REQnnnNAME contains the name of the server object from the request. ZSPI-TKN-OSSERRNO contains the OSS error number returned by the PROCESS_SPAWN_ procedure.
PAGE 265
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT.
PAGE 266
ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZPWY-TKN-ERRINFO ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-UINT. ZSPI-TYP-nnnNAME. ZSPI-TYPE-INT. ZSPI-TYP-SSCTL. Error-Message Text *1164* LICENSING ERROR: PRODUCT NOT LICENSED Token Descriptions ZSPI-TKN-ERROR ZSPI-TKN-ERRINFO contains ZPWY-ERR-PM-PRODUCTNOTLICENSED. indicates either ZPWY-VAL-PATHWAYTS or ZPWY-VAL-NONSTOPTSMP, the product that is not licensed. Effect. The command fails. Recovery.
PAGE 267
13 ACS Subsystem Messages Introduction This section describes the event and error messages logged by the PATHMON process on behalf of the ACS subsystem processes. The descriptions are given in ascending order by message number. NOTE: The messages described in the section are a subset of the messages in the message number range 1000 to 1071 and 3000 to 3999 that are reported by ACS subsystem processes. The messages reported by TCPs are described in the Pathway/iTS Management Programming Manual.
PAGE 268
Event-Message SPI Format Each event message in this chapter includes: • The number and name of the event message • A description of the event-message cause • A syntax box listing : ◦ The tokens associated with the message ◦ Unconditional and conditional tokens that have specific values for the event message. For a description of each token, see “Event Management” (page 163). ◦ The text version of the event message.
PAGE 269
The following unconditional tokens, which can have different values for each event message, occur in each event message generated by the ACS subsystem and are not individually listed in the message descriptions: ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN contains the value ZSPI-VAL-FALSE if the value of ZACL-TKN-EVENT-LEVEL is less than ZACL-VAL-EVENT-LEVEL-WARNING. Contains the value ZSPI-VAL-TRUE if the value of ZACL-TKN-EVENT-LEVEL is greater than or equal to ZACL-VAL-EVENT-LEVEL-WARNING.
PAGE 270
Error Presentation 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” (page 171). 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.
PAGE 271
indicates that an ACS subsystem process encountered a condition that prevented it from performing any more operations. The process terminates immediately aborting any operations that are in progress. If the condition was an internal error in the process logic or data, then it generates a SaveAbend file. Typically, the process termination disables the CPU in which it was running. Recovery actions, including restarting the ACS subsystem, are required for fatal events.
PAGE 272
Effect. The domain coordinator process runs as a single process. Recovery. Correct the error condition. If the problem persists, contact your HP support analyst. 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.
PAGE 273
1004: ZACL-EVT-CP-LAUNCH-ERROR Either the domain coordinator process cannot create an ACS subsystem process in the specified CPU on the local system because the PROCESS_LAUNCH_() operation failed or the ACS subsystem process was created but the PROCESS_LAUNCH_() operation returned a warning.
PAGE 274
ZACL-TKN-EVENT-ERROR-CODE ZACL-TKN-EVENT-ERROR-DETAIL 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-SSID. token-type ZSPI-TYP-PHANDLE. token-type ZSPI-TYP-STRING.
PAGE 275
WARNING 1006 - Guardian file operation FILE_OPEN_() failed, file , error Token Descriptions ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCEDURE has one of the values ZACL-VAL-EVENT-LEVEL-WARNING, ZACL-VAL-EVENT-LEVEL-ERROR, or ZACL-VAL-EVENT-LEVEL-FATAL. the name of the Guardian file-system procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the failed process.
PAGE 276
1008: ZACL-EVT-PROCINFO-ERROR An ACS subsystem process invoked a Guardian process information procedure and the operation failed unexpectedly. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-PROCEDURE 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-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INT. ZSPI-TYP-INT.
PAGE 277
ZACL-TKN-EVENT-PROCEDURE contains the name of the Pathsend or link-management procedure that reported the failure. This token is the subject of the event message. ZACL-TKN-EVENT-ERROR-CODE contains the Pathsend error code returned by the failed operation. ZACL-TKN-EVENT-ERROR-DETAIL contains the file-system error code returned by the failed operation. If the value of this token is zero in an event message, the token is null and is omitted from the message.
PAGE 278
1011: ZACL-EVT-SEGMENT-CORRUPT An ACS subsystem process detected corruption in the ACS subsystem shared memory segment in the CPU. 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 1011 - Corruption detected in shared memory segment segment-id Token Descriptions ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-SEGMENT-ID has the value of ZACL-VAL-EVENT-LEVEL-FATAL.
PAGE 279
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 ZACL-TKN-EVENT-SEGMENT-ID has the value of ZACL-VAL-EVENT-LEVEL-FATAL.
PAGE 280
1016 ZACL-EVT-MEMPOOL-NOSPACE An ACS subsystem process not allocate the space it needed in the ACS shared memory segment in the CPU. Depending upon why the process needed the memory allocation, the operation it was performing may have failed or the ACS subsystem processes in the CPU may need to be restarted. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-SEGMENT-ID token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-INT.
PAGE 281
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.
PAGE 282
If the process identified by this token still exists when the event message text is generated, the EMS event message formatting facilities convert process handle tokens to named or unnamed process descriptor strings. If the process no longer exists, EMS generates a question mark instead of the process descriptor string. Cause. An ACS subsystem process received an incompatible version of a request message. Effect. The request message is ignored.
PAGE 283
ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-ERROR. ZACL-TKN-EVENT-PROCESS-ID contains the process handle of the process that committed the protocol error. This token is the subject of the event message. Effect. The operation in which the protocol error occurred is aborted. Recovery. Contact your HP support analyst. 1022: ZACL-EVT-PATHMON-IO-TIMEOUT An I/O operation from an ACS subsystem process to a PATHMON process timed out.
PAGE 284
Recovery. Retry the send operation. If the problem persists, check the PATHMON process. You may need to shutdown and restart your application. 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.
PAGE 285
1026: ZACL-EVT-PATHMON-NOOPEN A PATHMON process not open an ACS subsystem 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 1026 - No OPEN received from PATHMON process-name 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.
PAGE 286
ZACL-TKN-EVENT-PROCESS-NAME contains the name of the PATHMON process. This token is the subject of the event message. Effect. If the MAT message was sent in response to an operational command from PATHCOM or from SPI requesters, the command fails. PATHMON logs an EMS event. Recovery. No recovery action is required. 1029: ZACL-EVT-CPU-STARTED The ACS subsystem processes in the specified CPU were started in response to a START command or were restarted in response to a CONTROL command.
PAGE 287
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.
PAGE 288
1033: ZACL-EVT-LOG1-CLOSED The LOG1 event log file was closed either in response to an operator command or because an error occurred while writing to the log file. 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.
PAGE 289
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.
PAGE 290
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. ZSPI-TYP-FNAME32. ZSPI-TYP-STRING. ZSPI-TYP-PHANDLE.
PAGE 291
ZSPI-TKN-MANAGER ZACL-TKN-EVENT-ACCESS-ID token-type ZSPI-TYP-FNAME32. token-type ZSPI-TYP-UINT. Event-Message Text 1042 - Unauthorized attempt to invoke server pathmonname. serverclass-name, access-user access-id Token Descriptions ZACL-TKN-EVENT-LEVEL has the value ZACL-VAL-EVENT-LEVEL-WARNING. ZACL-TKN-EVENT-SERVER-NAME contains the name of the server class specified in the Pathsend operation. This token is the subject of the event message.
PAGE 292
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 ZACL-TKN-EVENT-CPU-NUMBER has the value of ZACL-VAL-EVENT-LEVEL-FATAL. token-type ZSPI-TYP-INT. contains the invalid CPU number. This token is the subject of the event message. Effect. The primary domain coordinator process terminates immediately. Recovery. Start the domain coordinator process.
PAGE 293
Recovery. Use the STOP command to stop the ACS subsystem, then purge the corrupt file and start the subsystem again. 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.
PAGE 294
1068: ZACL-EVT-INVALID-HOMETERM The home terminal is no longer valid and cannot be used to create a backup domain coordinator process or other ACS subsystem process. Unconditional Tokens ZACL-TKN-EVENT-LEVEL ZACL-TKN-EVENT-FILE-NAME ZACL-TKN-EVENT-PROCESS-NAME token-type ZACL-TYP-EVENT-LEVEL. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-STRING.
PAGE 295
1070 - Process pair for process-name cannot switch over Token Descriptions ZACL-TKN-EVENT-LEVEL has the value of ZACL-VAL-EVENT-LEVEL-INFO. ZACL-TKN-EVENT-PROCESS-NAME contains the name of the process pair. Effect. The process pair cannot switch; ACS subsystem processes may not be available to handle requests. Recovery. If the backup-process CPU is down, reload it. If the backup-process CPU is up, use the CONTROL command to restart the ACS subsystem processes.
PAGE 296
ZACL-TKN-EVENT-TERM-TEXT contains the termination text associated with the primary process termination. This token is omitted if no termination text was associated with the process termination. ZACL-TKN-EVENT-ERROR-DETAIL contains the termination information code associated with the process termination. If the value of this token is 0 (zero), the token is null and can be regarded as omitted from the message.
PAGE 297
3100: ZPWY-EVT-TCP-SCPROCESSOPEN A file-system error (errnum) occurred while a server process was being opened. This event can be reported by either the ACS subsystem processes, or the Pathway/iTS TCP. For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163).
PAGE 298
ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-SCNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type ZSPI-TYP-SSCTL. ZPWY-TYP-nnnNAME. ZPWY-TYP-SCNAME. ZSPI-TYP-ENUM. Conditional Tokens N ZPWY-TKN-ERROR ZPWY-TKN-INSTRUCTION ZPWY-TKN-PUNAME ZPWY-TKN-PUOFFSET ZPWY-TKN-PUVERSION ZPWY-TKN-TCLPROGFNAME token-type ZSPI-TYP-INT token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. SCOBOL-PUNAME. ZSPI-TYP-INT2. ZSPI-TYP-INT2. ZSPI-TYP-FNAME32.
PAGE 299
ZPWY-TKN-PUVERSION ZPWY-TKN-TCLPROGFNAME token-type ZSPI-TYP-INT2. token-type ZSPI-TYP-FNAME32. Event-Message Text *3117* link manager-name, SERVER CLASS UNDEFINED --INST CODE: inst-code AT OFFSET %offset IN PROGRAM UNIT program-unit (version) IN TCLPROG tclprog Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-TCP-SCNOTDEFINED (3117).
PAGE 300
ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-LMNAME or ZPWY-TKN-TCPNAME, which contains the name of the ACS Process Broker, or the TCP that is the subject of this message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. Effect. The operation fails. Recovery. Contact your Global Customer Support Center (GCSC). 3200: ZPWY-EVT-TCP-BADPMTCPMSG The specified TCP, or ACS subsystem processes received an invalid request from the PATHMON process.
PAGE 301
*3201* link manager-name, SYNCID VIOLATION IN MESSAGE RECEIVED BY TCP Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-TRUE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-TCP-BADSYNCID (3201). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-LMNAME or ZPWY-TKN-TCPNAME, which contains the name of the ACS Process Broker, or TCP that is the subject of this message. ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. Effect. The request cannot be processed. Recovery.
PAGE 302
ZEMS-TKN-SUBJECT-MARK token-type ZSPI-TYP-SSCTL. ZPWY-TKN-nnnNAME token-type ZPWY-TYP-nnnNAME. ZPWY-TKN-EVENTCLASS token-type ZSPI-TYP-ENUM. Event-Message Text *3233* link manager-name, SERVER PROCESS UNKNOWN Token Descriptions ZEMS-TKN-EMPHASIS has a value of ZSPI-VAL-TRUE. ZEMS-TKN-EVENTNUMBER contains ZPWY-EVT-TCP-SPUNKNOWN (3233). ZEMS-TKN-SUBJECT-MARK indicates ZPWY-TKN-LMNAME or ZPWY-TKN-TCPNAME, which contains the name of the , the ACS Process Broker, or TCP that is the subject of this message.
PAGE 303
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 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 “Event Management” (page 163).
PAGE 304
Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-TCP-BADSYNCID. Effect. The request cannot be processed. Recovery. Contact your Global Customer Support Center (GCSC). 3226: ZPWY-ERR-TCP-PMTCPFNS The PATHMON process requested a function not supported in this version of the TCP or the ACS subsystem process. For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163).
PAGE 305
14 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 message numbers range represent events and errors reported to the PATHMON process by other processes.
PAGE 306
For descriptions of these object types, see “Object Types” (page 32). Object types not listed above are Pathway/iTS objects, described in the Pathway/iTS Management Programming Manual. Error-Message Range 4000 Through 4999 Error messages numbered from 4000 to 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.
PAGE 307
ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZSPI-TKN-PARM-ERR ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR token-type token-type token-type token-type ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-DDL-PARM-ERR. ZSPI-TYP-SSCTL. contains ZPWY-ERR-SPI-WRONGTOKEN. contains the code of the extraneous token and the offset to the field in error. Effect. The request fails. Recovery. Remove the inappropriate token, replace it with the correct token, and reissue the request.
PAGE 308
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-PARM-ERR Token Descriptions ZSPI-TKN-ERROR ZSPI-TKN-PARM-ERR token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT.
PAGE 309
ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type ZSPI-TYP-UINT. token-type ZSPI-TYP-nnnNAME. token-type ZSPI-TYP-SSCTL. contains ZPWY-ERR-SPI-TOOMANYDEFSERVERS. Effect. The request fails. Recovery. Redefine the value of the ZMAXSERVERS field and reissue the request. 4009: ZPWY-ERR-SPI-INVALIDBUFFER The SPI procedures report an invalid message buffer.
PAGE 310
ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type token-type token-type token-type ZSPI-TYP-INT. ZSPI-TYP-UINT. ZSPI-TYP-nnnNAME. ZSPI-TYP-SSCTL. contains ZPWY-ERR-SPI-SSPUT. Effect. The call to SSPUT fails. Recovery. For information regarding this error, see the Guardian Procedure Calls Reference Manual. 4012: ZPWY-ERR-SPI-SSGET An error occurred on the call to SSGET.
PAGE 311
ZSPI-TKN-ERROR contains ZPWY-ERR-SPI-SSNULL. Effect. The call to SSNULL fails. Recovery. For information regarding this error, see the Guardian Procedure Calls Reference Manual. 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 “Event Management” (page 163).
PAGE 312
Effect. The request fails. Recovery. Correct the context token and reissue the request. 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 “Event Management” (page 163).
PAGE 313
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST Token Descriptions ZSPI-TKN-ERROR token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT.
PAGE 314
Effect. The OSS server attribute CWD is not reset. Recovery. Before resetting the CWD attribute, you must change any relative OSS pathname to an absolute pathname. 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 “Event Management” (page 163).
PAGE 315
For a description of tokens that are present in this event message but are not listed or described below, see “Event Management” (page 163). ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZPWY-TKN-REQCOMMAND ZPWY-TKN-REQOBJECTTYPE ZPWY-TKN-REQnnnNAME ZPWY-TKN-ERRCOMMAND ZPWY-TKN-ERROBJECTTYPE ZPWY-TKN-nnnNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-UINT. ZPWY-TYP-nnnNAME. ZSPI-TYP-INT.
PAGE 316
*4028* THE COMBINED LENGTH OF ARGLIST AND ENV IS GREATER THAN IS ALLOWED Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-SPI-ARGENVEXCEEDMAX. Effect. Whichever token was specified last, ZPWY-TKN-DEF-SCARGLIST or ZPWY-TKN-DEF-SCENV, is not set. The ADD or ALTER command fails. Recovery. Set the startup arguments and the environment variables within the allowed maximum length. See the descriptions of “ZPWY-TKN-DEF-SCARGLIST” (page 71) and “ZPWY-TKN-DEF-SCENV” (page 72).
PAGE 317
Token Descriptions ZSPI-TKN-ERROR contains ZPWY-ERR-SPI-NAMENOTABSOLUTE. Effect. The ADD or ALTER command fails. Recovery. Either specify an absolute pathname for the given field or token, or set an absolute pathname for ZPWY-TKN-DEF-SCCWD. 4031: ZPWY-ERR-SPI-BUFFEREXHAUSTION There are already five pending requests from this SPI requester; no new request can be processed now.
PAGE 318
15 Management Programming Examples This section contains the following 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 3 (page 319) presents a management program (written in COBOL) that configures a Pathway subsystem. 1. Starts the PATHMON process 2. Starts the Pathway subsystem 3.
PAGE 319
Example 3 TS/MP Configuration Program * 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.zspidef) * On TNS/E, use this command: * ECOBOL /IN / ;SUPPRESS;RUNNABLE;ELD (-SET RUNNAMED ON) * For TNS COBOL, add this define.
PAGE 320
05 05 05 05 05 05 WS-BACKUP-CPU PIC S9(4) COMP VALUE 1. WS-SS-RESULT NATIVE-2 VALUE -1. WS-SPI-RESULT NATIVE-2 VALUE -1. WS-COBOL-RESULT PIC S9(4) COMP VALUE 0. WS-ERROR-DETAIL NATIVE-2 VALUE 0. WS-PHANDLE. 10 filler occurs 10 times. 15 filler native-2. 05 WS-TEMPORARY-RESULT PIC S9(4) COMP VALUE 0. 05 WS-TEMPORARY-AREA PIC X(80). 05 WS-PARA-NAME PIC X(80). 05 WS-ERROR-TEXT PIC X(80). 01 PRINT-LINES. 05 WS-BLANK-LINE PIC X(2) VALUE SPACES.
PAGE 321
PROCEDURE DIVISION. 100-ENTRY. PERFORM 200-INITIALIZE PERFORM 300-START-PATHMON PERFORM 400-OPEN-PATHMON PERFORM 500-MAINLINE PERFORM 1800-TERMINATE STOP RUN . 200-INITIALIZE. MOVE "200-INITIALIZE" TO WS-PARA-NAME * Null structures for later comparisons.
PAGE 322
IF OK-TO-CONTINUE THEN OPEN I-O PATHMON-FILE END-IF . 500-MAINLINE. PERFORM 600-CONFIGURE-PATHWAY IF OK-TO-CONTINUE THEN PERFORM 900-ADD-SERVERCLASS PERFORM 1500-START-SERVERCLASS PERFORM 1600-STATUS-SERVERCLASS-DETAIL END-IF . / 600-CONFIGURE-PATHWAY. MOVE "600-CONFIGURE-PATHWAY" TO WS-PARA-NAME * Construct a START PATHWAY command to cold start Pathway.
PAGE 323
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. PERFORM 3800-ISSUE-PATHMON-COMMAND * Finally, obtain the default values for the * server class definition.
PAGE 324
MOVE "FILE-2" TO WS-LOGICAL-FILE MOVE "FILE2" TO FILE-NAME OF WS-FILE-NAME PERFORM 1100-ADD-SERVERCLASS-ASSIGN MOVE "FILE-3" TO WS-LOGICAL-FILE MOVE "FILE3" TO FILE-NAME OF WS-FILE-NAME PERFORM 1100-ADD-SERVERCLASS-ASSIGN MOVE "FILE-4" TO WS-LOGICAL-FILE 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.
PAGE 325
* Issue the STATUS SCPROCESS command. PERFORM 2300-STATUS-SCPROCESS-CONTINUE UNTIL NOT OK-TO-CONTINUE IF EOF-HIT THEN SET OK-TO-CONTINUE TO TRUE END-IF . 1700-STATUS-SERVERCLASS. * Construct the STATUS SC command. MOVE ZPWY-CMD-STATUS 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. PERFORM 3100-SELECT-SERVERCLASS * Issue the STATUS SC cmd (ZPWY-DDL-PAR-STATUS-SC is not needed).
PAGE 326
IF ZINFO OF ZPWY-DDL-STATUS-SC IS NOT EQUAL TO ZINFO OF NULL-STATUS-SC MOVE ZINFO OF ZPWY-DDL-STATUS-SC TO LAST-INFO OF WS-STATUS-SC-DETAIL END-IF EVALUATE ZFREEZESTATE OF ZPWY-DDL-STATUS-SC WHEN ZPWY-VAL-PENDING MOVE "FREEZE-PENDING" TO FREEZE-STATE OF WS-STATUS-SC-DETAIL WHEN ZPWY-VAL-FROZEN MOVE "FROZEN" TO FREEZE-STATE OF WS-STATUS-SC-DETAIL END-EVALUATE DISPLAY WS-STATUS-SC-DETAIL . 2700-DISPLAY-STATUS-SCPROCESS.
PAGE 327
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 . 3200-SELECT-SCASSIGN. MOVE "3200-SELECT-SCASSIGN" TO WS-PARA-NAME * Clear, build, and put the object-selector token for the * server class ASSIGN message into the buffer.
PAGE 328
* Get the RETCODE token. ENTER TAL "SSGET" USING ZPWY-DDL-MSG-BUFFER, ZSPI-TKN-RETCODE, WS-SPI-RESULT GIVING WS-SS-RESULT STRING WS-PARA-NAME DELIMITED BY SPACE " - 3800-ISSUE-PATHMON-COMMAND" DELIMITED BY SIZE INTO WS-PARA-NAME MOVE "SSGET of ZSPI-TKN-RETCODE" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR END-IF IF OK-TO-CONTINUE THEN * Evaluate the Pathway error, if any.
PAGE 329
MOVE WS-COBOL-VAL-YES TO ZIGNORE OF ZPWY-DDL-PAR-START-PATHWAY ENTER TAL "SSPUT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-MAP-PAR-START-PATHWAY, ZPWY-DDL-PAR-START-PATHWAY GIVING WS-SS-RESULT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Build and put the Pathway definition into the buffer.
PAGE 330
PERFORM 2800-SELECT-COMMAND-OBJECT * Construct the object-selector token for the server class. MOVE "SERVER-SPI" TO OBJECT-NAME OF WS-SPI-INPUT PERFORM 3100-SELECT-SERVERCLASS * Set appropriate server class definition values.
PAGE 331
* * * * ENTER TAL "SSNULL" USING ZPWY-MAP-DEF-SCASSIGN, ZPWY-DDL-DEF-SCASSIGN GIVING WS-SS-RESULT 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 ".
PAGE 332
1800-TERMINATE. SET OK-TO-CONTINUE TO TRUE PERFORM 1900-SHUTDOWN-PATHWAY CLOSE PATHMON-FILE . 1900-SHUTDOWN-PATHWAY. * Construct the STOP PATHWAY command. MOVE ZPWY-CMD-STOP TO COMMAND OF WS-SPI-INPUT MOVE ZPWY-OBJ-PATHWAY TO OBJECT-TYPE OF WS-SPI-INPUT PERFORM 2800-SELECT-COMMAND-OBJECT * Issue the STOP PATHWAY command. PERFORM 3800-ISSUE-PATHMON-COMMAND . 2200-BUILD-STATUS-SP-ALL. * Construct the STATUS SCPROCESS command.
PAGE 333
MOVE "SSGET of ZPWY-DDL-SEL-SCPROCESS" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Get the SCPROCESS status definition.
PAGE 334
PERFORM 4000-CHECK-SUBSYSTEM-ERROR MOVE OBJECT-NAME OF WS-SPI-INPUT TO ZSERVERCLASS OF ZPWY-DDL-SEL-SCASSIGN MOVE WS-PROGRAM-UNIT TO ZPROGRAMUNIT OF ZPWY-DDL-SEL-SCASSIGN MOVE WS-LOGICAL-FILE TO ZLOGICALFILE OF ZPWY-DDL-SEL-SCASSIGN ENTER TAL "SSPUT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-MAP-SEL-SCASSIGN, ZPWY-DDL-SEL-SCASSIGN GIVING WS-SS-RESULT MOVE "SSPUT of ZPWY-DDL-SEL-SCASSIGN" TO WS-ERROR-TEXT PERFORM 4000-CHECK-SUBSYSTEM-ERROR . 3300-SELECT-SCPROCESS.
PAGE 335
WHEN ZPWY-VAL-OK SET OK-TO-CONTINUE TO TRUE WHEN ZPWY-ERR-PM-EOF SET NOT-OK-TO-CONTINUE TO TRUE WHEN OTHER SET NOT-OK-TO-CONTINUE TO TRUE * CALL PATHWAY-SPI-ERROR IN PATHWAY-UTILITIES * USING ZPWY-DDL-MSG-BUFFER ENTER TAL "DEBUG" END-EVALUATE END-IF . 3900-CHECK-COBOL-ERROR. IF WS-COBOL-RESULT IS NOT ZERO THEN DISPLAY "COBOL UTILITY ERROR: " WS-COBOL-RESULT SET NOT-OK-TO-CONTINUE TO TRUE END-IF . 4000-CHECK-SUBSYSTEM-ERROR.
PAGE 336
Example 4 Adding or Altering a Server ?TACL MACRO #FRAME [#PUSH X^ Y^ read^err io^err reply request pmon^name result^1 j^1 result^2 j^2 result^3 res^cmd res^obj res^err res^name cont^true svr^name command^ ] == end #push == == == == == == == == == == == == == variables for zspi and zpwy ddls #requester variables pathmon name parameter contains result of ssget operation contains # of tokens ssget returned contains ssget pathway error contains command from response buffer contains object type from response
PAGE 337
OTHERWISE] |1| [#CASE [#ARGUMENT END OTHERWISE] |1| [#IF [#MATCH [T^svr^name] [ast^]] |THEN| #OUTPUT You can only ADD/ALTER one server at a time !!! #OUTPUT Please enter a valid server name................ #RESULT 0 |ELSE| #SET cont^true 0 [#IF ([#CHARCOUNT T^svr^name] > 15) |THEN| #RESULT 0 #OUTPUT ERROR Server name > 15 characters:[T^svr^name] |ELSE| == now make sure the server name starts with an == alphanumeric character.
PAGE 338
== Set the SSID (subsystem ID) value, which tells SPI what product you are == interfacing with. #SET zpwy^val^ssid [zspi^val^tandem].[zspi^ssn^zpwy].[zpwy^val^version] == Initialize the buffer (spi^buf) with the SSID value and the command == that is to be executed. SINK [#SSINIT /TYPE 0/ spi^buf [zpwy^val^ssid] [zpwy^cmd^[command^]] /OBJECT [zpwy^obj^sc]/] == == == == Initialize the ZPWY^DDL^SEL^SC token with null values using ZPWY^MAP^SEL^SC to determine how each field is to be initialized.
PAGE 339
[#IF ([result^3] > 0) |THEN| #OUTPUT The [command^] command terminated with an #OUTPUT Error **** [result^3] **** SINK [#SSGET/ INDEX 1 /spi^buf zspi^tkn^errlist] #SETMANY j^1 j^2 res^cmd, [#SSGET/ INDEX 1 /spi^buf zpwy^tkn^reqcommand] [#IF [#MATCH [res^cmd] [zpwy^cmd^add]] |THEN| #OUTPUT ZPWY^TKN^REQCOMMAND = ZPWY^CMD^ADD |ELSE| #OUTPUT ZPWY^TKN^REQCOMMAND = ZPWY^CMD^ALTER ] == end if match res^cmd .....
PAGE 340
Example 5 Obtaining Subsystem Information Program Example ?TACL MACRO #FRAME [#PUSH X^ Y^ read^err io^err reply request pmon^name result^1 result^2 result^3 ] == end push == == == == == == variables for zspi and zpwy ddls #requester variables pathmon name from input parameter contains result of ssget operation contains # of tokens ssget returned contains ssget pathway error == Make sure the PATHMON name is provided and that is starts with a "$".
PAGE 341
#SET read^err [#REQUESTER/WAIT [zpwy^val^buflen] / READ & [pmon^name].#ZSPI io^err reply request] [#IF read^err |THEN| #OUTPUT Error [read^err] opening PATHMON [pmon^name] [#IF not [#EMPTYV io^err] |THEN| #OUTPUT Error [io^err] is the culprit... ] == end if not [emptyv io^err] ... |ELSE| #APPENDV request spi^buf == send the request #EXTRACTV reply spi^buf == receive the reply SINK [#REQUESTER CLOSE request] == Check to ensure no Pathway errors occurred.
PAGE 342
Example 6 ASCICONV Source File INT PROC ASCII (V,RJUST,STG); INT V; INT RJUST; STRING .STG; BEGIN STRING .
PAGE 343
16 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 7 (page 344) 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 angular brackets (< >). For example, you must change: .#ZSPI to: $PM.
PAGE 344
Example 7 ADD SCDEFINE Programming Example ?TACL MACRO #FRAME == First load the SPI token definition files "ZPWYTACL" and "ZSPITACL". == These files are usually found on $DSV.ZSPIDEF. #PUSH X^ Y^ == Variable to load definition files into. This prevents == TACL from running out of segment space. #LOAD/LOADED X^/ ZPWYTACL #LOAD/LOADED Y^/ ZSPITACL == Add the DEFINE with its specific attributes to the TACL working set. #DEFINESETATTR CLASS MAP #DEFINESETATTR FILE $PQA3.MZDEFTST.
PAGE 345
== Set the ssid (subsystem ID) value, which tells SPI what product your == system is interfacing with and the version of that product. #SET zpwy^val^ssid [zspi^val^tandem].[zspi^ssn^zpwy].[zpwy^val^version] == Execute SSNULL and SSINIT functions to set up the request buffer.
PAGE 346
Obtaining Server Class DEFINE Information Example 8 (page 347) presents a functioning SPI requester that obtains DEFINE information from 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 angular brackets (< >). For example, you must change: .#ZSPI to: $PM.#ZSPI where $PM is the name of the PATHMON process controlling your Pathway subsystem.
PAGE 347
Example 8 INFO SCDEFINE Programming Example ?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. #LOAD/LOADED X^/ ZPWYTACL #LOAD/LOADED Y^/ ZSPITACL == == == == == == == == Define a structure to hold the DEFINEs that are sent to PATHMON and received from PATHMON.
PAGE 348
#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. [#PUSH reply^var == holds the reply from PATHMON io^err == holds I/O error returned during I/O with PATHMON prompt^var == holds the input to PATHMON ] == end push #REQUESTER /WAIT [zpwy^val^buflen]/ READ $.
PAGE 349
17 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-TKN-RETCODE token, see the SPI Programming Manual. 2. Locates and displays the error message text. 3.
PAGE 350
Example 9 Handling Errors IDENTIFICATION DIVISION. PROGRAM-ID. PATHWAY-SPI-ERROR. ?CONSULT COBOLEX0 ENVIRONMENT DIVISION. DATA DIVISION. WORKING-STORAGE SECTION. 01 MISCELLANEOUS. 05 WS-SS-RESULT 05 WS-SPI-RESULT 05 WS-FIRST-OCCURRENCE 05 WS-REQUEST. 10 COMMAND 10 OBJECT-TYPE 10 OBJECT-FLAG 88 OBJECT-HAS-NO-NAME 88 OBJECT-HAS-NAME 10 REQ-NAME-TKN 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.
PAGE 351
05 FILLER PIC X(15) VALUE "RESUME". 05 FILLER PIC X(15) VALUE "START". 05 FILLER PIC X(15) VALUE "STATS". 05 FILLER PIC X(15) VALUE "STATUS". 05 FILLER PIC X(15) VALUE "STOP". 05 FILLER PIC X(15) VALUE "SUSPEND". 05 FILLER PIC X(15) VALUE "SWITCH". 05 FILLER PIC X(15) VALUE "TELL". 05 FILLER PIC X(15) VALUE "THAW". 05 FILLER PIC X(15) VALUE "SHUTDOWN2". 01 WS-COMMAND-NAMES REDEFINES WS-COMMAND-NAME-TABLE. 05 COMMAND-ENTRY PIC X(15) OCCURS 21 TIMES. / 01 WS-OBJECT-TYPE-NAME-TABLE.
PAGE 352
05 FILLER NATIVE-4. 05 FILLER NATIVE-4. 05 FILLER PIC X(12) VALUE "TCP". 05 FILLER PIC 9 VALUE 1. 05 FILLER NATIVE-4. 05 FILLER NATIVE-4. 05 FILLER PIC X(12) VALUE "TCPLINK". 05 FILLER PIC 9 VALUE 1. 05 FILLER NATIVE-4. 05 FILLER NATIVE-4. 05 FILLER PIC X(12) VALUE "TCPSC". 05 FILLER PIC 9 VALUE 1. 05 FILLER NATIVE-4. 05 FILLER NATIVE-4. 05 FILLER PIC X(12) VALUE "TCPTERM". 05 FILLER PIC 9 VALUE 1. 05 FILLER NATIVE-4. 05 FILLER NATIVE-4. 05 FILLER PIC X(12) VALUE "TELL". 05 FILLER PIC 9 VALUE 1.
PAGE 353
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 354
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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER
PAGE 355
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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PIC PIC PIC PIC PIC PI
PAGE 356
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 357
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 358
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 359
05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC X(20) S9(4) X(20) S9(4) X(20) S9(4) X(20) S9(4) X(20) S9(4) VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE "OSSPROCESSFAILURE". 1159. "OSSNOTAVAILABLE". 1160. "PROCTYPEMISMATCH". 1161. "RESIZESEGMENT". 1162. "PRODUCTNOTLICENSED". 1164. 01 WS-PM-ERROR-NAMES REDEFINES WS-PM-ERROR-NAME-TABLE.
PAGE 360
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 361
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 362
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 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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER F
PAGE 363
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 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 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PI
PAGE 364
==ZPWY-DDL-PROGNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-PROGTERMNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-PROGTERMNAME BY ==ZPWY-DDL-PROGTERMNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-SCNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-SCNAME BY ==ZPWY-DDL-SCNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-SCASSIGNNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-SCASSIGNNAME BY ==ZPWY-DDL-SCASSIGNNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-SCLMNAME IN "$SYSTEM.ZSPIDEF.
PAGE 365
EVALUATE WS-SPI-RESULT WHEN ZPWY-VAL-OK DISPLAY "NO PATHMON ERROR: " WS-SPI-RESULT WHEN 1000 THRU 1999 PERFORM 200-DISPLAY-PM-ERROR WHEN 3000 THRU 3999 PERFORM 300-DISPLAY-TCP-ERROR WHEN 4000 THRU 5999 PERFORM 400-DISPLAY-SPI-ERROR WHEN OTHER DISPLAY "UNKNOWN ERROR: " WS-SPI-RESULT END-EVALUATE 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-DIS
PAGE 366
MOVE 0 TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE 0 TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY-TKN-REQPMREQUESTERNAME TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY-TKN-REQPROGNAME TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY-TKN-REQPROGTERMNAME TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY-TKN-REQSCNAME TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY-TKN-REQSCASSIGNNAME TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY-TKN-REQSCLMNAME TO REQ-NAME-TKN OF WS-OBJECT-TYPE-NAMES MOVE ZPWY
PAGE 367
COMMAND OF WS-REQUEST, WS-FIRST-OCCURRENCE GIVING WS-SS-RESULT PERFORM 1300-CHECK-SUBSYSTEM-ERROR IF WS-SS-RESULT IS ZERO THEN ADD 1 TO COMMAND OF WS-REQUEST GIVING PARAMETER OF WS-DECODE IF PARAMETER OF WS-DECODE IS LESS THAN 1 OR PARAMETER OF WS-DECODE IS GREATER THAN MAX-COMMANDS THEN DISPLAY " REQUEST COMMAND: " COMMAND OF WS-REQUEST ELSE DISPLAY " REQUEST COMMAND: " COMMAND-ENTRY OF WS-COMMAND-NAMES ( PARAMETER OF WS-DECODE ) END-IF END-IF . / 600-DISPLAY-REQUEST-OBJTYPE.
PAGE 368
GIVING WS-SS-RESULT IF WS-SS-RESULT IS ZERO THEN DISPLAY " PARAMETER ERROR" PERFORM 1700-DISPLAY-TOKEN-NUMBER DISPLAY " ERROR INDEX: " Z-INDEX OF ZSPI-DDL-PARM-ERR DISPLAY " ERROR OFFSET: " Z-OFFSET OF ZSPI-DDL-PARM-ERR END-IF . 900-DISPLAY-ERROR-CMD.
PAGE 369
STRING " ERROR OBJECT NAME: " DELIMITED BY SIZE INTO IMAGE OF WS-PRINT WITH POINTER INDENT OF WS-PRINT END-STRING PERFORM 1600-DISPLAY-OBJECT-NAME END-IF END-IF . 1200-DISPLAY-ERROR-INFO.
PAGE 370
MOVE 1 TO OBJECT-NAME-COUNT OF WS-DECODE WHEN ZPWY-OBJ-PMREQUESTER MOVE Z-I OF ZPWY-DDL-PMREQUESTERNAME TO OBJECT-NUMBER OF WS-DECODE MOVE 1 TO OBJECT-NAME-COUNT OF WS-DECODE WHEN ZPWY-OBJ-PROG MOVE ZPROGRAM OF ZPWY-DDL-PROGNAME TO OBJECT-NAME-1 OF WS-DECODE MOVE 1 TO OBJECT-NAME-COUNT OF WS-DECODE WHEN ZPWY-OBJ-PROGTERM MOVE ZTERMTYPE OF ZPWY-DDL-PROGTERMNAME TO OBJECT-NAME-1 OF WS-DECODE MOVE ZPROGRAM OF ZPWY-DDL-PROGTERMNAME TO OBJECT-NAME-2 OF WS-DECODE MOVE 2 TO OBJECT-NAME-COUNT OF WS-DECODE WHEN ZPWY
PAGE 371
MOVE ZTCP OF ZPWY-DDL-TCPNAME TO OBJECT-NAME-1 OF WS-DECODE MOVE 1 TO OBJECT-NAME-COUNT OF WS-DECODE WHEN ZPWY-OBJ-TCPLINK MOVE ZTCP OF ZPWY-DDL-TCPLINKNAME TO OBJECT-NAME-1 OF WS-DECODE MOVE ZPROCESS OF ZPWY-DDL-TCPLINKNAME TO OBJECT-NAME-2 OF WS-DECODE MOVE ZSERVERCLASS OF ZPWY-DDL-TCPLINKNAME TO OBJECT-NAME-3 OF WS-DECODE MOVE 3 TO OBJECT-NAME-COUNT OF WS-DECODE WHEN ZPWY-OBJ-TCPSC MOVE ZSERVERCLASS OF ZPWY-DDL-TCPSCNAME TO OBJECT-NAME-1 OF WS-DECODE MOVE ZTCP OF ZPWY-DDL-TCPSCNAME TO OBJECT-NAME-2 OF WS
PAGE 372
A Configuration Limits and Defaults Table 33 (page 372) 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 33 Global Pathway Environment Limits Item Limits Per PATHMON Environment ASSIGNs 8191 for all server classes. ACS subsystem processes For Pathway limits with ACS subsystem processes for TS/MP 2.5, see TS/MP 2.5 Release Supplement.
PAGE 373
Table 34 Limits and Defaults for Parameters PATHCOM Parameter SPI Token/Field Value Limits and Defaults ARGLIST ZPWY-TKN-DEFSCARGLIST Values: OSS process startup argument list; from 2 to 24,000 characters. ZPWY-TKN-DEF-SCENV + ZPWY-TKN-DEF-SCARGLIST cannot exceed 24,000 bytes. ASSOCIATIVE AUTORESTART ZASSOCIATIVE ZAUTORESTART Default: Empty argument list Values: ON | OFF Default: OFF Values: 0 to 32,767 Value be greater than 0.
PAGE 374
Table 34 Limits and Defaults for Parameters (continued) PATHCOM Parameter SPI Token/Field Value Limits and Defaults ENV ZPWY-TKN-DEFSCENV Values: OSS process environment variable list.; from 3 to 24,000 characters. ZPWY-TKN-DEF-SCENV + ZPWY-TKN-DEF-SCARGLIST cannot exceed 24,000 bytes. ERRORS EVENTFORMAT EXT FILE N.A. ZEVENTFORMAT ZEXTENTSIZE ZFILE GUARDIANSWAP HELP HIGHPIN N.A. ZHIGHPIN Default: Empty environment variable list Values: -1 Allow infinite number of errors.
PAGE 375
Table 34 Limits and Defaults for Parameters (continued) PATHCOM Parameter SPI Token/Field Value Limits and Defaults Default: MAXEXTERNALT CPS ZMAXEXTERNALT CPS Values: 0 Total of values for MAXTCPS, MAXEXTERNALTCPS, and MAXLINKMONS must not exceed 800. Maximum number of concurrently running processes (TCP, external TCP, ACS subsytem processes, PATHCOM, and SPI) must not exceed 800.
PAGE 376
Table 34 Limits and Defaults for Parameters (continued) PATHCOM Parameter SPI Token/Field Value Limits and Defaults Total of MAXSERVERS values for all server classes must not exceed value of MAXSERVERPROCESSES. MAXSPI ZMAXSPI Default: 1 Values: 1 to 100 Maximum number of concurrent openers of PATHMON (TCP, external TCP, ACS subsystem processes, PATHCOM, and SPI) must not exceed 800.
PAGE 377
Table 34 Limits and Defaults for Parameters (continued) PATHCOM Parameter N.A. N.A. N.A. NODEINDEPENDENT N.A. NUMSTATIC SPI Token/Field ZFILECODE ZRECORDSIZE ZBLOCKSIZE ZNODEINDEPENDENT Value Limits and Defaults Default: No value is passed. Values: 0 to 65,535 Default: 0 Values: 1 to 4072 Default: No value is passed. Values: 1 to 4096 Default: No value is passed.
PAGE 378
Table 34 Limits and Defaults for Parameters (continued) PATHCOM Parameter SPI Token/Field Value Limits and Defaults For OSS server processes, the OSS pathname of the object file name; maximum of 1024 characters.
PAGE 379
Table 34 Limits and Defaults for Parameters (continued) PATHCOM Parameter SPI Token/Field Value Limits and Defaults value specified in the SERVERCLASS_SEND_ call. TMF UNTIL ZTMF N.A. Default (Pathway/TS TCP): No timeout; TCP waits indefinitely for server I/O operation to complete. Values: ON | OFF Default (SERVER): OFF Pathway/TS Default (PROGRAM): ON Pathway/TS Default (TERM): ON Values: DONE | TIMEOUT Default: DONE 1 PATHCOM is the interactive management interface.
PAGE 380
Index Symbols B !r, definition of, 49 $0 message collector, 165 32-byte file names, 42 ^ character, 31 … (ellipsis), 49 Backup process See ZBACKUP field, 23 BACKUPCPU attribute, 84 Boolean values, 65 Buffers declaration, 54 lengths, declaring, 38 See also ZPWY-VAL-BUFLEN, 23 size and length values, 67 size, event messages, 166, 174 Building blocks, 30 Building messages, 26, 27 A ACS Subsystem processes names, 55 Action events not supported, 166 ADD SC command, 130 ADD SCASSIGN command, 133 ADD SCDEFINE
PAGE 381
defining attributes, 76 obtaining information about, 120 Configuring See individual ADD commands, 23 Console messages, 164 Console printing, 165 Constants, reset, 43 Consumer distributors, starting, 173 Context token, 35, 44 Continuation example, 42 required object states, 41 specifying, 40 CONTROL command, EMS, 173 CONTROL PM command, 117 Control tasks, 25 CPU definitions, 23, 129 See also ZBACKUP field, ZPRIMARY field, 23 CREATEDELAY timer, 84 CWD attribute, 72 D Data block size, 92 Data declaration file
PAGE 382
Field types, 67 private, 59, 67 private for predefined values, 67, 69 Field values predefined, 67 resetting, 43 File extents size, 91 File names, 32-byte, 42, 43 Files See Definitions files, Log files, 23 Filters, EMS compiling, 174 description of, 166 when to use, 173, 174 FNAME32COLLAPSE procedure, 43 FNAME32EXPAND procedure, 43 FNAME32TOFNAME procedure, 43 FNAMETOFNAME32 procedure, 43 Formatting messages, 164 FREEZE SC command, 149 FROZEN object state, 41 L GETBACKUPCPU procedure, 84 GETEVENT command,
PAGE 383
buffer contents, 171 classifying, 166 error lists, 165 returned by LINKMON, 296, 304 returned by PATHMON, 225, 266 returned by SPI, 306 Messages, event buffer contents, 167 buffer size, 174 example, 170 filters for, 174 header tokens, 52, 167 manager token, 168 nested, 169 retrieving and decoding, 173, 174 returned by PATHMON, 178 subject token, 168 subsystem-specific standard tokens, 168 templates, 174 Messages, startup defining attributes, 94 maximum, specifying, 80 purpose, 138 See also SCSTARTUP objects
PAGE 384
Management Programming interface, 25, 27 managing, 17, 20 predefined token and field values, 67 private field types for predefined values, 67, 69 private token and field types, 59, 67 security, 45 simple tokens, 70 status of, 108, 111 subsystem number, 52 variable-length byte strings, 71, 74 PINs, setting, 90 PM objects altering attributes, 95 STATUS command, 125 status information, 111 STOP command, 128 SWITCH command, 128 PMREQUESTER objects description of, 32 selecting , 101 STATUS command, 126 status in
PAGE 385
specifying action for errors, 99 STATS command, 158 SCPARAM objects ADD command, 135 ALTER command, 142 defining attributes, 92 DELETE command, 147 description of, 33 INFO command, 153 name, selecting, 102 programming considerations, 47, 48 SCPROCESS objects ADD command, 136 ALTER command, 143 defining attributes, 93, 94 DELETE command, 147 description of, 33 INFO command, 153 name, selecting, 103 programming considerations, 47, 48 START command, 157 STATUS command, 160 status information, 115, 116 SCREEN C
PAGE 386
definition of, 20 error handling, 44 error list tokens, 171 event templates, 174 header tokens, 168 manager token, 168 naming convention, 46 nested message token, 169 object names, 55, 59 overview, 20 processes, specifying maximum, 79 programming elements, 31, 38 receiving and decoding responses, 44 retrieving and decoding events, 173, 174 security, 45 See also ZMAXSPI field, 23 standard definitions, 50, 52 writing C programs, 48 Subtype 30 processes, 173 Swap file See ZGUARDIANSWAP field, 23 SWITCH PM comm
PAGE 387
ZPWY-MAP-DEF-SC, 84 ZPWY-MAP-DEF-SCPROCESS, 93 ZBACKUPCPU field ZPWY-MAP-DEF-PATHWAY, 78 ZPWY-MAP-PAR-CONTROL-PM, 95 ZBLOCKSIZE field, 92 ZCOLDSTARTTIME field, 77 ZCOOLSTARTTIME field, 77 ZCPUINFO field, 83 ZCPUPAIR field ZPWY-MAP-DEF-SC, 83 ZPWY-MAP-DEF-SCPROCESS, 93 ZCPUPAIRCOUNT field, 83 ZCPUWTINFO field, 90 ZCREATEDELAY field ZPWY-DDL-DEF-SC, 133 ZPWY-MAP-DEF-SC, 84 ZCUR- fields, list of, 82 ZDEBUG fieldC, 85 ZDEFAULTVOLUME field, 89 ZDEFINE field, 57 ZDELETEDELAY field ZPWY-DDL-DEF-SC, 133 ZPWY-MAP-DE
PAGE 388
ZMAXSERVERCLASSES field, 79 ZMAXSERVERPROCESSES field, 79 ZMAXSERVERS field, 87 ZMAXSIZE field, 105 ZMAXSPI field, 27, 79 ZMAXSTARTUPS field, 80 ZMAXTCPS field, 80 ZMAXTELLQUEUE field, 80 ZMAXTELLS field, 80 ZMAXTERMS field, 80 ZMAXTMFRESTARTS field, 80 ZMAXWAITS field, 105 ZMEASCOUNT field, 107 ZMEASCOUNTACTIVE field, 107 ZMINRESP field, 107 ZMINTIME field, 107 ZMODE field, 98 ZNODEINDEPENDENT field, 81 ZNODEINDEPENDENTFORMAT field, 97 ZNUMBER field, 56 ZNUMSTATIC field, 87 ZOUT field, 88 ZOWNER field ZPWY
PAGE 389
BUFAIL, 251 CHECKCLOSE, 246 CHECKOPEN, 246 CHECKPOINT, 245 CLASSNOTDEFINED, 248 CONFIGDONE, 226 CONFIGNOTDONE, 227 CPTABLEFULL, 257 DUMPNOTTAKEN, 258 DUPNAME, 227 EMPTYENTRY, 227 EMSADDSUBJECT, 260 EMSADDTOKENS, 260 EMSBADDEVICETYPE, 260 EMSDISABLED, 259 EMSINIT, 260 ENTRYLOCKED, 228 ENTRYTYPEMISMATCH, 228 EOF, 44 FNS, 256 FREEZEINPROGRESS, 241 FREEZEPENDING, 241 FSERROR, 237 IN-SHUTDOWN, 261 INTERNAL, 232 INTERNALFATAL, 246 INVALIDHOMETERM, 250 LINEDOWN, 248 LOG1IO, 230 LOG2IO, 231 MAXWAITEDRUNPROGS, 261 M
PAGE 390
SSINIT, 310 SSNULL, 310 SSPUT, 309 TOOMANYDEFSERVERS, 308 WRONGSUBSYS, 311 WRONGTOKEN, 306 ZPWY-ERR-TCP- errors BADPMTCPMSG, 303 BADSCSTATE, 302 BADSYNCID, 303 PMTCPFNS, 304 SCNOTDEFINED, 302 SCPROCESSIO, 302 SCPROCESSOPEN, 302 SPUNKNOWN, 304 ZPWY-EVT-PM- events ABORTEDSTATUS, 178 ALLOCATESEGMENT, 213 AUTOABORTEDSTATUS, 211 AUTOSTARTEDSTATUS, 211 BACKUPISUP, 216 BADENTRYID, 202 BADFILENAME, 186 BADMSG, 188 BUCPUDOWN, 209 BUCREATEFAIL, 204 BUFAIL, 209 BUSTOPPED, 212 BUTAKEOVER, 206 CHECKCLOSE, 205 CHECKOPEN,
PAGE 391
STATS-SCLM, 99 STATUS-SC, 100 ZPWY-MAP-QUAL- object qualifier tokens category description, 75 SC, 100 ZPWY-MAP-SEL- selection tokens category description, 75 LM, 100 PMREQUESTER, 101 SC, 101 SCASSIGN, 101 SCDEFINE, 102 SCLM, 102 SCPARAM, 102 SCPROCESS, 103 SCSTARTUP, 103 ZPWY-MAP-SRVFORSP statistics token field descriptions, 103 ZPWY-MAP-STATS-SC statistics token category description, 75 field descriptions, 104, 107 ZPWY-MAP-STATUS- status tokens category description, 75 LM, 108 PATHWAY, 108, 111 PM, 111, 1
PAGE 392
BUFSIZE, 67 C, 69 CLOSED, 112 COLD, 76, 99 COOL, 76, 99 DISABLE, 70 ERROREVENT, 168 EXTTCP, 113 FROZEN, 100, 114 FROZENPENDING, 100 G, 69 GUARDIAN, 69, 90, 100 IMMEDIATE, 98 INPUT, 92 IO, 92 IODONE, 113 LINKMON, 113 LOCK, 113 LOCKQUEUE, 113 LOG, 113 LOGQUEUE, 113 LOGREQUEST, 113 MANUAL, 70 N, 69 NEWPROCESS, 113 NODEINDOWNERSYS, 65 NONSTOPTSMP, 266 O, 69 OK, 163, 176 OPEN, 112 ORDERLY, 98 OSS, 69, 90, 100 OSSGUARDIAN, 69, 100 OUTPUT, 92 PATHCOM, 113 PATHWAYTS, 266 PENDING, 68, 100, 114, 115 predefined values
PAGE 393
MANAGER, 166, 168 MAXRESP, 39 OBJECT-TYPE, 51 RESPONSE-TYPE not supported, 44 RETCODE, 44 SERVER-BANNER, 51 SERVER-VERSION, 51 simple, list of, 50 special, list of, 51 SSID, 52 USEDLEN token, 165 ZSPI-TKN-ERRLIST nested message token, 169 ZSPI-TYP-xxx token types, list of, 51 ZSPI-VAL-xxx values, list of, 51 ZSPIDDL file, 50 ZSPIDEF.