OC1000 OCOMEG INQUIRE TRANSACTION FAILED WITH cccccccccc

Explanation

During OMEGAMON shutdown processing, a response of cccccccccc was returned in EIBRESP for an INQUIRE TRANSACTION command issued by KOCOME00.

System action

KOCOME00 stops processing but OMEGAMON service tasks remain active.

User response

If INQUIRE TRANSACTION failed with NOTAUTH, make sure the user who initiated the OMEGAMON or the CICS® shutdown process is also authorized to issue an INQUIRE TRANSACTION command against the transaction being entered.

OC1001 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

IBM Z 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.

OC1002 KOCOME00 PHASE 2 PLT PROCESSING IGNORED

Explanation

The KOCOME00 program could not run because it was not entered in the PLT in the correct position for phase 2 processing.

System action

The KOCOME00 program does not run.

User response

Verify that the entry for the KOCOME00 program appears in the PLT after DFHDELIM. See the IBM Z OMEGAMON for CICS Configuration and Customers Guide for more information regarding changes to the CICS PLT.

OC1003 LOAD FAILED FOR MODULE aaaaaaaa

Explanation

OMEGAMON could not load a required program from DFHRPL.

System action

OMEGAMON 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 DFHRPL.

OC1004 LINK FAILED FOR MODULE aaaaaaaa

Explanation

OMEGAMON could not find a required program from DFHRPL.

System action

OMEGAMON does not supply the response time collector, ONDV collector, or interval record collector with data.

User response

Make sure the data set containing all the modules from the distribution tape is present in DFHRPL.

OC1005 NEW VERSION OF KOCOME00 NEEDED TO SUPPORT RELEASE

Explanation

OMEGAMON found a back level version of a module.

System action

OMEGAMON does not supply the response time collector, ONDV collector, or interval record collector with data.

User response

Make sure the data set containing all the modules from the distribution tape is present in STEPLIB. Delete any modules from prior releases of OMEGAMON.

OC1006 COMMAND PROCESSING TABLE IS MISSING

Explanation

This is an internal error with Tivoli OMEGAMON.

System action

Tivoli OMEGAMON does not supply the response time collector, ONDV collector, or interval record collector with data.

User response

Contact IBM Software Support.

OC1007 DEBUG CHAIN ANCHOR IS 0

Explanation

This is an internal error with IBM Z OMEGAMON for CICS.

System action

The DEBUG command is ignored.

User response

Contact IBM Software Support.

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 Tivoli OMEGAMON.

System action

Tivoli OMEGAMON does not supply the response time collector, ONDV collector, or interval record collector with data.

User response

Contact IBM Software Support.

OC1010 KOCOME00 INCORRECTLY DEFINED AS RELOAD=YES

Explanation

The program KOCOME00 was defined as RELOAD=YES when it must be RELOAD=NO.

System action

Tivoli OMEGAMON 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.

OC1011 CICS LOAD FAILED FOR KOCOME00

Explanation

The program KOCOME00 could not be loaded from the RPL library.

System action

Tivoli OMEGAMON 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.

OC1012 AUTHORIZATION FAILED WHEN LOADING KOCOME00

Explanation

CICS prevented Tivoli OMEGAMON from loading KOCOME00.

System action

Tivoli OMEGAMON 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 IBM Z OMEGAMON for CICS Configuration and Customization Guide.

OC1013 COMMON AREA VERSION cccccccc DETECTED

Explanation

Tivoli OMEGAMON found a back level version of a module.

System action

Tivoli OMEGAMON 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 Tivoli OMEGAMON.

OC1014 BYPASS IS SET, KOCOME00 PROCESSING TERMINATING

Explanation

This is an internal error.

System action

Tivoli OMEGAMON does not supply the response time collector, ONDV collector, or interval record collector with data.

User response

Contact IBM Software Support.

OC1015 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 enter the command.

OC1016 (The text varies.)

Explanation

This is an informational message in response to a debug request.

System action

Processing continues.

User response

None.

OC1017 LINK FAILED FOR MODULE cccccccc DURING COMMAND PROCESSING

Explanation

This is an internal error.

System action

Processing continues.

User response

Contact IBM Software Support.

OC1018 INITIALIZATION HAS ALREADY COMPLETED, INIT IGNORED

Explanation

OMEG INIT was entered, but initialization was already performed.

System action

The command is ignored.

User response

None.

OC1019 Tivoli® IBM Z OMEGAMON for CICS on z/OS® INITIALIZATION COMPLETE

Explanation

The IBM Z OMEGAMON for CICS on z/OS initialization is complete.

System action

None.

User response

None.

OC1020 IBM Z OMEGAMON for CICS TERMINATION IS COMPLETE

Explanation

The IBM Z OMEGAMON for CICS termination is complete.

System action

None.

User response

None.

OC1021 MVS nnn AND CICS yyy: UNSUPPORTED ENVIRONMENT

Explanation

The versions of MVS and CICS that are currently running are displayed in this message. One version, normally CICS, is not supported by this release of IBM Z OMEGAMON for CICS.

System action

IBM Z OMEGAMON for CICS fails to initiate.

User response

See the Program Directory for IBM Z OMEGAMON for CICS for versions supported at your release level and the current Preventive Service Planning (PSP) information for versions supported in subsequent maintenance.

OC1022 IBM Z OMEGAMON for CICS SUCCESSFULLY DE-INSTALLED

Explanation

IBM Z OMEGAMON for CICS has been de installed from the CICS region.

System action

None.

User response

None.

OC1023 RKANMOD IS IN USE FOR PROGRAM LOADING

Explanation

IBM Z OMEGAMON for CICS will load its modules from the RKANMOD data set.

System action

None.

User response

None.

OC1024 IBM Z OMEGAMON for CICS TERMINATION IN PROGRESS

Explanation

IBM Z OMEGAMON for CICS termination is in progress.

System action

None.

User response

None.

OC1025 IBM Z OMEGAMON for CICS RESTART IN PROGRESS

Explanation

IBM Z OMEGAMON for CICS restart is in progress.

System action

None.

User response

None.

OC1026 IBM Z OMEGAMON for CICS INITIALIZATION IN PROGRESS

Explanation

IBM Z OMEGAMON for CICS initialization is in progress.

System action

None

User response

None.

OC1027 ALTERNATIVE TRANSACTION ID tttt WILL BE USED

Explanation

During PLTPI processing, a transaction ID of tttt, rather than the default of the OMEG transaction, was found.

System action

Processing continues. Tivoli OMEGAMON will run under the alternative transaction ID.

User response

None.

OC1028 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, Tivoli OMEGAMON processing within CICS will not start.

User response

Contact IBM Software Support.

OC1029 PCT ENTRY NOT FOUND FOR MODULE KOCOME00

Explanation

During PLTPI processing, no transaction ID that specified the KOCOME00 module 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).

OC1030 OMEG REMOVE HAS BEEN DONE, NEWCOPY KOCOME00 AND RETRY

Explanation

For CICS/MVS users only, this message indicates that IBM Z OMEGAMON 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.

OC1031 DE-INSTALL HALTED BECAUSE CROSS-MEMORY CONNECTION NOT ESTABLISHED

Explanation

IBM Z OMEGAMON for CICS de-install processing stopped. The OMEG REMOVE command 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 IBM Z OMEGAMON for CICS address space is active and OMEGAMON has been fully initialized in the CICS region before you issue the OMEG REMOVE command.

OC1032 DE-INSTALL HAS ALREADY BEEN PERFORMED; NOTHING TO REMOVE

Explanation

IBM Z OMEGAMON for CICS de-install processing has completed on prior execution of OMEG REMOVE command. However, this command was issued again, but there is nothing to de-install or remove.

System action

The command is rejected.

User response

None.

OC1033 DE-INSTALL HALTED BECAUSE OMEGAMON INITIALIZATION NOT COMPLETED

Explanation

IBM Z OMEGAMON for CICS de-install processing or OMEG REMOVE command 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 IBM Z OMEGAMON for CICS address space must be active and OMEGAMON must be fully initialized in the CICS region before de-install processing can be initiated.

OC1034 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.

System action

None.

User response

This is an informational message that only applies to CICS/ TS 2.2 with Version 520 of IBM Z OMEGAMON for CICS.

OC1035W OMEGAMON II FOR CICS CANNOT BE INITIALIZED IN A CMAS REGION.

Explanation

The OMEGAMON program, transactions, and CICS Exits cannot be initialized in a CICSPlex SM address space.

System action

The initialization of the OMEGAMON program in the CICSPlex SM address space is ignored.

User response

None.

OC1036 THE OMEGAMON IS NOT BEING LOADED FROM AN AUTHORIZED LIBRARY

Explanation

The library concatenation that OMEGAMON is being loaded from in the CICS address space is not APF authorized.

System action

OMEGAMON for CICS did not initialize in the CICS region.

User response

Verify that all the libraries in the RKANMOD concatenation are APF authorized.

OC1037 IBM Z OMEGAMON for CICS RECYCLE START FAILURE

Explanation

During the recycle processing for OMEGAMON for CICS there was a failure in starting the OMEGAMON transaction to re initialize in the CICS region.

