IBM. IBM Tivoli Candle Products Messages. Volume 4 (KONCV - OC) Tivoli. Version SC

Transcription

1 Tivoli IBM Tivoli Candle Products Messages IBM Version Volume 4 (KONCV - OC) SC

2 12 1 2

3 Tivoli IBM Tivoli Candle Products Messages IBM Version Volume 4 (KONCV - OC) SC

4 Note Before using this information and the product it supports, read the information in Notices on page 329. Fourth Edition (November 2005) This edition applies to version 1, release 0, modification 3 of IBM Tivoli Candle Products Messages and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC Copyright International Business Machines Corporation 1992, All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Preface Chapter 1. KONCV001 KXDFC Chapter 2. LAT000 MRG Chapter 3. OB0101 OB Chapter 4. OBV101 OC Chapter 5. OC1000 OC Appendix A. Support Information Appendix B. Notices

6 6 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

7 P Preface The IBM Tivoli Candle Products Messages: Volume 4 (KONCV OC) book contains product messages with prefixes KONCV to OC. This manual is Volume 4 of a five-volume message set that documents messages issued by IBM Tivoli Candle products. It is intended as a reference for operations staff, systems programmers, and performance analysts who need to interpret messages that are issued by IBM Tivoli Candle products. The five-volume set of message manuals includes messages that are issued by the following products: AF/OPERATOR on z/os Alert Adapter for OMEGACENTER Gateway on MVS Candle Management Server EPILOG for VM OMEGACENTER Gateway for MVS OMEGAMON for VM OMEGAMON II for CICS OMEGAMON II for IMS and DBCTL OMEGAMON II for Mainframe Networks OMEGAMON II for MVS OMEGAMON II for SMS IBM Tivoli OMEGAMON XE for CICS on z/os IBM Tivoli OMEGAMON XE for IMS on z/os IBM Tivoli OMEGAMON XE for Mainframe Networks IBM Tivoli OMEGAMON XE for Storage on z/os IBM Tivoli OMEGAMON XE on z/os OMEGAVIEW Preface 7

8 What s New in This Release? For this release, the following message sets have been removed from these volumes. Explanation of these messages are found within the documentation sets for the individual products: Table 1. Message sets removed from the Candle Products message set Message Set IBM Tivoli OMEGAMON XE for WebSphere MQ (previously CCC for MQSeries and CCC for MQSeries Configuration) IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers IBM Tivoli OMEGAMON XE for WebSphere InterChange Server IBM Tivoli OMEGAMON XE for DB2 Performance Monitor/Expert on z/os OMEGAMON II for DB2 Prefix KMQ, KCF, and KMC KQI KIE O2, KDP H2 Types of Messages There are two types of messages: Standard messages and abend codes on page 8 Online messages on page 9 Standard messages and abend codes IBM Tivoli Candle products routinely issue standard messages and display them on the screen. Messages with the following prefixes are exceptions. Products OMEGAMON II for DB2 OMEGAMON II for DBCTL OMEGAMON II for IMS OMEGAMON II for MVS OMEGAMON II for MVS All OMEGAMON II products All OMEGAMON II products Prefix Exceptions EB, EU, and EP messages are written to the file or SYSOUT class specified by the RKM2OUTM dataset. EC messages appear as WTO messages on the system operator console, in the RKM2OUTM or RKM2DUMP dataset output, or as messages to TSO user terminals (if the NOTIFY keyword is specified in &rhilev.&midlev.rkanpar(kepoptn)). Note: EU messages are equivalent to EP messages. OM2 KLE, KLU, and KLV messages are written to the RKLVLOG dataset. Messages displayed by additional features, such as PRO for MVS or OBTAIN, are included in this manual. 8 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

9 OMEGAMON II or OMEGAVIEW issues abend codes when an error occurs. Note: For OMEGAMON II for MVS and OMEGAMON II for SMS, messages that appear during the operation of OMEGAMON II may be issued from the product, Candle Management Server (CMS), or Candle subsystem address spaces. Online messages OMEGAMON II messages are also available as online documentation for OMEGAMON II for DB2 OMEGAMON II for DBCTL OMEGAMON II for IMS OMEGAMON II for MVS These messages are in member KOCMSGS of thilev.tkansam. The online message file is allocated and unloaded during the standard installation procedure. The online messages can be browsed using ISPF or printed with JCL similar to that in the following figure. FIGURE 1. Sample JCL To Print the Online Message File //Jobcard //PRINT EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DISP=OLD,DSN=thilev.KANSAM(KOCMSGS) //SYSUT2 DD SYSOUT= Manual organization This section explains the organization of this set of manuals. Message numbering The IBM Tivoli Candle Products Messages set of books consists of five volumes: Volume 1 contains messages with prefixes AOP ETX. Volume 2 contains messages with prefixes EU KLVGM. Volume 3 contains messages with prefixes KLVHS KONCT. Volume 4 contains messages with prefixes KONCV OC. Volume 5 contains messages with prefixes ODC VEB and the appendixes. The messages within each of these volumes appear in alphanumeric order by message number. The message number begins with a prefix that identifies the product or component that generated the message. The message text appears on the same line as the message number. Following the message number and message text is one or more of the following: Explanation of the message Description of the system conditions that generated the message Suggested response to the message Description of the message type Destination for the message Preface 9

10 Severity of the message Some messages are informational only; others advise you to take an action. Message prefixes The following table lists message prefixes for the specified products or components. Product or Component Name AF/OPERATOR Alert Adapter for OG/MVS Candle Management Server CCC for MQSeries CCC for MQSeries Configuration CCC for MQSeries Integrator CCC for Sysplex Classic OMEGAMON CT/Engine DEXAN End-to-End EPILOG OMEGACENTER Gateway for MVS OMEGAMON Base OMEGAMON for VM OMEGAMON II for CICS OMEGAMON II for DB2 OMEGAMON II for IMS OMEGAMON II for Mainframe Networks OMEGAMON II for MVS OMEGAMON II for SMS IBM Tivoli OMEGAMON XE for CICS on z/os IBM Tivoli OMEGAMON XE on z/os IBM Tivoli OMEGAMON XE for IMS on z/os Prefixes AOP, KAO, KAT, KOG, OMG KAM KDS, KFAA, KLC, KLG, KLI, KLS, KMS, KO4, KQM KMQ KCF and KMC KQI KOS CSAA, IA, IN, LSCX, OM, OM0 KBB, KDC, KLE, KLU, KLV, KLX DX ETE EB, EC, ED, EI, EO, EP AOP, KAO, KAT, KOG, OMG CI, CNDL, OB, OBV, OMV CV, EU, EV, OGN, OV BG, KC2, KOCJ, OC H2C, KD2, O2 ATF, DSM, ETX, EVS, ICF, LAT, ML, MRG, OR, OS, OTR, PWA, REG, TRF EX, KON These messages are also found in IBM Tivoli OMEGAMON XE for Mainframe Networks and OMEGAMON II for Mainframe Networks: Messages. EA, KM2, KXDF, OM2, VEB KDF, KRC KCP KM5, KM3, KOS KIP 10 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

11 Product or Component Name IBM Tivoli OMEGAMON XE for Mainframe Networks IBM Tivoli OMEGAMON XE for Storage on z/os IBM Tivoli OMEGAMON XE for WebSphere MQ IBM Tivoli OMEGAMON XE for WebSphere InterChange Server IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers OMEGAVIEW Prefixes KN3 These messages are also found in IBM Tivoli OMEGAMON XE for Mainframe Networks and OMEGAMON II for Mainframe Networks: Messages. KS3 KCF, KMC KCF and KMC messages are found in Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (SC ) KMQ KMQ messages are found in Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring (SC ) KIE These messages are found in Using IBM Tivoli OMEGAMON XE for WebSphere InterChange Server (SC ). KQI These messages are now found in Using IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers (SC ) KMV, KSD Reporting Problems to IBM Software Support These problem reporting topics are covered in this section: Product problems on page 11 OMEGAMON II collector problems on page 12 Product problems Some messages suggest that you generate a system dump and forward it to IBM Software Support for more help. If your product malfunctions, do the following before you call IBM Software Support: Record the error message number and any error codes that the error message displays. Record output from the DEBUG screen space, when possible. To obtain these DEBUG screens, type DEBUG on the INFO-line and press Enter. Your product executes various screen spaces and logs important information to hardcopy. Preface 11

12 Note: For OMEGAMON II for CICS, OMEGAMON II for DB2, OMEGAMON II for DBCTL, OMEGAMON II for IMS, and OMEGAMON II for MVS, fill in the information on the hardcopy of the first debug screen (DEBUG). Gather any dumps that the product produces (on cartridge, tape, or hardcopy). You can write product dumps to one or more of the following: Products OMEGAMON II for DB2 OMEGAMON II for DBCTL OMEGAMON II for IMS OMEGAMON II for MVS OMEGAMON II for DB2 OMEGAMON II for DBCTL OMEGAMON II for IMS OMEGAMON II for MVS OMEGAMON II for SMS OMEGAMON II for VTAM OMEGAVIEW All products All products Description the Common Interface SYSABEND DD statement the O2SNAP dataset the RKLVLOG and RKLVSNAP data sets MPcc data set Be prepared to send them to IBM Software Support if a service representative requests that you to do so. You can also FTP dumps to IBM Software Support. Note: If you send a cartridge or tape, specify the format, density, and label information. Record any error messages that product writes to the system log. OMEGAMON II collector problems For the OMEGAMON II products, if the collector malfunctions, take the following actions before calling IBM Software Support: Record the error message number and any codes displayed with the error message. Record the output from the collector log. Note: Call IBM Software Support before sending in any dumps produced. IBM Software Support can accept dumps on tape, fiche, or hardcopy. Accessing terminology online The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site: 12 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

13 The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: Accessing publications online Documentation CDs for individual products or groups of products contain the publications that are in the product library. The format of the publications is PDF. Refer to the readme file on the CD for instructions on how to access the documentation. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the product name link to access the product library at the Tivoli software information center. If you print PDF documents on other than letter-sized paper, set the option in the File -> Print window that allows Adobe Reader to print letter-sized pages on your local paper. Ordering publications You can order many Tivoli publications online at the following Web site: You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, contact your software account representative to order Tivoli publications. Tivoli technical training For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Searching knowledge bases: You can search across a large collection of known problems and workarounds, Technotes, and other information. Preface 13

14 Obtaining fixes: You can locate the latest fixes that are already available for your product. Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support. For more information about these three ways of resolving problem, see Support Information on page 323. Documentation Conventions Overview This guide uses several conventions for special terms and actions, and operating system-dependent commands and paths. Abbreviations used through this book This guide uses the following abbreviations: hilev meaning high-level qualifier midlev meaning mid-level qualifier rhilev meaning runtime high-level qualifier (non-vsam) rvhilev meaning runtime high-level qualifier (VSAM) shilev meaning installation high-level qualifier thilev meaning SMP/E target high-level qualifier Panels and figures The panels and figures in this document are representations. Actual product panels may differ. Required blanks The slashed-b ( ) character in examples represents a required blank. The following example illustrates the location of two required blanks. eba*servicemonitor Revision bars Revision bars ( ) may appear in the left margin to identify new or updated material. Variables and literals In examples of z/os command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored. LOGON APPLID (cccccccc) 14 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

15 In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses. Symbols The following symbols may appear in command syntax: Table 2. Symbols in Command Syntax Symbol Usage The or symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example: YES NO In this example, YES or NO may be specified. [ ] Denotes optional arguments. Those arguments not enclosed in square brackets are required. Example: APPLDEST DEST [ALTDEST] In this example, DEST is a required argument and ALTDEST is optional. { } Some documents use braces to denote required arguments, or to group arguments for clarity. Example: COMPARE {workload} - REPORT={SUMMARY HISTOGRAM} The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM. _ Default values are underscored. Example: COPY infile outfile - [COMPRESS={YES NO}] In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES. Preface 15

16 16 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

17 1 KONCV001 KXDFC012 KONCV001 KONCV002 KONCV003 KONCV004 KONCV005 FIND REQUIRES STRING Explanation: The FIND command was entered at the VTAM Console without a character string. User Response: Enter the FIND command with a character string. Message Type: User input error. CHARACTER STRING NOT FOUND Explanation: A FIND command was entered at the VTAM Console. The console log was searched, but no matching character string was found. User Response: Verify that the correct character string was specified. Message Type: Information. LOCATE REQUIRES STRING Explanation: A LOCATE command was issued at the VTAM Console. The VTAM console log was searched, but no matching character string was located. User Response: Verify that the correct character string was specified. Message Type: Information. VTAM COMMAND ERROR Explanation: An internal error was detected while attempting to execute a VTAM console command. User Response: Verify that the OMEGAMON II console APPLID prefix specified on the Global Options panel contains the same first six characters of the applids with auth=(pass,acq,spo) in the SYS1.VTAMLST member used to define OMEGAMON II to VTAM. Message Type: Installation error. VR IS NOT ACTIVE Explanation: The VR that was selected is currently not active. Only active VRs can be selected with a / or an action code. User Response: Select an active VR. Message Type: User input error. KONCV001 KXDFC012 17

18 KONCV006 KONCV007 KONCV008 KONCV009 KONCV010 FIELD IS NOT PROMPTABLE Explanation: The prompt key (F4) was pressed when the cursor was not in a promptable field. The prompt key can only be used in fields that are accompanied by an adjacent plus (+) sign. When the input field is not promptable, you must type the requested data. User Response: Enter the requested data. Message Type: User input error. MUST BE EQ, NE, LT, LE, GT, or GE Explanation: An invalid Operator was entered in response to a View Some popup. User Response: Place the cursor in the operator field and press the prompt (F4) key to obtain a list of valid operators. Tab to the desired operator and press Enter. Message Type: User input error. MUST BE NUMERIC Explanation: A non-numeric value was entered in a field that requires a numeric value. User Response: Enter a numeric value in the field. Message Type: User input error. INVALID SELECTION Explanation: An attempt to select an item from a menu was made; the number or mnemonic that was entered is not on the menu, or the cursor is not positioned to the left of a valid selection. User Response: Retype the selection character, or place the cursor to the left of a valid selection and press Enter. Message Type: User input error. SAMPLING INTERVAL WAS TOO LONG, TRY AGAIN Explanation: The sampling interval used for calculating PIU rates is measured from one panel refresh to the next panel refresh, with 30 seconds being the maximum sample interval. The interval between presses of the Enter or F5 key exceeded 30 seconds. System Action: When the system detects that the maximum sample interval has been exceeded, it issues this message and a new sampling interval is started. Elapsed time in the interval is reset to zero. User Response: Press the Enter key any time within the next 30 seconds to display the current PIU rate. Message Type: Information. 18 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

19 KONCV011 KONCV012 KONCV013 KONCV014 KONCV015 KONCV016 KONCV017 USER COMMANDS UPDATED Explanation: The user added, changed or deleted a user VTAM command. System Action: The user commands update successfully. Message Type: Confirmation. TYPE A / NEXT TO THE DESIRED SELECTIONS Explanation: The action bar Action pulldown panel allows the user to select one or more selections by entering the / character. User Response: Type a / next to the desired selections and press Enter. Message Type: User input error. SELECTION NOT AVAILABLE Explanation: The menu selection is unavailable due to the current state of the application. User Response: Make another selection. Message Type: Warning. MUST BE Y OR N Explanation: The input field accepts only Y or N (for Yes or No). User Response: Enter Y or N in the field. Message Type: User input error. FIELD VALUE NOT VALID Explanation: The data entered in this field is not valid. User Response: Press F1 for additional help on the field. Enter a valid value. Message Type: User input error. COLLECTION INTERVAL TIMEOUT; DATA REINITIALIZED Explanation: The interval between data requests cannot exceed 5 minutes. System Action: A new collection interval is initiated, and all current values are reset to zero. Message Type: Information. INTERNAL MVS COUNTER WRAPPED; DATA REINITIALIZED Explanation: A reset condition has been detected for an MVS internal counter. System Action: A new collection interval is initiated, and all current values are reset to zero. Message Type: Information. KONCV001 KXDFC012 19

20 KONCV018 KONCV019 KONCV020 KONCV021 KONCV022 KONCV023 WRAP DETECTED IN SIO COUNTER; DATA REINITIALIZED Explanation: A reset condition has been detected for a VTAM SIO counter. System Action: A new collection interval is initiated, and all current values are reset to zero. Message Type: Information. WRAP DETECTED IN SYSSIO COUNTER; DATA REINITIALIZED Explanation: A reset condition has been detected for the MVS SIO counter. System Action: A new collection interval is initiated, and all current values are reset to zero. Message Type: Information. WRAP DETECTED IN PAGING COUNTER; DATA REINITIALIZED Explanation: A reset condition has been detected for the MVS paging counter. System Action: A new collection interval is initiated, and all current values are reset to zero. Message Type: Information. AUTHORIZATION REQUIRED Explanation: The user tried to perform a function that requires authority. User Response: Contact the system administrator to have your user authorities updated. When your user authorities are updated by the administrator, log off and logon, and retry the operation. Message Type: Security. COMMAND REQUIRES ADDITIONAL OPERAND Explanation: A command that requires one or more operands was entered on the command line. User Response: Place the cursor on the command line and enter Help followed by the command attempted. A help pop-up appears describing the command. Re-enter the command with the appropriate operands. Message Type: User input error. VARIABLE NAMED varname CONTAINS contents_of_varname Explanation: A user with administrator authority issued the SHOW variable command. System Action: Displays the current contents of the variable. Severity: Information. 20 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

21 KONCV024 KONCV025 KONCV026 KONCV027 KONCV028 KONCV029 DIALOG ERROR Explanation: A user with administrator authority issued the DIALOG dlgname command, but the dialog specified does not exist or contains errors and could not be compiled and executed successfully. User Response: Edit and refresh the dialog, then retry the operation. Message Type: Internal error. REQUEST SUCCESSFUL Explanation: A user entered a command on the command line. System Action: The command executes successfully. Message Type: Confirmation. INVALID COMMAND Explanation: A user entered an invalid command on the command line. User Response: Place the cursor on the command line and press F1 to view the help panel that lists valid commands. Message Type: User input error. function_key KEY IS NOT ACTIVE Explanation: A function key was pressed that is not supported on the current panel. The available function keys are listed in the function key area at the bottom of each panel. User Response: Use a valid function key. Message Type: User input error. INVALID SELECTION Explanation: A selection character, an action code, or a mnemonic was entered which is not listed on the menu. User Response: Enter one of the listed choices. Message Type: User input error. HELP PANEL help_dialog MISSING OR SYNTAX ERROR Explanation: The user has requested a help panel that is either missing or contains errors preventing it from displaying. User Response: Gather any logs or dumps produced and report the missing panels to IBM Software Support. Message Type: Information. KONCV001 KXDFC012 21

22 KONCV030 KONCV031 KONCV032 KONCV033 KONCV034 KONCV035 KONCV036 SELECT THE ACTIONS PULL-DOWN MENU Explanation: One or more / selection characters have been entered, but no actions have been selected from the Actions pulldown menu. User Response: Select the Actions pulldown from the action bar, then select the desired actions from the pulldown. Message Type: User input error. NOTEPAD UPDATED Explanation: The user added, changed or deleted personal notes using the command line NOTE command. System Action: The user notepad updates successfully. Message Type: Confirmation. NOTEPAD CLEARED Explanation: The user requested a notepad to be cleared while using the command line NOTE command. System Action: The user notepad clears successfully. Message Type: Confirmation. THRESHOLD CRITERIA UPDATED Explanation: The user entered exception thresholds and pressed Enter. System Action: Thresholds are successfully updated and become effective within a few minutes. Message Type: Confirmation. RESOURCE(S) ADDED Explanation: A response time, terminal, or group was added. System Action: The response time, terminal, or group is added to ETE response time monitoring. Message Type: Confirmation. FIELD IS REQUIRED Explanation: The input field cannot contain blanks. User Response: Enter the appropriate data. Message Type: User input error. FIRST CHARACTER MUST BE ALPHA Explanation: The first character of the input field must begin with an alphabetic character. User Response: Enter the appropriate data. Message Type: User input error. 22 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

23 KONCV037 KONCV038 KONCV039 KONCV040 KONCV041 KONCV042 GLOBAL OPTIONS UPDATED Explanation: A user with administrator authority pressed Enter while viewing the Global Options panel. System Action: The Global options are updated. Message Type: Confirmation. INVALID NUMERIC RANGE Explanation: The input field requires a number within a specified range. User Response: Enter a number within the valid range. Message Type: User input error. THRESHOLD UPDATE FAILED Explanation: An internal error was detected while attempting to change exception thresholds. User Response: Retry the operation. If the problem persists, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. GLOBAL OPTIONS UPDATE FAILED Explanation: An internal error was detected while attempting to update the Global Options. User Response: Retry the operation. If the problem persists, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. VR NUMBER INVALID Explanation: An invalid virtual route number was specified. User Response: Specify a valid VR number. Message Type: User input error. TP NUMBER INVALID Explanation: An invalid TP number was specified. User Response: Specify a valid TP number. Message Type: User input error. KONCV001 KXDFC012 23

24 KONCV043 KONCV044 KONCV045 KONCV046 ETE INTERFACE DISABLED Explanation: The ETE response time monitor component is currently disabled. This is the initial default when the product is installed. The ETE feature must be specifically enabled after first verifying that system incompatibilities do not exist. System Action: All ETE response time monitor functions are disabled. User Response: Refer to the OMEGAMON II for Mainframe Networks instructions shipped with the product, the Configuring OMEGAMON II for Mainframe Networks manual, and the End-to-End Response Time Feature Reference Manual for information about installing and activating the ETE response time component. Message Type: Installation error. THE OPERAND FOR THE AUTOREFRESH COMMAND MUST BE ON, OFF, OR A NUMERIC VALUE FROM SECONDS Explanation: The AUTOREFRESH command was entered on the command line without specifying a valid operand. User Response: Enter the AUTOREFRESH command in one of the following formats: AUTO ON AUTO OFF AUTO nnnn where nnnn is 10 to 3600 seconds. Message Type: User input error. MUST BE IN THE RANGE OF MINUTES Explanation: An invalid value was specified for the recording interval on the Global Options panel. User Response: Specify a number within the valid range ( minutes). Message Type: User input error. THE SAS SOURCE LIBRARY SPECIFIED CANNOT BE LOCATED. THE DATASET MAY HAVE BEEN DELETED, RENAMED OR UNCATALOGED. Explanation: The SAS source library name specified on the historical graph options panel cannot be located. User Response: Verify the SAS macro library name specified is valid. Message Type: User input error. 24 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

25 KONCV047 KONCV048 KONCV049 KONCV050 KONCV051 THE SAS CLIST WAS NOT ENTERED IN THE CORRECT FORMAT. PLEASE USE THE FOLLOWING FORMAT: CANDLE.ON.V500.SASCNTL(KONCLST6) Explanation: The SAS clist and member name specified on the historical graphs options panel was entered in the wrong format. User Response: Enter the SAS clist name and member name in the following format: filename(membername) Message Type: User input error. THE SAS CLIST DATASET NAME SPECIFIED CANNOT BE LOCATED. THE DATASET MAY HAVE BEEN DELETED, RENAMED OR UNCATALOGED. Explanation: The SAS CLIST dataset name specified on the historical graph options panel cannot be located. User Response: Verify that the SAS CLIST library name specified is valid and that the library name is cataloged. Message Type: User input error. THE SAS CLIST MEMBER NAME SPECIFIED CANNOT BE LOCATED. THE MEMBER MAY HAVE BEEN DELETED OR RENAMED. Explanation: The SAS CLIST member name specified on the historical graphs options panel cannot be located. User Response: Verify that the specified member exists. Message Type: User input error. THE USAGE SELECTION IS ONLY VALID FOR THE IO00 AND CRPL BUFFER POOLS Explanation: The user requested the U (usage) action while accessing a buffer pool panel. The U action is only valid for the IO00 and the CRPL buffer pools. User Response: Use the U action only for IO00 and CRPL buffer pools. Message Type: User input error. ACTION IS ONLY VALID ON A SUBAREA Explanation: The user entered an L (list) action code next to a virtual route number while working with the Virtual Route Monitor List. The L action code is only valid next to a subarea. User Response: Do not enter the L action code next to a VR. Message Type: User input error. KONCV001 KXDFC012 25

26 KONCV052 KONCV053 KONCV054 KONCV055 KONCV056 KONCV057 MONITORING STARTED Explanation: The user requested monitoring of a subarea and/or VRs while working with the Virtual Route Monitor List. System Action: The specified subarea/vrs are monitored. Message Type: Confirmation. MONITORING STOPPED Explanation: The user requested to stop monitoring a subarea and/or VRs while working with the Virtual Route Monitor List. System Action: The specified subarea/vrs are not monitored. Message Type: Confirmation. MONITORING THRESHOLDS CHANGED Explanation: The user requested monitoring of a subarea and/or VRs and specified exception thresholds values while working with the Virtual Route Monitor List. System Action: The specified subarea/vr exception thresholds are changed. Message Type: Confirmation. MONITORING THRESHOLDS DELETED Explanation: The user entered a D action code next to a subarea/vr that appears undefined while working with the Virtual Route Monitor List. System Action: The subarea/vr is removed from the list. Message Type: Confirmation. SUBAREA/VIRTUAL ROUTE UNDEFINED Explanation: The user tried to start monitoring a subarea/vr that is no longer defined to VTAM while using the Virtual Route Monitor List. User Response: Check with your system network configuration staff. It is likely that VTAM tables were reconfigured, making certain subarea/vrs invalid. Use the D action code to delete the definitions for undefined subareas/vrs. Message Type: User input error. ONLY ALLOWED TO DELETE UNDEFINED ITEMS Explanation: The user tried to enter the D action code next to a subarea/vr while using the Virtual Route Monitor List. User Response: The D action code is only valid next to UNDEFINED subarea/vrs. Message Type: User input error. 26 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

27 KONCV058 KONCV059 KONCV060 KONCV061 KONCV062 KONCV063 KONCV064 MONITOR OPTIONS UPDATE ERROR Explanation: An internal error was detected while attempting to update the Virtual Route Monitor List. System Action: Detailed message written to job log. User Response: Retry the operation. If the error persists, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. MONITOR OPTIONS UPDATED Explanation: The user pressed Enter while viewing Monitor Options for buffer pools, CTC, LOCALS, NCP, response time or virtual routes. System Action: The specified monitoring options are updated. Message Type: Confirmation. TERMINAL OPTIONS UPDATED Explanation: The user pressed Enter while viewing the Terminal Options panel. System Action: The terminal options are updated. Message Type: Confirmation. AUTOREFRESH OPTIONS UPDATED Explanation: The user pressed Enter when viewing the Autorefresh Options panel. System Action: The autorefresh options are updated. Message Type: Confirmation. STATUS BAR OPTIONS UPDATED Explanation: The user pressed Enter when viewing the Status Bar Options panel. System Action: The status bar options are updated. Message Type: Confirmation. NETWORK MANAGER OPTIONS UPDATED Explanation: The user pressed Enter when viewing the Network Manager Options panel. System Action: The network manager options are updated. Message Type: Confirmation. HISTORICAL GRAPH OPTIONS UPDATED Explanation: The user pressed Enter when viewing the historical graph options panel. System Action: The historical graph options are updated. Message Type: Confirmation. KONCV001 KXDFC012 27

28 KONCV065 KONCV066 KONCV067 KONCV068 KONCV069 KONCV070 KONCV071 SMF DEFINITION ADDED Explanation: The user added a response time SMF definition. System Action: The SMF definition is added. Message Type: Confirmation. SMF DEFINITION CHANGED Explanation: The user changed a response time SMF definition. System Action: The SMF definition is changed. Message Type: Confirmation. SMF DEFINITION DELETED Explanation: The user deleted a response time SMF definition. System Action: The SMF definition is deleted. Message Type: Confirmation. RESPONSE TIME MUST BE GREATER THEN PREVIOUS RANGE Explanation: When adding or changing a response time SMF definition, the values specified in the upper bound range fields conflicted. The range 2 upper bound must be greater then range 1. Range 3 must be greater then Range 2. Range 4 must be greater then Range 3. User Response: Enter correct values for upper bounds in each range. Message Type: User input error. THIS SMF DEFINITION ALREADY EXISTS Explanation: When adding a response time SMF definition, the user specified a terminal or group name that is already defined. User Response: The terminal or group name cannot conflict with any other existing response time SMF definition. Message Type: User input error. USERID ALREADY EXISTS Explanation: The userid specified when adding a new user authority already exists. User Response: Use the C (change) action or correct the userid and retry. Message Type: User input error. USER AUTHORITY ADDED Explanation: An administrator added a new user authority. System Action: The user authorities are updated and take effect the next time the user logs onto OMEGAMON II. Message Type: Confirmation. 28 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

29 KONCV072 KONCV073 KONCV074 KONCV075 KONCV078 KONCV079 USER AUTHORITY CHANGED Explanation: An administrator changed an existing user s.s authorities. System Action: The user s authorities are updated and take effect the next time the user logs onto OMEGAMON II. Message Type: Confirmation. USER AUTHORITY DELETED Explanation: An administrator deleted an existing user s authorities. System Action: The authorities will be set to the $DEFAULT userid definitions the next time the deleted user logs on. Message Type: Confirmation. AT LEAST 1 ADMINISTRATOR IS REQUIRED Explanation: An administrator attempted to delete the only user with administrator authority. User Response: Transfer administrator authority to another user before deleting the desired user. Message Type: Warning. NOT ALLOWED TO DELETE THE ONLY ADMINISTRATOR Explanation: An administrator attempted to delete the only user with administrator authority. User Response: Transfer administrator authority to another user before deleting the desired user. Message Type: Warning. SAS GRAPH PRINTED Explanation: The user entered the P action code next to one of the SAS graphs while using the historical graph component. System Action: The SAS graph is routed for printing. Message Type: Confirmation. SAS GRAPHS PRINTED Explanation: The user entered the P action code next to two or more SAS graphs while using the historical graph component. System Action: The SAS graphs are routed for printing. Message Type: Confirmation. KONCV001 KXDFC012 29

30 KONCV080 KONCV081 KONCV082 KONCV083 KONCV084 KONCV085 KONCV086 NAVIGATION NOT ALLOWED Explanation: The user attempted to navigate to a panel that is already active in the stack. As navigation takes place from the Status Display panel, the display panels are stacked so that as you press F12, you can return up the stack. User Response: Choose another selection or press F12 until you return to the panel you wish to view. Message Type: Information. NEW RACHSRT PARAMETER IS NOT PRIME Explanation: When using the SRT modeling, a number was entered that is not prime. Message Type: Information. LIGHT PEN IS NOT SUPPORTED Explanation: The user attempted to use a terminal light pen. User Response: Do not use a light pen with OMEGAMON II. Message Type: User input error. TRACE ALREADY ACTIVE OR COMPLETED Explanation: The user attempted to start a VTAM trace that is either already started or has already completed. User Response: Add and start a new trace. Message Type: User input error. TRACE IS STILL ACTIVE Explanation: The user attempted to save a VTAM trace that is either active or wrapping. User Response: Traces that are either ended or manually stopped can be saved. Message Type: User input error. TRACE IS ALREADY SAVED Explanation: The user attempted to save a trace that has already been saved. Message Type: User input error. TRACE WAS NEVER STARTED Explanation: The user attempted to save a trace that was never started. User Response: Start the trace and let it complete before attempting to save it. Message Type: User input error. 30 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

31 KONCV087 KONCV088 KONCV089 KONCV090 KONCV091 KONCV092 KONCV093 TRACE IS NOT ACTIVE Explanation: The user attempted to stop a trace that was never started. User Response: The stop action is only valid for active or wrapped traces. Message Type: User input error. NUMBER EXCEEDS SYSTEM MAX OF nnnnnnn Explanation: The number of PIUs requested exceeds the maximum allowed which is set by the administrator on the Global Options panel. User Response: Specify a number less then or equal to the allowed maximum. Message Type: User input error. CLOSE FAILED FOR SYSOUT DATASET Explanation: An internal error was detected while attempting to close the screen print log and route it for printing. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. nn SCREEN(S) ROUTED FOR PRINTING Explanation: The user closed the screen print log. System Action: The captured screen prints are routed for printing. Message Type: Confirmation. NO SCREEN PRINTS WERE REQUESTED Explanation: The user closed the screen print log, but there were no screens captured. User Response: Use the F11 key to capture screens before closing the screen print log. Message Type: Information. GET FAILED FOR DEFAULT PRINTER OPTIONS Explanation: An internal error was detected while closing the screen print log. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. CREATE FAILED FOR SCREEN PRINT LOG Explanation: An internal error was detected while closing the screen print log. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 31

32 KONCV094 KONCV095 KONCV096 KONCV097 KONCV098 KONCV099 KONCV100 ALLOCATE FAILED FOR SYSOUT DATASET Explanation: An internal error was detected while closing the screen print log. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. ADD FAILED FOR SCREEN PRINT LOG Explanation: An internal error was detected while closing the screen print log. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. OPEN FAILED FOR SYSOUT DATASET Explanation: An internal error was detected while closing the screen print log. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. PUT FAILED FOR SYSOUT DATASET Explanation: An internal error was detected while closing the screen print log. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem continues, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. VTAM TRACE ROUTED FOR PRINTING Explanation: The user requested a VTAM trace report. System Action: The VTAM trace is routed for printing. Message Type: Confirmation. YOU CAN ONLY PRINT ENDED, STOPPED, OR SAVED TRACES Explanation: The user requested a VTAM trace report. User Response: Make sure the trace is ended, stopped, or saved before attempting to print. Message Type: User input error. THERE IS NO TRACE DATA TO PRINT Explanation: The user requested a VTAM trace report on a trace that did not capture any PIUs. User Response: Rerun the trace, then retry the print operation. Message Type: User input error. 32 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

33 KONCV101 KONCV102 KONCV103 KONCV104 KONCV105 KONCV106 PRINTER OPTIONS UPDATED Explanation: The user pressed Enter while viewing the Printer \Options panel. System Action: The printer options are updated. Message Type: Confirmation. ERROR, SEE VIEWLOG Explanation: An internal error was detected while OMEGAMON II was attempting to refresh the Status Display panel. System Action: OMEGAMON II detected an unexpected error. User Response: If the message persists, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. TRACE ABENDED, DATA STILL GOOD Explanation: An internal error was detected while a VTAM trace was in progress. System Action: A dump is generated. User Response: Gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. LU NOT FOUND Explanation: The LU specified was not found while attempting to start a VTAM trace. User Response: Enter a valid LU name to trace. Message Type: User input error. ENTER A NUMBER, THEN PRESS F2 Explanation: The user pressed the F2 key before entering a non-zero RACHSRT parameter while using the SRT modeling feature. User Response: Specify a numeric RACHSRT parameter before pressing the F2 key. Message Type: User input error. THE EXCEPTIONS SELECTION IS NOT VALID FOR THIS COMPONENT Explanation: Exceptions do not apply to the selected component. Only the Show Details action applies. User Response: Enter the S action code to Show Details of this component. Message Type: User input error. KONCV001 KXDFC012 33

34 KONCV107 KONCV108 KONCV109 KONCV110 KONCV111 ETE STARTED TASK IS NOT AVAILABLE Explanation: OMEGAMON II has detected that the ETE Response Time feature is currently not available to collect response time or VTAM trace data. User Response: Report the problem to your data center. Message Type: Internal error. VTAM TRACE ERROR (SENSE CODE=sense_code) Explanation: OMEGAMON II has detected that the ETE Response Time feature is currently not available to collect response time or VTAM trace data. System Action: Detailed message written to job log. User Response: Retry the operation. If the problem persists, gather any logs or dumps produced and contact IBM Software Support. Message Type: Internal error. THE FOLLOWING ERROR OCCURRED WHEN OMEGAMON ATTEMPTED TO ACCESS THE SPECIFIED SAS PRINT OPTIONS LIBRARY. [RETURN CODE=return_code nn SYSTEM CODE=X xxxx USER CODE=X xxxxxxxx ] Explanation: When OMEGAMON II attempted to store the new historical graph print options in the SAS Print Options Library partitioned dataset, an error was detected. User Response: Research the Return Code, System Code, or User Code displayed to determine the cause of the error. A possible cause is that OMEGAMON II has not been given write access by the external security system (such as CA-ACF2 or RACF ). Message Type: Internal error. USE THE R ACTION CODE TO START MONITORING Explanation: The user attempted to change monitoring for a subarea or virtual route that was not started. User Response: Use the R action code to start monitoring for a subarea or a specific virtual route. Message Type: User input error. TREND/EXCEPTION LOG FILE ACCESS ERROR Explanation: OMEGAMON II was unable to access the Trend/Exception Log VSAM file. User Response: Report the problem to your OMEGAMON II for Mainframe Networks product administrator. The KONINVSM member in the RKANPAR dataset must contain the correct name of the Trend/Exception Log VSAM dataset. Browse the sysout for OMEGAMON II for Mainframe Networks. A detailed explanation of the type of error encountered is listed there. Message Type: Installation error. 34 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

35 KONCV112 REQUESTED PIU WAS NOT FOUND Explanation: A VTAM Trace browse request was issued. The requested PIU was not found. User Response: In most cases, there is nothing wrong. The message indicates the browse request could not find the specified PIU. You also receive this message if the browse request is not valid. For example: you requested an invalid PIU number; you requested a find for a hexadecimal or character string that does not exist; or you requested the search string PIU when a search string was never specified in the trace definition. Message Type: Warning. KONCV115 THE HISTORICAL GRAPH OPTIONS LOCATED ON THE ACTION BAR OPTIONS PULLDOWN PANEL ARE NOT VALID. PLEASE UPDATE HISTORICAL GRAPH OPTIONS BEFORE ATTEMPTING TO ACCESS HISTORICAL GRAPHS. Explanation: The user attempted to access historical graphs, but the historical graphs options are not valid. User Response: Update the historical graph options from the action bar options pulldown panel, then retry the operation. Message Type: Information. KONCV116 AN UNEXPECTED ERROR OCCURRED Explanation: When OMEGAMON II attempted to process a user request, an unexpected error occurred. User Response: First check to see if the Tables Database ran out of space. If that is not the problem, retry the operation. If the problem persists, look at OMEGAMON II's SYSOUT or message log, note the CT/Engine table services return code, and report the problem to IBM Software Support. Message Type: Internal error. KONCV117 VALID RANGE IS Explanation: The sampling interval must be in the range of seconds. User Response: Specify a value that is not less than 20 and not greater than 300. Message Type: User input error. KONCV118 ENTER N, L, S, OR B Explanation: The only acceptable characters to specify in this field are N (None), L (Log), S (SMF), or B (Both). User Response: Specify an N for no recording, an L for Log File recording, an S for SMF recording, or a B for both Log File and SMF recording. Message Type: User input error. KONCV001 KXDFC012 35

36 KONCV119 KONCV120 KONCV121 KONCV122 KONCV123 KONCV124 ENTER YES OR NO Explanation: This input field requires a value of Yes or No. User Response: Specify Yes to activate the option or No to deactivate the option. Message Type: User input error. ENTER C OR W Explanation: The only acceptable characters in this field are W or C. User Response: Specify a W to indicate that the exception should have warning (yellow) severity, or a C to indicate that the exception should have critical (red) severity. Message Type: User input error. ENTER A NUMERIC VALUE OR LEAVE BLANK Explanation: This field requires a numeric value or no value. User Response: When you want OMEGAMON II to monitor for this exception, specify the numeric threshold that must be reached for an exception condition to be generated. Leave this field blank if you do not want OMEGAMON II to monitor for this exception. Message Type: User input error. CRITICAL MUST BE GREATER THAN WARNING Explanation: The critical threshold specified must have a value that exceeds the warning value specified. User Response: Raise the critical threshold and/or lower the warning threshold. Message Type: User input error. ENTER N, L, OR A Explanation: The only acceptable characters in this field are N (None), L (Monitor List), or A (All). User Response: Specify an N for no monitoring of virtual routes, an L to monitor only the VRs in the monitor list, or an A to monitor all VRs. Message Type: User input error. CRITICAL MUST BE LESS THAN WARNING Explanation: The critical threshold specified must have a value that is less than the warning value specified. User Response: Lower the critical threshold and/or raise the warning threshold. Message Type: User input error. 36 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

37 KONCV125 THE CATEGORIES SELECTION IS ONLY VALID FOR THE IO00 BUFFER POOL Explanation: When accessing a buffer pool display, the G (Categories) action was requested. User Response: The G action code is only valid for the IO00 buffer pool. Choose one of the other action codes listed. Message Type: User input error. KONCV126 THE DATA FOR THE table tablename IS NOT AVAILABLE IN THIS DOMAIN. Explanation: The PLU is a cross-domain resource (CDRSC) and the COSTAB resides in the other domain, or the SLU is a CDRSC and the USSTAB resides in the other domain. The name of the COSTAB displays, but the name of the USSTAB is unavailable. The requested table is available in the other domain. User Response: Press Enter to continue. To view the table, log onto the OMEGAMON II that monitors the other domain. Message Type: Information. KONCV127 VALID RANGE IS Explanation: The entry field requires a percentage and the value is out of range. User Response: Specify a number that is not less than zero and is not greater than 100. Message Type: User input error. KONCV128 VALID RANGE IS Explanation: The trend recording interval must be in the range of minutes. User Response: Specify a number that is not less than 15 and is not greater than 360. Message Type: User input error. KONCV129 VALID RANGE IS Explanation: The number of hours of trend or exception records to display must be User Response: Specify a number that is not less than 1 and is not greater than 120. Message Type: User input error. KONCV001 KXDFC012 37

38 KONCV130 VALID RANGE IS Explanation: The SMF record number to be generated must be in the range User Response: Specify a number that is not less than 128 and is not greater than 255. Message Type: User input error. KONCV131 VALID RANGE IS Explanation: The maximum number of PIUs to be retained for one trace must be in the range User Response: Specify a number that is not less than 1 and is not greater than 500. Message Type: User input error. KONCV132 KONCV133 KONCV134 ALPHANUMERIC FIELD REQUIRED Explanation: The field must consist only of alphabetic and numeric characters, and the first character must be alphabetic. User Response: Enter only alphabetic and numeric characters (A Z, 0 9) and start with an alphabetic character. Message Type: User input error. VIEW COMMAND INVALID WHEN DISPLAYING DIRECTORY Explanation: Since the VIEW command displays the Snapshot Directory, it is invalid to enter the VIEW command while the Snapshot Directory is displayed. User Response: The Snapshot Directory displays all the snapshots you have saved. Enter action code S (Show Snapshot) next to the snapshot you want to view. Message Type: User input error. ENTER N OR S Explanation: The only acceptable characters to specify in this field are N or S. User Response: Specify an N for no response time trend recording or an S for response time trend recording to SMF. Message Type: User input error. KONCV135 VALID RANGE IS 1 99 Explanation: The response time definite response frequency must be in the range User Response: Specify a number that is not less than 1 and is not greater than 99. Message Type: User input error. 38 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

39 KONCV136 VALID RANGE IS Explanation: The automatic screen refresh interval must be in the range of seconds. User Response: Specify a number that is not less than 10 and is not greater than Message Type: User input error. KONCV137 KONCV138 KONCV139 KONCV140 KONCV141 THE CONTROL BLOCK CANNOT BE ACCESSED FOR ONE OF THE FOLLOWING REASONS: 1. THE CONTROL BLOCK IS NO LONGER VALID. 2. AN ATTEMPT TO ACCESS THE ADDRESS SPACE FAILED Explanation: The control block is not available for display because the control block address is no longer valid, or an attempt to swap in the address space failed. User Response: Press Enter to continue. Message Type: Information. THE ADDRESS SPACE HAS TERMINATED Explanation: The control block data is not available for display because the address space is gone. User Response: Press Enter to continue. Message Type: Information. THE ADDRESS SPACE IS BEING SWAPPED IN, TRY AGAIN LATER Explanation: The control block data is not available for display because the address space is being swapped in. User Response: Press Enter to continue. Try to access the data at a later time, after the address space has been swapped in. Message Type: Information. THERE WAS NO RPL CONTROL BLOCK FOUND FOR THIS SESSION Explanation: Due to the transient nature of control blocks, an RPL with a CID matching this session's CID could not be found. The data cannot be displayed. User Response: Press Enter to continue. Message Type: Information. UNABLE TO DISPLAY THE CONTROL BLOCK DATA. CHECK THE MESSAGE LOG FOR MORE INFORMATION Explanation: An error occurred while trying to display the requested data User Response: Press Enter to continue. Note the OMEGAMON II collector's return and sense codes, on the message log or OMEGAMON II's SYSOUT, and report them to IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 39

40 KONCV142 KONCV143 KONCV144 KONCV145 KONCV147 UNABLE TO FIND THE ACTUAL RPL. THE CRPL IS DISPLAYED INSTEAD. MOST OF THE DATA FROM THE ORIGINAL RPL CAN BE FOUND IN THE CRPL Explanation: The actual RPL was not available. The CRPL is shown instead. The CRPL contains most of the data from the original RPL. User Response: Press Enter to continue. Message Type: Information. THE LOGMODE ENTRY FOR MODETAB tablename CANNOT BE DETERMINED AT THIS TIME. Explanation: The LOGMODE entry was not found in the MODETAB. The LOGMODE entry was in an undetermined state at the time the request was made. It is possible that the MODETAB was being dynamically refreshed or the session was in a transitional state such as initiation or termination. User Response: Press Enter to continue. Try again later; a change in state may synchronize the names. Message Type: Information. THE DATA FOR THE LOGMODE ENTRY entryname IS NOT AVAILABLE IN THIS DOMAIN. Explanation: The PLU is a cross-domain resource (CDRSC) and the LOGMODE entry resides in the other domain. The name of the LOGMODE entry displays. The MODETAB is available in the domain in which the PLU resides. User Response: Press Enter to continue. To view the table, log onto the OMEGAMON II that monitors the other domain where the PLU resides. Message Type: Information. TUNING STATISTICS ARE NOT ACTIVE Explanation: Tuning statistics are not currently active. If the VTAM command F procname, NOTNSTAT was issued, VTAM stops recording tuning statistics, OMEGAMON II for Mainframe Networks stops generating trend records for CTC, NCP, and local devices and sets the three TNSTATS status lights on the Mains Status panel to turquoise with text displaying NOTNSTAT. User Response: You can reactivate TNSTATS by entering the appropriate VTAM command: F procname,tnstats Message Type: Information. TRACE ALREADY EXISTS Explanation: The trace ID requested is already in use. User Response: Specify a unique trace ID, or if you want to restart the existing trace, use the R (Restart) action code. Message Type: Information. 40 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

41 KONCV148 KONCV149 KONCV150 KONCV151 KONCV152 KONCV153 TRACE NOT STARTED Explanation: The selected trace was not started. Message Type: Information. NOT VALID FOR GROUPS. USE LIST (L) AND SELECT AN INDIVIDUAL RESOURCE. Explanation: User requested resource analysis for a group item in response time analysis. User Response: Select only listed terminals or applids. Message Type: User input error. RESOURCE NOT FOUND Explanation: User requested resource analysis for a resource that could not be found. When adding a response time definition for a line, user specified a non-sdlc line. Only a SDLC line can be specified as a response time monitoring line group. User Response: Verify resource name or network address through the VTAM applications feature of OMEGAMON II for Mainframe Networks. When adding a response time line group definition, specify an SDLC line in the Group Name field. Message Type: User input error. RESOURCE NOT ACTIVE Explanation: User requested resource analysis for a resource that was not active. Message Type: Information. INVALID RESOURCE TYPE Explanation: User requested resource analysis for an invalid resource type; not an applid, terminal, or CDRSC. User Response: Enter a valid resource name. Message Type: User input error. INVALID PARAMETER LENGTH Explanation: The parameter input by the user was too long for the type of field required. User Response: Reenter the parameter. Message Type: User input error. KONCV001 KXDFC012 41

42 KONCV154 KONCV155 KONCV156 KONCV157 KONCV158 SPECIFY EITHER RESOURCE NAME OR NETWORK ADDRESS Explanation: User entered both a resource name and a network address. User Response: Specify either a resource name or network address, not both. Message Type: User input error. RPL DATA IS ONLY AVAILABLE FOR APPLID RESOURCES Explanation: User requested a display of RPL data from terminal or CDRSC type resources. RPL data is available only from applid type resources. Message Type: User input error. RESOURCE HAS NO SESSIONS Explanation: User has requested session information for a resource that currently is not in session. Message Type: None. Message Type: Information. THE VTAM REPLACEABLE CONSTANTS MODULE ISTRACON IS NOT USED BY THIS RELEASE OF VTAM Explanation: The VTAM constants function was selected, however the VTAM replaceable constants module ISTRACON is not used by this release of VTAM. Message Type: Information. THE FOLLOWING ERROR OCCURRED WHEN OMEGAMON ATTEMPTED TO VERIFY THE SPECIFIED SAS CLIST LIBRARY. RETURN CODE=return_code SYSTEM CODE=X xxxx USER CODE=X xxxxxxxx Explanation: An unexpected error was encountered when OMEGAMON II for Mainframe Networks was verifying the user-specified SAS CLIST library. User Response: Research the error return code displayed to determine the cause of the problem. See the IBM TSO System Programming Command Reference manual for more information. Message Type: User error. KONCV159 VALUE MUST BE LESS THAN Explanation: The data entered in this field exceeded User Response: Press F1 for additional help on the field, and enter an acceptable value. Message Type: User input error. 42 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

43 KONCV160 KONCV161 KONCV162 KONCV163 KONCV164 KONCV165 STORAGE REQUIRED FOR MODELLING NOT AVAILABLE. ENSURE THAT LIMIT(23,X) IS CODED FOR THE STARTUP PARAMETER. Explanation: Storage required for SRT modeling is not available from the existing storage pool. This storage requirement is temporary and equals 4 times the new RACHSRT parameter in panel KONDENM, plus 8. Typically, this problem is due to the storage request exceeding the largest storage block allowed for this job. User Response: Ensure that LIMIT(23,X) is coded for the start-up parameter in member KONSYSIN of the RKANPAR dataset. If the problem persists, you may need to increase your MAXIMUM(,X) definition. Use command STORAGE D to display and analyze your storage allocations. Message Type: Probable user error. ENTER N, L, P, OR U Explanation: The only acceptable characters to specify in this field are N (NCPs), L (lines), P (PUs), and U (LUs). User Response: Enter a valid selection. Message Type: User input error. ENTER M OR C Explanation: The only acceptable characters to specify in this field are M (monitor) and C (collect). User Response: Enter M or C in the field. Message Type: User input error. ENTER S, M, H Explanation: The only acceptable characters to specify in this field are S (seconds), M (minutes), and H (hours). User Response: Enter an S, M, or H in the field. Message Type: User input error. INVALID LINE TYPE; PRESS F4 FOR PROMPT. Explanation: The input field accepts only the following line type defaults SDLC, TRPL, TRLL, and NONE. User Response: Enter a valid line type, or press F4 for a prompt list. Message Type: User input error. ENTER L, P, OR U Explanation: The only acceptable characters to specify in this field are L (lines), P (PUs), and U (LUs). User Response: Enter L, P, or U in the field. Message Type: User input error. KONCV001 KXDFC012 43

44 KONCV166 KONCV167 KONCV168 KONCV169 KONCV170 KONCV171 ENTER P OR U Explanation: The only acceptable characters to specify in this field are P (PUs) and U (LUs). User Response: Enter P or U in the field. Message Type: User input error. RESOURCES MUST BE THE SAME TYPE Explanation: Two different resource types were selected for a mark-and-copy operation. Only matching resources can be copied. User Response: Select only matching resource types for Mark and Copy actions. Message Type: User input error. SELECT ONLY ONE RESOURCE WITH MARK Explanation: More than one resource was selected with the Mark action code. Only one Mark and one Copy action code are allowed per operation. User Response: Select one resource to be marked as the source and one matching type resource as the copy target. Message Type: User input error. SELECT ONLY ONE RESOURCE WITH COPY Explanation: More than one resource was selected with the Copy action code. Only one Mark and one Copy action code are allowed per operation. User Response: Select one resource to be marked as the source, and one matching type resource as the copy target. Message Type: User input error. SELECT A SOURCE RESOURCE WITH MARK Explanation: A Copy action was selected without a corresponding Mark action code. User Response: Use the Mark action code to select the source resource to be copied. Message Type: User input error. SELECT A TARGET RESOURCE WITH COPY Explanation: A Mark action was selected without a corresponding Copy action code. User Response: Use the Copy action code to select the target resource to be copied to. Message Type: User input error. 44 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

45 KONCV172 KONCV173 KONCV174 KONCV175 KONCV176 KONCV177 RESOURCE HAS NO SUBORDINATE RESOURCES Explanation: A List action was selected for a resource that has no subordinate resources. User Response: Check to be sure the action was entered next to the correct resource. Message Type: Information. RESOURCE HAS ALREADY BEEN STARTED Explanation: A Start action was requested for a resource that was already started. User Response: Check to be sure the action was entered next to the correct resource. Message Type: Information. RESOURCE HAS NPACOLL=NO AND CANNOT BE MONITORED Explanation: A Start action was requested for a resource that has the NPACOLL parameter set to NO in the NCP generation source. Data cannot be collected for this resource. User Response: Only resources with NPACOLL=YES can be monitored. If you want to monitor this resource, reset the NPACOLL parameter. Message Type: Information. RESOURCE IS NOT ACTIVE TO VTAM AND CANNOT BE MONITORED Explanation: A Start action was requested for a resource that is not active in this system's VTAM. Inactive resources cannot be monitored. User Response: If you want to monitor this resource, activate the resource under VTAM. Message Type: Information. RESOURCE NOT STARTED OR WAS ALREADY STOPPED Explanation: A Stop action was requested for a resource that is not active or was already stopped. User Response: Check to be sure the action was entered next to the correct resource. Message Type: User input error. DELETE VALID ONLY FOR NCP TYPE RESOURCES Explanation: A Delete action was requested on a resource other than an NCP. Delete is valid only for NCPs. User Response: Check to be sure the action was entered next to the resource. Message Type: User input error. KONCV001 KXDFC012 45

46 KONCV178 KONCV179 KONCV180 KONCV181 KONCV182 KONCV183 NO EXCEPTIONS ARE GENERATED FOR THIS FIELD Explanation: Exceptions were requested for a data type that has no threshold settings and cannot be monitored. Message Type: Information. MONITOR OPTIONS UPDATE ERROR Explanation: While updating the NCP performance monitor options, an internal error was detected. User Response: Retry the operation. If the error persists, contact IBM Software Support. Message Type: Internal error. MONITOR OPTIONS WILL BE UPDATED WITH THE CURRENT SITE DEFAULTS Explanation: User has requested a reset of the NCP monitor options settings from a Change pop-up. Options are set to current site default settings when the user exits with an update (with the Enter key). User Response: Use the Enter key to update the monitor options, or use F12 to cancel the update. Message Type: Information. DELETE NOT ALLOWED FOR AN ACTIVE RESOURCE Explanation: User has requested a delete from the Site Monitor List for an NCP resource whose status is not NA. Available or active resources cannot be deleted. Message Type: Information. RESOURCE NOT FOUND Explanation: User has requested a resource that is not valid or does not exist. Message Type: Information. RESOURCE ALREADY USING SITE DEFAULT OPTIONS Explanation: User has requested a reset for a resource that is already using site default monitoring options. Resources with monitor options of Site (displayed on the NCP Site Monitor List) are using the site default monitor options. Message Type: User input error. 46 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

47 KONCV184 KONCV185 KONCV186 KONCV187 KONCV188 RESOURCE MUST BE AN LU OR TERMINAL Explanation: User has requested resource analysis for a resource other than an LU or terminal. Resource analysis returns session level data for partners in session. SDLC and BSC lines or PUs and clusters are not valid selections for resource analysis. Message Type: Information. NO SUBORDINATE RESOURCES ARE BEING MONITORED Explanation: A List action was selected for a resource that has no subordinate resources or whose subordinate resources are not being monitored. User Response: To start monitoring a resource, start the resource from the Site Monitor List (under NCP performance monitor options) with the R action code (Start). The Monitor or Collect option for the resource must be set to Monitor. Administrator authority is required. Message Type: Information. RESOURCE(S) ALREADY ADDED Explanation: Response time terminal or group with the same name already added. User Response: Use a unique name when adding a response time terminal or group. Message Type: Information. RESOURCE MUST BE STOPPED BEFORE MONITORING OPTIONS CAN BE CHANGED Explanation: A change action code has been entered for an NCP resource that is currently being monitored. The resource is in a started, or a pending start, mode. Monitoring options can be changed only when a resource is stopped. User Response: Enter a P action code (Stop) to stop monitoring the resource, and a C action code (Change) to change monitoring options. Then enter an R action code (Start) to resume monitoring. Message Type: Information. NCP PERFORMANCE IS VALID ONLY FOR LU TYPES NCP, LINE, OR PU Explanation: NCP Performance action cannot determine the type of LU when collection is for APPLS or TERMINALs. User Response: Enter NCP Performance (N) action on a LU collected from an NCP, Line, or PU. Message Type: User input error. KONCV001 KXDFC012 47

48 KONCV189 KONCV190 KONCV191 KONCV192 KONCV193 GROUP DESCRIPTION ALREADY EXISTS Explanation: Group description is already assigned to a group being monitored by ETE. User Response: Choose a different group description. Message Type: User input error. USER REQUESTED TO STOP MONITORING resource_name. SUBORDINATE RESOURCES MUST BE STOPPED BEFORE THIS RESOURCE CAN BE STOPPED. Explanation: A Stop action was issued for a resource that had subordinates that were being monitored. The high level resource cannot be stopped until the lower level resources are stopped. User Response: List the lower level resources and issue Stop actions for each one, beginning with the lowest level resource, LUs, and then PUs and lines. Message Type: User input error. NCP RESOURCE IS NOT BEING MONITORED Explanation: NCP resource has not been started in the NCP Site Monitor List. User Response: Under NCP performance monitor options, start the resource from the Site Monitor List with the R action code (Start). Message Type: User input error. NO UPDATE AUTHORIZATION, VIEW ONLY Explanation: The user has no administrative authority to update the monitoring options. System Action: Monitoring options displays are view only. User Response: If update authorization is required, have a product administrator authorize the user ID. Message Type: Information. RECORDING INTERVAL MUST BE GREATER THAN OR EQUAL TO THE NCP COLLECTION INTERVAL OF nnnnnnnn SECONDS Explanation: In the Global Monitoring Options panel, a value was specified for the trend recording interval that was less than the current value of the NCP collection interval. This is only acceptable if NCP trend recording is turned off. User Response: Set the trend recording interval greater than or equal to the NCP collection interval, or use the installation and configuration assistance tool reconfiguration option to set the NCP collection interval to a value less than or equal to the trend recording interval, or turn NCP trend recording off. Message Type: User input error. 48 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

49 KONCV198 KONCV199 KONCV205 KONCV206 THE TREND RECORDING INTERVAL (interval) IS LESS THAN THE NCP COLLECTION INTERVAL (interval). TREND RECORDING FOR NCP RESOURCES HAS BEEN DISABLED. Explanation: NCP trend recording cannot occur if the global trend recording interval is less than the NCP collection interval. At OMEGAMON II for Mainframe Networks initialization, NCP trend recording is disabled if the NCP collection interval is larger than the global trend recording interval System Action: Trend recording is turned off for NCP resources. User Response: Use the Global Monitoring Options panel to increase the trend recording interval to a value greater than or equal to the NCP collection interval and then re-enable the NCP trend recording option, or use installation and configuration assistance tool reconfiguration option to decrease the NCP collection interval to a value less than or equal to the trend recording interval. Decreasing the NCP collection interval requires a restart of OMEGAMON II for Mainframe Networks. Message Type: User specification error. NCP TREND RECORDING DISABLED AT STARTUP Explanation: The trend recording interval must be greater than or equal to the NCP collection interval. At initialization, if the collection interval exceeds the global trend recording interval, NCP trend recording is turned off. System Action: NCP trend recording is disabled. User Response: If you want NCP trend recording, change the NCP trend recording interval or the NCP collection interval so that the trend recording interval is greater than or equal to the NCP collection interval. Then turn NCP trend recording on. Message Type: User specification error. ENTER M OR H Explanation: The only acceptable characters to specify in this field are M (minutes) and H (hours). System Action: Field not updated. User Response: Enter an M or H in the field. Message Type: User input error. THE NCP TOPOLOGY UPDATE INTERVAL MUST BE GREATER THAN OR EQUAL TO THE NCP COLLECTION INTERVAL OF nnn SECONDS Explanation: While entering NCP default monitoring options, a value for NCP topology update interval was specified that was less than the NCP collection interval specified during installation and configuration assistance tool customiztion of OMEGAMON II for Mainframe Networks. System Action: NCP default monitoring options are not updated. User Response: Set the NCP topology update interval greater than or equal to the NCP collection interval. Message Type: User input error. KONCV001 KXDFC012 49

50 KONCV207 KONCV208 KONCV210 KONCV211 KONCV212 KONCV213 INVALID SCROLL AMOUNT Explanation: While attempting to scroll forward, an invalid scroll amount was entered in the line input field. User Response: Choose a number of lines to scroll that falls within the length of the table displayed. Message Type: User input error. Enter V or U Explanation: The only acceptable character to specify in this field is V for virtual circuits or U for logical units. User Response: Enter V or U in the field. Message Type: User input error. NO LUS ASSOCIATED WITH RESOURCE Explanation: The response time group for the specified resource did not locate any LUs associated with the resource to be monitored. System Action: The group does not appear in the response time display. User Response: Check the resource name in the Site Monitor List or in the NCP gen. Message Type: Warning. ADDRESS SPACE NAME ALREADY EXISTS Explanation: The TCP/IP address space could not be added to the list of monitored TCP/IP address spaces because the address space name is already in the list. User Response: Scroll through the list of TCP/IP address spaces on the TCP/IP Status Summary panel to locate the address space. Message Type: User error. CONNECTION ALREADY SPECIFIED Explanation: The TCP/IP high priority connection could not be added to the high priority connection list because the connection is already in the list. User Response: Scroll through the list of TCP/IP connections on the TCP/IP Connections panel to locate the connection. Message Type: User error. UPDATE SUCCESSFUL Explanation: Indicates a successful update. Message Type: Confirmation. 50 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

51 KONCV214 KONCV215 KONCV216 KONCV217 KONCV218 KONCV219 UPDATE ERROR Explanation: An error occurred during an update operation. User Response: The cursor is positioned at the field that was entered incorrectly. Verify your input and reenter. Message Type: User error. MUST BE ALPHABETIC Explanation: An attempt was made to enter non-alphabetic characters into a field that accepts only alphabetic characters. User Response: The cursor is positioned at the field that was entered incorrectly. Verify your input and reenter. Message Type: User error. BUFFER POOL DATA NOT AVAILABLE Explanation: Buffer Pool data is available for TCP/IP versions 3.2 and below. A TCP/IP release of greater than 3.2 was detected. Message Type: Information. CONNECTION NUMBER REQUIRED FOR DROP Explanation: An attempt was made to drop a connection that had no connection number. Message Type: Information. UDP CONNECTIONS CANNOT BE HIGH PRIORITY Explanation: Addition of a UDP connection to the high-priority list of monitored connections failed. UDP connections cannot be specified as high-priority. Message Type: Information. ADD OF TCP/IP ADDRESS SPACE FAILED Explanation: Addition of a TCP/IP address space to the monitored list of address spaces failed. User Response: The most likely cause of this error is an incorrect configuration dataset name and member specification. Ensure the configuration dataset information is correct and reenter. Message Type: User input error. KONCV001 KXDFC012 51

52 KONCV221 AT LEAST ONE ENTRY IS REQUIRED Explanation: User pressed Enter is a data entry dialog that required an entry and no entry was made. User Response: Enter a value in at least one of the data entry fields or press F12 to cancel out of the dialog. Message Type: User input error. KONCV222 CRITICAL MUST BE LESS THAN WARNING Explanation: The critical threshold value must be less than the warning value, when the less than or equal option is chosen. User Response: Raise the critical threshold and/or lower the warning threshold. Message Type: User input error. KONCV223 MUST BE >= OR <=. Explanation: A logical operator is required for the threshold settings. Either >= or <= must be specified. User Response: Use the F4=Prompt key to select a logical operator. Message Type: User input error. KONCV224 OID NAME IS UNKNOWN Explanation: The MIB object name specified on the TCP/IP console command line with the BULKWALK command is not a recognized MIB object name. User Response: Names are case-sensitive. Check the spelling and case of the object name, or use the Command pull-down to select an MIB object from the MIB Browser menu. Message Type: User input error. KONCV225 OID NUMBER IS UNKNOWN Explanation: The MIB object ID number specified on the TCP/IP console command line with the BULKWALK command is not a recognized MIB object number. User Response: Check that the object ID number was specified correctly, including the ending period, or use the Command pull-down to select an MIB object from the MIB Browser menu. Message Type: User input error. KONCV226 TCP/IP COMMAND ERROR Explanation: When attempting to execute a TCP/IP console command, an error was detected. User Response: Ensure that the command format and syntax are correct and resubmit the command. Otherwise, the command is not supported. Message Type: User input error. 52 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

53 KONCV227 KONCV228 KONFC000 KONFC001 KONFC002 command COMMAND FAILED Explanation: An attempt to execute the indicated command failed. User Response: Review all TCP/IP configuration steps relating to TCP/IP command authorization and security. Ensure that the OMEGAMON address space has the proper security authorization to perform the indicated command. Review the RKLVLOG for additional messages relating to the error. If the problem persists, gather the preceding 30 minutes of RKLVLOG and contact IBM Software Support. Message Type: Possible configuration error. HI PRIORITY CONNECTION NOT DEFINED Explanation: An attempt was made to delete an undefined TCP/IP high-priority connection. User Response: Verify the connection definition in the CT/Engine operator table manager. Log onto the CT/Engine operator and browse the OMVTAM.TCPIP.EXCPSHUN.TABLE to determine how the connection was originally defined. Once the error has been identified, retry the delete request. Message Type: User input error. KONFCCMD COMMAND PROCESSING COMPLETE Explanation: The feature control command, KONFCCMD, completed processing. Message Type: Confirmation. KONFCCMD COMMAND REQUEST FAILED ROUTINE=routine_name REASON=reason_code RETURN=return_code Explanation: An error was detected during feature control command (KONFCCMD) processing. System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONFCCMD COMMAND SYNTAX ERROR COMMAND(command_name) Explanation: A syntax error was detected while processing feature control command (KONFCCMD) arguments. System Action: The command request fails. User Response: Enter KONFCCMD HELP to list supported arguments. Re-enter the command specifying valid KONFCCMD arguments. Message Type: User input error. KONCV001 KXDFC012 53

54 KONFC003 KONFC004 KONFC005 KONFC010 KONFC011 KONAYFCV NOT AVAILABLE. INSTALL OPTION REQUIRED. Explanation: The KONAYFCV resource was not found while processing one of the following feature control command (KONFCCMD) options: START STOP STATUS System Action: The command request fails. The feature was not installed. User Response: Enter a KONFCCMD INSTALL request specifying the features requiring installation. Then you can use KONFCCMD to start, stop, or obtain the status of a feature. See the appendix in the OMEGAMON II for Mainframe Networks Configuration and Customization Guide for more information about the KONFCCMD command. Message Type: User input error. KONFCCMD INVALID OPTION(option_name) FOR COMMAND (command_name) Explanation: An invalid command option was detected while processing feature control command (KONFCCMD) arguments. System Action: The command request fails. User Response: Enter KONFCCMD HELP to list supported command options. Reenter KONFCCMD specifying valid command options. See the appendix in the OMEGAMON II for Mainframe Networks Configuration and Customization Guide for more information about the KONFCCMD command. Message Type: User input error. <help text> Explanation: This is a prefix for feature control command (KONFCCMD) HELP output. Message Type: Information. FPON COMPONENT FUNCTIONS INSTALLATION COMPLETE Explanation: The feature control command (KONFCCMD) installed OMEGAMON II for Mainframe Networks features (FPON) successfully. System Action: None Message Type: Confirmation. FPON COMPONENT FUNCTIONS INSTALLATION FAILED ROUTINE=KONAHOF0 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing OMEGAMON II for Mainframe Networks features (FPON). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. 54 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

55 KONFC012 KONFC015 KONFC016 KONFC017 KONFC020 KONFC021 <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS FPON output. Message Type: Information. FPCT COMPONENT FUNCTIONS INSTALLATION COMPLETE Explanation: The feature control command (KONFCCMD) installed FPCT features successfully. Message Type: Confirmation. FPCT COMPONENT FUNCTIONS INSTALLATION FAILED ROUTINE=KONAHCF0 REASON=reason_code RETURN= return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing FPCT features. System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS FPCT output. Message Type: Information. SEVT VTAM ENVIRONMENT INSTALLATION COMPLETE Explanation: The feature control command (KONFCCMD) installed VTAM environment features (SEVT) successfully. Message Type: Confirmation. SEVT VTAM ENVIRONMENT INSTALLATION FAILED ROUTINE=KONAHEV0 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing VTAM environment features (SEVT). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 55

56 KONFC023 KONFC024 KONFC025 KONFC026 KONFC027 KONFC028 <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS SEVT output. Message Type: Information. SEVT VTAM ENVIRONMENT STATUS FAILED ROUTINE=KONAHEV3 REASON=abend RETURN=abend_code Explanation: An error was detected while the feature control command (KONFCCMD) was checking the status of VTAM environment features (SEVT). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. SEMV MVS ENVIRONMENT INSTALLATION COMPLETE Explanation: The feature control command (KONFCCMD) installed MVS environment features (SEMV) successfully. Message Type: Confirmation. SEMV MVS ENVIRONMENT INSTALLATION FAILED ROUTINE=KONAHMF0 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing MVS environment features (SEMV). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS SEMV output. Message Type: Information. SEMV VTAM ENVIRONMENT STATUS FAILED ROUTINE=KONAHEM3 REASON=abend RETURN=abend_code Explanation: An error was detected while the feature control command (KONFCCMD) was checking the status of VTAM environment features (SEMV). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. 56 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

57 KONFC030 KONFC031 KONFC032 KONFC035 KONFC040 NCPC NPALU COLLECTOR INSTALLATION COMPLETE Explanation: The feature control command (KONFCCMD) installed the NCP data collection feature (NCPC). Message Type: Confirmation. NCPC NPALU COLLECTOR INSTALLATION FAILED ROUTINE=KONAHNP0 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing the NCP collector environment features (NCPC). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. option_name OPTION REQUIRED FOR NCPC INSTALLATION Explanation: A required component was not available to allow the feature control command (KONFCCMD) to install the NCP collector environment features (NCPC). System Action: The command request fails. User Response: Check the following: Was KONFCCMD INSTALL FPCT successful? Was KONFCCMD INSTALL SEMV successful? Was KONFCCMD INSTALL SEVT successful? Was NCPCACBN specified? Was NCPCINTV specified? If the problem persists, contact IBM Software Support. Message Type: User error. NCPC NPALU COLLECTOR START FAILED ROUTINE=KONAHNP1 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was starting the NCP collector environment features (NCPC). System Action: The command request fails. User Response: Check if KONFCCMD INSTALL NCPC was successful. If the problem persists, contact IBM Software Support. Message Type: User error. NCPC NPALU COLLECTOR STOP FAILED ROUTINE=KONAHNP2 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was stopping the NCP collector environment features (NCPC). System Action: The command request fails. User Response: Check if KONFCCMD INSTALL NCPC was successful. If the problem persists, contact IBM Software Support. Message Type: User error. KONCV001 KXDFC012 57

58 KONFC045 KONFC050 KONFC051 KONFC052 KONFC055 <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS NCPC output. Message Type: Information. NDMT NCP DATA MANAGER TASK INSTALLATION COMPLETE Explanation: The feature control command (KONFCCMD) installed the NCP data manager feature (NDMT) successfully. Message Type: Confirmation. NDMT NCP DATA MANAGER TASK INSTALLATION FAILED ROUTINE=KONAHNT0 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing the NCP data manager environment features (NDMT). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. option_name OPTION REQUIRED FOR NDMT INSTALLATION Explanation: Because a required component was unavailable, the feature control command (KONFCCMD) was unable to install the NCP data manager environment features (NDMT). System Action: The command request fails. User Response: Check the following: Was KONFCCMD INSTALL FPON successful? See message KONFC010. Was NDMTPATH specification for the KONFCCMD correct? Was NDMTSRVR specification for the KONFCCMD correct? Was NDMTUSER specification for the KONFCCMD correct? If the problem persists, contact IBM Software Support. Message Type: User error. NDMT NCP DATA MANAGER TASK START FAILED ROUTINE=KONAHNT1 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was starting the NCP data manager environment features (NDMT). System Action: The command request fails. User Response: Check if KONFCCMD INSTALL NDMT was successful. See message KONFC050. If the problem persists, log the information and contact IBM Software Support. Message Type: User error. 58 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

59 KONFC060 KONFC065 KONFC070 KONFC071 KONFC072 KONFC073 NDMT NCP DATA MANAGER TASK STOP FAILED ROUTINE=KONAHNT2 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was stopping the NCP data manager environment features (NCPC). System Action: The command request fails. User Response: Check if KONFCCMD START NDMT was successful. See message KONFC050. If the problem persists, log the information and contact IBM Software Support. Message Type: User error. <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS NDMT output. Message Type: Information. DBUG EXTENDED DIAGNOSTICS MODE STARTED Explanation: Extended diagnostics mode is active. Message Type: Confirmation. DBUG EXTENDED DIAGNOSTICS MODE START FAILED ROUTINE=KONAHFD1 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was starting extended diagnostic mode (DBUG). System Action: The command request fails. User Response: Log the information and contact IBM Software Support. Message Type: Internal error. DBUG EXTENDED DIAGNOSTICS MODE STOPPED Explanation: Extended diagnostics mode is inactive. Message Type: Confirmation. DBUG EXTENDED DIAGNOSTICS MODE STOP FAILED ROUTINE=KONAHFD2 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was stopping extended diagnostic mode (DBUG). System Action: The command request fails. User Response: Log the information and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 59

60 KONFC074 KONFC075 KONFC081 KONFC082 <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS DBUG output. Message Type: Information. DBUG EXTENDED DIAGNOSTICS MODE STATUS FAILED ROUTINE=KONAHFD3 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was displaying extended diagnostic mode (DBUG). System Action: The command request fails. User Response: Log the information and contact IBM Software Support. Message Type: Internal error. TCPC TCP/IP COLLECTOR INSTALLATION FAILED ROUTINE=KONACTC0 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was installing the TCP/IP collector feature (TCPC). System Action: The command request fails. User Response: Log the entire error message for problem diagnosis and contact IBM Software Support. Message Type: Internal error. option_name OPTION REQUIRED FOR TCPC INSTALLATION Explanation: Because a required component was not available, the feature control command (KONFCCMD) could not install the TCP/IP collector feature (TCPC). System Action: The command request fails. User Response: User Response: Check the following: Was KONFCCMD INSTALL SEMV successful? Was KONFCCMD INSTALL FPON successful? KONFC083 If the problem persists, contact IBM Software Support. Message Type: User error. TCPC TCP/IP COLLECTOR LOAD FAILED FOR MODULE module_name Explanation: The specified TCP/IP collector module could not be loaded into storage during installation of the TCP/IP collector feature (TCPC). System Action: TCP/IP collector installation fails. User Response: Log the information for problem diagnosis and contact IBM Software Support. Message Type: Internal error. 60 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

61 KONFC084 KONFC085 KONFC089 KONFC090 KONFC095 TCP/IP PROFILE ALLOCATION FAILED. RC(return_code), ERROR(reason_code), INFO(information_code) Explanation: Dynamic allocation of a TCP/IP profile dataset failed during the addition of a target TCP/IP to the address space list. System Action: The target TCP/IP is not added to the address space list and cannot be monitored. User Response: Log the information for problem diagnosis and contact IBM Software Support. Message Type: Internal error. I/O FAILED FOR TCP/IP PROFILE DATASET. FUNCTION: function_name REASON: reason_code Explanation: An open or read I/O of a TCP/IP profile dataset failed during the addition of a target TCP/IP to the address space list. System Action: The target TCP/IP is not added to the address space list and cannot be monitored. User Response: Log the information for problem diagnosis and contact IBM Software Support Message Type: Internal error. TCPC TCP/IP COLLECTOR START FAILED ROUTINE=KONACTC1 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was starting the TCP/IP collector feature (TCPC). System Action: The command request fails. User Response: Check if KONFCCMD INSTALL TCPC was successful. If the problem persists, contact IBM Software Support. Message Type: User error. TCPC TCP/IP COLLECTOR STOP FAILED ROUTINE=KONACTC2 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was stopping the TCP/IP collector feature (TCPC). System Action: The command request fails. User Response: Check if KONFCCMD INSTALL TCPC was successful. If the problem persists, contact IBM Software Support. Message Type: User error. <status text> Explanation: This is a prefix for feature control command (KONFCCMD) STATUS TCPC output. Message Type: Information. KONCV001 KXDFC012 61

62 KONFC096 KONFC100 KONFC101 KONFC102 KONFC103 KONFC104 TCPC STATUS COMMAND FAILED ROUTINE=KONACTC3 REASON=reason_code RETURN=return_code Explanation: An error was detected while the feature control command (KONFCCMD) was executing the status function for the TCP/IP collector feature (TCPC). System Action: The command request fails. User Response: Check if KONFCCMD INSTALL TCPC was successful. If the problem persists, contact IBM Software Support. Message Type: Internal error. OMEGAMON II for Mainframe Networks DIAGNOSTIC feature MODE ACTIVATED Explanation: The internal diagnostic trace or trap facility was started in response to a KONFCCMD START feature command. System Action: Processing continues. Message Type: Informational. OMEGAMON II for Mainframe Networks DIAGNOSTIC feature ACTIVATION FAILED ROUTINE=KONAHFT1 REASON=reason RETURN=return Explanation: An error was detected during the processing of a KONFCCMD START TRACE or TRAP command. System Action: Processing continues. The facility is not activated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. OMEGAMON II for Mainframe Networks DIAGNOSTIC feature MODE DEACTIVATED Explanation: The internal diagnostic trace or trap facility was stopped in response to a KONFCCMD STOP feature command. System Action: Processing continues. Message Type: Informational. OMEGAMON II for Mainframe Networks DIAGNOSTIC feature MODE DEACTIVATION FAILED ROUTINE=KONAHFT2 REASON=reason RETURN=return Explanation: An error was detected during the processing of a KONFCCMD STOP TRACE or TRAP command. System Action: Processing continues. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. OMEGAMON II for Mainframe Networks DIAGNOSTIC feature IS status 62 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

63 KONFC105 KONLC100 KONLC101 KONLC102 KONLC103 DEACTIVATED Explanation: This message reports the status of the diagnostic trace or trap facility in response to a KONFCCMD STATUS feature command. System Action: Processing continues. Message Type: Informational. OMEGAMON II for Mainframe Networks DIAGNOSTIC feature STATUS FAILED ROUTINE=KONAHFT3 REASON=reason RETURN=return Explanation: An error was detected during the processing of a KONFCCMD STATUS TRACE or TRAP command. System Action: Processing continues. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. LOCAL APPLID applid UNAVAILABLE, NDM TASK WILL TERMINATE. Explanation: OMEGAMON II for Mainframe Networks was unable to open the VTAM ACB applid. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Check that the APPL applid is defined to VTAM and active. Message Type: Information. COLLECTOR APPLID applid UNAVAILABLE, NDM TASK WILL TERMINATE. Explanation: OMEGAMON II for Mainframe Networks was unable to connect to the VTAM ACB applid. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Check that the APPL applid is defined to VTAM and active. Check that the OMEGAMON II for Mainframe Networks which contains the NCP collection component is active. Message Type: Information. APPC REQUEST ERROR appc_request ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: An APPC service failed. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. CLIENT MODULE module_name NOT FOUND ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: OMEGAMON II for Mainframe Networks was not able to locate a module required for communication with the NCP collector component. KONCV001 KXDFC012 63

64 System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. 64 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

65 KONLC104 KONLC106 KONLC107 KONLC108 KONLC109 MISSING KONAYLCA WORK AREA ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: OMEGAMON II for Mainframe Networks was not able to locate the communications work area. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. APPC VERSION MISMATCH. LOCAL VERSION local_version COLLECTOR VERSION collector_version Explanation: OMEGAMON II for Mainframe Networks detected that the NCP collector component was at an incompatible service level. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Verify the service level of the OMEGAMON II for Mainframe Networks containing the NCP collector component. Message Type: User Error. SQL REQUEST ERROR, ROUTINE=routine-name REQUEST=sql_request_codes Explanation: An invalid SQL request was received. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. FAILURE TO ACQUIRE STORAGE FOR storage_area ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: OMEGAMON II for Mainframe Networks was not able to obtain the storage required to process the current request. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. KONAYNCE SELECT COUNT ERROR ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: OMEGAMON II for Mainframe Networks detected an error with the data returned from the NCP collection component. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 65

66 KONLC110 KONLC111 KONLC112 KONLS100 KONLS101 KONLS102 APPC CLIENT SERVICES ABEND CODE=abend_code PSW=psw ROUTINE=routine_name Explanation: An abend occurred in the module indicated. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. Rnn - Rnn: registers Explanation: Registers associated with abend message KONLC110. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. CONNECTION FAILURE ACBNAME localid Explanation: The VTAM APPL localid has been terminated abnormally. System Action: Collection of NCP data terminates. OMEGAMON II for Mainframe Networks will attempt to restart collection at a regular interval. User Response: Check that the APPL is active to VTAM. IBM Software Support. Message Type: Information. COLLECTOR APPLID applid IS UNAVAILABLE ROUTINE=routine_name Explanation: APPC initialization failed during start-up. System Action: APPC initialization will retry next collection interval. User Response: None Message Type: User error. APPC REQUEST ERROR appc_request DURING startup shutdown ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: APPC service failure occurred during initialization. System Action: APPC request failed and the NCPC collector task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. FAILURE TO ACQUIRE STORAGE FOR storage_area ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: Storage could not be obtained for the specified area. System Action: The APPC environment and NCPC collector are terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. 66 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

67 KONLS103 KONLS104 KONLS105 KONLS106 KONLS107 KONLS108 INVALID COLLECTOR APPLID RECEIVED ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: Invalid acbname received from the collector keyword. System Action: The APPC environment and NCPC collector are terminated. User Response: Check the COLLECTOR acbname keyword on the KONFCCMD INSTALL NCPC command in the start-up member. Message Type: User error. MODULE ENTRY POINT module_name NOT FOUND ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: The entry point of the module name is not found. System Action: The APPC environment and NCPC collector are terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. MISSING storage_area WORK AREA ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: The storage area is not available for normal APPC processing. System Action: The APPC environment and NCPC collector are terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. APPC REQUEST ERROR appc_request ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: APPC service failure occurred during communication. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. INVALID TOKEN PASSED TOKEN=token ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: Incorrect data is representing the token. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. KONAXNPA npa_request FAILED ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: The NPA service request did not complete. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 67

68 KONLS109 KONLS110 KONLS111 KONLS112 KONLS113 KONLS114 TABLE REQUEST ERROR ROUTINE=routine_name TABLE=table_name Explanation: Invalid NCP resource table request. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. INVALID RESOURCE COUNT ERROR ROUTINE=routine_name RETURN=return_code COUNT=count Explanation: Invalid number received and cannot be processed. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. KONAYWKG CHAIN ERROR ROUTINE=routine_name RETURN=return_code REASON=reason_code Explanation: The WORKG area does not exist when session terminating. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. LUCS SERVICES ABEND CODE=abend_code PSW=psw ROUTINE=routine_name Explanation: The referenced routine received a abend. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. R00 - R15: registers r0-r15 Explanation: Registers associated with abend in message KONLS112. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. CONNECTION FAILURE USING ACBNAME applid ROUTINE=routine_name Explanation: The applid referenced received a communication failure. System Action: The NDMT task is terminated. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. 68 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

69 KONND000 KONND001 KONND002 KONND003 KONND004 KONND005 NCP STATISTICS COLLECTOR AVAILABLE FOR REQUESTS Explanation: The NCP NPALU collector task can receive requests. Message Type: Confirmation. NCP STATISTICS COLLECTOR IS TERMINATING Explanation: The NCP NPALU collector task is terminating. Message Type: Information. NCP STATISTICS COLLECTOR ABENDED, CODE=abend_code PSW=program_status_word Explanation: The NCP NPALU collector task abended. The code and Program Status Word (PSW) are displayed. System Action: The NCP NPALU collector task attempts to recover and continue executing. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message KONND003 follows. Message Type: Internal error. Rregister_number - Rregister_number register_value Explanation: This is diagnostic information following message KONND002. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. SESSION ESTABLISHED WITH NPALU=npalu_name Explanation: The NCP NPALU collector task is in contact with NPALU=npalu_name and is ready to monitor requests for the corresponding NCP. Message Type: Confirmation. SESSION REJECTED FOR NPALU=npalu_name reason_description Explanation: The NCP NPALU collector task was unable to establish a session with NPALU=npalu_name because of the specified reason. System Action: NCP statistics data is not available from the NPALU. User Response: Check the dataset names assigned to ddname KONRRT (Resource Resolution Table) and ddname KONSRC (NCP-generated NDF source library) in the started task JCL for the local NCP collector address space. Message Type: User configuration or resource availability error. KONCV001 KXDFC012 69

70 KONND006 KONND007 KONND008 KONND009 KONND010 KONND011 SESSION TERMINATED WITH NPALU=npalu_name Explanation: The NCP NPALU collector task lost the session with NPALU= npalu_name. System Action: NCP statistics data is not available from the NPALU. Message Type: User configuration or resource availability error. NCP STATISTICS COLLECTOR COMPLETED TERMINATION Explanation: The NCP NPALU collector task completed termination. Message Type: Confirmation. FAILURE TO ACQUIRE STORAGE FOR MONITORING ROUTINE=KONAHN00 REASON=reason_code Explanation: A storage failure prevented a resource from being monitored. Message Type: Warning. FAILURE ADDING RESOURCE(resource_name) TO USER TOPOLOGY ROUTINE=KONAHN00 REASON=NETWORK TOPOLOGY SERVICES FAILURE Explanation: A resource could not be added to the user NCP topology due to a failure in network topology services. User Response: See previously issued messages. Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. STORAGE FAILURE IN NPALU COLLECTOR ROUTINE=routine_name REASON=reason_code Explanation: Storage could not be acquired in the specified routine. Message Type: Warning. FAILURE TO OPEN VTAM ACB NAME(acb_name) Explanation: The specified ACB name could not be opened to VTAM for the NPALU collector task. User Response: Determine if the specified ACB name is in a connectable state. Message Type: Warning. 70 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

71 KONND012 KONND013 KONND014 KONND015 KONND016 FAILED TO FIND OWNING RESOURCE owning_resource_name FOR RESOURCE resource_name DURING DYNAMIC DELETE Explanation: The owning resource named owning_resource_name was not found in the topology as the owner of the resource named resource_name during a dynamic resource delete. System Action: The resource named resource_name is not deleted. User Response: Log the message for problem diagnosis and call IBM Software Support. Message Type: Internal error. FORWARD REQUEST FOR NPALU(npalu_name) FAILED STORAGE FAILURE MODULE=KONAHN05 REASON=reason_code Explanation: Collection data could not be forwarded from the specified NPALU on the current collection interval. Collection will be attempted on the next interval. Message Type: Warning. NCP DICTIONARY(module_name) FOR NCP RELEASE(NCP_release) LOAD FAILED Explanation: The data dictionary for the specified NCP release could not be loaded. The NCP cannot be monitored. User Response: If the NCP is a supported release, contact IBM Software Support. Message Type: Internal error. $PAM($PAM_name) FAILED ROUTINE=KONAHN04 DDNAME=KONRRT R15=return_code R0=return_code R1=return_code Explanation: The specified CT/Engine function failed in accessing ddname KONRRT. User Response: Verify that the ddname KONRRT is available to the NPALU collector. Message Type: User error. INPUT EXIT RECEIVE FAILED MODULE=KONAHN06 R0=return_code R1=return_code R15=return_code Explanation: A VTAM receive function failed. User Response: See previously issued messages. Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 71

72 KONND017 KONND018 KONND019 KONND020 KONND021 KONND022 FAILURE ADDING DYNAMIC RESOURCE(resource_name) TO TOPOLOGY ROUTINE=KONAHN12 R0=register_value R1=register_value R15=register_value Explanation: Storage could not be acquired to add the specified resource to the topology. NCP statistics are not available for that resource. Message Type: Warning. MAXCOLL REACHED WHEN STARTING COLLECTION ON resource_name NPALU=npalu_name Explanation: The specified resource cannot start collection because the NCP is already collecting data from the maximum number of resources allowed. User Response: Increase the MAXCOLL parameter in the NCP generation. Message Type: User error. SEND OF START NETWORK DATA ACQUISITION RU FOR resource_name FAILED ROUTINE=KONAHN16 R0=return_code R1=return_code Explanation: The NCP sent a negative response to a start network data acquisition RU for the specified resource. Message Type: Warning. SEND OF STOP NETWORK DATA ACQUISITION RU FAILED ROUTINE=KONAHN16 R0=return_code R1=return_code Explanation: The NCP sent a negative response to a stop network data acquisition RU. Message Type: Warning. SEND OF FORWARD NETWORK DATA RU FAILED ROUTINE=KONAHN16 R0=return_code R1=return_code Explanation: The NCP sent a negative response to a forward network data RU. Message Type: Warning. $PAM($PAM_name) FAILED ROUTINE=KONAGSRC DDNAME=ddname R15=return_code R0=return_code R1=return_code Explanation: The specified CT/Engine $PAM (PDS services) function failed. User Response: Check the dataset names assigned to ddname KONRRT (Resource Resolution Table) and ddname KONSRC (NCP-generated NDF source library) in the started task JCL for the local NCP collector address space. Message Type: Warning. 72 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

73 KONND023 KONND024 KONND025 KONND026 KONND027 KONND028 $PAM($PAM_name) FAILED ROUTINE=KONAGSRC DDNAME=ddname MEMBER=member_name R15=register_value R0=register_value R1=register_value Explanation: The specified CT/Engine $PAM (PDS services) function failed accessing the specified member. Message Type: Warning. FAILURE OPENING DDNAME(ddname) FOR MVS LOAD ROUTINE=KONAGLOD Explanation: The specified ddname could not be opened for an MVS load. System Action: See previously issued messages. Message Type: User error. FAILURE DELETING MODULE(module_name) Explanation: The specified module could not be deleted from MVS storage. Message Type: Warning. FAILURE LOADING MODULE(module_name) ROUTINE=KONAGLOD SYSTEM CODE=system_code REASON CODE=reason_code Explanation: The specified module could not be loaded into MVS storage. The accompanying system and reason codes are provided. System Action: See previously issued messages. Message Type: User error. NETWORK TOPOLOGY ERROR LOADING OR READING RRT (RRT_name) Explanation: The specified RRT could not be loaded or read. The corresponding NCP topology could not be built. User Response: Verify that a valid RRT by the specified name is pointed to by ddname KONRRT. Message Type: User error. NETWORK TOPOLOGY ERROR NPALU NAME MISMATCH IN RRT (RRT_name) FOR NPALU(npalu_name) Explanation: The specified RRT did not contain the correct NPALU name for the indicated NPALU. User Response: Verify that the correct RRT is available to the NPALU collector. Message Type: User error. KONCV001 KXDFC012 73

74 KONND029 KONND030 KONND031 KONND032 KONND033 NETWORK TOPOLOGY DUPLICATE RESOURCE(resource_name) FOUND IN RRT(RRT_name) Explanation: The specified resource was found in the indicated RRT but already exists in the current NCP topology. User Response: Verify your NCP generation. Message Type: User error. NETWORK TOPOLOGY ERROR IN LOCATE FUNCTION DURING ADDITION OF NCP(NCP_name) R15=register_value Explanation: An unrecoverable error occurred locating resources in the current topology while adding the indicated NCP. A check is being made in the current topology for any duplicate resources. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. NETWORK TOPOLOGY ERROR NCP(NCP_name) NOT FOUND IN TOPOLOGY FOR DELETION Explanation: You requested the deletion of a specified NCP, but it does not exist. User Response: Check the status of the NCP. Message Type: User or internal error. NCP SOURCE TO RRT MISMATCH FOR MEMBER NCP_source_member DURING function_call. FOUND LABEL NCP_source_label Explanation: The indicated NCP source member did not match the resources found in its corresponding Resource Resolution Table (RRT). User Response: Verify that the NCP source member and its RRT match. Message Type: User error. OPEN OF SOURCE MEMBER FOR NCP(NCP_source_member) FAILED Explanation: The indicated NCP source member could not be opened. User Response: Verify the indicated NCP source member is available in ddname KONSRC, the NCP generated NDF source library. Message Type: User error. 74 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

75 KONND034 KONND035 KONND036 KONND037 KONND100 KEYWORD(keyword) ON(macro_name) MACRO WITH LABEL(label_name) IS NOT SPECIFIED Explanation: This keyword is not explicitly specified on the macro with the indicated label in the NCP source member. The keyword is used by the NCP statistics component. System Action: Some calculated statistics may not be available. See the Planning chapter in the OMEGAMON II for Mainframe Networks Configuration and Customization Guide. User Response: Specify the keyword on the macro in the NCP source member. Message Type: Warning. DYNAMIC MOVE FAILED TO FIND (resource_name) RESOURCE IN CURRENT TOPOLOGY Explanation: A target or source resource, resource_name, was not found in the current topology during a dynamic move. NCP topology information may be incorrect. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. RRT RELEASE LEVEL rrt_level UNKNOWN FOR NCP_name. USING LEVEL rrt_level1 NCP RELEASE ncp-level. Explanation: The NCP(NCP_name) is not generated at a supported release level and cannot be monitored at that level. System Action: The NCP will be monitored using rrt_level1 and ncp-level as shown in the message. User Response: If the NCP is a supported release, contact IBM Software Support. Message Type: Internal error. NCP WILL NOT BE MONITORED Explanation: The NCP(NCP_name) specified in previous messages cannot be monitored. User Response: See previous messages. Message Type: Information. NCP DATA MANAGER TASK AVAILABLE FOR REQUESTS Explanation: The NCP data manager task can receive requests. Message Type: Confirmation. KONCV001 KXDFC012 75

76 KONND101 KONND102 KONND103 KONND104 KONND105 NCP DATA MANAGER TASK IS TERMINATING Explanation: The NCP data manager task is terminating. Message Type: Confirmation. NCP DATA MANAGER TASK ABENDED, CODE=abend_code PSW=program_status_word ROUTINE=routine_name Explanation: The NCP data manager task abended. The code, Program Status Word (PSW), and routine are displayed. System Action: The NCP data manager task attempts error recovery. User Response: Log the information displayed for problem diagnosis, and contact IBM Software Support. Message KONND103 follows. Message Type: Internal error. Rregister_number - Rregister_number register_value Explanation: This is diagnostic information following message KONND102. User Response: Log this information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. NCP DATA MANAGER TASK TERMINATION COMPLETE Explanation: The NCP data manager task terminates. Message Type: Confirmation. NCP DATA MANAGER TASK INITIALIZATION FAILED REASON=reason_code RETURN=return_code Explanation: An error occurred while initializing the NCP Data Manager task. Return codes are dependent upon reason code and are used by IBM Software Support for problem determination. Reason codes are TASKLRN ALLOCTHT PATHCTDS TOKNCTDS CNCTCTDS NCPCINTV System Action: Unable to establish CT/Engine logical resource number. Unable to allocate memory. Unable to connect to NCP collector. Unable to acquire token for NCP collector. Unable to connect to NCP collector. Unable to retrieve NCP collector interval value. NCP Data Manager task does not initialize. 76 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

77 KONND106 KONND107 KONND108 KONND109 User Response: Depending on the reason code, take recommended action or contact IBM Software Support as follows: TASKLRN ALLOCTHT PATHCTDS TOKNCTDS CNCTCTDS NCPCINTV Log information and contact IBM Software Support. Change your memory allocations. See previous message. See OMEGAMON II for Mainframe Networks RKLVLOG. Check if NCP collector is available. See previous message. Message Type: Internal or user error. NRE ADD RESOURCE FAILED FOR NCP_name NPALU=npalu_name RETURN=return_code Explanation: An internal error has occurred within the NCP data manager task. System Action: The NCP data manager task terminates. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. NRE DELETE RESOURCE FAILED FOR NCP_name NPALU=npalu_name RETURN=return_code Explanation: An internal error has occurred within the NCP data manager task. System Action: The NCP data manager task terminates. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. SQL RESOURCE ALLOCATION FAILED RETURN=return_code Explanation: An internal request for SQL resources by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API UPDATE TOPOLOGY REQUEST FAILED RETURN=return_code SENSE=sense_code Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 77

78 KONND110 KONND111 KONND112 KONND113 KONND114 KONND115 API UPDATE TOPOLOGY ERROR KONAYNCE SNAP Explanation: An internal request by the NCP data manager task has failed. Message is diagnostic information. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API UPDATE TOPOLOGY ERROR KONAYNRE SNAP Explanation: An internal request by the NCP data manager task has failed. Message is diagnostic information. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API UPDATE DATA REQUEST FAILED RETURN=return_code SENSE=sense_code Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API UPDATE DATA ERROR KONAYNCE SNAP Explanation: An internal request by the NCP data manager task has failed. The message is diagnostic information. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API UPDATE DATA ERROR KONAYNRE SNAP Explanation: An internal request by the NCP data manager task has failed. The message is diagnostic information. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAYNRE RDI SEGMENT ALLOCATION FAILED Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. 78 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

79 KONND116 KONND117 KONND118 KONND119 KONND120 KONND121 KONAYNRE RDS SEGMENT ALLOCATION FAILED Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAYNRE HEADER ALLOCATION FAILED Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API ADD MONITOR REQUEST FAILED FOR resource_name NPALU=npalu_name RETURN=return_code SENSE=sense_code Explanation: A request to start monitoring resource (resource_name) failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API DELETE MONITOR REQUEST FAILED FOR resource_name NPALU=npalu_name RETURN=return_code SENSE=sense_code Explanation: A request to stop monitoring resource cccccccc failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAYNCE ALLOCATION FAILED Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API EXTRACT RESOURCE REQUEST FAILED FOR resource_name NPALU=npalu_name RETURN=return_code SENSE=sense_code Explanation: A request to extract resource data for resource_name failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 79

80 KONND122 KONND123 KONND124 KONND125 KONND126 KONND130 API EXTRACT RESOURCE LIST REQUEST FAILED FOR resource_name NPALU=npalu_name RETURN=return_code SENSE=sense_code Explanation: A request to extract resource data owned by resource_name failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API ADD MONITOR LIST REQUEST FAILED FOR resource_name NPALU=npalu_name RETURN=return_code SENSE=sense_code Explanation: A request to add monitoring for a list of resources owned by resource_name failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API ADD MONITOR LIST KONAXNTS ERROR RETURN=return_code Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API DELETE MONITOR LIST REQUEST FAILED FOR resource_name NPALU=npalu_name RETURN=return_code SENSE=sense_code Explanation: A request to delete a list of monitored resources owned by resource_name failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. API DELETE MONITOR LIST KONAXNTS ERROR RETURN=return_code Explanation: An internal request by the NCP data manager task has failed. System Action: The NCP data manager task request fails. User Response: Log the information for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAGNPB SERVICE FUNCTION - ABENDED, CODE=abend_code Explanation: A request being processed by the KONAGNPB API module has abended. System Action: The site default or resource specific monitor options are not modified. User Response: Log the information displayed for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. 80 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

81 KONND131 KONND132 KONND133 KONND134 KONND135 KONAGNPB SERVICE FUNCTION - FAILED, FUNCTION=function_name, RETURN=return_code Explanation: A request being processed by the KONAGNPB API module has failed. System Action: The site default or resource specific monitor options are not modified. User Response: Log the information displayed for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAGNPB ENTERED FOR AN INVALID FUNCTION Explanation: An invalid or unsupported function code was passed to the KONAGNPB API. System Action: The site default or resource specific monitor options are not modified. User Response: Log the information displayed for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAGNPB NO HASH TABLE ADDRESS FOUND IN THE ACT WORK AREA Explanation: The address of the hash table used to look up the KONAGNPB control block addresses could not be found in the KONAYACT work area. System Action: The site default or resource specific monitor options are not modified. User Response: Log the information displayed for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. KONAGNPB GET NRE ERROR RETURN=return_code REASON=reason Explanation: The NRE representing the CCU was not found. System Action: The NPB task request fails. User Response: Log the information displayed for problem diagnosis, and contact IBM Software Support. Message Type: Internal error. NDMT SERVICE REQUEST FAILED Explanation: The NDM task detected a connection loss with the NCP collector. System Action: The NDM task terminates. User Response: Check the availability of the NCPC collector task. The NDM task attempts to reconnect when available. For more details, see other messages in the OMEGAMON II for Mainframe Networks RKLVLOG. Message Type: Resource availability error. KONCV001 KXDFC012 81

82 KONND136 KONND137 KONND138 KONND139 KONND140 BIND FAILURE FOR NPALU=npalu_name SENSE=sense_code Explanation: The NCP NPALU collector task was unable to establish a session with the named NPALU because of the specified sense bytes. System Action: The session between the NPALU and NCP collector is not established. User Response: Look up the sense bytes in the IBM VTAM Messages and Codes manual. Message Type: User configuration or resource availability error. SESSION LOGON FAILED FOR NPALU=npalu_name REASON=reason_code Explanation: The NCP NPALU collector task was unable to establish a session with the named NPALU because of the specified reason. System Action: The session between the NPALU and the NCP collector is not established. User Response: Log the information for problem diagnosis and contact IBM Software Support. Message Type: Internal error. KONAGFPF FLOATING POINT FUNCTION FAILED REASON=ABEND CODE=abend_code Explanation: The floating point function (FPF) service module abended. System Action: The FPF task request fails. User Response: Log the information displayed for problem diagnosis and contact IBM Software Support. Message Type: Internal error. SEVERE ERROR IN OWNER LOOKUP RES=resource_name, OWNER=owner_name,RETURN=hex_return_code Explanation: While attempting to insert resource_name into the monitored topology, the NCP data manager was unable to locate the owning resource (owner_name). Note the resource and owner names, and the hexadecimal return code for problem diagnosis. System Action: Monitoring of this resource fails. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. NMVRU REJECTED, REASON: reason_code ru_contents Explanation: While processing TIC3 data, a Network Manager Vector (NMV) RU was rejected. reason_code is 04 Invalid or unsupported NMVRU. 08 Associated resource not found. 12 Resource descriptor not found. 16 BER envelope not located in NMVRU 20 Invalid BER envelope 24 General error processing NMVRU counters. 82 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

83 KONND212 KONND213 KONND214 KONND215 KONND216 The contents of the RU appears on the log in character and hexadecimal format after the message text. System Action: The TIC3 data is ignored, but processing continues. User Response: Save the logged information and contact IBM Software Support. Message Type: Internal error. X.25 VC DEFINITIONS IN ERROR: SUFFIX=suffix, HEXNAME=hexname, PRFPU=prfpu, PRFLU=prflu Explanation: The specified names in the X.25 generation are not valid names. User Response: Verify that the names in your X.25 generation are valid. Message Type: Warning. GENPUNAM ERRORS DETECTED Explanation: The PU name generated in message KONND212 is not valid. User Response: Refer to message KONND212. Message Type: Informational. GENLUNAM ERRORS DETECTED Explanation: The LU name generated in message KONND212 is not valid. User Response: Refer to message KONND212. Message Type: Informational. ERRORS DETECTED DURING X.25 RESOURCE SCANNING FOR resource.ncp WILL NOT BE MONITORED Explanation: The specified resource in the X.25 generation cannot be processed. System Action: The NCP controlling the resource is not monitored. User Response: Refer to message KONND212, KONND213, or KONND214. Verify that the names in your X.25 generation are valid. Message Type: User configuration error. RRT TYPE FOR RESOURCE resource IS NOT IN TABLE - MODULE (KONAGNTS) LABEL(TYPETAB) Explanation: The specified resource in the Resource Resolution Table (RRT) has an unknown resource type. System Action: The resource is not monitored, but processing of the RRT continues. To resolve the problem, IBM Software Support requires a copy of your RRT. Message Type: Internal error. KONCV001 KXDFC012 83

84 KONND217 KONND218 KONND219 KONND220 SCANNING OF NCP ncp_name STARTED Explanation: The NCP topology build is being processed. Message Type: Informational. APPC ENVIRONMENT NOT INITIALIZED. Explanation: The APPC initialization failed during start-up. System Action: APPC initialization will retry next interval. User Response: Check the VTAM configuration definitions. Message Type: User error. APPC ENVIRONMENT TERMINATION FAILED. Explanation: The APPC termination failed during shutdown. User Response: Log the diagnostic information and contact IBM Software Support. Message Type: Internal error. ADDITION OF NCP ncp_name IS COMPLETE. Explanation: The NCP collector has successfully added the resources of the named NCP to the topology. Message Type: Confirmation. KONPN001 OMEGAMON II for Mainframe Networks (version_number) INITIALIZATION COMPLETED Explanation: OMEGAMON II for Mainframe Networks initialization has completed for the specified version. Message Type: Confirmation. KONPN002 ACT STARTED SUCCESSFULLY Explanation: ACT (Automatic Collector Task) has successfully started. ACT is required for trending and exception analysis. It is started automatically during start-up time of OMEGAMON II for Mainframe Networks. Message Type: Confirmation. 84 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

85 KONPN003 KONPN004 KONPN005 KONPN006 KONPN007 ACT TERMINATED WITH ERROR RC(return_code) SC(sense_code) Explanation: ACT (Automatic Collector Task) terminated with error. OMEGAMON II for Mainframe Networks continues to run without providing trending and exception analysis. All status lights on the main status panel display IDLE status. System Action: OMEGAMON II for Mainframe Networks continues to run without the ACT. User Response: Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and contact IBM Software Support. Message Type: Internal error. ETE CONNECTION FAILED RC(return_code) SC(sense_code) Explanation: During product initialization, OMEGAMON II for Mainframe Networks encountered an error while attempting to connect the end-to-end response time environment. System Action: OMEGAMON II for Mainframe Networks continues to run without ETE. User Response: Verify that the ETE started task is active and that you are running the correct level of ETE. Also, review the information on enabling ETE in the OMEGAMON II for Mainframe Networks Configuration and Customization Guide. Verify that all steps were completed accurately. Then, restart OMEGAMON II for Mainframe Networks. If problem persists, gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and contact IBM Software Support. Message Type: Probable user error. ETE CONNECTED SUCCESSFULLY Explanation: OMEGAMON II for Mainframe Networks successfully established the ETE connection during product start-up. Message Type: Confirmation. userid LOGGED ON USERWORK(user_workarea_address) RC(return_code) Explanation: Specified user ID logged on. Message Type: Confirmation. OMEGAMON II FOR VTAM (V500) - INITIALIZATION ERROR Explanation: OMEGAMON II for Mainframe Networks encountered an error during start-up. System Action: OMEGAMON II for Mainframe Networks fails to initialize and shuts down. User Response: Search the RKLVLOG dataset for one of the following messages: KONPN020, KONPN021, KONPN022, or KONPN024. These messages provide more detailed information about the nature of the error. KONCV001 KXDFC012 85

86 Message Type: Probable user error. 86 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

87 KONPN008 LOGON ERROR ENCOUNTERED FOR USER userid FUNCTION function_name) RC(return_code) SENSE(sense_code) USERWORK(user_workarea_address) text_string Explanation: This message is issued in conjunction with display panel KONDFATD when a user logon to OMEGAMON II for Mainframe Networks fails. System Action: Logon fails. User Response: Perform the action recommended on panel KONDFATD. Message Type: Probable user error. KONPN011 ERROR IN DIALOG calling_dialog MODULE(dialog_function) RC(return_code) SENSE(sense_code) LU(lu_name) APPL(applid) USERID(userid) text string Explanation: A generalized message providing diagnostics information when a call from a dialog to a dialog function fails. System Action: OMEGAMON II for Mainframe Networks will bypass the function and continue if possible. User Response: This message usually indicates a problem performing the requested function. Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and call IBM Software Support. Message Type: Internal error. KONPN012 TABLE SERVICE ERROR IN DIALOG calling_dialog FUNCTION(table_services-function) TABLE(table_name) RC(return_code) LU(lu_name) APPL(applid) USERID(userid) text_string Explanation: A generalized message providing diagnostics information when a table service function returns a non-zero return code. System Action: OMEGAMON II for Mainframe Networks will bypasses the requested function and continues operation. User Response: This message usually indicates there is a problem performing the requested table service function. Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and call IBM Software Support. Message Type: Internal error. KONPN013 PDS ERROR IN DIALOG calling_dialog FUNCTION(pds_function) RC(return_code) LU(lu_name) APPL(applid) USERID(userid) text_string Explanation: A generalized message providing diagnostics information when a PDS function returns a non-zero return code. User Response: This message usually indicates a problem performing the requested PDS function. The text string information usually explains the nature of the error. Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and contact IBM Software Support. Message Type: Internal error. KONCV001 KXDFC012 87

88 KONPN014 SAM ERROR IN DIALOG calling_dialog FUNCTION(SAM_function) RC(return_code) LU(lu_name) APPL(applid) USERID(userid) text string Explanation: A generalized message providing diagnostics information when a SAM (Sequential Access Manager/Dynamic Allocation) service function returns a non-zero return code. System Action: OMEGAMON II for Mainframe Networks bypasses the SAM function and continues operation. User Response: This message usually indicates a problem performing the requested SAM function. The accompanying text string, if any, can be helpful in identifying the cause of the problem. Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and contact IBM Software Support. Message Type: Internal error. KONPN015 ENGINE SERVICES ERROR IN DIALOG calling_dialog FUNCTION(engine_services_function) RC(return_code) LU(lu_name) APPL(applid) USERID(userid) text string Explanation: A generalized message providing diagnostics information when a call from a dialog to a dialog function fails. System Action: OMEGAMON II for Mainframe Networks bypasses the function and continues operation, if possible. User Response: Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and contact IBM Software Support. Message Type: Internal error. KONPN016 ERROR IN DIALOG error_dialog LU(lu_name) APPL(applid) USERID(userid) text_string Explanation: Error in specified dialog. System Action: OMEGAMON II for Mainframe Networks continues operation. User Response: Gather up to the preceding 30 minutes of the RKLVLOG and any dumps that were produced, and contact IBM Software Support. Message Type: Internal error. KONPN017 V500 PRODUCT CONVERSION COMPLETE Explanation: During product initialization, OMEGAMON II for DB2 detected the use of a previous version administrator's monitoring options and converted them. System Action: Administrator's monitoring options were converted. Message Type: Confirmation. KONPN018 V500 USER CONVERSION COMPLETE FOR user_id Explanation: During user initialization, OMEGAMON II for Mainframe Networks detected the use of a previous version user response time table and converted it. System Action: User response time table was converted. Message Type: Confirmation. 88 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

89 KONPN020 KONPN021 KONPN022 KONPN023 OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - APF AUTHORIZATION FAILED Explanation: OMEGAMON II for Mainframe Networks is not running with APF-authorization. System Action: OMEGAMON II for Mainframe Networks fails to initialize and shuts down. User Response: Verify that each library in the STEPLIB concatenation for OMEGAMON II for Mainframe Networks is APF-authorized. Message Type: Probable user error. OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - INVALID VTAM LEVEL DETECTED Explanation: OMEGAMON II for Mainframe Networks was started under an unsupported release of VTAM. System Action: OMEGAMON II for Mainframe Networks fails to initialize and shuts down. User Response: Contact IBM Software Support to order the proper maintenance for your VTAM release. Message Type: Probable user error. OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - UNABLE TO OPEN CNM ACB. ACBERFLG(acberr_name) Explanation: OMEGAMON II for Mainframe Networks was unable to open the ACB used for communication network management (CNM) communication with VTAM. acberr_name contains the contents of the ACBERFLG field of the ACB, in hexadecimal. System Action: OMEGAMON II for Mainframe Networks fails to initialize and shuts down. User Response: Look up the meaning of acberr_name in the IBM publication VTAM Programming. The following are some common values for acberr_name: 58 APPLID is already opened by another ACB. 5A APPLID is not defined to VTAM. Verify that the major node containing the APPL statement referenced in RKANPAR(KONCNMAP) has been varied active to VTAM. Correct the problem as indicated, and contact IBM Software Support. Message Type: Probable user error. OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - UNABLE TO ACTIVATE PMI EXIT. ERROR(pmi_error) Explanation: OMEGAMON II for Mainframe Networks was unable to activate the Performance Monitor Interface exit in a VTAM 4.3 environment. pmi_error contains the error code as indicated by VTAM in the IST985I message. System Action: OMEGAMON II for Mainframe Networks fails to initialize and shuts down. KONCV001 KXDFC012 89

90 User Response: Look up the meaning of pmi_error in the IBM publication VTAM Message and Codes. A common value for pmi_error is 20 Unable to load the exit module. Verify that the OMEGAMON II for Mainframe Networks load library is part of the VTAMLIB concatenation within the VTAM start-up JCL. For other values of pmi_error, contact IBM Software Support. Message Type: Probable user error. KONPN024 OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - RC(return_code) SC(sense_code) Explanation: OMEGAMON II for Mainframe Networks initialization failed. return_code is the return code from the initialization process; sense_code is the sense code. System Action: OMEGAMON II for Mainframe Networks fails to initialize and shuts down. Message Type: Internal error. KONPN025 KONPN026 KONPN027 NCP GLOBAL OPTIONS TABLE CONVERSION COMPLETE Explanation: During initialization, OMEGAMON II for Mainframe Networks converted the NCP global options table for use with the user-specified NCP topology update interval feature. This message is issued one time to confirm the conversion. Message Type: Confirmation. THE TREND RECORDING INTERVAL (interval) IS LESS THAN THE NCP COLLECTION INTERVAL (interval). TREND RECORDING FOR NCP RESOURCES HAS BEEN DISABLED. Explanation: The NCP trend recording interval must be greater than or equal to the NCP collection interval. At OMEGAMON II for Mainframe Networks initialization, NCP trend recording is disabled if the NCP collection interval is greater than the global trend recording interval. System Action: NCP trend recording is disabled. User Response: Use the Global Monitoring Options panel to increase the trend recording interval to a value greater than or equal to the NCP collection interval and then re-enable the NCP trend recording option, or use installation and configuration assistance tool reconfiguration option to decrease the NCP collection interval to a value less than or equal to the trend recording interval. Decreasing the NCP collection interval requires a restart of OMEGAMON II for Mainframe Networks. Message Type: User specification error. OMEGAMON II for Mainframe Networks STACK ERROR DETECTED Explanation: An error was detected either releasing or obtaining stack storage. System Action: The task abends with a system dump. 90 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

91 KONPN028 User Response: Log the diagnostic information and contact IBM Software Support Message Type: Internal error. OMEGAMON II for DB2 FOR VTAM EXTERNAL FUNCTION LEVEL SECURITY ENABLED Explanation: OMEGAMON II for Mainframe Networks is configured to use an external security package to control access to certain product functions. Message Type: Confirmation. KONCV001 KXDFC012 91

92 KONPN029 OMEGAMON II for DB2 FOR VTAM INTERNAL FUNCTION LEVEL SECURITY ENABLED Explanation: OMEGAMON II for Mainframe Networks is configured to use an internal facility to control access to certain product functions. Message Type: Confirmation. KONPN030 MEMBER mbr_name NOT FOUND IN RKANPAR Explanation: An error occurred during the configuration of external function level security. System Action: Initialization continues using internal facilities to control access to product functions. User Response: Review configuration steps for function level security. If the problem cannot be resolved, contact IBM Software Support. Message Type: Error. KONSD001 SDM LOGON INITIATED FOR PRODUCT(SDM_product) SESSION(SDM_session_name) SDMAPPL(SDM_applid) SYSTERM(SDM_luname) REFRESH(SDM_refresh_interval) TRIGGER(SDM_hot_key) Explanation: A message indicating an SDM (Status Data Manager) session has been established between an SDM product (OMEGAVIEW or Status Monitor) and OMEGAMON II for Mainframe Networks. The parameters have the following meaning: SDM_product SDM_session_name SDM_applid SDM_luname SDM_refresh_interval SDM_hot_key System Action: User Response: Message Type: Product that establishes the SDM session: OMEGAVIEW or Status Monitor. Name assigned to this session by the SDM product. Applid defined in the SDM product with which OMEGAMON II for Mainframe Networks can establish a session to emit SDM status to the SDM product. Name of LU that has established the session with OMEGAMON II for Mainframe Networks. Auto-update interval requested by the SDM product. Key used to return to the SDM. None. None. Information. 92 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

93 KONSD002 ERROR PROCESSING AN SDM FUNCTION IN DIALOG calling_dialog APPL(SDM_application) SESSION(SDM_session_name) FUNCTION(SDM_function_name) STATUS_ITEM(SDM_status_item) RC(return_code) Explanation: A generalized message generated only when there is a non-zero return code from an SDM function call. The parameters have the following meaning: KONSD003 KQM0001 KQM0002 KQM0003 calling_dialog SDM_application SDM_session_name SDM_function_name SDM_status_item return_code OMEGAMON II for Mainframe Networks dialog that calls this SDM function. Applid defined in the SDM product with which OMEGAMON II for Mainframe Networks established the session to emit SDM status to the SDM product. Name assigned to this session by the SDM product. SDM function requested. One of the status light items to be emitted to the SDM product, such as the CTC TNSTATS light or the NCP TNSTATS light. Return code from the SDM function. System Action: The SDM session was not established, but OMEGAMON II for Mainframe Networks continues to operate. User Response: Make sure that the SDM definitions are correct according to the OMEGAMON II for Mainframe Networks Configuration and Customization Guide and the customization guide for OMEGAVIEW or Status Monitor (depending on the product installed). Message Type: Probable user error. [ENHANCED] [ORIGINAL] ZOOM ACTIVATED Explanation: The OMEGAVIEW enhanced or original zoom function has been activated. Message Type: Information. FTO started at &1. Explanation: FTO started. Severity: 40 System Programmer Response:No FTO ended at &1. Explanation: FTO Hot-Standby ended. Severity: 40 System Programmer Response:No FTO connected to &1 at &2. Explanation: FTO is trying to connect to the parent CMS. Severity: 40 System Programmer Response:No KONCV001 KXDFC012 93

94 KQM0004 KQM0005 KQM0006 KQM0007 KQM0008 KQM0009 KQM0010 KQM0011 KQM0012 KOS101I FTO detected lost parent connection at &1. Explanation: FTO/HotStandby has lost connection. Severity: 40 System Programmer Response:No FTO has recovered parent connection at &1. Explanation: FTO/HotStandby recovered lost parent connection. Severity: 40 System Programmer Response:No FTO inserted &1 with id &2 at &3. Explanation: FTO inserted object with key. Severity: 40 System Programmer Response:No FTO updated &1 with id &2 at &3. Explanation: FTO updated object with key. Severity: 40 System Programmer Response:No FTO deleted &1 with id &2 at &3. Explanation: FTO deleted object. Severity: 40 System Programmer Response:No FTO promoted &1 as the acting HUB. Explanation: FTO promoted the CMS as the HUB. Severity: 40 System Programmer Response:No FTO detected a manual switch at &1. Explanation: FTO detected a manual switch. Severity: 40 System Programmer Response:No &1. Explanation: Some general FTO information. Severity: 40 System Programmer Response:No FTO routing node &1 to the parent CMS. Explanation: FTO is rerouting a CMS or an IRA to another CMS. Severity:40 System Programmer Response:No CMS cmsname IS NOW THE SYSPLEX PROXY Explanation: The CMS indicated by cmsname has become the Sysplex Proxy. A CMS becomes the Sysplex Proxy in one of two scenarios: during startup, when designated (during product configuration) as the Primary Sysplex Proxy. 94 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

95 KRCXSY01 KRCXSY02 KRCXSY03 KRCXSY04 KRCXSY05 during recovery, when designated as a Backup Sysplex Proxy and the current Sysplex Proxy CMS fails. System Action: This message appears in the CMS RKLVLOG. Notification can also be sent to the MVS console, enabling access by automated operations tools. User Response: Take whatever action is necessary when the Sysplex Proxy function is assigned, or reassigned, to a CMS. System Programmer Response: PRIMARY SERVER NOT FOUND IN PROFILE Explanation: A server designated as the primary server could not be found in the server s member of the profile. This message may indicate that the primary=yes statement in the profile has been removed or is syntactically incorrect. User Response: Verify that the server profile contains the primary=yes statement or correct any syntax problems with the statement. You will not be able to log on to OMEGAMON II unless you designate a primary server in the profile or specify a remote server ID. Destination: The CT/Engine log, RKLVLOG. R c PACKAGE NOT FOUND Explanation: A global anchor could not be found during product initialization. This indicates an internal problem with OMEGAMON II for SMS. Destination: The CT/Engine log, RKLVLOG. SQL1 REQUEST SQL1_CreatePath SUCCESSFUL FOR sssss SQL1 STATUS ddd(xx) Explanation: This message informs you that you have successfully connected to server sssss Destination: The CT/Engine log, RKLVLOG. SQL1 REQUEST rrrrr FAILED FOR sssss SQL1 STATUS ddd(xx) Explanation: The server failed to respond to the specified request. This message may indicate that OMEGAMON II is experiencing problems connecting to the server. User Response: Check the availability of the server to which you are attempting to connect. Try to reconnect when the server becomes available using the Specify Systems for Cross-system Monitoring panel within an OMEGAMON II session. Destination: The CT/Engine log, RKLVLOG. COULD NOT CONNECT TO PRIMARY SERVER Explanation: The Create_Path to the primary server failed. This message will be preceded by a KRCXSY04 message when the Create_Path was issued. KONCV001 KXDFC012 95

96 KRCXSY06 KS3C001E KS3C002E KS3C003E KS3D001E User Response: Check the availability of the primary server. It may not have completed initialization or may have abended. Restart the server if it has abended. You will not be able to log on to OMEGAMON II unless you designate a primary server in the profile or specify a remote server ID. Destination: The CT/Engine log, RKLVLOG. rnode: {LOCALID= locname REMOTEID= remname MODE= logmode} snode: {SERVER= srvrname USER= xsys} Explanation: This message displays the path string used to log on to a specified data server. This information is derived from the configuration data in the profile and is useful in determining server connection problems. Destination: The CT/Engine log, RKLVLOG. modname Unable to acquire the address of the S3 PDS work area Explanation: Allocation of the PDS work area normally takes place when the Candle Management Server is initialized. However, the vector which should point to this area contains zeros. Possible values for modname include KS3CPLCU and KS3CPCHP. System Action: Historical data for Logical Control Units (LCU) will not be written to the Persistent Data Stores until this situation is corrected. User Response: Check for message KS3D002E in the RKLVLOG. If found, take the recommended actions. Otherwise, contact IBM Software Support. Destination: The CT/Engine log, RKLVLOG. KS3CPLCU Unable to allocate memory for PDSRec Explanation: The LCU historical retriever was unable to allocate sufficient CT/Engine storage for a work area. System Action: Historical data for Logical Control Units (LCU) will not be written to the persistent Data Stores until this situation is corrected. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the Candle Management Server startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. KS3CIHUB: InsertNodeAtHub call returned with return code Explanation: Module KS3CIHUB issued an InsertNodeAtHubExtended call and received a non-zero return code. A request was made for a date/time for which there is not an applicable record available. System Action: OMEGAMON XE for Storage continues without returning historical data for this request. User Response: To increase the amount of historical data available, it may be necessary to expand the Persistent Data Store. Destination: The CT/Engine log, RKLVLOG. modname : UNABLE TO FIND OM2SMVCT Explanation: This is an inernal error. 96 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

97 KS3D002E Possible values for modname include: KS3CHUB KS3DINIT System Action: Most storage monitoring functions will be disabled. Destination: The CT/Engine log, RKLVLOG. KS3DINIT : ALLOCATION FAILED FOR S3VECTOR: SIZE=size, RC=rc Explanation: An attempt to allocate storage for the S3 vector table failed. Possible values for size are release/maint_level dependent and cannot be adjusted using RKANPAR. Possible values for rc are as follows: 1 There is not enough storage available. 2 The size of the vector table exceeds the LIMIT value. 3 The size of the vector table has been determined to be zero. 4 Storage quiesce mode is in effect. KS3D003W KS3D004E System Action: Storage monitoring in CNP will be disabled. Destination: The CT/Engine log, RKLVLOG. KS3DINIT : UNABLE TO LOAD modname Explanation: A load failed for the named module. Possible values for modname include: KS3DPSUM KS3DPCCU KS3CPLCU KS3DPLCU KS3DPCHP System Action: Most of the modules named by this message are used to gather data to be written to the Persistent Data Store for historical reporting. Data associated with the module named in this message will not be written to the PDS until the problem is corrected. Destination: The CT/Engine log, RKLVLOG. UNABLE TO FIND SE VECTOR Explanation: This is an internal error. System Action: Most storage monitoring functions will be disabled for the CandleNet Portal. Destination: The CT/Engine log, RKLVLOG. KONCV001 KXDFC012 97

98 KS3D005W KS3D006E KS3D007I KS3D008E KS3D009E KS3D010W KS3DINIT : ALLOCATION FAILED FOR APPWORK Explanation: An attempt to allocate storage for the application work area has failed. System Action: Application monitoring will be disabled. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size, if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. KS3CINIT - UNABLE TO FIND OPERATOR RESOURCE Explanation: An attempt to locate the operator logical resource failed. System Action: The OMEGAMON XE for Storage node will not be able to register with the hub CMS. Destination: The CT/Engine log, RKLVLOG. KS3CINIT - PROCESSING Explanation: This is an informational message indicating that the CMS initialization routine is executing. System Action: OMEGAMON XE for Storage CMS initialization has commenced. This message is informational. Destination: The CT/Engine log, RKLVLOG. modname: - pds table RECORDING DISABLED - reason Explanation: Module modname has detected a problem while attempting to write historical data. Historical recording for the table pds table has been disabled due to the given reason. System Action: OMEGAMON XE for Storage continues without recording historical data for the given table. Destination: The CT/Engine log, RKLVLOG. modname: - SETUP FAILED FOR pds table INSERTS; RC = rc Explanation: Module modname has detected a problem while attempting to setup the table pds table. The setup call returned with a return code of rc. System Action: OMEGAMON XE for Storage continues without recording historical data for the given table. Message Type: The CT/Engine log, RKLVLOG. modname: - pds table RECORDING SKIPPED THIS INTERVAL - reason Explanation: Module modname has found no entries to write to the PDS table pds table. Further information is provided by the reason. System Action: OMEGAMON XE for Storage continues without recording historical data for the given table for this interval. User Response: If this message persists, contact IBM Software Support. An occurrence of this message during product initialization could be normal. Destination: The CT/Engine log, RKLVLOG. 98 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

99 KS3D011E modname: - INSERT FAILED FOR pds table TABLE INSERT; RC = rc -- RECORDING TERMINATING FOR THIS INTERVAL Explanation: Module modname has received return code rc while attempting to write a record to PDS table pds table. System Action: OMEGAMON XE for Storage continues without recording historical data for the given table for the current interval. User Response: If this message persists, contact IBM Software Support. An occurrence of this message during product initialization could be normal. Destination: The CT/Engine log, RKLVLOG. KS3D012W modname: - RMF SYNCHRONIZATION FAILED - RECORDING INTERVAL DEFAULTING TO 15 MINUTES Explanation: Module modname has not been able to synchronize historical recording with the RMF interval. System Action: OMEGAMON XE for Storage continues; however, the recording interval for historical recording is set to 15 minutes. User Response: If this message persists and RMF monitor 1 is active contact IBM Software Support. Destination: The CT/Engine log, RKLVLOG. KS3D013E modname: ALLOCATION FAILED FOR item, SIZE = size,rc = return code Explanation: Module modname was unsuccessful in obtaining size number of bytes of storage to allocate the control block item. The request failed with return code return code. System Action: OMEGAMON XE for Storage continues; PDS recording for this interval is skipped. Destination: The CT/Engine log, RKLVLOG. KS3L006E modname Unable to acquire view storage Explanation: The probe modname has failed to acquire storage to complete a request for data. System Action: No information will be retrieved for this request. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. KS3L007E modname Unable to acquire address/size of Application Table Explanation: A call to program KS3CGAT has returned with a non-zero return code. The call originated from module modname. System Action: All application monitoring will fail. User Response: This is an internal error and should be reported to IBM Software Support immediately. Destination: The CT/Engine log, RKLVLOG. KONCV001 KXDFC012 99

100 KS3L008E KS3L009E KS3L010E KS3L011E KS3L012E Unable to allocate storage for new application entry Explanation: An attempt to add an application for monitoring has failed because there is insufficient CT/Engine storage available. System Action: The requested application will not be added to the list of monitored applications. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. Unable to acquire ASID work area of nnnnnnn bytes Explanation: An application monitoring request has failed because there is insufficient CT/Engine storage available. nnnnnnn indicates the number of bytes requested. System Action: All application monitoring will fail. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. modname Unable to acquire address of Application Name Table Explanation: A call to program KS3CGPTR has failed. The call originated from module modname. Possible values for modname include KS3LAPPL and KS3DAPCL. System Action: All application monitoring will fail. User Response: This is an internal error and should be reported to IBM Software Support immediately. Destination: The CT/Engine log, RKLVLOG. KS3LAPPL Unable to allocate storage for the Application Name Table Explanation: An attempt to allocate storage from the CT/Engine pool was unsuccessful. System Action: Application monitoring will not be available in the CandleNet Portal. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIB RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. modname Unable to allocate nnnn bytes storage for xxx volume dataset work table Explanation: An attempt to allocate storage from the CT/Engine pool was unsuccessful. Possible values for modname include KS3LAPDD and KS3LAPVP. nnnn xxx number indicating the size of the attempted storage allocation number of volumes or datasets to be contained in the table 100 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

101 KS3L014E KS3L015E KS3L016E KS3L017E System Action: Application monitoring dataset and volume details information will be unavailable until the problem is corrected. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. modname Invalid or missing WHERE clause Explanation: An SQL request was received that requires a WHERE clause, but none was found. Possible values for modname include: KS3LAPDD KS3LAPVP KS3LAPVS System Action: This SQL request will fail. User Response: If you have modified the Candle supplied SQL, be sure you still have a valid WHERE clause. Otherwise, contact IBM Software Support. Destination: The CT/Engine log, RKLVLOG. modname Unable to allocate storage for node table Explanation: An attempt to allocate storage from the CT/Engine pool was unsuccessful. Possible values for modname include KS3LXSUM and KS3LXSYS. System Action: Cross-system DASD monitoring will be unavailable in CandleNet Portal until the problem is corrected. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. modname Unable to allocate storage for volume table Explanation: An attempt to allocate storage from the CT/Engine pool was unsuccessful. Possible values for modname include KS3LXSUM and KS3LXSYS. System Action: Cross-system DASD monitoring will be unavailable in CandleNet Portal until the problem is corrected. User Response: Increase the value specified in the MINIMUM parameter of the KDSSYSIN RKANPAR member. This may also require an increase in region size if the CMS startup proc does not specify REGION=0M. Destination: The CT/Engine log, RKLVLOG. modname: - REQUEST FOR HISTORICAL DATA FAILED - reason Explanation: Module modname has detected a problem while attempting to retrieve historical data. The retrieval of historical data is unsuccessful due to the given reason. System Action: OMEGAMON XE for Storage continues without returning historical data. Destination: The CT/Engine log, RKLVLOG. KONCV001 KXDFC

102 KS3L018E KS3L019E KSDCY010E KSDCY011E KSDCY012E KSDDM001E KSDDM002E KSDDM003E modname: FETCH FAILED FOR pds table TABLE; RC = return code -- DATA RETRIEVAL FROM PDS TERMINATING Explanation: Module modname received return code return code when attempting to retrieve data from the historical table pds table. System Action: OMEGAMON XE for Storage continues without returning historical data. Message Type: The CT/Engine log, RKLVLOG. modname: INVALID pds table RECORD DETECTED, HEADER = header Explanation: Module modname retrieved a record from historical table pds table and found the heading information to be invalid. The invalid data, header, is printed as part of the message. System Action: OMEGAMON XE for Storage continues without returning historical data. Message Type: The CT/Engine log, RKLVLOG. SHORT ON STORAGE CONDITION ENCOUNTERED. OG ALERT NOT SENT. FOR STATUS ITEM item Explanation: Short-on-storage condition encountered. System Action: OG alert not sent. Message Type: Internal error. 1PSIMDATA => data Message Type: Internal error. 1PSIMPARM => parm Message Type: Internal error. SDMBLDN RETURNED, RC= return_code Explanation: Error returned from SDMBLDN request. System Action: Request terminated. Message Type: Internal error. CREATESTATUS RULECOMPILER RETURNED, RC= return_code Explanation: Error returned from rule compiler for a CreateStatus request. System Action: Request terminated. Message Type: Internal error. KSD_NEWXATTRSSPL ERROR RC= return_code Explanation: Error returned when requesting new attribute for item. System Action: Request terminated. 102 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

103 KSDDM004E KSDDM005E Message Type: Internal error. KSD_RECONCILEPARENTS ERROR RC= return_code Explanation: Error encountered when reconciling parents of item. System Action: Request terminated. User Response: Contact IBM Software Support Message Type: Internal error. KSD_DELXATTRSSPL ERROR RC= return_code Explanation: Error encountered when deleting attribute of item. System Action: Request terminated. User Response: Contact IBM Software Support Message Type: Internal error. KONCV001 KXDFC

104 KSDDM006E KSDDM007E KSDDM008E KSDDM009E KSDDM010E KSDDM011E KSDDM012E KSDDM013E KSD_NEWXATTRVBB ERROR RC= return_code Explanation: Error encountered when adding attribute to item. System Action: Request terminated. Message Type: Internal error. KSD_DISOWNCHILDREN ERROR RC= return_code Explanation: Error encountered when disconnecting children from item. System Action: Request terminated. Message Type: Internal error. KSD_RECONCILECHILDREN ERROR RC= return_code Explanation: Error encountered when reconciling children of item. System Action: Request terminated. User Response: Contact IBM Software Support Message Type: Internal error. KSD_DISOWNPARENTS ERROR RC= return_code Explanation: Error encountered when disconnecting parents from item. System Action: Request terminated. User Response: Contact IBM Software Support Message Type: Internal error. KSD_RECONCILEPARENTS ERROR RC= return_code Explanation: Error encountered when reconciling parents of item. System Action: Request terminated. User Response: Contact IBM Software Support Message Type: Internal error. KSD_DELXATTR() ERROR RC= return_code Explanation: Error encountered when deleting attribute of item. System Action: Request terminated. Message Type: Internal error. KLE_TABLEMODIFY ERROR RC= return_code FOR STATUS ITEM item Explanation: Error encountered from TableModify request. System Action: Request terminated. Message Type: Internal error. DIALOG dialog FAILED, RC= return_code Explanation: Error occurred during the execution of the named dialog. System Action: Execution of the dialog is terminated. Message Type: Internal error. 104 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

105 KSDIN001I KSDIN002I KSDVS001I KSDVS002E KSDVS003E KSDVS004E KSDVS005E KSDVS005I PRINT PARENTS OF CHILD child Explanation: These are the parents of the specified child. Severity: Information. CHILD child PARENT parent Explanation: This is the specified child and parent. Message Type: Information. VARNAME variable VARVALUE value Explanation: This is the name of the variable and its value. Message Type: Information. ALLOC PCT-STR FAILED Explanation: Allocation of the PCT string failed. System Action: Request terminated. User Response: Contact IBM Software Support Message Type: Internal error. ALLOC COLUPDAT FAILED Explanation: Allocation of the column update failed. System Action: Request terminated. Message Type: Internal error. ALLOC VARVALUE FAILED Explanation: Allocation of the variable value failed. System Action: Request terminated. Message Type: Internal error. REFRESHDM STATUS status VARNAME name VARVALUE value Explanation: These are the refresh data manager values. Message Type: Request terminated. Message Type: Internal error. PRINT VALUES FROM VBB Explanation: These are the values from the VBB. Message Type: Information. KONCV001 KXDFC

106 KSDXA001I KSDXA002E KSDXA003E KSDXA004E KSDXA005E KSDXA006E KSDXA007E KSDXA008E PRINT XATTR OBJECT Explanation: These are the attributes of the object. Message Type: Information. KSD_NEWXATTRVBB ERROR RC=return_code Explanation: Error encountered when adding attribute of item. System Action: Request terminated. Message Type: Internal error. KSD_DISOWNCHILDREN RC= return_code Explanation: Error encountered when disconnecting children from item. System Action: Request terminated. Message Type: Internal error. KSD_RECONCILECHILDREN RC= return_code Explanation: Error encountered when reconciling children of item. System Action: Request terminated. Message Type: Internal error. KSD_DISOWNPARENTS RC= return_code Explanation: Error encountered when disconnecting parents of item. System Action: Request terminated. Message Type: Internal error. KSD_RECONCILEPARENTS RC= return_code Explanation: Error encountered when reconciling parents of item. System Action: Request terminated. Message Type: Internal error. KSD_DELXATTR() ERROR RC= return_code Explanation: Error encountering when deleting attribute of item. System Action: Request terminated. Message Type: Internal error. INVALID RULE COLUMN NAME, RC= return_code Explanation: Problem when specifying rule of specific roll-up item. System Action: Item not matched. Message Type: Internal error. 106 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

107 KSDXA009E KXDFC001 KXDFC002 KXDFC003 KXDFC004 KXDFC005 ERROR IN RULE TEXT, RC= return_code Explanation: Problem when specifying rule of specific roll-up item. System Action: Item not matched. Message Type: Internal error. CF-XCF COLLECTION INITIALIZING Explanation: The CF-XCF collection task is initializing. System Action: Normal processing continues. CF-XCF SHUTDOWN COMPLETE Explanation: The CF-XCF collection task has stopped. System Action: Normal processing continues. COUPLING FACILITY NOT PRESENT RC(rc1,rc2), REASON CODE(reason). Explanation: A problem was encountered while attempting to gather data from the coupling facility, the error is further defined by rc1, rc2, and reason. System Action: No coupling facility data is gathered. User Response: 1. If a coupling facility is not attached to the system then no further action is necessary. 2. If a coupling facility is present then investigate possible reasons why the current MVS image cannot access the coupling facility. If necessary note the contents of the message and contact IBM Software Support. XCF DATA ERROR ON MACRO macronum, RC(rc), REASON CODE(reason). Explanation: An error occurred while executing an XCF macro. The specific macro is identified by macronum and the error is further defined by rc and reason. System Action: Snap dumps of the internal workarea and the collection vector table are produced, no XCF data is gathered. User Response: Note the contents of the message and contact IBM Software Support. COUPLING FACILITY DATA ERROR RC(rc), REASON CODE(reason). Explanation: An error occurred while executing a coupling facility macro, the error is further defined by rc and reason. System Action: Snap dumps of the internal workarea, the collection vector table, and the answer area are produced, no coupling facility data is gathered. User Response: Note the contents of the message and contact IBM Software Support. KONCV001 KXDFC

108 KXDFC006 KXDFC007 KXDFC008 DATA ERROR ON MACRO macronum, RC(rc), REASON CODE(reason). Explanation: An error occurred while executing a data collection macro. The specific macro is identified by macronum and the error is further defined by rc and reason. System Action: Snap dumps of the internal workarea, the collection vector table, the answer area, and the current member area are produced, no data is gathered. User Response: Note the contents of the message and contact IBM Software Support. XCF MEMBER COUNT UNMATCHED, GROUP(group_name), COUNTS(new_count,old_count). Explanation: The number of members of the XCF group identified by group_name has changed from new_count to old_count. System Action: Normal processing continues. ERROR(error_id.), PROCESSING CF COLLECTION REQUEST. {RC(rc), REASON CODE(reason).} Explanation: An error occurred while collecting Coupling Facility data. The error_id can be one of the following: 1. The collector work area could not be located 2. The CFCV table failed a validity check 3. An internal I/O counter has overflowed 4. An internal table has overflowed Each of the above errors may be further defined by rc and reason. System Action: Depending on the error_id a snap dump may be produced. Coupling facility data collection is terminated. User Response: Note the contents of the message and contact IBM Software Support. KXDFC009-caller_id OVERFLOW IN AVERAGE REQUEST TIME INTERVAL CALCULATION. Explanation: An overflow condition occurred while calculating an average time interval. The caller_id identifies the caller of the calculation routine. System Action: Snap dumps of the parameters, and the old and the new answer areas are produced, the data gathered during this interval is ignored. User Response: Note the contents of the message and contact IBM Software Support. KXDFC011 GMEM(count) LEN(length), ADR(xxxxxxxx). Explanation: A getmain request failed. length indicates the requested length of the storage, xxxxxxxx is the address where the address of the getmained storage is to be placed, count is a sequential value that is incremented by each getmain and decremented by each freemain. System Action: The getmain request is terminated. User Response: If this message recurs attempt to discover the reason for the getmain failure, otherwise contact IBM Software Support. 108 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

109 KXDFC012 FMEM(count) AT(xxxxxxxx). Explanation: A freemain request failed. xxxxxxxx is the address of the storage to be freed, count is a sequential value that is incremented by each getmain and decremented by each freemain. System Action: The freemain request is terminated. User Response: If this message recurs contact IBM Software Support. The started task should be recycled at the earliest opportunity to free any orphaned storage. KONCV001 KXDFC

110 110 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

111 2 LAT000 MRG999 LAT000 LAT005 LSCX* ML0000 ML0001 ML0002 EPILOG/IMS WILL NOT COLLECT LATCH STATISTICS - ERROR Explanation: The EPILOG collector module that gathers IMS latch statistics found an incorrect value for the number of latch types in an IMS control block. System Action: The EPILOG collector does not gather latch statistics. User Response: Call IBM Software Support. EPILOG/IMS WILL NOT COLLECT LATCH STATISTICS - ERROR Explanation: See message LAT000. System Action: See message LAT000. User Response: See message LAT000. (message text varies) Explanation: SAS/C generates messages that have LSCX prefixes. MLOG COMMAND SYNTAX ERROR Explanation: The MLOG command entered is invalid. System Action: OMEGAMON ignores the command. User Response: Correct the error and reissue the MLOG command. MESSAGE LOGGING FACILITY IS ACTIVE Explanation: OMEGAMON received an MLOG START command to activate the message logging facility. MESSAGE LOGGING FACILITY IS INACTIVE Explanation: The message logging facility is inactive. User Response: Issue the MLOG START command to activate the message logging facility. LAT000 MRG

112 ML0003 ML0005 ML0006 ML0008 ML0009 ML0010 ML0011 SYSOUT CLASS=c Explanation: The message logging facility is active and currently recording to SYSOUT class displayed in the message. SYSOUT class * indicates the default message class. RECORDS LOGGED SINCE LAST FLUSH: nnnn Explanation: The message logging facility has written nnnn records since start-up or since the last MLOG FLUSH. CURRENT RECORD FLUSH THRESHOLD: nnnn. Explanation: The message logging facility will flush the current sysout dataset after recording nnnn records. System Action: After nnnn records, the current SYSOUT file is flushed. NO STORAGE AVAILABLE FOR THE MESSAGE MERGE TABLE Explanation: The message logging facility could not allocate the merge message table for the message merge task. System Action: The message logging facility is not started. User Response: Restart OMEGAMON specifying a larger region. UNABLE TO SERVICE YOUR REQUEST AT THIS TIME Explanation: The MLOG command could not be executed due to serialization problems. System Action: The command is ignored. User Response: Retry the command. If this problem persists, call IBM Software Support. MESSAGE LOGGING FACILITY START REJECTED Explanation: The MLOG START command was issued, but the message logging facility was already started, start-up was in progress, or shutdown was in progress. System Action: OMEGAMON ignores the request. User Response: Wait for the current message logging facility state to change. MESSAGE LOGGING FACILITY STARTUP PENDING Explanation: The MLOG START command was issued, and the message logging facility is in start-up processing. System Action: The message logging facility continues start-up processing. 112 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

113 ML0012 ML0020 ML0021 ML0022 ML0030 ML0031 ML0032 ML0099 MESSAGE LOGGING FACILITY STARTUP QUEUED Explanation: The MLOG START command was issued, and was accepted by OMEGAMON. System Action: Message logging facility start-up is attempted. MESSAGE LOGGING FACILITY STOP REJECTED Explanation: The MLOG STOP command was issued, but the message logging facility is already inactive or shutdown processing is in progress. System Action: OMEGAMON ignores the request. User Response: Wait until the state of the message logging facility changes. MESSAGE LOGGING FACILITY SHUTDOWN PENDING Explanation: The MLOG STOP command was issued, and the message logging facility is in shutdown processing. System Action: The message logging facility continues shutdown processing. MESSAGE LOGGING FACILITY SHUTDOWN QUEUED Explanation: The MLOG STOP command was issued, and was accepted by OMEGAMON. System Action: Message logging facility shutdown is attempted. MESSAGE LOGGING FACILITY FLUSH REJECTED Explanation: The MLOG FLUSH command was issued, but the message logging facility is inactive, or is in start-up, shutdown, or flush processing. System Action: OMEGAMON ignores the request. User Response: Wait for the current message logging facility state to change. MESSAGE LOGGING FACILITY FLUSH PENDING Explanation: The MLOG FLUSH command was issued, and the message logging facility is in flush processing. System Action: The message logging facility continues with flush processing. MESSAGE LOGGING FACILITY FLUSH QUEUED Explanation: The MLOG FLUSH command was issued and was accepted by OMEGAMON. System Action: The message logging facility initiates flush processing. MESSAGE LOGGING FACILITY ERROR. CODE: nnnn Explanation: The message logging facility has encountered a severe error. System Action: The message logging facility terminates. User Response: Call IBM Software Support. LAT000 MRG

114 MLG040 MLG041 MLG042 MLG043 MLG044 VSAM MESSAGE LOG DATASET SWITCH IN PROGRESS Explanation: The current Message Log VSAM dataset is full. An automatic switch to the second VSAM dataset is occurring. System Action: The dataset switch proceeds. This is an informational message only. ERROR DURING TYPE T CLOSE, VSAM MESSAGE LOGGING INTEGRITY COMPROMISED Explanation: An unexpected return code was received from a VSAM type T close of the current Message Log dataset. As a result, the CUA Interface console screen may not see all the current messages. User Response: The most likely cause of this problem is a VSAM error or an error in the VSAM definition of the dataset. If you cannot locate the cause of the problem, contact IBM Software Support. VSAM MESSAGE LOGGING ACTIVE Explanation: Either the VSAM Message Logging has been started or the switch of VSAM datasets has been completed. VSAM MESSAGE LOG DYNAMIC ALLOCATION FAILED Explanation: OMEGAMON was unable to dynamically allocate the VSAM Message Log dataset specified in the KI2VSM00 member or via the MODIFY MERGE Interface command. System Action: VSAM Message Logging terminates. User Response: Verify that the name specified in the DSN= parameter of the MODIFY MERGE command that was either entered on the console or via an EXEC Interface command is correct. It must match the high level qualifier of the dataset name used by the IDCAMS utility in the KI2CUAIN JCL member of rhilev.midlev.rkanpar. If the name is correct, verify that the dataset is available on which OMEGAMON for IMS is executing. VSAM MESSAGE LOG I/O ERROR Explanation: An unexpected return code was received from VSAM during open processing of a VSAM Message Logging dataset. System Action: VSAM Message Logging terminates. User Response: Determine the cause of the error. The most probable causes are VSAM errors or an error in the VSAM definition of the dataset. If you cannot locate the cause of the problem, contact IBM Software Support. 114 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

115 MLG045 MLG046 MLG047 MLG048 MRG001 MRG024 VSAM MESSAGE LOGGING TERMINATED DUE TO LACK OF LOG DATASETS Explanation: VSAM Message Logging is unable to continue processing as there are no initialized VSAM Message Log datasets available for use. System Action: VSAM Message Logging terminates. User Response: Initialize the VSAM Message Log datasets by running either the KI2CUAIN JCL member of rhilev.midlev.rkanpar or the KI2ARCH.n. JCL members in your system procedure library and then start VSAM Message Logging again. VSAM MESSAGE LOG OPEN ERROR Explanation: An unexpected return code was received from VSAM when opening the VSAM Message Log dataset. System Action: VSAM Message Logging terminates. User Response: Determine the cause of the error. The most probable causes are VSAM errors or an error in the VSAM definition of the dataset. If you cannot locate the cause of the problem, contact IBM Software Support. VSAM MESSAGE LOGGING PUT ERROR Explanation: An unexpected return code was received from VSAM during the execution of a PUT to the VSAM Message Log dataset. System Action: VSAM Message Logging terminates. User Response: Determine the cause of the error. The most probable causes are VSAM errors or an error in the VSAM definition of the dataset.if you cannot locate the cause of the problem, contact IBM Software Support. VSAM MESSAGE LOGGING ENDREQ FOR RPL FAILED Explanation: During close processing of the VSAM Message Log dataset, an unexpected return code was received from VSAM following an ENDREQ for the RPL request. System Action: VSAM Message Logging terminates. User Response: Determine the cause of the error. The most probable causes are VSAM errors or an error in the VSAM definition of the dataset. You can attempt to close and deallocate the file by stopping the MERGE task using the STOP ID=MR Interface command. When the file is deallocated, use the IDCAMS utility VERIFY function to ensure that it was closed correctly before attempting to archive the messages. MESSAGE MERGE TASK ALREADY ACTIVE, TERMINATING Explanation: The message merge was already active when a user issued the interface command START MERGE. User Response: Do not attempt to start the merge task when it is already active. MESSAGE MERGE TASK SHUTDOWN COMPLETE Explanation: The message merge task has terminated. LAT000 MRG

116 MRG099 MRG202 MRG203 MRG205 MRG206 MRG999 MESSAGE MERGE TASK TERMINATING DUE TO ERROR Explanation: The message merge task abended due to an unanticipated problem and is in the process of terminating. User Response: The task cleans up all resources and terminates with a dump. Call IBM Software Support. UNABLE TO INITIALIZE LWHA, VSAM MESSAGE LOGGING NOT STARTED Explanation: An internal error occurred when trying to initialize the facility used to extract IMS messages from the MVS and MTO consoles. System Action: VSAM Message Logging cannot be started. GETMAIN OF VSAM MESSAGE LOGGING WORK ARE FAILED Explanation: Insufficient virtual storage was available to perform a GETMAIN for an internal work area for VSAM Message Logging. System Action: VSAM Message Logging cannot be started. User Response: Increase the region size of the OMEGAMON address space. If this fails to resolve the problem, contact IBM Software Support. UNABLE TO INITIALIZE GWHA, VSAM MESSAGE LOGGING NOT STARTED Explanation: An internal error occurred when trying to initialize the facility used to extract IMS messages from the MVS and MTO consoles. System Action: VSAM Message Logging cannot be started. UNABLE TO GETMAIN MRWA, VSAM MESSAGE LOGGING NOT STARTED Explanation: Insufficient virtual storage was available to perform a GETMAIN for an internal work area for VSAM Message Logging. System Action: VSAM Message Logging cannot be started. User Response: Increase the region size of the OMEGAMON address space. If this fails to resolve the problem, contact IBM Software Support. MESSAGE MERGE TASK TERMINATING DUE TO SEVERE ERROR Explanation: The message merge task abended due to an unanticipated problem and is unable to recover. User Response: The task terminates with a dump. Call IBM Software Support. User Response: 116 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

117 3 OB0101 OB9269 OB0101 OB0102 OB0104 OB0106 OB0107 INVALID FIELD DETECTED, INPUT IGNORED Explanation: The cursor was placed on a field which the command processor determined to be invalid. System Action: Processing continues as determined by the particular command. User Response: Make corrections as determined by the particular command. THIS PRODUCT EXPIRES ON mm/dd/yy Explanation: The current product expires on the date displayed. System Action: Command execution continues. User Response: Install a new version of OMEGAMON. If you have not received a new version, contact IBM Software Support..MFY ONLY WORKS IN DEDICATED MODE Explanation: The OMEGAMON session is not in the proper mode. The.MFY command only works in dedicated mode. User Response: Restart OMEGAMON in dedicated mode, or do not attempt to execute this command. keyword KEYWORD VALUE cc INVALID Explanation: The color or highlighting value entered for the specified keyword is not valid. When Display=BASIC, valid keyword values are HI and LO. When Display=COLOR, valid keyword values are any of the seven color names available on terminals that support the extended data stream. System Action: Command execution terminates. User Response: Correct the appropriate keyword value and retry. MAJOR NOT FOUND Explanation: The major command name supplied during a help request was not found. System Action: Command execution terminates. User Response: Correct the major command name and re-enter it. OB0101 OB

118 OB0108 OB0109 OB0110 OB0111 OB0112 OB0113 OB0114 OB0115 OB0116 COMMAND IS NOT A MINOR OF THIS MAJOR Explanation: The major command name supplied during a help request exists, but the minor supplied is not valid for this major. System Action: Command execution terminates. User Response: Correct the minor command name and re-enter. MAXIMUM MESSAGE LENGTH IS 60 CHARACTERS Explanation: An attempt has been made to specify an XTXT message greater than 60 characters. User Response: Respecify the message using less than 60 characters. INVALID.VAR OPTION - ccccccc Explanation: The option ccccccc is unknown to the.var command. System Action: Command execution terminates. User Response: Correct the option and retry the command. INVALID VARIABLE NAME - cccccccc Explanation: The name cccccccc contains invalid characters. System Action: Command execution terminates. User Response: Correct the name and retry the command. VARIABLE NAME TOO LONG Explanation: Name exceeds 8 characters. System Action: Command execution terminates. User Response: Correct the name and retry the command. STRING TOO LONG Explanation: The length of the replacement string set with.var can be no larger than 64 characters. System Action: The string is not installed. User Response: Supply a shorter string and retry the command. VARIABLE cccccccc HAS BEEN SET Explanation: The requested variable cccccccc has been updated in the table. System Action: The command executes successfully. This is an informational message only. VARIABLE NAME NOT FOUND IN TABLE Explanation: The requested name could not be located. User Response: Correct the command and retry. To see a list of the values in the table, issue the.var command. VARIABLE TABLE IS EMPTY Explanation: The user attempted to list variables with the.var command, however there were no variables in the table. This is an informational message only. 118 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

119 OB0117 OB0119 OB0120 OB0121 OB0122 OB0123 OB0124 OB0125 NO ENTRIES FOUND ON STACK Explanation: The.DSE command determined that no stack entries exist. System Action: The.DSE command terminates normally and waits for the next user request. This is an informational message only. VARIABLE NAME IS RESERVED, CANNOT BE SET Explanation: The variable name on a.var SET operation is reserved. Either the full name as entered is reserved, or the format is reserved. For example, the exception analysis format (ZX...) is reserved. System Action: OMEGAMON suppresses the.var SET function. User Response: Change the variable name to a valid name and re-enter the command. CANNOT LOCATE PREVIOUS MAJOR COMMAND Explanation: OMEGAMON could not locate the major command associated with this minor command. System Action: OMEGAMON does not execute the minor command. User Response: Enter the minor command after a major command and retry. NO WAIT INDICATED Explanation: The.WAT command requires a numeric argument. No numeric argument was supplied. System Action: Command execution terminates. User Response: Re-enter the command, specifying a wait value. nn SECOND WAIT COMPLETED Explanation: OMEGAMON completed the requested wait. System Action: Command execution completes normally. This is an informational message only. NO MINOR COMMAND NAME GIVEN Explanation: This command expects you to supply a minor command name as an argument. User Response: Enter a valid minor name. MINOR COMMAND NAME TOO LONG Explanation: The user entered a minor command name longer than 4 characters. User Response: Correct the entry and retry. NO MAJOR COMMAND HAS A MINOR WITH THIS NAME Explanation: The user entered an invalid minor command name. User Response: Enter a different minor command. OB0101 OB

120 OB0126 OB0127 OB0128 OB0129 OB0130 OB0131 OB0132 STATUS MODE ccc Explanation: Status mode has been turned ON or OFF. System Action: The command executes. This is an informational message only. INVALID LENGTH FOR KEYWORD - cccccccc Explanation: A keyword that is too long has been entered. The value cccccccc is the first 8 characters of the keyword specified with the invalid length. The maximum length for a conditional keyword is 8; the maximum length for a relational keyword is 2 characters. System Action: The screen is not fetched. User Response: Correct the keyword and re-enter it. INVALID RELATIONAL KEYWORD Explanation: An invalid relational keyword has been entered. Valid relational keywords are EQ, LT, LE, NE, GT, GE, and the equal (=) sign. System Action: The screen is not fetched. User Response: Correct the keyword and re-enter it. INVALID CONDITIONAL SYNTAX Explanation: An invalid conditional syntax has been entered. The valid syntax is: condition relation condition System Action: The screen is not fetched. User Response: Correct the keyword and re-enter. DEFINITION MODE {ENABLED HELD DISABLED} Explanation: OMEGAMON set definition mode to ENABLED, HELD, or DISABLED. System Action: The command completes processing. This is an informational message only. DELETE FAILED - cccccccc NOT FOUND IN PROCSAVE Explanation: Member cccccccc, the member to delete, was not found. User Response: Correct the name and retry the command. You can issue the SCRN command to display a list of screens in RKOMPCSV. You cannot use DELT to delete screens from the OBOMPROC dataset. DIRECTORY UPDATE FAILED, CODE = xx Explanation: An attempt to modify the RKOMPCSV directory failed; the return code (from STOW) is xx. The explanation of the return code is found in the IBM MVS Data Administration Macro Instruction Reference manual (STOW macro). User Response: Examine the return code and take appropriate action. 120 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

121 OB0133 OB0134 OB0135 OB0136 OB0137 OB0138 OB0139 OB0140 OB0141 ENTER MEMBER NAME TO BE DELETED Explanation: The DELT command requires a member name. No member name was found. User Response: Enter a member name and retry the command. MEMBER NAME LENGTH GREATER THAN 8 BYTES Explanation: The member name exceeds the maximum length of 8 bytes. User Response: Correct the member name and retry the command. PROCSAVE MEMBERNAME cccccccc CHANGED TO aaaaaaaa Explanation: The requested name change was made. System Action: The command terminates normally. This is an informational message only. PROCSAVE MEMBERNAME cccccccc DELETED Explanation: The named member was deleted. System Action: The command completes. This is an informational message only. RENAME FAILED - cccccccc ALREADY EXISTS IN PROCSAVE Explanation: The screen space name already exists in the RKOMPCSV dataset. System Action: The rename process terminates. User Response: Either delete or rename the member in RKOMPCSV, or specify another name and retry. RENAME FAILED - cccccccc NOT FOUND IN PROCSAVE Explanation: The member to be renamed is not in the RKOMPCSV dataset. System Action: OMEGAMON terminates the command. User Response: You can issue the SCRN command to list screens. Correct the name and retry the command. RENAME FAILED - PROCSAVE DIRECTORY FULL Explanation: An attempt to update the directory failed. System Action: OMEGAMON terminates the command. User Response: Increase the size of the directory or delete members, then retry the command. DIR ABORT NOT ALLOWED FROM DIRECTOR SESSION Explanation: The ABORT function can only be performed from a collector. System Action: OMEGAMON terminates the command. User Response: If you want to abort the collector, enter the command in the collector segment and retry. NO SYSTEM ID SPECIFIED. NO LINES TRANSFERRED. Explanation: The /GIVE command requires a target collector. System Action: OMEGAMON terminates the command. User Response: Add the required collector ID and retry. OB0101 OB

122 OB0142 OB0143 OB0144 OB0145 OB0146 OB0147 OB0150 OB0151 OB0152 SAME SESSION SPECIFIED. NO LINES TRANSFERRED Explanation: The target and source for /GIVE are the same. System Action: OMEGAMON terminates the command. User Response: Specify the correct collector ID and retry. SESSION NOT FOUND. NO LINES TRANSFERRED Explanation: The target ID is not an active session. System Action: OMEGAMON terminates the command. User Response: Specify the correct collector ID and retry. PROCSAVE DATASET CONCATENATED, UPDATE REQUESTS IGNORED Explanation: The RKOMPCSV dataset cannot be concatenated. Use OBPROC to concatenate datasets for updating screen spaces. User Response: Correct the starting PROC or JCL, and restart OMEGAMON. ENTER FROM AND TO MEMBER NAMES FOR RENAME REQUEST Explanation: The user did not specify the old and new names required for the RENM command. System Action: OMEGAMON terminates the command. User Response: Supply the required parameters and retry the command. {1st 2nd} MEMBER NAME IS INVALID Explanation: The indicated name (from or to) is invalid for OMEGAMON. System Action: OMEGAMON terminates the command. User Response: Correct the indicated name and retry the command. SCREEN SPACE NAME MISSING Explanation: No screen space name was supplied, or an undefined variable was used. This message usually occurs with the.sgo command. System Action: OMEGAMON terminates the command. User Response: Enter a valid screen space name or variable and retry the command. DUPLICATE NAME Explanation: The command synonym already exists. System Action: OMEGAMON cancels the request. User Response: Specify a unique name and retry. LOG RESET REQUIRED. USE.LOGOUT Explanation: Issue the.logout command to activate the changes made to the log file. System Action: The command continues. User Response: Reset the LOG as indicated. SYNONYM NAME NOT SPECIFIED Explanation: A name is required for this function. System Action: OMEGAMON ignores the request. User Response: Reissue the command and specify a synonym name. 122 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

123 OB0153 OB0154 OB0155 OB0156 OB0160 OB0161 OB0162 OB0163 SYNONYM VALUE NOT SPECIFIED Explanation: You must supply an OMEGAMON command name for the synonym to represent. System Action: OMEGAMON terminates the request. User Response: Supply a value for the synonym. UNKNOWN REQUEST Explanation: An invalid function was specified. System Action: OMEGAMON terminates the request. User Response: Specify a valid function (for example, ADD, DELETE). THIS COMMAND WORKS IN TSO MODE ONLY Explanation: The command is reserved for use in the TSO environment. System Action: OMEGAMON terminates the command. User Response: Execute this command only in a TSO environment. VALID ONLY IN DIRECTOR OR COLLECTOR MODE Explanation: The.DIR command allows execution of director or collector commands from within a screen space. It only works in director or collector mode. System Action: The command does not execute. User Response: Execute this command only in a cross memory or cross system environment..fgo LOOP DETECT HAS BEEN RESET Explanation: OMEGAMON processed the RESET=YES parameter of the.fgo command which reset the loop detect function. System Action: OMEGAMON execution continues. This is an informational message only. SCREEN SPACE FETCH {DELAYED PENDING} Explanation: The screen space processor suspends processing (delayed) until the count in the label field reaches 0. The screen space is scheduled for fetch (pending). System Action: OMEGAMON execution continues. This is an informational message only. SCREEN SPACE NOT FETCHED Explanation: The screen space was not fetched because the specified condition was not met. System Action: OMEGAMON execution continues. This is an informational message only. NOT A VALID KEYWORD Explanation: Conditional screen space fetch processing detected a keyword not contained in its tables. User Response: Correct the keyword and retry the command. OB0101 OB

124 OB0164 OB0165 OB0170 OB0171 OB0172 OB0201 OB0202.FGO LOOP DETECT, NO FAST GO Explanation: There are too many.fgos in a row (64) without an intervening display..fgo assumes that OMEGAMON is in a loop. System Action: OMEGAMON disables the.fgo function and changes it to.sgo. User Response: Correct the screen space loop and reset the.fgo command..fgo LOOP DETECT SWITCH SET Explanation: OMEGAMON processed the TEST=YES parameter of the.fgo command which set the loop detect function. System Action: OMEGAMON execution continues. OMEGAMON continues to treat.fgo as.sgo until you reissue the.fgo command with the RESET=YES keyword. This is an informational message only. n OF m MINOR COMMANDS GENERATED FOR cccc Explanation: The user issued the.exm immediate command with parameters. The variable m is the total number of minor commands associated with major command cccc and the variable n is the number of minors that.exm displays for this request. System Action: Command execution continues. This is an informational message only. NO MINOR COMMANDS AVAILABLE Explanation: The user issued the.exm immediate command with parameters. However, there are no minors associated with this major command. System Action: The command executes. This is an informational message only. CONDITIONAL TEST FAILED - VARIABLE NOT SET Explanation: The condition set with the.var immediate command tested not true. System Action: OMEGAMON does not set the variable. This is an informational message only. INVALID COMMAND OPTION SPECIFIED Explanation: An incorrect option was specified for the /DEF command. The valid options are ON and OFF. User Response: Correct the error and retry. MEMBER NAME TOO LONG Explanation: The member name exceeds 8 characters. User Response: Correct the name and retry. 124 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

125 OB0203 OB0204 OB0205 OB0206 OB0207 OB0208 OB0209 OB0210 MEMBER ALREADY EXISTS, TO REPLACE, USE /REP Explanation: The user attempted to save a screen space with the /SAVE command, but a member with the same name already exists. User Response: Use the /REP command or enter a new name and retry. MEMBER NOT FOUND - USE /SAVE Explanation: A replace was attempted but no corresponding member was found in the dataset. User Response: Correct the name or use the /SAVE command. OBPROC DD MISSING Explanation: OMEGAMON could not find the OBPROC DD statement and could not open the file. User Response: Allocate the proper file and restart OMEGAMON. PDS IS BUSY (ENQUEUE FAILED) Explanation: An attempt to access the dataset failed because it was in use by another job. User Response: Wait a few moments and retry the command. NO SPACE IN DIRECTORY Explanation: The directory is full. There is no room to add additional members. User Response: Increase the size of the directory and restart OMEGAMON, use an existing name, or delete entries. I/O ERROR Explanation: An I/O error has occurred. See other accompanying messages. User Response: This is a generic message. Examine the specific error messages and take appropriate action. PROGRAM ERROR, CONTACT IBM CORP Explanation: An internal error has occurred. NO PFKS SAVED BECAUSE NONE MODIFIED Explanation: No PF keys were modified, so OMEGAMON did not save them in the OBPROC file. This is an informational message only. OB0101 OB

126 OB0211 OB0212 OB0213 OB0214 OB0215 OB0219 OB0220 OB0221 /PWD SUPPRESSED BY SECURITY Explanation: The user security verification routine has permanently assigned a security level. This command is therefore disabled. This is an informational message only. LOGGED Explanation: The screen space was logged to the report dataset. System Action: The command continues. This is an informational message only. REPORT FILE NOT AVAILABLE Explanation: The allocation of a report file has failed. User Response: Check the minors of the OUTP major command: DDNM, DEST, DSTU, and FORM. INVALID ARGUMENT Explanation: An operand was found which was not valid for the specified command. User Response: See the help entry for the specified command to determine the correct operands. Correct the operand and retry. VTAM MINIMUM WAIT IS 5 SECONDS Explanation: An attempt was made to set the automatic update interval below 5 seconds in VTAM auto update mode. System Action: The request is denied. An interval of less than 5 seconds is invalid in this mode. User Response: Set a valid time and retry. COLLECTOR ATTACHED Explanation: The requested collector is attached to this director. System Action: Processing continues. This is an informational message only. MEMBER NAME IS INVALID Explanation: The name is specified incorrectly; it must begin with an alphanational character. User Response: Correct the name and retry. RKOMPCSV DD STATEMENT MISSING Explanation: A DD statement that allocates a user PROCFILE library was not present in the JCL. Therefore, the screen space cannot be saved or replaced. System Action: OMEGAMON does not make the screen space available to the user. User Response: Supply a DD statement that points to a PROCFILE library. 126 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

127 OB0222 OB0223 OB0224 OB0225 OB0226 OB0227 ARGUMENT NOT ALLOWED ON /RETURN Explanation: The /RETURN command (alias /R) does not allow an argument. /R is often mistaken as an alias for /REP, which does allow an argument. System Action: OMEGAMON ignores the command. User Response: Correct the command and retry. INVALID STACK ENTRY NUMBER Explanation: OMEGAMON attempted to recall an invalid stack entry. A valid stack entry number is greater than 0 but less than the number of entries in the stack. System Action: OMEGAMON ignores the command. User Response: Correct the stack entry number. Use the.dse command to display the entries on the stack. REQUIRED MEMORY FOR ccc NOT AVAILABLE Explanation: OMEGAMON is unable to allocate storage for the stack work area, where ccc is either SIA or SIB. System Action: The /STK command terminates normally and waits for the next user request. User Response: Increase the region size. cccccccc STACKED Explanation: The /STK command successfully placed screen space cccccccc on the stack. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: This is an informational message only. Enter the next command. cccccccc RECALLED Explanation: The /STK command successfully retrieved screen space cccccccc from the stack. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: This is an informational message only. Enter the next command. STACK ENTRY nnnn DELETED Explanation: The user successfully deleted stacked screen entry nnnn from the stack. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: This is an informational message only. Enter the next command. OB0101 OB

128 OB0228 OB0229 OB0230 OB0231 OB0232 OB0233 OB0234 STACK EMPTIED Explanation: The user cleared all stack entries. OMEGAMON freed all GETMAINed storage for the stack. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: This is an informational message only. Enter the next command. INVALID KEYWORD cccccccc Explanation: The user entered an invalid keyword cccccccc. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: Correct the keyword and retry. INVALID CURSOR LOCATION Explanation: The cursor must not be in row 0 or in the first or last column of a row. User Response: Place the cursor in the proper position and retry. UNABLE TO LOCATE GENERATING COMMAND Explanation: The backscan for a nonblank in column 2 failed. The scanner backed into the INFO-line. This most likely occurred if there were only comments on the screen. User Response: Correct the screen and retry. INVALID COMMAND NAME FOUND - cccc Explanation: The command name cccc is not a valid 3 or 4 alphanumeric character name. User Response: Correct the command name and retry. INCORRECT OPTIONAL PARAMETER - cccccccc Explanation: The optional parameter for the /ZOOM INFO-line command is invalid. It is not 4 characters long, or it contains invalid characters. User Response: Correct the parameter and retry. THERE ARE NO PFK ASSIGNMENTS AT THIS TIME Explanation: The user has not issued any.pfk immediate commands to assign screen spaces or INFO-line commands to PF keys. System Action: OMEGAMON waits for the next user request. User Response: Use the.pfk immediate command to assign screen spaces or INFO-line commands to PF keys. 128 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

129 OB0235 OB0236 OB0237 OB0238 OB0239 OB0240 OB0241 PFK nn NOT CURRENTLY ASSIGNED Explanation: The user pressed PF key nn to execute a screen space or an INFO-line command, but a screen space or INFO-line command is not assigned to PF key nn. This message appears on the INFO-line. System Action: OMEGAMON waits for the next user request. User Response: Use the.pfk immediate command to assign a screen space or an INFO-line command to PF key nn, or try another PF key. RECALL DENIED - AT cccccc OF STACK Explanation: The user entered a /STK U or /STK D command and the stack entry pointer is currently at the top or bottom of the stack. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: Enter the next command. MAXIMUM STACK ENTRIES Explanation: There is currently a maximum of 999 stacked screens; the user cannot save another screen. This message appears on the INFO-line. System Action: The /STK command terminates and waits for the next user request. User Response: Keep the number of stacked screens under 999. ERROR IN $SQZ Explanation: There is an error in the $SQZ routine. System Action: The /STK command terminates. EXTERNAL SECURITY ROUTINE CANNOT BE FOUND Explanation: An attempt has been made to enter a new user ID via the /PWD command. However, the user s external security routine cannot be located. System Action: The command is terminated. User Response: Contact your security administrator to verify that an external security routine has been properly installed. INVALID LENGTH FOR USERID Explanation: An attempt has been made to enter a new user ID via the /PWD command that is more than 8 characters. System Action: The command is terminated. User Response: Correct the user ID and retry. RELOGON NOT ALLOWED IN TSO OR SPF MODE Explanation: An attempt has been made to enter a new user ID via the /PWD command while in TSO or ISPF mode. The relogon function is not allowed in these modes. System Action: The command is terminated. User Response: Log off from TSO and log on with the new user ID and password. OB0101 OB

130 OB0242 OB0243 RELOGON REQUEST DENIED - NO PASSWORD Explanation: An attempt was made to relogon via the /PWD command, but no password was entered. System Action: The command is terminated. User Response: To relogon, re-execute the command and enter a password. If you want to reset the security level, enter /PWD without a user ID. RELOGON SUCCESSFUL Explanation: Relogon via the /PWD command was successful. This is the default message. System Action: The command executes. This is an informational message only. If you have customized your own message and it failed to display in place of the default message, verify the following information: The message has no more than 60 characters. U#CHMSGL contains the message s length. U#CHMSG contains the message. U#CHRESP indicates that a message is pending (U@CHMSHO). OB0244 RELOGON REQUEST DENIED Explanation: Relogon via the /PWD command was not successful. This is the default message. The user s security exit did not return a message and message length, or returned an invalid message length. Therefore, OMEGAMON issued this default message. This is an informational message only. If you have customized your own message and it failed to display in place of the default message, verify the following information: The message has no more than 60 characters. U#CHMSGL contains the message s length. U#CHMSG contains the message. U#CHRESP indicates that a message is pending (U@CHMSHO). OB0245 OB0246 INVALID RETURN CODE nn FROM EXTERNAL SECURITY EXIT Explanation: An invalid return code nn was passed from the external security exit. System Action: OMEGAMON terminated the command and disallowed execution of EXTERNAL=YES commands. User Response: Correct the external security exit to issue only these valid return codes: 0, 4, 8, and 12. /AUPON NOT ALLOWED IN TSO OR SPF MODE Explanation: Automatic update is not allowed under the VTM1 interface. System Action: OMEGAMON terminated the command. User Response: If you want to update automatically, use VTAM or dedicated mode. 130 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

131 OB0247 OB0248 OB0249 OB0308 OB0310 OB0311 OB0312 RELOGON NOT ALLOWED UNDER OLD EXIT Explanation: The relogon feature is not available with this version of the user exit. System Action: OMEGAMON terminated the command. User Response: Upgrade the user exit to the current version. INTERVAL NOT EFFECTIVE IN ccc MODE Explanation: The interval that was set cannot take effect in the mode in which the user is operating, because the current mode does not support automatic updating. System Action: The interval value set is retained. If the value is saved in a user profile, it may be used in dedicated or VTAM mode. This is an informational message only. EFFECTIVE INTERVAL IN ccc MODE IS nn.n SECONDS Explanation: The interval that was set cannot take effect in the mode in which the user is operating. The current mode has a minimum interval of nn.n seconds. System Action: The interval value set is retained, however the minimum of nn.n seconds becomes the effective interval in the current mode of operation. If the value is saved in a user profile, it may be effective in other modes. This is an informational message only. INVALID KEYWORD, EXCESSIVE LENGTH - cccccccccccc Explanation: The character string is longer than OMEGAMON allows (maximum 12 characters). System Action: OMEGAMON bypasses the string. It makes no attempt to validate the string against the internal tables. User Response: Correct the parameter and retry. PARAMETER keyword value DATA IS INVALID Explanation: The value associated with the keyword parameter is incorrect. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. PARAMETER keyword value DATA IS NOT UNIQUE Explanation: The value associated with the keyword parameter is incorrect. The data does not uniquely distinguish between entries. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. UNKNOWN KEYWORD PARAMETER - cccccccccccc Explanation: The indicated parameter is not in any of the tables associated with this command. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. OB0101 OB

132 OB0315 OB0316 OB0317 OB0318 OB0319 OB0320 OB0321 OB0322 PARAMETER cccccccccccc (nnnnnnnnnnnn) MAX DECIMALS = nn Explanation: The data nnnn associated with parameter cccc contains too many significant digits to the right of the decimal point. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. KEYWORD FORMAT ERROR - cccccccccccc Explanation: The parameter was specified in the wrong format. It must either be specified as a single word or as a keyword followed by an equal sign (=) and a data value. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. PARAMETER cccccccccccc (xxxxxxxxxxxx) MUST BE HEX DATA Explanation: The data xxxx associated with parameter cccccccc must contain only hex digits (0 9 and A F). System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. PARAMETER cccccccccccc (aaaaaaaaaaaa) MUST BE bbbbbbbb OR dddddddd Explanation: The data aaaaaaaaaaaa associated with parameter cccccccccccc must be either bbbbbbbbb or ddddddddd. No other values are allowed. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. PARAMETER cccccccccccc (nnnnnnnnnnnn) MUST BE NUMERIC Explanation: The data nnnn associated with parameter cccccccc must be a numeric value. Only the digits 0 9 and a decimal point are allowed. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. PARAMETER cccccccccccc (aaaaaaaaaaaa) Explanation: The data aaaaaaaa associated with parameter cccccccc is in error. This message will be followed by additional messages explaining the error. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. LENGTH MUST BE GE xxxxxxxx AND LE yyyyyyyy Explanation: The length of the character or hex string data must be within the bounds xxxxxxxx and yyyyyyyy. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. VALUE MUST BE GE cccccccc AND LE aaaaaaaa Explanation: The value of the number in message OB0320 must be within the bounds cccccccc and aaaaaaaa. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. 132 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

133 OB0323 EXCESSIVE DATA LENGTH, MUST BE LE 12 Explanation: The length of the data is too long. The maximum length of any data string is 12 characters. System Action: OMEGAMON bypasses the parameter. User Response: Correct the parameter and retry. OB0408 EXCEPTION NOT FOUND; CALL IBM CORPORATION Explanation: An exception in the OBUSER module could not be processed because of an error in the exception analysis tables. System Action: Exception analysis initialization terminates. OB0409 OB0410 OB0411 OB0412 OB0418 OB0419 MAXIMUM BELL INTERVAL IS 99 SECONDS Explanation: An attempt has been made to set the bell interval to more than 99 seconds. User Response: Enter a value that is less than 99 seconds. MINIMUM BELL INTERVAL IS 5 SECONDS Explanation: An attempt has been made to set the bell interval to less than 5 seconds. User Response: Enter a value that is 5 seconds or more. $DFNEXC MISSING - CALL IBM CORPORATION Explanation: An internal exception analysis table is missing from the OMEGAMON module. System Action: Exception analysis initialization terminates. NEED nnnk MORE TO INITIALIZE EXCEPTION ANALYSIS Explanation: OMEGAMON requires nnnk more storage to initialize exception analysis. User Response: Run OMEGAMON in a larger region. EXCEPTION ANALYSIS NOT INITIALIZED Explanation: Exception analysis has not been initialized. GROUP ID IS INVALID Explanation: OMEGAMON does not recognize the group ID supplied as a valid group ID. System Action: OMEGAMON ignores the request. User Response: Enter a defined group ID or define the group to OMEGAMON. OB0101 OB

134 OB0420 OB0421 OB0422 OB0423 OB0424 OB0425 OB0426 OB0427 EXCEPTION LIMIT OF 25 ENTRIES Explanation: A user attempted to enter more than 25 exceptions into this group. It is not possible to have more than 25 exceptions in a single user exception group. User Response: Create a group of 25 or less exceptions. LIST KEYWORD HAS NO EXCEPTIONS Explanation: A user entered the keyword LIST= without any exceptions. User Response: Enter the desired exceptions for the group. cccc ENTRY NON EXISTENT NOT DELETED Explanation: A user requested the deletion of an exception from a group that does not have that exception assigned. User Response: Determine the correct exception to be deleted. GROUP ID MUST BE PRESENT Explanation: The GROUP= keyword was not entered. User Response: Enter the GROUP= keyword along with the desired group ID. DELETE PARAMETER IS INVALID Explanation: The DELETE= keyword does not have GROUP or EXCEPTION specified. User Response: Enter the DELETE= keyword with either GROUP or EXCEPTION as the option. INVALID KEYWORD SPECIFIED FOR COMMAND Explanation: An undefined keyword was specified for this command. User Response: Correct the keyword and retry. LAST, WORST, AND CUMULATIVE VALUES HAVE BEEN RESET Explanation: Exception group trip statistics were reset. System Action: Last, worst, and cumulative counters were set to zero. This is an informational message only. STATE OPTION IS INVALID Explanation: A user entered an option for an exception state other than NULL, NDSP, TEST, ON, or OFF. User Response: Enter a valid option. 134 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

135 OB0428 OB0429 OB0430 OB0431 OB0432 OB0433 OB0434 OB0435 OB0437 GROUP CHANGED FROM cc TO aa FOR EXCEPTION bbbb Explanation: Exception bbbb was previously in exception group cc before being assigned to group aa. This is an informational message only. DELETE INVALID, GROUP NOT IN TABLE Explanation: Requested delete for exception group not processed, exception group is not in the table. User Response: Correct the exception group code and retry. EXCEPTION GROUP cc DELETED Explanation: OMEGAMON deleted exception group cc from exception group table. User Response: This is an informational message only. EXCEPTION cccc DELETED FROM EXCEPTION GROUP aa Explanation: OMEGAMON deleted exception cccc from exception group aa. It is now available for assignment to another exception group. User Response: This is an informational message only. cccccccc - INVALID COLOR, PLEASE RE-ENTER Explanation: The color entered was not a valid color. User Response: Enter a valid color (red, yellow, green, blue, turquoise, pink, or white). EXCEPTION NAME cccc IS INVALID Explanation: The exception name specified was not defined. User Response: Enter a defined exception name. SEQUENCE NUMBER IS INVALID Explanation: A non-numeric sequence was entered for the exception. User Response: Enter a numeric sequence number. GROUP ID cc IS INVALID Explanation: The GROUP= parameter for the XACB command was not specified or was specified incorrectly. System Action: The XACB command terminates. User Response: Enter a valid group identification code. POSITION KEYWORD HAS NO ENTRY Explanation: The POSITION= keyword was entered with no value following it. User Response: Enter a correct POSITION= value. OB0101 OB

136 OB0438 OB0439 OB0440 OB0441 OB0442 OB0443 OB0444 OB0445 POSITION nnn IS INVALID Explanation: OMEGAMON received a POSITION=nnn request that is greater than the number of entries in the table that was specified. User Response: Enter a value within the table range. NAME KEYWORD PARAMETER IS INVALID Explanation: The exception group NAME is null. User Response: Enter a valid name for the exception group. MORE THAN GROUP ID REQUIRED TO ADD ENTRY Explanation: An undefined group ID was entered with no other parameters. User Response: Enter the group ID, name, and list of desired exceptions to add a new entry to the table. cccccccc IS AN INVALID KEYWORD Explanation: An undefined keyword was entered. User Response: Correct the spelling of the keyword. KEYWORDS ALL/LIST/GROUP ARE MUTUALLY EXCLUSIVE Explanation: The XACB command uses the ALL, LIST, and GROUP keywords to select exceptions for display. Only one of these selection options may be specified at a time. System Action: XACB output is suppressed. User Response: Enter only one of the three keywords. VERBOSE AND TERSE ARE MUTUALLY EXCLUSIVE Explanation: The XACB command produces either a VERBOSE or TERSE display. The presence of both keywords creates a conflict. System Action: XACB output is suppressed. User Response: Select either VERBOSE or TERSE. GROUP cc HAS NO EXCEPTIONS ASSIGNED TO IT Explanation: The XACB command was used to select exception group cc for display. There are no exceptions currently assigned to group cc. System Action: The command is ignored. User Response: Select another exception group for display. THERE ARE NO EXCEPTIONS AVAILABLE FOR DISPLAY Explanation: The XACB command did not find any exceptions that met the selection criteria specified. This could have happened because the LIST= parameter was specified without any exception name. System Action: The command is ignored. User Response: Enter a valid group identifier or exception name. 136 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

137 OB0510 OB0515 OB0520 OB0525 OB0526 OB0527 OB0530 OB0532 OB0535 USER PROFILE cc ADDED TO LIBRARY Explanation: The user added a new profile cc to the profile library. System Action: The command executes. This is an informational message only. USER PROFILE cc DELETED FROM LIBRARY Explanation: The user deleted profile cc from the profile library. System Action: The command executes. This is an informational message only. USER PROFILE cc REPLACED IN LIBRARY Explanation: The user replaced existing profile cc in the profile library. System Action: The command executes. This is an informational message only. USER PROFILE cc NOT IN LIBRARY Explanation: The user attempted to delete profile cc which does not exist in the library. User Response: Correct the profile ID and retry. OMEGAMON WILL EXECUTE USING IBM DEFAULTS Explanation: This message indicates which profile defaults will execute for this session. System Action: The command completes processing. This is an informational message only. OMEGAMON WILL EXECUTE USING YOUR INSTALLATION PROFILE Explanation: This message indicates which profile defaults will execute for this session. System Action: The command executes. This is an informational message only. USER PROFILE ID cc IS NOT VALID Explanation: The user issued a profile command with an invalid profile identifier (suffix). User Response: Enter a valid 2-character profile identifier. Use the PPRF LIST command to list valid identifiers at your installation. USER PROFILE KEYWORD cccccccc IS INVALID Explanation: The user issued a profile command with an invalid profile keyword. User Response: Enter the profile keyword SAVE or DELETE. INSTALLATION PROFILE cc DELETED FROM LIBRARY Explanation: The installer deleted the installation profile from the library. This is an informational message only. OB0101 OB

138 OB0540 OB0544 OB0545 OB0546 OB0547 OB0580 OB0590 OB0590 (cont.) INSTALLATION PROFILE ADDED TO LIBRARY Explanation: The installer added a new installation profile to the profile library. This is an informational message only. INSTALLATION PROFILE DELETED FROM LIBRARY Explanation: The installer deleted the existing installation profile from the profile library. This is an informational message only. INSTALLATION PROFILE REPLACED IN LIBRARY Explanation: The installer replaced the existing installation profile in the profile library. This is an informational message only. INSTALLATION PROFILE IDENTIFIER NOT ALLOWED Explanation: The user entered a profile identifier for the installation profile command. It does not accept an identifier. User Response: Either use the PPRF command for a user profile, or delete the identifier on the IPRF command for the installation profile. INSTALLATION PROFILE NOT IN LIBRARY Explanation: The installer attempted to delete or replace a non-existent installation profile from the profile library. This is an informational message only. COMMENT ccccccccccccccccccc IS MORE THAN 18 CHARACTERS LONG Explanation: A comment was added with the PPRF command that is longer than the maximum allowed. User Response: Add a comment that is a maximum of 18 characters and retry the command. PROFILE SERVICE REQUEST FAILED - {reason} Explanation: A user profile request failed for the specified reason. System Action: The request is terminated. User Response: The reasons that appear follow. Take the appropriate action for the reason displayed with this message. ABEND X'13' OCCURRED IN cccc Explanation: An X'13' abend occurred when the specified routine (cccc) tried to open the profile dataset. System Action: The request is terminated. User Response: Check the SYSLOG for the X'13' abend and correct the problem. 138 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

139 OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) ABEND X'14' OCCURRED IN cccc Explanation: An X'14' abend occurred attempting to close the profile dataset from routine cccc. System Action: The request is terminated. User Response: Check the SYSLOG for the X'14' abend and correct the problem. ABEND X'37' OCCURRED IN cccc Explanation: An X'37' abend occurred while processing the profile dataset from routine cccc. System Action: The request is terminated. User Response: Compress and/or re-allocate the dataset as required. ABEND 913, SECURITY VIOLATION Explanation: An abend 913 occurred attempting to access a profile dataset. System Action: The request is terminated. User Response: Contact the person in charge of system security at your installation. FILE NOT AVAILABLE Explanation: A prior error occurred during user profile facility processing and the file was flagged as unavailable to this OMEGAMON session. System Action: The request is terminated. User Response: There should be a prior error message. Follow the instructions to correct the first error. GETMAIN FAIL, INCREASE REGION Explanation: An attempt to GETMAIN storage failed with a non-zero return code. System Action: The request is terminated. User Response: Increase the region parameter on the EXEC statement or job card of the OMEGAMON session. INPUT DCB OPEN FAILED Explanation: An attempt to open the input profile dataset was not successful. System Action: The request is terminated. User Response: Make sure that the input profile dataset is properly defined. Contact IBM Software Support. INPUT FILE NOT AVAILABLE Explanation: A prior error occurred during user profile facility processing and the input file was flagged as unavailable to this OMEGAMON session. System Action: The request is terminated. User Response: Another OB0590 message with a different reason was issued prior to this one. Follow the procedure to correct the first error. OB0101 OB

140 OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) INTERNAL ERROR, cccccc Explanation: Routine cccccc has detected an OMEGAMON internal error. System Action: The request is terminated. INTERNAL PROFILE HEADER ERROR Explanation: The user profile header record about to be written to the output dataset has an error. System Action: The request is terminated. INVALID DDNAME IN cccc Explanation: An internal OMEGAMON error has occurred. System Action: The request is terminated. INVALID SERVICE REQUEST TYPE Explanation: An invalid parameter type was presented to the user profile facility I/O driver. System Action: The request is terminated. IOWA NOT AVAILABLE Explanation: The user profile I/O work area is not available. System Action: The request is terminated. MEMBER IS EMPTY Explanation: The requested profile member contains no records. System Action: The request is terminated. User Response: Delete or replace the empty profile. nnnnnnnn NOT FOUND Explanation: Member nnnnnnnn was not found in the profile dataset. System Action: The request is terminated. User Response: Insure that the proper member name was requested. Use the PPRF LIST command to see what profiles are available and what profile datasets are allocated. OPEN FAILURE IN cccc Explanation: An attempt to open a profile dataset in routine cccc was not successful. System Action: The request is terminated. User Response: Insure that the profile datasets are properly defined. If you still cannot open the dataset, contact IBM Software Support. 140 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

141 OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OB0590 (cont.) OUTPUT DCB OPEN FAILED Explanation: An attempt to open the output profile dataset was not successful. System Action: The request is terminated. User Response: Make sure that the output profile dataset is properly defined. Contact IBM Software Support. OUTPUT FILE NOT AVAILABLE Explanation: A prior error occurred during user profile facility processing and the output file was flagged as unavailable to this OMEGAMON session. System Action: The request is terminated. User Response: Another OB0590 message with a different reason was issued prior to this one. Follow the procedure to correct the first error. OUTPUT TEMPORARILY UNAVAILABLE Explanation: The output profile dataset is being used by another OMEGAMON session. System Action: The request is terminated. User Response: Once the output profile dataset is free, you can enter the command again. If the condition persists, contact IBM Software Support. PROFILE DATASETS NOT ALLOCATED Explanation: The OBPROF and OBPROFSV datasets are not allocated. System Action: The request is terminated. Profile services are not available. User Response: Allocate the OBPROF and OBPROFSV datasets by DD statements or CLIST as appropriate for the session mode. If the problem persists, contact IBM Software Support. SEQUENCE ERROR IN cccc Explanation: An internal error occurred during user profile facility processing in routine cccc. System Action: The request is terminated. User Response: Another OB0590 message with a different reason was issued prior to this one. Follow the procedure to correct the first error. SERVICE NOT AVAILABLE Explanation: An invalid parameter was presented to the user profile facility I/O driver. System Action: The request is terminated. SPANNED RECORD ERROR Explanation: A profile being read for input was found to have an invalid value in the spanned record field. System Action: The request is terminated. User Response: Attempt to recreate the profile and if the problem still exists, contact IBM Software Support. OB0101 OB

142 OB0800 OB0801 OB0802 OB0803 OB0900 OB0901 OB0902 INFORMATION UNAVAILABLE NOT A MULTI-USER ENVIRONMENT Explanation: In response to the.vtm command, OMEGAMON determined that the current environment does not support multi-user sessions. There is no meaningful information for the.vtm command to display. Valid multi-user environments are VTM, VTS, and VTT. User Response: Use this command only in a valid multi-user environment controlled by OBVTAM. INFORMATION UNAVAILABLE INTERNAL ERROR Explanation: In response to the.vtm command, OMEGAMON attempted to display multi-session status information. However, OMEGAMON detected one or more problems in the internal subtask configuration for OBVTAM. This problem may be caused by transitory changes in OBVTAM subtask structures, which could result in a program check. User Response: Reissue the command. If this message persists, contact IBM Software Support. NO DATA ONLY SPACES ARE OWNED BY THIS ADDRESS SPACE Explanation: No tasks within the address space specified by the PEEK major command own any data-only spaces. This is an informational message only. ERROR DETECTED IN INTERNAL SCAN ROUTINE Explanation: An internal subroutine detected an error while collecting information on data-only spaces for the specified address space. User Response: Try the command again. If this message persists, contact IBM Software Support. COMMAND cccc IS NOT A VALID COMMAND Explanation: The command cccc is not a minor of the current major command or is not itself a major or immediate command. System Action: OMEGAMON bypasses this line. User Response: Correct the command and retry. COMMAND SUPERSEDED BY cccc Explanation: OMEGAMON no longer supports the specified command. Command cccc now performs a similar function. System Action: OMEGAMON selects the new version of the command. In the future, use command cccc. COMMAND INVALID UNDER nnn Explanation: This command is not valid with the MVS version you are running (nnn). System Action: OMEGAMON selects the next command. User Response: Use this command with the correct version of MVS. 142 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

143 OB0903 OB0906 OB0910 OB0915 INVALID INFO-LINE COMMAND Explanation: The INFO-line command entered does not exist. System Action: The command is not executed. User Response: Correct the command and retry. COMMAND DISABLED Explanation: The specified command was disabled by user security processing. System Action: OMEGAMON bypasses this line. User Response: Issue another command. PROGRAM CHECK - RECOVERY SUCCESSFUL - xxxxxxxx Explanation: An OMEGAMON command terminated abnormally due to a program check at location xxxxxxxx. System Action: OMEGAMON aborts the command. User Response: Retry the command. If the problem persists, follow the instructions given in the Preface, then contact IBM Software Support. CROSS MEMORY ERROR, ADDRESS SPACE SWAPPED OUT Explanation: Cross memory operations were attempted to an address space that was swapped out. System Action: Program recovery is successful, although the operation is suppressed. This is an informational message only. OB0916 PATTERN MUST BE SET BY.SPT COMMAND Explanation: A pattern-controlled operation was requested, but the pattern was not defined. System Action: Operation is ignored. User Response: Set a proper pattern using the.spt command. OB0917 PATTERN ARGUMENT MUST BE NUMERIC Explanation: The command requires a pattern that only has numeric values. System Action: Pattern operation is ignored. User Response: Correct the command and retry. OB0918 NO PATTERN EXISTS Explanation: No pattern exists for the requested pattern number. System Action: Pattern operation is ignored. User Response: Correct the command or assign a pattern. OB0919 PATTERN NUMBER MUST BE 0 THROUGH 9 Explanation: Invalid pattern number. System Action: Pattern operation is ignored. User Response: Correct the command and retry. OB0101 OB

144 OB0920 OB0921 OB0922 OB0924 OB0925 OB0926 OB0930 COMMAND LOOP RECOVERY SUCCESSFUL Explanation: OMEGAMON built-in loop detection encountered a possible loop in an OMEGAMON command processor. System Action: OMEGAMON terminates the command. User Response: Use the.set command to increase the LOOPTIME and/or LOOPCOUNT values. If the problem persists after setting these values to the maximum, follow the instructions given in the Preface and contact IBM Software Support. SECURITY CHECK FAILED (INTERNAL) Explanation: A password was not supplied for the security level associated with this command. System Action: OMEGAMON suppresses the command. User Response: Supply a valid password, or see your security administrator. SECURITY CHECK FAILED (EXTERNAL) Explanation: The OMEGAMON external security interface determined that the command is not authorized for execution. System Action: OMEGAMON suppresses the command. User Response: See your security administrator. cccc COMMAND NOT VALID WITH cc ARGUMENT Explanation: This command does not support a.d or a.r argument. System Action: The command is not executed. User Response: Correct the command syntax and retry. LOOP IN OMEGAMON BASE Explanation: OMEGAMON s built-in loop detection encountered a possible loop in an OMEGAMON service module. System Action: OMEGAMON terminates with a user ABEND User Response: Use the.set command to increase the LOOPTIME and/or LOOPCOUNT values. If the problem persists after setting these values to the maximum, follow the instructions given in the Preface and contact IBM Software Support. LOOP IN OMEGAMON BASE TERMINATION Explanation: A loop was detected while termination operations were under way. System Action: Termination operations are suspended and OMEGAMON abends. User Response: If the problem persists, contact IBM Software Support. UNEXPECTED PROGRAM CHECK - xxxxxxxx Explanation: OMEGAMON abend protection (ESTAE) processing detected a program check error in a module at location xxxxxxxx. System Action: OMEGAMON terminates the command. User Response: Follow the instructions given in the Preface, then contact IBM Software Support. 144 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

145 OB0931 OB0932 OB0933 OB0934 OB0935 OB0936 CP LOCATE OR CANDLE DIAGNOSE REQUIRED Explanation: The command cannot be executed without having either the authority to issue the CP LOCATE, or the IBM Tivoli Candle User Diagnose installed. System Action: OMEGAMON terminates the command. User Response: Get the privilege class needed to execute the CP LOCATE command or install the IBM Tivoli CandleUser Diagnose as documented in the OMEGAMON and EPILOG for VM Installation and Customization Guide and regenerate the VM operating system. CANDLE DIAGNOSE OR CP LOCK COMMAND REQUIRED Explanation: The command cannot be executed without having either the IBM Tivoli Candle User Diagnose installed or authority to issue the CP LOCK command. System Action: OMEGAMON terminates the command. User Response: Install the IBM Tivoli Candle User Diagnose as documented in the OMEGAMON and EPILOG for VM Installation and Customization Guide and regenerate the VM operating system, or get the privilege class needed to execute the CP LOCK command. OMEGAMON resource cleanup initiated for abend ccccc RC=xxxxxxxx Explanation: An abend occurred for an OMEGAMON session, and the non-private area resources will be removed. ccccc is the abend code and xxxxxxxx is the return code associated with the failure. This message is always followed by OB0935. System Action: Termination continues. This is an informational message only. LOAD FAILED FOR USER SECURITY EXIT - cccccccc Explanation: At initialization, this message appears if OMEGAMON was unable to load the designated user security exit. System Action: All EXTERNAL=YES commands with associated security levels of 0 are disabled. User Response: Ensure that the user security exit is specified in the MODULE= keyword of the security update program. OMEGAMON RESOURCE CLEANUP COMPLETE Explanation: Abend processing removed non-private area resources in preparation for abnormal termination. System Action: Termination continues. This is an informational message only. WARNING RUNNING KOBASnnn ON MVS/SPmmm. USE KOBASbbb. Explanation: The MVS version level of OMEGAMON you are attempting to initialize (nnn) does not match the MVS version under which you are running (mmm). Because we do not distinguish among all possible MVS variations, mmm can be 13x, 2xx, or 3xx. The variable bbb is the correct level. System Action: The system prompts you on whether you want to continue initialization. If you do continue to run an OMEGAMON version that does not OB0101 OB

146 OB0937 OB0938 OB0939 OB0940 OB0941 match the MVS version level, the integrity of some OMEGAMON data may be compromised. User Response: Determine whether your site is licensed for the version of OMEGAMON that matches your MVS level. If so, check the version level specified in the start-up parameters and change nnn to bbb. If not, contact IBM Software Support. WARNING RUNNING MVS/SPnnn MODULE pppppppp ON MVS/SPmmm Explanation: The variable nnn is the MVS version on which the module (pppppppp) is supported. It does not match the MVS version under which you are running (mmm). Because we do not distinguish among all possible MVS variations, mmm can be one of 13x, 2xx, or 3xx. System Action: The system prompts you on whether you want to continue initialization. If you do continue and run an OMEGAMON version that does not match the MVS version level, the integrity of some OMEGAMON data may be compromised. User Response: Determine whether your site is licensed for the version of OMEGAMON that matches your MVS level. If so, check the version level specified in the start-up parameters and change nnn to bbb. If not, contact IBM Software Support. WARNING OMEGAMON UNSUPPORTED ON MVS PRE-SP1.3. Explanation: OMEGAMON no longer supports versions of MVS prior to SP1.3. System Action: The system prompts you on whether you want to continue initialization. If you continue to run an OMEGAMON version that does not match the MVS version level, the integrity of some OMEGAMON data may be compromised. User Response: Upgrade your MVS version. STORAGE UNAVAILABLE FOR COWA Explanation: A collector is starting and needs memory for the work area to communicate with the director. The request for memory has failed. System Action: The collector terminates. User Response: Increase region size and try again. NO RESPONSE FROM DIRECTOR FOR 5 MINUTES Explanation: During the last 5 minutes, an OMEGAMON collector session did not detect a response from its associated director session. System Action: OMEGAMON terminates the collector. User Response: Determine why the director failed and restart the session. COLLECTOR CONNECTION FAILED: NO SEGMENTS AVAILABLE Explanation: The user tried to establish more than the maximum number (7) of cross memory collector sessions with a single OMEGAMON director. System Action: OMEGAMON cancels the request. User Response: If you need to display more than 7 cross memory collectors on this system, start another OMEGAMON director. 146 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

147 OB0942 OB0943 OB0944 OB0945 OB0946 OB0947 COLLECTOR AT WRONG VERSION: CONNECTION FAILED Explanation: A cross memory collector at a different (and incompatible) release level tried to start a cross memory session with an OMEGAMON director. System Action: OMEGAMON cancels the request. User Response: Bring up the director and cross memory collector using the same (or a compatible) version of OMEGAMON. NO RESPONSE FROM COLLECTOR FOR 5 MINUTES Explanation: An OMEGAMON director did not detect a response from one of its associated collectors during the last 5 minutes. System Action: The director terminates this collector session. User Response: Determine why the collector failed, and restart the collector. If the condition continues, contact IBM Software Support. DIRECTOR INITIALIZATION FAILED: ID ALREADY IN USE Explanation: An attempt to bring up an OMEGAMON director failed because OMEGAMON was already running in another address space using the same system ID (via the SYS= start-up keyword). System Action: OMEGAMON cancels the request. User Response: To initialize the OMEGAMON director, specify a unique value for the SYS= parameter. DIRECTOR INITIALIZATION FAILED: NOT AUTHORIZED Explanation: An attempt was made to bring up an OMEGAMON director that did not have APF authorization. System Action: OMEGAMON terminates the director. User Response: APF authorize all of the necessary load libraries and restart the director. TARGET DIRECTOR NOT FOUND (RC=20) Explanation: OMEGAMON could not start the requested OMEGAMON cross memory collector because it could not find the specified director (via the DIR= start-up keyword). System Action: OMEGAMON cancels the request. User Response: Bring up the OMEGAMON director before you try to initialize the collector or specify the ID of an active director. ANOTHER COLLECTOR HAS THE SAME ID (RC=24) Explanation: An attempt to start the requested OMEGAMON collector failed because another collector was already active using the specified system ID (via the SYS= start-up keyword). You must specify a unique system ID for each collector when you bring up multiple OMEGAMON collectors in the same system. System Action: OMEGAMON cancels the request. User Response: Specify a unique system ID for each collector. OB0101 OB

148 OB0948 OB0949 OB0950 OB0951 OB0952 OB0953 INVALID NUMBER OF COLUMNS SPECIFIED (RC=36) Explanation: The number of columns you specified (via the COLS= keyword) for the cross memory or cross system collector does not match the number of columns for the director with which the collector is attempting to begin a session. System Action: OMEGAMON cancels the request. User Response: Correct the COLS= value at either the collector or director and restart the session. DIRECTOR AT WRONG VERSION: CONNECTION FAILED (RC=40) Explanation: A cross memory collector tried to start a cross memory session with an OMEGAMON director of a different and incompatible release level. System Action: OMEGAMON cancels the request. User Response: Bring up the director and cross memory collector using the same (or compatible) version of OMEGAMON. DISK DATASET AT WRONG VERSION - REFORMAT (RC=40) Explanation: This session s cross system dataset was formatted with an incompatible version of the format program. System Action: OMEGAMON cancels the request. User Response: Reformat the cross system dataset with the current version of the KOBXDSK program. ONLY EIGHT SEGMENTS ALLOWED Explanation: The /ATTACH command generates this message. OMEGAMON allows no more than 7 collectors plus the director segment at the director screen for cross memory/cross system mode terminal input/output processing. System Action: OMEGAMON cancels the request. User Response: If you need to display more than 7 collectors on this system, start another OMEGAMON director. COLLECTOR ID ALREADY ACTIVE Explanation: The /ATTACH command generates this message. While trying to bring up a cross system collector session, OMEGAMON detected that this collector was already in session with a director. System Action: OMEGAMON cancels the request. User Response: Specify the correct collector ID. DDNAME MISSING Explanation: This message may be issued in either of two situations: When the /ATTACH command is issued and OMEGAMON did not find the correct DD statement for the cross system dataset. When attempting to start a collector and OMEGAMON did not find the correct DD statement for the cross system dataset. System Action: OMEGAMON cancels the request. 148 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

149 OB0954 OB0955 OB0956 OB0957 OB0958 User Response: To correct the error, check the following: A collector system ID for the session that matches the name specified on the SYS= start-up parameter. A missing or incorrect DD statement in the director start-up JCL or EXEC file to point to the cross system dataset. A missing or incorrect DD statement in the collector start-up JCL or EXEC file to point to the cross system dataset. When you have corrected the error, restart the OMEGAMON director. COLLECTOR ID REQUIRED Explanation: The /ATTACH command generates this message. An /ATTACH INFO-line command was entered without a collector ID. System Action: OMEGAMON cancels the request. User Response: Re-enter the /ATTACH command and specify a valid collector ID. DATASET AT WRONG LEVEL - REFORMAT Explanation: The /ATTACH command generates this message. A different release level format program was used to format the cross system dataset for this cross system session and its director. System Action: OMEGAMON cancels the request. User Response: Reformat the cross system dataset with the current version of the KOBXDSK program. DATASET HAS WRONG NUMBER OF COLUMNS - REFORMAT Explanation: The /ATTACH command generates this message. The cross system dataset used for cross system session initialization was formatted for a different screen size (via the COLS= parameter) than that of the director terminal. System Action: OMEGAMON cancels the request. User Response: Reformat the cross system dataset with KOBXDSK and specify the proper COLS= value. DIRECTOR MODE IS REQUIRED Explanation: The /ATTACH command generates this message. The attempt to attach a cross system collector at an OMEGAMON console failed because it was not initiated as an OMEGAMON director. System Action: OMEGAMON cancels the request. User Response: Restart OMEGAMON, specifying the proper parameter for director mode. ENQUEUE ALREADY OUTSTANDING. QNAME: cccc Explanation: An enqueue attempt by the director controller failed. System Action: The attach is suppressed. User Response: If this problem persists, contact IBM Software Support. OB0101 OB

150 OB0959 OB0960 OB0962 OB0963 OB0964 OB0965 DEQUEUE ATTEMPTED FOR RESOURCE NOT OWNED. QNAME:cccc Explanation: A dequeue attempt by the director controller failed. System Action: The detach is suppressed. User Response: If this problem persists, contact IBM Software Support. BASE(Vnnnccc) AND INIT(Vnnnccc) VERSIONS ARE NOT COMPATIBLE Explanation: You are using two incompatible levels of OMEGAMON load modules. System Action: OMEGAMON does not start. User Response: Verify that the proper libraries are in use. If necessary, reinstall OMEGAMON using the appropriate distribution tape. UNABLE TO OPEN PRIMARY CONSOLE Explanation: OMEGAMON could not bring up the requested dedicated OMEGAMON session because the OMEGAMON console (specified by the UNIT= start-up keyword) is not available. System Action: If this is the first OMEGAMON console session in the address space, OMEGAMON terminates. Otherwise, the particular OMEGAMON console session terminates. User Response: Check to see whether the terminal address is attached to another user or owned by VTAM. Specify an available console and retry. cc MODE INVALID: NOT A TSO SESSION Explanation: You can only specify TS or LS mode at OMEGAMON start-up when OMEGAMON is running under a TSO session. System Action: OMEGAMON terminates. User Response: Correct the MODE= parameter and restart OMEGAMON. TS CHANGED TO LS AS THIS IS NOT A SCREEN DEVICE Explanation: An OMEGAMON TSO session was altered to low-speed mode, since the OMEGAMON terminal is not a display device. System Action: TS mode becomes LS mode. User Response: Specify MODE=LS when starting OMEGAMON at this device. WARNING: NUMBER OF ROWS REQUESTED DOES NOT MATCH YOUR TERMINAL SIZE Explanation: The value specified for the ROWS= start-up parameter does not match the actual size of the OMEGAMON terminal screen. System Action: OMEGAMON changes ROWS to match the terminal size; initialization continues. User Response: Specify a ROWS= value that matches your terminal s physical characteristics at OMEGAMON start-up. 150 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

151 OB0966 RKOMPCSV DD CONCATENATED, UPDATES IGNORED Explanation: The RKOMPCSV DD statement consists of more than one dataset. System Action: MVS data management constraints prevent OMEGAMON from performing any PDS updates to RKOMPCSV. OMEGAMON ignores requests by the /SAVE and /REP INFO-line commands and the DELT and RENM immediate commands. User Response: Remove the concatenated datasets from the RKOMPCSV DD statement and restart OMEGAMON. OB0967 xxprocsv PRIOR SECURITY VIOLATION xxproc ABEND SX13 Explanation: A /SAVE or /REP command failed due to a security problem. User Response: Consult your security coordinator to gain access to the datasets in the xxproc DD statement. OB0969 INSUFFICIENT MEMORY TO INITIALIZE Explanation: OMEGAMON was unable to GETMAIN enough virtual storage to complete initialization. System Action: Start-up fails. User Response: Increase the region size address space and restart OMEGAMON. (See message OB0970). OB0970 INCREASE REGION SIZE BY nnnk AND RERUN Explanation: Initialization failed because OMEGAMON needed additional virtual storage. System Action: OMEGAMON terminates. User Response: Increase the REGION= parameter by the amount that this message indicates and restart OMEGAMON. (See message OB0969.) OB Explanation: This ruler appears below message OB0972 to help you locate PARM line errors. Additional message text (as listed below) appears below the ruler line, followed by the column location of the error, except when the error is in column 1. System Action: The OMEGAMON session terminates. User Response: Examine the message text and make suitable corrections. Additional message text: OMEGAMON STARTUP PARAMETER ERROR PARM FIELD SYNTAX ERROR PARAMETERS MUST BE SEPARATED BY A COMMA KEYWORD MUST END IN EQUAL SIGN UNKNOWN KEYWORD PARAMETER PARAMETER STRING TOO SHORT PARAMETER STRING TOO LONG PARAMETER NOT VALID HEXADECIMAL VALUE PARAMETER VALUE TOO LOW PARAMETER VALUE TOO HIGH OB0101 OB

152 THIRD CHARACTER MUST BE NUMERIC FIRST PARAMETER LENGTH ERROR UNABLE TO ACQUIRE STORAGE FOR PARAMETER TABLES UNIT SAME AS EXISTING TASK OMEGAMON HAS PROBABLY BEEN ENTERED AS A TSO COMMAND UNSUPPORTED MODE - BASE UNSUPPORTED MODE - OMEGAMON UNSUPPORTED MODE - NO IC DRIVER OB0972 OB0973 OB0974 OB0975 OB0976 OB0977 (USER INPUT APPEARS HERE) Explanation: OMEGAMON issues this message with OB0971 (see above). System Action: OMEGAMON terminates. User Response: See the error code for OB0971. WARNING -- RUNNING nnn OMEGAMON ON yyy SYSTEM Explanation: This level of OMEGAMON (nnn) is incompatible with this level of VM (yyy). System Action: OMEGAMON initialization continues, but with unpredictable results. User Response: If OMEGAMON did not terminate itself, stop it, install the correct OMEGAMON level, and restart OMEGAMON. aaaaaaaa LOADER ERROR Explanation: OMEGAMON attempted to load module aaaaaaaa, but could not find it in the load library. System Action: The load fails and OMEGAMON issues an abend code User Response: Check that module aaaaaaaa is in the load library. aaaaaaaa MODULE HAS REENTRANT LINKAGE EDITOR ATTRIBUTE Explanation: OMEGAMON could not update the module aaaaaaaa because it resides in a store-protected subpool. System Action: OMEGAMON terminates. User Response: Relink module aaaaaaaa without the RENT linkage editor parameter. RMF ASCB NOT FOUND Explanation: OMEGAMON was unable to locate proper ASCB during RMF search. System Action: The process terminates. {SMF WTO} AUDITING IS BEING SUPPRESSED FOR THIS SESSION Explanation: The user security exit has explicitly requested that SMF and/or WTO auditing be suppressed for this session; this request is made at initialization and/or relogon time. This message only appears once. This is an informational message only. 152 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

153 OB0978 OB0979 OB0980 OB0981 OB0982 OB0983 OB0984 OB0985 SECURITY ROUTINE HAS ABORTED STARTUP Explanation: An external security routine passed back a non-zero return code to initialization. System Action: OMEGAMON terminates. User Response: See your security officer. ERROR LOADING PRODUCT MODULE cccccccc Explanation: The product module could not be loaded successfully. System Action: OMEGAMON terminates. User Response: Be sure the named module is in the product library. See accompanying MVS system messages and take appropriate action. If it is not in the product library, contact IBM Software Support. SAVE STACK RECOVERY SUCCESSFUL Explanation: The save area stack overflowed. COMMAND TABLE ERROR cccc Explanation: A validation error occurred while loading the command table module. System Action: OMEGAMON terminates. ERROR DETECTED IN COMMAND TABLES Explanation: An error occurred while loading the command tables. System Action: This is a secondary message. It follows messages that contain validation error information. User Response: Examine the previous errors and follow the recommended user responses. CANNOT LOCATE COMMAND TABLE MODULE, ABEND=cccc, RC=cc Explanation: The usual cause of this message is insufficient region size for OMEGAMON to load the command table module. System Action: OMEGAMON aborts the session start. User Response: See your installer to increase the region size. For other possible causes, look up the abend code in the IBM System Codes manual for your system. You may also need to refer to the IBM System Messages manual. NO COMMAND TABLE MODULE NAME Explanation: An error occurred in command table processing. System Action: OMEGAMON terminates. SAVE STACK RECOVERY SUCCESSFUL Explanation: Invalid stack release by a command. System Action: OMEGAMON terminates the command execution. User Response: This is an internal error. Contact IBM Software Support. OB0101 OB

154 OB0986 OB0987 OB0988 OB0989 OB0990 OB0991 OB0992 GETMAIN FAILED FOR COMMAND TABLES Explanation: The request for storage for a copy of the command module failed. System Action: OMEGAMON terminates. User Response: Increase the region size for OMEGAMON. PRODUCT INITIALIZATION FAILED, RC=nnn Explanation: The product initialization routines have returned an error code which is non-zero. System Action: OMEGAMON terminates. User Response: Read any other messages that accompany this message. If unable to find the problem, contact IBM Software Support. PRODUCT LEVEL nnn INCOMPATIBLE WITH DRIVER LEVEL mmm Explanation: The base driver module cannot service the current product. System Action: OMEGAMON initialization stops. User Response: Use a base driver which is at the same or greater level than the product you are trying to initialize. Retry using this new driver. OBUSERcc MUST BE REASSEMBLED; IT IS NOT COMPATIBLE WITH THIS RELEASE OF OMEGAMON Explanation: The user assembled an old OBUSER module that is incompatible with the current release of OMEGAMON. System Action: OMEGAMON initialization stops. User Response: Obtain the current OBUSER from the product tape and reassemble. SECURITY LOGGING, userid, cccccccc, ACCESS(aaaaaaaa) Explanation: The security settings of the command table produce this security logging message. The variable cccccccc is the command being validated and aaaaaaa is the result. The userid is displayed if AUDIT=WTO is specified. System Action: OMEGAMON terminates execution of any command to which it denies access. This is an informational message only. DYNAMIC ALLOCATION ERROR: ERROR=cccc, INFO=cccc Explanation: A dynamic allocation request failed with the ERROR and INFO codes indicated. System Action: The allocation process terminates. User Response: Examine the error and information codes in the message and take appropriate action. aauserbb VALIDATION FAILED. RC=n Explanation: The user profile aauserbb did not pass product validation. System Action: Session initialization terminates. User Response: If other messages were issued previously, take the action suggested for those messages. If no other messages were issued, contact IBM Software Support. 154 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

155 OB0993 OB0994 OB0995 OB0996 OB0997 OB0998 NO ARGUMENT HAS BEEN SUPPLIED Explanation: A valid argument was not supplied for the command. User Response: Supply a valid argument and reissue the command. NO VALID PATTERN HAS BEEN SUPPLIED Explanation: A valid pattern was not supplied for the command. User Response: Supply a valid pattern and reissue the command. UNABLE TO LOG AUDIT RECORD TO SMF, RC=cc Explanation: A non-zero return code was received from SVC 83 while attempting to track an audited command. These codes are documented in the IBM System Programming Library: System Management Facilities (SMF) manual for your system. System Action: A WTO is issued to the console with audit information. User Response: Consult the appropriate IBM documentation for an explanation and interpretation of the non-zero return code. This return code may indicate a serious problem with SMF. APF AUTHORIZATION REQUIRED FOR SMF LOGGING Explanation: OMEGAMON cannot write SMF records unless it is APF-authorized. This message will appear only once; thereafter, all audit activity will be directed to the console for the duration of the session. System Action: A WTO is issued to the console with audit information. User Response: Determine whether OMEGAMON should be authorized. This is an installation decision. RECORD NUMBER MUST BE BETWEEN 128 AND 255 (INCLUSIVE) FOR SMF LOGGING Explanation: OMEGAMON detected a request to write an SMF record with an invalid record ID. User SMF records must use a record ID between 128 and 255, inclusive. This message will appear only once; thereafter, all audit activity will be directed to the console for the duration of the session. System Action: A WTO is issued to the console with audit information. User Response: Use the Security Update Program to specify a valid SMF record ID. EXTERNAL SECURITY IS UNAVAILABLE Explanation: OMEGAMON could not locate the user security routine to process a command for which external security was requested. Internal security was not invoked because the command did not have a security level associated with it. System Action: OMEGAMON suppresses command execution. User Response: Determine why the user security routine is missing. Make sure it is in a link-list library or in the OMEGAMON STEPLIB. OB0101 OB

156 OB1112 OB1116 OB1120 OB1124 OB1140 OB1148 OB1191 DATA COLLECTOR IS NOT ACTIVE Explanation: The requested collector is not currently active. System Action: The IPRO command processor suppresses the display. User Response: Start the collector and retry the command. REQUEST NOT SUPPORTED Explanation: The request is not supported by the target collector. System Action: The IPRO command processor suppresses the display. User Response: Correct the parameters and retry the request. REQUESTED DATA NOT VALID Explanation: The IPRO collector s data is currently statistically invalid. Sufficient data has not yet accumulated for a meaningful display. System Action: The IPRO command processor suppresses the display until enough samples have accumulated. User Response: Wait for sufficient time to gather data. This is an informational message only. REQUESTED DATA NOT AVAILABLE Explanation: The requested data is not being collected at this time. System Action: The IPRO command processor suppresses the display. User Response: Stop and restart the collector requesting the required data, or correct the collector start-up parameters and retry the request. REQUEST INCONSISTENT OR UNDEFINED Explanation: The IPRO display parameters are not valid, so the processor suppresses the display. System Action: The extractor was unable to process the parameters successfully. User Response: Correct the parameters and retry. SUCCESSFUL ABEND RECOVERY IN EXTRACTOR Explanation: An error occurred in the IPRO data display extractor. No presentation is made during this cycle. System Action: The IPRO command processor suppresses the display. UNABLE TO LOAD IANL PROCESSOR MODULE Explanation: OMEGAMON could not find the Impact Analysis processor module to load. System Action: The IPRO command processor suppresses the display. User Response: If this module should be available, contact IBM Software Support. 156 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

157 OB1195 OB1196 OB1197 OB1198 OB1199 OB1200 OB1201 OB1202 MISSING EXTRACTOR NAME Explanation: No extractor identification was given to the IPRO command processor. Either this is the first time the command was used, or it was cleared by the first extractor and there are no new operands. System Action: The IPRO command processor suppresses the display. User Response: Supply a proper extractor ID. DATA EXTRACTOR ADDRESS = 0 - xxxx Explanation: The IPRO display processor for xxxx could not be located in this set of OMEGAMON modules. System Action: The IPRO command processor suppresses the display. UNKNOWN RETURN CODE FROM EXTRACT - cc Explanation: The IPRO display processor returned the code cc which is unknown to the IPRO command. System Action: The IPRO command processor suppresses the display. INVALID PARAMETER - cccc Explanation: The first 4 characters (cccc) of the operand are invalid. System Action: The IPRO command processor suppresses the display. User Response: Specify a valid IPRO collector and retry. IPRO COMMAND NOT SUPPORTED Explanation: The IPRO command is not supported at this product level. IPRO requires DEXAN. System Action: The IPRO command processor suppresses the display. SEVERE ISPF ERROR DETECTED Explanation: ISPF has returned a severe error condition code to the OMEGAMON ISPF driver. System Action: The ISPF session terminates. User Response: Look for other messages and take appropriate action. TSO SERVICE ERROR RETURN CODE nnn Explanation: The TSO service task has returned the error code indicated. System Action: The ISPF session terminates. User Response: Examine the error code and take appropriate action. Refer to the IBM manual, TSO Extensions User s Guide. ATTACH FAILED FOR MONITOR TASK Explanation: ISPF issued a non-zero return code in response to /ATTACH. System Action: The ISPF session terminates. User Response: Examine the return code and take appropriate action. OB0101 OB

158 OB1203 OB1204 OB1210 OB1211 OB1212 OB1213 OB1214 OB1215 MONITOR TASK COMPLETE, RETURN CODE = cc Explanation: The monitor task (OMEGAMON) terminated with the indicated return code. System Action: The task terminates. This is an informational message only. MONITOR TASK ABENDED, COMPLETION CODE = cc Explanation: The monitor task (OMEGAMON) terminated with the indicated abend code. System Action: The task terminates. PARM STRING LENGTH ERROR Explanation: The PARM string entered was too long, causing internal buffer overflow. System Action: The task terminates. User Response: Shorten the PARM string and retry the command. UNABLE TO LOAD ISPLINK MODULE Explanation: The ISPF driver module was unable to load ISPLINK, the ISPF interface. System Action: The task terminates. User Response: Make sure a copy is available to the ISPF driver. PANEL OMSPF01 NOT FOUND Explanation: The SPF driver module could not find the OMSPF01 panel. System Action: The task terminates. User Response: Be sure the panel is in the correct ISPF library and retry. VARIABLE OMSPFD NOT IN PANEL OMSPF01 Explanation: The OMSPFD variable was not in the panel. System Action: The task terminates. User Response: Make sure that the correct panel is installed and that user changes have not caused this field to be omitted. INSUFFICIENT SPACE FOR PQUERY FUNCTION Explanation: ISPF indicated a short-on-storage condition. System Action: The task terminates. User Response: Increase the TSO address space region and retry. DATA TRUNCATION HAS OCCURRED Explanation: Internal data truncation occurred within a panel variable. System Action: The task terminates. User Response: Make sure that the variable lengths shown in the panel have not been changed. 158 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

159 OB1216 OB1217 OB1220 OB1250 OB1251 OB1252 OB1253 OB1254 VARIABLE NOT FOUND Explanation: A variable that the ISPF driver requires could not be found in the ISPF subpools. System Action: The task terminates. User Response: This is an internal error. Contact IBM Software Support. INVALID SCREEN SIZE Explanation: The screen parameters are invalid for ISPF mode. COLS and ROWS must match the TSO specification for the device. System Action: The task terminates. User Response: Correct the screen specification parameters (COLS and ROWS) and restart. UNKNOWN RETURN CODE FROM ISPLINK Explanation: ISPLINK returned a code 20 or above to the calling task. System Action: The task terminates. cccccccc STORAGE REQUEST FAILED Explanation: The request for storage for module cccccccc failed. System Action: The TSO or ISPF mode task terminates. User Response: Increase the region size for the TSO address space. ATTACH FAILED FOR cccccccc, RETURN CODE = xx Explanation: A non-zero return code from ATTACH of module cccccccc was received. System Action: The TSO or ISPF mode task terminates. User Response: Examine the error code and call your systems support. If the problem persists, contact IBM Software Support. MODULE ABENDED, COMPLETION CODE = xxx Explanation: The module abended with the indicated return code. System Action: The application using the module is terminated. User Response: Examine the abend code and call your systems support. If the problem persists, contact IBM Software Support. SET STFSMODE ON FAILED AT INITIALIZATION Explanation: OMEGAMON could not set full-screen mode on as requested for TSO mode. System Action: The task terminates. SET STTMPMD OFF FAILED AT INITIALIZATION Explanation: OMEGAMON could not set display manager off as requested for TSO mode. System Action: The task terminates. OB0101 OB

160 OB1255 OB1256 OB1257 OB1258 OB1259 OB1260 OB1261 OB1401 OB1402 SET STFSMODE OFF FAILED AT TERMINATION Explanation: OMEGAMON could not set full-screen mode off as requested for TSO mode. System Action: The task terminates. SET STTMPMD ON FAILED AT TERMINATION Explanation: OMEGAMON could not set display manager on as requested for TSO mode. System Action: The task terminates. {TSO ISPF} MODE TASK TERMINATED Explanation: The task completed its processing with a normal termination. System Action: The TSO or ISPF mode task terminates. This is an informational message only. cccccccc FREE STORAGE REQUEST FAILED Explanation: The free storage request has failed in module cccccccc. System Action: The task terminates. User Response: Examine the error code in the SYSLOG. If the problem persists, contact IBM Software Support. LOAD cccccccc FAILED Explanation: The load request for module cccccccc has failed. System Action: The task terminates. User Response: Examine the error code in the SYSLOG. Ensure that load module cccccccc is in the proper load library. If the problem persists, contact IBM Software Support. DELETE cccccccc FAILED Explanation: The delete request for module cccccccc has failed. System Action: The task terminates. GTTERM FAILED Explanation: The request to get terminal attributes has failed. System Action: The task terminates. MISSING USER ID Explanation: The user ID field in the logon panel is missing. System Action: OMEGAMON redisplays the logon panel. User Response: Enter the required user ID. MISSING PASSWORD Explanation: The password field in the logon panel is missing. System Action: OMEGAMON redisplays the logon panel. User Response: Enter your password. 160 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

161 OB1404 OB1405 OB1501 OB1502 OB1503 OB1504 OB1505 RE-ENTER NEW PASSWORD FOR VERIFICATION Explanation: The system asks the user to re-enter the new password. System Action: The system waits for the user to re-enter the new password to verify that the new password is correct. User Response: Enter the new password in the new password field. VERIFICATION OF NEW PASSWORD FAILED Explanation: When the password was entered a second time for verification, it did not match the new password. System Action: The system waits for the user to attempt another logon. User Response: Enter the correct password. INVALID ARGUMENT: cc Explanation: The argument field contains invalid data for the command that appears above this message on the screen. System Action: OMEGAMON does not process the command. User Response: Enter appropriate data in the command argument field. INSUFFICIENT MEMORY FOR SCRN COMMAND Explanation: OMEGAMON does not have sufficient memory to build the screen member name lists from the various sources (main storage, OBPROC, and RKOMPCSV) that the SCRN command displays. System Action: OMEGAMON does not process the command. User Response: Provide additional storage resources for the executing OMEGAMON. DATASET EMPTY Explanation: There were no members in the indicated OBPROC dataset for the SCRN command to display. System Action: The SCRN command displays member names in the other OBPROC datasets. This is an informational message only. NO MEMBERS FOUND WITHIN RANGE (cccccccc THRU cccccccc) Explanation: OMEGAMON found no screen names within the from/through range specified by the SCRN command. User Response: Enter a different from/through selection range. TOO MANY MEMBERS SPECIFIED Explanation: There are too many screen space members for the LSCR command to load into main storage. The maximum number is 62. System Action: OMEGAMON does not load the screen spaces into main storage. User Response: Reduce the number of members to load. OB0101 OB

162 OB1506 OB1507 OB1508 OB1509 OB1521 OB1522 OB1523 INVALID MEMBER NAME cccccccc Explanation: The LSCR command detected a screen member name that is too long or that contains invalid characters. System Action: OMEGAMON does not load the screen into main storage. User Response: Correct the screen member name on the LSCR command. LOAD FAILED - MEMBER cccccccc NOT FOUND Explanation: The user specified screen space cccccccc with an LSCR command; OMEGAMON did not find it in the OBPROC library. System Action: OMEGAMON ignores specification of screen space cccccccc and loads any other specified screen spaces. User Response: Make sure that the specified screen space exists in OBPROC or RKOMPCSV library. Check OBPROC concatenation. nnn MEMBERS LOADED Explanation: The LSCR command successfully loaded nnn screen spaces to main storage. System Action: The command executes. This is an informational message only. ENTER MEMBER NAMES TO LOAD Explanation: The LSCR command attempted to load screen spaces to main storage, but there were no member names specified. User Response: Enter member names following the LSCR command. MEMBER cccccccc DELETED BOTH IN-STORAGE AND FROM RKOMPCSV Explanation: The user specified screen space cccccccc with a DELTB command, and OMEGAMON successfully deleted it from main storage (in-storage) and RKOMPCSV. System Action: The command executes. This is an informational message only. MEMBER NAME - cccccccc NOT FOUND IN-STORAGE Explanation: The user specified screen space cccccccc with a DELTI or DELTB command; OMEGAMON did not find it in main storage (in-storage). User Response: Verify that the screen space name is correct. MEMBER cccccccc DELETED IN-STORAGE Explanation: OMEGAMON successfully deleted screen space cccccccc from main storage (in-storage) as a result of DELTB or DELTI command. System Action: The command executes. This is an informational message only. 162 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

163 OB1524 OB1525 OB1531 OB1532 OB1533 OB1534 OB1535 MEMBER cccccccc DELETED FROM RKOMPCSV Explanation: OMEGAMON successfully deleted screen space cccccccc from RKOMPCSV as a result of DELTB or DELTD command. System Action: The command executes. This is an informational message only. DELETE FAILED - cccccccc NOT FOUND IN RKOMPCSV Explanation: The user specified screen space cccccccc with a DELTB or DELTD command, and OMEGAMON did not find it in RKOMPCSV. User Response: Verify that the screen space name is correct. MEMBER oldname RENAMED TO newname BOTH IN-STORAGE AND IN RKOMPCSV Explanation: The user specified screen space oldname with a RENMB command, and OMEGAMON successfully renamed it to newname in main storage (in-storage) and in RKOMPCSV. System Action: The command executes. This is an informational message only. MEMBER NAME - cccccccc NOT FOUND IN-STORAGE Explanation: The user specified screen space cccccccc with a RENMI or RENMB command; OMEGAMON did not find it in main storage (in-storage). User Response: Verify that the screen space name is correct. MEMBER oldname RENAMED TO newname IN-STORAGE Explanation: OMEGAMON successfully renamed screen space oldname to newname in main storage (in-storage) as a result of RENMI or RENMB command. System Action: The command executes. This is an informational message only. MEMBER oldname RENAMED TO newname IN RKOMPCSV Explanation: OMEGAMON successfully renamed screen space oldname to newname in RKOMPCSV as a result of a RENMD or RENMB command. System Action: The command executes. This is an informational message only. RENAME FAILED - cccccccc NOT FOUND IN RKOMPCSV Explanation: The user specified screen space cccccccc on a RENMD or RENMB command, and OMEGAMON did not find it in main storage (in-storage). User Response: Verify that the screen space name is correct. OB0101 OB

164 OB1537 OB1538 OB1539 OB2001 OB2002 OB2003 RENAME FAILED - cccccccc DIRECTORY FULL Explanation: The PDS directory for file cccccccc is full and cannot contain additional screen space names. System Action: OMEGAMON does not rename the screen space in RKOMPCSV. User Response: Compress the PDS library or provide additional directory space. RENAME FAILED - cccccccc ALREADY EXISTS IN-STORAGE Explanation: The user issued a RENMI or RENMB command with a screen space name cccccccc that already exists in main storage (in-storage) and cannot be renamed. System Action: OMEGAMON does not change the original screen space name. User Response: Correct the new screen space name and retry the command. RENAME FAILED - cccccccc ALREADY EXISTS IN RKOMPCSV Explanation: The user issued a RENMD or RENMB command with a screen space name cccccccc that already exists in RKOMPCSV and cannot be renamed. System Action: OMEGAMON does not change the original screen space name. User Response: Correct the new screen space name and retry the command. DATA-ONLY SPACE cccccccc DOES NOT EXIST Explanation: The data-only space cccccccc specified in the command cannot be found. cccccccc is the name of the data-only space or the first 1 7 characters of the data-only space name. If cccccccc is displayed in the message as less than 8 characters, it means that there were no data-only spaces found beginning with the characters cccccccc. System Action: The command is terminated. User Response: Correct the data-only space name and reissue the command. The PEEK command may be used to find the names of data-only spaces owned by a job. DATA-ONLY SPACE cccccccc IS NOT OWNED BY JOB aaaaaaaa Explanation: Job aaaaaaaa is not the owner of data-only space cccccccc. aaaaaaaa is the jobname given in the command or the name of the job identified by the ASID. User Response: Correct the data-only space name, the jobname, or ASID and reissue the command. The PEEK command may be used to find the names of data-only spaces owned by a job s TCBs. The OSPC command may be used to find the jobname and ASID of the owning TCB of a data-only space. aaaaaaaa cccccccc HAS BEEN DELETED Explanation: The TCB owning data-only space aaaaaaaa of type cccccccc has deleted the space or has itself been terminated. The space no longer exists. System Action: The command is terminated. 164 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

165 OB2005 OB2006 OB2007 OB2008 OB2009 OB2010 OB2011 DATA-ONLY SPACE PROCESSING UNAVAILABLE - RC=nnnn Explanation: Due to an internal OMEGAMON error, OMEGAMON is unable to perform data-only space processing. User Response: Contact IBM Software Support with the return code. DATA-ONLY SPACE NAME MUST BE 8 CHARACTERS OR LESS Explanation: A data-only space name of greater than 8 characters was entered as input. User Response: Correct the name of the data-only space. The OSPC command may be issued to obtain the name of all data-only spaces in the system. DATA-ONLY SPACE NAME IS A REQUIRED PARAMETER Explanation: A data-only space command (e.g., SLST, SZAP) was issued without the name of a data-only space as input. User Response: Correct the command input by supplying a data-only space name as the second parameter. The OSPC command may be issued to obtain the name of all data-only spaces in the system. ALESERV ADD NON-ZERO RETURN CODE, RC = nn Explanation: An attempt to obtain addressability to a data space failed with return code nn. User Response: Ensure that the data space input to the affected command has not been deleted. If the data space still exists, contact IBM Software Support. HSPSERV return code, RC = xx Explanation: An attempt to access a Hiperspace failed with return code xx. ACCESS TO aaaaaaaaaa cccccccc IS NOT AUTHORIZED Explanation: An attempt was made to access a non-shareable data-only space aaaaaaaa of type cccccccc without authorization. User Response: Authorization may be obtained to non-shareable data-only spaces by issuing the command.dsaon. ACCESS TO DATA SPACE aaaaaaaa DENIED, SCOPE UNKNOWN Explanation: An attempt was made to access data space aaaaaaaa, but OMEGAMON was not able to determine the SCOPE of the data space. OB0101 OB

166 OB2100 OB2101 OB2102 OB2103 OB2104 RMF SUBROUTINE LOAD MODULE OBRMFSnn NOT AVAILABLE Explanation: OMEGAMON attempted to access module OBRMFSnn but failed. User Response: Check to make sure that the OBRMFSnn modules were copied from the OMEGAMON distribution tape. If the modules are in the OMEGAMON load library, contact IBM Software Support. RMF LEVEL nnnnn IS NOT IN TABLE Explanation: An attempt was made to set the RMF level to a level that OMEGAMON did not recognize. User Response: Check to make sure that the correct RMF level is entered on the input screen. If it is entered correctly but OMEGAMON does not recognize it, contact IBM Software Support. You may need to receive support for a new level of RMF. INPUT MUST BE EITHER nnn OR n.n.n Explanation: The operand on the RMFS command must have the format nnn or n.n.n. User Response: Correct the input to the RMFS command and press ENTER. RMF LEVEL HAS BEEN DYNAMICALLY DETERMINED - COMMAND INVALID Explanation: OMEGAMON determined the level of RMF dynamically. RMFS cannot be used to override the RMF level in this situation. This is an informational message only. RMF LEVEL UNCHANGED - UNABLE TO LOAD MODULE nnnnnnnn Explanation: An attempt was made to change to a new level of RMF, however, the required load module was not available. The RMF level stays unchanged. User Response: Make sure that the load module is copied from the installation tape. If the module is not on the tape, contact IBM Software Support. 166 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

167 OB2200 OB2201 OB2202 OB2203 SUBSYSTEM aaaa REQUEST RETURNED RC=bbbb AND ERRCODE cccccccc Explanation: A call to the Candle Subsystem has resulted in a non-zero return code. aaaa Identifies the type of request: INIT or REQ. bbbb Identifies the return code. 4 Internal error A common cause of this return code is a version or maintenance level mismatch between the running Candle subsystem and the product issuing the message. If you have multiple SMP/E environments make sure that all have the same Candle subsystem FMID and maintenance installed. cccccccc 8 Subsystem not active 20 Subsystem module not found Identifies the error code. System Action: The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. You may also need a later version of the Candle Subsystem. CN SUBSYSTEM INACTIVE. STATIC DEVICE TABLE IS USED Explanation: The interface to the Candle Subsystem determined that the Candle Subsystem is inactive. System Action: The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. User Response: Activate the Candle Subsystem. CN SUBSYSTEM NOT DEFINED. STATIC DEVICE TABLE IS USED Explanation: The interface to the Candle Subsystem determined that the Candle Subsystem is not defined. System Action: The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. User Response: Define the Candle Subsystem. SSCVT CHAIN NOT VALID. STATIC DEVICE TABLE IS USED Explanation: The interface to the Candle Subsystem determined that the SSCVT chain is not valid. System Action: The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. User Response: Define the Candle Subsystem and IPL the system. OB0101 OB

168 OB2204 OB2205 OB2206 OB2207 OB4101 OB4222 CNSS INTERFACE MODULE NOT FOUND. STATIC DEVICE TABLE IS USED Explanation: The interface to the Candle Subsystem cannot load the Candle Subsystem interface module (KCNDLI). System Action: The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. User Response: Ensure that OMEGAMON can access the Subsystem interface module through STEPLIB, JOBLIB, LINKLST or LPALST concatenation. CONFIGURATION CHANGE PENDING Explanation: The interface to the Candle Subsystem determined that configuration change is pending. System Action: The interface to the Candle Subsystem returns the address of dynamic device table. DYNAMIC DEVICE TABLE IS OBSOLETE Explanation: The interface to the Candle Subsystem determined that the dynamic device table is obsolete. System Action: The interface to the Candle Subsystem returns the address of the dynamic device table. User Response: Reissue command causing such a message. FUNCTION aaaa IS NOT AVAILABLE RC=bbbb Explanation: A call to a function residing in the Candle Subsystem resulted in non-zero return code. aaaa Identifies the function: DIOC. bbbb Identifies the return code. System Action: The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. MEMORY FOR USER PROFILE TABLES NOT AVAILABLE Explanation: There is not enough memory available for the user profile tables. User Response: Increase the region size and retry. UNABLE TO LOCATE REQUIRED LEVEL-DEPENDENT BASE MODULE KOBASnnn Explanation: OMEGAMON attempted to locate the corresponding base module required for the current operating system level. The required module could not be found. System Action: OMEGAMON terminates. User Response: Make sure that OMEGAMON is executed at the operating system level for which your installation is licensed. Contact IBM Corporation for licensing and sales information. 168 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

169 OB4223 OB7001 OB7002 OB7003 OB7004 OB7005 OB7006 CURRENT OPERATING SYSTEM LEVEL NOT SUPPORTED Explanation: OMEGAMON has determined that the current operating system level is not supported. Only MVS/SP 1, 2, and 3 are supported; earlier versions are not supported. (SP 1 support is further limited to SP 1.3 and above.) System Action: OMEGAMON terminates. User Response: Run OMEGAMON only on those systems with supported operating system levels. OVUSERcc DATA FILE NOT FOUND Explanation: The OVUSERcc DATA file specified by USER xx in the startup parms or the.usr command was not found. System Action: OMEGAMON uses all default values for execution parameters. The default OVUSER DATA file is 99. User Response: Continue with OMEGAMON initialization or restart OMEGAMON specifying the correct USER startup parameter value, or reissue the.usr command specifying the correct parameter. INVALID SWITCH SETTING - MUST BE ON OR OFF Explanation: The indicated parameter must be specified as either ON or OFF. System Action: OMEGAMON uses the default value. User Response: Correct the parameter value to specify ON or OFF at next execution. INVALID PARAMETER Explanation: The indicated word is not a valid OMEGAMON startup parameter. System Action: OMEGAMON ignores the entire parameter group (including any possible subordinate keywords). User Response: Check for spelling problems. Check to make sure that a previous parameter was not continued incorrectly. INVALID SYNTAX Explanation: The format of the indicated input stream is invalid. System Action: OMEGAMON ignores either all or part of the current parameter group. User Response: Correct the formatting error. Ensure that all required delimiters (commas, parentheses, and so on) are entered correctly. INVALID CHARACTER - ACCEPTED AS DELIMITER Explanation: An invalid character was found in the input stream. System Action: The character is assumed to be a delimiter. User Response: Enter a valid character if a delimiter was not intended. INVALID KEYWORD Explanation: The indicated word is not a valid keyword for the current parameter group being processed. System Action: OMEGAMON ignores the keyword. User Response: Check for possible spelling or continuation errors. OB0101 OB

170 OB7007 OB7008 OB7009 OB7010 OB7011 OB7012 OB7013 INVALID KEYWORD VALUE Explanation: The value specified for the indicated parameter keyword is invalid. System Action: OMEGAMON ignores the keyword. User Response: Specify the keyword value as required. INVALID HEX DATA Explanation: EBCDIC characters were specified for a keyword requiring hexadecimal data. System Action: OMEGAMON ignores the keyword. User Response: Correct the keyword value. INVALID NUMERIC DATA Explanation: EBCDIC characters were specified for a keyword requiring numeric data. System Action: OMEGAMON ignores the keyword. User Response: Correct the keyword value. KEYWORD VALUE OR LENGTH BELOW ALLOWED MIN Explanation: The value specified for the indicated keyword is either too short (character) or too small (integer or hex). System Action: OMEGAMON ignores the keyword. User Response: Check the minimum that can be specified for the keyword and correct the keyword value. KEYWORD VALUE OR LENGTH ABOVE ALLOWED MAX Explanation: The value specified for the indicated keyword is either too long (character) or too large (integer or hex). System Action: OMEGAMON ignores the keyword. User Response: Check the maximum that can be specified for the keyword and correct the keyword value. DUPLICATE PARAMETER Explanation: A duplicate keyword has been found in the input stream. System Action: OMEGAMON ignores the duplicate parameter. User Response: Remove or correct the duplicate keyword. MISSVM LIMIT EXCEEDED Explanation: The internal buffers required to hold the data specified by the OVUSER MISSVM parameter have overflowed. System Action: The MISSVM keyword specifications that will fit in storage will be accepted with the remainder ignored. User Response: Increase the virtual storage size of the OMEGAMON for VM virtual machine or specify few MISSVM keyword values. 170 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

171 OB7014 OB7017 OB7018 OB7019 OB7020 OB7021 MISSDA LIMIT EXCEEDED Explanation: The internal buffers required to hold the data specified by the OVUSER MISSDA parameter have overflowed. System Action: The MISSDA keyword specifications that will fit in storage will be accepted with the remainder ignored. User Response: Increase the virtual storage size of the OMEGAMON for VM virtual machine or specify few MISSDA keyword values. USERID OR ACCOUNT NOT SPECIFIED Explanation: For the PGNAMES parameter a USERID= or ACCOUNT= keyword was expected and not found. System Action: OMEGAMON ignores the entire PGNAMES parameter group. User Response: Check for a spelling error to ensure that either a USERID= or an ACCOUNT= keyword is specified. UNEXPECTED END-OF-FILE RECEIVED Explanation: While processing a continuation, the end of the OVUSERcc DATA file was reached. System Action: OVUSERcc parameter processing terminates. User Response: Check to see if the OVUSER DATA file is complete. If not, enter the missing parameter keyword(s). NAME= KEYWORD MISSING Explanation: The NAME keyword was not specified on the PGNAME statement. System Action: OMEGAMON ignores the entry. User Response: The PGNAME statement requires a name for each group being defined. Specify a name. UNBALANCED OR INVALID USE OF PARENTHESES Explanation: Either an unexpected parenthesis was detected or an expected parenthesis was not detected. System Action: OMEGAMON ignores either the current keyword or the remaining parameter keywords. User Response: Add or remove parentheses as required. MAXIMUM 64 PERFORMANCE GROUP NAMES ALLOWED Explanation: For the PGNAMES parameter group more than 64 performance groups were specified. System Action: OMEGAMON ignores the remaining performance groups. User Response: Remove less important performance groups so that the maximum will not be exceeded. OB0101 OB

172 OB7022 OB7023 OB7024 OB7025 OB7026 OB7027 OB7028 INVALID cccccccc THRESHOLD GROUP KEYWORD Explanation: A keyword for the DEFVMTG, DASDTG, or RSCSTG parameter was entered that is not a valid exception override name. System Action: OMEGAMON ignores the keyword. User Response: Check for a possible spelling error. For DEFVMTG, ensure that the exception name entered is a valid VM exception and not a SYSTEM exception. For DASDTG, ensure that the exception name entered is one of the DASD exceptions. For RSCSTG, ensure that the exception name entered is RSCA or RSCQ. ON/OFF EXPECTED, ON ASSUMED Explanation: The indicated parameter must be specified as either ON or OFF. System Action: The keyword value defaults to ON. User Response: Correct the parameter value to specify ON or OFF. EXPECTED PARENTHESIS NOT FOUND Explanation: A parenthesis was expected at or near the column indicated by an asterisk. System Action: OMEGAMON ignores the current keyword. User Response: Check the format for the keyword and make the appropriate corrections. EXPECTED ON OR AUTO, AUTO ASSUMED Explanation: The indicated parameter must be specified as either ON or AUTO. System Action: Missing VM analysis for this VM user ID defaults to AUTO. User Response: Correct the parameter value to specify ON or AUTO. THRESHOLD EXCEEDS THE MAXIMUM ALLOWED, MAXIMUM WILL BE USED Explanation: The value specified for the THRESH= keyword is larger than the value allowed for an exception name. System Action: OMEGAMON uses the maximum value allowed. User Response: Check the maximum value for this exception name and correct the keyword value. THRESHOLD LESS THAN MINIMUM ALLOWED, MINIMUM WILL BE USED Explanation: The value specified for the THRESH= keyword is less than the value allowed for an exception name. System Action: OMEGAMON uses the minimum value allowed. User Response: Check the minimum value for this exception name and correct the keyword value. EXPECTED TIME=, SS=, OR SL= KEYWORD NOT RECEIVED Explanation: An invalid keyword was received for the TSF parameter group. The only valid keywords are TIME=, and either SS= or SL=. System Action: OMEGAMON ignores the remaining TSF keywords. User Response: Check for possible spelling problems. 172 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

173 OB7029 OB7030 OB7031 OB7032 OB7033 OB7036 BOX= KEYWORD INVALID FOR VM EXCEPTIONS. ENTER OK TO CONTINUE OR C TO CANCEL. Explanation: The BOX= keyword was specified and is not valid for a VM exception. System Action: OMEGAMON ignores the BOX= keyword. User Response: Reply OK or C, then remove the BOX= keyword from this exception. CHNM CPUID INVALID Explanation: The value specified for the CPUID= keyword is invalid (must be between 0 and 15) for the CHNM parameter group. System Action: OMEGAMON skips the CPUID= keyword and subsequent CHANNELS= keywords. User Response: Specify the correct CPU identification. CHNM CHANNEL NUMBER INVALID Explanation: One of the values specified for the CHANNELS= keywords is invalid for the CHNM parameter group (must be between 0 and 31). System Action: OMEGAMON ignores the channel ID value. User Response: Specify the correct channel ID. CPUID= KEYWORD MISSING Explanation: The CPUID= keyword for the CHNM parameter group was expected and not received. System Action: OMEGAMON ignores the subsequent CHANNELS= parameter. User Response: Check for spelling errors or enter a CPUID= keyword preceding the CHANNELS= keyword. CHANNELS= KEYWORD MISSING Explanation: The CHANNELS= keyword for the CHNM parameter group was expected and not received. System Action: OMEGAMON ignores the current CPUID= value. User Response: Check for spelling errors or enter a CHANNELS= keyword following the CPUID= keyword. DUPLICATE KEYWORD FOUND Explanation: OMEGAMON encountered a duplicate keyword in OVUSER. System Action: OMEGAMON displays the message and asks if you wish to continue. User Response: Reply OK to continue processing and ignore the error or type C to cancel and correct the OVUSER file. OB0101 OB

174 OB7037 OB7038 OB7039 OB7040 OB7041 OB7042 OB7101 INCLUDE OR EXCLUDE NOT SPECIFIED Explanation: OMEGAMON requires either an INCLUDE or EXCLUDE list to be specified with the FORCE parameter in OVUSER. System Action: OMEGAMON displays the message and asks if you wish to continue. User Response: Reply OK to continue processing and ignore the error or type C to cancel and correct the OVUSER file. FORCE PARAMETER VALID ONLY FOR VM EXCEPTIONS Explanation: OMEGAMON encountered the FORCE parameter on an exception that is not VM user-related. Force processing is not valid for other than user-related exceptions. System Action: OMEGAMON displays the message and asks if you wish to continue. User Response: Reply OK to continue processing and ignore the error or type C to cancel and correct the OVUSER file. SCREEN SPACE NOT FOUND Explanation: The indicated screen space name (with filetype PROCFILE) was not found on any accessed CMS disk. System Action: The screen space name is accepted. The error message displays as a warning. User Response: Correct the screen space name or create a new screen space with this name. TABLE WORK AREA OVERFLOW Explanation: An internal storage buffer overflowed processing the indicated parameter or keyword.l System Action: Processing terminates for the current parameter. User Response: Increase your virtual storage size or decrease the number of operands of this parameter. INTERNAL ERROR OBTAINING WORK BUFFERS Explanation: An internal error occurred attempting to acquire storage. System Action: OVUSERcc processing terminates. User Response: Call IBM Software Support Services. KEYWORD DOES NOT APPLY TO THIS EXCEPTION Explanation: The indicated keyword does not pertain to the current exception name being processed. System Action: OMEGAMON ignores the keyword. User Response: Remove the keyword from this exception parameter. ERROR, COMMAND ARGUMENT UNKNOWN Explanation: An invalid operand was given to the command. User Response: For the proper operands, see the extended help (;commandname) for the command. Correct the operand and retry. 174 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

175 OB7102 OB7103 OB7104 OB7105 OB7106 OB7107 OB7108 OB7109 OB7110 USER TABLE HAS BEEN DELETED Explanation: OMEGAMON deleted the user table. System Action: Processing continues. This is an informational message only. NAME NOT IN TABLE Explanation: The requested name cannot be found in the tables. User Response: Correct the name and retry the command. cccccccc HAS BEEN DELETED Explanation: The indicated memory location symbol was deleted from the symbolic address table. System Action: Processing continues. This is an informational message only. cccccccc HAS BEEN ADDED TO THE TABLE Explanation: The indicated memory location symbol was added to the symbolic address table. System Action: Processing continues. This is an informational message only. TABLE DOES NOT EXIST Explanation: No entries have been defined in the table. This is an informational message only. WORKAREA OVERFLOW Explanation: The internal work area for string manipulation has overflowed. User Response: Use shorter strings to define the storage locations. PLPA MZAP CANNOT CROSS PAGE BOUNDARY Explanation: The zap would cross a page boundary and this is not allowed. System Action: Command terminates. This is an informational message only. PLPA PAGES FIXED Explanation: OMEGAMON fixed PLPA pages as requested. System Action: Processing continues. This is an informational message only. MEMORY ZAP SUCCESSFUL Explanation: OMEGAMON successfully executed the MZAP command. System Action: Processing continues. This is an informational message only. OB0101 OB

176 OB7111 VERIFY REJECT - MEMORY NOT ZAPPED Explanation: The verify data in the command does not match the data in storage. User Response: Correct the data and retry. OB7112 SCAN DATA NOT FOUND Explanation: The requested data could not be found within the scan limits. This is an informational message only. OB7113 DYNAMIC ADDRESS NOT RESOLVED Explanation: A symbol in a dynamic address string could not be resolved. User Response: Correct the symbol and retry the command. OB7114 MODULE NOT AVAILABLE Explanation: An OMEGAMON module address was found to be 0, indicating that it is not available for this command. This is an informational message only. OB7115 OMEGAMON NAME INVALID IN CROSS MEMORY Explanation: The cross memory commands are not allowed against this address space. User Response: Use the appropriate local commands. OB7117 INDIRECT ADDRESS IS 0 Explanation: The address pointer value was 0 when an indirect request (? or %) was encountered while interpreting the address string. This is not necessarily an error. OB7118 JOB NOT FOUND Explanation: The requested address space or jobname cannot be found. User Response: Correct the name and retry. OB7119 OB7120 REGION DOES NOT BELONG TO CL/SUPERSESSION and CLGATEWAY Explanation: A cross-memory zap was attempted on an unauthorized region. User Response: Make sure that the zap is being applied to the correct region. USE cccc FOR OMEGAMON PRIVATE AREA Explanation: A cross memory command was used where a local command is appropriate. User Response: Use the local command format. 176 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

177 OB7121 OB7122 OB7123 OB7125 OB7126 OB7127 OB7128 OB7129 OB7130 ADDRESS IN COMMON AREA - USE cccc Explanation: A cross memory command was used where a local command is appropriate. User Response: Use the local command format. GENERATED ADDRESS INVALID - xxxxxxxx Explanation: The displayed address was developed while interpreting the address string. It is not valid for the named address space. User Response: Correct as necessary. TARGET ADDRESS INVALID - xxxxxxxx Explanation: The displayed address was used to fetch data and is not a valid target address. User Response: Correct and retry. VERIFY FAILED - ACTUAL CODE WAS: nn Explanation: The verify data does not match the storage data. User Response: Correct and retry. INVALID RETURN CODE - cc = nn Explanation: The SRB that was scheduled returned an unknown code. {TARGET INDIRECT} ADDRESS xxxxxxxx IS STORE PROTECTED Explanation: The target/indirect address xxxxxxxx is store-protected and should not be modified. User Response: Use the action character if APF-authorized and retry. {TARGET INDIRECT} ADDRESS xxxxxxxx IS FETCH PROTECTED Explanation: The target/indirect address xxxxxxxx is fetch-protected and cannot be read. User Response: Use the action character if APF-authorized and retry. {TARGET INDIRECT} ADDRESS xxxxxxxx DOES NOT EXIST Explanation: The target/indirect address xxxxxxxx cannot be located. User Response: Correct the address and retry. TRUNCATION HAS OCCURRED AT PAGE BOUNDARY Explanation: The current display truncated because of an invalid address. The next page of storage is either undefined or fetch-protected. User Response: Correct the address or length and retry. OB0101 OB

178 OB7131 OB8110 OB8111 OB8112 OB8113 OB8114 SUBSTITUTION SYMBOL NOT DEFINED - cccccccc Explanation: The MDEF command could not define the substitution symbol cccccccc. OMEGAMON cannot define a substitution symbol that begins with an ampersand (&). User Response: Replace the ampersand with another character and retry the MDEF command. NOT ENOUGH REGION FOR WORKAREA - nnnk MORE NEEDED Explanation: The specified command could not obtain a work area. User Response: Increase the region size of the address space by a minimum of nnnk. Alternatively, use the WSIZ minor of PEEK or FNDU to decrease the work area size by nnnk. WARNING - WSIZ TOO SMALL ADDR= xxxxxx, SIZE = yyyyyy, USED =zzzzzz Explanation: The FNDU or PEEK SRB to collect data failed to complete its task because the data area it needed was too small. User Response: Use the WSIZ minor of FNDU or PEEK to increase the work area. DATA COLLECTION INITIATED Explanation: The command was issued with the action character, and OMEGAMON was collecting. This is an informational message only. WARNING cccc FAILED VALIDITY CHECK Explanation: The SRB to collect data failed to complete its task because a control block does not contain valid data. The variable cccc is one of the following control blocks: ASCB DSAB JFCB JFCX TCB User Response: Re-enter the command. You may want to list the control block and verify its contents. WARNING - POSSIBLE LOOP DETECTED IN SRB ROUTINE Explanation: The SRB to collect data failed to complete its task (possibly because the SRB is in a loop). xxxx is the hex offset into the PEEK module. User Response: If the problem persists, contact IBM Software Support. 178 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

179 OB8115 OB8116 OB8117 OB8118 OB8121 OB8130 OB8131 OB8132 OB8202 WARNING - INVALID RETURN CODE - RC = nn Explanation: The SRB routine returned a nonstandard code. System Action: The PEEK process terminates. User Response: If the error persists, contact IBM Software Support. DANGER - INSUFFICIENT SQA, COMMAND ABORTED Explanation: There is insufficient SQA. System Action: The command aborts. User Response: Try the command later when more SQA is available. INSUFFICIENT MEMORY FOR SRB SAVE AREA Explanation: There is insufficient memory for the save area. User Response: Try the command later when there is more memory available. SRBD - SRB FAILED DURING INITIALIZATION Explanation: The SRB failed during initialization. CHANNEL SET NOT DEFINED Explanation: The user requested an invalid channel set. System Action: Command processing terminates. User Response: Correct command parameters and retry. COMMAND TEXT IS TOO LONG Explanation: The command text can be a maximum of 126 characters. System Action: The command is not executed. User Response: Specify the command text so that it is no more than 126 characters. INVALID CHARACTER AFTER SYSTEM NAME Explanation: The system name was not followed by a blank space or by a comma. System Action: The command is not executed. User Response: Supply a system name followed by a blank space or a comma. SYSTEM NAME IS TOO LONG, MUST BE 1 8 CHARS Explanation: System names must be from 1 8 characters in length. System Action: The command is not executed. User Response: Supply a valid system name. CPU NOT DEFINED Explanation: The CPU is not defined in the PCCA. User Response: Specify a CPU that is defined to your system (see the IBM OS/VS2 System Programming Library or MVS/Extended Architecture Debugging Handbooks for a CPU definition). OB0101 OB

180 OB8203 NO CHANNEL AVAILABILITY TABLE Explanation: The specified channel does not exist. User Response: Specify a channel number that exists on the system. OB8204 LINK ERROR, CODE = {8 12} Explanation: The external routine for GDEV encountered a link error. OB8205 INVALID INPUT - aaaaaaaaaaaaaaa Explanation: An invalid device class was entered as input to the GLST command. System Action: The GLST command is terminated. User Response: Correct the invalid input parameter. The help text for the GLST command displays the valid input parameters. OB8206 PROCESSING ERROR, DEVICE CLASS aaaa, RC=nn Explanation: The EDTINFO interface routine used by the GLST command returned with a non-zero return code, nn, processing device class aaaa. System Action: Processing continues, but that device class will not be displayed. OB8207 OB8208 SUBSYSTEM RETURN CODE aaaaaaaa bbbbbbbb cccccccc dddddddd Explanation: A call to the Candle Subsystem has resulted in a non-zero return code during execution of the GDEV command. aaaaaaaa Identifies the Subsystem return code. bbbbbbbb Identifies the function return code. cccccccc Identifies the subroutine invocation return code. dddddddd Identifies the subroutine invocation reason code. System Action: The GDEV command continues to process, however, there will be no data for devices defined as dynamic. CN SUBSYSTEM NOT INITIALIZED Explanation: A contact to the Candle Subsystem cannot be made because the Candle Subsystem has not been initialized by this OMEGAMON session. System Action: The GDEV command continues to process, however, there will be no data for devices defined as dynamic. User Response: Check to see that the Candle Subsystem is running on the system. If it is not running, start it. If it is running, contact IBM Software Support. 180 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

181 OB8209 UCB INFORMATION UNAVAIABLE. RC=xxxxxxxx yyyyyyyy zzzzzzzz Explanation: A call to internal OMEGAMON service to obtain UCB information resulted in a non-zero return code. xxxxxxxx Register 15 contains the return code. yyyyyyyy Register 0 contains the reason code. zzzzzzzz Register 1 contains the associated reason code. System Action: The OMEGAMON command is terminated. OB8277 SYNTAX ERROR NEAR COLUMN FLAGGED ABOVE Explanation: A syntax error was found in the input command line. An asterisk (*) marks the start of the invalid field. User Response: Verify the command syntax, correct the input as needed, and retry the command. OB8280 CONSOLE NOT FOUND Explanation: The console ID or device address specified located a type of device other than a console. User Response: Specify a valid console ID or device address. OB8281 HARDCOPY DEVICE Explanation: The console specified in the CONS command is a hardcopy device and therefore cannot be monitored. User Response: Select a non-hardcopy device to monitor. OB8282 INVALID CONSOLE NAME, MUST BE 2 8 CHARS Explanation: Console names must be from 2 8 characters. The first character must be A #, or $, and subsequent characters must be A #, $, or 0 9. System Action: The command is not executed. User Response: Supply a valid console name or console ID number. OB8283 INVALID CONSOLE ID NUMBER, MUST BE 1 99 Explanation: Console ID numbers must be from System Action: The command is not executed. User Response: Supply a valid console ID number or console name. OB8284 MISSING CONSOLE VALUE Explanation: Either a console name or console ID number must be supplied after the CONS= keyword. System Action: The command is not executed. User Response: Supply a valid console name or console ID number. OB0101 OB

182 OB8285 OB8286 OB8287 OB8288 OB8289 OB8290 OB8291 OB8292 INVALID CHARACTER AFTER CONSOLE VALUE Explanation: The console name or console ID number was not followed by a blank space or by a comma. System Action: The command is not executed. User Response: Supply a valid console name or console ID number, followed by a blank space or a comma. CONSOLE DOES NOT EXIST OR IS INACTIVE Explanation: The console specified is not defined to the operating system, or is defined but not active. System Action: The command is not executed. User Response: Supply a valid console name or console ID number. INCREASE GDEV UCB SLOTS TO MORE THAN nnnnn Explanation: OMEGAMON needs more than nnnnn slots for GDEV command UCBs. User Response: Increase the number of slots to more than nnnnn. NO ONLINE DEVICES FOUND WITH THIS GENERIC Explanation: No online devices match the generic name specified. User Response: Try another generic name. DLIST OFFSET GREATER THAN DLIST TABLE Explanation: The DLIST offset calculation is greater than that allowed in the DLIST table. NO GENERIC DEVICE NAME SUPPLIED Explanation: A generic device name was expected. User Response: Enter a generic device name. Use the GLST device major command to list valid generic names for your site. NO GENERIC DEVICES DEFINED FOR THIS NAME Explanation: No devices were defined for the generic name specified. User Response: Enter a different generic device name. GENERIC DEVICE NAME TOO LONG Explanation: A generic device name must be 8 characters or less. User Response: Enter a valid device name with 8 characters or less. 182 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

183 OB8293 OB8294 OB8295 OB8296 OB8310 OB8312 OB8313 OB8320 NO MATCH FOUND FOR THIS GENERIC NAME Explanation: The generic device name specified is not defined at your installation. User Response: Use the GLST device major command to list all defined generic device names. IGNORED - DEVICE NOT ALLOCATED, ONLINE DASD OR TAPE Explanation: An attempt was made to deallocate a device that was either offline or was not a disk/tape. User Response: Specify an online disk or tape. IGNORED - DEVICE IS PERMANENTLY RESIDENT Explanation: An attempt was made to deallocate a permanently resident volume. User Response: Specify a volume that is not permanently resident. IGNORED - DEVICE NOT PERMANENTLY RESIDENT Explanation: An attempt was made to mark a device reserved that was not permanently resident. User Response: Specify a volume that is permanently resident. JOB NOT FOUND Explanation: The requested jobname could not be found in the queue of currently running jobs. System Action: The PEEK command is suppressed. User Response: Correct the jobname. PEEK COMMAND NOT SUCCESSFULLY EXECUTED Explanation: An error prevented the PEEK command from executing. System Action: The PEEK command is suppressed. User Response: Observe prior error messages and take appropriate action. NO cccc INFORMATION AVAILABLE FOR *MASTER* ADDRESS SPACE Explanation: The control blocks necessary to map virtual storage for the *MASTER* address space using the cccc minor of PEEK are incomplete or absent. These commands are not supported for the *MASTER* address space. RETURN FETCH DELAYED Explanation: The return was delayed due to a cycle count in the command label. System Action: The command continues normally. This is an informational message only. OB0101 OB

184 OB8321 OB8322 OB8323 OB8324 OB8325 OB8326 OB8327 OB8501 OB8551 RETURN FETCH PENDING Explanation: A return is scheduled for the next cycle. This is an informational message only. PROCFILE DD STATEMENT MISSING Explanation: The indicated DD statement is missing from the job s JCL. User Response: Add the statement and restart OMEGAMON. NOT IN AUTOMATIC MODE - RETURN IGNORED Explanation: The command is valid only in automatic mode. System Action: The command terminates without taking action. User Response: Correct the command or use only in automatic mode. NO TARGET SCREEN SPACE Explanation: The target screen space name is missing. User Response: Supply a correct name and retry the command. ENTRY DOES NOT EXIST - MUST BE ADDED TO OBUSERcc Explanation: A search of the currently active OBUSER module failed to find the required entry. User Response: Check the name and verify the libraries. SCREEN SPACE cccccccc NOT FOUND Explanation: The specified screen space name was not in OBPROC. Either it is missing or the name is incorrect. User Response: Correct the screen space name and verify the libraries. Retry the command. INVALID VALUE cccccc FOR KEYWORD aaaaaa SPECIFIED, INPUT IGNORED Explanation: The value cccccc supplied for keyword aaaaaa is not valid. System Action: OMEGAMON ignores the invalid input and continues processing. User Response: Correct the keyword value and retry the command. XLF/TSF FUNCTIONS DISABLED Explanation: The XLF/TSF functions are not available with this level of OMEGAMON. System Action: The associated commands are inoperative. User Response: Use a level of OMEGAMON that has these functions. LOG RESET REQUIRED. USE.XLFOUT. Explanation: Changes made to the log file require that it be reset. System Action: The command continues. User Response: To activate the new parameters, reset the log as indicated. 184 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

185 OB8601 LOG RESET FAILED. INVALID cccccccc FIELD. Explanation: The log reset failed because of the invalid field. System Action: The log is not available. User Response: Look up dynamic allocation in the appropriate IBM manual and retry the reset command. OB8602 LOG RESET FAILED. CODE cccccccc,nnnn,xxxx Explanation: The log reset failed because of a bad return code from the dynamic allocation routine. The variable cccccccc is a return code. The variable nnnn is an error code. The variable xxxx is an error reason code. System Action: The log is not available. User Response: Look up the dynamic allocation return code in the appropriate IBM manual and retry the reset command. OB8603 DDNAME NOT AVAILABLE. SYSOUT USED Explanation: The ddname specified is not allocated or is in use by another session. System Action: The system used SYSOUT. User Response: If the ddname is not being used by another session, correct the spelling or allocate the intended ddname and retry the reset command. If it is in use by another session, use another ddname, wait for the other session to be done, or accept the system use of SYSOUT. OB8604 LINE COUNT MUST BE NUMERIC Explanation: An attempt was made to enter a non-numeric line count. User Response: Correct the line count value and reissue the command. OB8605 LINE COUNT GREATER THAN 255 Explanation: An attempt was made to enter a line count greater than the maximum of 255. User Response: Correct the line count value and reissue the command. OB9001 BAD OPEN ON CONTROL STATEMENT FILE (SYSIN) Explanation: This is probably the result of a missing SYSIN DD statement in the JCL. System Action: The update terminates. OMEGAMON does not process any updates. User Response: Include a SYSIN DD statement in the job s JCL and resubmit the job. OB9003 BLANK CARD - IGNORED Explanation: OMEGAMON encountered a blank card in the input stream. System Action: OMEGAMON ignores the blank card and continues the edit and update. User Response: Remove the blank record from control record input. Verify that the record was intentionally blank. OB0101 OB

186 OB9004 OB9005 OB9006 INVALID CONTROL STATEMENT FORMAT Explanation: The syntax or the spelling of the control statement was incorrect. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the syntax or spelling and resubmit the statement. INVALID LEVEL NUMBER SPECIFIED. PASSWORD IGNORED Explanation: OMEGAMON allows only level number 1, 2, or 3 as valid level numbers for passwords. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the level number and resubmit the statement. INVALID LEVEL NUMBER. DEFAULT OF 0 ASSIGNED Explanation: You specified an invalid level number for a command. Valid level numbers are 0, 1, 2, or 3. System Action: OMEGAMON assigns a default level of 0 to the command in question. OMEGAMON continues the edit and update. User Response: Correct the level number in the control statement and resubmit it if it is other than 0. OB9007 INVALID KEYWORD SPECIFIED Explanation: The keyword specified does not exist or is not valid on this statement. (For example, VOLUME= is invalid on a COMMAND statement, and LEVEL= is invalid on an AUTHLIB statement.) System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Verify the keywords on the control statement to make sure that they belong together. When you find the error, correct it and resubmit the new control statements. OB9008 LEVEL KEYWORD MUST BE SPECIFIED WITH PASSWORD. PASSWORD IGNORED Explanation: OMEGAMON did not find the LEVEL= keyword. The PASSWORD statement requires a LEVEL= parameter to specify the password level. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Add a LEVEL= keyword to all PASSWORD= statements and resubmit the job. OB9009 INVALID COMMAND LENGTH. INFO-LINE COMMANDS MUST BE 1 THROUGH 8 CHARACTERS PLUS A SLASH Explanation: The security installation utility detected an INFO-line command that was longer than eight characters, not including the slash (/). System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the command name and resubmit it. 186 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

187 OB9010 INVALID EXTERNAL VALUE SPECIFIED. DEFAULT OF NO ASSIGNED Explanation: The security installation utility detected an invalid value for the EXTERNAL= keyword. System Action: OMEGAMON assumes EXTERNAL=NO on this statement and continues the edit and update. User Response: Correct the value of the EXTERNAL keyword, and resubmit the statement. OB9011 INTERNAL ERROR IN MESSAGE PROCESSING ROUTINE. NOTIFY CANDLE CORPORATION Explanation: OMEGAMON encountered an error in the message processing routine. System Action: The job terminates. User Response: Record any console messages and contact IBM Software Support. OB9012 PASSWORD IS OF AN INVALID LENGTH. MUST BE BETWEEN 1 AND 8 CHARACTERS Explanation: The security installation utility detected a password that is not 1 8 characters long. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the length of the password and resubmit the statement. OB9013 IMPROPER LENGTH FOR DSNAME Explanation: The security installation utility detected a dataset name of improper length. The dataset name for the AUTHLIB keyword must follow the standard rules for dataset names (no imbedded blanks or special characters, and 44 or less characters in length). System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the dataset name and resubmit the statement. OB9014 MAJOR AND MINOR COMMANDS MUST BE 3 TO 4 CHARACTERS LONG. STATEMENT IGNORED Explanation: The security installation utility detected a major or minor command that was not 3 4 characters long. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the major or minor command name and resubmit it. OB0101 OB

188 OB9015 OB9016 OB9017 OB9018 OB9019 OB9020 AUTHLIB ALREADY SPECIFIED. STATEMENT IGNORED Explanation: The security installation utility detected more than one AUTHLIB statement in this run. OMEGAMON only allows one AUTHLIB statement per update run. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Make sure that the AUTHLIB statements OMEGAMON found did not have conflicting information. Remove extra AUTHLIB statements and resubmit if necessary. PASSWORD FOR THIS LEVEL NUMBER ALREADY SPECIFIED. THIS PASSWORD IGNORED Explanation: You can only specify one password for a specific level number. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Make sure that you specified the correct level number for this password. Correct and resubmit if necessary. INTERNAL ERROR DETECTED IN UPDATE PROCESS. CONTACT IBM CORP. Explanation: OMEGAMON encountered an error in the security update program. System Action: The job terminates. COMMAND NOT DEFINED Explanation: You specified an invalid major, minor, or INFO-line command name, or a command not supported under this operating system (for example, an XA command under a 370 system). System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Check for spelling errors. Correct the command and resubmit it. *** WARNING *** - UPDATE CANCELLED Explanation: This is usually the result of processing the UPDATE=NO control statement. The message appears after the end of the control statement input. If you specified LIST=YES, the listing reflects the contents of the security file as if the changes have already taken place. System Action: OMEGAMON cancels the update. This is an informational message only. INVALID VOLUME SERIAL NUMBER FORMAT Explanation: OMEGAMON found an invalid volume serial number. A valid volume serial number or the characters NOVOLUME are the only values OMEGAMON allows. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the volume serial number and resubmit the statement. 188 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

189 OB9021 OB9022 OB9023 OB9024 OB9025 OB9026 INVALID VALUE SPECIFIED FOR AUDIT KEYWORD. MUST BE YES OR NO Explanation: The security installation utility detected an invalid value for the AUDIT keyword. The AUDIT keyword only accepts the values YES or NO. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Resubmit the statement specifying a valid value for the AUDIT= keyword. WARNING INVALID LEVEL NUMBER FOUND IN COMMAND TABLE FOR THIS COMMAND Explanation: Security update was attempted on an OMEGAMON version that does not support external security. System Action: The job terminates. User Response: Verify that you are using a current level of OMEGAMON. INTERNAL ERROR IN LIST ROUTINE. CONTACT IBM CORPORATION Explanation: OMEGAMON encountered an error in the security update program. System Action: The job terminates. MULTIPLE UPDATE STATEMENTS ENCOUNTERED. UPDATE CANCELLED Explanation: The security update utility found more than one update control statement in this run. OMEGAMON only allows one UPDATE= statement per run. System Action: OMEGAMON continues the edit but cancels the update. User Response: Remove the extra update statements from the control statement input. INVALID KEYWORD VALUE. ACCEPTABLE VALUES ARE YES OR NO Explanation: OMEGAMON received an invalid value for a specified keyword. OMEGAMON only accepts the values YES or NO. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Correct the keyword value and resubmit the statement. LIST STATEMENT ALREADY SPECIFIED. STATEMENT IGNORED Explanation: The security update utility found more than one LIST statement in this run. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Remove the extra LIST= statements from the control statement input. OB0101 OB

190 OB9027 OB9028 OB9029 OB9030 OB9031 OB9032 OB9033 ALIASES OF INFO-LINE (SLASH) COMMANDS CANNOT BE UPDATED. ACTUAL COMMAND NAME MUST BE SPECIFIED Explanation: When you protect an INFO-line command, OMEGAMON also protects its aliases. You cannot protect only an alias. The security file listing identifies the aliases. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Resubmit with the actual command name. INTERNAL ERROR DETECTED IN INFO-LINE COMMAND TABLE SEARCH. CONTACT IBM CORP. Explanation: OMEGAMON encountered an error in the security update program. System Action: The job terminates. VOL= KEYWORD MUST BE SPECIFIED FOR AUTHLIB. ENTER VOL=NOVOLUME IF NO VOLUME SERIAL NUMBER IS TO BE USED Explanation: OMEGAMON found no keyword for VOL=. System Action: OMEGAMON ignores the control statement and continues the edit and update. User Response: Resubmit with a volume serial number or VOL=NOVOLUME if you do not want OMEGAMON to perform volume serial number checking. COMMAND TABLE IS INVALID. SECURITY UPDATE PROGRAM TERMINATED Explanation: A security update was attempted on an OMEGAMON version that does not support external security. System Action: The job terminates. User Response: Verify that you are using a current level of OMEGAMON. RESET KEYWORD VALUE MUST END WITH A BLANK Explanation: A nonblank character terminated the reset operand. System Action: OMEGAMON suppresses the operation. User Response: Correct the command and retry. UNKNOWN RESET KEYWORD VALUE Explanation: The reset keyword operand is not valid. System Action: OMEGAMON suppresses the operation. User Response: Correct the keyword value and retry. MAJOR COMMAND TABLES WILL BE RESET Explanation: The security level, audit, and external switches will be cleared for all major and immediate commands. These commands will be unprotected unless you specify new settings and rerun the update program. System Action: Processing continues. This is an informational message only. 190 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

191 OB9034 OB9035 OB9036 OB9037 OB9038 OB9039 OB9040 MINOR COMMAND TABLES WILL BE RESET Explanation: The security level, audit, and external switches will be cleared for all minor commands. These commands will be unprotected unless you specify new settings and rerun the update program. System Action: Processing continues. This is an informational message only. INFO-LINE COMMANDS WILL BE RESET Explanation: The security level, audit, and external switches will be cleared for all INFO-line commands. These commands will be unprotected unless you specify new settings and rerun the update program. System Action: Processing continues. This is an informational message only. PASSWORDS AND AUTHLIB WILL BE RESET Explanation: The passwords and the authorized dataset will be cleared. System Action: Processing continues. User Response: Specify new settings and rerun the update program to reset these fields. ONLY SECURITY LEVEL 0 ALLOWED FOR /PWD LEVEL 0 ASSIGNED Explanation: OMEGAMON allows a security level 0 only for the /PWD INFO-line command. System Action: OMEGAMON assigns security level 0. This is an informational message only. INVALID SMF RECORD NUMBER SPECIFIED Explanation: Installer specified an invalid parameter for the SMFNUM control statement. Valid SMF record numbers are 128 through 255. System Action: The security update program ignored the statement. User Response: Correct the SMF record number to a number between 128 and 255 and resubmit. SMFNUM ALREADY SPECIFIED. STATEMENT IGNORED. Explanation: Installer specified the SMFNUM parameter in the security update program more than once. System Action: The security update program ignored the statement. User Response: Submit a new SMFNUM statement. MODULE ALREADY SPECIFIED. STATEMENT IGNORED. Explanation: Installer specified the MODULE parameter in the security update program more than once. System Action: The security update program ignored the statement. User Response: Submit a new MODULE statement. OB0101 OB

192 OB9041 MODULE LENGTH IS INVALID; MUST BE BETWEEN 1 AND 8 CHARACTERS Explanation: The security installation utility detected a name specified for the MODULE control statement that was not 1 8 characters. System Action: The security update program ignored the statement. User Response: Submit a new MODULE statement. OB9042 PASSWORD SPECIFICATION WILL BE RESET Explanation: The installer executed the security update program to reset the indicated password. System Action: The security update program will reset the password. This is an informational message only. OB9043 SMF RECORD NUMBER SPECIFICATION WILL BE RESET Explanation: Installer executed security update program to reset the indicated SMF record number. System Action: The security update program will reset the SMF record number. This is an informational message only. OB9044 EXTERNAL SECURITY MODULE NAME SPECIFICATION WILL BE RESET Explanation: The installer executed the security update program to clear the indicated module name. The external security exit routine will not be accessible unless you specify a new setting and rerun the security update program. System Action: The security update program will clear the name. User Response: If you want to use external security specify a valid module name for the security exit and rerun the security update program. OB9045 ***WARNING*** - UPDATE DENIED BY CONSOLE OPERATOR Explanation: This message appears on the security update report. The console operator replied NO to a request to update the security tables, so the request was denied. System Action: The update is cancelled. User Response: If appropriate, provide information on authorization to the console operator. OB9089 UPDATE OF OMEGAMON SECURITY TABLES HAS BEEN REQUESTED BY jobname Explanation: This message appears on the operator console to advise the operator that a job is attempting to update the security tables. OB9090 REPLY Y TO ALLOW OR N TO DISALLOW UPDATE PROCESSING Explanation: This message appears on the operator console following message OB9089. It prompts the operator to allow or disallow updating. System Action: The update job waits for the operator s reply. User Response: Respond Y or N. 192 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

193 OB9144 OB9145 OB9146 OB9147 OB9148 OB9149 OB9150 OB9151 OBSELR00 CALLED TO READ cccccccc Explanation: This is an informational message returned from running the security update program. The variable cccccccc is the security table. System Action: The security update program completes. OBSELW00 CALLED TO WRITE cccccccc Explanation: This is an informational message returned from running the security update program. The variable cccccccc is the security table. System Action: The security update program continues processing. LOAD MODULE TEXT SUCCESSFULLY READ Explanation: This is an informational message returned from running the security update program. System Action: The security update program continues processing. LOAD MODULE TEXT SUCCESSFULLY UPDATED Explanation: This is an informational message returned from running the security update program. Message OB9158 accompanies this message. System Action: The security update program completes. SYSLIB DCB {OPENED CLOSED} SUCCESSFULLY Explanation: This is an informational message returned from running the security update program. System Action: Security update program continues processing. LIBRARY DSNAME IS: cccccccc Explanation: This is an informational message returned from running the security update program. It provides the library dataset name cccccccc. System Action: Security update program continues processing. SYSLIB DCB CLOSED Explanation: This is an informational message returned from running the security update program. System Action: The security update program completes. SYSLIB DCB FAILED TO OPEN Explanation: OMEGAMON encountered an error opening the dataset specified in the SYSLIB DD statement. System Action: The job terminates. User Response: Verify that the SYSLIB DD statement specifies a valid and correctly spelled dataset. OB0101 OB

194 OB9152 OB9153 OB9154 OB9155 OB9156 OB9157 OB9158 SYNADAF ERROR MESSAGE Explanation: An error occurred during a read/write of a file by the security update program. System Action: The job terminates. BLDL MACRO FAILED WITH RETURN CODE nnnn/nnnn Explanation: OMEGAMON cannot find the command table. The variable nnnn/nnnn is an IBM return code. System Action: The job terminates. User Response: Verify that the job specifies the correct load library. FIND MACRO FAILED WITH RETURN CODE nnnn/nnnn Explanation: OMEGAMON cannot find the command table. The variable nnnn/nnnn is an IBM return code. System Action: The job terminates. User Response: Verify that the job specifies the correct load library. TEXT READ OVERFLOWS DIRECTORY SIZE INDICATION Explanation: An error occurred during the security update program s processing. System Action: The job terminates. UNEXPECTED END-OF-FILE WHILE READING cccccccc Explanation: An error occurred during the security update program s processing. System Action: The job terminates. RDJFCB MACRO FAILED WITH RETURN CODE nnnn Explanation: An error occurred during the security update program s processing. System Action: The job terminates. LOAD MODULE ID: cccccccc Explanation: This message accompanies OB9146. The list that follows contains information on: An internal module name An internal version identifier An internal date and time stamp System Action: User Response: The security update processing completes. None. This is an informational message only. 194 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

195 OB9261 OB9262 OB9263 OB9269 KOBSUPDT BEGUN Explanation: This is an informational message generated at the start of the security update program. System Action: The security update program continues processing. LOAD MODULE ccccccc RETURN CODE IS nnnn Explanation: The variable ccccccc is READ, UPDATE, or REWRITE. This is an informational message returned from running the security update program. System Action: The security update program continues processing. User Response: If return code nnnn is other than 0, contact IBM Software Support. KOBSUPDT LISTING FILE FAILED TO OPEN Explanation: The attributes of the SYSPRINT file are wrong. System Action: The job terminates. User Response: Verify that the file is a SYSOUT dataset, or that the file has the following attributes: RECFM=FBA, LRECL=133, DSORG=PS, and BLKSIZE is a multiple of 133. KOBSUPDT ENDED Explanation: This is an informational message returned from running the security update program. System Action: The security update program completes. OB0101 OB

196 196 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

197 4 OBV101 OC0999 OBV101 OBV102 OBV103 OBV104 OBV105 OBV106 OBV107 VTPRELOG MODULE ENTERED Explanation: This message is issued after the VTM1WK workarea is initialized. System Action: Processing continues. This is an informational message only. USER INIT EXIT BEING CALLED Explanation: This message is issued before the exit is called. System Action: Processing continues. This is an informational message only. USER INIT EXIT NOT BEING CALLED Explanation: The initiation exit is optional. This message indicates that the user did not supply the exit. System Action: Processing continues. This is an informational message only. OPEN ACB BEING ISSUED Explanation: VTM1 must open an ACB that points to an applid. This message is issued before every attempt to open an ACB. System Action: Processing continues. This is an informational message only. OPEN ACB SUCCESSFUL, NOW ISSUE SETLOGON Explanation: This message is issued before the VTAM SETLOGON instruction. System Action: Processing continues. This is an informational message only. SETLOGON SUCCESSFUL, NOW ISSUE REQSESS Explanation: This message is issued before the VTAM REQSESS instruction. System Action: Processing continues. This is an informational message only. REQSESS SUCCESSFUL, NOW ISSUE STIMER Explanation: This message is issued before the MVS STIMER instruction. System Action: Processing continues. This is an informational message only. OBV101 OC

198 OBV108 OBV109 OBV110 OBV111 OBV112 OBV113 OBV114 OBV115 OBV116 STIMER SUCCESSFUL, NOW ISSUE WAIT Explanation: This message is issued before the MVS WAIT instruction. VTM1 will wait for one of two ECBs to be posted. This will either be the STIMER ECB (from STIMER) or SCIP exit ECB (from REQSESS). System Action: Processing continues. This is an informational message only. WAIT POPPED, BRANCH TO VTENVIR Explanation: One of the two ECBs named in OBV108 has been posted. VTM1 branches to module VTENVIR. System Action: Processing continues. This is an informational message only. MODULE VTENVIR ENTERED Explanation: This message is issued upon entry to module VTENVIR. System Action: Processing continues. This is an informational message only. SCIP ECB POSTED Explanation: The VTAM SCIP exit was scheduled due to the receipt of an SC RU. It posted the SCIP ECB. System Action: Processing continues. This is an informational message only. BIND RECEIVED FROM PLU Explanation: The BIND RU was received by the VTAM SCIP exit. A previous REQSESS macro resulted in this BIND. System Action: Processing continues. This is an informational message only. MODULE VTCOMM ENTERED Explanation: This message is issued upon entry to module VTCOMM. System Action: Processing continues. This is an informational message only. UNBIND DETECTED Explanation: The UNBIND RU was received by the VTAM SCIP exit. System Action: Processing terminates. This is an informational message only. CALLING ROUTINE TO CREATE RPL FOR RECEIVE Explanation: The VTAM GENCB macro is being issued to create an RPL which a later RECEIVE macro will use. System Action: Processing continues. This is an informational message only. RECEIVE ISSUED AND COMPLETE Explanation: The VTAM RECEIVE macro has completed. System Action: Processing continues. This is an informational message only. 198 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

199 OBV117 OBV118 OBV119 OBV120 OBV121 OBV122 OBV123 OBV124 OBV125 UNBIND DETECTED Explanation: The UNBIND RU was received by the VTAM SCIP exit. System Action: Processing terminates. This is an informational message only. SENT DEFINITE RESPONSE Explanation: The VTAM SEND macro, used to send a definite response, has completed. The return code from the SEND has not yet been checked. System Action: Processing continues. This is an informational message only. CALLING USER PUT EXIT Explanation: This message is issued just before the user exit is called. System Action: Processing continues. This is an informational message only. CALLING USER GET EXIT Explanation: This message is issued just before the user exit is called. System Action: Processing continues. This is an informational message only. CALLING ROUTINE TO CREATE RPL FOR SEND Explanation: The VTAM GENCB macro is being issued to create a RPL which a later SEND macro will use. System Action: Processing continues. This is an informational message only. CALLING ROUTINE TO ISSUE SEND Explanation: This message is issued before the VTAM SEND instruction is executed. System Action: Processing continues. This is an informational message only. MODULE VTTERM ENTERED Explanation: Issued upon entry to module VTTERM. System Action: Processing continues. This is an informational message only. CALLING USER TERM EXIT Explanation: This message is issued just before the user exit is called. System Action: Processing continues. This is an informational message only. VTAM LOSTTERM EXIT ENTERED FOR VTM1 Explanation: This message is issued upon entry to the VTAM LOSTTERM exit for VTM1. System Action: Processing continues. This is an informational message only. OBV101 OC

200 OBV126 OBV127 OBV128 OBV129 OBV130 OBV131 OBV132 OBV133 OBV134 VTAM TPEND EXIT ENTERED FOR VTM1 Explanation: This message is issued upon entry to the VTAM TPEND exit for VTM1. System Action: Processing continues. This is an informational message only. VTAM SCIP EXIT ENTERED FOR VTM1 Explanation: This message is issued upon entry to the VTAM SCIP exit for VTM1. System Action: Processing continues. This is an informational message only. VTSCIP RECEIVES UNBIND REQUEST Explanation: The VTAM SCIP exit for VTM1 received an UNBIND request. System Action: Processing continues. This is an informational message only. VTSCIP RECEIVES BIND REQUEST Explanation: The VTAM SCIP exit for VTM1 received a BIND request. System Action: Processing continues. This is an informational message only. RECEIVED FIRST SDT REQUEST Explanation: The VTAM SCIP exit for VTM1 received its first Start Data Traffic request. System Action: Processing continues. This is an informational message only. RECEIVED SECOND SDT REQUEST Explanation: The VTAM SCIP exit for VTM1 received its second Start Data Traffic request. System Action: Processing continues. This is an informational message only. RECEIVED CLEAR REQUEST Explanation: The VTAM SCIP exit for VTM1 received a CLEAR request. System Action: Processing continues. This is an informational message only. VTSCIP POSTING ECB Explanation: The VTAM SCIP exit for VTM1 posted its ECB to notify the mainline VTM1 code. System Action: Processing continues. This is an informational message only. MVS STIMER EXIT ENTERED FOR VTM1 Explanation: The MVS STIMER issued previously has popped, and its exit is being driven. System Action: Processing continues. This is an informational message only. 200 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

201 OBV135 OBV136 OBV201 OBV202 OBV203 OBV204 OBV205 OBV206 VTM1 USER cccccccc LOGGING ON TO aaaaaaaa Explanation: This message is issued via WTO after a user logs onto a VTAM application through VTM1. The fields cccccccc and aaaaaaaa are filled in with the user ID and system name of the PLU, respectively. System Action: Processing continues. This is an informational message only. VTLOGON MODULE ENTERED Explanation: The module VTLOGON was entered. System Action: Processing continues. This is an informational message only. ERROR WITH IDENTIFY MACRO USED TO LOCATE MODULE VTPRELOG Explanation: An attempt to locate VTM1 module VTPRELOG failed. System Action: Processing terminates with an error. GETMAIN FAILED FOR ATTACH MACRO WORKAREA Explanation: Storage request for the ATTACH macro s workarea, as defined by the list form of ATTACH, failed. This area is needed to make the attach request reentrant. System Action: Processing terminates with an error. User Response: Increase the region size. ATTACH OF MAIN VTM1 MODULE VTPRELOG FAILED Explanation: The ATTACH macro, used to create the main VTM1 task executing module VTPRELOG, failed. System Action: Processing terminates with an error. DETACH OF MAIN VTM1 MODULE VTPRELOG FAILED Explanation: The detach of the VTM1 module VTPRELOG failed. Note that when this message is issued, regular VTM1 processing was already completed. System Action: Processing terminates with an error. FREEMAIN FAILED FOR ATTACH MACRO WORKAREA Explanation: Storage request for the ATTACH macro s workarea, as defined by the list form of ATTACH, failed. When this message is issued, regular VTM1 processing is already completed. System Action: Processing terminates with an error. GETMAIN FAILED FOR MAIN VTM1 WORKAREA - VTM1WK Explanation: The storage request for the main VTM1 workarea failed. System Action: Processing terminates with an error. User Response: Increase the region size. OBV101 OC

202 OBV207 OBV208 OBV209 OBV210 OBV211 OBV212 OBV213 OBV214 GETMAIN FAILED FOR VTALTER Explanation: The storage request for the VTM1 workarea failed. This workarea holds information describing the VTM1 processing environment. System Action: Processing terminates with an error. User Response: Increase the region size. GETMAIN FAILED FOR VTM1 USER WORKAREA Explanation: The storage request for the VTM1 workarea failed. This workarea is for the VTM1 user. System Action: Processing terminates with an error. User Response: Increase the region size. ERROR SETTING ESTAE Explanation: The MVS ESTAE macro that is used to trap VTM1 processing errors failed. System Action: Processing terminates with an error. ERROR CREATING NIB CB Explanation: The VTAM GENCB macro that is used to create an NIB control block failed. System Action: Processing terminates with an error. ERROR CREATING RPL CB Explanation: The VTAM GENCB macro that is used to create an RPL control block failed. System Action: Processing terminates with an error. ERROR CREATING ACB CB Explanation: The VTAM GENCB macro that is used to create an ACB control block failed. System Action: Processing terminates with an error. ERROR CREATING EXLST CB Explanation: The VTAM GENCB macro that is used to create an EXLST control block failed. System Action: Processing terminates with an error. USER INIT EXIT RETURNS WITH ERROR Explanation: After issuing this message, VTM1 begins termination processing. The message is not passed back to the VTM1 user. System Action: Processing terminates with an error. 202 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

203 OBV215 OBV216 OBV217 OBV218 OBV219 OBV220 OBV221 OBV222 ERROR CREATING RPL CB FOR OPNSEC Explanation: The VTAM GENCB macro that is used to create a RPL control block failed. The RPL was to be used by the VTAM OPNSEC macro in the SCIP exit. System Action: Processing terminates with an error. OPEN ACB FAILED, NONSPECIFIC Explanation: An attempt to open an ACB using one of the applids in the pool failed. This message is not passed back to the user. System Action: Processing continues; VTM1 tries the next applid in the pool. OPEN ACB FAILED, APPLID ALREADY IN USE Explanation: An attempt to open an ACB using one of the applids in the pool failed. This message is not passed back to the user. System Action: Processing continues; VTM1 tries the next applid in the pool. OPEN ACB FAILED, APPLID INACT OR UNKNOWN Explanation: An attempt to open an ACB using one of the applids in the pool failed. This message is not passed back to the user. System Action: Processing continues; VTM1 tries the next applid in the pool. NO LOGON MODE ENTRY AVAILABLE Explanation: The user-supplied table was searched, but no logmode entry was found that matched the VTALTER fields. System Action: Processing terminates with an error. User Response: Check the CALLVT macro parameter VTNAME. Make sure that there is a logon mode table entry specified for the given environment. SESSION CANNOT START - NO VIRTUAL TERMINAL AVAILABLE Explanation: The VTM1 virtual terminal pool was searched, but none of the virtual terminals was available for use. System Action: Processing terminates with an error. User Response: Verify that the VTAM major node definition of the virtual terminal pool, KOBVTPL, is active to VTAM. Also, verify that at least one minor node within the major node has a VTAM status of CONCT. SETLOGON FAILED Explanation: The VTAM SETLOGON macro failed. System Action: Processing terminates with an error. REQSESS FAILED Explanation: The VTAM REQSESS macro failed. System Action: Processing terminates with an error. OBV101 OC

204 OBV223 OBV224 OBV225 OBV226 OBV228 OBV229 OBV230 OBV231 STIMER FAILED Explanation: The MVS STIMER macro failed. System Action: Processing terminates with an error. SESSION REQUEST TIMEOUT Explanation: VTM1 has not received a response to a session request sent to KOBVTAM. The cause of the failure is not known, but the nature of the problem is probably temporary. System Action: VTM1 session request is terminated. User Response: Try starting another session at a later time. If the condition persists, contact IBM Software Support. UNBIND REQUEST RECEIVED Explanation: An unexpected UNBIND request was received. System Action: Processing terminates with an error. User Response: Check the application system that VTM1 was logged onto. Try to logon again. If the error persists, contact IBM Software Support. UNKNOWN ERROR ENCOUNTERED WHILE EXAMINING THE VTM1 ECB LIST Explanation: There is an unclear reason for the transfer of control within VTM1. Neither the STIMER or SCIP ECB was posted. System Action: Processing terminates with an error. GETMAIN FOR GBUFF FAILED Explanation: The storage request for the VTM1 get buffer area failed. System Action: Processing terminates with an error. User Response: Increase the region size. GETMAIN FOR PBUFF FAILED Explanation: The storage request for the VTM1 put buffer area failed. System Action: Processing terminates with an error. User Response: Increase the region size. UNABLE TO DETERMINE THE USERID Explanation: The VTM1 code that examines the ASCB in order to determine user ID encountered an error. System Action: Processing terminates with an error. RECEIVE FAILED, NONSPECIFIC REASON Explanation: The VTAM RECEIVE macro failed. System Action: VTM1 abends with user abend code U231. This message is seen only by the internal VTM1 trace routine. 204 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

205 OBV232 OBV233 OBV234 OBV235 OBV236 OBV237 OBV238 SENDING OF DEFINITE RESPONSE FAILED Explanation: The VTAM SEND macro that is issued to send a definite response failed. System Action: VTM1 abends with user abend code U232. This message is seen only by the internal VTM1 trace routine. USER PUT EXIT RETURNS WITH ERROR Explanation: After issuing this message, VTM1 begins termination processing. The message is not passed back to the VTM1 user. System Action: Processing terminates with an error. USER GET EXIT RETURNS WITH ERROR Explanation: After issuing this message, VTM1 begins termination processing. The message is not passed back to the VTM1 user. System Action: Processing terminates with an error. SEND FAILED, NONSPECIFIC REASON Explanation: The VTAM SEND macro failed. System Action: VTM1 abends with user abend code U235. This message is seen only by the internal VTM1 trace routine. ERROR CREATING RPL CB FOR RECEIVE Explanation: The VTAM GENCB macro that is used to create an RPL control block failed. System Action: VTM1 abends with user abend code U236. This message is seen only by the internal VTM1 trace routine. TESTCB FAILED Explanation: The VTAM TESTCB macro failed. System Action: VTM1 abends with user abend code U237. This message is seen only by the internal VTM1 trace routine. ERROR CREATING RPL CB FOR SEND Explanation: The VTAM GENCB macro that is used to create an RPL control block failed. System Action: VTM1 abends with user abend code U238. This message is seen only by the internal VTM1 trace routine. OBV101 OC

206 OBV239 OBV300 OBV301 OBV302 OBV303 OBV304 OBV305 OPNSEC FAILED Explanation: The VTAM OPNSEC macro that is issued from the SCIP exit failed. This message is seen only by the internal VTM1 trace routine. System Action: Processing terminates as if an UNBIND had been received. VTM1 LOGMODE cccccccc ERROR - FM/TS nnnn NOT SUPPORTED Explanation: VTAM logmode cccccccc specifies FM/TS profile nnnn, which VTM1 does not support. VTM1 requires a logmode with FM/TS profile "0202". System Action: The session terminates. User Response: Correct the KOBVTPL definitions to specify an appropriate VTAM logmode, and retry. OMEGAMON SESSION REQUEST FAILED - OBVTAM APPL NOT SPECIFIED Explanation: A null (blank) applid has been specified. System Action: The session terminates. User Response: Verify that the applid has been properly supplied by all clists, panels, or procedures, and retry. SESSION REQUEST FAILED - OBVTAM APPL cccccccc NOT DEFINED Explanation: VTM1 requested a session with the KOBVTAM application specified. VTAM does not have a network definition for the KOBVTAM APPL. System Action: VTM1 session request terminates. User Response: Activate the proper network definition and start KOBVTAM. If KOBVTAM is a cross-domain resource, verify that the VTM1 host has a cross-domain resource definition active for KOBVTAM. VTM1 APPL cccccccc NOT ACTIVE Explanation: The VTM1 appl cccccccc is not active. System Action: The session terminates. User Response: Make sure that the VTM1 appls have been properly defined and are active. OPEN ERROR cc DETECTED FOR APPL aaaaaaaa Explanation: OPEN failed to complete successfully for APPL aaaaaaaa, due to error condition cc. System Action: The session terminates. TEMPORARY VTAM ERROR. RETRY LATER Explanation: VTAM is temporarily short on storage. System Action: The session terminates. User Response: Retry later. If the problem persists, contact your Network Support group. 206 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

207 OBV306 OBV307 OBV308 OBV309 OBV310 OBV311 OBV312 OBV313 VIRTUAL TERMINAL POOL cccccccc IS NOT DEFINED TO VTAM Explanation: No match was found in VTAM s configuration tables for the VTM1 virtual terminal pool cccccccc. System Action: The session terminates. User Response: Verify that the VTM1 application major node is properly defined in SYS1.VTAMLST, and active. VIRTUAL TERMINAL POOL cccccccc DEFINITION ERROR Explanation: cccccccc is not a valid APPL entry. System Action: The session terminates. User Response: Correct the entry and retry. NO APPL AVAILABLE IN VIRTUAL TERMINAL POOL cccccccc Explanation: All cccccccc virtual terminals are currently in use. System Action: The session terminates. User Response: Retry later. VIRTUAL TERMINAL POOL cccccccc IS NOT ACTIVE TO VTAM Explanation: VTAM cannot access the specified virtual terminal pool. System Action: The session terminates. User Response: Activate the VTM1 application major mode. SESSION REQUEST FAILED - ERROR cccc DETECTED Explanation: REQSESS failed to complete successfully, due to error condition cccc. System Action: The session terminates. SESSION REQUEST FAILED - OBVTAM APPL cccccccc NOT AVAILABLE Explanation: The KOBVTAM appl cccccccc is not active, or is terminating. System Action: The session terminates. User Response: Be sure that the KOBVTAM appl is active, and retry. SESSION REQUEST REJECTED - VTAM REASON CODE xxxx yyyy Explanation: The session request initiated by VTM1 was rejected by VTAM. The reason code is described as follows: xxxx is the VTAM Request Parameter List return code/feedback information, and yyyy is the SNA System Sense information associated with the request. System Action: VTM1 session request terminates. User Response: Refer the VTAM reason code information to your network support group or contact IBM Software Support. SESSION REJECTED - OBVTAM APPL cccccccc AT MAX USERS Explanation: The session request initiated by VTM1 was rejected by KOBVTAM APPL cccccccc because KOBVTAM reached its active session limit. The limit was established with the UMAX parameter when KOBVTAM was started. System Action: VTM1 session request terminates. User Response: Try starting another session at a later time, or increase the value of the KOBVTAM start-up parameter UMAX. OBV101 OC

208 OBV314 OBV315 OBV316 OBV317 OBV318 OBV319 SESSION REJECTED FAILED - LOGMODE cccccccc IS INVALID Explanation: The session request initiated by VTM1 failed because VTAM rejected the logmode name cccccccc as invalid. System Action: VTM1 session request is terminated. User Response: Verify the logmode name definitions in KOBVTPL. If they are correct, it may be necessary to update VTAM s logmode tables. VTM1 SLU(sluname) MATCH(match#) BLOCK SENT Explanation: VTM1 full-duplex communications has sent a block for the specified match on the session for the specified SLU. This message is output only if the TRACE keyword is specified on the LOGON command. System Action: Processing continues. The message is informational. VTM1 SLU(sluname) MATCH(match#) BLOCK RECEIVEDRECEIVE BLOCK QUEUED Explanation: VTM1 full-duplex communications has either received or queued a block for the specified match on the session for the specified SLU. This message is output only if the TRACE keyword is specified on the LOGON command. System Action: Processing continues. The message is informational. SLU(sluname) MATCH(match#) PLU(pluname) LENGTH(block length) SEQ(block seq#) Explanation: VTM1 full-duplex communications has sent or received a block for the specified match on the session for the specified SLU. Block length and sequence number are given. This message accompanies either message OBV315 or OBV316. This message is output only if the TRACE keyword is specified on the LOGON command. System Action: Processing continues. The message is informational. VTM1 FDX RECEIVE PROCESS STARTED FOR luname Explanation: VTM1 full-duplex communications has started receiving from its session partner on the session for the specified SLU. This message is output only if the TRACE keyword is included on the LOGON command. System Action: Processing continues. The message is informational. SESSION ENDED. LU(luname) REASON(text) Explanation: A VTM1 full-duplex communications session has ended for the specified reason. System Action: The session terminates, and VTM1 cleans up associated session resources. 208 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

209 User Response: The following table lists each reason text and describes the response which should be taken: Reason LOGOFF COMMAND ISSUED UNBIND RECEIVED COMMUNICATIONS ERROR INVALID SEQUENCE NUMBER RPL CREATION ERROR RECEIVE QUEUE CLOSED SEND QUEUE CLOSED UNKNOWN ERROR Description and User Response The logoff command was issued to intentionally terminate the session. The session partner has terminated the session. Inspect the job log of the partner component for messages explaining the reason for the session termination. Inspect the message log for message OBV322, which documents the cause of the communications error. The session partner has transmitted an invalid sequence number. Contact IBM Software Support. VTAM was unable to generate an RPL control block. Contact IBM Software Support. The session has terminated. Determine why the session has terminated before expected data block(s) from the session partner were received. Session termination is in progress so no data blocks can be dequeued from the outbound send queue for the session. If the session has terminated prematurely inspect the log for further messages documenting the reason for the session termination. Contact IBM Software Support. The associated return code is unknown. OBV320 OBV321 VTM1 SLU(sluname) MATCH(match#) SEND BLOCK DEQUEUED. Explanation: VTM1 full-duplex communications has dequeued a block from the outbound send queue to send it to the partner PLU for the session with the specified SLU. This message is output only if the TRACE keyword is specified on the LOGON command. System Action: Processing continues. The message is informational. SLU(sluname) MATCH(match#) LENGTH(block length) SEQ(block seq#) Explanation: This message gives detailed information on the block associated with message OBV320, including block length and sequence number. This message is output only if the TRACE keyword is specified on the LOGON command. System Action: Processing continues. The message is informational. OBV101 OC

210 OBV322 OBV323 OC0001 OC0002 OC0003 OC0004 VTAM ERROR, LU(luname) REQ(request) RCFB(rrff) Explanation: VTM1 has encountered an error on a VTAM request. The request name (such as send or receive) and RPL return code and feedback information are returned. System Action: The session is terminated. User Response: Look up the return code and feedback information then correct the problem, given the cause of the communications error. VTAM ERROR, LU(luname) SSENSE(request) Explanation: This message accompanies message OBV322 and documents the system sense for the VTAM request error described in that message. System Action: The session is terminated. User Response: Look up the sense code and correct the problem, given the cause of the communications error. ESAA UNABLE TO ACQUIRE SESSION ACCOUNTING AREA Explanation: The GETMAIN for an OMEGAMON II for CICS control block in CSA (subpool 241) failed. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Increase the amount of CSA available to the system and restart the session. SUPR UNABLE TO OBTAIN WORK AREA Explanation: Communication between CICS and the Common Interface could not be established due to a work area GETMAIN failure. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Increase the region available to the CICS address space. SUPR UNABLE TO ESTABLISH RECOVERY Explanation: The module that sets up communication between CICS and CANSOCnnn received a non-zero return code from the ESTAEX macro. This is usually caused by a lack of LSQA. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Decrease the region available to the CICS address space. SUPR UNABLE TO CONNECT TO CANSOCnn Explanation: An attempt to connect to the OMEGAMON II for CICS entry table failed. System Action: OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Ensure that the cross memory interface task (XMIT) is active as a subtask of the Common Interface. 210 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

211 OC0005 OC0006 OC0007 OC0008 OC0009 OC0010 SUPR XMIT HAS NOT SET SPACE SWITCH PC Explanation: The cross memory interface task (XMIT) running under the Common Interface did not format the program call necessary for setting up communication between CICS and the CANSOCnn address space. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Ensure that the cross memory interface task (XMIT) is active as a subtask of the Common Interface. SUPR UNABLE TO RESERVE LINKAGE INDEX Explanation: An attempt to reserve a non-system linkage index with the LXRES macro failed. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. SUPR UNABLE TO CREATE ENTRY TABLE Explanation: An error occurred during the attempt to build a program cal entry table. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. SUPR UNABLE TO CONNECT ENTRY TABLE Explanation: The ETCON macro generated a non-zero return code when trying to connect a program call in the CICS address space. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. SUPR UNABLE TO DISCONNECT FROM CANSOC nn Explanation: An attempt to disconnect from the OMEGAMON II for CICS entry table failed. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. SUPR OMEGAMON II FOR CICS PC CREATE FAILED Explanation: An abend occurred when OMEGAMON II for CICS attempted to establish a cross memory environment between the Common Interface and CICS. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. OBV101 OC

212 OC0011 OC0012 OC0013 OC0014 XMCR UNABLE TO OBTAIN WORK AREA Explanation: Communication between CICS and the Common Interface could not be established due to a work area GETMAIN failure. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates.components that depend on the data provided by the subtask, such a response time collector and ONDV collector, do not function. User Response: Increase the region available to the CICS address space, or decrease the DSA size. XMCR UNABLE TO ESTABLISH RECOVERY Explanation: The module that sets up communication between CICS and CANSOC nn received a non-zero return code from the ESTAEX macro. This is usually caused by a lack of LSQA. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Decrease the region available to the CICS address space. XMCR CROSS MEMORY INTERFACE TASK INACTIVE Explanation: The module that sets up communication between CICS and CANSOC nn found that the cross memory interface task (XMIT) is not active. System Action: The OMEGAMON II for CICS subtask in the CICS region terminates. Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: This message could occur if there is an inconsistency between the common interface and the monitor. For example, the monitor is using a load library with a different version of OMEGAMON II for CICS than the one used by the common interface. Another reason could be that XMIT (cross memory interface task) is not running as a subtask of the common interface. XMCR COMMUNICATION BUFFER HAS WRAPPED FOR: aaa Explanation: Insufficient space was available in the communication buffer used to send response time collector and ONDV collector data from the CICS to the Common Interface. System Action: The oldest records in the buffer are overlayed and the information they contain is lost. The component that is losing data is denoted by aaa. The display of this message is limited to a maximum of once every five minutes. User Response: Check that the Common Interface is running at a dispatching priority greater than that of CICS to ensure that records are pulled from the buffer in a timely manner. The size of the buffer can be increased, if necessary, using the XMRCDS= parameter of the KOCGLOB macro in the Global module. 212 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

213 OC0015 OC0016 OC0017 OC0018 OC0019 XMCR COMPONENT AUTO START FAILURE Explanation: One or more of the components marked for auto start in the Global module could not be initiated. System Action: The auto start logic is not completed. User Response: Check that the cross memory interface task is active under the Common Interface. Also, examine the console log for any messages that might indicate why the auto starts failed. XMCR UNABLE TO RETRIEVE DATA FROM KOCGLB Explanation: Data from the Global module could not be moved from the CANSOC nn address space to CICS. System Action: The OMEGAMON II for CICS logic that runs in the CICS region will not honor the values set in the Global module. User Response: Check that the cross memory interface task is active under the Common Interface. Also, examine the console log for any messages that might indicate why the data extraction failed. XMCR UNABLE TO CROSS MEMORY POST XMIT Explanation: The cross memory communication subtask running in the CICS region was unable to POST a task running in the Common Interface. System Action: The POST failure means that some desired request is not performed by a task running in the Common Interface. Such requests include auto starts, Global data extraction, and notifying either the response time collector or ONDV collector that there is transaction data to process. User Response: Ensure that XMIT is running as a subtask of the Common Interface address space. XMST CROSS MEMORY SUBTASK ABEND: CODE=aaaaaaaa Explanation: The subtask used to coordinate communication between CICS and the Common Interface has abnormally terminated with the completion code denoted by aaaaaaaa. System Action: Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Inspect the console log for messages that may provide a clue as to why the abend occurred. If problems persist, contact IBM Software Support. XMST ATTACH FAILED: SYSTEM ERROR Explanation: The ATTACH macro used to create the cross memory communication subtask in the CICS region failed. System Action: Components that depend on the data provided by the subtask, such as response time collector and ONDV collector, do not function. User Response: Check for messages on the system console. If problems persist, contact IBM Software Support. OBV101 OC

214 OC0020 OC0021 OC0022 OC0023 XMST UNABLE TO ALLOCATE COMMUNICATION BUFFER Explanation: The GETMAIN macro used to allocate the cross memory communication buffer above the line in the CICS region returned a non-zero return code. System Action: The communication buffer is not allocated. Consequently, components that depend on the data sent via the communication buffer, such as response time collector and ONDV collector, do not function. User Response: Either increase the CICS region size, or decrease the amount of storage required for the communication buffer by changing the number of records the buffer holds using the XMRCDS= operand of the KOCGLOB macro in the Global module. XMST CONNECT TO CANSOCnn aaaaaaaa FAILED Explanation: An attempt to establish communication between CICS and the Common Interface failed. The jobname of the Common Interface is denoted by aaaaaaaa. System Action: Components that depend on the communication link between CICS and the Common Interface, such as the response time collector and ONDV collector, do not function. User Response: Check the console for any messages that may serve to explain why CICS and CANSOC nn are unable to communicate with one another. Ensure that the cross memory interface task (XMIT) is active as a subtask of the common interface job aaaaaaaa., and that PARM=LXRES is coded on the EXEC card of the CANSOCnn PROC. XMST COMMON INTERFACE UNAVAILABLE Explanation: An attempt to establish communication between CICS and the Common Interface failed and the Common Interface JOBNAME was unavailable. System Action: Components that depend on the communication link will not function. User Response: Verify that the Common Interface is active. See User Response for message OC0021. XMCR OMEGAMON-TO-CICS CONNECTION IN PROGRESS, REPLY CANCEL TO SKIP CONNECTION Explanation: During CICS initialization, OMEGAMON has waited more than 30 seconds for a response from the OMEGAMON XMIT address space. If a significant number of CICS systems initialize at the same time, it may take the OMEGAMON XMIT address space more than 30 seconds to respond to some of the initialization requests. This may cause message OC0023 to be issued. You can circumvent the contention by staggering the CICS initialization requests so that fewer initializations occur simultaneously. System Action: OMEGAMON waits for an operator response. User Response: A reply of cancel will allow CICS initialization to continue without the cross-memory connection to OMEGAMON. You can establish this at a later time by issuing an OMEG INIT from a CICS terminal. 214 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

215 OC0024 XMST KOCGLBcc PTF aaaaaaa INCOMPATIBLE WITH XMST PTF bbbbbbb Explanation: During initialization, OMEGAMON II for CICS detected that the global data area module with the suffix cc was assembled with PTF aaaaaaa, whereas the cross memory communication code was using PTF bbbbbbb. System Action: Initialization continues. Results are unpredictable. User Response: Ensure that the global data area module was assembled using the same service level as the OMEGAMON II for CICS code within the CICS region. OC0025 XMST PTF aaaaaaa INCOMPATIBLE WITH XMST PTF bbbbbbb Explanation: During initialization, OMEGAMON II for CICS detected that the service level aaaaaaa of the OMEGAMON II for CICS code in the CICS address space was different from the service level 123 bbbbbbb of the CANSOC nn address space. System Action: Initialization continues. Results are unpredictable. User Response: Ensure that both the CICS address space and the CANSOC nn address space are at the same service level. OC0026 OCXMST CICS, CANSOCnn AND GLOBALS MUST BE AT THE SAME SERVICE LEVEL Explanation: This message follows message OC0024 or message OC0025. System Action: Initialization continues. Results are unpredictable. User Response: See the user response for the preceding OC0024 or OC0025 message. OC0030 XMCR UNABLE TO PROCESS CICS RKC2XM DD STATEMENT Explanation: This is an internal error. System Action: Processing stops. User Response: Call IBM Software Support. OC0031 XMCR WILL USE DEFAULT CICS RKC2XM NUMBER 00 Explanation: The system uses a default DD of RKC2XM00. OC0032 XMCR CICS RKC2XM NUMBER INVALID Explanation: An invalid RKC2XM DD card was found in the CICS JCL. The CICS RKC2XM number must be blank or a two-digit number from 00 through 15. System Action: The system uses the default CICS RKC2XM number, 00. OC0033 XMCR CICS IS USING 'RKC2XMnn' DD NAME Explanation: The OMEG INIT has found an RKC2XMnn DD card defined in the CICS JES JCL deck when it was processing. System Action: The system uses nn as the RKC2XM number. OBV101 OC

216 OC0061 OC0063 OC0066 OC0068 OC0070 OC0071 OC0072 XRFD ERROR ENCOUNTERED DURING ACCESS TO CAVM FILE FUNCTION=aaaaaaaaaaa, REASON=bbbbbbbb, RC=cccccccc Explanation: An error occurred while OMEGAMON II for CICS attempted to read the state management record from the CAVM control file. The function being performed when the error occurred is aaaaaaaaaaa; the reason code, if any, is only used for dynamic allocation. It is a combination of the error reason code and the information reason code. These codes are documented in the IBM System Macros Manual. The return code is dependent on the function encountering the error. System Action: The XRF command does not display information contained in the state management record. User Response: Check the console to determine whether or not the dataset is experiencing I/O errors. If problems persist, contact IBM Software Support. INPUT NOT NUMERIC Explanation: An invalid character was found where a numerical value is expected. User Response: Re-enter the correct command input. INTERNAL ERROR: UCB/DEV POINTERS MISSING Explanation: The exception analysis routine, which looks for devices that are not responding (DNRS and TNRS), encountered an internal error. System Action: DNRS and TNRS displays are invalid. GLOBAL AREA (KOCGLB) NOT ACCESSIBLE Explanation: The GRPS command requires access to the global module but was unable to locate it. System Action: The GRPS command fails. INVALID GROUP SPECIFICATION Explanation: The affected command expects a group identifier but found an invalid value. The value must be in the range 1-maxgrp (maxgrp is the value specified in the KOCGLOB macro). User Response: Correct the group specification and re-enter the command. INVALID OPTION SPECIFIED, RE-ENTER Explanation: The option specified with the command was an invalid keyword. System Action: No output is produced by the command. User Response: Re-enter the valid command options. NULL INPUT Explanation: The affected command is expecting input, but none was provided. User Response: Specify the requested parameters. 216 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

217 OC0073 OC0076 MODIFY TEXT EXCEEDS MAXIMUM ALLOWABLE LENGTH Explanation: The CICM command will only accept a modify command that is 115 characters or less in length. User Response: Reduce the length of the modify text and re-enter the command. CSWP INVALID OPERAND SPECIFIED Explanation: The CSWP command encountered an invalid keyword. User Response: Correct the input, and re-issue the command. OC0083 VALID RANGE FOR THRESH IS 0 99 Explanation: A value for the THRESH operand on the DEX command has been entered that is outside the acceptable range. System Action: The DEX command ignores the new value. User Response: Decide what value in the range 0 99 is required for the bottleneck analysis display threshold, and re-enter it. OC0084 VALID RANGE FOR SHORT IS 0 LONG TERM, OR CLEAR Explanation: An invalid SET value for the bottleneck analysis short interval was entered. System Action: The command displays the current values for the bottleneck analysis subtask. User Response: Correct the value and re-enter. OC0085 VALID RANGE FOR LONG IS SHORT-TERM-999, OR 0, OR CLEAR Explanation: An invalid SET value for the bottleneck analysis long interval was entered. System Action: The command displays the current values for the bottleneck analysis subtask. User Response: Correct the value and re-enter. OC0086 OC0099 CYCLE VALUE MUST BE IN THE RANGE SECONDS Explanation: An invalid SET value for the bottleneck analysis cycle timer was entered. System Action: The command displays the current values for the bottleneck analysis subtask. User Response: Correct the value and re-enter. INVALID VALUE FOR SPECIFIED PARAMETER Explanation: The value provided for a keyword was incorrect. System Action: No output is produced by the command. User Response: Re-enter the valid keyword values. OBV101 OC

218 OC0104 OC0112 OC0113 OC0114 OC0115 DL/I NOT IN SYSTEM Explanation: The DLI or DL1 command was executed and the system was not connected to DL/I. If you are using DBCTL, the region has not attached to DBCTL yet. If you are using local DL/I support, the CICS you are monitoring does not have DLI=YES in the SIT. System Action: The DLI command fails. User Response: Determine if the system you are monitoring should have local DL/I support. Determine if you are connected to DBCTL. If DL/I support does exist, either local or DBCTL, contact IBM Software Support. DL/I REMOTE SUPPORT ONLY Explanation: The DLI or DL1 command was executed and the DL/I support was remote only. Under these circumstances the DLI command cannot provide any information, since DL/I is not installed in the region being monitored. System Action: The DLI command fails. User Response: You may use the TABL PDIR SEL=REM command to determine the CICS SYSID that owns your PSBs. You can then monitor DL/I activity by monitoring that CICS. DB STATISTICS BLOCK NOT PRESENT Explanation: The DLI DBD= command was entered and there were no DB statistics blocks found. This usually means DL/I is not local to the CICS you are monitoring. System Action: The DLI DBD= command fails. User Response: Enter the DL/I command by itself. If the output is for DBCTL then no statistics are kept by CICS. If you receive either message OC0104 or OC0112, then DL/I is not local in this CICS, and no statistics are kept by CICS. If DL/I is local, contact IBM Software Support. DB STATISTICS BLOCK SEARCH ERROR Explanation: An error occurred while trying to find the DB statistics block. System Action: The DLI DBD= command fails. User Response: Determine if any storage violations have occurred in your CICS that might have corrupted you DB statistics blocks. Use the STOR VIOLATION command to determine this. If none have occurred contact IBM Software Support. LOAD FAILED FOR IMS COLLECTOR Explanation: A load was attempted for module KOCM nnxy where nn is the release of IMS you are running (13, 21, 22, or 31), x is a CICS indicator, and y is an MVS indicator. The load failed. Verify that you are running a supported release of IMS. The supported releases are release 1.3, 2.1, 2.2, and 3.1. System Action: The DLI command fails. User Response: Check the system log for messages related to a load failure and determine the release of DLI you are running. Then contact IBM Software Support. 218 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

219 OC0117 OC0118 OC0119 OC0132 OC0133 OC0134 UNKNOWN CALL TYPE PASSED TO DLIC Explanation: An internal error has occurred in the IMS collector. System Action: The DLI command fails. DB STATISTICS BLOCK ENTRY NOT FOUND Explanation: The DLI DBD=cccccccc command was entered and the DB statistics block you requested was not found. System Action: The DLI DBD= command fails. User Response: Enter the DLI DBD=* command. This will list the DB statistics blocks available. The statistics blocks listed are the only statistics blocks available. LOAD FAILED FOR DB2 COLLECTOR Explanation: A load was attempted for module KOCB nn 0 y where nn is the release of DB2 you are running (13, 21, or 22) and y is an MVS indicator. The load failed. Verify that you are running a supported release of DB2. The supported releases are release 1.3, 2.1, and 2.2. System Action: The DB2 command fails. User Response: Check the system log for messages related to a load failure and determine the release of DB2 you are running, then contact IBM Software Support. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: An invalid keyword was specified for the affected command. User Response: Correct the keyword and re-enter. POOL KEYWORD SPECIFIED WITHOUT NUMBER Explanation: The LSR POOL command was entered without specifying a pool number. System Action: The LSR command fails. User Response: If you want a summary display for all LSR pools, or you are not certain which pools are available, enter the LSR command without an argument. If you would like to see details for a specific LSR pool, enter the LSR command in this format: LSR POOL=1. INVALID LSR POOL ID SPECIFIED Explanation: The LSR POOL requested does not exist for your combination of CICS and IMS. System Action: The LSR command fails. User Response: If the available LSR pools are used, or you are not certain which pools are available, enter the LSR command without an argument. If you would like to see details for a specific LSR pool, enter the LSR command in this format: LSR POOL=1. OBV101 OC

220 OC0135 OC0136 OC0137 OC0138 OC0139 OC0142 NO VSAM LSR IN THE SYSTEM Explanation: The LSR command could not find any LSR pools allocated to this CICS. System Action: The LSR command fails. User Response: Verify that you have LSR pools allocated for this CICS and that they are open. If both of the above are true, then contact IBM Software Support. IMS REQUESTED BUT NO IMS/DLI IN THE SYSTEM Explanation: The LSR command could not find any IMS LSR pools allocated to this CICS. When the IMS keyword is specified for the LSR command, only IMS pools are shown. System Action: The LSR command fails. User Response: Verify that you have IMS LSR pools allocated for this CICS and that they are open. If both of the above are true, then contact IBM Software Support. KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: A keyword of the affected command is expecting an argument, but none was provided. User Response: Supply an argument for the keyword. NO CICS LSR POOLS HAVE BEEN OPENED Explanation: The LSR command could not find any CICS LSR pools allocated to this CICS. When the CICS keyword is specified for the LSR command only CICS pools are shown. System Action: The LSR command fails. User Response: Verify that you have CICS LSR pools allocated for this CICS and that they are open. If both of the above are true, then contact IBM Software Support. NO IMS LSR POOLS HAVE BEEN OPENED Explanation: The LSR command could not find any IMS LSR pools allocated to this CICS. When the IMS keyword is specified for the LSR command only IMS pools are shown. System Action: The LSR command fails. User Response: Verify that you have IMS LSR pools allocated for this CICS and that they are open. If both of the above are true, then contact IBM Software Support. NO INDEX COMPONENT LSR SUBPOOL Explanation: The index component for the LSR pool was requested and there was no index subpool for the LSR pool. System Action: The LSR command fails. User Response: Verify that you have an index pool allocated for the LSR pool. If the LSR pool is allocated with an FCT SHRCNTL macro rather than CEDA, the index pool option is not available. If the LSR pool was created using CEDA, and index buffers were specified, then contact IBM Software Support. 220 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

221 OC0143 ARGUMENT SPECIFIED IS TOO LONG Explanation: The argument supplied with the keyword is too long. For example: the VOLSER is greater than six characters; the DDNAME is greater than eight characters; or TRANID is greater than four characters. System Action: The command fails. User Response: Re-enter argument within the valid length limitations. OC0144 INVALID SELECTION OPTION SPECIFIED Explanation: The selection criteria specified are invalid. For example, SELECT=ABCXYZ or SELECT=ACQUIRED on the TABL command when the table specified is not the TCT. System Action: The command fails. User Response: Re-enter a valid (or applicable) criterion. OC0145 ARGUMENT SUPPLIED IS INVALID Explanation: The argument supplied with the keyword is invalid. For example, DISP=BAD on the FILE command, since BAD is not a valid disposition. System Action: The command fails. User Response: Re-enter a valid argument. OC0146 SPECIFY LIBRARY NUMBER INSTEAD OF OFFSET Explanation: The dataset name specified on the FILE command includes a + character directly after the ddname. Library offsets are not supported but relative library numbers are. System Action: The command fails. User Response: Re-enter the desired file name, and specify the relative library number after the file name, separated by a comma. If DFHRPL+3 was originally entered, specify DFHRPL,4 instead. OC0160 TEMPORARY STORAGE COLLECTION ERROR, CODE=nnnn Explanation: An error occurred while the TMPS command was collecting data about temporary storage. System Action: The TMPS command fails. OC0163 TRANSIENT DATA COLLECTION ERROR, CODE=nnnn Explanation: An error occurred while the TRND command was collecting data about transient data. System Action: The TRND command fails. OC0164 DBCTL IS NOT VALID FOR CICS 1.7 AND 2.1 Explanation: The DLI command with operand of DBCTL has been issued while monitoring a CICS 1.7 or a CICS 2.1 region. CICS does not support DBCTL in releases prior to CICS 3.1. System Action: The DLI command fails. OBV101 OC

222 OC0165 XRF IS NOT VALID FOR CICS 1.7 Explanation: The XRF command has been issued while monitoring a CICS 1.7 region. CICS does not support XRF in releases prior to CICS 2.1. System Action: The XRF command fails. OC0166 PROGRAM CHECK ABEND TRACE TABLE NOT FOUND Explanation: The TRAC command was entered with an operand of PCATT and the Program Check/Abend Trace table base address is zero, but neither exists in CICS/ESA. System Action: The command fails. OC0167 REQUEST IS NOT VALID FOR CICS/ESA Explanation: The TRAC command was entered with an operand of TRTAB (CICS Trace Table) or PCATT (Program Check/Abend Trace Table), but neither exists in CICS/ESA. System Action: The command fails. OC0168 CICS TRACE TABLE NOT FOUND Explanation: The TRAC command was entered with an operand of TRTAB, but the CICS internal trace table base address is zero. System Action: The command fails. OC0169 INVALID OPERAND FOR THE DLI COMMAND Explanation: The keyword specified was not valid for the DLI command. System Action: The DLI command fails. User Response: Correct the keyword and re-enter the command. OC0173 IMS RELEASE NOT SUPPORTED Explanation: The release of IMS you are executing is not supported by OMEGAMON II for CICS. System Action: The DLI command fails. OC0175 CICS CONNECTION TO DBCTL IS NOT READY Explanation: The connection to DBCTL has not yet finished, and for that reason the control blocks associated with DBCTL are not yet fully initialized. System Action: The DLI command fails. User Response: Determine if the connection to DBCTL is waiting for DBCTL, or for some other reason. If so correct the problem. Then re-enter the DLI DBCTL command. 222 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

223 OC0176 OC0178 OC0183 OC0184 OC0185 CICS HAS NOT CONNECTED TO DBCTL YET Explanation: This indicates that CICS is not yet connected to DBCTL. Either the DBCTL keyword was entered incorrectly, or CICS is not yet connected to DBCTL. System Action: The DLI command fails. User Response: If you intended to display DBCTL information, use the CDBC transaction to connect to DBCTL. Then re-enter the DLI DBCTL command. OC0177 NO EXIT PROGRAM BLOCKS WERE FOUND Explanation: The EXIT EPB command was entered and no exit program blocks (EPBS) were found. System Action: The EXIT command fails. User Response: Verify that EPBs exist in your system. If there are EPBs, and EXIT is not displayed, then contact IBM Software Support. DB2 RELEASE NOT SUPPORTED Explanation: The release of DB2 you are executing is not supported by OMEGAMON II for CICS. System Action: The DB2 command fails. NO GLOBAL USER EXITS FOUND Explanation: The EXIT command was entered and no global user exits were found. System Action: The EXIT command fails. User Response: Verify that you have global user exits installed in your CICS. If there are global user exits and the EXIT command is not displayed, then contact IBM Software Support. DB2 SUBSYSTEM NOT UP Explanation: The DB2 command has been issued before the DB2 subsystem has been started. System Action: The DB2 command fails. User Response: If required, arrange for the DB2 subsystem to be started and re-issue the command. DB2 RESOURCE CONTROL TABLE NOT PRESENT Explanation: The Resource Control Table (RCT) was not found in CICS. Generally this means that CICS has not yet been connected to DB2 or that CICS has been disconnected from DB2. System Action: The DB2 command fails. User Response: Verify that you have connected CICS to DB2. If you are connected and the DB2 command still produces this error, then contact IBM Software Support. OBV101 OC

224 OC0186 OC0187 OC0188 OC0189 OC0190 OC0196 OC0201 TRANSACTION NOT FOUND IN RCT Explanation: The specified transaction was not found in the RCT. System Action: The DB2 command fails. User Response: Verify that the transaction-id you specified is in the RCT. If it is in the RCT and the DB2 command still produces this error, then contact IBM Software Support. FILE NOT FOUND OR IS NOT OPEN Explanation: The VSAM command was entered with an operand of a file name, but the file specified could not be located internally with CICS s VSAM control blocks. The file may not be VSAM, may not be allocated to CICS, or may not have been opened by CICS. System Action: The command fails. INVALID TABLE ENTRY LENGTH Explanation: A table entry (such as FCT, PCT, or PPT) was found with an entry length of over 1,000 bytes. The length of the entry was determined to be invalid. System Action: The command is terminated. User Response: Determine why entry length was invalid, correct, and then retry the command XRF IS NOT ACTIVE FOR THIS CICS Explanation: XRF=NO was coded in the SIT. System Action: OMEGAMON II for CICS ignores the command. LU GROUP INVALID FOR THIS FUNCTION Explanation: The requested function does not support VTAM Logical Unit (LU) group. System Action: OMEGAMON II for CICS ignores the command. GROUP TYPE INVALID. USE TX, TR, PG, LU Explanation: The RSP command or one of the minor commands (either TIME or CNT) was specified with an invalid group type suffix. System Action: OMEGAMON II for CICS ignores the command. User Response: Correct the group type suffix, specifying either TX (transactions), TR (terminals), PG (programs) or LU (logical units), and re-enter the command COLLECTOR NOT ACTIVE, REQUEST IGNORED Explanation: The bottleneck analysis collector subtask is not active. User Response: Start the collector and re-issue the command. 224 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

225 OC0202 OC0203 OC0204 OC0205 OC0207 OC0208 OC0209 COLLECTOR IS BUSY, TRY AGAIN Explanation: The bottleneck analysis collector is currently analyzing the CICS environment. The display command cannot access the collection data until the collector finishes. User Response: Re-issue the command. COLLECTOR SUSPENDED, VALUES SHOWN NOT CURRENT Explanation: The bottleneck analysis collector is suspended and is not sampling data. Only the values accumulated up to the time of suspend are displayed by the command. System Action: The command continues execution. User Response: Resume the bottleneck analysis collector and re-issue the command. BOTTLENECK ANALYSIS COLLECTOR HAS ABENDED, CODE=ssuuu Explanation: The bottleneck analysis subtask abnormally terminated. The abend code is ssuuu. COLLECTOR ESTAE, SDWA NOT AVAILABLE, CODE=aaaaaaaa Explanation: This message is produced by the DEX DEBUG command. The bottleneck analysis collector subtask has abended, but system recovery did not have enough storage to obtain an SDWA (System Diagnostic Work Area) to save the status at the time of abend. aaaaaaaa indicates the cause of the abend. COLLECTOR DETACHED DUE TO TOO MANY PROGRAM CHECKS Explanation: The bottleneck analysis collector was detached due an excessive number of program checks. COLLECTOR START ERROR, CODE=nnnnnn Explanation: The bottleneck analysis collector failed to START successfully. The code indicates the reason for the error. System Action: The bottleneck analysis collector does not initialize. COLLECTOR NOT ACTIVE, STORAGE SHORTAGE, CODE=nnnnnn Explanation: The bottleneck analysis collector could not obtain storage for the analysis work area. nnnnnn indicates how much storage is needed. System Action: The bottleneck analysis collector terminates. User Response: Increase available virtual storage by the amount indicated, by reducing the number of tasks running in the common interface address space or by increasing the region size. OBV101 OC

226 OC0214 OC0215 OC0217 OC0219 OC0224 OC0225 BOTTLENECK ANALYSIS COLLECTOR HAS ABENDED (LOOP) Explanation: The bottleneck analysis collector s cycle took longer than expected. System Action: The bottleneck analysis collector abnormally terminates. OCTB INSUFFICIENT DATA Explanation: The IPRO PDEX command determined that an insignificant amount of degradation data was collected for meaningful display. IPRO PDEX only honors the display request if 25 or more samples are collected and there are wait reasons (other than RUNNING) that exceed the threshold value set by the TPCT command. User Response: Allow OMEGAMON II for CICS some time for data capture. Use the PDEX command to observe tasks counted thus far. BUCKET SET ADDRESS DOES NOT CORRESPOND TO BUCKET ID Explanation: An internal error was detected in the bottleneck analysis bucket structure. OC0218WAIT REASON ID NOT FOUND BY ZOOM FUNCTION Explanation: An internal error was detected in the bottleneck analysis bucket structure. WAIT REASON ID NOT FOUND IN BUCKET Explanation: The bottleneck analysis buckets were searched but no match was found for the wait reason ID entered with the command. User Response: Re-enter the command with a valid wait reason ID. COLLECTOR ATTACHED, REQUEST IGNORED Explanation: This message is in response to a DEX START command. The subtask is already attached. System Action: The command is ignored. COLLECTOR NOT ATTACHED, REQUEST IGNORED Explanation: This message is in response to a DEX STOP command. The subtask is not attached. System Action: The command is ignored. 226 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

227 OC0226 OC0232 OC0233 OC0234 OC0235 OC0236 OC0237 OC0245 INTERVAL SPECIFICATION MUST BE NUMERIC Explanation: This message is in response to a bottleneck analysis sample time interval set request. The value entered is not numeric. User Response: Correct the input, and re-enter. COLLECTOR ATTACHED Explanation: This message is in response to a DEX START command. The bottleneck analysis collector was successfully attached. System Action: Bottleneck analysis collection is started. COLLECTOR DETACHED Explanation: This message is in response to a DEX STOP command. The subtask was terminated and detached. SHORT TERM BUCKETS WILL BE RESET Explanation: This message is in response to a DEX SET SHORT=CLEAR command. System Action: The bottleneck analysis short term counters are set to zero. LONG TERM BUCKETS WILL BE RESET Explanation: This message is in response to a DEX SET LONG=CLEAR command. System Action: The bottleneck analysis long term counters are set to zero. COLLECTOR NOT ATTACHED Explanation: This is a status message, the collector is not attached. COLLECTOR NOT ACTIVE Explanation: The bottleneck analysis collector was not activated (DEX START command). BOTTLENECK ANALYSIS INTERFACE IS BUSY, TRY AGAIN Explanation: A PDEX command was entered while bottleneck analysis was busy performing its analysis. System Action: The command does not execute. User Response: Re-enter the command. OBV101 OC

228 OC0252 OC0253 OC0260 OC0261 OC0262 OC0263 INVALID BUCKET SET NAME, USE BLST COMMAND FOR LIST Explanation: An invalid ID was entered with the BLST command. User Response: Use the BLST command without operands to list all IDs. BOTTLENECK ANALYSIS INTERFACE BUSY; TRY AGAIN Explanation: The bottleneck analysis subtask is updating its collection buckets, so they are temporarily unavailable to the display components. System Action: The command is ignored. User Response: Re-enter the command. INTR INVALID VALUE SPECIFIED FOR aa. RANGE=b-c Explanation: This message is in response to an INTR SET command. The value specified for the keyword denoted by aa is not in the proper range (between the values indicated by b and c inclusive). System Action: The command is ignored. User Response: Correct the value and re-enter the command. INTR ERROR RETURN FROM SMFRTEST MACRO, CODE=aaaaaaaa Explanation: The SMFRTEST macro, used by the interval record collector to determine whether records can be written to the SMF dataset, returned a non-zero return code. System Action: The interval record collection terminates. User Response: Find the meaning of the return code denoted by aaaaaaa in the IBM SMF manual. Correct the cause of the error and restart the interval record collector. INTR UNABLE TO OBTAIN WORK AREA. LENGTH=aaaaaaaa, SP=bbb Explanation: A GETMAIN request for aaaaaa bytes from subpool bbb could not be satisfied. System Action: The interval record collection terminates. User Response: Increase the region size for the common interface and restart the interval record collector. INTR KOCGLB MODULE DOES NOT CONTAIN KOCINTR MACRO Explanation: The Global module was not assembled with the KOCINTR macro. System Action: The interval record collection terminates. User Response: Reassemble the Global module with the KOCINTR macro. See the OMEGAMON II for CICS Configuration and Customization Guide for instructions on coding the KOCINTR macro. 228 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

229 OC0264 OC0265 OC0266 OC0267 OC0268 OC0269 INTR PROGRAM CHECKS = aa Explanation: This message is displayed by the INTR DEBUG command if one or more program checks are encountered by the interval record collector. The interval record collector continues to process normally. User Response: A small number of recoverable program checks may be considered normal. They may be the result of chains being altered in CICS while the interval record collector is attempting to collect CICS data. If the number of program checks is large, then something could be wrong with the interval record collector s data collection mechanism. Contact IBM Software Support. INTR INVALID CALL MADE TO OCEP Explanation: The interval record collection component has received an invalid request, such as a request to record data before it has been initialized. System Action: The interval record collector terminates. INTR ERROR COLLECTING BOTTLENECK DATA Explanation: The bottleneck data collection within interval recording has too much data to fit into one SMF record. This indicates a problem either in the bottleneck analysis buckets or in the interval record collection of the bottleneck data. System Action: The interval record collector terminates. INTR ERROR IN RECORDING, THERE ARE LOST RECORDS Explanation: Interval recording expects to be driven every minute. In this case the recorder detects that it has been more than one minute since the last collection. System Action: The interval record collector terminates. User Response: Check to see if there is some reason why the collector is not getting driven at the expected time, such as MVS system hang. If no reason can be found, contact IBM Software Support. INTR TOO MANY IDS FOR RTA SMF RECORD, SOME DATA MAY BE LOST Explanation: The interval record collector has detected that there is too much response time data to fit in one SMF record. The interval record collector is able to hold the response times for approximately one thousand transactions, programs, terminals, or LUs in one SMF record. System Action: The interval record collector collects only data for the transactions, programs, terminals, or LUs that it can fit in one SMF record. User Response: Using the response time analysis displays, determine if there really have been intervals of one minute that contain so many different transactions, programs, terminals, or LUs. If not, contact IBM Software Support. INTR ERROR RETURN FROM SMFWTM MACRO, CODE=aaaaaaaa Explanation: The SMFWTM macro, used by the interval record collector to write records to SMF, returned a code in register 15 denoted by aaaaaaaa. OBV101 OC

230 OC0270 OC0271 OC0272 OC0273 OC0274 System Action: The interval record collector terminates. User Response: Locate the meaning of the SMFWTM return code in the IBM SMF manual. Correct the cause of the problem and restart the interval record collector. INTR MONITOR ESTAEX SDWA NOT AVAILABLE, CODE=aaaaaaaa Explanation: This message is produced by the INTR DEBUG command. The bottleneck analysis collector subtask has abended while it is driving interval record collection, but system recovery did not have enough storage to obtain an SDWA (System Diagnostic Work Area) to save the status at the time of abend. aaaaaaaa indicates the cause of the abend. INTR MONITOR HAS NOT ABENDED Explanation: This message is issued in response to an INTR DEBUG command. The collector did not abend, therefore no abend information is available. INTR I/O ANALYSIS FAILED, I/O INFORMATION IS NO LONGER BEING RECORDED Explanation: The interval record collector has failed to load the required RMF module KOCRcc0a, where cc is an RMF indicator and a is an MVS indicator. System Action: The interval record collector no longer collects I/O analysis information. User Response: Check the system operator console for loader messages to see why the load failed (CSVnnnn). If possible, correct the problem and restart the interval record collector. Otherwise, contact IBM Software Support. INTR INTERVAL RECORDING ALREADY ACTIVE Explanation: This message is in response to an INTR START command. The collector is already active. System Action: The command is ignored. INTR INTERVAL RECORDING IS NOT ACTIVE Explanation: This message is in response to an INTR STOP command. The collector was already stopped. System Action: The command is ignored. 230 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

231 OC0275 OC0276 OC0277 OC0278 OC0279 OC0281 INTR INTERVAL RECORDING ACTIVATED Explanation: This message is in response to an INTR START command. The collector was successfully started. INTR INTERVAL RECORDING DE-ACTIVATED Explanation: This message is in response to an INTR STOP command. The collector was successfully stopped. INTR ABEND DIAGNOSTICS ARE UNAVAILABLE Explanation: This message is in response to an INTR DEBUG command. Diagnostic information for the interval record collector has been overwritten by a subsequent bottleneck analysis collector abend. The INTERVAL RECORD COLLECTOR FOR cicsjobn HAS ABENDED Explanation: Interval record collection is abnormally terminated. System Action: The interval record collector is terminated. INTR HAS IDENTIFIED RMF VERSION: nnn Explanation: This message is in response to an INTR START command. INTR has determined the current RMF level to be nnn. INTR LOAD FAILED FOR RMF ANALYSIS MODULE KOCRcc0a, ABEND CODE=nnnnnnnn, REASON CODE=rrrrrrrr Explanation: This message is in response to an INTR START command. INTR has failed to load the required RMF module KOCRcc0a, where cc is an RMF indicator and a is an MVS indicator. Abend code nnnnnnnn and reason code rrrrrrrr make up the MVS Contents Supervisor return code information returned when an MVS LOAD is issued for the module. These values may occur in MVS system console messages issued by the loader (CSVnnnn). System Action: The interval recorder no longer collects I/O analysis information. User Response: If possible, ensure that module KOCRcc0a is available and correct the problem. Then attempt to restart the interval recorder. Otherwise, contact IBM Software Support. OBV101 OC

232 OC0282 INTR RMF ANALYSIS INITIALIZATION FAILED. RETURN CODE=nnnnnnnn Explanation: This message is in response to an INTR START command. INTR has encountered an unrecoverable initialization error identified by return code nnnnnnnn. Possible return codes (RC) are as follows: RC Meaning 20 Level of RMF (or equivalent) is not known. 24 RMF Supervisor Control Table core mark is invalid (for RMF level greater than 4.3.0). 28 RMF Supervisor Control Table coremark is invalid (for RMF level less than or equal to 4.3.0). 30 RMF Supervisor Control Table not resident. 34 Unallocated RMF ASCB. 38 RMF is inactive. OC0283 System Action: The interval recorder no longer collects I/O analysis information. User Response: Ensure that RMF is available and correct any problem it is experiencing. Restart interval recording. If the problem persists contact IBM Software Support. INTR RMF ANALYSIS MODULE, KOCRcc0a, IS IN ERROR. RETURN CODE=nnnnnnnn Explanation: This message is in response to an INTR START command. INTR has encountered an unrecoverable initialization error related to the use of loaded module KOCRcc0a where cc is an RMF indicator and a is an MVS indicator. Possible return codes (RC) are as follows: RC Meaning 8 Module length is zero. 12 Module address is zero. System Action: information. User Response: The interval recorder no longer collects I/O analysis Contact IBM Software Support. 232 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

233 OC0284 INTR RMF ANALYSIS PROCESSING ERROR. RETURN CODE=nnnnnnnn, REASON=rrrrrrrr Explanation: INTR has encountered a processing error while gathering I/O analysis information identified by return code nnnnnnnn and reason code rrrrrrrr. Possible return codes (RC) are as follows: RC Meaning 8 Insufficient storage for the RMF API return buffer. OC RMF API (ERBSMFI) not found. 14 The size calculated for the RMF API return buffer is not large enough. Data collection will continue but data for some devices is lost. 18 Non-zero return code from the RMF API (ERBSMFI). The reason code contains the RMF API return code. See the appropriate IBM RMF documentation (or the equivalent if you are using an alternative to RMF). OC0285 OC0300 OC0301 System Action: This message may indicate a recoverable error if it is not followed by message OC0272. In this case, the message is for information only. If message OC0272 does follow, the interval recorder no longer collects I/O analysis information. User Response: If message OC0272 follows this message, contact IBM Software Support. RMF VERSION CANNOT BE DETERMINED; VERSION nnn PRESUMED Explanation: INTR has been unable to confirm the RMF level in use in your system. A level compatible with the level of MVS in use has been presumed (nnn). User Response: This is only a warning message. The likelihood is that the RMF level that has been presumed is indeed the level of RMF in your system. If you are using software that supports the RMF API in place of RMF itself, this message may be displayed whenever INTR START is issued. Otherwise, if the message persists, bring it to the attention of your IBM Software Support representative. RTA COLLECTOR DEACTIVATE REQUEST ACCEPTED Explanation: This message is in response to an RTA STOP command. It acknowledges the request to deactivate the response time collector. System Action: The response time collector is stopped. RTA COLLECTOR NOT ACTIVE Explanation: This message is in response to an RTA STOP command. The response time collector is not currently active. System Action: The request is ignored, and the response time collector status is displayed. OBV101 OC

234 OC0302 OC0303 OC0304 OC0305 OC0306 OC0307 OC0308 RTA INITIALIZING SO CANNOT ACCEPT STOP COMMANDS Explanation: This message is in response to an RTA STOP command. The response time collector is in the process of initializing. System Action: The request is ignored, and the response time collector status is displayed. User Response: Once the response time collector is initialized, re-enter the RTA STOP command. RTA START REQUEST IGNORED - RTA IS INITIALIZING Explanation: This message is in response to an RTA START command. The response time collector is in the process of initializing. System Action: The request is ignored, and the response time collector status is displayed. RTA MONITOR ACTIVE, REQUEST IGNORED Explanation: This message is in response to an RTA START command. The response time collector is already active. System Action: The request is ignored, and the response time collector status is displayed. RTA COLLECTOR ACTIVATE REQUEST ACCEPTED Explanation: This message is in response to an RTA START command. It acknowledges the request to activate the response time collector. System Action: The response time collector is started. RTA SCALE= VALUE INVALID, MUST BE SECS Explanation: This message indicates that the SCALE= parameter of the response time collector command is invalid. The valid range for the SCALE parameter is User Response: Correct the value, and re-enter the command. RTA NOT ACTIVATED - ALL GROUPS EMPTY Explanation: A request was made to start the response time collector. The request is not completed because all the defined groups are empty. System Action: The request is ignored. User Response: Use the GRPS command to list the currently defined groups and their entries. Modify the current groups and retry the request. ETE NO LUS MEET SELECTION CRITERIA Explanation: The ETE command could find no defined Logical Units that satisfy the selection criteria specified on the command. 234 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

235 OC0309 OC0310 OC0311 OC0312 OC0313 OC0314 ETE NO LUS ARE BEING MONITORED Explanation: No VTAM Logical Unit names have been assigned to an LU group. RTA DATA MODULE MISSING Explanation: A request was made to start the response time collector, or a response time collector command was entered, however the response time collector portion of KOCGLBcc cannot be located. ETE INTERVAL= PARM INVALID, MUST BE MINS Explanation: The valid range for the INTERVAL parameter is minutes inclusive (1 minute to 5 days). User Response: Re-enter the command, specifying a valid value. RTA WINDOW= VALUE INVALID, MUST BE 1 10 MINUTES Explanation: The valid range for the SCALE parameter is User Response: Correct the value, and re-enter the command. ETE SPECIFIED GROUP IS NOT LU TYPE Explanation: The GROUP= operand of the ETE command specified a non-lu type group. ETE can only process Logical Unit groups. User Response: Specify a group that has been defined for LUs. RTA NOT STARTED, OMEGAMON INITIALIZATION WAS NOT DONE FOR THIS CICS REGION Explanation: A request was made to start the response time collector, however the CICS transaction OMEG INIT was not entered. System Action: The request fails. User Response: Issue the OMEG INIT transaction to initialize OMEGAMON II for CICS. You can initialize automatically by including the program KOCOME00 in the PLT. Refer to the OMEGAMON II for CICS Configuration and Customization Guide for more information. OBV101 OC

236 OC0315 OC0316 OC0320 RTA NOT STARTED, XMEM RECEIVE NOT AVAILABLE Explanation: This message occurs when the response time collector is unable to obtain response time information because it cannot locate the OMEGAMON II for CICS cross memory communication buffer. System Action: The response time collector subtask terminates. User Response: Check that KOCOME00 successfully ran under CICS either at PLTPI time or via an OMEG INIT transaction. Also, make sure that the XMRCDS= parameter of the KOCGLOB macro does not specify a value of zero in the Global module. If XMRCDS=0, then the communication buffer will never be allocated. This message may appear if CICS is in the process of termination at the time the response time collector tries to extract data. RTA HAS ISSUED A MISMATCHING XMEM RECEIVE FOR DATA Explanation: The response time collector subtask supplied an area that is too small to accommodate the response time information collected by OMEGAMON II for CICS code running under CICS. System Action: The response time collector subtask abnormally terminates with a U0316 abend. Contact IBM Software Support. LU RESPONSE TIME FACILITY FAILED DURING cc-cc RC=nn Explanation: An error occurred in the response time collector s LU Response Time Facility. The variable cc-cc is replaced by one of the following response time analysis internal call types: INSTALL, ADD, EXTRACT, or REMOVE. The variable nn is a hexadecimal return code (for a complete description, see the End-to-End Response Time Feature(ETE) Reference Manual) and is replaced by one of the following decimal return codes: 00 request was successful 04 not APF authorized 08 handle invalid 10 ZAPLOG does not match 14 request failed 18 RTINSTAL module LOAD failed OC RSP1 not installed System Action: The response time collector does not collect LU response time data for some or all of your defined LUs. 236 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

237 OC0321 OC0322 OC0330 OC0380 OC0390 LU RESPONSE TIME FACILITY FAILED DURING c-c REASON=nnnnnnnn LU=mmmmmmmm Explanation: An error occurred in the response time collector s LU Response Time Facility. The variable c-c is replaced by one of the following RTA internal call types: INSTALL, ADD, EXTRACT, or REMOVE. LU=mmmmmmmm is displayed for ADD request errors, and is replaced by the Logical Unit ID of the device for which the ADD request was issued. The variable nn is a hexadecimal return code (for a complete description, see the End-to-End Response Time Feature(ETE) Reference Manual) and is replaced by a decimal return code. System Action: The response time collector does not collect LU response time data for some or all of your defined LUs. RTA COLLECTOR START ERROR, RC=nn Explanation: This message is in response to an RTA START command. OMEGAMON II for CICS was unable to start the response time collector subtask. System Action: The request is ignored, and the response time collector status is displayed. The response time collector does not start. User Response: Note the return code that accompanies this message and call IBM Software Support. RTA COLLECTOR NOT ACTIVE Explanation: One of the response time collector commands was entered (CRSP, CSLT, RSP or ETE) but the response time collector was not active. User Response: Use the RTA START command to activate the response time collector. RTA - NO WORKING STORAGE AVAILABLE Explanation: There is insufficient virtual storage for the RSP command s work area. System Action: The RSP command terminates. User Response: Increase the region for the common interface. RTA DATA AREA BUSY - RETRY Explanation: A GRPS or RTA command issued by another OMEGAMON II for CICS session is currently modifying the thresholds, SCALE or WINDOW in the response time collector data area. User Response: Re-enter the command. OBV101 OC

238 OC0400 ONDV COLLECTOR HAS ENDED DUE TO AN ERROR, RC=nn Explanation: The ONDV collector abnormally terminated. A return code of 10 may occur if multiple CICS regions are started and OMEGAMON is not given enough cycles to complete the cross memory initialization within 30 seconds. A return code of 20 may indicate one of the following: The ONDV dataset does not exist. The ONDV dataset is not initialized. The ONDV dataset is corrupted. The ONDV dataset must have a secondary extent of 1 cylinder. A mismatch in maintenance has occurred. OC0401 OC0402 A return code of 34 indicates that an error occurred during dynamic allocation. System Action: The ONDV collector abnormally terminates. User Response: If you have a return code of 10, stagger the start-up of the CICS regions or issue the command OMEG SHUT followed by the command OMEG INIT in the CICS region where initialization failed. If you have a return code of 20, make sure that your ONDV dataset has been allocated and initialized properly. If you have recently applied maintenance, make sure OMEG REMOVE/ OMEG INIT have been issued, or recycle all CICSes to activate the new maintenance in all regions. If you receive a return code of 34, look for accompanying OC040x messages containing additional return codes. In these messages, the return and reason codes are the same as those produced by DYNALLOC SVC (SVC99). For a complete description of these return codes, see the IBM documents MVS/XA System Programming Library: System Macros and Facilities Vol I. or MVS/ESA Application Development Guide: Authorized Assembler Language Programs. ONDV WAITING FOR OMEGAMON TO INITIALIZE Explanation: The ONDV collector is waiting for initialization in CICS to complete. System Action: The collector waits for 20 seconds and then terminates. User Response: Start the collector manually with the ONDV START command in an OMEGAMON II for CICS session. If the collector still does not start, see if there are any problems in CICS preventing the OMEG transaction from completing. If OMEG is not present, this indicates a problem with OMEGAMON II for CICS. Perform a system dump and send in the dump and DEBUG screens to IBM Software Support. ONDV ERROR FROM DSPSERV, RC=nn, REASON=00yyyy00 Explanation: The ONDV collector encountered an error from the DSPSERV macro. This is an IBM macro for using data space services. System Action: The collector terminates. User Response: Consult the IBM Application Development Macro Reference manual for the cause of the error. 238 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

239 OC0403 OC0404 OC0405 OC0406 OC0407 ONDV DATA SPACE SIZE EXCEEDS INSTALLATION LINIT, DEFAULT SIZE USED Explanation: The size of the data space for the ONDV collector exceeded the limit defined by your installation as set by the SMF user exit IEFUSI or by the IBM default size. System Action: The collector reduces the size of the data space to the installation default size. User Response: Check that the size of the data space you specified in the KOCONDV macro in KOCGLB does not exceed any limit defined at your installation. ONDV ERROR FROM ALESERV, RC=nn Explanation: The ONDV collector encountered an error from the ALESERV macro. This is an IBM macro for using address space control services. System Action: The collector terminates. User Response: Consult the IBM Application Development Macro Reference manual for a description of the return codes. ONDV UNABLE TO ALLOCATE HISTORICAL DATA FILE, RC=nn ERROR=eeee I=iiii NAME=dataset_name Explanation: The ONDV collector could not allocate the historical file you specified in the KOCONDV macro in KOCGLB. System Action: The collector terminates. User Response: Make sure the dataset you specified exists and is a linear dataset. The return codes in the error message are based on the SVC 99 call. Consult the IBM SPL Application Development Guide for a description of the return codes. ONDV UNABLE TO DEALLOCATE HISTORICAL DATA FILE, RC=nn ERROR=eeee INFO=iiii Explanation: The ONDV collector could not deallocate the historical file as it was terminating. System Action: The collector continues termination, but the dataset may still be allocated to the common interface address space. User Response: The return codes in the error message are based on the SVC 99 call. Consult the IBM SPL Application Development Guide for a description of the return codes. ONDV UNABLE TO MAP HISTORICAL DATA FILE, RC=nn REASON=yyyy Explanation: The ONDV collector encountered an error from the DIV macro while trying to map the linear data set to a data space. The DIV macro is an IBM macro for using the Data-In-Virtual facility of MVS. System Action: The collector terminates. User Response: Consult the IBM Application Development Macro Reference manual for a description of the return codes. OBV101 OC

240 OC0408 OC0409 OC0410 OC0411 OC0412 ONDV HISTORICAL DATA FILE WILL BE CLEARED Explanation: The ONDV collector detected invalid control information while initializing the historical data file. System Action: All data in the historical data file is erased. User Response: Make sure that the collector used the allocated data set. If this occurs again, contact IBM Software Support. ONDV NOT STARTED, OMEGAMON INITIALIZATION WAS NOT DONE FOR THIS CICS REGION Explanation: A request was made to start the ONDV collector, but the CICS transaction OMEG INIT was not entered or the program KOCOME00 was not run in the PLT during CICS initialization. System Action: The request fails. User Response: Issue the OMEG INIT transaction to initialize OMEGAMON II in CICS. You can automatically initialize by including the program KOCOME00 in the PLT. Refer to the OMEGAMON II for CICS Configuration and Customization Guide for more information. ONDV HISTORICAL DATA FILE TOO SMALL Explanation: The size of the historical data file was less than 8K and therefore could not be used. System Action: The ONDV collector terminates. User Response: Make sure that historical data file is at least 8K and that the data file is initialized according to the procedure described in the OMEGAMON II for CICS Configuration and Customization Guide. ONDV COMPONENT IS NOT AVAILABLE UNDER MVS/XA Explanation: The ONDV subtask cannot be used in an MVS/XA environment. System Action: The command is ignored. ONDV GENERIC DATASET NAME TOO LONG Explanation: The name of the VSAM linear dataset used to store task history (which is specified on the KOCONDV macro of the global data area module) contains the asterisk wildcard character. When the ONDV subtask was started, the asterisk was replaced by the job name of the CICS region being monitored. (This allows a global data area module to be shared by several CICS regions even though each region requires its own task history dataset.) After the job name was substituted for the asterisk, the resulting dataset name exceeded the maximum of 44 characters. System Action: The subtask is terminated with a return code of 100, (x'64'). User Response: Correct the filename field on the KOCONDV macro so that, after CICS job name substitution, it specifies the name you assigned to the task history dataset when it was allocated. Then reassemble the global data area module and recycle the common interface address space. 240 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

241 OC0413 OC0414 OC0415 OC0416 REDEFINE THE VSAM DATASET WITH SHAREOPTIONS(3,3) Explanation: While attempting to access the linear VSAM task history dataset, it was found that the dataset was not defined with SHAREOPTIONS(3,3). These SHAREOPTIONS are required to enable the ONDV collector to provide its own serialization of the dataset rather than let VSAM control it. System Action: The collector terminates with a return code of 56 (x'38'). This message will be preceded by messages OC0407 and IEC161I User Response: Use the installation and configuration assistance tool to delete and redefine the historical dataset. When allocated, restart the ONDV subtask from an OMEGAMON II for CICS session or through the console Modify command. ONDV SEVERE LOGIC ERROR IN HISTORICAL DATA FILE INDEX STRUCTURE Explanation: The ONDV collector detected an invalid index pointer within the historical data file. System Action: The collector issues an ABENDU414 and terminates. This message should be followed by message OC0416. User Response: Keep the dump and make a copy of the historical data file, then contact IBM Software Support. If this message is not followed by message OC0416, reinitialize your historical data file prior to starting ONDV. ONDV SEVERE LOGIC ERROR IN HISTORICAL DATA FILE DATA STRUCTURE Explanation: The ONDV collector detected an invalid data pointer within the historical data file. System Action: The collector issues an ABENDU415 and terminates. This message should be followed by message OC0416. User Response: Keep the dump and make a copy of the historical data file, then contact IBM Software Support. If this message is not followed by message OC0416, reinitialize your historical data file prior to starting ONDV. ONDV HISTORICAL DATA FILE HAS BEEN ERASED DUE TO THE ABOVE ERROR Explanation: The ONDV collector has erased the data in the historical file due to the error previously reported. System Action: The collector terminates. The next restart causes the file to be reinitialized. Processing then begins again normally. User Response: From the CANSOCnn console log, determine the reason for the collector failure. OBV101 OC

242 OC0417 OC0418 OC0420 OC0421 OC0422 OC0423 OC0424 INCOMPATIBLE ONDV COLLECTOR/DATASTORE CICSJOBN. ERASE DATASTORE? REPLY 'Y' OR 'N'. Explanation: The ONDV collector has been started for the specified CICS region, but on the KOCONDV macro in the global data area module used by that region, one of the following occurred: STORE=(FILEONLY,LINEAR.*.DATASET) has been specified and the dataset is formatted for the FILEOCMP version of the collector, or STORE=(FILEOCMP,LINEAR.*.DATASET) has been specified and the dataset is formatted for the FILEONLY version of the collector. System Action: Suspends collector initialization pending operator response. User Response: Enter Y to continue initialization and erase current data or N to terminate collector without affecting current datastore contents. ONDV COLLECTOR WAITING FOR CONSOLE RESPONSE Explanation: An attempt has been made to stop or start the collector from an OMEGAMON session while the collector status is REPLY. System Action: The command is ignored. User Response: See accompanying message OC0417 and respond Y or N from the console. INVALID PARAMETER SPECIFIED Explanation: An invalid parameter was specified in the ONDV command. System Action: The command is ignored. User Response: Correct the syntax of the command. COLLECTOR NOT ACTIVE Explanation: The ONDV collector is not running. System Action: No records are displayed. User Response: You must start the collector in order to view records. COLLECTOR STOP REQUEST ACCEPTED Explanation: This is an informational message in response to a STOP request. COLLECTOR ALREADY ACTIVE Explanation: A request was made to start the ONDV collector but the collector is already active. System Action: The command is ignored. COLLECTOR START REQUEST ACCEPTED Explanation: This is an informational message in response to a START request. 242 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

243 OC0425 OC0426 OC0427 OC0428 OC0429 OC0430 COLLECTOR STOP REQUEST REJECTED Explanation: A request was made to start the ONDV collector via an MVS command but that command was rejected by MVS. System Action: The collector is not started. User Response: Check the SYSLOG common interface job for more information. NO STATUS INFORMATION AVAILABLE Explanation: Status information on the ONDV collector is not available because the collector is not active. System Action: The command is ignored. User Response: Make sure the collector is active. INTERNAL ERROR, RC=yy Explanation: The ONDV collector detected an internal error in processing the request. System Action: The request is ignored. INSUFFICIENT LINES FOR THE DISPLAY Explanation: The ONDV command did not have enough lines on the terminal to produce a display. System Action: No display is produced. User Response: When entering the ONDV command, make sure at least six lines are available at the bottom of the screen to account for titles, headings, and so on. ONDV does not write records past the physical end of the screen. NO RECORDS TO DISPLAY Explanation: The ONDV collector is active but there are no records to display. System Action: No display is produced. User Response: Enter CICS transactions and try the command over. If this condition persists, verify the following: Use the CEMT INQ MON transaction in CICS to verify that CICS monitoring is active (for CICS 3.x). Verify that the status of the collector is active using the ONDV STATUS command. Contact IBM Software Support for additional assistance. INVALID RECORD NUMBER TO DISPLAY Explanation: An invalid record number was entered with the ONDV command. System Action: No display is produced. User Response: The record number corresponds to the entry number of the record that appears on the screen. The first record is 1, the second 2, and so on. OBV101 OC

244 OC0431 ERROR IN RETRIEVING RECORDS, RC=nn Explanation: The ONDV collector has encountered an internal error in processing the request. System Action: No display is produced. User Response: Contact IBM Software Support with the return code. OC0432 NO DETAILED STATISTICS ARE AVAILABLE Explanation: A request was made to display detailed file or database statistics for a transaction but no statistics are available. System Action: No display is produced. User Response: Verify that collect is active for the file or database using the COLL command and that a KOCDBCOL macro was used in KOCGLB to define the parameters for the file or database. Also verify that the transaction carried out file or database operations from the task level statistics. OC0434 DETAILED STATISTICS HAVE BEEN DELETED FROM ONDV BUFFER Explanation: A request was made to display detailed file or database statistics for a transaction but the statistics were deleted from the ONDV collector data store. The statistics are saved in a wraparound table. Statistics on a file level are saved separately from statistics on a task level. Therefore, file-level statistics might be overwritten while task-level statistics are still available. System Action: No display is produced. User Response: You can set the size of the buffer area for task- an file-level statistics with the KOCONDV macro in KOCGLB. See the OMEGAMON II for CICS Configuration and Customization Guide for more information. OC0435 TOP OF FILE << Explanation: OMEGAMON II for CICS displays this message on the command line when the first record in the datastore is displayed. When scrolling backwards in OMEGAMON II for CICS, the task history component needs to determine the first record in the datastore to prevent any further scrolling. OC0436 ONDV FOR CICS JOB cicsjobn USING xxxxxxxx Explanation: This is an informational message indicating the name of the ONDV historical dataset in use for this ONDV subtask. OC0437 ONDV UNABLE TO ALLOCATE LINEAR DATASET. IT IS ALREADY IN USE. Explanation: ONDV has detected that the linear dataset is currently in use by another ONDV subtask. System Action: The ONDV collector terminates. User Response: Make sure that multiple ONDV subtasks are not attempting to share the same historical dataset. Refer to the OMEGAMON II for CICS Configuration and Customization Guide for instructions on how to code the KOCONDV macro in the global data area module. 244 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

245 OC0438 OC0490 OC0491 OC0492 OC0493 OC0495 OC0500 ONDV CLOSE ERROR DETECTED ON PREVIOUS EXECUTION AGAINST THIS LINEAR DATASET. Explanation: This is an informational message indicating that the previous ONDV subtask to use this historical dataset did not terminate correctly. No status information was recorded and therefore the data contained within this file will be erased. System Action: This message is followed by OC0408 and initialization continues. TIME VALUE MUST BE <= STALL INTERVAL Explanation: A request was made to change the system region exit TIME to a value greater than the current STALL time interval. System Action: The CMT command fails. User Response: Correct the value and re-enter the CMT command. STALL INTERVAL MUST BE >= TIME VALUE Explanation: A request was made to change the STALL time interval to a value less than the current region exit TIME. System Action: The CMT command fails. User Response: Correct the value and re-enter the CMT command. MAX TASKS MUST BE >= ACTIVE MAX TASKS Explanation: A request was made to set max tasks below the current value for active max tasks. System Action: The CMT command fails. User Response: Correct the value and re-enter the CMT command. MAX TASKS MUST BE > ALL CLASS MAX TASKS Explanation: A request was made to set max tasks below the current value for class max tasks for one of the ten transaction classes. System Action: The CMT command fails. User Response: Correct the value and re-enter the CMT command. INVALID MASTER TERMINAL REQUEST FOR THIS CICS RELAESE Explanation: A CMT keyword was entered that was unrecognized by the command for the current CICS release. System Action: The CMT command fails. User Response: Verify the input keywords and parameters for the current CICS release. INVALID FUNCTION REQUEST Explanation: A CMT keyword was entered that was unrecognized by the command. System Action: The CMT command fails. User Response: Verify the input keywords and parameters. OBV101 OC

246 OC0501 UNABLE TO VALID VALUE IN CICS Explanation: OMEGAMON II for CICS was unable to verify that the correct data would be changed in CICS, so the command was not executed. System Action: The CMT command fails. User Response: Determine if CICS has had a storage violation. If not, contact IBM Software Support. OC0502 TIME VALUE MUST BE GREATER THAN SCANDELAY VALUE Explanation: A request was made to change the TIME to a value less than the current SCANDELAY value. System Action: The CMT command fails. User Response: Correct the value and re-enter the CMT command. OC0503 CMT REQUIRES A KEYWORD PARAMETER Explanation: The CMT command requires a keyword as an argument. System Action: The CMT command fails. User Response: Enter the correct keyword (and optional argument) after the CMT command. OC0504 VALUE TOO LOW Explanation: The value for an argument to a CMT keyword was below the minimum value for that keyword. System Action: The CMT command fails. User Response: Correct the argument value and re-enter the CMT command. OC0505 VALUE TOO HIGH Explanation: The value for an argument to a CMT keyword was above the maximum value for that keyword. System Action: The CMT command fails. User Response: Correct the argument value and re-enter the CMT command. OC0506 CLASS ID MUST BE SPECIFIED Explanation: When changing the class max tasks, as class ID must be specified. System Action: The CMT command fails. User Response: Re-enter the CMT command specifying the class ID for the class that you want to change in the CMXT. OC0507 CLASS ID MUST BE 1 10 Explanation: The only valid class IDs are the values of System Action: The CMT command fails. User Response: Re-enter the CMT command specifying the correct class ID for the class that you want to change in the CMXT. OC0508 ACTIVE MAX TASKS MUST BE <= MAX TASKS Explanation: An attempt was made to set active max tasks below the current value for max tasks. System Action: The CMT command fails. User Response: Re-enter the CMT command specifying a value for active max tasks greater than or equal to max tasks. 246 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

247 OC0509 OC0510 OC0515 OC0520 OC0521 OC0522 CLASS MAX TASKS MUST BE < MAX TASKS Explanation: An attempt was made to set class max tasks above the current value for max tasks. System Action: The CMT command fails. User Response: Re-enter the CMT command specifying a value for class max tasks less than max tasks. SCANDELAY VALUE MUST BE <= TIME VALUE Explanation: An attempt was made to set the SCANDELAY value to a value greater than the time value. The SCANDELAY value must be less than or equal to the TIME value. System Action: The CMT command fails. User Response: Re-enter the CMT command specifying a value for SCANDELAY less than or equal to the TIME value. KILL NOT POSSIBLE, OMEG INIT WAS NOT DONE FOR THIS CICS Explanation: The KILL command was issued, but the OMEGAMON for CICS interface is not active in the CICS region or the interface was activated after the task you are attempting to kill was started. System Action: The KILL command fails. User Response: Ensure that transaction OMEG and program KOCOME00 are defined to CICS and that transaction OMEG has been successfully executed in CICS. PROGRAM CHECK DURING KILL PROCESSING Explanation: The KILL command program checked during processing because of a no longer valid CICS pointer. System Action: The KILL command fails. User Response: Re-enter the command. SELECTED TASK ALREADY MARKED FOR CANCEL Explanation: A task was selected with the KILL command, but the task is already being cancelled. System Action: The KILL command fails. INVALID CONTROL BLOCKS WERE DETECTED IN THE TASK TO BE KILLED Explanation: The task selected with the KILL command did not have a valid TCA or DCA (for CICS/MVS ) or TQE (CICS/ESA). This may indicate the task is already being purged by CICS. System Action: The KILL command fails. OBV101 OC

248 OC0523 OC0524 OC0525 OC0526 OC0527 OC0528 OC0529 NO KILL PERFORMED, THE TASK IS IN A DL/I REQUEST Explanation: The task selected with the KILL command has issued a DL/I request that has not yet finished processing. To avoid data integrity exposures, no KILL is attempted. System Action: The KILL command fails. NO KILL PERFORMED, DFHKCP IS IN CONTROL, TRY AGAIN Explanation: DFHKCP is in control in the CICS address space before a KILL is attempted. To avoid CICS integrity exposure, the KILL command does not complete process. System Action: The KILL command fails. NO KILL PERFORMED, LIFO STACK ERROR IN TASK TO BE KILLED Explanation: When checking the LIFO stack of the task to be killed, an error was found. System Action: The KILL command fails. NO KILL PERFORMED, SELECTED TASK IS KCP Explanation: The task selected with the KILL command represents the CICS Task Control Program (KCP). System Action: The KILL command fails. NO KILL PERFORMED, SELECTED TASK IS TCP Explanation: The task selected with the KILL command represents the CICS Terminal Control Program (TCP). System Action: The KILL command fails. NO KILL PERFORMED, GETMAIN FAILURE Explanation: An SQA getmain issued in behalf of the KILL command was unsuccessful because not enough SQA storage was available in the system. System Action: The KILL command fails. User Response: Increase the amount of SQA available to the system and restart the session. KILL PROCESSING COMPLETE Explanation: The KILL command was successful. System Action: This is an informational message. 248 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

249 OC0530 NO KILL PERFORMED, SYSEVENT FAILURE -CODE: X 'yy' Explanation: A SYSEVENT macro issued in behalf of the KILL command was unsuccessful. CODE: 08 indicates that the DONTSWAP count of the CICS address space has reached its maximum. CODE: 04 indicates that the CICS address space was not the current address space. System Action: The KILL command fails. Caution This caution applies to messages OC0538 through OC0546: The KILL command and the KILL FORCE command attempt to remove a task from your CICS region. There are circumstances, however, in which this is not possible. The integrity of CICS and its associated data cannot be guaranteed when either of these commands is used. They should be used only as a last resort. OC0538 OC0539 OC0540 OC0541 OC0542 KIL1 TASK NO. xxxxx: ABOUT TO ISSUE PURGE REQUEST Explanation: OMEGAMON II for CICS has determined that the selected task exists and is able to request CICS services to KILL the task. System Action: CICS will process the KILL request. User Response: Check the system log for further messages. These messages will indicate the result of KILL processing. KIL1 TASK NO. xxxxx: DEFERRED KILL ISSUED Explanation: OMEGAMON has requested CICS services to KILL the selected task. The task is marked Cancel Inhibited or Nonpurgeable. A deferred KILL request is issued to attempt to KILL the task later in its processing. System Action: An attempt to KILL the task will be made at an appropriate time. User Response: Wait for CICS to process the KILL request. KIL1 TASK NO. xxxxx: TASK IN VSAM I/O Explanation: The selected task is in a file control wait. It is not possible to KILL a task in this state and guarantee the integrity of CICS and its associated data. System Action: The KILL request will not be processed. The task is not purged. KIL1 TASK NO. xxxxx: TASK PURGE FAILED Explanation: OMEGAMON II for CICS issued a deferred KILL request for a task. CICS rejected that request. The selected task will not be processed. User Response: Check the system log for other messages from the KILL process. These messages indicate what caused the request to be rejected. KIL1 TASK NO. xxxxx: TASK NOT FOUND Explanation: The selected task either had finished executing or had been processed by a previous KILL command. This is an informational message only. User Response: Ensure that the correct task was selected for KILL processing. OBV101 OC

250 OC0543 OC0544 OC0545 OC0546 OC0590 OC0592 OC0593 KIL1 TASK NO. xxxxx: TASK ALREADY ABENDING Explanation: The selected task is already marked as abending. The task will not be processed by subsequent KILL commands. This is an informational message only. The abending task should complete abend processing. KIL1 TASK NO. xxxxx: THIS IS A SYSTEM TASK Explanation: The selected task is a CICS System task. Such tasks are not eligible for KILL processing. This is an informational message only. User Response: Ensure that the correct task was selected for KILL processing. KIL1 TASK NO. xxxxx: TASK PURGE REQUESTED Explanation: OMEGAMON II for CICS has requested CICS services to purge the selected task. System Action: CICS will purge the task. The task should be purged by CICS. KIL1 TASK NO. xxxxx: INVALID TASK CONTROL BLOCKS Explanation: During KILL processing, the control block structure of the selected task is verified. An error was detected; therefore, the request cannot be processed. The task cannot be processed by the KILL command. User Response: Investigate the task in question. You should attempt to ensure that CICS has not suffered a storage corruption that has damaged task-related control block structures. Requested task(s) not found Explanation: The task requested with the CMQM command could not be found. System Action: The command terminates normally after issuing this error message. User Response: Make sure that the correct task was selected for the CMQM command. INVALID VALUES SPECIFIED FOR THE DUMP KEYWORD Explanation: The DUMP= keyword was specified with the TASK command, but the values after the equal sign were not valid. System Action: The TASK command fails. User Response: Review the command keywords and re-enter. INVALID VALUES SPECIFIED FOR THE DETAIL KEYWORD Explanation: The DETAIL= keyword was specified with the TASK command, but the values after the equal sign were not valid. System Action: The TASK command fails. User Response: Review the command keywords and re-enter. 250 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

251 OC0595 OC0624 OC0625 OC0700 OC0701 OC0702 OC0703 INVALID KEYWORD FOR THIS CICS RELEASE Explanation: A keyword entered for the TASK command is not appropriate for the CICS release being monitored. System Action: The TASK command fails. User Response: Review the command keywords and re-enter. SSCVT CHAIN IS EMPTY Explanation: OMEGAMON II for CICS was unable to locate an SSCVT chain for scanning. System Action: The command fails. User Response: The SSCVT chain should not be empty; there is a possibility that your MVS has been corrupted. If your system appears to be running properly, contact IBM Software Support. INVALID SSCVT FOUND ON CHAIN Explanation: OMEGAMON II for CICS found an invalid entry in the SSCVT chain during scanning. System Action: The command fails. User Response: The SSCVT chain should not contain invalid entries, there is a possibility that your MVS has been corrupted. If your system appears to be running properly, contact IBM Software Support. OCRO CICS JOBNAME PARAMETER IS MISSING OR INVALID Explanation: The CICS jobname parameter for a monitoring session is invalid or omitted. System Action: The session is not initiated. User Response: Restart the session using a valid CICS jobname parameter. OCRO SEARCH FAILED: aaaaaaaa Explanation: An address space with a jobname of aaaaaaaa cannot be found in the system. System Action: The session is not initiated. User Response: Restart the session using a valid CICS jobname parameter. OCRO VALIDATION ABORTED; TARGET IS SWAPPED OUT: aaaaaaaa Explanation: CICS validation for the target address space with jobname aaaaaaaa cannot be completed because the address space was swapped out for longer than two minutes. System Action: The session is not initiated. User Response: Restart the session when the target address space is swapped in or ensure that the target it nonswappable. OCRO CICS VALIDATION FAILED: aaaaaaaa Explanation: The OMEGAMON II for CICS validation routine could not determine that the target address space is CICS. System Action: The session is not initiated. User Response: Restart the session after ensuring that the target address space is CICS and that the CICS step is currently running. OBV101 OC

252 OC0704 OC0705 OC0706 OC0707 OC0708 OC0709 OC0710 OC0711 OCRO UNSUPPORTED CICS RELEASE RUNNING Explanation: The version of CICS running is not supported by this release of OMEGAMON II for CICS. System Action: The session is not initiated. OCXI CICS HAS TERMINATED: aaaaaaaa Explanation: The target CICS with jobname aaaaaaaa terminated. System Action: The session terminates. OCRO CICS SWAPPED OUT: aaaaaaaa Explanation: The target CICS with jobname aaaaaaaa swapped out at a point in OMEGAMON II for CICS s processing where the session cannot continue. System Action: The session terminates. OCRO MODE PARAMETER IS MISSING OR INVALID Explanation: The mode parameter for a monitoring session is invalid or was omitted. System Action: The session is not initiated. User Response: Restart the session using a valid mode parameter. OCXI CICS aaaaaaaa HAS ABENDED; CODE:Sbbb Ucccc Explanation: The CICS with job name aaaaaaaa abnormally terminated. The system and user codes are denoted by bbb and cccc, respectively. System Action: The session terminates. OCXI INSUFFICIENT STORAGE TO START SESSION Explanation: There is not enough virtual storage available to start a session. System Action: The session is not initiated. User Response: Increase the available region. OCXI INVALID PARAMETER LIST PASSED TO OMEGAMON Explanation: The parameter string passed to OMEGAMON II for CICS is in error. System Action: The session is not initiated. User Response: Verify that such entries as the ROWS/COLS parameters are correctly specified. OCXI OMEGAMON INIT FAIL - CODE: aaaaaaaa Explanation: OMEGAMON II for CICS initialization cannot continue due to an error in the start-up environment. System Action: The session is not initiated. User Response: Check the system console log for any other messages. If problems persist, contact IBM Software Support. 252 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

253 OC0712 OC0713 OC0714 OC0716 OC0718 OC0719 OC0720 OCXI ERROR LOADING PRODUCT MODULE aaaaaaaa Explanation: The product module could not be loaded successfully. System Action: OMEGAMON II for CICS terminates. User Response: Check that the named module is in the product library. If it is not in the product library, contact IBM Software Support. OCXI TARGET CICS STALLED IN INITIALIZATION Explanation: While waiting for CICS initialization, an OMEGAMON II for CICS monitoring session is timed out. System Action: The session is not initiated. User Response: Restart the session after CICS is initialized. OCXI CROSS MEMORY INTERFACE TASK HAS TERMINATED Explanation: An OMEGAMON II for CICS monitoring session detected the termination of the cross memory interface task. System Action: The session terminates. User Response: Restart the session after first restarting the cross memory interface task. OCRO VALIDATION ABORTED; TARGET HAS TERMINATED: aaaaaaaa Explanation: The target address space with jobname aaaaaaaa terminated while OMEGAMON II for CICS was performing CICS validation. System Action: The session is not initiated. OCXI CICS TO BE MONITORED IS AN XRF ALTERNATE Explanation: An attempt was made to start an OMEGAMON II for CICS session against a standby CICS region in an XRF configuration. System Action: OMEGAMON II for CICS terminates the session. User Response: Start a session against the active CICS region. OCRO CANSOCnn AND CICS RKC2XM NUMBERS INCOMPATIBLE Explanation: The RKC2XMnn DD statements in the CANSOCnn and CICS JCL procedures do not have the same numeric suffix (denoted by nn). The suffix for the RKC2XMnn DD statement must be a two-digit number from The default is 00. System Action: The session is not initiated. User Response: Match the RKC2XMnn DD statement in the JCL procedure for CANSOCnn to the one in the JCL for CICS. Restart the session. OMEGAMON II FOR CICS LINKAGE STACK ERROR Explanation: The linkage stack maintained by OMEGAMON II for CICS either ran out of available entries or an attempt was made to pop the stack when the stack was empty. System Action: OMEGAMON II for CICS terminates. OBV101 OC

254 OC0721 OC0723 OC0724 OC0750 OC0752 OC0753 OC0755 OCRO UNABLE TO OBTAIN MVS/XA LINKAGE STACK Explanation: An attempt to allocate the OMEGAMON II for CICS linkage stack in above-the-line private storage has failed. System Action: OMEGAMON II for CICS terminates. User Response: Increase the amount of CSA available to the system and restart the session. OCRO UNABLE TO PROCESS CICS RKC2XM DD STATEMENT Explanation: This is an internal error. System Action: Processing stops. User Response: Call IBM Software Support. OCRO INSUFFICIENT MEMORY TO INITIATE SESSION Explanation: There is not enough private storage below the line for the data areas and control blocks necessary to operate a monitoring session or subtask. System Action: The session is not initiated. User Response: Increase the available region, or use the UMAX parameter to limit the number of users that may log on. PWAI INSUFFICIENT MEMORY FOR OMEGAMON II FOR CICS PRODUCT WORK AREA IN CSA Explanation: The GETMAIN for a monitoring session product work area failed. System Action: The session is not initiated. User Response: Increase the amount of CSA available to the system and restart the session. PWAI INSUFFICIENT MEMORY FOR DYNAMIC LOAD AREA Explanation: Session initialization has failed to allocate a required internal work area due to insufficient storage System Action: The session fails to initialize. User Response: Increase the amount of CSA available to the system and restart the session. PWAI INSUFFICIENT MEMORY FOR OMEGAMON II FOR CICS CROSS MEMORY WORK AREA Explanation: The GETMAIN for an OMEGAMON II for CICS session cross memory work area failed. System Action: The session is not initiated. User Response: Increase the amount of CSA available to the system and restart the session. OCRO OCVRSN VALIDATION FAILURE Explanation: An attempt was made to start a version of OMEGAMON II for CICS that does not recognize either the release of the CICS region or the MVS operating system. System Action: The session is not initiated. User Response: Ensure that the session is being started for an operating system and CICS release that is supported by OMEGAMON II for CICS. If problems persist, contact IBM Software Support. 254 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

255 OC0759 OC0760 OC0761 OC0762 OC0763 OC0764 OCRO LINK TO aaaaaaaa FAILED; CODE=bbbbbbbb Explanation: the load module identified by aaaaaaaa could not be loaded. The ABEND code is represented by bbbbbbbb. System Action: The session is not initiated. User Response: Locate the ABEND code (bbbbbbbb) in the IBM System Codes manual; correct the cause of the failure; and restart the session. OCRO LOAD OF aaaaaaaa FAILED: CODE=bbbbbbbb, REASON=cccccccc Explanation: The load module identified by aaaaaaaa could not be loaded. The abend code is represented by bbbbbbbb, and cccccccc denotes the reason code that is associated with the abend. System Action: The session is not initiated. User Response: Locate the abend code (bbbbbbbb) in the IBM System Codes manual; correct the cause of the load failure; and restart the session. OCRO ESTAEX PC FAILURE Explanation: The OMEGAMON II for CICS session received a non-zero return code from the ESTAEX macro. This is usually caused by a lack of LSQA. System Action: The session is not initiated. User Response: Increase the amount of CSA available to the system and restart the session. If problems persist, contact IBM Software Support. OCPR HOLD COUNT DISPLACEMENT VALIDATION FAILED Explanation: OMEGAMON II for CICS was unable to verify the location of the hold count field in the OUCB. System Action: XMIT terminates because OMEGAMON II for CICS components are unable to verify target address spaces if the CICS region is swappable. OCPR(Vnnn) AND aaaaaaaa(vyyy) INCOMPATIBLE Explanation: OMEGAMON II for CICS found a discrepancy in the versions of modules OCPR (XMIT) and aaaaaaaa. System Action: Further processing is stopped. User Response: Verify that all OMEGAMON II for CICS modules are of the same version and restart the cross memory interface task. OCPR MAINTENANCE LEVEL MISMATCH BETWEEN CICS AND CANSOCnn STEPLIB DATASETS Explanation: OMEGAMON II for CICS found a discrepancy in the lengths of data areas in the Global Data Area in CICS and the equivalent area in the CANSOCnn address space. System Action: Further processing is stopped. User Response: Verify that all OMEGAMON II for CICS libraries in the STEPLIB concatenations of CICS and CANSOCnn are the same version, maintenance level, and order. Verify that the Global Data Area Module (KOCGLBxx) has been assembled at the latest maintenance level. OBV101 OC

256 OC0765 OC0766 OC0767 OC0795 OC0796 OC0799 OCPR EXTRACT AREA LENGTHS DIFFERENT -- CICS (xxxx) and CANSOCnn (yyyy) Explanation: See message OC0764. System Action: See message OC0764. User Response: See message OC0764. Quote the two data area lengths if you call IBM Software Support. OCPR KOCGLBcc PTF aaaaaaa INCOMPATIBLE WITH CANSOCnn PTF bbbbbbb Explanation: During the load of a global data area module, OMEGAMON II for CICS detected that the module with the suffix cc was assembled with PTF aaaaaaa, whereas the CANSOCnn was using PTF bbbbbbb. System Action: Initialization continues. Results are unpredictable. User Response: Ensure that the global data area module was assembled using the same service level as the OMEGAMON II for CICS code within the CICS region. OCPR CANSOCnn AND GLOBALS MUST BE AT THE SAME SERVICE LEVEL Explanation: This message follows message OC0766. System Action: The load of the global data area module continues. Results are unpredictable. User Response: Ensure that the global data area module was assembled using the same service level as the OMEGAMON II for CICS code within the CICS region. OCRO ERROR DURING CASB INITIALIZATION Explanation: An unexpected error occurred while building the CICS Architecture Summary Block (CASB). The CASB is an internal OMEGAMON II for CICS control block that is required for session start-up. System Action: The session is not initiated. OCRO UNABLE TO OBTAIN STORAGE FOR CASB Explanation: The first session or subtask initialized against a particular CICS obtains a CASB work area that is required for monitoring of that CICS region. System Action: The session or subtask fails to initialize. Further sessions or subtasks initialized against the same CICS region are also likely to fail. User Response: Increase the amount of CSA available to the system and restart the session. OCRO APF AUTHORIZATION CHECK FAILED Explanation: An OMEGAMON II for CICS session is not running APF authorized. System Action: The session terminates. User Response: Verify that all OMEGAMON II for CICS modules reside in authorized libraries. The OMEGAMON II for CICS Configuration and Customization Guide contains additional information about APF authorization. 256 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

257 OC0800 OC0801 OC0802 OC0803 OC0804 OC0805 OCPR ENVIRONMENT MISMATCH, SYSTEM MUST BE MVS/ESA OR HIGHER Explanation: An attempt was made to execute at an operating system level prior to MVS/ESA. System Action: The session does not initiate. OCRO ENVIRONMENT MISMATCH, THE MVS LEVEL DOES NOT MATCH THE MVS LEVEL IT IS RUNNING ON Explanation: An attempt was made to execute a monitoring module in an incompatible operating system. System Action: The session does not initiate. User Response: Verify that the correct version of OMEGAMON II for CICS is installed. OCRO OCSS SSCVT NOT FOUND ON CHAIN Explanation: The monitor was unable to locate the SSCVT control block. System Action: The session does not initiate. User Response: This message could occur if XMIT (cross memory interface task) is not running as a subtask of the common interface. If this is not the case, contact IBM Software Support. OCPR SSCVT CHAIN IS EMPTY Explanation: The SSCVT chain was scanned, and was found to be empty. System Action: The session does not initiate and a user abend U0803 occurs with a dump. User Response: If problems persist, contact IBM Software Support. OCPR INVALID SSCVT FOUND ON CHAIN Explanation: While searching through the Subsystem Communication Vector Table chain for the element belonging to the Common Interface, OMEGAMON II for CICS encountered an improperly formatted SSCVT. System Action: OMEGAMON II for CICS abends with a U0804 completion code. User Response: Indicates that main storage was overlaid. If problems persist, contact IBM Software Support. OCRO CROSS MEMORY INTERFACE TASK IS NOT ACTIVE Explanation: An initializing OMEGAMON II for CICS session found that the cross memory interface task (XMIT) is not active. System Action: The session does not initiate. User Response: Ensure that the cross memory interface task is running as a subtask of the Common Interface, then restart the session. OBV101 OC

258 OC0806 OC0807 OC0808 OC0809 OC0810 XMCR OCCIREQ SPECIFIED IN STARTUP JCL BUT RKC2XM NOT ACTIVE. REPLY ABEND, IGNORE OR RETRY. Explanation: The //OCCIREQ DD statement was included in the CICS start-up JCL but no entry could be found in the subsystem communication vector table (SSCVT) for the cross memory interface task (XMIT) with the specified suffix. System Action: CICS initialization is suspended until the operator responds to the console message. User Response: Enter one of the following replies: ABEND IGNORE RETRY The CICS address space is abended with a U0806 The OCCIREQ requirement is overridden and CICS initialization continues. When OMEGAMON II for CICS becomes available, support components in the CICS address space must be initialized manually at a terminal through the "OMEG INIT" transaction. Start the XMIT subtask by issuing the modify command: /F CIjobname,START XMIT Once the interface task is active, reply to the OC0806 message with: The SSCVT chain will be searched again for the subtask. If active, initialization will proceed. If not, the WTOR message will be reissued. ARINIT UNABLE TO GETMAIN STORAGE FOR AR$WORK Explanation: OMEGAMON II for CICS attempted to GETMAIN storage for a required control block. The GETMAIN was unsuccessful. OMEGAMON II for CICS is unable to continue without this storage. System Action: The subtask either an OMEGAMON II for CICS session, KOCRTA, KOCDEX, or ONDC terminates with a U0807 abend code. User Response: Increase the amount of CSA available to the system and restart the session. OCPR XM INTERFACE TASK ALREADY ACTIVE Explanation: A second cross memory interface task was started while another one is still active. System Action: The task terminates. OCPR XM INTERFACE TASK IS ACTIVE Explanation: The cross memory interface task completed initialization and is waiting for work. OCPR XM INTERFACE TASK IS TERMINATING Explanation: The cross memory interface task received a request to terminate. 258 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

259 OC0811 OC0812 OC0813 OC0814 OC0815 OC0816 OC0817 OCPR XM INTERFACE TASK HAS ABENDED Explanation: The cross memory interface task error exit intercepted an abnormal termination. System Action: The cross memory interface task attempts resource cleanup before continuing with termination. User Response: Restart XMIT, and contact IBM Software Support. OCPR XM INTERFACE TASK RESOURCE CLEANUP IS COMPLETE Explanation: The cross memory interface task successfully completed resource cleanup. OCPR ESTAEX MACRO FAILURE Explanation: The cross memory interface task received a non-zero return code from the ESTAEX macro. This is usually caused by a lack of LSQA. System Action: The cross memory interface task terminates. User Response: Decrease the amount of CSA available to the system and restart the session. If problems persist, contact IBM Software Support. ARINIT ALESERV MACRO FAILURE: CODE=rc Explanation: An attempt to add an entry for the monitored CICS region to an access list failed. System Action: Processing continues, but cross-memory code will not be executed optimally. User Response: Review the return code, referring to the MVS Assembler Services Reference Manual. OCPR SUBSYSTEM TABLE BUILD FUNCTION WAS UNABLE TO CREATE ITS TABLES Explanation: An internal error occurred during the attempt to create the OMEGAMON II for CICS SSCVT and related control blocks. System Action: The cross memory interface task terminates. User Response: Ensure that the Common Interface is active in the system and that no other attempt is being made to start the cross memory interface task. Then attempt to start the cross memory interface task again. OCPR ENTRY TABLE CREATE FAILED Explanation: An error occurred during the attempt to build a program call-entry table. System Action: The cross memory interface task (XMIT) terminates with a U0816 abend code. OCPR LINKAGE INDEX RESERVE FAILED Explanation: An attempt to reserve a linkage index failed. System Action: The cross memory interface task (XMIT) terminates with a U0817 abend code. OBV101 OC

260 OC0818 OC0819 OC0820 OC0821 OCRO aaaaaaaa IS NOT A VALID PROGRAM NAME Explanation: An invalid program name was requested in a START command. For valid program names, see the OMEGAMON II for CICS Configuration and Customization Guide. System Action: START processing ends. User Response: Correct the START command and re-enter. WARNING: CONNECT TO OCCI aaaaaaaa FAILED Explanation: An attempt to connect to OMEGAMON II for CICS s entry table failed. The jobname of the common interface is denoted by aaaaaaaa. System Action: Processing continues unless the CICS job has the OCCIREQ DD statement in its JCL stream, indicating that the common interface is required. If the OCCIREQ card is present, OMEGAMON II for CICS gives the user a message to ABEND, IGNORE, or RETRY. User Response: Verify that the cross memory interface task (XMIT) is active as a subtask of the common interface job aaaaaaaa, that PARM=LXRES is coded on the EXEC card of the OCCIPROC, and that you are using compatible product releases. OCPR CANSOCnn RKC2XM NUMBER INVALID Explanation: An invalid RKC2XM DD card was found in the CANSOCnn JCL. The RKC2XM number must be blank or a two-digit number from System Action: The system uses the default RKC2XM number, 00. OCPR UNABLE TO PROCESS CANSOCnn RKC2XM DD STATEMENT Explanation: This is an internal error. System Action: Processing stops. User Response: Call IBM Software Support. OC0822 OCPR WILL USE DEFAULT CANSOCnn RKC2XM NUMBER 00 Explanation: The system uses a default DD of RKC2XM00. OC0823 OCPR CANSOCnn IS USING 'RKC2XMnn' DD NAME Explanation: The OCPR CANSOCnn has found an RKC2XMnn DD card defined in the CANSOCnn JES JCL deck when it was initializing. System Action: The system uses nn as the RKC2XM number. OC0824 OCRO ALESERV MACRO FAILURE: CODE=rc Explanation: An attempt to delete an entry for the monitored CICS region from an access list failed. System Action: Task continues terminating normally. User Response: Review the return code, referring to the MVS Assembler Services Reference Manual. 260 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

261 OC0827 OCRO TASK STARTUP FAILED -- XMIT RESIDES IN A DIFFERENT ADDRESS SPACE Explanation: An attempt was made to start an OMEGAMON II for CICS component in an address space other than the one in which XMIT is running. System Action: OMEGAMON II for CICS abends the task. User Response: Verify that the Common Interface has XMIT running for the CICS region to be monitored. TSO and SPF users must use the VTM1 component, rather than attempting to run OMEGAMON II for CICS within the TSO address space. OC0830 OCRO CAUTION - CICS DISPATCHING PRIORITY GREATER THAN 239 Explanation: The dispatching priority of the target CICS is greater than 239. A missing data situation, in which response time collector and historical task display data are lost, may result if the Common Interface runs at a priority lower than CICS. System Action: Processing continues. User Response: Determine why the CICS dispatching priority has been set so high, and reset it to a lower priority if possible. OC0831 DL/I COLLECTOR NOT STARTED; NO DL/I PROCESSING PRESENT Explanation: OMEGAMON II for CICS has been started up in a CICS region that does not have DL/I present but is using a global module with the DLI collector activated. System Action: The DLI collector will not collect DLI clocks and counters. User Response: Code and assemble a GLOBAL module without DLI collection. Add an KOCGLBxx DD card to the CICS job and the next restart of the CICS region will not put out this message. OC0832 DL/I COLLECTOR NOT STARTED; DFHCMP VALIDATION FAILED Explanation: OMEGAMON II for CICS has detected an error in its validation of the DFHCMP module that is addressed by the CSA address in field CSATRNAC. System Action: The DLI collector stops collecting DLI clocks and counters. User Response: Ensure that KOCOME00 is the first entry in the PLTPI table. OC0833 DL/I COLLECTOR NOT STARTED; OMOCMP NOT FOUND Explanation: The load of the DLI collector load module has failed. System Action: The DLI collector stops collecting DLI clocks and counters. User Response: Check the associated loader messages in the CICS job log (CSVxxxxx) and fix the indicated problem. OC0834 DL/I COLLECTOR DISABLE PROCESSING COMPLETE Explanation: This message is issued by CCDI when the DLI collector is turned off. OBV101 OC

262 OC0835 OC0836 OC0837 OC0838 OC0839 OC0850 OC0851 DL/I COLLECTOR NOT STARTED; CSATRNAC PROCESSING FAILED Explanation: OMEGAMON II for CICS has detected that the CSATRNAC field in the CICS CSA has changed while DLI collection is active. System Action: The DLI collector stops collecting DLI clocks and counters. User Response: Verify that the KOCOME00 is the first entry in the PLTPI table. DL/I COLLECTOR NOT STARTED DUE TO PREVIOUS ERROR TERMINATION Explanation: OMEGAMON II for CICS has detected an error that previously caused termination of DLI collector processing and therefore prevents the restart. System Action: The DLI collector does not start. User Response: Check to see if there were errors the last time that the collector processing terminated; if not, contact IBM Software Support. DL/I COLLECTOR NOT FOUND, DISABLE REQUEST IGNORED Explanation: An attempt has been made to stop the collector when it was not active. OCRO FAILURE TO LINK TO KOCDGS00, BLST BUCKET OVERRIDES HAVE NOT BEEN DONE Explanation: An attempt to link to the KOCDGS00 modules has failed. System Action: The bottleneck analysis buckets are not overridden by the settings coded on the KOCBLST macros in the global assembly. If no KOCBLST macros are coded, this has no effect. User Response: Look on the system log for messages from the MVS loader (CSVxxxx) to discover why the link failed. The bucket settings can be changed online using the BLST command. These settings remain in effect until the common interface is recycled. DL/I COLLECTOR SUCCESSFULLY ENABLED Explanation: OMEGAMON II for CICS has enabled the DLI collection mechanism in CICS. System Action: The DLI collector can now be started in order to collect DLI clocks and counters. OCPR TARGET CICS FOR KOCGLB DELETE NOT FOUND Explanation: The XMIT Global module delete command specified a CICS jobname that was not found in the system. System Action: The modify command is ignored. User Response: Re-enter the modify command using a valid CICS jobname parameter. OCPR COMMAND FORMAT IS INVALID Explanation: An unacceptable modify command was sent to the XMIT subtask. System Action: The modify command is ignored. User Response: Re-enter the modify command after correcting the syntax. 262 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

263 OC0852 OC0910 OC0940 OC0941 OC0942 OC0943 OCPR KOCGLBcc USED BY aaaaaaaa HAS BEEN DELETED Explanation: The request that XMIT subtask delete an KOCGLB module was successfully processed for the CICS job identified by aaaaaaaa. UNABLE TO LOCATE CSECTS IN aaaaaaaa Explanation: The VALV routine has been called to verify that a load module has the correct version for the product that is running but the load module contains no CSECTS. System Action: The calling routine fails and then issues a message indicating the results of the failure. User Response: Check the load module aaaaaaaa to see if it is in error. If you can find no obvious problem, contact IBM Software Support. MVSDRV WORK AREA GETMAIN FAILURE Explanation: Not enough storage was available for the work area used to load an MVS, CICS, IMS, or DB2 version dependent module. System Action: The load, and its invoking facility, fail. User Response: Increase the amount of CSA available to the system and restart the session. MVSDRV MVS VERSION UNKNOWN Explanation: When attempting to load an MVS, CICS, IMS or DB2 version dependent module, MVSDRV was unable to verify the MVS version in the system. System Action: The load fails. User Response: After obtaining a dump of the CVT, contact IBM Software Support. MVSDRV KOCVRS00 FAILURE Explanation: When attempting to load an MVS, CICS, IMS or DB2 version dependent module, the link to module KOCVRS00 failed. System Action: The link fails and the invoking facility terminates. User Response: Verify that the OMEGAMON II for CICS installation process completed successfully and that KOCVRS00 is in the OMEGAMON II for CICS common interface library. MVSDRV NO TABLE ENTRY FOR aaaaaaaa Explanation: MVSDRV was invoked to load an MVS, CICS, IMS or DB2 version dependent module but the module is unknown to MVSDRV. System Action: The load and its invoking facility fail. OBV101 OC

264 OC0944 OC0945 OC0946 OC0960 OC0961 OC0962 OC0963 MVSDRV ERROR LOADING aaaaaaaa Explanation: An error occurred when loading aaaaaaaa, an MVS, CICS, IMS or DB2 version dependent module. System Action: The load fails. User Response: Verify that the OMEGAMON II for CICS installation process completed successfully and that module aaaaaaaa is in the OMEGAMON II for CICS common interface library. MVSDRV INVALID HEADER FORMAT IN aaaaaaaa Explanation: An error has been encountered with verifying load module aaaaaaaa for a correct internal header. System Action: The load of aaaaaaaa. MVSDRV(Vnnn) AND aaaaaaaa(vyyy) INCOMPATIBLE Explanation: The version of module MVSDRV and the module it is attempting to load are incompatible. System Action: The load and its invoking facility fail. User Response: Verify that the OMEGAMON II for CICS installation process completed successfully and that module aaaaaaaa is in the OMEGAMON II for CICS common interface library. OCDB UNABLE TO OBTAIN WORK AREA Explanation: Insufficient storage was available for the internal work area obtained by the OCDB command. User Response: Increase the region size for the OMEGAMON II for CICS common interface address space. OCDB PARAMETER SCAN ERROR Explanation: An internal error occurred while attempting to process the OCDB parameter list. User Response: Check that all operands of OCDB are correct, make any necessary changes and re-enter the command. If problems persist, contact IBM Software Support. OCDB INVALID CONTROL PARAMETER - aaaaaa Explanation: The operand aaaaaa is not recognized by OCDB. User Response: Use a valid control operand in the OCDB command. Obtain a list of available options by entering OCDB without operands. OCDB ERROR LOADING aaaaaaaa Explanation: The module identified by aaaaaaaa could not be brought into virtual storage by OCDB. User Response: Check the console for messages that may explain the cause of the load failure. If problems persist, contact IBM Software Support. 264 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

265 OC0964 OC0965 OC0966 OC0967 OC0970 OC0972 OCDBHD MISSING MODULE NAME Explanation: A request for module header data could not be satisfied because a module name was not supplied. User Response: Provide the name of the module and re-enter the command. OCDBHD UNABLE TO LOCATE aaaaaaaa Explanation: The module aaaaaaaa could not be found on the load list of either CICS or the Common Interface. User Response: Check that the module name is correct. If an error is found, correct the module name and re-enter the command. If the name is correct, use the PEEK command to inspect the load lists of both the CICS and CANSOCnn address spaces. If the module was not loaded into storage, then its header cannot be displayed by OCDB. OCDBHD MODULE aaaaaaaa NOT VALID FOR SEARCH Explanation: Module aaaaaaaa does not conform to the naming convention associated with programs that contain a diagnostic header. The module name must be eight characters long and begin with the letters KOC. User Response: Correct the module name and re-enter the command. OCDBHD MODULE aaaaaaaa DOES NOT HAVE A HEADER Explanation: The specified module, aaaaaaaa, was not link-edited with a diagnostic header. MAXR UNABLE TO LOCATE OCEXEC INTERFACE Explanation: The CPU limiting function has been unable to locate the required OMEGAMON II for CICS control blocks in the CICS region. System Action: The MAXR exception is not available. User Response: Check the messages on the CICS job log when OMEGAMON II for CICS is started in the CICS region. If you can find no obvious problem, contact IBM Software Support. OCPR INTERNAL ERROR, CONTACT IBM SOFTWARE SUPPORT Explanation: An internal logic error has been detected while processing session initialization. System Action: The session fails to initialize. OBV101 OC

266 OC0997 OC0998 OC0999 OCRO LOAD OF GLOBAL MODULE KOCGLB FAILED Explanation: An attempt was made to load the default global module, but that module is not available. System Action: The requested session with OMEGAMON II for CICS is not started. User Response: Make sure that the default global module is in the OMEGAMON load library. OCRO LOAD OF GLOBAL MODULE aaaaaaaa FAILED, DEFAULT KOCGLB UNAVAILABLE Explanation: An attempt was made to load a suffixed global module, but that module is not available. The default (nonsuffixed) module is also unavailable. System Action: The requested session with OMEGAMON II for CICS is not started. User Response: Make sure that the user-suffixed module is in the OMEGAMON load library. You should also ensure that the default module is available. INTERNAL ERROR - CALL IBM SOFTWARE SUPPORT Explanation: OMEGAMON II for CICS detects an internal sequence "that should not occur". System Action: OMEGAMON II for CICS executes an ABEND 1, DUMP for the task. 266 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

267 5 OC1000 OC8903 OC1000 OC1001 OC1002 OC1003 OCOMEG INQUIRE TRANSACTION FAILED WITH cccccccccc Explanation: During OMEGAMON II shutdown processing, a response of cccccccccc was returned in EIBRESP for an INQUIRE TRANSACTION command issued by KOCOME00. System Action: KOCOME00 terminates but OMEGAMON II service tasks remain active. User Response: If INQUIRE TRANSACTION failed with NOTAUTH, make sure the user who initiated the OMEGAMON II or the CICS shutdown process is also authorized to issue an INQUIRE TRANSACTION command against the transaction being entered. OMEG DEFINED WITH TRANSACTION CLASS - PROCESSING STOPPED Explanation: Transaction OMEG is defined with TCLASS=nn, where nn is 1 through 10. It should be defined with TCLASS=NO. System Action: OMEGAMON for CICS does not supply the response time collector, ONDV collector and interval record collector with data. The service task is not started. User Response: Define transaction OMEG with TCLASS=NO. KOCOME00 PHASE 2 PLT PROCESSING IGNORED Explanation: Program KOCOME00 could not execute because it was not entered in the PLT in the correct position for phase 2 processing. System Action: KOCOME00 does not execute. User Response: Make sure that the entry for the KOCOME00 program appears in the PLT after DFHDELIM. See the OMEGAMON II for CICS Configuration and Customers Guide for more information regarding changes to the CICS PLT. LOAD FAILED FOR MODULE aaaaaaaa Explanation: OMEGAMON II could not load a required program from STEPLIB. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Make sure the dataset containing all the modules from the distribution tape is present in STEPLIB. OC1000 OC

268 OC1004 LINK FAILED FOR MODULE aaaaaaaa Explanation: OMEGAMON II could not find a required program from STEPLIB. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Make sure the dataset containing all the modules from the distribution tape is present in STEPLIB. OC1005 NEW VERSION OF KOCOME00 NEEDED TO SUPPORT RELEASE Explanation: OMEGAMON II found a back level version of a module. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Make sure the dataset containing all the modules from the distribution tape is present in STEPLIB. Delete any modules from prior releases of OMEGAMON II. OC1006 COMMAND PROCESSING TABLE IS MISSING Explanation: This is an internal error with OMEGAMON II. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. OC1007 DEBUG CHAIN ANCHOR IS 0 Explanation: This is an internal error with OMEGAMON II. System Action: The DEBUG command is ignored. OC1008 cccccccc IS AN INVALID FUNCTION REQUEST Explanation: The option specified with OMEG is incorrect. System Action: The OMEG transaction is ignored. User Response: Make sure the option on the OMEG transaction is valid. OC1009 CANNOT FIND MODULE LIST TO LOAD FROM STEPLIB Explanation: This is an internal error with OMEGAMON II. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. OC1010 KOCOME00 INCORRECTLY DEFINED AS RELOAD=YES Explanation: The program KOCOME00 was defined as RELOAD=YES when it must be RELOAD=NO. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Use CEDA to change the definition for KOCOME00 and retry. 268 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

269 OC1011 OC1012 OC1013 OC1014 OC1015 OC1016 OC1017 CICS LOAD FAILED FOR KOCOME00 Explanation: The program KOCOME00 could not be loaded from the RPL library. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Make sure the program KOCOME00 is present in an RPL library. AUTHORIZATION FAILED WHEN LOADING KOCOME00 Explanation: CICS prevented OMEGAMON II from loading KOCOME00. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Make sure OMEG and KOCOME00 are defined without security as described in the OMEGAMON II for CICS Configuration and Customization Guide. COMMON AREA VERSION cccccccc DETECTED Explanation: OMEGAMON II found a back level version of a module. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. User Response: Make sure the dataset containing all the modules from the distribution tape is present in STEPLIB. Delete any modules from prior releases of OMEGAMON II. BYPASS IS SET, KOCOME00 PROCESSING TERMINATING Explanation: This is an internal error. System Action: OMEGAMON II does not supply the response time collector, ONDV collector, or interval record collector with data. COMMAND PROCESSING NOT AVAILABLE, INIT NOT COMPLETE Explanation: An OMEG INIT was not done. System Action: The command is ignored. User Response: Perform an OMEG INIT and re-enter the command. (The text varies.) Explanation: This is an informational message in response to a debug request. System Action: Processing continues. LINK FAILED FOR MODULE cccccccc DURING COMMAND PROCESSING Explanation: This is an internal error. System Action: Processing continues. OC1000 OC

270 OC1018 OC1019 OC1020 OC1021 OC1022 OC1023 OC1024 OC1025 OC1026 INITIALIZATION HAS ALREADY COMPLETED, INIT IGNORED Explanation: OMEG INIT was entered, but initialization was already performed. System Action: The command is ignored. OMEGAMON II for CICS INITIALIZATION COMPLETE Explanation: The OMEGAMON II for CICS initialization is complete. OMEGAMON II for CICS TERMINATION IS COMPLETE Explanation: The OMEGAMON II for CICS termination is complete. MVS nnn AND CICS yyy: UNSUPPORTED ENVIRONMENT Explanation: The versions of MVS and CICS running are not supported by this release of OMEGAMON II. System Action: OMEGAMON II fails to initiate. User Response: See the OMEGAMON II for CICS Configuration and Customization Guide. OMEGAMON II for CICS SUCCESSFULLY DE-INSTALLED Explanation: OMEGAMON II for CICS has been deinstalled from the CICS region. RKANMOD IS IN USE FOR PROGRAM LOADING Explanation: OMEGAMON II for CICS will load its modules from the RKANMOD dataset. OMEGAMON II for CICS TERMINATION IN PROGRESS Explanation: OMEGAMON II for CICS termination is in progress. OMEGAMON II for CICS RESTART IN PROGRESS Explanation: OMEGAMON II for CICS restart is in progress. OMEGAMON II for CICS INITIALIZATION IN PROGRESS Explanation: OMEGAMON II for CICS initialization is in progress. System Action: None 270 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

271 OC1027 OC1028 OC1029 OC1030 OC1031 OC1032 ALTERNATIVE TRANSACTION ID tttt WILL BE USED Explanation: During PLTPI processing, a transaction ID of tttt, rather than the default of OMEG, was found. System Action: Processing continues. OMEGAMON II will run under the alternative transaction ID. INQUIRE TRAN RESP nnnnnnnn, OMEG DEFAULT USED Explanation: During PLTPI processing, a response of nnnnnnnn was returned in EIBRESP for an INQUIRE TRANSACTION command issued by KOCOME00. System Action: KOCOME00 will use the default transaction ID of OMEG. If transaction OMEG is not defined, OMEGAMON II processing within CICS will not start. PCT ENTRY NOT FOUND FOR MODULE KOCOME00 Explanation: During PLTPI processing, no transaction ID that specified module KOCOME00 was found. System Action: OMEGAMON does not supply the response time collector, the ONDV collector, or interval record collector with data. User Response: Define the transaction that initiates the OMEGAMON-to-CICS interface (that is, OMEG or an alternative ID). OMEG REMOVE HAS BEEN DONE, NEWCOPY KOCOME00 AND RETRY Explanation: For CICS/MVS users only, this message indicates that OMEGAMON II for CICS was previously deinstalled and that to permit reinstallation the program KOCOME00 must be refreshed. System Action: The command is rejected. User Response: Issue the 'CEMT SET PROG(KOCOME00) NEW' command and retry the original command. DE-INSTALL HALTED BECAUSE CROSS-MEMORY CONNECTION NOT ESTABLISHED Explanation: OMEGAMON II for CICS de-install processing stopped. Command 'OMEG REMOVE' was rejected because the OMEGAMON cross-memory connection was not established before the command was issued. System Action: The command is rejected. User Response: The OMEGAMON cross-memory interface task should be active and connected to the common interface. Make sure the OMEGAMON II for CICS address space is active and OMEGAMON has been fully initialized in the CICS region before you issue the 'OMEG REMOVE' command. DE-INSTALL HAS ALREADY BEEN PERFORMED; NOTHING TO REMOVE Explanation: OMEGAMON II for CICS de-install processing has completed on prior execution of command 'OMEG REMOVE.' However, this command was issued again, but there is nothing to de-install or remove. System Action: The command is rejected. OC1000 OC

272 OC1033 OC1034 OC1099 OC1100 OC1101 DE-INSTALL HALTED BECAUSE OMEGAMON INITIALIZATION NOT COMPLETED Explanation: OMEGAMON II for CICS de-install processing or command 'OMEG REMOVE' cannot continue because either OMEGAMON has not been fully initialized in the CICS address space or the common interface is not active. System Action: The command is rejected. User Response: The OMEGAMON II for CICS address space must be active and OMEGAMON must be fully initialized in the CICS region before de-install processing can be initiated. EXEN MODULE KOCOME00 WILL RUN IN (THREADSAFE QUASIREENTRANT) MODE Explanation: The KOCOME00 module will run in threadsafe or quasireentrant mode. If KOCOME00 is defined to CICS with CONCURRENCY(THREADSAFE), the module will execute in threadsafe mode; otherwise, the module will execute in quasireentrant mode. EXEN refers to the OMEGAMON CICS EXit ENabling code. User Response: This is an informational message that only applies to CICS/TS 2.2 with Version 520 of OMEGAMON II for CICS. DEBUG LIST COMPLETE. SEE CONSOLE LOG FOR OUTPUT Explanation: The output in response to an OMEG DEBUG command is complete. QRYC COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: OMEGAMON II could not load a program it required for monitoring CICS transactions. System Action: Support for umbrella services, MAXR processing and file and database statistics is disabled. User Response: Enter the CICS transaction OMEG DEBUG and send in a copy of the CICS SYSLOG to IBM Software Support. EVENT MONITORING POINT NOT DEFINED IN THE MCT Explanation: An event monitoring point (EMP) was defined to OMEGAMON II in the KOCEPOPT macro in KOCGLB, but the EMP was not defined in the CICS Monitor Control Table. System Action: OMEGAMON II does not write umbrella, DL/I or DB2 data to CMF. User Response: Make sure the MCT contains the EMP definitions. See the OMEGAMON II for CICS Configuration and Customization Guide for more details. 272 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

273 OC1102 OC1130 OC1131 OC1132 OC1133 EXEC CICS MONITOR POINT FAILED Explanation: An error occurred as OMEGAMON II tried to write data to CMF. System Action: OMEGAMON II does not write umbrella, DL/I or DB2 data to CMF. User Response: In addition to the usual documentation, send an assembled listing of the MCT and KOCGLB to IBM Software Support. DICTIONARY ENTRY FOR RTYPE IN THE MCT IS MISSING Explanation: OMEGAMON II could not find the field RTYPE in the CICS monitoring record. System Action: OMEGAMON II does not write umbrella, DL/I or DB2 data to CMF. In addition, the response time collector and ONDV collector contain only one record per transaction regardless of the number of conversations. User Response: Modify your MCT to include field 112 (RTYPE). See the CICS Resource Definition (MACRO) for more information. DICTIONARY ENTRY FOR BASIC USER DATA IN THE MCT IS MISSING Explanation: OMEGAMON II could not find the entry in the CICS monitoring control table for the user event monitoring point that matches the one specified in the KOCEPOPT macro in KOCGLB. System Action: OMEGAMON II does not write umbrella data to CMF. User Response: Make sure you have an event monitoring point defined in the MCT and that the entry name and field name for this point match the name in the KOCEPOPT macro. If this problem persists, send an assembled listing of your KOCGLB and a CICS system dump to IBM Software Support. DICTIONARY ENTRY FOR DL/I USER DATA IN THE MCT IS MISSING Explanation: OMEGAMON II could not find the entry in the CICS monitoring control table for the user event monitoring point that matches the one specified in the KOCEPOPT macro in KOCGLB. System Action: OMEGAMON II does not write DL/I data to CMF. User Response: Make sure you have an event monitoring point defined in the MCT and that the entry name and field name for this point match the name in the KOCEPOPT macro. If this problem persists, send an assembled listing of your KOCGLB and a CICS system dump to IBM Software Support. DICTIONARY ENTRY FOR DB2 USER DATA IN THE MCT IS MISSING Explanation: OMEGAMON II could not find the entry in the CICS monitoring control table for the user event monitoring point that matches the one specified in the KOCEPOPT macro in KOCGLB. System Action: OMEGAMON II does not write DB2 data to CMF. User Response: Make sure you have an event monitoring point defined in the MCT and that the entry name and field name for this point match the name in the KOCEPOPT macro. If this problem persists, send an assembled listing of your KOCGLB and a CICS system dump to IBM Software Support. OC1000 OC

274 OC1134 OC1135 OC1136 OC1137 OC1140 OC1141 WORK AREA FOR TRUE IS MISSING Explanation: OMEGAMON II could not locate the work area for its task related user exit program. System Action: OMEGAMON II does not write umbrella data, DL/I data, or DB2 data to CMF. AUTHORIZATION FAILED FOR SMF WRITE, LOGGING STOPPED Explanation: OMEGAMON II attempted to write an SMF record containing transaction related data for a CICS V 1.7 or 2.1 system, but was not authorized for the SMF request. System Action: OMEGAMON II does not log any transaction related monitoring data to SMF. DICTIONARY ENTRY FOR WLM USER DATA IN THE MCT IS MISSING Explanation: OMEGAMON II for CICS could not find the entry for the user event monitoring point CANWLMSC in the CICS monitoring control table. (MVS 5.1/CICS 4.1 and above only) This message only applies if you are using the Candle Command Center for CICS and want to collect this data. Otherwise, you can ignore this message. System Action: OMEGAMON II for CICS does not write WLM data to CMF. User Response: If you want to collect this data, make sure you have an event monitoring point defined in the MCT and that the entry name and field name for this point are CANWLMSC. DUPLICATE DATA FOR CANDLE BASIC SEGMENT WILL BE COLLECTED Explanation: Both the OMEGBSC EMP and one or more individual fields that make up the segment have been used. System Action: OMEGAMON II for CICS writes duplicate data to CMF. User Response: Choose either the OMEGBSC or selective method of collecting the data, not both. OCEXEN INSUFFICIENT WORK AREA FOR EXIT ENABLEMENT Explanation: OMEGAMON II could not enable CICS global exits due to an insufficient work area. System Action: No data is collected for the response time collector or ONDV collector. OCEXEN TRUE COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: OMEGAMON II could not load a program it required for monitoring CICS transactions. System Action: No data is collected for the response time collector or ONDV collector. 274 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

275 OC1142 OC1143 OC1144 OC1145 OC1146 OC1147 OCEXEN GLUE COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: OMEGAMON II could not load a program it required for monitoring CICS transactions. System Action: No data is collected for the response time collector or ONDV collector. OCEXEN NOT AUTHORIZED FOR cccccccccccccccc Explanation: OMEGAMON II could not enable a program it required for monitoring CICS transactions. System Action: No data is collected for the response time collector or ONDV collector User Response: Make sure the transaction OMEG is defined with no resource security (RESSEC(NO)) or command security (CMDSEC=NO). Also make sure the group DFHEXEC is installed. You should also check the CICS system log for messages from the External Security Manager, which will give additional information. If this condition persists change the resource security number for the program KOCOME00 to PUBLIC (RESSECNUM(PUBLIC)). OCEXEN PROCESS cccccccccccccccc ERROR nnnn Explanation: OMEGAMON II encountered an error issuing an EXEC CICS command. System Action: No data is collected for the response time collector or ONDV collector. User Response: Send the message to IBM Software Support. OCEXEN PGMIDERR DURING ccccccccccc Explanation: OMEGAMON II encountered an error issuing an EXEC CICS command. System Action: No data is collected for the response time collector or ONDV collector. OCEXEN QRYC COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: OMEGAMON II could not load a program it required for monitoring CICS transactions. System Action: No data is collected for the response time collector or ONDV collector. OCEXEN CICS MONITORING IS BEING TURNED ON Explanation: OMEGAMON II has detected that CICS monitoring is off. OMEGAMON II is turning CICS monitoring on since it is required for the response time collector and ONDV collector (for CICS 3.x). System Action: CICS monitoring is activated. OC1000 OC

276 OC1148 OC1149 OC1150 OC1151 OC1152 OC1153 OC1154 OC1155 OCEXEN PERFORMANCE CLASS IS BEING TURNED ON Explanation: OMEGAMON II has detected that the performance class of CICS monitoring is off. OMEGAMON II is turning it on since it is required for the response time collector and ONDV collector. System Action: CICS monitoring for the performance class is activated. OCEXEN EXIT INITIALIZATION COMPLETED Explanation: OMEGAMON II enabled CICS exits for data collection. OCEXEN EXIT RESTART COMPLETED Explanation: OMEGAMON II re-enabled CICS exits for data collection. INSUFFICIENT STORAGE FOR THE SMF BUFFER Explanation: OMEGAMON II was not able to acquire a buffer of approximately 32K from CICS OSCOR below 16M. System Action: OMEGAMON II does not log any transaction related monitoring data to SMF. User Response: Increase OSCOR in your CICS region so that at least 32K of contiguous storage is available. UNABLE TO LOCATE OCA RESOURCE MANAGER Explanation: OMEGAMON II could not find the umbrella services exit module. System Action: OMEGAMON II for CICS initialization continues in CICS. Transactions that use umbrella services will fail with a return code of 8. OCA RESOURCE MANAGER ERROR Explanation: OMEGAMON II for CICS could not initialize the umbrella services exit module. System Action: OMEGAMON II for CICS initialization continues in CICS. Transactions that use umbrella services will fail with a return code of 8. EXEN GLUE RESTART COMPLETED Explanation: This is an informational message indicating that the OMEGAMON II global user exits have been re-enabled. EXEN GLUE SHUTDOWN COMPLETED Explanation: This is an informational message indicating that the OMEGAMON II global user exits have been disabled. 276 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

277 OC1156 OC1160 OC1161 OC1162 OC1163 OC1164 OC1165 INVALID RLIM DATA FOUND, RLIM NOT ACTIVATED Explanation: During OMEGAMON initialization under CICS, it was detected that there was no valid resource limiting data present. System Action: The RLIM and RLMU commands will not function. User Response: The most likely cause of this error is that the global data area module is out of step with the runtime code. Reassemble the global data area module and retry. If the problem persists, contact IBM Software Support. OCSETI INSUFFICIENT WORK AREA FOR OCEXEC PROCESSING Explanation: OMEGAMON II could not process its internal monitoring of CICS OCEXEC level calls due to an insufficient work area. System Action: Support for database statistics and MAXR is disabled. OCSETI OCEXEC COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: OMEGAMON II could not load a program it required for monitoring CICS OCEXEC level calls. System Action: Support for database statistics and MAXR is disabled. OCSETI VALIDATION FAILED FOR OCEXEC ENVIRONMENT Explanation: OMEGAMON II detected that internal addresses in CICS were changed, which prevents OMEGAMON II from monitoring CICS OCEXEC level calls. System Action: Support for database statistics and MAXR is disabled. OCSETI OCEXEC MODULE IS NOT IN LOW PRIVATE Explanation: OMEGAMON II detected an error in loading a program required for monitoring CICS OCEXEC level calls. System Action: Support for database statistics and MAXR is disabled. OCSETI OCEXEC INTERFACE IS NOW INSTALLED IN CICS Explanation: OMEGAMON II installed its support for monitoring CICS OCEXEC level calls. OCSETI OCEXEC INTERFACE HAS BEEN DISABLED Explanation: OMEGAMON II removed its support for monitoring CICS OCEXEC level OC1000 OC

278 OC1166 OC1167 OC1168 OC1169 OC1170 OC1171 OCSETI OCEXEC INTERFACE HAS BEEN RESTARTED Explanation: OMEGAMON II restarted its support for monitoring CICS OCEXEC level calls. EXEC VALIDATION NOTED ALTERED CICS ENTRY Explanation: OMEGAMON II initialization processing validates certain pointers in CICS. The validation expects certain conditions but allows for some variations. This message indicates such a variation was found at the CICS Command Level entry points. This condition may occur in conjunction with some other vendor product. System Action: Processing continues. OCSETI EXEC MODULE IS NOT IN LOW PRIVATE Explanation: An error has been encountered in the loading of a module required for monitoring EXEC level calls, it must reside in low private storage. System Action: Support for database statistics and MAXR is disabled. EXEC VALIDATION NOTED UPDATED CICS POINTERS Explanation: OMEGAMON II initialization processing validates certain pointers in CICS. The validation expects certain conditions but allows for some variations. This message indicates such a variation had been found at the CICS Command Level CSA anchor point. This condition may occur in conjunction with some other vendor product. System Action: Processing continues. STARTING OMEGAMON II FOR CICS OCEXEC PROCESSING Explanation: Identifies the part of the OMEGAMON II initialization in process. System Action: Processing continues. USER MODIFIED PRN ENTRY Explanation: The OMEGAMON II EXEC interface was unable to determine the proper entry point for CICS PRN calls. The user has applied a special zap to force the installation at this point. This condition happens only in conjunction with another product installed in CICS. System Action: Processing continues. 278 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

279 OC1172 OC1173 OC1174 OC1175 OC1176 OC1180 OC1182 USER MODIFIED PCN ENTRY Explanation: The OMEGAMON II EXEC interface was unable to determine the proper entry point for CICS PCN calls. The user has applied a special zap to force the installation at this point. This condition happens only in conjunction with another product installed in CICS. System Action: Processing continues. OCSETI KOCDIN COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: An internal error has occurred. System Action: OMEGAMON II for CICS will not initialize. OCSETI KOCDBP COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: An internal error has occurred. System Action: OMEGAMON II for CICS will not initialize. OCSETI KOCDBT COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: An internal error has occurred. System Action: OMEGAMON II for CICS will not initialize. OCSETI KOCOCM COULD NOT BE LOCATED OR WAS NOT LOADED Explanation: An internal error has occurred. System Action: OMEGAMON II for CICS will not initialize. OCDBIN cccccccc IS AN UNSUPPORTED PRODUCT Explanation: File level monitoring was specified for a product in KOCGLB that is not supported by OMEGAMON II. System Action: OMEGAMON II continues processing other products. User Response: The invalid product name is specified in the KOCDBCOL macro in KOCGLB. Correct the macro, reassemble KOCGLB and restart CICS in order to prevent occurrence of this message. OCDBIN INVALID GLOBAL EXTRACT AREA, FILE LEVEL MONITORING DISABLED Explanation: OMEGAMON II detected an internal error in attempting to activate file level monitoring. System Action: OMEGAMON II does not monitor file usage. OC1000 OC

280 OC1183 OC1184 OC1190 OC1191 OC1192 OMEGAMON II FOR CICS COLLECTION IS NOT ACTIVE Explanation: The data collection component of OMEGAMON II that runs in CICS is not active. System Action: A display of file level collectors is not produced. User Response: Make sure the data component of OMEGAMON II is active by entering OMEG INIT as a CICS transaction or placing the program KOCOME00 in the PLT. See the OMEGAMON II for CICS Configuration and Customization Guide for more information. If this problem persists, contact IBM Software Support. NO STORAGE AVAILABLE, FILE LEVEL MONITORING DISABLED Explanation: OMEGAMON II for CICS was unable to acquire a 64K buffer in the extended private region of CICS for collecting file clock and counter statistics. System Action: OMEGAMON II for CICS does not collect file clock and counter statistics for CICS tasks. User Response: Make sure 64K of storage is available in the extended private region of CICS. UNABLE TO OBTAIN WORK AREA FOR SYSTEM RECORDS. LENGTH=nnnnnn Explanation: OMEGAMON II was not able to acquire a work area from OSCOR to send system initialization or system termination records to SMF. The number of bytes requested is given in the message. System Action: OMEGAMON II does not write system initialization or system termination records to SMF. User Response: Increase the amount of OSCOR in your region and restart the session. INVALID TCB ADDRESS, SYSTEM RECORDS NOT WRITTEN TO SMF Explanation: OMEGAMON II attempted to determine the TCB under which it was running in order to write to SMF. System Action: OMEGAMON II does not write system initialization or system termination records to SMF. AUTHORIZATION FAILED, NO SYSTEM RECORDS WRITTEN Explanation: OMEGAMON II attempted to acquire authorization to write a system record to SMF. System Action: OMEGAMON II does not write system initialization or system termination records to SMF. 280 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

281 OC1193 OC1200 OC1201 OC1201 OC1202 OC1203 OC1204 OCSYSI INVALID GLOBAL EXTRACT AREA. SYSTEM RECORD NOT WRITTEN. Explanation: OMEGAMON II has detected an internal error when attempting to write a system record to SMF. System Action: OMEGAMON II does not write system initialization or system termination records to SMF. ddname DD MISSING Explanation: No ddname DD statement was found during execution of job KOCSMFDI. System Action: Processing stops. User Response: Correct the ddname DD statement and rerun job KOCSMFDI. MCT PARAMETER IS INVALID AND IS IGNORED Explanation: An input card contained an MCT parameter, which is invalid for pre-esa CICS, during execution of job KOCSMFDI. System Action: Processing continues and the next input card is read. PRECEDING INPUT IS INVALID, PROCESSING STOPPED Explanation: An input card was blank or contained no equal sign during execution of job KOCSMFDI. System Action: Processing stops. User Response: Correct the input card and rerun job KOCSMFDI. PRECEDING INPUT HAS AN INVALID FIELD NAME, PROCESSING STOPPED Explanation: An input card contained an invalid field name during execution of job KOCSMFDI. System Action: Processing stops. User Response: Correct the input card and rerun job KOCSMFDI. Valid field names are: APPLID, SYSID, DATE, TIME, and SMFID. INVALID VALUE FOR TIME, PROCESSING STOPPED Explanation: An input card contained an invalid value in the TIME field during execution of job KOCSMFDI. System Action: Processing stops. User Response: Correct the input card using a valid time (HHMMSS) and rerun job KOCSMFDI. INVALID VALUE FOR DATE, PROCESSING STOPPED Explanation: An input card contained an invalid value in the DATE field during execution of job KOCSMFDI. System Action: Processing stops. User Response: Correct the input card using a valid date (YYDDD.) and rerun job KOCSMFDI. OC1000 OC

282 OC1208 OC1209 OC1210 OC1211 OC1212 OC1213 OC1214 THE SERVICE TASK IS ALREADY RUNNING, CANNOT START A NEW ONE Explanation: OMEG SRVINIT was issued but the service task is already running. User Response: If you wish to reinitialize the service task, issue OMEG SRVSHUT first, then OMEG SRVINIT. THE SERVICE TASK WAS SUCCESFULLY SHUTDOWN Explanation: The service task shutdown process finished. UNABLE TO SHUTDOWN THE SERVICE TASK Explanation: Either at PLTSD or as a result of the OMEG SRVSHUT transaction, exceptional conditions were encountered. These conditions are described by messages KOC1217 and KOC1218. User Response: Refer to messages KOC1217 and KOC1218. SERVICE TASK INITIALIZATION GETMAIN FOR nnnnx FAILED Explanation: The GETMAIN issued for nnnnb (bytes) or nnnnk (kilobytes) failed. System Action: Service task initialization is not performed. User Response: Increase the size of the CICS address space by nnnnb or nnnnk. TEMPORARY STORAGE LIMIT (nnn) EXCEEDS AVAILABLE STORAGE Explanation: This is an internal error. System Action: Processing stops. SERVICE TASK INITIALIZATION COMPLETED Explanation: Initialization of the service task is complete. SECONDARY TASK LIMIT (nnn) EXCEEDS AVAILABLE STORAGE Explanation: This is an internal error. System Action: Processing stops. 282 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

283 OC1215 OC1216 OC1217 OC1218 OC1223 OC1224 SERVICE TASK START aaaaaaaa FAILURE Explanation: CICS returned aaaaaaaa when a START command for the service task was issued. System Action: Processing stops. User Response: If aaaaaaaa is NOTAUTH, make sure the transaction OMEG is defined with no resource security (RESSEC(NO)) or command security (CMDSEC=NO). Also make sure the group DFHEXEC is installed. If this condition persists, change the resource security number for the program KOCOME00 to PUBLIC (RESSECNUM(PUBLIC)). For other values in aaaaaaaa contact IBM Software Support. TSBROWSE ENTRY IN SERVICE LIMITS TABLE COULD NOT BE LOCATED Explanation: This is an internal error. System Action: Processing stops. PURGE OF SECONDARY SERVICE TASK FAILED WITH aaaaaaaa Explanation: The SET TASK command for one of the secondary tasks failed. aaaaaaaa is the exceptional condition raised for the EXEC CICS SET TASK command. This message is only applicable to CICS/ESA. System Action: Processing continues. Refer to the CICS/ESA System Programming Reference, command SET TASK. PURGE OF SERVICE TASK FAILED WITH aaaaaaaa Explanation: The SET TASK command for the service task failed. aaaaaaaa is the exception condition raised for the EXEC CICS SET TASK command. This message is only applicable to CICS/ESA. System Action: Processing continues. Refer to the CICS/ESA System Programming Reference, command SET TASK. SECONDARY SERVICE TASK START aaaaaaaa FAILURE Explanation: CICS returned aaaaaaaa when the service task attempted to start a secondary task. System Action: Processing continues. User Response: If aaaaaaaa is NOTAUTH, make sure the transaction OMEG is defined with no resource security (RESSEC(NO)) or command security (CMDSEC=NO). Also, make sure the group DFHEXEC is installed. If this condition persists, change the resource security number for the program KOCOME00 to PUBLIC (RESSECNUM(PUBLIC)). For any other value of aaaaaaaa, contact IBM Software Support. FIRST SECONDARY SERVICE TASK FAILED TO INITIALIZE Explanation: The service task started a secondary task which failed to respond. System Action: Processing continues. OC1000 OC

284 OC1225 OC1226 OC1227 OC1228 OC1229 OC1230 OC1231 SECONDARY SERVICE TASK NOT STARTED BECAUSE OF MAXTASKS LIMIT Explanation: Starting a new secondary task would put CICS in a MAXTASKS condition; therefore, the task is not started. System Action: Processing continues. User Response: Revise the MXT SIT parameter. SECONDARY SERVICE TASK NOT STARTED BECAUSE OF AMAXTASKS LIMIT Explanation: Starting a new secondary task would put CICS in an AMAXTASKS condition; therefore, the task is not started. System Action: Processing continues. User Response: Revise the AMXT SIT parameter. UNABLE TO SETUP PARAMETERS FOR THE SECONDARY TASK Explanation: This is an internal error. System Action: Processing stops. FIRST SECONDARY SERVICE TASK ABENDED Explanation: The first secondary task started by the service task abended. System Action: Processing continues. RM CALL WAS UNSUCCESSFUL - RETURN CODE = cc Explanation: The service task or one of the secondary tasks failed with return code cc when trying to establish its umbrella transaction or program ID. System Action: Processing continues. User Response: Refer to the OMEGAMON II for CICS Configuration and Customization Guide for an explanation of the return code and contact IBM Software Support. ABEND aaaa DETECTED - SERVICE TASK IS TERMINATING Explanation: The service task abended with abend code aaaa and is terminating. System Action: The service task is no longer available. User Response: Issue the transaction OMEG SRVSHUT to terminate any secondary service tasks, then issue OMEG SRVINIT to make the service task available again. OCSRV SERVICE TASK WAITING FOR WORK Explanation: The service task has initialized successfully and is waiting for work. This is an informational message only. 284 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

285 OC1240 OC1241 OC1242 OC1243 OC1244 OC1245 OC1246 SECONDARY TASK GETMAIN FOR nnnnx FAILED Explanation: One of the secondary tasks failed when issuing a GETMAIN for nnnnx, where nnnn is a number, b is for bytes or k is for kilobytes. System Action: The secondary task does not initialize. User Response: Further requests issued by the AIDK command will cause a new secondary task to initialize. If the situation persists, increase the CICS region size. ABEND aaaa DETECTED - SECONDARY SERVICE TASK IS TERMINATING Explanation: Abend aaaa was detected by the secondary service task. It is terminating. System Action: The main service task remains available. OCSR2 SECONDARY SERVICE TASK WAITING FOR WORK Explanation: The secondary service task has initialized successfully and is waiting for work. This is an informational message only. OCSR2 SMF DATA COLLECTION QUIESCED Explanation: This is an informational message. For CICS/MVS users it indicates that OMEGAMON II will no longer write SMF records. For CICS/ESA users it indicates that CICS will no longer write SMF records. OCSR2 SMF DATA COLLECTION INITIATED Explanation: This is an informational message. For CICS/MVS users it indicates that OMEGAMON II will start writing SMF records. For CICS/ESA users it indicates that CICS will start writing SMF records. OCSR2 CICS MONITORING TURNED OFF Explanation: This is an informational message indicating that CICS performance monitoring has been turned off. OCSR2 CICS MONITORING TURNED ON Explanation: This is an informational message indicating that CICS global and performance monitoring have been turned on. OC1000 OC

286 OC1401 OC1402 OC1403 OC1404 OC1405 SHOULD OMEGAMON II FOR CICS PURGE CONVERSATIONS? REPLY YES OR NO. Explanation: This is the text of a Write To Operator with Reply (WTOR). It is issued when SHUTOPT=OPER has been specified and OMEGAMON II has found a task to purge. This process happens only at CICS termination. System Action: The SHUTOPT process of OCSHUT waits for a reply. User Response: Only the first character of the reply is checked. If you specify NO, SHUTOPT processing terminates immediately. The rest of OMEGAMON II PLTSD processing continues. If you specify YES, the processing will operate as though you had specified SHUTOPT=PURGE. All tasks waiting for terminal I/O are purged. OMEGAMON II FOR CICS HAS PURGED nnnn TASKS Explanation: After completing the SHUTOPT=PURGE cycle (or after a user reply of YES to OC1401), SHUTOPT processing tells you how many tasks have been purged. For CICS 1.7/2.1, this is the number of tasks canceled, whether or not the cancel was successful. For CICS and above, this is the number of tasks canceled and CICS return codes indicated success. System Action: SHUTOPT processing ends. OMEGAMON II termination processing continues. PROCESS cccccccccccccccc ERROR nnnn Explanation: SHUTOPT processing has reached an error state. This message is issued from a subroutine, and ccc identifies the process that invoked the error routine. nnnn is the value from an EXEC CICS request (EIBRESP). System Action: SHUTOPT processing ends. OMEGAMON II PLT shutdown processing does not continue. OCSHUT INSUFFICIENT WORK AREA FOR TASK PURGE Explanation: The OMEGAMON II PLT shutdown program could not purge tasks due to an insufficient work area. System Action: The OMEGAMON II PLT shutdown program terminates without purging all tasks waiting for terminal input. START OF SHUTOPT=PURGE PROCESSING Explanation: CICS termination has been detected. Your GLOBAL assembly has requested OMEGAMON II to purge all tasks waiting in terminal control. System Action: Task purging immediately follows. OC1402 follows the purge process. 286 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

287 OC1406 OC2001 OC2002 OC2003 OC2004 OC2005 OC2051 START OF SHUTOPT=OPER PROCESSING Explanation: CICS termination has been detected. Your GLOBAL assembly has requested OMEGAMON II to check for tasks waiting in terminal control. If any are found, confirm permission to cancel the tasks (message OC1401). System Action: OMEGAMON II waits for response to message OC1401. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: The ENQ command was entered with an invalid keyword. System Action: The command fails. User Response: Correct the keyword, and re-enter the ENQ command. KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: The ENQ RESOURCE command was entered without a resource argument or the ENQ QEA command was entered without a QEA address argument. System Action: The command fails. User Response: Use the zoom key to select an enqueue resource from the ENQ display, or specify a resource or a QEA address and re-enter the ENQ command. SPECIFIED ARGUMENT IS NOT HEXADECIMAL Explanation: The ENQ QEA command argument was not hexadecimal. System Action: The command fails. User Response: Use the zoom key to select an enqueue resource from the ENQ display, or specify a valid QEA address and re-enter the ENQ command. SPECIFIED ARGUMENT IS TOO LONG Explanation: The ENQ RESOURCE command argument was more than 16 characters, or the ENQ QEA command QEA address was more than 8 hexadecimal digits. System Action: The command fails. User Response: Use the zoom key to select an enqueue resource from the ENQ display, or specify a valid resource argument or QEA address and re-enter the ENQ command. NO TASKS WAITING ON ENQUEUES Explanation: The ENQ command has found no tasks waiting on enqueues (for a list of all enqueues in the system, enter ENQ RESOURCE=*). System Action: The ENQ command terminates. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: The STOR command was entered with an invalid keyword. System Action: The command fails. User Response: Correct the keyword, and re-enter the STOR command. OC1000 OC

288 OC2053 OC2054 OC2055 OC2060 OC2071 OC2072 INVALID GROUP SPECIFIED, RE-ENTER Explanation: The STOR GROUP command was entered with an invalid group argument. System Action: The command fails. User Response: Use the zoom key to select the required group from the STOR GROUP=ALL display. Correct the group argument, and re-enter the STOR GROUP command. SPECIFIED ARGUMENT IS TOO LONG Explanation: The STOR PAMDSA or PAMEDSA command page number was greater than 8 digits. System Action: The command fails. User Response: Use the zoom key to select the required page from the STOR or PAMEDSA display, or specify a page number with 8 or fewer digits and re-enter the STOR PAMDSA or PAMEDSA command. SPECIFIED ARGUMENT IS NOT AN INTEGER Explanation: The STOR PAMDSA or PAMEDSA command page number was not a decimal integer. System Action: The command fails. User Response: Use the zoom key to select the required page from the STOR or PAMEDSA display, or specify a decimal page number and re-enter the STOR PAMDSA or PAMEDSA command. SPECIFIED PAGE NOT IN DSA/EDSA Explanation: The STOR PAMDSA or PAMEDSA command page number was not in the current DSA/EDSA. System Action: The command fails. User Response: Use the zoom key to select the required page from the STOR or PAMEDSA display, or check the number of pages in the DSA/EDSA and re-enter the STOR PAMDSA or PAMEDSA command. INVALID STOR REQUEST FOR THIS CICS RELEASE Explanation: A STOR keyword was entered that was unrecognized by the command for the current CICS release. System Action: The STOR command terminates. User Response: Verify the input keywords for the current CICS release. PROGRAM COMPRESSION DATA NOT CURRENT Explanation: The STOR command has detected that the program compression data has not been updated in the last minute. This probably means that CICS is not being dispatched. System Action: The STOR command terminates. User Response: Investigate why CICS is not being dispatched. If CICS is being dispatched, contact IBM Software Support. 288 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

289 OC2073 OC2074 OC2200 OC2201 OC2202 OC2203 OC2204 PROGRAM COMPRESSION DATA NOT AVAILABLE, ISSUE OMEG INIT Explanation: Display of program compressions using the STOR command with the COMPRESSIONS keyword requires that OMEGAMON II be initialized in the CICS region being monitored. System Action: The command fails. User Response: Issue an OMEG INIT in the required CICS region. PROGRAM COMPRESSION ACCESS ERROR Explanation: Display of program compressions using the STOR command with the COMPRESSIONS keyword has failed to locate a required OMEGAMON II control block (SVCOM) in the CICS region. System Action: The command fails. INVALID CALL TYPE Explanation: An invalid call has been generated by the RLMU command processor. System Action: The call is rejected. ENTRY NOT FOUND Explanation: An RLMU DEL command has been issued and the item to be processed cannot be found. System Action: The call is rejected. NO SPACE FOR REQUESTED ADDITION Explanation: An RLMU ADD command has been issued and there is insufficient room to perform the addition. System Action: The call is rejected. User Response: Review existing RLIM definitions and free up space through the RLMU DEL command. INITIALIZATION IN PROGRESS Explanation: An RLMU ADD DEL command has been issued while another user is initializing the resource limiting environment. System Action: The call is rejected. User Response: Retry the command. If this incurs the same response, contact IBM Software Support. RLIMDATA IS IN AN INCONSISTENT STATE Explanation: The RLMU command processor has detected a problem with the data that it is managing. System Action: The call is rejected. OC1000 OC

290 OC2205 OC2206 OC2207 OC2208 OC2209 OC2210 OC2220 EXPANSION AREA GETMAIN FAILURE Explanation: The first RLMU command issued caused a GETMAIN attempt that has incurred a bad response. System Action: The RLMU command will be unavailable during this OCCI session. User Response: Review your OCCI region size. SYSTEM BUSY, PLEASE RETRY Explanation: An RLMU call has coincided with a call from another OCCI user. System Action: The call is rejected. User Response: Retry the command. If this incurs the same response, contact IBM Software Support. RESOURCE LIMITING IS UNAVAILABLE Explanation: During OMEGAMON initialization under CICS, it was detected that there was no valid resource limiting data present. System Action: The RLIM and RLMU commands will not function. User Response: The most likely cause of this error is that the global data area module is out of step with the runtime code. Reassemble the global data area module and retry. If the problem persists, contact IBM Software Support. INVALID RLIMDATA FOUND IN GLOBAL DATA AREA MODULE Explanation: While attempting to either display or update resource limits, it was detected that the RLIMDATA present in the global data area module was invalid. System Action: The GLOB RLIM command and the RLMU command will not function. User Response: The most likely cause of this error is that the global data area module is out of step with the runtime code. Reassemble the global data area module and retry. If the problem persists, contact IBM Software Support. LOCKING ERROR Explanation: There has been a failure in the serialization of access to OMEGAMON's resource limiting data. System Action: The RLMU command will no longer function. RESOURCE LIMITS REFRESHED Explanation: An RLMU command has successfully executed. OPERATION ERROR - USE ADD, DEL OR REFRESH Explanation: An invalid RLMU call has been generated. System Action: The command will be rejected. User Response: Refer to the documentation for details for the syntax of the RLMU command. 290 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

291 OC2221 OC2222 OC2223 OC2224 OC2225 OC3001 OC3002 OC3003 FUNCTION ERROR - USE INC OR EXC Explanation: An invalid RLMU call has been generated. System Action: The command will be rejected. User Response: Refer to the documentation for details for the syntax of the RLMU command. RESOURCE ERROR - SEE KOCRLIM MACRO FOR VALID NAMES Explanation: An invalid RLMU call has been generated. System Action: The command will be rejected. User Response: Refer to the documentation for details for the syntax of the RLMU command. TRANSACTION ERROR - USE Tarantula Explanation: An invalid RLMU call has been generated. System Action: The command will be rejected. User Response: Refer to the documentation for details for the syntax of the RLMU command. LIMIT ERROR - USE KILL=nnnnnnnn OR WARN=nnnnnnnn Explanation: An invalid RLMU call has been generated. System Action: The command will be rejected. User Response: Refer to the documentation for details for the syntax of the RLMU command. INCOMPLETE COMMAND - REFER TO DOCUMENTATION FOR SYNTAX Explanation: An invalid RLMU call has been generated. System Action: The command will be rejected. User Response: Refer to the documentation for details for the syntax of the RLMU command. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: The OPT command was entered with an invalid keyword. System Action: Command OPT? is displayed. User Response: Correct the keyword, and re-enter the OPT command. UNABLE TO ACCESS SHUTDOWN OPTION, ISSUE OMEG INIT Explanation: The OPT command was entered before OMEG INIT was issued in the CICS address space. The shutdown option can only be used during PLT shutdown after OMEGAMON II has been initialized in CICS. System Action: The OPT command fails. User Response: Issue the OMEG INIT transaction to initialize OMEGAMON II in CICS. SHUTDOWN OPTION ACCESS ERROR, CODE=nn Explanation: An internal error occurred in the OPT command when accessing the PLT shutdown option. System Action: The OPT command fails. OC1000 OC

292 OC3051 OC3052 OC3053 OC3054 OC3401 OC3402 OC3403 OC3404 UNABLE TO FORMAT SIT, CODE=aaaaaaaa Explanation: The SIT command was unable to format the SIT. The length of the SIT is denoted by aaaaaaaa. The most likely explanation is that the user has applied IBM maintenance to CICS. System Action: The SIT command fails. UNABLE TO DUMP SIT, CODE=aaaaaaaa Explanation: The SIT command was unable to display the SIT in hexadecimal dump format. The length of the SIT is denoted by aaaaaaaa. System Action: The SIT command fails. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: An invalid keyword was specified as an argument to the SIT command. System Action: The SIT command fails. User Response: Correct the keyword and re-enter the SIT command. KEYWORK SPECIFIED WITHOUT ARGUMENT Explanation: A keyword was specified for the SIT command but no argument was specified for the keyword. System Action: The SIT command fails. User Response: Enter the appropriate argument for the specified keyword. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: An invalid keyword was specified as an argument to the AIDS command. System Action: The AIDS command fails. User Response: Correct the keyword and re-enter the AIDS command. KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: A keyword was specified for the AIDS command but no argument was specified for the keyword. System Action: The AIDS command fails. User Response: Enter the appropriate argument for the specified keyword. INVALID AID ADDRESS SPECIFIED Explanation: The AID address must be eight characters or less and must be hexadecimal. System Action: The AIDS command fails. User Response: Enter an eight character hexadecimal address as an argument to the ADDRESS keyword. INVALID ENTRY LENGTH SPECIFIED Explanation: The argument for the AIDS keyword must be 4 bytes or less. System Action: The AIDS command fails. User Response: Enter a four byte (or less) argument for the AIDS keyword. 292 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

293 OC3405 OC3406 OC3407 OC3411 OC3412 OC3413 OC3414 NO AIDS FOUND IN CICS Explanation: CICS was searched for Automatic Initiate Descriptors and none were found. System Action: The AIDS does not produce output. User Response: This is a normal response if no AIDs currently exist in CICS. NO MATCHING AIDS FOUND IN CICS Explanation: CICS was searched for Automatic Initiate Descriptors and none matched the specified keyword arguments. System Action: The AIDS command fails. User Response: Use the AIDS command without keywords to determine if the AID you are looking for exists. If the AID is displayed by the AIDS command, and you have entered the keyword=cccc argument correctly, contact IBM Software Support. REQUESTED AID NOT FOUND IN CICS Explanation: CICS was searched for an Automatic Initiate Descriptor and none matched the specified address. System Action: The AIDS command fails. User Response: Use the AIDS command without keywords to determine if the AID you are looking for exists. If the AID is displayed by the AIDS command, and you have entered the ADDRESS=cccccccc argument correctly, contact IBM Software Support. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: An invalid keyword was specified as an argument to the ICE command. System Action: The ICES command fails. User Response: Correct the keyword and re-enter the ICES command. KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: A keyword was specified for the ICES command but no argument was specified for the keyword. System Action: The ICES command fails. User Response: Enter the appropriate argument for the specified keyword. INVALID ICE ADDRESS SPECIFIED Explanation: The ICE address must be eight characters or less and must be hexadecimal. System Action: The ICES command fails. User Response: Enter an eight character hexadecimal address as an argument to the ADDRESS keyword. INVALID ENTRY LENGTH SPECIFIED Explanation: The argument for this ICES keyword must be 4 bytes or less. System Action: The ICES command fails. User Response: Enter a four byte (or less) argument for the ICES keyword. OC1000 OC

294 OC3415 OC3416 OC3417 OC3420 OC3422 OC3423 OC3430 NO ICES FOUND IN CICS Explanation: CICS was searched for Interval Control Elements and none were found. System Action: The ICES command does not produce output. NO MATCHING ICES FOUND IN CICS Explanation: CICS was searched for Interval Control Elements and none matched the specified keyword arguments. System Action: The ICES command fails. REQUESTED ICE NOT FOUND IN CICS Explanation: CICS was searched for an Interval Control Element and none matched the specified address. System Action: The ICES command fails. AIDK MUST BE QUALIFIED BY TERM, TRAN OR ADDRESS Explanation: When killing an AID, the AID must be qualified with either a TERM, TRAN, or ADDRESS argument. System Action: The AIDK command fails. User Response: Enter the appropriate keyword with argument and re-enter the command. KILL PROCESSING WAS BYPASSED FOR THIS AID Explanation: The AID was no longer in the AID chain. It was either already killed, or had completed processing and was dechained by CICS. System Action: The AIDK command fails. KILL PROCESSING WAS BYPASSED FOR 1 OR MORE AIDS Explanation: The AIDs was no longer in the AID chain. It (they) had already been killed or processed by CICS. System Action: The AIDK command fails. ICEK MUST BE QUALIFIED BY TERM, TRAN OR ADDRESS Explanation: When killing an ICE, the ICE must be qualified with either a TERM, TRAN, or ADDRESS argument. System Action: The ICEK command fails. User Response: Enter the appropriate keyword with argument and re-enter the command. 294 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

295 OC3432 OC3433 OC3434 KILL PROCESSING WAS BYPASSED FOR THIS ICE Explanation: The ICE is no longer in the ICE chain. It has either already been killed, or has completed processing and has been dechained by CICS. Kill processing is also bypassed if the ICE type is Wait or Post or if the ICE is a DWE. System Action: The ICEK command fails. KILL PROCESSING WAS BYPASSED FOR 1 OR MORE ICES Explanation: The ICEs was no longer in the ICE chain. It (they) had either already been killed, or had completed processing and was dechained by CICS. System Action: The ICEK command fails. KILL BYPASSED, SERVICE TASK RETURNED = cccccccc Explanation: This message is issued in response to an AIDK command, and indicates that the service task was not able to perform the service. The possible values for cccccccc are: secondary tasks are already started. No more are allowed Invalid request (internal error) The secondary task is not responding The secondary task abended A new secondary task was started during the last second No room is available in the secondary tasks table b c Unable to start a new secondary task. Unable to start a new secondary task due to MXT or AMXT The service task could not find the AID to be killed A task was already started for the AID to be killed The AID was unchained, but its storage could not be freed The AID was located by the service task but its terminal ID was not the same as that recorded by the AIDK command. The aid is not killed The AID was located by the service task but its transaction ID was not the same as that recorded by the AIDK command. The aid is not killed The AID was located by the service task but its request ID was not the same as that recorded by the AIDK command. The AID is not killed F F F2 The service task is not responding. The AID is not killed. There are no available work elements to use for this request. The AID is not killed. The service task is not available. The AID is not killed. OC1000 OC

296 000000F F4 The service task work area could not be found. The AID is not killed. OMEG INIT was not issued. The AID is not killed. System Action: User Response: None. Action: Retry the command later Contact IBM Software Support Due to activity in the CICS region, the service task did not complete the request in the allotted time. Check whether the AID still exists and, if so, enter the command again. If the situation persists, shut down and initialize the service task by issuing the OMEG transaction with the SRVSHUT and SRVINIT keywords Issue OMEG SRVSHUT to finish the service task processing. Then, issue OMEG SRVINIT to initialize it and reenter the command Retry the command later Contact IBM Software Support b c Contact IBM Software Support. Increase the MXT and AMXT SIT values Correct the AID address entered with the command and reenter the command None None Due to CICS activity, data for the AID has changed. Verify that the AID still exists for the terminal, and, if so, reenter the command Due to CICS activity, data for the AID has changed. Verify that the AID still exists for the transaction ID, and, if so, reenter the command Due to CICS activity, data for the AID has changed. Verify that the AID with the REQID exists and reenter the command F F F F F4 The service task is taking longer than expected to perform the request, probably due to high activity in CICS. If the marked AIDs were not killed, issue the request again. Issue the OMEG SRVSHUT transaction, then OMEG SRVINIT to reinitialize the service task. Issue the OMEG SRVINIT transaction to initialize the service task. Issue the OMEG SRVSHUT transaction, then OMEG SRVINIT to reinitialize the service task. Ensure that transaction OMEG and program KOCOME00 are defined to CICS and that transaction OMEG has been successfully executed in CICS. 296 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

297 OC3460 OC3461 OC3462 OC3463 OC3464 OC3500 INVALID USER TCA ADDRESS SPECIFIED Explanation: The address specified for the TCA keyword is invalid. This keyword must contain an existing User TCA address. Either the address was entered incorrectly or the task has already ended. System Action: The EIB command terminates. User Response: Specify a valid User TCA address for the task you are inquiring about if the transaction has not yet ended. POINTER TO EXEC INTERFACE STRUCTURE NOT AVAILABLE Explanation: During EIB command processing, the control block structure of the specified task is verified. An error was detected; therefore, the request cannot be processed. System Action: The EIB command terminates. User Response: Investigate the task in question. Make sure that the transaction has not ended yet or CICS has not suffered a storage corruption, damaging task-related control block structures. POINTER TO EXEC INTERFACE BLOCK NOT AVAILABLE Explanation: During EIB command processing, the control block structure of the specified task is verified. An error was detected; therefore the request cannot be processed. System Action: The EIB command terminated. User Response: Investigate the task in question. Make sure the transaction has not ended yet or CICS has not suffered a storage corruption that has damaged task-related control block structures. PLEASE SPECIFY USER TCA ADDRESS WITH KEYWORD TCA= Explanation: The EIB command was entered without the TCA keyword. System Action: The EIB command terminated. User Response: The User TCA address must be specified with keyword 'TCA=' for the EIB command to furnish the request. To view the format of the EIB command, enter '/' in column one followed by EIB. EIB COMMAND DOES NOT SUPPORT CICS SYSTEM TASKS Explanation: The specified User TCA address belongs to a CICS system task. Such tasks are not eligible for the EIB command processing. System Action: None, this is only an informational message. User Response: Ensure that the correct User TCA address was specified for other than CICS system tasks. TABL Invalided ENTRY SUPPLIED Explanation: The entry name/number specified for the table identified by aaa. User Response: Correct the table entry name/number and re-enter the command. OC1000 OC

298 OC3501 OC3502 OC3503 OC3504 OC3505 OC4001 OC4002 OC4003 TABL ENTRY CONFLICTS WITH CICS TABLE SPECIFIED Explanation: The table name is incompatible with the entry name specified. User Response: Use the proper entry name/number keyword for the desired file, or use the generic ID= keyword operand to specify an entry. TABL INVALID SELECTION OPTION SPECIFIED Explanation: The selection criteria specified are unsupported. User Response: Correct the arguments of the SELECT= keyword and re-enter the command. TABL SELECTION INVALID FOR CICS TABLE SPECIFIED Explanation: The selection criteria specified are not compatible with the table name entered. User Response: Correct the arguments of the SELECT= keyword and re-enter the command. TABL SELECTION CRITERIA INVALID WITH SPECIFIC ENTRY Explanation: Selection criteria and a specific entry name/number were specified as operands of the TABL command. User Response: Change the entry name/number to specify a generic value (using wild card characters) or choose either the selection criteria or an entry name/number (but not both), for the table search. TABL DISPLAY OPTIONS ONLY VALID FOR SINGLE TABLE ENTRY Explanation: The DUMP option was specified for a generic table search. User Response: Limit the table search to a specific entry or remove the DUMP operand from the TABL command. GRPS INVALID GROUP KEYWORD SPECIFIED, RE-ENTER Explanation: The command encountered an invalid keyword. User Response: Correct the input, and re-enter the command. GRPS EXCESS KEYWORDS IGNORED Explanation: Extra keywords were specified in the GRPS command. System Action: The command ignores the additional keywords. GRPS KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: A parameter is missing for a keyword on the GRPS command. User Response: Correct the input, and re-enter the command. 298 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

299 OC4004 GRPS GROUP MUST BE NUMERIC IN THE RANGE 1 MAXGRPS OR * Explanation: The GRPS command expects a group identifier but finds an invalid value. The value must be in the range 1 maxgrps inclusive, where maxgrps is the value specified in the KOCGLOB macro, or the wildcard value * representing all groups must be specified. User Response: Correct the input, and re-enter the command. OC4005 GRPS GROUP NUMBER WAS NOT SUPPLIED Explanation: The GRPS command expects a group identifier but finds none. User Response: Correct the input, and re-enter the command. OC4006 GRPS GROUP=* IS INVALID WITHOUT SPECIFYING ELEMENTS Explanation: The generic group identifier may only be used if specific group elements are included (TERM=, TRAN=, PROG=). User Response: Correct the input, and re-enter the command. OC4007 GRPS GROUP TYPE NOT SPECIFIED Explanation: A requested group change could not be made because the group type was not included in the command. User Response: Correct the input, and re-enter the command. OC4008 GRPS INVALID GROUP TYPE. SPECIFY TRAN, PROG, TERM, OR LU Explanation: The GRPS command specified an unrecognized group type. User Response: Correct the input, and re-enter the command. OC4009 GRPS GROUP TYPE AND ELEMENT TYPE CONFLICT Explanation: The TYPE= keyword parameter of GRPS does not agree with the type of elements specified. User Response: Correct the input, and re-enter the command. OC4010 OC4011 GRPS INVALID ELEMENTS SPECIFIED Explanation: The group elements were improperly formatted or have an invalid length. User Response: Correct the input, and re-enter the command. GRPS NO GROUPS DEFINED Explanation: There are no groups currently defined to OMEGAMON II. OC1000 OC

300 OC4012 OC4013 OC4014 OC4015 OC4016 OC4017 OC4018 GRPS REQUESTED GROUP WAS NOT FOUND Explanation: The specified group does not exist. GRPS REQUESTED GROUP HAS NO ELEMENTS DEFINED Explanation: The specified group is empty. GRPS GROUP IS NOT DEFINED Explanation: The specified group is not currently defined to OMEGAMON II. GRPS GROUP IS ALREADY DEFINED Explanation: An attempt was made to add a group that already exists. User Response: Specify a group that is not already created. GRPS RTA MONITOR ACTIVE, REQUEST IGNORED Explanation: Groups cannot be modified while the response time collector is active. System Action: The request is ignored. User Response: Use the RTA STOP command to terminate the response time collector. Then re-enter the GRPS command, followed by the RTA START command, to reactivate the response time collector GRPS ELEMENT THRESHOLD REQUIRES AN ELEMENT NAME Explanation: The GRPS command has been issued with the RESP, HOST, or NET threshold setting keyword, but no element has been specified. These keywords are applicable only to elements. System Action: The update or add fails. User Response: Add an element keyword and argument and re-issue the command. GRPS HOST AND NET TIMES VALID ONLY WITH LUs Explanation: The GRPS command has been issued with the HOST or NET threshold setting keyword for a program, terminal, or transaction. These thresholds are applicable only to LUs. System Action: The update or add fails. User Response: Remove the HOST or NET keyword and re-issue the command. 300 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

301 OC4020 OC4021 OC4023 OC4024 OC4026 OC4027 OC4029 OC4030 GRPS WARNING: GROUP NAME TRUNCATED TO 12 BYTES Explanation: The group name exceeds the twelve character limit. System Action: The group s name includes the first twelve characters specified. GRPS WARNING: GROUP NAME DEFAULTED TO GROUP NUMBER Explanation: A group name was not specified when creating a group. System Action: The group number will be assigned as the name of the group. For example, if group one is defined, it will have the name GROUP 01. GRPS INVALID CRITICAL THRESHOLD SPECIFIED, RE-ENTER Explanation: The interval record collector (critical) threshold specified is not valid. User Response: Correct the threshold, and re-enter the command. GRPS INVALID RESPONSE THRESHOLD SPECIFIED, RE-ENTER Explanation: The response time threshold specified is not valid. User Response: Correct the threshold, and re-enter the command. GRPS WARNING: GROUP CRITICAL THRESHOLD DEFAULT IS 2 SECS Explanation: No critical threshold was specified on the GRPS command, so a default value of two seconds was assumed. GRPS WARNING: RESPONSE THRESHOLD DEFAULT IS 1 SEC Explanation: No response time threshold was specified on the GRPS command, so a default value of one second was assumed. GRPS GENERIC IDS ARE INVALID FOR LU NAMES Explanation: Generic Logical Unit IDs are not supported. The full LU name must be used. System Action: The request is ignored. User Response: Specify only complete VTAM Logical Unit IDs. GRPS INVALID ADD, ELEMENTS ALREADY DEFINED IN GROUP Explanation: The specified group already contains the element being added. System Action: The request is ignored. OC1000 OC

302 OC4031 OC4032 OC4033 OC4034 OC4035 OC4036 OC4037 GRPS NO SPACE REMAINING THE GROUPS ID TABLE Explanation: An attempt to add an element to the group table failed due to a lack of available space. User Response: The maximum number of IDs that can be supported via the GRPS facility is defined on the KOCGLOB MAXIDS=nnn parameter. Increase the value and reassemble the GLOBAL module. GRPS INVALID HOST THRESHOLD SPECIFIED, RE-ENTER Explanation: The specified end-to-end host threshold is not valid. User Response: Correct the threshold, and re-enter the command. GRPS INVALID NETWORK THRESHOLD SPECIFIED, RE-ENTER Explanation: The specified end-to-end network threshold is not valid. User Response: Correct the threshold, and re-enter the command. GRPS WARNING: HOST THRESHOLD DEFAULT IS 1 SEC Explanation: No LU host threshold was specified on the GRPS command, so a default value of one second was assumed. GRPS WARNING: NETWORK THRESHOLD DEFAULT IS 1 SEC Explanation: No LU network time threshold was specified on the GRPS command, so a default value of one second was assumed. GRPS WARNING: HOST THRESHOLD > RESPONSE THRESHOLD Explanation: The end-to-end host threshold exceeds the total response time threshold for the Logical Unit specified. The host response time is a component of the total response time. Specifying a host threshold that is greater than the total response time threshold guarantees that the response threshold will always be exceeded before the host threshold. GRPS WARNING: NETWORK THRESHOLD > RESPONSE THRESHOLD Explanation: The end-to-end network threshold exceeds the total response time threshold for the Logical Unit specified. The network response time is a component of the total response time. Specifying a network threshold that is greater than the total response time threshold guarantees that the response threshold will always be exceeded before the network threshold. 302 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

303 OC4040 OC4041 OC4042 OC4043 OC4044 OC4045 OC4050 OC4051 GRPS GROUP=* IS INVALID ON UPDATE Explanation: A generic group identifier may not be used when performing an update. User Response: Correct the input, and re-enter the command. GRPS GROUP UPDATES INVALID WHEN ELEMENTS SPECIFIED Explanation: The UPD operand of GRPS cannot be used with a specific group identifier when elements are specified on the command. User Response: Correct the input, and re-enter the command. GRPS GROUP TYPE CANNOT BE UPDATED UNTIL GROUP IS EMPTY Explanation: Groups containing entries cannot have their type changed until all elements are deleted from the group. User Response: Correct the input, and re-enter the command. GRPS INVALID UPDATE, ELEMENTS NOT DEFINED Explanation: An attempt was made to update a group element which could not be found in the group table. User Response: Correct the input, and re-enter the command. GRPS THRESHOLD MUST BE SUPPLIED WHEN UPDATING ELEMENTS Explanation: A request to update one or more group elements did not include a threshold value. User Response: Correct the input, and re-enter the command. GRPS INVALID UPDATE, NO CHANGES SPECIFIED Explanation: The GRPS command has been issued with the UPDATE keyword but other keywords are missing. System Action: The update fails. User Response: Add keywords for the UPDATE request that is required and re-issue the command. GRPS INVALID DELETE, NO ELEMENTS SPECIFIED Explanation: The elements to be deleted by GRPS were not specified. User Response: Correct the input, and re-enter the command. GRPS INVALID DELETE, ELEMENTS NOT DEFINED IN GROUP Explanation: The elements to be deleted by GRPS do not belong to the group specified. User Response: Correct the input, and re-enter the command. OC1000 OC

304 OC4060 OC4061 OC4101 OC4102 OC4103 OC4104 OC4151 GRPS GROUP=* IN INVALID ON CLEARANCE Explanation: A generic group identifier may not be used when performing a clear operation. User Response: Correct the input, and re-enter the command. GRPS ELEMENT LIST IS INVALID ON CLEARANCE Explanation: An element list may not be specified when performing a clear. Clear will remove all elements from a given group. Use the DEL operand of GRPS to selectively remove entries from a group. User Response: Correct the input, and re-enter the command. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: The TSQ command has been entered with an invalid keyword. System Action: The command fails. User Response: Correct he keyword and re-enter the command. Use the help facility to determine valid keywords. KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: The TSQ command has been entered without an ID or SEL argument. System Action: The command fails. User Response: Add an ID argument or valid select criteria to the requisite keyword and re-enter the command. INVALID SELECT CRITERIA, USE HELP FOR A VALID LIST Explanation: The TSQ command has been entered with an invalid argument for the SELECT keyword. System Action: The command fails. User Response: Use an argument for the SELECT keyword that is valid and re-enter the command. SPECIFIED ARGUMENT IS TOO LONG Explanation: The TSQ command has been entered with an ID that is longer than eight characters. System Action: The command fails. User Response: Change the ID argument to be eight or fewer characters and re-enter the command. INVALID KEYWORD SPECIFIED, RE-ENTER Explanation: The RESP command has been entered with an invalid keyword. System Action: The command fails. User Response: Correct he keyword and re-enter the command. Use the help facility to determine valid keywords. 304 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

305 OC4152 KEYWORD SPECIFIED WITHOUT ARGUMENT Explanation: The RESP command has been entered without an ID or NUM argument. System Action: The command fails. User Response: Add an ID argument or a group number to the requisite keyword and re-enter the command. OC4153 GROUP NUMBER MUST BE BETWEEN 1 AND 30 Explanation: The TSQ command has been entered with an argument for the NUM keyword that is not in the valid range. System Action: The command fails. User Response: Change the group number to be in the range 1 30 and re-enter the command. OC4154 SPECIFIED ARGUMENT IS TOO LONG Explanation: The RESP command has been entered with an ID that is longer than 8 characters. System Action: The command fails. User Response: Change the ID argument to be 8 or fewer characters and re-enter the command. OC4200 OC4221 OC4222 INTERNAL ERROR, RC=nn Explanation: Collector of information about the CICS dump component has detected an internal error in processing the request. System Action: The request is ignored. Invalid control block structure detected Explanation: OMEGAMON II for CICS is unable to process the MQ control blocks detected in CICS. System Action: The command terminates normally after issuing this error message. User Response: Contact IBM Software Support for assistance with this problem. Unknown version of MQ detected Explanation: The version/release of MQ you executing is not supported by OMEGAMON II for CICS. System Action: The command terminates normally after issuing this error message. User Response: Contact IBM Software Support for assistance with this problem. OC1000 OC

306 OC4230 OC4231 OC4232 OC4233 OC5000 Subroutine IGGCSI00 was not loaded at startup Explanation: OMEGAMON II for CICS uses the IBM subroutine IGGCSI00 to collect VSAM details. The subroutine is loaded during OMEGAMON startup. User Response: Review the OMEGAMON log for any messages which may indicate why the module was not loaded. Contact IBM Software Support for further assistance. FCT error received from IGGCSI00: RC=04, Reason code=xxxx Explanation: OMEGAMON II for CICS uses the IBM subroutine IGGCSI00 to collect VSAM details. The subroutine returned a response code 4, with the specified reason code. User Response: See the response and reason codes for the IGGCSI00 subroutine, which are listed in the IBM manual Catalog Search Interface User s Guide in the section "Managing Catalogs". Contact IBM Software Support for further assistance. FCT error received from IGGCSI00: RC=08, Reason code=xxxx Explanation: OMEGAMON II for CICS uses the IBM subroutine IGGCSI00 to collect VSAM details. The subroutine returned a response code 8, with the specified reason code. User Response: See the response and reason codes for the IGGCSI00 subroutine, which are listed in the IBM manual Catalog Search Interface User s Guide in the section "Managing Catalogs". Contact IBM Software Support for further assistance. FCT error received from IGGCSI00: RC=xx Explanation: OMEGAMON II for CICS uses the IBM subroutine IGGCSI00 to collect VSAM details. The subroutine returned a response code 12 or 16. User Response: See the response and reason codes for the IGGCSI00 subroutine, which are listed in the IBM manual Catalog Search Interface User s Guide in the section "Managing Catalogs". Contact IBM Software Support for further assistance. UNABLE TO OBTAIN WORK AREA STORAGE Explanation: Insufficient storage was available to allocate a work area. System Action: The Global Maintenance Program terminates. User Response: Increase the region size of the job used to run the Global Maintenance Program. 306 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

307 OC5001 OC5002 OC5003 OC5004 OC5005 OC5006 UNABLE TO OPEN DATASET WITH DDNAME= aaaaaaaa Explanation: A non-zero return code was detected by the OPEN macro when attempting to open the dataset denoted by aaaaaaaa. System Action: For a read request, the default copy of the global module will be used. All other functions will terminate without further processing. User Response: Verify that the KOC2GLBL DD name is properly specified in the JCL. WILDCARDS ONLY ALLOWED WITH CONVERT AND VERIFY FUNCTIONS Explanation: A wildcard character (*) was included in the suffix of either a read, write, or test function. System Action: For a read request, the default copy of the global module will be used. All other functions will terminate without further processing. User Response: Remove the wildcard character from the global module suffix. UNABLE TO OBTAIN GLOBAL I/O BUFFERS, LENGTH= aaaaaaaa Explanation: Insufficient storage was available below the line for the I/O buffers used to process the global source file. The amount of storage that could not be allocated is denoted by aaaaaaaa. System Action: For a read request, the default copy of the global module will be used. All other functions will terminate without further processing. User Response: Increase the region size available to the Global Maintenance Program. PARM NOT SPECIFIED AS FUNCTION,SUFFIX=XX Explanation: When the Global Maintenance Program is run as a batch job, an 11 byte parameter must be passed on the EXEC card that includes a single character function followed by the global suffix. System Action: The request is ignored. User Response: Correct the PARM operand on the EXEC card and rerun the job. FUNCTION CODE IS NEITHER C, T, OR V Explanation: When the Global Maintenance Program is run as a batch job, only three function codes are permitted to either convert, test, or verify global source. System Action: The request is ignored. User Response: Correct the function code on the EXEC card and rerun the job. RKC2GLBL DATASET NOT ALLOCATED WITH LRECL=80 Explanation: The DD name RKC2GLBL points to a dataset that has not been allocated with an 80 byte logical record length. System Action: For a read request, the default copy of the global module will be used. All other functions will terminate without further processing. User Response: Allocate the RKC2GLBL dataset with an LRECL of 80 bytes. OC1000 OC

308 OC5007 OC5008 OC5009 OC5010 OC5011 OC5012 CLOSE MACRO FAILED FOR DDNAME aaaaaaaa Explanation: The DD name identified by aaaaaaaa could not be closed. System Action: For a read request, the default copy of the global module will be used. All other functions will terminate without further processing. User Response: Check the operator console for messages that may indicate why the dataset failed to close properly. ESTAE MACRO FAILED WITH RC=aaaaaaaa Explanation: Recovery could not be established using the ESTAE macro. System Action: For a read request, the default copy of the global module will be used. All other functions will terminate without further processing. User Response: Look up the ESTAE return code in the IBM Application Development Macro Reference manual, correct the problem and resubmit the job. DEQ MACRO FAILED WITH RC=aaaaaaaa Explanation: The ENQ used to serialize access to the global source dataset could not be released with a corresponding DEQ. System Action: The resource remains enqueued until the job terminates. This may result in an ENQ failure if another global maintenance request is made before the job completes. User Response: Look up the DEQ return code in the IBM Application Development Macro Reference manual, correct the problem and resubmit the job. PROCESSING SUCCESSFUL FOR GLOBAL aaaaaaaa Explanation: The global module identified by aaaaaaaa was processed without error. PROCESSING FAILED FOR GLOBAL aaaaaaaa Explanation: The global module identified by aaaaaaaa encountered problems. System Action: For a read request, the default copy of the global module will be used. All other functions will not be honored. User Response: Consult the operator console for previous messages that indicate why the global function failed. Correct the cause of the errors and retry the request. NOT AUTHORIZED, UNABLE TO LOAD DEFAULT GLOBAL Explanation: The default copy of the global module could not be brought into memory using a directed load because the job does not have APF authorization. System Action: The global request is not honored. User Response: The default module is used only when an error is encountered during processing of the global source dataset. Inspect the operator console for previous errors and make any necessary changes. To ensure that the default will be available on a failed read request, change the job to run with APF authorization. 308 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

309 OC5013 OC5014 OC5020 OC5021 OC5022 ABNORMAL TERMINATION DETECTED DURING I/O OPERATION, CODE=Sxxx Explanation: Either an x13 or x37 ABEND was encountered while trying to access the global source dataset. System Action: For a read request, the default copy of the global module will be used. No other global request functions will be honored. User Response: Refer to the IBM System Codes manual for a description of the ABEND code identified by Sxxx. Correct the cause of the error and retry the request. DEFAULT COPY OF GLOBAL HAS BEEN SELECTED Explanation: Due to an error during global processing, the Global Maintenance Program has loaded a default copy of the global module. System Action: The default copy of the global module is returned, rather than the source member requested by the caller. User Response: Refer to the operator console for errors that might explain why the Global Maintenance Program had to resort to loading a default copy of the global module. CARD: Explanation: A syntax error has been found in a global control card. This message displays the card in error. System Action: The control card is not processed. For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Refer to the operator console for an associated error message that details the syntactical problem with the control statement. CONVERSE_TIME OPERAND NOT RECOGNIZED Explanation: The CONVERSE_TIME operand is neither, IRWAIT, IOWAIT, NOIRWAIT, nor NOIOWAIT. System Action: The control card is not processed. For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify a valid CONVERSE_TIME operand. NO DATABASE SUB-COMPONENT SPECIFIED Explanation: A database control statement was found, however, no sub-component header was active at the time. System Action: The control card is not processed. For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Database sub-components are coded within << >> characters. For example, the DLI database must be specified as <<DLI>>. Ensure one of the database sub-components is properly specified for the control card in error. OC1000 OC

310 OC5023 OC5024 OC5025 OC5026 OC5027 UNABLE TO OPEN RKC2GLBL DATASET FOR INPUT Explanation: The OPEN macro used to gain access to RKC2GLBL has returned a non-zero completion code. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Check the operator console for messages that may indicate why the RKC2GLBL dataset could not be opened. Correct the cause of the error and retry the request. UNABLE TO LOCATE GLOBAL SOURCE MEMBER aaaaaaaa Explanation: The FIND macro could not locate the global member denoted by aaaaaaaa. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Verify that the specified global member appears in the partitioned dataset pointed to by the RKC2GLBL DD statement. UNABLE TO OBTAIN GLOBAL MODULE STORAGE, LENGTH=aaaaaaaa Explanation: Insufficient memory was available to store the symbol table used to harbor global settings. The value aaaaaaaa indicates the number of bytes requested on the failed GETMAIN attempt. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Increase the region size available to the job. NO COMPONENT HEADING SPECIFIED FOR KEYWORD Explanation: A control card was encountered for which no component heading could be found. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Component headings are enclosed in < > characters. They are necessary to indicate which section of a global module a particular control card is intended to effect. Check that a component heading precedes the control card in error and retry the request. SYNTAX ERROR DETECTED IN COMPONENT HEADING Explanation: A control card was encountered whose first non-blank character was a < indicating a component heading. However, a trailing > character was not found. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that the component heading is bracketed by < > characters. 310 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

311 .OC5028 OC5029 OC5030 OC5031 OC5032 OC5033 COMPONENT HEADING NOT RECOGNIZED Explanation: The component heading does not appear in the Global Maintenance Program validation tables. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that the component heading is properly specified. SYNTAX ERROR DETECTED IN CONTROL STATEMENT Explanation: The control card does not have an equals sign (=) separating the keyword from its operand. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that an equals sign is used to delimit a control keyword. CONTROL STATEMENT NOT RECOGNIZED FOR COMPONENT Explanation: The control card does not belong to the list of acceptable statements for the active component header. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Check the previous component header, enclosed in < > characters, to ensure that it accepts the specified control card. If not, place the control card under its proper component heading. SYNTAX ERROR DETECTED IN SUB-COMPONENT STATEMENT Explanation: A sub-component was indicated by the presence of << characters in the first non-blank positions of the control card. No trailing >> characters were found for the sub-component. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that sub-components are enclosed in << >> characters. SUB-COMPONENT STATEMENT NOT RECOGNIZED Explanation: A sub-component, enclosed in << >> characters, does not appear in the translation tables for the currently active component heading. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that the sub-component reflects a valid name, and that it appears under the proper component heading. INVALID CONTROL STATEMENT OPERAND Explanation: Either the control statement operand is too long, or it begins with a left parenthesis character ( to indicate a sublist, but does not end with a corresponding right parenthesis ) sublist trailer. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that the operand ends with either a blank, or in the case of a sublist, a trailing right parenthesis. OC1000 OC

312 OC5034 OC5035 OC5036 OC5037 OC5038 OC5039 OC5040 UNABLE TO CLOSE RKC2GLBL DATASET Explanation: The CLOSE macro used to release access to the KOC2GLBL dataset returned a non-zero completion code. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Check the operator console for messages that might explain why the dataset could not be closed. Correct the error and retry the request. NUMERIC OPERAND NOT WITHIN RANGE aa bb Explanation: The control card operand is not a numeric value that falls within the range denoted by aa bb. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to a valid numeric setting. SYNTAX ERROR DETECTED IN SUBLIST Explanation: A sublist was specified, enclosed in parentheses, that either contains null values or an extraneous parenthesis. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that the sublist is delimited by a single set of parentheses and that no null values are specified. SHUT_OPTIONS MUST BE PURGE/NOPURGE/OPER Explanation: The SHUT_OPTIONS keyword specifies an invalid operand. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to a valid option. OPERAND MUST BE YES/NO Explanation: The specified keyword does not have an operand of YES or NO. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to a valid option. OPERAND MUST BE AUTO/NOAUTO Explanation: The specified keyword does not have an operand of AUTO or NOAUTO. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to a valid option. CPU_THRESHOLDING MUST BE ENABLE/DISABLE/AUTO Explanation: CPU_THRESHOLDING does not specify a valid operand. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to a valid option. 312 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

313 OC5041 OC5043 OC5044 OC5045 OC5046 OC5047 OC5048 DLI_CLOCKS_AND_COUNTERS MUST BE AUTO/NOAUTO/NO Explanation: The specified keyword does not indicate a valid option. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to a valid option. TRANSACTION ID HAS ILLEGAL FORMAT Explanation: The transaction identifier exceeds four bytes in length. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify a valid transaction ID. Note that for the EXCLUDED_TRANS keyword, an asterisk (*) wildcard may only appear at the end of the transaction ID. That is, the EXCLUDED_TRANS control may not include embedded asterisk (*) wildcards. ENTRY NAME EXCEEDS EIGHT CHARACTER LIMIT Explanation: The name is greater than eight bytes, not including any MCT suffix. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify an entry name that is not greater than eight bytes in length. GLOBAL USER EXIT NAME NOT RECOGNIZED Explanation: The exit name does not appear in the global translation tables. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify a valid global user exit name. EXCLUDE LIST EXCEEDS 63 TRANSACTION IDS Explanation: The sublist contains more entries than can be accommodated in the fixed portion of the global module. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Reduce the number of IDs to 63 or fewer. NO <<GROUP>> SUB-COMPONENT HEADER ACTIVE Explanation: Control cards that define an OMEGAMON group were found without a corresponding <<GROUP>> sub-component header. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include a <<GROUP>> sub-component header to properly isolate the different group definitions. GROUP NAME EXCEEDS TWELVE CHARACTERS Explanation: The group name is too long. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Reduce the length of the group name to 12 bytes or less. OC1000 OC

314 OC5049 OC5050 OC5051 OC5052 OC5053 OC5054 OC5055 DUPLICATE GROUP_NAME DETECTED Explanation: The group name is not unique. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Select a group name that has not already been defined. GROUP NAME CONTAINING LEADING BLANKS IS INVALID Explanation: The group name starts with a blank. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Begin the group name with a non-blank character. GROUP_NAME=(*) IS INVALID Explanation: The group name is set to a single wildcard character. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Select another group name. GROUP TYPE IS NOT TRAN, TERM, PROG, OR LU Explanation: The group type keyword specifies an invalid operand. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Choose one of the four valid group types. GROUP_NUMBER NOT SPECIFIED FOR GROUP Explanation: A group number was never assigned to a group definition. Every group must have both a numeric setting and a name. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include a GROUP_NUMBER keyword in the group definition. GROUP_NAME NOT SPECIFIED FOR GROUP Explanation: A group name was never assigned to a group definition. Every group must have a unique name. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include a GROUP_NAME keyword in the group definition. UNABLE TO OBTAIN GROUP TABLE STORAGE Explanation: Insufficient storage was available to store group definitions. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Increase the region size available to the job. 314 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

315 OC5056 OC5057 OC5058 OC5059 OC5060 OC5061 OC5062 NO <<ID>> SUB-COMPONENT ACTIVE Explanation: Control cards that define an OMEGAMON group element were found without a corresponding <<ID>> sub-component header. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include an <<ID>> sub-component header to properly isolate the different group element definitions. OPERAND MUST BE 1 4 CHARACTERS Explanation: The specified keyword operand is too long. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Limit the operand to a maximum length of four characters. OPERAND MUST BE 1 8 CHARACTERS Explanation: The specified keyword operand is too long. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Limit the operand to a maximum length of eight characters. GENERIC LU IDS ARE NOT SUPPORTED Explanation: A logical unit group element contains wildcard (*) characters. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Remove the wildcard characters from the logical unit definition. TASKREQ INVALID ID SPECIFIED Explanation: The TASKREQ operand is not one of the permissible values described in the Configuration and Customization Guide. Valid options include #PAn (n=1 3), #Fnn (nn=01 36), #LPA, #MAG, or #OCD. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change the operand to specify a valid TASKREQ ID. GROUP ELEMENT NAME IS MISSING Explanation: A group element definition does not include the name of the corresponding transaction, terminal, program, or logical unit. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Supply one of the four permissible element types. ELIGIBLE_GROUPS NOT SPECIFIED FOR ID Explanation: A group element was never assigned to one or more groups. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify the groups to which the element belongs. OC1000 OC

316 OC5064 NUMBER OF IDS EXCEEDS LIMIT OF 2000 Explanation: More than 2000 groups elements have been defined. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Reduce the number of group elements to a maximum of OC5065 DATA_STORE_TYPE MUST BE EITHER DSPACE OR FILEOCMP Explanation: An invalid operand was specified for the Online Data Viewing storage medium. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Select a valid operand for the DATA_STORE_TYPE. OC5066 FILE NAME EXCEEDS 44 CHARACTERS IN LENGTH Explanation: The DATA_STORE_FILE_NAME operand is longer than the maximum length permitted for IBM datasets. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Choose a valid dataset name for the Online Data Viewing facility. OC5067 NO RESOURCE SUB-COMPONENT SPECIFIED Explanation: Control cards that define resource limiting were found without a corresponding resource sub-component header. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include a resource header, enclosed in << >> characters, that indicates the name of the resource to be monitored. OC5068 TRANSACTION COUNT FOR RESOURCE EXCEEDS LIMIT OF 999 ENTRIES Explanation: The number of either included or excluded transactions for a given resource is too large. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Limit the size of the transaction lists to 999 or less. OC5069 RTA INTERVAL NOT OF FORM (X,Y,Z) Explanation: The TIME_INTERVALS operand does not contain three sublist values. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Provide three intervals as described in the Configuration and Customization Guide. 316 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

317 OC5070 OC5071 OC5072 OC5073 OC5074 OC5075 OC5076 RTA INTERVALS ARE NOT PROPER MULTIPLES Explanation: The TIME_INTERVALS operand does not specify either a second value that is a multiple of the first, or a third value that is a multiple of the second. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Supply an operand in the form (x,y,z), where y is a multiple of x, and z is a multiple of y. TIME_SLOT END TIME BEFORE START TIME Explanation: The second TIME_SLOT sublist element is less than or equal to the first sublist element. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Select an ending time that is greater than the start time. MORE THAN 48 TIME_SLOT DEFINITIONS USED Explanation: Too many time slots have been defined. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Limit the number of time slot definitions to a maximum of 48. RTA TIME_SLOT NOT OF FORM (HHMM,HHMM) Explanation: The TIME_SLOT operand has not been specified as a sublist with two entries. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify an operand that includes both the start and end times. UNIT_ADDRESS IS MISSING Explanation: A dedicated session definition does not specify the requisite unit address. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include a UNIT_ADDRESS keyword for each dedicated session. UNIT_ADDRESS MUST BE 3 OR 4 CHARACTERS Explanation: The dedicated session unit address has an invalid length. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify a proper three- or four-character unit address. USER_PROFILE MUST BE TWO CHARACTERS Explanation: The user profile suffix has an invalid length. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Select a suffix that is two characters long. OC1000 OC

318 OC5077 OC5078 OC5079 OC5080 OC5100 OC5101 NO <<UNIT>> SUB-COMPONENT HEADER ACTIVE Explanation: Control cards that define a dedicated session were found without a corresponding <<UNIT>> sub-component header. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Include a <<UNIT>> sub-component header to properly isolate the different session definitions. UNABLE TO OBTAIN STORAGE FOR SYMBOL TABLE Explanation: Insufficient memory was available to build the variable lists that are contained within the global control block definition. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Increase the region size of the job. TOO MANY SUBLIST ENTRIES SPECIFIED, LIMIT=aa Explanation: The operand, enclosed in parenthesis, contains more than the maximum number of sublist elements allowed, as denoted by aa. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that the count of sublist entries does not exceed the limit. INCLUDED AND EXCLUDED TRANSACTIONS ARE MUTUALLY EXCLUSIVE Explanation: A resource limiting definition contains both included and excluded transaction names. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Separate the included and excluded transactions for a given resource by placing them under their own resource sub-component ID. I/O ERROR DETECTED - SYNAD MESSAGE: Explanation: During a READ or WRITE operation, a permanent I/O error was detected on the global source dataset. Data from the SYNAD message buffer is sent to the operator console. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: The SYNAD message buffer describes the source of the problem. Take appropriate action to ensure the success of I/O operations on the global source dataset. UNABLE TO OBTAIN GLOBAL MODULE STORAGE, LENGTH=aaaaaaaa Explanation: Insufficient memory was available to build the global data area in private storage above the 16MB line. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Increase the region size of the job. 318 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

319 OC5102 OC5103 OC5104 OC5105 OC5106 OC5107 INTERVAL_RECORDING=AUTO REQUIRES BOTTLENECK_ANALYSIS=AUTO Explanation: Two keywords in the global source file are inconsistent. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Change one of the keyword operands to resolve the conflict. WARNING, DLI_CLOCKS_AND_COUNTERS=NO SPECIFIED, NO DLI STATISTICSWILL BE PRODUCED Explanation: Database collection was defined for DLI. However, no clocks and counters have been requested. System Action: No DLI statistics will be produced. User Response: This message serves only as a warning and will not interfere with the creation of the global data area. CLEAR_INTERVAL_LONG MUST BE GREATER THAN CLEAR_INTERVAL_SHORT Explanation: The bottleneck analysis clear intervals are improperly set. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Alter the bottleneck analysis intervals. GROUP DEFINITION EXCEEDS MAX_GROUPS LIMIT Explanation: A GROUP_NUMBER keyword specifies an operand that is higher than the MAX_GROUPS setting. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Either increase the MAX_GROUPS limit, or eliminate the group definitions that are beyond the acceptable range. IMPROPER GROUP ASSIGNMENT FOR ID=aaaaaaaa Explanation: A group element of a particular type has been assigned to a group with a different type. For example, a transaction element includes an eligible group that is defined as containing programs. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Ensure that group elements defined under the <<ID>> sub-component all specify eligible groups with matching types. FILE NAME NOT SPECIFIED FOR DATA_STORE_TYPE=FILEOCMP Explanation: The DATA_STORE_FILE_NAME keyword was not included for an Online Data Viewing type of FILEOCMP. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Provide a file name for use by the Online Data Viewing facility. OC1000 OC

320 OC5108 OC5109 OC5110 OC5111 OC5112 OC8900 RTA TIME_SLOT OVERLAP HAS BEEN DETECTED Explanation: Two or more time slots share a common period. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Revise the slot definitions to ensure they do not overlap. LIMIT NOT SPECIFIED FOR RESOURCE aaaaaaaa Explanation: The resource denoted by aaaaaaaa does not include either a KILL or WARN limit. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Specify a limit that will act as a resource threshold. LIMITS MAY NOT BE USED WITH EXCLUDED TRANSACTIONS FOR RESOURCE aaaa Explanation: The resource denoted by aaaa contains an EXCLUDED_TRANSACTION keyword in addition to either KILL or WARN limits. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Remove the KILL_LIMIT and WARN_LIMIT keywords from resource definitions that exclude transactions. WARN_LIMIT NOT LESS THAN KILL_LIMIT FOR RESOURCE aaaaaaaa Explanation: The limiting thresholds are not properly synchronized. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Alter the limits to ensure a warning happens prior to a kill. NUMBER OF IDS EXCEEDS MAX_IDS LIMIT Explanation: Too many group elements have been defined. System Action: For a read request, a default copy of the global module will be returned to the caller. All other functions will fail to complete successfully. User Response: Either increase the MAX_IDS limit, or eliminate enough group elements to satisfy the ID constraints. RESOURCE LIMIT EXCEEDED: tttt RLaa - xxxxxxxxxxxxxxxx Explanation: The CICS transaction tttt has exceeded the xxxxxxxxxxxxxxxx resource threshold. The ACTION specified in the KOCRLIM macro was WARN or the transaction is executing under CEDF. (To terminate a transaction with abend code RLaa specify ACTION=KILL in the KOCRLIM macro.) xxxxxxxxxxxxxxxx is a text string explaining the reason for the abend code. The abend codes and their associated texts are listed below. RLAD RLCP RLDB RLDC ADABAS requests CPU time usage DB2 requests DATACOM requests 320 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

321 RLDL RLDS RLED RLEL RLFC RLID RLMQ RLSU DL/I requests DSA HWM storage EDSA HWM storage elapsed time file requests IDMS requests MQ requests SUPRA requests OC8902 System Action: Prior to issuing the message, RLIM disables the exceeded threshold to prevent the reissuing of identical messages. All remaining thresholds are kept intact and active. The transaction reverts to normal execution. User Response: Correct the application or increase the limit value in the KOCRLIM macro, if appropriate. HH:MM:SS WARNING LIMIT EXCEEDED FOR xxxxxxxxxxxxxxxx: TRANS=ttttt, TASKNO=nnnnnnnn, USER=UNKNOWN Explanation: The CICS transaction tttt has exceeded the xxxxxxxxxxxxxxxx resource threshold. The ACTION specified in the KOCRLIM macro was warn. (To terminate a transaction with abend code RLaa specify ACTION+KILL in the KOCRLIM macro.) xxxxxxxxxxxxxxxx is a text string explaining the reason for the abend code. The abend codes and their associated texts are listed below. RLAD RLCP RLDB RLDC RLDL RLDS RLED RLEL RLFC RLID RLMQ RLSU ADABAS requests CPU time usage DB2 requests DATACOM requests DL/I requests DSA HWM storage EDSA HWM storage elapsed time file requests IDMS requests MQ requests SUPRA requests System Action: Prior to issuing the message, RLIM disables the exceeded threshold to prevent the reissuing of identical messages. All remaining thresholds are kept intact and active. The transaction reverts to normal execution. User Response: Correct the application or increase the limit value in the KORCLIM macro, if appropriate. OC1000 OC

322 OC8903 HH:MM:SS ABEND RLaa ISSUED DUE TO xxxxxxxxxxxxxxxx: TRANS=ttttt, TASKNO=nnnnnnnn, USER=UNKNOWN Explanation: The CICS transaction tttt has exceeded the xxxxxxxxxxxxxxxx resource threshold. The ACTION specified in the KOCRLIM macro was kill. xxxxxxxxxxxxxxxx is a text string explaining the reason for the abend code. The abend codes and their associated texts are listed below. RLAD RLCP RLDB RLDC RLDL RLDS RLED RLEL RLFC RLID RLMQ RLSU ADABAS requests CPU time usage DB2 requests DATACOM requests DL/I requests DSA HWM storage EDSA HWM storage elapsed time file requests IDMS requests MQ requests SUPRA requests System Action: Prior to issuing the message, RLIM disables the exceeded threshold to prevent the reissuing of identical messages. All remaining thresholds are kept intact and active. The transaction is abended. User Response: Correct the application or increase the limit value in the KORCLIM macro, if appropriate. 322 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

323 X Support Information IIf you have a problem with your IBM software, you want to resolve it quickly. This section describes the following options for obtaining support for IBM software products: Searching knowledge bases on page 323 Obtaining fixes on page 324 Receiving weekly support updates on page 324 Contacting IBM Software Support on page 325 Searching knowledge bases You can search the available knowledge bases to determine whether your problem was already encountered and is already documented. Searching the information center IBM provides extensive documentation that can be installed on your local computer or on an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, and reference information. Searching the Internet If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. To search multiple Internet resources for your product, use the Web search topic in your information center. In the navigation frame, click Troubleshooting and support > Searching knowledge bases and select Web search. From this topic, you can search a variety of resources, including the following: IBM technotes IBM downloads IBM Redbooks IBM developerworks Forums and newsgroups Google Support Information 323

324 Obtaining fixes A product fix might be available to resolve your problem. To determine what fixes are available for your IBM software product, follow these steps: 1. Go to the IBM Software Support Web site at ( 2. Click Downloads and drivers in the Support topics section. 3. Select the Software category. 4. Select a product in the Sub-category list. 5. In the Find downloads and drivers by product section, select one software category from the Category list. 6. Select one product from the Sub-category list. 7. Type more search terms in the Search within results if you want to refine your search. 8. Click Search. 9. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix. For more information about the types of fixes that are available, IBM Software Support Handbook at Receiving weekly support updates To receive weekly notifications about fixes and other software support news, follow these steps: 1. Go to the IBM Software Support Web site at 2. Click My Support in the upper right corner of the page. 3. If you have already registered for My Support, sign in and skip to the next step. If you have not registered, click register now. Complete the registration form using your address as your IBM ID and click Submit. 4. Click Edit Profile. 5. In the Products list, select Software. A second list is displayed. 6. In the second list, select a product segment, for example, Application servers. A third list is displayed. 7. In the third list, select a product sub-segment, for example, Distributed Application & Web Servers. A list of applicable products is displayed. 8. Select the products for which you want to receive updates, for example, IBM HTTP Server and WebSphere Application Server. 9. Click Add products. 10. After selecting all products that are of interest to you, click Subscribe to on the Edit profile tab. 11. Select Please send these documents by weekly IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

325 12. Update your address as needed. 13. In the Documents list, select Software. 14. Select the types of documents that you want to receive information about. 15. Click Update. If you experience problems with the My support feature, you can obtain help in one of the following ways: Online: Send an message to describing your problem. By phone: Call IBM-4You ( ). Contacting IBM Software Support IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online: Go to the Passport Advantage Web page ( Passport_Advantage_Home) and click How to Enroll By phone: For the phone number to call in your country, go to the IBM Software Support Web site at and click the name of your geographic region. For customers with Subscription and Support (S & S) contracts, go to the Software Service Request Web site at For customers with IBMLink, CATIA, Linux, S/390, iseries, pseries, zseries, and other support agreements, go to the Support Line Web site at For IBM eserver software products (including, but not limited to, DB2 and WebSphere products that run in zseries, pseries, and iseries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eserver software products, go to the IBM Technical Support Advantage Web site at If you are not sure what type of software maintenance contract you need, call IBMSERV ( ) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at Support Information 325

326 and click the name of your geographic region for phone numbers of people who provide support for your location. To contact IBM Software Support, follow these steps: 1. Determining the business impact on page Describing problems and gathering information on page Submitting problems on page 327 Determining the business impact When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria: Severity 1 Severity 2 Severity 3 Severity 4 The problem has a critical business impact. You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. The problem has a significant business impact. The program is usable, but it is severely limited. The problem has some business impact. The program is usable, but less significant features (not critical to operations) are unavailable. The problem has minimal business impact. The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented. Describing problems and gathering information When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: What software versions were you running when the problem occurred? Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. Can you re-create the problem? If so, what steps were performed to re-create the problem? Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, and so on. Are you currently using a workaround for the problem? If so, be prepared to explain the workaround when you report the problem. What software versions were you running when the problem occurred? 326 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

327 Submitting problems You can submit your problem to IBM Software Support in one of two ways: Online: Click Submit and track problems on the IBM Software Support site at Type your information into the appropriate problem submission form. By phone: For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook ( and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution. Support Information 327

328 328 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

329 X Notices Overview This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in Notices 329

330 new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any 330 IBM Tivoli Candle Products Messages: Volume 4 (KONCV to OC)

331 similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information in softcopy form, the photographs and color illustrations might not display. Trademarks IBM, the IBM logo, AF/Operator, Candle, Candle Command Center, Candle Management Server, CandleNet, CandleNet Portal, CICS, CICS/ESA, CICS/MVS, CL/SUPERSESSION, CUA, DB2, developerworks, Dexan, eserver, Epilog, ETE, Hiperspace, IBMLink, IMS, iseries, MQSeries, MVS, MVS/ESA, MVS/SP, MVS/XA, OMEGACENTER, OMEGAMON, OMEGAMON II, OMEGAVIEW, Passport Advantage, pseries, RACF, RMF, SP, Tivoli, VTAM, WebSphere, z/os, and zseries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Intel, Intel Inside (logos), MMX, Celeron, Intel Centrino, Intel Xeon, Itanium, Pentium and Pentium III Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiares in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Notices 331