DSM/SCM Event Management Programming Manual Abstract This manual provides information about the token-oriented event messages from the programmatic interface to the Distributed Systems Management/Software Configuration Manager (DSM/SCM). It serves as both a reference manual for DSM/SCM event messages and a programmer’s manual for writing applications and filters to select DSM/SCM event messages.
Document History Part Number Product Version Published 520610-005 DSM/SCM D46 December 2003 520610-006 DSM/SCM D46 April 2004 520610-007 DSM/SCM D46 December 2004 529844-003 DSM/SCM G01 (ABP) and H01 July 2005
DSM/SCM Event Management Programming Manual Index Examples What’s New in This Manual Manual Information xi New and Changed xii Figures xi About This Manual xiii Who Should Use This Manual xiii What’s in This Manual xiii Where to Get More Information xiv Notation Conventions xiv 1. Introduction What Is DSM/SCM? 1-1 How Event Management Works 1-4 How EMS Handles DSM/SCM Event Messages 1-5 2.
. Common Definitions Contents 4. Common Definitions SPI Standard Definitions 4-2 EMS Standard Definitions 4-4 DSM/SCM Definitions 4-6 Buffer Declarations 4-6 Predefined Token and Field Values Simple Tokens 4-21 4-6 5.
. Event Messages (continued) Contents 5.
5. Event Messages (continued) Contents 5.
5. Event Messages (continued) Contents 5.
5. Event Messages (continued) Contents 5.
5. Event Messages (continued) Contents 5.
6. Event Messages From Other Subsystems Contents 6. Event Messages From Other Subsystems 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0001 ZBRT-EVT-DPTERR 6-2 ZBRT-EVT-DPTWARN 6-3 ZBRT-EVT-DPTMERR 6-4 ZBRT-EVT-DPTMWARN 6-5 ZBRT-EVT-DPTMOUNTMESSAGE 6-6 ZBRT-EVT-BKUPTERR 6-7 ZBRT-EVT-BKUPTWARN 6-8 ZBRT-EVT-BKUPTMERR 6-9 ZBRT-EVT-BKUPTMWARN 6-10 ZBRT-EVT-BKMOUNTMESSAGE 6-11 ZBRT-EVT-BKUPERROR 6-11 ZSGN-EVT-SYSGEN-COMPLETED 6-12 A. Token Codes B. File-System Errors C.
Tables (continued) Contents Tables (continued) Table A-1. Table B-1. Table C-1.
Contents DSM/SCM Event Management Programming Manual—529844-003 x
What’s New in This Manual Manual Information DSM/SCM Event Management Programming Manual Abstract This manual provides information about the token-oriented event messages from the programmatic interface to the Distributed Systems Management/Software Configuration Manager (DSM/SCM). It serves as both a reference manual for DSM/SCM event messages and a programmer’s manual for writing applications and filters to select DSM/SCM event messages.
What’s New in This Manual New and Changed New and Changed • • This manual has been updated to indicate support for H-series RVUs. The file-system error codes have been updated.
About This Manual The Distributed Systems Management/Software Configuration Manager (DSM/SCM) is a system for the centralized planning, management, and installation of software on distributed HP NonStop™ servers. This manual provides information on the tokenoriented event messages from the programmatic interface to DSM/SCM.
Where to Get More Information About This Manual Where to Get More Information When appropriate, this manual refers you to other manuals for information about a particular subject, such as the HP Data Definition Language for NonStop systems. While using this manual, you might need to refer to other manuals. Other DSM/SCM Information Sources DSM/SCM User’s Guide Provides detailed step-by-step procedures for performing the various tasks possible through each of the DSM/SCM interfaces and tools.
General Syntax Notation About This Manual General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual: UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type.
Notation for Messages About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … 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}...
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
1 Introduction This section provides a brief overview of the Distributed Systems Management/ Software Configuration Manager (DSM/SCM) and its token-oriented programmatic interface. This interface is based on the Subsystem Programmatic Interface (SPI) message format. DSM/SCM supports this programmatic interface for event management only. Using the Event Management Service (EMS), a management application can retrieve the event messages in SPI format generated by DSM/SCM.
What Is DSM/SCM? Introduction • Object Manager The Object Manager runs as a host and target system static server class. It performs all security checks and many database inquiries. The Object Manager is the initial server interface for the user interfaces. It satisfies user interface requests when the other servers are not involved. • Schedule Manager The Schedule Manager runs as a host and target static server.
What Is DSM/SCM? Introduction Figure 1-1. DSM/SCM Components in the Host and Target Environments Host Environment Configuration Builder Planner Interface Object Manager Schedule Manager Input Supervisor PC Utility Server Target Environment Target Activator Target Interface Object Manager Schedule Manager 6530 Utility Server VST001.
How Event Management Works Introduction How Event Management Works Event management is provided by EMS—a collection of processes, tools, and interfaces for the reporting and retrieval of event messages. An event message is a special type of SPI buffer. As a SPI buffer, the event message is in the form of tokens that can be decoded programmatically by management applications.
How EMS Handles DSM/SCM Event Messages Introduction How EMS Handles DSM/SCM Event Messages DSM/SCM components report informational, warning, and error event messages to EMS in response to DSM/SCM batch activities. In addition, events generated by some utilities are included within DSM/SCM events and are also reported to EMS. DSM/SCM records these events in two EMS collectors: • DSM/SCM Alternate Collector ($ZPHI) All DSM/SCM events are sent to this collector.
How EMS Handles DSM/SCM Event Messages Introduction Figure 1-2.
2 Elements of SPI Messages for DSM/SCM A DSM/SCM event message is formatted as a special SPI buffer. Event Management Service (EMS) provides high-level procedures that call SPI procedures to format the event-message buffer. This buffer consists of tokens representing units of information that describe the event in a form that can be retrieved programmatically. This section describes elements of Subsystem Programmatic Interface (SPI) event messages for DSM/SCM.
Source Definition Files Elements of SPI Messages for DSM/SCM Source Definition Files If you write a management application in C, COBOL, TACL, or TAL to receive DSM/SCM event messages, each source module must include these definition files, depending on the language you are using, located on a disk volume chosen by your site: Definition File C COBOL TACL TAL SPI ZSPIC ZSPICOB ZSPITACL ZSPITAL EMS ZEMSC ZEMSCOB ZEMSTACL ZEMSTAL DSM/SCM ZPHIC ZPHICOB ZPHITACL ZPHITAL All language files ar
Elements of SPI Messages for DSM/SCM Other Tokens Other Tokens DSM/SCM event messages also include other tokens to provide information about the event. This subsection briefly reviews the form these tokens can take and the elements that make up these tokens. For more information on the construction of these tokens, see the SPI Programming Manual. Simple Tokens Simple tokens are tokens whose values are single fields or fixed structures. Simple tokens are identified by token codes.
Elements of SPI Messages for DSM/SCM Components of an Event Message Components of an Event Message For the structure and components of each DSM/SCM event message, see Section 5, Event Messages. For more information on the components of an event message, see the EMS Manual.
3 SPI Programming Considerations for DSM/SCM This section describes programming considerations for Distributed Systems Management/Software Configuration Manager (DSM/SCM) event messages. Topic Page Retrieving and Decoding Event Messages 3-1 Considerations for DSM/SCM Event Management 3-2 Writing a Filter 3-3 For more information on event management and the Event Management Service (EMS) filter language (EMF), see the EMS Manual.
SPI Programming Considerations for DSM/SCM Considerations for DSM/SCM Event Management c. Call SSMOVE or SSMOVETKN to move the context token from the response buffer to the GETEVENT command buffer. The context token is needed later, when your application resends the command to get the next event message. d. Call SSGET or SSGETTKN to retrieve the token containing the event message (ZEMS-TKN-EVENT) from the response buffer. e.
Writing a Filter SPI Programming Considerations for DSM/SCM Writing a Filter You can write a filter to select all DSM/SCM event messages or only specific messages, such as messages for certain activities. You have two options: Option File Type Page Create and load a filter object file. Type 845 file generated by the filter compiler 3-3 Create and load a filter table.
SPI Programming Considerations for DSM/SCM Creating and Loading a Standard Filter where: $DPHI is the name of the distributor process. [\system].$0 [\system].$ZPHI filtrobj yyyy-mm-dd hh:mm is the primary collector process. evtsfile printing | P is a disk file that will contain the filtered events. is the alternate collector process. is the filter object file. specifies the date and time when the distributor starts examining events. specifies the type of distributor to be started.
SPI Programming Considerations for DSM/SCM Creating and Loading a Standard Filter Example 3-1.
Creating and Loading a Filter Table SPI Programming Considerations for DSM/SCM Creating and Loading a Filter Table You can use filter tables instead of or in conjunction with the standard compiled filters. Because a compile step is not required, filter tables offer ease of maintenance and improved efficiency. They are particularly useful when you need to filter events by simple criteria such as event number and subsystem ID and when you need frequent and fast online update of filter contents.
Creating and Loading a Filter Table SPI Programming Considerations for DSM/SCM owner-name is the subsystem owner or ID and can include wild-card characters. The subsystem owner in the filter table can be as many as eight characters and starts in column 1. Subsystem owners and IDs must appear only once. You receive an error if you specify a duplicate subsystem owner or ID. subsys-number, NNE event#, n, is the subsystem ID or event number and can include wild-card characters.
Filter Table Examples SPI Programming Considerations for DSM/SCM Filter Table Examples The filter specifications in Example 3-2 select all DSM/SCM event messages by checking for the DSM/SCM subsystem number. Example 3-2. Passing All DSM/SCM Events ?COMMENT Pass all DSM/SCM events owner ?PASS TANDEM subsys event# DSMSCM * The filter specifications in Example 3-3 select event messages only for selected DSM/SCM commands.
4 Common Definitions This section contains general descriptions of the common definitions used by DSM/SCM. DSM/SCM event messages use: Topic Page SPI Standard Definitions 4-2 EMS Standard Definitions 4-4 DSM/SCM Definitions 4-6 For specific information about each definition as it applies to a particular message, see Descriptions of DSM/SCM Event Messages on page 5-24. HP provides each set of definitions in several programming languages. (See Source Definition Files on page 2-2.
SPI Standard Definitions Common Definitions SPI Standard Definitions Definitions whose names begin with ZSPI are SPI definitions. SPI definitions are available to all subsystems that support SPI procedures. They are provided in the SPI DDL file, ZSPIDEF.ZSPIDDL, and in the corresponding definition files for other languages. The SPI definitions used by DSM/SCM consist of header tokens and token types. Table 4-1.
SPI Standard Definitions Common Definitions definition ZPHI-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZPHI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-UINT value is ZPHI-SSN-DSMSCM. 02 Z-VERSION type ZSPI-DDL-UINT value is ZPHI-VAL-VERSION. end. ZSPI-TKN-USEDLEN is the number of bytes actually used in the buffer. A subsystem that reports events can use this value to determine how many bytes to send to $0 through the WRITEREAD procedure.
EMS Standard Definitions Common Definitions EMS Standard Definitions Definitions whose names begin with ZEMS are EMS definitions. EMS definitions are available to all subsystems that support EMS. They are provided in the EMS DDL file, ZSPIDEF.ZEMSDDL, and in the corresponding definition files for other languages. The only EMS definitions used by DSM/SCM are header tokens. Table 4-2.
EMS Standard Definitions Common Definitions ZEMS-TKN-PIN is the process identification number (PIN) of the reporting DSM/SCM process. ZEMS-TKN-PROC-DESC is the process descriptor of the event creator. ZEMS-TKN-SENDERID is the process name of the process reporting the event. ZEMS-TKN-USERID is the user ID of the reporting process.
DSM/SCM Definitions Common Definitions DSM/SCM Definitions Definitions whose names begin with ZPHI are DSM/SCM definitions. DSM/SCM definitions are provided in ZSPIDEF.ZPHIDDL and in the corresponding definition files for other languages. General information about the DSM/SCM standard definitions is provided here. For specific information about these definitions as they apply to a particular event message, see the individual message description in Section 5, Event Messages.
Predefined Token and Field Values Common Definitions ZPHI-VAL-ACT-CB-INIT-BLD-CNFG indicates the message was generated by the Build Configuration activity used to initially synchronize the host database with the software on a target system. ZPHI-VAL-ACT-IS-INPUT-SS indicates the message was generated by an Input Snapshot activity. ZPHI-VAL-ACT-IS-INPUT-SW indicates the message was generated by an Input Software activity.
Predefined Token and Field Values Common Definitions ZPHI-VAL-ACT-UT-HOST-REP-P indicates the message was generated by a Host Report to Print activity. ZPHI-VAL-ACT-UT-IPMREP-REP-D indicates the message was generated by an IPM Replaces Report to Disk activity. ZPHI-VAL-ACT-UT-IPMREP-REP-P indicates the message was generated by an IPM Replaces Report to Print activity. ZPHI-VAL-ACT-UT-IPMREQ-REP-D indicates the message was generated by an IPM Requisite Report to Disk activity.
Predefined Token and Field Values Common Definitions ZPHI-VAL-ACT-UT-USER-DEF-P indicates the message was generated by a User-Defined Report to Print activity. ZPHI-VAL-ACTION-nnn is a possible value of the ZPHI-TKN-ACTION-CD token. The ZPHI-TKN-ACTIONCD token identifies the procedure or action in progress when the error or warning occurred: ZPHI-VAL-ACTION-AWAITIO indicates the error or warning occurred during an AWAITIO procedure.
Predefined Token and Field Values Common Definitions ZPHI-VAL-ACTION-EDITREADINIT indicates the error or warning occurred during an EDITREADINIT procedure. ZPHI-VAL-ACTION-FILEINFO indicates the error or warning occurred during a FILEINFO procedure. ZPHI-VAL-ACTION-FILEINQUIRE indicates the error or warning occurred during a FILEINQUIRE procedure. ZPHI-VAL-ACTION-FUP-DUP indicates the error or warning occurred during a File Utility Program (FUP) DUP command.
Predefined Token and Field Values Common Definitions ZPHI-VAL-ACTION-SETMODE indicates the error or warning occurred during a SETMODE procedure. ZPHI-VAL-ACTION-SFG-ACCESS indicates the error or warning occurred during a Safeguard access check. ZPHI-VAL-ACTION-SFG-ADD-FILE indicates the error or warning occurred during a Safeguard ADD FILE command. ZPHI-VAL-ACTION-SFG-DEL-FILE indicates the error or warning occurred during a Safeguard DELETE FILE command.
Predefined Token and Field Values Common Definitions ZPHI-VAL-COMP-nnn is a possible value of the ZPHI-TKN-ACT-COMP-CD token. The ZPHI-TKN-ACTCOMP-CD token returns the completion code assigned to an activity. It is returned when an activity completes processing. The completion code values are: ZPHI-VAL-COMP-CANCELLED indicates the activity was cancelled. ZPHI-VAL-COMP-ERROR indicates the activity completed with errors. ZPHI-VAL-COMP-SUCCESS indicates the activity completed successfully.
Predefined Token and Field Values Common Definitions ZPHI-VAL-DB-OBJ-TYP-nnn is a possible value of the ZPHI-TKN-DB-OBJ-TYPE token. The ZPHI-TKN-DBOBJ-TYPE token specifies the database object type that caused the error: ZPHI-VAL-DB-OBJ-TYP-CNFG-MGR-PRF indicates the error was caused by a Configuration Manager Profile database object. ZPHI-VAL-DB-OBJ-TYP-CNFG-REV indicates the error was caused by a Configuration Revision database object.
Predefined Token and Field Values Common Definitions ZPHI-VAL-ERR-nnn is a possible value of the ZPHI-TKN-ERR-TYP-CD token. The ZPHI-TKN-ERRTYP-CD indicates whether an error is restartable or a warning. The values and error type they represent are: ZPHI-VAL-ERR-RSTBLE indicates the error is a restartable error. ZPHI-VAL-ERR-WARNING indicates the error is a warning. ZPHI-VAL-EVT-BUFLEN is the recommended buffer size (in bytes) for event messages for the DSM/SCM.
Predefined Token and Field Values Common Definitions ZPHI-VAL-FTYP-ARCHIVE indicates the file is an archive file. ZPHI-VAL-FTYP-CNFGINFO indicates the file is an A0CINFO file. ZPHI-VAL-FTYP-FAB-FILE indicates the file is a fabricated file. ZPHI-VAL-FTYP-MAP-FILE indicates the file is a map file. ZPHI-VAL-FTYP-PROCESS indicates the file is a process file. ZPHI-VAL-FTYP-PURGEME indicates the file is a Purgeme file. ZPHI-VAL-FTYP-RDOC-FILE indicates the file is a release doc file.
Predefined Token and Field Values Common Definitions ZPHI-VAL-FTYP-TARGET-FILE indicates the file is a target file. ZPHI-VAL-FTYP-TOOL-FILE indicates the file is a tool file. ZPHI-VAL-FTYP-TRACE indicates the file is a trace file. ZPHI-VAL-FTYP-ZPHIFI indicates the file is a ZPHIFI file. ZPHI-VAL-FTYP-ZPHI6030 indicates the file is a ZPHI6030 file. ZPHI-VAL-FTYP-ZPHISYS indicates the file is a ZPHISYS file. ZPHI-VAL-FTYP-ZSSLIST indicates the file is a ZSSLIST file.
Predefined Token and Field Values Common Definitions ZPHI-VAL-IR-INCSNT-DATA indicates inconsistent data. ZPHI-VAL-IR-INV-ACT-CD indicates an invalid activity code. ZPHI-VAL-IR-INV-DB-INFO indicates invalid information was received from the database. ZPHI-VAL-IR-INV-IPC-PARAM indicates an invalid interprocess control (IPC) parameter. ZPHI-VAL-IR-INV-PARAM-CODE indicates an invalid internal parameter. ZPHI-VAL-IR-INV-PWY-PARAM indicates an invalid Pathway parameter.
Predefined Token and Field Values Common Definitions ZPHI-VAL-IR-UNABLE-TO-ACCESS indicates a device could not be accessed. ZPHI-VAL-LCNS-SET-nnn is a possible value of the ZPHI-TKN-LCNS-SET-CD token. The ZPHI-TKN-LCNSSET-CD token specifies whether the file is licensed: ZPHI-VAL-LCNS-SET-OFF indicates the file is not licensed. ZPHI-VAL-LCNS-SET-ON indicates the file is licensed. ZPHI-VAL-MED-nnn is a possible value of the ZPHI-TKN-MEDIUM-CD token.
Predefined Token and Field Values Common Definitions ZPHI-VAL-PRGD-SET-OFF indicates the PROGID attribute for the file is set off. ZPHI-VAL-PRGD-SET-ON indicates the PROGID attribute for the file is set on. ZPHI-VAL-SERVER-nnn is a possible value of the ZPHI-TKN-SRVR-COD token. The ZPHI-TKN-SRVRCOD token specifies the server process that completed the activity: ZPHI-VAL-SERVER-BACKUP indicates BACKUP completed the activity. ZPHI-VAL-SERVER-SQLCI indicates SQLCI completed the activity.
Predefined Token and Field Values Common Definitions ZPHI-VAL-SSID is the DSM/SCM subsystem ID. For the structure definition, see the description for ZSPI-TKN-SSID on page 4-2. For more information on ZPHI-VAL-SSID, see the subsystem ID discussion in the SPI Programming Manual. ZPHI-VAL-STOP-nnn is a possible value of the ZPHI-TKN-ACT-STOP-CD token. The ZPHI-TKN-ACTSTOP-CD token returns the stopped code assigned to an activity.
Simple Tokens Common Definitions ZPHI-VAL-TIMER-START indicates the error occurred at the timer used to schedule the start of an activity. ZPHI-VAL-VERSION is the product version number of DSM/SCM. This value is a 16-bit unsigned integer. The left byte contains the letter part of the product version as an ASCII uppercase alphabetic character, and the right byte contains the numeric part of the product version as an unsigned integer value.
Simple Tokens Common Definitions Table 4-3.
5 Event Messages This section describes the content and meaning of all the event messages that DSM/SCM generates. Event messages are composed of tokens in Subsystem Programmatic Interface (SPI) buffers. A management application can obtain these event messages by opening an Event Management Service (EMS) distributor process and requesting the messages. The application can also specify that a filter be applied to select certain event messages.
Summary of DSM/SCM Event Messages Event Messages In addition, some utilities can share use of the DSM/SCM message templates, so they can use the DSM/SCM message header to report their own subsystem event messages. These NonStop utilities include support for the DSM/SCM message header: BACKUP File Manager DISKGEN SYSGEN Tape Reader For more information on the format and content of the DSM/SCM message header, see DSM/SCM Event Message Header on page 5-23.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 2 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 2030 FILE-ACTION-ERR A restartable file error or warning occurred. 5-45 2031 FILE-ACTION2-ERR A restartable file error or warning occurred. 5-47 2032 OSSFL-ACTION-ERR A restartable file error or warning occurred. 5-49 2035 REM-SYS-UNAVAIL User request to a remote system could not be completed because the remote system is unavailable.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 3 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 2081 OSS-RENAME-ERR An error occurred while renaming an OSS file. 5-66 2085 UNABLE-TO-ACCESS File cannot be accessed at this time. 5-67 2090 NO-SCRATCH-SPACE Space requirements for the activity exceed the space remaining on scratch or archive volumes, or no scratch or archive volumes were specified.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 4 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 2999 INT-ERR Internal DSM/SCM error occurred. 5-87 3000 SS-OUTDTD An outdated system snapshot file was received. 5-89 3005 NO-CNFG-FILE DSV does not contain an A0CINFO file. 5-90 3006 NO-A1CNFG-FILE DSV does not contain an A1CINFO file. 5-91 3007 NO-A7CNFG-FILE DSV does not contain an A7CINFO file.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 5 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 3030 INV-RLSEID-CUST SUT has invalid or missing RLSEID or CUSTFILE files. 5-107 3031 INPUT-SW-PROGRESS 5-108 3032 INPUT-SW-IN-PROGRESS A Receive-All-Files software input was started while another input was processing A software input was started while a Receive-All-Files input was processing.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 6 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 4030 BAD-RELEASE Product list built from a SUT containing an internal NonStop release ID. 5-119 4031 PART-ENABLED-OSS-PROD An OSS product is only partially DSM/SCM-enabled. 5-119 4032 OSS-PROD-NOT-ENABLED Some pax archive files are not DSM/SCM-enabled. 5-120 4033 UNPROCESSED-A7CINFO A7CINFO files in the configuration are unprocessed.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 7 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 4150 NO-SRL-ZTILT SRL ZTILT source file does not exist. 5-133 4151 ZPHI-EVT-SRL-RELOCSEXCLUDED Relocatable SRLs were found in the TNS/E configuration. 5-133 4152 ZPHI-EVT-SRL-EXESEXCLUDED Executable SRLs were found in the TNS/E configuration.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 8 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 4260 RUNNING-SYSGEN System generation is required and about to run. 5-143 4261 ZPHI-EVT-NO-ZIMPIMP DSM/SCM can not find the manufactured ZIMPIMP file in the configuration.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 9 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 5015 CANNOT-BACKOUT DSM/SCM cannot find a previously saved configuration. 5-152 5020 INSUFF-DISK-SPACE Insufficient disk space is available to execute Apply or Backout activity.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 10 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 5028 CANNOT-OVERRIDE-EOF An Apply detected that the new and old OSIMAGE files are different versions, and the OVERRIDE-SYSNNDIFFERENT-OS parameter is needed to ignore the difference. 5-160 5029 OVERRIDE-SYSNN An Apply detected that the new and old OSIMAGE files are the same size. OVERRIDESYSNN was specified, so the old OSIMAGE is not replaced.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 11 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 5047 NEW-MNGD-FLS-CREATED DSM/SCM re-created missing zzDSMSCM.Managed files. 5-168 5048 OSS-FL-MISS-OR-WRONG Managed OSS file is missing. 5-168 5050 DISP-PRVW An operator instruction. 5-169 5055 NOT-ONLINE Apply activity stopped because the TSV volume was not online.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 12 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 5135 CHG-IN-SYS-ENV Files were modified since DSM/SCM placed them. 5-182 5140 DEL-SFG-SEC-ERR A Safeguard SPI error occurred while deleting Safeguard security attributes for a file. 5-182 5145 INCONSIS-DB An inconsistency exists between the target database and the actual files on the target system.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 13 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 5200 MISSING-PREV-SYSNN DSM/SCM is deleting the previous configuration for a logical target from the target system. 5-191 5210 NN-TSV-MOVED A SYSnn subvolume was manually moved. 5-192 5220 BAD-SYS-CSS-MOVE The associated SYSnn and CSSnn subvolumes are on different volumes.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 14 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 5320 MISSING-OSS-WRK-FLS DSM/SCM files are missing from OSS environment. 5-202 5321 REM-OSS-MNG-4-BACKOUT OSS management cleanup is required due to a recent backout. 5-202 5325 MNGD-OSSFL-NOT-RMVD1 OSS management was removed, but work files remain. 5-203 5330 MNGD-OSSFL-NOT-REMVD OSS management was removed, but work files remain.
Summary of DSM/SCM Event Messages Event Messages Table 5-1. DSM/SCM Event Messages (page 15 of 15) Event Number Symbolic Name (ZPHI-EVT-) Description Page 6005 PSEND-ERR A Pathsend error occurred. 5-209 6010 CANNOT-CANCEL DSM/SCM activity cannot be cancelled from a remote node. 5-210 6015 TIMER-ERR An internal DSM/SCM scheduling error occurred. 5-210 6020 TA-DEP-ERR An attempt was made to start a simultaneous Apply, Backout, or Snapshot activity.
DSM/SCM Event Message Generation Event Messages DSM/SCM Event Message Generation DSM/SCM events are generated in response to DSM/SCM activities. Each time a DSM/SCM activity starts, a sequence of messages is generated. All events for an activity are identified by the activity-ID token (ZPHI-TKN-ACTIVITY-ID) in the header. The messages in the sequence vary depending on whether an error occurs and whether the activity stops or completes processing.
DSM/SCM Event Message Error Ranges Event Messages DSM/SCM Event Message Error Ranges Table 5-2.
DSM/SCM Event Message Classifications Event Messages DSM/SCM Event Message Classifications In addition to the error ranges, DSM/SCM events are classified as described in Table 5-3. Table 5-3. DSM/SCM Event Message Classifications Message type Meaning Informational Informational message only; no corrective action is needed. DSM/SCM continues processing. Error An error occurred. DSM/SCM might or might not continue processing. Warning A warning occurred. DSM/SCM continues processing.
Tokens in All Event Messages Event Messages Tokens in All Event Messages Event-message buffers, like other SPI buffers, contain header tokens. The header tokens in Table 5-4 appear in all DSM/SCM event messages. For descriptions of tokens that appear only in certain event messages, see those message descriptions in this section. Table 5-4.
Tokens in All Event Messages Event Messages ZEMS-TKN-GENTIME is the time (Greenwich Mean Time) that the event message was created. ZEMS-TKN-LOGTIME is the time (Greenwich Mean Time) that the collector wrote the event message to its log files. ZEMS-TKN-NODENAME is the Expand node name where the event was reported. ZEMS-TKN-NODENUM is the Expand node number where the event was reported. ZEMS-TKN-PIN is the process identification number (PIN) of the reporting DSM/SCM process.
Tokens in All Event Messages Event Messages ZPHI-TKN-PLANNER-ID.Z-USERNAME is the user name portion of the planner ID. The planner ID identifies the DSM/SCM operator or planner who created the request. ZPHI-TKN-STAGE-CODE is an internal value that reports the stage within the activity that the event message was reported. ZPHI-TKN-SVR-CLS-NM is the server class name of the DSM/SCM component issuing the event or interfacing to the utility issuing the event.
DSM/SCM Event Message Header Event Messages DSM/SCM Event Message Header DSM/SCM has its own EMS message header, in the format: "<1> <2> <3>DSM/SCM: *<4>* Server Class <5> of PATHMON <6> activity id <7>, activity code <8>, planner id <9>.
Descriptions of DSM/SCM Event Messages Event Messages Descriptions of DSM/SCM Event Messages The descriptions of the DSM/SCM event messages are in ascending order by event number, which is followed by ZPHI-EVT-name, where name identifies a unique message. Each description contains: • • • The header shows the numeric and symbolic values for the event number. The first paragraph briefly describes the event message. The syntax box contains a list of tokens that can appear in the event message.
1000 ZPHI-EVT-FILE-LOCATION Event Messages 1000 ZPHI-EVT-FILE-LOCATION This message reports the location of certain files created by DSM/SCM. This message typically reports the location of files of these types: system snapshot, trace file, target file, or activation package. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-FILE-NM <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-FNAME Message Text <1> files(s) is/are located at <2>.
1005 ZPHI-EVT-ACT-STARTED Event Messages 1005 ZPHI-EVT-ACT-STARTED This message reports the start of an activity by a DSM/SCM component. Tokens ZPHI-TKN-ACT-NM-CD <1> token-type ZSPI-TYP-INT Message Text <1> activity started. ZPHI-TKN-ACT-NM-CD is the activity that started.
1005 ZPHI-EVT-ACT-STARTED Event Messages ZPHI-VAL-ACT-UT-SOFTDOC-P Softdoc to Print ZPHI-VAL-ACT-UT-TARG-REP-DK Target Report to Disk ZPHI-VAL-ACT-UT-TARG-REP-P Target Report to Print ZPHI-VAL-ACT-UT-USER-DEF-D User-Defined Report to Disk ZPHI-VAL-ACT-UT-USER-DEF-P User-Defined Report to Print Cause. A DSM/SCM component started the specified activity. Effect. This message reports the start of the activity. Recovery. Informational message only; no corrective action is needed.
1010 ZPHI-EVT-ACT-COMPLETED Event Messages 1010 ZPHI-EVT-ACT-COMPLETED This message indicates the completion status of an activity completed by DSM SCM. Tokens ZPHI-TKN-ACT-NM-CD ZPHI-TKN-ACT-COMP-CD <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-ENUM Message Text <1> completed <2>. ZPHI-TKN-ACT-NM-CD is the activity that has just completed execution by DSM/SCM.
1010 ZPHI-EVT-ACT-COMPLETED Event Messages ZPHI-VAL-ACT-UT-SOFTDOC-D Softdoc to Disk ZPHI-VAL-ACT-UT-SOFTDOC-P Softdoc to Print ZPHI-VAL-ACT-UT-TARG-REP-DK Target Report to Disk ZPHI-VAL-ACT-UT-TARG-REP-P Target Report to Print ZPHI-VAL-ACT-UT-USER-DEF-D User-Defined Report to Disk ZPHI-VAL-ACT-UT-USER-DEF-P User-Defined Report to Print ZPHI-TKN-ACT-COMP-CD is the completion status of the activity.
1015 ZPHI-EVT-SS-REQD Event Messages 1015 ZPHI-EVT-SS-REQD This message indicates an error occurred during an Apply activity and a system snapshot is needed to synchronize the host and target. Tokens ZPHI-TKN-HOST-NODE-NM <1> token-type ZSPI-TYP-STRING Message Text Snapshot needed for host <1> to correct Apply error. Run Target Interface and select CREATE SNAPSHOT activity. ZPHI-TKN-HOST-NODE-NM is the host name where the error occurred. Cause. An error occurred during an Apply activity.
1020 ZPHI-EVT-ACT-STOPPED Event Messages 1020 ZPHI-EVT-ACT-STOPPED This message indicates the stopped status of an activity that stopped. Tokens ZPHI-TKN-ACT-NM-CD ZPHI-TKN-ACT-STOP-CD <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-ENUM Message Text <1> stopped <2>. ZPHI-TKN-ACT-NM-CD is the activity that stopped.
1020 ZPHI-EVT-ACT-STOPPED Event Messages ZPHI-VAL-ACT-UT-SOFTDOC-P Softdoc to Print ZPHI-VAL-ACT-UT-TARG-REP-DK Target Report to Disk ZPHI-VAL-ACT-UT-TARG-REP-P Target Report to Print ZPHI-VAL-ACT-UT-USER-DEF-D User-Defined Report to Disk ZPHI-VAL-ACT-UT-USER-DEF-P User-Defined Report to Print ZPHI-TKN-ACT-STOP-CD is the stopped status of the activity. Possible values and the statuses they represent are: restartable.
1025 ZPHI-EVT-RETRY-EXCEEDED Event Messages 1025 ZPHI-EVT-RETRY-EXCEEDED The Pathsend retry count has been exceeded for a Pathway server class. Tokens ZPHI-TKN-PMON-PRCS-NM ZPHI-TKN-SERVER-CLASS-NM <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Retry count exceeded, PATHMON <1> server class <2> could not be started. The planner must retry the request. ZPHI-TKN-PMON-PRCS-NM is the name of Pathway monitor (PATHMON) process associated with the error.
2000 ZPHI-EVT-GF-ERR Event Messages 2000 ZPHI-EVT-GF-ERR The Software Identification (SWID) utility returned an error that is reported in the values of P error and S error. Tokens ZPHI-TKN-P-ERROR ZPHI-TKN-S-ERROR ZPHI-TKN-INT-FILE-NM <1> <2> <3> token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT token-type ZSPI-TYP-FNAME Message Text Error returned from SWID utility, <1>, <2> on <3>. Correct the error and RESTART the activity. ZPHI-TKN-P-ERROR is the P error value.
2000 ZPHI-EVT-GF-ERR Event Messages Table 5-5.
2005 ZPHI-EVT-UT-SERVER-ERR Event Messages 2005 ZPHI-EVT-UT-SERVER-ERR A file warning or error occurred at the File Manager or Tape Reader utility.
2005 ZPHI-EVT-UT-SERVER-ERR Event Messages ZPHI-TKN-FILE-TYPE-CD is the file type of the file.
2010 ZPHI-EVT-DECOMPRESS-ERR Event Messages 2010 ZPHI-EVT-DECOMPRESS-ERR The Software Archive (SWARC) utility could not compress or decompress a file. Tokens ZPHI-TKN-PROC-NAME ZPHI-TKN-ERROR-CODE <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT Message Text Error <1> <2> returned from SWARC. SWARC failed to compress/decompress file. Contact HP. ZPHI-TKN-PROC-NAME is the name of the procedure where the error occurred. ZPHI-TKN-ERROR-CODE is the error code returned by SWARC.
2015 ZPHI-EVT-INV-FILE-ENTITY Event Messages 2015 ZPHI-EVT-INV-FILE-ENTITY A file inconsistency exists in an activation package, system snapshot, or archive file. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-FILE-NM ZPHI-TKN-MEDIUM-CD ZPHI-TKN-ERR-ENTITY-CD <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-FNAME ZSPI-TYP-ENUM ZSPI-TYP-ENUM Message Text Specified <1> file <2> on <3> has incorrect <4>. Ensure filename is correct and created by DSM/SCM.
2015 ZPHI-EVT-INV-FILE-ENTITY Event Messages Cause. A file inconsistency exists in the activation package, system snapshot, or archive file located on the medium type specified. Either the file name specified is incorrect, or a data entity in the file is invalid. Effect. The activity stops in a restartable state. Recovery. The planner should check that the correct file name was specified and that the file itself was created by DSM/SCM and is the correct type.
2017 ZPHI-EVT-UN-MAN-TARGET-SNAP Event Messages 2017 ZPHI-EVT-UN-MAN-TARGET-SNAP An incorrect system snapshot file was specified. Tokens ZPHI-TKN-INT-FILE-NM ZPHI-TKN-TARGET-NODE-NM ZPHI-TKN-HOST-NODE-NM ZPHI-TKN-MEDIUM-CD <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-FNAME ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-ENUM Message Text You specified a snapshot file <1> created at a target <2> not managed by this host <3>. Ensure you have the correct <4> for this host.
2020 ZPHI-EVT-CORR-DB-ERR Event Messages 2020 ZPHI-EVT-CORR-DB-ERR A correctable database error occurred. Tokens ZPHI-TKN-DB-ERROR-NUM ZPHI-TKN-SQL-DB-ERR-BUF <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text Correctable database error <1>. SQL/data base manager returned <2>. Correct error. RESTART activity. ZPHI-TKN-DB-ERROR-NUM is the error code that identifies the error. ZPHI-TKN-SQL-DB-ERR-BUF contains the error text. Cause.
2020 ZPHI-EVT-CORR-DB-ERR Event Messages 17 DB_ERR_DEFINE_NOTFOUND The define pointing to the Database Manager does not exist. 23 DB_ERR_BEGIN_TRANSACTION_FAILED Transaction cannot begin. Check the HP NonStop Transaction Management Facility (TMF) status for errors.
2020 ZPHI-EVT-CORR-DB-ERR Event Messages 38 DB_ERR_UNABLE_TO_RET_TARGETS_DEFINE The transaction tag passed to the Database Manager does not match the transaction tag that corresponds to the transaction that this Database Manager process started. -8300 SQL/MP encountered a file-system error. The file-system error and a one line description are displayed as part of db-error-buf.
2030 ZPHI-EVT-FILE-ACT-ERR Event Messages 2030 ZPHI-EVT-FILE-ACT-ERR A warning or restartable file error occurred during the specified procedure or action. Tokens ZPHI-TKN-ERR-TYP-CD ZPHI-TKN-FE-ERROR ZPHI-TKN-ACTION-CD ZPHI-TKN-INT-FILE-NM <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-INT ZSPI-TYP-ENUM ZSPI-TYP-FNAME Message Text <1> <2> on <3> of file/process <4>. If error type is Warning, decide upon corrective action.
2030 ZPHI-EVT-FILE-ACT-ERR Event Messages ZPHI-VAL-ACTION-FILEINFO FILEINFO procedure ZPHI-VAL-ACTION-FILEINQUIRE FILEINQUIRE procedure ZPHI-VAL-ACTION-FUP-DUP FUP DUP command ZPHI-VAL-ACTION-NEWPROCESS NEWPROCESS procedure ZPHI-VAL-ACTION-NEXTFILENAME NEXTFILENAME procedure ZPHI-VAL-ACTION-OPEN OPEN procedure ZPHI-VAL-ACTION-POSITION POSITION procedure ZPHI-VAL-ACTION-PUP-LISTLABEL PUP LISTLABEL command ZPHI-VAL-ACTION-READ READ procedure ZPHI-VAL-ACTION-READUPDATE READUPDATE procedure
2031 ZPHI-EVT-FILE-ACTION2-ERR Event Messages 2031 ZPHI-EVT-FILE-ACTION2-ERR A warning or restartable file error occurred during the specified procedure or action. Tokens ZPHI-TKN-ERR-TYP-CD ZPHI-TKN-FE-ERROR ZPHI-TKN-ACTION-CD ZPHI-TKN-INT-FILE-NM ZPHI-TKN-TO-INT-FILE-NM <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-INT ZSPI-TYP-ENUM ZSPI-TYP-FNAME ZSPI-TYP-FNAME Message Text <1> <2> on <3> of process <4>, file <5>.
2031 ZPHI-EVT-FILE-ACTION2-ERR Event Messages ZPHI-VAL-ACTION-EDITREADINIT EDITREADINIT procedure ZPHI-VAL-ACTION-FILEINFO FILEINFO procedure ZPHI-VAL-ACTION-FILEINQUIRE FILEINQUIRE procedure ZPHI-VAL-ACTION-FUP-DUP FUP DUP command ZPHI-VAL-ACTION-NEWPROCESS NEWPROCESS procedure ZPHI-VAL-ACTION-NEXTFILENAME NEXTFILENAME procedure ZPHI-VAL-ACTION-OPEN OPEN procedure ZPHI-VAL-ACTION-POSITION POSITION procedure ZPHI-VAL-ACTION-PUP-LISTLABEL PUP LISTLABEL command ZPHI-VAL-ACTION-READ READ p
2032 ZPHI-EVT-OSSFL-ACTION-ERR Event Messages including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the error is a warning, the operator or planner might need to decide if corrective action is needed. If the error is restartable, correct the error and restart the activity. 2032 ZPHI-EVT-OSSFL-ACTION-ERR A restartable file error or warning occurred.
2035 ZPHI-EVT-REM-SYS-UNAVAIL Event Messages ZPHI-VAL-ACTION-OPENDIR opendir() procedure ZPHI-VAL-ACTION-MKDIR mkdir() procedure ZPHI-VAL-ACTION-MKFIFO mkfifo() procedure ZPHI-VAL-ACTION-REMOVE-OSS remove_oss() procedure ZPHI-VAL-ACTION-LINK link() procedure ZPHI-VAL-ACTION-SYMLINK symlink() procedure ZPHI-TKN-INT-FILE-NM is the qualified filename of the file where the error occurred. Cause. A warning or restartable file error occurred during the specified procedure or action. Effect.
2040 ZPHI-EVT-MALLOC-ERR Event Messages 2040 ZPHI-EVT-MALLOC-ERR A memory allocation error occurred. Tokens None. Message Text Memory allocation error. RESTART the activity. If the error persists, contact your HP representative. Cause. A memory allocation error has occurred. Effect. The activity stops in a restartable state. Recovery. Restart the activity.
2045 ZPHI-EVT-SERVER-COMP Event Messages 2045 ZPHI-EVT-SERVER-COMP A server process completed an activity for DSM/SCM. Tokens ZPHI-TKN-SRVR-COD ZPHI-TKN-SERVER-COMP-CD <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-ENUM Message Text <1> completed <2>. Examine server warning(s)/error(s), correct error(s) if necessary, RESTART activity if stopped in a restartable state. ZPHI-TKN-SRVR-COD is the server process that has completed the activity.
Event Messages • • • 2045 ZPHI-EVT-SERVER-COMP If the server completes the activity successfully, this is an informational message only; no corrective action is needed. If the server completes the activity with warnings, the operator should examine the events from the server process and any appropriate output files to determine if corrective action is needed. (SYSGEN/R always completes with warnings.) If corrective action is needed, correct the error and start a new activity.
2046 ZPHI-EVT-SERVER-COMP-DETAIL Event Messages 2046 ZPHI-EVT-SERVER-COMP-DETAIL A server process for DSM/SCM completed with errors or warnings. Tokens ZPHI-TKN-SRVR-COD ZPHI-TKN-SERVER-COMP-CD ZPHI-TKN-COMPLETION-TEXT ZPHI-TKN-INT-FILE-NM <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-FNAME Message Text <1> completed <2>. Completion text: <3>.
Event Messages 2046 ZPHI-EVT-SERVER-COMP-DETAIL Cause. A server process has completed an activity for DSM/SCM. The activity has completed successfully, with warnings, or with errors. Effect. Depending on the completion status, either the server completed processing the activity (if the server completes successfully or with warnings), or the server stopped processing the activity (if the server stops with errors). If the server stops with errors, the activity stops in a restartable state. Recovery.
2047 ZPHI-EVT-SERVER-COMP-SUCCESS Event Messages 2047 ZPHI-EVT-SERVER-COMP-SUCCESS This message indicates that an activity has completed successfully. Tokens ZPHI-TKN-SRVR-COD <1> ZPHI-TKN-EXT-FNAME <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING Message Text <1> completed successfully. See the output at <2>. ZPHI-TKN-SRVR-COD is the server process that completed the activity successfully. Possible values and the process they represent.
2050 ZPHI-EVT-PSEND-LINK-DOWN Event Messages 2050 ZPHI-EVT-PSEND-LINK-DOWN A Pathsend link used by DSM/SCM is down. Tokens None. Message Text PATHSEND link down, processing terminated. Correct any associated error(s). RESTART the activity. Cause. A Pathsend link that DSM/SCM uses is down. Effect. The activity stops in a restartable state. Recovery. Determine why the link is down or unavailable, correct any associated errors, and restart the activity when the link is available.
2055 ZPHI-EVT-FNAME-GEN Event Messages 2055 ZPHI-EVT-FNAME-GEN DSM/SCM could not create a unique name for a file because of a problem with the cleanup of a previous DSM/SCM activity. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-SVNM <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-SUBVOL Message Text Cannot create unique name for <1> file on <2>. Delete unneeded files. RESTART activity. ZPHI-TKN-FILE-TYPE-CD is the file type of the affected file.
2057 ZPHI-EVT-OSSFL-NAME-GEN Event Messages 2057 ZPHI-EVT-OSSFL-NAME-GEN DSM/SCM could not create a unique name for an OSS file because of a problem with the cleanup of a previous DSM/SCM activity. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-TDL-NAME <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text Cannot create unique name for <1> file in directory <2>. Delete unneeded files. RESTART activity. ZPHI-TKN-FILE-TYPE-CD is the file type of the affected file.
2060 ZPHI-EVT-INV-EMS-TKN Event Messages 2060 ZPHI-EVT-INV-EMS-TKN Event Management Service (EMS) does not recognize the requested token. Tokens ZPHI-TKN-TOKEN-NM ZPHI-TKN-EMS-ERR-CD <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT Message Text Invalid token value returned from EMS, <1>, <2>. ZPHI-TKN-TOKEN-NM is the name of the token that EMS does not recognize. ZPHI-TKN-EMS-ERR-CD is the error code that EMS returns. For EMS error code descriptions, see the EMS Manual. Cause.
2065 ZPHI-EVT-MISSING-FILE Event Messages 2065 ZPHI-EVT-MISSING-FILE DSM/SCM cannot locate the specified file. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-FILE-NM ZPHI-TKN-FE-ERR <1> <2> <3> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-FNAME token-type ZSPI-TYP-INT Message Text Existence check on <1> file <2> received error <3>. ZPHI-TKN-FILE-TYPE-CD is the file type of the file that could not be found.
2066 ZPHI-EVT-MISSING-OSSFL Event Messages Recovery. Check the file-system error code in the message. For a definition of the specified error, see Appendix B, File-System Errors. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. The recovery procedure depends on the cause of the error: • • If the error occurred because the intended file is not in the proper location, put the file in the appropriate location, and restart the activity.
2070 ZPHI-EVT-INV-PWY-SVR-CLS Event Messages 2070 ZPHI-EVT-INV-PWY-SVR-CLS A server class parameter in the DSM/SCM Pathway configuration is missing or has an invalid value. Tokens ZPHI-TKN-SVR-CLS-PRM-NM ZPHI-TKN-SVR-CLS-PRM-VAL <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT Message Text Server class parameter missing or invalid: parameter <1>, value <2>. Planner must correct Pathway configuration to correct parameter.
2075 ZPHI-EVT-INV-DATA Event Messages 2075 ZPHI-EVT-INV-DATA The specified file contains invalid data. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-FILE-NM ZPHI-TKN-MEDIUM-CD <1> <2> <3> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-FNAME token-type ZSPI-TYP-ENUM Message Text <1> file <2> on <3> contains invalid data. Correct the error and RESTART the activity. ZPHI-TKN-FILE-TYPE-CD is the file type of the file.
2080 ZPHI-EVT-RNAME-ERR Event Messages 2080 ZPHI-EVT-RNAME-ERR An error occurred while renaming a file. Tokens ZPHI-TKN-FE-ERROR ZPHI-TKN-FROM-INT-FILE-NM ZPHI-TKN-TO-INT-FILE-NM <1> <2> <3> token-type ZSPI-TYP-INT token-type ZSPI-TYP-FNAME token-type ZSPI-TYP-FNAME Message Text Error <1> renaming file from <2> to <3>. Contact security administrator or Planner if problem is a security or user error. ZPHI-TKN-FE-ERROR is the file-system error that is returned.
2081 ZPHI-EVT-OSS-RENAME-ERR Event Messages 2081 ZPHI-EVT-OSS-RENAME-ERR An OSS file-system error occurred while renaming a file in the OSS environment. Tokens ZPHI-TKN-FE-ERROR ZPHI-TKN-FM-OSSFL ZPHI-TKN-TO-OSSFL <1> <2> <3> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Error <1> renaming OSS file <2> to <3>. Contact security administrator or Planner if the problem is a security or user error. ZPHI-TKN-FE-ERROR is the OSS error that is returned.
2085 ZPHI-EVT-UNABLE-TO-ACCESS Event Messages 2085 ZPHI-EVT-UNABLE-TO-ACCESS The file is incorrectly specified. Tokens ZPHI-TKN-EXT-FNAME <1> token-type ZSPI-TYP-STRING Message Text <1> is incorrectly specified. RESTART activity specifying the correctly formatted name. ZPHI-TKN-EXT-FNAME is the file name of the file that is incorrectly specified. Cause. The specified file could not be converted to an internal file-name format. The file name was probably entered incorrectly. Effect.
2090 ZPHI-EVT-NO-SCRATCH-SPACE Event Messages 2090 ZPHI-EVT-NO-SCRATCH-SPACE The space requirements for the activity exceed the space remaining on volumes in the list of scratch or archive subvolumes, or no scratch or archive volumes have been specified. Tokens ZPHI-TKN-VOL-TYPE-CD <1> token-type ZSPI-TYP-ENUM Message Text Insufficient disk space on <1> volume(s) or no <1> volumes specified. Use DSM/SCM Maintenance Interface to indicate usable <1> volumes.
2095 ZPHI-EVT-INV-PWY-CONFIG Event Messages 2095 ZPHI-EVT-INV-PWY-CONFIG A Pathway server class is running on an incorrect node. Tokens ZPHI-TKN-SERVER-CLASS-NM ZPHI-TKN-PMON-PRCS-NM ZPHI-TKN-HOST-NODE-NM <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Pathway configuration error. Server class <1>, PATHMON <2> must run on <3> node. ZPHI-TKN-SERVER-CLASS-NM is the name of the Pathway server class that is running on an incorrect node.
2100 ZPHI-EVT-NO-UNIQUE-FILES Event Messages 2100 ZPHI-EVT-NO-UNIQUE-FILES DSM/SCM could not create a unique name for a file. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-SVNM <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-SUBVOL Message Text DSM/SCM exceeded an internal threshold while trying to create a unique name for <1> file on <2>. Delete unneeded files from subvolume. ZPHI-TKN-FILE-TYPE-CD is the type of file that could not be created.
2101 ZPHI-EVT-NO-UNIQUE-SUBVOL Event Messages 2101 ZPHI-EVT-NO-UNIQUE-SUBVOL An empty ZDLLrrr[a] subvolume to place public DLLs in could not be found. Tokens ZPHI-TKN-EXT-FNAME <1> token-type ZSPI-TYP-STRING Message Text An empty <1>[A-Z] subvolume could not be found to place public DLLs in. Remove or rename one or more of these subvolumes and restart the Apply. ZPHI-TKN-EXT-NAME is the fully qualified subvolume name that DSM/SCM uses to create a new target subvolume (TSV) for public DLLs. Cause.
2105 ZPHI-EVT-INPUT-CONFLICT Event Messages 2105 ZPHI-EVT-INPUT-CONFLICT A database input conflict occurred when DSM/SCM attempted to process the same file for two different activities at the same time. Tokens ZPHI-TKN-CONFLICT-FILE-CD ZPHI-TKN-CONFLICT-TYPE-CD ZPHI-TKN-REQUEST-NM <1> <2> <3> token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text DSM/SCM cannot process the same <1> file for two different <2> at the same time. Retry the request <3> later.
2110 ZPHI-EVT-FILE-NOT-LICENSED Event Messages 2110 ZPHI-EVT-FILE-NOT-LICENSED The activity cannot proceed because it requires the use of a program file that is not licensed. Tokens ZPHI-TKN-INT-FILE-NM <1> token-type ZSPI-TYP-FNAME Message Text <1> needs to be licensed before activity can proceed. RESTART the activity after the file has been licensed. ZPHI-TKN-INT-FILE-NM is the file name in the internal format of the file that is not licensed. Cause.
2120 ZPHI-EVT-INV-USERID Event Messages 2120 ZPHI-EVT-INV-USERID The specified user ID is invalid. Tokens ZPHI-TKN-INT-OWNER-ID <1> token-type ZSPI-TYP-USERID Message Text Invalid userid <1>. ZPHI-TKN-INT-OWNER-ID is the invalid user ID. This number is the group-ID and member-ID together. For example: user-ID group-ID member-ID 00 0 0 999 9 or 99 99 or 9 9999 99 99 (not 999 because > 255) 2255 2 or 22 or 225 255 or 55 or 5 2030 20 30 (not 2030 because no leading zero) Cause.
2125 ZPHI-EVT-DB-OBJ-IN-USE Event Messages 2125 ZPHI-EVT-DB-OBJ-IN-USE The activity in progress requires a database object that is currently being used by another activity. Tokens ZPHI-TKN-DB-OBJ-TYPE ZPHI-TKN-DB-OBJ-NAME <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING Message Text Cannot proceed with activity. Necessary <1> <2> currently in use. Try request later. ZPHI-TKN-DB-OBJ-TYPE is the type of database object in use.
2130 ZPHI-EVT-DB-OBJ-CHECKED-OUT Event Messages 2130 ZPHI-EVT-DB-OBJ-CHECKED-OUT A database object is already in use by another request. Tokens ZPHI-TKN-REQUEST-NM <1> token-type ZSPI-TYP-STRING Message Text A necessary database object is in use by another request <1>. Restart this request after <1> has completed. ZPHI-TKN-REQUEST-NM is the name of the request that is already using the database object. Cause. Another request was running and locked the database object that this activity needed.
2140 ZPHI-EVT-INCOMPAT-AP-VER Event Messages 2140 ZPHI-EVT-INCOMPAT-AP-VER An unexpected version of an activation package could not be read.
Event Messages 2140 ZPHI-EVT-INCOMPAT-AP-VER Cause. The specified activation package file was created by a host system running a different DSM/SCM version than the target it is intended for. The host database indicated that the DSM/SCM version on the target system was later than it actually is, so a later version of the specified file was created, which the target cannot understand.
2150 ZPHI-EVT-INCOMPAT-SS-VER Event Messages 2150 ZPHI-EVT-INCOMPAT-SS-VER An unexpected version of a snapshot file could not be read. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-FILE-NM ZPHI-TKN-MEDIUM-CD ZPHI-TKN-EXPECTED-VERSION ZPHI-TKN-ACTUAL-VERSION ZPHI-TKN-INT-SCM-VERSION <1> <2> <3> <4> <5> <6> token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-FNAME ZSPI-TYP-ENUM ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT Message Text <1> file <2> on <3> has incorrect version.
2150 ZPHI-EVT-INCOMPAT-SS-VER Event Messages Cause. The specified snapshot file was created by a target system running a different DSM/SCM version than the host system. The target database indicated that the DSM/SCM version on the host system was later than it actually is, so a later version of the specified file was created, which the host cannot understand. This error might occur if the DSM/SCM version on the host is lowered, and the target database is not updated before this Build/Apply.
2161 ZPHI-EVT-SERVER-VERSION Event Messages 2161 ZPHI-EVT-SERVER-VERSION A server program, such as the software identification program (SWID) server program, is too old. DSM/SCM requires a more recent product version. Tokens ZPHI-TKN-DSMSCM-TEXT ZPHI-TKN-EXT-FNAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text DSM/SCM requires version <1> or later of server <2>. The current server appears to be an earlier version.
2997 ZPHI-EVT-OSS-INT-ERR Event Messages 2997 ZPHI-EVT-OSS-INT-ERR An internal DSM/SCM error occurred. Tokens ZPHI-TKN-INT-ERROR-CD ZPHI-TKN-INTERR-BUF-OSS <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text Internal error <1>, <2>. ZPHI-TKN-INT-ERROR-CD is the error code that occurred. For possible values and brief descriptions of their meanings, see Table 5-6, DSM/SCM Internal Error Codes and Their Meanings, on page 5-88.
2998 ZPHI-EVT-FATAL-DB-ERR Event Messages 2998 ZPHI-EVT-FATAL-DB-ERR A database error occurred that caused DSM/SCM to stop processing. Tokens ZPHI-TKN-DB-ERROR-NUM ZPHI-TKN-SQL-DB-ERR-BUF <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text Fatal data base error <1>. SQL/data base manager returned <2>. Contact your HP representative. ZPHI-TKN-DB-ERROR-NUM is the error code that occurred.
2998 ZPHI-EVT-FATAL-DB-ERR Event Messages 3 DB_ERR_UNABLE_TO_DELETE DSM/SCM cannot delete a database record. 4 DB_ERR_UNABLE_TO_ADD DSM/SCM cannot add a record to the database. 8 DB_ERR_LIST_NOT_IN_SYNC The Database Manager received an incorrect number of elements in the request buffer. 11 DB_ERR_NOT_FOUND The object does not exist in the database. 13 DB_ERR_INCORRECT_ACTION_CODE The action code for the transaction is incorrect.
2998 ZPHI-EVT-FATAL-DB-ERR Event Messages 28 DB_ERR_INVALID_TRANSACTION_TAG The transaction tag passed to the Database Manager is invalid. 29 DB_ERR_RESUME_TRANSACTION_FAILED An error occurred while a resume transaction was being performed. 30 DB_ERR_END_TRANSACTION_FAILED The End TMF Transaction Operation (commit) resulted in an error. 31 DB_ERR_UNABLE_TO_OPEN_CURSOR An error occurred while DSM/SCM was trying to open an SQL cursor.
2998 ZPHI-EVT-FATAL-DB-ERR Event Messages 49 DB_ERR_UNKNOWN_COMMAND The command code specified to the Database Manager is not known. 52 DB_ERR_UNKNOWN_USG_STATE Internal error. Most likely the database has been corrupted. 55 DB_ERR_INVALID_LCS Internal error indicates an invalid Life Cycle State. 56 DB_ERR_CKOUT_NO_CKR The variant is checked out, but there is no associated checker variant. 58 DB_ERR_NOT_CHECKED_OUT The object has not been checked out. 62 DB_ERR_WRONG_USAGE_STATE Internal error.
2999 ZPHI-EVT-INT-ERR Event Messages 75 DB_ERR_INVALID_RELEASE_VERSION The RVU is neither C nor D. 76 DB_ERR_UNABLE_TO_LOCK DSM/SCM cannot lock the database table. 2999 ZPHI-EVT-INT-ERR A DSM/SCM component issued an internal error. Tokens ZPHI-TKN-INT-ERR-CD ZPHI-TKN-INT-ERR-BUF <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text Internal error <1>, <2>. ZPHI-TKN-INT-ERR-CD is the internal error code that identifies the error.
2999 ZPHI-EVT-INT-ERR Event Messages Table 5-6.
3000 ZPHI-EVT-SS-OUTDTD Event Messages 3000 ZPHI-EVT-SS-OUTDTD A host received an outdated system snapshot file. Tokens ZPHI-TKN-TARGET-NODE-NM <1> token-type ZSPI-TYP-STRING Message Text Specified snapshot file is not most recent for <1>. Not processed. ZPHI-TKN-TARGET-NODE-NM is the node name of the target that received the outdated file. Cause. A host received an outdated system snapshot file. Effect. The specified system snapshot file is not processed. Recovery.
3005 ZPHI-EVT-NO-CNFG-FILE Event Messages 3005 ZPHI-EVT-NO-CNFG-FILE A distribution subvolume (DSV) does not contain an A0CINFO file. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text The DSV <1> does not contain A0CINFO file. Planner must use CNFGINFO tool to create a correct A0CINFO file, bring it in as a separate input and assign to the same input group as this input through the Planner Interface. DSV skipped, processing continues.
3006 ZPHI-EVT-NO-A1CNFG-FILE Event Messages 3006 ZPHI-EVT-NO-A1CNFG-FILE A distribution subvolume (DSV) does not contain an A1CINFO file. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text The DSV <1> does not contain A1CINFO file. DSV skipped, processing continues. ZPHI-TKN-INT-SVNM is the name of the DSV where the error occurred. Cause. The specified DSV did not contain an A1CINFO file, or the A1CINFO file has an incorrect file code. Effect. The activity finishes with warnings.
3007 ZPHI-EVT-NO-A7CNFG-FILE Event Messages 3007 ZPHI-EVT-NO-A7CNFG-FILE A distribution subvolume (DSV) does not contain an A7CINFO file. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text The DSV <1> has an entry in the A0CINFO file for A7CINFO file, which is not present in the DSV. DSV skipped, processing continues. ZPHI-TKN-INT-SVNM is the name of the DSV where the error occurred. Cause. The A7CINFO file was removed from the DSV after the A0CINFO file was generated. Effect.
3008 ZPHI-EVT-GUARDIAN-OR-EXPAND-FL Event Messages 3008 ZPHI-EVT-GUARDIAN-OR-EXPAND-FL The A7CINFO file contains a record for an OSS file in an invalid /G or /E directory. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-INT-SVNM ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING Message Text pax archive file <1> in DSV <2> contains invalid file <3>. Files in /G or /E are not allowed. DSV skipped, processing continues.
3009 ZPHI-EVT-UNKNOWN-OSSFL-RECTYPE Event Messages 3009 ZPHI-EVT-UNKNOWN-OSSFL-RECTYPE The A7CINFO file contains a record for an OSS file with an invalid file type. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-INT-SVNM ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING Message Text pax archive file <1> in DSV <2> contains invalid file <3> which has an OSS file type other than Regular File, Directory, Symbolic Link, Hard Link, or FIFO.
3010 ZPHI-EVT-NO-CNFG-ENTRY Event Messages 3010 ZPHI-EVT-NO-CNFG-ENTRY The A0CINFO file is missing an entry for a distribution subvolume (DSV) file. Tokens ZPHI-TKN-INT-SVNM ZPHI-TKN-INT-FILE-NM <1> <2> token-type ZSPI-TYP-SUBVOL token-type FNAME Message Text The DSV <1> file <2> has no entry in A0CINFO. Planner must use CNFGINFO tool to update A0CINFO file for DSV and bring it into DSM/SCM as a separate input, then assign two inputs to the same Input Group. DSV skipped, processing continued.
3011 ZPHI-EVT-DUP-OSSFL-IN-A7CINFO Event Messages 3011 ZPHI-EVT-DUP-OSSFL-IN-A7CINFO The A7CINFO file contains two records for the same OSS file. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-INT-SVNM ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING Message Text pax archive file <1> in DSV <2> contains duplicate records for file <3>. DSV skipped, processing continues.
3012 ZPHI-EVT-OSSFL-IN-REL-PATHNM Event Messages 3012 ZPHI-EVT-OSSFL-IN-REL-PATHNM The A7CINFO file contains an OSS file with a relative path name. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-INT-SVNM ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING Message Text pax archive file <1> in DSV <2> contains invalid file <3> with a relative path name. Relative path names are not allowed by DSM/SCM. DSV skipped, processing continues.
3013 ZPHI-EVT-ARCH-FNAME-NOT-IN-A0C Event Messages 3013 ZPHI-EVT-ARCH-FNAME-NOT-IN-A0C The A7CINFO file contains an OSS file that refers to a nonexistent pax archive file. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-INT-SVNM ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING Message Text pax archive file <1> is missing from the A0CINFO file in DSV <2>. According to the A0CINFO file, <1> contains OSS file <3>. DSV skipped, processing continues.
3014 ZPHI-EVT-ARC-FN-NOT-TO-ZOSSUTL Event Messages 3014 ZPHI-EVT-ARC-FN-NOT-TO-ZOSSUTL A pax archive file referenced by an A7CINFO file is not placed in the ZOSSUTL TSV. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-INT-SVNM ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING Message Text pax archive file <1> in DSV <2> is not placed in the ZOSSUTL TSV. According to the A7CINFO file, <1> contains OSS file <3>. DSV skipped, processing continues.
3015 ZPHI-EVT-NO-DSV-FILE Event Messages 3015 ZPHI-EVT-NO-DSV-FILE The A0CINFO file has an entry for a file that is not in the distribution subvolume (DSV). Tokens ZPHI-TKN-INT-SVNM ZPHI-TKN-INT-FILE-NM <1> <2> token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-FNAME Message Text The DSV <1> has an entry in the A0CINFO file for the file <2>, which is not in the DSV. DSV skipped, processing continues. ZPHI-TKN-INT-SVNM is the name of the DSV where the error occurred.
3016 ZPHI-EVT-A7CINFO-FORMAT-ERROR Event Messages 3016 ZPHI-EVT-A7CINFO-FORMAT-ERROR The data in the A7CINFO file is not formatted correctly.
3016 ZPHI-EVT-A7CINFO-FORMAT-ERROR Event Messages Recovery. Contact the product vendor to re-create the A7CINFO file. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface.
3020 ZPHI-EVT-INV-CNFGINFO Event Messages 3020 ZPHI-EVT-INV-CNFGINFO You attempted to input a distribution subvolume (DSV), but the DSV contained an invalid A0CINFO file. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text Invalid A0CINFO file detected in DSV <1>. DSV processing skipped. ZPHI-TKN-INT-SVNM is the name of the DSV with the invalid A0CINFO file. Cause. You attempted to input a DSV, but the DSV contained an invalid A0CINFO file.
3021 ZPHI-EVT-INV-A1CINFO Event Messages 3021 ZPHI-EVT-INV-A1CINFO You attempted to input a distribution subvolume (DSV), but the DSV contained an invalid A1CINFO file. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text Invalid A1CINFO file detected in DSV <1>. DSV processing skipped. ZPHI-TKN-INT-SVNM is the name of the DSV with the invalid A1CINFO file. Cause. You attempted to input a DSV, but the DSV contained an invalid A1CINFO file.
3022 ZPHI-EVT-INV-VERSION Event Messages 3022 ZPHI-EVT-INV-VERSION You attempted to input a DSV containing a product that uses a version 3 A0CINFO file, which this version of DSM/SCM cannot read. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text The A0CINFO file in DSV <1> is version 3, which this version of DSM/SCM cannot read. Processing of this DSV stopped. Upgrade to a newer DSM/SCM version and retry your request.
3025 ZPHI-EVT-NO-DSMSCM-ON-SUT Event Messages 3025 ZPHI-EVT-NO-DSMSCM-ON-SUT The DSM/SCM product is not on the specified SUT. Tokens ZPHI-TKN-INPUT-NAME <1> token-type ZSPI-TYP-STRING Message Text Input <1> does not contain DSM/SCM product. Contact HP. ZPHI-TKN-INPUT-NAME is the name specified for the software input. Cause. The DSM/SCM product was not found on the specified SUT. Effect. If you copy this input to a new configuration revision, DSM/SCM is removed from the new revision. Recovery.
3030 ZPHI-EVT-INV-RLSEID-CUST Event Messages 3030 ZPHI-EVT-INV-RLSEID-CUST You attempted to input a site update tape (SUT) with invalid or missing RLSEID or CUSTFILE files. Tokens ZPHI-TKN-A-SITE-ID ZPHI-TKN-INT-SVNM <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-SUBVOL Message Text The A<1> subvolume <2> has invalid/missing RLSEID/CUSTFILE files. Contact HP. ZPHI-TKN-A-SITE-ID is the name of the first subvolume on the SUT.
3031 ZPHI-EVT-INPUT-SW-PROGRESS Event Messages 3031 ZPHI-EVT-INPUT-SW-PROGRESS A Receive-All-Files software input was started while another input was processing. Tokens None. Message Text Another software input is in progress. This Receive-All-Files software input cannot be started or cancelled when other software input requests are in progress. Restart this request after all the other software inputs are complete. Cause.
3035 ZPHI-EVT-INV-SUT-VERSION Event Messages 3035 ZPHI-EVT-INV-SUT-VERSION The SUT contains software at an RVU earlier than C30.10 or D20.00. Tokens ZPHI-TKN-SW-REL-VERSION <1> token-type ZSPI-TYP-STRING Message Text Invalid SUT version <1>. DSM/SCM can only accept SUTs for level C30.10/D20 and later. Ensure you have SUT at correct release level. ZPHI-TKN-SW-REL-VERSION is the NonStop RVU ID. Cause. The SUT contained software at an RVU earlier than C30.10 (C-series RVU) or D20.00 (D-series RVUs).
3045 ZPHI-EVT-DUP-SW-INP-NAME Event Messages 3045 ZPHI-EVT-DUP-SW-INP-NAME You specified a software input name that already exists. Tokens ZPHI-TKN-INPUT-NAME <1> token-type ZSPI-TYP-STRING Message Text Specified software input name <1> already exists. Specify another name and process the input again. ZPHI-TKN-INPUT-NAME is the name specified for the software input. Cause. You specified a software input name that already exists. Effect. The activity finishes with errors.
3050 ZPHI-EVT-DUP-PRODUCT Event Messages 3050 ZPHI-EVT-DUP-PRODUCT This software input contains a duplicate distribution subvolume (DSV). Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text Duplicate product in software input. Duplicate DSV <1> skipped, processing continues. ZPHI-TKN-INT-SVNM is the name of the duplicate DSV. Cause. The specified DSV corresponds to a product that has already been processed in a previous DSV for this software input. Effect.
3060 ZPHI-EVT-BAD-FILE-SIZE Event Messages 3060 ZPHI-EVT-BAD-FILE-SIZE The specified and real A0CINFO file sizes do not match. Tokens ZPHI-TKN-INT-SVNM ZPHI-TKN-FILE-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text The DSV <1> has an inconsistent A0CINFO file. File <2> has an incorrect file size. ZPHI-TKN-INT-SVNM is the name of a DSV in the software input. ZPHI-TKN-FILE-NAME is the name of the A0CINFO file in the DSV. Cause.
3065 ZPHI-EVT-BAD-FILE-LMT Event Messages 3065 ZPHI-EVT-BAD-FILE-LMT The last modification time of a PAX file has changed since the A7CINFO file was created. Tokens ZPHI-TKN-INT-SVNM ZPHI-TKN-FILE-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text The DSV <1> has an inconsistent A7CINFO file. File <2> has an incorrect last modification time. To correct, put DSV on disk, run CNFGINFO on DSV without changing any fields. Repeat Receive Software.
3070 ZPHI-EVT-UNKNOWN-A1-VERSION Event Messages 3070 ZPHI-EVT-UNKNOWN-A1-VERSION This version of DSM/SCM cannot recognize this version A1CINFO file. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-SUBVOL Message Text The DSV <1> has an A1CINFO file with an unknown file format version. A more recent version of DSM/SCM is required to receive this software. ZPHI-TKN-INT-SVNM is the name of a DSV in the software input. Cause.
3080 ZPHI-EVT-UNKNOWN-CAPABILITY Event Messages 3080 ZPHI-EVT-UNKNOWN-CAPABILITY A specific capability that is not in the current DSM/SCM product version is required to install the product. Tokens ZPHI-TKN-INT-SVNM ZPHI-TKN-CAPABILITY ZPHI-TKN-DSMSCM-VERSION <1> <2> <3> token-type ZSPI-TYP-SUBVOL token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text WARNING: The DSV <1> requires the <2> capability to be installed correctly. The <3> and later versions of DSM/SCM have this capability.
4010 ZPHI-EVT-SCRATCH-VOL-ERR Event Messages 4010 ZPHI-EVT-SCRATCH-VOL-ERR DSM/SCM could not access a scratch volume on the target scratch list. Tokens ZPHI-TKN-FE-ERROR ZPHI-TKN-INT-VOL-NM <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-DEVICE Message Text Error <1> accessing scratch volume <2>. Correct problem indicated in error. RESTART activity. ZPHI-TKN-FE-ERROR is the file-system error that occurred. For file-system error definitions, see Appendix B, File-System Errors.
4015 ZPHI-EVT-MOD-CONFTEXT Event Messages 4015 ZPHI-EVT-MOD-CONFTEXT The user tried to modify the CONFTEXT file to add software instead of adding it to the new revision. Tokens None. Message Text DSM/SCM does not allow user extensions to the standard defines in the STANDARD_MICROCODE, SYSTEM_PROCESS_LIBRARY_FILES, SYSTEM_LIBRARY_CODE_FILES, SYSTEM_PROCESS_CODE_FILES, FILES_TO_COPY_TO_NEW_SYSTEM sections of the SYSGEN configuration file.
4020 ZPHI-EVT-DB-OUT-OF-SYNC Event Messages 4020 ZPHI-EVT-DB-OUT-OF-SYNC The Configuration Builder and the Planner Interface received conflicting database information regarding operator activation instructions. Tokens None. Message Text Current database information for operator activation instructions out of sync with request information. Cause. The Configuration Builder and the Planner Interface received conflicting database information regarding operator activation instructions.
4030 ZPHI-EVT-BAD-RELEASE Event Messages 4030 ZPHI-EVT-BAD-RELEASE DSM/SCM could not perform the Build because the product list was created from an internal HP release. Tokens ZPHI-TKN-SW-REL-NAME ZPHI-TKN-DELF-CONFIG-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Release level <1> of configuration revision <2> is not supported by DSM/SCM. ZPHI-TKN-SW-REL-NAME is the name of the internal HP software release ID.
4032 ZPHI-EVT-OSS-PROD-NOT-ENABLED Event Messages ZPHI-TKN-FILE-NAME is the name of one of the pax archive files that DSM/SCM installs the OSS files from. Cause. The product likely contains a base version and several overlaid SPRs, not all of which are DSM/SCM-enabled. Effect. DSM/SCM does not manage the OSS files in the pax archive files listed in the subsequent event message 4032. The Build completes with warnings. Recovery.
4033 ZPHI-EVT-UNPROCESSED-A7CINFO Event Messages 4033 ZPHI-EVT-UNPROCESSED-A7CINFO One or more A7CINFO files in the configuration have not been processed. Tokens ZPHI-TKN-PRODUCT-LIST <1> token-type ZSPI-TYP-STRING Message Text The following OSS products either have unprocessed A7CINFO files, or contain non-pax files in ZOSSUTL: <1>. To process the A7CINFO files, re-receive these products into the archive using the Receive All Files option. Use CNFGINFO to remove any non-pax files from ZOSSUTL.
4035 ZPHI-EVT-NO-PROCESSED-PAX Event Messages 4035 ZPHI-EVT-NO-PROCESSED-PAX DSM/SCM cannot manage OSS files for a configuration that does not have any DSM/SCM-enabled OSS products. Tokens None Message Text No DSM/SCM enabled OSS products found(no A7CINFO files) in the configuration. CANCEL the Build, Remove OSS management from this Logical Target, and perform another Build. Cause.
4050 ZPHI-EVT-TOO-MANY-SRL-ZTILT Event Messages 4050 ZPHI-EVT-TOO-MANY-SRL-ZTILT The configuration contains more than one ZTILT source file. Tokens None. Message Text More than one SRL ZTILT source file exists. Cause. The configuration being built contains more than one ZTILT source file. Effect. The Build stops nonrestartable. Recovery. Cancel the Build, remove all but one ZTILT source file from the configuration, and start a new Build.
4070 ZPHI-EVT-FILE-CONFLICT-SRL Event Messages Recovery. If the indicated SRL file is needed, get a version of this SRL that contains an SRL relocatable that DSM/SCM can build an SRL executable with. 4070 ZPHI-EVT-FILE-CONFLICT-SRL A file conflicts with an SRL executable file.
4080 ZPHI-EVT-SRL-BUILD-MISMATCH Event Messages 4080 ZPHI-EVT-SRL-BUILD-MISMATCH The number of SRL relocatable files does not match the number of built SRL executable files. Tokens ZPHI-TKN-NUM-OF-SRL-RELOCS <1> ZPHI-TKN-NUM-OF-SRL-EXES <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT Message Text The number of SRL relocatable and ZTILT files, <1>, does not match the number of executable and ZTILT files, <2>, that were built by DSM/SCM.
4090 ZPHI-EVT-RELOC-NOT-FOUND Event Messages 4090 ZPHI-EVT-RELOC-NOT-FOUND An SRL relocatable file in the SRL log file is not in the configuration. Tokens ZPHI-TKN-FILE-NAME <1> token-type ZSPI-TYP-STRING Message Text The SRL relocatable file <1> referred to in the SRL log file could not be found in the configuration. ZPHI-TKN-FILE-NAME is the name of SRL relocatable file indicated in the NSKCOM output file named ZASRL*.SRLBLDOF. Cause.
4100 ZPHI-EVT-EXE-NOT-FOUND Event Messages 4100 ZPHI-EVT-EXE-NOT-FOUND An SRL executable file in the SRL log file is not in the Build subvolume. Tokens ZPHI-TKN-FILE-NAME ZPHI-TKN-SUBVOL-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text The SRL executable file <1> referred to in the SRL log file could not be found in the build subvolume <2>. ZPHI-TKN-FILE-NAME is the name of SRL executable file indicated in the NSKCOM output file named ZASRL*.SRLBLDOF.
4110 ZPHI-EVT-SRL-SERVER-COMP Event Messages 4110 ZPHI-EVT-SRL-SERVER-COMP A server process completed a DSM/SCM activity with warnings or errors. Tokens ZPHI-TKN-SRVR-COD ZPHI-TKN-SERVER-COMP-CD ZPHI-TKN-INT-FILE-NM <1> <2> <3> token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text <1> completed <2>. Examine server warning(s)/error(s) in file <3>, correct error(s) if necessary, RESTART activity if stopped in a restartable state.
4116 ZPHI-EVT-DLL-BUILD Event Messages • If the server completes the activity with errors, the operator should examine the messages from the server process and any appropriate output files to determine the corrective action needed. Correct the error, then either cancel the activity and resubmit it after the corrections have been made, or restart the activity. 4116 ZPHI-EVT-DLL-BUILD A set of public dynamic-link libraries (DLLs) is being built for the reason indicated.
4120 ZPHI-EVT-INV-SRL-OUTFILE Event Messages ZPHI-TKN-SRL-OUT-FILENAME is the name of the SRL build output file created during the SRL build. ZPHI-TKN-SUBVOL-NAME is the name of the subvolume where the SRL build output file is located. Cause. An inconsistency occurred in the SRL build output file. The expected sequence of INFO SRL commands and associated output was not found. Effect. The build stops nonrestartable. Recovery.
4130 ZPHI-EVT-INV-SRL-INFO-EXENM Event Messages 4130 ZPHI-EVT-INV-SRL-INFO-EXENM The expected SRL executable name was not in the SRL build output file. Tokens ZPHI-TKN-SRL-OUT-FILENAME ZPHI-TKN-SUBVOL-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Invalid SRL executable name in the SRL build output file <1> in the build subvolume <2>. ZPHI-TKN-SRL-OUT-FILENAME is the name of the SRL build output file created during the SRL build.
4140 ZPHI-EVT-INV-SRL-INFO-RELNM Event Messages 4140 ZPHI-EVT-INV-SRL-INFO-RELNM The expected SRL relocatable name was not in the SRL build output file. Tokens ZPHI-TKN-SRL-OUT-FILENAME ZPHI-TKN-SUBVOL-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Invalid SRL relocatable name in the SRL build output file <1> in the build subvolume <2>. ZPHI-TKN-SRL-OUT-FILENAME is the name of the SRL build output file created during the SRL build.
4150 ZPHI-EVT-NO-SRL-ZTILT Event Messages 4150 ZPHI-EVT-NO-SRL-ZTILT The SRL ZTILT source file does not exist. Tokens None. Message Text The SRL ZTILT source file does not exist. Cause. DSM/SCM is attempting to build the SRL executable files. A ZTILT source file is required to build and cannot be found in the configuration. The ZTILT source file should be supplied as file TPRETILT in product T7898. This can occur if: • • The ZTILT source file was not included in the configuration properly.
4152 ZPHI-EVT-SRL-EXES-EXCLUDED Event Messages Effect. DSM/SCM ignores these files. SRLs are not used for Integrity NonStop systems. Recovery. Informational message only; no corrective action is needed. 4152 ZPHI-EVT-SRL-EXES-EXCLUDED Executable shared run-time libraries (SRLs) were found in the TNS/E configuration. Tokens ZPHI-TKN-CNFG-FILE-NAME ZPHI-TKN-PRODUCT-NUMBER <1> <2> token-type ZSPI-TYP-STRING token_type ZSPI-TYP-STRING Message Text WARNING: Executable SRL found in the TNS/E configuration.
4155 ZPHI-EVT-NOT-IN-ARCHIVE Event Messages Recovery. Cancel the Build and create a new corrected revision including the public DLL loadfiles. 4155 ZPHI-EVT-NOT-IN-ARCHIVE One or more products in the configuration being built have been backed up to tape. Tokens None. Message Text One or more products in the Configuration being built has been backed up to tape. Restore the tape in the Software Archive and restart the activity. Cause.
4170 ZPHI-EVT-DUP-INSTR-ERROR Event Messages 4170 ZPHI-EVT-DUP-INSTR-ERROR A duplicate product file instruction was found. Tokens ZPHI-TKN-PRODUCT-NUMBER ZPHI-TKN-SECOND-PROD-NUM ZPHI-TKN-FILE-NAME ZPHI-TKN-SUBVOL-NAME <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Message Text ERROR: A duplicate file was found. Product <1> and Product <2> both place file <3> in TSV <4>. These two files have different fingerprints.
4171 ZPHI-EVT-DUP-OSS-FILE-ERR Event Messages 4171 ZPHI-EVT-DUP-OSS-FILE-ERR A duplicate product OSS file instruction was found. Tokens ZPHI-TKN-PRODUCT-NUM-1 ZPHI-TKN-PAX-FILE-1 ZPHI-TKN-PRODUCT-NUM-2 ZPHI-TKN-PAX-FILE-2 ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Message Text ERROR: A duplicate OSS file was found.
4180 ZPHI-EVT-DUP-INSTR-WARNING Event Messages 4180 ZPHI-EVT-DUP-INSTR-WARNING A duplicate product file instruction was found. Tokens ZPHI-TKN-PRODUCT-NUMBER ZPHI-TKN-SECOND-PROD-NUM ZPHI-TKN-FILE-NAME ZPHI-TKN-SUBVOL-NAME <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Message Text WARNING: A duplicate file was found. Product <1> and Product <2> both place file <3> in TSV <4>. These two files have the same fingerprints.
4181 ZPHI-EVT-DUP-OSS-FILE-WARN Event Messages 4181 ZPHI-EVT-DUP-OSS-FILE-WARN A duplicate product OSS file instruction was found. Tokens ZPHI-TKN-PRODUCT-NUM-1 ZPHI-TKN-PAX-FILE-1 ZPHI-TKN-PRODUCT-NUM-2 ZPHI-TKN-PAX-FILE-2 ZPHI-TKN-ABS-OSS-FILENAME <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Message Text WARNING: A duplicate OSS file was found.
4190 ZPHI-EVT-VERIF-READ-ERROR Event Messages 4190 ZPHI-EVT-VERIF-READ-ERROR An internal error occurred during the read of the verification list file. Tokens None. Message Text WARNING: Internal error on read of verification list file. Verification will be partial with regard to restart. Cause. An error occurred reading verified instructions from the restart verification list. Effect. Verification is not be performed against the instructions that could not be read from the list file.
4210 ZPHI-EVT-VERIF-INP-OPEN-ERR Event Messages 4210 ZPHI-EVT-VERIF-INP-OPEN-ERR A verification list file internal error occurred. Tokens None. Message Text WARNING: Internal error on open of previous restart verification list file. Only partial verification possible. Cause. An error occurred opening the file for instructions verified before restart. Effect. The activation package instructions left to be verified are not checked against the previously verified instructions. Recovery.
4230 ZPHI-EVT-NO-ARCHIVE-FILE Event Messages 4230 ZPHI-EVT-NO-ARCHIVE-FILE An activation package file could not be found in the archive. Tokens ZPHI-TKN-EXT-FNAME ZPHI-TKN-FE-ERROR ZPHI-TKN-NUM-ARCH-MISSING <1> <2> <3> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT Message Text WARNING: File <1> <2>. There were a found.
4250 ZPHI-EVT-LABEL-TAPE-APPLY Event Messages Cause. DSM/SCM is writing an activation package to a labeled tape as the user requested. Check the system EMS log to see any labeled tape operator messages. Effect. Informational message only; no corrective action is needed. Recovery. Informational message only; no corrective action is needed. 4250 ZPHI-EVT-LABEL-TAPE-APPLY The activation package is on a labeled tape, which the Apply process does not automatically support.
4261 ZPHI-EVT-NO-ZIMPIMP Event Messages 4261 ZPHI-EVT-NO-ZIMPIMP DSM/SCM can not find the manufactured ZIMPIMP file in the configuration. Tokens None. Message Text Internal Error: DSM/SCM can not find the manufactured ZIMPIMP file in the TNS/E configuration. CANCEL Build. Perform another Build request that requires a sysgen. Cause. The ZIMPIMP file is not found in the TNS/E configuration in the host database. Effect. The Build stops restartable. Recovery. Cancel the Build.
4270 ZPHI-EVT-RUNNING-SYSGEN-SIT Event Messages Cause. You either used a Gnn.nn RVU to build a configuration for a TNS/E target or an Hnn.nn RVU to build a configuration for a TNS/R target. • • A Gnn.nn SUT is intended only for a TNS/R target. An Hnn.nn SUT is intended only for a TNS/E target. Effect. The Build stops restartable. Recovery. Cancel the Build request. Check that the processor type for the target configuration is set correctly in the system maintenance profile.
4282 ZPHI-EVT-SPOOL-CONFLIST-SKIP Event Messages Effect. Informational message only; no corrective action is needed. Recovery. Informational message only; no corrective action is needed. 4282 ZPHI-EVT-SPOOL-CONFLIST-SKIP The spooler is not available. Spooling of the CONFLIST file is skipped.
4290 ZPHI-EVT-CREATE-ACTIV-PKG Event Messages 4290 ZPHI-EVT-CREATE-ACTIV-PKG DSM/SCM is ready to create the activation package. Tokens Message Text Creating activation package. Cause. The DSM/SCM Build process is ready to create the activation package. Effect. Informational message only; no corrective action is needed. Recovery. Informational message only; no corrective action is needed. 4300 ZPHI-SIT-COPY-FINISHED A DSM/SCM-generated SIT copy has finished. Tokens Message Text SIT tape copy finished.
5000 ZPHI-EVT-GRDN-SEC-ERR Event Messages Recovery. Informational message only; no corrective action is needed. 5000 ZPHI-EVT-GRDN-SEC-ERR An error occurred in setting an operating system security attribute for a file.
5005 ZPHI-EVT-ADD-SFG-SEC-ERR Event Messages ZPHI-TKN-CLRNPRG-SET-CD specifies whether the CLEARONPURGE attribute for the file is on or off: ZPHI-VAL-CLRNPRG-SET-OFF indicates that the CLEARONPURGE attribute for the file is set off. ZPHI-VAL-CLRNPRG-SET-ON indicates that the CLEARONPURGE attribute for the file is set on. ZPHI-TKN-LCNS-SET-CD specifies whether the file is licensed: ZPHI-VAL-LCNS-SET-OFF indicates that the file is not licensed. ZPHI-VAL-LCNS-SET-ON indicates that the file is licensed.
5010 ZPHI-EVT-VOL-NOT-ONLINE Event Messages ZPHI-TKN-SFG-ERROR is the Subsystem Programmatic Interface (SPI) error that occurred on a command to the Safeguard subsystem. For Safeguard SPI error definitions, see the Safeguard Management Programming Manual. ZPHI-TKN-INT-FILE-NM is the file name in the internal format of the file whose Safeguard attributes are being set. ZPHI-TKN-TO-INT-FILE-NM is the file name in the internal format of the file whose Safeguard attributes are being duplicated. Cause.
5012 ZPHI-EVT-OSS-NOT-UP Event Messages ZPHI-TKN-TARGET-NAME is the system name of the target. Cause. A Target Interface request to perform a Verify Database activity includes a TSV volume that is not online. DSM/SCM cannot process volumes that are not online. Effect. DSM/SCM skips processing the target and continues with the next target. Recovery. Ensure that the correct volume was specified. If so, check that the drive is up and accessible. Resubmit another Verify Database activity for the target.
5014 ZPHI-EVT-DO-OSSFL-INSTALL Event Messages ZPHI-TKN-TARGET-NAME is the system name of the target. Cause. The OSS root fileset is not started. Effect. The Apply stops in a restartable state. Recovery. Check the status of the root fileset. Check that it is started, and then restart the Apply request. 5014 ZPHI-EVT-DO-OSSFL-INSTALL DSM/SCM is installing OSS files for this configuration.
5020 ZPHI-EVT-INSUFF-DISK-SPACE Event Messages ZPHI-TKN-REASON-CD is the reason the backout could not be performed. Possible values are: not most recently applied no backup exists Cause. You are trying to perform a backout, but DSM/SCM cannot find a previously saved configuration. Either a backout was already performed, or the previous configuration was incorrectly specified. Effect. The activity finishes with errors. DSM/SCM does not perform a backout. Recovery.
5021 ZPHI-EVT-OVERRIDE-OS-DIFF Event Messages Cause. Not enough space is available on the volume specified to execute an Apply or Backout activity for the specified configuration. Effect. The activity stops in a restartable state. Recovery. Free space on the specified volume, or cancel the request and resubmit it specifying a different work volume on the Maintenance Interface.
5022 ZPHI-EVT-HOST-RUNNING-PREAAX Event Messages 5022 ZPHI-EVT-HOST-RUNNING-PREAAX OVERRIDE parameters cannot be used if the host is not running on DSM/SCM version T6031AAX or later. Tokens None. Message Text OVERRIDE SYSnn not allowed because the host system is not running DSM/SCM version T6031AAX or later Cause. The DSM/SCM product version of the host system is not T6031AAX or later. Effect. The Apply stops restartable. Recovery. Install the SPR T6031AAX or later on the host system.
5024 ZPHI-EVT-REPLACE-SYSGEN-FILE Event Messages Effect. The Apply stops restartable. Recovery. You have three alternatives: • Force the Apply to the same SYSnn subvolume and not place the new file created by a system generation program, specifying this OVERRIDE Pathway parameter to the Target Activator (TA): PATHCOM $YPHI =Alter TA-001, param OVERRIDE-SYSNN-DIFFERENT-OS "logical_target_nameRevision".
5025 ZPHI-EVT-CANNOT-REP-SYSNN Event Messages 5025 ZPHI-EVT-CANNOT-REP-SYSNN The Apply could not finish because the specified current configuration SYSnn subvolume could not be replaced. Tokens ZPHI-TKN-STATE-CD ZPHI-TKN-SYS-NN-NBR <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Cannot proceed, cannot replace <1> SYSnn <2>. Either coldload a different SYSnn and RESTART the activity or CANCEL this APPLY and start a new APPLY specifying a different target SYSnn.
5026 ZPHI-EVT-OVRIDE-PRM-PASSED Event Messages 5026 ZPHI-EVT-OVRIDE-PRM-PASSED The Apply could not finish because the specified SYSnn subvolume could not be replaced. Tokens ZPHI-TKN-SYS-NN-NBR <1> token-type ZSPI-TYP-STRING Message Text DSM/SCM has detected that the OSIMAGE file is different from the currently executing OSIMAGE file in SYSnn <1>.
5027 ZPHI-EVT-OVRIDE-PRM-MISSING Event Messages DSM/SCM checks for the OVERRIDE Pathway parameters and matches their values with the configuration revision being applied. If a match occurs, the Apply continues to the specified SYSnn subvolume without replacing the OSIMAGE, and no system load is required because the system continues running on the same OSIMAGE.
5028 ZPHI-EVT-CANNOT-OVERRIDE-EOF Event Messages 5028 ZPHI-EVT-CANNOT-OVERRIDE-EOF An Apply request detected that the old and new OSIMAGE files are different versions. The OVERRIDE-SYSNN-DIFFERENT-OS parameter is required for processing to continue. Tokens ZPHI-TKN-SYS-NN-NBR <1> token-type ZSPI-TYP-STRING Message Text DSM/SCM has detected that the new OSIMAGE file is different from the currently executing OSIMAGE in SYSnn <1>.
5029 ZPHI-EVT-OVERRIDE-SYSNN Event Messages 5029 ZPHI-EVT-OVERRIDE-SYSNN OVERRIDE-SYSNN parameters were specified to continue the Apply to a currently executing SYSnn subvolume. The new OSIMAGE is the same size as the running OSIMAGE. Tokens ZPHI-TKN-SYS-NN-NBR <1> token-type ZSPI-TYP-STRING Message Text DSM/SCM has detected that the new OSIMAGE file is different from the currently executing OSIMAGE in SYSnn <1>. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn <1> anyway.
5031 ZPHI-EVT-OVERRIDE-NOT-ALLOWED Event Messages 5031 ZPHI-EVT-OVERRIDE-NOT-ALLOWED OVERRIDE-SYSNN parameters were specified to continue the Apply to a currently executing SYSnn subvolume. The new OSIMAGE is the same version as the running OSIMAGE. Override parameters cannot be used. Tokens ZPHI-TKN-SYS-NN-NBR <1> token-type ZSPI-TYP-STRING Message Text DSM/SCM has detected that the new OSIMAGE file is same version as the ‘currently executing’ OSIMAGE file in SYSnn <1>.
5039 ZPHI-EVT-OSS-CLEANUP-NEEDED Event Messages ZPHI-TKN-FE-ERROR is the file-system error that is returned. For file-system error definitions, see Appendix B, File-System Errors. ZPHI-TKN-INT-FILE-NM is the file name in the internal format of the file that could not be accessed. Cause. DSM/SCM could not access a file because of a security violation. Effect. The activity stops in a restartable state. Recovery. Check the file-system error code in the message.
5040 ZPHI-EVT-MISSING-SYSNN Event Messages Effect. You cannot apply OSS files to the current OSS environment until these old DSM/SCM work files are removed. Recovery. Run CLEANOSS to remove the old DSM/SCM work files. 5040 ZPHI-EVT-MISSING-SYSNN The SYSnn target subvolume (TSV) is not present in the list of volumes you supplied.
5042 ZPHI-EVT-OSS-HRCHY-NOT-AVBLE Event Messages ZPHI-TKN-TARGET-NAME is the name of the logical target that manages OSS files. Cause. OSS is not started with the root fileset mounted. Effect. No OSS file verification is performed. Recovery. Start OSS and mount the root fileset. 5042 ZPHI-EVT-OSS-HRCHY-NOT-AVBLE A Verify Database request cannot verify OSS files for this logical target because the OSS environment is not available.
5044 ZPHI-EVT-OSS-HRCHY-DIFF-LT Event Messages ZPHI-TKN-TARGET-NAME is the name of the logical target that manages OSS files according to the DSM/SCM target database. ZPHI-TKN-HIERARCHY-LT is the name of the logical target that manages OSS files according to the /zzDSMSCM.Managed file. Cause. There are several possible causes, including: • • The OSS environment is shared between two different logical targets, and both are trying to manage the same OSS environment. The /zzDSMSCM.
5046 ZPHI-EVT-REMOVE-OSS-MANAGEMENT Event Messages ZPHI-TKN-HIERARCHY-LT is the name of the logical target that manages OSS files according to the /zzDSMSCM.Managed file. ZPHI-TKN-TARGET-NAME is the name of the logical target that manages OSS files according to the DSM/SCM target database. Cause. The OSS environment for this logical target is not running. A different OSS environment is running. Effect. No OSS file verification is performed for logical target ZPHI-TKN-TARGETNAME. Recovery.
5047 ZPHI-EVT-NEW-MNGD-FLS-CREATED Event Messages 5047 ZPHI-EVT-NEW-MNGD-FLS-CREATED A Verify Database request re-created missing zzDSMSCM.Managed files. Tokens ZPHI-TKN-CD-NUM <1> token-type ZSPI-TYP-INT Message Text Verify Database has created <1> new zzDSMSCM.Managed file(s) that were missing in the current OSS environment. ZPHI-TKN-CD-NUM is the number of zzDSMSCM.Managed files created. Cause. There should be a zzDSMSCM.Managed file in every directory that DSM/SCM manages.
5050 ZPHI-EVT-DISP-PRVW Event Messages 5050 ZPHI-EVT-DISP-PRVW This informational message contains an instruction to be performed by the operator to complete the Apply or Backout activity. Tokens ZPHI-TKN-DSMSCM-TEXT <1> token-type ZSPI-TYP-STRING Message Text DSM/SCM operator instruction: <1>. ZPHI-TKN-DSMSCM-TEXT is the operator instruction. Cause. The operator is required to perform a task to activate the software just applied. Effect. This message is sent with an operator instruction. Recovery.
5065 ZPHI-EVT-CANNOT-SHARE-TSV Event Messages 5065 ZPHI-EVT-CANNOT-SHARE-TSV An Apply activity completed with errors because the planner indicated that a configuration had a target subvolume (TSV) on a volume that was already being used by another target. DSM/SCM does not allow the same TSV to be shared by targets.
5070 ZPHI-EVT-TSV-CHANGE Event Messages 5070 ZPHI-EVT-TSV-CHANGE A target subvolume (TSV) has changed location. Tokens ZPHI-TKN-SUBVOL-NAME ZPHI-TKN-MOVE-ACTION-CD ZPHI-TKN-FROM-INT-VOL-NM ZPHI-TKN-FROM-FREE-TEXT ZPHI-TKN-TO-INT-VOL-NM <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-ENUM ZSPI-TYP-DEVICE ZSPI-TYP-STRING ZSPI-TYP-DEVICE Message Text DSM/SCM has detected that TSV <1> <2> from <3> <4> <5>.
5075 ZPHI-EVT-TSV-REMOVED Event Messages Effect. This message informs the operator and planner of the location change. The DSM/SCM database is updated to reflect the new TSV file location. Recovery. Informational message only; no corrective action is needed. 5075 ZPHI-EVT-TSV-REMOVED This informational message informs the operator and planner that a target file managed by DSM/SCM has been removed from its expected volume and subvolume location.
5080 ZPHI-EVT-NO-SAFEGUARD Event Messages 5080 ZPHI-EVT-NO-SAFEGUARD No file placement can be done at the target until Safeguard is running. Tokens None. Message Text No file placement performed; SAFEGUARD must be running before this APPLY or BACKOUT activity can be RESTARTED.
5090 ZPHI-EVT-FP-MISSING Event Messages Cause. DSM/SCM cannot be used with systems where two or more disk volumes have the same primary volume name and alternate volume name pair. Effect. The activity finishes with errors. DSM/SCM cannot process this request. DSM/SCM cannot use these volumes as destinations. They can exist on this system if not used by DSM/SCM. Recovery. If you want DSM/SCM to use these disk volumes for its activities, contact your system manager.
5095 ZPHI-EVT-INV-FILE Event Messages 5095 ZPHI-EVT-INV-FILE The specified file is corrupted. Tokens ZPHI-TKN-FILE-TYPE-CD ZPHI-TKN-INT-FILE-NM ZPHI-TKN-MEDIUM-CD <1> <2> <3> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-FNAME token-type ZSPI-TYP-ENUM Message Text Bad <1> file <2> on <3>. ZPHI-TKN-FILE-TYPE-CD is the file type of the file.
5100 ZPHI-EVT-INCOMPLETE-AP Event Messages ZPHI-VAL-FTYP-ZPHI6030 ZPHI6030 file ZPHI-VAL-FTYP-ZPHISYS ZPHISYS file ZPHI-VAL-FTYP-ZSSLIST ZSSLIST file ZPHI-TKN-INT-FILE-NM is the file name in the internal format of the file. ZPHI-TKN-MEDIUM-CD is the type of medium where the file is located. Possible values and the media they represent are: ZPHI-VAL-MED-DISK Disk ZPHI-VAL-MED-TAPE Tape Cause. The specified file is corrupted. Effect. The activity stops in a restartable state. Recovery.
5110 ZPHI-EVT-UNMNGD-RENAME Event Messages ZPHI-TKN-INT-SVNM is the name of the subvolume where the incomplete activation package is located. ZPHI-TKN-MEDIUM-CD is the medium where the incomplete activation package is located. Possible values and the media they represent are: ZPHI-VAL-MED-DISK Disk ZPHI-VAL-MED-TAPE Tape Cause. An activation package was incomplete. Effect. DSM/SCM completes the activity with errors. Recovery.
5115 ZPHI-EVT-CANT-CLD-DIFF-NN Event Messages Cause. A new file managed by DSM/SCM has the same name as an existing unmanaged file. The unmanaged file has been renamed into the PURGEME subvolume. Effect. DSM/SCM renames the file, issues this informational message, and continues processing. Recovery. If the file is no longer needed, purge the file from the PURGEME subvolume.
5125 ZPHI-EVT-CURR-NN-TSEGF-BLD Event Messages Effect. The new TACLSEGF file is for a different RVU than that of the currently running system. Recovery. If you perform a system load, TACL attempts to build the TACLSEGF file. After a system load, check that the TACLSEGF file has been built without errors.
5130 ZPHI-EVT-CANT-DO-FL-ACTION Event Messages If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well. If you need to process additional requests, you can cancel the activity and start a new Apply activity. After the problem is diagnosed, delete the nonrestartable request through the Maintenance Interface.
5130 ZPHI-EVT-CANT-DO-FL-ACTION Event Messages ZPHI-VAL-ACTION-EDITREAD EDITREAD procedure ZPHI-VAL-ACTION-EDITREADINIT EDITREADINIT procedure ZPHI-VAL-ACTION-FILEINFO FILEINFO procedure ZPHI-VAL-ACTION-FILEINQUIRE FILEINQUIRE procedure ZPHI-VAL-ACTION-FUP-DUP FUP DUP command ZPHI-VAL-ACTION-NEWPROCESS NEWPROCESS procedure ZPHI-VAL-ACTION-NEXTFILENAME NEXTFILENAME procedure ZPHI-VAL-ACTION-OPEN OPEN procedure ZPHI-VAL-ACTION-POSITION POSITION procedure ZPHI-VAL-ACTION-PUP-LISTLABEL PUP
5135 ZPHI-EVT-CHG-IN-SYS-ENV Event Messages 5135 ZPHI-EVT-CHG-IN-SYS-ENV Files have been modified since DSM/SCM placed them. Tokens NONE. Message Text Change in target system environment detected. Cause. One or more files have been modified since DSM/SCM placed them on the target system. Effect. The requested activity finishes nonrestartable. Recovery. Cancel the current request; then: 1. Use the Target Interface to perform a Verify Database request. 2.
5145 ZPHI-EVT-INCONSIS-DB Event Messages Effect. The activity stops in a restartable state. Recovery. Check the error code in the message. For a definition and recovery action for the specified error, see the Safeguard Management Programming Manual. Secure the file under Safeguard so that DSM/SCM can delete the file’s Safeguard attributes. Restart the activity. 5145 ZPHI-EVT-INCONSIS-DB An inconsistency exists between the target database and the actual files on the target system.
5150 ZPHI-EVT-OBSOLETE-TSV Event Messages 5150 ZPHI-EVT-OBSOLETE-TSV DSM/SCM could not delete the files in the specified TSV. Tokens ZPHI-TKN-INT-SVNM <1> token-type ZSPI-TYP-STRING Message Text Managed TSV <1> has become obsolete. Cannot delete files from the TSV because SYSnn associated with the configuration being obsoleted is currently executing. Delete files from the TSV manually once the SYSnn is no longer in use. ZPHI-TKN-INT-SVNM is the name of the obsolete target subvolume (TSV). Cause.
5152 ZPHI-EVT-OBSOLETE-TDL Event Messages Recovery. When the SYSnn subvolume of the old configuration is no longer needed, delete the TSV manually. The configuration files in these TSVs are kept. The DSM/SCM files (ZFBccncc, ZPHI6030, ZMPccncc, ZPHIFI, and so on) are removed from the TSV. This does not affect the success of the Apply for the new configuration.
5160 ZPHI-EVT-OBSOLETE-FILE Event Messages ZPHI-TKN-TDL-NAME is the name of the obsolete OSS directory. Cause. The last two configurations (the new configuration being placed and the previous configuration) share the same SYSnn subvolume. The (now obsolete) configuration prior to them went to a different SYSnn subvolume. Effect. This is an informational message. DSM/SCM does not purge obsolete OSS directories in this situation because they could be useful as backups.
5161 ZPHI-EVT-OBSOLETE-OSSFL Event Messages 5161 ZPHI-EVT-OBSOLETE-OSSFL DSM/SCM could not remove the specified file because of an OSS file-system error. Tokens ZPHI-TKN-FE-ERROR ZPHI-TKN-OSS-FILE-NM <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Message Text Error <1> encountered attempting to remove obsolete managed OSS file <2>. Remove the specified file manually. ZPHI-TKN-FE-ERROR is the OSS file-system error that occurred.
5171 ZPHI-EVT-BAD-PUB-DLL-SV-NAME Event Messages ZPHI-TKN-FROM-SUBVOL-NM is the name of the source subvolume of the TSV. ZPHI-TKN-TO-INT-VOL-NM is the name of the destination volume of the TSV. ZPHI-TKN-TO-SUBVOL-NM is the name of the destination subvolume of the TSV. ZPHI-TKN-TARGET-NAME is the name of the logical target being verified. Cause. The SYSnn subvolume has been moved or renamed to a subvolume not of the format SYSnn. Effect. DSM/SCM skips verification of the logical target. Recovery.
5180 ZPHI-EVT-BAD-SYSNN-NUMBER Event Messages ZPHI-TKN-TO-SUBVOL-NM indicates the name of the subvolume for the second TSV; for example, MYDLLS. Cause. A public DLL TSV was moved or copied to a subvolume whose name does not conform to the ZDLLrrr[a] naming convention. Effect. DSM/SCM removes the DSM/SCM work files from this subvolume. The Verify DB completes with warnings. The ZREGPTR file is not updated to point to the new subvolume. Recovery.
5190 ZPHI-EVT-MISSING-CURR-SYSNN Event Messages Cause. The SYSnn subvolume has been moved or renamed, but the nn portion of the new SYSnn subvolume is not a valid octal number. Effect. The activity finished with warnings. Recovery. Rename the SYSnn subvolume to specify a valid octal number. 5190 ZPHI-EVT-MISSING-CURR-SYSNN DSM/SCM is deleting the current configuration for a logical target from the target system.
5200 ZPHI-EVT-MISSING-PREV-SYSNN Event Messages 5200 ZPHI-EVT-MISSING-PREV-SYSNN DSM/SCM is deleting the previous configuration for a logical target from the target system. Tokens ZPHI-TKN-SUBVOL-NAME ZPHI-TKN-TARGET-NAME ZPHI-TKN-INT-VOL-NM <5> <3> <4> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING token-type ZSPI-TYP-DEVICE Message Text The SYSnn <1> for the previous configuration of target <2> is missing from <3> and was not found anywhere else on the system.
5210 ZPHI-EVT-NN-TSV-MOVED Event Messages 5210 ZPHI-EVT-NN-TSV-MOVED A SYSnn subvolume has been manually moved. Tokens ZPHI-TKN-FROM-INT-VOL-NM ZPHI-TKN-FROM-SUBVOL-NM ZPHI-TKN-TO-INT-VOL-NM ZPHI-TKN-TO-SUBVOL-NM ZPHI-TKN-TARGET-NAME <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type ZSPI-TYP-DEVICE ZSPI-TYP-DEVICE ZSPI-TYP-DEVICE ZSPI-TYP-DEVICE ZSPI-TYP-STRING Message Text DSM/SCM has detected that TSV <1>.<2> has been moved to <3>.<4> for target <5>.
5220 ZPHI-EVT-BAD-SYS-CSS-MOVE Event Messages 5220 ZPHI-EVT-BAD-SYS-CSS-MOVE The associated SYSnn and CSSnn subvolumes are on different volumes.
5221 ZPHI-EVT-TSVS-ON-DIFF-VOLS Event Messages 5221 ZPHI-EVT-TSVS-ON-DIFF-VOLS Two target subvolumes (TSVs) that are required to be on the same volume, usually the $SYSTEM volume, were found on two different volumes.
5222 ZPHI-EVT-ZREGPTR-UPDATE-FAILED Event Messages 5222 ZPHI-EVT-ZREGPTR-UPDATE-FAILED Verify Database is unable to modify the ZREGPTR file to point to the new public DLL location. Tokens ZPHI-TKN-DSMSCM-TEXT ZPHI-TKN-SUBVOL-NAME <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Unable to update <1> to point to the location of moved Public DLL TSV <2>. Modify the ZREGPTR file to point to the new Public DLL location.
5230 ZPHI-EVT-USING-TARGET-FILES Event Messages 5230 ZPHI-EVT-USING-TARGET-FILES A DSM/SCM file that should be on the system is missing. An error occurred while attempting to re-create the missing DSM/SCM file. The missing file is not critical to the success of the request, so the Apply is continuing. Tokens ZPHI-TKN-INT-FILE-NM <1> token-type ZSPI-TYP-FNAME Message Text WARNNG: File <1> is incorrect or missing and needs to be placed.
5250 ZPHI-EVT-BAD-ASSIGN Event Messages ZPHI-TKN-FILE-TYPE-CD is the type of file whose location is being reported. Typical values returned and the file types they represent are: ZPHI-VAL-FTYP-ZPHIFI ZPHIFI file ZPHI-VAL-FTYP-ZPHI6030 ZPHI6030 file ZPHI-VAL-FTYP-ZPHISYS ZPHISYS file For a complete list of the possible values for this token, see ZPHI-VAL-FTYP-nnn on page 4-14. Cause. The error in the previous message occurred while trying to re-create the missing file. Effect. The Apply continues.
5260 ZPHI-EVT-ASSIGN-IN-USE Event Messages Recovery. Correct the ASSIGN value through the Pathway server. For example: > PATHCOM $YPHI > ALTER ta-001, ASSIGN FILEMGR, $SYSTEM.CUSTOM.FILEMGR If you do not want the file specified in the ASSIGN to be used, cancel the request, delete the ASSIGN, and restart the activity: > ALTER ta-001, DELETE ASSIGN FILEMGR 5260 ZPHI-EVT-ASSIGN-IN-USE DSM/SCM is using the ASSIGN.
5280 ZPHI-EVT-PLACE-ALL-DISABLED Event Messages ZPHI-TKN-INT-FILE-NM is the file that contains an invalid alternate key file reference. Cause. DSM/SCM received error 21 from the File Utility Program (FUP) when attempting to copy (DUP) this file. The file has an incorrect alternate key attribute. Effect. The activity stops in a restartable state. Recovery. Correct the alternate key file name referenced in the specified file and restart the activity.
5300 ZPHI-EVT-NOT-COLDLOAD-VOLUME Event Messages 5300 ZPHI-EVT-NOT-COLDLOAD-VOLUME The target volume where SYSnn is located is not up as $SYSTEM. Tokens ZPHI-TKN-PRI-INT-VOL-NM ZPHI-TKN-ALT-INT-VOL-NM <1> <2> token-type ZSPI-TYP-DEVICE token-type ZSPI-TYP-DEVICE Message Text The target SYSNN volume <1> <2> is not up as $SYSTEM. The target SYSNN volume must be the coldload volume because OSS files are being installed. CANCEL the Apply. Coldload from the target SYSNN volume and RESTART the Apply.
5310 ZPHI-EVT-OLD-OSS-WRK-FLS Event Messages ZPHI-TKN-TARGET-NAME is the name of the logical target attempting to manage OSS files in the current OSS environment. Cause. According to the /zzDSMSCM.Managed file, the current OSS environment is being managed by a logical target other than the one trying to manage OSS files with the current Apply. Effect. The activity stops in a restartable state. Recovery.
5320 ZPHI-EVT-MISSING-OSS-WRK-FLS Event Messages 5320 ZPHI-EVT-MISSING-OSS-WRK-FLS The OSS environment contains old DSM/SCM work files that need to be cleaned up before the Apply can continue. Tokens ZPHI-TKN-APPLY-LT <1> token-type ZSPI-TYP-STRING Message Text Missing /zzDSMSCM.Managed file. CANCEL Apply. Run CLEANOSS, then Verify Database to remove prior OSS file management for Logical Target <1>. Then start Apply. Management of OSS files will be restored.
5325 ZPHI-EVT-MNGD-OSSFL-NOT-RMVD1 Event Messages Recovery. Cancel the Apply. Run CLEANOSS and Verify Database to remove OSS management of the current OSS environment. Then restart the Apply. 5325 ZPHI-EVT-MNGD-OSSFL-NOT-RMVD1 Management of OSS files by the specified logical target is being removed. DSM/SCM work files are not removed from the OSS environment because OSS is not started.
5331 ZPHI-EVT-MNGD-OSSFL-NOT-RMVD2 Event Messages ZPHI-TKN-TARGET-NAME is the name of the logical target on which OSS file management will be removed. Cause. The OSS environment is not available because a different $SYSTEM volume was system loaded. Effect. The Apply completes with warnings. OSS management is removed from the logical target, and the target database is updated. DSM/SCM work files are not removed from the OSS environment.
5335 ZPHI-EVT-OSS-MNGMT-REMOVED Event Messages Recovery. If the OSS environment is managed by ZPHI-TKN-HIERARCHY-LT, no action is required. Otherwise, run CLEANOSS. 5335 ZPHI-EVT-OSS-MNGMT-REMOVED The specified logical target no longer manages OSS files. Tokens ZPHI-TKN-TARGET-NAME <1> token-type ZSPI-TYP-STRING Message Text Management of OSS files has been removed for target <1>. ZPHI-TKN-TARGET-NAME is the name of the logical target for which OSS file management was removed. Cause.
5350 ZPHI-EVT-ZDLLRRRA-NOT-FOUND Event Messages ZPHI-TKN-TO-SUBVOL-NAME is the TSV where the new set of public DLLs are placed. Cause. You specified the OVERRIDE-SYSNN parameter and a new set of public DLLs is to be placed in a new ZDLLrrr[a] TSV. Effect. A new set of public DLL files are placed in the specified subvolume. The ZREGPTR file is not changed to point to these new public DLLs. The Apply continues but completes with warnings.
5360 ZPHI-EVT-ZDLLRRRA-NOT-ACTIVE Event Messages ZPHI-TKN-FROM-SUBVOL-NAME is the subvolume where the active set of public DLLs exist. An active set of public DLLs is the set used at last system load. ZPHI-TKN-FILE-NAME is the name of the first active public DLL file found to be incorrect. ZPHI-TKN-DSMSCM-TEXT indicates why ZPHI-TKN-FILE-NAME was incorrect. The value is either missing or different (expected fingerprint=%s, actual=%s)”.
6000 ZPHI-EVT-REQ-CANCLD Event Messages ZPHI-TKN-TO-SUBVOL-NAME indicates the subvolume where the active set of public DLLs are. ZPHI-TKN-FILE-NAME is the name of the first active public DLL file found to be incorrect. ZPHI-TKN-DSMSCM-TEXT indicates why ZPHI-TKN-FILE-NAME was incorrect. The value is either missing or different (expected fingerprint=%s, actual=%s). ZPHI-TKN-SUBVOL-NAME is the ZDLLrrr[a] TSV name that contains a correct set of public DLLs. Cause.
6005 ZPHI-EVT-PSEND-ERR Event Messages 6005 ZPHI-EVT-PSEND-ERR A Pathsend error occurred. Tokens ZPHI-TKN-PATHSEND-ERROR ZPHI-TKN-FE-ERROR ZPHI-TKN-SERVER-CLASS-NM ZPHI-TKN-PMON-PRCS-NM <1> <2> <3> <4> token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-STRING Message Text Cannot communicate with server, PATHWAY error <1>, file system error <2>, serverclass <3>, PATHMON <4>. Correct PATHWAY error. RESTART the activity.
6010 ZPHI-EVT-CANNOT-CANCEL Event Messages 6010 ZPHI-EVT-CANNOT-CANCEL A DSM/SCM cancel operation could not be performed at this node because the activity to be cancelled is being performed at a remote node. Tokens ZPHI-TKN-REQUEST-NM ZPHI-TKN-TARGET-NODE-NM <1> <2> token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Message Text Cannot cancel <1> at this node. Planner must issue a CANCEL at the local node <2>. ZPHI-TKN-REQUEST-NM is the text of the request that was not cancelled.
6020 ZPHI-EVT-TA-DEP-ERR Event Messages ZPHI-TKN-TIMER-TYPE-CD is the timer where the error occurred. Possible values and their meanings are: ZPHI-VAL-TIMER-CANCEL indicates that the error occurred while attempting to cancel a timer via the CANCELTIMEOUT procedure. ZPHI-VAL-TIMER-START indicates that the error occurred while attempting to start a timer via the SIGNALTIMEOUT procedure. Cause. An internal DSM/SCM scheduling error occurred. Effect. The activity stops in a restartable state. Recovery.
6025 ZPHI-EVT-ERR-REP Event Messages ZPHI-TKN-ACT-NM-CD2 is the name of the request you are trying to submit. Cause. A second activity was requested while one activity was in progress. Only one activity can execute at one time. Effect. The second request is not started. A second activity can be performed only after the current one is completed. Recovery. Restart the activity after the current activity finishes. 6025 ZPHI-EVT-ERR-REP An error occurred at a remote system.
7000 ZPHI-EVT-FILES-EXPORTED Event Messages 7000 ZPHI-EVT-FILES-EXPORTED Files were exported from the DSM/SCM archive. Tokens ZPHI-TKN-EXPORT-TYPE-CD ZPHI-TKN-EXPORT-SUBVOL <1> <2> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-SUBVOL Message Text <1> file(s) exported to <2>. ZPHI-TKN-EXPORT-TYPE-CD is the type of file that was exported.
Event Messages 7000 ZPHI-EVT-FILES-EXPORTED DSM/SCM Event Management Programming Manual—529844-003 5 -214
6 Event Messages From Other Subsystems This section describes the content and meaning of all the event messages generated by other subsystems that are returned by DSM/SCM. Some utilities (BACKUP, DISKGEN, File Manager, SYSGEN, and Tape Reader) use a DSM/SCM template that includes a SHARED_SSID statement specifying the DSM/SCM subsystem ID, ZPHIVAL-SSID. This lets these utilities share use of the DSM/SCM message header and to report their events to DSM/SCM.
0001 ZBRT-EVT-DPTERR Event Messages From Other Subsystems 0001 ZBRT-EVT-DPTERR The Tape Reader subsystem returned a tape error. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT Message Text DSM/SCM TapeReader *0001* : *ERROR* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape error that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0002 ZBRT-EVT-DPTWARN Event Messages From Other Subsystems 0002 ZBRT-EVT-DPTWARN The Tape Reader subsystem returned a tape warning. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT Message Text DSM/SCM TapeReader *0002* : *WARNING* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape warning that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0003 ZBRT-EVT-DPTMERR Event Messages From Other Subsystems 0003 ZBRT-EVT-DPTMERR The Tape Reader subsystem returned a tape mount error. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP- Message Text DSM/SCM TapeReader *0003* : *ERROR* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape mount error that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0004 ZBRT-EVT-DPTMWARN Event Messages From Other Subsystems 0004 ZBRT-EVT-DPTMWARN The Tape Reader subsystem returned a tape mount warning. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP- Message Text DSM/SCM TapeReader *0004* : *ERROR* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape mount warning that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0005 ZBRT-EVT-DPTMOUNTMESSAGE Event Messages From Other Subsystems 0005 ZBRT-EVT-DPTMOUNTMESSAGE The Tape Reader subsystem returned a tape mount message to inform you to mount a tape. Tokens ZEMS-TKN-TEXT <1> token-type ZSPI-TYP-INT Message Text DSM/SCM TapeReader *0005* : *MOUNT MESSAGE*: <1>. ZEMS-TKN-TEXT contains the text of the tape mount message. Cause. The Tape Reader subsystem returned a tape mount message to inform you to mount a tape. Effect.
0006 ZBRT-EVT-BKUPTERR Event Messages From Other Subsystems 0006 ZBRT-EVT-BKUPTERR The BACKUP subsystem returned a tape error. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP- Message Text Backup *0001* : *ERROR* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape error that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0007 ZBRT-EVT-BKUPTWARN Event Messages From Other Subsystems 0007 ZBRT-EVT-BKUPTWARN The BACKUP subsystem returned a tape warning. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP- Message Text Backup *0002* : *WARNING* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape warning that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0008 ZBRT-EVT-BKUPTMERR Event Messages From Other Subsystems 0008 ZBRT-EVT-BKUPTMERR The BACKUP subsystem returned a tape mount error. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP- Message Text Backup *0003* : *ERROR* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape mount error that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0009 ZBRT-EVT-BKUPTMWARN Event Messages From Other Subsystems 0009 ZBRT-EVT-BKUPTMWARN The BACKUP subsystem returned a tape mount warning. Tokens ZBRT-TKN-ERROR ZBRT-TKN-ERROR <1> <2> token-type ZSPI-TYP-INT token-type ZSPI-TYP- Message Text Backup *0004* : *ERROR* Tape-<1>: <2>. ZBRT-TKN-ERROR (1) is the numeric value of the tape mount warning that occurred. For possible values for this token, see Appendix C, BACKUP Errors. ZBRT-TKN-ERROR (2) is a text translation of the error.
0010 ZBRT-EVT-BKMOUNTMESSAGE Event Messages From Other Subsystems 0010 ZBRT-EVT-BKMOUNTMESSAGE The BACKUP subsystem returned a tape mount message to inform you to mount a tape. Tokens ZEMS-TKN-TEXT <1> token-type ZSPI-TYP-STRING Message Text Backup *0005* : *Mount Message*: <1>. ZEMS-TKN-TEXT contains the text of the tape mount message. Cause. The BACKUP subsystem returned a tape mount message to inform you to mount a tape. Effect.
0001 ZSGN-EVT-SYSGEN-COMPLETED Event Messages From Other Subsystems 0001 ZSGN-EVT-SYSGEN-COMPLETED A system generation program has finished. The number of errors returned (if any) is reported. Tokens ZSGN-TKN-ERROR-COUNT <1> token-type ZSPI-TYP-INT Message Text SYSGEN COMPLETED FOR DSM/SCM WITH error-num ERRORS ZSGN-TKN-ERROR-COUNT is the number of errors (if any) returned by a system generation program. Cause. System generation has finished. Effect. The number of errors (if any) is reported. Recovery.
A Token Codes Table A-1 summarizes the token codes specific to the DSM/SCM subsystem. The token type is given for each token code. To derive the symbolic name of the token number from the name of the token code, replace -TKN- with -TNM-. Table A-1.
Token Codes Table A-1.
Token Codes Table A-1.
Token Codes Table A-1.
B File-System Errors Table B-1 lists file-system errors and provides a brief description of each error. For information about correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. Note. To display the message text of a file-system error, at a TACL prompt, type error followed by the error number; for example, error 2. To display the message text and number of all file-system and sequential query language (SQL) errors, type: error -1. Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1.
File-System Errors Table B-1. File-System Errors (page 10 of 12) Decimal Number Octal Number 713 %1311 An attempt was made to remove a recoverable resource manager from the directory using the TM_REC_RM_REMOVE_ procedure, but the resource manager still has unresolved transactions outstanding. 714 %1312 A call to TMF_EXPORT_ or TMF_IMPORT_ specified an invalid combination of protocols and options for the transaction branch. 715 %1313 An invalid transaction handle was specified.
File-System Errors Table B-1. File-System Errors (page 11 of 12) Decimal Number Octal Number 728 %1328 An attempt was made to set the current transaction of a process by invoking TMF_SETTXHANDLE_ passing in the TxHandle obtained by exporting a transaction branch to a volatile resource manager with the pre-prepare option, but the exported transaction branch is prepared. 729 %1331 An attempt was made to write branch data to a prepared exported or imported transaction branch.
File-System Errors Table B-1.
C BACKUP Errors Table C-1 lists BACKUP errors and provides text descriptions. These errors appear as the value of ZBRT-TKN-ERROR in the BACKUP event messages described in Section 6, Event Messages From Other Subsystems. For information on correcting BACKUP errors, see the Guardian Disk and Tape Utilities Reference Manual. Table C-1. BACKUP Errors (page 1 of 2) Error Number Text Description of Error 7500 Not positioned to the beginning of the tape.
BACKUP Errors Table C-1. BACKUP Errors (page 2 of 2) Error Number Text Description of Error 7522 Tape verify found problem with ending volume label. 7523 Tape verify found different number of data blocks than were supposed to have been written. 7524 Tape verify found file label problem. 7525 Tape verify found data block problem. 7526 Tape verify found beginning volume label does not match what was supposed to have been written. 7527 System image tape too short.
Index A Alternate collector ($ZPHI), EMS 1-5, 3-3 Archive and Database Maintenance Interface 1-2 B tokens 4-21 user interfaces 1-2 Distributors, EMS 1-4 DSM/SCM See Distributed Systems Management/Software Configuration Manager (DSM/SCM) Buffer declaration 4-6 E C C language 2-2 Circumflex (^) in symbolic names 2-2 CNFGINFO 1-2 COBOL 2-2 Collectors, EMS alternate ($ZPHI) 1-5, 3-3 primary ($0) 1-5, 3-3 Compatibility distributor ($Z0), EMS 1-4 Compiler, EMS filter 3-3 Conditional tokens 5-25 Configuration
F Index Event messages (continued) retrieving 3-1 selection 3-3 table of 5-2/5-16 tokens 2-1 Event numbers 2-2 F Field types 2-3 Filter object file 3-3 Filter table creating and loading 3-6/3-8 examples 3-8 format 3-6/3-7 writing 3-3 Filter, EMS 3-3/3-4 Forwarding distributor, EMS 1-4 P P error and S error tokens 5-34 Pathway environment, defined 1-1 Pathway messages used by DSM/SCM components 1-2 Pathway server classes of DSM/SCM components 1-1 Planner Interface 1-2 Predefined DSM/SCM values 4-6/4-21 P
T Index T TACL 2-2 TAL 2-2 Target Activator 1-2 Target environment 1-1/1-3 Target Interface 1-2 Token codes A-1 Token numbers A-1 Token types 2-3 Token values, predefined 4-6 Tokens conditional 5-25 description 2-1 DSM/SCM 2-1 related manuals 2-1 simple 4-21 unconditional 5-24 U Unconditional tokens 5-24 Underscore (_) in symbolic names 2-2 Utility Server 1-2 Z ZBRT-EVTBKMOUNTMESSAGE 6-11 BKUPERROR 6-11 BKUPTERR 6-7 BKUPTMERR 6-9 BKUPTMWARN 6-10 BKUPTWARN 6-8 DPTERR 6-2 DPTMERR 6-4 DPTMOUNTMESSAGE 6-6 D
Z Index ZPHI-EVT- (continued) BAD-ALT-KEY-FILENM 5-198 BAD-ASSIGN 5-197 BAD-FILE-LMT 5-113 BAD-PUB-DLL-SV-NAME 5-188 BAD-RELEASE 5-119 BAD-SYSNN-NAME 5-187 BAD-SYSNN-NUMBER 5-189 BAD-SYS-CSS-MOVE 5-193 CANNOT-BACKOUT 5-152 CANNOT-CANCEL 5-210 CANNOT-OVERRIDE-EOF 5-160 CANNOT-REP-SYSNN 5-157 CANNOT-SHARE-TSV 5-170 CANT-CLD-DIFF-NN 5-178 CANT-DO-FL-ACTION 5-180 CHG-IN-SYS-ENV 5-182 CORR-DB-ERR 5-42 CREATE-ACTIV-PKG 5-147 CREATING-SIT-COPY 5-147 CURR-NN-TSEGF-BLD 5-179 DB-OBJ-CHECKED-OUT 5-76 DB-OBJ-IN-USE 5
Z Index ZPHI-EVT- (continued) MISSING-CURR-SYSNN 5-190 MISSING-FILE 5-61 MISSING-OSSFL 5-62 MISSING-OSS-WKR-FLS 5-202 MISSING-PREV-SYSNN 5-191 MISSING-SYSNN 5-164 MNGD-OSSFL-NOT-REMVD 5-203 MNGD-OSSFL-NOT-RMVD1 5-203 MNGD-OSSFL-NOT-RMVD2 5-204 MOD-CONFTEXT 5-117 NEW-MNGD-FLS-CREATED 5-168 NEW-NN-TSEGF-BLD 5-178 NN-TSV-MOVED 5-192 NOT-COLDLOAD-VOLUME 5-200 NOT-ONLINE 5-169 NO-A1CNFG-FILE 5-91 NO-A7CNFG-FILE 5-92 NO-ARCHIVE-FILE 5-142 NO-CNFG-ENTRY 5-95 NO-CNFG-FILE 5-90 NO-DSMSCM-ON-SUT 5-106 NO-DSV-FILE 5
Z Index ZPHI-EVT- (continued) SERVER-COMP 5-52 SERVER-COMP-DETAIL 5-54, 5-56 SERVER-VERSION 5-81 SREGPTR-NOT-CHANGED 5-205 SRL-BUILD-MISMATCH 5-125 SRL-MISMATCH 5-122 SRL-NOMATCH-BUILT 5-123 SRL-RELOCS-EXCLUDED 5-133 SRL-SERVER-COMP 5-128, 5-129 SS-OUTDTD 5-89 SS-REQD 5-30 TA-DEP-ERR 5-211 TIMER-ERR 5-210 TOO-MANY-SRL-ZTILT 5-123 TSVS-ON-DIFF-VOLS 5-194, 5-195 TSV-CHANGE 5-171 TSV-REMOVED 5-172 UNABLE-TO-ACCESS 5-67 UNKNOWN-A1-VERSION 5-114 UNKNOWN-A7-VERSION 5-114 UNKNOWN-CAPABILITY 5-115 UNKNOWN-OSSFL-R
Z Index FE-ERROR 5-36, 5-45, 5-47, 5-49, 5-65, 5-66, 5-101, 5-116, 5-142, 5-148, 5-150, 5-163, 5-182, 5-186, 5-187, 5-209, 5-210 FILE-FINGERPRINT 5-174 FILE-NAME 5-93, 5-94, 5-96, 5-97, 5-98, 5-99, 5-101, 5-112, 5-113, 5-120, 5-123, 5-124, 5-126, 5-127, 5-136, 5-138, 5-172, 5-174, 5-181, 5-198 file-name 5-154, 5-155, 5-156 FILE-NM 5-77, 5-79 FILE-TYPE-CD 5-25, 5-37, 5-39, 5-58, 5-59, 5-61, 5-62, 5-64, 5-70, 5-77, 5-79, 5-175, 5-197, 5-198, 5-199, 5-200, 5-201, 5-202, 5-203, 5-204, 5-205 FILE-TYPE-NM 5-196
Z Index SERVER-CLASS-NM 5-33, 5-69, 5-209 SERVER-COMP-CD 5-52, 5-54, 5-128 SPACE-EXISTS 5-153 SPACE-REQUIRED 5-153 SQL-DB-ERR-BUF 5-42, 5-83 SRL-OUT-FILENAME 5-130, 5-131, 5-132 SRVR-COD 5-52, 5-54, 5-128 STAGE-CODE 5-22 STATE-CD 5-157 SUBVOL-NAME 5-127, 5-130, 5-131, 5-132, 5-136, 5-138, 5-164, 5-171, 5-174, 5-181, 5-190, 5-191 SVR-CLS-NM 5-22 SVR-CLS-PRM-NM 5-63 SVR-CLS-PRM-VAL 5-63 SW-REL-NAME 5-119 SYSNN-INT-VOL-NM 5-193 SYSNN-NBR 5-178, 5-179, 5-189 SYSNN-SUBVOL-NM 5-193 SYS-NN-NBR 5-154, 5-155, 5-15
Z Index ACT-TA-APP-CNFG 4-7 ACT-TA-BACKOUT-CNFG 4-7 ACT-TA-CREATE-SS 4-7 ACT-TA-GET-PREVIEW 4-7 ACT-TA-IND-SS 4-7 ACT-TA-INIT-APP-CNFG 4-7 ACT-TA-VERIFY-DB 4-7 ACT-UT-EXPORT-FILES 4-7 ACT-UT-HOST-REP-D 4-7 ACT-UT-HOST-REP-P 4-8 ACT-UT-IPMREP-REP-D 4-8 ACT-UT-IPMREP-REP-P 4-8 ACT-UT-IPMREQ-REP-D 4-8 ACT-UT-IPMREQ-REP-P 4-8 ACT-UT-REL-DOC-D 4-8 ACT-UT-REL-DOC-P 4-8 ACT-UT-SOFTDOC-D 4-8 ACT-UT-SOFTDOC-P 4-8 ACT-UT-TARG-REP-D 4-8 ACT-UT-TARG-REP-P 4-8 ACT-UT-USER-DEF-D 4-8 ACT-UT-USER-DEF-P 4-9 CLRNPRG-SET-OF
Special Characters Index IR-INV-ACT-CD 4-17 IR-INV-DB-INFO 4-17 IR-INV-IPC-PARAM 4-17 IR-INV-PARAM-CODE 4-17 IR-INV-PWY-PARAM 4-17 IR-INV-RETURN-CODE 4-17 IR-INV-STATUS 4-17 IR-INV-USER-FUNC 4-17 IR-NO-FILE-INSTR 4-17 IR-NO-SS-FILENAME 4-17 IR-NO-SVOL 4-17 IR-TOOL-NOT-FOUND 4-17 IR-TRGT-NOT-SPEC 4-17 IR-UNABLE-TO-ACCESS 4-18 LCNS-SET-OFF 4-18 LCNS-SET-ON 4-18 MED-DISK 4-18 MED-TAPE 4-18 MOVE-COPIED 4-18 MOVE-MISSING 4-18 MOVE-MOVED 4-18 PRGD-SET-OFF 4-19 PRGD-SET-ON 4-19 SERVER-BACKUP 4-19 SERVER-COMP-ERR