System action

OMEGAMON for CICS did not initialize in the CICS region.

User response

Attempt to manually restart the OMEGAMON using the OMEG INIT transaction. Contact IBM Software Support.

OC1099 DEBUG LIST COMPLETE. SEE CONSOLE LOG FOR OUTPUT

Explanation

The output in response to an OMEG DEBUG command is complete.

System action

None.

User response

None.

OC1100 QRYC COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

Tivoli OMEGAMON 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.

OC1101 EVENT MONITORING POINT NOT DEFINED IN THE MCT

Explanation

An event monitoring point (EMP) was defined to Tivoli OMEGAMON in the KOCEPOPT macro in KOCGLB, but the EMP was not defined in theCICS Monitor Control Table.

System action

Tivoli OMEGAMON does not write umbrella, DL/I or DB2® data to CMF.

User response

Make sure the MCT contains the EMP definitions. See the IBM Z OMEGAMON for CICS Configuration and Customization Guide for more details.

OC1102 EXEC CICS MONITOR POINT FAILED

Explanation

An error occurred as Tivoli OMEGAMON tried to write data to CMF.

System action

Tivoli OMEGAMON 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.

OC1130 DICTIONARY ENTRY FOR RTYPE IN THE MCT IS MISSING

Explanation

Tivoli OMEGAMON could not find the field RTYPE in the CICS monitoring record.

System action

Tivoli OMEGAMON 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.

OC1131 DICTIONARY ENTRY FOR BASIC USER DATA IN THE MCT IS MISSING

Explanation

Tivoli OMEGAMON 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

Tivoli OMEGAMON 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.

OC1132 DICTIONARY ENTRY FOR DL/I USER DATA IN THE MCT IS MISSING

Explanation

Tivoli OMEGAMON 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

Tivoli OMEGAMON 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.

OC1133 DICTIONARY ENTRY FOR DB2 USER DATA IN THE MCT IS MISSING

Explanation

Tivoli OMEGAMON 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

Tivoli OMEGAMON 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.

OC1134 WORK AREA FOR TRUE IS MISSING

Explanation

Tivoli OMEGAMON could not locate the work area for its task related user exit program.

System action

Tivoli OMEGAMON does not write umbrella data, DL/I data, or DB2 data to CMF.

User response

Contact IBM Software Support.

OC1135 AUTHORIZATION FAILED FOR SMF WRITE, LOGGING STOPPED

Explanation

Tivoli OMEGAMON 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

Tivoli OMEGAMON does not log any transaction related monitoring data to SMF.

User response

Contact IBM Software Support.

OC1136 DICTIONARY ENTRY FOR WLM USER DATA IN THE MCT IS MISSING

Explanation

IBM Z OMEGAMON 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 higher only)

This message only applies if you are using the Tivoli Enterprise Monitoring Server for CICS and want to collect this data. Otherwise, you can ignore this message.

System action

IBM Z OMEGAMON 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.

OC1137 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

IBM Z OMEGAMON for CICS writes duplicate data to CMF.

User response

Choose either the OMEGBSC or selective method of collecting the data, not both.

OC1140 OCEXEN INSUFFICIENT WORK AREA FOR EXIT ENABLEMENT

Explanation

Tivoli OMEGAMON 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.

User response

Contact IBM Software Support.

OC1141 OCEXEN TRUE COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

Tivoli OMEGAMON 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.

User response

Contact IBM Software Support.

OC1142 OCEXEN GLUE COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

Tivoli OMEGAMON 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.

User response

Contact IBM Software Support.

OC1143 OCEXEN NOT AUTHORIZED FOR cccccccccccccccc

Explanation

Tivoli OMEGAMON 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)).

OC1144 OCEXEN PROCESS cccccccccccccccc ERROR nnnn

Explanation

Tivoli OMEGAMON 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.

OC1145 OCEXEN PGMIDERR DURING ccccccccccc

Explanation

Tivoli OMEGAMON encountered an error issuing an EXEC CICS command.

System action

No data is collected for the response time collector or ONDV collector.

User response

Contact IBM Software Support.

OC1146 OCEXEN QRYC COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

Tivoli OMEGAMON 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.

User response

Contact IBM Software Support.

OC1147 OCEXEN CICS MONITORING IS BEING TURNED ON

Explanation

Tivoli OMEGAMON has detected that CICS monitoring is off. Tivoli OMEGAMON 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.

User response

None.

OC1148 OCEXEN PERFORMANCE CLASS IS BEING TURNED ON

Explanation

Tivoli OMEGAMON has detected that the performance class of CICS monitoring is off. Tivoli OMEGAMON 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.

User response

None.

OC1149 OCEXEN EXIT INITIALIZATION COMPLETED

Explanation

Tivoli OMEGAMON enabled CICS exits for data collection.

System action

None.

User response

None.

OC1150 OCEXEN EXIT RESTART COMPLETED

Explanation

Tivoli OMEGAMON re-enabled CICS exits for data collection.

System action

None.

User response

None.

OC1151 INSUFFICIENT STORAGE FOR THE SMF BUFFER

Explanation

Tivoli OMEGAMON was not able to acquire a buffer of approximately 32K from CICS OSCOR less than 16M.

System action

Tivoli OMEGAMON 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.

OC1152 UNABLE TO LOCATE OCA RESOURCE MANAGER

Explanation

Tivoli OMEGAMON could not find the umbrella services exit module.

System action

Tivoli OMEGAMON for CICS initialization continues in CICS. Transactions that use umbrella services will fail with a return code of 8.

User response

Contact IBM Software Support.

OC1153 OCA RESOURCE MANAGER ERROR

Explanation

Tivoli OMEGAMON for CICS could not initialize the umbrella services exit module.

System action

Tivoli OMEGAMON for CICS initialization continues in CICS. Transactions that use umbrella services will fail with a return code of 8.

User response

Contact IBM Software Support.

OC1154 EXEN GLUE RESTART COMPLETED

Explanation

This is an informational message indicating that the Tivoli OMEGAMON global user exits have been re-enabled.

System action

None.

User response

None.

OC1155 EXEN GLUE SHUTDOWN COMPLETED

Explanation

This is an informational message indicating that the Tivoli OMEGAMON global user exits have been disabled.

System action

None.

User response

None.

OC1156 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.

OC1160 OCSETI INSUFFICIENT WORK AREA FOR OCEXEC PROCESSING

Explanation

Tivoli OMEGAMON 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.

User response

Contact IBM Software Support.

OC1161 OCSETI OCEXEC COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

Tivoli OMEGAMON could not load a program it required for monitoring CICS OCEXEC level calls.

System action

Support for database statistics and MAXR is disabled.

User response

Contact IBM Software Support.

OC1162 OCSETI VALIDATION FAILED FOR OCEXEC ENVIRONMENT

Explanation

Tivoli OMEGAMON detected that internal addresses in CICS were changed, which prevents Tivoli OMEGAMON from monitoring CICS OCEXEC level calls.

System action

Support for database statistics and MAXR is disabled.

User response

Contact IBM Software Support.

OC1163 OCSETI OCEXEC MODULE IS NOT IN LOW PRIVATE

Explanation

Tivoli OMEGAMON detected an error in loading a program required for monitoring CICS OCEXEC level calls.

System action

Support for database statistics and MAXR is disabled.

User response

Contact IBM Software Support.

OC1164 OCSETI OCEXEC INTERFACE IS NOW INSTALLED IN CICS

Explanation

Tivoli OMEGAMON installed its support for monitoring CICS OCEXEC level calls.

System action

None.

User response

None.

OC1165 OCSETI OCEXEC INTERFACE HAS BEEN DISABLED

Explanation

Tivoli OMEGAMON removed its support for monitoring CICS OCEXEC level

System action

None.

User response

None.

OC1166 OCSETI OCEXEC INTERFACE HAS BEEN RESTARTED

Explanation

Tivoli OMEGAMON restarted its support for monitoring CICS OCEXEC level calls.

System action

None.

User response

None.

OC1167 EXEC VALIDATION NOTED ALTERED CICS ENTRY

Explanation

Tivoli OMEGAMON 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.

User response

None.

OC1168 OCSETI DFHBPKOC MUST BE IN LINKLIST OR STEPLIB - PROG TRACKING DISABLED

Explanation

At CICS initialisation, CICS did not find the IBM Z OMEGAMON for CICS module DFHBPKOC.

System action

IBM Z OMEGAMON for CICS continues without the Program Tracking feature.

User response

Copy the DFHBPKOC module to a STEPLIB or LNKLST data set and restart CICS for the OMEGAMON Program Tracking feature to be available.

OC1169 EXEC VALIDATION NOTED UPDATED CICS POINTERS

Explanation

Tivoli OMEGAMON 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.

User response

None.

OC1170 STARTING IBM Z OMEGAMON for CICS OCEXEC PROCESSING

Explanation

Identifies the part of the Tivoli OMEGAMON initialization in process.

System action

Processing continues.

User response

None.

OC1171 OCSETI FEATURE NOT AVAILABLE UNTIL CICS RESTART - ffffffffffffffffffff

Explanation

