NonStop Pathway/iTS Management Programming Manual Abstract This manual describes the Subsystem Programmatic Interface (SPI) interface to Pathway/iTS product; it is intended for programmers writing applications that manage Pathway/iTS. It describes the SPI commands and messages for Pathway/iTS objects—those related to terminal control processes (TCPs), terminals, and intelligent devices. Product Version Pathway/iTS 1.0 Supported Release Version Updates (RVUs) This publication supports D42.
Document History Part Number Product Version Published 120042 Pathway/TS D42 August 1996 426749-001 Pathway/iTS 1.0 October 2000 426749-002 Pathway/iTS 1.
NonStop Pathway/iTS Management Programming Manual Index Examples What’s New in This Manual ix Manual Information ix New and Changed Information About This Manual xi Who Should Read This Manual Related Documentation xii Notation Conventions xiii Figures Tables ix xi 1. Introduction Which Sections Do You Need? 1-1 Architecture and Components 1-2 Distributed Systems Management 1-4 Management Interfaces 1-5 PATHCOM Interface 1-6 SPI Interface 1-6 2.
Contents 3. SPI Programming Considerations (continued) 3.
4. SPI and EMS Standard Definitions Contents 4. SPI and EMS Standard Definitions SPI Standard Definitions 4-1 EMS Standard Definitions 4-1 5.
5. ZPWY-DDL- Definitions (continued) Contents 5.
6. ZPWY-MAP- Definitions (continued) Contents 6.
7. Terminal Control Process (TCP) Commands (continued) Contents 7. Terminal Control Process (TCP) Commands (continued) STATS TCP 7-19 STATS TCPSC 7-21 STATUS TCP 7-23 STATUS TCPLINK 7-25 STOP TCP 7-27 SWITCH TCP 7-29 8.
. PROG Commands (continued) Contents 9. PROG Commands (continued) INFO PROG 9-13 INFO PROGTERM 9-15 START PROG 9-17 10. Tell Message Commands ADD TELL 10-1 DELETE TELL 10-3 INFO TELL 10-4 START TELL 10-5 TELL TERM 10-6 TELL TCPTERM 10-7 11.
14. Error Handling Example Program Contents 14. Error Handling Example Program Index Examples Example 3-1. Example 13-1. Example 13-2. Example 14-1. Format for 32-Byte File Names 3-25 Pathway/iTS Configuration Program 13-2 Obtaining PROG Information 13-15 Handling Errors 14-2 Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 2-1.
What’s New in This Manual Manual Information NonStop Pathway/iTS Management Programming Manual Abstract This manual describes the Subsystem Programmatic Interface (SPI) interface to Pathway/iTS product; it is intended for programmers writing applications that manage Pathway/iTS. It describes the SPI commands and messages for Pathway/iTS objects—those related to terminal control processes (TCPs), terminals, and intelligent devices. Product Version Pathway/iTS 1.
What’s New in This Manual Product Changes Product Changes This manual edition documents the following changes in the Pathway/iTS management programming interface: • • • • A new gateway program has been provided to support web clients.
About This Manual This is a reference manual for the token-oriented management programming interface to Pathway/iTS, which, together with TS/MP, is called the Pathway subsystem in HP Distributed Systems Management (DSM) terminology. It describes Subsystem Programmatic Interface (SPI) commands used to configure and control Pathway/iTS objects in a PATHMON environment and to monitor the status and performance of those objects.
Related Documentation About This Manual Related Documentation In addition to this manual, information about Pathway/iTS appears in the following publications: Pathway SCREEN COBOL Reference Manual Describes the SCREEN COBOL programming language which is used for writing programs that define and control terminal displays or intelligent devices for online transaction processing applications running in a PATHMON environment.
Notation Conventions About This Manual For information about other HP products associated with Pathway/iTS management programming, see the following publications: SPI Programming Manual Describes the Subsystem Programmatic Interface (SPI), which is used for writing applications that manage HP subsystems for NonStop systems. SPI provides a set of procedure calls and a set of definition files to be used in management programs.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may 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.
Notation for Messages About This Manual … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
Notation for Management Programming Interfaces About This Manual lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
About This Manual Change Bar Notation NonStop Pathway/iTS Management Programming Manual—426749-002 xviii
1 Introduction This manual describes the management programming interface to the PATHMON environment provided by Pathway/iTS. It describes how to use programmatic commands in a management application to configure Pathway/iTS objects that support transaction-processing requesters, how to monitor the status and performance of these objects, and how to handle error and event messages returned by the Pathway subsystem. Note.
Architecture and Components Introduction TS/MP is described in a separate manual set. For more information about that product, see the TS/MP Management Programming Manual. 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.
Architecture and Components Introduction Figure 1-1 shows a simple TS/MP application that uses Pathway/iTS. This example shows the TCP and the PATHMON process managing communications between requesters and servers in the Guardian operating environment. Figure 1-1.
Distributed Systems Management Introduction Distributed Systems Management Distributed Systems Management (DSM) is a group of software tools that enables you to construct an integrated view of a system or network. DSM tools allow you to: • • • • • • Manage your system from a single control point. Distribute control of transaction processing among systems.
Management Interfaces Introduction • The Distributed Name Service (DNS)—a subsystem that manages a distributed database of names for network objects, facts about object relationships, and instructions for replicating name definitions on remote nodes. Figure 1-2 illustrates a Pathway subsystem that uses the SPI and EMS procedures for subsystem control and event management. Figure 1-2.
PATHCOM Interface Introduction Figure 1-3. Pathway/iTS Management Interfaces Management Interfaces Devices Management Application Process PATHMON Process PATHCOM Command Terminal VST004.vsd PATHCOM Interface PATHCOM is a command language interpreter and interactive command interface to the PATHMON process, the central control process for your Pathway subsystem. By using PATHCOM, which consists of sets of object-related commands, you can interactively define and manage all PATHMON-controlled objects.
SPI Interface Introduction Figure 1-4 shows the management programming environment. Figure 1-4. Management Programming Environment Management Programming Interface Operations Environment Commands, Inquiries NonStop TS/MP Environment SPI Pathway Subsystem Management Application EMS Responses, Messages TMF Subsystem VST005.
SPI Interface Introduction NonStop Pathway/iTS Management Programming Manual—426749-002 1 -8
2 Pathway/iTS Management Programming This section summarizes the SPI interface to the Pathway subsystem and the commands and object types defined for the subsystem. Comparison of PATHCOM and SPI Commands Like PATHCOM, the SPI management programming interface to the Pathway subsystem uses commands that operate on objects. A combination of a command and an object type determines what action the PATHMON process should take, as well as what additional information you must specify.
Pathway/iTS Management Programming Comparison of PATHCOM and SPI Commands Some PATHCOM functions are implemented with a new or different command name. For example, the PRIMARY TCP command is no longer a separate command, but instead is implemented as part of the SWITCH TCP command. Table 2-1 compares the PATHCOM commands with the equivalent SPI command for the objects supported by Pathway/iTS. All SPI commands begin with the prefix ZPWYCMD-, and all SPI object types begin with the prefix ZPWY-OBJ-.
Pathway/iTS Management Programming Comparison of PATHCOM and SPI Commands Table 2-1.
Pathway/iTS Management Programming Pathway Management Programming Interface Table 2-1.
Pathway/iTS Management Programming Control and Inquiry Control and Inquiry To communicate with the PATHMON process through the Pathway management programming interface, a management application must follow these steps: 1. Start a PATHMON process if one is not already running. 2. Open the PATHMON process. 3. Build a message to send to PATHMON. 4. Send the message to PATHMON. 5. Receive a response from PATHMON. 6. Decode the response. 7. Handle errors. 8. Take any appropriate actions. 9. Close PATHMON.
Sending Commands and Receiving Replies Pathway/iTS Management Programming Figure 2-1. Sending Commands and Receiving Responses Message Buffer SSINIT START PATHWAY DEF PATHWAY Management Application WRITEREAD SSPUT PATHMON SSGET RESPONSE PATHMON Config File VST006.vsd For more information about how to build command messages and decode responses, see Section 3, SPI Programming Considerations.
3 SPI Programming Considerations After your subsystem and EMS processes are running and your management application has established communication with the Pathway subsystem, the main business of your management application is to format and send commands, decode responses and act on the results, and interpret event messages and act on their information. This section provides summary information about SPI programming and discusses SPI programming considerations specific to the Pathway subsystem.
SPI Programming Considerations Naming Conventions SPI and EMS) also provide definition files. Each software component includes definition files for the TAL, COBOL, TACL, C, PASCAL, and DDL languages. To use the data declarations defined by a particular NonStop software component, your application must incorporate the appropriate programming-language definition file associated with that software component.
SPI Programming Considerations • • • • • • • • • Location Token numbers, which uniquely identify each token Token codes, used in defining simple tokens Predefined values Token maps, used to reference extensible structured tokens Error numbers Subsystem ID definition Message buffer declaration Event tokens Building blocks, which are definitions that appear at the beginning of a definition file and are referenced by TYPE clauses that appear later in the file.
Message Elements for the Pathway Subsystem SPI Programming Considerations you were writing the COBOL management application mentioned previously and also wanted to manage a TMF subsystem, you would need the following additional definition file: ZSPIDEF.ZTMFCOB For information about the SPI, EMS, extended SPI definitions, operating system, and file-system definitions, see the SPI Programming Manual, the EMS Manual, and the Guardian Procedure Errors and Messages Manual, respectively.
Commands SPI Programming Considerations Table 3-1.
Object Types SPI Programming Considerations Table 3-2.
Object Types SPI Programming Considerations Table 3-3. Pathway/iTS Object Types (page 2 of 2) Object Type Description ZPWY-OBJ-TERM TERM objects represent tasks that control I/O devices such as terminals or workstations, or that control processes that enable users to interoperate with a transaction-processing application. Each task runs as a thread in the TCP; the TCP can handle many such threads concurrently. There are two types: configured TERM objects and temporary TERM objects.
Object Names SPI Programming Considerations Table 3-4.
SPI Programming Considerations Event Numbers Event Numbers All event messages contain a header token identifying the event by number. This event number, in combination with the subsystem ID header token, uniquely identifies the kind of event being reported. Event numbers for event messages defined by the Pathway subsystem are identified by symbolic names of the form ZPWY-EVT-name, where name gives a brief description of the event being reported.
Extensible Structured Tokens SPI Programming Considerations Extensible Structured Tokens The following is a sample DDL definition for an extensible structured token that defines the attributes for a program. The TAL, COBOL, TACL, PASCAL, and C code generated follows the DDL definition. Note. The TAL, COBOL, TACL, and C codes redefine each character field (Z^C and Z-C in the examples) as an integer array and as an array of individual bytes to accommodate certain HP NonStop operating system procedures.
SPI Programming Considerations Extensible Structured Tokens Corresponding TAL structure for ZPWY-DDL-DEF-PROG: STRUCT ZPWY^DDL^DEF^PROG^DEF (*); BEGIN INT ZERRORABORT; STRUCT ZOWNER; BEGIN INT ZSYSTEMNUMBER; INT ZGROUPNUMBER; INT ZUSERNUMBER; END; STRUCT ZPRINTERINFO; BEGIN INT ZISATTACHED; STRUCT ZPRINTERFILE; BEGIN STRUCT Z^SYSNAME; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; END; STRUCT Z^LOCALNAME; BEGIN STRUCT Z^DISC; BEGIN STRUCT Z^VOLUME; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; END; STR
SPI Programming Considerations Extensible Structured Tokens TAL structure for ZPWY-DDL-DEF-PROG (continued): STRUCT Z^PID; BEGIN STRING Z^CPU; STRING Z^PIN; END; INT Z^CPUPIN = Z^PID; END; STRUCT Z^QUAL1; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; END; STRUCT Z^QUAL2; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; END; END; STRUCT Z^DEVICE = Z^DISC; BEGIN STRUCT Z^DEVNAME; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; END; STRUCT Z^SUBDEVNAME; BEGIN STRUCT Z^C; BEGIN STRING BYTE [0:7]; END; END; S
SPI Programming Considerations Extensible Structured Tokens Corresponding COBOL level-01 variable for ZPWY-DDL-DEF-PROG: 01 ZPWY-DDL-DEF-PROG. 02 ZERRORABORT PIC X(2). 02 ZOWNER. 03 ZSYSTEMNUMBER NATIVE-2. 03 ZGROUPNUMBER NATIVE-2. 03 ZUSERNUMBER NATIVE-2. 02 ZPRINTERINFO. 03 ZISATTACHED PIC X(2). 03 ZPRINTERFILE. 04 Z-SYSNAME. 05 Z-C PIC X(8). 04 Z-LOCALNAME. 05 Z-DISC. 06 Z-VOLUME. 07 Z-C PIC X(8). 06 Z-SUBVOLUME. 07 Z-C PIC X(8). 06 Z-FILENAME. 07 Z-C PIC X(8). 05 Z-PROCESS REDEFINES Z-DISC.
SPI Programming Considerations Extensible Structured Tokens Corresponding TACL structure variable for ZPWY-DDL-DEF-PROG: ZPWY^DDL^DEF^PROG Struct Begin BOOL ZERRORABORT; STRUCT ZOWNER; Begin INT ZSYSTEMNUMBER; INT ZGROUPNUMBER; INT ZUSERNUMBER; End; STRUCT ZPRINTERINFO; Begin BOOL ZISATTACHED; FNAME32 ZPRINTERFILE; End; ENUM ZSECURITY; STRUCT ZTCP; Begin STRUCT Z^C; BEGIN CHAR BYTE(0:14); END; End; FILLER 1; BOOL ZTMF; End; Corresponding C pragma for ZPWY-DDL-DEF-PROG: #pragma fieldalign matched2 __zpwy_d
SPI Programming Considerations Extensible Structured Tokens C pragma for ZPWY-DDL-DEF-PROG (continued): } u_z_c; } z_sysname; struct { union { struct { struct { union { char struct { short } z_s; char } u_z_c; } z_volume; struct { union { char struct { short } z_s; char } u_z_c; } z_subvolume; struct { union { char struct { short } z_s; char } u_z_c; } z_filename; } z_disc; struct { struct { union { z_c[8]; z_i[4]; z_b[8]; NonStop Pathway/iTS Management Programming Manual—426749-002 3- 15 z_c[8]; z_i[4
Extensible Structured Tokens SPI Programming Considerations C pragma for ZPWY-DDL-DEF-PROG (continued): struct { union { char struct { short } z_s; char } u_z_c; } z_procname; short } u_z_procname; union { struct { char char } z_pid; unsigned short } u_z_pid; } z_crtpid; struct { union { char struct { short } z_s; char } u_z_c; } z_qual1; struct { union { char struct { short } z_s; char } u_z_c; } z_qual2; } z_process; struct { NonStop Pathway/iTS Management Programming Manual—426749-002 3- 16 z_c[6]; z
Types for Fields in Structured Tokens SPI Programming Considerations C pragma for ZPWY-DDL-DEF-PROG (continued): struct { union { char struct { short } z_s; char } u_z_c; } z_devname; struct { union { char struct { short } z_s; char } u_z_c; } z_subdevname; char } z_device; } u_z_disc; } z_localname; } zprinterfile; } zprinterinfo; short struct { union { char struct { short char } z_s; char } u_z_c; } ztcp; char short } zpwy_ddl_def_prog_def; z_c[8]; z_i[4]; z_b[8]; z_c[8]; z_i[4]; z_b[8]; z_filler[8];
Data Lists and Error Lists SPI Programming Considerations For example, the command-modifier token ZPWY-DDL-PAR-CONTROL-TCP has the following DDL definition: def ZPWY-DDL-PAR-CONTROL-TCP. 02 ZBACKUPCPU token-type 02 ZDUMPINFO. 03 ZDUMP token-type 03 ZDUMPFILE token-type 02 ZSTATS token-type end. ZPWY-DDL-CPU. ZPWY-DDL-ON-OFF. ZSPI-DDL-FNAME32. ZPWY-DDL-ON-OFF. Within ZPWY-DDL-PAR-CONTROL-TCP, the ZBACKUPCPU field has the type ZPWY-DDL-CPU.
SPI Programming Considerations Building and Sending a Command Message subsystems if you include the ZSPI-TKN-MAXRESP token with a value not equal to zero. Building and Sending a Command Message The following subsections summarize the steps your application must take to create and send SPI commands. These summaries are followed by subsystem-specific programming considerations for the Pathway subsystem. For more information on creating and sending SPI commands and responses, see the SPI Programming Manual.
Considerations for SSINIT SPI Programming Considerations Considerations for SSINIT When setting up a call to SSINIT, you need to consider the following information. Using ZSPI-TKN-MAXRESP ZSPI-TKN-MAXRESP is used by some subsystems to enable multiple responses in a single response buffer.
SPI Programming Considerations Considerations for SSPUT Considerations for SSPUT The Pathway subsystem does not support multiple commands in the same message, or arrays or multiple occurrences of the same token. Considerations for SSNULL and Extensible Structured Tokens Your program should always call SSNULL to initialize an extensible structured token before assigning values to fields in that token, even if you assign a value to each field and even if the extensible structured token has only one field.
Specifying Continuation SPI Programming Considerations 2. Initialize the ZNAME field in the ZPWY-DDL-SEL-objecttype token by assigning a value in the form ZPWY-VAL-ALLobjecttype to the field. The values are described under Values for Specifying Continuation on page 3-22. Note. When the value you assign to the name field is longer than the name field itself, do not move the entire literal to the name field. Instead, move only what is needed of the literal. 3.
Required Object States for Continuation SPI Programming Considerations Required Object States for Continuation For each type of command, continuation only acts on objects in a specific state. If an object is not in the required state, responses might not be returned for all objects or subobjects requested. Table 3-5 indicates the required state for each Pathway subsystem command that supports continuation and each object type applicable to that command. Table 3-5.
Continuation Example SPI Programming Considerations Table 3-5.
32-Byte File Names SPI Programming Considerations The Application… The PATHMON Process… 10. Reissues the INFO TERM command with the special selector and adds the context token from the previous response to the message. 11. Returns an empty response buffer (the context token is absent) and the error value ZPWY-ERR-PMNODATA. 12. Interprets that there are no more TERM objects about which to obtain information.
Resetting Values in Fields SPI Programming Considerations • • • • FNAME32COLLAPSE, similar to the system procedure FNAMECOLLAPSE, converts 32-byte file names to external format. FNAME32EXPAND, like the system procedure FNAMEEXPAND, converts file names in external format to 32-byte internal format. FNAME32TOFNAME converts a file name from 32-byte format to Guardian internal format, if possible. FNAMETOFNAME32 converts a file name from Guardian internal format to 32-byte format, if possible.
SPI Programming Considerations Receiving and Decoding Response Messages Receiving and Decoding Response Messages The following subsections summarize the steps your application must take to receive and decode SPI command responses. These summaries are followed by subsystemspecific programming considerations for the Pathway subsystem. For more information on receiving and decoding SPI commands and responses, see the SPI Programming Manual.
Event and Error Handling SPI Programming Considerations structured token, you must first obtain the entire structured token by using SSGET. Then refer to the fields of the structure by using the defined field names. The PATHMON process does not provide support for selecting the types of responses to be returned with the SPI standard token ZSPI-TKN-RESPONSE-TYPE. The Pathway subsystem always returns a response for every object—whether or not errors or warnings occur for the object.
Event-Specific Tokens SPI Programming Considerations Table 3-7. Event Message Subject Tokens Token Description ZPWY-TKN-TELLNAME Event concerns a tell message. ZPWY-TKN-TERMNAME Event concerns a terminal (TERM object). ZPWY-TKN-UNKNOWNNAME The subject of the event is unknown to PATHMON. The subject token indicated by ZEMS-TKN-SUBJECT-MARK contains the name of the specific object involved in the event.
Message Numbers SPI Programming Considerations Scenario Your management application issues the START TCP command for TCP-A, but the buffer is corrupted. The response message contains the following: 1. The message header, including the command (ZPWY-CMD-START), the object type (ZPWY-OBJ-TCP), the version of the PATHMON process, and the subsystem ID 2. ZSPI-TKN-RETCODE, containing the value ZPWY-ERR-SPI-INVALIDBUFFER 3. ZSPI-TKN-ERRLIST 4.
Security SPI Programming Considerations Security The owner of the user ID that starts the PATHMON process can set the ZOWNER and ZSECURITY fields in ZPWY-DDL-DEF-PATHWAY during the execution of a START PATHWAY command to restrict the use of a specific group of commands. Commands included in this restricted group are those that can directly alter the state of an object. Table 3-9 lists the restricted commands and their object types. Table 3-9.
SPI Programming Considerations Programming Considerations for Specific Object Types Programming Considerations for Specific Object Types The following paragraphs discuss special programming considerations for each Pathway/iTS object type. TCP Objects When developing a management application that defines and controls TCPs, consider the following: • To perform the equivalent of the PATHCOM STATS TCP, DETAIL command, follow these steps: 1.
SPI Programming Considerations TERM Objects 1. Issue the STATUS TCP command, initializing the ZTCP field in ZPWY-DDL-SEL-TCP to the TCP name. 2. Issue the STATUS TCPTERM command, initializing the ZTCP field in ZPWY-DDL-SEL-TCPTERM to the TCP name and initializing the ZTERM field to ZPWY-VAL-ALLTERM. 3. Reissue the STATUS TCPTERM command continually, using the context token returned by PATHMON, until no data is returned in the reply buffer.
SPI Programming Considerations Writing C Programs 2. Call SSNULL to initialize the fields in ZPWY-MAP-DEF-TELL with null values. 3. Assign “HELLO” to the ZAREA field in ZPWY-MAP-DEF-TELL and a value of 5 (the number of characters in HELLO) to the ZLENGTH field. Call SSPUT. 4. Send the buffer and ZPWY-VAL-BUFLEN to PATHMON, using a mechanism appropriate to the language you are using. 2. Queue the tell message for the TERM objects: 1. Call SSGET with ZPWY-MAP-TELLNUM.
SPI Programming Considerations Command Presentation Generating The ZPWYC Include File Under certain conditions, the DDL compiler introduces an extra level in the structure definitions in the ZPWYC file. If any C compiler errors indicate a problem with the structure fields, make sure the structure definition in the ZPWYC file matches the structure used in the program.
Unlisted Tokens SPI Programming Considerations The notation used for simple tokens in the syntax box is an abbreviated version of the essential information given in the DDL TOKEN-CODE statement. You define extensible structured tokens by using DDL DEFINITION statements. The order of the tokens in the syntax box is not necessarily the order in which they must occur in a command or response buffer—except for the ZSPI-TKN-ENDLIST token.
SPI Programming Considerations Required Tokens and Fields value other than its null value; a token that is present but has no assigned value is interpreted as having a value of all blanks.
SPI Programming Considerations Required Tokens and Fields NonStop Pathway/iTS Management Programming Manual—426749-002 3- 38
4 SPI and EMS Standard Definitions 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. For an explanation of DDL, see the Data Definition Language (DDL) Reference Manual.
SPI and EMS Standard Definitions EMS Standard Definitions NonStop Pathway/iTS Management Programming Manual—426749-002 4 -2
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 NonStop 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.
Pathway Subsystem Definitions ZPWY-DDL- Definitions Table 5-3.
Buffer Declarations ZPWY-DDL- Definitions Buffer Declarations Pathway/iTS provides the following buffer declarations for message buffers you can use with the SPI procedures. ZPWY-DDL-MSG-BUFFER is a message buffer of the appropriate size for use with most SPI procedures. def ZPWY-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER token-type token-type token-type token-type occurs ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-CHAR. 0 to ZPWY-VAL-BUFLEN times depending on Z-OCCURS.
Token Codes for Object Names ZPWY-DDL- Definitions The DDL definitions for object names are also used to define the error tokens ZPWY-TKN-REQobjecttypeNAME and ZPWY-TKN-objecttypeNAME and the subject tokens for event messages. Token Codes for Object Names The DDL definitions for object names describe token types that have the prefix ZPWY-TYP-. The token types are used to build token codes, which have the prefix ZPWY-TKN-.
ZPWY-DDL-SCOBOL-PUNAME ZPWY-DDL- Definitions ZPWY-DDL-SCOBOL-PUNAME ZPWY-DDL-SCOBOL-PUNAME identifies a SCREEN COBOL program unit. This name is the program name specified in the PROGRAM-ID sentence of the identification division in a SCREEN COBOL program. def ZPWY-DDL-SCOBOL-PUNAME token-typ ZPWY-DDL-CHAR30. ZPWY-DDL-SCTCPNAME ZPWY-DDL-SCTCPNAME specifies the name of a server class and the name of a TCP that is linked to that server class. def ZPWY-DDL-SCTCPNAME.
ZPWY-DDL-TCPLINKNAME ZPWY-DDL- Definitions ZPWY-DDL-TCPLINKNAME ZPWY-DDL-TCPLINKNAME specifies a link between a TCP and a specific server process in a server class. def ZPWY-DDL-TCPLINKNAME. 02 ZSERVERCLASS 02 FILLER 02 ZPROCESS 02 ZTCP 02 FILLER-1 end. token-type token-type token-type token-type token-type ZPWY-DDL-OBJECT-NAME. ZPWY-DDL-FILLER. ZSPI-DDL-CHAR6. ZPWY-DDL-OBJECT-NAME. ZPWY-DDL-FILLER. ZSERVERCLASS is the name of the server class.
ZPWY-DDL-TCPTERMNAME ZPWY-DDL- Definitions ZTCP is the name of the TCP. ZSERVERCLASS is the name of the server class. ZPWY-DDL-TCPTERMNAME ZPWY-DDL-TCPTERMNAME identifies a terminal associated with a specific TCP. def ZPWY-DDL-TCPTERMNAME. 02 ZTCP 02 FILLER 02 ZTERM 02 FILLER-1 end. token-type token-type token-type token-type ZPWY-DDL-OBJECT-NAME. ZPWY-DDL-FILLER. ZPWY-DDL-OBJECT-NAME. ZPWY-DDL-FILLER. ZTERM is the name of a TERM object.
ZPWY-DDL-UNKNOWNNAME ZPWY-DDL- Definitions ZTERM is the name of the specific TERM object. ZPWY-DDL-UNKNOWNNAME ZPWY-DDL-UNKNOWNNAME is used in event management to identify the name of the subject when the object type (for example, TCP or TERM) is unknown. It is also used for internal errors when the type of the subject is not known. def ZPWY-DDL-UNKNOWNNAME. 02 UNKNOWN 02 FILLER-1 end. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER.
ZPWY-DDL-CHAR30 ZPWY-DDL- Definitions ZPWY-DDL-CHAR30 ZPWY-DDL-CHAR30 designates 30 ASCII characters, addressable as a STRUCT, as bytes or as integers. def ZPWY-DDL-CHAR30. 02 Z-C 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C end. PIC X(30). type BINARY 16 occurs 15 times. PIC X occurs 30 times. 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 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C end.
ZPWY-DDL-DUMP-INFO ZPWY-DDL- Definitions ZDUMP enables or disables memory dumping. The following values are valid: ZPWY-VAL-OFF Directs the TCP not to write data stack information to a file when it encounters an internal or fatal error. This is the default value. ZPWY-VAL-ON Directs the TCP to create one or more disk files and write the contents of its data stack and its extended data segment to these files.
ZPWY-DDL-ERRINFO2 ZPWY-DDL- Definitions ZPWY-DDL-ERRINFO2 ZPWY-DDL-ERRINFO2 provides process-creation error information in a two-word format. def ZPWY-DDL-ERRINFO2. 02 ZERROR2 02 ZINFO2 02 ZDETAIL2 end. token-type ZPWY-DDL-INT. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT. ZERROR2 contains a Pathway subsystem error number. The error numbers are described by symbolic names in the Pathway/iTS System Management Manual.
ZPWY-DDL-ERROR-INFO ZPWY-DDL- Definitions ZERROR2 ZINFO2 ZDETAIL2 1038 1 11 ZPWY-DDL-ERROR-INFO ZPWY-DDL-ERROR-INFO provides error information. def ZPWY-DDL-ERROR-INFO. 02 ZERROR 02 ZINFO end. token-type ZPWY-DDL-INT. token-type ZSPI-DDL-INT. ZERROR contains a Pathway environment error number. The error numbers are described by symbolic names in the NonStop Pathway/iTS Management Reference Manual. ZINFO contains the number of a second error that provides further information about ZERROR.
ZPWY-DDL-IO-PROTOCOL ZPWY-DDL- Definitions ZINSPECT specifies whether a SCREEN COBOL program running on a TERM object starts the Inspect process when the program begins execution. The following values are valid: ZPWY-VAL-OFF The Inspect process is not started when the program begins. ZPWY-VAL-ON The Inspect process is started when the program begins. The program is positioned at a breakpoint before the first instruction executes. If you do not assign a value to this field, the default is ZPWY-VAL-OFF.
ZPWY-DDL-ON-OFF ZPWY-DDL- Definitions 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 values are supported in COBOL.
ZPWY-DDL-PRINTER-INFO ZPWY-DDL- Definitions ZSYSTEMNUMBER is a number from 0 through 255 that uniquely identifies a system. To find your system number, call the MYSYSTEMNUMBER procedure as described in the Guardian Procedure Calls Reference Manual. You need not specify a system number if the system associated with the user ID is the same as the system in which your management application is running. To specify node-independence, set this field to ZPWY-VAL-NODEINDOWNERSYS.
ZPWY-DDL-TERM-TYPE ZPWY-DDL- Definitions ZISATTACHED directs the copy of the screen image to the attached printer. The field has the following associations: T16-6530 Directs copy to a printer attached directly to the terminal. T16-6520 Directs copy to a printer attached directly to the terminal. IBM-3270 Directs copy to the printer, which must be attached to the same control unit as the terminal.
ZPWY-DDL-TERMTYPE-INFO ZPWY-DDL- Definitions T16-6540 6540 terminal emulating a 6530 terminal INTELLIGENT Intelligent device T16-6530WP 6530WP terminal When specifying a device type, consider the following: • • • • • If a program is running on an incompatible device type, the results can be unpredictable, depending on the device type. For example, the results are unpredictable when a SCREEN COBOL program compiled for an IBM 3270 terminal is executed on a 6530 terminal.
ZPWY-DDL- Definitions ZPWY-DDL-TERMTYPE-INFO ZTERMTYPE specifies the type of device on which the TERM runs or selects from the PROG definition the type of device on which the program runs. The ZTERMTYPE field in ZPWY-DDL-TERMTYPE-INFO has the same possible values as ZPWY-DDL-TERM-TYPE. When specifying the type of device on which a TERM runs, consider the following: • • • • • If ZTERMTYPE specifies IBM-3270 or INTELLIGENT, then you must also assign a value to the ZSUBTYPE field.
ZPWY-DDL-TERMTYPE-INFO ZPWY-DDL- Definitions • If the device type derived from the DEVICEINFO reply is not defined in the PROG definition, the START PROG command fails with the following error: *1086* TERM TYPE NOT DEFINED FOR PROGRAM To reset this field using the TACL program, you must use the #SETBYTES built-in function. For more information on this function, see the SPI Programming Manual. ZSUBTYPE contains additional information about specific device types on which TERM objects run.
ZPWY-DDL-TMF-RESTARTS ZPWY-DDL- Definitions • If a value for ZSUBTYPE is not specified in the TERMINAL IS clause of a program for an intelligent device or in ZPWY-DDL-TERMTYPE-INFO, a default value is used rather than the value obtained from the file-system DEVICEINFO call. ZPWY-DDL-TMF-RESTARTS ZPWY-DDL-TMF-RESTARTS specifies the maximum number of times a TCP can attempt to restart a logical TMF transaction after the transaction aborts and before the SEND error occurs.
ZPWY-DDL-0-4095 ZPWY-DDL- Definitions ZPWY-DDL-0-4095 ZPWY-DDL-0-4095 is a value from 0 through 4095. def ZPWY-DDL-0-4095 token-type ZSPI-DDL-INT. ZPWY-DDL-1-199 ZPWY-DDL-1-199 is a value from 1 through 199. def ZPWY-DDL-1-199 token-type ZSPI-DDL-INT. ZPWY-DDL-1-255 ZPWY-DDL-1-255 is a value from 1 through 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.
Private Field Types for Predefined Values ZPWY-DDL- Definitions ZPWY-VAL-VERSION is the product version number of the Pathway subsystem. This value is a 16-bit unsigned integer. The left byte contains the letter part of the version as an ASCII uppercase alphabetic character, and the right byte contains the numeric part of the version as an unsigned integer value; for example, D30.
ZPWY-DDL-FRZSTATETERM-VALUE ZPWY-DDL- Definitions ZPWY-DDL-FRZSTATETERM-VALUE ZPWY-DDL-FRZSTATETERM-VALUE specifies the freeze status of a TERM object preventing a server process from being frozen. def ZPWY-DDL-FRZSTATETERM-VALUE token-type ZSPI-DDL-ENUM. Values are described with ZPWY-MAP-STATUS-TERMFREEZE on page 6-79. ZPWY-DDL-NONSTOP-VALUE ZPWY-DDL-NONSTOP-VALUE designates whether the TCP runs with a backup process. def ZPWY-DDL-NONSTOP-VALUE token-type ZPWY-DDL-ENUM.
ZPWY-DDL-SECURITY-VALUE ZPWY-DDL- Definitions ZPWY-DDL-SECURITY-VALUE ZPWY-DDL-SECURITY-VALUE identifies the users who can issue commands that directly alter the state of Pathway subsystem objects. def ZPWY-DDL-SECURITY-VALUE token-type ZSPI-DDL-ENUM.
ZPWY-DDL-TERMWAIT-VALUE ZPWY-DDL- Definitions Values are described under ZPWY-MAP-STATUS-TERMDETAIL on page 6-73. ZPWY-DDL-TERMWAIT-VALUE ZPWY-DDL-TERMWAIT-VALUE specifies the reason a TERM object is waiting. def ZPWY-DDL-TERMWAIT-VALUE type ZSPI-DDL-ENUM. Values are described under ZPWY-MAP-STATUS-TERMDETAIL on page 6-73. ZPWY-DDL-TRMQUALSTATE-VALUE ZPWY-DDL-TRMQUALSTATE-VALUE specifies the state of a TERM object. def ZPWY-DDL-TRMQUALSTATE-VALUE type ZSPI-DDL-INT-PAIR.
ZPWY-DDL- Definitions NonStop Pathway/iTS Management Programming Manual—426749-002 5- 26 Simple Tokens
6 ZPWY-MAP- Definitions This section discusses extensible structured tokens used in the token-oriented management programming interface to NonStop 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. Definitions of structures use DDL definition statements.
Extensible Structured Tokens ZPWY-MAP- Definitions Table 6-1. Categories of Extensible Structured Tokens (page 2 of 2) Category Token Format Description Selector tokens ZPWY-MAP-SEL- These tokens select specific objects by name. Statistics tokens ZPWY-MAP-STATS- These tokens contain status information returned from the PATHMON process. Status tokens ZPWY-MAP-STATUS- These tokens contain statistics and performance information returned from the PATHMON process.
ZPWY-MAP-DEF-PATHWAY ZPWY-MAP- Definitions Note. For a field of an extensible structured token, the notation “!r” means that the field must have a value other than its null value. The absence of the “!r” notation means that the field might or might not have a value other than its null value. ZPWY-MAP-DEF-PATHWAY ZPWY-MAP-DEF-PATHWAY identifies an extensible structured token that defines all the attributes for the PATHMON process and for the Pathway subsystem.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PATHWAY TCPs, and LINKMON processes are allowed to concurrently hold links to a single server process. If you do not assign a value to this field, the default value is 0; any attempt by an external TCP to access a server controlled by the PATHMON process fails. ZMAXPROGRAMS is the maximum number of PROGRAM descriptions that you can add to the PATHMON configuration file. The value must be a number from 0 through 4095.
ZPWY-MAP-DEF-PATHWAY ZPWY-MAP- Definitions This field is required; there is no default. ZMAXTMFRESTARTS is the maximum number of times a TCP attempts to restart a logical TMF transaction after the transaction aborts and before the SEND error occurs. If this limit is reached and the SCREEN COBOL BEGIN-TRANSACTION verb does not have an ON ERROR clause, the terminal is suspended, but can be restarted.
ZPWY-MAP-DEF-PROG ZPWY-MAP- Definitions ZPWY-MAP-DEF-PROG ZPWY-MAP-DEF-PROG identifies an extensible structured token that defines the attributes for a Pathway subsystem PROG object (equivalent to the PROGRAM object in PATHCOM). def ZPWY-DDL-DEF-PROG. 02 ZERRORABORT 02 ZOWNER. 03 ZSYSTEMNUMBER 03 ZGROUPNUMBER 03 ZUSERNUMBER 02 ZPRINTERINFO. 03 ZISATTACHED 03 ZPRINTERFILE 02 ZSECURITY 02 ZTCP !r 02 FILLER 02 ZTMF end. token-type ZPWY-DDL-ON-OFF. token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PROG ZSECURITY specifies the users who can issue a START PROGRAM command. For the values associated with ZSECURITY, see the ZPWY-DDL-SECURITY-VALUE token in this section. This security checking controls who can start the application programs through the START PROGRAM command, but not through a CALL statement from another SCREEN COBOL program unit. If you do not assign a value to this field, the default is ZPWY-VAL-N.
ZPWY-MAP-DEF-PROGTERM ZPWY-MAP- Definitions ZPWY-MAP-DEF-PROGTERM ZPWY-MAP-DEF-PROGTERM identifies an extensible structured token that defines the attributes for a Pathway subsystem TERM object associated with a specific PROG object. def ZPWY-DDL-DEF-PROGTERM. 02 ZBREAK token-type 02 ZDISPLAYPAGES token-type 02 ZECHO token-type 02 ZEXCLUSIVE token-type 02 ZINITIAL token-type 02 ZIOPROTOCOL token-type 02 ZMAXINPUTMSGS token-type 02 ZTCLPROG token-type 02 ZTRAILINGBLANKS token-type end. ZPWY-DDL-ON-OFF.
ZPWY-MAP-DEF-PROGTERM ZPWY-MAP- Definitions ZPWY-VAL-OFF. This parameter is effective only for devices running in conversational mode. ZDISPLAYPAGES specifies the depth of the terminal’s screen caching. ZDISPLAYPAGES determines the maximum number of screen displays stored in the terminal’s memory. If you do not assign a value to this parameter, the default is used. If you specify a value greater than the defined maximum, the defined maximum is used.
ZPWY-MAP-DEF-PROGTERM ZPWY-MAP- Definitions ZECHO overrides the echo mode (that is, the mode configured for a terminal at system generation) so that character input appears correctly on the screen. This field supports terminals running in conversational or intelligent mode. ZECHO has the following values: ZPWY-VAL-OFF Corrects the display by suppressing the duplicate characters (if a terminal is configured so that it normally displays input characters).
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PROGTERM ZIOPROTOCOL specifies the protocol the TCP follows when a SCREEN COBOL SEND MESSAGE statement completes with a timeout or unsolicited message. ZIOPROTOCOL can have the following values: 0 Directs the TCP to issue a Guardian CANCEL procedure to cancel a SEND MESSAGE I/O operation. The I/O operation is cancelled because an unsolicited message arrives or a SEND MESSAGE TIMEOUT occurred.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-PROGTERM To reduce the amount of file checking, copy program units from the PROGTERM TCLPROG file to the TCP TCLPROG file. Then, either eliminate the PROGTERM TCLPROG file or copy all modules from TCP TCLPROG into PROGTERM TCLPROG. ZTRAILINGBLANKS specifies whether the TCP should suppress the display of trailing ASCII blank characters in output lines sent to terminals by the SCREEN COBOL DISPLAY and SEND MESSAGE verbs.
ZPWY-MAP-DEF-TCP ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP ZPWY-MAP-DEF-TCP identifies an extensible structured token that defines the attributes for a TCP. def ZPWY-DDL-DEF-TCP. 02 ZAUTORESTART 02 ZCHECKDIRECTORY 02 ZCODEAREALEN 02 ZCPUPAIR. 03 ZPRIMARY 03 ZBACKUP 02 ZDEBUG 02 ZDUMPINFO.
ZPWY-MAP-DEF-TCP ZPWY-MAP- Definitions The value for this field can be: 0 Specifies no automatic restarts. 1 through 32,767 Directs the PATHMON process to allow this many automatic restarts in 10 minutes. Directs the PATHMON process to allow unlimited automatic restarts.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP The value you assign for this field depends on the number and the size of the screen programs in your applications and also on the available swap space. Some guidelines for this field are: • • • Use the size of the SCREEN COBOL programs (the screen data plus the RUNUNIT SIZE listed for these programs compiled with MAP) that make up the applications for this TCP.
ZPWY-MAP-DEF-TCP ZPWY-MAP- Definitions ZDEBUG specifies whether a TCP enters debug mode on startup. ZDEBUG can have the following values: ZPWY-VAL-OFF Directs the TCP not to enter debug mode on startup. ZPWY-VAL-ON Directs the TCP to enter debug mode on startup. If the PATHMON process was started with INSPECT ON or the server program was compiled or bound with the HP Inspect symbolic debugger process defined, the servers enter Inspect mode for debugging. For more information, see the Inspect Manual.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP using the nld program development tool for combining object files. For more information, see the Pathway/iTS TCP and Terminal Programming Guide. You can specify either a specific node name or \*, a generic name representing the node on which the PATHMON process is currently running. If you do not specify a node name, the default node for file-name expansion can be affected by the value you specify for the ZNODEINDEPENDENT field of the TS/MP START PATHWAY command.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP If you do not assign a value to this field, the default is the home terminal of the PATHMON process. ZINSPECTINFO indicates whether the SCREEN COBOL programs running on the TERM objects controlled by this TCP can be examined by using the Inspect process, and specifies an Inspect command terminal. The fields are described under ZPWYDDL-INSPECT-INFO on page 5-12.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP ZMAXREPLY is the maximum number of bytes permitted for an outgoing SEND message or a server reply message. For a TCP that runs the gateway requester program to support Pathway/iTS web clients, set the value of ZMAXREPLY to 32000.
ZPWY-MAP-DEF-TCP ZPWY-MAP- Definitions If you do not assign a value to this field, the default is 8000 bytes. ZMAXTERMS is the maximum number of TERM objects that the TCP can have open at the same time. Valid values range from 0 through 4095. The TCP opens its TERM objects with a syncdepth of 1. ZNONSTOP specifies whether the TCP runs with a backup process and performs normal checkpoint operations. ZNONSTOP can have the following values: ZPWY-VAL-NONSTOP0 Directs the TCP to run without a backup process.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP maximum number of bytes that the TCP allocates for a server I/O buffer; it must be at least the size of the largest predefined server reply message. For a TCP that runs the gateway requester program to support Pathway/iTS web clients, set the value of ZSERVERPOOL to 40,000 bytes. Otherwise, the suggested range is 10,000 to 30,000 bytes. The minimum value is 32 bytes. If you do not assign a value to this field, the default is 20,000 bytes.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TCP If you specify a TCLPROG file name in either an ADD TERM or ADD PROGTERM command, the TCP first checks that file for the requested program unit before it checks the file specified in the ADD TCP command. This field is required to create a valid TCP definition; there is no default value.
ZPWY-MAP-DEF-TCP ZPWY-MAP- Definitions ZTERMPOOL is the number of bytes that the TCP allocates in its data area for all terminal I/O buffers. The value for this field is the minimum number of bytes that the TCP allocates for the pool size. ZTERMPOOL must be large enough to hold at least one copy of the largest terminal input buffer, the largest UMP message, or the value that you assign to the ZTERMBUF field.
ZPWY-MAP-DEF-TCP ZPWY-MAP- Definitions The following values are valid: ZPWY-VAL-ON Directs the TCP to recover the screen automatically, except for data and display characteristics, by first executing a DISPLAY BASE statement for the current base screen and a DISPLAY OVERLAY statement for every current overlay screen. Then, after all the current screens are displayed, the TCP checks for a user exception code declared in the USE FOR SCREEN RECOVERY clause.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TELL ZPWY-MAP-DEF-TELL ZPWY-MAP-DEF-TELL is an extensible structured token that defines the content of a tell message. def ZPWY-DDL-DEF-TELL. 02 ZTIMESTAMP 02 ZLENGTH 02 ZAREA end. token-type ZSPI-DDL-TIMESTAMP. token-type ZSPI-DDL-INT. token-type ZPWY-DDL-CHAR132. !r !r ZTIMESTAMP is a four-word Julian timestamp in Greenwich mean time (GMT) that the PATHMON process adds to the PATHCTL file upon receiving the TELL message.
ZPWY-MAP-DEF-TERM ZPWY-MAP- Definitions ZPWY-MAP-DEF-TERM ZPWY-MAP-DEF-TERM is an extensible structured token that defines the attributes for a Pathway TERM object. def ZPWY-DDL-DEF-TERM. 02 ZAUTORESTART 02 ZBREAK 02 ZDIAGNOSTIC 02 ZDISPLAYPAGES 02 ZECHO 02 ZEXCLUSIVE 02 ZFILE 02 ZINITIAL 02 ZINSPECTINFO. 03 ZINSPECT 03 ZINSPECTFILE 02 ZIOPROTOCOL 02 ZMAXINPUTMSGS 02 ZPRINTERINFO. 03 ZISATTACHED 03 ZPRINTERFILE 02 ZTCLPROG 02 ZTCP !r 02 FILLER 02 ZTMF 02 ZTERMTYPEINFO.
ZPWY-MAP-DEF-TERM ZPWY-MAP- Definitions ZAUTORESTART can have the following values: 0 Specifies no automatic restarts. 1 through 32,767 Directs the PATHMON process to allow this many automatic restarts in 10 minutes. Directs the PATHMON process to allow unlimited automatic restarts. -1 If you do not assign a value to this field, the default is 0. ZBREAK specifies whether the TCP accepts the Break key function for its devices running in conversational mode.
ZPWY-MAP-DEF-TERM ZPWY-MAP- Definitions ZDIAGNOSTIC specifies whether diagnostic screens are displayed to inform the application user when an error condition or termination occurs. ZDIAGNOSTIC can have the following values: ZPWY-VAL-OFF Specifies that the diagnostic screens should not be displayed. ZPWY-VAL-ON Specifies that the diagnostic screens should be displayed.
ZPWY-MAP-DEF-TERM ZPWY-MAP- Definitions attributes. The more memory assigned to one, the less available to the other. Therefore, if your application has many fields per screen, you should set ZDISPLAYPAGES to a small value to leave room for the field attributes. If you specify too many display pages, you might receive the terminal error ALL FIELDS USED. For more information on how to select the appropriate value for the ZDISPLAYPAGES field, see the Pathway/iTS System Management Manual.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TERM process file name to ZFILE, you must also assign a value to the ZTERMTYPE field, because ZTERMTYPE specifies the type of terminal that the process is emulating. System defaults for file-name expansion are based on the value you specify for the ZNODEINDEPENDENT field of the TS/MP START PATHWAY command.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TERM If you specify a value of 1, the front-end process must be written according to rules specified in the Pathway/iTS TCP and Terminal Programming Guide. Front-end processes can use this feature to avoid loss of data. If you do not assign a value to this field, the default is 0. ZMAXINPUTMSGS specifies the maximum number of unsolicited messages that the TCP queues for the Pathway requester associated with the terminal.
ZPWY-MAP- Definitions ZPWY-MAP-DEF-TERM ZTMF specifies whether the TMF subsystem runs with this program. For more information about this parameter, see the Pathway/iTS System Management Manual. The following values are valid: ZPWY-VAL-ON Invokes TMF auditing when necessary. The ABORTTRANSACTION, BEGIN-TRANSACTION, ENDTRANSACTION, and RESTART-TRANSACTION verbs perform the functions described in the Pathway SCREEN COBOL Reference Manual. ZPWY-VAL-OFF Prevents TMF auditing.
ZPWY-MAP-PAR-CONTROL-TCP ZPWY-MAP- Definitions ZPWY-MAP-PAR-CONTROL-TCP This token specifies whether the TCP writes its data stack information to a file on encountering an internal or fatal error, and if so, specifies the name and location of the dump file. def ZPWY-DDL-PAR-CONTROL-TCP. 02 ZBACKUPCPU token-type 02 ZDUMPINFO. 03 ZDUMP token-type 03 ZDUMPFILE token-type 02 ZUNUSED token-type 02 ZSTATS token-type end. ZPWY-DDL-CPU. ZPWY-DDL-ON-OFF. ZSPI-DDL-FNAME32. ZSPI-DDL-INT. ZPWY-DDL-ON-OFF.
ZPWY-MAP- Definitions ZPWY-MAP-PAR-CONTROL-TCP specific default value enables you to specify where the TCP creates its dump files. The file name can be as follows: [\node][.$volume].[subvolume][.ZZ ] [.filename] You can specify either a specific node name or \*, a generic name representing the node on which the PATHMON process is currently running.
ZPWY-MAP-PAR-INFO ZPWY-MAP- Definitions ZSTATS enables or disables the statistical-gathering mechanism within the TCP while the TCP is running. ZSTATS can have the following values: ZPWY-VAL-ON Enables the performance-collection mechanism. ZPWY-VAL-OFF Disables the performance-collection mechanism. ZPWY-MAP-PAR-INFO This token specifies which node names are returned in the response buffer of an INFO command. def ZPWY-DDL-PAR-INFO. 02 ZNODEINDEPENDENTFORMAT end. token type ZPWY-DDL-YES-NO.
ZPWY-MAP- Definitions ZPWY-MAP-PAR-INSPECT-TERM ZPWY-MAP-PAR-INSPECT-TERM This token specifies the file in which a SCREEN COBOL program to be debugged is running. def ZPWY-DDL-PAR-INSPECT-TERM. 02 ZFILE. token-type ZSPI-DDL-FNAME32. end. ZFILE specifies the name of the file in which the SCREEN COBOL program is running.
ZPWY-MAP- Definitions ZPWY-MAP-PAR-START-PROG ZPWY-MAP-PAR-START-PROG This token specifies startup information for a terminal or process emulating a terminal used as the I/O device for a PROG object. def ZPWY-DDL-PAR-START-PROG. 02 ZFILE. token-type ZSPI-DDL-FNAME32. !r 02 ZTERMTYPEINFO. 03 ZTERMTYPE token-type ZPWY-DDL-TERM-TYPE. 03 FILLER token-type ZPWY-DDL-FILLER. 03 ZSUBTYPE token-type ZSPI-DDL-INT. 02 ZPRINTERINFO. 03 ZISATTACHED token-type ZPWY-DDL-YES-NO.
ZPWY-MAP-PAR-START-TERM ZPWY-MAP- Definitions ZNOWAIT allows the program to execute concurrently with your Pathsend requester application program. The following values are valid: ZPWY-VAL-OFF Specifies that the PATHMON process replies to the START PROG request after the SCREEN COBOL application started by START PROG completes. This is the default value. ZPWY-VAL-ON Specifies that the PATHMON process replies after starting a TERM object based on the PROG attributes.
ZPWY-MAP- Definitions ZPWY-MAP-PAR-STATS-SCTCP If you do not assign a value to this field, the default is ZPWY-VAL-NO.
ZPWY-MAP-PAR-STATS-TCP ZPWY-MAP- Definitions ZPWY-MAP-PAR-STATS-TCP This token specifies whether the counters used for statistics measurements should be set back to zero after returning the statistics data. def ZPWY-DDL-PAR-STATS-TCP. 02 ZRESETSTATS token-type ZPWY-DDL-YES-NO. end. ZRESETSTATS indicates whether to reset the statistics counters to zero. The following values are possible: ZPWY-VAL-NO Counters are not reset to 0. ZPWY-VAL-YES Counters are reset to 0.
ZPWY-MAP-PAR-STATS-TCPTERM ZPWY-MAP- Definitions ZPWY-MAP-PAR-STATS-TCPTERM This token specifies whether the counters used for statistics measurements should be set back to zero after returning the statistics data. def ZPWY-DDL-PAR-STATS-TCPTERM. 02 ZRESETSTATS token-type ZPWY-DDL-YES-NO. end. ZRESETSTATS indicates whether to reset the statistics counters to zero. The following values are possible: ZPWY-VAL-NO Counters are not reset to 0. ZPWY-VAL-YES Counters are reset to 0.
ZPWY-MAP-PAR-SUSPEND-TERM ZPWY-MAP- Definitions ZPWY-MAP-PAR-SUSPEND-TERM this token specifies whether to disregard the SCREEN COBOL special register STOPMODE, thereby suspending execution of the SCREEN COBOL program. def ZPWY-DDL-PAR-SUSPEND-TERM. 02 ZIGNORESTOPMODE end. token-type ZPWY-DDL-YES-NO. ZIGNORESTOPMODE specifies whether to ignore the STOP-MODE special register.
ZPWY-MAP-QUAL-TCP ZPWY-MAP- Definitions ZPWY-MAP-QUAL-TCP This token specifies the state used to select TCPs. def ZPWY-DDL-QUAL-TCP. 02 ZSTATE token-type ZPWY-DDL-TCPQUALSTATE-VALUE. end. ZSTATE is an integer pair indicating whether the specified state is to be used as an inclusive or exclusive selection criteria. Valid values for the first integer are: ZSPI-VAL-TRUE Selects objects in the specified state (that is, the PENDING, RUNNING, or STOPPED state).
ZPWY-MAP-QUAL-TERM ZPWY-MAP- Definitions ZPWY-MAP-QUAL-TERM This token specifies the state used to select configured or temporary TERM objects. def ZPWY-DDL-QUAL-TERM. 02 ZSTATE token-type ZPWY-DDL-TRMQUALSTATEVALUE. end. ZSTATE is an integer pair. Valid values for the first integer are: ZSPI-VAL-TRUE Selects objects in the specified state (that is, the RUNNING, STOPPED, or SUSPENDED state). ZSPI-VAL-FALSE Selects objects in the state that is the complement of the specified state.
ZPWY-MAP-SEL-PROGTERM ZPWY-MAP- Definitions ZPWY-MAP-SEL-PROGTERM this token specifies a PROG object name and the type of device on which the program runs. The token fields are described under ZPWY-DDL-PROGTERMNAME on page 5-4. def ZPWY-DDL-SEL-PROGTERM. 02 ZNAME. 03 ZPROGRAM token-type 03 FILLER token-type 03 ZTERMTYPE token-type 03 FILLER-1 token-type end. ZPWY-DDL-OBJECT-NAME. ZPWY-DDL-FILLER. ZPWY-DDL-TERM-TYPE. ZPWY-DDL-FILLER.
ZPWY-MAP-SEL-TCP ZPWY-MAP- Definitions ZPWY-MAP-SEL-TCP This token specifies the name of a TCP. The token fields are described under ZPWYDDL-TCPNAME on page 5-6. def ZPWY-DDL-SEL-TCP. 02 ZNAME. 03 ZTCP !r 03 FILLER-1 end. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. When returned in a response buffer, this token specifies the TCP acted upon. ZPWY-MAP-SEL-TCPLINK This token specifies a link between a TCP and a specific server process in a server class.
ZPWY-MAP-SEL-TCPTERM ZPWY-MAP- Definitions ZPWY-MAP-SEL-TCPTERM This token specifies a link between a TCP and a specific terminal. The token fields are described under ZPWY-DDL-TCPTERMNAME on page 5-7. def ZPWY-DDL-SEL-TCPTERM. 02 ZNAME. 03 ZTCP !r 03 FILLER 03 ZTERM !r 03 FILLER-1 end. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. When returned in a response buffer, this token specifies the link acted upon.
ZPWY-MAP-STARTPROG ZPWY-MAP- Definitions ZPWY-MAP-STARTPROG This token specifies the name of a temporary TERM object that was created. def ZPWY-DDL-STARTPROG. 02 ZTERM 02 FILLER-1 end. token-type ZPWY-DDL-OBJECT-NAME. token-type ZPWY-DDL-FILLER. ZTERM specifies the name of the temporary TERM object.
ZPWY-MAP-STATS-SC ZPWY-MAP- Definitions ZPWY-MAP-STATS-SC is an extensible structured token that reports statistics on a server class. The token fields are described under Section 6, “ZPWY-MAP- Tokens,” in the TS/MP Management Programming Manual. def ZPWY-DDL-STATS-SC. 02 ZSTATSTIME 02 ZQUEUEINFO. 03 ZREQCNT 03 ZWAITS 03 ZMAXWAITS 03 ZAGGREGATEWAITS 03 ZDYNAMICLINKS 02 ZIOINFO. 03 ZSEND. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZREPLY.
ZPWY-MAP-STATS-TCP1 ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP1 This token reports statistics on a TCP with the program name PATHTCP2. ZPWY-MAP-STATS-TCP1 includes the same fields as ZPWY-MAP-STATS-TCP2. In addition, statistics are reported on ZCPMEMMAN (a field of the ZQUEUEINFO field) and ZIOCOMP, as described next. def ZPWY-DDL-STATS-TCP1. 02 ZSTATSTIME 02 ZPOOLINFO. 03 ZTERMPOOL. 04 ZSIZE 04 ZREQCNT 04 ZMAXALLOC 04 ZAGGREGATEALLOC 04 ZCURALLOC 04 ZMAXREQ 04 ZAGGREGATEREQSIZE 03 ZSERVERPOOL.
ZPWY-MAP-STATS-TCP1 ZPWY-MAP- Definitions 02 ZQUEUEINFO. 03 ZTERMPOOL. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZSERVERPOOL. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZMEMMAN. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZLINK. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZDELINK. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZCHECKPOINT. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZCPMEMMAN.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP1 ZCPMEMMAN reports statistics on checkpoint requests that must be handled as a memorymanagement request (that is, checkpoints written directly to disk). ZCPEMEMMAN contains the following subfields: ZREQCNT is the number of requests for TCP resources. ZWAIT is the percentage of requests that were queued because the resource was in use. ZMAXWAITS is the count of the greatest number of queued requests encountered at the time a new request was queued.
ZPWY-MAP-STATS-TCP2 ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP2 This token reports statistics on a TCP with the program name PATHTCP2. def ZPWY-DDL-STATS-TCP2. 02 ZSTATSTIME 02 ZPOOLINFO. 03 ZTERMPOOL. 04 ZSIZE 04 ZREQCNT 04 ZMAXALLOC 04 ZAGGREGATEALLOC 04 ZCURALLOC 04 ZMAXREQ 04 ZAGGREGATEREQSIZE 03 ZSERVERPOOL. 04 ZSIZE 04 ZREQCNT 04 ZMAXALLOC 04 ZAGGREGATEALLOC 04 ZCURALLOC 04 ZMAXREQ 04 ZAGGREGATEREQSIZE 02 ZAREAINFO. 03 ZDATA. 04 ZSIZE 04 ZMAXALLOC 04 ZCURALLOC 04 ZMAXREQ 03 ZCODE.
ZPWY-MAP-STATS-TCP2 ZPWY-MAP- Definitions 03 ZSERVERPOOL. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZMEMMAN. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZLINK. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZDELINK. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS 03 ZCHECKPOINT. 04 ZREQCNT 04 ZWAITS 04 ZMAXWAITS 04 ZAGGREGATEWAITS token-type token-type token-type token-type ZSPI-DDL-INT4. ZSPI-DDL-INT4. ZSPI-DDL-INT4. ZSPI-DDL-INT4.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP2 ZREQCNT is the number of requests the TCP receives for I/O buffer space during the time that the TCP gathers these statistics. ZMAXALLOC is the greatest number of words allocated from the pool area during the time that the TCP reports these statistics. This number represents the largest amount of the total pool area used at one time for all TERM I/O buffers. ZAGGREGATEALLOC is the total number of words allocated from the pool area.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP2 ZSIZE is the total context data area allocated for all of the TERM objects defined with the ZMAXTERMS field in ZPWY-DDL-DEF-TCP. The TCP allocates space for each TERM object by using the approximate values defined for the ZMAXTERMDATA and ZMAXREPLY fields: ZMAXTERMDATA for simulating an execution stack for the SCREEN COBOL programs, and ZMAXTERMDATA plus ZMAXREPLY for the latest checkpoint information.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP2 ZCURALLOC is the number of words allocated from this code area at the time that the TCP reports these statistics. ZMAXREQ is the greatest number of words used in a request for SCREEN COBOL code space. This request includes the total number of words for, at most, three code segments. ZAGGREGATEREQSIZE is the total number of words in a request for SCREEN COBOL code space.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP2 ZAGGREGATEWAITS is the total number of queued I/O buffer requests encountered during the interval for which the TCP reports these statistics. To find the average number of queued I/O buffer requests, divide ZAGGREGATEWAITS by ZREQCNT. ZSERVERPOOL contains the same subfields as ZTERMPOOL and reports information about server I/O buffers. ZMEMMAN reports queue information about requests for SCREEN COBOL object code.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TCP2 response by the TCP; these requests generally have a timeout interval that must elapse before the requests can be granted. ZMAXWAITS is the greatest number of queued link requests encountered during the interval for which the TCP reports these statistics. ZAGGREGATEWAITS is the total link requests that queued during the interval for which the TCP reports these statistics. To find the average number of link requests that queued, divide ZAGGREGATEWAITS by ZREQCNT.
ZPWY-MAP-STATS-TERM1 ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM1 ZPWY-MAP-STATS-TERM1 identifies an extensible structured token that provides statistics on a TERM object running under PATHTCP2. def ZPWY-DDL-STATS-TERM1. 02 ZSTATSTIME TIMESTAMP. 02 ZIOINFO. 03 ZDISPLAY. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZACCEPT. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZSEND. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZREPLY.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM1 ZAGGREGATEREQSIZE is the total size, in words, of requests for code area space. To find the average size, divide ZAGGREGATEREQSIZE by ZREQCNT.
ZPWY-MAP-STATS-TERM2 ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM2 This token reports statistics on a TERM object running under PATHTCP2. def ZPWY-DDL-STATS-TERM2. 02 ZSTATSTIME 02 ZIOINFO. 03 ZDISPLAY. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZACCEPT. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZSEND. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZREPLY. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 03 ZCHECKPOINT. 04 ZREQCNT 04 ZMAXSIZE 04 ZAGGREGATESIZE 04 ZIOS 02 ZAREAINFO.
ZPWY-MAP-STATS-TERM2 ZPWY-MAP- Definitions 02 ZPERFINFO. 03 ZAGGREGATE. 04 ZTOTALMEASCOUNT 04 ZAVGRESP 04 ZMAXRESP 04 ZMINRESP 04 ZSUMOFSQUARES 03 ZFREQTABLE. 04 ZMEASCOUNT 04 ZMEASCOUNTACTIVE 04 ZMINTIME 04 ZTIMEINCR token-type token-type token-type token-type token-type ZSPI-DDL-INT2. ZSPI-DDL-INT4. ZSPI-DDL-INT4. ZSPI-DDL-INT4. ZSPI-DDL-INT4. token-type ZSPI-DDL-INT2. occurs 20 times token-type ZSPI-DDL-INT. token-type ZSPI-DDL-INT4. token-type ZSPI-DDL-INT4. end.
ZPWY-MAP-STATS-TERM2 ZPWY-MAP- Definitions ZIOS is the number of I/O operations in which the TCP writes the data in the I/O buffer to the TERM object. For TERM objects running in block mode, the TCP writes output to the TERM when: • • • The buffer, defined by the ZTERMBUF field in ZPWY-DDL-DEF-TCP, is full. Executing an ACCEPT statement. Any of the statements listed in ZREQCNT is followed by certain other SCREEN COBOL statements, such as DELAY.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM2 ZSEND reports server I/O information about the SCREEN COBOL SEND statements that it executes for the TERM object. ZSEND has the following subfields: ZREQCNT is the number of SCREEN COBOL SEND statements that cause the TCP I/O operations to the servers during the interval that the TCP reports these statistics. ZMAXSIZE is the size, in bytes, of the largest amount of data transferred to a server for a SEND statement.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM2 ZIOS is the total number of I/O operations to the server. ZIOS has the same value as ZREQCNT. ZCHECKPOINT reports information from the TCP about the SCREEN COBOL CHECKPOINT statement; the TCP normally performs more checkpoint operations than those generated by this statement. ZCHECKPOINT has the following subfields: ZREQCNT is the total number of CHECKPOINT requests.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM2 ZCURSIZE is the current amount of data space, in words, requested for terminal context at the time that the TCP reports these statistics. ZREQCNT gives the number of terminal requests for context data space. ZAGGREGATEREQSIZE gives the total size, in words, of requests for context data space. To find the average size in words for context data space, divide ZAGGREGATEREQSIZE by ZREQCNT. ZCODE contains information about the terminal requests for code space.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM2 For additional information on performance statistics, see the Pathway/iTS System Management Manual. ZPERFINFO contains the following fields: ZAGGREGATE contains the following subfields: 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.
ZPWY-MAP- Definitions ZPWY-MAP-STATS-TERM2 ZMEASCOUNTACTIVE is the number of time intervals. If no frequency distribution table is generated because ZTOTALMEASCOUNT is less than 50 or ZTIMEINCR is less than 0.01 second, the value of ZMEASCOUNTACTIVE is 0. For Pathway C31, ZMEASCOUNTACTIVE is fixed at 20. ZMINTIME is the value of the first time interval. ZTIMEINCR is the time increment from one interval to the next.
ZPWY-MAP-STATUS-TCP ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TCP This token reports status information on a TCP. def ZPWY-DDL-STATUS-TCP. 02 ZSTATUSTIME 02 ZSTATE 02 ZERRORINFO. 03 ZERROR 03 ZINFO 02 ZPROCESS 02 ZERRORINFO2 03 ZERROR2 03 ZINFO2 03 ZDETAIL2 02 ZPPRIMARY. 03 ZCPU 03 ZPIN 02 ZBACKUP. 03 ZCPU 03 ZPIN end. token-type ZSPI-DDL-TIMESTAMP. token-type ZPWY-DDL-OBJSTATE-VALUE. token-type token-type token-type token-type token-type token-type token-type ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-CRTPID.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TCP ZCPU returns the primary processor. ZPIN returns the primary process ID number. ZBACKUP returns the processor and PIN of the backup TCP: ZCPU returns the backup processor. ZPIN returns the backup process ID number.
ZPWY-MAP-STATUS-TCPLINK ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TCPLINK This token reports either the count of links to the server (if LINKDEPTH is greater than 1) or the rank of the server in the server class (if LINKDEPTH is 1). def ZPWY-DDL-STATUS-TCPLINK. 02 ZSTATUSTIME token-type ZSPI-DDL-TIMESTAMP. 02 ZISCOUNT token-type ZPWY-DDL-YES-NO. 02 ZRANKCOUNT token-type ZSPI-DDL-INT. end. ZSTATUSTIME gives the time this status was collected, as a four-word GMT timestamp.
ZPWY-MAP-STATUS-TERMDETAIL ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TERMDETAIL This token reports the information contained in the PATHCOM STATUS TCP, DETAIL listing. It is returned in the response message to a STATUS TERM or STATUS TCPTERM command. def ZPWY-DDL-STATUS-TERMDETAIL. 02 ZSTATUSTIME token-type 02 ZSTATE token-type VALUE. 02 ZTCP token-type 02 FILLER token-type 02 ZERRORINFO. 03 ZERROR token-type 03 ZINFO token-type 02 ZFILE token-type 02 ZWAIT token-type VALUE. 02 ZPENDING token-type VALUE.
ZPWY-MAP-STATUS-TERMDETAIL ZPWY-MAP- Definitions ZTCP is the name of the controlling TCP. ZERRORINFO gives error information. The fields are described under ZPWY-DDL-ERROR-INFO in this section. ZFILE is the file name of the device. The following information is returned only if the TERM object is running or suspended: ZWAIT indicates whether the TERM object is ready or unable to proceed.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TERMDETAIL This ZWAIT Value… Indicates That The TERM Object… ZPWY-VAL-SERVBUF Is waiting for internal server I/O buffer space to become available. ZPWY-VAL-SERVER Is waiting for a server process to become available— all links to the desired server class are currently in use. ZPWY-VAL-SERVERIO Is waiting for a request to a server to complete.
ZPWY-MAP-STATUS-TERMDETAIL ZPWY-MAP- Definitions ZPENDING is the reason a TERM object is not yet suspended. The following values are valid: ZPWY-VAL-STOP indicates that a STOP command has been issued to the TERM object, but either the terminal’s SCREEN COBOL special register STOP-MODE is nonzero or execution has not reached a state in which suspension is possible.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TERMDETAIL ZSCREENRECOVERY indicates whether screen recovery is currently taking place for the TERM. The following values are valid: ZPWY-VAL-NO The screen recovery is not currently taking place. ZPWY-VAL-YES The screen recovery is currently taking place. ZPUFILE is the name of the currently executing SCREEN COBOL program file from the SET TERM or the SET TCP TCLPROG parameter. ZPUNAME is the name of the currently executing SCREEN COBOL program unit.
ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TERMDETAIL ZSERVER is the name of a server class with which the TERM object is communicating or for which it is waiting.
ZPWY-MAP-STATUS-TERMFREEZE ZPWY-MAP- Definitions ZPWY-MAP-STATUS-TERMFREEZE This token reports the freeze status of a terminal that is preventing a server from being frozen. It is returned in the response message to a FREEZESTATUS SCTERM command. def ZPWY-DDL-STATUS-TERMFREEZE. 02 ZSTATUSTIME token-type ZSPI-DDL-TIMESTAMP. 02 ZSTATE token-type ZPWY-DDL-FRZSTATETERMVALUE. end. ZSTATUSTIME gives the time this status was collected as a four-word GMT timestamp. ZSTATE is the state of the TERM object.
ZPWY-MAP- Definitions ZPWY-MAP-TELLNUM NonStop Pathway/iTS Management Programming Manual—426749-002 6- 80
7 Terminal Control Process (TCP) Commands This section provides complete descriptions for the commands that enable you to define and control TCPs within a Pathway subsystem (that is, TCPs controlled by the same PATHMON process): Commands Object Types ZPWY-CMD-ADD ZPWY-OBJ-TCP ZPWY-CMD-ALTER ZPWY-OBJ-TCP ZPWY-CMD-CONTROL ZPWY-OBJ-TCP ZPWY-CMD-DELETE ZPWY-OBJ-TCP ZPWY-CMD-GETVERSION ZPWY-OBJ-TCP ZPWY-CMD-INFO ZPWY-OBJ-TCP ZPWY-CMD-REFRESHCODE ZPWY-OBJ-TCP ZPWY-CMD-START ZPWY-OBJ-TCP ZPWY-CMD
ADD TCP Terminal Control Process (TCP) Commands ADD TCP Use the ADD TCP command to enter the name of a TCP and its description into the PATHMON configuration file. For guidelines on calculating appropriate configuration values, see the TS/MP System Management Manual. Continuation You cannot use continuation with this command to add more than one TCP. You must add the TCPs one at a time.
ADD TCP Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For ADD TCP, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1012 ZPWY-ERR-PM-DUPNAME The PATHMON process encountered a duplicate TCP name. 1100 ZPWY-ERR-PM-TOOMANYTCP The value specified for ZMAXTCPS was reached. For descriptions of error-token values and their associated error lists, see Section 11, TCP Event Messages and Section 12, TCP Error Messages.
ALTER TCP Terminal Control Process (TCP) Commands ALTER TCP Use the ALTER TCP command to change the attribute values of a TCP that was previously added to the PATHMON configuration file. Use the ALTER command to alter one or more attribute values. The TCP must be stopped before you can alter an attribute value. To alter a TCP in the running state, use the CONTROL TCP command. This command affects only TCPs controlled by the PATHMON process in your subsystem.
Terminal Control Process (TCP) Commands ALTER TCP ZSWAP, or ZTCLPROG using the TACL program, you must use the #SETBYTES built-in function. See the SPI Programming Manual for more information.
CONTROL TCP Terminal Control Process (TCP) Commands CONTROL TCP Use the CONTROL TCP command to change specific TCP attributes while the TCP is running and to record the changes in the PATHMON configuration file. Additional TCP attributes can be changed while the TCP is stopped by using the ALTER TCP command. If you restart the TCP after a CONTROL command, the TCP runs with the attribute changes that resulted from this command.
Terminal Control Process (TCP) Commands • • CONTROL TCP If the primary TCP process is running in the processor defined for the backup TCP process because of a SWITCH command or some other processor change, assigning a value to the ZBACKUPCPU field causes the PATHMON process to change the PATHMON configuration file so that it contains the current processor numbers for both the primary and backup TCP processes.
DELETE TCP Terminal Control Process (TCP) Commands DELETE TCP Use the DELETE TCP command to remove a TCP description from the PATHMON configuration file. A TCP must be stopped before it can be deleted by the PATHMON process. This command affects only TCPs controlled by the PATHMON process in your subsystem. It does not affect external TCPs (TCPs that are controlled by another PATHMON process and are therefore outside this PATHMON environment).
Terminal Control Process (TCP) Commands GETVERSION TCP GETVERSION TCP Use the GETVERSION TCP command to obtain the software version of a TCP. This command only obtains the version of a TCP controlled by your subsystem’s PATHMON process. It does not obtain information about an external TCP (a TCP that is controlled by another PATHMON process and is therefore outside this PATHMON environment).
Terminal Control Process (TCP) Commands GETVERSION TCP Tokens in Response Buffer ZSPI-TKN-SERVER-BANNER is an ASCII character string that identifies the Pathway/iTS or TS/MP product name, product number, release date, and sometimes additional information, in displayable form. Note. The value of ZSPI-TKN-SERVER-BANNER is intended only for display, not for programs to examine. Its format might change in future versions of the product.
INFO TCP Terminal Control Process (TCP) Commands INFO TCP Use the INFO TCP command to display the attribute values defined in the PATHMON configuration file for a TCP. This command returns information only for TCPs controlled by the PATHMON process in your subsystem. It does not return information for external TCPs (TCPs that are controlled by another PATHMON process and are therefore outside this PATHMON environment).
Terminal Control Process (TCP) Commands INFO TCP Considerations • If you include a specific selector, the INFO TCP command obtains the configured values for that TCP. Those values include the attribute values you explicitly defined for a TCP (in ZPWY-DDL-DEF-TCP) and the default values for the attributes you did not explicitly define. This command returns information about a TCP only after the description has been added to the PATHMON configuration file.
Terminal Control Process (TCP) Commands REFRESHCODE TCP REFRESHCODE TCP Use the REFRESHCODE TCP command to have the TCP read the SCREEN COBOL directory file for the latest version of a called program. This command is effective only if the TCP is running and the ZCHECKDIRECTORY field has the value ZPWY-VAL-OFF. Use this command when a new version of a SCREEN COBOL program (in the TCLPROG file) becomes available to the TCP. This command affects only TCPs controlled by the PATHMON process in your subsystem.
REFRESHCODE TCP Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For REFRESHCODE TCP, a common error value for ZSPI-TKN-RETCODE is: Error Number 1116 Error Token Description ZPWY-ERR-PMALREADYREFRESHED The ZCHECKDIRECTORY field in ZPWYMAP-DEF-TCP is set to ZPWY-VAL-ON. For descriptions of all error-token values and their associated error lists, see Section 11, TCP Event Messages and Section 12, TCP Error Messages.
START TCP Terminal Control Process (TCP) Commands START TCP Use the START TCP command to initiate operation of a TCP. This command cannot initiate an external TCP (a TCP that is controlled by another PATHMON process and is therefore outside this PATHMON environment). If the primary processor defined for a TCP is unavailable, the PATHMON process starts the TCP in the backup processor defined for that TCP. Continuation To start all TCPs, initialize the ZTCP field in ZPWY-DDL-SEL-TCP to ZPWY-VAL-ALLTCP.
START TCP Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For START TCP, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1003 ZPWY-ERR-PMALREADYSTARTED The TCP is already started. 1038 ZPWY-ERR-PMNEWPROCESS An error occurred while the PATHMON process was attempting to create a new process for the TCP. 1091 ZPWY-ERR-PMINVALIDHOMETERM The specified file cannot be used for a home terminal.
STATS SCTCP Terminal Control Process (TCP) Commands STATS SCTCP Use the STATS SCTCP command to obtain resource usage and performance statistics collected by all Pathway/iTS TCPs linked to the specified server class. The ZSTATS field in ZPWY-DDL-DEF-TCP controls the gathering of these statistics for the TCPs.
STATS SCTCP Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-SCTCP token-type ZPWY-DDL-SEL-SCTCP. ZPWY-MAP-STATS-SC token-type ZPWY-DDL-STATS-SC. Considerations • • If the server class stops for any reason, its statistics are lost. As a result, when a server in that class is restarted, the TCP has no statistics for the server process.
STATS TCP Terminal Control Process (TCP) Commands STATS TCP Use the STATS TCP command to obtain resource usage and performance statistics collected by the TCP. These statistics provide information about the TCP operations and data space allocations. The ZSTATS field in ZPWY-DDL-DEF-TCP and the ZSTATS field in ZPWY-DDL-PARCONTROL-TCP control the gathering of these statistics. Statistics are returned for PATHTCP or PATHTCP2, depending on which version of the TCP you are running.
STATS TCP Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCP token-type ZPWY-DDL-SEL-TCP. ZPWY-MAP-STATS-TCP2 token-type ZPWY-DDL-STATS-TCP2. ZPWY-MAP-STATS-TCP1 token-type ZPWY-DDL-STATS-TCP1. Considerations • • • If the ZSTATS field in ZPWY-DDL-DEF-TCP has the value ZPWY-VAL-OFF, the TCP does not gather statistics for this command.
STATS TCPSC Terminal Control Process (TCP) Commands STATS TCPSC Use the STATS TCPSC command to obtain resource usage and performance statistics collected by a TCP for all server classes to which it is linked. The ZSTATS field in ZPWY-DDL-DEF-TCP controls the gathering of these statistics for the TCP. The ZSTATS field in ZPWY-DDL-PAR-CONTROL-TCP controls the gathering of statistics on performance.
STATS TCPSC Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPSC token-type ZPWY-DDL-SEL-TCPSC. ZPWY-MAP-STATS-SC token-type ZPWY-DDL-STATS-SC. Considerations • • If the ZSTATS field in ZPWY-DDL-DEF-TCP has a value of ZPWY-VAL-OFF, the TCP does not gather information for this command.
STATUS TCP Terminal Control Process (TCP) Commands STATUS TCP Use the STATUS TCP command to obtain the status of TCPs, including external TCPs (TCPs that are controlled by another PATHMON process and are therefore outside this PATHMON environment) that have links to local server processes. Continuation To obtain the status of more than one TCP, initialize the ZTCP field in ZPWY-DDL-SEL-TCP to ZPWY-VAL-ALLTCP.
Terminal Control Process (TCP) Commands • • STATUS TCP When a TCP from one Pathway subsystem requests a link to a server class in a different Pathway subsystem, the PATHMON process controlling the server class considers the TCP to be an external process. However, a STATUS TCP command issued to the local the PATHMON process (the PATHMON process controlling the server class) returns information about both the external and local TCPs.
STATUS TCPLINK Terminal Control Process (TCP) Commands STATUS TCPLINK Use the STATUS TCPLINK command either to count the number of links between a TCP and a server process or to obtain the preferential rank given by a TCP to a server process. The information returned by this command is the same as that returned by the PROCESSES parameter of the PATHCOM STATUS SERVER command.
STATUS TCPLINK Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPLINK token-type ZPWY-DDL-SEL-TCPLINK. ZPWY-MAP-STATUS-TCPLINK token-type ZPWY-DDL-STATUS-TCPLINK. Consideration You can use this command, along with the STATUS SC and STATUS SCPROCESS commands, to implement the equivalent of the PATHCOM STATUS SERVER, PROCESSES command.
STOP TCP Terminal Control Process (TCP) Commands STOP TCP Use the STOP TCP command to stop a TCP. This command does not stop an external TCP (a TCP that is controlled by another PATHMON process and is therefore outside this PATHMON environment) that is linked to a local server process. Continuation To stop all TCPs, initialize the ZTCP field in ZPWY-DDL-SEL-TCP to ZPWY-VAL-ALLTCP.
STOP TCP Terminal Control Process (TCP) Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For STOP TCP, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1004 ZPWY-ERR-PMALREADYSTOPPED The TCP is already stopped. 1045 ZPWY-ERR-PMSTATEMISMATCH The TCP is not in the appropriate state to allow the PATHMON process to execute the STOP request. One possible cause is that some of the TERM objects controlled by this TCP are running.
SWITCH TCP Terminal Control Process (TCP) Commands SWITCH TCP Use the SWITCH TCP command to direct the TCP to exchange the function of its primary process with the function of its backup process while the TCP is running. The TCP must have an initialized backup process. This command does not change the TCP’s configured CPUs definition in the PATHMON configuration file.
Terminal Control Process (TCP) Commands SWITCH TCP Considerations • • The SWITCH TCP command does not affect the TCP definition. If you restart a TCP that was running with its primary and backup processes switched, the primary and backup processes start in their configured CPUs. The SWITCH TCP command can be used together with the CONTROL TCP command (and the ZBACKUPCPU field in ZPWY-DDL-PAR-CONTROL-TCP) to implement the PATHCOM PRIMARY command. To implement the PATHCOM PRIMARY TCP command: 1.
8 TERM Commands This section provides complete descriptions for the commands that enable you to define and control configured TERM objects and control and inquire about temporary TERM objects; the commands are listed in alphabetical order: Commands Object Types ZPWY-CMD-ABORT ZPWY-OBJ-TCPTERM ZPWY-OBJ-TERM ZPWY-CMD-ADD ZPWY-OBJ-TERM ZPWY-CMD-ALTER ZPWY-OBJ-TERM ZPWY-CMD-DELETE ZPWY-OBJ-TCPTERM ZPWY-OBJ-TERM ZPWY-CMD-FREEZESTATUS ZPWY-OBJ-SCTERM ZPWY-CMD-INFO ZPWY-OBJ-TCPTERM ZPWY-OBJ-TERM ZP
ABORT TCPTERM TERM Commands ABORT TCPTERM Use the ABORT TCPTERM command to stop a suspended or running TERM object under the control of a specific TCP. This command can be issued to configured and temporary TERM objects. Continuation To abort all TERM objects under the control of a single TCP, initialize the ZTCP field in ZPWY-MAP-SEL-TCPTERM to the name of the TCP and initialize the ZTERM field to ZPWY-VAL-ALLTERM.
ABORT TERM TERM Commands ABORT TERM Use the ABORT TERM command to stop a suspended or running TERM object. This command can be issued to configured and temporary TERM objects. Continuation To abort all TERM objects, initialize the ZTERM field in ZPWY-MAP-SEL-TERM to ZPWY-VAL-ALLTERM. Reissue the command repeatedly, using the context token returned by PATHMON, until no data is returned in the response buffer. For more information, see Specifying Continuation on page 3-21.
ADD TERM TERM Commands ADD TERM Use the ADD TERM command to enter the name and description of a TERM object into the PATHMON configuration file. This command can be issued only for configured TERM objects. Continuation You cannot use continuation to add all TERM objects; you must add each TERM object separately. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-36.
ADD TERM TERM Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For ADD TERM, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1012 ZPWY-ERR-PM-DUPNAME The PATHMON process encountered a duplicate TERM object name. 1101 ZPWY-ERR-PMTOOMANYTERM The value specified for ZMAXTERMS was reached. For descriptions of error-token values and their associated error lists, see Section 11, TCP Event Messages and Section 12, TCP Error Messages.
ALTER TERM TERM Commands ALTER TERM Use the ALTER TERM command to change the attribute values of a TERM object that was previously added to the PATHMON configuration file. This command can be issued only to configured TERM objects. The TERM object must be stopped before you can alter an attribute value. Continuation You cannot alter more than one TERM object by specifying continuation; you must alter each TERM individually by name.
ALTER TERM TERM Commands exists, the PATHMON process does not have the space to create a new TERM entry. To avoid generating this error, define and add the maximum number of TERM entries allowed, minus 1 (that is, 4094 TERM objects). • For ALTER commands, the values for tokens and fields omitted from the command buffer remain unchanged. Reset values for each field are predefined. These values are described in Section 3, SPI Programming Considerations.
DELETE TCPTERM TERM Commands DELETE TCPTERM Use the DELETE TCPTERM command to remove from the PATHMON configuration file a TERM object description under the control of a specific TCP. The TERM object must be stopped before it can be deleted. This command can be issued to configured and temporary TERM objects.
DELETE TERM TERM Commands DELETE TERM Use the DELETE TERM command to remove a TERM object description from the PATHMON configuration file. A TERM object must be stopped before it can be deleted. This command can be issued to configured and temporary TERM objects. Continuation To delete all TERM objects, initialize the ZTERM field in ZPWY-MAP-SEL-TERM to ZPWY-VAL-ALLTERM.
FREEZESTATUS SCTERM TERM Commands FREEZESTATUS SCTERM Use the FREEZESTATUS SCTERM command to obtain the freeze status of a TERM object that is preventing a server from being frozen. Continuation To obtain the status of all TERM objects preventing a server class from being frozen, initialize the ZSERVERCLASS field in ZPWY-DDL-SEL-SCTERM to the server class name and initialize the ZTERM field in ZPWY-DDL-SEL-SCTERM to ZPWY-VALALLTERM.
FREEZESTATUS SCTERM TERM Commands Considerations • • The PATHMON process returns an error if any of the following conditions apply: • • • A FREEZE command has not been issued against the server. The specified TERM object is not communicating with the specified server. The TERM object’s STOP-MODE special register is zero, signifying that the TERM object is not preventing the server from being frozen. The PATHMON process also returns an error if the server is already frozen.
INFO TCPTERM TERM Commands INFO TCPTERM Use the INFO TCPTERM command to obtain the attribute values defined in the PATHMON configuration file for a TERM object under the control of a specific TCP. This command can be issued for configured and temporary TERM objects. Continuation To obtain information for all TERM objects under the control of a single TCP, initialize the ZTCP field in ZPWY-DDL-SEL-TCPTERM to the name of the TCP and initialize the ZTERM field to ZPWY-VAL-ALLTERM.
INFO TCPTERM TERM Commands Consideration To obtain the default values for TCPTERM attributes, assign null values to the ZTCP and ZTERM fields in ZPWY-DDL-SEL-TCPTERM.
INFO TERM TERM Commands INFO TERM Use the INFO TERM command to obtain the attribute values defined in the PATHMON configuration file for a TERM object. This command can be issued for configured and temporary TERM objects. Continuation To obtain information for all TERM objects, initialize the ZTERM field in ZPWY-DDLSEL-TERM to ZPWY-VAL-ALLTERM. Reissue the command repeatedly, using the context token returned by the PATHMON process, until no data is returned in the response buffer.
INFO TERM TERM Commands Consideration To obtain the default values for TERM object attributes, assign a null value to the ZTERM field in ZPWY-DDL-SEL-TERM. The SPI requester can use the default values to implement the equivalent of a PATHCOM SHOW TERM command issued before any TERM attributes are set.
INSPECT TERM TERM Commands INSPECT TERM Use the INSPECT TERM command to invoke the HP Inspect symbolic debugger process to debug a SCREEN COBOL program running on a TERM object. This command establishes a breakpoint at the next program instruction; the program waits for commands from the Inspect process. This command can be issued for configured and temporary TERM objects.
RESUME TCPTERM TERM Commands RESUME TCPTERM Use the RESUME TCPTERM command to restart a SCREEN COBOL program on a suspended TERM object under the control of a specific TCP. This command can be issued to configured and temporary TERM objects. Continuation To restart all suspended TERM objects under the control of a single TCP, initialize the ZTCP field in ZPWY-DDL-SEL-TCPTERM to the name of the TCP and initialize the ZTERM field to ZPWY-VAL-ALLTERM.
RESUME TCPTERM TERM Commands Considerations • • • • If a TERM object is suspended by the TCP because of a fatal TERM error, you might not be able to restart the TERM object using the RESUME TCPTERM command. Instead, you might have to issue the ABORT TCPTERM command and then restart the TERM object using the START TCPTERM command.
RESUME TERM TERM Commands RESUME TERM Use the RESUME TERM command to restart a screen program that has been suspended with the SUSPEND TERM command. The RESUME TERM command changes the TERM state to RUNNING. This command can be issued to configured and temporary TERM objects. Continuation To restart all suspended TERM objects, initialize the ZTERM field in ZPWY-DDL-SELTERM to ZPWY-VAL-ALLTERM.
RESUME TERM TERM Commands Considerations • • • • If the TERM object is suspended by the TCP because of a fatal TERM error, you might not be able to restart the TERM object using the RESUME TERM command. Instead, you might have to issue the ABORT TERM command and then restart the TERM object using the START TERM command.
START TCPTERM TERM Commands START TCPTERM Use the START TCPTERM command to direct a specific TCP to begin executing a SCREEN COBOL program on one or more designated TERM objects. The TCP that controls the TERM objects must be running before you issue this command. This command can be issued only to configured TERM objects.
START TCPTERM TERM Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For START TCPTERM, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1003 ZPWY-ERR-PM-ALREADYSTARTED The TERM object is already running. 1052 ZPWY-ERR-PM-TCPNOTDEFINED The TCP named in the TERM object’s configuration has not been configured. 1053 ZPWY-ERR-PM-TCPNOTRUNNING The TCP named in the TERM object’s configuration is not running.
START TERM TERM Commands START TERM Use the START TERM command to direct the TCP to begin executing a SCREEN COBOL program on one or more designated TERM objects. The TCP that controls the TERM objects must be running before you issue this command. This command can be issued only to configured TERM objects. Continuation To start all TERM objects, initialize the ZTERM field in ZPWY-DDL-SEL-TERM to ZPWY-VAL-ALLTERM.
START TERM TERM Commands Tokens in Response Buffer ZSPI-TKN-RETCODE For START TERM, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1003 ZPWY-ERR-PM-ALREADYSTARTED The TERM object is already running. 1052 ZPWY-ERR-PM-TCPNOTDEFINED The TCP named in the TERM object’s configuration has not been configured. 1053 ZPWY-ERR-PM-TCPNOTRUNNING The TCP named in the TERM object’s configuration is not running.
STATS TCPTERM TERM Commands STATS TCPTERM Use the STATS TCPTERM command to obtain resource-usage and performance statistics, including response time information, collected by a TCP for a TERM object under its control. The search is restricted to one TCP. The TERM object must be running or suspended for this command to complete successfully. This command can be issued for configured and temporary TERM objects.
STATS TCPTERM TERM Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPTERM token-type ZPWY-DDL-SEL-TCPTERM. ZPWY-MAP-STATS-TERM2 token-type ZPWY-DDL-STATS-TERM2. ZPWY-MAP-STATS-TERM1 token-type ZPWY-DDL-STATS-TERM1. Consideration Either ZPWY-MAP-STATS-TERM1 or ZPWY-MAP-STATS-TERM2, but not both, is present in the response buffer.
STATS TERM TERM Commands STATS TERM Use the STATS TERM command to obtain resource-usage and performance statistics, including response time information, collected by the TCP. These statistics provide information about TERM object operations. The TERM object must be running or suspended for this command to complete successfully. This command can be issued for configured and temporary TERM objects.
STATS TERM TERM Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TERM token-type ZPWY-DDL-SEL-TERM. ZPWY-MAP-STATS-TERM2 token-type ZPWY-DDL-STATS-TERM2. ZPWY-MAP-STATS-TERM1 token-type ZPWY-DDL-STATS-TERM1. Considerations • • If the ZSTATS field in ZPWY-DDL-DEF-TCP has a value of ZPWY-VAL-OFF, the TCP does not gather information for this command.
STATUS TCPTERM TERM Commands STATUS TCPTERM Use the STATUS TCPTERM command to obtain the current status of a TERM object running under the control of a specific TCP. This command can be issued for configured and temporary TERM objects. This command does not return information collected by an external TCP (a TCP controlled by another PATHMON process and therefore outside this PATHMON environment).
STATUS TCPTERM TERM Commands Consideration Information for the following fields is returned only if the TERM object is running: ZACCEPT ZCHARSET ZINSTADDR ZINSTCODE ZPENDING ZPUFILE ZPUNAME ZPUVERSION ZSCREENRECOVERY ZSERVER ZSTOPMODENZ ZTRANSID ZTRANSMODE ZTRANSRESTARTED ZTRANSRESTARTS ZWAIT NonStop Pathway/iTS Management Programming Manual—426749-002 8- 30
STATUS TERM TERM Commands STATUS TERM Use the STATUS TERM command to obtain the current status of a TERM object. This command can be issued for configured and temporary TERM objects. Continuation To obtain the status of all TERM objects, initialize the ZTERM field in ZPWY-MAP-SEL-TERM to ZPWY-VAL-ALLTERM. Reissue the command repeatedly, using the context token returned by the PATHMON process, until no data is returned in the response buffer. For more information, see Specifying Continuation on page 3-21.
STATUS TERM TERM Commands Consideration Information for the following fields is returned only if the TERM object is running: ZACCEPT ZCHARSET ZINSTADDR ZINSTCODE ZPENDING ZPUFILE ZPUNAME ZPUVERSION ZSCREENRECOVERY ZSERVER ZSTOPMODENZ ZTRANSID ZTRANSMODE ZTRANSRESTARTED ZTRANSRESTARTS ZWAIT NonStop Pathway/iTS Management Programming Manual—426749-002 8- 32
STOP TCPTERM TERM Commands STOP TCPTERM Use the STOP TCPTERM command to stop a TERM object under the control of a specific TCP. The TCP stops a TERM object as soon as the TERM object reaches a qualified state. A qualified state exists when the following three conditions are met: • • • The TERM object has reached a SCREEN COBOL ACCEPT statement. The SCREEN COBOL special register STOP-MODE is set to zero. The TERM object (if running under TMF auditing) is not in TMF transaction mode.
STOP TCPTERM TERM Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPTERM token-type ZPWY-DDL-SEL-TCPTERM. ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT. Tokens in Response Buffer ZSPI-TKN-RETCODE For STOP TCPTERM, a common error value for ZSPI-TKN-RETCODE is: Error Number Error Token Description 1004 ZPWY-ERR-PM-ALREADYSTOPPED The TERM object is already stopped.
STOP TERM TERM Commands STOP TERM Use the STOP TERM command to stop a TERM object. The TCP stops a TERM object as soon as the TERM object reaches a qualified state. A qualified state exists when the following three conditions are met: • • • The TERM object has reached a SCREEN COBOL ACCEPT statement. The SCREEN COBOL special register STOP-MODE is set to zero. The TERM object (if running under TMF auditing) is not in TMF transaction mode.
STOP TERM TERM Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TERM token-type ZPWY-DDL-SEL-TERM. ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT. Tokens in Response Buffer ZSPI-TKN-RETCODE For STOP TERM, a common error value for ZSPI-TKN-RETCODE is: Error Number Error Token Description 1004 ZPWY-ERR-PM-ALREADYSTOPPED The TERM object is already stopped.
SUSPEND TCPTERM TERM Commands SUSPEND TCPTERM Use the SUSPEND TCPTERM command to direct a specific TCP to temporarily suspend execution of the SCREEN COBOL program. The TCPTERM object must be running before it can be suspended. This command can be used for debugging when it is important to preserve the TERM object in its most recent state. The RESUME TERM or RESUME TCPTERM command releases the suspension.
SUSPEND TCPTERM TERM Commands Tokens in Command Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPTERM token-type ZPWY-DDL-SEL-TCPTERM. ZPWY-MAP-QUAL-TERM token-type ZPWY-DDL-QUAL-TERM. ZPWY-MAP-PAR-SUSPEND-TERM token-type ZPWY-DDL-PAR-SUSPENDTERM. Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPTERM token-type ZPWY-DDL-SEL-TCPTERM.
SUSPEND TERM TERM Commands SUSPEND TERM Use the SUSPEND TERM command to direct the TCP to temporarily suspend execution of the SCREEN COBOL program. This command can be used for debugging when it is important to preserve the TERM object in its most recent state. The RESUME TERM command releases the suspension. A TERM object is suspended as soon as it reaches a qualified state, which exists when the following three conditions are met: • • • The TERM has reached a SCREEN COBOL ACCEPT statement.
SUSPEND TERM TERM Commands Tokens in Command Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TERM token-type ZPWY-DDL-SEL-TERM. ZPWY-MAP-QUAL-TERM token-type ZPWY-DDL-QUAL-TERM. ZPWY-MAP-PAR-SUSPEND-TERM !r token-type ZPWY-DDL-PAR-SUSPENDTERM. Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TERM token-type ZPWY-DDL-SEL-TERM.
9 PROG Commands This section provides complete descriptions of the commands that enable you to define and control PROG objects; the commands are listed in alphabetical order: Commands Object Types ZPWY-CMD-ADD ZPWY-OBJ-PROG ZPWY-OBJ-PROGTERM ZPWY-CMD-ALTER ZPWY-OBJ-PROG ZPWY-OBJ-PROGTERM ZPWY-CMD-DELETE ZPWY-OBJ-PROG ZPWY-OBJ-PROGTERM ZPWY-CMD-INFO ZPWY-OBJ-PROG ZPWY-OBJ-PROGTERM ZPWY-CMD-START ZPWY-OBJ-PROG These commands define and control templates used by the PATHMON process when creating
ADD PROG PROG Commands Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-36. For descriptions of tokens and fields, see Section 4 through Section 6. Command ZPWY-CMD-ADD Object Type ZPWY-OBJ-PROG Tokens in Command Buffer ZPWY-MAP-SEL-PROG token-type ZPWY-DDL-SEL-PROG. !r ZPWY-MAP-DEF-PROG token-type ZPWY-DDL-DEF-PROG. !r Tokens in Response Buffer ZPWY-MAP-SEL-PROG token-type ZPWY-DDL-SEL-PROG.
ADD PROG PROG Commands • To specify node-independence for PROG object attributes, specify \* for node names or omit node names and set ZNODEINDEPENDENT to ON in the TS/MP START PATHWAY command.
ADD PROGTERM PROG Commands ADD PROGTERM Use the ADD PROGTERM command to add all of the attributes that define a given device type supported by a PROG object. Continuation You cannot use continuation with this command to add more than one PROGTERM; you must add each PROGTERM object separately. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-36. For descriptions of tokens and fields, see Section 4 through Section 6.
ADD PROGTERM PROG Commands For descriptions of error-token values and their associated error lists, see Section 11, TCP Event Messages and Section 12, TCP Error Messages. Considerations • • • An ADD PROG command must already have been issued for the PROG object before you issue the ADD PROGTERM command. Before adding a PROGTERM object to the PATHMON configuration file, you must assign values to all of the required fields listed in this command.
ALTER PROG PROG Commands ALTER PROG Use the ALTER PROG command to change the attribute values of a PROG object description that was previously added to the PATHMON configuration file. Continuation You cannot use continuation with this command to alter more than one PROG object description; you must alter each PROG object description separately. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-36.
ALTER PROG PROG Commands • For ALTER commands, the values for tokens and fields omitted from the command buffer remain unchanged. Reset values for each field are predefined. These values are described in Section 3, SPI Programming Considerations. To reset ZPRINTERFILE using the TACL program, you must use the #SETBYTES built-in function. See the SPI Programming Manual for more information.
ALTER PROGTERM PROG Commands ALTER PROGTERM Use the ALTER PROGTERM command to change the attributes that define a given device type supported by a PROG object. Continuation You cannot use continuation with this command to alter more than one PROGTERM object; you must alter each PROGTERM separately. Command Syntax For tokens that may be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-36. For descriptions of tokens and fields, see Section 4 through Section 6.
PROG Commands ALTER PROGTERM new PROG. To avoid generating this error, define and add the maximum number of PROG entries allowed, minus 1 (that is, 4094 programs). • For ALTER commands, the values for tokens and fields omitted from the command buffer remain unchanged. Reset values for each field are predefined. These values are described in Section 3, SPI Programming Considerations. To reset ZPRINTERFILE using the TACL program, you must use the #SETBYTES built-in function.
DELETE PROG PROG Commands DELETE PROG Use the DELETE PROG command to remove a PROG object description from the PATHMON configuration file and all PROGTERM definitions associated with the PROG object. Continuation To delete all PROG object descriptions, initialize the ZPROGRAM field in ZPWY-DDLSEL-PROG to ZPWY-VAL-ALLPROG. Reissue the command repeatedly, using the context token returned by the PATHMON process, until no data is returned in the response buffer.
DELETE PROGTERM PROG Commands DELETE PROGTERM Use the DELETE PROGTERM command to remove a device-type definition associated with a given PROG object. Continuation To delete all device-type definitions associated with a PROG object without deleting the PROG object definition itself, initialize the ZPROGRAM field in ZPWY-DDL-SELPROGTERM to the PROG name and assign ZPWY-VAL-ALLTERMTYPE to the ZTERMTYPE field.
PROG Commands • DELETE PROGTERM If you want to delete the PROG object definition and all associated PROGTERM objects, issue a DELETE PROG command. You do not have to issue a DELETE PROGTERM command if you issue a DELETE PROG command because the DELETE PROG command deletes all associated PROGTERM objects.
INFO PROG PROG Commands INFO PROG Use the INFO PROG command to obtain the attribute values defined in the PATHMON configuration file for a PROG object. Continuation To obtain information about all PROG object descriptions, initialize the ZPROGRAM field in ZPWY-DDL-SEL-PROG to ZPWY-VAL-ALLPROG. Reissue the command repeatedly, using the context token returned by the PATHMON process, until no data is returned in the response buffer. For more information, see Specifying Continuation on page 3-21.
INFO PROG PROG Commands object. These values include the attribute values you explicitly defined for the PROG object in ZPWY-DDL-DEF-PROG and the remaining attributes with default values. • To obtain the default values for PROG object attributes, issue the INFO PROG command and assign a null value to the ZPROGRAM field in ZPWY-DDL-SELPROG. The SPI requester can use the default values to implement the equivalent of a PATHCOM SHOW PROGRAM command issued before any PROGRAM attributes are set.
INFO PROGTERM PROG Commands INFO PROGTERM Use the INFO PROGTERM command to return the attribute values defined in the PATHMON configuration file for a device type associated with a given PROG object. Continuation To obtain information on all PROGTERM definitions associated with a given PROG object, initialize the ZPROGRAM field in ZPWY-DDL-SEL-PROGTERM to the PROG name and initialize the ZTERMTYPE field to ZPWY-VAL-ALLTERMTYPE.
INFO PROGTERM PROG Commands values for the specified PROGTERM definition. These values include the attribute values that you explicitly defined for the PROGTERM in ZPWY-DDL-DEFPROGTERM and the remaining attributes with default values. • To obtain the default values for PROGTERM attributes, issue the INFO PROGTERM command and assign null values to the ZTERMTYPE and ZPROGRAM fields in ZPWY-DDL-SEL-PROGTERM.
START PROG PROG Commands START PROG Use the START PROG command to initiate the execution of a SCREEN COBOL program on a device interoperating with your PATHMON environment. When this command is executed, the PATHMON process performs the following: 1. Creates a temporary TERM object entry based on the configuration information in the PROG object template. Assigns an object name beginning with a number to distinguish it from configured TERM objects. 2. If necessary, starts the TCP that controls the device.
START PROG PROG Commands Tokens in Response Buffer ZPWY-MAP-SEL-PROG token-type ZPWY-DDL-SEL-PROG. ZPWY-MAP-STARTPROG token-type ZPWY-DDL-STARTPROG. ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT. !r Tokens in Response Buffer ZSPI-TKN-RETCODE For START PROG, common error values for ZSPI-TKN-RETCODE are: Error Number Error Token Description 1052 ZPWY-ERR-PM-TCPNOTDEFINED The TCP named in the PROG object’s definition is not configured.
START PROG PROG Commands ZPWY-DDL-PAR-START-PROG. If you do not specify a different name, the SCREEN COBOL program and the application program may contend for the same device. • • • The START PROG command can cause a TCP to be started. When a PROG object completes, if a TCP was started as a result of any START PROG command and no TERM objects are running in the TCP, the TCP is stopped. If the TCP stops, any properly coded server process that has links only from that TCP also stops.
START PROG PROG Commands NonStop Pathway/iTS Management Programming Manual—426749-002 9- 20
10 Tell Message Commands This section provides complete descriptions of the commands that enable you to define and control messages that TCPs display. These messages are displayed only to operators who are using devices associated with configured TERM objects and temporary TERM objects created with the START PROG command. The issuing of tell messages is controlled by the SCREEN COBOL TELL-ALLOWED special register.
ADD TELL Tell Message Commands Command ZPWY-CMD-ADD Object Type ZPWY-OBJ-TELL Tokens in Command Buffer ZPWY-MAP-DEF-TELL token-type ZPWY-DDL-DEF-TELL. !r Tokens in Response Buffer ZPWY-MAP-TELLNUM token-type ZPWY-DDL-TELLNUM. ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT. Tokens in Response Buffer ZSPI-TKN-RETCODE For ADD TELL, a common error value for ZSPI-TKN-RETCODE is: Error Number Error Token Description 1107 ZPWY-ERR-PM-TOOMANYTELL The ZMAXTELLS value was reached.
DELETE TELL Tell Message Commands DELETE TELL Use the DELETE TELL command to delete a pending tell message. Continuation You cannot use continuation with this command to delete all tell messages; you must explicitly delete each tell message by number. Command Syntax For tokens that might be present in the command and response buffers but are not listed, see Unlisted Tokens on page 3-36. For descriptions of tokens and fields, see Section 4 through Section 6.
INFO TELL Tell Message Commands INFO TELL Use the INFO TELL command to obtain the text of a pending tell message. Continuation To obtain information on all tell messages, initialize the ZNUMBER field in ZPWY-MAP-SEL-TELL to ZPWY-VAL-ALLTELL. Reissue the command repeatedly, using the context token returned by the PATHMON process, until no data is returned in the reply buffer. For more information, see Specifying Continuation on page 3-21.
START TELL Tell Message Commands START TELL Use the START TELL command to allow a pending tell message to be delivered to the terminals for which it has been queued by the TELL TERM command. The TCP waits for the terminal operator to complete the current screen before displaying the message, so normal operation is not disrupted.
TELL TERM Tell Message Commands TELL TERM Use the TELL TERM command to display a message on a terminal or set of terminals. The TCP waits for the terminal operator to complete the current screen before displaying the message, so normal operation is not disrupted. Continuation To queue a tell message on all terminals, initialize the ZTERM field in ZPWY-MAP-SEL-TERM to ZPWY-VAL-ALLTERM.
TELL TCPTERM Tell Message Commands ZMAXTELLQUEUE field in ZPWY-DDL-DEF-PATHWAY. See the START PATHWAY command description in TS/MP Management Programming Manual for more details. • • When you issue a TELL command, the tell message is assigned a number between zero and the value of the ZMAXTELLS field in ZPWY-DDL-DEFPATHWAY. For the complete sequence for displaying a tell message, see Programming Considerations for Specific Object Types on page 3-32.
TELL TCPTERM Tell Message Commands Tokens in Response Buffer ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. ZPWY-MAP-SEL-TCPTERM token-type ZPWY-DDL-SEL-TCPTERM. Consideration For the complete sequence for displaying a tell message, see Programming Considerations for Specific Object Types on page 3-32.
11 TCP Event Messages This section describes event messages reported by TCPs. The descriptions are given in ascending order by event number; that is, in ascending order by the ZPWY-EVTvalues. Message Numbers All messages returned by the PATHMON environment are logged by the PATHMON process; however, some messages in some number ranges represent events and errors reported to the PATHMON process by other processes.
TCP Event Messages • • • • Unlisted Tokens The unconditional and conditional tokens that have specific values for that event message. See the TS/MP Management Programming Manual for descriptions of these tokens.
Event-Message Text TCP Event Messages syntax boxes in this section, subject tokens may be presented in the form ZPWY-TKNnnnNAME, where nnn represents one of the following Pathway/iTS object types: LM PMREQUESTER PROG PROGTER SCTCP SCTERM TCP TCPLINK TCPSC TCPTERM TERM TELL For a description of these object types, see Object Types on page 3-6. Object types not listed above are TS/MP objects, described in the TS/MP Management Programming Manual.
TCP Event Messages Error Recovery Error Recovery When an error originates in the SCREEN COBOL program, use the additional eventmessage text to obtain the name, version, and instruction address of the program unit being executed. You can isolate the problem to a paragraph in the source program using the information obtained from the additional event-message text and the compiler listing with a MAP.
Event-Message Range 3000 Through 3999 TCP Event Messages 3001: ZPWY-EVT-TCP-BADPCODE A SCREEN COBOL object file is corrupted, or the SCREEN COBOL compiler generated invalid code. 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 here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-PADDR contains a P-register value. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The terminal is suspended. Recovery. Contact your service provider.
Event-Message Range 3000 Through 3999 TCP Event Messages 3002: ZPWY-EVT-TCP-DEPENDVARTOOBIG The value of a DEPENDING ON data item was larger than the limit specified in the OCCURS clause. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The terminal is aborted; the operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3003: ZPWY-EVT-TCP-BADINDEX The value of a subscript expression is either zero or larger than the limit implied by the OCCURS clause. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The TERM is aborted; the operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3004: ZPWY-EVT-TCP-BADRECOVERY The TCP detected a SCREEN COBOL verb that is not allowed during screen recovery. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3005: ZPWY-EVT-TCP-BADPUPARAMS The TCP detected that the number of parameters passed in the USING clause of a CALL statement did not equal the number of parameters given in the procedure division header of the called program. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3006: ZPWY-EVT-TCP-BADPUPARAMSIZE The TCP detected that the maximum size of a parameter passed in the USING clause of a CALL statement did not equal the maximum size of the corresponding parameter given in the procedure division header of the called program. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3007: ZPWY-EVT-TCP-NOBASEDISPLAY The TCP detected an attempt to perform a screen manipulation before the execution of a DISPLAY BASE statement. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3008: ZPWY-EVT-TCP-BADDATAREF The TCP detected an attempt to reference data outside the SCREEN COBOL program’s local data area. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3009: ZPWY-EVT-TCP-BADSCREENTERM The TCP detected an attempt to execute a SCREEN COBOL program unit compiled for one type of device on an incompatible device. If the device types are compatible, then a Pathway subsystem internal error has occurred. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-PADDR contains a P-register value. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3010: ZPWY-EVT-TCP-TERMFORMAT The TCP detected an error in its terminal’s format routines. 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 here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-PADDR contains a P-register value. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3011: ZPWY-EVT-TCP-BADTERMTYPE The TCP detected an attempt to execute a SCREEN COBOL program unit compiled for one type of device on an incompatible device. If the device types are compatible, then a Pathway subsystem internal error has occurred. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-PADDR contains a P-register value. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3012: ZPWY-EVT-TCP-SCREENNOTDISPLAY The TCP detected that a reference was made to a screen that is not displayed. screen-number identifies the screen; 0 corresponds to the first screen declared in the program source. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-SCREEN contains a SCREEN COBOL screen number, identifying a screen in a program unit. 0 corresponds to the first screen defined in the program source. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message.
Event-Message Range 3000 Through 3999 TCP Event Messages 3013: ZPWY-EVT-TCP-DUPOVERLAY The TCP detected an attempt to display an overlay screen in more than one overlay area at the same time. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3014: ZPWY-EVT-TCP-INVALIDIOPROTOCOL The TCP detected an invalid I/O protocol value; or, 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 here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-PADDR contains a P-register value. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3015: ZPWY-EVT-TCP-ARITHOVERFLOW The TCP detected a data-related error during numeric manipulation. The error can be caused by an overflow, by dividing by zero, by an invalid value in a numeric data item (for example, blank spaces in a USAGE DISPLAY item), or by attempting to move a value into a data item that is not large enough to hold it.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3016: ZPWY-EVT-TCP-STACKOVERFLOW The TCP detected that the limit specified for the ZMAXTERMDATA field was exceeded. bytes indicates the terminal data area length needed at the point of error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-STACKSIZE contains the size, in bytes, of the data stack in a SCREEN COBOL program unit. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3017: ZPWY-EVT-TCP-TERMOPEN A file-system error (errnum) occurred while the TCP was opening the TERM. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
Event-Message Range 3000 Through 3999 TCP Event Messages 3018: ZPWY-EVT-TCP-TERMIO A file-system error (errnum) occurred while the TCP was performing a terminal I/O operation. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-ERROR contains a file-system error number. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The I/O operation fails. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3019: ZPWY-EVT-TCP-TERMIOLEN The number of bytes actually transferred to or from the terminal was not in the allowed range. This might indicate a terminal hardware problem. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The I/O operation fails. Recovery. If a front-end process is being used, check that it is correctly coded to emulate the type of the device specified. If a front-end process is not being used, see Error Recovery on page 11-4 for instructions on how to locate the problem within the program. If this is not a program-related problem, run diagnostics for the device and make any necessary repairs.
Event-Message Range 3000 Through 3999 TCP Event Messages 3020: ZPWY-EVT-TCP-PUNOTDEFINED The program unit specified in a CALL statement could not be found in the TCLPROG files. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3021: ZPWY-EVT-TCP-SENDFAIL A SCREEN COBOL SEND operation to a server failed for the reason indicated in an earlier event message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. If the transaction message was sent to the server, information about how much processing was done by the server before the failure is not available to the system. Recovery. Recovery depends on why the SEND operation failed. For additional information, see the previous event message received.
Event-Message Range 3000 Through 3999 TCP Event Messages 3022: ZPWY-EVT-TCP-BADSCNAME The value specified in a SCREEN COBOL SEND statement did not have the format of a valid server class name. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3023: ZPWY-EVT-TCP-CODETOOBIG The size of the code for a program unit is greater than that allowed by the value of the ZCODEAREALEN field in ZPWY-DDL-DEF-TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The program terminates abnormally. Recovery. Increase the value for the ZCODEAREALEN field. Use the compiler listing for the program unit to determine the minimum size that can be specified for the field.
Event-Message Range 3000 Through 3999 TCP Event Messages 3024: ZPWY-EVT-TCP-BADDIRENTRY The TCLPROG directory file is corrupt. 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 here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The program terminates abnormally. Recovery. Contact your service provider.
Event-Message Range 3000 Through 3999 TCP Event Messages 3025: ZPWY-EVT-TCP-TERMDATAFORMAT The input data received from the TERM did not have the correct structure, even after screen recovery and retries. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The I/O operation fails. Recovery. Run diagnostics for the device. If a front-end process is being used, check that it is correctly coded to emulate the type of the device specified.
Event-Message Range 3000 Through 3999 TCP Event Messages 3027: ZPWY-EVT-TCP-TMFVIOLATION The requested operation did not match the TMF transaction mode state. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3028: ZPWY-EVT-TCP-TMFFATAL A fatal error (errnum) occurred during a call to a TMF procedure. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The call to the TMF procedure fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
Event-Message Range 3000 Through 3999 TCP Event Messages 3029: ZPWY-EVT-TCP-TMFMAXRESTARTS The TCP attempted to restart a transaction more than the number of times defined in the ZMAXTMFRESTARTS field. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The transaction is not restarted. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3030: ZPWY-EVT-TCP-TMFNOTCONFIG An attempt to use TMF software was made, but TMF software is not configured in this system. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. None. Recovery. Configure TMF software or isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3031: ZPWY-EVT-TCP-TMFNOTRUNNING An attempt to use the TMF subsystem was made, but the TMF subsystem is not running in this system. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. None. Recovery. Configure TMF software or isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3032: ZPWY-EVT-TCP-TFILEOPEN A file-system error (errnum) occurred while the TCP backup process was attempting to open the TMF TFILE. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
Event-Message Range 3000 Through 3999 TCP Event Messages 3036: ZPWY-EVT-TCP-TERMERRORDECL An attempt was made to call a program unit with a USE FOR TERMINAL-ERRORS statement from a USE FOR TERMINAL-ERRORS declarative. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The call fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3037: ZPWY-EVT-TCP-BADACCEPTTIMEOUT An invalid value was specified for the timeout parameter in an ACCEPT statement. The value was either less than 0 or too large to be represented in an INT(32) field. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3040: ZPWY-EVT-TCP-BADNUMERIC The referenced field did not contain numeric data. number appears in the DESC column; read across to the left to find the item name that caused this error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-DESCRIPTOR contains a number that indicates the item name that caused the error. The number appears on the compiler MAP listing in the DESC column. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message.
Event-Message Range 3000 Through 3999 TCP Event Messages 3041: ZPWY-EVT-TCP-BADPRINTER Either an invalid device was specified or the printer for the IBM 3270 terminal is not attached to the same control unit as the terminal. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3042: ZPWY-EVT-TCP-PRINTERATTN A file-system error (errnum) occurred during a PRINT SCREEN operation. The error requires intervention by hand. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual .
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-ERROR contains a file-system error number. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The PRINT SCREEN operation terminates abnormally. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3043: ZPWY-EVT-TCP-PRINTERIO A Guardian error occurred during a PRINT SCREEN operation. This I/O error is fatal. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-ERROR contains a file-system error number. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The PRINT SCREEN operation terminates abnormally. Recovery.
Event-Message Range 3000 Through 3999 TCP Event Messages 3044: ZPWY-EVT-TCP-BADPUNAME An invalid program unit name was specified in a CALL statement. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3050: ZPWY-EVT-TCP-STOPBYREQUEST The TERM object was stopped because of a pending stop request. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. None. Recovery. Informational message only; no corrective action is needed.
Event-Message Range 3000 Through 3999 TCP Event Messages 3051: ZPWY-EVT-TCP-SUSPENDBYREQUEST The TERM object was suspended because of a pending suspend request. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Event-Message Range 3000 Through 3999 Effect. None. Recovery. Informational message only; no corrective action is needed.
Event-Message Range 3000 Through 3999 TCP Event Messages 3052: ZPWY-EVT-TCP-STOPBYPROG The TERM object was stopped because it encountered an exit in the highest-level program unit. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. None. Recovery. Informational message only; no corrective action is needed.
Event-Message Range 3000 Through 3999 TCP Event Messages 3053: ZPWY-EVT-TCP-BADNUMERICNODD An operation that does not involve screen presentation, such as an ADD or MOVE operation, attempted to perform a numeric operation using nonnumeric data. %address is the octal address of the instruction that failed. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
Event-Message Range 3000 Through 3999 TCP Event Messages 3054: ZPWY-EVT-TCP-IOPROTOCOLDENIED The I/O protocol is invalid. The value of the ZIOPROTOCOL field was 1, but the frontend process does not support completion of outstanding READ requests as specified in the TCP’s call to the Guardian CONTROL procedure. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-IOPROTOCOL contains the I/O protocol number specified in the TERM configuration. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
TCP Event Messages Event-Message Range 3000 Through 3999 3055: ZPWY-EVT-TCP-BADIOPROTOCOL The I/O protocol specified in the terminal configuration is invalid. A value other than 0 or 1 was specified for the ZIOPROTOCOL field. The PATHMON process reports this error if the invalid value is greater than 15; otherwise, PATHCOM reports error 2011, ILLEGAL NUMBER. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Event-Message Range 3000 Through 3999 ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-IOPROTOCOL contains the I/O protocol number specified in the TERM configuration. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens.
TCP Event Messages 11 TCP Event Messages 3056: ZPWY-EVT-TCP-CACHEFATAL A 6540 terminal device encountered a fatal error while running in caching mode. This situation might be caused by memory parity errors, disk errors, or diskette errors. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The terminal is suspended. Recovery. Issue a RESUME TERM command to correct the situation; however, this will only succeed if the 6540 device error was transient. If the error is not transient, run terminal diagnostics.
TCP Event Messages 3057: ZPWY-EVT-TCP-CACHEMODECHANGE A 6540 terminal that was performing screen caching had an error that forced it to 6530 device emulation. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The caching function is disabled and the 6540 device is emulating a 6530 terminal. Recovery. Check the 6540 terminal for disk errors and other problems.
TCP Event Messages 3058: ZPWY-EVT-TCP-BADPCODEVERSION The SCREEN COBOL pseudocode for the program unit is not compatible with this version of the TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery. Upgrade the TCP you are using to the same version level as the SCOBOLX compiler with which the program unit was compiled.
TCP Event Messages 3059: ZPWY-EVT-TCP-DEVICEINFO A file-system error was returned on a call to the DEVICEINFO procedure. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages 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. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
TCP Event Messages 3060: ZPWY-EVT-TCP-NODBCSSUPPORT The terminal task that the TCP is attempting to communicate with has been aborted for one of the following reasons: • • • An attempt was made to run a SCREEN COBOL program unit containing doublebyte characters on an IBM 3270 device or emulator that does not support Start Field Extended (SFE) orders.
TCP Event Messages 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-ERROREVENT. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery.
TCP Event Messages 3061: ZPWY-EVT-TCP-NODBCSINSTALLED An attempt was made to run a SCREEN COBOL program unit containing double-byte characters on a system that does not have the correct set of procedures for the support of double-byte character sets. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery.
TCP Event Messages 3062: ZPWY-EVT-TCP-BADDBCSKKDATA1 Translation routines were unable to correctly translate data from internal format to the external format required by the device. descriptor-number identifies the field in error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-DESCRIPTOR contains the number of a SCREEN COBOL data item. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery. Abort the terminal from the Pathway subsystem.
TCP Event Messages 3063: ZPWY-EVT-TCP-BADDBCSKKDATA2 Translation routines were unable to correctly translate data from the internal format to the external format required by the device. inst-addr identifies the SCREEN COBOL operand that encountered the problem. This is the same error as reported by 3062, except that, for internal reasons, the data descriptor number is not available for reporting in the message. The offset can be mapped to the SCOBOLX verb that failed if the compiler ?MAP directive is used.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery. Abort the terminal from the Pathway subsystem.
TCP Event Messages 3064: ZPWY-EVT-TCP-DATATRUNCATION The TCP displayed a truncated data item. Truncation can occur with double-byte character data items that equal the maximum field length specified. A screen field containing double-byte characters was truncated for one of the following reasons: • • • Insertion of Shift In-Shift Out characters into a data stream being sent to an IBM device caused the number of displayable characters to exceed the field size.
TCP Event Messages 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-INFOEVENT. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. None. Recovery.
TCP Event Messages 3065: ZPWY-EVT-TCP-NOKATAKANALLOWED1 An attempt was made to run a SCREEN COBOL program unit containing Katakana data on a device that does not support Katakana data. descriptor-number identifies the field in error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-DESCRIPTOR contains the number of a SCREEN COBOL data item. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery.
TCP Event Messages 3066: ZPWY-EVT-TCP-NOKATAKANALLOWED2 An attempt was made to run a SCREEN COBOL program unit containing Katakana data on a device that does not support Katakana data. inst-addr identifies the SCREEN COBOL operand that encountered the problem. This is the same error as reported by 3065, except that, for internal reasons, the data descriptor number is not available for reporting in the message.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery. Abort the terminal from the Pathway subsystem and either upgrade the terminal to support the application data or modify the requester-server application to conform to the device environment.
TCP Event Messages 3067: ZPWY-EVT-TCP-NOTDBCSDATA1 The TCP encountered a data field that did not contain only double-byte (Kanji) character data. The SCREEN COBOL programmer has attempted to display mixed or single-byte characters in a PIC N only screen field, or to display a mixed field on an IBM 3270 device that does not support mixed fields. descriptor-number identifies the field in error.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-DESCRIPTOR contains the number of a SCREEN COBOL data item. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery.
TCP Event Messages 3068: ZPWY-EVT-TCP-NOTDBCSDATA2 The TCP encountered a data field that did not contain only double-byte (Kanji) character data. The SCREEN COBOL programmer has attempted to display mixed or single-byte characters in a PIC N only screen field, or to display a mixed field on an IBM 3270 device that does not support mixed fields. inst-addr identifies the SCREEN COBOL operand that encountered the problem.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates abnormally. Recovery.
TCP Event Messages 3069: ZPWY-EVT-TCP-UNILATERALABORT A terminal task has been suspended because the backup TCP encountered a backup open error for the terminal task identified by term-name. This message is logged when the following sequence of events occurs: 1. The backup TCP marks the terminal task as suspended but does not delete it until the ABORT TERM command is executed. 2. The backup TCP sends a request to the primary TCP to suspend the corresponding primary terminal task.
TCP Event Messages 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-ERROREVENT. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect.
TCP Event Messages 3070: ZPWY-EVT-TCP-BACKUPOPENERROR A TERM task has been suspended because the backup TCP encountered a backup open error for the TERM task identified by term-name. This message is logged when the following sequence of events occurs: 1. The backup TCP marks the TERM task as suspended but does not delete it until the ABORT TERM command is executed. 2. The backup TCP sends a request to the primary TCP telling it to suspend the corresponding primary TERM task.
TCP Event Messages 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. ZPWY-TKN-ERROR contains a file-system error number. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message.
TCP Event Messages 3071: ZPWY-EVT-TCP-TERMNOTCAPABLE The terminal does not have the attribute or color capability specified by the running SCREEN COBOL program unit. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The TERM object is terminated abnormally. Recovery. Upgrade the terminal to support the application data or modify the requester-server application to conform to the device’s limits.
TCP Event Messages 3072: ZPWY-EVT-TCP-ILLRUNTIMEATTRS During the run-time processing of a control structure associated with a CONTROLLED clause, an invalid token name or an invalid value has been detected, or the specified token count has caused an out-of-bounds condition to occur. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-PUNAME contains the name of the program unit executing at the time the error was detected. ZPWY-TKN-PUOFFSET contains the offset into the program unit at which the instruction is located. ZPWY-TKN-PUVERSION contains the version of the program unit executing at the time the error was detected. ZPWY-TKN-TCLPROGFNAME contains the name of the SCREEN COBOL pseudocode file. Effect. The SCREEN COBOL program is suspended. Recovery.
TCP Event Messages 3073: ZPWY-EVT-TCP-INSUFFTERMPOOL A SCREEN COBOL statement required a larger terminal input buffer than was configured. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages ZPWY-TKN-INSTRUCTION contains the instruction executing at the time the error was detected. ZPWY-TKN-PUNAME contains the name of the program unit executing at the time the error was detected. ZPWY-TKN-PUOFFSET contains the offset into the program unit at which the instruction is located. ZPWY-TKN-PUVERSION contains the version of the program unit executing at the time the error was detected. ZPWY-TKN-TCLPROGFNAME contains the name of the SCREEN COBOL pseudocode file. Effect.
TCP Event Messages 3074: ZPWY-EVT-TCP-ILLEGALDELAY An invalid DELAY variable timeout value was used. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-TCPNAME. ZSPI-TYP-ENUM.
TCP Event Messages ZPWY-TKN-PUNAME contains the name of the program unit executing at the time the error was detected. ZPWY-TKN-PUOFFSET contains the offset into the program unit at which the instruction is located. ZPWY-TKN-PUVERSION contains the version of the program unit executing at the time the error was detected. ZPWY-TKN-TCLPROGFNAME contains the name of the SCREEN COBOL pseudocode file. Effect. The terminal task is suspended. Recovery.
TCP Event Messages 3100: ZPWY-EVT-TCP-SCPROCESSOPEN A file-system error (errnum) occurred while the TCP was opening a server process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The OPEN operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Event Messages 3101: ZPWY-EVT-TCP-DIROPEN A file-system error (errnum) occurred while the TCP was opening the TCLPROG directory file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The OPEN operation fails. Recovery.
TCP Event Messages 3102: ZPWY-EVT-TCP-CODOPEN A file-system error (errnum) occurred while the TCP was opening the TCLPROG code file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The OPEN operation fails. Recovery.
TCP Event Messages 3103: ZPWY-EVT-TCP-BADDIR The format of the file specified as the TCLPROG directory file is invalid. 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 here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
TCP Event Messages 3104: ZPWY-EVT-TCP-BADCOD The format of the file specified as the TCLPROG code file is invalid. 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 here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
TCP Event Messages 3106: ZPWY-EVT-TCP-CONFIGTOOBIG The TCP configuration parameter values are incorrect. This is usually caused by incompatible values for two of the following fields: ZTERMBUF, ZTERMPOOL, ZMAXTERMDATA, ZSERVERPOOL, ZMAXREPLY, and possibly ZMAXTERMS, ZMAXSERVERCLASSES, and ZMAXSERVERPROCESSES. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3107: ZPWY-EVT-TCP-SWAPCREATE A file-system error (errnum) occurred while the TCP was attempting to obtain swap space from the Kernel Managed Swap Facility (KMSF). errnum is a negative value from -1 to -10 returned by the Guardian ALLOCATESEGMENT procedure. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The swap space is not obtain from the KMSF. Recovery.
TCP Event Messages 3108: ZPWY-EVT-TCP-SWAPOPEN A file-system error (errnum) occurred while the specified TCP was opening a swap file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The swap file is not opened. Recovery.
TCP Event Messages 3109: ZPWY-EVT-TCP-SWAPIO A file-system error (errnum) occurred during an I/O operation to a swap file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Event Messages 3110: ZPWY-EVT-TCP-MAXSC An attempt was made to communicate with more server classes than the value of the ZMAXSERVERCLASSES field in ZPWY-DDL-DEF-TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The SEND operation to the server class fails. Recovery. Redefine the value of the ZMAXSERVERCLASSES field or reattempt the SEND operation when a request in progress completes.
TCP Event Messages 3112: ZPWY-EVT-TCP-REPLYNOTDEFINED A server reply message includes a reply code not listed in the SEND statement of the program. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3113: ZPWY-EVT-TCP-SENDTOOBIG The size of the SEND message exceeded the size allowed by the value of the ZSERVERPOOL field in ZPWY-DDL-DEF-TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Redefine the value of the ZSERVERPOOL field or isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3114: ZPWY-EVT-TCP-MAXREPLY The size of either the largest SEND message or the longest possible reply exceeds the size allowed by the value of the ZMAXREPLY field in ZPWY-MAP-DEF-TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Redefine the value of the ZMAXREPLY field or isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3115: ZPWY-EVT-TCP-BADREPLYLENGTH The size of the reply received from the server did not correspond to the size of the selected YIELDS list given in the SEND statement of the program. byte-length is the length of the reply received, in bytes. The TCP returns the number of bytes received from the server. If the reply exceeds the largest number of bytes allowed, the TCP reports the byte count as the largest allowed reply length, plus 1.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-MESSAGELENGTH contains the size in bytes of a message resulting from a SCREEN COBOL SEND statement. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect.
TCP Event Messages 3116: ZPWY-EVT-TCP-SCPROCESSIO A file-system error (errnum) occurred during an I/O operation to a server process. This event can be triggered by either the TCP or the TS/MP LINKMON process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The I/O operation fails; the TCP or LINKMON process returns the links it has to the server class. Recovery.
TCP Event Messages 3117: ZPWY-EVT-TCP-SCNOTDEFINED The server class specified in a SEND statement is not defined for the Pathway subsystem. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message; these tokens are included only if the subject token is ZPWY-TKN-TERMNAME. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Event Messages 3118: ZPWY-EVT-TCP-BADSCSTATE The state of the specified server does not allow the requested operation to take place. This is a Pathway internal error. This event can be triggered by either the TCP or the TS/MP LINKMON process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3119: ZPWY-EVT-TCP-MAXSCPROCESS The value configured for the ZMAXSERVERPROCESSES field in ZPWY-MAP-DEFTCP was exceeded. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages 3121: ZPWY-EVT-TCP-DIRIO A file-system error (errnum) occurred during an I/O operation to the TCLPROG directory file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Event Messages 3122: ZPWY-EVT-TCP-CODIO A file-system error (errnum) occurred during an I/O operation to the TCLPROG code file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The I/O operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Event Messages 3123: ZPWY-EVT-TCP-NOSCPROCESS The TCP could not link to a server. The SCREEN COBOL run unit was waiting for a link to a server class when the server class became unavailable. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The SEND operation fails. Recovery. Recovery depends on why the SEND failed, which is indicated in an earlier message. For additional information, see the description of the earlier message.
TCP Event Messages 3124: ZPWY-EVT-TCP-EXITWITHERROR A SCREEN COBOL program executed an EXIT PROGRAM WITH ERROR verb with no higher-level CALL ON ERROR verb present to handle the exit. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-TERMINATIONSTATUS contains the value from the SCREEN COBOL TERMINATION-STATUS special register. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The program terminates. Recovery.
TCP Event Messages 3125: ZPWY-EVT-TCP-UNSOLREJECTEDSTOP The TCP rejected unsolicited messages that were queued for a terminal when the terminal was stopped, suspended, or aborted, either programmatically or by an operator command. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-UNSOLCOUNT contains the count of unsolicited messages. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The unsolicited messages are rejected. Recovery.
TCP Event Messages 3140: ZPWY-EVT-TCP-ROUTIO A file-system error occurred during an I/O operation to the router process performed by the terminal control process (TCP) on behalf of the specified TERM object. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The I/O operation fails and the TERM object is aborted. Recovery. Ensure that the router process is running. Then stop and restart the TERM object.
TCP Event Messages 3141: ZPWY-EVT-TCP-SOCKERR A TCP/IP file-system error occurred during a socket function call performed by the terminal control process (TCP) on behalf of the specified TERM object. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The socket function call fails; however, the TERM object is not aborted or stopped. The TCP issues a new connection request to the router process. Recovery. Informational message only; no corrective action is needed.
TCP Event Messages 3142: ZPWY-EVT-TCP-ROUTRTCPLIM A newly created terminal control process (TCP) sent its first “waiting for connection” request to the router process on behalf of the specified TERM object. However, the router could not handle the request because it was already servicing the maximum number of TCP processes (800). For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. All the TERM objects configured under the TCP that made the “waiting for connection” request are aborted. Recovery. Change the FILE attribute of each of the suspended TERM objects to point to another router process.
TCP Event Messages 3143: ZPWY-EVT-TCP-ROUTRTRMLIM The sum of the number of TERM object requests for connection queued to the router process and the number of TERM objects currently connected to clients (that is, “in session”) has reached the maximum limit (32767). For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The specified TERM object is aborted. Recovery. Wait for a period of time (how long a time depends on the application) and then stop and restart the TERM object.
TCP Event Messages 3144: ZPWY-EVT-TCP-ROUTRMEMALC A memory allocation error occurred within the router process while the router was maintaining connection request status information for the TERM objects. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Effect. The router process terminates abnormally. The TERM objects that were waiting for connections resend their requests to the router process. Recovery. Restart the router process.
TCP Event Messages 3145: ZPWY-EVT-TCP-SESSIONCRETERR An error occurred when the terminal control process (TCP) attempted to create a session after establishing a socket connection with the client. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Effect. For the TERM object, the socket connection with the client is broken, the socket is closed, and a new “waiting for connection” request is made to the router process. Recovery. Informational message only; no corrective action is needed.
TCP Event Messages 3146: ZPWY-EVT-TCP-PROTOCOLERROR The communication protocol that the client used is not supported by Pathway/iTS. Pathway/iTS supports the HTTP and TCP/IP Raw Socket protocols. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Effect. The operation fails, the session is closed, and the TERM object is reinitialized for a new session. Recovery. If the router process was not started with the protocol parameter set to HTTP or SOCKET, restart the router process with one of these protocol settings.
TCP Event Messages 3147: ZPWY-EVT-TCP-SESSIONISNULL The TCP/IP session associated with the socket connection was null when the terminal control process (TCP) either performed an I/O operation on the socket or attempted to delete it. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation (send to/receive from the client or session deletion) fails. The session is closed and the TERM object is reinitialized for a new session. Recovery. Informational message only; no corrective action is needed.
TCP Event Messages 3148: ZPWY-EVT-TCP-NWSENDERROR A TCP/IP file-system error occurred during a nowait socket send operation to the client. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the TCP/IP file-system error that occurred. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The send operation fails.
TCP Event Messages 3149: ZPWY-EVT-TCP-XMLGENERATION The terminal control process (TCP) received an error in generating an Extended Markup Language (XML) document while sending a message to the browser-based client. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The send operation to the client fails. The session is closed and the TERM object is reinitialized for a new session. Recovery. Informational message only; no corrective action is needed.
TCP Event Messages 3150: ZPWY-EVT-TCP-NWRECVERROR A TCP/IP file-system error occurred during a nowait receive operation on a socket. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The receive operation fails. The session is closed and the TERM object is reinitialized for a new session. Recovery. Informational message only; no corrective action is needed.
TCP Event Messages 3161: ZPWY-EVT-TCP-MSGIO A file-system error (errnum) occurred during a SEND MESSAGE operation or during a REPLY TO UNSOLICITED MESSAGE operation. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
TCP Event Messages 3162: ZPWY-EVT-TCP-RCVDMSGTOOSMALL The message received from a RECEIVE UNSOLICITED MESSAGE operation, a TRANSFORM operation, or a SEND MESSAGE operation was smaller than allowed. byte-length is the length of the message received in bytes. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-MESSAGELENGTH contains the size, in bytes, of a message resulting from a SCREEN COBOL SEND statement. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
TCP Event Messages 3163: ZPWY-EVT-TCP-RCVDMSGTOOBIG The message received from a RECEIVE UNSOLICITED MESSAGE operation, a TRANSFORM operation, or a SEND MESSAGE operation was larger than allowed; a data overflow occurred. byte-length is the number of bytes the TCP received. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-MESSAGELENGTH contains the size, in bytes, of a message resulting from a SCREEN COBOL SEND statement. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery.
TCP Event Messages 3164: ZPWY-EVT-TCP-MSGCODENOTDEFINED The message received from a RECEIVE UNSOLICITED MESSAGE operation or as a reply to a SEND MESSAGE operation is undefined because the message code did not match any of the reply codes specified in the YIELDS or SELECT list. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. See the TS/MP Management Programming Manual for descriptions of these tokens. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages NonStop Pathway/iTS Management Programming Manual—426749-002 11- 202
TCP Event Messages 11 TCP Event Messages 3165: ZPWY-EVT-TCP-EDITERRORINPUT An edit error occurred on input from an intelligent device. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3167: ZPWY-EVT-TCP-MSGEXCEEDSCONFIG After conversion of message data from an unsupported format to a supported format, the message to be sent or received with a SEND MESSAGE statement was larger than the maximum number of bytes supported by the buffer. byte-length is the length of the received message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-MESSAGELENGTH contains the size, in bytes, of a message resulting from a SCREEN COBOL SEND statement. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect.
TCP Event Messages 3168: ZPWY-EVT-TCP-BADDEVICESUBTYPE The device subtype value (subtype) specified for an intelligent device is invalid. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-DEVICESUBTYPE contains the device subtype that was specified by the TYPE parameter in the TERM configuration. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery.
TCP Event Messages 3169: ZPWY-EVT-TCP-BADTIMEOUTVALUE The SCREEN COBOL program unit specified an invalid timeout value (timeout). The value was either less than 0 or too large to be represented in an INT(32) field. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-TIMEOUTVALUE contains the timeout value, in micro-seconds, that was used. N indicates that this token can occur in a nested error message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Event Messages 3170: ZPWY-EVT-TCP-BADENDOFMSG An invalid end-of-message character was encountered in an intelligent device message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3171: ZPWY-EVT-TCP-FIELDTOOBIG The length of a field in an intelligent device message exceeded the maximum number of bytes allowed. byte-length represents the number of bytes in the field For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-FIELDLENGTH contains the size in bytes of a SCREEN COBOL field. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Event Messages 3172: ZPWY-EVT-TCP-MSGTOOBIG After conversion of message data from an unsupported format to a supported format, the message length exceeded the maximum number of bytes allowed for all messages. byte-length represents the number of bytes in the message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-MESSAGELENGTH contains the size in bytes of the message. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. If the user conversion routine is causing the error, correct the routine.
TCP Event Messages 3173: ZPWY-EVT-TCP-CTL26ERROR A file-system error (errnum) occurred during a CONTROL-26 operation to the TERM. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery.
TCP Event Messages 3174: ZPWY-EVT-TCP-CTL26TIMEOUT A timeout occurred during a CONTROL-26 operation to the TERM. The operation did not complete within 60 seconds. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. If a front-end process is being used, verify that it handles CONTROL-26 properly.
TCP Event Messages 3175: ZPWY-EVT-TCP-EDITERROROUTPUT An edit error occurred on output to an intelligent device. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4. If a USER CONVERSION clause is used in the program, check the user conversion routine.
TCP Event Messages 3176: ZPWY-EVT-TCP-UNSOLNOTREPLIED A SCREEN COBOL program unit attempted to receive an unsolicited message before replying to a previously received unsolicited message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3177: ZPWY-EVT-TCP-UNSOLNONETOREPLY A SCREEN COBOL program unit attempted to reply to an unsolicited message that when there was no pending unsolicited message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The reply attempt fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3178: ZPWY-EVT-TCP-MAXINPUTMSGSZERO A SCREEN COBOL program unit attempted to receive an unsolicited message, but the terminal was not configured for unsolicited messages. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Configure the ZMAXIMPUTMSGS field for the associated TERM or PROG object to a value greater than zero.
TCP Event Messages 3179: ZPWY-EVT-TCP-TOOMUCHDATA A SCREEN COBOL program unit attempted to execute the TRANSFORM verb, but there was data left unprocessed from the source data stream. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3180: ZPWY-EVT-TCP-NOTENOUGHDATA A SCREEN COBOL program unit tried to execute the TRANSFORM verb, but there was not enough data in the source data stream to meet the requirements of the destination data items. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3181: ZPWY-EVT-TCP-BADFIELDSIZE A field being processed during delimited field processing was larger than the maximum size specified in the declaration. This situation is disallowed only on output processing through the message section. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3182: ZPWY-EVT-TCP-DELIMNOTALIGNED The delimiter’s offset was not byte-aligned during delimited field processing. Consequently, a delimiter either cannot be appended to the field in an outbound message or cannot be found in the input data stream of an inbound message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3183: ZPWY-EVT-TCP-BADDEPENDVALUE The value of a DEPENDING ON data item in the message section was larger than the limit specified in the OCCURS clause. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3184: ZPWY-EVT-TCP-PIFCONFLICT The data type of the control field for PRESENT IF processing conflicts with the data supplied for its value. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-FIELDOFFSET contains the byte offset of a field from the beginning of the message. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Event Messages 3185: ZPWY-EVT-TCP-MAXWSOCCURS The message section definition cannot support the structure in working storage. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-FIELDOFFSET contains the byte offset of a field from the beginning of the message. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Event Messages 3197: ZPWY-EVT-TCP-DUMPNOTTAKEN The TCP encountered an internal error (errnum) and its memory dump failed. The values for errnum are: • • 1 to 512 are file-system errors. 1000 to 1512 are fatal file errors that, during the dump operation, cause the TCP to abend. • -1 to -9 are errors that prevent the TCP dump operation. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-EVENTCLASS has a value of ZPWY-VAL-ERROREVENT. ZPWY-TKN-DUMPERROR contains PATHMON internal information describing the reason for the dump failure. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The memory dump fails.
TCP Event Messages 3200: ZPWY-EVT-TCP-BADPMTCPMSG The specified TCP or LINKMON process received an invalid request from the PATHMON process. This is an internal Pathway failure generally caused by running versions of the PATHMON process incompatible with the TCP or LINKMON process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3201: ZPWY-EVT-TCP-BADSYNCID A TCP or LINKMON process received an invalid message synchronous ID (SYNCID). This is a TCP internal error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
TCP Event Messages 3202: ZPWY-EVT-TCP-TERMUNKNOWN The TCP encountered an unknown terminal identifier. This is a TCP internal error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages 3203: ZPWY-EVT-TCP-SCOBOLFNS The TCP does not support the SCREEN COBOL function that was used. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages Effect. The SCREEN COBOL program cannot be executed. Recovery. Use a more recent version of the TCP.
TCP Event Messages 3209: ZPWY-EVT-TCP-NOMICRO The microcode required to operate the Pathway subsystem is not installed. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-TCPNAME.
TCP Event Messages 3210: ZPWY-EVT-TCP-BUCPUDOWN The processor for the backup TCP has failed. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-TCPNAME. ZSPI-TYP-ENUM.
TCP Event Messages 3211:ZPWY-EVT-TCP-BUCREATEFAIL An error occurred while the operating system was attempting to create the TCP’s backup process using the NEWPROCESS procedure. process-creation-detail provides more information about the failure. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS BOOLEAN.
TCP Event Messages process-creation-detail (continued) ILLEGAL HOME TERMINAL (file-system error) FILE SYSTEM ERROR ON HOME TERMINAL (file-system error) OBJECT FILE HAS ILLEGAL DEVICE SUBTYPE PROCESS DEVICE SUBTYPE IN BACKUP NOT EQUAL PRIMARY format-file-type is one of the following: PROGRAM LIBRARY format-error is one of the following: NOT A DISK FILE NOT FILE CODE 100 NOT CORRECT FILE STRUCTURE REQUIRES LATER VERSION OF GUARDIAN NO MAIN PROCEDURE LIB FILE HAS MAIN PROCEDURE NO DATA PAGES INVALID PEP HEADE
TCP Event Messages ZPWY-TKN-NEWPROCERROR contains the number of the process creation error. N indicates that this token can occur in a nested message. ZPWY-TKN-NEWPROCRESULT, ZPWY-TKN-NEWPROCFORMATFILETYPE, ZPWY-TKN-NEWPROCFORMATERROR, and ZPWY-TKN-PROCCREATRESULT are reserved tokens for internal use only. N indicates that these tokens can occur in a nested message. For more information on these tokens, see the TS/MP Management Programming Manual. Effect.
TCP Event Messages 3212: ZPWY-EVT-TCP-BUFAIL The backup process of the TCP failed for an unknown reason. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-TCPNAME. ZSPI-TYP-ENUM.
TCP Event Messages 3213: ZPWY-EVT-TCP-BUOPEN A file-system error (errnum) occurred while the TCP was trying to open a file to the backup process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages ZPWY-TKN-ERROR contains the number of a file-system error. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery.
TCP Event Messages 3214: ZPWY-EVT-TCP-CHECKPOINT A file-system error (errnum) occurred during a CHECKPOINT operation. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-TCPNAME.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The CHECKPOINT operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Event Messages 3215: ZPWY-EVT-TCP-BUERROR An error occurred in the backup processor for the reason described in nestedmessage. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages 3216: ZPWY-EVT-TCP-INTERNAL An internal TCP failure occurred.%p-reg is the value of the P-register at the time of the failure. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The TCP terminates. This message may or may not be reported to the PATHMON process and written to the LOG1, but this message is written to the $0 collector process. Recovery. Contact your service provider.
TCP Event Messages 3217: ZPWY-EVT-TCP-TRAPPED A trap occurred in the TCP because of a hardware or software failure. This is a TCP internal error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The TCP terminates. This message may or may not be reported to the PATHMON process and logged. The message, with the addition of the trap number, is written to the $0 collector process. Recovery. Contact your service provider.
TCP Event Messages 3218: ZPWY-EVT-TCP-BUTAKEOVER The backup process took over processing from the primary process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL. ZPWY-TYP-TCPNAME.
TCP Event Messages 3219: ZPWY-EVT-TCP-DUMPTAKEN A TCP memory dump occurred. file-name specifies the name of the dump file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages 3226: ZPWY-EVT-TCP-PMTCPFNS The PATHMON process requested a function not supported in this version of the TCP or LINKMON process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-nnnNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages 3227: ZPWY-EVT-TCP-BADPMNAME The PATHMON name given in a SCREEN COBOL SEND statement is not in the correct form; for example, the first character is not a dollar sign ($). For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3228: ZPWY-EVT-TCP-BADSYSNAME The system name given in a SCREEN COBOL SEND statement is not in the correct form; for example, the first character is not a backslash (\). For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3229: ZPWY-EVT-TCP-SYSNOTDEFINED The SCREEN COBOL SEND statement does not contain a NonStop system name or the system name is not identified to the network. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3230: ZPWY-EVT-TCP-MAXPM A request requires the TCP to contact an external PATHMON process, but the number of PATHMON processes with which the TCP can communicate has been reached. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery. Try the SEND operation again or increase the value defined for the ZMAXPATHWAYS field in ZPWY-MAP-DEF-TCP.
TCP Event Messages 3231: ZPWY-EVT-TCP-PMIO An error (errnum) occurred during an OPEN or WRITEREAD operation to an external PATHMON process. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. 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.
TCP Event Messages ZPWY-TKN-ERROR contains the number of the file-system error. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The operation fails. Recovery.
TCP Event Messages 3232: ZPWY-EVT-TCP-TERMDATATOOBIG The TCP received a request that required more data space than what is defined by the ZMAXTERMDATA field in ZPWY-DDL-DEF-TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3233: ZPWY-EVT-TCP-SPUNKNOWN The TCP or LINKMON process received a message from the PATHMON process containing a reference to a server process that is unknown to the TCP or LINKMON process. This is a TCP internal error. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3235: ZPWY-EVT-TCP-CODEAREATHRASHING The TCP is replacing excessive amounts of code because it cannot allocate space for new programs. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT.
TCP Event Messages 3237: ZPWY-EVT-TCP-FILEERRORFATAL The TCP encountered persistent I/O errors while it was attempting to access the TCLPROG files. The errors persisted for at least 100 to 500 retries, with a 1 second delay for each retry. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3238: ZPWY-EVT-TCP-BADPUREFPARAM A linkage section in a called program is larger than the maximum size of the corresponding parameter in the calling program. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The call fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Error Recovery on page 11-4.
TCP Event Messages 3239: ZPWY-EVT-TCP-BADLIBVERSION The TCP program object file is incompatible with its user-library object file. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages 3240: ZPWY-EVT-TCP-MAXINPUTMSGS The value specified for the ZMAXINPUTMSGS field in ZPWY-DDL-DEF-TCP exceeded 2045. This is a TCP internal error, because the PATHMON process does not accept ZMAXINPUTMSGS values greater than 2045. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZPWY-TKN-MAXINPUTMSGS contains the value specified for ZMAXINPUTMSGS in ZPWY-MAP-DEF-TCP. N indicates that this token can occur in a nested message. ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are conditional tokens specific to this event message. For descriptions of these tokens, see the TS/MP Management Programming Manual. Effect. The TCP terminates. Recovery. Contact your service provider.
TCP Event Messages 3241: ZPWY-EVT-TCP-UNSOLREJECTED The TCP rejected an unsolicited message for the reason specified by the error number. (This error number is also returned in the ZINFO field of the STATUS TERM command.) This message can be generated on behalf of either an individual requester or the entire TCP. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages ZEMS-TKN-SUBJECT-MARK indicates either ZPWY-TKN-TERMNAME or ZPWY-TKN-TCPNAME, which contains the name of the TERM or TCP that is the subject of this event message. If the subject token is ZPWY-TKN-TERMNAME, then ZPWY-TKN-INSTRUCTION, ZPWY-TKN-PUNAME, ZPWY-TKN-PUOFFSET, ZPWY-TKN-PUVERSION, and ZPWY-TKN-TCLPROGFNAME are included; otherwise, these tokens are omitted. ZPWY-TKN-EVENTCLASS has the value ZPWY-VAL-ERROREVENT.
TCP Event Messages 9 MAXINPUTMSGS value has been exceeded. 1 0 RECEIVE UNSOLICITED MESSAGE error occurred. INFO1 provides the reason, which is the value obtained from the TERMINATION-STATUS register. 11 The number of bytes in the reply message sent by the SCREEN COBOL requester exceeded the number of bytes supported by the sender of the unsolicited message. This is a warning and should occur only during the application-debugging phase.
TCP Event Messages 3242: ZPWY-EVT-TCP-UNSOLREJECTEDMANY This message is returned only if unsolicited messages are arriving and being rejected with sufficient frequency that the TCP cannot log individual error messages for each rejected unsolicited message. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual.
TCP Event Messages 3243: ZPWY-EVT-TCP-BADOSVERSION The TCP cannot execute on the currently running version of the operating system. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
TCP Event Messages 3244: ZPWY-EVT-TCP-BUTCPREADY A backup TCP process has been started and is ready to take over for the primary TCP process, if necessary. For a description of tokens that are present in this event message but are not listed or described here, see the TS/MP Management Programming Manual. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZPWY-TKN-TCPNAME ZPWY-TKN-EVENTCLASS token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN.
12 TCP Error Messages This section describes the error messages reported by link managers. The descriptions are given in ascending order by error number; that is, in ascending order by the ZPWY-ERR- values. Message Numbers All messages returned by the PATHMON environment are logged by the PATHMON process; however, some messages in some number ranges represent events and errors reported to the PATHMON process by other processes.
Errors in STATUS TCP and STATUS TERM Command Responses TCP Error Messages • • In an error list (The number returned in ZSPI-TKN-RETCODE is duplicated in ZSPI-TKN-ERROR.) As a number in ZSPI-TKN-RETCODE, which is returned in the response buffer For more information about receiving errors and the contents of Pathway error lists, see the TS/MP Management Programming Manual.
TCP Error Messages Additional Information for Terminal Errors Additional Information for Terminal Errors Some messages pertaining to terminal errors include additional error-message text on the reason for the terminal error.
TCP Error Messages Error-Message Range 3000 Through 3999 This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The terminal is aborted; the operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3.
TCP Error Messages Error-Message Range 3000 Through 3999 3006: ZPWY-ERR-TCP-BADPUPARAMSIZE The maximum size of a parameter passed in the USING clause of the CALL statement did not equal the maximum size of the corresponding parameter given in the procedure division header of the called program. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3. 3010: ZPWY-ERR-TCP-TERMFORMAT There is an error in the TCP format routines. This is a TCP internal error.
TCP Error Messages Error-Message Range 3000 Through 3999 This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3.
TCP Error Messages Error-Message Range 3000 Through 3999 3017: ZPWY-ERR-TCP-TERMOPEN A file-system error occurred while the TCP was opening the TERM. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The program terminates abnormally. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3. 3021: ZPWY-ERR-TCP-SENDFAIL A SCREEN COBOL SEND operation to a server failed for the reason indicated in a previous error message.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The program terminates abnormally. Recovery. Contact your service provider. 3025: ZPWY-ERR-TCP-TERMDATAFORMAT The input data received from the terminal did not have the correct structure, even after screen recovery and retries. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The I/O operation fails. Recovery. Run diagnostics for the device.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3. 3030: ZPWY-ERR-TCP-TMFNOTCONFIG An attempt to use the TMF subsystem was made, but the TMF subsystem is not configured in this system.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The call fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3. 3037: ZPWY-ERR-TCP-BADACCEPTTIMEOUT An invalid value was specified for the timeout parameter in an ACCEPT statement. The value was either less than 0 or too large to be represented in an INT(32) field.
TCP Error Messages Error-Message Range 3000 Through 3999 This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The PRINT SCREEN operation terminates abnormally. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3043: ZPWY-ERR-TCP-PRINTERIO A Guardian operating environment error occurred during a PRINT SCREEN operation.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. Informational message only; no corrective action is needed. 3052: ZPWY-ERR-TCP-STOPBYPROG The TERM object stopped because it encountered an exit in the highest-level program unit. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. None. Recovery. Informational message only; no corrective action is needed.
TCP Error Messages Error-Message Range 3000 Through 3999 This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. Use the ALTER TERM command to specify a valid value for the ZIOPROTOCOL field. The ZINFO field of the STATUS TERM display shows the reply value received by the TCP from the PATHMON process.
TCP Error Messages Error-Message Range 3000 Through 3999 3059: ZPWY-ERR-TCP-DEVICEINFO A file-system error was returned on a call to the DEVICEINFO procedure. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual.
TCP Error Messages Error-Message Range 3000 Through 3999 3062: ZPWY-ERR-TCP-BADDBCSKKDATA1 Translation routines were unable to correctly translate data from internal format to the external format required by the device. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The program terminates abnormally. Recovery.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. Truncation of double-byte data may be acceptable. If not, define larger data field lengths in the requester-server application, or define fields that do not wrap from one row to the next. 3065: ZPWY-ERR-TCP-NOKATAKANALLOWED1 An attempt was made to run a SCREEN COBOL program unit containing Katakana data on a device that does not support Katakana data.
TCP Error Messages Error-Message Range 3000 Through 3999 3068: ZPWY-ERR-TCP-NOTDBCSDATA2 The TCP encountered a data field that did not contain only double-byte (Kanji) character data. The SCREEN COBOL programmer has attempted to display mixed or single-byte characters in a PIC N only screen field, or to display a mixed field on an IBM 3270 device that does not support mixed fields.
TCP Error Messages Error-Message Range 3000 Through 3999 Once the primary TCP suspends the TERM task, this error is generated. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The primary and backup terminal task is abnormally terminated. Recovery. Restart the TERM either manually through PATHCOM or automatically by setting the ZAUTORESTART field in ZPWY-DDL-DEF-TERM to a value greater than 0.
Error-Message Range 3000 Through 3999 TCP Error Messages As an alternative, you can alter the TCP to increase the size of either ZTERMPOOL or ZTERMBUF, or both. 3100: ZPWY-ERR-TCP-SCPROCESSOPEN A file-system error occurred while the TCP was opening a server process. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The OPEN operation fails. Recovery.
Error-Message Range 3000 Through 3999 TCP Error Messages 3102: ZPWY-ERR-TCP-CODOPEN A file-system error occurred while the TCP was opening the TCLPROG code file. For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual .
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. Contact your service provider. 3106: ZPWY-ERR-TCP-CONFIGTOOBIG The TCP configuration parameters are incorrect. This is usually caused by incompatible values for two of the following fields in ZPWY-DDL-DEF-TCP: ZTERMBUF, ZTERMPOOL, ZMAXTERMDATA, ZSERVERPOOL, and ZMAXREPLY. This may also be caused by incompatible values for two of the following fields in ZPWY-DDL-DEF-PATHWAY: ZMAXTERMS, ZMAXSERVERCLASSES, and ZMAXSERVERPROCESSES.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3110: ZPWY-ERR-TCP-MAXSC An attempt was made to communicate with more server classes than the number defined for the ZMAXSERVERCLASSES field in ZPWY-DDL-DEF-PATHWAY. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Redefine the value of the ZMAXREPLY field or isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3.
Error-Message Range 3000 Through 3999 TCP Error Messages 3118: ZPWY-ERR-TCP-BADSCSTATE The state of the specified server does not allow the requested operation to take place. This is a Pathway internal error. This event can be triggered by either the TCP or the TS/MP LINKMON process. For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. For information regarding the specified file-system error, see the Guardian Procedure Errors and Messages Manual. 3122: ZPWY-ERR-TCP-CODIO A file-system error occurred during an I/O operation to the TCLPROG code file. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The I/O operation fails. Recovery.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. Unsolicited messages are rejected. Recovery. The ZINFO field of the STATUS TERM display specifies the number of unsolicited messages that were rejected. Restart the terminal and resend the unsolicited messages. 3140: ZPWY-ERR-TCP-ROUTIO A file-system error occurred during an I/O operation to the router process performed by the terminal control process (TCP) on behalf of the specified TERM object.
TCP Error Messages Error-Message Range 3000 Through 3999 3143: ZPWY-ERR-TCP-ROUTRTRMLIM The sum of the number of TERM object requests for connection queued to the router process and the number of TERM objects currently connected to clients (that is, “in session”) has reached the maximum limit (32767). This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The specified TERM object is aborted. Recovery.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. If the router process was not started with the protocol parameter set to HTTP or SOCKET, restart the router process with one of these protocol settings. 3147: ZPWY-ERR-TCP-SESSIONISNULL The TCP/IP session associated with the socket connection was null when the terminal control process (TCP) either performed an I/O operation on the socket or attempted to delete it.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The receive operation fails. The session is closed and the TERM object is reinitialized for a new session. Recovery. Informational message only; no corrective action is needed. 3161: ZPWY-ERR-TCP-MSGIO An I/O error occurred during a SEND MESSAGE operation or during a REPLY TO UNSOLICITED MESSAGE operation. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command.
TCP Error Messages Error-Message Range 3000 Through 3999 3164: ZPWY-ERR-TCP-MSGCODENOTDEFINED The message received from a RECEIVE UNSOLICITED MESSAGE operation or as a reply to a SEND MESSAGE operation is undefined because the message code does not match any of the reply codes specified in the YIELDS or SELECT list. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery.
TCP Error Messages Error-Message Range 3000 Through 3999 This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. Specify the correct subtype value (that is, 0, 1, or 2) for the intelligent device. 3169: ZPWY-ERR-TCP-BADTIMEOUTVALUE The SCREEN COBOL program unit specified an invalid timeout value. The value was either less than 0 or too large to be represented in an INT(32) field.
TCP Error Messages Error-Message Range 3000 Through 3999 3172: ZPWY-ERR-TCP-MSGTOOBIG After conversion of message data from an unsupported format to a supported format, the message length exceeded the maximum number of bytes allowed for all messages. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. If the user conversion routine is causing the error, correct the routine.
TCP Error Messages Error-Message Range 3000 Through 3999 Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3. If a USER CONVERSION clause is used in the program, check the user conversion routine. 3176: ZPWY-ERR-TCP-UNSOLNOTREPLIED A SCREEN COBOL program unit attempted to receive an unsolicited message before replying to a previous message.
TCP Error Messages Error-Message Range 3000 Through 3999 3179: ZPWY-ERR-TCP-TOOMUCHDATA A SCREEN COBOL program unit attempted to execute the TRANSFORM verb, but there was still data left unprocessed from the source data stream. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program. For instructions on how to locate the problem within the program, see Additional Information for Terminal Errors on page 12-3. 3183: ZPWY-ERR-TCP-BADDEPENDVALUE The value of the DEPENDING ON data item in the message section was larger than the limit specified in the OCCURS clause.
Error-Message Range 3000 Through 3999 TCP Error Messages • • • 1 to 512 are file-system errors. 1000 to 1512 are fatal file errors that, during the dump operation, cause the TCP to abend. -1 to -9 are errors that prevent the TCP dump operation. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The memory dump fails. If the error is a fatal error, the TCP terminates. Recovery. Contact your service provider.
Error-Message Range 3000 Through 3999 TCP Error Messages For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages 3203: ZPWY-ERR-TCP-SCOBOLFNS The TCP does not support the SCREEN COBOL function that was used. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The SCREEN COBOL program cannot be executed. Recovery. Use a more recent version of the TCP.
Error-Message Range 3000 Through 3999 TCP Error Messages 3205: ZPWY-ERR-TCP-BADTERMSTATE The TERM object is not in the appropriate state for the attempted operation. For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages Recovery. Use the SCREEN COBOL Utility Program (SCUP) to merge program units for all the requesters configured for the TCP into fewer than 16 pseudocode files; or, reassign requesters among TCPs so that the requesters assigned to a given TCP share fewer pseudocode files. 3210: ZPWY-ERR-TCP-BUCPUDOWN The processor for the backup TCP has failed.
TCP Error Messages Error-Message Range 3000 Through 3999 This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The TCP recreates the backup process, if possible. Recovery. If the problem persists, contact your service provider. 3213: ZPWY-ERR-TCP-BUOPEN A file-system error occurred while the TCP was trying to open a file to the backup process.
TCP Error Messages Error-Message Range 3000 Through 3999 Effect. The TCP terminates. This message may or may not be reported to the PATHMON process and written to the LOG1, but this message is written to the $0 collector process. Recovery. Contact your service provider. 3217: ZPWY-ERR-TCP-TRAPPED A trap occurred in the TCP because of a hardware or software failure. This is a TCP internal error.
TCP Error Messages Error-Message Range 3000 Through 3999 For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
TCP Error Messages Error-Message Range 3000 Through 3999 For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages 3225: ZPWY-ERR-TCP-INSPECTBADTERM The file name specified with an Inspect command names a device different from the one currently used for debugging the SCREEN COBOL program. For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
Error-Message Range 3000 Through 3999 TCP Error Messages For a description of tokens that are present in this event message but are not listed or described here, see “Event Management,” in Section 6 of the TS/MP Management Programming Manual.
TCP Error Messages Error-Message Range 3000 Through 3999 3229: ZPWY-ERR-TCP-SYSNOTDEFINED The SCREEN COBOL SEND statement does not contain a NonStop system name or the system name is not identified to the network. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The operation fails. Recovery. Isolate and correct the problem within the SCREEN COBOL program.
TCP Error Messages Error-Message Range 3000 Through 3999 3235: ZPWY-ERR-TCP-CODEAREATHRASHING The TCP is replacing excessive amounts of code because it cannot allocate space for new programs. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The TCP functions inefficiently. Recovery. Increase the value of the ZCODEAREALEN field.
TCP Error Messages Error-Message Range 3000 Through 3999 3240: ZPWY-ERR-TCP-MAXINPUTMSGS The value specified for the ZMAXINPUTMSGS field in ZPWY-DDL-DEF-TCP exceeded 2045. This is a TCP internal error. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect. The TCP terminates. 3241: ZPWY-ERR-TCP-UNSOLREJECTED The TCP rejected an unsolicited message for the reason specified in the returned error number.
TCP Error Messages Error-Message Range 3000 Through 3999 3242: ZPWY-ERR-TCP-UNSOLREJECTEDMANY This message is returned only if unsolicited messages are arriving and being rejected with sufficient frequency that the TCP cannot log individual error messages for each rejected unsolicited message. This error does not appear in the RETCODE token or in an error list; it appears only in response to a STATUS TCP or STATUS TERM command. Effect.
13 Management Programming Examples This section contains the following three management programming examples: • • • A NonStop Pathway/iTS configuration program, written in COBOL A program that issues an INFO PROG command, written in TAL An error handling program, written in COBOL. Configuring Pathway/iTS Example 13-1 on page 13-2 contains an example management program that configures Pathway/iTS. The program, which is written in COBOL, performs the following tasks: 1. Starts the PATHMON process 2.
Configuring Pathway/iTS Management Programming Examples Example 13-1. Pathway/iTS Configuration Program (page 1 of 13) IDENTIFICATION DIVISION. PROGRAM-ID. PATHWAY-SPI-EXAMPLE. ?SAVE STARTUP ?CONSULT COBOLEX0 ENVIRONMENT DIVISION. CONFIGURATION SECTION. SOURCE-COMPUTER. TXP. OBJECT-COMPUTER. TXP. SPECIAL-NAMES. FILE "$SYSTEM.SYSTEM.COBOLLIB" IS COBOL-LIB FILE "PWYUTIL" IS PATHWAY-UTILITIES. INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT PATHMON-FILE ASSIGN TO #DYNAMIC. DATA DIVISION. FILE SECTION.
Configuring Pathway/iTS Management Programming Examples Example 13-1. Pathway/iTS Configuration Program (page 2 of 13) * End of special boolean declarations. 05 WS-PATHMON-PROCESS-NAME 05 WS-PATHMON-PROCESS-EXT 05 WS-FILE-NAME. 10 VOLUME-NAME 10 SUBVOL-NAME 10 FILE-NAME 05 WS-SPI-INPUT. 10 COMMAND 10 OBJECT-TYPE 10 OBJECT-NAME 10 OBJECT-NAME-2 05 WS-PATHMON-PROGRAM-FILE PIC X(6). NATIVE-2 VALUE -1. PIC X(8) PIC X(8) PIC X(8) VALUE SPACES. VALUE SPACES. VALUE SPACES. NATIVE-2 VALUE -1.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 3 of 13) 01 DEF-AREA PIC X(02). COPY ZPWY-DDL-DEF-PATHWAY IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-DEF-PATHWAY BY ==ZPWY-DDL-DEF-PATHWAY REDEFINES DEF-AREA==. COPY ZPWY-DDL-DEF-TCP IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-DEF-TCP BY ==ZPWY-DDL-DEF-TCP REDEFINES DEF-AREA==. COPY ZPWY-DDL-DEF-TERM IN "$SYSTEM.ZSPIDEF.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 4 of 13) 300-START-PATHMON. * Get a process name for PATHMON. ENTER TAL "CREATEPROCESSNAME" USING WS-PATHMON-PROCESS-NAME * Start a named PATHMON process. ENTER "CREATEPROCESS" IN COBOL-LIB USING WS-PATHMON-PROGRAM-FILE, WS-PATHMON-PROCESS-NAME, WS-PATHMON-CREATE-OPTION, OMITTED, WS-PRIMARY-CPU GIVING WS-COBOL-RESULT PERFORM 3900-CHECK-COBOL-ERROR . 400-OPEN-PATHMON.
Configuring Pathway/iTS Management Programming Examples Example 13-1. Pathway/iTS Configuration Program (page 5 of 13) * Build and put the modifier token into the buffer.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 6 of 13) * Clear the TCP definition. ENTER TAL "SSNULL" USING ZPWY-MAP-DEF-TCP, ZPWY-DDL-DEF-TCP GIVING WS-SS-RESULT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Set appropriate TCP definition values. MOVE 5 TO ZMAXTERMS OF ZPWY-DDL-DEF-TCP MOVE WS-PRIMARY-CPU TO ZPRIMARY OF ZPWY-DDL-DEF-TCP MOVE WS-BACKUP-CPU TO ZBACKUP OF ZPWY-DDL-DEF-TCP * Point to the TCLPROG file on the current subvolume.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 7 of 13) * Clear the TERM definition. ENTER TAL "SSNULL" USING ZPWY-MAP-DEF-TERM, ZPWY-DDL-DEF-TERM GIVING WS-SS-RESULT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Set appropriate TERM definition values.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 8 of 13) * Set appropriate PROGRAM definition values. MOVE "TCP-SPI" TO ZTCP OF ZPWY-DDL-DEF-PROG MOVE WS-COBOL-VAL-OFF TO ZTMF OF ZPWY-DDL-DEF-PROG * Put the PROGRAM definition into the buffer. ENTER TAL "SSPUT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-MAP-DEF-PROG, ZPWY-DDL-DEF-PROG GIVING WS-SS-RESULT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Issue the ADD PROG command.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 9 of 13) * Put the PROGRAM TERM definition into the buffer. ENTER TAL "SSPUT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-MAP-DEF-PROGTERM, ZPWY-DDL-DEF-PROGTERM GIVING WS-SS-RESULT PERFORM 4000-CHECK-SUBSYSTEM-ERROR * Issue the ADD PROGTERM command. PERFORM 3800-ISSUE-PATHMON-COMMAND . / / 1800-TERMINATE. SET OK-TO-CONTINUE TO TRUE PERFORM 1900-SHUTDOWN-PATHWAY CLOSE PATHMON-FILE .
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 10 of 13) 2000-BUILD-ABORT-TERM-ALL. * Construct the ABORT TERM command. MOVE ZPWY-CMD-ABORT TO COMMAND OF WS-SPI-INPUT MOVE ZPWY-OBJ-TERM TO OBJECT-TYPE OF WS-SPI-INPUT PERFORM 2800-SELECT-COMMAND-OBJECT * Construct the object-selector token for the TERM. MOVE ZPWY-VAL-ALLTERM TO OBJECT-NAME OF WS-SPI-INPUT PERFORM 3500-SELECT-TERM . 2100-ABORT-TERM-CONTINUE.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 11 of 13) / 2800-SELECT-COMMAND-OBJECT. ENTER TAL "SSINIT" USING ZPWY-DDL-MSG-BUFFER, ZPWY-VAL-BUFLEN, ZPWY-VAL-SSID, ZSPI-VAL-CMDHDR, COMMAND OF WS-SPI-INPUT, OBJECT-TYPE OF WS-SPI-INPUT GIVING WS-SS-RESULT PERFORM 4000-CHECK-SUBSYSTEM-ERROR . 2900-SELECT-PROGRAM. * * Clear, build, and put the object-selector token for the PROGRAM into the buffer.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 12 of 13) 3400-SELECT-TCP. * * Clear, build, and put the object-selector token for the TCP into the buffer.
Management Programming Examples Configuring Pathway/iTS Example 13-1. Pathway/iTS Configuration Program (page 13 of 13) * Move continuation request to I/O area. MOVE REQUEST-SAVE-BUFFER to ZPWY-DDL-MSG-BUFFER WHEN ZSPI-ERR-MISTKN SET EOF-HIT TO TRUE WHEN OTHER PERFORM 4000-CHECK-SUBSYSTEM-ERROR END-EVALUATE . / 3800-ISSUE-PATHMON-COMMAND. IF OK-TO-CONTINUE THEN READ PATHMON-FILE WITH PROMPT ZPWY-DDL-MSG-BUFFER IF OK-TO-CONTINUE THEN * Protect against a long buffer being returned by a server.
Obtaining PROG Information Management Programming Examples Obtaining PROG Information Example 13-2 contains an example management program that issues an INFO PROG command. The example, which is written in the TAL programming language, performs the following tasks: 1. Opens the PATHMON process 2. Initializes the SPI buffer, calls SSNULL, and places an extensible token in the buffer 3. Determines the length of the message to be sent and sends the message 4. Corrects a change to the BUFLEN value 5.
Obtaining PROG Information Management Programming Examples Example 13-2. Obtaining PROG Information (page 2 of 3) STRUCT .SEL^PROG(ZPWY^DDL^SEL^PROG^DEF); STRUCT .DEF^PROG(ZPWY^DDL^DEF^PROG^DEF); ! PROG SELECTOR TOKEN ! PWY PROGRAM PARAMS STRING .S^TERM^BUF := @TERM^BUF '<<' 1, .S^SEL^PROG := @SEL^PROG '<<' 1, .S^SYS^NAME := @SYS^NAME '<<' 1, .END^OF^TEXT; ?NOLIST ?SOURCE $SYSTEM.SYSTEM.
Management Programming Examples Obtaining PROG Information Example 13-2. Obtaining PROG Information (page 3 of 3) ZPWY^SSID ':=' [ ZSPI^VAL^TANDEM, ! INITIALIZATION OF SSID ZSPI^SSN^ZPWY, ZPWY^VAL^VERSION ]; -- Open PATHMON with #ZSPI. CALL OPEN(PWY^NAME,PWY); IF <> THEN CALL DEBUG; -- Initialize SPI buffer. SPI^ERR := SSNULL(MAP^SEL^PROG,SEL^PROG); ZSPI^VAL^CMDHDR,ZPWY^CMD^INFO, ZPWY^OBJ^PROG); -- Use SSNULL for extensible token.
Management Programming Examples Obtaining PROG Information NonStop Pathway/iTS Management Programming Manual—426749-002 13 -18
14 Error Handling Example Program This example management program decodes a Pathway subsystem SPI error list. It is written in COBOL. The program does the following: 1. Obtains and interprets the ZSPI-TKN-RETCODE token and selects a table based on the range of ZSPI-TKN-RETCODE. For information on the ZSPI-TKNRETCODE token, see the SPI Programming Manual and Section 1, Introduction, through Section 10, Tell Message Commands, of this manual. 2. Locates and displays the error message text. 3.
Error Handling Example Program H Example 14-1. Handling Errors (page 1 of 26) 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 NATIVE-2 VALUE -1. NATIVE-2 VALUE -1. PIC S9(4) COMP VALUE 1. NATIVE-2 VALUE -1. NATIVE-2 VALUE -1.
Error Handling Example Program Example 14-1. Handling Errors (page 2 of 26) 05 WS-ERROR. 10 OBJECT-TYPE 10 OBJECT-FLAG 88 OBJECT-HAS-NO-NAME 88 OBJECT-HAS-NAME 10 NAME-TKN 10 INFO 05 WS-DECODE. 10 PARAMETER 10 OBJECT-FLAG 88 OBJECT-HAS-NO-NAME 88 OBJECT-HAS-NAME 10 OBJECT-TYPE-NAME 10 OBJECT-NAME-COUNT 10 OBJECT-NAME-TABLE. 15 OBJECT-NAME-1 15 OBJECT-NUMBER NATIVE-2 VALUE -1. PIC S9(4) COMP VALUE 0. VALUE 0. VALUE 1. NATIVE-4. NATIVE-2 VALUE -1. NATIVE-2 VALUE -1. PIC S9(4) COMP VALUE 0. VALUE 0. VALUE 1.
Error Handling Example Program Example 14-1. Handling Errors (page 3 of 26) 01 WS-COMMAND-NAMES REDEFINES WS-COMMAND-NAME-TABLE. 05 COMMAND-ENTRY PIC X(15) OCCURS 21 TIMES. 01 WS-OBJECT-TYPE-NAME-TABLE.
Error Handling Example Program Example 14-1. Handling Errors (page 4 of 26) 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC X(12) PIC 9 NATIVE-4. NATIVE-4. PIC X(12) PIC 9 NATIVE-4. NATIVE-4. PIC X(12) PIC 9 NATIVE-4. NATIVE-4.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1. Handling Errors (page 7 of 26) 05 05 05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) X(23) VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE "DEF-SCPROGRAMOSS". "DEF-SCCWD". "DEF-SCSTDERR". "DEF-SCSTDIN". "DEF-SCSTDOUT". "DEF-SCENV". "DEF-SCARGLIST".
Error Handling Example Program Example 14-1. Handling Errors (page 8 of 26) 05 05 05 05 05 05 05 05 05 05 05 05 05 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC PIC X(19) S9(4) X(19) S9(4) X(19) S9(4) X(19) S9(4) X(19) S9(4) S9(4) X(19) S9(4) VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE VALUE "OSSATTRUSED". 4025. "OSSATTRTOOBIG". 4026. "INVALIDPATHNAME". 4027. "ARGENVEXCEEDSMAX".
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1. Handling Errors (page 12 of 26) 05 05 05 05 05 05 05 05 01 FILLER FILLER FILLER FILLER FILLER FILLER FILLER FILLER PIC X(20) VALUE "OSSNOTAVAILABLE". PIC S9(4) VALUE 1160. PIC X(20) VALUE "PROCTYPEMISMATCH". PIC S9(4) VALUE 1161. PIC X(20) VALUE "RESIZESEGMENT". PIC S9(4) VALUE 1162. PIC X(20) VALUE "PRODUCTNOTLICENSED". PIC S9(4) VALUE 1164. WS-PM-ERROR-NAMES REDEFINES WS-PM-ERROR-NAME-TABLE.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1. Handling Errors (page 18 of 26) COPY ZPWY-DDL-SCTERMNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-SCTERMNAME BY ==ZPWY-DDL-SCTERMNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-TCPLINKNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-TCPLINKNAME BY ==ZPWY-DDL-TCPLINKNAME REDEFINES OBJECT-NAME-AREA==. COPY ZPWY-DDL-TCPNAME IN "$SYSTEM.ZSPIDEF.ZPWYCOB" REPLACING ZPWY-DDL-TCPNAME BY ==ZPWY-DDL-TCPNAME REDEFINES OBJECT-NAME-AREA==.
Error Handling Example Program Example 14-1. Handling Errors (page 19 of 26) PERFORM 500-DISPLAY-REQUEST-CMD PERFORM 600-DISPLAY-REQUEST-OBJTYPE PERFORM 700-DISPLAY-REQUEST-OBJNAME PERFORM 800-DISPLAY-PARM-ERROR PERFORM 900-DISPLAY-ERROR-CMD PERFORM 1000-DISPLAY-ERROR-OBJTYPE PERFORM 1100-DISPLAY-ERROR-OBJNAME PERFORM 1200-DISPLAY-ERROR-INFO EXIT PROGRAM . / 100-INITIALIZATION.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1. Handling Errors (page 21 of 26) 400-DISPLAY-SPI-ERROR. SEARCH ALL ERROR-ENTRY OF WS-SPI-ERROR-NAMES AT END DISPLAY "PATHMON SPI ERROR: " WS-SPI-RESULT WHEN ERROR-NUMBER OF WS-SPI-ERROR-NAMES ( SPI-ERROR-INDEX ) = WS-SPI-RESULT DISPLAY "PATHMON SPI ERROR: " ERROR-NAME OF WS-SPI-ERROR-NAMES ( SPI-ERROR-INDEX ) . 500-DISPLAY-REQUEST-CMD.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1. Handling Errors (page 23 of 26) / 1000-DISPLAY-ERROR-OBJTYPE.
Error Handling Example Program Example 14-1. Handling Errors (page 24 of 26) MOVE SPACES TO IMAGE OF WS-PRINT STRING " " DELIMITED "(%" DELIMITED NAME OF WS-NUMOUT DELIMITED ")" DELIMITED INTO IMAGE OF WS-PRINT END-STRING DISPLAY IMAGE OF WS-PRINT END-IF END-IF BY BY BY BY SIZE SIZE SIZE SIZE . / 1300-CHECK-SUBSYSTEM-ERROR. IF WS-SS-RESULT IS NOT ZERO THEN DISPLAY "SS ERROR: " WS-SS-RESULT END-IF . 1400-DECODE-OBJECT-TYPE.
Error Handling Example Program Example 14-1.
Error Handling Example Program Example 14-1.
Error Handling Example Program NonStop Pathway/iTS Management Programming Manual—426749-002 14 -28
Index Numbers 32-byte file names 3-25/3-26 A A 5-21 ABORT TCPTERM command 8-2 ABORT TERM command 8-3, 13-11 Access, exclusive or shared 6-10, 6-29 ADD PROG command 9-1, 13-8 ADD PROGTERM command 9-4, 13-9 ADD TCP command 7-2/7-3, 13-6 ADD TELL command 10-1 ADD TERM command 8-4, 13-7 All 4-1 ALL FIELDS USED error 6-9, 6-28 ALTER PROG command 9-6 ALTER PROGTERM command 9-8 ALTER TCP command 7-4 ALTER TERM command 8-6 Applications management 2-4 Architecture 1-2/1-3 Arrays, unsupported 3-18 ASCII blank charac
D Index Configuring (continued) See individual ADD commands Constants, reset 3-26 Context token 3-9, 3-27 Continuation example 3-24 required object states 3-23/3-24 specifying 3-21/3-22 Control tasks 2-5 CONTROL TCP command 7-6/7-7 Conversational mode 5-17, 5-18 CPU definitions See ZBACKUP field, ZPRIMARY field D Data declaration files 3-2 Data lists 3-18, 3-36 Data tokens, messages 4-1 Data-portion tokens, EMS 4-1 DDL (Data Definition Language) definition files 3-1/3-4 sample definition 3-10 Debug mode
F Index Errors (continued) status, obtaining for frozen servers 8-11 Event Management Service (EMS) 1-4, 4-1 Events See Messages, event Event-specific tokens 3-29 Exclusive or shared access 6-10, 6-29 Extended data segment, TCP 6-14, 6-21 Extensible structured tokens caution on initializing 3-19 descriptions 6-1/6-79 initializing with SSNULL 3-21 list of 6-2 sample DDL definitions 3-10/3-17 External PATHMON processes, maximum 6-18 External TCPs maximum, specifying 6-3 naming 7-24 status, obtaining 7-24 st
J Index J Julian timestamp 6-25 K Kernel Managed Swap Facility (KMSF) 6-21 L Language definition files 3-1/3-4 Link managers See TCP objects Lists, presentation format 3-36 M Management programming, Zxxx naming convention 3-31 Management tasks See System management tasks Managing a Pathway subsystem 1-1/1-7 Messages command elements 3-4/3-5 event numbers 3-9 number ranges 3-30, 11-1, 12-1 object elements 3-6/3-8 receiving and decoding responses 3-27 response 2-5/2-6 unsolicited 6-11, 6-18, 6-31 warning
Q Index PATHTCP2 statistics 6-53/6-59, 6-62/6-69 PATHTCPL file 6-17 PATHWAY object START command example 13-5 STOP command example 13-10 Pathway subsystem architecture 1-2/1-3 defining attributes 6-3/6-5 ID 3-20 management programming interface 2-4/2-6 managing 1-1/1-7 predefined token and field types 5-21/5-22 private field types for predefined values 5-22/5-25 private token and field types 5-8/5-21 security 3-31 simple tokens 5-25 PINs, setting 6-23 Pool space 6-20 Predefined field types 5-2 Predefined
S Index REFRESHCODE TCP command 7-13/7-14 Reply messages 2-5/2-6 Requesters limit 7-16 links, sharing 7-3 Reset constants 3-26 Responses, receiving and decoding summary 3-27 Response-control token 3-20 Restarts, number accomplished 6-77 RESUME TCPTERM command 8-17 RESUME TERM command 8-19 Retrieving messages 2-5/2-6 Return token 3-27 Run priority 6-20 RUN PROGRAM error action 6-6 S SCREEN COBOL allocating space for object code 6-14 DIAGNOSTIC-ALLOWED special register 6-28 directory check, specifying 6-14
T Index START TCPTERM command 8-21 START TELL command 10-5 START TERM command 8-23 STATE field 6-43 Statistics, collecting 6-21, 6-35 See also ZSTATS field, individual STAT commands STATS SCTCP command 7-17/7-18 STATS TCP command 7-19/7-20 STATS TCPSC command 7-21/7-22 STATS TCPTERM command 8-25 STATS TERM command 8-27 Status information See individual commands and object types STATUS TCP command 7-23/7-24 STATUS TCPLINK command 7-25/7-26 STATUS TCPTERM command 8-29 STATUS TERM command 8-31 STOP PATHWAY c
T Index TCP objects (continued) backup process, specifying 6-20 CONTROL command 7-6/7-7 defining attributes 6-13/6-24 DELETE command 7-8 description 3-6 GETVERSION command 7-9 INFO command 7-11/7-12 Inspect process, allowing 6-18 maximum, specifying 6-4 name of link to server 5-6 name selection 6-46 names, specifying 5-5, 5-6, 6-20, 6-31 object file name 6-20 programming considerations 3-32/3-33 qualifying 6-43 REFRESHCODE command 7-13/7-14 requester limit 7-16 specifying action for errors 6-33/6-35, 6-40
T Index TERM objects See also SCTERM objects, TCPTERM objects, PROGTERM objects, ZTERM field ABORT command 8-3 ABORT command example 13-11 ADD command 8-4 ADD command example 13-7 ALTER command 8-6 debugging 8-39 default values, obtaining 8-15 defining attributes 6-26/6-32 DELETE command 8-9 deleting 8-8 detailed status information 6-73/6-78 devices, specifying 5-18 freeze status information 6-79 ignoring STOP-MODE register 6-42 INFO command 8-14 INSPECT command 8-16 maximum, specifying 6-4, 6-20 name sel
U Index Token types (continued) structure, description of 3-17/3-18 Tokens See also Attribute tokens, Comment token, Context token, Qualifier tokens arrays, unsupported 3-18 codes for object names 5-4 comment 3-9 definition 3-1 extensible structured, initializing caution 3-19 maps, categories of 6-1 multiple 3-18 notation for 3-36 order of 3-36 private 5-2 required notation 3-36 unlisted in syntax 3-36 Transaction Application Language (TAL) See TAL Transaction Management Facility (TMF) See TMF subsystem T
Z Index ZBREAK field (continued) ZPWY-MAP-DEF-PROGTERM 6-8 ZPWY-MAP-DEF-TERM 6-27 ZCHARSET field 6-77 ZCHECKDIRECTORY field relation to REFRESHCODE command 7-14 ZPWY-MAP-DEF-TCP 6-14 ZCHECKPOINT field ZPWY-MAP-STATS-TCP2 6-59 ZPWY-MAP-STATS-TERM2 6-66 ZCODE field ZPWY-MAP-STATS-TCP2 6-56 ZPWY-MAP-STATS-TERM2 6-67 ZCODEAREALEN field 6-14 ZCPMEMMAN field 6-52 ZCPU field ZPWY-MAP-STATUS-TCP 6-71 ZCPUPAIR field ZPWY-MAP-DEF-TCP 6-15 ZCURALLOC field 6-56, 6-57 ZPWY-MAP-STATS-TCP2 6-55 ZCUR- fields, list of 6-5
Z Index ZINSPECT field 5-13 ZINSPECTFILE field 5-13 ZINSPECTINFO field ZPWY-MAP-DEF-TCP 6-18 ZPWY-MAP-DEF-TERM 6-30 ZINSTADDR field 6-77 ZINSTCODE field 6-77 ZIOCOMP field 6-52 ZIOINFO field ZPWY-MAP-STATS-TERM2 6-63 ZIOPROTOCOL field ZPWY-MAP-DEF-PROGTERM 6-11 ZPWY-MAP-DEF-TERM 6-30 ZIOS field ZPWY-MAP-STATS-TERM2 6-64 ZISATTACHED field 5-15 ZISCOUNT field 6-72 ZLENGTH field ZPWY-MAP-DEF-TELL 6-25 ZLINK field 6-58 ZLINKDEPTH field ZPWY-DDL-DEF-SC 7-3 ZMAXALLOC field 6-55, 6-56 ZMAXEXTERNALTCPS field 6-3
Z Index ZPOOLINFO field 6-54 ZPRIMARY field ZPWY-MAP-DEF-TCP 6-15 ZPWY-MAP-STATUS-TCP 6-70 ZPRINTERFILE field 5-16 ZPRINTERINFO field ZPWY-MAP-DEF-PROG 6-6 ZPWY-MAP-DEF-TERM 6-31 ZPWY-MAP-PAR-START-PROG 6-37 ZPRIORITY field ZPWY-MAP-DEF-TCP 6-20 ZPROCESS field ZPWY-DDL-TCPLINKNAME 5-6 ZPWY-MAP-DEF-TCP 6-20 ZPWY-MAP-STATUS-TCP 6-70 ZPROGRAM field ZPWY-DDL-PROGNAME 5-4 ZPWY-DDL-PROGTERMNAME 5-4 ZPWY-MAP-DEF-TCP 6-20 ZPUFILE field 6-77 ZPUNAME field 6-77 ZPUVERSION field 6-77 ZPWY 5-22 ZPWYC file 3-35 ZPWYDD
Z Index ZPWY-DDL- definitions (continued) YES-NO 5-20 ZPWY-ERR- errors PM-EOF 3-27 PM-NODATA 3-22 ZPWY-ERR-TCP- errors ARITHOVERFLOW 12-7 BACKUPOPENERROR 12-19 BADACCEPTTIMEOUT 12-12 BADCOD 12-23 BADCODE 12-3 BADDATAREF 12-5 BADDBCSKKDATA1 12-17 BADDBCSKKDATA2 12-17 BADDEPENDVALUE 12-38 BADDEVICESUBTYPE 12-33 BADDIR 12-22 BADDIRENTRY 12-9 BADENDOFMSG 12-34 BADFIELDSIZE 12-37 BADINDEX 12-4 BADIOPROTOCOL 12-14 BADLIBVERSION 12-54 BADNUMERIC 12-12 BADNUMERICNODD 12-14 BADOSVERSION 12-56 BADPCODEVERSION 12-15
Z Index ZPWY-ERR-TCP- errors (continued) INSPECTBADTERM 12-51 INSPECTIO 12-50 INSPECTMAXBKPT 12-49 INSPECTMAXTERM 12-48 INSPECTNOTENABLED 12-47 INSUFFTERMPOOL 12-20 INTERNAL 12-46 INVALIDIOPROTOCOL 12-7 IOPROTOCOLDENIED 12-14 MAXINPUTMSGS 12-55 MAXINPUTMSGSZERO 12-36 MAXPM 12-53 MAXREPLY 12-25 MAXSC 12-25 MAXSCPROCESS 12-27 MAXTCLPROG 12-44 MAXTERMS 12-42 MAXWSOCCURS 12-38 MSGCODENOTDEFINED 12-33 MSGEXCEEDSCONFIG 12-33 MSGIO 12-32 MSGTOOBIG 12-35 NOBASEDISPLAY 12-5 NODBCSINSTALLED 12-16 NODBCSSUPPORT 12-1
Z Index ZPWY-ERR-TCP- errors (continued) TMFFATAL 12-10 TMFMAXRESTARTS 12-10 TMFNOTCONFIG 12-11 TMFNOTRUNNING 12-11 TMFVIOLATION 12-10 TOOMUCHDATA 12-37 TRAPPED 12-47 UNILATERALABORT 12-19 UNSOLNONETOREPLY 12-36 UNSOLNOTREPLIED 12-36 UNSOLREJECTED 12-55 UNSOLREJECTEDMANY 12-56 UNSOLREJECTEDSTOP 12-28 XMLGENERATION 12-31 ZPWY-EVT-TCP- events ARITHOVERFLOW 11-33 BACKUPOPENERROR 11-121 BADACCEPTTIMEOUT 11-69 BADCOD 11-138 BADDATAREF 11-19 BADDBCSKKDATA1 11-105 BADDBCSKKDATA2 11-107 BADDEPENDVALUE 11-237 BADD
Z Index ZPWY-EVT-TCP- events (continued) DUMPTAKEN 11-266 DUPOVERLAY 11-29 EDITERRORINPUT 11-203 EDITERROROUTPUT 11-221 EXITWITHERROR 11-168 FIELDTOOBIG 11-213 FILEERRORFATAL 11-281 ILLEGALDELAY 11-129 ILLRUNTIMEATTRS 11-125 INSUFFTERMPOOL 11-127 INTERNAL 11-261 INVALIDIOPROTOCOL 11-31 IOPROTOCOLDENIED 11-89 MAXINPUTMSGS 11-285 MAXINPUTMSGSZERO 11-227 MAXPM 11-274 MAXREPLY 11-152 MAXSC 11-146 MAXSCPROCESS 11-161 MAXWSOCCURS 11-241 MSGCODENOTDEFINED 11-200 MSGEXCEEDSCONFIG 11-205 MSGIO 11-194 MSGTOOBIG 11-
Z Index ZPWY-EVT-TCP- events (continued) TERMOPEN 11-37 TERMUNKNOWN 11-247 TFILEOPEN 11-65 TMFFATAL 11-57 TMFMAXRESTARTS 11-59 TMFNOTCONFIG 11-61 TMFNOTRUNNING 11-63 TMFVIOLATION 11-55 TOOMUCHDATA 11-229 TRAPPED 11-263 UNILATERALABORT 11-119 UNSOLNONETOREPLY 11-225 UNSOLNOTREPLIED 11-223 UNSOLREJECTED 11-287 UNSOLREJECTEDMANY 11-290 UNSOLREJECTEDSTOP 11-170 XMLGENERATION 11-190 ZPWY-MAP- structured tokens, list of 6-2 ZPWY-MAP-DEF- attribute tokens category description 6-1 PATHWAY 6-3/6-5 PROG 6-6/6-7 PRO
Z Index ZPWY-TKN- event-specific tokens (continued) PUNAME 3-29 PUOFFSET 3-29 PUVERSION 3-29 TCLPROGFNAME 3-29 ZPWY-TKN- subject tokens FNAME 3-28 LMNAME 3-28 PMNAME 3-28 PROGNAME 3-28 SCNAME 3-28 TCPNAME 3-28 TELLNAME 3-28 TERMNAME 3-28 UNKOWNNAME 3-28 ZPWY-TYP- token types, description 5-4 ZPWY-VAL- values A 5-24 ALLnnn, list of 3-22 ALLPROG 9-10 ALLTCP 7-8, 7-17 ALLTELL 10-4 ALLTERM 8-3, 8-10 ALLTERMTYPE 9-11 BKPTHOLD 6-74 BUFLEN 3-19, 5-21 BUFSIZE 5-21 C 5-24 CHECKPOINT 6-74 DANSKNORSK 5-22 DEUTSCH 5-
Z Index ZPWY-VAL- values (continued) TIMEOUT 6-75 U 5-24 UK 5-22 USASCII 5-22 VERSION 5-22 ZQUEUEINFO field ZPWY-MAP-STATS-TCP1 6-51 ZPWY-MAP-STATS-TCP2 6-57 ZRANKCOUNT field 6-72 ZREPLY field ZPWY-MAP-STATS-TERM2 6-65 ZREQCNT field ZPWY-MAP-STATS-TCP1 6-52 ZPWY-MAP-STATS-TCP2 6-55, 6-59 ZPWY-MAP-STATS-TERM1 6-60 ZPWY-MAP-STATS-TERM2 6-63 ZRESETSTATS field 6-40 ZSCREENRECOVERY field 6-77 ZSECURITY field ZPWY-MAP-DEF-PROG 6-7 ZSEND field ZPWY-MAP-STATS-TERM2 6-65 ZSERVER field 6-78 ZSERVERCLASS field ZPWY-
Special Characters Index ZTCP field (continued) ZPWY-MAP-STATUSTERMDETAIL 6-74 ZTERM field ZPWY-DDL-SCTERMNAME 5-5 ZPWY-DDL-TCPTERMNAME 5-7 ZPWY-DDL-TERMNAME 5-8 ZPWY-MAP-STARTPROG 6-48 ZTERMBUF field 6-22 ZTERMPOOL field ZPWY-MAP-DEF-TCP 6-23 ZPWY-MAP-STATS-TCP2 6-54, 6-57 ZTERMTYPE field ZPWY-DDL-PROGTERMNAME 5-4 ZPWY-DDL-TERM-TYPE-INFO 5-18 ZTERMTYPEINFO field ZPWY-MAP-DEF-TERM 6-32 ZPWY-MAP-PAR-START-PROG 6-37 ZTIMEINCR field ZPWY-MAP-STATS-TERM2 6-69 ZTIMESTAMP field 6-25 ZTMF field ZPWY-MAP-DEF-PROG
Special Characters Index NonStop Pathway/iTS Management Programming Manual—426749-002 Index -22
