Subsystem Control Point (SCP) Management Programming Manual Abstract This manual describes the Subsystem Programmatic Interface (SPI) commands, events, errors, and data definitions (ZCOM, ZSCP, and ZTRC) supported by the Subsystem Control Point (SCP) program, and provides an overview of tracing. Product Version SCP D45/G02/G05 Supported Releases This manual supports D45.00 and all subsequent D-series releases, G02.00 through G04.00 (for SCP G02), and G05.
Document History Part Number Product Version Published 520619-001 SCP D45/G02/G05 November 2001 031851 SCP D10 January 1993 085741 SCP C30.08/D00 July 1992 26114 SCP C20 March 1989 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice.
Subsystem Control Point (SCP) Management Programming Manual Glossary Index Figures Tables What’s New in This Manual ix Manual Information ix New and Changed Information x About This Manual xiii Your Comments Invited xiii Notation Conventions xiv 1. Introduction Overview of SCP 1-1 The D-Series Environment 1-2 Summary of Changes 1-2 2.
3. SPI Programming Considerations for SCP (continued) Contents 3.
4. Common Definitions (continued) Contents 4. Common Definitions (continued) Retired Definitions 4-28 5.
. Event Messages (continued) Contents 6.
A. Errors Contents A.
A. Errors (continued) Contents A.
B. Tracing (continued) Contents B. Tracing (continued) Tracing to Memory B-5 Tracing to Disk B-6 The Trace Information Structure Initiating a Trace B-8 B-10 Specifying Tracing Process and Object B-10 Specifying the Trace-Data Disk File B-10 Modifying a Trace B-12 Stopping a Trace B-12 Index Figures Figure 1-1. Overview of the Subsystem Control Point (SCP) Process 1-1 Figure 3-1. Managing an SCP Process Directly Figure 3-2. Managing an SCP Process Indirectly Figure B-1.
Tables (continued) Contents Tables (continued) Table A-6.
What’s New in This Manual Manual Information Subsystem Control Point (SCP) Management Programming Manual Abstract This manual describes the Subsystem Programmatic Interface (SPI) commands, events, errors, and data definitions (ZCOM, ZSCP, and ZTRC) supported by the Subsystem Control Point (SCP) program, and provides an overview of tracing. Product Version SCP D45/G02/G05 Supported Releases This manual supports D45.00 and all subsequent D-series releases, G02.00 through G04.00 (for SCP G02), and G05.
What’s New in This Manual New and Changed Information New and Changed Information This update to the Subsystem Control Point (SCP) Management Programming Manual contains these changes: • • • • • Updated the lists of devices that SCP supports in Table 4-1, Device Types and Subtypes Supported by the LISTDEV Command, by Name, on page 4-3, and Table 4-1, Device Types and Subtypes Supported by the LISTDEV Command, by Name, on page 4-3.
What’s New in This Manual New and Changed Information The previous update to the Subsystem Control Point (SCP) Management Programming Manual contained these changes for SCP version D10: • • • A new LISTOPENS response token, ZSCP-MAP-XLISTOPENS-PROC, conveys the CPU and PIN of an SCP opener and its backup. The maximum number of pages that can be specified using the DATAPAGES startup parameter increased from 2046 to 65280.
What’s New in This Manual New and Changed Information Subsystem Control Point (SCP) Management Programming Manual—520619-001 xii
About This Manual This manual contains information for programmers developing applications to manage a Subsystem Control Point (SCP) process using the Subsystem Programmatic Interface (SPI). It also contains a general discussion of tracing that is relevant to any subsystem that supports tracing. Information describing D-series and G-series SCP processes is included, as well as listings of obsolete information from older SCP processes.
About This Manual Notation Conventions Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual.
About This Manual General Syntax Notation { } 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. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id , error ) ; !i !o !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program).
About This Manual Notation for Management Programming Interfaces [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
About This Manual !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. Notation for Management Programming Interfaces token-type ZSPI-TYP-STRING. !r The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.
1 Introduction Overview of SCP Subsystem Control Point (SCP) processes are part of the Distributed Systems Management (DSM) architecture. An SCP process is a central point through which management applications and subsystems exchange Subsystem Programmatic Interface (SPI) messages. Management processes, including the Subsystem Control Facility (SCF), send SPI messages to an SCP process, which routes each message to a specified subsystem process.
The D-Series Environment Introduction This manual presents the SCP process as a manageable subsystem, and describes: Data definitions used by SCP processes Section 4, Common Definitions The subset of the standard SPI commands supported by SCP processes Section 5, Commands and Responses Event messages generated by SCP processes Section 6, Event Messages Error messages generated by SCP processes Appendix A, Errors The role of SCP processes in subsystem tracing Appendix B, Tracing For a detailed de
Introduction • • • • • • Summary of Changes Subsystems can use the new GETVSN-LVL token to declare their support for Dseries data structures. New token and token data type definitions are available for conveying D-series data structures. The Subsystem Control Point (SCP) program has been adapted to the D-series environment. EMS provides new procedures and tokens for D-series data structures.
Introduction Summary of Changes Subsystem Control Point (SCP) Management Programming Manual—520619-001 1 -4
2 Communicating With an SCP Process To route commands to most subsystems, a management application must open an SCP process. If no SCP process exists, the management application or an interactive user must start one. The management application opens the SCP process, specifying that messages are in SPI format. The management application and SCP process then exchange SPI command and response messages using the Guardian WRITEREAD and READUPDATE procedures.
Communicating With an SCP Process Starting an SCP Process Starting an SCP Process This subsection describes two methods for starting an SCP process: • • Issuing a RUN command to a command interpreter Calling the Guardian PROCESS_CREATE_ procedure You declare SCP process run options and startup parameters in the RUN command or in the PROCESS_CREATE_ procedure call and subsequent startup message. For a description of these parameters, see Starting an SCP Process Using the RUN Command.
Communicating With an SCP Process Starting an SCP Process Using the RUN Command D-Series SCP [RUN] [[$vol.]subvol.
Communicating With an SCP Process Starting an SCP Process Using the RUN Command MEM pages should not be specified. SCP processes ignore this option and are allocated 64 pages of virtual data space. OUT filename identifies the log file used by the SCP process if either LOG * or LOGFILE * is declared as a startup parameter. For help selecting an appropriate log file, see Selecting a LOG File on page 2-11. Also see LOG filename LOGFILE filename on page 2-6.
Communicating With an SCP Process Starting an SCP Process Using the RUN Command AUTOSTOP time [ HRS | MINS | SECS ] specifies how long the SCP process waits before stopping itself if another process does not open it. Select time from these values: -1 The SCP process runs until it is explicitly stopped. 0 The SCP process stops after the last requester closes it (default). 1…9999 HRS The SCP process runs for the specified number of hours after the last requester closes it, then stops itself.
Communicating With an SCP Process Starting an SCP Process Using the RUN Command DELETEDELAY time [ HRS | MINS | SECS ] specifies the interval between the time that the SCP process receives its last response from a subsystem and the time that the SCP process closes the subsystem. This parameter is optional. Select time from these values: -1 The SCP process keeps the communications subsystem open indefinitely.
Communicating With an SCP Process Starting an SCP Process Using the PROCESS_CREATE_ Procedure SWAPVOL volname specifies the volume on the local node to which extended memory is swapped. If you omit this parameter, the SCP process uses the volume to which the data area is swapped. See the SWAP process option on page 2-4.
Communicating With an SCP Process Starting an SCP Process Using the PROCESS_CREATE_ Procedure error := PROCESS_CREATE_(file-name:len , ,[swap-file:len] ,[ext-swap-file:len] ,[priority] ,[cpu] , ,[error-detail] , name-option , process-name:len , , , ,[hometerm:len] ,[mem-pages] ,[create-options]); error := FILE_OPEN_(process-name:len,file-number); CALL WRITE (file-number,startup-message,message-len); error := FILE_CLOSE_(file-number); file-name:len is a string containing the name of the SCP program object
Communicating With an SCP Process Starting an SCP Process Using the PROCESS_CREATE_ Procedure name-option is set to 1 to indicate that the process will be named and that the name follows in process-name. process-name:len is a string containing the name assigned to the SCP process. The length of the string follows the colon. This parameter can be used in the subsequent call to the FILE_OPEN_. hometerm:len is a string containing the name of the home terminal for the SCP process.
Communicating With an SCP Process Starting an SCP Process Using the PROCESS_CREATE_ Procedure subvol is not used by SCP and should be blank. in is not used by SCP and should be blank. out is not used by SCP and should be blank. parameter value is any of the startup parameter/value pairs described in Starting an SCP Process Using the RUN Command on page 2-2. message-len is the length of the startup message. Startup Message Structure This TAL code reveals the structure of a startup message: STRUCT .
Communicating With an SCP Process Creating a High-PIN SCP Process Creating a High-PIN SCP Process The SCP program has the HIGHPIN object-file attribute set to OFF so processes generated from it always run at a low PIN (a process identification number less than 255).
Communicating With an SCP Process Opening an SCP Process Opening an SCP Process To send SPI commands to an SCP process, the process must be opened using the #ZSPI qualifier; in other words, the SCP process name must be specified as $processname.#ZSPI. If, for example, the SCP process name is $ZNET, your application would open it as $ZNET.#ZSPI. The #ZSPI qualifier indicates to the SCP process that subsequent messages from this process will follow the SPI protocol. Note.
Communicating With an SCP Process Stopping an SCP Process Stopping an SCP Process An SCP process can stop itself. How and when it does this depends on the value of the AUTOSTOP SCP process execution parameter you specify when you start the SCP process. See Starting an SCP Process Using the RUN Command on page 2-2.
Communicating With an SCP Process Abnormal Process Termination Subsystem Control Point (SCP) Management Programming Manual—520619-001 2- 14
3 SPI Programming Considerations for SCP This section presents topics of interest to programmers who are using the Subsystem Programmatic Interface (SPI) to manage an SCP process: Topic Summary Page Communication Alternatives Managing an SCP process directly versus managing it through an intermediate SCP process 3-2 Data Definition Files Where to find the necessary data definitions in a form suited to your application development language 3-3 SCP CommandMessage Processing How SCP processes handle
Communication Alternatives SPI Programming Considerations for SCP Communication Alternatives If the SCP to which the command is directed is already opened by your management process, you can send the command directly to it, as Figure 3-1 shows. Figure 3-1. Managing an SCP Process Directly SPI Command for SCP1 SCP Process SCP1 Management Process SPI Response from SCP1 VST002.
SPI Programming Considerations for SCP Data Definition Files Data Definition Files The tokens, values, and other data items necessary to use SPI to manage an SCP process are contained in files with names of the form: ZSPIxxxx (Subsystem Programmatic Interface definitions) ZCOMxxxx (common communications subsystem definitions) ZCMKxxxx (common subsystem definitions) ZSCPxxxx (Subsystem Control Point definitions) ZTRCxxxx (tracing definitions) where xxxx represents a specific development language: C (C) CO
SPI Programming Considerations for SCP Command-Message Queueing assigning it to ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR. Only one ZCOM-TKNXMGR token or one ZSPI-TKN-MANAGER token is allowed in a request. To derive the manager process name from the tokens in the request buffer: 1. If ZCOM-TKN-XMGR appears in the request, SCP uses its value as the identity of the manager process. Otherwise, the search continues with Step 2.
SPI Programming Considerations for SCP Command-Message Validation Command-Message Validation Before forwarding a command message to another SCP process or processing a command directed to itself, the SCP process performs additional command-message validation. Security Validation An SCP process accepts a sensitive command only if one of these is true: • • The requester’s process access ID (PAID) group is the super group.
Command-Message Timeout SPI Programming Considerations for SCP To messages bound for converted subsystems, an SCP process adds a set of REQID tokens conveying process identifiers: REQID Token Value ZCOM-TKN-REQID-PAID The process access ID of the requester ZCOM-TKN-REQID-PHANDLE The process handle of the requester ZCOM-TKN-REQID-PPROGXFILE The program file name of the requester ZCOM-TKN-REQID-PSTRING The process string of the requester For more information on these tokens, see the SPI Common Ext
SPI Programming Considerations for SCP D-Series Changes D-Series Changes These changes directly affect programmatic management of SCP processes: • • • • • • • • • • SCP processes are based on the ZCMK definitions, and therefore include ZCMKdefined tokens in commands and response messages and allow additional process startup parameters. Management applications can use the new subsystem manager process identification token ZCOM-TKN-XMGR to identify the SCP process to which a command is directed.
SPI Programming Considerations for SCP Obsolete Fields in Structured Tokens However, if the SCP process cannot fit a value in an obsolete token, it omits the token from the response and stores the value in a new token. The subsystem does not return an error. The requester does not discover the problem until it encounters the error ZSPIERR-MISTKN when it tries to get the old token from the buffer. Obsolete Fields in Structured Tokens Similar considerations apply to the fields of structured tokens.
SPI Programming Considerations for SCP Interprocess Communications Restrictions Interprocess Communications Restrictions These restrictions apply to communications among processes on a D-series node or in a mixed C-series and D-series network. They are relevant to all instances of requesterSCP-server communications. • • No process on a C-series node can be opened by a high-PIN process on a D-series node.
SPI Programming Considerations for SCP SCP and the ZCMK Definitions SCP and the ZCMK Definitions The SCP process is based on the ZCMK definitions described in the SPI Common Extensions Manual. This subsection highlights some implications of this. ZCMK Command and Response Tokens Commands sent to and responses generated by an SCP process can contain ZCMK tokens. For descriptions of each token, see the SPI Common Extensions Manual and specific command descriptions in Commands and Responses on page 5-7.
4 Common Definitions This section describes data definitions relevant to the programmatic management of an SCP process and to the initiation of a trace, including these categories of definitions: Topic Page ZCOM Definitions 4-1 ZSCP Definitions 4-3 ZTRC Definitions 4-25 Retired Definitions 4-28 For descriptions of common ZCOM and ZCMK definitions, see the SPI Common Extensions Manual. For descriptions of common ZSPI definitions, see the Distributed Systems Management (DSM) Manual.
ZCOM Maps Common Definitions ZCOM Maps ZCOM-MAP-TRACE-MODIF This structure has been retired and replaced by ZTRC-MAP-TRACE-MODIF on page 4-25.
ZSCP Definitions Common Definitions ZSCP Definitions ZSCP definitions are defined by the SCP subsystem and are unique to it. ZSCP Tokens ZSCP-TKN-DEVTYPE token-code value token-type ZSCP-TKN-DEVTYPE ZSCP-TNM-DEVTYPE ZSPI-TYP-INT-PAIR. Management applications can include this token in LISTDEV commands to request information about a specific device type. The token value consists of an integer pair. The first integer specifies a device type, and the second specifies a device subtype.
ZSCP Tokens Common Definitions Table 4-1.
ZSCP Tokens Common Definitions Table 4-1.
ZSCP Tokens Common Definitions Table 4-1. Device Types and Subtypes Supported by the LISTDEV Command, by Name (page 4 of 7) Device Description Type,Subtype D/G-Series Open System Services (OSS or POSIX) OSS Monitor 24,0 Both Operator Console $0 (Operator Process) or alternate collector $0.
ZSCP Tokens Common Definitions Table 4-1.
ZSCP Tokens Common Definitions Table 4-1.
ZSCP Tokens Common Definitions Table 4-1.
ZSCP Tokens Common Definitions Table 4-2. Device Types and Subtypes Supported by the LISTDEV Command, by Device Type (page 1 of 7) Type,Subtype Device Description D/G-Series 1,0 Operator Console $0 (Operator Process) or alternate collector Both 1,1 $0.
ZSCP Tokens Common Definitions Table 4-2.
ZSCP Tokens Common Definitions Table 4-2.
ZSCP Tokens Common Definitions Table 4-2.
ZSCP Tokens Common Definitions Table 4-2.
ZSCP Tokens Common Definitions Table 4-2.
ZSCP Maps Common Definitions Table 4-2.
ZSCP Maps Common Definitions ZAUTO-STOP contains the AUTOSTOP startup parameter value specified when the SCP process was started. For a description of the AUTOSTOP parameter, see AUTOSTOP time [ HRS | MINS | SECS ] on page 2-5. ZDEL-DELAY contains the DELETEDELAY startup parameter value specified when the SCP process was started. For a description of the DELETEDELAY parameter, see DELETEDELAY time [ HRS | MINS | SECS ] on page 2-6.
Common Definitions ZSCP Maps ZBKUP-PID contains the backup cpu,pin of the I/O process controlling the device. ZDEVTYPE contains the device type and subtype. ZREC-SIZE contains the record size specified in the system-generation configuration file for the device. ZPRI contains the priority of the I/O process controlling the device. ZPROGNAME contains the name of the program file from which the I/O process controlling the device is derived.
ZSCP Maps Common Definitions process. New SCP processes do not keep a count of queued requests and return a zero in this field. ZSCP-MAP-STATUS-PROC SCP processes include this structure in STATUS command responses to describe the current status of the process. ZSCP-MAP-STATUS-PROC is based on ZSCP-DDLSTATUS-PROC, which is defined as: def ZSCP-DDL-STATUS-PROC.
ZSCP Maps Common Definitions ZSCB-CNT contains the number of subsystem (server) processes that this SCP process currently has open. ZRCB-CNT contains the number of command messages (requests) currently being processed. ZRCB-QUEUED contains the number of command messages (requests) currently queued. ZRCB-TOTAL-CNT contains the total number of command messages (requests) processed since this SCP process was started. ZTRACE-FNAME contains the name of the trace-data disk file.
ZSCP Maps Common Definitions ZSCP-MAP-XLISTDEV-PROC is based on ZSCP-DDL-XLISTDEV-PROC, which is defined as: def ZSCP-DDL-XLISTDEV-PROC. 02 ZLDEV 02 ZDEVNAME 02 ZDEV-ADDR 02 ZPRIM-CPU 02 ZPRIM-PIN 02 ZBKUP-CPU 02 ZBKUP-PIN 02 ZDEVTYPE 02 ZREC-SIZE 02 ZPRI end. type type type type type type type type type type ZSPI-DDL-INT. ZSPI-DDL-DEVNAME. ZSPI-DDL-EXIOADDR. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-INT-PAIR. ZSPI-DDL-INT. ZSPI-DDL-INT.
ZSCP Maps Common Definitions ZPRI contains the execution priority of the logical device. ZSCP-MAP-XLISTOPENS-PROC SCP processes return this structure in LISTOPENS responses to identify processes that have the SCP process open. ZSCP-MAP-XLISTOPENS-PROC is based on ZSCP-DDL-XLISTOPENS-PROC: def ZSCP-DDL-XLISTOPENS-PROC. 02 ZPRIM-CPU type 02 ZPRIM-PIN type 02 ZBKUP-CPU type 02 ZBKUP-PIN type end. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-UINT.
ZSCP Maps Common Definitions ZSCP-MAP-XSTATUS-PROC is based on ZSCP-DDL-XSTATUS-PROC, which is defined as: def ZSCP-DDL-XSTATUS-PROC. 02 ZSUMSTATE 02 ZPRIM-CPU 02 ZPRIM-PIN 02 ZBKUP-CPU 02 ZBKUP-PIN 02 ZMEM-USED 02 ZMEM-FREE 02 ZACB-CNT 02 ZSCB-CNT 02 ZRCB-CNT 02 ZRCB-TOTAL-CNT end. type type type type type type type type type type type ZSPI-DDL-ENUM. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-UINT. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT2.
Values Common Definitions ZRCB-CNT contains the number of command messages (requests) that have not finished. ZRCB-TOTAL-CNT contains the total number of command messages (requests) processed since this SCP process was started. Values ZSCP-VAL-SSID This token value specifies the destination subsystem ID for the SCP process. def ZSCP-VAL-SSID. 02 ZSSOWNER 02 ZSSNUMBER 02 ZSSVERSION type character 8 value is ZSPI-VAL-TANDEM. type unsigned integer value is ZSPI-SSN-ZSCP.
ZTRC Definitions Common Definitions ZTRC Definitions The tracing-related definitions in this subsection are defined by ZTRC. ZTRC Tokens ZTRC-TKN-INIT-ERR-DETAIL token-code value token-type ZTRC-TKN-INIT-ERR-DETAIL ZTRC-TNM-INIT-ERR-DETAIL ZSPI-TYP-INT. Both SCP processes and traced processes can include this token in ZTRC error messages to provide an additional detail to characterize the error. This information is only available to processes that use the DSM_TRACE_ procedure.
ZTRC Maps Common Definitions ZPRIM specifies the path to be traced. Valid values are: ZSPI-VAL-TRUE or blank Trace the primary path. ZSPI-VAL-FALSE Trace the backup path. ZREC-SIZE specifies the size of the trace record, in bytes. Valid values are: 0 When modifying a trace (that is, if ZFNAME is blank), the current record size is retained. When starting a trace (ZFNAME contains a file name), the default record size of 120 bytes is used.
ZTRC Maps Common Definitions ZFNAME is the name of the disk file to which trace information is written. If ZFNAME is empty and ZSTOP is not TRUE, the current trace is modified. If ZFNAME contains a file name and ZSTOP is not TRUE, a new trace is initiated. (If ZSTOP is TRUE, the trace stops regardless of the value of ZFNAME.) The default value for ZFNAME is blank. ZWRAP specifies whether to wrap data in the trace collector file or the extended segment.
Retired Definitions Common Definitions Retired Definitions Retired definitions are still recognized, and applications based on them continue to run as before. However, you should not use retired definitions in any new application development.
Retired Definitions Common Definitions Retired Definition Replaced By...
Common Definitions Retired Definitions Subsystem Control Point (SCP) Management Programming Manual—520619-001 4- 30
5 Commands and Responses This section describes the SPI commands supported by SCP processes and includes: Topic Page Common Command Tokens 5-2 Common Response Tokens 5-5 Command Security 5-7 Commands and Responses 5-7 Table 5-1. SCP-Supported Commands Command (ZCOM-CMD-) Security Classification Description Page ABORT Sensitive Abruptly stops an SCP process in spite of any current opens. 5-8 ALTER Sensitive Modifies SCP internal processing parameters.
Common Command Tokens Commands and Responses Common Command Tokens These common command-message tokens appear in most or all SCP commands: Values Assigned to Command Header Tokens ZSPI-TKN-COMMAND ZSPI-TKN-OBJECT-TYPE ZSPI-TKN-SSID ZSPI-TKN-MAXRESP assigned assigned or assigned assigned ZCOM-CMD-command ZCOM-OBJ-PROC ZCOM-OBJ-NULL ZSCP-VAL-SSID appropriate value Common Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN
Common Command Tokens Commands and Responses ZSPI-TKN-SSID is a header token that identifies the subsystem expected to process the command. To specify an SCP process, assign the value ZSCP-VAL-SSID. ZSPI-TKN-MAXRESP is a header token used by the requester to specify the maximum number of response records that can be accepted in the response buffer. Use the SSINIT procedure to assign one of these values: -1 The response contains as many response records as fit in the buffer.
Commands and Responses Common Command Tokens These tokens are described in the SPI Common Extensions Manual. Either ZCOMMAP-REQID or the ZCOM-TKN-REQID-desc tokens must be present in requests delivered to subsystem processes by intermediate routing processes like SCP. ZCOM-TKN-OBJNAME specifies the name or name template that the subsystem uses to select objects for processing. To specify an SCP process, assign the SCP process name.
Common Response Tokens Commands and Responses Common Response Tokens Many of the tokens associated with a response are common to all responses. Tokens from the command-message header are put into the response header. ZSPI-TKNSERVER-VERSION is also put into the response header.
Common Response Tokens Commands and Responses ZSPI-TKN-RETCODE indicates the outcome of command processing. Possible values are: 0 (ZCOM-ERR-OK) No error occurred during command processing. If a warning occurred, the response contains an error list that specifies the warning. <>0 An error occurred during command processing. If an error occurred, the response contains an error list that specifies the error. This token is always present in the response.
Commands and Responses Command Security Command Security SCP enforces basic command security on the basis of the distinction between sensitive and nonsensitive commands. A command capable of affecting SCP’s operation in any way is called a sensitive command. This includes any command that can change the summary state, status, or configuration of an SCP process. A command that retrieves information about an SCP process without affecting the process in any way is called a nonsensitive command.
ABORT Command Commands and Responses ABORT Command ZCOM-CMD-ABORT (sensitive) The ABORT command stops operation of an SCP process immediately. In the case of an SCP process pair, both the primary and backup processes are stopped.
ALTER Command Commands and Responses ALTER Command ZCOM-CMD-ALTER (sensitive) The ALTER command directed to the PROC object type of an SCP process lets the requester modify these internal operating parameters: • • • • • • Whether to call DEBUG after detecting an internal error Whether to start the backup process in DEBUG Backup CPU number EMS collector process names Log file name Message file name Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-PROC ALTER Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-
ALTER Command Commands and Responses .ZDEBUG-ON-ERR specifies how the SCP primary process responds to internal errors. Valid values and their meanings are: ZSPI-VAL-TRUE The SCP process calls DEBUG when it detects an internal error. The primary process does not terminate, and the backup process does not take over until a stop command is issued to the DEBUG process.
ALTER Command Commands and Responses ZCMK-TKN-EMS-XFNAME ZCMK-TKN-EMS-XFNAME-1 ZCMK-TKN-EMS-XFNAME-2 ZCMK-TKN-EMS-XFNAME-3 specifies the identity of the EMS collector for the primary collector and alternate collectors 1, 2, and 3, respectively. A zero-length name stops EMS event collection for the corresponding collector. To leave a collector unchanged, omit the corresponding token from the request.
GETVERSION Command Commands and Responses GETVERSION Command ZCOM-CMD-GETVERSION (nonsensitive) The GETVERSION command returns SCP program version information and optional information describing SCP process support for command security and object tracing.
GETVERSION Command Commands and Responses command containing ZCOM-TKN-GETVSN-SUPP-PARAMS set to TRUE is called a supplemental GETVERSION command.
GETVERSION Command Commands and Responses ZCOM-TKN-GETVSN-SECUR-SUPP is included in the response to a supplemental GETVERSION command. It indicates the level of command security that the SCP process expects an intermediate SCP process to provide. It is always set to: ZCOM-VAL-SECUR-SUPP-ALL The queried SCP process lets an intermediate routing SCP process (if one is used) enforce command security. ZCOM-TKN-GETVSN-TRACE-SUPP is included in the response to a supplemental GETVERSION command.
INFO Command Commands and Responses INFO Command ZCOM-CMD-INFO (nonsensitive) The INFO command returns the values of the AUTOSTOP, DELETEDELAY, and SEGPAGES startup parameters specified when the SCP process was created, along with the name of the object file from which the process was derived. SCP processes return additional information in the listed ZCMK response tokens.
Commands and Responses INFO Command structure and returns the information in ZSCP-MAP-XINFO-PROC and ZCMKTKN-PROG-XFNAME. .ZAUTO-STOP contains the value of the AUTOSTOP startup parameter. .ZDEL-DELAY contains the value of the DELETEDELAY startup parameter. .ZSEG-PAGES contains the value of the SEGPAGES startup parameter. .ZPROG-FNAME contains the name of the SCP process object file. ZSCP-MAP-XINFO-PROC returns SCP process startup parameters in these fields: .
Commands and Responses INFO Command .ZBKUP-CPU reports the current backup CPU number. The backup process might not be running. If it is not, this value specifies where the backup runs when initiated. .ZBUF-SWAPVOL specifies the name of the disk volume to which the data space (stack space) is swapped. This value is assigned by the SWAP argument in the startup command issued to a command interpreter when the program is initiated.
LISTDEV Command Commands and Responses LISTDEV Command ZCOM-CMD-LISTDEV (nonsensitive) The LISTDEV command retrieves DEVICEINFO information for all devices of the type and subtype specified in the command.
LISTDEV Command Commands and Responses If this token is omitted from the command, information is returned for all devices configured in the system.
Commands and Responses LISTDEV Command ZSCP-MAP-XLISTDEV-PROC returns DEVICEINFO information in data structures (CPU and PIN in separate fields). Multiple occurrences of this structure can be returned, one for each device type and subtype combination specified in the command. The information is returned in these fields: .ZLDEV specifies the logical device number. .ZDEVNAME specifies the logical device name. .ZDEV-ADDR contains the full device address. .
LISTOPENS Command Commands and Responses LISTOPENS Command ZCOM-CMD-LISTOPENS (nonsensitive) The LISTOPENS command returns the identity of each process that has the SCP process open. If requested, an SCP process segments the response.
LISTOPENS Command Commands and Responses LISTOPENS Response Tokens (Unsegmented Response) ZSPI-TKN-DATALIST ZSPI-TKN-RETCODE ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-LIST token-type ZSPI-TYP-INT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSCP-MAP-LISTOPENS-PROC ZSCP-MAP-XLISTOPENS-PROC ZCMK-TKN-LISTOP-XPNAME ZCMK-TKN-LISTOP-QUALIFS ZCMK-MAP-LISTOP ZSPI-TKN-ENDLIST token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SSCTL LISTOPENS Response Tokens (Segmented
Commands and Responses LISTOPENS Command For a description of this structure, see ZSCP-MAP-XLISTOPENS-PROC on page 4-22. ZCMK-TKN-LISTOP-XPNAME records the process name of an opener. The nth occurrence of ZCMK-TKNLISTOP-XPNAME corresponds to the nth occurrence of ZCMK-TKN-LISTOPQUALIFS and ZCMK-MAP-LISTOP. ZCMK-TKN-LISTOP-QUALIFS records the qualifiers used when the process or object managed by the process was opened.
RESETSTATS Command Commands and Responses RESETSTATS Command ZCOM-CMD-RESETSTATS (sensitive) The RESETSTATS command retrieves and resets statistics describing these internal SCP processing parameters: • • • • Use of buffer-storage pools Use of memory-storage pools Number of SCP process openers Depth of SCP process receive queue Command ZCOM-CMD-RESETSTATS Object Type ZCOM-OBJ-PROC RESETSTATS Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING or
RESETSTATS Command Commands and Responses For a description of these structures, see the RESETSTATS response syntax. RESETSTATS Response Tokens ZSPI-TKN-DATALIST ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-RETCODE ZCMK-MAP-STATS-BUF ZCMK-MAP-STATS-MEM ZCMK-MAP-STATS-OPNR ZCMK-MAP-STATS-RECV ZSPI-TKN-ENDLIST token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-INT token-type ZSPI-TYP-SSCTL ZCMK-MAP-STATS-BUF summarizes SCP’s use of buffer-storage pools.
START Command Commands and Responses START Command ZCOM-CMD-START (sensitive) The START command cancels the effects of a STOP, ORDERLY command if it is issued to an SCP process that is still reporting the STOPPING summary state. In response, the SCP process returns to the STARTED state and continues processing as normal. This command is not used to start an SCP process. See Starting an SCP Process on page 2-2.
STATISTICS Command Commands and Responses STATISTICS Command ZCOM-CMD-STATISTICS (nonsensitive) The STATISTICS command retrieves statistics describing these internal SCP processing parameters: • • • • Use of buffer-storage pools Use of memory-storage pools Number of SCP process openers Depth of SCP process receive queue All statistics are returned in a token of the form STAT-TEMPLATE, as described in the response syntax.
STATISTICS Command Commands and Responses ZCOM-TKN-ENQ can be used to retrieve a particular statistic by assigning the token number that carries the statistic. You can specify these statistics tokens in commands directed to the native object type of an SCP process: ZCMK-MAP-STATS-BUF ZCMK-MAP-STATS-MEM ZCMK-MAP-STATS-OPNR ZCMK-MAP-STATS-RECV For a description of these structure, see the STATISTICS response syntax.
STATUS Command Commands and Responses STATUS Command ZCOM-CMD-STATUS (nonsensitive) The STATUS command returns current information on the status of an SCP process.
Commands and Responses STATUS Command .ZSUMSTATE contains the summary state. .ZPRIM-PID contains the cpu,pin of the SCP primary process. .ZBKUP-PID contains the cpu,pin of the SCP backup process. If there is no backup process, cpu,pin is 0,0. .ZMEM-FREE-BLOCK contains the number of free blocks in the memory pool. .ZMEM-USED contains the number of bytes used in the memory pool. .ZMEM-FREE contains the number of available bytes in the memory pool. .
Commands and Responses STATUS Command .ZSUMSTATE specifies the summary state. .ZPRIM-CPU specifies the CPU of the primary SCP process. .ZPRIM-PIN specifies the PIN of the primary SCP process. .ZBKUP-CPU specifies the CPU of the backup SCP process. If there is no backup process, this field contains 0. .ZBKUP-PIN specifies the PIN of the backup SCP process. If there is no backup process, this field contains 0. .ZMEM-USED specifies the number of bytes used in the memory pool. .
STOP Command Commands and Responses STOP Command ZCOM-CMD-STOP (sensitive) The STOP command stops the SCP process to which it is directed. You can stop the process only after outstanding opens from other processes are closed. You can modify the STOP command to either fail if there are outstanding opens or to wait until the outstanding opens are closed. For an SCP process pair, the primary and backup processes are stopped.
STOP Command Commands and Responses ZCOM-VAL-POWER-ORDERLY The SCP process immediately returns a response containing error number ZCOM-ERR-OK but continues to run if it is supporting any opens from other processes. The SCP process reports the STOPPING summary state while it waits for these outstanding opens to be closed. No new opens are allowed during this time. When all opens are closed, the SCP process stops.
SWITCH Command Commands and Responses SWITCH Command ZCOM-CMD-SWITCH (sensitive) The SWITCH command causes the backup process of an SCP process pair to take over.
TRACE Command Commands and Responses TRACE Command ZCOM-CMD-TRACE (sensitive) A TRACE command directed to the SCP process causes the process to initiate, modify, or stop a trace of its activity. SCP processes use the SCPTRACE tracing environment. For a discussion of tracing and the related token definitions, see Appendix B, Tracing.
TRACE Command Commands and Responses TRACE Response Tokens ZSPI-TKN-DATALIST ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-RETCODE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-INT ZSPI-TYP-SSCTL Subsystem Control Point (SCP) Management Programming Manual—520619-001 5- 36
6 Event Messages SCP processes generate these categories of event messages: • • • ZSCP-defined events ZCMK-defined events ZCOM-defined events as issued by ZCMK-based subsystems The SPI Common Extensions Manual describes the common ZCMK and ZCOM events. The EMS Manual contains general information on events and event management.
ZSCP Events Event Messages Table 6-1. ZSCP Events Generated by SCP Processes, by Number (page 2 of 2) Number Name (ZSCP-EVT-...) Message Text 21 RCB-FULL Request table full 22 TIMEOUT-MSG-REJ Bad timeout tag: ... 23 SCB-FULL Subserver open table full 24 POOL-FULL Memory pool full 25 BKP-SIGNALTIMEOUT-ERR SIGNALTIMEOUT for backup failed; no backup 26 BKP-NEWPROCESS-ERR No backup; fs: ...; ... 27 CHKPT-WRITE-ERR Checkpoint write failed; error ...
ZSCP Events Event Messages Table 6-2. ZSCP Events Generated SCP Processes, by Name (page 2 of 2) Name (ZSCP-EVT-...) Number Message Text BAD-REPLY 34 Could not handle reply: ... BAD-TABLE 7 Internal table error; type ...; error: ... BKUP-DOWN 32 Backup process terminated BKP-NEWPROCESS-ERR 26 No backup; fs: ...; ... BKP-OPEN-ERR 28 OPEN to backup failed; error ...
ZSCP Events Event Messages Table 6-3. ZSCP Events Generated by SCP Processes, by Message Text (page 1 of 2) Message Text Name (ZSCP-EVT-...) Number $RECEIVE READUPDATE error: ... RECV-READUPDATE-ERR 5 ALLOCATESEGMENT failed: ... ALLOCSEGMENT-ERR 2 Application open table full ACB-FULL 20 AWAITIO on $RECEIVE error: ... AWAITIO-ERR 6 Backup process terminated BKUP-DOWN 32 Backup received invalid checkpoint BAD-CHKPT 4 Bad PUTMEMORY call: ... BAD-PUTMEMORY 38 Bad timeout tag: ...
Event Messages Event Messages and Programmatic Error Recovery Table 6-3. ZSCP Events Generated by SCP Processes, by Message Text (page 2 of 2) Message Text Name (ZSCP-EVT-...) Number Security Violation: PAID: ..., Cmd: ..., For: ... SECURITY-VIOL 35 SIGNALTIMEOUT for backup failed; no backup BKP-SIGNALTIMEOUT-ERR 25 SIGNALTIMEOUT for deletedelay failed DEL-SIGNALTIMEOUT-ERR 17 SIGNALTIMEOUT for shutdown failed SHUT-SIGNALTIMEOUT-ER 1 State changed from ... to ...
Event Messages About the Event Descriptions About the Event Descriptions The ZSCP event descriptions are listed in order by event number. Use the tables on the preceding pages to find the event number that corresponds to a particular name or message text.
2 ZSCP-EVT-ALLOCSEGMENT-ERR Event Messages 2 ZSCP-EVT-ALLOCSEGMENT-ERR A call to the ALLOCATESEGMENT or SEGMENT_ALLOCATE_ procedure failed. Tokens in Event Message ZSCP-TKN-ERRCODE <1> token-type ZSPI-TYP-INT. Message Text ALLOCATESEGMENT failed: <1> ZSCP-TKN-ERRCODE contains the error code returned by the ALLOCATESEGMENT or SEGMENT_ALLOCATE_ procedure. Cause.
Event Messages 3 ZSCP-EVT-USESEGMENT-ERR overloaded. For ALLOCATESEGMENT and SEGMENT_ALLOCATE_ error codes, see Guardian Procedure Errors and Messages Manual. 3 ZSCP-EVT-USESEGMENT-ERR An SCP call to the Guardian USESEGMENT procedure failed. Tokens in Event Message (contains only standard event-message tokens) Message Text USESEGMENT failed Cause. The SCP process called the USESEGMENT procedure to access a segment, but the USESEGMENT procedure failed because the specified segment has not been allocated.
Event Messages 5 ZSCP-EVT-RECV-READUPDATE-ERR Recovery. Direct command messages to another SCP process or hold them until another SCP process is started. The SCP process might need more data pages. Try restarting the SCP process using a larger value for the DATAPAGES startup parameter. If the problem recurs, obtain this information (if available) before calling a Compaq representative: the SAVEABEND file, the SCF log, the SCP trace file, and the CPU dump.
Event Messages 7 ZSCP-EVT-BAD-TABLE ZSCP-TKN-ERRCODE contains the error code returned by the file system. Cause. An SCP call to the AWAITIO procedure failed on the file $RECEIVE with the indicated error. SCP calls AWAITIO to complete an I/O operation initiated by a procedure such as READUPDATE. AWAITIO returned a condition code other than CCE; the cause might be an error in the SCP program. Effect. The SCP process issues this event message and calls the ABEND or PROCESS_STOP_ procedure.
Event Messages 8 ZSCP-EVT-SWITCH-CMD-FAIL If there is no backup process, the file system returns error 201 (nonexistent process) to every application that is awaiting a response from the SCP process. The process that created the SCP process receives system message –101, indicating process abnormal deletion. Recovery. If there is no backup process, direct command messages to another SCP process or hold them until another SCP process is started.
Event Messages 10 ZSCP-EVT-BAD-BKP Cause. An SCP call to the CHECKPOINT procedure failed. The SCP process tried to checkpoint too much data (the stack size, the counts for all of the buffers, and the total size of all of the file sync blocks). Effect. The backup process does not receive the most recent checkpoint information. The SCP process issues this message and calls the ABEND or PROCESS_STOP_ procedure.
11 ZSCP-EVT-SPI-ERR Event Messages 11 ZSCP-EVT-SPI-ERR An SCP call to one of the Guardian SPI procedures failed. Tokens in Event Message ZSCP-TKN-ERRCODE <1> token-type ZSPI-TYP-INT. Message Text Unrecoverable SPI error: <1> ZSCP-TKN-ERRCODE contains the error code returned by the SPI procedure.
Event Messages 12 ZSCP-EVT-BAD-QUEUE this information (if available) before calling a Compaq representative: the SAVEABEND file, the SCF log, the SCP trace file, and the CPU dump. 12 ZSCP-EVT-BAD-QUEUE The SCP process encountered an internal queue error during command processing. Tokens in Event Message ZSCP-TKN-TYPE <1> token-type ZSPI-TYP-INT. ZSCP-TKN-ERRCODE <2> token-type ZSPI-TYP-INT.
Event Messages 13 ZSCP-EVT-CANCELTIMEOUT-ERR 13 ZSCP-EVT-CANCELTIMEOUT-ERR An SCP call to the Guardian CANCELTIMEOUT procedure failed. Tokens in Event Message ZSCP-TKN-TAG <1> token-type ZSPI-TYP-INT. Message Text Request CANCELTIMEOUT failed; tag: <1> ZSCP-TKN-TAG contains the CANCELTIMEOUT tag. Cause. An SCP call to the CANCELTIMEOUT procedure failed. CANCELTIMEOUT cancels a timer (requested by SIGNALTIMEOUT) by using the tag that resulted from the SIGNALTIMEOUT procedure.
Event Messages 15 ZSCP-EVT-BUF-SPACE-MISCALC ZSCP-TKN-ERRCODE contains a Compaq internal program error, useful only to members of the Compaq development organization. Cause. The SCP process encountered an internal memory-pool error. The memory pool, usually allocated in extended data segments, is not available for processing. Effect. The SCP process calls the ABEND or PROCESS_STOP_ procedure and stops. The backup process created the SCP process.
Event Messages 16 ZSCP-EVT-BAD-BUF 16 ZSCP-EVT-BAD-BUF The SCP process received a system message that it cannot process. Tokens in Event Message (contains only standard event-message tokens) Message Text Internal buffer error Cause. The SCP process received a system message that it could not process. The SCP process code does not include processing of a system message with this message number. This message was not anticipated. Effect. The SCP process calls the ABEND or PROCESS_STOP_ procedure and stops.
Event Messages 18 ZSCP-EVT-CANCEL-MSG-REJ This event commonly results from an insufficient number of time-list elements (TLEs). TLEs are a system resource configured during system generation. A TLE is allocated for every timeout procedure. If all TLEs are allocated, a procedure call requiring a TLE fails. Effect. The SCP process stops the backup process, if there is one, and calls the ABEND or PROCESS_STOP_ procedure.
Event Messages 20 ZSCP-EVT-ACB-FULL ZSCP-TKN-ERRCODE contains the error code returned by the file system. Cause. The SCP process uses the READUPDATE procedure to read incoming command messages from its $RECEIVE file. If no response is required, the SCP process completes the command message using the REPLY procedure. If the REPLY procedure does not complete with condition code CCE (condition code equal), the command-message originator is left with an uncompleted command message. Effect.
Event Messages 22 ZSCP-EVT-TIMEOUT-MSG-REJ Cause. The SCP RCB is full. The SCP process is receiving new command messages more quickly than pending commands are being processed. Effect. The SCP process issues this event message and stops reading command messages until table space becomes available (as pending command messages are completed). Recovery. Divide the processing load by starting and opening additional SCP processes. If the event begins to repeat, notify the system manager.
Event Messages 24 ZSCP-EVT-POOL-FULL process receives a request for a subsystem process that is not already open, it creates a new entry in the table. If the table is full, the SCP process searches the table for an entry that it can delete. The SCP process searches for an entry for a subsystem process for which no request is pending. In either case, if the SCP process cannot find an entry to delete, it issues this event. Effect.
26 ZSCP-EVT-BKP-NEWPROCESS-ERR Event Messages created, and the backup process is not created. The procedure can fail due to a shortage of time-list elements (TLEs). TLEs are system resources configured during system generation. The system allocates one TLE for each call to a timeout procedure. If all configured TLEs are allocated, a procedure call requiring a TLE fails. Effect. There is no backup process.
Event Messages 27 ZSCP-EVT-CKPT-WRITE-ERR Recovery. If the SCP process gives up trying to create a backup process, notify the system manager. The SCP process should have a backup process. 27 ZSCP-EVT-CKPT-WRITE-ERR An SCP checkpoint write to the backup process failed. Tokens in Event Message ZSCP-TKN-ERRCODE <1> token-type ZSPI-TYP-INT. Message Text Checkpoint write failed; error <1> ZSCP-TKN-ERRCODE contains the error code returned by the file system. Cause.
29 ZSCP-EVT-SCPTRACE-ERR Event Messages ZSCP-TKN-ERRCODE contains the error code returned by the file system. Cause. The OPEN or FILE_OPEN_ procedure returned an error when SCP attempted to open its backup process. Effect. If the backup process exists, it is stopped and restarted. If there is no backup process, one is started. Recovery. The SCP process should have a backup process.
30 ZSCP-EVT-CPU-SWITCH Event Messages Cause. The SCP process issues this noncritical event message when there is a problem with tracing (initiated with a TRACE command). The error code indicates the cause. Effect. The SCP process issues this event message, turns tracing off, and continues processing. Recovery. Determine a recovery action based on the SPI error code.
31 ZSCP-EVT-PROC-DOWN Event Messages 31 ZSCP-EVT-PROC-DOWN The primary SCP process has stopped in a sufficiently orderly manner to be able to issue this event before stopping. Tokens in Event Message ZSCP-TKN-CAUSE-PROC-DOWN <1> token-type ZSPI-TYP-ENUM. Message Text Process terminated because <1> ZSCP-TKN-CAUSE-PROC-DOWN specifies the reason that the primary process was stopped.
33 ZSCP-EVT-SUMSTATE-CHG Event Messages 33 ZSCP-EVT-SUMSTATE-CHG The summary state of the SCP process changed. Tokens in Event Message ZCOM-TKN-OLD-OBJSTATE <1> token-type ZSPI-TYP-ENUM. ZCOM-TKN-OBJSTATE <2> token-type ZSPI-TYP-ENUM. Message Text State changed from <1> to <2> ZCOM-TKN-OLD-OBJSTATE specifies the old object summary state.
Event Messages 35 ZSCP-EVT-SECURITY-VIOL ZSCP-TKN-REPLY-ERROR indicates the reason that SCP cannot deliver the reply. Valid values and their meanings are: ZSCP-VAL-REPLY-ERROR-CANCELED The command specified in the original request was canceled between the time the request was issued and the time the response was returned. ZSCP-VAL-REPLY-ERROR-UNKNOWN The requester that issued the command either no longer exists or has been reopened under another file number. Cause.
Event Messages 36 ZSCP-EVT-DEAD-DEVICE Cause. An unauthorized requester issued a sensitive command. SCP processes accept sensitive commands from requesters that belong to the super ID, requesters with the same group as the creator access ID of the SCP process handling the request, or requesters that belong to groups specified by SCP in ZCOM-TKN-GETVSN-SENSGRP tokens in SCP’s GETVERSION response. Effect. The command is rejected. Recovery. Reissue the request from an authorized requester.
Event Messages 37 ZSCP-EVT-BAD-GETVSN ZCOM-TKN-OBJNAME contains the name of the object to which the GETVERSION command was directed. ZSCP-TKN-VSN-PROB contains the specific error encountered. Possible values and the error conditions they indicate are: ZCOM-ERR-BAD-SERV-GETVSN The SCP process received an error from the SSGETTKN procedure when trying to retrieve a token from the GETVERSION response buffer. ZCOM-ERR-BAD-SERV-VSN The SCP process detected an unknown token in the GETVERSION response buffer.
38 ZSCP-EVT-BAD-PUTMEMORY Event Messages SERV-ERR on page A-9, and the description of ZCOM-ERR-FS-ERR in the SPI Common Extensions Manual. Recovery. Check the software versions for incompatibilities and make sure the request contains the correct name of the subsystem manager process. 38 ZSCP-EVT-BAD-PUTMEMORY The SCP process cannot allocate memory for processing a request because of insufficient buffer space.
Event Messages 39 ZSCP-EVT-PFS-FULL Recovery. Start a new SCP process other than the current one and send the request to the new SCP process.
A Errors SCP processes generate errors that fall into five categories: • • • • • Startup error messages issued during SCP process initialization ZCOM errors returned in SPI error lists ZCMK errors returned in SPI error lists ZSCP errors returned in SPI error lists ZTRC errors returned in SPI error lists This section describes SCP startup errors, ZCOM errors issued exclusively by SCP processes, ZSCP errors, and ZTRC errors.
Startup Errors Errors Startup Errors An SCP process generates the following text messages in response to the indicated error conditions encountered during process startup (before the process enters its routine processing cycle). After issuing the message, the SCP process calls the Guardian ABEND or PROCESS_STOP_ procedure. The SCP process writes the message to its home terminal. If a home terminal was not specified in the RUN command, the default is the terminal that is running the command interpreter.
Additional Startup Errors Errors Must be run as super ID The SCP program PROGID must be set to the super ID. $RECEIVE open error: file-system-error When the SCP process attempted to open its $RECEIVE file, the OPEN procedure returned a file-system error and did not finish successfully.
Error Notation Errors Error Notation For each error, a syntax box lists the tokens that appear in the error list. The notation used in the box for simple tokens is a shorthand version of the essential information given in the DDL TOKEN-CODE statement. Following the box, tokens in the error list are described in the order that they appear. If there is associated message text, key numbers within angle brackets () identify the tokens from which message text is derived.
–987 ZCOM-ERR-REQID-INV Errors Table A-2.
–989 ZCOM-ERR-CMD-CANCELED Errors –989 ZCOM-ERR-CMD-CANCELED The specified command message was canceled. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZSPI-TKN-ENDLIST Corresponding SCF Error Message Request has been cancelled Cause. The SCP process received a command to cancel a command message that it was processing. The command message was successfully canceled. Effect.
–991 ZCOM-ERR-RCB-FULL Errors –991 ZCOM-ERR-RCB-FULL The SCP process request control block table is full. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZSPI-TKN-ENDLIST Corresponding SCF Error Message SCP's request control block table is full Cause. All command-message control blocks are in use.
–993 ZCOM-ERR-NO-TLE Errors –993 ZCOM-ERR-NO-TLE A command message containing ZCOM-TKN-CMD-TIMEOUT could not be processed because no time-list element (TLE) is available. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZSPI-TKN-ENDLIST Corresponding SCF Error Message No TLE was available for command timeout Cause. A TLE is used to measure when a specified interval of time has expired.
–995 ZCOM-ERR-SERVNAME-INV Errors –995 ZCOM-ERR-SERVNAME-INV An invalid communications subsystem process name was specified by ZSPI-TKNMANAGER, ZCOM-TKN-XMGR, or ZCOM-TKN-OBJNAME. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZSPI-TKN-ENDLIST Corresponding SCF Error Message Internal Error: invalid name specified in MANAGER or OBJNAME token Cause.
–997 ZCOM-ERR-BAD-SERV-GETVSN Errors Recovery. Reissue the request. If this does not help, restart the subsystem and reissue the request. If the problem recurs, contact a Compaq representative. –997 ZCOM-ERR-BAD-SERV-GETVSN A subsystem returned an invalid GETVERSION response to an SCP process.
–999 ZCOM-ERR-MGRNAME-INV Errors Recovery. Try reissuing the command. If the problem persists with a NonStop Kernel subsystem, contact your Compaq representative. –999 ZCOM-ERR-MGRNAME-INV The process name specified by ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR was invalid, or the process does not exist. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZSPI-TKN-ENDLIST Error Text Manager name is invalid Cause.
1 ZSCP-ERR-OBJ-ACTIVE Errors Table A-4. ZSCP Errors, Listed by Name Name Number ZSCP-ERR-OBJ-ACTIVE 1 ZSCP-ERR-TKN-VAL-REQ 4 ZSCP-ERR-TRACE-MOD-REQ 6 1 ZSCP-ERR-OBJ-ACTIVE The SCP process is still opened by other processes and therefore cannot be stopped.
3 ZSCP-ERR-NO-INFO Errors Effect. The command is rejected, and this error is returned in the response. Recovery. No recovery is required. However, because SCP processes normally run as fault-tolerant process pairs, you might want to investigate why there is no backup process. 3 ZSCP-ERR-NO-INFO No information is available for a specified object.
4 ZSCP-ERR-TKN-VAL-REQ Errors .Z-TOKENCODE contains the token code of the token or structure missing the value. For the printed message, SCF converts this value to a printable name.
5 ZSCP-ERR-BKUP-MODIF-NOT-ALLOW Errors 5 ZSCP-ERR-BKUP-MODIF-NOT-ALLOW An attempt was made to modify a trace of a backup process. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZSPI-TKN-ENDLIST Corresponding SCF Error Message Trace parameters may not be modified for a backup SCP process Cause. A TRACE command was issued to modify the trace of a backup process.
ZTRC Errors Errors ZTRC Errors Table A-5 and Table A-6 on page A-17 list the tracing-related errors defined by ZTRC. Table A-5.
ZTRC Errors Errors Table A-5. ZTRC Errors, Listed by Number Number Name -984 ZTRC-ERR-TRACE-MODIF-CONFL -985 ZTRC-ERR-COLL-FAIL -986 ZTRC-ERR-ATTR-NOT-MODIF Table A-6.
–801 ZTRC-ERR-ATTR-INV Errors Table A-6. ZTRC Errors, Listed by Name Name Number ZTRC-ERR-START-PEND -849 ZTRC-ERR-TRACE-FILE-ERR -854 ZTRC-ERR-TRACE-FILE-SIZE -862 ZTRC-ERR-TRACE-MODIF-CONFL -984 ZTRC-ERR-TRACE-MODIF-REQ -983 ZTRC-ERR-TRC-RCV-FILE-ERR -861 ZTRC-ERR-WORK-LOCK -831 –801 ZTRC-ERR-ATTR-INV A TRACE command contained an invalid parameter.
–810 ZTRC-ERR-LCB-INV Errors ZTRC-TKN-INIT-ERR-DETAIL is included in the error list generated by an SCP process. It is not applicable to this error and is set to 0. Cause. A specified trace parameter value is out of range or had the wrong format. Effect. The request is rejected. Recovery. Correct the value and reissue the request. –810 ZTRC-ERR-LCB-INV Tracing of the SCP process was interrupted by a processing error involving an invalid link control block (LCB).
–812 ZTRC-ERR-FUNC-INV Errors –812 ZTRC-ERR-FUNC-INV A collector process detected an invalid tracing function in a request.
–819 ZTRC-ERR-SEG-OVERFLOW Errors Recovery. Verify that the command is being sent to the correct SCP process and that the process is actively tracing. –819 ZTRC-ERR-SEG-OVERFLOW The trace collector encountered a MOVEX procedure error when working with an extended data segment.
–830 ZTRC-ERR-NEWPROCESS Errors Recovery. Let the existing trace proceed, or stop it and reissue the new trace request. –830 ZTRC-ERR-NEWPROCESS A NEWPROCESS or PROCESS_CREATE_ error occurred during an attempt to start a collector process.
–834 ZTRC-ERR-SEG-ALLOC Errors Cause. This is an operating system problem. Effect. Trace data might be lost. Recovery. Contact your Compaq representative. –834 ZTRC-ERR-SEG-ALLOC An extended data segment, used for storing trace information, could not be allocated.
–836 ZTRC-ERR-SEG-LOCK Errors Effect. Trace data might be lost. Recovery. Contact your Compaq representative. –836 ZTRC-ERR-SEG-LOCK The extended data segment allocated for trace processing could not be locked.
–841 ZTRC-ERR-DEV-NOT-FOUND Errors Effect. The request is rejected. Recovery. Correct the device name and reissue the request. –841 ZTRC-ERR-DEV-NOT-FOUND The device specified by ZSPI-TKN-MANAGER or ZCOM-TKN-OBJNAME in the TRACE command could not be found. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME <1> token-type ZSPI-TYP-STRING ZSPI-TKN-ENDLIST Corresponding SCF Error Message Unable to find trace device for <1> Cause.
–846 ZTRC-ERR-SCP-INTL-ERR Errors –846 ZTRC-ERR-SCP-INTL-ERR An SCP process trace-processing error occurred. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZSPI-TKN-ENDLIST Corresponding SCF Error Message Internal Error: SCP trace error encountered Cause. The SCP process detected an error during tracing activity (a call to DSM_TRACE_INIT_ specified the wrong CPU). Effect. The trace is canceled. Recovery.
–848 ZTRC-ERR-COLL-INTL-ERR Errors –848 ZTRC-ERR-COLL-INTL-ERR A collector process encountered a file-system error. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZSPI-TKN-ENDLIST Corresponding SCF Error Message Internal Error: Trace collector error Cause. The trace-data collector process initiated by an SCP process attempted to execute a file-system procedure call, and the procedure returned an error.
–850 ZTRC-ERR-COLL-VSN-INCOMP Errors –850 ZTRC-ERR-COLL-VSN-INCOMP There is a software-release version incompatibility between the SCP process and the collector process that is being initiated for tracing.
–852 ZTRC-ERR-BAD-TRACE-PARAMS Errors ZTRC-TKN-INIT-ERR-DETAIL contains the error number returned by the DSM_TRACE_INIT_ procedure.
–854 ZTRC-ERR-TRACE-FILE-ERR Errors Error Number Parameter Name Text Inserted in SCF Message Problem 20 “BACKUP” Not checked 21 “COUNT” Number of trace records to record is less than 0 or too large 22 “RECSIZE” Specified record size is less than 16 or greater than the specified block size Cause. The SCP process issues a call to the DSM_TRACE_INIT_ procedure based on the information provided by the requester in the TRACE-MODIF structure in the TRACE command.
–855 ZTRC-ERR-LOCK-MEMORY-ERR Errors –855 ZTRC-ERR-LOCK-MEMORY-ERR A collector process could not lock memory. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZTRC-TKN-INIT-ERR-DETAIL <1> token-type ZSPI-TYP-INT ZSPI-TKN-ENDLIST Corresponding SCF Error Message Lock memory error [; Detail = <1>] ZTRC-TKN-INIT-ERR-DETAIL is included in the error list generated by an SCP process.
–857 ZTRC-ERR-COLL-OPEN-ERR Errors –857 ZTRC-ERR-COLL-OPEN-ERR The SCP process could not open a collector process. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZTRC-TKN-INIT-ERR-DETAIL <1> token-type ZSPI-TYP-INT ZSPI-TKN-ENDLIST Corresponding SCF Error Message File error while opening the collector; File System error: <1> ZTRC-TKN-INIT-ERR-DETAIL contains the file-system error. Cause.
–859 ZTRC-ERR-INTR-NOT-RECVD Errors –859 ZTRC-ERR-INTR-NOT-RECVD The subsystem failed to start a trace that was prepared by the collector.
–861 ZTRC-ERR-TRC-RCV-FILE-ERR Errors Recovery. Retry the request. If the problem recurs, contact your Compaq representative. –861 ZTRC-ERR-TRC-RCV-FILE-ERR The SCP process detected an error trying to write to or read from its $RECEIVE file.
–983 ZTRC-ERR-TRACE-MODIF-REQ Errors Recovery. Specify a larger file, a smaller ZXDS-PAGES value, or a nonexistent trace file, and retry the request. –983 ZTRC-ERR-TRACE-MODIF-REQ No modifiers were specified in the trace command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZSPI-TKN-ENDLIST Corresponding SCF Error Message Trace command modifier required. Cause.
–985 ZTRC-ERR-COLL-FAIL Errors .Z-OFFSET specifies the byte offset (within the structured token) of the fields containing the incompatible values. Cause. This error is generated if the request tries to modify the record size to a value less than 16 or greater than 4050 bytes. Effect. The request is rejected. Recovery. Reissue the request after correcting the modifier value or omitting one of the modifiers from the request.
–986 ZTRC-ERR-ATTR-NOT-MODIF Errors –986 ZTRC-ERR-ATTR-NOT-MODIF A TRACE command specified an attribute that cannot be modified. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZSPI-TKN-PARM-ERR token-type ZSPI-TYP-PARM-ERR .Z-TOKENCODE <1> type ZSPI-DDL-TOKENCODE .Z-INDEX type ZSPI-DDL-UINT .
Retired Error Definitions Errors Effect. The request is rejected. Recovery. Correct the request and reissue it.
B Tracing Topic Page Tracing Overview B-2 The Trace Information Structure B-8 Initiating a Trace B-10 Modifying a Trace B-12 Stopping a Trace B-12 Subsystem Control Point (SCP) Management Programming Manual—520619-001 B- 1
Tracing Overview Tracing Tracing Overview Use the TRACE command to keep a record of an object’s activity (messages sent and received, for example). The subsystem process that controls the object performs the trace. If requested by the subsystem, SCP starts and initializes the collector process that receives the trace records. The trace procedure writes trace records to an extended data segment in memory, and the collector eventually copies them to a disk file.
The Tracing Environment Tracing The Tracing Environment A tracing environment consists of the trace procedure called by the tracing process, the extended data segment to which the trace data is written, a disk file for recording the trace records, and a collector process that copies trace data from the extended data segment into the disk file.
TRACE Command Processing Tracing SCP Process Interpretation of ZCOM-TKN-GETVSN-TRACE-SUPP ZTRC-VAL-SUPP-NONE SCP performs no trace work for the subsystem. SCP forwards all TRACE commands to the subsystem without intervention. ZTRC-VAL-SUPP-ALL Equivalent to ZTRC-VAL-SUPP-SCP-ONLY. ZTRC-VAL-SUPP-SCP-ONLY SCP uses the SCP tracing environment for all subsystem objects: LDEV and non-LDEV. ZTRC-VAL-SUPP-LDEV Equivalent to ZTRC-VAL-SUPP-SCP-ONLY.
Tracing to Memory Tracing Tracing to Memory If ZTRC-DDL-TRACE-MODIF.ZCOLL has a value of ZSPI-VAL-FALSE, trace data is written primarily to the extended data segment. The collector passively monitors the trace and writes the data remaining in the segment to disk only when the trace is stopped because: • • • The requester issues a TRACE command to stop the trace. The number of records written to the segment is equal to ZTRC-DDL-TRACEMODIF.ZCNT (if ZCNT contains a positive value).
Tracing to Disk Tracing Tracing to Disk If ZTRC-DDL-TRACE-MODIF.ZCOLL has a value of ZSPI-VAL-TRUE or is blank, the collector actively monitors the extended segment and write blocks of trace records to the disk file as they become available. When tracing to disk, the collector process reads and writes a block of trace records from the segment, as Figure B-3 shows. Figure B-3.
Tracing to Disk Tracing Figure B-4. A Tracing Process Overtakes a Collector Process Trace Records Wrap to Beginning of Segment Extended Data Segment New Records Written Over Old by Tracing Process Old Records Already Written to Disk by Collector Records Written by Tracing Process Start of Next Block to Be Written to Disk VST040.vsd Resolving a File-Full Condition The value of ZTRC-DDL-TRACE-MODIF.
The Trace Information Structure Tracing The Trace Information Structure Requesters include the extensible structured token ZTRC-MAP-TRACE-MODIF in TRACE commands to specify the details of the trace. ZTRC-MAP-TRACE-MODIF is based on ZTRC-DDL-TRACE-MODIF: def ZTRC-DDL-TRACE-MODIF. 02 ZSTOP type ZSPI-DDL-BOOLEAN. 02 ZPRIM type ZSPI-DDL-BOOLEAN. 02 ZREC-SIZE type ZSPI-DDL-INT. 02 ZCNT type ZSPI-DDL-INT2. 02 ZXDS-PAGES type ZSPI-DDL-INT. 02 ZCOLL type ZSPI-DDL-BOOLEAN. 02 ZFNAME type ZSPI-DDL-FNAME32.
The Trace Information Structure Tracing ZCNT specifies the maximum number of trace records to be collected. Valid values are: 0 When modifying a trace, the current maximum is retained. When starting a trace, this value is equivalent to -1. -1 Records are collected until the trace is stopped or until end-offile is encountered on the collector file (if ZWRAP is set to FALSE). 1 through (2**32)-1 Tracing stops after the specified number of records is captured.
Initiating a Trace Tracing Initiating a Trace To initiate a trace, issue a TRACE command containing: ZSPI-TKN-MANAGER (old) or ZCOM-TKN-XMGR Set to the name of the subsystem manager process. If no OBJNAME token is included, this is the object that will be traced. ZCOM-TKN-OBJNAME Set to the name of the object to be traced. If omitted, the object is the manager process specified in the MANAGER or XMGR token. Some subsystems might include the manager name as part of the object name.
Specifying the Trace-Data Disk File Tracing Algorithm for Computing Trace File Extent Size and Number of Extents The trace collector uses this algorithm to calculate an extent size and maximum number of extents for trace files it creates: 1. Calculate the required number of disk pages. a. Add 3 pages (for header information) to the number of extended memory segment pages requested in ZTRC-DDL-TRACE-MODIF.ZXDS-PAGES. 2. Set the test extent size to 2 pages. 3.
Modifying a Trace Tracing Modifying a Trace Your application can modify a currently executing trace by sending a TRACE command containing: ZTRC-DDL-TRACE-MODIF.ZSTOP Set to ZSPI-VAL-FALSE (default) or blank. ZTRC-DDL-TRACE-MODIF.ZFNAME Set to blank. Three parameters can be modified: • • • The number of records to be recorded (ZTRC-DDL-TRACE-MODIF.ZCNT). If ZCNT contains 0, the current record count is retained. Otherwise, the record count is set to the new value.
Index A ABORT command 5-8 ALTER command 5-9 AUTOSTOP startup parameter starting an SCP process 2-5 stopping an SCP process 2-13 B BACKUPCPU startup parameter 2-4 Buffer see Message buffer size C CMPTC trace collector B-3 CMPTRACE tracing environment B-3 Collector see Event collector or Trace collector COLLECTOR startup parameter 2-5 COLLECTOR-n startup parameters 2-5 Command security general 5-7 request validation role of SCP 3-5 Command timeout 3-6 Commands ABORT 5-8 ALTER 5-9 GETVERSION 5-12 INFO 5-15 L
E Index D-series SCP processes (continued) handling of obsolete fields in structures 3-8 message routing 3-3 native object type 3-10 requester identification 3-5 ZCMK command and response tokens 3-10 E Errors during SCP startup A-2 file-system error 201 2-12, 2-13 file-system message -38 3-4 retired definitions 4-28, A-38 returned by DSM_TRACE_INIT_ procedure A-29 see also ZCOM-ERR-... see also ZSCP-ERR-... see also ZTRC-ERR-...
M Index Log file (continued) specifying with LOG or LOGFILE startup parameter 2-6 specifying with OUT process option 2-4 LOG startup parameter see LOGFILE startup parameter LOGFILE startup parameter considerations for specifying 2-11 starting a D-series SCP process 2-6 M Management applications acting as message router 5-7 communicating with an SCP process 212, 3-2, 3-3 converting to D-series 3-9 implications of D-series changes 3-7 interprocess communications restrictions 3-9 Manager process D-series id
R Index R RECEIVEDEPTH startup parameter 2-6 REQID see Requester Identification Requester Identification (REQID) 3-5 RESETSTATS command 5-24 Response-message tokens, common 5-5 Retired definitions 4-28 RUN command process options 2-3 starting an SCP process 2-2 startup parameters 2-4 S SCB see Server Control Block table 6-28 SCF see Subsystem Control Facility SCP see Subsystem Control Point SCPTC trace collector B-3 SCPTCOL trace collector B-3 SCPTRACE tracing environment B-3 Security see Command securit
T Index Subsystem Control Point (SCP) (continued) starting with NEWPROCESS procedure 2-10 starting with PROCESS_CREATE_ procedure 2-7 starting with RUN command 2-2 supported commands 4-2 sync depth 2-12, 2-13 SWAP process option 2-4 Swap volume see SWAP process option SWAPVOL startup parameter 2-7 SWITCH command 5-34 T TERM process option 2-4 Tokens ZCOM 4-1 ZSCP 4-3 ZTRC 4-25 Trace collectors B-3 TRACE command 5-35 Trace facility see Tracing Tracing an SCP process 5-35 CMPTRACE environment B-3 initiatin
Z Index ZCOM-DDL-TRACE-MODIF 4-29 ZCOM-DDL-TRACE-WORK 4-29 ZCOM-ERR-ATTR-NOT-MODIF A-38 ZCOM-ERR-BAD-SERV-GETVSN cause of ZSCP-EVT-BAD-GETVSN 630 error definition A-10 ZCOM-ERR-BAD-SERV-VSN cause of ZSCP-EVT-BAD-GETVSN 630 error definition A-10 ZCOM-ERR-BAD-TIMEOUT A-8 ZCOM-ERR-CMD-CANCELED A-6 ZCOM-ERR-CNTXT-INV A-6 ZCOM-ERR-FS-ERR 6-30 ZCOM-ERR-MGRNAME-INV A-11 ZCOM-ERR-NO-TLE A-8 ZCOM-ERR-OBJ-ALRDY-INSUMSTATE and sync-depth 2-12 ZCOM-ERR-RCB-FULL A-7 ZCOM-ERR-REQID-INV A-5 ZCOM-ERR-SCB-FULL A-7 ZCOM-ER
Z Index ZCOM-TKN-NEWPROCESS-ERR 4-1 ZCOM-TKN-NEW-CPU 6-25 ZCOM-TKN-OBJNAME common command token 5-4 common response token 5-6 in ZSCP-EVT-BAD-GETVSN 6-30 in ZSCP-EVT-DEAD-DEVICE 6-29 role in message routing 3-3 ZCOM-TKN-OBJSTATE 6-27 ZCOM-TKN-OBJTYPE 5-5, 5-6 ZCOM-TKN-OLD-CPU 6-25 ZCOM-TKN-OLD-OBJSTATE 6-27 ZCOM-TKN-REQID-PAID 3-6, 5-3 in ZSCP-EVT-SECURITY-VIOL 6-28 ZCOM-TKN-REQID-PHANDLE 3-6, 5-3 ZCOM-TKN-REQID-PPROGXFILE 3-6, 5-3 ZCOM-TKN-REQID-PSTRING 3-6, 5-3 ZCOM-TKN-SERV-ERR 4-1 in ZCOM-ERR-SERV-ERR
Z Index ZSCP-EVT-BUF-SPACE-MISCALC 6-16 ZSCP-EVT-CANCELTIMEOUT-ERR 615 ZSCP-EVT-CANCEL-MSG-REJ 6-18 ZSCP-EVT-CHKPT-OVERFLOW 6-11 ZSCP-EVT-CKPT-WRITE-ERR 6-23 ZSCP-EVT-CPU-SWITCH 6-25 ZSCP-EVT-DEAD-DEVICE 6-29 ZSCP-EVT-DEL-SIGNALTIMEOUTERR 6-17 ZSCP-EVT-MEMORY-POOL-ERR 6-15 ZSCP-EVT-PFS-FULL 6-31 ZSCP-EVT-POOL-FULL 6-21 ZSCP-EVT-PROC-DOWN 6-26 ZSCP-EVT-RCB-FULL 6-19 ZSCP-EVT-RECV-READUPDATEERR 6-9 ZSCP-EVT-SCB-FULL 6-20 ZSCP-EVT-SCPTRACE-ERR 6-24 ZSCP-EVT-SECURITY-VIOL 6-28 ZSCP-EVT-SHUT-SIGNALTIMEOUTER 6-
Z Index ZSCP-TKN-ERRCODE (continued) in ZSCP-EVT-BKP-NEWPROCESSERR 6-22 in ZSCP-EVT-BKP-OPEN-ERR 6-24 in ZSCP-EVT-CKPT-WRITE-ERR 623 in ZSCP-EVT-MEMORY-POOLERR 6-16 in ZSCP-EVT-RECV-READUPDATEERR 6-9 in ZSCP-EVT-SCPTRACE-ERR 6-24 in ZSCP-EVT-SPI-ERR 6-13 in ZSCP-EVT-SPI-REPLY-ERR 6-19 ZSCP-TKN-PUTMEM-PROB 6-31 ZSCP-TKN-REPLY-ERROR 6-28 ZSCP-TKN-TAG in ZSCP-EVT-CANCELTIMEOUTERR 6-15 in ZSCP-EVT-CANCEL-MSG-REJ 618 in ZSCP-EVT-TIMEOUT-MSG-REJ 620 ZSCP-TKN-TYPE in ZSCP-EVT-BAD-QUEUE 6-14 in ZSCP-EVT-BAD-TABLE
Special Characters Index ZTRC-ERR-NEWPROCESS A-22 ZTRC-ERR-NOT-ACTV A-20 ZTRC-ERR-RCV-OPEN-ERR A-31 ZTRC-ERR-SCP-INTL-ERR A-26 ZTRC-ERR-SEG-ALLOC A-23 ZTRC-ERR-SEG-LOCK A-24 ZTRC-ERR-SEG-OVERFLOW A-21 ZTRC-ERR-SEG-UNAVAIL A-23 ZTRC-ERR-START-PEND A-27 ZTRC-ERR-TRACE-FILE-ERR A-30 ZTRC-ERR-TRACE-FILE-SIZE A-34 ZTRC-ERR-TRACE-MODIF-CONFL A35 ZTRC-ERR-TRACE-MODIF-REQ A-35 ZTRC-ERR-TRC-RCV-FILE-ERR A-34 ZTRC-ERR-WORK-LOCK A-22 ZTRC-MAP-TRACE-MODIF 4-25, B-8 in TRACE command 5-35 ZTRC-TKN-INIT-ERR-DETAIL 4-25