IBM Z OMEGAMON for CICS feature ffffffffffffffffffff was added in maintenance, but cannot be activated until this CICS region restarts.

System action

IBM Z OMEGAMON for CICS continues without the feature.

User response

This feature will be available when this CICS region restarts.

OC1172 USER MODIFIED PCN ENTRY

Explanation

The Tivoli OMEGAMON 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.

User response

None.

OC1173 OCSETI KOCDIN COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

An internal error has occurred.

System action

IBM Z OMEGAMON for CICS will not initialize.

User response

Contact IBM Software Support.

OC1174 OCSETI KOCDBP COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

An internal error has occurred.

System action

IBM Z OMEGAMON for CICS will not initialize.

User response

Contact IBM Software Support.

OC1175 OCSETI KOCDBT COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

An internal error has occurred.

System action

IBM Z OMEGAMON for CICS will not initialize.

User response

Contact IBM Software Support.

OC1176 OCSETI xxxxxx COULD NOT BE LOCATED OR WAS NOT LOADED

Explanation

An internal error has occurred.

System action

IBM Z OMEGAMON for CICS will not initialize.

User response

Contact IBM Software Support.

OC1177 OCSETI KOCPGM INTERFACE IS NOW INSTALLED IN CICS

Explanation

IBM Z OMEGAMON for CICS installed its support for Program Tracking.

System action

None.

User response

None required.

OC1178 OCSETI KOCPGM INTERFACE HAS BEEN DISABLED

Explanation

IBM Z OMEGAMON for CICS removed its support for Program Tracking.

System action

None.

User response

None required.

OC1179 OCSETI KOCPGM INTERFACE HAS BEEN RESTARTED

Explanation

IBM Z OMEGAMON for CICS restarted its support for Program Tracking.

System action

None.

User response

None required.

OC1180 OCDBIN cccccccc IS AN UNSUPPORTED PRODUCT

Explanation

File level monitoring was specified for a product in KOCGLB that is not supported by Tivoli OMEGAMON.

System action

Tivoli OMEGAMON 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.

OC1182 OCDBIN INVALID GLOBAL EXTRACT AREA, FILE LEVEL MONITORING DISABLED

Explanation

Tivoli OMEGAMON detected an internal error in attempting to activate file level monitoring.

System action

Tivoli OMEGAMON does not monitor file usage.

User response

Contact IBM Software Support.

OC1183 IBM Z OMEGAMON for CICS COLLECTION IS NOT ACTIVE

Explanation

The data collection component of Tivoli OMEGAMON 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 Tivoli OMEGAMON is active by entering OMEG INIT as a CICS transaction or placing the program KOCOME00 in the PLT. See the IBM Z OMEGAMON for CICS Configuration and Customization Guide for more information. If this problem persists, contact IBM Software Support.

OC1184 NO STORAGE AVAILABLE, FILE LEVEL MONITORING DISABLED

Explanation

IBM Z OMEGAMON 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

IBM Z OMEGAMON 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.

OC1190 UNABLE TO OBTAIN WORK AREA FOR SYSTEM RECORDS. LENGTH=nnnnnn

Explanation

Tivoli OMEGAMON 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

Tivoli OMEGAMON 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.

OC1191 INVALID TCB ADDRESS, SYSTEM RECORDS NOT WRITTEN TO SMF

Explanation

Tivoli OMEGAMON attempted to determine the TCB under which it was running in order to write to SMF.

System action

Tivoli OMEGAMON does not write system initialization or system termination records to SMF.

User response

Contact IBM Software Support.

OC1192 AUTHORIZATION FAILED, NO SYSTEM RECORDS WRITTEN

Explanation

Tivoli OMEGAMON attempted to acquire authorization to write a system record to SMF.

System action

Tivoli OMEGAMON does not write system initialization or system termination records to SMF.

User response

Contact IBM Software Support.

OC1193 OCSYSI INVALID GLOBAL EXTRACT AREA. SYSTEM RECORD NOT WRITTEN.

Explanation

Tivoli OMEGAMON has detected an internal error when attempting to write a system record to SMF.

System action

Tivoli OMEGAMON does not write system initialization or system termination records to SMF.

User response

Contact IBM Software Support.

OC1200 ddname DD MISSING

Explanation

No ddname DD statement was found during the running of the KOCSMFDI job.

System action

Processing stops.

User response

Correct the ddname DD statement and run the KOCSMFDI job again.

OC1201 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.

User response

None.

OC1201a PRECEDING INPUT IS INVALID, PROCESSING STOPPED

Explanation

An input card was blank or contained no equal sign during execution of the KOCSMFDI job.

System action

Processing stops.

User response

Correct the input card and run the KOCSMFDI job again.

OC1202 PRECEDING INPUT HAS AN INVALID FIELD NAME, PROCESSING STOPPED

Explanation

An input card contained an invalid field name during execution of the KOCSMFDI job.

System action

Processing stops.

User response

Correct the input card and rerun the KOCSMFDI job. Valid field names are: APPLID, SYSID, DATE, TIME, and SMFID.

OC1203 INVALID VALUE FOR TIME, PROCESSING STOPPED

Explanation

An input card contained an invalid value in the TIME field during execution of the KOCSMFDI job.

System action

Processing stops.

User response

Correct the input card using a valid time (HHMMSS) and rerun the KOCSMFDI job.

OC1204 INVALID VALUE FOR DATE, PROCESSING STOPPED

Explanation

An input card contained an invalid value in the DATE field during execution of the KOCSMFDI job.

System action

Processing stops.

User response

Correct the input card using a valid date (YYDDD.) and rerun the KOCSMFDI job.

OC1208 THE SERVICE TASK IS ALREADY RUNNING, CANNOT START A NEW ONE

Explanation

OMEG SRVINIT was issued but the service task is already running.

System action

None.

User response

If you wish to re initialize the service task, issue OMEG SRVSHUT first, then OMEG SRVINIT.

OC1209 THE SERVICE TASK WAS SUCCESFULLY SHUTDOWN

Explanation

The service task shutdown process finished.

System action

None.

User response

None.

OC1210 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.

System action

None.

User response

Refer to messages KOC1217 and KOC1218.

OC1211 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.

OC1212 TEMPORARY STORAGE LIMIT (nnn) EXCEEDS AVAILABLE STORAGE

Explanation

This is an internal error.

System action

Processing stops.

User response

Contact IBM Software Support.

OC1213 SERVICE TASK INITIALIZATION COMPLETED

Explanation

Initialization of the service task is complete.

System action

None.

User response

None.

OC1214 SECONDARY TASK LIMIT (nnn) EXCEEDS AVAILABLE STORAGE

Explanation

This is an internal error.

System action

Processing stops.

User response

Contact IBM Software Support.

OC1215 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 KOCOME00 program to PUBLIC (RESSECNUM(PUBLIC)). For other values in aaaaaaaa contact IBM Software Support.

OC1216 TSBROWSE ENTRY IN SERVICE LIMITS TABLE COULD NOT BE LOCATED

Explanation

This is an internal error.

System action

Processing stops.

User response

Contact IBM Software Support.

OC1217 PURGE OF SECONDARY SERVICE TASK FAILED WITH aaaaaaaa

Explanation

The SET TASK command for one of the secondary tasks failed. The aaaaaaaa value is the exceptional condition raised for the EXEC CICS SET TASK command. This message is only applicable to CICS/ESA.

System action

Processing continues.

User response

None. Refer to the CICS/ESA System Programming Reference, command SET TASK.

OC1218 PURGE OF SERVICE TASK FAILED WITH aaaaaaaa

Explanation

The SET TASK command for the service task failed. The aaaaaaaa value is the exception condition raised for the EXEC CICS SET TASK command. This message is only applicable to CICS/ESA.

System action

Processing continues.

User response

None. Refer to the CICS/ESA System Programming Reference, command SET TASK.

OC1223 SECONDARY SERVICE TASK START aaaaaaaa FAILURE

Explanation

CICS returned the aaaaaaaa value 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 KOCOME00 program to PUBLIC (RESSECNUM(PUBLIC)). For any other value of aaaaaaaa, contact IBM Software Support.

OC1224 FIRST SECONDARY SERVICE TASK FAILED TO INITIALIZE

Explanation

The service task started a secondary task which failed to respond.

System action

Processing continues.

User response

None.

OC1225 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.

OC1226 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.

OC1227 UNABLE TO SETUP PARAMETERS FOR THE SECONDARY TASK

Explanation

This is an internal error.

System action

Processing stops.

User response

Contact IBM Software Support.

OC1228 FIRST SECONDARY SERVICE TASK ABENDED

Explanation

The first secondary task started by the service task abended.

System action

Processing continues.

User response

None.

OC1229 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

Please refer to the IBM Z OMEGAMON for CICS Configuration and Customization Guide for an explanation of the return code and contact IBM Software Support.

OC1230 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.

OC1231 OCSRV SERVICE TASK WAITING FOR WORK

Explanation

The service task has initialized successfully and is waiting for work. This is an informational message only.

System action

None.

User response

None.

OC1240 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.

OC1241 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.

User response

None.

OC1242 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.

System action

None.

User response

None.

OC1243 OCSR2 SMF DATA COLLECTION QUIESCED

Explanation

This is an informational message. For CICS/MVS users it indicates that Tivoli OMEGAMON will no longer write SMF records. For CICS/ESA users it indicates that CICS will no longer write SMF records.

System action

None.

User response

None.

OC1244 OCSR2 SMF DATA COLLECTION INITIATED

Explanation

This is an informational message. For CICS/MVS users it indicates that Tivoli OMEGAMON will start writing SMF records. For CICS/ESA users it indicates that CICS will start writing SMF records.

System action

None.

User response

None.

OC1245 OCSR2 CICS MONITORING TURNED OFF

Explanation

This is an informational message indicating that CICS performance monitoring has been turned off.

System action

None.

User response

None.

OC1246 OCSR2 CICS MONITORING TURNED ON

Explanation

This is an informational message indicating that CICS global and performance monitoring have been turned on.

System action

None.

User response

None.

OC1247 RECYCLE TASK START aaaa FAILURE

Explanation

CICS returned a abend code of aaaa when OMEGAMON for CICS attempted to start a transaction to recycle OMEGAMON in the CICS region.

System action

The recycle of OMEGAMON in the CICS region did not occur.

User response

Investigate the possible cause of the abend codeaaaa and contact IBM Software Support.

OC1401 SHOULD IBM Z OMEGAMON 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 Tivoli OMEGAMON 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 stops immediately. The rest of Tivoli OMEGAMON PLTSD processing continues. If you specify YES, the processing operates as though you had specified SHUTOPT=PURGE; all tasks waiting for terminal I/O are purged.

OC1402 IBM Z OMEGAMON for CICS HAS PURGED nnnn TASKS

Explanation

After completing the SHUTOPT=PURGE cycle (or after a user reply of YES to message 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 3.1.1 and higher, this is the number of tasks canceled and CICS return codes indicated success.

System action

SHUTOPT processing ends. OMEGAMON processing continues.

User response

None.

OC1403 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. Tivoli OMEGAMON PLT shutdown processing does not continue.

User response

Contact IBM Software Support.

OC1404 OCSHUT INSUFFICIENT WORK AREA FOR TASK PURGE

Explanation

The Tivoli OMEGAMON PLT shutdown program could not purge tasks due to an insufficient work area.

System action

The Tivoli OMEGAMON PLT shutdown program stops without purging all tasks waiting for terminal input.

User response

Contact IBM Software Support.

OC1405 START OF SHUTOPT=PURGE PROCESSING

Explanation

CICS termination has been detected. Your GLOBAL assembly has requested Tivoli OMEGAMON to purge all tasks waiting in terminal control program.

System action

Task purging immediately follows. Message OC1402 follows the purge process.

User response

None.

OC1406 START OF SHUTOPT=OPER PROCESSING

Explanation

CICS termination has been detected. Your GLOBAL assembly has requested Tivoli OMEGAMON to check for tasks waiting in terminal control. If any are found, confirm permission to cancel the tasks (message OC1401).

System action

Tivoli OMEGAMON waits for response to message OC1401.

User response

None.

OC2001 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 enter the ENQ command.

OC2002 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 enter the ENQ command.

OC2003 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 enter the ENQ command.

OC2004 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 enter the ENQ command.

OC2005 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 stops processing.

User response

None.

OC2020I xxxxx yyy GLUE CODE HAS BEEN ENABLED

Explanation

OMEGAMON for CICS has enabled or disabled it GLUE code for the feature yyy, where yyy can be ATF, MQ or DLI. xxxxx will be set to EXEN or OCSR2, depending on the module which has issued the request.

System action

The messages are informational and may be used to verify which exits are affected by the command(s) that you have issued.

The GLUE code will run at the following exit points:
  • ATF uses XRMIOUT and XPCABND
  • MQ uses XRMIOUT
  • DLI uses XDLIPRE and XDLIPOST

Additional Documentation: You can now control which GLUEs are enabled (or disabled) in a monitored CICS region by choosing the appropriate values in your global source, or issuing the equivalent online commands. Be aware that the exit code running at XEIOUT and XMNOUT is essential to the operation of OMEGAMON for CICS so these exits will not be disabled unless an OMEG SHUT / REMOVE command is issued.

In the DATABASE_COLLECTION section coding

<<MQ>>
AUTO_START=NO
will not enable the GLUE code at XDLIPRE
<<DLI>>
AUTO_START=NO
will not enable the GLUE code at XDLIPRE or XDLIPOST. In addition you must also code the parameter,
DLI_CLOCKS_AND_COUNTERS=NO
to ensure that the DLI exits are not enabled.
<<TRACE>>
AUTO_START=NO
If you do not use the Application Trace Facility, ATF, you will not enable code at XPCABND or XRMIOUT (although XRMIOUT code will be active if you enable the MQ clocks and counters.)

Excluding the entries is equivalent to coding AUTO_START=NO in the Global Data Area.

You can use the OMEGAMON for CICS (3270) command COLL (fastpath= O.P) to turn the collection on or off, and the exits will be turned on or off accordingly.

The OMEGAMON File/Database collection and Application Trace Facility panels can also be used to control the data collection. The exits will be enabled or disabled as appropriate.

The OOMEGAMON for CICS (3270) command EXIT (fastpath=CI) will display the exits that are currently active.

The OMEGAMON Global User Exits panel (fastpath=CE) will display the exits that are enabled in CICS.

In summary you can now expect to see GLUE code at the following exit points activated.

Exit Point Name      DLI=  MQ=  ATF=
                      YES   YES   YES
XMNOUT                 Y     Y     Y
XEIOUT                 Y     Y     Y
As mentioned earlier, XMNOUT and XEIOUT will be activated when an OMEG INIT transaction is run, or the KOCOME00 program executes in the PLT
XRMIOUT                N     Y    Y
XPCABND                N     N    N
XDLIPRE                Y     N    N
XDLIPOST               Y     N    N
In a CICS region with DLI, MQ and ATF active you can expect to see all of the exit points active whereas a region with only DB2 (no DLI, no MQ, and no ATF) would only have XMNOUT and XEIOUT active.

The OMEGAMON for CICS (3270) COLL command can display one of the following messages, if a non zero return code is received during an attempt to enable or disable an exit:

ENABLE EXIT REQUEST EIBRCODE 808000
ENABLE EXIT REQUEST EIBRCODE 804000
ENABLE EXIT REQUEST EIBRCODE 802000
ENABLE EXIT REQUEST EIBRCODE 801000
ENABLE EXIT REQUEST EIBRCODE 800800
ENABLE EXIT REQUEST EIBRCODE 800400
DISABLE EXIT REQUEST EIBRCODE 808000
DISABLE EXIT REQUEST EIBRCODE 804000
DISABLE EXIT REQUEST EIBRCODE 802000
DISABLE EXIT REQUEST EIBRCODE 801000
DISABLE EXIT REQUEST EIBRCODE 800800
The EIBRCODES are documented in the CICS System Programming Reference under ENABLE PROGRAM and DISABLE PROGRAM. If you receive any of these messages you should determine the cause of the error using the CICS documentation and correct the error before reissuing the command.

User response

None.

OC2021I OCSR2 yyy GLUE CODE HAS BEEN DISABLED

Explanation

OMEGAMON for CICS has enabled or disabled it GLUE code for the feature yyy, where yyy can be ATF, MQ or DLI. xxxxx will be set to EXEN or OCSR2, depending on the module which has issued the request.

System action

The messages are informational and may be used to verify which exits are affected by the command(s) that you have issued.

The GLUE code will run at the following exit points:
  • ATF uses XRMIOUT and XPCABND
  • MQ uses XRMIOUT
  • DLI uses XDLIPRE and XDLIPOST

Additional Documentation: You can now control which GLUEs are enabled (or disabled) in a monitored CICS region by choosing the appropriate values in your global source, or issuing the equivalent online commands. Be aware that the exit code running at XEIOUT and XMNOUT is essential to the operation of OMEGAMON for CICS so these exits will not be disabled unless an OMEG SHUT / REMOVE command is issued.

In the DATABASE_COLLECTION section coding:

<<MQ>>
AUTO_START=NO
will not enable the GLUE code at XDLIPRE
<<DLI>>
AUTO_START=NO
will not enable the GLUE code at XDLIPRE or XDLIPOST. In addition you must also code the parameter,
DLI_CLOCKS_AND_COUNTERS=NO
to ensure that the DLI exits are not enabled.
<<TRACE>>
AUTO_START=NO
If you do not use the Application Trace Facility, ATF, you will not enable code at XPCABND or XRMIOUT (although XRMIOUT code will be active if you enable the MQ clocks and counters.)

Excluding the entries is equivalent to coding AUTO_START=NO in the Global Data Area.

You can use the OMEGAMON for CICS (3270) command COLL (fastpath= O.P) to turn the collection on or off, and the exits will be turned on or off accordingly.

The OMEGAMON File/Database collection and Application Trace Facility panels can also be used to control the data collection. The exits will be enabled or disabled as appropriate.

The OMEGAMON Global User Exits panel (fastpath=CE) will display the exits that are enabled in CICS.

In summary you can now expect to see GLUE code at the following exit points activated.

Exit Point Name       DLI=  MQ=  ATF=
                      YES   YES   YES
XMNOUT                 Y     Y     Y
XEIOUT                 Y     Y     Y
As mentioned earlier, XMNOUT and XEIOUT will be activated when an OMEG INIT transaction is run, or the KOCOME00 program executes in the PLT
XRMIOUT                N     Y    Y
XPCABND                N     N    N
XDLIPRE                Y     N    N
XDLIPOST               Y     N    N
In a CICS region with DLI, MQ and ATF active you can expect to see all of the exit points active whereas a region with only DB2 (no DLI, no MQ, and no ATF) would only have XMNOUT and XEIOUT active.

The OMEGAMON for CICS (3270) COLL command may display one of the following messages, if a non-zero return code is received during an attempt to enable or disable an exit:

ENABLE EXIT REQUEST EIBRCODE 808000
ENABLE EXIT REQUEST EIBRCODE 804000
ENABLE EXIT REQUEST EIBRCODE 802000
ENABLE EXIT REQUEST EIBRCODE 801000
ENABLE EXIT REQUEST EIBRCODE 800800
ENABLE EXIT REQUEST EIBRCODE 800400
DISABLE EXIT REQUEST EIBRCODE 808000
DISABLE EXIT REQUEST EIBRCODE 804000
DISABLE EXIT REQUEST EIBRCODE 802000
DISABLE EXIT REQUEST EIBRCODE 801000
DISABLE EXIT REQUEST EIBRCODE 800800
The EIBRCODES are documented in the CICS System Programming Reference under ENABLE PROGRAM and DISABLE PROGRAM. If you receive any of these messages you should determine the cause of the error using the CICS documentation and correct the error before reissuing the command.

User response

None.

OC2022I xxxxx Unable to activate ATF due to KOCCI level

Explanation

OMEGAMON for CICS was unable to activate Application trace in this CICS region due to the OMEGAMON KOCCI address space not having the required maintenance to process the produced trace. xxxxx will be set to EXEN or OCSR2, depending on the module which has issued the request.

System action

Processing continues. Application trace is not enabled.

User response

Ensure the KOCCI address space has the same level of maintenance as the CICS region for OMEGAMON CICS.

OC2023I OCSR2 Unable to enable Program Tracking because DFHBPKOC was not found

Explanation

OMEGAMON for CICS was unable to activate Program Tracking in this CICS region because DFHBPKOC was not available at CICS initialization.

System action

Processing continues. Program Tracking is not enabled.

User response

Copy the DFHBPKOC module to a STEPLIB or LNKLST data set and restart CICS for the OMEGAMON Program Tracking feature to be available.

OC2024I OCSR2 Program Tracking has been enabled

Explanation

OMEGAMON for CICS enabled Program Tracking.

System action

Processing continues. Program Tracking is enabled.

User response

None

OC2025I OCSR2 Program Tracking has been disabled

Explanation

OMEGAMON for CICS disabled Program Tracking.

System action

Processing continues. Program Tracking is disabled.

User response

None

OC2051 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 enter the STOR command.

OC2053 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 enter the STOR GROUP command.

OC2054 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 enter the STOR PAMDSA or PAMEDSA command.

OC2055 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 enter the STOR PAMDSA or PAMEDSA command.

OC2060 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 enter the STOR PAMDSA or PAMEDSA command.

OC2071 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 stops processing.

User response

Verify the input keywords for the current CICS release.

OC2072 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 stops processing.

User response

Investigate why CICS is not being dispatched. If CICS is being dispatched, contact IBM Software Support.

OC2073 PROGRAM COMPRESSION DATA NOT AVAILABLE, ISSUE OMEG INIT

Explanation

Display of program compressions using the STOR command with the COMPRESSIONS keyword requires that Tivoli OMEGAMON be initialized in the CICS region being monitored.

System action

The command fails.

User response

Issue an OMEG INIT in the required CICS region.

OC2074 PROGRAM COMPRESSION ACCESS ERROR

Explanation

Display of program compressions using the STOR command with the COMPRESSIONS keyword has failed to locate a required Tivoli OMEGAMON control block (SVCOM) in the CICS region.

System action

The command fails.

User response

Contact IBM Software Support.

OC2200 INVALID CALL TYPE

Explanation

An invalid call has been generated by the RLMU command processor.

System action

The call is rejected.

User response

Contact IBM Software Support.

OC2201 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.

User response

None.

OC2202 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.

OC2203 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.

OC2204 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.

User response

Contact IBM Software Support.

OC2205 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.

OC2206 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.

OC2207 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.

OC2208 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.

OC2209 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.

User response

Contact IBM Software Support.

OC2210 RESOURCE LIMITS REFRESHED

Explanation

An RLMU command has successfully executed.

System action

None.

User response

None.

OC2220 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.

OC2221 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.

OC2222 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.

OC2223 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.

OC2224 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.

OC2225 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.

OC2226 INTERVAL ERROR - USE TIME=nnnnnnnn IN SECONDS

Explanation

The RLMU INT,TIME= command was entered without a valid interval.

System action

The command will be rejected.

User response

Follow the TIME=keyword with the number of seconds (1 through 604800).

OC2227 INTERVAL ERROR - USE EXEC=nnnnnnnn AND/OR NDB=nnnnnnnn

Explanation

The RLMU INT,EDXEC= or RLMU INT,NDB= or RLMU INT,EXEC=nnnnnnnn,NDB=nnnnnnnn command was entered without a valid number for EXEC and/or NDB.

System action

The command will be rejected.

User response

Follow the EXEC= and NDB= keywords with a number from 1 to 99999999.

OC2228 INTERVAL ERROR - MAXIMUM TIME VALUE IS 604800 SECONDS

Explanation

The RLMU INT,TIME= command was entered with a value greater than 604800.

System action

The command will be rejected.

User response

Specify a value of 9 through 604800.

OC2229 INTERVAL ERROR - MAXIMUM NUMBER OF EXEC/NBD is 99999999

Explanation

The RLMU INT,EXEC= or RLMU INT,NDB= or RLMU INT,EXEC=nnnnnnnn,NDB=nnnnnnnncommand was entered with a value greater than 99999999.

System action

The command will be rejected.

User response

Correct the value and reenter.

OC2300 CEMT COMMAND SUCCESSFULLY EXECUTED

Explanation

This message is in response to a CMT SET command.

System action

The CICS value was successfully set.

User response

None.

OC3001 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 enter the OPT command.

OC3002 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 Tivoli OMEGAMON has been initialized in CICS.

System action

The OPT command fails.

User response

Issue the OMEG INIT transaction to initialize Tivoli OMEGAMON in CICS.

OC3003 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.

User response

Contact IBM Software Support.

OC3051 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.

User response

Contact IBM Software Support.

OC3052 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.

User response

Contact IBM Software Support.

OC3053 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 enter the SIT command.

OC3054 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.

OC3401 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 enter the AIDS command.

OC3402 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.

OC3403 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.

OC3404 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.

OC3405 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.

OC3406 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.

OC3407 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.

OC3411 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 enter the ICES command.

OC3412 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.

OC3413 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.

OC3414 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.

OC3415 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.

User response

None.

OC3416 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.

User response

None.

OC3417 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.

User response

None.

OC3420 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 enter the command.

OC3422 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.

User response

None.

OC3423 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.

User response

None.

OC3430 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 enter the command.

OC3432 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 de chained 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.

User response

None.

OC3433 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.

User response

None.

OC3434 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:

Table 1. The possible values for the service task that was not able to perform the service.
Value Description
00000001 10 secondary tasks are already started. No more are allowed.
00000002 Invalid request (internal error).
00000003 The secondary task is not responding.
00000004 The secondary task abended.
00000005 A new secondary task was started during the last second.
00000006 No room is available in the secondary tasks table.
0000000b Unable to start a new secondary task.
0000000c Unable to start a new secondary task due to MXT or AMXT.
00000042 The service task could not find the AID to be killed.
00000043 A task was already started for the AID to be killed.
00000044 The AID was unchained, but its storage could not be freed.
00000045 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.
00000046 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.
00000047 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.
000000F0 The service task is not responding. The AID is not killed.
000000F1 There are no available work elements to use for this request. The AID is not killed.
000000F2 The service task is not available. The AID is not killed.
000000F3 The service task work area could not be found. The AID is not killed.
000000F4 OMEG INIT was not issued. The AID is not killed.

System action

None.

User response

Action:

Table 2. User Actions
Value Description
00000001 Retry the command later.
00000002 Contact IBM Software Support.
00000003 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.
00000004 Issue OMEG SRVSHUT to finish the service task processing. Then, issue OMEG SRVINIT to initialize it and reenter the command.
00000005 Retry the command later.
00000006 Contact IBM Software Support.
0000000b Contact IBM Software Support.
0000000c Increase the MXT and AMXT SIT values.
00000042 Correct the AID address entered with the command and reenter the command.
00000043 None.
00000044 None.
00000045 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.
00000046 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.
00000047 Due to CICS activity, data for the AID has changed. Verify that the AID with the REQID exists and reenter the command.
000000F0 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.
000000F1 Issue the OMEG SRVSHUT transaction, then OMEG SRVINIT to reinitialize the service task.
000000F2 Issue the OMEG SRVINIT transaction to initialize the service task.
000000F3 Issue the OMEG SRVSHUT transaction, then OMEG SRVINIT to reinitialize the service task.
000000F4 Ensure that transaction OMEG and program KOCOME00 are defined to CICS and that transaction OMEG has been successfully executed in CICS.

OC3460 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 stops processing.

User response

Specify a valid User TCA address for the task you are inquiring about if the transaction has not yet ended.

OC3461 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 stops processing.

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.

OC3462 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.

OC3463 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.

OC3464 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.

OC3500 TABL Invalided ENTRY SUPPLIED

Explanation

The entry name/number specified for the table identified by aaa.

System action

The command stops processing.

User response

Correct the table entry name/number and enter the command.

OC3501 TABL ENTRY CONFLICTS WITH CICS TABLE SPECIFIED

Explanation

The table name is incompatible with the entry name specified.

System action

The command stops processing.

User response

Use the proper entry name/number keyword for the desired file, or use the generic ID= keyword operand to specify an entry.

OC3502 TABL INVALID SELECTION OPTION SPECIFIED

Explanation

The selection criteria specified are unsupported.

System action

The command stops processing.

User response

Correct the arguments of the SELECT= keyword and enter the command.

OC3503 TABL SELECTION INVALID FOR CICS TABLE SPECIFIED

Explanation

The selection criteria specified are not compatible with the table name entered.

System action

The command stops processing.

User response

Correct the arguments of the SELECT= keyword and enter the command.

OC3504 TABL SELECTION CRITERIA INVALID WITH SPECIFIC ENTRY

Explanation

Selection criteria and a specific entry name/number were specified as operands of the TABL command.

System action

The command stops processing.

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.

OC3505 TABL DISPLAY OPTIONS ONLY VALID FOR SINGLE TABLE ENTRY

Explanation

The DUMP option was specified for a generic table search.

System action

The command stops processing.

User response

Limit the table search to a specific entry or remove the DUMP operand from the TABL command.

OC4001 GRPS INVALID GROUP KEYWORD SPECIFIED, RE-ENTER

Explanation

The command encountered an invalid keyword.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4002 GRPS EXCESS KEYWORDS IGNORED

Explanation

Extra keywords were specified in the GRPS command.

System action

The command ignores the additional keywords.

User response

None.

OC4003 GRPS KEYWORD SPECIFIED WITHOUT ARGUMENT

Explanation

A parameter is missing for a keyword on the GRPS command.

System action

The command stops processing.

User response

Correct the input, and enter the command.

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.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4005 GRPS GROUP NUMBER WAS NOT SUPPLIED

Explanation

The GRPS command expects a group identifier but finds none.

System action

The command stops processing.

User response

Correct the input, and 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=).

System action

The command stops processing.

User response

Correct the input, and 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.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4008 GRPS INVALID GROUP TYPE. SPECIFY TRAN, PROG OR TERM

Explanation

The GRPS command specified an unrecognized group type.

System action

The command stops processing.

User response

Correct the input, and 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.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4010 GRPS INVALID ELEMENTS SPECIFIED

Explanation

The group elements were improperly formatted or have an invalid length.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4011 GRPS NO GROUPS DEFINED

Explanation

There are no groups currently defined to Tivoli OMEGAMON.

System action

None.

User response

None.

OC4012 GRPS REQUESTED GROUP WAS NOT FOUND

Explanation

The specified group does not exist.

System action

None.

User response

None.

OC4013 GRPS REQUESTED GROUP HAS NO ELEMENTS DEFINED

Explanation

The specified group is empty.

System action

None.

User response

None.

OC4014 GRPS GROUP IS NOT DEFINED

Explanation

The specified group is not currently defined to Tivoli OMEGAMON.

System action

None.

User response

None.

OC4015 GRPS GROUP IS ALREADY DEFINED

Explanation

An attempt was made to add a group that already exists.

System action

The command stops processing.

User response

Specify a group that is not already created.

OC4016 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 enter the GRPS command, followed by the RTA START command, to reactivate the response time collector

OC4017 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.

OC4020 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.

User response

None.

OC4021 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.

User response

None.

OC4023 GRPS INVALID CRITICAL THRESHOLD SPECIFIED, RE-ENTER

Explanation

The interval record collector (critical) threshold specified is not valid.

System action

The command stops processing.

User response

Correct the threshold, and enter the command.

OC4024 GRPS INVALID RESPONSE THRESHOLD SPECIFIED, RE-ENTER

Explanation

The response time threshold specified is not valid.

System action

The command stops processing.

User response

Correct the threshold, and enter the command.

OC4026 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.

System action

None.

User response

None.

OC4027 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.

System action

None.

User response

None.

OC4030 GRPS INVALID ADD, ELEMENTS ALREADY DEFINED IN GROUP

Explanation

The specified group already contains the element being added.

System action

The request is ignored.

User response

None.

OC4031 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.

System action

The command stops processing.

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.

OC4040 GRPS GROUP=* IS INVALID ON UPDATE

Explanation

A generic group identifier may not be used when performing an update.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4041 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.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4042 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.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4043 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.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4044 GRPS THRESHOLD MUST BE SUPPLIED WHEN UPDATING ELEMENTS

Explanation

A request to update one or more group elements did not include a threshold value.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4045 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 issue the command again.

OC4050 GRPS INVALID DELETE, NO ELEMENTS SPECIFIED

Explanation

The elements to be deleted by GRPS were not specified.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4051 GRPS INVALID DELETE, ELEMENTS NOT DEFINED IN GROUP

Explanation

The elements to be deleted by GRPS do not belong to the group specified.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4060 GRPS GROUP=* IN INVALID ON CLEARANCE

Explanation

A generic group identifier may not be used when performing a clear operation.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4061 GRPS ELEMENT LIST IS INVALID ON CLEARANCE

Explanation

An element list may not be specified when performing a clear. Clear will remove ll elements from a given group. Use the DEL operand of GRPS to selectively remove entries from a group.

System action

The command stops processing.

User response

Correct the input, and enter the command.

OC4101 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 enter the command. Use the help facility to determine valid keywords.

OC4102 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 enter the command.

OC4103 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 enter the command again.

OC4104 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 enter the command again.

OC4105 INVALID HEXADECIMAL VALUE, RENTER

Explanation

An invalid hexadecimal value was detected where a hexadecimal value is expected.

System action

The command stops processing.

User response

Reenter the command using an even number of characters 0-9 or A-F.

OC4106 ID PARAMETER NOT SPECIFIED

Explanation

The TSQD detected that the required ID parameter was not specified.

System action

The command stops processing.

User response

Reenter the command specifying the ID parameter.

OC4107 TSMODEL NOT FOUND

Explanation

The TSMD was entered with MODEL=xxxxxxxx parameter specified. The specified Temporary Storage model was not detected in the CICS region.

System action

The command stops processing.

User response

Reenter the command specifying a model that exists in CICS.

OC4108 MISSING KEYWORD. SPECIFY QUEUE=NAME,OWNER or WAITER

Explanation

The TSWD was entered without one of the required parameters.

System action

The command stops processing.

User response

Reenter the command specifying one of the required parameters. Enter a slash / before the command to obtain detailed help.

OC4109 REQUESTED QUEUE OWNER OR WAITER NOT FOUND

Explanation

The TSWD was could not detect any owner or waiter for the specified Temporary Storage queue. This could be either the queue does not exist or because no owner or waiter could be located.

System action

The command stops processing.

User response

None.

OC4151 INVALID KEYWORD SPECIFIED, RE-ENTER

Explanation

The RESP command has been entered with an invalid keyword.

System action

The command fails.

User response

Correct the keyword and enter the command. Use the help facility to determine valid keywords.

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 enter the command again.

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 enter the command again.

OC4200 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.

User response

Contact IBM Software Support.

OC4210 INVALID INTERNAL SPECIFIED. MUST BE 1 TO 60

Explanation

The DUMP command detected that the INTERVAL=parameter was specified with a value that was outside the acceptable range.

System action

The command stops processing.

User response

Enter the command again and specify an interval value between 1 and 60..

OC4221 Invalid control block structure detected

Explanation

IBM Z OMEGAMON for CICS is unable to process the MQ control blocks detected in CICS.

System action

The command stops processing normally after issuing this error message.

User response

Contact IBM Software Support for assistance with this problem.

OC4222 Unknown version of MQ detected

Explanation

The version/release of MQ you executing is not supported by OMEGAMON for CICS.

System action

The command stops processing normally after issuing this error message.

User response

Contact IBM Software Support for assistance with this problem.

OC4230 Subroutine IGGCSI00 was not loaded at startup

Explanation

IBM Z OMEGAMON for CICS uses the IBM subroutine IGGCSI00 to collect VSAM details. The subroutine is loaded during OMEGAMON startup.

System action

None.

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.

OC4231 FCT error received from IGGCSI00: RC=04, Reason code=xxxx

Explanation

IBM Z OMEGAMON for CICS uses the IBM subroutine IGGCSI00 to collect VSAM details. The subroutine returned a response code 4, with the specified reason code.

System action

None.

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.

OC4232 FCT error received from IGGCSI00: RC=08, Reason code=xxxx

Explanation

IBM Z OMEGAMON for CICS uses the IBM IGGCSI00 subroutine to collect VSAM details. The subroutine returned a response code 8, with the specified reason code.

System action

None.

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.

OC4233 FCT error received from IGGCSI00: RC=xx

Explanation

IBM Z OMEGAMON for CICS uses the IBM IGGCSI00 subroutine to collect VSAM details. The subroutine returned a response code 12 or 16.

System action

None.

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.

OC4401 THE DISPATCHER SUBTASK ANCHOR WAS NOT LOCATED

Explanation

The DB2 command was unable to locate the CICS Dispatcher Anchor block; this indicates an internal OMEGAMON error.

System action

The command stops processing.

User response

Contact IBM Software Support.

OC4402 NO CICS TCBS MEET THE SELECTION CRITERIA

Explanation

The DB2 command was entered with the SEL=TCBS parameter. OMEGAMON was unable to locate any DB2 TCBs in this CICS region.

System action

The command stops processing.

User response

Use this command only on CICS regions that have active DB2 TCBs.

OC5000 UNABLE TO OBTAIN WORK AREA STORAGE

Explanation

Insufficient storage was available to allocate a work area.

System action

The Global Maintenance Program stops processing.

User response

Increase the region size of the job used to run the Global Maintenance Program.

OC5001 UNABLE TO OPEN DATASET WITH DDNAME= aaaaaaaa

Explanation

A nonzero 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 is used. All other functions stop without further processing.

User response

Verify that the KOC2GLBL ddname is properly specified in the JCL.

OC5002 GMP WILDCARDS ONLY ALLOWED WITH VERIFY, REFORMAT, AND NOREFORMAT 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 is used. All other functions stop without further processing.

User response

Remove the wildcard character from the global module suffix.

OC5003 UNABLE TO OBTAIN GLOBAL I/O BUFFERS, LENGTH= aaaaaaaa

Explanation

Insufficient storage was available less than 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 is used. All other functions stop without further processing.

User response

Increase the region size available to the Global Maintenance Program.

OC5004 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.

OC5005 GMP FUNCTION CODE IS NOT T, V, N, R, OR S

Explanation

When the Global Maintenance Program is run as a batch job, only five function codes are permitted to either test (T), verify without reformatting (V), verify without reformatting (N), verify with reformatting (R), or build sample default global source members (S).

System action

The request is ignored.

User response

Correct the function code on the EXEC card and rerun the job.

OC5006 RKC2GLBL DATASET NOT ALLOCATED WITH LRECL=80

Explanation

The RKC2GLBL ddname 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 is used. All other functions stops without further processing.

User response

Allocate the RKC2GLBL dataset with an LRECL of 80 bytes.

OC5007 CLOSE MACRO FAILED FOR DDNAME aaaaaaaa

Explanation

The ddname identified by aaaaaaaa could not be closed.

System action

For a read request, the default copy of the global module is used. All other functions stop without further processing.

User response

Check the operator console for messages that may indicate why the dataset failed to close properly.

OC5008 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 is used. All other functions stop without further processing.

User response

Look up the ESTAE return code in the IBM Application Development Macro Reference manual, correct the problem and submit the job again.

OC5009 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 stops processing. 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 submit the job again.

OC5010 PROCESSING SUCCESSFUL FOR GLOBAL aaaaaaaa

Explanation

The global module identified by aaaaaaaa was processed without error.

System action

None.

User response

None.

OC5011 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.

OC5012 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 is available on a failed read request, change the job to run with APF authorization.

OC5013 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 is used; no other global request functions are honored.

User response

Refer to the IBM System Codes manual for a description of the ABEND code identified by the Sxxx value. Correct the cause of the error and retry the request.

OC5014 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.

OC5020 GVR CARD 0255: GROUP_TYPE=LU

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 is returned to the caller. All other functions 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.

OC5021 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 is returned to the caller. All other functions fail to complete successfully.

User response

Specify a valid CONVERSE_TIME operand.

OC5022 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 is returned to the caller. All other functions 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.

OC5023 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 is returned to the caller. All other functions 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.

OC5024 UNABLE TO LOCATE GLOBAL SOURCE MEMBER aaaaaaaa

Explanation

The FIND macro could not locate the global member denoted by the aaaaaaaa value.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Verify that the specified global member appears in the partitioned dataset pointed to by the RKC2GLBL DD statement.

OC5025 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 is returned to the caller. All other functions fail to complete successfully.

User response

Increase the region size available to the job.

OC5026 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 is returned to the caller. All other functions 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. Verify that a component heading precedes the control card in error and retry the request.

OC5027 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 is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that the component heading is bracketed by < > characters.

OC5028 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 is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that the component heading is properly specified.

OC5029 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 is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that an equals sign is used to delimit a control keyword.

OC5030 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 is returned to the caller. All other functions 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.

OC5031 SYNTAX ERROR DETECTED IN SUB-COMPONENT STATEMENT

Explanation

A subcomponent was indicated by the presence of ’<<’ characters in the first non-blank positions of the control card. No trailing ’>>’ characters were found for the subcomponent.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that subcomponents are enclosed in << >> characters.

OC5032 SUB-COMPONENT STATEMENT NOT RECOGNIZED

Explanation

A subcomponent, 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 is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that the subcomponent reflects a valid name, and that it appears under the proper component heading.

OC5033 INVALID CONTROL STATEMENT OPERAND

Explanation

Either the control statement operand is not the correct style, or it begins with a parenthesis character ’(’ to indicate a sub list, but does not end with a corresponding parenthesis ’)’ sub list trailer.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that the operand is completed with either a blank, or in the case of a sub list, a trailing ' ) ' parenthesis.

OC5034 UNABLE TO CLOSE RKC2GLBL DATASET

Explanation

The CLOSE macro used to release access to the KOC2GLBL data set 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 data set could not be closed. Correct the error and retry the request.

OC5035 NUMERIC OPERAND NOT WITHIN RANGE aabb

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.

OC5036 SYNTAX ERROR DETECTED IN SUBLIST

Explanation

A sub list 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 is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that the sub list is delimited by a single set of parentheses and that no null values are specified.

OC5037 SHUT_OPTIONS MUST BE PURGE/NOPURGE/OPER

Explanation

The SHUT_OPTIONS keyword specifies an operand that is not valid option.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Change the operand to a valid option.

OC5038 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 is returned to the caller. All other functions fail to complete successfully.

User response

Change the operand to a valid option.

OC5039 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.

OC5040 CPU_THRESHOLDING MUST BE ENABLE/DISABLE/AUTO

Explanation

CPU_THRESHOLDING does not specify a valid operand option.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Change the operand to a valid option.

OC5041 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 is returned to the caller. All other functions fail to complete successfully.

User response

Change the operand to a valid option.

OC5043 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.

OC5044 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 is returned to the caller. All other functions fail to complete successfully.

User response

Specify an entry name that is not greater than eight bytes in length.

OC5045 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 is returned to the caller. All other functions fail to complete successfully.

User response

Specify a valid global user exit name.

OC5046 EXCLUDE LIST EXCEEDS 63 TRANSACTION IDS

Explanation

The sub list 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 is returned to the caller. All other functions fail to complete successfully.

User response

Reduce the number of IDs to 63 or less.

OC5047 NO <<GROUP>> SUB-COMPONENT HEADER ACTIVE

Explanation

Control cards that define an OMEGAMON group were found without a corresponding <<GROUP>> subcomponent header.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Include a <<GROUP>> subcomponent header to properly isolate the different group definitions.

OC5048 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 is returned to the caller. All other functions fail to complete successfully.

User response

Reduce the length of the group name to 12 bytes or less.

OC5049 DUPLICATE GROUP_NAME DETECTED

Explanation

The group name is not unique.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Select a group name that has not already been defined.

OC5050 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 is returned to the caller. All other functions fail to complete successfully.

User response

Begin the group name with a non-blank character.

OC5051 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.

OC5052 GROUP TYPE IS NOT TRAN, TERM, PROG, OR LU

Explanation

The group type keyword specifies an operand that is not valid.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Choose one of the four valid group types.

OC5053 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.

OC5054 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 is returned to the caller. All other functions fail to complete successfully.

User response

Include a GROUP_NAME keyword in the group definition.

OC5055 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 is returned to the caller. All other functions fail to complete successfully.

User response

Increase the region size available to the job.

OC5056 NO <<ID>> SUB-COMPONENT ACTIVE

Explanation

Control cards that define an OMEGAMON group element were found without a corresponding <<ID>> subcomponent header.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Include an <<ID>> subcomponent header to properly isolate the different group element definitions.

OC5057 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 is returned to the caller. All other functions fail to complete successfully.

User response

Limit the operand to a maximum length of four characters.

OC5058 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 is returned to the caller. All other functions fail to complete successfully.

User response

Limit the operand to a maximum length of eight characters.

OC5059 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.

OC5060 TASKREQ INVALID ID SPECIFIED

Explanation

The TASKREQ operand is not one of the permissible values described in the OMEGAMON configuration guide. These are the valid options:
  • #PAn (n=1–3)
  • #Fnn (nn=01–36)
  • #LPA, #MAG
  • #OCD.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Change the operand to specify a valid TASKREQ ID.

OC5061 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 is returned to the caller. All other functions fail to complete successfully.

User response

Supply one of the four permissible element types.

OC5062 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 is returned to the caller. All other functions fail to complete successfully.

User response

Specify the groups to which the element belongs.

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 is returned to the caller. All other functions fail to complete successfully.

User response

Reduce the number of group elements to a maximum of 2000.

OC5065 DATA_STORE_TYPE MUST BE DSPACE OR FILEOCMP OR AUTO

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 data sets.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions 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 is returned to the caller. All other functions 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 sub list values.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Provide three intervals as described in the OMEGAMON configuration guide.

OC5070 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 is returned to the caller. All other functions 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.

OC5071 TIME_SLOT END TIME BEFORE START TIME

Explanation

The second TIME_SLOT sub list element is less than or equal to the first sub list element.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Select an ending time that is greater than the start time.

OC5072 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.

OC5073 RTA TIME_SLOT NOT OF FORM (HHMM,HHMM)

Explanation

The TIME_SLOT operand has not been specified as a sub list with two entries.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Specify an operand that includes both the start and end times.

OC5074 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 is returned to the caller. All other functions fail to complete successfully.

User response

Include a UNIT_ADDRESS keyword for each dedicated session.

OC5075 UNIT_ADDRESS MUST BE 3 OR 4 CHARACTERS

Explanation

The dedicated session unit address has an length that is not valid.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Specify a proper three- or four-character unit address.

OC5076 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.

OC5077 NO <<UNIT>> SUB-COMPONENT HEADER ACTIVE

Explanation

Control cards that define a dedicated session were found without a corresponding <<UNIT>> subcomponent header.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Include a <<UNIT>> subcomponent header to properly isolate the different session definitions.

OC5078 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 is returned to the caller. All other functions fail to complete successfully.

User response

Increase the region size of the job.

OC5079 TOO MANY SUBLIST ENTRIES SPECIFIED, LIMIT=aa

Explanation

The operand, enclosed in parenthesis, contains more than the maximum number of sub list elements allowed, as denoted by the aa value.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that the count of sublist entries does not exceed the limit.

OC5080 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 is returned to the caller. All other functions fail to complete successfully.

User response

Separate the included and excluded transactions for a given resource by placing them under their own resource subcomponent ID.

OC5100 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. The 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 is returned to the caller. All other functions fail to complete successfully.

User response

The SYNAD message buffer describes the source of the problem. Take the appropriate action to ensure the success of I/O operations on the global source dataset.

OC5101 UNABLE TO OBTAIN GLOBAL MODULE STORAGE, LENGTH=aaaaaaaa

Explanation

Insufficient memory was available to build the global data area in private storage more than the 16MB line.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Increase the region size of the job.

OC5102 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 is returned to the caller. All other functions fail to complete successfully.

User response

Change one of the keyword operands to resolve the conflict.

OC5103 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 are produced.

User response

This message serves only as a warning and does not interfere with the creation of the global data area.

OC5104 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 is returned to the caller. All other functions fail to complete successfully.

User response

Alter the bottleneck analysis intervals.

OC5105 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 is returned to the caller. All other functions fail to complete successfully.

User response

Either increase the MAX_GROUPS limit, or eliminate the group definitions that are beyond the acceptable range.

OC5106 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 is returned to the caller. All other functions fail to complete successfully.

User response

Ensure that group elements defined under the <<ID>> subcomponent all specify eligible groups with matching types.

OC5107 FILE NAME NOT SPECIFIED FOR DATA_STORE_TYPE=xxxxx

Explanation

The DATA_STORE_FILE_NAME keyword was not included for Online Data Viewing. The file type of xxxxx, where xxxxx is FILEOCMP or AUTO, requires a valid dataset name be provided.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Provide a file name for use by the Online Data Viewing facility.

OC5108 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 is returned to the caller. All other functions fail to complete successfully.

User response

Revise the slot definitions to ensure they do not overlap.

OC5109 LIMIT NOT SPECIFIED FOR RESOURCE aaaaaaaa

Explanation

The resource denoted by the aaaaaaaa value does not include either a KILL or WARN limit.

System action

For a read request, a default copy of the global module is returned to the caller. All other functions fail to complete successfully.

User response

Specify a limit that will act as a resource threshold.

OC5110 LIMITS MAY NOT BE USED WITH EXCLUDED TRANSACTIONS FOR RESOURCEaaaa

Explanation

The resource denoted by the aaaa value 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 is returned to the caller. All other functions fail to complete successfully.

User response

Remove the KILL_LIMIT and WARN_LIMIT keywords from resource definitions that exclude transactions.

OC5111 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.

OC5112 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 is returned to the caller. All other functions fail to complete successfully.

User response

Either increase the MAX_IDS limit, or eliminate enough group elements to satisfy the ID constraints.

OC5115I GBR PROGRAM CALLS WILL NOT BE TRACED BECAUSE NOAUTO WAS SPECIFIED FOR ENABLE_APPLICATION_TRACE.

Explanation

The TRACE_ALL_PROGRAM_CALLS=YES was specified with ENABLE_APPLICATION_TRACE=NOAUTO. This message informs the user that program trace setting will be ineffective until application trace is activated.

System action

System processing of the GLOBAL continues.

User response

For tracing of all program calls to be effective, the Application Trace Facility must also be enabled; as: ENABLE_APPLICATION_TRACE=AUTO TRACE_ALL_PROGRAM_CALLS=YES.

OC5117E GWR FIND THE SHARE OPTIONS DO NOT ALLOW ACCESS TO datasetname(global)

Explanation

OMEGAMON for CICS needs to expand Global global but was unable to because the datasetname (specified in RKC2GLBL DD) is already allocated to another job or task.

System action

Processing will fail for Global global.

User response

When generating a sample Global, the original member can be deleted; otherwise ensure that datasetname is not already allocated to another job or task. Re-run this job.

OC8900 RESOURCE LIMIT EXCEEDED: tttt RLaa - xxxxxxxxxxxxxxxx

Explanation

The CICS transaction tttt has exceeded either the xxxxxxxxxxxxxxxx resource warning threshold or the kill threshold, and the transaction was running under CEDF. To stop a transaction with abend code RLaa, specify a KILL limit in the resource limiting definition in the global definition member. The xxxxxxxxxxxxxxxx value is a text string explaining the reason for the abend code. These are the abend codes and their associated texts:

RLAD
ADABAS requests
RLCP
CPU time usage
RLCT
Container HWM
RLDB
DB2 requests
RLDC
DATACOM requests
RLDL
DL/I requests
RLDS
DSA HWM storage
RLED
EDSA HWM storage
RLEL
elapsed time
RLFC
file requests
RLGD
GDSA HWM storage
RLID
IDMS requests
RLMQ
MQ requests
RLSU
SUPRA requests
RLU1
USREVNT1 requests

System action

Prior to issuing the message, RLIM stops 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 global definition, if appropriate.

OC8902 HH:MM:SS WARNING LIMIT EXCEEDED FOR xxxxxxxxxxxxxxxx: TRANS=ttttt, TASKNO=nnnnnnnn, USER=UNKNOWN

Explanation

The CICS transaction tttt has exceeded the xxxxxxxxxxxxxxxx resource warning threshold. The xxxxxxxxxxxxxxxx value is a text string explaining the reason for the abend code. These are the abend codes and their associated texts:

RLAD
ADABAS requests
RLCP
CPU time usage
RLCT
Container HWM
RLDB
DB2 requests
RLDC
DATACOM requests
RLDL
DL/I requests
RLDS
DSA HWM storage
RLED
EDSA HWM storage
RLEL
elapsed time
RLFC
file requests
RLGD
GDSA HWM storage
RLID
IDMS requests
RLMQ
MQ requests
RLSU
SUPRA requests
RLU1
USREVNT1 requests

System action

Prior to issuing the message, RLIM stops the exceeded threshold to prevent the reissuing of identical messages. All remaining thresholds are kept intact and active. The transaction reverts to normal processing.

User response

Correct the application, or increase the limit value in the global definition, if appropriate.

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 kill threshold. Thexxxxxxxxxxxxxxxx value is a text string explaining the reason for the abend code. These are the abend codes and their associated texts:

RLAD
ADABAS requests
RLCP
CPU time usage
RLCT
Container HWM
RLDB
DB2 requests
RLDC
DATACOM requests
RLDL
DL/I requests
RLDS
DSA HWM storage
RLED
EDSA HWM storage
RLEL
elapsed time
RLFC
file requests
RLGD
GDSA HWM storage
RLID
IDMS requests
RLMQ
MQ requests
RLSU
SUPRA requests
RLU1
USREVNT1 requests

System action

Prior to issuing the message, RLIM stops 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 global definition, if appropriate.