Omcics Troubleshooting

IBM Z OMEGAMON for CICS
5.6.0
Troubleshooting Guide
IBM
Note
Before using this information and the product it supports, read the information in “Notices” on page
645.
Notices
This edition applies to Version 5, Release 6 of IBM® Tivoli® OMEGAMON® XE for CICS on z/OS (program number 5698-
T07) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2004, 2022.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents
Figures................................................................................................................ vii
Tables.................................................................................................................. ix
Chapter 1. Troubleshooting Guide.......................................................................... 1

Troubleshooting checklist............................................................................................................................1
Troubleshooting a problem..........................................................................................................................1
Tools for troubleshooting.............................................................................................................................3
Finding information about known problems............................................................................................... 3
Collecting diagnostic data............................................................................................................................4
Using the pdcollect tool..........................................................................................................................4
Analyzing data.............................................................................................................................................. 4
Submitting problems to IBM Software Support.......................................................................................... 5
Chapter 2. Setting up traces...................................................................................7

Setting up RAS1 tracing for OMEGAMON for CICS..................................................................................... 7
Setting trace levels by editing RKANPARU(KppENV)............................................................................ 8
Setting trace levels dynamically from the IBM Tivoli Monitoring Service Console...............................8
Syntax for RAS1 traces.........................................................................................................................11
Redirecting output of RAS1 tracing .....................................................................................................12
Communications tracing............................................................................................................................12
Dynamically controlling OMEGAMON monitoring exit (TxnMonitor) trace in CICS TG............................ 13
Chapter 3. Troubleshooting installation and configuration problems..................... 15

Self-describing agent processing fails; Java root directory is not valid................................................... 15
Symptoms of an unsuccessful self-describing agent installation............................................................ 15
Self-describing agent deletes all prior versions of the product installation record.................................17
A monitored system is displayed in the wrong place............................................................................... 18
One or more CICS regions are not displayed on the interface; no communication between the
agent and the region............................................................................................................................. 18
Verifying CICS region status with a situation in the Tivoli Enterprise Portal............................................18
The CICSTG_Health_Critical situation is triggered persistently for a monitored CICS TG ..................... 19
The CTGSTATS module failed for the OMEGAMON for CICS TG agent.....................................................19
Orphaned CICS TG transactions remain in active transaction workspaces.............................................19
Historical workspaces in Tivoli Enterprise Portal contain no data........................................................... 21
U200 Port in use message found in the RKLVLOG output, indicating an incorrect default port for
TCP/IP profile........................................................................................................................................21
Chapter 4. Troubleshooting usage problems......................................................... 23

Analyzing the OMEGAMON CICSplex configuration................................................................................. 23
OC STATUS,CICSPLEX command......................................................................................................... 23
OC DISPLAY,PLEX=cicsplex command................................................................................................ 24
OC DISPLAY,PLEXRULES command.................................................................................................... 24
OC DISPLAY,PREFERENCES command............................................................................................... 25
Problems with SLA Batch Utility ............................................................................................................... 26
The DTD file cannot be found in the same folder as the XML file....................................................... 26
The SLA definitions that you are trying to import are always rejected............................................... 26
The correct Java version is not found.................................................................................................. 27
SLA definitions cannot be imported or exported ................................................................................27
iii
The log file cannot be found.................................................................................................................27
Chapter 5. Tivoli Enterprise Portal - based issues................................................. 29

Cannot log on to Tivoli Enterprise Portal with valid user ID and password............................................. 29
Cross-product links are missing from the link list.................................................................................... 29
A link to a terminal emulator session fails................................................................................................ 30
A terminal emulator script fails ................................................................................................................ 30
Chapter 6. Problems with Service Level Analysis.................................................. 33

KCP0215: UNABLE TO OBTAIN RECORD CELL, DATA LOST ....................................................................33
KCP0243: WSR WAITING FOR WORKLOAD DEFINITIONS......................................................................33
Chapter 7. Miscellaneous problems...................................................................... 35

The KILL ICE command fails for a member on the ICE Chain in the 3270 environment and
produces the OC3432 message........................................................................................................... 35
The KFWITM081E message is displayed when attempting to link to another product workspace........35
SQL queries to Tivoli Data Warehouse fail because of invalid column name...........................................35
Summarization and Pruning does not function as described................................................................... 36
Summarization and Pruning agent fails to run as scheduled................................................................... 36
Chapter 8. Troubleshooting data collection problems............................................37

Using OMEGAMON for CICS (3270) to collect screen logs.......................................................................37
Monitoring agent cannot insert all requested data rows into the persistent data store......................... 37
Monitoring agent running out of storage .................................................................................................. 38
Tivoli Enterprise Portal workspace displays no data or does not show all the data you expected.........41
Chapter 9. Troubleshooting performance problems...............................................43

The monitoring agent captures a dump in the event of an unexpected abend....................................... 43
The KOCOME00 program must not be defined as OPENAPI....................................................................43
Long response times or no results returned when specifying historical collection time spans for
some workspaces................................................................................................................................. 43
A message is displayed when the monitoring system tries to return data to a table.............................. 44
Monitoring agent receives remote procedure call errors during warehousing, with some requests
timing out and failing............................................................................................................................ 44
Performance for the Tivoli Data Warehouse database is degraded or there are gaps where
historical data is unavailable for a specified collection period........................................................... 45
Chapter 10. Messages overview........................................................................... 47

Message log locations................................................................................................................................47
Generating and viewing log files................................................................................................................47
Message prefixes....................................................................................................................................... 48
Message prefix tables................................................................................................................................ 48
Standard messages and abend codes................................................................................................. 49
Reporting problems..............................................................................................................................49
Chapter 11. KCP messages.................................................................................. 51
Chapter 12. KCPAC messages.............................................................................131
Chapter 13. KCPFH messages............................................................................ 141
Chapter 14. KCPPA messages............................................................................ 143
Chapter 15. KCPPL messages.............................................................................165
iv
Chapter 16. KCPPR messages............................................................................ 175
Chapter 17. KCPSB messages............................................................................ 201
Chapter 18. KCPSP messages............................................................................ 221
Chapter 19. KCPUI messages............................................................................. 235
Chapter 20. KCPZZ messages.............................................................................237
Chapter 21. KGW messages............................................................................... 239
Chapter 22. KGWRM messages...........................................................................275
Chapter 23. KGWRM messages...........................................................................287
Chapter 24. KGWUI messages............................................................................289
Chapter 25. BG messages.................................................................................. 291
Chapter 26. KC2 messages.................................................................................313
Chapter 27. KOCJ messages...............................................................................315
Chapter 28. OC messages.................................................................................. 325
Chapter 29. CI0410-LSCX messages.................................................................. 443
Chapter 30. OB0101-OB9269 messages............................................................. 497
Chapter 31. OBV101-OMV9991 messages.......................................................... 579
Appendix A. Abend codes.................................................................................. 641

KILL Services Transaction abend codes................................................................................................. 641
Resource Limiting abend codes.............................................................................................................. 641
Support information.......................................................................................... 643
Notices..............................................................................................................645
Privacy policy considerations ................................................................................................................. 646
Trademarks.............................................................................................................................................. 647
Index................................................................................................................ 649
v
vi
Figures
1. Transaction Analysis workspace showing likely orphaned transactions in the Active Transactions
subpanel..................................................................................................................................................... 20
vii
viii
Tables
1. Locations of log and trace information for z/OS components......................................................................7
2. Message prefixes.........................................................................................................................................48
3. Standard messages and abend codes........................................................................................................ 49
4. Collecting memory dumps.......................................................................................................................... 50
5. Return codes when IBM Z OMEGAMON for CICS on z/OS is unable to monitor a CICS region................ 58
6. SMFEWTM return code values.................................................................................................................. 101
7. Return codes when IBM Z OMEGAMON for CICS TG cannot monitor a CICS region..............................240
8. Return codes for Message KGWRM1019E............................................................................................... 281
9. Return codes for Message KGWRM1020W.............................................................................................. 282
10. Return codes for Message KGWRM1031E............................................................................................. 284
11. Return codes for Message KGWRM1032W............................................................................................ 285
12. Return codes when INTR has encountered an unrecoverable initialization error................................ 347
13. Return codes when INTR has encountered an unrecoverable initialization error................................ 347
14. Return codes when INTR has encountered a processing error............................................................. 348
15. Decimal return codes that replace a hexadecimal return code for the LU Response Time Facility..... 351
16. The possible values for the service task that was not able to perform the service..............................415
17. User Actions............................................................................................................................................ 415
ix
x
Chapter 1. Troubleshooting Guide
In a complex environment such as the one in which IBM Z OMEGAMON for CICS® operates, identifying the
source and cause of problems can be difficult.
A problem that you experience with IBM Z OMEGAMON for CICS data in the Tivoli Enterprise Portal might
ultimately be traced to a component such as a Tivoli Enterprise Monitoring Server or to Tivoli Enterprise
Portal Server, rather than to the monitoring agent. The IBM Tivoli Monitoring: Troubleshooting Guide
provides extensive information about resolving problems you might experience with Tivoli Management
Services components and describes in detail the tools available to help you collect and analyze diagnostic
data.
The material in this Troubleshooting Guide helps you decide where to look for information about what
is causing a problem with the IBM Z OMEGAMON for CICS base product and the IBM Z OMEGAMON
for CICS TG, OMEGAMON II for CICS and OMEGAMON enhanced 3270 user interface components. This
information also includes the messages generated by the base product, the SLA Batch Utility, the TG and
OMEGAMON II for CICS components, and the OMEGAMON enhanced 3270 user interface component.
This information focuses on collecting and analyzing data specific to the OMEGAMON for CICS monitoring
agent. This section introduces a systematic approach to troubleshooting that can help you determine
which problems are caused by common components and which are associated with the monitoring agent.
It also provides an overview of the tools available for collecting and analyzing diagnostic data and for
documenting problems and reporting them to IBM Software Support.
Troubleshooting checklist
Use this checklist to identify and eliminate any known problems.
1. Ensure that all applicable PTFs and fix packs have been applied to the monitoring agents, common
z/OS® components (such as OMEGAMON Subsystem), and shared Tivoli Management Services
components (such as Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal, and TMS:Engine):
• Check the OMEGAMON for CICS on z/OS and OMEGAMON for CICS TG on z/OS and Tivoli
Management Services on z/OS program directories for required PTFs and Fix Packs.
• Check the PSP bucket for new information.
• Check the README file and TechNotes for known problems or workarounds.
2. Check the IBM Tivoli Monitoring: Troubleshooting Guide for known problems.
3. Review the troubleshooting scenarios recorded in this information unit.
After you have eliminated any known problem at the source, set up tracing for the affected components
(see “Setting up RAS1 tracing for OMEGAMON for CICS” on page 7) and use the tools available with
IBM Support Assistant to correlate and analyze the logs (see “Tools for troubleshooting” on page 3).
For detailed suggestions on finding the source of problems, see “Troubleshooting a problem” on page
1.
Troubleshooting a problem
Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to
determine why something does not work as expected and explain how to resolve the problem.
The first step in the troubleshooting process is to describe the problem completely. Problem descriptions
help you and the IBM Software Support person know where to start to find the cause of the problem. This
step includes asking yourself basic questions:
• What are the symptoms of the problem?
• Where does the problem occur?
© Copyright IBM Corp. 2004, 2022 1

• When does the problem occur?
• Under which conditions does the problem occur?
• Can the problem be reproduced?
The answers to these questions typically lead to a good description of the problem, and that is the best
way to start down the path of problem resolution.
What are the symptoms of the problem?

When starting to describe a problem, the most obvious question is “What is the problem?” This
might seem like a straightforward question; however, you can break it down into several more-focused
questions that create a more descriptive picture of the problem. These questions can include:
• Who, or what, is reporting the problem?
• What are the error codes and messages?
• How does the system fail? For example, is it a loop, hang, crash, performance degradation, or incorrect
result?
• What is the business impact of the problem?
Where does the problem occur?

Determining where the problem originates is not always easy, but it is one of the most important steps in
resolving a problem. Many layers of technology can exist between the reporting and failing components.
Tivoli Management Services components, networks, disks, and drivers are only a few of the components
to consider when you are investigating problems. The following questions help you to focus on where the
problem occurs to isolate the problem layer:
• Is the problem specific to one platform or operating system, or is it common across multiple platforms
or operating systems?
• Is the current environment and configuration supported?
Remember that if one layer or component reports the problem, the problem does not necessarily
originate in that layer or component. Part of identifying where a problem originates is understanding
the environment in which it exists. Take some time to completely describe the problem environment,
including the operating system and version, all corresponding software and versions, and hardware
information. Confirm that you are running within an environment that is a supported configuration; many
problems can be traced back to incompatible levels of software that are not intended to run together or
have not been fully tested together.
When does the problem occur?

Develop a detailed timeline of events leading up to a failure, especially for those cases that are one-time
occurrences. You can most easily do this by working backward: start at the time an error was reported
(as precisely as possible, even down to the millisecond), and work backward through the available logs
and information. Typically, you need to look only as far as the first suspicious event that you find in a
diagnostic log; however, this is not always easy to do and takes practice. Knowing when to stop looking is
especially difficult when multiple layers of technology are involved, and when each has its own diagnostic
information.
To develop a detailed timeline of events, answer these questions:
• Does the problem happen only at a certain time of day or night?
• How often does the problem happen?
• What sequence of events leads up to the time that the problem is reported?
• Does the problem happen after an environment change, such as upgrading or installing software or
hardware?
2 IBM Z OMEGAMON for CICS: Troubleshooting Guide

Responding to questions like this helps to provide you with a frame of reference in which to investigate
the problem.
Under what conditions does the problem occur?

Knowing which systems and applications are running at the time that a problem occurs is an important
part of troubleshooting. These questions about your environment can help you to identify the root cause
of the problem:
• Does the problem always occur when the same task is being performed?
• Does a certain sequence of events need to occur for the problem to surface?
• Do any other applications fail at the same time?
Answering these types of questions can help you explain the environment in which the problem occurs
and correlate any dependencies. Remember that just because multiple problems might have occurred
around the same time, the problems are not necessarily related.
Can the problem be reproduced?

From a troubleshooting standpoint, the ideal problem is one that can be reproduced. Typically, problems
that can be reproduced have a larger set of tools or procedures at your disposal to help you investigate.
Consequently, problems that you can reproduce are often easier to debug and solve. However, problems
that you can reproduce can have a disadvantage: if the problem is of significant business impact, you
do not want it to recur. If possible, re-create the problem in a test or development environment, which
typically offers you more flexibility and control during your investigation.
Ask the following questions:
• Can the problem be recreated on a test system?
• Are multiple users or applications encountering the same type of problem?
• Can the problem be recreated by running a single command, a set of commands, or a particular
application, or a stand-alone application?
Tools for troubleshooting

IBM Tivoli Monitoring provides a number of tools to help you troubleshoot problems with Tivoli
Management Services components and monitoring agents.
The IBM Tivoli Monitoring: Troubleshooting Guide describes these tools in detail and gives information on
how to obtain them. Most of these tools have been incorporated into the IBM Support Assistant.
The IBM Support Assistant is a free, downloadable tool that helps you find information about known
problems, collect and analyze diagnostic information, and report problems to IBM Support and track their
resolution.
Finding information about known problems

The IBM Tivoli Monitoring: Troubleshooting Guide contains a great deal of information about problems and
solutions for Tivoli Management Services components on both distributed and z/OS platforms.
This information unit contains information on problems commonly encountered with OMEGAMON for
CICS on z/OS.
In addition, you can visit the Tivoli OMEGAMON for CICS on z/OS page on the IBM support portal to
see the latest flashes and alerts. For more information, see http://www.ibm.com/support/entry/portal/
product/tivoli/tivoli_omegamon_xe_for_cics_on_z~os.
Chapter 1. Troubleshooting Guide 3

Collecting diagnostic data
The primary resource for diagnostic data is logs. Logs are records of text messages and trace data
generated by the software and written to an output destination, such as a console screen or a file.
Typically, an OMEGAMON XE monitoring agent on z/OS does not display messages at the Tivoli Enterprise
Portal. Instead, messages are sent to more typical z/OS output locations, such as SYSOUT data sets or
spool files or, more rarely, to the z/OS system console. Logging is enabled on all monitoring agents by
default.
Tracing is the recording of the processing of a computer program or transaction. Trace logs capture
information about the operating environment to help you diagnose problems when component software
fails to operate as intended. The principal log type for Tivoli Management Services and monitoring agents
that share those services is the reliability, availability, and serviceability (RAS1) trace log.
When the Tivoli Management Services z/OS components are initialized, RAS1 service initialization is
one of the first processes started. The RAS1 trace log mechanism is available on the Tivoli Enterprise
Monitoring Server, the Tivoli Enterprise Portal Server, and the monitoring agents. Most logs are located in
a logs subdirectory on the host computer. RAS logs are in the English language only.
By default, an OMEGAMON XE monitoring agent on z/OS has minimal tracing enabled. The RAS1=ERROR
setting means that only error messages are captured. When you report a problem, IBM Software Support
might ask you to enable a more in-depth and detailed form of tracing, such as one of those discussed
under “Syntax for RAS1 traces” on page 11. IBM Software Support uses the information captured
by trace logging to trace a problem to its source or to determine why an error occurred. The default
configuration for trace logging, such as the level of trace logging, depends on the source of the trace
logging. Trace logging is always enabled.
Note: There is CPU and I/O overhead associated with detailed RAS1 tracing that might degrade
performance of the monitoring agent. Restore RAS1 tracing to the minimal KBB_RAS1=ERROR after
problem diagnosis is completed.
Log files and trace information are provided in a common fashion across all monitoring agents on
z/OS and the z/OS components of the Tivoli Management Services. See “Setting up RAS1 tracing for
OMEGAMON for CICS” on page 7 to understand the locations of log and trace files for the monitoring
agent and the Tivoli Management Services components on z/OS.
For the locations for log files for distributed components, see the IBM Tivoli Monitoring: Troubleshooting
Guide.
Using the pdcollect tool

The pdcollect tool allows you to collect the most commonly-used information from a system to
troubleshoot on your own or to allow for IBM service to investigate a problem. It gathers log files,
configuration information, version information, and the like.
This tool also provides the ability to manage the size of trace data repositories. This tool is available
for Windows, UNIX, Linux®, and z/OS systems. It is located in the ITM_Install/bin directory on Windows,
UNIX, and Linux systems. It is supplied as the KMSPDCOL member of the RKANSAM dataset on z/OS
systems.
It is also included in IBM Support Assistant, available at http://www.ibm.com/software/support/isa/. For
more information on using pdcollect, see the IBM Tivoli Monitoring: Troubleshooting Guide.
Analyzing data
This information unit contains explanations of messages issued by OMEGAMON for CICS on z/OS,
OMEGAMON for CICS TG on z/OS, OMEGAMON for CICS and the components that they share with other
OMEGAMON XE monitoring agents on z/OS and provides suggested responses.
You can use this information to help analyze the logs that you collect. In addition, the Log Analyzer
tool, included in the IBM Support Assistant workbench, provides a graphical user interface that helps

you browse, analyze, and correlate logs files from multiple products. You can use the tool to view and
correlate logs from the portal server or monitoring server on a distributed system, or the RKLVLOG from a
monitoring agent or monitoring server on a z/OS system. With the Log Analyzer, you can evaluate multiple
event and error logs with time synchronization. You can import and select symptom catalogs against
which log files can be analyzed and correlated.
A symptom catalog is a set of predefined product-specific problem scenarios and possible solutions
that can be identified through automatic review of messages that might appear in a product log file
(for example, a monitoring server or monitoring agent RKLVLOG). Log records can be analyzed using a
symptom catalog to interpret known events and error conditions, and to provide detailed information on
how to resolve problems.
OMEGAMON for CICS on z/OS provides symptom catalogs for versions 4.2.0, 5.1.01, 5.1.1, and 5.3.0. IBM
Tivoli Monitoring also provides symptom catalogs. You can also use the Symptom Editor to create custom
symptom catalogs.
OMEGAMON for CICS on z/OS and IBM Tivoli Monitoring also provide specialized IBM Support Assistant
plug-ins with product-specific dialogs that provide you with diagnostic information you can use to
troubleshoot or even resolve problems. You install product-specific plug-ins using the IBM Support
Assistant Updater.
Submitting problems to IBM Software Support

If you have a problem that you are unable to solve by referring to this guide and to the IBM Tivoli
Monitoring: Troubleshooting Guide, gather the following information about the problem and contact IBM
Software Support for further assistance.
The IBM Support Assistant can help you gather and submit the required information about the problem.
Be prepared to supply the following items:
• Monitored application file.
• Appropriate RAS1 trace output. See “Setting up RAS1 tracing for OMEGAMON for CICS” on page 7 for
information about RAS1 trace output.
• Description of the operation scenario that led to the problem.
• Incorrect output, such as Tivoli Enterprise Portal screen prints or a description of what you observed, if
applicable.
• Log files from failing systems or regions. You can collect all logs or logs of a certain type, such as RAS
trace logs or message logs.
• Application information, such as version number and patch level.
• Operating system version number and patch level.
• Messages and other information displayed on the screen.
• Version number of the following components of the monitoring environment:
– Tivoli Enterprise Portal client
– Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server on distributed systems. Also
provide the IBM Tivoli Monitoring patch level, if available.
– Tivoli Enterprise Monitoring Server on z/OS
– Monitoring agent
For more information about collecting problem information, see the IBM Tivoli Monitoring:
Troubleshooting Guide for distributed components and “Setting up RAS1 tracing for OMEGAMON for CICS”
on page 7 for z/OS components.
Chapter 1. Troubleshooting Guide 5

Chapter 2. Setting up traces
Trace logs capture information about the operating environment to help you diagnose problems when
components fail to operate as intended.
The principal log type is the reliability, availability, and serviceability (RAS1) trace log. When the
monitoring agents and Tivoli Management Services components are initialized, RAS1 is one of the first
processes started. You can set up RAS tracing for the monitoring agents, Tivoli Enterprise Monitoring
Server, and Tivoli Enterprise Portal Server. RAS logs are in the English language only.
You can also use communications traces during TCP/IP initialization to help diagnose problems in
connections between the monitoring agent and the monitoring server.
Finally, you can control the OMEGAMON for CICS TG monitoring exit (TxnMonitor) trace dynamically to
collect trace information in the STDERR log file.
Setting up RAS1 tracing for OMEGAMON for CICS

RAS1 tracing is the primary diagnostic tool for product and infrastructure components.
Trace logging is always enabled, but the default configuration for trace logging, such as the level of
trace logging, depends on the source of the trace. For monitoring agents on z/OS, the default level is
KBB_RAS1=ERROR, which means that only error messages are captured. This is the setting for minimal
tracing. When you report a problem, IBM Software Support might ask you to enable a more in-depth and
detailed form of tracing, such as one of those discussed under “Syntax for RAS1 traces” on page 11.
RAS1 tracing can be set dynamically in the IBM Tivoli Monitoring Service Console interface or by a more
direct method of modifying the KBB_RAS1 parameter. For agents that run in their own address space,
the KBB_RAS1 parameter is located in the KppENV member in hilev.rte.RKANPARU, where pp is the
two-letter product code. For agents that run in the monitoring server address space, the KBB_RAS1
parameter is located in hilev.rte.RKANPARU(KDSENV). If you modify the KBB_RAS1 parameter by directly
editing the ENV file, you must stop and restart the monitoring server. To change the trace settings without
having to recycle the monitoring server, use the Service Console interface ras1 command.
RAS1 messages are sent to STDOUT and redirected to the files shown in Table 1 on page 7. RAS1
trace log files can grow very large with the wrong amount of filtering. Be careful with the levels of tracing
that you specify. Restore RAS1 tracing to the default level KBB_RAS1=ERROR after you complete problem
diagnosis.
Table 1. Locations of log and trace information for z/OS components

Component Component description and location
Monitoring agents The RKLVLOG for the monitoring agent started task is the single most
helpful piece of service information for an agent. The RKLV (R = runtime,
KLV = the prefix associated with IBM Tivoli Monitoring Services:Engine or
TMS:Engine) is the sysout data set or spool file that contains log and trace
messages.
These additional z/OS log files (if available) are also useful:
• The RKLVSNAP sysout data set or spool file contains formatted dump
output.
• The RKPDLOG sysout data set or spool file contains the information and
error messages related to the handling of persistent datastores.
• Some agents have other files defined to collect log and trace messages.
Refer to your started procedures for the locations of these serviceability
log files.

Table 1. Locations of log and trace information for z/OS components (continued)
Component Component description and location
Tivoli Enterprise Monitoring Server The Tivoli Enterprise Monitoring Server runs under TMS:Engine just as an
on z/OS agent does, and the logging is handled in the same way: log and trace data
are written to RKLVLOGs and RKPDLOGs.
End-to-End Response Time The End-to-End Response Time Features is a base component and does
Feature not have its own RKLVLOG file. This component writes messages to the
IBM System Display and Search Facility (SDSF) Job Log.
IBM Tivoli Management TMS:Engine is a collection of basic operating system and communication
Services:Engine (TMS:Engine) service routines built specifically for z/OS. All address spaces used by
monitoring agents load and use the services of TMS:Engine.
TMS:Engine writes messages to the same RKLVLOG file as the product
it is running. In the RKLVLOG file, product-specific messages start with
the product code (for example, KCP for OMEGAMON for CICS on z/OS
and KGW for OMEGAMON for CICS TG on z/OSmonitoring agents). The
messages for the Tivoli Enterprise Monitoring Server start with KDS. The
messages for the TMS:Engine itself start with that component prefix, KLV.
OMEGAMON Subsystem The OMEGAMON Subsystem does not allocate an RKLVLOG. This
component issues messages to either the SYSPRINT or SYSTRACE
allocation in the Subsystem procedure.
Persistent data store The RKPDLOG SYSOUT data set or spool file contains the information and
error messages related to the handling of persistent data stores.
Setting trace levels by editing RKANPARU(KppENV)

One of the simplest ways to set trace levels for an agent or monitoring server is to edit the
rhilev.rte.RKANPARU(KppENV) member.
The following examples show how to set RAS1 tracing for monitoring agents in OMEGAMON for CICS on
z/OS.
• This example sets RAS1 tracing for OMEGAMON for CICS TG on z/OS. To write all available CICS TG
monitoring agent messages to the RKLVLOG, edit the KGWENV member and add (UNIT:KGW ALL) to
the default KBB_RAS1=ERROR setting as shown:
KBB_RAS1=ERROR (UNIT:KGW ALL)
• This example sets RAS1 tracing for OMEGAMON for CICS on z/OS agents. To write all available CICS
monitoring agent messages, edit the KC5ENV member and add (UNIT:KCP ALL) to the default
KBB_RAS1=ERROR. To write all available CICSplex monitoring agent messages, edit the KC5ENV
member and add (UNIT:KCE ALL) to the default KBB_RAS1=ERROR setting. You can set RAS1 tracing
to write all available messages for both monitoring agents by adding the combination of keywords to the
default KBB_RAS1=ERROR setting as shown:
KBB_RAS1=ERROR (UNIT:KCP ALL) (UNIT:KCE ALL)
After you update a KppENV member, you must stop and restart the address space for the settings to take
effect. After that, the settings remain in effect for the life of the address space. To end the trace, you must
edit the file again to reset the trace level, and stop and restart the address space.
Setting trace levels dynamically from the IBM Tivoli Monitoring Service
Console
You can use the IBM Tivoli Monitoring Service Console to set trace levels for monitoring agents on z/OS,
as well as for a Tivoli Enterprise Monitoring Server on z/OS or for distributed components. Using the

service console, you can read logs and turn on traces for remote product diagnostics and configuration. If
you use the Service Console, you can change trace levels without recycling the monitoring server or other
components.
The Service Console is uniquely identified by its service point name. All Service Consoles for a host are
linked and presented on the IBM Tivoli Monitoring Service Index for that host. You can perform operations
on a specific component process by selecting the service console associated with the service point name
of the component.
Note: Enabling tracing may cause large amounts of trace data and degrade performance, so only turn on
tracing for the minimal amount of time as required to do problem determination.
Accessing the Service Console from a browser

You can access the Service Console from a browser window.
Use the following procedure to start the service console:
1. Start the browser.
2. In the Address field, type the URL for the IBM Tivoli Monitoring browser client:
http://hostname:1920
where hostname specifies the system where the process (monitoring server, portal server, Warehouse
Proxy Agent, Tivoli Data Warehouse, or monitoring agent) is installed. 1920 is the default port,
however, your system administrator may have configured this to a different value. If the service
console is not displayed, a system administrator might have blocked access to it.
3. On the IBM Tivoli Monitoring Service Console window, select the desired component process (service
point name).
4. Specify a valid user ID and password in the pop-up, then click OK.
The IBM Tivoli Monitoring Service Console performs user authentication using the native OS security
facility. If you use the IBM Tivoli Monitoring Service Console on z/OS systems, your user ID and password
are checked by the z/OS security facility. If you use the IBM Tivoli Monitoring Service Console on Windows
systems, then you must pass the Windows workstation user ID and password prompt. This is the rule
except for instances of a NULL or blank password. The IBM Tivoli Monitoring Service Console never
accepts a NULL or BLANK password.
A password is always required to access the service console. Blank passwords, even if correct, cannot
access the service console. Even if a user ID is allowed to login to the operating system without a
password, access to the service console is denied. Create a password for the user ID that is being used to
login to the service console.
You can issue service console commands in the command input area. For a list of available commands,
type a question mark (?) and click Submit.
Accessing the Service Console through the enhanced 3270 user interface
You can access the Service Console from the ITM Service Index workspace in the OMEGAMON enhanced
3270 user interface.
To use the ITM Service Console workspace, you must supply a user ID and password. This information is
sent to a Tivoli Enterprise Monitoring Server. The user ID and password (and the Service Console or SOAP
commands and their results) are normally sent in clear text using TCP/IP and the HTTP protocol. If you
want the password and ID to be sent in encrypted form instead of clear text, you must use the secure
version of this workspace. To use the secure versions of these workspaces, the address space must be
enabled to use the Hypertext Transfer Protocol Secure (HTTPS) communications protocol.
Use the following procedure to access the ITM Service Index (KOBHNDX) workspace in the OMEGAMON
enhanced 3270 user interface:
1. Navigate to the KOBHUBS workspace by entering =KOBHUBS on the command line.
Chapter 2. Setting up traces 9

2. Use one of the following methods to proceed to the ITM Service Index workspace.
• Place your cursor next to the name of the hub Tivoli Enterprise Monitoring Server name that you are
interested in, type / and press Enter, then select either ITM Service Index for Hub or ITM
Service Index for Hub (secure HTTPS) from the Options Menu.
• Place your cursor next to the name of the hub Tivoli Enterprise Monitoring Server name that you are
interested in, type I and press Enter for an HTTP connection to ITM Service Index or type J and
press Enter for an HTTPS connection to ITM Service Index, if enabled
The ITM Service Index workspace is displayed.
Service Console commands

The Service Console supports the ras1 command, which is especially useful for dynamically enabling
and disabling RAS1 traces. The documentation requests from IBM Software Support may conflict with
your availability requirements. The ras1 command can be used to alter KBB_RAS1 tracing parameters
dynamically without the need to recycle the product. The Service Console also supports the bss1
command, which is also useful for troubleshooting.
For example, you can issue the following ras1 command from the Service Console to enable the kpx
trace:
ras1 set (UNIT:kpx ALL)
After you capture this trace, you can disable it with the following service console command:
ras1 set (UNIT:kpx ANY)
The ras1 command is paired with one of the following subcommands:

log
Display RAS1 log capture buffer.
list
List the RAS1 filters in effect.
set serviceunit
Control traces and filters for serviceunit
To see what tracing is already in effect, submit the following command:
ras1 list
Note:
1. The information inside the parentheses may be case-sensitive. Use the values provided by IBM
Software Support.
2. The settings set by Service Console commands remain in effect for the current activation of the
product. After the product is recycled, the original trace settings are restored.
The bss1 command manages BSS1 (Basic System Services). The command is paired with one of the
following subcommands:
listenv
Display the resident TMS:Engine variables.
getenv envvar
Display environment variable, where envvar is any variable that can be returned from listenv.
setenv envvar
Assign an environment variable where envvar is any variable that can be returned from listenv.
info
Display BSS1_Info() data.

config debugenv
Modifies the settings of the TMS:Engine debug environment variables: RES1_DEBUG, KDH_DEBUG,
KDC_DEBUG, and KDE_DEBUG. The possible values, from most to least tracing messages, are: M
(Max), D (Detail), Y (Yes) and N (Nominal). For example, the following config command alters the
setting of KDC_DEBUG:
BSS1 CONFIG KDC_DEBUG=Y
Syntax for RAS1 traces

This syntax is used to specify a RAS1 trace in the rhilev.rte.RKANPARU(KppENV) file. An IBM Software
Support representative can tell you the values to set for the RAS1 trace parameters.
The basic syntax of the RAS1 trace command is:
KBB_RAS1= global_class
(COMP: component_type)
(ENTRY: entry_point) (UNIT: unit_name, class)
where:
global_class
Indicates the level of tracing that you want. This is a global setting that applies to all RAS1 filters in
the process. If you set this global class by itself, it is global in scope and the trace cannot filter on any
of the other keywords. Separate combined classes with a space. The following values are possible.
Valid abbreviations are in parentheses.
• ERROR (ER): returns severe error messages only (this is the default for most applications).
• STATE (ST): records the condition or current setting of flags and variables in the process. If state
tracing is enabled, you can see the current state of particular variables or flags as the process is
running.
• FLOW (FL): causes a message to be generated at an entry or exit point of a function.
• DETAIL (DE): produces a detailed level of tracing.
• INPUT (IN): records data created by a particular API, function, or process.
• ALL: causes all available messages to be recorded. This setting combines all the other forms of
tracing.
COMP
Indicates that the trace includes a component type. The COMP keyword is used to trace groups of
routines related by function (or component). Use this keyword only at the explicit request of an IBM
Software Suppor representative.
component_type
Identifies a component type. An IBM Software Support representative can tell you what value to
specify.
ENTRY
Narrows a filtering routine to specify a specific ENTRY POINT. Since multiple entry points for a
single routine are rare, use this keyword only at the explicit request of an IBM Software Support
representative.
entry_point
Represents the name of the entry point. An IBM Software Support representative can tell you what
value to specify.
UNIT
Indicates that the trace is to look for a match between the compilation unit dispatched and the fully or
partially qualified compilation unit specified on the RAS1 statement. A match results in a trace entry.

unit_name
Represents the name of the compilation unit. In most instances, this name defines the component
that is being traced. The value is likely to be the three-character component identifier for the
monitoring agent (Kpp).
class
One of the same values specified for global_class, but, because of its position inside the parentheses,
narrowed in scope to apply only to the unit_name specified.
Note: The default setting for monitoring agents on z/OS is KBB_RAS1=ERROR, meaning that only error
tracing is enabled. You can specify any combination of UNIT, COMP, and ENTRY keywords. No keyword is
required. However, the RAS1 value you set with the global class applies to all components.
Redirecting output of RAS1 tracing

Nearly all diagnostic information for the z/OS components is delivered by the RAS1 component. This
component is configured by the KBB_RAS1 environment variable in member KBBENV of RKANPARU. You
can redirect the initialization member using the TMS:Engine INITLIST processing. INITLIST processing is
always echoed to the RKLVLOG with the KLVIN411 message.
This example shows a typical KBBENV override to a different member, KDSENV:
KLVIN410 INITLIST MEMBER KDSINIT BEING PROCESSED

KLVIN411 KLVINNAM=KDSINNAM
KLVIN411 KLVINTB=KDSINTB
KLVIN411 KLVINVLG=KDSINVLG
KLVIN411 KLVINNAF=KDSINNAF
KLVIN411 KLVINVPO=KDSINVPO
KLVIN411 KLVINSTG=KDSINSTG
KLVIN411 KLVINVAM=KDSINVAM
KLVIN411 KBBENV=KDSENV
In this example, configuration of KBB_RAS1 is recorded in member KDSENV of RKANPARU.
Communications tracing
Communications tracing during TCP/IP initialization is controlled by the KDC_DEBUG environment
variable.
To obtain the level of tracing required for the TCP/IP initialization messages to be recorded in the RAS1
log, add the string KDC_DEBUG=Y to &rhilev.&rte.RKANPARU(KppENV). You can also set the KDC_DEBUG
variable dynamically using the Service Console bss1 command.
Possible values for KDC_DEBUG are:
Y
The data flow between the monitoring agent and the monitoring server during TCP/IP initialization
is recorded, including data packages sent and received. When KDC_DEBUG=Y is active in the
environment during initialization of TCP/IP services for this address space, you can confirm successful
initialization of TCP/IP by looking for one of the following messages in RKLVLOG:
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.tcp

"KDE1I_OpenTransportProvider") Transport opened: socket/ip.pipe
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.udp
N
The data flow between the monitoring agent and the monitoring server during TCP/IP initialization is
not recorded. This is the default and the recommended setting for normal operation.
D
Full packet tracing plus STATE and FLOW tracing.
M
D plus INPUT and OUTPUT Help tracing

Dynamically controlling OMEGAMON monitoring exit (TxnMonitor)
trace in CICS TG
Full (level 4) tracing may be enabled and disabled dynamically in CICS Transaction Gateway daemon
regions. The trace output destination for this information is the STDERR log file.
Issue the following z/OS Modify command to start the trace:
/F <ctgjobname>,APPL=RMEXIT,CMD=KGWTRACE_ON
The response to the above command is as follows:
KGWRM0040I: SETTR100 Trace level 04 has been requested.

KGWRM1011I: KGWRM Trace level set to 4.
Issue the following z/OS Modify command to stop the trace:
/F <ctgjobname>,APPL=RMEXIT,CMD=KGWTRACE_OFF
The response to this command is as follows:
KGWRM0040I: SETTR100 Trace level 00 has been requested.

KGWRM1011I: KGWRM Trace level set to 0.

Chapter 3. Troubleshooting installation and
configuration problems
This information describes problems that might be associated with the installation and configuration of
OMEGAMON for CICS on z/OS base product and the OMEGAMON for CICS TG on z/OS component.
Self-describing agent processing fails; Java root directory is not

valid
If you use the path for the Java root directory as it is displayed on the Specify TEMS Self-Describing Agent
Values panel, and it does not match the Java path in your environment, you will receive error messages.
The self-describing agent (SDA) feature requires that you have Java version 1.5.0 (also known as Java
5.0) or higher installed in your environment. In the Configuration Tool, the Specify TEMS Self-Describing
Agent Values panel displays the Java root directory for the TEMS_JAVA_BINPATH parameter.
For example:
(0008-D772CCCB:kfasdwlm.c,777,"KFASDM_RequestMgr") KFASDM_InstallSDpackage failed

status <1011>.
product code <CP> product version <05100163> managed system <RKCPXM03:XXXX:CPIRA>
thrunode <NODE>
KFASD102 Self-Describing Install Failed with STATUS <1011> for PRODUCT <CP>,
VER <05100163>, ID <TMS>,
If SDA processing fails due to an invalid Java root directory path, error messages are written to the hub
Tivoli Enterprise Monitoring Server started task RKLVLOG output. If you see these messages in the hub
Tivoli Enterprise Monitoring Server RKLVLOG output, verify with your system administrator that you have
the correct Java path, and, if needed, enter the correct path using the GBL_HFS_JAVA_DIRn parameter in
PARMGEN.
Symptoms of an unsuccessful self-describing agent installation

If you experience symptoms of an unsuccessful self-describing agent (SDA) installation, verify that the
components operating as part of your runtime environment have the SDA function enabled.
These are the symptoms of an unsuccessful self-describing agent (SDA) installation:
• No data is displayed on the Tivoli Enterprise Portal
• No data is displayed on the OMEGAMON enhanced 3270 user interface
• Unresolved workspace names on the Tivoli Enterprise Portal
When one or more of these symptoms occur, you must verify that all components operating as part of
your runtime environment have the SDA function enabled. By default, the SDA function is enabled at the
monitoring agent, but disabled at the hub Tivoli Enterprise Monitoring Server. You can verify the CICS
agent status by looking at the KC5ENV member of the &hilev.RKANPARU library for OMEGAMON for CICS
on z/OS, the KGWENV member of the &hilev.RKANPARU library for OMEGAMON for CICS TG on z/OS or
the KDSENV member of the &hillev.RKANPARU library, if the agents are running within a Tivoli Enterprise
Monitoring Server address space. You can verify the Tivoli Enterprise Monitoring Server status by looking
at the KDSENV member of the &hillev.RKANPARU library, if the Tivoli Enterprise Monitoring Server is on
the z/OS operating system, or if it is on a distributed platform in the Tivoli Enterprise Monitoring Server
configuration file.
For the agent, verify that the following setting is applied:
TEMA_SDA=Y
For the Tivoli Enterprise Monitoring Server, ensure the following setting is applied:

KMS_SDA=Y
If SDA is enabled, verify that the process has completed successfully using the IBM Tivoli Monitoring-
supplied tacmd command line interface utility. This utility is provided by IBM Tivoli Monitoring as part
of the Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server installation on distributed
platforms only.
If your monitoring environment is based exclusively on the z/OS operating system, you will need to install
either a Tivoli Enterprise Portal Server or Tivoli Enterprise Monitoring Server onto a machine running a
distributed platform to access the tacmd command. You can then use the command to connect to your
hub Tivoli Enterprise Monitoring Server running on the z/OS operating system.
You can also use the tacmd command to verify the installation level of IBM Z OMEGAMON for CICS
application support within your runtime environment, if you used the installation image provided on the
application support DVD instead of SDA.
To verify the state of your application support, perform the following steps:
1. Log on to the Tivoli Enterprise Monitoring Server, for example:
C:\ibm\ITM\BIN>tacmd login -s 9.42.46.74:35108
Where port 35108 is the http port number and not the global (GLB) port that agents connect through.
2. List the application installation records for OMEGAMON for CICS on z/OS and for OMEGAMON for CICS
TG on z/OS:
C:\ibm\ITM\BIN>tacmd listappinstallrecs -t CP,GW
HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS

MYHUB:CMS CP 05300000 5655 TMS 05300000 Y IC 0
MYHUB:CMS CP 05300000 5655 TPS 05300000 IC 0
MYHUB:CMS CP 05300000 5655 TPW 05300000 IC 0
MYHUB:CMS GW 05300000 5655 TMS 05300000 Y IC 0
MYHUB:CMS GW 05300000 5655 TPS 05300000 IC 0
MYHUB:CMS GW 05300000 5655 TPW 05300000 IC 0
This example shows that application support for the OMEGAMON for CICS on z/OS and for
OMEGAMON for CICS TG on z/OS products has been installed successfully using the SDA feature.
To verify this action, see the STATE column for each component is IC (Install Complete), The
SEEDSTATE column at the hub Tivoli Enterprise Monitoring Server ( MYHUB:CMS) is Y (Yes) and the
STATUS column return code for each component is 0.
There are three components installed for both products identified by the ID column:
• Tivoli Enterprise Monitoring Server application support (TMS)
• Tivoli Enterprise Portal Server application support (TPS)
• Tivoli Enterprise Portal browser application support (TPW)
In this example, the application support installed is at the V5.3.0 base level (VERSION = 05300000).
Check that the version displayed matches the level you expect to see, particularly if you have applied
any maintenance to your monitoring agent.
If you have a remote Tivoli Enterprise Monitoring Server within your runtime environment, you should
see this similar output:
C:\ibm\ITM\BIN>tacmd listappinstallrecs -t CP

MYRTEMS:CMS CP 05300000 5655 TMS 05300000 N IC 0
MYHUB:CMS CP 05300000 5655 TMS 05300000 Y IC 0

Note that in this example, the remote Tivoli Enterprise Monitoring Server (MYRTEMS:CMS) in the
SEEDSTATE column the value of N (No). This is correct as the remote Tivoli Enterprise Monitoring
Server does not require seeding unlike the hub Tivoli Enterprise Monitoring Server. The self-describing
agent seeding has completed successfully because the STATE column shows the IC value. The TPS
and TPW support is also not stored at any remote Tivoli Enterprise Monitoring Server.
If there is a problem with the self-describing agent seeding support, it is shown in the STATE column.
The error displays a ME (Metadata Error).
C:\ibm\ITM\BIN>tacmd listappinstallrecs -t CP
For example:

MYHUB:CMS CP 05300000 5655 TMS 05300000 ME 1002
This example shows that application support failed for the Tivoli Enterprise Monitoring Server (TMS)
while it was successful for the TPS and TPW support. The STATUS column provides a reason code
for the error. In this example, the STATUS column shows 1002, which indicates a memory shortage
occurred during the installation process. After you correct this error within your system, you must
delete the installation record for the application; this causes the self-describing agent process to
restart if the agent is already connected or when it reconnects again.
To delete an installation record, issue the following command:
C:\ibm\ITM\BIN>tacmd deleteappinstallrecs -t CP -v 05300000 -n MYHUB:CMS
KUIDIR009I: The following records are going to be deleted:

HUB/RTEMS PRODUCT VERSION ID IDVER STATE STATUS
MYHUB:CMS CP 05300000 TMS 0530000 ME 1011
Are you sure you want to delete the selected records?
Type Y for yes. Type N for no.
KUIDIR005I: The selected install records were successfully deleted.
3. Log out from the hub Tivoli Enterprise Monitoring Server:
C:\ibm\ITM\BIN>tacmd logout
If problems persist with your installation using the self-describing agent, consider installing application
support directly using the application support DVD.
For further details on the self-describing agent or the tacmd command, see the Self-describing agent
feature in the Planning section of the OMEGAMON Shared Documentation.
Self-describing agent deletes all prior versions of the product

installation record
After the successful installation of the OMEGAMON for CICS on z/OS product, the self-describing agent
(SDA) tries to delete all the prior versions of the installation record, if any exist.
If there is no prior version installation record, the delete action returns a code of 79.
You might receive the following message during the SDA processing:
2011.264 17:00:24.57 (0002-E9A166E3:kfasdwlm.c,1961,"KFASDM_RequestMgr")

Self-Describing Install Completed Successfully for PRODUCT
2011.264 17:00:24.57 "CP", VER "05100173", ID "TMS", IDVER "05100173".
2011.264 17:00:24.57 (0003-E9A166E3:kfasdsrm.c,1531,"KFASDM_DeleteTapplpropLocal")
Open request for delete local TAPPLPROPS failed.
2011.264 17:00:24.57 status <79> product <CP> product version <05100173>
2011.264 17:00:24.57 (0004-E9A166E3:kfasdwlm.c,1976,"KFASDM_RequestMgr")
KFASDM_DeleteTapplpropLocal returned sqlStatus 79. product
2011.264 17:00:24.57 <CP> product version <05100173>
Chapter 3. Troubleshooting installation and configuration problems 17

The return code of 79 can be safely ignored.
A monitored system is displayed in the wrong place

In an environment with multiple hub Tivoli Enterprise Monitoring Servers, when the server and monitoring
agents are brought back down and then brought up, the monitoring agents forward data to the wrong hub
Tivoli Enterprise Monitoring Server.
The data is not where you expect to find it, either the Tivoli Enterprise Portal or the OMEGAMON enhanced
3270 user interface, yet the RKLVLOG output indicates that the monitoring agent is running.
If you see this situation, be sure that the runtime environment where the monitoring agent is running is
configured correctly. Check the sequence of protocols that the monitoring agent uses to connect to the
server and confirm that the correct values are provided for each protocol.
For OMEGAMON for CICS on z/OS and OMEGAMON for CICS TG on z/OS, you should check the globals and
XMIT IDs assigned to the monitored systems and ensure they match the monitoring agent. If they do not
match, then it will not be monitored. If no XMIT/Global is specified on the monitored system then it will be
monitored by an agent that does not have a XMIT/Global specified.
One or more CICS regions are not displayed on the interface; no

communication between the agent and the region
If one or more CICS regions do not show on the Tivoli Enterprise Portal navigation tree view or on the
OMEGAMON enhanced 3270 user interface, issue a command to the agent for each missing CICS region.
Issue the following command to the agent for each missing CICS region:
/f agent,OC START ID=TDA,CICS=cicsjobn
The command response is written in the RKLVLOG KCP0103: UNABLE TO MONITOR CICS
cicsjobn: RC=returncode. If the returncode is non-0, then see the Explanation area in this book for
the message and take the appropriate action. The following message is issued if the CICS region is being
monitored: KCP0107I: MONITORING CICS cicsjobn (PLEX cicsplex, NAME FROM xxxxxxx)
If you do not find this problem, it might be an IBM Tivoli Monitoring issue and would require further
investigation, for example, if all the missing CICS regions connect through one agent or one remote Tivoli
Enterprise Monitoring Server there might be a connectivity problem.
Another issue might be, when a CICS region that you want to monitor is running, but not showing up in the
Tivoli Enterprise Portal Server and there is no evidence of communication between the agent and CICS
region.
You must verify that the agent and CICS region are using the correct RKCPXM DD cards. If the cards do not
match, the agent does not monitor the CICS region.
For example, you might notice an erroneous node on the Navigator Physical tree view in your Tivoli
Enterprise Portal under the parent CICS node. The node might say, for example, CP IRA MANAGER and
have a child node nested underneath with the name of the RKCPXM DD card (RKCPXM03:SYS_CPIRA).
This occurs when you use mismatched RKCPXMD DD cards in the CICS region and the monitoring agent.
Verifying CICS region status with a situation in the Tivoli

Enterprise Portal
You can create a situation to verify the status of the CICS region in the Tivoli Enterprise Portal.
When you create the situation, select the CICSplex Region Overview attribute group and the CICS Region
Name and Region Status attributes. Set the value of CICS Region Name to the region name to verify (or do
not select this attribute if you want to monitor all CICS regions). Set the value of Region Status to inactive.
Distribute the situation to *MVS_CICS.

See the topic on creating a situation in the Tivoli Enterprise Portal online help.
The CICSTG_Health_Critical situation is triggered persistently for a

monitored CICS TG
While there may be several reasons why this situation is being triggered on a persistent basis, one
possibility is that the Stats API port is either specified incorrectly in the OMEGAMON for CICS TG on
z/OS component configuration, or the CICS TG configuration file (ctg.ini) does not have the Stats API port
enabled.
Ensure the Statistics API (statsapi) protocol is enabled in the CICS TG configuration file and note the
hostname/IP address and port number. Verify that your OMEGAMON for CICS TG on z/OS configuration
matches the specified hostname/IP address and port number for the monitored CICS TG. This is found in
the KGWSAPIP member of the &hilev.RKANPARU library.
The CTGSTATS module failed for the OMEGAMON for CICS TG agent
When attempting to start the OMEGAMON for CICS TG on z/OS monitoring agent a series of CEE dumplets
and SYSOUT output might appear.
The following messages are what is displayed from this symptom:
• CEE3501S The module CTGSTATS was not found.
To correct this problem, add the CICS TG DLL (for example, CTG.V9R0M0.SCTGDLL) to the STEPLIB
concatenation of the affected monitoring agent.
• CEE3512S An HFS load of module CTGSTATS failed.
This error message was caused by HFS system errors in a sysplex environment. To confirm this issue,
verify the syslog for HFS errors:
FILE SYSTEM OPERATIONS ARE DISABLED UNTIL UNMOUNT AND MOUNT

*IGW027E HFS HFS_dataset_name
SYNC WRITE-PROTECT ERROR. RC=00000024 RSN=5B26000D
Unmount and remount the offending HFS data set or contact USS Systems Support.
Orphaned CICS TG transactions remain in active transaction

workspaces
Under some conditions, the Active Transactions (KGWTRNO) and CICS TS Server Details (KGWCTSD)
workspaces in the OMEGAMON enhanced 3270 user interface and the Active Transaction Details
workspace in Tivoli Enterprise Portal continue to report in-flight transactions that have completed and
should be removed.
Occasionally, the CICS TG may not inform OMEGAMON that a transaction has completed, and the agent
is unaware that it should remove the transaction record from the active transactions table. We refer
to this as an orphaned transaction record. The likely cause of an orphaned transaction is an abnormal
termination of a flow, such as a client application disconnecting from the CICS TG when CICS resources
are pending changes and no commit or roll-back call is made. These "orphaned" transactions have no
further flows associated with them, but they remain in the workspaces with ever-increasing elapsed times
that skew the calculations of other statistics about active transactions.
How do you identify an orphaned transaction? If you were monitoring a CICS TG region where, for
example, a transaction for program name EC01 was running and you navigated to CICS TS Region Details
workspace and looked at the Active Transaction subpanel, you might find that this subpanel displayed
one row describing the in-flight transaction. However, after the transaction ends, you would expect the
CICS TS Region Details workspace Active Transaction subpanel to no longer show the transaction. Instead
you find that the transaction name is still displayed. Other transactions by the same program might be
added and then disappear as expected, but the original transaction remains. Even after cancelling the

CICS region, the transactions remain listed as in-flight as part of the Active Transaction subpanels. The
transaction continues to be displayed as long as CICS TG is active. Figure 1 on page 20 shows such
orphaned transactions:
Figure 1. Transaction Analysis workspace showing likely orphaned transactions in the Active Transactions
subpanel
In this example, it may be reasonable to assume that these transaction records have been orphaned
because of the excessively long Elapsed Time value. These transaction records have not been removed
because the current sweep policy has not yet identified them as orphaned. Either this is because a check
has not taken place (as defined by by the sweepInterval JVM property) or the last known flow of the
transaction occurred more recently than the timeout limit for sweeping (defined by the sweepTimeout
JVM). If you check the RKLVLOG, you would find this message:
KGWRM1028I - Orphaned transaction sweep timeout set to {0} minutes

KGWRM1029I - Orphaned transaction sweep interval set to {1} minutes
where {0} and {1} represent the currently defined values for the sweep policy.
If you see too many reported active transactions that you are certain have really completed, it means
that the values defining the policy need to be adjusted. Either sweepInterval needs to be increased
because the sweep processing occurs too infrequently, or sweepTimeout needs to be reduced to a lower
value. See "Defining a policy to periodically sweep away any orphaned transactions" in the OMEGAMON
for CICS on z/OS: Planning and Configuration Guide for more information about updating the orphaned
transactions sweep interval and timeout.

Historical workspaces in Tivoli Enterprise Portal contain no data
If historical collection is not enabled and the historical workspace does not contain data, operators see
message KFWITM220E Request failed during execution displayed in the Tivoli Enterprise Portal
message area.
Use the information found in the Tivoli Data Warehouse solution topics in the IBM Tivoli Monitoring:
Installation Guide to configure historical data collection and retry the operation.
U200 Port in use message found in the RKLVLOG output, indicating

an incorrect default port for TCP/IP profile
After you have completed all installation and configuration of a monitoring agent and try to start the
agent, you might find a "U200 Port in use" abend message in RKLVLOG, indicating a connection failure.
One possible cause of this problem is when the port defined for communication among the Tivoli
Management Services components was reserved for a different application in the PORT statement of
your TCP/IP profile.
If this is your problem, follow these steps:
1. Verify that the existing port reservation is no longer needed or choose a different port for
communication among the Tivoli Management Services components.
2. Edit your TCP/IP profile to reserve the port for the Tivoli Enterprise Monitoring Server stated procedure
or change your configuration (Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring Server, and
monitoring agent) to communicate with the Tivoli Enterprise Monitoring Server on a different port.
3. Stop, and then start the started task affected by your configuration change.

Chapter 4. Troubleshooting usage problems
This information describes problems and useful settings with the usage of OMEGAMON for CICS on z/OS.
Analyzing the OMEGAMON CICSplex configuration

When an OMEGAMON for CICS on z/OS agent detects a CICS region is online, it searches through the
CICSplex classification rules for the first rule that matches attributes of the CICS region.
These are the attributes of the CICS region that are used for matching in CICSplex classification rules:
• JOBNAME
• SYSPLEX ID
• SMF ID
• VTAM® APPLID
• GENERIC APPLID
• XCF GROUP NAME
If the first matching rule exists and has a PLEXNAME value other than OMEGPLEX, then the OMEGAMON
for CICS on z/OS agent uses the PLEXNAME value as the CICS region's CICSplex name. Otherwise, the
agent uses the CICSplex name that is supplied by CICSPlex® System Manager.
If CICSPlex System Manager is not running, then the agent uses the OMEGPLEX CICSplex name default
setting. When an agent uses a particular CICSplex name initially, that CICSplex name becomes known to
the agent. If the CICSplex name is not known to any other agents, then the agent registers the CICSplex
as an IBM Tivoli Monitoring managed object.
You can use the following OC commands to analyze the OMEGAMON CICSplex configuration:
• OC STATUS,CICSPLEX
• OC DISPLAY,PLEX=cicsplex
• OC DISPLAY,PLEXRULES
• OC DISPLAY,PREFERENCES
OC STATUS,CICSPLEX command
You can issue a command to determine which CICSplex groups are known by the OMEGAMON for CICS on
z/OS agent and the status of each one.
Issue the following command:
/F agent,OC STATUS,CICSPLEX
This command generates the output in the RKLVLOG similar to the following example:
KCP9030: ATC PROCESSING THE FOLLOWING COMMAND:

STATUS,CICSPLEX
KCP9329I: DISPLAYING INFORMATION FOR CICSPLEX CICSPLX1:
KCP9330I: ORIGIN NODE: CICSPLX1::CICSplex
KCP9331I: NUMBER OF CICS REGIONS: 1
KCP9332I: REGISTERED BY THIS AGENT: NO
KCP9332I: REGISTERED BY THIS AGENT: YES
In this example, CICSplex CICSPLX1 and CICSPLX2 are known by the agent. This agent has one active
CICS region in the CICPLX1 CICSplex. The IBM Tivoli Monitoring managed object name for CICSPLX1 is
CICSPLX1::CICSplex. The CICSPLX1 CICSplex was registered by another agent. The CICSPLX1::CICSplex
managed object was defined to IBM Tivoli Monitoring by another agent. The CICS agent has two

active CICS regions in the CICPLX2 CICSplex. The IBM Tivoli Monitoring managed object name for
CICSplex CICSPLX2 is CICSPLX2::CICSplex; the CICSPLEX CICSPLX2 was registered by this agent. The
CICSPLX2::CICSplex managed object was defined to IBM Tivoli Monitoring by the agent that is being
queried.
To determine which CICS regions an agent has active in a particular CICSplex, use the “OC
DISPLAY,PLEX=cicsplex command” on page 24, where cicsplex is the name of your CICSplex. For
example, issue the following command to determine which CICS regions the agent has active in CICSplex
CICSPLX2:
/F agent,OC DISPLAY,PLEX=CICSPLX2
You can use this command and the “OC DISPLAY,PLEXRULES command” on page 24 to determine why a
CICS region is assigned to a particular CICSplex.
OC DISPLAY,PLEX=cicsplex command
You can issue a command to display the status of a particular CICSplex and list the active CICS regions in
the CICSplex.
Issue the following command:
/F agent,OC DISPLAY,PLEX=cicsplex
For example, a valid OC DISPLAY,PLEX=CICSPLX2 command generates the RKLVLOG output similar to
the following example:

DISPLAY,PLEX=CICSPLX2
KCP9332I: REGISTERED BY THIS AGENT: NO
KCP9333I: LISTING CICS REGIONS IN CICSPLEX CICSPLX2:
KCP9334I: JOBNAME CICSRGN1, PLEX NAME FROM CPSM
KCP9334I: JOBNAME CICSRGN2, PLEX NAME FROM OMEGAMON
In this example, the OMEGAMON for CICS on z/OS agent has two active CICS regions in CICSplex
CICSPLX2: CICSRGN1 and CICSRGN2. In the KCP9334I message, the source value of CPSM indicates that
the CICSRGN1 jobname was assigned to CICSplex CICSPLX2 by CPSM. The second KCP9334I message,
lists the source value of OMEGAMON, which indicates that the CICSRGN2 jobname was assigned to
CICSplex CICSPLX2 by the CICSplex classification rules. A third possible source value in the KCP9334I
message is DEFAULT, which indicates that the default CICSplex name of OMEGPLEX was used because
neither CPSM nor the CICSplex classification rules assigned a name.
OC DISPLAY,PLEXRULES command
You can display the rules that the OMEGAMON for CICS on z/OS agent is using to assign CICSplex names
to CICS regions by issuing a command.
Issue the following command to assign CICSplex names to CICS regions:
/F agent,OC DISPLAY,PLEXRULES
This command generates output in the RKLVLOG output similar to the following example:

DISPLAY,PLEXRULES
KCP9337I: DISPLAYING THE CICSPLEX NAME RULES:
KCP9338I: PLEXNAME JOBNAME SYSPLEX SMFID APPLID GAPPLID XCFGROUP
KCP9339I: CICSPLX1 CICSM* SYSPLEX1 SYSA CICS* TST* *
KCP9339I: CICSPLX2 CICSRGN2 * * * * *
KCP9339I: CICSPLX3 * * * * TSTGAPPL *
KCP9339I: CICSPLX4 * * * * * XCRGRP01
KCP9339I: OMEGPLEX * * * * * *

In this example, there are four CICSplex classification rules that the OMEGAMON for CICS on z/OS agent
searches for in the order listed by the KCP9339I messages:
• CICSPLX1
• CICSPLX2
• CICSPLX3
• CICSPLX4
• OMEGPLEX
The first classification rule indicates that the CICS region is assigned to CICSPLX1 CICSplex, if the
following attributes match:
• JOBNAME must begin with CICSM
• SYSPLEX ID must be SYSPLEX1
• SMF ID must be SYSA
• VTAM APPLID must begin with CICS
• GENERIC APPLID must begin with TST
The second classification rule indicates that the CICS region is assigned to CICSPLX2 CICSplex only if the
first attribute matches; the JOBNAME must be CICSRGN2 .
The third classification rule indicates that the CICS region is assigned to the CICSPLX3 CICSplex, only if
the GAPPLID attribute matches; the generic APPLID must be TSTGAPPL.
The fourth classification rule uses the CICSplex name supplied by CPSM regardless of the CICS region's
attributes. The OMEGAMON for CICS on z/OS agent assigns a CICS region with a JOBNAME of CICSRGN1
to the CICSplex since this rule is the first matching rule. The agent assigns a CICS region with a JOBNAME
of CICSRGN2 to the CICSPLX2 CICSplex because the second rule is the first one that matches.
The final classification rule indicates that the CICS region is assigned to the CICSPLX4 CICSplex, if and
only when the XCFGROUP attribute matches; the XCFGROUP must be XCFGRP01 .
OC DISPLAY,PREFERENCES command
You can display the criteria used to select the preferred agent to monitor a given CICSplex by issuing a
command.
Issue the following command against any OMEGAMON for CICS on z/OS agent address space that is part
of your monitoring runtime environment:
/F agent,OC DISPLAY,PREFERENCES
This command generates output in the agent’s RKLVLOG output similar to the following example:

DISPLAY,PREFERENCES
KCP9341I: DISPLAYING THE CICSPLEX AGENT PREFERENCES:
KCP9342I: PLEXNAME SMFID XM TIMEOUT
KCP9343I: *DFLT * * 5
KCP9343I: TESTPLEX SYST 11 NO
KCP9343I: PRODPLEX SYSP 15 5
In this example, there are preferences defined specifically for two CICSplexes, TESTPLEX and PRODPLEX,
plus a default set of criteria, named *DFLT, that will be used to select the agent that should report
CICSplex-level information and samples data for short-term historical collection about the CICSplex. The
attributes specify the LPAR and XM number of the preferred agent to monitor the given CICSplex. There
is also a timeout attribute that indicates how long the monitoring environment will wait for the preferred
agent to come online before any other online agent within the environment can assume responsibility
for monitoring this CICSplex. The timeout value is specified in minutes, or can be NO, indicating the wait
period should never time out and that only the preferred agent should be used to monitor this CICSplex.
Chapter 4. Troubleshooting usage problems 25

The preference for the TESTPLEX CICSplex is the agent found on the SYST LPAR identified with XM
number 11. PRODPLEX's preferred agent can be found on the SYSP LPAR with XM number 15. PRODPLEX
will wait for up to 5 minutes for its preferred agent to come online, while TESTPLEX will wait indefinitely.
The default set attributes apply to all CICSplexes that do not have a specific preferred agent defined;
these indicate that any agent on any LPAR can be used as the monitor of a new CICSplex.
When a new CICS region is detected by an agent within the monitoring environment, it is immediately
classified into a CICSplex. If this is the first region within this CICSplex to be monitored, a check is
made against this table to determine which agent should be the preferred collector of CICSplex-level
information. If that agent is online within this runtime environment, it is selected. If not, the timeout
period begins, which, if exceeded and the preferred agent is not online, allows any other online agent
within your environment to assume responsibility for monitoring this CICSplex. Once an agent has
assumed responsibility for monitoring a given CICSplex, it will continue to do so provided it remains
online, even if the originally preferred agent later comes online.
The CICSplex agent preferences can be updated through the enhanced 3270 user interface.
Problems with SLA Batch Utility

You might experience the following problems with the SLA Batch Utility (kcp_slabatch).
The DTD file cannot be found in the same folder as the XML file
The kcp_slabatch utility uses the kcp_slabatch.dtdfile to validate the structure of the XML document
prior to importing the definitions.
By default, the path to the kcp_slabatch.dtd file is found in the same folder as your XML file. If
the DTD file cannot be found at this location, then validation cannot take place and updates to the SLA
definitions cannot take place. If this occurs, the following message is written to the log:
KCPSB1011E: Unable to read or write XML file: C:\test\kcp_slabatch.dtd

(The system cannot find the file specified.)
The path specified in the log message indicates where the kcp_slabatch utility thinks the DTD file should
be found.
To correct this issue, perform one of the following actions:
• Copy the DTD file into the same folder as your XML file that you are trying to import. The DTD file is
found in the same folder as the kcp_slabatch utility script.
• Edit the XML file to point at the correct location of the DTD file. The second line of your XML document
needs to be changed with the path value inserted within the double-quotes. For example:
<!DOCTYPE CicsSlaDefinitions SYSTEM "C:\IBM\ITM\CNP\kcp_slabatch.dtd">
After you edit your XML document, save it, and run the kcp_slabatch utility again.
The SLA definitions that you are trying to import are always rejected
If the SLA definitions that you are trying to import are always rejected, check the log file for validation
messages.
Check the log file for any of the following messages. These messages indicate that the XML format
supplied in the input file is not correctly formatted and has been rejected before the kcp_slabatch utility
attempts to make changes to the current definitions.
• KCPSB2040E XML Validation Error at line: {0}. Message: {1}
• KCPSB2041E XML Validation Fatal Error at line: {0}. Message: {1}
• KCPSB2042W XML Validation Warning at line: {0}. Message: {1}
The values for {0} and {1} provide details for the initial problem and suggest where the changes are
needed. The kcp_slabatch utility uses the Document Type Definition (DTD) to interpret the XML structure,

you can also use the DTD before you run the utility to verify that you have a valid XML format for the task.
Load your XML document into a text editor that has the ability to verify XML, or, if this is not available,
open the XML document within a web browser. If the full XML is displayed without an error, then you can
import it using the utility. The DTD file (kcp_slabatch.dtd) must be located locally to your XML file for
this test. Copy the XML file to the same folder as the DTD file (usually found in the Tivoli Enterprise Portal
installation folder) or copy the DTD file to your current folder with your source XML file. Alternatively, you
can edit the path to the DTD file at the beginning of the XML file:
<!DOCTYPE CicsSlaDefinitions SYSTEM "kcp_slabatch.dtd">
The aforementioned line appears in the second line of the XML document. If this line is missing, add it,
and attempt to import the document again.
The correct Java version is not found

The SLA Batch Utility requires Java version 6.0 or higher to be used with this utility; this Java version
should be installed as part of your IBM Tivoli Monitoring installation process.
If the version is working correctly, the version number is displayed on the console when the utility starts.
For example:
Using Java Release: 1.6.0

Java Home = C:\Program Files\IBM\Java60\jre
IBM Z OMEGAMON for CICS - SLA Command Line Utility
(C) Copyright IBM Corporation 2013. All rights reserved.
If you have configured the Java runtime environment correctly or if you have multiple Java runtimes
installed, the wrong Java level might be used. To fix the version level of Java for a specific release use
these steps:
1. Open the kcp_slabatch.bat (Windows) or kcp_slabatch.sh (UNIX or Linux) file in a text editor.
2. Find the section near the beginning of the file where the environment variable TEP_JAVA_HOME is
declared and uncomment this line.
3. Specify the path to the bin folder of the Java runtime environment you want to use.
4. Save the file and retry it using the utility. Comment the line out again, if you wish to revert back to your
Java runtime environment.
SLA definitions cannot be imported or exported

You must have permission to export existing definitions or import updated definitions.
If you do not have permission, the following log message might be displayed in the log:
KCPSB1069E: User not authorized to make SLA updates.
In order to have authorization, you must have an ID that is defined on the Tivoli Enterprise Portal Server,
the SLA Batch Utility (kcp_slabatch utility) that it is connecting to, and that ID must have permission to
view the CICS SLA view. To assign the view, logon as an administrator to the Tivoli Enterprise Portal client
and open the Administer Users dialog; select the user ID and assign it to the CICS SLA view. When you
retry the import or export functions, you see the following message in the log:
KCPSB1068I: User has permission to view or modify SLA definitions.
The log file cannot be found

Basic logging is provided to the console running the SLA Batch Utility (kcp_slabatch utility) unless you
select the no output option and the full logging is written to a file on every invocation of the utility.
The default location of the log file is determined by the environment variables set by you or the IBM Tivoli
Monitoring installation. The following environment variables are verified in the following order:
Chapter 4. Troubleshooting usage problems 27

• ITMHOME
• CANDLE_HOME
• CANDLEHOME
If any of these variables are found, the log is displayed in the logs subfolder, in the location that is
identified by the environment variable. For example, C:\IBM\ITM\logs. If no variables are located, then
the current working folder, where the SLA Batch Utility started from, is used and the following message is
displayed at the start of the log:
KCPSB2043W: No ITMHOME/CANDLE_HOME/CANDLEHOME directory found.

Using current working folder: {0}
To change the folder that you want to write the log output to, set the ITMHOME environment variable to
a new value; avoid changing either the CANDLE_HOME or CANDLEHOME variables, if already set, because
this might affect the functioning of other IBM Tivoli Monitoring applications.
The only situation where the full log output is not written to a file is when the utility does not have
permission to write to the file system. If this occurs, the following message is written to the log:
KCPSB1010W: Unable to create log file: {0}
The full log output is written to the console regardless of whether you specified no output option or not. To
fix this issue, ensure the SLA Batch Utility is writing to a viable location, that it has the correct permission,
or contact you system administrator.

Chapter 5. Tivoli Enterprise Portal - based issues
You might experience the following problems with the Tivoli Enterprise Portal with regard to logon and
terminal emulator concerns.
Cannot log on to Tivoli Enterprise Portal with valid user ID and

password
When you log on to Tivoli Enterprise Portal, a valid user ID and password combination is rejected. If you
provided a correct user ID and password, you should try these instructions.
Although Integrated Cryptographic Service Facility (ICSF) provides robust password encryption, you are
not required to use it because the ICSF affects compatibility with the z/OS OMEGAMON XE monitoring
products.
The following messages are displayed when the portal server cannot connect to the monitoring server:
Call to KLE_CryptoGetFP failed with exit code 8.

Cannot get CSNBXAE function pointer
Logon validation did not complete - system error.
User:username keyfile:key ip:ip_address
If you see these failed connection messages, perform the following steps so that the Tivoli Enterprise
Portal Server can connect to the Tivoli Enterprise Monitoring Server.
To reconfigure using PARMGEN, do the following:
1. Locate the configuration profile for this instance of the monitoring agent.
2. In the configuration profile, locate the following KDS_TEMS_SECURITY_KDS_VALIDATE parameter
and set the value to N. Save the configuration profile.
3. If you change any of these values, you must update the configuration values in the RTE.
After the Tivoli Enterprise Monitoring Server configuration is complete and the server is running, you must
modify the portal server configuration to use an older, less robust encoding algorithm by performing the
following steps:
1. Edit the kfwenv file, for Windows, install_dir\CNPS (where install_dir is C:\IBM\ITM by default) using a
text editor.
On Linux/UNIX, you must edit the <ITM Home>/<OS Specific Folder>/cq/bin/<OS name>env file. (For
example, on Linux for System z: /opt/IBM/ITM/ls3263/cq/bin/lnxenv). The following steps are the
same.
2. On a line by itself, enter the following text:
USE_EGG1_FLAG=1
3. Save the file and exit.

4. Stop the Tivoli Enterprise Portal Server, if it is running, and start it again.
Cross-product links are missing from the link list

Cross-product workspace links are displayed in the link list, if the product workspace you are linking to
has been installed and your Tivoli Enterprise Portal user ID is authorized to access the target product.
If a cross-product link is missing from the link list, contact your system administrator to verify that the
following items exist:
• Your user ID is authorized to access the target product.

• Product help files, workspaces, and situations are installed using the self-describing agent feature or
manually using IBM Tivoli OMEGAMON Application Support Files for z/OS DVD.
A link to a terminal emulator session fails

If a link to a terminal emulator session fails, there are several techniques to use in order to resolve the
problems with context sensitive linking to 3270 interface workspaces. The initial step is to ensure that
your environment is suitable for the links to function.
The following conditions must exist for the scripts to function:
• IBM Tivoli Monitoring and the Tivoli Enterprise Portal must be at V6.2.1 or higher. If you are not running
the correct version, then the Tivoli Enterprise Portal client is unable to prompt the user for the user ID
and password or provide the necessary values to the script.
• The OMEGAMON for CICS level for both the monitoring agent and the product support on the Tivoli
Enterprise Portal must be at least V4.1.0 with Interim fix pack 4. If the agent is back level then the
agent does not have the correct version of the Service Task Details query and the Tivoli Enterprise Portal
is not able to query the agent for the connection values.
• The OMEGAMON for CICS (3270) session must be reachable by the terminal emulator session over a
non-encrypted connection. The terminal emulator does not support encrypted connections at this time.
• The logon panel that is displayed when the terminal emulator first connects to the host must support
the entry of the command to log in to the OMEGAMON 3270 session for the product-provided scripts to
function properly. Modified scripts can be created to handle alternative initial terminal emulator panels.
If you satisfy all of the previous noted conditions and the scripts still fail, you must investigate further.
See the "Managing workspaces" topic in the IBM Z OMEGAMON for CICS: User's Guide for more details on
3270 linking, queries, and scripts.
If you are not prompted for a user ID and password when a link is executed, then the Tivoli Enterprise
Portal client is not the correct version or there should be an error message displayed that describes the
problem. If you are prompted for a user ID and password, but the terminal emulator fails to connect to
the host, then it is necessary to verify that the correct host name and port are being used; these are auto
discovered by the Service Task Details query. If the host name and port have not been specified during
configuration, but in certain network configurations, the values returned might not be correct. These
values are displayed in the user ID and password dialog, and you can modify them there if they are not
correct. If the terminal emulator session connects to the host, but fails to display the correct OMEGAMON
3270 workspace, then it might be necessary to check and potentially modify the script being driven by the
terminal emulator session.
A terminal emulator script fails

If a script to a terminal emulator session fails, there are several techniques to use in order to resolve the
problem. The most useful resource available when debugging a script is the description of the scripting
language and the editing function in the online help. See the Tivoli Enterprise Portal online help for further
details on the terminal emulator script.
You can comment- out the hide() call at the start of the script; this hides the terminal emulator screen
while the script is running. The values that are retrieved from the query (including the user ID and
password) are read by the script using the getProperty() command. For example:
APPLID = getProperty("TRM_QUERYKOCCIAPPL");
If this command fails to return the expected values, then the script does not run successfully.
Another useful technique is to add msgBox(…) function calls to the script. These calls stop the script from
running and prompt you with some text. These calls can be used to check values in the variables while
the script is running, and to stop processing at a key moment so that the data on screen can be checked
against expectations.

See the Managing workspaces topic in the OMEGAMON XE for CICS on z/OS: User's Guide for more details
on 3270 linking, queries, and scripts.
Chapter 5. Tivoli Enterprise Portal - based issues 31

Chapter 6. Problems with Service Level Analysis
You might experience the following problems with the Service Level Analysis feature.
KCP0215: UNABLE TO OBTAIN RECORD CELL, DATA LOST

The appearance of message KCP0215 in the RKLVLOG is an indication that the WLM subtask does not
have sufficient storage in the dataspace to process all the records being sent to it.
To resolve this issue, edit the KC5AGST member of the RKANCMDU data set and increase the dataspace
size:
OC START ID=WLM or
OC START ID=WLM,BLOCKS=nnn
You increase the dataspace size by adding the BLOCKS=nnnnnn parameter or increasing the existing
BLOCKS=nnnnnn, where nnnnnn is a value between 10 and 524287. The default setting is BLOCKS=2048.
You can display the current value for the BLOCKS parameter by using the F agent,OC
STATUS,WLMBLOCKS command in order to display it in the RKLVLOG output.
Start with a BLOCKS= value of 2560. If this is too small, increase the size by 256 until the problem is
resolved.
If you want to change the dataspace size, stop and restart the WLM subtask:
/F agent,OC STOP ID=WLM

/F agent,OC START ID=WLM,BLOCKS=2560 << Increase by 256 each time
You might also see message KCP0244: WSR - UNABLE TO OBTAIN ACCUMULATION BUFFER, DATA
LOST if the workload summarizer subtask is unable to obtain sufficient storage for the transaction volume
it is currently receiving from CICS address spaces. If this occurs, you should also consider increasing the
dataspace size.
KCP0243: WSR WAITING FOR WORKLOAD DEFINITIONS

The KCP0243 message means the workload summarizer subtask is waiting for workload definitions. This
usually means that application support has not been installed.
The workload definitions are stored in the RKCPDEFW file on the hub Tivoli Enterprise Monitoring Server
(Hub TEMS) and sent to the IBM Z OMEGAMON for CICS agent when required. The RKCPDEFW file is built
by the installation process when application support for IBM Z OMEGAMON for CICS is added to the Hub
TEMS. If message KCP0243 appears, it usually means that application support was not installed. If this is
the case, install application support, or enable self-describing agent (SDA) processing:
• To install application support, see Installing and enabling application support and Adding application
support to a monitoring server on z/OS in the OMEGAMON shared documentation.
• To enable SDA, see Enabling the self-describing agent.

Chapter 7. Miscellaneous problems
These are miscellaneous problems that might affect the KILL ICE command, SQL queries, Summarization
and Pruning and cross product linking.
The KILL ICE command fails for a member on the ICE Chain in the
3270 environment and produces the OC3432 message
If you have Interval Control Elements, (ICE) that are in a WAIT state and were issued by a transaction
that waits for the ICE to expire before continuing processing and you killed the ICE, it would leave the
transaction waiting indefinitely for the ICE process to complete.
Clean up would be difficult because you would be required to trace back and backout anything previously
touched by the initial transaction. This would be a costly process and vulnerable to errors. A better way to
get rid of such an ICE issue would be to cancel the transaction that caused the creation of the ICE initially,
therefore reducing the expiration time for the ICE.
The KFWITM081E message is displayed when attempting to link to

another product workspace
Many of the OMEGAMON XE products include predefined links to Tivoli Enterprise Portal workspaces that
are provided by other products. The KFWITM081E message is displayed whenever you try to link to a
workspace that does not exist. You receive this message if the target product's workspaces have been
installed but the monitoring agent responsible for retrieving data for the target workspace is not running.
After Tivoli Enterprise Portal workspaces are installed, all predefined links to the workspaces become
enabled, meaning that links to the target workspaces will be included in the link list when an operator
uses the link icon on a row.
If you installed the application support for products that you are not monitoring within your environment,
links to these products are displayed as valid destinations for dynamic cross-product links.
Note: It is not likely that all OMEGAMON XE monitoring agents will be running on all z/OS systems
being monitored. In such cases, the KFWITM081E message does not necessarily indicate a problem. For
example, if you are monitoring two z/OS systems and only one of the z/OS systems is running DB2®, you
will most likely have the IBM Z OMEGAMON for CICS monitoring agent running on both systems, but the
OMEGAMON for DB2 monitoring agent will be running only on the system where DB2 is installed. Because
you are running both OMEGAMON XE products, you install help files, workspaces, and situations for both
products, which enables the links to both products. As a result, if you try to perform a cross-product
link to the OMEGAMON for DB2 workspace on the system where the OMEGAMON for DB2 product is not
running, you receive the KFWITM081E message.
SQL queries to Tivoli Data Warehouse fail because of invalid

column name
When you are writing a Structured Query Language (SQL) query against Tivoli Data Warehouse (without
using the Tivoli Enterprise Portal) where your database manager is DB2 or Oracle, the query sometimes
fails, indicating that the column name is invalid.
The cause of this problem might be that your column name is greater than 30 characters in length, and
DB2 and Oracle do not support column names greater than 30 characters.
The warehouse proxy creates the table with the abbreviated column names. These abbreviations are
shown in the WAREHOUSEID database table.

Additionally, column names which seem to meet the fewer than 30 characters rule might also fail when
the summarization and pruning agent is used, because this agent adds a four-character prefix to the
column name (for example, AVG_).
To avoid this problem, revise your SQL queries to match the abbreviated column names in the
WAREHOUSEID table.
Summarization and Pruning does not function as described

If the hub Tivoli Enterprise Monitoring Server on the z/OS system is located on a different computer than
the Tivoli Enterprise Portal Server or if the IBM Z OMEGAMON for CICS monitoring agent is not configured
in the same SMP/E CSI (Consolidated Software Inventory) as the hub Tivoli Enterprise Monitoring Server,
you must enable summarization and pruning manually.
To enable the Summarization and Pruning Agent to run against OMEGAMON XE for CICS on z/OS
tables in the Tivoli Data Warehouse, you must install the catalog and attribute data files on the Hub
Tivoli Enterprise Monitoring Server on z/OS. These files are not automatically installed on a Hub Tivoli
Enterprise Monitoring Server if that component is located on a different computer than the Tivoli
Enterprise Portal Server.
There are several ways you can do this; here is one way.
Copy the following members from the SMP/E Target libraries where the IBM Z OMEGAMON for CICS
monitoring agent has been installed and configured to the RTE where the hub Tivoli Enterprise Monitoring
Server is installed:
• TKANDATV (KC5ATR)
• TKANDATV(KC5CAT)
• TKANPAR (KC5PDICT)
When you complete these steps, restart your hub Tivoli Enterprise Monitoring Server.
Summarization and Pruning agent fails to run as scheduled

The summarization and pruning agent provides the ability to customize the length of time to save data
(pruning) and how often to compress data (summarization).
This agent is configured to determine how much data you summarize and how often you perform
this space-saving operation. For more information about this agent, refer to the IBM Tivoli Monitoring:
Administrator's Guide.
If the summarization and pruning agent fails to run on schedule, it is possible that the
UADVISOR_KSY_ENABLE situation is not started on the hub Tivoli Enterprise Monitoring Server. You can
determine if this is your problem if you search the RKLVLOG output for the Tivoli Enterprise Monitoring
Server on z/OS, and fail to find the UADVISOR_KSY_ENABLE situation.

Chapter 8. Troubleshooting data collection problems
This information describes problems that might be associated with the collection of data by OMEGAMON
for CICS monitoring agents.
Using OMEGAMON for CICS (3270) to collect screen logs

An IBM Software Support request for diagnostics might include screen logging.
Use these steps to collect the screen logs using OMEGAMON for CICS (3270):
1. From the OMEGAMON II for CICS (CUA) interface Region Status (KC2B01D6 or KC2B01D7) screen,
enter: GZ.
2. Press enter when the KC2ZOOM screen is displayed; go to the ZMENU display.
3. From the ZMENU display, enter P.H.B. ; this activates OMEGAMON for CICS (3270) logging.
4. Click PA2 to return to the Region Status display.
5. Recreate the problem and take any screen shots that are needed.
6. Enter GZ to zoom to OMEGAMON for CICS (3270) interface again.
7. When you are at the ZMENU screen, enter P.H.C.; this turns off OMEGAMON for CICS (3270) logging.
8. Click PA2 to return to the Region Status display.
The logged output spools to a sysout, DDNAME SYSnnnnn allocated to your OMEGAMON for CICS (3270)
STC. Start with the last DDNAME spooled out and browse it looking for the output from the preceding
process.
Monitoring agent cannot insert all requested data rows into the
persistent data store
Failure to write data to the persistent data store can indicate a number of problems that sometimes
appear to be tuning problems. Other possible causes could be performance issues.
The problem also occurs if the persistent data store is full. If this is the problem, then log messages are
displayed showing problems with components prefixed by KPD or KPX in the RKPDLOG sysout data set.
These prefixes indicate problems with the persistent data store.
To determine if the persistent data store files (Short Term History) are full complete the following steps.
1. From the TSO SDSF log enter the following commands against your OMEGAMON for CICS on z/OS
Tivoli Enterprise Monitoring Agent job (for example, IBMC5):
/F IBMC5, KPDCMD QUERY CONNECT

/F IBMC5, KPDCMD QUERY DATASTORE
2. Examine the RKPDLOG output.
a. To examine the RKPDLOG output, from the TSO SDSF Status panel (ST) or Active users panel (DA),
enter a question mark (?) next to the name of the agent job (for example, IBMC5). This action
causes the RKPDLOG to be presented.
b. Enter S next to the RKPDLOG entry to view the contents.
c. Scroll to the end of the RKPDLOG to see the output of the QUERY command and determine if the
RKC5HIS* files are full.
CPU usage and memory usage might increase in the z/OS address space where the persistent data store
stores data, this can be the monitoring agent address space or the Tivoli Enterprise Monitoring Server
address space depending upon which location was selected to store history.

Monitoring agent running out of storage
If response time is slow on the monitoring agent, check the RKLVLOG output for indications about a
possible storage problem.
A storage usage event might be generated every hour and written to the RKLVLOG output. Typically the
STORAGE command is used in conjunction with the EVERY command to schedule period issuance of the
STORAGE command.
The KC5AGST and KGWAGST members of the &hilev.RKANCMDU library have the following line by
default:
EVERY 00:60:00 STORAGE D * LOG STORAGE USE
Where:
EVERY
Is a command that is used to schedule another command for periodic execution.
00:60:00
Shows the hours, minutes, and second. A value of 00:60:00 says run this command every 60 minutes.
STORAGE
Displays statistics of TMS:Engine storage usage.
D
Stands for Detail. STORAGE provides both primary and extended storage statistics. This information is
helpful in tuning TMS: Engine memory management.
The default entry causes the STORAGE D command to be issued every 60 minutes. The interval where the
command is automatically issued is defined during the Tivoli Enterprise Monitoring agent configuration
with the KDS_TEMS_STORAGE_DETAIL_INT_HR parameter in PARMGEN.
If the monitoring agent is already running with storage detail logging initially disabled, it can be activated
without having to recycle the monitoring agent. To control storage detail logging dynamically, you can
issue one of the following z/OS Modify commands against the monitoring agent started task to enable
storage detail logging:
MODIFY procname,STORAGE D
MODIFY procname,EVERY 00:60:00 STORAGE D
Where:
MODIFY
Is the z/OS command.
procname
Is the name of the monitoring server or monitoring agent started task. The default name of monitoring
server started task is IBMDS. The default name of the monitoring agent started task is IBMC5.
STORAGE
Displays statistics of TMS:Engine storage usage.
D
Stands for Detail. STORAGE provides both primary and extended storage statistics. This information is
helpful in tuning TMS:Engine memory management.
After you issue this command, look in the RKLVLOG for the output. There will be KLVSD001, KLVSD003,
KLVSD004, KLVSD005, KLVSD006, KLVSD007, and KLVSD008 messages describing Primary Storage, that
is less than the 16M line, and KLVSD002, KLVSD003, KLVSD004, KLVSD005, KLVSD006, KLVSD007, and
KLVSD008 messages describing Extended Storage, that is higher than the 16M line. Primary Storage
generally does not get exhausted so Extended Storage is used in this example.
Typical output of this command and an explanation are found in the following lines.

01 KLVSD002 EXTENDED MAIN STORAGE INFORMATION:
02 KLVSD003 ALLOCATION DETAIL:
03 KLVSD004 SIZE(1-16) USE(12418) TOTAL(12533) ACCESSED(1142629)
44 KLVSD005 LIMIT(8388608) SLOPE(15) SIZES(45) TOTAL(341615K)
45 KLVSD006 FREE(314014K) CARVED(28066K) OVERHEAD(566136)
46 KLVSD007 8% IS IN USE; 90% ALLOWED
47 KLVSD008 8% HAS BEEN CARVED; 95% ALLOWED
Where:
01
Is a TMS:Engine Header message showing Primary or Extended.
02
Is a TMS:Engine header message.
03-43
Is a TMS:Engine message specifying the following values:
Chapter 8. Troubleshooting data collection problems 39

• SIZE: The range (m-n, in bytes) of the sizes of data blocks in the storage area. For example,
SIZE(1-16) indicates that this area contains all of the blocks that are from 1 to 16 bytes long.
• USE: The number of blocks in use.
• TOTAL: The total number of storage blocks allocated.
Note: If the values of both USE and TOTAL are zero, the message does not appear
• ACCESSED: The total number of times the storage block size was accessed.
44-45
• OVERHEAD: The amount of storage (in bytes) used for storage control.
• LIMIT: The size (in bytes) of the largest block that can be allocated.
• SLOPE: An IBM-internal parameter.
• SIZES: Specifies the number of storage areas.
• TOTAL: Specifies (in kilobytes) the total amount of storage available for storage areas.
• FREE: Specifies (in kilobytes) the amount of storage available.
46-47
• Storage is allocated (carved) from the MINIMUM() as needed and assigned to the appropriate
storage area. When freed it remains in the storage area for reuse. The IN USE % statement
shows current usage and CARVED % shows the high-water mark. The % ALLOWED statement is the
threshold at which a warning message will be issued, for example:
KLVSQ000 QUIESCE MODE HAS BEEN ENTERED FOR CARVED EXTENDED STORAGE
When the KLVSQ000 message is issued, the agent will enter a storage quiesce mode and produce a
KLVSQ000 dump on the first occurrence. Storage quiesce mode will not allow any new tasks to start,
but will allow currently running tasks to continue. As storage is freed the condition might alleviate, in
which case, an information message will be issued, for example:
KLVSQ000 QUIESCE MODE HAS BEEN RELEASED FOR CARVED EXTENDED STORAGE
The agent will continue to run until storage is exhausted when a KLVGM005 dump will be taken and a
warning message will be issued:
KLVGM005 FREE STORAGE AREA EXHAUSTED
There are many legitimate reasons why more storage is used: monitoring more CICS regions; more
situations being distributed; more Tivoli Enterprise Portal users; an increase in the number of
monitored resources, for example thousands of Temporary Storage Queues.
The first response should be to increase the value of MINIMUM() in &hilev.RKANPARU(KC5SYSIN) and
restart the agent; this might be the solution or it might just be a circumvention until any problem
is diagnosed. Permanent changes are made using the KDS_TEMS_STORAGE_MINIMUM_EXTEND
parameter in PARMGEN to change this default value on Tivoli Enterprise Monitoring Server or the
KC5_AGT_STORAGE_MINIMUM_EXTEND parameter in PARMGEN to override the monitoring server
value locally.
The STORAGE D output should be monitored. Specifically monitor the KLVSD007 and KLVSD008
messages for increases in % IN USE or % CARVED. Storage usage depends upon a number of factors
so increases are normal. Warning signs are % IN USE and % CARVED increasing and having similar
values and storage areas where USE() and TOTAL() are increasing and having similar values.
If diagnosis is required, the KLVSQ000 and KLVGM005 dumps along with the agent RKLVLOG will be
required by IBM Software Support.

Tivoli Enterprise Portal workspace displays no data or does not
show all the data you expected
You have clicked a navigation item or you have clicked a link and the workspace either displays no data or
does not show all the data that you are expecting.
Many of the workspaces that are provided with OMEGAMON for CICS on z/OS are defined with filters.
Each view in the workspace may have filters defined. These filters restrict the data that is displayed to the
rows that might be interesting to the user. To view the filters that are defined to a workspace, right-click in
the view and select Properties. Click Select a Query and the Filters tab to view or change the filters that
are defined. Adjust the filters to meet the needs of your system. Some queries are used by multiple views
and workspaces; changing the query filter changes the behavior of all views and workspaces that use the
query.
See the "Managing workspaces" topic in the IBM Tivoli OMEGAMON for CICS on z/OS: User's Guide and the
IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide for information on customizing workspaces and
views.
This data collection problem might also occur in the OMEGAMON for CICS TG on z/OS component. In this
situation, there might be an issue with the resources allocated to the OMEGAMON monitor that allows
it to collect and send data to the Tivoli Enterprise Portal. If the monitor becomes overloaded with data,
it must discard some to allow processing to continue. Check the log of the monitored CICS TG that may
have problems. You may see the following message to confirm the data loss:
KGWRM1012W: TxnMonitor internal queue is full. Exit data will be discarded.
There are several reasons why the queue might be becoming full. There may be not enough storage
allocated. Also, the monitor may not be processing the data records quickly enough for the high workload
that is flowing through the CICS TG. To alleviate the issue, the following properties may be set on startup:
• The size (in number of records) of the monitor's internal queue.
• The sleep time (in milliseconds) the monitor waits between testing to see if there are records available
in the queue and processing the records.
• The depth (in number of records) the queue reaches when the monitor is informed that it must start
processing records as the queue is becoming full.
To set these properties to values other than defaults requires a change to the CICS TG startup options.
In the CICS TG environment file, called the CTGENV file by default, modify the CTGSTART_OPTS entry to
include one or more of the following options:
• To increase the internal queue size, append -j-
Dcom.ibm.omegamon.kgw.rmexit.queuesize=<new value>.
• To shorten the queue monitor sleep time, append -j-
Dcom.ibm.omegamon.kgw.rmexit.queuesleep=<new value>.
• To reduce the queue depth trigger, append -j-
Dcom.ibm.omegamon.kgw.rmexit.queuedepth=<new value>.
The CICS TG needs to be restarted for the changes to take effect. On startup, you should see a log
message indicating the new value set. For example:
KGWRM1010I: TxnMonitor internal queue sleep time set to 500 ms.

KGWRM1009I: TxnMonitor internal queue length set to 30,000 records.
KGWRM1025I: TxnMonitor internal queue depth trigger set to 1,000 records.
If this is a WebSphere® Application Server running the CICS TG resource adapters, make the previous
changes within the Administration Console. The settings need to be added as Custom Properties to the
JVM that your WebSphere Application Server is running under. Consult the appropriate administration
documentation for details.
Chapter 8. Troubleshooting data collection problems 41

Chapter 9. Troubleshooting performance problems
This information describes problems that might be associated with performance troubleshooting in IBM Z
OMEGAMON for CICS.
The monitoring agent captures a dump in the event of an

unexpected abend
The number of dumps that are implemented are limited to one by default, although the DUMP command
can be used to reset the dump taken count or to set a different dump limit.
The DUMP command allows these possibilities:
/f agent,OC DUMP RESET
/f agent,OC DUMP RESET MAX=n
/f agent,OC DUMP MAX=n
Where n is 1 to 9.
RESET clears the count of dumps taken to zero, so a dump can take place, if another unexpected abend
occurs.
MAX= sets the limit for the number of dumps that can be taken.
The KOCOME00 program must not be defined as OPENAPI

In CICS Transaction Server, it is possible to define a program as threadsafe OPENAPI in which case the
program runs on a CICS open TCB. The OPENAPI parameter implies that a program runs on an open TCB.
The KOCOME00 program would be dispatched on an open TCB, and return to the QR TCB as soon as a
non-threadsafe CICS call was detected; the net effect would be to introduce unnecessary TCB switching.
On some releases of CICS the use of OPENAPI causes abends in the OMEGAMON GLUE.
Long response times or no results returned when specifying

historical collection time spans for some workspaces
When a time span of several hours (for example, 24 hours) is selected for a workspace, where a large
number of rows of data have been stored in the persistent data store, the resulting query might take 60
seconds or longer to complete and the monitoring agent may use a very high percentage of available CPU
while the query is processed.
The situation is exacerbated, if you are displaying a historical workspace with a 60 second interval.
The monitoring agent processing required to complete the request may not complete within the refresh
interval, causing subsequent requests to be queued. The monitoring agent works continuously processing
the query, sustaining the high CPU utilization until the user has navigated to another workspace or closed
the Tivoli Enterprise Portal.
Perform the following tasks to mitigate this problem:
1. Specify longer historical collection intervals of 30 minutes to one hour, instead of the 15 minute
defaults, for the attribute groups where you are experiencing this problem. This reduces the number
of rows per hour stored in the persistent data store while still making historical data available to your
users.
2. Only collect historical data for attribute groups you are interested in. This will reduce the monitoring
agent processing time required by eliminating unnecessary collection and reduce the amount of
storage needed by the persistent data store.

3. Modify the KFW_REPORT_TERM_BREAK_POINT parameter in the Tivoli Enterprise Portal ENV file.
This parameter controls how many hours of historical data (counting back from the present time) are
to be retrieved from the persistent data store (short term history) data sets. The default is 86400
seconds, or 24 hours. Reducing this value shortens the search of the persistent data store by the Tivoli
Enterprise Portal. Older data (data excluded by changing this parameter) may be accessed if you are
populating historical data in the Tivoli Data Warehouse.
The Tivoli Enterprise Portal queries the Tivoli Data Warehouse Tivoli Data Warehouse for data older than
the value of KFW_REPORT_TERM_BREAK_POINT. Configure a one-hour warehousing interval to ensure
that data is available in the Tivoli Data Warehouse. A one-hour warehousing interval also improves
performance of situations and real-time queries.
A message is displayed when the monitoring system tries to return

data to a table
The monitoring agent tries to return data for the table specified by the product.table variable, and it fails.
The following message is displayed from IBM Tivoli Monitoring:
Cannot allocate nnnnnnnn bytes for sample data, <xxxxxxxxxxxxxxxxxx> on
product.table
OMEGAMON for CICS on z/OS issues this message in the RKLVLOG output, for some of the tables:
KCP0229W: ira AddData for cicjobn failed after n rows.
The most common cause of this error is a query that returns a large number of rows of data, causing
an out-of-memory condition. Tivoli Management Services:Engine (TMS:Engine) startup parameters are
defined with appropriate defaults for many customer environments. The parameters are defined in the
data set pointed to by the RKLVIN DD statement. TMS:Engine startup parameters specify the execution
and resource management environment. The TMS:Engine component uses two of these parameters, the
LIMIT and MINIMUM parameters, to determine how much data can be sent to the Tivoli Enterprise
Monitoring Server.
To address this issue, you can modify the query so that it returns fewer rows of data or change the LIMIT
and MINIMUM values. Change the parameters in the RKLVIN file or the EXEC PARM field of the JCL.
Monitoring agent receives remote procedure call errors during

warehousing, with some requests timing out and failing
While the monitoring agent is performing a warehousing operation, the agent might receive multiple
remote procedure call (RPC) errors, upload failures, and requests that time out while other succeed.
You might see messages similar to this one in the warehousing log:
[IBM][CLI Driver][DB2/NT] SQL0911N

The current transaction has been rolled back because of a deadlock or timeout.
Reason code "2".
SQLSTATE=40001
These RPC calls may indicate that the warehouse proxy agent gets locked up temporarily and cannot
respond to new requests. Eventually, the proxy clears and continues processing. These kinds of problems
are symptoms of insufficient database tuning.
If you plan to install your Tivoli Data Warehouse on DB2, update the DB2 configuration to reduce the
likelihood of database deadlocks when large amounts of monitor data are transferred to the warehouse.
Use the following examples as a guide to making the configuration changes. It is best to make these
changes before installing both the Warehouse Proxy and Summarization and Pruning agents and creating
the warehouse database. To ensure that tablespaces are created correctly, use the database creation
support provided during the installation (or re installation) of the Tivoli Data Warehouse agent from the
Manage Tivoli Enterprise Services window.

To relieve database deadlock, follow these steps:
1. Stop the Warehouse Proxy and Summarization and Pruning Agents, and drop and recreate the existing
warehouse database.
2. Review the "Relational database design and performance tuning for DB2 database servers" topic in
the Performance Tuning / Tivoli Data Warehouse section of the IBM Tivoli Monitoring: Installation Guide
to learn about DB2 tuning considerations. Then, from the DB2 command window, issue the following
command:
db2 update db cfg for WAREHOUS using parameter value

Use the following data configuration parameters:
DFT_DEGREE
LOGBUFSZ
LOCKLIST
SORTHEAP
NUM_IOCLEANERS
NUM_IOSERVERS
LOGFILSIZ
LOGPRIMARY
3. Restart the Warehouse Proxy and Summarization and Pruning Agents.
4. Configure historical collection at the Tivoli Enterprise Portal.
Performance for the Tivoli Data Warehouse database is degraded

or there are gaps where historical data is unavailable for a
specified collection period
A number of symptoms indicate that your database or persistent data store is in need of maintenance.
You might, for example, note that your DB2 transaction logs are filling up.
You might see gaps in the data in the middle or at the end where no historical data is available for
a specified collection period. This problem also manifests itself as degraded performance, such that
database inserts take a very long time. Inserts must be completed between display intervals. Operation
needs to be completed before the next collection interval to prevent the persistent data store from
wrapping.
To prevent these problems:
1. Practice good database maintenance. Schedule regular maintenance outages and reorganize your
Tivoli Data Warehouse tables, including the summarization and pruning tables, using a command to
reorganize the table storage, such as (in DB2) the REORG command.
2. Refer to the "Relational database design and performance tuning for DB2 database servers" topic in
the Performance Tuning / Tivoli Data Warehouse section of the IBM Tivoli Monitoring: Installation Guide
for database tuning information.
3. Change your Send to warehouse setting from daily to hourly for performance tuning in your DB2
database settings.
4. Increase the size of your database transaction log.
5. To eliminate gaps in displays of historical data less than 24 hours old, increase the size of the
persistent data store on the mainframe using the Kpp_PD_CYL parameter in PARMGEN to change the
PDS size in the agent and the KDS_PD_CYL parameter in PARMGEN to change the PDS size in Tivoli
Enterprise Monitoring Server.
Chapter 9. Troubleshooting performance problems 45

Chapter 10. Messages overview
The following information provides an overview of messages and trace information for the IBM Z
OMEGAMON for CICS component, OMEGAMON for CICS TG on z/OS component, IBM Z OMEGAMON for
CICS monitoring agent, and the SLA Batch Utility, which is a separate utility and not part of the monitoring
agent. This information describes the source of messages and the message formats.
Messages can also be viewed on the web by searching on the message number assigned to each
message.
Message log locations

The IBM Z OMEGAMON for CICS monitoring and CICSplex agents generate log files that contain messages
and trace information. The log files contain message and trace information about the events and
processing being performed.
The OMEGAMON log files provide a record of system activity, not just a record of problems. The log files
are created when you start the OMEGAMON components.
When you have a problem, first check the messages in the log files to determine if the source is a
problem in your environment or with an OMEGAMON product. If you determine that the problem is due
to a product defect, refer to "Support Information" on how to proceed to contact IBM Software Support.
IBM Software Support might request that you activate tracing so that the log files collect additional
information needed to resolve the problem. Some of the tracing options produce large amounts of trace
information. Therefore, monitor the disk or spool space when activating tracing to prevent your disk or
spool from reaching capacity. Return the trace settings to the default settings after the desired trace
information has been collected.
Expected failures on the z/OS operating system are recorded as external messages located in the
RKLVLOG file and RKGWSLOG file of the agent address space or Tivoli Enterprise Monitoring Server.
Unexpected errors which result in product failure are accompanied with software dumps, traces, or logs.
Extra tracing and debugging methods may also be available depending on the failed component.
The statistics component, Statistical Application Programming Interface (SAPI) for the OMEGAMON
for CICS TG on z/OS component, and the transaction monitoring component provide their own set of
messages, logs, and traces. The destination of standard messages can be either to the system ('WTO') or
the RKGWSLOG file ('LOG') and is specified using the KGW_SAPI_CLIENT_MESSAGES_SYSOUT parameter
in PARMGEN.. The RKGWSLOG file is dynamically allocated if no RKGWSLOG DD statement is specified in
the JCL.
The OMEGAMON for CICS TG component monitoring exit (TxnMonitor) provides its own set of log and
trace messages that are issued within the address space of the monitored CICS TG. If this is a Gateway
daemon, the messages are written to the STDERR file by default. If this is a WebSphere Application Server
instance, the messages are written to the SYSPRINT file of the SERVANT region by default.
For more information about message logs for components, see IBM Tivoli Monitoring: Troubleshooting
Guide.
Generating and viewing log files

The log files for the IBM Z OMEGAMON for CICS monitoring and CICSplex agents are created as defined in
the started procedure when you start the agent. You can view the log files with any text editor.
For the CICS TG daemon, this occurs during startup of the component. For the WebSphere Application
Server, this occurs during the initial creation of a connection from a monitored connection factory.
When you investigate problems in the monitoring agent, view the sysout data sets or spool files in the job
output and the z/OS system log for any messages that might pertain to the problem.

Message prefixes
This information provides the assigned message prefixes for the IBM Z OMEGAMON for CICS base
product and its various components.
The messages are generated from the IBM Z OMEGAMON for CICS product and are divided into these
general parts:
• Those that apply to the IBM Z OMEGAMON for CICS base product with the prefix KCP
• Those that apply to the OMEGAMON for CICS TG on z/OS component with the prefix KGW
• Those that apply to OMEGAMON for CICS and OMEGAMON for CICS (3270) with prefixes BG, OGJ, KC2,
KO2, and OCJ.
Some messages are informational only, while others advise you to take an action. These are the message
formats:
• An explanation of the message
• A description of the system conditions that generated the message
• A suggested response to the message
• A description of the message type
• A destination for the message
• The severity of the message
Message prefix tables

The following table lists message prefixes for the specified products or components.
Table 2. Message prefixes

Product or component name Prefixes
AF/OPERATOR AOP, KAO, KAT, KOG, OMG
Alert Adapter for OG/MVS KAM
OMEGAMON for CICS (3270) CSAA, IA, IN, LSCX, OM, OM0
ITMS: Engine KBB, KDC, KLE, KLU, KLV, KLX
End-to-End ETE
OMEGAMON Base CI, CNDL, OB, OBV, OMV
OMEGAMON for VM CV, EU, EV, OGN, OV
IBM Z OMEGAMON for CICS BG, KC2, KOCJ, OC
OMEGAMON for DB2 on z/OS H2C, KD2, O2
OMEGAMON for IMS on z/OS ATF, DSM, ETX, EVS, ICF, LAT, ML, MRG, OR, OS, OTR,
PWA, REG, TRF
OMEGAMON II for Mainframe Networks EX, KON
OMEGAMON for z/OS EA, KM2, KXDF, OM2, VEB
OMEGAMON for Storage KDF, KRC
OMEGAMON II for VTAM EX, KON
IBM Z OMEGAMON for CICS KCP
OMEGAMON enhanced 3270 user interface KOB

Table 2. Message prefixes (continued)
Product or component name Prefixes
OMEGAMON for CICS TG on z/OS KGW
OMEGAMON for DB2 KDP
OMEGAMON for IBM Cryptographic KCG
Coprocessors
OMEGAMON for IMS and IMSplex KIP
OMEGAMON for Networks KN3
OMEGAMON for Storage KS3
OMEGAMON for Sysplex KOS, KCN
OMEGAMON for WebSphere MQ Configuration KCF, KMC
OMEGAMON for Messaging KMQ
OMEGAMON for WebSphere Integration KQI
Brokers
OMEGAVIEW KMV, KSD
Standard messages and abend codes

OMEGAMON XE products routinely issue standard messages and display them on the screen. Messages
with the following prefixes are exceptions.
Table 3. Standard messages and abend codes

Products Prefix exceptions
EB, EU, and EP messages are written to the file or SYSOUT
OMEGAMON for CICS
class specified by the RKM2OUTM data set. EC messages appear
OMEGAMON for DB2 on z/OS
as WTO messages on the system operator console, in the
OMEGAMON for DBCTL
RKM2OUTM or RKM2DUMP data set output, or as messages
OMEGAMON for IMS on z/OS
to TSO user terminals (if the NOTIFY keyword is specified in
OMEGAMON for z/OS
rhilev.midlev.RKANPAR(KEPOPTN)).
Note: EU messages are equivalent to EP messages.
OMEGAMON for z/OS OM2

All Tivoli OMEGAMON II products KLE, KLU, and KLV messages are written to the RKLVLOG data set.
All Tivoli OMEGAMON II products Messages displayed by additional features, such as PRO for MVS™
or OBTAIN, are included in this manual.
OMEGAMON IIor OMEGAVIEW issues abend codes when an error occurs.

Note: For OMEGAMON for z/OS and OMEGAMON for Storage messages that appear during the operation
of OMEGAMON can be issued from the product, Tivoli Enterprise Monitoring Server, or OMEGAMON
Subsystem address spaces.
Reporting problems
Some messages suggest that you generate a system memory dump and forward it to IBM Software
Support for more help.
If your OMEGAMON XE product malfunctions, complete the following steps before you call IBM Software
Support:
Chapter 10. Messages overview 49

• Record the error message number and any error codes that the error message displays.
• Record output from the DEBUG screen space, when possible.
To obtain these DEBUG screens, type DEBUG on the INFO-line and press Enter. Your product executes
various screen spaces and logs important information to hardcopy.
Note: For IBM Z OMEGAMON for CICS, OMEGAMON for DB2 on z/OS, OMEGAMON II for DBCTL,
OMEGAMON XE for IMS on z/OS, and OMEGAMON for z/OS, or the OMEGAMON for CICS TG component
fill in the information on the hardcopy of the first debug screen (DEBUG).
• Gather any dumps that the OMEGAMON XE product produces (on cartridge, tape, or hardcopy). You can
write product memory dumps to one or more of the following:
Table 4. Collecting memory dumps

Products Description
IBM Z OMEGAMON for CICS The common interface SYSABEND DD statement

OMEGAMON for DB2 on z/OS
OMEGAMON II for DBCTL
OMEGAMON for z/OS
OMEGAMON for DB2 on z/OS The O2SNAP data set

OMEGAMON II for DBCTL
OMEGAMON for z/OS
OMEGAMON for Storage
OMEGAVIEW
All products The RKLVLOG and RKLVSNAP data sets

All products MPcc data set
Be prepared to send the dumps to IBM if a Software Support representative requests you to do so. You
can also use FTP to transmit dumps to IBM.
Note: If you send a cartridge or tape, specify the format, density, and label information.
• Record any error messages that OMEGAMON XE product writes to the system log.

Chapter 11. KCP messages
This information is a listing of the KCP messages, which are generated from the OMEGAMON for CICS on
z/OS product.
KCP0001E aaaaaa $SUPER0 REQUEST User response
FAILED
Contact IBM Software Support.
Explanation KCP0003 function table PDS AGENT DID NOT

SUPPLY COLUMN: col
An OMEGAMON internal request for service has failed.
The most likely cause is an earlier failure or corruption
of OMEGAMON areas within CICS. The program Explanation
invoking the service is denoted by aaaaaa. The function indicated by function was unable to
locate the column identified by type in the CMS
System action catalog.
Processing continues; however results are

unpredictable. System action
The function identified by function terminates.
User response
Contact IBM Software Support. User response
KCP0001E aaaaaa UNABLE TO OBTAIN A Contact IBM Software Support.
NEW MNTC BLOCK KCP0004 subtask CANNOT COMMUNICATE
WITH XMI
Explanation
OMEGAMON was unable to obtain sufficient storage Explanation
higher than the line in order to save the transaction The system was unable to locate the address of the
data for a task. The program requesting the storage XMI communication control block using ITMS:Engine
denoted by aaaaaa. services.
System action System action

Processing continues. The subtask identified by subtask stops processing.
User response User response

Increase the size of the region available to CICS. If this Confirm that XMI successfully started as a subtask
problem persists contact IBM Software Support. of the Tivoli Enterprise Monitoring Server address
KCP0002 function table PLN I/O ERROR ON space. Ensure that there is a START command in the
PDS: TYPE=type, RC=rc Tivoli Enterprise Monitoring Server CONFIG file that
automatically starts XMI. If problems persist, contact
IBM Software Support.
Explanation
KCP0005 AGENT module PTF ptfno@
The function indicated by function was unable to address ASSEMBLY time date
perform an I/O request to the Persistent Data Store.
type denotes the function that failed, and rc is the
return code generated by the PDS subroutine. Explanation
This informational message is written to the RKLVLOG
System action when an agent is first invoked. It lists the agent name,
most recently applied PTF, the load point and time and
The function identified by function stops processing. date of assembly.

System action space prior to the expiration of a one minute time
interval for the named region.
None.
System action
User response
The agent bypasses ONDV processing for the named
None, the message is informational. CICS region.
KCP0006 agent MEMORY REQUEST FAILURE
FOR ACCESS LIST User response
Ensure that the ONDV subtask is active in the common
Explanation interface used to monitor the identified CICS region.
The specified agent was unable to allocate storage for Also, check that the dispatching priority of the OCCI
the distribution list associated with a situation. job is high enough to permit its responding to cross-
memory requests in a timely fashion.
System action KCP0009 function CANNOT ACCESS OC CVT

Data is collected for every CICS region.
Explanation
User response The system was unable to locate the address of the
CVT control block in the ITMS:Engine GSA.
Consider increasing either the Tivoli Enterprise
Monitoring Server region size or the GMMPERCENT
value in the Tivoli Enterprise Monitoring Server startup System action
configuration file. The function identified by function stops.
KCP0007 XAM PROCESSING FOR
THE SPECIFIED CONNECTIONS User response
PARAMETER IS BYPASSED
ID=table Contact IBM Software Support.
KCP0010 agent $ONDVREQ MACRO FAILURE
Explanation FOR CICS region: RC=rc
The connections parameter specified on the start

command for the exception analysis manager (XAM) Explanation
subtask is invalid. The agent was unable to communicate with the ONDV
subtask of the common interface. The return code
System action denoted by rc indicates the cause of the error.
The exception analysis manager processes all

connections in the monitored CICS regions. System action
The agent bypasses ONDV processing for the named
User response CICS region.
Specify a valid connections parameter. The valid

format is CONNECTIONS=parameter, where parameter User response
is 1 to 4 characters, including an asterisk. Examples Ensure that the ONDV subtask is active in the common
include: interface used to monitor the identified CICS region. If
• CONNECTIONS=C* problems persist, contact IBM Software Support.
• CONNECTIONS=C*6 KCP0011 agent UNABLE TO OBTAIN
STORAGE IN OCCI LENGTH=length
KCP0008 agent ONDV REQUEST TIMED OUT
FOR CICS region
Explanation
Explanation The agent was unable to acquire storage in the
common interface address space for ONDV record
The agent did not receive a record buffer from the
collection.
ONDV subtask of the Common Interface address

The agent bypasses ONDV processing for the named The CICS region is ignored.
CICS region.
User response
User response
Ensure that the ONDV subtask is active in the common
Consider increasing the OCCI region size. If problems interface used to monitor the CICS region.
persist, contact IBM Software Support.
KCP0016 CICS aaaaaaaa: bbb
KCP0012 agent UNIT-OF-WORK
DESCRIPTOR NOT SUPPLIED VIA Explanation
PARMA
The agent was unable to extract shared Temporary
Storage queue information from the service task
Explanation
operating within the CICS address space denoted by
The agent was unable to locate the unit-of-work used aaaaaaaa.
to search for related transactions.
System action
System action
Temporary Storage queue data is not collected for the
The agent stops processing. CICS region.

The SQL generated internally to drive the unit-of-work Based on the text of the message denoted by bbb,
agent is in error. Contact IBM Software Support. attempt to correct the cause of the service task error.
If problems persist, contact IBM Software Support.
KCP0013E WDR UNABLE TO EXTRACT
WORKLOAD RECORDS FROM KCP0017 UNABLE TO ALLOCATE XCB
aaaaaa CONTROL BLOCK
Explanation Explanation
A serious internal error occurred when attempting to The cross-memory interface (XMI) subtask was unable
retrieve transaction information from a CICS region. to allocate one of its primary communications control
The CICS region is denoted by aaaaaa. blocks from subpool 251 storage.

Processing continues, however, no further attempt The cross-memory interface task stops processing.
is made to retrieve transaction information for the
CICS region. Service level reporting does not contain User response
information for that CICS region until the CICS region
or the address space where the agent runs is recycled. Consider increasing the region size of the ITMS:Engine
address space in which XMI is started.
User response KCP0018 ERROR WHILE COLLECTING RLS
Contact IBM Software Support. DATA: aaa
KCP0014 agent ONDV NOT RUNNING FOR Explanation

CICS region:
The agent was unable to extract Record Level Sharing
(RLS) information due to the error denoted by aaa.
Explanation
The agent was unable to locate the ONDV subtask in System action
the common interface for the specified CICS region.
RLS data is not collected for the z/OS image.
Chapter 11. KCP messages 53

User response extension, and RLS timeout rates. Therefore, columns
that contain "Last Hour" data in the VSAM Analysis
Based on the text of the message, attempt to correct table are always zero.
the cause of the error. If problems persist, contact IBM
Software Support.
User response
KCP0019 SYSTEM FAILURE DURING ATTACH
OF subtask RC=rc None.
KCP0022 XAM EXCEPTION ANALYSIS
Explanation MANAGER IS TERMINATING
The ATTACH macro used to create the subtask

identified by subtask failed. The return code denoted Explanation
by rc represents the contents of register fifteen passed The Exception Analysis Manager (XAM) received a
back by the ATTACH macro. request to terminate.

The component being started stops processing. None.

Consult the IBM Macro Reference for a description of None.
each return code generated by the ATTACH macro
and take the necessary corrective action. If problems KCP0023 XAM EXCEPTION ANALYSIS
persist, contact IBM Software Support. MANAGER IS ACTIVE
KCP0020 agent PERSISTENT DATASTORE

NOT INITIALIZED Explanation
The Exception Analysis Manager (XAM) completed
Explanation initialization.
The function indicated by agent was unable to perform

an I/O request to the Persistent Data Store (PDS). System action
None.
System action
The function identified by agent stops processing. User response
None.
User response KCP0024 XAM CONNECTIONS FILTER
Verify that the PDS has been properly configured. If SETTING = aaaa
historical records are not desired, consider stopping
the automatic situations that attempt to write records Explanation
to the PDS. If problems persist, contact IBM Software
Support. The generic connections filter used to limit the TCT
scan has been accepted.
KCP0021 XAM UNABLE TO ACQUIRE TABLE
STORAGE
System action
Explanation None.
The VSAM=NO operand was included on the OC

START, ID=XAM command. User response
None.
System action KCP0025 Agent WHERE CLAUSE PREEMTS
The Exception Analysis Manager (XAM) does not USE OF PARMA FOR CICS NAMES
collect VSAM file information used to compute split,

The agent detected CICS names being passed using The exception analysis manager (XAM) subtask
both PARMA (keyword CICSNAME) and WHERE clause encountered a program check in one of its cross-
filters. memory mode collection routines while attempting to
monitor the CICS denoted by region.
System action
System action
The PARMA values for CICS names are ignored.
XAM continues processing. No dump is produced.
User response
User response
Remove the PARMA filter for CICS job names.
This may be the result of corrupted storage in the
KCP0026 aaa PARAMETER LIST HAS AN CICS address space. If problems persist, contact IBM
INVALID FORMAT Software Support.
Explanation KCP0029 FCJ LOAD OF AAAAAAAA

FAILED FOR CICS=BBBBBBBB,
The agent denoted by aaa detected either a missing or CODE=CCCCCCCC,
incorrect set of parameters. REASON=DDDDDDDD
System action Explanation

The query is ignored. FCJ failed to LOAD the CSI API routine. The
CODE=cccccccc and REASON=dddddddd indicates the
User response cause of the error.

System action
KCP0027 XAM UNABLE TO ACQUIRE
Partial data is collected. The data displayed on a
TABLE STORAGE: LENGTH=length,
report may be collected from various sources. Only the
ID=table
data from a valid return code is displayed.
Explanation User response

The exception analysis manager (XAM) subtask was
unable to allocate length bytes of private storage for
table identified by table. KCP0030 FCJ ERROR RECEIVED FROM
IGGCSI00. CICS=AAAAAAAA,
System action RC=BBBBBBBB, REASON=CCCC
If the error occurs during initialization, the exception

Explanation
analysis subtask stops processing. Otherwise, XAM
continues processing with a decreased ability to The FCJ module called MVS module IGGCSI00 failed
compute rates per hour for the storage violation and and returned error RC=bbbbbbbb and REASON=cccc
VSAM control block exceptions.
System action
User response
Partial data is collected. The data displayed on a
Consider increasing either the region size or the report may be collected from various sources. Only the
RESERVE(n,X) value in the startup configuration file for data from a valid return code is displayed.
the agent address space.
KCP0028 XAM PROGRAM CHECK RECOVERY User response
FOR CICS: region

KCP0031 CSD UNABLE TO COLLECT • REQUESTED SERVICE IS INVALID
STORAGE INFORMATION FOR • SECONDARY SERVICE TASK (OSEC) IS NOT
CICS=AAAAAAAA, RC=BBBBBBBB RESPONDING
• THE SECONDARY SERVICE TASK (OSEC) HAS
Explanation ABENDED
The CSD failed to collect CICS storage information. • REQUEST RATE FOR SECONDARY TASKS IS AT
MAXIMUM
System action • SECONDARY TASK TABLE HAS NO MORE ENTRIES
No data is collected. • AVAILABLE CONCURRENT NUMBER OF REQUESTS
IS AT MAXIMUM
User response • INCOMING NUMBER OF REQUESTS IS AT MAXIMUM

RATE
If problems persist, contact IBM Software Support. • ATTEMPT TO SET CM#SRVST TO START OSEC HAS
KCP0032 AGENT, module name IN CICS cics FAILED
jobname : text • START OF A SECONDARY SERVICE TASK WILL PUT
CICS AT MAXTASKS
Explanation • REQUEST FOR A SERVICE TASK STATISTICS BLOCK
FAILED
The data collection in the module name for the
CICS region cics jobname might not have completed • THE COPY OF THE CICS STATISTICS BLOCK FAILED
successfully. If the message is issued as a result of • UNABLE TO SAVE THE ADDRESS OF THE STATISTICS
an Action command (using the Tivoli Enterprise Portal BLOCK
Action command facility in OMEGAMON for CICS on
• THE 4K BUFFERS TIMED OUT DURING THE
z/OS) then message KCP0032E is issued instead.
OPERATION
• THE SERVICE TASK IS NOT AUTHORIZED FOR A
System action COMMAND
Data collection might have been bypassed or the • AN UNEXPECTED RETURN CODE WAS RECEIVED
Action command might have failed, depending on the FROM CICS
content of the text in the message, therefore, data
might not be available in some workspaces. • SERVICE FAILED DUE TO CICS COMMAND
SECURITY
• SERVICE FAILED DUE TO CICS RESOURCE
User response
SECURITY
Review the text value in the message and take • THE SERVICE TASK IS NOT RESPONDING
corrective action. If the problem persists, contact IBM
Software Support. • NO WORK ELEMENTS IN THE FREE QUEUE
• THE SERVICE TASK IS INACTIVE
KCP0032E This message text can be any
of the following reasons. See the • THE SERVICE TASK WORK AREA COULD NOT BE
User Response. FOUND
• OMEG HAS NOT BEEN INITIALIZED IN THE CICS
Explanation ADDRESS SPACE
• THE SERVICE TASK HAS BEEN SHUTDOWN
The Action command could not be completed.
• CICS IS SHUTTING DOWN
The Action command is bypassed.
• SERVICE NOT AVAILABLE FOR THIS CICS RELEASE
• THE SERVICE TASK AND OMEGAMON HAVE
User response
INCOMPATIBLE VERSIONS
Review one of the following message text and take • AID TO BE KILLED WAS NOT CHAINED TO THE
corrective action where possible. If the problem TCTSE
persists, IBM Software Support.
• A TASK HAD ALREADY BEEN STARTED FOR THE AID
• NUMBER OF SECONDARY SERVICE TASKS AT TO BE KILLED
MAXIMUM
• THE FREEMAIN FOR THE KILLED AID FAILED

• AID NOT KILLED. THE TERMINAL DID NOT MATCH System action
• AID NOT KILLED. THE TRANSACTION DID NOT None.
MATCH
• AID NOT KILLED. THE REQID DID NOT MATCH
User response
• THE TERMINAL DID NOT MATCH. ICE NOT KILLED
None.
• THE TRANSACTION DID NOT MATCH. ICE NOT
KILLED KCP0040E The fff FUNCTION RECEIVED
UNEXPECTED RC xxxxxxxx AND RS
• THE REQID DID NOT MATCH. ICE NOT KILLED
ssssssss
• THE EXPIRY TIME DID NOT MATCH. ICE NOT KILLED
• TD QUEUE IS DISABLED - CAN NOT BE DELETED Explanation
• TD QUEUE IS EXTRAPARTITION - CAN NOT BE
An unexpected error was detected by the fff function.
DELETED
The xxxxxxxxvalue is the ABEND code and the ssssssss
• THE REMOTE SYSTEM RETURNED ISCINVREQ value is the REASON code.
AFTER A DELETEQ TD
• TRANSIENT DATA QUEUE NOT FOUND System action
• REMOTE SYSTEM SPECIFIED FOR TD QUEUE
System processing continues.
DELETE IS INVALID
• CAN NOT DELETE A TEMPORARY STORAGE QUEUE
OWNED BY CICS
User response
• THE TS QUEUE COULD NOT BE DELETED IN THE If the problem persists, contact IBM Software Support.
REMOTE SYSTEM KCP0051E csect OMEGAMON AUTHORIZED
• TEMPORARY STORAGE QUEUE NOT FOUND FUNCTION ERROR RC=nnnn
• INVALID REMOTE SYSTEM ID ROUTINE xx
• CICS DETECTED AN UNRECOVERABLE I/O ERROR
Explanation
• END OF TEMPORARY STORAGE QUEUE
• CICS LINK TO DFHEMTA FAILED A call to OMEGAMON Authorized functions has
returned an invalid return code.
KCP0033E OTR UNABLE TO ALLOCATE TRACE
BUFFER STORAGE, CONSIDER
System action
INCREASING MINIMUM VALUE
This depends upon the routine number and csect.
Explanation
User response
Memory could not be allocated to retrieve the data
needed to process an Application Trace query. Collect all logs and contact IBM support.
KCP0070 INVALID GROUP SPECIFICATION
System action FOR CICS aaaaaaaa
The query returns no data.
Explanation
User response The agent expects a group identifier for CICS
Increase the amount of storage available to the Tivoli aaaaaaaa, but found an invalid value. The value must
Enterprise Monitoring Server or agent address space. be in the range 1-MAX_GROUPS (MAX_GROUPS is
the value specified in the Global definition file of the
KCP0034I USER=xxxxxxxx CICS=cicsname OMEGAMON for CICS on z/OS product).
REQUEST WAS COMPLETED
SUCCESSFULLY.
System action
Explanation The query is ignored.
This message is issued when a Take Action command

is successfully completed.

User response KCP0103 agent UNABLE TO MONITOR CICS
region: RC=rc
Specify a valid group number in the query predicate
and retry the request.
Explanation
KCP0100 agent GET PARM
ERROR: PARMNAME=parmname, IBM Z OMEGAMON for CICS on z/OS is unable to
STATUS=status monitor CICS region. Return code rc indicates the type
of error:
Explanation Table 5. Return codes when IBM Z OMEGAMON for
The agent was unable to obtain the address of the CICS on z/OS is unable to monitor a CICS region.
parameter identified by parmname. Status code status Return
indicates the cause of the error. Code Description
04 XMI did not register the XCB address.
System action
08 CICS region could not be found.
No data is collected.
0C Specified region does not belong to
CICS.
User response
Contact IBM Software Support. 10 CICS release is not supported by
OMEGAMON for CICS on z/OS.
KCP0101 agent GET VIEW STORAGE ERROR:
LENGTH=length, STATUS=status 14 CICS job is swapped out.
18 ESTAEX macro failed.
Explanation 1C Cross memory error occurred during
The specified agent was unable to allocate the CICS validation.
specified length of bytes of storage. Status code status 20 CICS initialization is not complete.
indicates the cause of the error.
24 XMIT DD card suffix used in CICS does
System action not match that of the agent.
No data is collected. 28 Unable to obtain memory required to

build TDA.
User response 2C Session Accounting Area build error

occurred.
Consider increasing either the Tivoli Enterprise
Monitoring Server region size or the GMMPERCENT 30 Module load error occurred (see console
value in the Tivoli Enterprise Monitoring Server startup for message OC0760).
configuration file.
34 OCCI Session Accounting Area not
KCP0102 agent PUT PARM found.
ERROR: PARMNAME=parmname,
38 CICS is an XRF alternate.
STATUS=status
Explanation System action

The specified agent was unable to identify the address No data is collected.
of the parameter identified by parmname. Status code
status indicates the cause of the error. User response
Use the return code to determine the appropriate
System action action. If problems persist, contact IBM Software
No data is collected. Support.
Note: The accompanying message KCP0103E returns
User response the text for the return codes that are listed with the
KCP0103 message.

KCP0104 EXCEPTION ANALYSIS SUBTASK KCP0107I MONITORING cicsname,
IS NOT ACTIVE CICSPLEX plexname FROM source
The OMEGAMON for CICS on z/OS exception analysis This message is issued in response to the OC START
subtask is not running in the Tivoli Enterprise ID=TDA,ID=cicsname command, if the response code
Monitoring Server address space. is 0; it is written to the RKLVLOG output.

No data is collected. None.

Confirm that XMI successfully started as a subtask None, but verify that the CICSPLEX matches what you
of the Tivoli Enterprise Monitoring Server address defined in your global data options.
space. Ensure that there is a START command in the
Tivoli Enterprise Monitoring Server CONFIG file that KCP0108I UNABLE TO OBTAIN STORAGE FOR
automatically starts XAM. If problems persist, contact CICSPLEX nnnnnnnn, RC=xxxx.
IBM Software Support. THE CICSPLEX CANNOT BE
MONITORED BY THIS AGENT.
KCP0105 agent CROSS MEMORY ERROR,
CICS SWAPPED OUT: region Explanation
OMEGAMON for CICS on z/OS is unable to obtain
Explanation
storage for the CICSplex control block (PDA) when
The system attempted cross memory operations to a registering a CICS region. The nnnnnnnn value is the
CICS region that was swapped out. name of the CICSplex that was being registered. The
xxxx value is the return code from the STORAGE
System action OBTAIN macro.
System action
User response The system continues processing but the CICSplex is
not monitored by this agent.
None.
KCP0106 IRA CROSS MEMORY ABEND User response
COLLECTING DATA FOR Use the return code information to determine why the
CICScccccccc, ID=iiiiiiii system was unable to obtain the required storage. If
the problem persists, contact IBM Software Support.
Explanation
KCP0109 COPY TMA/$OCMNTA ERROR;
The agent experienced an abend while attempting to POSSIBLE DATA LOSS
collect data for a specific CICS region, where ccccccccc
is the name of the CICS region, iiiiiiii is the name of the
Explanation
agent.
The work area allocated by the agent that extracts
System action transaction data is not large enough to accommodate
the information gathered by the task cross-memory
The agent continues to attempt data collection for collector.
remaining columns.
System action
User response
Data in transaction reports may be incomplete.
None.

User response System action
Contact IBM Software Support. No data is collected.
KCP0110 IRA DATA COLLECTOR ABEND
COLLECTING DATA FOR CICS User response
cccccccc, Id=iiiiiiii Contact IBM Software Support.
KCP0113 WSR FLOATING POINT
Explanation
cccccccccccccccc, DETECTED
Where cccccccc is the name of the CICS region that RA=xxxxxxxx
was being queried when the abend occurred and iiiiiiii
is the name of the agent that suffered the abnormal Explanation
termination.
This is the diagnostic message previous to Abend
U113, indicating the type of function that failed.
System action
cccccccccccccccc represents the error type and
The collector abandons the attempt to collect data xxxxxxxx is a hexadecimal address.
from the current CICS region.
System action
User response
WSR collector will ABEND U113.
This message should be associated with a set of
KCP098x messages. Contact IBM Software Support. User response
KCP0111 WSR FLOATING POINT cccccccc, Contact IBM Software Support.
ERROR OCCURRED RESULT SET
ZERO RA=xxxxxxxx KCP0114E UNABLE TO OBTAIN STORAGE FOR
CICS REGION nnnnnnnn, RC=xxxx.
THIS CICS REGION CANNOT BE
Explanation
MONITORED BY THIS AGENT.
A floating point calculation generated a value too large
to represent. cccccccc represents the calculation type Explanation
(ADD|SUBTRACT|MULTIPLY|DIVIDE) and xxxxxxxx is a
hexadecimal address. The product is unable to obtain storage for the CICS
control block (TDA) when registering a CICS region.
The nnnnnnnn value is the name of the CICS region
System action
that is being registered. The xxxx value is the return
No data is collected. code from the GETMAIN macro.

Contact IBM Software Support. The system continues processing but the CICS region
is not monitored by this agent
KCP0112 WSR FP cccccccc,
IN1=xxxxxxxxxxxxxxxx,
IN2= xxxxxxxxxxxxxxxx, User response
OUT=xxxxxxxxxxxxxxxx, Use the return code information to determine why the
RA=xxxxxxxx system was unable to obtain the required storage. If
Explanation
KCP0190 LU GROUP INVALID FOR THIS
A floating point calculation generated a value too large FUNCTION FOR CICS aaaaaaaa
to represent. cccccccc represents the calculation type
(ADD|SUBTRACT|MULTIPLY|DIVIDE) and xxxxxxxx is a Explanation
hexadecimal value or address.
The requested function does not support VTAM Logical
Unit (LU) groups for CICS aaaaaaaa.

System action values accumulated up to the time of suspend are
returned by the query.
The query is ignored.
System action
User response
The query continues execution.
Specify one of the other group types and retry the
request.
User response
KCP0201 BOTTLENECK ANALYSIS
COLLECTOR NOT ACTIVE FOR Resume the Bottleneck Analysis collector and retry the
CICS aaaaaaaa request.
KCP0207 COLLECTOR DETACHED DUE TO
Explanation TOO MANY PROGRAM CHECKS
FOR CICS aaaaaaaa
The Bottleneck Analysis collector is not active in
the OMEGAMON for CICS on z/OS common interface
(OCCI) address space used to monitor the CICS Explanation
aaaaaaaa value. The Bottleneck Analysis collector, running in the
OMEGAMON for CICS on z/OS common interface
System action (OCCI) address space, was detached for the CICS
aaaaaaaa value due to an excessive number of
The query is ignored. program checks.

Start the collector and retry the request. The query is ignored.
KCP0202 BOTTLENECK ANALYSIS
COLLECTOR IS BUSY FOR CICS User response
aaaaaaaa
Explanation KCP0210 DSPSERV MACRO FAILURE:

CODE=error, REASON=reason
The Bottleneck Analysis collector, running in the
(OCCI) address space, is currently analyzing the Explanation
environment of the CICS aaaaaaaa value. The agent The system was unable to create the data space
cannot access the collection data until the collector used to hold CICS transaction data. The error code is
finishes. represented by the error, and reason values denotes
the reason code that is associated with the problem.
System action
The query is ignored. System action
The workload manager subtask stops processing.
User response
Retry the request. User response
KCP0203 COLLECTOR SUSPENDED, VALUES Error and reason codes for the DSPSERV macro are
SHOWN NOT CURRENT FOR CICS described in the IBM System Programming Library:
aaaaaaaa Application Development Macro Reference manual.
Correct the cause of the problem and restart the
subtask.
Explanation
KCP0211 ALESERV MACRO FAILURE:
The Bottleneck Analysis collector, running in the CODE=rc
(OCCI) address space, is suspended and is not
sampling data for the CICS aaaaaaaa value. Only the

The system was unable to add an entry in the access The OMEGAMON for CICS on z/OS data collection exits
list for the data space that harbors CICS transaction are not running in the CICS region identified by region.
data. The rc value is the return code provided by the
ALESERV macro. System action
Service level data for the CICS region value is not
System action
gathered.
The workload manager subtask stops processing.
User response
User response
Ensure that an 'OMEG INIT' transaction has been run
Return codes for the ALESERV ADD function are in the CICS region value. If problems persist, contact
described in the IBM System Programming Library: IBM Software Support.
Application Development Macro Reference manual.
Correct the cause of the problem and restart the KCP0215 UNABLE TO OBTAIN RECORD
subtask. CELL, DATA LOST
KCP0212 WORKLOAD ANALYSIS TASK IS Explanation

TERMINATING
The data space used to hold CICS transaction records
is full.
Explanation
The workload subtask used to summarize CICS data System action
by service class is stopping because of an operator
request, or some kind of abnormal termination. Until the workload summarization subtask processes
the records in the data space, service level data for
some transactions are lost.
System action
None. User response
Ensure that the Tivoli Enterprise Monitoring Server
User response
is getting sufficient cycles to process all of
If the shutdown is unexpected, check the console the CICS transaction data. Consider increasing
log for other messages that might indicate why the the size of the data space by coding the
workload subtask is stopping. If problems persist, BLOCKS= parameter on the WLM START command
contact IBM Software Support. (OC START ID=WLMBLOCKS=nnnnnn) found in
RKANCMD(KDSSTART). If the BLOCKS keyword is not
KCP0213 WCR PASSED INVALID LENGTH TO coded, the workload subtasks use the installation
XMCOM default when creating the data space.
Use the /OC STATUS,WLMBLOCKS command to display
Explanation
the current status of the values in the RKLVLOG output.
The workload subtask improperly formatted the
Setting a higher value gives the WLM subtasks
parameter list it uses to extract CICS transaction data.
additional time to process transaction information. If
problems persist, contact IBM Software Support.
System action
KCP0216 SUMMARY SUBTASK ABEND,
The workload manager subtask abnormally stops CODE=cc
processing.
Explanation
User response
The workload summarization routine abnormally
Contact IBM Software Support. terminated with completion code cc.
KCP0214 WORKLOAD ANALYSIS IS NOT
RECEIVING DATA FROM region System action
The workload analysis subtask stops processing.

User response Explanation
Contact IBM Software Support. The service level analysis subtask is not running in the
KCP0217 WCR BLOCKS VALUE EXCEEDS
RANGE (10-524288)
System action
Explanation Service level data cannot be written to the persistent
data store.
The BLOCKS value coded on the OC START ID=WLM
command is not within the permissible range for the
DSPSERV macro. User response
Ensure that the WLM subtask was started under
System action the Tivoli Enterprise Monitoring Server. If problems
KCP0222 function table CREATE PATH
User response FAILURE, RC=rc
Enter the command, specifying a valid value.

Explanation
KCP0218 WCR UNABLE TO CREATE The function indicated by function was unable to
ADEQUATE DATA SPACE, perform an SQL CreatePath for table table. rc is the
BLOCKS=cc return code generated by the SQL request.

A minimum of ten blocks must be available in the data
The function identified by function stops processing.
space created by the WLM subtask. The actual number
of blocks allocated by the DSPSERV macro is displayed
as cc. User response
System action
KCP0223 agent INPUT SQLDA ERROR,
The workload analysis subtask stops processing. COLUMNS=columns

Modify the IEFUSI exit to permit a data space size of at The number of columns expected by agent agent does
least ten blocks. not match the column count returned in the SQLDA.
columns shows the number of columns contained in
KCP0219E THE INTERVAL VALUE IS INVALID,
the SQLDA input buffer.
MUST SPECIFY 1 or TEP.
System action
Explanation
The agent identified by agent stops processing.
The INTERVAL value coded on the OC START ID=WLM
command is incorrect.
User response
System action Contact IBM Software Support.
The workload analysis subtask stops processing. KCP0224 function table OPEN REQUEST
FAILURE, RC=rc
User response
Explanation
Enter the command with a valid value. The valid values
are 1 or TEP. Function function was unable to perform an SQL
OpenRequest for table table. rc is the return code
KCP0220 SERVICE LEVEL ANALYSIS
generated by the SQL request.
SUBTASK IS NOT ACTIVE

System action User response
The function identified by function stops processing. Review the RKLVLOG output for the errors. Consider
filtering the query or increasing the ITMS:Engine LIMIT
User response parameter.
This message is generated from the CICS agent, you
need to edit the KppSYSIN member that the agent
KCP0225 function table DROP PATH is using, it will either be KDSSYSIN (agent running
FAILURE, RC=rc in a Tivoli Enterprise Monitoring Server) or KC5SYSIN
(agent running in its own address space). The defaults
are:
Explanation
Function function was unable to perform an SQL LIMIT(23,X)
LIMIT(16,P)
DropPath for table table. rc is the return code
generated by the SQL request. KCP0230E WCR RESP VALUE IS INCORRECT
OR OUT OF RANGE, SHOULD BE
System action 0.001 TO 9999.999
Explanation
User response The RESP= parameter that is specified on the OC
START WLM command contained a value that was not
valid or was not within the permissible range.
KCP0226 function table SERVICE LEVEL
ANALYSIS SUBTASK HAS System action
TERMINATED
Explanation
User response
The function encountered an error when attempting to
retrieve data from the data space. The data space is Enter the OC START WLM command again and specify
no longer available because the service level analysis a value that is valid.
subtask has terminated. KCP0231E WCR GOAL VALUE IS INCORRECT
OR OUT OF RANGE, SHOULD BE 1
System action TO 99 OR A
The function identified by the function value stops.
Explanation
User response The GOAL= parameter that is specified on the OC
START WLM command contained a value that was not
Identify the reason for the termination of the
valid or was not within the permissible range. The
service level analysis subtask. If the termination
value should be a percentage from 1 to 99 or A to
was abnormal, collect the CMS message log and
represent the average.
SYSUDUMP output and contact IBM Software Support.
KCP0229W aaa AddData for cicsname failed System action
after n rows.
Explanation
User response
The agent identified by the aaa value was unable to
return all the rows that are available. Enter the OC START WLM command again and specify
a value that is valid.
System action KCP0233W THE 'INTERVAL=' PARAMETER IS
NO LONGER USED AND WILL BE
The collector returns no more rows for the CICS region
IGNORED.
in the query.

The workload analysis subtask detected the The system displays this message at 5 minute
INTERVAL=1 parameter in the OC START ID=WLM intervals until function WSP initializes the user defined
command. interval, services classes and service policy, in storage.
Function WSP is triggered by IRAMAN KCPAGENT
System action SWLM.
System processing continues; the workload analysis

System action
subtask uses the interval specified on the Tivoli
Enterprise Portal CICS SLA view. Processing continues.

Remove the INTERVAL=1 parameter from If the message is displayed repeatedly after Tivoli
hilev.RKANCMDU(KC5AGST). if the agent is configured Enterprise Monitoring Server start up use the following
to run in its own address space, or the steps:
hilev.RKANCMDU(KDSAGST), if the agent is configured
1. Verify that member KC5AGST in the RKANCMD
to run in a Tivoli Enterprise Monitoring Server.
dataset contains the start command:
KCP0241 WSR - WLM COLLECTION WILL
START IRAMAN KCPAGENT SWLM
USE HH:MM: HRS. AS THE
COLLECTION INTERVAL 2. Verify that message KCP0259 DSI $WLMSP
INITIALIZATION COMPLETE was displayed in
Explanation RKLVLOG.
The workload summarizer subtask (WSR) displays this 3. If message KCP0259 is not found in RKLVLOG,
message at initialization time, or when the workload search RKLVLOG for WSP error messages:
analysis interval is changed at the workstation. It is an • KCP0211 and KCP0222
information message only.
• KCP0224 and KCP0225
• KCP0251 to KCP0258
System action
4. Perform the corrective action indicated for these
Processing continues. messages.
KCP0244 WSR - UNABLE TO OBTAIN
User response ACCUMULATION BUFFER, DATA
None. LOST
KCP0242 IWMPQRY MACRO FAILURE,
REASON CODE=reason. Explanation
The workload summarizer subtask (WSR) is unable
Explanation to obtain storage for an accumulation buffer. This
condition might occur in busy systems with many
The workload summarizer subtask (WSR) received CICS address spaces. The situation subsides when
reason code reason while attempting to obtain the the subtask catches up with the transaction volume
current z/OS service policy definition. arriving from the CICS address spaces. The data for
the transaction currently being processed does not
System action accumulate.
WSR stops processing.
System action
User response Processing continues.
User response
KCP0243 WSR WAITING FOR WORKLOAD
DEFINITIONS Use the /OC STATUS,WLMBLOCKS command to display
the current status of the values in the RKLVLOG output.

KCP0246 WSR REQUESTED TERMINATION User response
IN PROGRESS
None.
Explanation KCP0248 WSR ENFREQ ACTION=LISTEN

MACRO FAILURE, RC=rc
The workload summarizer subtask (WSR) has been
posted to terminate.
Explanation
System action Installation of the user exit that listens for changes in
z/OS's service policy failed with return code rc.
WSR ends.
System action
User response
The summarizer subtask stops processing if the choice
None. of rules is z/OS. If the choice of rules is AUTO
KCP0247 WSR - WLM COLLECTION or OMEGAMON, the summarizer subtask continues
USES cccccccc SERVICE POLICY processing.
service_policy, RULE: rule
User response
Explanation Contact IBM Software Support.
The workload summarizer subtask (WSR) issues this KCP0249 WSR ENFREQ ACTION=DELETE
message at initialization, or when a new service policy MACRO FAILURE, RC=rc
becomes effective.
The cccccccc value represents one of the following Explanation
service policies:
During termination processing, an attempt to delete
• OMEGAMON when the service policy is activated at the user exit that listens for z/OS service policy
the workstation from the CICS Workload Definitions changes failed with return code rc.
icon under the Administration folder.
• z/OS when the service policy was defined using the System action
z/OS WLM ISPF application.
Termination processing continues.
service_policy is the service policy name.
rule shows one of the following values: User response
• z/OS Service policies, workloads and service classes
defined under the z/OS WLM ISPF application are
used exclusively by the Tivoli Enterprise Monitoring KCP0251 WSP table FETCH REQUEST
Server. FAILURE, RC=rc
• z/OS Service policies, workloads and service classes
defined under the IBM WLM ISPF application are Explanation
used exclusively by the Tivoli Enterprise Monitoring
Server. Function WSP was unable to perform an SQL Fetch
for the table identified by table. rc is the return code
• AUTO Provides service-level analysis using first the generated by the SQL request. The table identified by
z/OS and then the native OMEGAMON workload table can be either the INTERVAL or SVPOL table. This
managers. The OMEGAMON for CICS on z/OS problem can occur if there is no interval specified for
workload-summarizer component ensures it can the workload analysis collector, or if there is no service
communicate with the z/OS WLM and get a copy of policy specified as active when the OMEGAMON
its service classes and goals. If for any LPAR, the workload definitions are being used.
z/OS definitions cannot be obtained, OMEGAMON for
CICS on z/OS uses the OMEGAMON service classes
and goals. System action
The function stops processing.
System action
Processing continues.

If the table is INTERVAL, use the workstation to verify Increase the size of the OMEGAMON for CICS on z/OS
that an interval is shown in the Interval and Rule region. If the problem persists, contact IBM Software
Choice panel of the CICS SLA view. If the table is Support.
SVPOL, select Service Policies in the Interval and Rule
KCP0255 function UNABLE TO ACQUIRE
Choice panel of the CICS SLA view, and activate a
SCLASS WORK STORAGE, RC=rc
service policy. If the problem persists, contact IBM
Software Support.
Explanation
KCP0252 function table FETCH RESULTED IN
NULL DATA The function identified by the function value was
unable to acquire work storage for the service class
work area. The rc value is the return code generated by
Explanation
the storage request.
An attempt by function function to perform an SQL
Fetch for table table unexpectedly resulted in null data System action
being returned.
The function identified by function value stops
processing.
System action
The function identified by function stops processing. User response
Increase the size of the OMEGAMON for CICS on z/OS
User response
region. If the problem persists, contact IBM Software
Contact IBM Software Support. Support.
KCP0253 function table CLOSE FAILURE, KCP0256 function UNABLE TO PROCESS
RC=rc TOKEN token FOR SERVICE CLASS
sclass
Explanation
Explanation
The function identified by function was unable to
perform an SQL CloseRequest for table table. rc is the The total length of the values specified to classify a
return code generated by the SQL request. service class exceeds allocated storage for the service
class.
System action
System action
The function identified by function value stops
User response processing.

User response
KCP0254 function UNABLE TO ACQUIRE Test to see if there are any Service Class definitions
STORAGE FOR storage that have missing rules by using the kcp_slabatch
validateserviceclass utility and take any required
Explanation corrective action. If problems persist, contact IBM
Software Support.
The function identified by the function value was
unable to acquire storage for the storage value control KCP0257 function UNABLE TO ALLOCATE
block. STORAGE FOR SERVICE CLASS
sclass
System action
Explanation
The function identified by the function value stops
processing. The function identified by function value was unable to
acquire storage for an internal control block.

System action • At data server initialization time
The function identified by the function value stops • When a service policy is activated or reactivated at
processing. the workstation
• When the rules choice is changed at the workstation
User response
System action
Increase the size of the OMEGAMON for CICS on z/OS
region. If the problem persists, contact IBM Software WSP processing stops. If the message appears at
Support. initialization, workloads data collection does not start.
If the message appears due to a service policy
KCP0258 function FAILURE PROCESSING activation/reactivation, or a change in the choice of
sclass rules at the workstation, workloads data collection
continues with the old definitions.
Explanation
The function identified by function value encountered User response
an error while processing the classification rules for If the message appears at initialization, issue the
the sclass value. A previous message described the following commands at the MVS console:
error.
F jobname,IRAMAN KCPAGENT SWLM
System action
Monitor the RKLVLOG output for the following
The function identified by the function value stops messages, which indicate normal completion of
processing. the initialization process. The user should see the
following messages:
User response KCP0280: SERVICE POLICY THREAD IS ACTIVE
Contact IBM Software Support. KCP0287: MOS PROCESSING OMEGAMON SERVICE
KCP0260 WSP MISSING GOAL ROW FOR CLASSES
SERVICE CLASS sclass KCP0288: MOS MOSTATUS PROCESSING COMPLETE
If the message appears because of a service policy
Explanation activation/reactivation, or because of a change in the
The function WSP did not find a GOAL table row for the choice of rules, retry the action at the workstation.
service class identified by the sclass value. KCP0262 MOSPR ZERO SERVICE POLICY
ADDRESS DETECTED
System action
Processing continues. Note that data collected for the Explanation
service class does not reflect the correct response Function MOS found that the current service policy
time goal. address was zero.

Enter the goal for the sclass value. The function stops processing.
KCP0261 WSP CRITICAL ERROR:
TABLE SCLASS RETURNED NO User response
ROWS, $WLMSP PROCESSING
ABANDONED Contact IBM Software Support.
KCP0263I WSS - The CICSplex service class
Explanation records will be freed to relieve a
data space storage constraint.
Function WSP found no rows in the SLCASS table,
which should contain the classification rules for
service classes. This message is displayed, if the
following exist:

Explanation KCP0269 WSR - STORAGE OBTAIN FOR
USER EXIT PARAMETER LIST
The workload summarizer subtask (WSS) is unable FAILURE, RC=rc
to obtain storage for an accumulation buffer. This
condition might occur in busy systems with many
CICS address spaces. The subtask attempts to delete Explanation
CICSplex service class records in order to catch up The workloads summarizer subtask received a return
with the transaction volume coming in from the CICS code rc value when attempting to obtain common
address spaces. storage for the parameter list of the ENF listener user
exit.
System action
System processing continues. System action
The summarizer subtask stops processing if the choice
User response of rules for workload analysis is the z/OS system.
It continues processing if the choice of rules is
None OMEGAMON.
KCP0264I WSS - The number of CICSplex
service class records freed is User response
nn,nnn
Investigate the reason for common storage to be
depleted, correct the problem and retry starting WLM.
Explanation
KCP0270W zzz AddData failed after xxx of yyy
The workload summarizer subtask (WSS) freed the rows.
nn,nnn number value of CICSplex service class
records in order to make room for new service class
summarization records. Explanation
During the collection of data, for the zzz collector, the
System action AddData function failed. This is most likely due to an
inability to obtain a large enough buffer to contain
System processing continues. the rowset. The request failed after xxx rows. The
complete results set was yyy rows.
User response
None System action
KCP0268 WSR - LOAD FOR MODULE module The contents of the data returned to the requester are
FAILED, RC=rc truncated after xxx rows.
User response:
Explanation You should look for the most recent KLVSD008
message, for extended main storage, in the RKLVLOG
The workload summarizer subtask received the return to determine the extent that carved storage has been
code rc value when attempting to load the module used. If the address space is near the limit of extended
value. carved storage you should consider increasing
the KC5_AGT_STORAGE_MINIMUM_EXTEND value
System action for the RTE. If Carved storage is not near
the limit you can consider increasing the
The summarizer subtask stops processing, if the KC5_X_AGT_STORAGE_LIMIT_EXTEND value. Each
choice of rules for workload analysis is the z/OS increase in the value by 1 doubles the size of storage
system. It continues processing if the choice of rules available.
is OMEGAMON. Ensure that module value is in the
STEPLIB for the Tivoli Enterprise Monitoring Server, KCP0271W zzz AddData failed after xxx of yyy
correct the problem and retry the command. rows.
/F stask,OC START ID=WLM

Explanation
where stask is the name of the started task for the During the collection of data, for the zzz collector, The
Tivoli Enterprise Monitoring Server. AddData function failed. This is most likely due to an

inability to obtain a large enough buffer to contain System action
the rowset. The request failed after xxx rows. The
complete results set was yyy rows. None.

The contents of the data returned to the requester are None.
truncated after xxx rows. KCP0281 IBM SERVICE CLASS COLLECTOR
User response: ALREADY ACTIVE
You should look for the most recent KLVSD008
message, for extended main storage, in the RKLVLOG Explanation
to determine the extent that carved storage has been
used. If the address space is near the limit of extended A command was issued to start the service policy
carved storage you should consider increasing thread, but it was already active.
for the RTE. If Carved storage is not near System action
the limit you can consider increasing the
KC5_X_AGT_STORAGE_LIMIT_EXTEND value. Each The second thread is not started
increase in the value by 1 doubles the size of storage
available. User response
KCP0272W zzz AddData failed after xxx of yyy None.
rows of CICS data.
KCP0282 SERVICE POLICY THREAD IS NOT
ACTIVE
Explanation
During the collection of data, for the zzz collector, The Explanation
AddData function failed. This is most likely due to an
inability to obtain a large enough buffer to contain A command to stop the service policy thread was
the rowset. The request failed after xxx rows. The issued, but the thread is not active.
complete results set was yyy rows.
System action
System action None.
The contents of the data returned to the requester are
truncated after xxx rows. User response
User response: None.
You should look for the most recent KLVSD008
message, for extended main storage, in the RKLVLOG KCP0283 SERVICE POLICY THREAD IS
to determine the extent that carved storage has been TERMINATING
used. If the address space is near the limit of extended
carved storage you should consider increasing Explanation
for the RTE. If Carved storage is not near The z/OS service policy thread has received a request
the limit you can consider increasing the to terminate.
KC5_X_AGT_STORAGE_LIMIT_EXTEND value. Each
increase in the value by 1 doubles the size of storage System action
available.
None.
KCP0280 SERVICE POLICY THREAD IS
ACTIVE
User response
Explanation None.
The z/OS service class collector has completed KCP0284 SERVICE POLICY THREAD IS NOT
initialization. RESPONDING

The service policy thread failed to stop processing None.
within thirty seconds after being notified to stop.
KCP0289 function SERVICE CLASSES
EXCEED AVAILABLE STORAGE
System action
The service policy thread stops processing when it Explanation
detects the shutdown request.
The function value has encountered an internal error
while attempting to build a list of service classes.
User response
None. System action
KCP0285 function INVALID RULE TYPE The function value stops processing.
DETECTED: x
User response
Explanation
The type of rule detected for Service Level Analysis is
KCP0290 function UNABLE TO LOAD
not OMEGAMON, z/OS, nor AUTO.
MODULE KCPISP0z
System action
Explanation
The function identified by the function value stops
processing. The function value attempted to load module
KCPISP0z, where z. is the z/OS release dependent
suffix.
User response
Contact IBM Software Support. System action
KCP0287 function PROCESSING XXXXXX The function value stops processing.
SERVICE CLASSES
User response
Explanation
Verify that module KCPISP0z is in the TLVLOAD
The function value is building a list of XXXXXX service concatenation.
classes; The XXXXXX indicates which, OMEGAMON,
z/OS, or AUTO. KCP0291 function ABEND RETRY IN
PROGRESS
System action
Explanation
None.
The function value has abended and is attempting
recovery.
User response
None. System action
KCP0288 function MOSTATUS PROCESSING The function value continues.
COMPLETE
User response
Explanation
None.
The function value has successfully finished building a
KCP0295I THE OMEGAMON KOCCI
list of service classes.
COLLECTOR ADDRESS SPACE IS
NOT MONITORING THE CICS
System action REGION AAAAAAAA.
None.

Explanation created to document the circumstances and provide
error information. The title of the dump describes the
The OMEGAMON collector (KOCCI) address space OMEGAMON CICS component that produced it. The
is not monitoring the CICS region. The value of xxx value can be FRB, FRR or blank, indicating where
AAAAAAAA is the specific CICS region. the message is issued from.

The query is ignored. Recovery is attempted and if not successful,
processing stops. Only one dump will be produced for
User response the error.
Ensure that OMEGAMON is installed and started in this
CICS region. Issue the OMEG INIT transaction. User response
KCP0296I AN INVALID RESOURCE NAME If the problem persists, contact IBM Software Support
WAS SPECIFIED TO RLIM. THE providing the job log and the dump.
RESOURCE WAS XXXXXXXX. KCP0740I THE SVC DUMP REQUEST FAILED
WITH RETURN CODE XX, REASON
Explanation CODE YY
A query was issued for the XXXXXXXX resource; this is
not a valid resource for the resource limiting feature. Explanation
The OMEGAMON CICS Recovery Routine intercepted
System action an ABEND and attempted to generate diagnostics
through an SVC DUMP. The XX value is the SDUMP
The query is ignored. return code and the YY value is the SDUMP reason
code. xxx is
User response
Ensure that you use a correct resource name to query System action
resource limiting. Recovery is attempted and if not successful,
KCP0330 RESPONSE TIME ANALYSIS processing stops.
COLLECTOR NOT ACTIVE FOR
CICS aaaaaaaa User response
If the problem persists, contact IBM Software Support.
Explanation
KCP0757I WAITING FOR THE PCLASS
The Response Time Analysis (RTA) collector is not MANAGER TO LOAD THE CICSPLEX
active in the OMEGAMON for CICS on z/OS common RULES
interface (OCCI) address space used to monitor the
CICS aaaaaaaa value.
Explanation
System action The agent is waiting for the cicsplex classification rules
manager to load the cicsplex classification rules.
The query is ignored.
System action
User response
The agent waits up to one minute for the cicsplex
Start the collector and retry the request. classification rules to be loaded. If the rules are
KCP0731I OMEGAMON CICS IS ABOUT TO loaded within one minute, then the agent issues the
TAKE AN SVC DUMP xxx KCP0758I message and initializes with the loaded
rules. Otherwise, the agent issues the KCP0759E
message and initializes with the default rules.
Explanation
An OMEGAMON CICS Recovery Routine intercepted User response
an error and will attempt recovery. Even though
recovery might be successful, an SVC dump may be None.

KCP0758I THE PCLASS MANAGER LOADED Explanation
THE CICSPLEX RULES
No OMEGAMON service tasks were available for use
when killing a task.
Explanation
The cicsplex classification rules manager loaded the System action
cicsplex classification rules.
The requested KILL action was not implemented.
System action
User response
The agent initializes with the loaded rules.
Ensure that the OMEGAMON service tasks are
available in the CICS region and retry the KILL action.
User response If the problem persists, contact IBM Software Support.
None. KCP0762 HOLD COUNT DISPLACEMENT
KCP0759E THE PCLASS MANAGER WAS VALIDATION FAILED
UNABLE TO LOAD THE CICSPLEX
RULES Explanation
OMEGAMON was unable to verify the location of the
Explanation hold count field in the OUCB control block.
The cicsplex classification rules manager failed to load
the defined cicsplex classification rules. System action
The cross-memory interface (XMI) task stops
System action processing because OMEGAMON components cannot
The agent initializes with default classification rules. verify a target address space if it is swapped out.

Check the cause of the failure by looking at the Contact IBM Software Support.
RKLVLOG output and the console logs for ABENDs. KCP0764 TAI DETECTED AN INCORRECT
KCP0760 LOAD OF module FAILED: WORK AREA LENGTH
CODE=abend, REASON=reason
Explanation
Explanation The size of the ECSA work area allocated by TAM
The load module value could not be loaded. The abend differs from that expected by the module TAI.
value is the abend code, and the reason value is the
reason code associated with the abend. System action
The cross memory interface task (XMI) abnormally
System action stops processing with a U0764 ABEND.
The session does not initiate.
User response
User response Contact IBM Software Support.
Locate the abend code in the IBM System Codes KCP0765W TAF DETECTED AN INCORRECT
manual, correct the cause of the load failure, and WORK AREA LENGTH
restart the session.
KCP0761I XMCR WAS UNABLE TO OBTAIN Explanation
STACK DURING KILL PROCESSING
An OMEGAMON function detected that is was provided
an incorrect work area. The most probable cause is
a failure to correctly apply service or load the correct
modules.

A system dump is produced. OMEGAMON stops Either use a CPXMITnn DD statement to start another
detecting new CICS regions. cross-memory interface task, or stop the Tivoli
Enterprise Monitoring Server in which the active task
User response is running.
Contact IBM Software Support. KCP0807I A ZIIP PROCESSOR IS NOT

AVAILABLE, OFFLOADING WILL
KCP0803 SSCVT CHAIN IS EMPTY NOT TAKE PLACE
The SSCVT chain was scanned, and was found to be An attempt to enable zIIP process offloading was
empty. made, but no zIIP processor is available.

The cross-memory interface (XMI) task abnormally System processing continues, but no zIIP processing
stops processing with a U0803 completion code. takes place.

Contact IBM Software Support. None
KCP0804 INVALID SSCVT FOUND ON CHAIN KCP0809 XM INTERFACE TASK IS ACTIVE
While searching through the Subsystem The cross-memory interface (XMI) task has completed
Communication Vector Table chain for the element initialization and is waiting for work.
belonging to OMEGAMON XE, the cross-memory
interface (XMI) task encountered an improperly
System action
formatted SSCVT.
None.
System action
User response
The cross-memory interface (XMI) task abnormally
stops processing with a U0804 completion code. None.
KCP0810 XM INTERFACE TASK IS
User response TERMINATING
Indicates that main storage was overlaid. If problems
persist, contact IBM Software Support. Explanation
KCP0808 XM INTERFACE TASK id ALREADY The cross-memory interface (XMI) task received a
ACTIVE IN job request to stop processing.

A second cross-memory interface task was started None.
while another one is still active. The CPXMIT number is
identified by id and the job running the interface task is User response
identified by job.
None.
System action KCP0811 XM INTERFACE TASK HAS
The subtask stops processing. ABENDED

The cross-memory interface (XMI) task error exit An internal error occurred during the attempt to create
intercepted an abnormal termination. the OMEGAMON for CICS on z/OS SSCVT and related
control blocks.
System action
System action
The cross-memory interface (XMI) task attempts
resource cleanup before continuing with termination. The cross-memory interface (XMI) task stops
processing.
User response
User response
Restart XMI, and contact IBM Software Support.
Ensure that no other attempt is being made to start the
KCP0812 XM INTERFACE TASK RESOURCE cross-memory interface task. Then attempt to start
CLEANUP IS COMPLETE the cross-memory interface task again.
Explanation KCP0816 ENTRY TABLE CREATE FAILED
The cross-memory interface (XMI) task successfully

Explanation
completed resource cleanup.
An error occurred during the attempt to build a
System action program call entry table.
None.
System action
User response The cross-memory interface (XMI) task abnormally
stops processing with a U0816 completion code.
None.
KCP0813 subtask ESTAEX MACRO FAILURE. User response
RC=rc Contact IBM Software Support.
Explanation KCP0817 LINKAGE INDEX RESERVE FAILED
The subtask denoted by the subtask value received a

Explanation
non zero return code from the ESTAEX macro; this is
usually caused by a lack of LSQA. An attempt to reserve a linkage index failed.

The subtask stops processing. The cross-memory interface (XMI) task abnormally
stops processing with a U0817 completion code.
User response
User response
The return code rc value for the ESTAEX macro is
described in the IBM Macro Reference manual. If the Contact IBM Software Support.
error was caused by a shortage of available storage,
decrease the Tivoli Enterprise Monitoring Server region KCP0818 program IS NOT A VALID
size and restart the subtask. If problems persist, PROGRAM NAME
contact IBM Software Support.
Explanation
KCP0815 SUBSYSTEM TABLE BUILD
FUNCTION WAS UNABLE TO A START command requested an invalid program name
CREATE ITS TABLES program value.
System action
START processing ends.

Correct the program name and enter the START An Abend has occurred, and has been trapped by
command again OMEGAMON. The MVS Software Diagnostic Area has
been passed to the recovery routine at the location
KCP0819 UNABLE TO CONNECT ENTRY displayed.
TABLE
System action
Explanation
The abend recovery continues.
An attempt to connect to the entry table created by
the cross-memory interface (XMI) task has failed.
User response
System action If problems persist, contact IBM Software Support.
The cross-memory interface (XMI) task abnormally KCP0981 Abend Sabendcode Uabendcode
stops processing with a U0819 completion code. has occurred in modname, Section
sectname, PSW XXXXXXXX
User response XXXXXXXX.

Explanation
KCP0920 IRA TIMEOUT OCCURRED WHILE An abend has occurred, and has been trapped by
COLLECTING DATA for CICS OMEGAMON. The MVS System and User Completion
AAAAAAAA Codes are displayed, along with the name of the
Module and CSECT that the abend occurred in, and the
Explanation failing PSW.
The agent intercepted a hard loop condition during
data collection for a specific CICS AAAAAAAA region. System action
System action
Data for the CICS region is not provided by the agent. User response
User response
KCP0982 R0-R7 XXXXXXXX XXXXXXXX
None. XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX
KCP0946 module1 (Vnnn) AND module2
(Vnnn) INCOMPATIBLE
Explanation
Explanation An abend has occurred, and has been trapped
by OMEGAMON. The contents of General Purpose
The versions of the module module1 value and
Registers 0 through 7 at the time of the abend are
the module it is attempting to load (module2) are
shown in hexadecimal format.
incompatible.
System action
System action
The load and its invoking facility failed.
User response
User response
Verify that the IBM Z OMEGAMON for CICS installation
process completed successfully, and that the module2 KCP0983 R8-R15 XXXXXXXX XXXXXXXX
value is in the Tivoli Enterprise Monitoring Server XXXXXXXX XXXXXXXX XXXXXXXX
library. XXXXXXXX XXXXXXXX XXXXXXXX
KCP0980 SDWA address

Explanation KCP0986 Storage addressed by GPR nn
An abend has occurred, and has been trapped
by OMEGAMON. The contents of General Purpose Explanation
Registers 8 through 15 at the time of the abend are The GPR nn value is a value between 00 and 15,
shown in hexadecimal format. denoting the General Register being displayed; this
message is always followed the KCP0985 message,
System action which attempts to display 16 bytes of main storage
addressed by the General Register.
System action
User response
KCP0984 Abend location address - adjacent User response
storage:
Explanation KCP0999 XMI INTERNAL ERROR – Call IBM
Software Support
An abend has occurred, and the abend location is
shown here. The storage in the immediate vicinity of
the abend location follows this message. Explanation
The cross-memory interface (XMI) task encountered
System action an event that should not occur.
System action
User response The cross-memory interface (XMI) task abnormally
stops processing.
KCP0985 aaaaaaaa XXXXXXXX XXXXXXXX User response
XXXXXXXX XXXXXXXX
cccccccccccccccc Contact IBM Software Support.
KCP1040I OCOMEG OMEGAMON II FOR CICS
Explanation WILL RETRY: INTERVAL ZZZZZZ
NOLIMIT
An abend has occurred, and has been trapped by
OMEGAMON. The contents of the 16 bytes at storage
location aaaaaaaa value are displayed in hexadecimal Explanation
and character format. The KOCOME00 program is run and detects that the
However, if the storage location is not retrievable common interface is not active. The INITPARM data
in the local address space, then it displays: was detected which specifies that a RETRY is to be
2005.124 14:15:47.29 KCP0985: 76543210 Not attempted, and the message text shows the user
displayable (Protected). specified interval and the number of retries that are
attempted. If there is no limit specified in the RETRY
If the abend occurred whilst the query is in cross- data for the number of attempts, the message displays
memory mode to a CICS Region, then the message the NOLIMIT;ZZZZZZ with the ZZZZZZ value specifying
displays: 2005.124 15:56:22.84 KCP0985: the interval.
1C087038 Not displayable (CICS).
System action
System action
The RETRY processing continues.
User response
User response
None.

KCP1041I OCOMEG OMEGAMON II FOR CICS User response
START REQUEST FAILED, EIBRESP
ZZ Enter the OMEG INIT command to initialize
OMEGAMON for CICS on z/OS; RETRY processing
restarts, if the common interface is not available.
Explanation
KCP1044I OCOMEG OMEGAMON II FOR
The RETRY processing issued an EXEC CICS START CICS RETRY PROCESSING IS NOT
request for the OMEGAMON transaction, but CICS ACTIVE
returned a nonzero return code in EIBRESP; the ZZ
value specifies the nonzero return code.
Explanation
System action The OMEG CANCEL command was entered, but there
was no RETRY processing currently being run.
The START request failed with the EIBRESP non zero
return code displayed in the message.
System action
User response None.
Review the EIBRESP in the OMEGAMON for CICS on

z/OS documentation to determine the appropriate next User response
steps. Enter the OMEG INIT command to initialize
KCP1042I OCOMEG OMEGAMON II FOR CICS OMEGAMON for CICS on z/OS; RETRY processing
RETRY LIMIT REACHED restarts, if the common interface is not available.
KCP1045E OCOMEG OMEGAMON II FOR
Explanation CICS INVALID RETRY PARAMETER
SPECIFIED:
The RETRY process ended when the specified number
of retry attempts was processed.
Explanation
System action During processing of the RETRY INITPARM data an
error was detected.
The RETRY process stops.
System action
User response
The OMEGAMON RETRY function stops. One attempt
The number of retry attempts is specified in the to connect to the OMEGAMON II address space is
RETRY data passed to KOCOME00 program in the CICS made, no further RETRY processing occurs.
INITPARM data. You can increase the value, up to a
value of 999999 (or leave the count blank, to specify
NOLIMIT). You can also log on to CICS and issue the User response
OMEG INIT command to restart the process. Review the RETRY parameter displayed in message
KCP1043I OCOMEG OMEGAMON II FOR KCP1046E and ensure that it conforms to the proper
CICS START REQUEST HAS BEEN format.
CANCELLED RETRY(hhmmss,count) where the hhmmss value is a
time value, specified in the range 1s - 99h 59m 59s
Explanation and count is a number in the range 1-999999. If
the count is omitted, the code attempts to reconnect
The OMEG CANCEL command was entered, which indefinitely. You can cancel the attempts by issuing
cancels any outstanding RETRY processing. the OMEG CANCEL command. Following the failure
of the RETRY process an attempt to connect to the
System action OMEGAMON II address space is made. If you have
coded an OCCIREQ DD card in the CICS JCL that
The RETRY process stops. is honored, otherwise you need to wait until the
OMEGAMON II address space is available, and activate
OMEGAMON using the OMEG INIT command.

KCP1046I OCOMEG OMEGAMON II FOR diagnosing a task that ends unexpectedly, or any other
CICS, retry parameter issues that result from killing a task.
KCP1051I KILL FORCE BY USERID OF
Explanation TRANID TRANID TASK TASKNO IN
CICS CICSJOB RESULTS_TEXT
During processing of the RETRY INITPARM data
an error was detected; this message follows the
KCP1045E message, and displays the RETRY data that Explanation
was provided as a CICS INITPARM to the KOCOME00
The KILL command was issued with the FORCE option.
program.
System action
System action
The task might be abnormally terminated with a CICS
The OMEGAMON RETRY function stops.
transaction dump.

See the KCP1045E message.
This WTO appears in SYSLOG and the OMEGAMON
KCP1047E OCOMEG OMEGAMON II FOR for CICS (3270) JOBLOG to document that a KILL
CICS RETRY PROCESSING HAS command with the FORCE option was attempted; this
STOPPED message is useful when diagnosing a task that ends
unexpectedly, or any other issues that result from
killing a task.
Explanation
KCP1101I TRK ITCAM FOR CICS PROGRAM
During processing of the RETRY INITPARM data
IS NOT INSTALLED
an error was detected. This message follows
the KCP1046I message and indicates that RETRY
processing has stopped. Explanation
An attempt was made to start ITCAM for CICS when it
System action was not installed or defined in the CICS region.
The OMEGAMON RETRY function stops. An attempt to
connect to the OMEGAMON II address space is made, System action
but no further RETRY processing occurs.
Processing continues and ITCAM for CICS is not
started.
User response
See message KCP1045E. User response
KCP1050I KILL BY USERID OF TRANID Verify that ITCAM for CICS is installed in the CICS
TRANID TASK TASKNO IN CICS regions and the required resources have been defined.
CICSJOB RESULTS_TEXT See ITCAM for Transactions z/OS Guide and Reference
for more information.
Explanation KCP1102I TRK NOT AUTHORIZED TO LINK
TO ITCAM FOR CICS
The KILL command was issued.

An attempt was made to start ITCAM for CICS, but the
The task might be abnormally terminated with a CICS
USERID defined in the PLTPIUSR SIT parameter does
transaction dump.
not have the authority to link to the ITCAM CYIPINIT
CICS program.
User response
This WTO appears in SYSLOG and the OMEGAMON System action
for CICS (3270) JOBLOG to document that a KILL
Processing continues and ITCAM for CICS is not
command was attempted; this message is useful when
started.

Verify that the USERID defined in the PLTPIUSR None. This message is controlled by the
SIT parameter is authorized to link to the CYIPINIT MCT_VALIDATION_MESSAGES= option of the
program. <USER_EVENT_MONITORING> section of the global
area.
KCP1103E TRK LINK TO CYIPINIT ITCAM
PROGRAM EIBRCODE: nnnnnnnn KCP1121I UMEX EXTRACTION ROUTINE
PROCESSING A DEFAULT CICS
Explanation MCT
An unidentified error occurred while an attempt was

Explanation
made to link to the CYIPINIT ITCAM for CICS program.
This message denotes nnnnnnnn as the hex contents OMEGAMON is extracting the information it uses from
of the CICS EIBRCODE for the command. the default CICS MCT.

Processing continues and the results might be None.
unpredictable.
User response
User response
None. This message is controlled by the
Check the CICS TS Application Programmers Reference MCT_VALIDATION_MESSAGES= option of the
for more information about EIBRCODE values. If <USER_EVENT_MONITORING> section in the Global.
necessary, contact IBM Software Support.
KCP1122I UMEX AN MCT ENTRY FOR name
KCP1104I TRK INSUFFICIENT WORK (description) IS NOT DEFINED
AREA FOR ITCAM FOR CICS
ENABLEMENT Explanation
The EMP indicated has not been defined in the MCT.
Explanation
The ITCAM for CICS enablement code was invoked System action
with a work area that was not valid.
The monitoring data for the EMP indicated is not
available to OMEGAMON II for CICS.
System action
A system dump is produced. User response
Modify the MCT as required.
User response
Retain the contents of the system log file and dump, KCP1123I UMEX AN MCT ENTRY FOR name
and contact IBM Software Support. IS NOT DEFINED
KCP1120I UMEX EXTRACTION ROUTINE Explanation

PROCESSING mctname
The EMP indicated has not been defined in the MCT.
Explanation
System action
OMEGAMON is extracting the information it uses from
the specified CICS MCT. The monitoring data for the EMP indicated is not
System action
User response
None.
KCP1124W UMEX AN MCT ENTRY FOR name
IS EXCLUDED FROM THE MCT

The EMP indicated has been excluded in the MCT. No OMEGAMON CICS data is added to the CICS
SMF record. The data is not available for historical
System action reporting.

User response
User response KCP1127I UMEX NO OMEGAMON CICS DATA
Modify the MCT as required. WILL BE ADDED TO THE CICS
RECORD
KCP1125E UMEX AN MCT ENTRY FOR name
(description) IS INCORRECTLY
Explanation
DEFINED
No OMEGAMON EMPs have been defined in this CICS
Explanation MCT.
The EMP indicated has been coded in

System action
the MCT with an incorrect length on the
PERFORM=(MOVE(offset,length)). No OMEGAMON CICS data is added to the CICS
SMF record. The data is not available for historical
System action reporting.

User response
User response KCP1128I UMEX OMEGAMON CICS DATA
Modify the MCT as in the samples in FOR THE FOLLOWING EMPS IS
TKANSAM(KOCMCT*). AVAILABLE
KCP1126E UMEX AN MCT ENTRY FOR name

Explanation
IS INCORRECTLY DEFINED
Introduces a list of OMEGAMON EMPs found in this
Explanation CICS MCT.
The EMP indicated has been coded in

System action
the MCT with an incorrect length on the
PERFORM=(MOVE(offset,length)). None.

The monitoring data for the EMP indicated is not None.
KCP1129I UMEX OMEGAMON CICS BASIC
SECTION (name)
User response
Modify the MCT as in the samples in Explanation
TKANSAM(KOCMCT*).
This message provides a list of OMEGAMON EMPs
KCP1127I UMEX NO OMEGAMON CICS EMPS found in this CICS MCT.
ARE DEFINED IN THIS MCT
This message can also be read in the following ways:
Explanation • KCP1129I UMEX OMEGAMON CICS DB2 (name)

• KCP1129I UMEX OMEGAMON CICS DLI (name)
No OMEGAMON EMPs have been defined in this CICS
MCT. • KCP1129I UMEX OMEGAMON CICS MQ (name)

• KCP1129I UMEX OMEGAMON CICS USER Explanation
DEFINED EVENT (name)
There is a severe error in CICS.
• KCP1129I UMEX OMEGAMON CICS WLOM EMP
(CAMWLMSC)
System action
• KCP1129I UMEX OMEGAMON CICS DATA FOR
CICS PA (OMEGCICS) This results in the loss of OMEGAMON function.

None. Contact IBM Software Support.
KCP1133I UMEX MCT PROCESSING HAS
User response COMPLETED
None.
Explanation
KCP1130I UMEX DUPLICATE OMEGAMON
CICS DATA MAY BE DELIVERED OMEGAMON has completed processing this CICS MCT.

Both the OMEGAMON Basic Section EMP and one None.
or more of the individual fields that comprise that
segment have been used. User response
None.
System action
KCP1201E THE MANAGED SYSTEMS
OMEGAMON II for CICS might write duplicate data to
MANAGER CANNOT
CMF.
COMMUNICATE WITH THE
OMEGAMON CICS AGENT.
User response
Choose either the Basic Section or the selective Explanation
method of collecting the data, not both. The Basic
The system was unable to locate the address of the
Section is specified by the BASIC_SECTION= option
communication control block for the OMEGAMON CICS
of the <USER_EVENT_MONITORING> section in the
agent.
Global Data Area, and defaults to OMEGBSC.
KCP1131I UMEX OMEGAMON CICS DATA System action
REDUCTION IS IN EFFECT
The managed systems manager task stops processing.
Explanation
User response
One or more of the individual fields that comprise the
OMEGAMON Basic Section EMP have been used. Confirm that XMI successfully started as a subtask
of the address space. Ensure that there is a START
command in the KC5AGST member of RKANCMDU
System action
file that automatically starts XMI. If problems persist,
OMEGAMON II for CICS writes less data to CMF, which contact IBM Software Support.
is added to the CICS SMF 110 record.
KCP1202I THE MANAGED SYSTEMS
MANAGER THREAD IS ALREADY
User response ACTIVE.
None.
Explanation
KCP1132E UMEX THE MCT CONTAINS NO
ENTRIES TO PROCESS A command was issued to start the managed systems
manager thread, but it was already active.

The second thread is not started. Contact IBM Software Support.
KCP1207E MANAGED SYSTEMS MANAGER
User response LOOKUP RESULTED IN NULL DATA
None.
Explanation
MANAGER THREAD IS NOT An attempt by the managed systems manager
ACTIVE. lookup function to perform an SQL Fetch request
unexpectedly resulted in null data being returned.
Explanation
System action
A command to stop the managed systems manager
thread was issued, but the thread is not active. The managed systems manager task stops processing.

None. Contact IBM Software Support.
User response INPUT SQLDA ERROR,
None. COLUMNS=nn

Explanation
MANAGER THREAD IS NOT
RESPONDING. The number of columns expected by the CICS agent
does not match the column count returned in the
Explanation SQLDA. The columns=nn value shows the number of
columns contained in the SQLDA input buffer.
The managed systems manager failed to stop
processing within 30 seconds after being notified to
System action
stop.
The managed systems manager task stops processing.
System action
User response
The managed systems manager stops processing
when it detects the shutdown request. Contact IBM Software Support.
User response MANAGER THREAD IS ACTIVE
None.
Explanation
LOOKUP CREATE PATH FAILURE, The managed systems manager task has completed
RC=rc initialization.

The managed systems manager lookup function was None.
unable to perform a SQL CreatePath request. The rc
value is the return code generated by the SQL request. User response
None.
System action
The managed systems manager task stops processing. KCP1221I THE MANAGED SYSTEMS
MANAGER THREAD IS
TERMINATING

The managed systems manager task has received a The CICSplex classification rules manager found no
request to stop processing. rows in the PLCASS table, which should contain the
cicsplex classification rules.
System action
System action
None.
The CICSplex classification rules manager task stops
None.
User response
KCP1222I OCSRV SERVICE TASKS HAVE NOT Contact IBM Software Support.
SHUTDOWN. REMOVE FUNCTION
NOW DISABLED KCP1260E THE PCLASS MANAGER CANNOT
COMMUNICATE WITH THE
Explanation OMEGAMON CICS AGENT
During a shutdown of the OMEGAMON service tasks,

Explanation
one of the service tasks did not shut down within one
minute. This can occur if a task requires an ENQUEUE The system was unable to locate the address of the
or other lock which has not been released. communication control block for the OMEGAMON CICS
agent.
System action
System action
The shutdown continues, but the OMEG REMOVE
function cannot be performed, as this has the potential The CICSplex classification rules manager task stops
to cause the service task to ABEND. The OMEGAMON processing.
components in CICS cannot be updated without
restarting the CICS region. Any OMEG RECYCLE User response
request will be treated as an OMEG SHUT followed by
an OMEG INIT. Confirm that XMI successfully started as a subtask
of the address space. Ensure that there is a START
User response
file that automatically starts XMI. If problems persist,
None required. contact IBM Software Support.
KCP1256E PCLASS TABLE tname FETCH KCP1261I THE PCLASS MANAGER THREAD
RESULTED IN NULL DATA IS ALREADY ACTIVE
Explanation:
The CICSplex classification rules manager found no Explanation
rows in the table named tname that contains the
A command was issued to start the CICSplex
CICSplex classification rules.
classification rules manager thread, but it was already
System action: active.
processing. System action
User response: The second thread is not started.
KCP1259E PCLASS MANAGER CRITICAL User response
ERROR: TABLE PCLASS
RETURNED NO ROWS, None.
PROCESSING STOPPED
KCP1262I THE PCLASS MANAGER THREAD
IS NOT ACTIVE

A command to stop the CICSplex classification rules None.
manager thread was issued, but the thread is not
KCP1270E THE BTE MANAGER WAS UNABLE
active.
TO ACQUIRE tttttttt WORK
STORAGE, RC=xxxxxxxx
System action
None. Explanation
The Background Task Manager was unable to acquire
User response work storage. The xxxxxxxx value is the return code
None. generated by the storage request.

System action
IS NOT RESPONDING
The Background Task manager stops processing.
Explanation
User response
The CICSplex classification rules manager failed to
stop processing within thirty seconds after being Increase the size of the OMEGAMON for CICS on z/OS
notified to stop. region. If the problem persists, contact IBM Software
Support.
System action KCP1271I Background task list is empty,
The CICSplex classification rules manager stops processing continues
processing when it detects the shutdown request.
Explanation
User response The CICSplex Background Task manager does not
None. have any transactions specified.

System action
IS ACTIVE
The CICSplex Background Task manager continues to
Explanation monitor for changes.
The CICSplex classification rules manager task has

User response
completed initialization.
None.
System action KCP1272E THE BTE MANAGER CANNOT
None. COMMUNICATE WITH THE
OMEGAMON CICS AGENT
User response
Explanation
None.
KCP1265I THE PCLASS MANAGER THREAD communication control block for the OMEGAMON CICS
IS TERMINATING agent.

The CICSplex classification rules manager task has The Background Task manager task stops processing.
received a request to stop processing.
User response
System action
Confirm that XMI successfully started as a subtask
None. of the address space. Ensure that there is a START

file that automatically starts XMI. If problems persist, System action
None.
KCP1273I THE BTE MANAGER THREAD IS
ALREADY ACTIVE
User response
Explanation None.
A command was issued to start the Background Task KCP1278I THE BTE MANAGER THREAD IS
manager thread, but it was already active. TERMINATING

The second thread is not started. The Background Task manager task has received a
request to stop processing.
User response
System action
None.
None.
KCP1274I THE BTE MANAGER THREAD IS
NOT ACTIVE
User response
Explanation None.
A command to stop the Background Task manager KCP1300E OCSR2 Program Module KOCSR3zz
thread was issued, but the thread is not active. Not Loaded

None. Program module KOCSR3zz was not loaded by IBM Z
OMEGAMON for CICS.
User response
System action
None.
The CICSPlex/SM system group definition information
KCP1275I THE BTE MANAGER THREAD IS will not be available.
NOT RESPONDING
User response
Explanation
Contact IBM Software Support with JESLOG of the
The Background Task manager failed to stop CICS job.
processing within thirty seconds after being notified to
stop. KCP1301E OCSR3 Missing OCSR2 Work Area
Address
System action
Explanation
The Background Task manager stops processing when
it detects the shutdown request. The required work area was not passed to the
CICSPlex/SM information collector when called by the
IBM Z OMEGAMON for CICS Secondary Service Task.
User response
None. System action
KCP1276I THE BTE MANAGER THREAD IS An internal error occurred resulting in CICSPlex/SM
ACTIVE system group definition information being unavailable.

The Background Task manager task has completed Contact IBM Software Support with JESLOG of the
initialization. CICS job.

KCP1302E OCSR3 Failed Local Buffer User response
Allocation
Enable the required Task-Related User Exit program.
Explanation KCP1305E X=xxxxxxxx S=ssssssss T=tttttttt

R=rrrrrrrr C=cccccccc L=llllllll
The CICSPlex/SM information collector failed to
allocate a local buffer required for processing EXEC
CPSM commands. Explanation
The IBM Z OMEGAMON for CICS Service Task failed to
System action execute a CICSPlex/SM API, where:
The CICSPlex/SM system group definition information • xxxxxxxx indicates the Context.
will not be available. • ssssssss indicates the Scope.
• tttttttt indicates the Thread ID.
User response • rrrrrrrr indicates the Result set ID.
Contact IBM Software Support with JESLOG of the • cccccccc indicates the Count.
CICS job.
• llllllll indicates the length.
KCP1303E CPSM cccccccc FAILED RESPONSE Note: This message is accompanied by message
= pppppppp REASON=rrrrrrrr KCP1303E, which describes the CPSM resource table
and the API command being executed.
Explanation
The IBM Z OMEGAMON for CICS Service Task failed to System action
execute a CICSPlex/SM API, where: An internal error occurred resulting in CICSPlex/SM
• cccccccc indicates the failing CICSPlex/SM API system group definition information not being
name. available.
• pppppppp indicates the CICS response code.
• rrrrrrrr indicates the CICS reason code. User response
Contact IBM Software Support with JESLOG of the
System action CICS job.
An internal error occurred resulting in CICSPlex/SM KCP2455E Invalid character found in vvvv
system group definition information not being value.
available.
Explanation
User response The vvvv value, which is either TRAN, TERM or
Contact IBM Software Support with JESLOG of the DURATION, contains an invalid character.
CICS job.
KCP1304E OCSR2 Task-Related User System action
Exit Program EYU9XLAP Not The command stops processing; no action is taken.
Connected to DFHERM
User response
Explanation
Correct the command and run it again.
The CICSPlex/SM information collector is not able to
perform CPSM API requests because the Task-related KCP4000E SET command translation error:
User Exit (TRUE) program EYU9XLAP is disabled or not text.
connected to its external resource manager.
Explanation
System action The SET command contains a syntax error. The
The CICSPlex/SM information is not collected. textvalue is a message from CICS explaining the
command translation error.

The SET command is not executed. Correct the Action command.
KCP4005E An unknown error was returned by
User response the TDA call.
Correct the error and resubmit the command.
Explanation
KCP4001E SET command execution
error:text. An internal error has occurred.

CICS determined that it can not execute the SET The Action command is bypassed.
command. The textvalue is a message from CICS
explaining the command execution error. User response
System action
KCP4007I Purge has been scheduled for the
The SET command is not executed.
selected AID.
User response
Explanation
Correct the error and resubmit the command.
The AID KILL has been scheduled.
KCP4003E Action command is missing.
System action
Explanation
None.
The Action command was not recognized.
User response
System action
None.
The Action command is bypassed.
KCP4008W Specify the KILL option to purge
this AID.
User response
Correct the Action command to be one of the following Explanation
commands:
The AID was located by the service task, but the KILL
• AIDK option was not specified by the AIDK command. The
• ICEK AID is not killed.
• SET
System action
• TDDL
• TSQD The AIDK command completes processing.
• WTO
User response
KCP4004E Action command is invalid.
If your intent is to KILL the AID, append the KILL
option to the Action command.
Explanation
KCP4009W The selected AID is invalid.
The Action command was not specified correctly.
Explanation
System action
The AID address must be a valid eight character
The Action command is bypassed. hexadecimal address.

System action KCP4013W Specify the KILL option to cancel
this ICE.
The AIDK command fails.
Explanation
User response
The ICE was located by the service task, but the KILL
Enter a valid eight character hexadecimal address, or option was not specified by the ICEK command; the
use the Tivoli Enterprise Portal variable substitution. ICE is not killed.
KCP4010E The selected AID cannot be
located in CICS. System action
The ICEK command completes.
Explanation
The AID address was no longer in the AID chain. It was User response
either already killed, or had completed processing, and
was de chained by CICS. If your intent is to KILL the ICE, append the KILL
option to the Action command.
System action KCP4014W The selected ICE is invalid.
Explanation
User response The ICE address must be a valid eight character
hexadecimal address.
None.
Note: If your site turns on security for the OMEGAMON System action
for CICS on z/OS Take Action commands within Tivoli
Enterprise Portal (your site specifies environment The ICEK command fails.
variable KC5_FTA_SECURITY=YES), then the only valid
responses from the External Security Manager (ESM) User response
are either permitted or not permitted. Any other
response cannot be processed; in this case, the Enter a valid eight character hexadecimal address, or
Tivoli Enterprise Portal response is to deny access use the Tivoli Enterprise Portal variable substitution.
to the command. Depending on the ESM response, KCP4015E The selected ICE cannot be
the following Tivoli Enterprise Portal messages are located in CICS.
returned to the RKLVLOG file:
• KCP4020I for not permitted Explanation
• KCP4021E for an invalid ESM response
The ICE is no longer in the ICE chain. It has either
If the Take Action command is allowed, a different already been killed, or has completed processing
Tivoli Enterprise Portal message is issued that and has been de chained by CICS. Kill processing is
indicates the result of the command, for example, bypassed, if the ICE type is Wait or Post, or, if the ICE
KCP4018I. is a DWE.
KCP4012I Cancel has been scheduled for the
selected ICE. System action
The ICEK command fails.
Explanation
The ICE KILL has been scheduled. User response
None.
System action
KCP4016I The SET command has been sent
None. to CICS.

None. The SET command was passed to the CEMT interface.

None. An SAF call to the External Security Manager could not
determine if this user is permitted to issue this Take
User response Action command, or an error prevented authorization
of the user to issue this Take Action command. The
None. <text> variable can be any of those listed under the
KCP4027I message except the first three.
KCP4017E The SET command has failed.
System action
Explanation
The command is bypassed.
An unexpected error occurred when passing the SET
command to the CEMT interface.
User response
System action Review messages KCP4025I, KCP4027I, and, if
present, KCP4026I in the RKLVLOG output to
The SET command might not have been completed.
determine why the SAF call did not succeed.
User response KCP4022E UNABLE TO LOAD MODULE module
Verify that the action is still required, and if necessary,

Explanation
issue the SET command again.
An unexpected error was encountered.
KCP4018I The WTO command has been
issued.
System action
Explanation If the <module> variable is KCPTAV00, the Take Action
commands are bypassed; if the module variable is
The WTO text has been sent to the system log.
KCPPPI00, command logging is bypassed.

Message KCP4032I appears in the system log with the
These modules should be in the RKANMODL library;
specified text.
validate your product installation. If the problem
occurs again, contact IBM Software Support.
User response
KCP4023E NetView logging failed: rc.
None.
KCP4020I USER IS NOT AUTHORIZED FOR Explanation
THIS ACTION.
An unexpected error was encountered when logging a
command to the NetView® on z/OS program.
Explanation
An SAF call to the External Security Manager has System action
determined that this user is not permitted to issue this
The Take Action command logging is bypassed.
Take Action command.
User response
System action
Depends on the rc returned:
The command is bypassed.
• 0C04 - indicates initialization errors; review the
RKLVLOG for messages, for example, KCP4024E.
User response
• 0C08 - indicates that the agent is not APF-
None. authorized.
KCP4021E <text> • 0C0C - indicates an internal error. Contact IBM
Software Support.

• 0C10 - indicates an internal error. Contact IBM User response
Software Support.
If diagnosing a validation error, refer to the NetView
For other return codes, refer to the NetView for z/OS Security Server RACROUTE Macro Reference manual
Application Programmer Guide. to understand the return codes from the RACROUTE
KCP4024E NETVIEW MODULE CNMCNETV request.
NOT FOUND. KCP4027I USER=<username> RESULT: <text>
NetView PPI module, CNMCNETV, was not found. This message displays the security decision. The
<text> variable can be one of the following messages:
System action • USER IS AUTHORIZED FOR THIS ACTION
The Take Action command logging to NetView is • VALIDATION NOT REQUESTED
bypassed. Command logging to the RKLVLOG output
• USER IS NOT AUTHORIZED FOR THIS ACTION
file continues.
• NO SECURITY DECISION COULD BE MADE
User response • INVALID USER NAME PASSED
• INVALID RESOURCE NAME PASSED
Ensure that the NetView CNMLINK library is available
to the address space; this can be through JPA, • RESOURCE NAME IS TOO LONG FOR THIS CLASS
TASKLIB, STEPLIB or JOBLIB, LPA, LNKLST, or • INVALID CLASS SPECIFIED IN KPPENV FILE
RKANMODL.
• AGENT NOT APF AUTHORIZED
KCP4025I USER=<username> • ESM OR SPECIFIED CLASS INACTIVE
CLASS=<classname>
• SPECIFIED CLASS INACTIVE
RESOURCE=<resourcename>
• USER NOT DEFINED TO ESM
Explanation • REJECTED BY INSTALLATION AUTHORIZATION
EXIT
This message displays the input to the command
validation; the <resourcename> variable is in the • UNEXPECTED SAF/ESM RETURN CODE
format: cicsname.KCP.function.value
System action
System action None.
None.
User response
User response If diagnosing a validation error, this message indicates
None. either the decision based upon the RACROUTE request
or an error unrelated to RACROUTE.
KCP4026I RACROUTE <request>
REG15=<r15> SAFPRRET=<prret> KCP4028E OCCVT NOT FOUND
SAFPRREA=<prrea>
SAFPSFRC=<psfrc> Explanation
SAFPSFRS=<psfrs>
An unexpected error was encountered.
Explanation
System action
This message displays the response from the last
The Take Action commands are bypassed.
RACROUTE request, where the <request> variable is
STAT, VERIFY, or AUTH.
User response
System action Review the RKLVLOG output for messages indicating
serious problems with the OMEGAMON for CICS on
The security decision is made based upon this
z/OS agent.
response.

KCP4029E $GMEM FAILED fixed, the rest of the message text is specified in the
take action command request. The take action WTO
command allows you to send text, with substituted
Explanation
variables, to the console using a situation or a
An error was encountered obtaining memory for the command. The user specified message text value can
environment (KppENV) variables. be used as input to a console automation package.

The Take Action commands are bypassed. None.

Review the RKLVLOG output for messages indicating None.
memory problems.
Parent topic: OC messages
KCP4030I USER <username> CICS <region>
KCP4033I TAKE ACTION SECURITY IS NOT
COMMAND c<cmd>
ACTIVE; OMEGDEMO CLASS WAS
SPECIFIED.
Explanation
This message is displayed in the NetView log if Explanation
KC5_FTA_SEC_LOG=YES was specified. It displays the
The class specified for Take Action command security
content of the Take Action command (with the CP:
was set to OMEGDEMO. This is a reserved name used
prefix removed).
to indicate that no SAF checking is required.

None.
System processing continues. The Take Action
commands with the prefix CP will have no authority
User response checking performed by the OMEGAMON for CICS on
z/OS agent.
None.
KCP4031I USER <username> CICS <region> User response
RESULT <message text showing
command result>. If security checking was desired then select a different
class name.
Explanation KCP4151 GROUPNUM CANNOT BE USED
MULTIPLE TIMES
This message is displayed in the NetView log if
KC5_FTA_SEC_LOG=YES was specified. It displays
the KCP message resulting from the Take Action Explanation
command.
Either multiple predicates in the same query include
the GROUPNUM column, or an arithmetic operator
System action other than EQ is used in the expression.
None.
System action
User response The query is ignored.
None.
User response
KCP4032I WTO user specified message text
Limit the use of GROUPNUM to a single predicate and
ensure that the predicate specifies equal (EQ), rather
Explanation than some other operator.
This message is issued in response to a take action
KCP4153 GROUPNUM FILTER VALUE nn
WTO request. The message number and WTO text are
MUST BE BETWEEN 1 AND 30

Explanation KCP4250E An unexpected error occurred
in the TRAC command. See the
A query requested a GROUPNUM of nn that is outside RKLVLOG output.
the range of permissible group numbers.
Explanation
System action
The CP:TRAC take action command was unable
The query is ignored. to process. Refer to the RKLVLOG output for the
messages that provide the details of the failure.
User response
Change the group number to be in the range 1-30 and System action
resubmit the request. The command stops. No action is taken.
KCP4247E An invalid repeat was specified for
the TRAC command. User response
Refer to the RKLVLOG output. If required, contact IBM
Explanation Software Support.
The Repeat value specified on the ATFF command was KCP4251I The TRAC command successfully
either not specified or contained invalid value. was successful in processing.
System action:
The command stops; no action is taken. Explanation
The CP:TRAC take action command was successfully
User response processed.
Correct the Repeat value specified on ATFF command
and try the command again. System action
KCP4248E An invalid call type was specified The take action command completes.
for the TRAC command.
User response
Explanation
None.
The value specified for CALL TYPE is not supported.
KCP4252E The keyword value was not
recognized for the TRAC
System action command.
The command stops. No action is taken.
Explanation
User response The CP:TRAC take action command contained a
Specify a valid call type and try again. keyword value that was not applicable for the
command.
KCP4249E An invalid exec call was specified
for the TRAC command.
System action
Explanation The command stops. No action is taken.
The value specified for EXEC CALL is not supported.

User response
System action Correct the keyword value in the command and try to
issue the command again.
KCP4253E An invalid command was passed
to the TRAC processor.
User response
Specify a valid exec call.

An internal error occurred. The trace command The command stops. No action is taken.
processor received a command that was not a
CP:TRAC command. User response
Correct the value for the command and try again.
System action
The command processing stops. KCP4257E OMEGAMON is not active in the
target CICS region.
User response
Explanation
OMEGAMON is not active in the selected CICS region;
KCP4254E An invalid task number was it is not possible to enable trace in a CICS region
specified for the TRAC command. where OMEGAMON is not currently enabled.

The CP:TRAC command received a task number that The command stops; no action is taken.
was not a valid number for a CICS task. The trace
command only enables trace for tasks that have User response
numeric task numbers; it processes system tasks with
numbers such as III. Start or restart OMEGAMON in the CICS region by
using the OMEG INIT transaction.
System action KCP4258W The task number specified could
not be located.

The CP:TRAC take action command provided a task
Correct the task number and issue the command
number that could not be located in the target CICS
again.
region; it is possible that the transaction has ended or
KCP4255E An invalid character was found in the command was not specified correctly.
vvvv VALUE.
System action
Explanation
The command stops; no action is taken.
The vvvv value, which is either TRAN or TERM,
DURATION or SIZE, contains an invalid character. User response
Determine if the task is still active. If necessary, issue
System action
the command with a task number that is currently
The command stops; no action is taken. active.
KCP4259E The TRAN= or TASK= keywords
User response must be specified for the TRAC
Correct the value for the command and try again. command.
KCP4256E An invalid value was specified for

Explanation
vvvv in the TRAC command.
The CP:TRAC take action command requires that
Explanation either the task number or the transaction identifier be
provided.
The value vvvv, which is either TRAN or TERM,
DURATION or SIZE, is either missing or contains more
System action
than the four character maximum value.

Make the correction to the command and issue the The duration of the update for the command is
command again. continuing; issue the command again.
KCP4260E The OMEGAMON common KCP4263W The trace filter matches an
interface is not active. existing entry.
The OMEGAMON common interface (KOCCI) could not An attempt was made to add a trace filter for a time
be located in the CICS region. span that overlapped an existing trace filter for the
same criteria. Only one filter for the same criteria can
System action be active at any given time.

System action
User response The command stops; no action is taken.
Restart the common interface for OMEGAMON for

User response
CICS on z/OS and start OMEGAMON in the required
region. Issue the command again.
KCP4261E The TRAC command cannot add KCP4264E No space remains to add the
trace filters to this version of the requested trace filter.
OMEGAMON common interface.
Explanation
Explanation
There is no space remaining to add any more trace
This version of the common interface for the CP:TRAC filters.
command cannot add the first filter for a CICS region.
If a filter has been added using the OMEGAMON for System action
CICS (3270) interface, then the CP:TRAC command is
able to add subsequent trace filters. The command stops; no action is taken.

The command stops; no action is taken. Manage the trace filters in the OMEGAMON for CICS
(3270) interface.
User response KCP4265I APPLICATION TRACE HAS BEEN
Either use the OMEGAMON for CICS (3270) interface ENABLED FOR CICS REGION
to add a trace filter or upgrade the common interface cccccccc.
to the same version as the agent.
Explanation
KCP4262W The OMEGAMON trace filters are
currently being updated, please The CP:TRAC command has been invoked to enable
try again later. Application Trace. The Application Trace feature
is disabled in CICS and the CP:TRAC take action
command enabled it.
Explanation
The trace filters for a CICS region can only be updated System action
by one user at a time. They are reserved for the
duration of the command. The Application Trace feature and any required exits
are enabled in CICS. Only tasks that explicitly have
trace turned on or that match existing filters have trace
System action
data collected.

None. Investigate the RKLVLOG output to determine the
cause of the error.
KCP4266E Error refreshing filters in CICS.
See the RKLVLOG for more KCP4269E An enable trace error occurred in
information. CICS region cccccccc:text.
A service task error occurred when attempting to A service task error occurred when attempting to
refresh the trace filters in CICS. The RKLVLOG output enable Application Trace in the CICS region cccccccc
contains the KCP4267E message with more detailed value. The text value contents describes the reason for
information. the failure in more detail.

The command stops; no action is taken. The command stops and Application Trace in CICS is
not enabled.
User response
User response
Investigate the RKLVLOG output to determine the
cause of the error Use the text value to determine the cause of the
failure.
KCP4267E Filter add service task error. CICS
cccccccc: text. KCP4270E A disable trace error occurred in
CICS region cccccccc:text.
Explanation
Explanation
A service task error occurred when attempting to
refresh the trace filters in the cccccccc CICS region. A service task error occurred when attempting to
The text value contents describe the reason for the disable Application Trace in the CICS region cccccccc
failure in more detail. value. The contents of the text value describe the
reason for the failure in more detail.
System action
System action
The command stops, and Application Trace in CICS is
User response not disabled.
Use the text value to determine the cause of the

User response
failure.
Use the text value to determine the cause of the
KCP4268E An error occurred enabling failure.
Application Trace in CICS. See the
RKLVLOG for more information. KCP4271I Trace was successfully activated.
A service task error occurred when attempting to The command successfully activated the application
enable Application Trace in CICS. The RKLVLOG output trace feature.
contains the KCP4269E message with more detailed
information. System action
The Application Trace feature and any required exits
System action
are enabled in CICS. Only tasks that explicitly have
The command stops; no action is taken. trace turned on or that match existing filters have trace
data collected.

None The command successfully deleted the application
trace filter.
KCP4272I Trace was successfully
deactivated.
System action
Explanation The filter is deleted, and tasks that match the filter no
longer collect application trace information.
The command successfully deactivated the application
trace feature.
User response
System action None.
The Application Trace feature and any required exits KCP4276E The delete trace command was
are disabled in CICS. incomplete.

None The command to delete a trace filter did not contain all
the required values required to identify the filter.
KCP4273E An error in the date or time field
was detected.
System action
Explanation The command stops processing.
The date or time field contained invalid characters or
an invalid date or time value. User response
Enter the command again, and ensure that the
System action following parameters are specified: TRAN, TERM,
DURATION, OWNER, USER, DATE and TIME.
The command stops processing.
KCP4277I The specified trace filter could not
User response be located.
Correct the invalid value and resubmit the command.

Explanation
KCP4274I The trace filter was successfully A command to delete a trace filter could not locate a
added. filter that matched the provided values.

The command successfully created the application The command stops processing.
trace filter operation that was requested.
User response
System action
This error could be the result of another user having
The new filter is created and tasks matching the deleted the trace filter or the values being processed
specified values are eligible for application trace. incorrectly.
User response KCP4278I The trace filter was successfully

modified.
None.
KCP4275I The trace filter was successfully Explanation
deleted. The trace filter modification completed successfully.

Processing continues. The trace filter has been OMEGAMON for CICS on z/OS was unable to obtain
changed. sufficient storage to monitor Web Services. The
storage is requested more than the line.
User response
System action
None.
System processing continues, however, the recording
KCP4280E KCPWBM UNABLE TO OBTAIN of Web Services response times, rate information and
STORAGE FOR THE OMEGAMON failure counts do not occur for this CICS region.
WEB SERVICES HEADER
User response
Explanation
Increase the size of the region available to CICS. If this
OMEGAMON for CICS on z/OS was unable to obtain problem persists, contact IBM Software Support.
sufficient storage to monitor Web Services. The
storage is requested more than the line. KCP4283E KCPOBA UNABLE TO OBTAIN
STORAGE FOR THE OMEGAMON
System action OUTBOUND API REQUEST ENTRY.

Explanation
of Web Services response times, rate information and
failure counts do not occur for this CICS region. OMEGAMON for CICS on z/OS was unable to obtain
User response storage is requested more than the line.

System action
problem persists, contact IBM Software Support.
KCP4281E KCPWBM UNABLE TO OBTAIN of Web Services response times, rate information and
STORAGE FOR AN OMEGAMON failure counts do not occur for this CICS region.
WEB SERVICES ENTRY.
User response
Explanation
OMEGAMON for CICS on z/OS was unable to obtain problem persists, contact IBM Software Support.
storage is requested more than the line. KCP4285E OMEGAMON FOR CICS WBS
HEADER FREEMAIN FAILURE.
System action
Explanation
of Web Services response times, rate information and An error was detected when attempting to release the
failure counts do not occur for this CICS region. Web Services header storage.

Increase the size of the region available to CICS. If this System processing continues.
KCP4282E KCPOBA UNABLE TO OBTAIN User response
STORAGE FOR THE OMEGAMON Contact IBM Software Support.
OUTBOUND API REQUEST
HEADER. KCP4286E OMEGAMON FOR CICS WBS
ENTRY FREEMAIN FAILURE.

An error was detected when attempting to release the LU group is not created in OMEGAMON for CICS
Web Services entry storage. (3270).

System processing continues. Specify GROUP_TYPE as TRAN, PROG or TERM.
KCP5104E GVR TRACE CALL_TYPE VALUE IS
User response INVALID
Explanation
KCP5096I GVR THE CICSPLEX NAME
CANNOT EXCEED 8 CHARACTERS The trace CALL_TYPE keyword specifies an operand
that is not valid. The call type must be either ALL,
Explanation NONE or any combination of RMI, MQ, PCABEND,
UMBRELLA, TPPS and EXEC.
The CICSPLEX name specified on the
CICSPLEX_NAME Global Data Area parameter is not
System action
valid.
For a read request, a default copy of the global module
System action is returned to the caller. All other functions fail to
complete successfully.
The default global is loaded; the CICSPLEX name must
be 1 - 8 character value in length.
User response
User response Correct the value and try the command again.
Change the CICSPLEX name to a valid 1-8 character KCP5105E GVR TRACE EXEC_CALL VALUE IS
value in the CICSPLEX_NAME global parameter and INVALID
resubmit your request.
Explanation
KCP5097E GVR WRITE_SYSTEM_RECORDS
MUST BE YES, NO, OR CMF The trace EXEC_CALL keyword specifies an operand
that is not valid. The EXEC call must be either
Explanation ALL, NONE or any combination of FILE, PROGRAM,
STORAGE, TERM and TS.
The WRITE_SYSTEM_RECORDS keyword does not
have an operand of YES, NO, or CMF.
System action
System action For a read request, a default copy of the global module
is returned to the caller. All other functions fail to
For a read request, a default copy of the global module complete successfully.
is returned to the caller. All other functions do not
User response
User response Correct the value in the global.
Change the WRITE_SYSTEM_RECORDS keyword to KCP5106E GVR TRACE USE OF START_TIME,

one of the correct operands and resubmit your DURATION OR REPEAT REQUIRES
request. ALL BE SPECIFIED
KCP5099I GVR <<GROUP>> GROUP_TYPE=LU

Explanation
IS NO LONGER SUPPORTED
A trace filter was defined that did not contain all the
Explanation required values. Trace filters defined in the global can
either be permanent or repeating. Repeating traces
Group type can not be defined as LU any more. must specify START_TIME, DURATION and REPEAT.

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

Correct the value in the global. Correct the value in the global.
KCP5107E GVR TRACE START_TIME VALUE IS KCP5110E GVR RLIM <<CPU>> LIMIT IS
OUT OF RANGE 0000-2359 INVALID
A trace filter was defined with a START_TIME that was An invalid RLIM CPU limit was defined in global. Limits
not in the range 0000-2359. must be defined in the range 0-32768.


Correct the value in the global. Correct the value in the global.
KCP5108E GVR TRACE REPEAT VALUE IS KCP5111E GVR RLIM <<CPUGP>> LIMIT IS
INVALID INVALID
A trace filter was defined with a REPEAT option that An invalid RLIM CPUGP limit was defined in global.
was not No, Hourly Daily or WEEKLY, day of the week Limits must be defined in the range 0-32768.
(SUN, MON etc.).
System action
System action
For a read request, a default copy of the global module is returned to the caller. All other functions fail to
is returned to the caller. All other functions fail to complete successfully.
User response
User response
Correct the value in the global.
Correct the value in the global.
KCP5112E GVR RLIM <<CPUQR>> LIMIT IS
KCP5109E GVR TRACE THE DURATION INVALID
CANNOT BE LONGER THAN THE
REPEAT INTERVAL Explanation
An invalid RLIM CPUQR limit was defined in global.
Explanation
Limits must be defined in the range 0-32768.
A trace filter was defined with a duration which was
not less than the repeat interval. System action

User response The CICS job name is represented by aaaaaaaa value.
The module invoking the error is represented by the
Correct the value in the global. bbbbbbbb value.
KCP5401I OCSYSI SMFEWTM MACRO CALL
FAILED, RETURN CODE=<rc> System action
OMEGAMON data is not written to SMF.
Explanation
During OMEGAMON II for CICS initialization, User response
OMEGAMON was unable to write the
initialization record to SMF. For <rc>=36, Determine the cause of the error. If the type
CICS_CMF_WRITE=YES has been specified in the 112 SMF record is suppressed, consider configuring
<USER_EVENT_MONITORING> section of the Global, OMEGAMON to not write these records using
but SMF Type 112 records are suppressed. PARMGEN to update the global.
KCP5404E aaaaaaaa bbbbbbbb SMFEWTM
System action MACRO CALL SUCCESSFUL
None.
Explanation
User response Following a KCP5403 message, OMEGAMON has been
successfully able to resume the writing of SMF data;
For <rc>=36, adjust CICS_CMF_WRITE= and SMF Type this implies that the condition that lead to the earlier
112 suppression to match as desired. For other values message has been resolved.
of <rc> value, consult the section on the SMFEWTM in
the MVS System Management Facilities manual. The CICS job name is represented by the aaaaaaaa
value. The module invoking the service is represented
KCP5403E aaaaaaaa bbbbbbbb SMFEWTM by the bbbbbbbb value.
MACRO CALL FAILED RC=cc
System action
Explanation
OMEGAMON resumes writing data to SMF.
An attempt to write data to SMF failed with the return
code of cc.
User response
These are the common values for the SMFEWTM
return codes: None.
KCP5405E aaaaaaaa bbbbbbbb UNABLE TO
Table 6. SMFEWTM return code values
OBTAIN SMF BUFFER LOCK
Return
Code Description Explanation
08 RDW LESS THAN 18 BYTES An internal error has prevented OMEGAMON from
16 SMF IS NOT ACTIVE obtaining exclusive control of the SMF buffer.
20 SMF SUPPRESSED THE RECORD The CICS job name is represented by the aaaaaaaa
value. The module invoking the service is represented
24 RECORD NOT WRITTEN, DATA LOST by the bbbbbbbb value.
36 RECORD TYPE IS SUPPRESSED
System action
40 BUFFER SHORTAGE CAUSED THE DATA
TO BE LOST A system dump of the CICS region is taken on the first
occurrence of this message.
- SMF DATA SETS FULL
44 SMF COULD NOT ESTABLISH RECOVERY User response
48 THE CALLER NOT IN PRIMARY ASC Contact IBM Software Support.
MODE OR INCORRECT ASID ENTERED
KCP5406E aaaaaa INTERNAL OMEGAMON
ERROR

An OMEGAMON internal request for service has failed. The command fails.
The most likely cause is an earlier failure or corruption
of OMEGAMON areas within CICS. The program User response
invoking the service is denoted by the aaaaaa value.
System action KCP5410I ATF Filter refreshed. Trace num=n
Processing continues, however, the results are
unpredictable. Explanation
The ATFF command has successfully refreshed the
User response trace filter.
System action
KCP5407E OCXEN GETMAIN FOR AN MNTC
HEADER FAILED None.

OMEGAMON was unable to obtain sufficient storage to None.
initialize correctly. The storage is requested more than
KCP5411I Overlapping trace times are not
the line.
allowed
System action
Explanation
Processing continues, however, the functions such as
An attempt was made to create a trace filter when
Task History, Response Time Analysis, and Service
an existing trace filter for the same combination of
Level Analysis do not function for this CICS region.
Transaction ID, Terminal ID and CICS User ID is
present that covers some of the same time period.
User response
Increase the size of the region available to CICS. If this System action
The trace filter is not added.
KCP5408E OCXEN GETMAIN FOR AN MNTC
BLOCK FAILED User response
Modify the request to ensure it does not overlap an
Explanation
existing entry.
OMEGAMON was unable to obtain sufficient storage
KCP5412I Complete information is required
higher than the line to save the transaction data for a
for a delete
task. The storage is requested more than the line.

An attempt was made to delete a trace filter that did
not specify all the attributes of the filter.
User response
System action
No trace filters are deleted.
KCP5409I Locking error User response
Use the ATFF DELETE command to select the entry to
Explanation
be deleted.
There has been a failure to serialize access to the trace
KCP5413I Invalid call type
filter data.

An invalid call type was passed to the Internal Attempt the command again; the initialization process
OMEGAMON trace filter management component. should complete within one second.
KCP5417I Expansion area getmain failure
System action
The command fails. Trace filters are not updated. Explanation
An error occurred while attempting to obtain storage
User response more than the 16 MB line in the KOCCI address space;
This is an internal error. Contact IBM Software this message indicates that the KOCCI address space
Support. is severely constrained.
KCP5414I Entry not found

System action
Explanation The command fails.
A request to delete a trace filter was unable to locate

User response
the specified filter.
Review the region size for the KOCCI address space.
System action KCP5418I System busy, retry later
The command fails. No entries are deleted.
Explanation
User response An attempt to update the trace filters has coincided
Correct the command and enter the command again. with another attempt from a different user.
KCP5415I No space for requested addition

System action
Explanation The command fails.
A request to add a trace filter was unable to proceed

User response
because there was insufficient space to add a new
trace filter. Retry the command. If this error persists, contact IBM
Software Support.
System action KCP5419I Invalid ATF FILTER data found in
The command fails. The requested filter is not added. global data area module

Use the ATFF command to delete one or more filters The Trace filter data was not formatted correctly.
and try to add a trace filter again.
System action
KCP5416I Initialization in progress
The command fails.
Explanation
User response
An attempt was made to modify the trace filters while
another command was in the process of initializing the Contact IBM Software Support.
trace filters.
KCP5423I TRANID is invalid
System action
Explanation
The command fails. No modifications are made.
The TRANID specified on the ATFF command was
either greater than four characters or contained invalid
values.

The command fails. The Stardate value, which specifies the start date for
the filter, on the ATFF command, contained a value
User response that was not valid.
Correct the TRANID value specified on the ATFF

System action
command and try the command again.
The command fails.
KCP5424I Owner is too long, maximum is 8
characters
User response
Explanation Correct the Stardate value specified on ATFF
The OWNER value specified on the ATFF command
was greater than eight characters. KCP5429I Term is invalid

The command fails. The Term value specified on the ATFF command was
either greater than four characters or contained invalid
User response values.
Correct the OWNER value specified on the ATFF

System action
The command fails.
KCP5425I TRANID must be supplied
User response
Explanation
Correct the Term value specified on ATFF command
The TRANID value was not provided to for an ADD or and try the command again.
DELETE command.
KCP5430I User is invalid
System action
Explanation
The command fails.
The User value specified on the ATFF command was
User response either greater than eight characters or contained
invalid values.
Correct the TRANID value specified on the ADD or
DELETE command and try the command again.
System action
KCP5426I Duration is invalid The command fails.

The Duration value specified on the ATFF command Correct the User value specified on ATFF command
was either not specified or contained invalid numeric and try the command again.
values.
KCP5432I Start time is invalid
System action
Explanation
The command fails.
The Start time value specified on the ATFF command
User response contained an hour greater than 24 or a minute value
greater than 59.
Correct the Duration value specified on ATFF
System action
KCP5428I Stardate is invalid The command fails.

User response • FILE
Correct the Start time value specified on ATFF • PROGRAM

command and try the command again. • TS
KCP5433I Calltype is invalid • TERM.

The Calltype value specified on the ATFF command The command fails.
contained a value that is not one of the following
values: User response
• ALL Correct the Execcall value specified on ATFF command
• EXEC and try the command again.
• PCABEND KCP5438I CALLTYPE=EXEC and
• RMI EXECCALL=NONE is invalid
• UMBRELLA
Explanation
• TPPS
• MQ The ATFF command was entered that contained a
Calltype value including EXEC and an Execcall of
NONE. This combination is not valid.
System action
The command fails. System action
The command fails.
User response
Correct the Calltype value specified on ATFF command User response
and try the command again.
Correct the ATFF command and try the command
KCP5436I Duration exceeds n maximum again.
value
KCP5439I Invalid return code passed from
V$AFF000
Explanation
The Duration value n exceeded the maximum Explanation
permitted value of 43200.
An invalid return code was received from an internal
request.
System action
The command fails. System action
The command fails.
User response
Correct the Duration value specified on ATFF User response
KCP5437I Execcall is invalid
KCP5440I Scroll is invalid
Explanation
Explanation
The Execcall value specified on the ATFF command
contained a value that is not one of the following The Scroll value specified on the ATFF command
values: contained a value that is not numeric.
• ALL
System action
• NONE
The command fails.
• STORAGE

Correct the Scroll value on the ATFF command and try Correct the SIZE value specified on the ATFF
the command again. command and try the command again.
KCP5441I Invalid keyword parm KCP5445I Repeat is invalid
Explanation:
Explanation The Repeat value specified on the ATFF command
was either not specified or contained invalid values.
An unrecognized parameter parm value was passed on
the ATFF command. System action:
The command fails.
System action
User response
The command fails.
Correct the Repeat value specified on the ATFF
User response command and try the command again.
Correct the ATFF command and try the command KCP5500E &SYSECT $SUPER0 REQUEST
again. FAILED
KCP5442I Must specify Yes or No for

Explanation
TRALPGMC.
An attempt to invoke $SUPER0, an internal
Explanation OMEGAMON function, failed; the &SYSECT can be one
of these values:
An unrecognized parameter parm value was passed on
the ATFF command. • OCTRUE
• OCGLUE
System action
System action
The command fails.
The OMEGAMON function stops processing.
User response
User response
Correct the ATFF command and try the command
again. Contact IBM Software Support.
KCP5443I Size is invalid KCP5501E &SYSECT UNABLE TO OBTAIN A
NEW MNTC BLOCK
Explanation:
The Size value specified on the ATFF command was
either not specified or contained invalid numeric Explanation
values. An attempt to GETMAIN an OMEGAMON control block
System action: failed; the &SYSECT can be one of these values:
The command fails. • OCTRUE
• OCGLUE
User response
Correct the Size value specified on the ATFF System action
The OMEGAMON function stops processing.
KCP5444I Size exceeds n maximum value
Explanation: User response
The SIZE value n exceeded the maximum permitted
value of 320. Contact IBM Software Support.
System action: KCP5502E &SYSECT UNABLE TO CHAIN A

The command fails. NEW MNTC BLOCK

Explanation RLDL
DL/I requests
The new GETMAIN MNTC control block could not be
chained to the previous block; the &SYSECT can be one RLDS
of these values: DSA HWM storage
RLED
• OCTRUE
EDSA HWM storage
• OCGLUE
RLEL
elapsed time
System action RLFC
The OMEGAMON function stops processing. file requests
RLID
User response IDMS requests
RLMQ
MQ requests
KCP5520E RSD CICS cicsname: object type IS RLSU
NOT A SUPPORTED OBJECT TYPE. SUPRA requests
RLU1
Explanation USREVNT1 requests
The Resource Signature Data collector was called for
the specified object type. This object type value is not System action
currently supported by the collector. The cicsname
value is the name of the CICS region. The task will not be killed by resource limiting and
this message will not be issued again for this resource
while resource limiting is disabled.
System action
The OMEGAMON function stops processing. User response
When a task is running under debugging tools, such
User response as the CICS Debug Tool, it is expected that some
Contact IBM Software Support. resource thresholds might be exceeded. Typically no
user response is required. Correct the application or
KCP8903I HH:MM:SS BYPASSED ABEND increase the limit value in the Global Data Area, if
RLaa DUE TO xxxxxxxxxxxxxxxx: appropriate.
TRANS=tttt, TASKNO=nnnnnnn,
USER=uuuuuuu - RLIM OFF. KCP8904I HH:MM:SS BYPASSED ABEND
RLaa DUE TO xxxxxxxxxxxxxxxx:
Explanation USER=uuuuuuu- SYSTASK.
The CICS task has exceeded the xxxxxxxxxxxxxxxx
resource KILL threshold; however resource limiting Explanation
has been disabled for this task using the KOCRMCLL
API. For example, it is running under the CICS Debug The CICS task has exceeded the
Tool. The xxxxxxxxxxxxxxxx value is a text string xxxxxxxxxxxxxxxx resource KILL threshold and
explaining the threshold. RESOURCE_LIMITING_SYSTEM_TASKS is set to YES;
however CICS has identified this task as a system
These are the abend codes and their associated texts: task and therefore OMEGAMON will not abend it. The
RLAD xxxxxxxxxxxxxxxx value is a text string explaining the
ADABAS requests threshold.
RLCP These are the abend codes and their associated texts:
CPU time usage RLAD
RLDB ADABAS requests
DB2 requests RLCP
RLDC CPU time usage
DATACOM requests

RLDB System action
DB2 requests
The task will be killed by RLIM when the next
RLDC opportunity arises. This will result in the message
DATACOM requests OC8903I also being issued for the same task.
RLDL
DL/I requests
User response
RLDS
DSA HWM storage The message serves as a notification that the task
has exceeded the threshold even though RLIM cannot
RLED ABEND it. You may use this message to automate
EDSA HWM storage actions to notify operators that external action may be
RLEL required.
elapsed time
KCP9000 routine INITIALIZATION HAS
RLFC STARTED
file requests
RLID Explanation
IDMS requests
The OMEGAMON for CICS on z/OS initialization routine
RLMQ
value now has control.
MQ requests
RLSU
SUPRA requests
System action
RLU1 None.
USREVNT1 requests
User response
System action None.
The task will not be killed by Resource limiting and this KCP9001 STATISTICS COMMUNICATION
message will not be issued again for this task. AREA NOT AVAILABLE

Determine if a limit is appropriate for the task The program used to provide performance statistics
identified. could not locate the communication area used to
KCP8906I HH:MM:SS UNABLE TO collect data.
ABEND "RLaa" DUE
TO xxxxxxxxxxxxxxxx: System action
USER=uuuuuuuu- RUNNING. The MONITOR subtask stops processing.

The CICS task has exceeded the xxxxxxxxxxxxxxxx None.
resource KILL threshold; however the task is not in KCP9002 IRA REGISTRATION THREAD IS
a state where RLIM is able to ABEND the task. The ACTIVE
xxxxxxxxxxxxxxxx value is a text string explaining the
threshold.
Explanation
These are the abend codes and their associated texts:
The Tivoli Enterprise Monitoring Server registration
RLCP thread has completed initialization.
CPU time usage
RLEL
System action
elapsed time
None.

None. The Tivoli Enterprise Monitoring Server registration
thread failed to terminate within thirty seconds after
KCP9003 IRA REGISTRATION THREAD being notified to stop.
ALREADY ACTIVE
System action
Explanation
When the Tivoli Enterprise Monitoring Server
A command was issued to start a Tivoli Enterprise registration thread detects the shutdown request, it
Monitoring Server registration thread when one was stops processing.
already active.
User response
System action
None.
The second thread is not started.
KCP9007 MODULE CSECT ADDRESS DATE
User response TIME SYSMOD
None.
Explanation
KCP9004 IRA REGISTRATION THREAD IS This message is the header line produced in response
NOT ACTIVE to an OC DISPLAY MODULES command.

A command was issued to stop the IRA registration None.
thread, but the thread was not active.
User response
System action
None.
None.
KCP9008 module csect address date time
User response sysmod
None.
Explanation
KCP9005 IRA REGISTRATION THREAD IS This message is generated for each CSECT on the MVS
TERMINATING load list in response to an OC DISPLAY MODULES
command. The six fields displayed in this message
Explanation include the module, csect, address, date, time, and
sysmod values associated with each CICS module
The Tivoli Enterprise Monitoring Server registration
loaded from STEPLIB.
thread has received a request to terminate.
System action
System action
None.
None.
User response
User response
None.
None.
KCP9009 phase INITIALIZATION HAS
KCP9006 IRA REGISTRATION THREAD IS
ENDED
NOT RESPONDING
Explanation
The IBM Z OMEGAMON for CICS initialization phase
identified by phase has finished.

None. Inspect the logs for a message that might indicate why
the thread failed to start. If problems persist, contact
User response IBM Software Support.
None. KCP9013 ATC UNABLE TO OBTAIN OCCVT

STORAGE
KCP9010 ATC NO CICS MODULES APPEAR
ON LOAD LIST
Explanation
Explanation The system was unable to allocate the IBM Z
OMEGAMON for CICS communications vector table.
The OC DISPLAY MODULES command found no
programs on the MVS load list that contained a prefix
System action
of KCP.
None of the OMEGAMON for CICS on z/OS collection
System action routines function.

User response
User response Increase the amount of memory available to the Tivoli
Enterprise Monitoring Server. If problems persist,
None. contact IBM Software Support.
KCP9011 ATC UNABLE TO OBTAIN COMMON KCP9014 PTHREAD_DETACH() ERROR
WORK AREA STORAGE
Explanation
Explanation
Unused resources associated with the subnode
The OMEGAMON for CICS on z/OS attach controller monitoring thread could not be freed.
could not acquire its work area.
System action
System action
Resources remain allocated until ITMS:Engine region
None of the OMEGAMON for CICS on z/OS collection termination.
routines function.
User response
User response
None.
Increase the amount of memory available to the Tivoli
Enterprise Monitoring Server. If problems persist, KCP9015 ATC entry_point ROUTINE ENTRY
contact IBM Software Support. POINT NOT FOUND
KCP9012 PTHREAD_CREATE() ERROR

Explanation
Explanation The program used by the attach controller to
start subtasks contains an invalid entry point. The
The thread used to monitor active CICS regions could entry_point value denotes the entry point that could
not be started. not be located.

None of the OMEGAMON for CICS on z/OS queries None of the IBM Z OMEGAMON for CICS collection
function. routines function.
User response

KCP9016 IRA MANAGER COMMAND Explanation
UNKNOWN: aaaaaaaa
This message provides a heading for work area
displays shown in the RKLVLOG output.
Explanation
The IRAMAN KCPAGENT modify command specified System action
an invalid argument, as denoted by the aaaaaaaa
value. None.

The command is ignored. None.
KCP9021 IRA_SUBNODE_DEREGISTER
User response ERROR: RC=aa, NODE=bbbbbbbb
Enter the correct IRAMAN KCPAGENT aaaaaaaa value

modify command. Explanation
KCP9017 IRA MANAGER COMMAND The function used to register the CICS
OPERAND MISSING node=bbbbbbbb as offline failed, with a return code
denoted by the aa value.
Explanation
System action
The IRAMAN KCPAGENT modify command did not
include an argument. The CICS subnode continues to reflect an online status
regardless of its actual state.
System action
User response
The command is ignored.
User response KCP9022 ATC START COMMAND FAILED.

SEE PRIOR MESSAGES
Enter the correct IRAMAN KCPAGENT aaaaaaaa
modify command.
Explanation
KCP9018 IRA_SUBNODE_REGISTER ERROR:
RC=aa, NODE=bbbbbbbb The attach controller was unable to start an
OMEGAMON for CICS on z/OS function.
Explanation
System action
The function used to register CICS node=bbbbbbbb as
online failed, with a return code denoted by the aa The function does not initiate.
value.
User response
System action Consult the RKLVLOG output for additional messages.
The CICS subnode is not available for situations and KCP9023 ATC COMMAND FORMAT INVALID,
workspaces. SEE PRIOR MESSAGES

Contact IBM Software Support. The attach controller detected a command with invalid
KCP9019 ATC INITIALIZATION RTN syntax.
DIAGNOSTIC DUMP
System action
The command is not processed.

Consult the RKLVLOG output for additional messages. An OC STOP command could not be processed.
KCP9024 IRA_SUBNODE_SENDREQUEST
CALL RETURNED WITH aa System action
The task is not be stopped.
Explanation
The function used to submit CICS subnode status has User response
failed with a return code denoted by the aa value. Contact IBM Software Support.
KCP9039 ATC STOP COMMAND FAILED.
System action
INTERNAL ERROR
The CICS subnode does not reflect the true state of
the region. Explanation
An OC STOP command could not be processed.
User response
Examine the RKLVLOG output for messages that System action
might indicate a problem with the register/deregister
functions. If problems persist, contact IBM Software The task is not be stopped.
Support.
KCP9025 aaa UNABLE TO OBTAIN WORK User response
AREA STORAGE Contact IBM Software Support.
KCP9040 ATC STATUS COMMAND BEING
Explanation
PROCESSED
The agent identified by the aaa value was unable to
allocate main memory. Explanation
A request for status has been received.
System action
No data is collected. System action
None.
User response
Consider increasing the ITMS:Engine region size. User response
KCP9030 ATC PROCESSING THE None.
FOLLOWING COMMAND:
KCP9060 ATC THREAD START COMPLETED
SUCCESSFULLY
Explanation
This message precedes any command received by the Explanation
attach controller.
A ITMS:Engine thread was initiated.
System action
System action
None.
None.
User response
User response
None.
None.
KCP9038 ATC STOP COMMAND FAILED
RC=rc KCP9069 ATC TASK START FAILED ON
$DISP ERROR

A program could not be initiated due to a dispatch The trace request is not started. Processing continues.
queue problem.
User response
System action
The initialization module was either unable to acquire
The task does not start. the control area, or acquired an area that was not large
enough. If the problem persists, contact IBM Software
User response Support.
Contact IBM Software Support. KCP9182I MODULE mmmmmmmm HAS

BEEN FLAGGED FOR TRACING
KCP9070 CICS JOBNAME PARAMETER IS
MISSING OR INVALID
Explanation
Explanation This message is issued in response to an OC START
TRACE mmmmmmmm command. Tracing is now in effect
A START command for a program that requires a CICS for module mmmmmmmm.
jobname did not properly specify the CICS keyword.
System action
System action
The task does not start.
User response
User response
None.
Ensure that a valid CICS name is passed on the START
command. KCP9183I MODULE mmmmmmmm IS NO
LONGER FLAGGED FOR TRACING
KCP9180W THE TRACING REQUEST
INTERFACE IS NOT YET
Explanation
AVAILABLE
This message is issued in response to an OC STOP
Explanation TRACE mmmmmmmm command. Tracing is no longer in
effect for module mmmmmmmm.
An OC START/STOP TRACE mmmmmmmm command
was issued before initialization of the trace request
System action
interface was completed.
System action
User response
Processing continues but the trace operation for
module mmmmmmmm is not started. None.
KCP9184E THE NAME SPECIFIED WITH THE
User response 'START TRACE' COMMAND IS
After you find message KCP9009 in the RKLVLOG, INVALID
issue this command to start a trace: OC START/STOP
TRACE mmmmmmmm. Explanation
KCP9181W MODULE mmmmmmmm IS NOT This message is issued in response to an OC START
CURRENTLY AVAILABLE FOR TRACE mmmmmmmm command. The module name
TRACING REQUESTS mmmmmmmm is not valid.

The control area for module mmmmmmmm is not Processing continues.
available to fulfill the trace start/stop request.

User response initialize. If problems persist, contact IBM Software
Support.
Correct the module name and enter the command
again. KCP9200 ATO OPERATOR INTERFACE NOT
INSTALLED
KCP9185E THE NAME SPECIFIED WITH
THE STOP TRACE' COMMAND IS
INVALID Explanation
The operator interface was not initialized during
Explanation ITMS:Engine initialization.
This message is issued in response to an OC STOP

TRACE mmmmmmmm command. The module name System action
mmmmmmmm is not valid. The command is ignored.

Processing continues. Contact IBM Software Support.
KCP9201 ATO OPERATOR INTERFACE
User response DISPATCH FAILURE
Correct the module name and enter the command
again. Explanation
KCP9198 ATC INITIALIZATION FAILED TO The system encountered an internal error when
COMPLETE SUCCESSFULLY attempting to dispatch the work required to process
an operator command.
Explanation
The OMEGAMON for CICS on z/OS attach controller System action
failed to initialize. The command is ignored.

None of the OMEGAMON for CICS on z/OS collection Contact IBM Software Support.
routines function.
KCP9202 ATO UNABLE TO OBTAIN
COMMAND PLIST STORAGE
User response
Consult the console log for additional messages that Explanation
would explain why the attach controller could not
initialize. If problems persist, contact IBM Software Memory could not be acquired for the operator
Support. command parameter list.
KCP9199 ATC OPERATOR INTERFACE

DISABLED, RESTART REQUIRED System action
Explanation
An error caused the attach controller to fail. User response
Increase the amount of storage available to the Tivoli
System action Enterprise Monitoring Server.
None of the OMEGAMON for CICS on z/OS operator KCP9300 ATC STATUS -- module: entry_point
commands works under ITMS:Engine.
Explanation
User response This message displays the entry point of module value
Consult the console log for additional messages that in response to a STATUS command with the DEBUG
would explain why the attach controller could not option.

None. This message displays the task ID of the active task
started by the attach controller.
User response
System action
None.
None.
KCP9311 ATC STATUS -- ATC OC$ATCWK:
address
User response
Explanation None.
This message displays the address of the attach KCP9315 ATC STATUS -- TASK ID: task_id
parameter list used by the attach controller in CICS: region
response to a STATUS command.
Explanation
System action
This message displays the task ID for the active task
None. started by the attach controller that is monitoring a
specific CICS region.
User response
System action
None.
None.
KCP9312 ATC STATUS -- ATC OC$CVT:
address
User response
Explanation None.
This message shows the address of the IBM Z KCP9316 ATC STATUS -- APARM: address
OMEGAMON for CICS CVT when a STATUS command TYPE: type
is entered.
Explanation
System action
This message displays the address and type of attach
None. parameter lists created by the attach controller.

None. None.
KCP9313 ATC STATUS -- ATC OC$APARM:
address User response
None.
Explanation
KCP9317 ATC STATUS -- MODULE: module
This message displays the attach controller anchor ENTRY PT: entry_point
control block address.
Explanation
System action
This message displays the name and entry point of
None. each module loaded by the attach controller.

None. None.
KCP9314 ATC STATUS -- TASK ID: task_id

None. This message is in response to the KCP9320I
message; this message indicates that the WLM
KCP9318 ATC STATUS -- TCB: address1 EOT component is not active.
ECB: address2
System action
Explanation
None.
This message displays the address of each TCB
(address1), and its corresponding end-of-task ECB
(address2), created by the attach controller. User response
Determine if the WLM component was intentionally
System action stopped.
None. KCP9323I WLM BLOCKS USAGE:

None. This message is in response to the KCP9320I
message; it forms the header for subsequent
KCP9320I ATC STATUS,BLOCKS messages.
PROCESSING IS STARTING
System action
Explanation
None.
The OC STATUS,BLOCKS command is being processed
by the attach controller task. This message indicates
the command has been entered and that status User response
messages will follow. None.
KCP9324I TYPE ALLOCATED CURRENT %
System action
PEAK %
None.
Explanation
User response
This message is in response to the KCP9320I
None. message; it forms the header for subsequent
messages.
KCP9321I WLM BLOCKS ALLOCATED blocks
System action
Explanation
None.
message; this message displays the number of blocks
requested for the WLM component. User response
None.
System action
KCP9325I Type Allocated Current
None. Current_percent Peak
Peak_percent
User response
Explanation
None.
KCP9322I WLM COMPONENT IS NOT ACTIVE message; it displays information about the usage of
the storage reserved through the WLM BLOCKS option.
These are the values:

• Type can be either TRAN for transaction records or KCP9327E INVALID INPUT, CICSPLEX NAME
SUMM for summary records. MUST BE BETWEEN 1 AND 8
CHARACTERS IN LENGTH
Transaction records are used to maintain information
about the completed transactions until they are
summarized. The number used is dependant upon Explanation
the total number of transactions that occur for a
This message is issued in response to an OC
given period of time for all the CICS regions that
DISPLAY,PLEX=cicsplex command if either no cicsplex
OMEGAMON agent is monitoring.
is specified as the PLEX value or the specified cicsplex
Summary records depend upon the number of is longer than 8 characters in length; it is written to the
service classes defined, the transactions that are RKLVLOG output.
categorized in those service classes and the CICS
regions.
System action
• Allocated is the number of records in storage.
None.
• Current is the current number of records in use.
• Current_percent is the percentage of records that are User response
currently in use.
• Peak is the maximum number of records in use. Issue the command again with a valid PLEX=cicsplex
parameter.
• Peak_percent is the maximum percentage of records
in use. KCP9328I CICSPLEX nnnnnnnn IS
UNKNOWN TO THIS AGENT.
System action
Explanation
None.
If the specified CICSPLEX nnnnnnnn name is not
known to the agent, this message is issued in response
User response to the OC DISPLAY,PLEX=cicsplex command; it is
Examine the values that are returned. If the peak written to the RKLVLOG output. The nnnnnnnn value
usage exceeds 80% you should consider increasing is the CICSplex name that you specified.
the value that you specified for the KC5_WLM_BLOCKS
parameter in PARMGEN. There is a direct relationship System action
between this parameter and the size available for each
type of record. Therefore, if 500 blocks results in a None, this message is informational.
consistent usage of 80%, changing the value to 1000
blocks results in a usage of 40%. User response
KCP9326I NO CICSPLEX IS KNOWN TO THIS None, although you can verify that this is expected
AGENT. result in your environment.
KCP9329I DISPLAYING INFORMATION FOR
Explanation CICSPLEX nnnnnnnn:
STATUS,CICSPLEX command if NO is the CICSplex that Explanation
is known by the agent; it is written to the RKLVLOG
output. This message is issued as part of OC
STATUS,CICSPLEX or OC DISPLAY,PLEX=cicsplex
command processing. It is written to the RKLVLOG
System action output. The nnnnnnnn value is the CICSplex name that
None, this message is informational. you specified.

None, although you can verify that this is expected None, this message is informational.
result in your environment.
User response
None.

KCP9330I THE ORIGIN NODE: nnnnnnnnn KCP9333I LISTING CICS REGIONS IN
CICSPLEX nnnnnnnn:
Explanation
Explanation
This message is issued as part of OC
STATUS,CICSPLEX or OC DISPLAY,PLEX=cicsplex This message is issued as part of OC
command processing. It is written to the RKLVLOG DISPLAY,PLEX=cicsplex command processing. It is
output. The nnnnnnnn value is the origin node name written to the RKLVLOG output. The nnnnnnnn value
that IBM Tivoli Monitoring recognizes. is the name of the CICSplex.

None, this message is informational. None, this message is informational.

None, although you can verify that this is expected None.
KCP9334I JOBNAME xxxxxxx, PLEX
KCP9331I THE NUMBER OF CICS REGIONS: n nnnnnnnn FROM yyyy
This message is issued as part of OC This message is issued as part of OC
STATUS,CICSPLEX or OC DISPLAY,PLEX=cicsplex DISPLAY,PLEX=cicsplex command processing. It is
command processing. It is written to the RKLVLOG written to the RKLVLOG output. The xxxxxxx value
output. The n numerical value is the number of CICS is the CICS jobname of the Cicsplex name value of
regions that are assigned to the CICSplex. nnnnnnnn. The yyyy value is the CPSM source if CPSM
assigned the CICSPLEX name; it is OMEGAMON if the
System action user-defined rules assigned the CICSPLEX name, and
DEFAULT if the default CICSPLEX name is used.
None, this message is informational.
System action
User response
None, although you can verify that this is expected
User response
KCP9332I THE CICSPLEX nnnnnnnn IS None, although you can verify that this response is the
REGISTERED BY THIS AGENT: expected value in your environment.
YES, NO
KCP9335I NO ACTIVE REGIONS IN THE
Explanation CICSPLEX ARE KNOWN TO THIS
AGENT
STATUS,CICSPLEX or OC DISPLAY,PLEX=cicsplex
Explanation
command processing. It is written to the RKLVLOG
output. The YES or NO values are YES if the CICSplex This message is issued as part of OC
nnnnnnnn value was registered by this agent and NO if DISPLAY,PLEX=cicsplex command processing if the
it was not registered. CICS agent does not have any active CICS regions that
have been assigned to the specified CICSPLEX. The
System action output is written to the RKLVLOG.

System action
User response None, this message is informational.
None, although you can verify that this response is the

expected value in your environment.

None, although you can verify that this response is the This message is issued as part of OC
expected value in your environment. DISPLAY,PLEXRULES command processing. It is
written to the RKLVLOG output. The plexname value is
KCP9336I NO CICSPLEX NAME RULES EXIST the CICSPLEX name assigned by the rule. The jobname
value is the pattern used to match the name of the
Explanation CICS job. The sysplex value is the pattern used to
match the SYSPLEX ID. The smfid value is the pattern
used to match the SMF ID. The applid value is the
DISPLAY,PLEXRULES command if no CICSPLEX name
pattern used to match the CICS APPLID. The gapplid
rules exist; it is written to the RKLVLOG output.
value is the pattern used for the generic APPLID for
both the active and the alternate CICS region.
System action
None, this message is informational. System action
User response
None, although you can verify that this response is the User response
KCP9337I DISPLAYING THE CICSPLEX NAME expected value in your environment.
RULES:
KCP9398 ATC STATUS -- NO TASKS
CURRENTLY ACTIVE
Explanation
This message is issued as part of OC Explanation
DISPLAY,PLEXRULES command processing; it is
The attach controller could not find any active tasks in
written to the RKLVLOG output.
response to a status request.

None.

None.
KCP9399 ATC STATUS -- NO TASKS STARTED
KCP9338I PLEXNAME JOBNAME SYSPLEX
YET
SMFID APPLID GAPPLID
Explanation
Explanation
The attach controller has not processed a START
command in response to a status request.
DISPLAY,PLEXRULES command processing; it is
written to the RKLVLOG output.
System action
System action None.
User response
User response None.
None, although you can verify that this response is the KCP9700 ATI SUBTASK INITIALIZATION
expected value in your environment. TDA NOT FOUND
KCP9339I plexname jobname sysplex smfid
applid gapplid

The system was unable to locate the target descriptor Messages are not written to the RKLVLOG output when
area used to monitor a CICS region. a CICS agent abnormally stops processing with a SOC4
abend code.
System action
User response
None.
User response KCP9891 ATC S0C4 MESSAGE
Contact IBM Software Support. SUPPRESSION NOT ACTIVE
KCP9701 ATI SUBTASK MODULE E.P.

Explanation
MISSING OR INVALID
The OMEGAMON for CICS on z/OS attach controller
Explanation received a request to suppress S0C4 messages, but
message suppression was never enabled.
The program entry point of a module to be started is
zero.
System action
System action The OC SUPRS0C4 command is ignored.

User response
User response None.
Contact IBM Software Support. KCP9892 ATC S0C4 MESSAGE

SUPPRESSION DEACTIVATED
KCP9889 ATC SOC4 MESSAGES ARE
ALREADY SUPPRESSED
Explanation
Explanation The OMEGAMON for CICS on z/OS attach controller
has acknowledged a request to stop suppressing S0C4
The OMEGAMON for CICS on z/OS attach controller log messages.
has received a request to suppress SOC4 log
messages, but message suppression is already
System action
enabled.
A message is written to the RKLVLOG when CICS
System action agents experience S0C4 ABENDs.
The OC SUPRS0C4 command is ignored.

User response
User response None.
None. KCP9893 ATC INVALID S0C4 MESSAGE

OPTION SPECIFIED
KCP9890 ATC SOC4 MESSAGE
SUPPRESSION ACTIVATED
Explanation
Explanation The OMEGAMON for CICS on z/OS suppression option
specified in the OC SUPRS0C4 command.
has acknowledged a request to suppress SOC4 log
System action
messages.
The OC SUPRS0C4 command is ignored.
User response
Reenter the command with an ON or OFF option.

KCP9900 ATC TERMINATION HAS STARTED System action
Explanation
The OMEGAMON for CICS on z/OS termination routine User response
now has control.
Increase the amount of memory available to the Tivoli
Enterprise Monitoring Server. If problems persist,
System action contact IBM Software Support.
None. KCP9924 ATC FREEMAIN FAILURE FOR
ITMS:Engine STORAGE
User response
None. Explanation
KCP9920 ATC START ATTACH ERROR RC=rc The system was unable to process a $FMEM request to
release ITMS:Engine managed storage.
Explanation
System action
was unable to start an function. None.

The function does not initiate. Contact IBM Software Support.
KCP9925 ATC TASK-START RESOURCE
User response ALREADY FREED
Consult the RKLVLOG output for additional messages.

Explanation
KCP9921 ATC START REJECTED. TASK
ID=task_id CURRENTLY RUNNING. The system has released resources associated with a
ONLY ONE COPY PERMITTED AT A task.
TIME
System action
Explanation None.
found an active copy of task_id value running in the User response
Data Server address space.
None.
System action KCP9941 function MVS VERSION UNKNOWN
The START command is ignored.

Explanation
User response The subroutine used to determine the operating
system release detected an unsupported release of
None. z/OS when called by function function.
KCP9922 ATC UNABLE TO OBTAIN ATTACH
PARAMETER LIST STORAGE System action
The function identified by the function value does not
Explanation start.
could not acquire memory for the ATTACH macro. User response

KCP9942 function OCVRSN FAILURE, R1=r1, System action
R15=r15
Explanation
User response
The subroutine used to determine the operating
system release failed with return code r1 value, when Correct the task name on the ID parameter and enter
called by function function. the command again.
KCP9948 ATC ID= PARM LENGTH ERROR
System action
The task does not start. Explanation
The ID keyword on the OC command specifies an
User response incorrect value.

System action
KCP9943 ATC NO TABLE ENTRY FOR task
Explanation
User response
The attach controller was unable to locate the task
value. Correct the task name on the ID parameter and
reenter the command.
System action KCP9949 ATC INVALID HEADER FORMAT IN

program
Explanation
User response
The internal module header in the program value
Contact IBM Software Support. cannot be validated.
KCP9945 ATC $LOAD ERROR FOR MODULE:
module System action
Explanation
The ITMS:Engine service used to load a program has User response
failed. The module value is the module that could be
found. Contact IBM Software Support.
KCP9950 ATC HAS LOADED MODULE:
System action program
The task is not started.

Explanation
User response The OMEGAMON for CICS on z/OS attach controller
loaded the program value.
KCP9947 ATC ID= PARM NOT SPECIFIED OR System action
INVALID
None.
Explanation
User response
The ID keyword on the OC command specifies an
incorrect value. None.
KCP9989 ATC TRACING HAS BEEN
ACTIVATED

The OMEGAMON for CICS on z/OS attach controller Tracing of OMEGAMON for CICS on z/OS discontinues.
has acknowledged a request to turn on trace.
User response
System action
None.
Tracing of OMEGAMON for CICS on z/OS is initiated.
KCP9993 ATC INVALID TRACE OPTION
SPECIFIED
User response
None. Explanation
KCP9990 ATC INITIALIZATION HAS ISSUED The OMEGAMON for CICS on z/OS attach controller did
ADDITIONAL ERROR MESSAGES not recognize the tracing option specified in the OC
TRACE command.
Explanation
System action
has failed to initialize. The OC TRACE command is ignored.

None of the OMEGAMON for CICS on z/OS collection Enter the command again with an ON or OFF option.
routines function.
KCP9994 ATC TRACING IS ALREADY ACTIVE
User response
Explanation
Consult the console log for additional messages that
would explain why the attach controller could not The OMEGAMON for CICS on z/OS attach controller
initialize. If problems persist, contact IBM Software has received a request to activate tracing, but tracing
Support. is already active.
KCP9991 ATC TRACING IS NOT CURRENTLY System action

ACTIVE
The OC TRACE command is ignored.
Explanation
User response
received a request to turn tracing off but tracing was None.
never turned on originally.
KCP9995 ATC TEST REJECTED, XDC(Y) NOT
IN KDSSYSIN
System action
The OC TRACE command is ignored. Explanation
User response has received a TEST command but found that the
None. XDC environment had not been established under the
Engine.
KCP9992 ATC TRACING HAS BEEN
DEACTIVATED System action
The OC TEST command is ignored.
Explanation
The OMEGAMON for CICS on z/OS attach controller User response
has acknowledged a request to turn off tracing.
Place an XDC(Y) control card in the KDSSYSIN
member of RKANPAR and restart the Tivoli Enterprise
Monitoring Server address space.

KCP9996 ATC NOW INOPERATIVE. RESTART KCP9999 ATC TERMINATION HAS ENDED
REQUIRED.
Explanation
Explanation
In order for OMEGAMON for CICS on z/OS to collect has stopped processing.
data, the error that caused the attach controller to fail
must be corrected and the Tivoli Enterprise Monitoring System action
Server address space restarted.
None.
System action
User response
None. This message is for informational purposes only.
None.
User response KCPDB001I OMEGAMON CICS COLLECTING
prodname DATA
initialize. If problems persist, contact IBM Software Explanation
Support.
The OMEGAMON for CICS on z/OS product has
KCP9997 ATC INITIALIZATION CANNOT BE started data collection for the database specified by
COMPLETED prodname, where prodname is one of the databases
supported by OMEGAMON CICS (such as VSAM or
IDMS).
Explanation
An error caused the attach controller to fail. System action
None.
System action
None of the OMEGAMON for CICS on z/OS collection User response
routines function.
None. This is an informational message.
User response KCPEC4000I EXOP PARAMETER EXTRACT IN
PROGRESS
Support.
OMEGAMON for CICS on z/OS has started the
KCP9998 ATC OPERATOR INTERFACE IS process of extracting parameters from INITPARM and
NOW DISABLED TERMINAL input.

An error caused the attach controller to fail. None.

None of the OMEGAMON for CICS on z/OS operator None. This is an informational message.
commands work under the Tivoli Enterprise Monitoring
KCPEC4001I EXOP LOCATED ddname
Server.
'RKANMOD ' DD_FLAG nn
User response
Explanation
OMEGAMON for CICS on z/OS has located the DD
card specified by ddname, where ddname is one
initialize. If problems persist, contact IBM Software
of the following: KOCGLBcc, KC2GLBcc, RKC2XMnn,
Support.

RKCPXMnn or RKANMOD. ddname displays the value cccccccc
that was supplied using the INITPARM, TERMINAL Is a count of the data sets that were found in that
input or the CICS JCL. concatenation.
This message lists the DD cards that were located aaaaaaaa
during initialization and is displayed if the LIST option Is the address, in CICS storage, of a lis of data sets
is supplied in the INITPARM or TERMINAL input. that was used by this code.
The FLAG value is used for problem determination The message is issued in conjunction with
purposes only. KCPEC4003I.

None. None.

None. This message is displayed only when the LIST This message is displayed only if the LIST option is
option is provided at OMEGAMON startup. This is used to display diagnostic messages.
typically done only when requested by IBM Software
Support. KCPEC4005W EXOP DUPLICATE LIBRARY IN
library load_library_dataset_name
KCPEC4003I EXOP MODULE KOCOME00
LOADED FROM LIBRARY 'library'
Explanation
Explanation During processing of data sets allocated to library, a
duplicate load library, load_library_dataset_name, was
This message displays where the OMEGAMON CICS detected, where library is either a LIBRARY definition
load module, KOCOME00, was loaded from. The or DFHRPL (CICS module request parameter list).
LIBRARY field can either be a LIBRARY definition, or
DFHRPL (CICS module request parameter list).
System action
System action None. The duplicate name is ignored and processing
continues.
None.
User response
User response
None. This message is displayed only if the LIST option
This is an information message, displayed only when is used to display diagnostic messages. Consider
LIST is specified as an option of INITPARM. Use this removing the duplicate entries from the LIBRARY or
message to verify that library is where you expect DFHRPL definition.
KOCOME00 to be loaded from. If not, review the
DFHRPL concatenation and any LIBRARY definitions. KCPEC4009E EXOP CICS/TS vvrrmm IS AN
Ensure that the library you expect to be used to load UNSUPPORTED RELEASE
KOCOME00 is first in the concatenation list.
KCPEC4004I EXOP LIBRARY 'library' Explanation
COUNTcccccccc LIST ADDR An unsupported release (version, release, modification
aaaaaaaa level) of CICS/TS was detected. The supported
releases are CICS/TS v3.2.0 and later.
Explanation
This message is displayed only if the LIST option is System action
used to display diagnostic messages, where: None
'library'
Is the name of the library that KOCOME00 is User response
loaded from.
None. This is an informational message. OMEGAMON
initialization will continue as normal in an earlier

release of CICS/TS by using your existing JCL This value can be used to validate that the
definitions. parameters passed to OMEGAMON CICS were
processed as expected.
KCPEC4010E EXOP RETURN CODR eibresp
OCCURRED IN AN command
REQUEST System action
None.
Explanation
A non-zero return code was received in response to User response
a CICS command issued by the extract parameters None.
process, where:
KCPEC4012I EXOP DD CARD ALLOCATION FLAG
command
SET AT EXIT TO nn
Is one of the following:
• INQUIRE SYSTEM
Explanation
• INQUIRE LIBRARY
This message is displayed only if the LIST option is
• INQUIRE PROGRAM used to display diagnostic messages, where nn is an
eibresp error code used by IBM Software Support.
The response received from CICS when the
command was issued. The eibresp values are System action
documented in the IBM CICS Transaction Server for
z/OS System Programming Reference. None.

The parameter extraction process stops when one of This message is used to explain an error condition to
these abnormal conditions is detected. IBM Software Support.
KCPEC4013I EXOP PARAMETER EXTRACT
User response COMPLETED NORMALLY
Use the eibresp return code value to determine why
the specified command failed and take appropriate Explanation
action. If the error persists, contact IBM Software OMEGAMON for CICS on z/OS has completed the
Support. process of extracting parameters from INITPARM and
KCPEC4011I EXOP DD CARD 'ddname' TERMINAL input.
ALLOCATED, SOURCE source
System action
Explanation None.
The DD card specified by 'ddname' was dynamically
allocated by OMEGAMON CICS, where: User response
'ddname' None. This is an informational message.
Is one of the following: RKC2XMnn, RKCPXMnn or
KC2GLBcc KCPEC4014I EXOP DEALLOCATE 'ddname'
R15 nnnnnnnn S99EROR nnnn
source
S99INFO nnnnn
Is the source of the definition, one of the following:
• INITPARM is the value was successfully
Explanation
extracted from the CICS INITPARM data.
• TERMINAL is the value was successfully A request to dynamically deallocate an OMEGAMON
extracted from TERMINAL input. for CICS on z/OS DD card was issued, and the result
is displayed in this message. The dd_name can be one
• DEFAULT is the value was provided as a default of the following: KC2GLBxx, RKANMOD, RKC2XMnn or
as no other input was detected RKCPXMnn. The R15, S99ERROR and S99INFO fields

display the results of the DYNALLOC request that was System action
issued.
None.
System action
User response
None.
Under most circumstances, this message is displayed
only when the LIST option is used to display diagnostic
User response messages. However, if a DYNALLOC request fails,
Under most circumstances, this message is displayed this message is written to the operating system
only when the LIST option is used to display diagnostic console and the CICS log. If you cannot diagnose the
messages. However, if a DYNALLOC request fails, problem by using the information provided, contact
this message is written to the operating system IBM Software Support.
console and the CICS log. If you cannot diagnose the KCPOC0001E INSUFFICIENT STORAGE FOR
problem by using the information provided, contact DATA_STORE_TYPE=AUTO
KCPEC4015I EXOP ALLOCATE 'ddname' Explanation
R15 nnnnnnnn S99EROR nnnn
S99INFO nnnnn The available storage is insufficient to be used to
allocate file when DATA_STORE_TYPE=AUTO.
Explanation
System action
A request to dynamically allocate an OMEGAMON for
CICS on z/OS DD card was issued, and the result is The task does not start.
displayed in this message. The ddname can be one
of the following: KC2GLBxx, RKANMOD, RKC2XMnn or User response
RKCPXMnn. The R15, S99ERROR and S99INFO fields
display the results of the DYNALLOC request that was Consider increasing the address space REGION
issued. parameter. If problems persist, contact IBM Software
Support.
System action KCPOC0002E ONDV UNABLE TO DEALLOCATE

HISTORICAL DATA FILE, RC=xx
None.
Explanation
User response
The request to deallocate historical data file is unable
Under most circumstances, this message is displayed to be issued when DATA_STORE_TYPE=AUTO.
only when the LIST option is used to display diagnostic
messages. However, if a DYNALLOC request fails,
this message is written to the operating system System action
console and the CICS log. If you cannot diagnose the None.
problem by using the information provided, contact
User response
KCPEC4016I EXOP CONCATENATE 'ddname'
R15 nnnnnnnn S99EROR nnnn The return code from the deallocate call to the
S99INFO nnnnn DYNALLOC macro is the value xx. If this return code
is insufficient to resolve the problem, contact IBM
Software Support.
Explanation
KCPOC1038I IBM Z OMEGAMON for CICS
A request to dynamically concatenate an OMEGAMON Version vrm is initializing.
for CICS on z/OS DD card was issued, and the result
is displayed in this message. The ddname is usually
RKANMOD. The R15, S99ERROR and S99INFO fields Explanation
display the results of the DYNALLOC request that was OMEGAMON for CICS on z/OS is initializing in the CICS
issued. address space at the release level designated by the
vrmvalue.

System action If this explanation does not lead to a solution, contact
IBM Software Support and provide the message text.
None.
KCPOC1051E KOCOME00 IS DEFINED AS
OPENAPI, IT MUST BE DEFINED
User response AS CICSAPI.
None.
KCPOC1049W UNABLE TO XXX RESMGR, Explanation
THE RETURN CODE IS ZZZZ, The program definition for KOCOME00 specifies
PROCESSING CONTINUES. API(OPENAPI). KOCOME00 must not be defined to
run only on an Open TCB.
Explanation
OMEGAMON for CICS on z/OS was unable to add or System action
delete a resource manager in the CICS address space, KOCOME00 terminates.
where:
XXX User response
Is the function that failed, either ADD or DEL.
Correct the program definition for KOCOME00 to
ZZZZ
specify API(CICSAPI).
Is the RESMGR return code. For explanations
of the RESMGR return codes, see IBM z/OS KCPOC1060E KCPOC1060E OMEGAMON
MVS Programming Authorized Assembler Services PROGRAM TRACKING DISABLED
Reference.
Explanation
System action
OMEGAMON for CICS Program Tracking encountered
The resource manager function failed. This failure has an unexpected condition.
no impact on product functionality, and processing
continues.
System action
User response OMEGAMON for CICS will request a dump with title
"KCPOC1060E OMEGAMON DUMP" and will disable its
Investigate the RESMGR return code. If this action support for Program Tracking. Program Tracking will
does not lead to a solution, contact IBM Software not be available until CICS restarts.
Support and provide the message text.
KCPOC1050E AN INQUIRE TASK FAILED WITH User response
ZZZZZZZZZ
Contact IBM Software Support and provide the dump
and CICS logs.
Explanation
KCPSG0001E Name field contains invalid
During OMEGAMON for CICS on z/OS processing, a characters
response of ZZZZZZZZZ was returned in EIBRESP
for an INQUIRE TASK command issued by
Explanation
KOCOME00, where ZZZZZZZZZ is INVREQ, NOTAUTH,
or TASKIDERR. The value entered into the Name field contains one or
more invalid characters. These are the valid characters
System action for the Name field: A-Z, a-z, 0-9, and any of the
following characters, $ @ # . / - _ % & ¢ ? ! : | = ¬ ;
KOCOME00 terminates. < >.

If the INQUIRE TASK operation failed with NOTAUTH, The value entered in the Name field is rejected.
ensure that the user who initiated the OMEGAMON
transaction is also authorized to issue an INQUIRE
TASK command against the OMEGAMON transaction.

Correct the entry in the Name field and submit again. The local value is reset to the default value of 15
minutes.
KCPSG0002E Description field contains invalid
characters
User response
Explanation Click Save within the CICS SLA view to commit the
change to the server. If the updated value is not
The value entered into the Description field contains
saved, the existing value remains stored at the server,
one or more invalid characters. The valid characters
however, the default value is used if the OMEGAMON
for the Description field are any basic Latin ASCII
for CICS on z/OS agent is restarted.
characters.
KCPXP001E UNABLE TO OPEN FILE. DDNAME =
System action cccccccc
The value entered in the Description field is rejected.

Explanation
User response The specified file could not be opened for processing.
Correct the entry in the Description field and submit

System action
again.
Expansion processing terminates, producing a return
KCPSG0003E Service Class Rule field contains
code of 8.
invalid characters.
User response
Explanation
Verify the JCL statements in the expansion job, and
The value entered into the Service Class Rule field
check the message log for additional information. If
contains one or more invalid characters. These are the
the problem cannot be resolved by reviewing the JCL
valid characters for the Service Class Rule field: A-Z,
and log, contact IBM Software Support.
a-z, 0-9, and any of the following characters, $ @ # . /
- _ % & ¢ ? ! : | = ¬ ; < >. KCPXP002W NO ELIGIBLE RECORDS WERE
READ
System action
Explanation
The value entered in the Service Class Rule field is
rejected. There were no valid CICS type 110 monitoring
performance class records and no valid system
User response records in the unloaded SMF file.
Correct the entry in the Service Class Rule field and

System action
submit again.
KCPSG0004W The current Collection Interval
code of 8.
value is invalid. A default value of
15 minutes has been set.
User response
Explanation Check that the correct file is being read. Verify that
the CICS monitoring facility was active. Verify that
The value of the interval defined for collecting Service
OMEGAMON CICS is configured to write file detail data
Level Analysis samples currently stored at the server is
to SMF.
invalid. This is likely to have occurred due to a change
in validity rules between releases of OMEGAMON for KCPXP003W NO ELIGIBLE RECORDS REQUIRED
CICS on z/OS. EXPANSION

Explanation 110 monitoring record or an SMF 112 monitoring
record. This error is issued when the z/OS Data
CICS type 110 monitoring performance class records Compression and Expansion service CSRCESRV
and/or system records were read from the unloaded FUNCTION=EXPAND is unable to expand the data
SMF file, but none required expansion. section in the SMF record.
For more information on the return codes issued by
System action the CSRCESRV service, see the z/OS MVS Assembler
Expansion processing terminates normally, producing Services Reference ABE-HSP.
a return code of 4.
System action
User response Expansion processing terminates; this message is
Check that CICS and OMEGAMON are configured to followed by a z/OS abend U0005 with a dump.
compress SMF data.
KCPXP004E CSRCESRV QUERY ERROR - xx User response
Contact IBM Software Support with the following
Explanation information: JCL and JESLOG of the job, and the
U0005 dump.
The KOCSMFXP program received an unexpected
(non-zero) return code from the z/OS Data KCPXP006E CSRCESRV EXPAND LENGTH
Compression and Expansion service CSRCESRV ERROR
FUNCTION=QUERY.
For more information on the return codes issued by Explanation
the CSRCESRV service, see the z/OS MVS Assembler The KOCSMFXP program was able to expand the
Services Reference ABE-HSP. compressed data section for an SMF 112 monitoring
record, however the expanded length does not match
System action the original uncompressed length.
code of 8. System action
Expansion processing terminates; this message is
User response followed by a z/OS abend U0006 with a dump.
If the problem cannot be resolved using the
information on the CSRCESRV service return codes, User response
contact IBM Software Support. Contact IBM Software Support with the following
KCPXP005E CSRCESRV QUERY ERROR - xx information: JCL and JESLOG of the job, and the
U0006 dump.
Explanation
The KOCSMFXP program was unable to expand
the compressed data section for a CICS SMF

Chapter 12. KCPAC messages
This information is a listing of the KCPAC messages, which are generated from OMEGAMON for CICS on
z/OS Take Action requests on the OMEGAMON enhanced 3270 user interface.
KCPAC0580E Background Task manager User response
experienced a CONNECT failure
while retrieving CICSBGT records, Contact IBM Software Support.
RC=xxxxxxxx. KCPAC0583E Background task update
function experienced an OPEN
Explanation SQL REQUEST failure while
nnnnnnnnnnnnnnn, RC=xxxxxxxx.
The Background Task manager was unable to connect
to the hub and perform the SQL create path request in
order to retrieve the records. Explanation
There was an OPEN SQL REQUEST failure.
System action
The Background Task manager terminates processing System action
for this cycle. The Background Task manager terminates processing
for this cycle.
User response
KCPAC0581E Background task update function Contact IBM Software Support.
experienced a CREATE SQL KCPAC0584E Background task update function
ACCESS PLAN failure while experienced a FETCH SQL DATA
nnnnnnnnnnnnnnn, RC=xxxxxxxx. failure while nnnnnnnnnnnnnnn,
RC=xxxxxxxx.
Explanation
There was a CREATE SQL ACCESS PLAN failure. Explanation
There was a FETCH SQL DATA failure.
System action
for this cycle.
User response
KCPAC0582E Background task update function Contact IBM Software Support.
experienced a CREATE SQL KCPAC0585E Background task update
ACCESS PLAN failure while function experienced a CLOSE
nnnnnnnnnnnnnnn, RC=xxxxxxxx. SQL REQUEST failure while
Explanation
There was a CREATE SQL ACCESS PLAN failure. Explanation
There was a CLOSE SQL REQUEST failure.
System action
for this cycle.

Contact IBM Software Support. Resource Limiting status was set to inactive in the
target CICS region.
KCPAC4300I The Resource Limiting command
was successfully processed.
System action
Explanation System processing continues.
A new Resource Limiting rule was added, the selected
rule was deleted or the Resource Limiting status was User response
changed. None.
KCPAC4304I Resource Limiting was already
System action
inactive.
Explanation
User response
The user attempted to set the Resource Limiting status
None. to inactive, but when the command was issued it was
found to be already inactive.
KCPAC4301I Resource Limiting was
successfully enabled.
System action
Explanation System processing continues.
Resource Limiting was set to active in the target CICS
region User response
Another user might have set the Resource Limiting
System action status to inactive. If the status now shows as inactive,
no further action is required. If the status shows as
System processing continues. active, try the request again.
User response KCPAC4305E The keyword value was not

recognized for the Resource
None. Limiting command.
KCPAC4302I Resource Limiting was already
active. Explanation
The Resource Limiting Take Action command
Explanation processor did not recognize a keyword in the Take
Action command.
The user attempted to set the Resource Limiting status
to active, but when the command was issued it was
found to be already active. System action
System processing continues; the command is not
System action processed.
User response
User response Determine why the keyword value is incorrect. Another
user might have modified the exec or panel that issued
Another user might have set the Resource Limiting
the Take Action command.
status to active. If the status now shows as active,
no further action is required. If the status shows as KCPAC4306E The value1 and value2 values
inactive, try the request again. are mutually exclusive for the
Resource Limiting command.
KCPAC4303I Resource Limiting was
successfully disabled.

The displayed values in value1 and value2 are The indicated keyword operand contained an invalid
mutually exclusive. value.

System processing continues; the command is not System processing continues; the request is not
processed. processed.

Determine why the values are incorrect. Another user Determine why the value is incorrect. Another user
might have modified the exec or panel that issued the might have modified the exec or panel that issued the
Take Action command. Take Action command.
KCPAC4307E An invalid command was KCPAC4310E OMEGAMON for CICS is not active
passed to the Resource Limiting in the target CICS region.
processor.
Explanation
Explanation
OMEG INIT processing has not been done in the target
The Resource Limiting Take Action command CICS region.
processor did not recognize the command keyword.
System action
System action
System processing continues; the command is not able to be processed.
processed.
User response
User response
Ensure that OMEGAMON for CICS has been activated
Determine why the command is incorrect. Another within the target CICS region.
user might have modified the exec or panel that issued
the Take Action command. KCPAC4311E Invalid call type.
KCPAC4308E An invalid character was found in Explanation

value value.
This message corresponds to message OC2200; the
call is rejected.
Explanation
The indicated value contains a character that is not System action
allowed in that field.
System processing continues; the request is not
processed.
System action
System processing continues; the command is not User response
processed.
User response KCPAC4312E Entry not found.
Determine why the input value is incorrect. Another
user might have modified the exec or panel that issued Explanation
the Take Action command.
This message corresponds to message OC2201. A user
KCPAC4309E An invalid value was specified attempted to delete an entry, but it was not found.
for value in the Resource Limiting Another user might have deleted the entry.
command.
Chapter 12. KCPAC messages 133

System action KCPAC4316E Invalid Resource Limiting data
found in global data area.
processed.
Explanation
User response Corresponds to message OC2208. While attempting
to either display or update resource limits, it was
None. detected that the Resource Limiting data present in
KCPAC4313E No space for requested addition. the global data area was invalid.

This message corresponds to message OC2202; the The user is unable to modify the Resource Limiting
call is rejected. rules.

The user attempted to add a new Resource Limiting Contact IBM Software Support.
rule and there is insufficient space. KCPAC4317E A locking error has occurred.

Review the existing Resource Limiting rules and free Corresponds to message OC2209. There has been a
up space by deleting unused entries. failure in the serialization of access to OMEGAMON XE
KCPAC4314E System busy, retry the command. for CICS resource limiting data.

Corresponds to message OC2206. The user is unable to modify the Resource Limiting
rules.
System action
User response
System processing continues; retry the command.
User response KCPAC4318E The status must be Active or
Inactive.
The Resource Limiting call has coincided with a call
from another user; retry the command.
Explanation
KCPAC4315E The Resource Limiting function is
unavailable. When attempting to activate or inactivate the Resource
Limiting status, the user must enter the new status in
the input field on the panel. The status must be Active
Explanation or Inactive.
Corresponds to message OC2207 . During
OMEGAMON initialization under CICS, it was detected System action
that there was no valid resource limiting data present.
The Resource Limiting status is not changed.
System action
User response
The user is unable to modify the Resource Limiting
rules. Correct the input and enter the command again.
KCPAC4319W No change to input found. The
User response status remains the same.

When attempting to activate or inactivate the Resource The rule is not added.
Limiting status, the user must enter the new status in
the input field on the panel. No change in the input User response
was detected.
Correct the input in the transaction id field on the
panel.
System action
The Resource Limiting status is not changed. KCPAC4323E The warn limit value must be
numeric.
User response
Explanation
Correct the input and enter the command again.
The value entered in the warn limit field is missing or
KCPAC4320E The rule type must be INC or EXC. invalid.

The rule type passed to the Resource Limiting Take The rule is not added.
Action command processor to add or delete a rule
must be INC (include) or EXC (exclude). User response
Correct the input in the warn limit field on the panel.
System action
The rule is not added or deleted. KCPAC4324E The warn limit value must be
greater than zero.
User response
Explanation
Determine why the rule type passed to the processor
was invalid. Possible causes are that a user has The value entered in the warn limit field is missing or
modified the panels or execs that built the command. invalid.
KCPAC4321E Enter a valid transaction id or System action

mask.
The rule is not added.
Explanation
User response
The transaction id field is blank or invalid.
Correct the input in the warn limit field on the panel.
System action KCPAC4325E The kill limit value must be
The rule is not added. numeric.

Correct the input in the transaction id field on the The value entered in the kill limit field is missing or
panel. invalid.
KCPAC4322E The asterisk must be at the end of System action

the transaction id.
The rule is not added.
Explanation
User response
Only one asterisk (*) can be specified as part of
the transaction id or mask and it must be the last Correct the input in the kill limit field on the panel.
character of the mask.
KCPAC4326E The kill limit value must be greater
than zero.

Explanation KCPAC4330E The rule type must be INC or EXC.
The value entered in the kill limit field must be greater
than zero. Explanation
The rule type keyword was not found.
System action
The rule is not added. System action
The action is not performed.
User response
Correct the input in the kill limit field on the panel. User response
KCPAC4327E The kill limit must be greater than Correct the Resource Limiting Take Action command.
the warn limit. KCPAC4331E The resource type is not specified.
The kill limit value must be greater than the warn limit A resource type was not found in the command input
value. field.

The rule is not added. The action is not performed.

Correct the input in the warn or kill limit fields on the Correct the Resource Limiting Take Action command.
panel.
KCPAC4332E The transaction id is not specified.
KCPAC4328E Cannot delete this line.
Explanation
Explanation
A transaction id was not found in the command input
The user attempted to delete the rule line that is field.
displayed when no Resource Limiting rules are defined
for the specified resource type.
System action
System action The action is not performed.
The rule is not deleted.

User response
User response Correct the Resource Limiting Take Action command.
None. KCPAC4333E The kill or warn limit value is

required.
KCPAC4329E The action must be ADD or DEL.
Explanation
Explanation
Neither a kill or warn limit value was found; at least
The action keyword was not found. one value is required.

The action is not performed. The action is not performed.

Correct the Resource Limiting Take Action command. Correct the Resource Limiting Take Action command.

KCPAC4334E The rule already exists for Explanation
<tranID> transaction.
There was a CREATE SQL ACCESS PLAN failure; this
can happen when reading the CICSBGT table, inserting
Explanation the CICSBGT table row, deleting a CICSBGT table row,
New rule matched transaction ID and resource type of updating the CICSBGT Table, retrieving the INTERVAL
one of existing rules. Duplicate rules are not allowed. row, deleting the INTERVAL row, or inserting the
INTERVAL row.
System action
System action
The action is not performed.
The Background Task manager terminates processing
for this cycle.
User response
Correct the Resource Limiting Take Action command. User response
KCPAC4355I The Background Task for CICSplex Contact IBM Software Support.
cccccccc, CICSNAME nnnnnnnn
was successfully deleted. KCPAC4372E Background task update function
experienced a CREATE SQL
ACCESS PLAN failure while
Explanation nnnnnnnnnnnnnnn, RC=xxxxxxxx.
Background Task delete was successful.
Explanation
System action There was a CREATE SQL ACCESS PLAN failure; this
Processing continues. can happen when reading the CICSBGT table, inserting
the CICSBGT table row, deleting a CICSBGT table row,
updating the CICSBGT Table, retrieving the INTERVAL
User response row, deleting the INTERVAL row, or inserting the
None. INTERVAL row.
KCPAC4370E Background task update function

experienced a CONNECT
System action
failure while nnnnnnnnnnnnnnn, The Background Task manager terminates processing
RC=xxxxxxxx. for this cycle.

There was a CONNECT failure; this can happen when Contact IBM Software Support.
reading the CICSBGT table, inserting the CICSBGT
table row, deleting a CICSBGT table row, updating the KCPAC4373E Background task update function
CICSBGT Table, retrieving the INTERVAL row, deleting experienced a OPEN SQL REQUEST
the INTERVAL row, or inserting the INTERVAL row. failure while nnnnnnnnnnnnnnn,
RC=xxxxxxxx.
System action
Explanation
The Background Task manager terminates processing
for this cycle. There was an OPEN SQL REQUEST failure; this can
happen when reading the CICSBGT table, inserting the
CICSBGT table row, deleting a CICSBGT table row,
User response updating the CICSBGT Table, retrieving the INTERVAL
Contact IBM Software Support. row, deleting the INTERVAL row, or inserting the
INTERVAL row.
System action
nnnnnnnnnnnnnnn, RC=xxxxxxxx. The Background Task manager terminates processing
for this cycle.

Contact IBM Software Support. The action is not performed.
experienced a FETCH SQL DATA User response
failure while nnnnnnnnnnnnnnn, None.
RC=xxxxxxxx.
KCPAC4402I The MRO connection cannot be
Explanation:
released with the Take Action
There was a FETCH SQL DATA failure; this can
command.
happen when reading the CICSBGT table, inserting
the CICSBGT table row, deleting a CICSBGT table row,
updating the CICSBGT Table, retrieving the INTERVAL Explanation
row, deleting the INTERVAL row, or inserting the The MRO connections can not be released through the
INTERVAL row. Take Action command.

The Background Task manager terminates processing The action is not performed.
for this cycle.
User response
User response
None.
KCPAC4411I The indirect TD queue cannot
KCPAC4375E Background task update be enabled with the Take Action
function experienced a CLOSE command.
SQL REQUEST failure while
Explanation
Explanation The indirect TD queues can not be enabled through the
Take Action command.
There was a CLOSE SQL REQUEST failure; this can
happen when reading the CICSBGT table, inserting
the CICSBGT table row, deleting a CICSBGT table row, System action
updating the CICSBGT Table, retrieving the INTERVAL The action is not performed.
row, deleting the INTERVAL row, or inserting the
INTERVAL row.
User response
System action None.
The Background Task manager terminates processing KCPAC4412I The indirect TD queue cannot be
for this cycle. disabled with the Take Action
command.
User response
Explanation
The indirect TD queue can not be disabled through the
KCPAC4401I The MRO connection cannot be Take Action command.
acquired with the Take Action
command.
System action
Explanation The action is not performed.
The MRO connections can not be acquired through the
Take Action commands. User response
None.

KCPAC4413I The indirect TD queue cannot KCPAC4415I The intrapartition TD queue
be opened with the Take Action cannot be opened with the Take
command. Action command.
The indirect TD queue can not be opened through use The intrapartition TD queue can not be opened
of the Take Action command. through use of the Take Action command.


None. None.
KCPAC4414I The indirect TD queue cannot KCPAC4416I The intrapartition TD queue
be closed with the Take Action cannot be closed with the Take
command. Action command.
The indirect TD queue can not be closed through use The intrapartition TD queue can not be closed through
of the Take Action command. the Take Action command.


None. None.

Chapter 13. KCPFH messages
This information is a listing of the KCPFH messages, which are generated by the FindHUb process that
discovers the protocols configured for the hub and establishes a connection to it. These messages are
displayed in RKLVLOG output.
KCPFH0001W The PORT parameter was not Explanation
found and 1918 will be used as the
default port number. This is an informational message that describes the
communication protocol, name or address and port
number that the agent will use to connect to the hub
Explanation Tivoli Enterprise Monitoring Server.
The KDE_TRANSPORT and KDC_FAMILIES parameters
in the hilev.RKANPARU(KC5ENV) member do not have System action
a port number defined for the agent to communicate
with the Tivoli Enterprise Monitoring Server. System processing continues.

The agent will use port number 1918 to communicate None.
with the Tivoli Enterprise Monitoring Server. KCPFH0004E The CICS agent is unable to
connect to the TEMS.
User response
Review the agent and Tivoli Enterprise Monitoring Explanation
Server configuration in PARMGEN. Verify that the An attempt by the CICS agent to connect to the Tivoli
agent and Tivoli Enterprise Monitoring Server specify Enterprise Monitoring Server using the protocol, port
a common protocol and port number. and address or name described in the KCPFH0002I
KCPFH0002I The CICS agent will connect message was unsuccessful.
to its managing TEMS using
protocol at TEMS name/address System action
port nnnnnn as specified in
The agent will retry the connection to the Tivoli
HUB_NAME/CT_CMSLIST.
Enterprise Monitoring Server once a minute.
Explanation
User response
This an informational message that describes the
If the problem persists, verify that the communication
communication protocol, name or address and the
protocol, port and address specified for the agent and
port number that the agent will use to connect to the
the Tivoli Enterprise Monitoring Server is functional.
Correct the configuration if appropriate.
System action KCPFH0005E A SQL request was attempted and

failed with error code nnn.
Explanation
User response
The CICS agent issued an SQL request (Prepare,
None. CreateRequest, OpenRequest, GetOutputSQLDA or
KCPFH0003I The CICS agent will connect to Fetch), which failed with error code =nnn.
the hub TEMS using protocol at
address port nnnnnn. System action
Verify that communications were established with
the Tivoli Enterprise Monitoring Server. See message
KCPFH0002I.

If the problem persists, contact IBM Software Support. The agent will retry communications with the hub
Tivoli Enterprise Monitoring Server once a minute.
KCPFH0009E The configured protocol settings
for the CICS agent and the hub
TEMS do not match. User response
Review messages KCPFH0010Iand KCPFH0011Iand
Explanation correct the protocol configuration for the hub Tivoli
Enterprise Monitoring Server and the CICS agent.
Incompatible protocols for the agent and hub Tivoli
Enterprise Monitoring Server have been configured. KCPFH0011I The configured protocols for the
hub TEMS are: <protocol>#address
System action and port</protocol>.
The agent will retry communications with the hub

Explanation
Tivoli Enterprise Monitoring Server once a minute.
This message lists all the protocols, addresses and
User response ports defined for the hub Tivoli Enterprise Monitoring
Server.
See messages KCPFH0010I and KCPFH0011I. These
messages describe the protocols that were configured
System action
for the agent and hub Tivoli Enterprise Monitoring
Server. Configure the agent and the hub Tivoli System processing continues.
Enterprise Monitoring Server again to correct the
problem. User response
KCPFH0010I The configured protocols for the Review the protocols listed by this message and the
CICS agent are: KCPFH0010I message, and correct the agent and hub
Tivoli Enterprise Monitoring Server configuration as
Explanation appropriate.
This a multi line message. The following lines describe
the protocol and port number configured for the CICS
agent.

Chapter 14. KCPPA messages
This information is a listing of the KCPPA messages, which are generated by the OMEGAMON for CICS on
z/OS CICSplex agent and the processes that coordinate data collection from individual CICS regions in
order to assemble them into CICSplexes. These messages are displayed in RKLVLOG ouput.
KCPPA0010E The number of arguments exceeds KCPPA0026E The IRA Manager command
the limit of 32, quitting. operand is missing.
The IRAMAN command was entered with more than The CICSplex IRA Manager detected a missing
32 arguments. The command is ignored. command operand in a previously entered command.

System processing continues. The command is ignored.

Enter a valid command with the correct number of Correct the command operand and enter the
arguments. command again.
KCPPA0011E The argument string length KCPPA0029E An error was detected
exceeds the limit of 4096, quitting. while registering node
cccccccc::CICSplex, RC=nnnn .
Explanation
Explanation
The IRAMAN command was entered with an argument
longer than 4096 characters. The command is ignored. The node registration function detected an error. The
cccccccc value is the name of the node to be registered
System action and the RC=nnnn value is the return code from the
IRA_Subnode_RegisterEx function.
System action
User response
The node is not registered.
Enter a valid command with the correct number of
arguments.
User response
KCPPA0025E The IRA Manager command is
unknown: cccc.
KCPPA0030E An error was detected
Explanation while deregistering node
cccccccc :CICSplex, RC= nnnn.
The CICSplex IRA Manager detected an unknown
command. The cccc value is name of the unknown
Explanation
command.
The node deregistration function detected an error.
System action The cccccccc value is the name of the registered node
and the RC=nnnn value is the return code from the
The command is ignored. IRA_Subnode_Deregister function.

None. The node is not de registered.

Contact IBM Software Support. None, system processing continues.
KCPPA0031E The IRA_Subnode_SendRequest
call returned RC=nnnn. User response
None.
Explanation
KCPPA0203I The Inquiry thread is not
The IRA_Subnode_SendRequest call function detected responding.
an error. The RC=nnnn value is the return code from
the failed request. Explanation
An attempt to stop the Node Inquiry thread was not
System action
successful.
The request is not honored.
System action
User response
None, system processing continues.
KCPPA0054I OMEGAMON for CICSplex Version User response
rr.vv.mm (Build Level bbbbbb) has None.
started.
KCPPA0204I The Inquiry thread is active.
Explanation
Explanation
The CICSplex agent has started to process.
The Node Inquiry thread finished initialization.
System action
System action
None.
User response
User response
None.
None.
KCPPA0201I The Node Inquiry thread is already
active. KCPPA0205I The Node Inquiry thread is
stopping.
Explanation
Explanation
A command was issued to start the Node Inquiry
thread, but it was already active. The Node Inquiry thread is stopping.

None, system processing continues. None.

None. None.
KCPPA0202I The Node Inquiry thread is not KCPPA0206E The Node Inquiry thread received
active. null data from a fetch.
A command was issued to stop the Node Inquiry The Node Inquiry thread received no rows while
thread, but it was not active. attempting to find out the status of the CICSplex.

The Inquiry thread stops processing. The history collection interval is shorter than the
cycle time being used by KCEPSL to collect the data.
User response Typically, KECPSL runs on a one or five minute cycle. If
the data interval for the history situation for CICSplex
Contact IBM Software Support. SLA is smaller the cycle time for the KCPEPSL module,
or if multiple SLA history situations are active, this
KCPPA0209E The Node Inquiry thread cannot
message might be displayed.
communicate with XMI. Ensure
the OC START ID=XMI command
exists RKANCMD(KxxAGST). System action
SLA CICSplex history data collection continue, but the
Explanation data collected might be incorrect
XMI communication control block using TMS:Engine User response
services. Ensure that only ONE history situation is active for
CICSplex SLA data and that the interval is greater than
System action that used by KCEPSL.
The Node Inquiry Thread continues to wait until XMI See message KCPPA0411I in the RKLVLOG output to
becomes available. determine the CICSplex SLA collection interval.
KCPPA0212I TEMS AT(xxxx) notified of TEMS
User response (yyyy) for CICSplex zzzzzzzz.
Confirm that XMI successfully started as a subtask
of the Tivoli Enterprise Monitoring Server address Explanation
The agent for the CICSplex zzzzzzzz, which is
Tivoli Enterprise Monitoring Server CONFIG file that
connected to the TEMS xxxx is notified that an agent
connected to the local TEMS yyyy should be included
in the processing of the CICSplex.
KCPPA0210I The Node Inquiry thread is
waiting for the CICSplex Agent System action
Preferences to be initialized.
Explanation
User response
The Node Inquiry thread is waiting for the CICSplex
Agent Preferences to be initialized. None required.
KCPPA0213I The agent (xxxx) AT (yyyy) has
System action been notified to start CICSplex
zzzzzzzz.
The Node Inquiry Thread continues to wait until the
CICSplex Agent Preferences become available
Explanation
User response The agent xxxx which is connected to the TEMS yyyy
should register the CICSplex zzzzzzzz.
Verify that the agent is able to connect to the hub
monitoring server. If problems persist, contact IBM
Software Support System action
KCPPA0211E The CICSplex SLA history Processing continues.
collection interval is too short.
User response
None required.
the agent
xxxx which is connected to the TEMS yyyy
Chapter 14. KCPPA messages 145

should register the
CICSplex zzzzzzzz
Explanation
KCPPA0214W The Node Inquiry thread will The Node Inquiry thread was unable to perform a
continue without the CICSplex create SQL access plan request in order to find out the
Agent Preferences. status of a CICSplex. The xxxxxxxx value is the return
code generated by the SQL request.
Explanation
System action
The agent has been unable to communicate with
the hub TEMS to retrieve the CICSplex rules within The Node Inquiry thread stops processing.
2 minutes of startup. This could be because the
application support for OMEGAMON XE for CICS User response
on z/OS has not been completed, SDA processing
has failed or there is a communications problem Contact IBM Software Support.
connecting to the hub TEMS. KCPPA0222E The Node Inquiry thread
System action REQUEST failure while looking
up the status of a CICSplex,
The thread will continue and use the default rules and RC=xxxxxxxx.
allow CICSplexes to be registered. Once the rules are
available the Regions and CICSplexes will be moved to
new CICSplexes if the rules require it. Explanation
The Node Inquiry thread was unable to perform a
User response create SQL request in order to find out the status
of a CICSplex. The xxxxxxxx value is the return code
Check that the hub TEMS is available and that generated by the SQL request.
application support for OMEGAMON XE for CICS on
z/OS has been installed successfully. Check for other
messages relating to communications failures in the System action
RKLVLOG of the agent. The Node Inquiry thread stops processing.
KCPPA0220E The Node Inquiry thread
experienced a CONNECT failure User response
while looking up the status of a
CICSplex, RC=xxxxxxxx. Contact IBM Software Support.
Explanation experienced an OPEN SQL
REQUEST failure while looking
The Inquiry thread was unable to connect to the hub up the status of a CICSplex,
and perform the SQL create path request in order to RC=xxxxxxxx.
find out the status of the CICSplex. The xxxxxxxx value
is the return code generated by the SQL request.
Explanation
System action The Node Inquiry thread was unable to perform an
open SQL request in order to find out the status of
The Inquiry thread stops processing. a CICSplex. The xxxxxxxx value is the return code
User response
KCPPA0221E The Node Inquiry thread The Node Inquiry thread stops processing.
ACCESS PLAN failure while User response
looking up the status of a
experienced a CLOSE SQL

REQUEST failure while looking KCPPA0232E The Node Inquiry thread
up the status of a CICSplex, experienced a RELEASE
RC=xxxxxxxx. CONNECTION failure while looking
up the status of a CICSplex,
Explanation RC=xxxxxxxx.

close SQL request in order to find out the status of
Explanation
a CICSplex. The xxxxxxxx value is the return code The Node Inquiry thread was unable to release the
generated by the SQL request. connection used to find out the status of a CICSplex.
The xxxxxxxx value is the return code generated by the
System action SQL request.
The Node Inquiry thread stops processing.

System action
User response The Node Inquiry thread stops processing.

User response
experienced a DROP SQL REQUEST
failure while looking up the status KCPPA0240E The Node Inquiry thread
of a CICSplex, RC=xxxxxxxx. experienced a CONNECT failure
while retrieving the status of a
Explanation CICSplex TEMS, RC=xxxxxxxx.

drop SQL request in order to find out the status of
Explanation
a CICSplex. The xxxxxxxx value is the return code The Inquiry thread was unable to connect to the hub
generated by the SQL request. and perform an SQL create path request in order to
find out the status of a CICSplex Tivoli Enterprise
System action Monitoring Server. The xxxxxxxx value is the return
System action
User response
KCPPA0227E The Node Inquiry thread User response
experienced a DROP SQL ACCESS
PLAN failure while looking up
the status of a CICSplex, KCPPA0241E The Node Inquiry thread
RC=xxxxxxxx. experienced a CREATE SQL
Explanation retrieving the status of a CICSplex
TEMS, RC=xxxxxxxx.
drop SQL access plan in order to find out the status
Explanation
generated by the SQL request. The Node Inquiry thread was unable to perform
a create SQL access plan request in order to
System action find out the status of a CICSplex Tivoli Enterprise
Monitoring Server. The xxxxxxxx value is the return
The Node Inquiry thread stops processing. code generated by the SQL request.

Contact IBM Software Support. The Node Inquiry thread stops processing.

User response xxxxxxxx value is the return code generated by the SQL
request.
KCPPA0242E The Node Inquiry thread System action
REQUEST failure while retrieving The Node Inquiry thread stops processing.
the status of a CICSplex TEMS,
RC=xxxxxxxx. User response
Explanation
The Node Inquiry thread was unable to perform a experienced a DROP SQL REQUEST
create SQL request in order to find out the status of failure while retrieving the status
a CICSplex Tivoli Enterprise Monitoring Server. The of a CICSplex TEMS, RC=xxxxxxxx.
xxxxxxxx value is the return code generated by the SQL
request.
Explanation
System action The Node Inquiry thread was unable to perform a
drop SQL request in order to find out the status of
The Node Inquiry thread stops processing. a CICSplex Tivoli Enterprise Monitoring Server. The
User response request.

System action
experienced an OPEN SQL The Node Inquiry thread stops processing.
REQUEST failure while retrieving
the status of a CICSplex TEMS, User response
RC=xxxxxxxx.
Explanation KCPPA0247E The Node Inquiry thread

The Node Inquiry thread was unable to perform an PLAN failure while retrieving
open SQL request in order to find out the status of the status of a CICSplex TEMS,
a CICSplex Tivoli Enterprise Monitoring Server. The RC=xxxxxxxx.
request.
Explanation
System action The Node Inquiry thread was unable to perform a drop
SQL access plan request in order to find out the status
The Node Inquiry thread stops processing. of a CICSplex Tivoli Enterprise Monitoring Server. The

System action
experienced a CLOSE SQL The Node Inquiry thread stops processing.
the status of a CICSplex TEMS, User response
RC=xxxxxxxx.
Explanation KCPPA0252E The Node Inquiry thread

experienced a RELEASE
The Node Inquiry thread was unable to perform a CONNECTION failure while
close SQL request in order to find out the status of retrieving the status of a CICSplex
a CICSplex Tivoli Enterprise Monitoring Server. The TEMS, RC=xxxxxxxx.

Explanation REQUEST failure while updating
the TEMS list for a CICSplex,
The Node Inquiry thread was unable to release the RC=xxxxxxxx.
connection used to find out the status of a CICSplex
Tivoli Enterprise Monitoring Server. The xxxxxxxx value
is the return code generated by the SQL request. Explanation
The Inquiry thread was unable to perform a create
System action SQL request in order to update the CICSplex Tivoli
Enterprise Monitoring list. The xxxxxxxx value is the
The Node Inquiry thread stops processing. return code generated by the SQL request.

experienced a CONNECT failure User response
while updating the TEMS list for a
Explanation experienced an OPEN SQL
REQUEST failure while updating
The Inquiry thread was unable to connect to the hub the TEMS list for a CICSplex,
and perform an SQL create path request in order to RC=xxxxxxxx.
update the CICSplex Tivoli Enterprise Monitoring list.
SQL request. Explanation
The Inquiry thread was unable to perform an open

experienced a CREATE SQL User response
updating the TEMS list for a Contact IBM Software Support.
CICSplex, RC=xxxxxxxx. KCPPA0265E The Node Inquiry thread
Explanation REQUEST failure while updating
the TEMS list for a CICSplex,
The Inquiry thread was unable to perform a create SQL RC=xxxxxxxx.
access plan request in order to update the CICSplex
Tivoli Enterprise Monitoring list. The xxxxxxxx value is
the return code generated by the SQL request. Explanation
The Inquiry thread was unable to perform a close


experienced a DROP SQL REQUEST User response
failure while updating the TEMS Contact IBM Software Support.
list for a CICSplex, RC=xxxxxxxx.
Explanation
while retrieving THRUNODEs,
The Inquiry thread was unable to perform a drop RC=xxxxxxxx
SQL request in order to update the CICSplex Tivoli
Enterprise Monitoring list. The xxxxxxxx value is the Explanation
return code generated by the SQL request.
The Node Inquiry thread was unable to connect to
the hub monitoring server and perform the SQL create
System action
path request used to determine the THRUNODE for
The Node Inquiry thread stops processing. a CICSplex. The xxxxxxxx value is the return code
User response
System action
PLAN failure while updating User response
the TEMS list for a CICSplex, Contact IBM Software Support.
RC=xxxxxxxx.
experienced a CREATE
Explanation
SQL ACCESS PLAN failure
The Inquiry thread was unable to perform a drop SQL while retrieving THRUNODEs,
access plan request in order to update the CICSplex RC=xxxxxxxx
Tivoli Enterprise Monitoring list. The xxxxxxxx value is
the return code generated by the SQL request. Explanation
System action
CREATE SQL ACCESS PLAN used to determine the
The Node Inquiry thread stops processing. THRUNODE of a CICSplex. The xxxxxxxx value is the
User response
System action
CONNECTION failure while User response
updating the TEMS list for a Contact IBM Software Support.
CICSplex, RC=xxxxxxxx.
Explanation
The Inquiry thread was unable to release the THRUNODEs, RC=xxxxxxxx
connection used to update the CICSplex Tivoli
Enterprise Monitoring list. The xxxxxxxx value is the Explanation
The Node Inquiry thread was unable to perform
a CREATE SQL REQUEST used to determine the

THRUNODE of a CICSplex. The xxxxxxxx value is the Explanation
The Node Inquiry thread was unable to perform
a DROP SQL REQUEST used to determine the
System action THRUNODE of a CICSplex. The xxxxxxxx value is the


experienced an OPEN SQL
User response
REQUEST failure while retrieving Contact IBM Software Support.
THRUNODEs, RC=xxxxxxxx
Explanation PLAN failure while retrieving
The Node Inquiry thread was unable to perform THRUNODEs, RC=xxxxxxxx
an OPEN SQL REQUEST used to determine the
THRUNODE of a CICSplex. The xxxxxxxx value is the Explanation
DROP SQL ACCESS PLAN used to determine the
System action THRUNODE of a CICSplex. The xxxxxxxx value is the


User response
THRUNODEs, RC=xxxxxxxx
Explanation CONNECTION failure while
The Node Inquiry thread was unable to perform a retrieving THRUNODEs,
close SQL request used to determine the THRUNODE RC=xxxxxxxx
generated by the SQL request. Explanation
The Node Inquiry thread was unable to release the
System action connection used to determine the THRUNODE of
The Node Inquiry thread stops processing. a CICSplex. The xxxxxxxx value is the return code
User response
System action
experienced a DROP SQL
User response
THRUNODEs, RC=xxxxxxxx Contact IBM Software Support.
KCPPA0301E The CICSplex agent cannot
communicate with XMI.

The CICSplex registration thread was unable to locate None.
the address of the XMI communication control block
KCPPA0306I The CICSplex registration thread
using CT/Engine services.
is stopping.
System action
Explanation
The CICSplex registration thread stops processing.
The CICSplex registration thread processing is
stopping.
User response
Confirm that XMI successfully started as a subtask System action
of the agent address space. Verify that there is a
START command in the RKANPARU agent file that None.
the IBM Software Support. User response
KCPPA0302I The CICSplex registration thread None.
is already active.
KCPPA0401I The CICSplex SLA thread is
already active.
Explanation
A command was issued to start the CICSplex Explanation
registration thread, but it was already active.
A command was issued to start the CICSplex SLA
thread, but it was already active.
System action
None, system processing continues. System action
User response
None. User response
is not active.
KCPPA0402I The CICSplex SLA thread is not
active.
Explanation
An attempt to stop the CICSplex registration thread Explanation
was initiated, but the thread was not active.
A command was issued to stop the CICSplex SLA
thread, but it was not active.
System action
None, system processing continues. System action
User response
None. User response
is active.
KCPPA0403I The CICSplex SLA thread is not
responding.
Explanation
The CICSplex registration thread finished initialization. Explanation
An attempt to stop the CICSplex SLA thread was not
System action successful.
None.

None, system processing continues. When processing data from the Tivoli Enterprise
Monitoring Server, no data was received for the xxxx
User response value field.
None.
System action
KCPPA0404I The CICSplex SLA thread is active. The data from this Tivoli Enterprise Monitoring Server
is not accumulated.
Explanation
The CICSplex SLA thread finished the initialization and User response
is currently active. Contact IBM Software Support.
System action KCPPA0411I CICSplex SLA collection interval is

n minutes.
None.
Explanation
User response
This messages displays the collection interval used by
None. the CICSplex SLA agent to collect CICSplex SLA data.
KCPPA0405I The CICSplex SLA thread is
stopping. System action
None.
Explanation
The CICSplex SLA thread is stopping. User response
None.
System action
KCPPA0420E The CICSplex SLA thread
None. experienced a CONNECT failure
while retrieving transaction data,
User response RC=xxxxxxxx.
None.
Explanation
KCPPA0407E The CICSplex SLA task was
The CICSplex SLA thread was unable to connect to the
unable to define a memory object.
hub and perform the SQL create path request in order
Return code=xxxxxxxx, reason
to retrieve the transaction data. The xxxxxxxx value is
code=xxxxxxxx.
the return code generated by the SQL request.

The CICSplex SLA thread received a failure when
The CICSplex SLA thread stops processing.
attempting to define a memory object.
User response
System action
Some service level data is not accumulated.
KCPPA0421E The CICSplex SLA thread
User response experienced a CREATE SQL
Try increasing the MEMLIMIT parameter for the agent retrieving transaction data,
address space. If the problem persists, contact IBM RC=xxxxxxxx.
Software Support.
KCPPA0410E No data was returned from the
TEMS ttttttttttttt for field xxxx.

The CICSplex SLA thread was unable to perform a The CICSplex SLA thread was unable to perform a
create SQL access plan request in order to retrieve the close SQL request in order to retrieve the transaction
transaction data. The xxxxxxxx value is the return code data. The xxxxxxxx value is the return code generated
generated by the SQL request. by the SQL request.

The CICSplex SLA thread stops processing. The CICSplex SLA thread stops processing.

Contact IBM Software Support. Contact IBM Software Support.
KCPPA0422E The CICSplex SLA thread KCPPA0426E The CICSplex SLA thread
experienced a CREATE SQL experienced a DROP SQL REQUEST
REQUEST failure while retrieving failure while retrieving transaction
transaction data, RC=xxxxxxxx. data, RC=xxxxxxxx.
The CICSplex SLA thread was unable to perform a The CICSplex SLA thread was unable to perform a
create SQL request in order to retrieve the transaction drop SQL request in order to retrieve the transaction
data. The xxxxxxxx value is the return code generated data. The xxxxxxxx value is the return code generated
by the SQL request. by the SQL request.


experienced an OPEN SQL experienced a DROP SQL ACCESS
REQUEST failure while retrieving PLAN failure while retrieving
transaction data, RC=xxxxxxxx. transaction data, RC=xxxxxxxx.
The CICSplex SLA thread was unable to perform an The CICSplex SLA thread was unable to perform a
open SQL request in order to retrieve the transaction drop SQL access plan request in order to retrieve the
data. The xxxxxxxx value is the return code generated transaction data. The xxxxxxxx value is the return code
by the SQL request. generated by the SQL request.


experienced a CLOSE SQL experienced a RELEASE
REQUEST failure while retrieving CONNECTION failure while
transaction data, RC=xxxxxxxx.

retrieving transaction data, System action
RC=xxxxxxxx.
This Tivoli Enterprise Monitoring Server will be
considered offline and no further requests will be
Explanation sent until agents connected to the Tivoli Enterprise
The CICSplex SLA thread was unable to release the Monitoring Server become again online.
connection used to retrieve the transaction data. The
xxxxxxxx value is the return code generated by the SQL User response
request.
System action KCPPA0502E THE CICSPLEX AGENT

EXPERIENCED A CREATE SQL
The CICSplex SLA thread stops processing. REQUEST FAILURE WHILE
RETRIEVING THE STATUS OF A
User response CICSPLEX TEMS, RC= xxxxxxxx .
Explanation
KCPPA0500E THE CICSPLEX AGENT
EXPERIENCED A CONNECT The CICSPLEX agent was unable to perform a create
FAILURE WHILE RETRIEVING THE SQL request in order to retrieve the status of a
STATUS OF A CICSPLEX TEMS, Tivoli Enterprise Monitoring Server that is managing
RC= xxxxxxxx . members of a CICSplex. The xxxxxxxx value is the
Explanation
System action
The CICSPLEX agent was unable to connect to the
hub and perform SQL create path request in order to This Tivoli Enterprise Monitoring Server will be
retrieve the status of a Tivoli Enterprise Monitoring considered offline and no further requests will be
Server that is managing members of a CICSplex. The sent until agents connected to the Tivoli Enterprise
xxxxxxxx value is the return code generated by the SQL Monitoring Server become again online.
request.
User response
This Tivoli Enterprise Monitoring Server will be KCPPA0503E THE CICSPLEX AGENT
considered offline and no further requests will be EXPERIENCED AN OPEN SQL
sent until agents connected to the Tivoli Enterprise REQUEST FAILURE WHILE
Monitoring Server become again online. RETRIEVING THE STATUS OF A
CICSPLEX TEMS, RC=xxxxxxxx .
User response
Contact IBM Software Support. Explanation
KCPPA0501E THE CICSPLEX AGENT The CICSPLEX agent was unable to perform an open
EXPERIENCED A CREATE SQL SQL request in order to retrieve the status of a
ACCESS PLAN FAILURE WHILE Tivoli Enterprise Monitoring Server that is managing
RETRIEVING THE STATUS OF A members of a CICSplex. The xxxxxxxx value is the
CICSPLEX TEMS, RC=xxxxxxxx . return code generated by the SQL request.

The CICSPLEX agent was unable to perform a create This Tivoli Enterprise Monitoring Server will be
SQL access plan in order to retrieve the status of a considered offline and no further requests will be
Tivoli Enterprise Monitoring Server that is managing sent until agents connected to the Tivoli Enterprise
members of a CICSplex. The xxxxxxxx value is the Monitoring Server become again online.

Contact IBM Software Support. The CICSPLEX agent was unable to perform a drop
SQL access plan request in order to retrieve the
KCPPA0505E THE CICSPLEX AGENT status of a Tivoli Enterprise Monitoring Server that is
EXPERIENCED A CLOSE SQL managing members of a CICSplex. The xxxxxxxx value
REQUEST FAILURE WHILE is the return code generated by the SQL request.
System action
Explanation This Tivoli Enterprise Monitoring Server will be
The CICSPLEX agent was unable to perform a close sent until agents connected to the Tivoli Enterprise
SQL request in order to retrieve the status of a Monitoring Server become again online.
Tivoli Enterprise Monitoring Server that is managing
members of a CICSplex. The xxxxxxxx value is the
return code generated by the SQL request. User response
System action
KCPPA0512E THE CICSPLEX AGENT
This Tivoli Enterprise Monitoring Server will be EXPERIENCED A RELEASE
considered offline and no further requests will be CONNECTION FAILURE WHILE
sent until agents connected to the Tivoli Enterprise RETRIEVING THE STATUS OF A
Monitoring Server become again online. CICSPLEX TEMS, RC= xxxxxxxx .

Contact IBM Software Support. The CICSPLEX agent was unable to release the
connection used to retrieve the status of a Tivoli
KCPPA0506E THE CICSPLEX AGENT Enterprise Monitoring Server that is managing
EXPERIENCED A DROP SQL members of a CICSplex. The xxxxxxxx value is the
REQUEST FAILURE WHILE return code generated by the SQL request.
System action
Explanation This Tivoli Enterprise Monitoring Server will be
The CICSPLEX agent was unable to perform a drop sent until agents connected to the Tivoli Enterprise
SQL request in order to retrieve the status of a Monitoring Server become again online.
Tivoli Enterprise Monitoring Server that is managing
members of a CICSplex. The xxxxxxxx value is the
return code generated by the SQL request. User response
System action
KCPPA0520I THE TEMS xxx IS OFFLINE,
This Tivoli Enterprise Monitoring Server will be TME ENTRY INVALIDATED FOR
considered offline and no further requests will be zzzzzzzz.
sent until agents connected to the Tivoli Enterprise
Monitoring Server become again online. Explanation
The TEMS xxx was determined to be no longer online.
User response
KCPPA0507E THE CICSPLEX AGENT Processing continues, the TEMS xxx is no longer polled
EXPERIENCED A DROP SQL as part of the CICSplex zzzzzzzz.
ACCESS PLAN FAILURE WHILE
CICSPLEX TEMS, RC= xxxxxxxx .

None. An attempt to obtain carved storage was unsuccessful.
The interval manager is unable to process. This would
KCPPA0521I THE TEMS xxx IS ONLINE, indicate a very severe shortage of storage.
CICSPLEX zzzzzzzz.
System action
Explanation
The CICSplex classification rules or service class
Following a communications error the target TEMS was definitions are not processed.
determined to be online.
User response
System action
Check for other errors in the RKLVLOG indicating
Processing continues, the TEMS xxx will continue to be storage problems in the OMEGAMON CICS agent.
polled as part of the CICSplex zzzzzzzz.
KCPPA0554E The Interval Record Manager
User response cannot initialize.
None.
Explanation
KCPPA0551E The Interval Record Manager During initialization the interval manager was unable
cannot communicate with the to publish the address of its global control block.
OMEGAMON CICS agent.
System action
Explanation
The CICSplex classification rules or service class
The interval record manager is attempting to run definitions are not processed.
before the OMEGAMON CICS agent is initialized. This
may be normal during initialization, but this message
should not persist. User response
If the situation persists, contact IBM Software
System action Support.
Processing continues, The CICSplex classification KCPPA0555E The HUB TEMS does not have
rules or service class definitions are not processed. application support for the
OMEGAMON CICS product.
User response
Explanation
If the situation persists contact IBM Software Support.
During initialization it was determined that the
KCPPA0552I The Interval Record Manager is not required install of application support has not
initialized. completed. If using the SDA feature this indicates that
the process has not completed.
Explanation
The interval record manager was asked to terminate System action
but it had not started. Processing continues, the CICSplex classification rules
or service class definitions are not processed.
System action
Processing continues. User response
Either install the application support or check the
User response status of the SDA for the KCP product.
None required. KCPPA0556E The Interval Record Manager
cannot communicate with the HUB
KCPPA0553I The Interval Record Manager is
TEMS.
unable to allocate global storage.

Explanation SQL ACCESS PLAN failure
while retrieving the record,
This message follows an earlier an earlier message RC=xxxxxxxx.
that indicates that the interval record manager has lost
connection to the Hub TEMS.
Explanation
System action The interval record manager was unable to perform a
create SQL access plan request in order to read the
Processing continues, the CICSplex classification rules interval record. The xxxxxxxx value is the return code
or service class definitions are not processed. generated by the SQL request.

Check that the hub TEMS is still available. If unable Changes to the CICSplex classification rules or service
to determine the cause of the failure contact IBM class definitions will not be checked for at least 1
Software Support. additional minute.
KCPPA0557I Minimal application support has
been installed. User response
Check that the hub TEMS is still available. If unable
Explanation to determine the cause of the failure, contact IBM
Minimal application support required for SLA and Software Support.
CICSplex rules has been installed automatically. KCPPA0562E The Interval Record Manager
experienced a CREATE
System action SQL ACCESS PLAN failure
while retrieving the record,
Processing continues. RC=xxxxxxxx.

None required. The interval record manager was unable to perform a
KCPPA0560E The Interval Record Manager create SQL access plan request in order to read the
experienced a CONNECT failure interval record. The xxxxxxxx value is the return code
while retrieving the record, generated by the SQL request.
RC=xxxxxxxx.
System action
Explanation Changes to the CICSplex classification rules or service
The interval record manager was unable to connect to class definitions will not be checked for at least 1
the hub and perform the SQL create path request in additional minute.
order to read the interval record. The xxxxxxxx value is
the return code generated by the SQL request. User response
Check that the Hub TEMS is still available. If unable
System action to determine the cause of the failure, contact IBM
Changes to the CICSplex classification rules or service Software Support.
class definitions will not be checked for at least 1 KCPPA0563E The Interval Record Manager
additional minute. experienced an OPEN SQL
User response the record, RC=xxxxxxxx.
to determine the cause of the failure, contact IBM Explanation
Software Support. The interval record manager was unable to perform a
KCPPA0561E The Interval Record Manager open SQL request in order to read the interval record.
experienced a CREATE The xxxxxxxx value is the return code generated by the
SQL request.

System action KCPPA0571E The Interval Record Manager
Changes to the CICSplex classification rules or service ACCESS PLAN failure while
class definitions will not be checked for at least 1 inserting the record to
additional minute. table OMCICS.nnnnnnnnnn,
RC=xxxxxxxx.
User response
Check that the Hub TEMS is still available. If unable Explanation
to determine the cause of the failure, contact IBM The interval record manager was unable to perform a
Software Support. create SQL access plan request in order to insert the
KCPPA0564E The Interval Record Manager minimal required records for SLA and CICSplex rules
experienced a FETCH SQL DATA to function properly. The xxxxxxxx value is the return
failure while retrieving the record, code generated by the SQL request. The nnnnnnnnnn
RC=xxxxxxxx. value is the CICS table name.

The interval record manager was unable to perform a There will be no more attempts to install minimal
fetch SQL request in order to read the interval record. application support.
SQL request. User response
System action to determine the cause of the failure, contact IBM
Changes to the CICSplex classification rules or service Software Support.
class definitions will not be checked for at least 1 KCPPA0572E The Interval Record Manager
additional minute. experienced a CREATE SQL
REQUEST failure while
User response inserting the record to
table OMCICS.nnnnnnnnnn,
RC=xxxxxxxx.
to determine the cause of the failure contact IBM
Software Support.
Explanation
KCPPA0565E The Interval Record Manager
experienced a CLOSE SQL The interval record manager was unable to perform
REQUEST failure while retrieving a create SQL request in order to insert the minimal
the record, RC=xxxxxxxx. required records for SLA and CICSplex rules to
function properly. The xxxxxxxx value is the return
code generated by the SQL request. The nnnnnnnnnn
Explanation value is the CICS table name.
The interval record manager was unable to perform a
close SQL request in order to read the interval record. System action
SQL request. There will be no more attempts to install minimal
application support.
System action
User response
Changes to the CICSplex classification rules or service
class definitions will not be checked for at least 1 Check that the hub TEMS is still available. If unable
additional minute. to determine the cause of the failure, contact IBM
Software Support.
User response KCPPA0573E The Interval Record Manager
REQUEST failure while
inserting the record to
Software Support.

table OMCICS.nnnnnnnnnn, The xxxxxxxx value is the return code generated by the
RC=xxxxxxxx. SQL request.

The interval record manager was unable to perform The Background Task Manager stops processing
a open SQL request in order to insert the minimal without returning a row.
required records for SLA and CICSplex rules to
function properly. The xxxxxxxx value is the return User response
value is the CICS table name. Contact IBM Software Support.
KCPPA0581E The BTE MANAGER EXPERIENCED
System action A CREATE SQL ACCESS PLAN
There will be no more attempts to install minimal FAILURE WHILE RETRIEVING THE
application support. RECORD, RC=xxxxxxxx.

Check that the hub TEMS is still available. If unable The Background Task Manager was unable to perform
to determine the cause of the failure, contact IBM a create SQL access plan request. The xxxxxxxx value
Software Support. is the return code generated by the SQL request.
KCPPA0575E The Interval Record Manager System action

REQUEST failure while There will be no more attempts to complete the
inserting the record to operation.
table OMCICS.nnnnnnnnnn,
Explanation
to determine the cause of the failure, contact IBM
The interval record manager was unable to perform Software Support.
a close SQL request in order to insert the minimal
KCPPA0582E The BTE MANAGER EXPERIENCED
required records for SLA and CICSplex rules to
A CREATE SQL ACCESS PLAN
function properly. The xxxxxxxx value is the return
FAILURE WHILE RETRIEVING THE
RECORD, RC=xxxxxxxx.
value is the CICS table name.

The Background Task Manager was unable to perform
There will be no more attempts to install minimal
a create SQL access plan request. The xxxxxxxx value
application support.
User response
System action
There will be no more attempts to complete the
to determine the cause of the failure, contact IBM
operation.
Software Support.
KCPPA0580E THE BTE MANAGER EXPERIENCED User response
A CONNECT FAILURE WHILE
RETRIEVING THE RECORD, Check that the hub TEMS is still available. If unable
RC=xxxxxxxx. to determine the cause of the failure, contact IBM
Software Support.
Explanation KCPPA0583E THE BTE MANAGER EXPERIENCED
AN OPEN SQL REQUEST FAILURE
The Background Task Manager was unable to connect
to the hub and perform the SQL create path request.

WHILE RETRIEVING THE RECORD, System action
RC=xxxxxxxx.
Changes to the CICSplex classification rules or service
class definitions will not be checked for at least 1
Explanation additional minute.
The Background Task Manager was unable to perform
a open SQL request in order to read the interval record. User response
SQL request. Check that the hub TEMS is still available. If unable
Software Support.
System action
KCPPA1010E THE CICSPLEX OVERVIEW IRA
Changes to the CICSplex classification rules or service EXPERIENCED A CONNECT
class definitions will not be checked for at least 1 FAILURE WHILE RETRIEVING
additional minute. REGION OVERVIEW DATA,
RC=xxxxxxxx.
User response
Check that the Hub TEMS is still available. If unable Explanation
to determine the cause of the failure, contact IBM The CICSplex Overview IRA was unable to connect
Software Support. to the hub and perform the SQL create path request
KCPPA0584E THE BTE EXPERIENCED A in order to retrieve CICS region overview data. The
FETCH SQL DATA FAILURE xxxxxxxx value is the return code generated by the SQL
WHILE RETRIEVING THE RECORD, request.
RC=xxxxxxxx.
System action
Explanation The CICSPlex Overview IRA stops processing without
The Batch Task Manager was unable to perform a fetch returning a row.
SQL request in order to read the interval record. The
xxxxxxxx value is the return code generated by the User response
SQL request.
System action KCPPA1011E THE CICSPLEX OVERVIEW IRA

Changes to the CICSplex classification rules or service ACCESS PLAN FAILURE WHILE
class definitions will not be checked for at least 1 RETRIEVING REGION OVERVIEW
additional minute. DATA, RC=xxxxxxxx.

Check that the Hub TEMS is still available. If unable The CICSplex Overview IRA was unable to perform a
to determine the cause of the failure contact IBM create SQL access plan request in order to retrieve
Software Support. CICS region overview data. The xxxxxxxx value is the
KCPPA0585E THE BTE MANAGER EXPERIENCED return code generated by the SQL request.
A CLOSE SQL REQUEST FAILURE
WHILE RETRIEVING THE RECORD, System action
RC=xxxxxxxx.
The CICSPlex Overview IRA stops processing without
returning a row.
Explanation
The Batch Task Manager was unable to perform a User response
close SQL request in order to read the interval record.
The xxxxxxxx value is the return code generated by the Contact IBM Software Support.
SQL request. KCPPA1012E THE CICSPLEX OVERVIEW
IRA EXPERIENCED A CREATE

SQL REQUEST FAILURE WHILE User response
RETRIEVING REGION OVERVIEW
DATA, RC=xxxxxxxx. Contact IBM Software Support.
KCPPA1016E THE CICSPLEX OVERVIEW
Explanation IRA EXPERIENCED A DROP
SQL REQUEST FAILURE WHILE
The CICSplex Overview IRA was unable to perform a RETRIEVING REGION OVERVIEW
create SQL request in order to retrieve CICS region DATA, RC=xxxxxxxx.
overview data. The xxxxxxxx value is the return code
Explanation
System action The CICSplex Overview IRA was unable to perform
a drop SQL request in order to retrieve CICS region
The CICSPlex Overview IRA stops processing without overview data. The xxxxxxxx value is the return code
returning a row. generated by the SQL request.

Contact IBM Software Support. The CICSPlex Overview IRA stops processing without
KCPPA1013E THE CICSPLEX OVERVIEW returning a row.
IRA EXPERIENCED AN OPEN
KCPPA1017E THE CICSPLEX OVERVIEW IRA
Explanation EXPERIENCED A DROP SQL
The CICSplex Overview IRA was unable to perform RETRIEVING REGION OVERVIEW
an open SQL request in order to retrieve CICS region DATA, RC=xxxxxxxx.
Explanation
System action The CICSplex Overview IRA was unable to perform a
drop SQL access plan request in order to retrieve CICS
The CICSPlex Overview IRA stops processing without region overview data. The xxxxxxxx value is the return
returning a row. code generated by the SQL request.

Contact IBM Software Support. The CICSPlex Overview IRA stops processing without
KCPPA1015E THE CICSPLEX OVERVIEW returning a row.
IRA EXPERIENCED A CLOSE
KCPPA1022E THE CICSPLEX OVERVIEW
Explanation IRA EXPERIENCED A RELEASE
CONNECTION FAILURE WHILE
The CICSplex Overview IRA was unable to perform RETRIEVING REGION OVERVIEW
a close SQL request in order to retrieve CICS region DATA, RC=xxxxxxxx.
Explanation
System action The CICSplex Overview IRA was unable to release the
connection used to retrieve CICS region overview data.
returning a row.

The xxxxxxxx value is the return code generated by the Explanation
SQL request.
The CICSplex agent has initialized successfully.
System action
System action
returning a row. This is an informational message; no action is required.

Contact IBM Software Support. None, system processing continues.
KCPPA7080I The CICSplex agent has been

initialized.

Chapter 15. KCPPL messages
This information is a listing of the KCPPL messages generated by the processes that coordinate the
definition of CICSplexes. They are displayed in the RKLVLOG output.
For definitions of the SQL return codes cited in this message set, see the "KDCNCnnn message status
codes topic" in the IBM Tivoli Monitoring: Messages Guide.
KCPPL1205E The Managed Systems Manager Explanation
while looking up regions in a The Managed Systems Manager was unable to perform
CICSplex, RC=xxxxxxxx. a create SQL request in order to find the regions that
belong to a CICSplex. The xxxxxxxx value is the return
Explanation
The Managed Systems Manager was unable to connect System action
to the hub and perform the SQL create path request in
order to find the regions that belong to a CICSplex. The The Managed Systems Manager stops processing.
request. User response
System action
KCPPL1208E The Managed Systems Manager
The Managed Systems Manager stops processing. experienced an OPEN SQL
User response up regions in a CICSplex,
RC=xxxxxxxx.
ACCESS PLAN failure while The Managed Systems Manager was unable to perform
looking up regions in a CICSplex, an open SQL request in order to find the regions that
RC=xxxxxxxx. belong to a CICSplex. The xxxxxxxx value is the return
Explanation
System action
The Managed Systems Manager was unable to perform
a create SQL access plan request in order to find the The Managed Systems Manager stops processing.
regions that belong to a CICSplex. The xxxxxxxx value
is the return code generated by the SQL request. User response
System action
The Managed Systems Manager stops processing. experienced a CLOSE SQL
User response up regions in a CICSplex,
RC=xxxxxxxx.
REQUEST failure while looking The Managed Systems Manager was unable to perform
up regions in a CICSplex, a close SQL request in order to find the regions that
RC=xxxxxxxx. belong to a CICSplex. The xxxxxxxx value is the return

System action that belong to a CICSplex. The xxxxxxxx value is the
The Managed Systems Manager stops processing.
System action
User response
KCPPL1211E The Managed Systems Manager User response
failure while looking up regions in Contact IBM Software Support.
a CICSplex, RC=xxxxxxxx. KCPPL1258E The PCLASS Manager was unable
to acquire tname work storage,
The Managed Systems Manager was unable to perform Explanation:

a drop SQL request in order to find the regions that The CICSplex classification rules manager was unable
belong to a CICSplex. The xxxxxxxx value is the return to acquire work storage. The tname value is the name
code generated by the SQL request. of the table being processed. The xxxxxxxx value is the
System action System action:
The Managed Systems Manager stops processing. processing.
User response:
Contact IBM Software Support. KCPPL1261E THE PCLASS MANAGER
KCPPL1212E The Managed Systems Manager EXPERIENCED A CREATE SQL
experienced a DROP SQL ACCESS ACCESS PLAN FAILURE WHILE
PLAN failure while looking RETRIEVING PCLASS RECORDS,
up regions in a CICSplex, RC=xxxxxxxx.
RC=xxxxxxxx.
Explanation
Explanation The PCLASS Manager was unable to perform the
The Managed Systems Manager was unable to perform create SQL access plan request in order to retrieve the
a drop SQL access plan request in order to find the CICSplex definitions. The xxxxxxxx value is the return
regions that belong to a CICSplex. The xxxxxxxx value code generated by the SQL request.
System action
System action The PCLASS Manager stops processing.
User response
Contact IBM Software Support. KCPPL1262E THE PCLASS MANAGER
KCPPL1257E The Managed Systems Manager EXPERIENCED A CREATE SQL
experienced a RELEASE REQUEST FAILURE WHILE
CONNECTION failure while RETRIEVING PCLASS RECORDS,
updating CICSplex members, RC=xxxxxxxx.
RC=xxxxxxxx.
Explanation
Explanation The PCLASS Manager was unable to perform a
The Managed Systems Manager was unable to release create SQL request in order to retrieve the CICSplex
the connection used to update the CICS region names definitions. The xxxxxxxx value is the return code

The PCLASS Manager stops processing. The PCLASS Manager was unable to perform a
drop SQL request in order to retrieve the CICSplex
User response definitions. The xxxxxxxx value is the return code
KCPPL1263E THE PCLASS MANAGER System action
EXPERIENCED AN OPEN SQL The PCLASS Manager stops processing.
REQUEST FAILURE WHILE
RETRIEVING PCLASS RECORDS,
Explanation
KCPPL1267E THE PCLASS MANAGER
The PCLASS Manager was unable to perform an EXPERIENCED A DROP SQL
open SQL request in order to retrieve the CICSplex ACCESS PLAN FAILURE WHILE
definitions. The xxxxxxxx value is the return code RETRIEVING PCLASS RECORDS,
generated by the SQL request. RC=xxxxxxxx.

The PCLASS Manager stops processing. The PCLASS Manager was unable to perform a drop
SQL access plan request in order to retrieve the
User response CICSplex definitions. The xxxxxxxx value is the return
KCPPL1265E THE PCLASS MANAGER System action
EXPERIENCED A CLOSE SQL The PCLASS Manager stops processing.
Explanation
The PCLASS Manager was unable to perform a EXPERIENCED A CONNECT
close SQL request in order to retrieve the CICSplex FAILURE WHILE RETRIEVING THE
definitions. The xxxxxxxx value is the return code INTERVAL RECORD, RC=xxxxxxxx.
Explanation:
The PCLASS Manager could not perform a fetch SQL
System action request so it could retrieve the single row from the
INTERVAL table. The xxxxxxxx value is the return code
The PCLASS Manager stops processing.
User response System action:

User response:
KCPPL1266E THE PCLASS MANAGER Contact IBM Software Support.
EXPERIENCED A DROP SQL
RC=xxxxxxxx.
RETRIEVING THE INTERVAL
Explanation:
Chapter 15. KCPPL messages 167

The PCLASS Manager could not create an SQL access KCPPL1275E THE PCLASS MANAGER
plan request so it could retrieve the single row from EXPERIENCED A CLOSE SQL
the INTERVAL table. The xxxxxxxx value is the return REQUEST FAILURE WHILE
code generated by the SQL request. RETRIEVING THE INTERVAL
System action:
The PCLASS Manager stops processing. Explanation:
The PCLASS Manager could not close the SQL request
User response:
after retrieving the single row from the INTERVAL
table. The xxxxxxxx value is the return code generated
KCPPL1272E THE PCLASS MANAGER by the SQL request.
System action:
RECORD, RC=xxxxxxxx. User response:
Explanation:
The PCLASS Manager could not create an SQL request KCPPL1276E THE PCLASS MANAGER
so it could retrieve the single row from the INTERVAL EXPERIENCED A DROP SQL
table. The xxxxxxxx value is the return code generated REQUEST FAILURE WHILE
by the SQL request. RETRIEVING THE INTERVAL
System action:
User response: The PCLASS Manager could not drop the SQL request
Contact IBM Software Support. after retrieving the single row from the INTERVAL
EXPERIENCED AN OPEN SQL
System action:
RECORD, RC=xxxxxxxx. User response:
Explanation:
The PCLASS Manager could not open an SQL request KCPPL1277E THE PCLASS MANAGER
so it could retrieve the single row from the INTERVAL EXPERIENCED A DROP SQL
table. The xxxxxxxx value is the return code generated ACCESS PLAN FAILURE WHILE
by the SQL request. RETRIEVING THE INTERVAL
System action: RECORD, RC=xxxxxxxx.
The PCLASS Manager could not drop the SQL access
User response:
plan after retrieving the single row from the INTERVAL
EXPERIENCED A FETCH SQL DATA
System action:
FAILURE WHILE RETRIEVING THE
INTERVAL RECORD, RC=xxxxxxxx.
User response:
Explanation:
The PCLASS Manager could not perform a fetch SQL
data so it could retrieve the single row from the KCPPL1281E The Managed Systems Manager
INTERVAL table. The xxxxxxxx value is the return code experienced a CREATE SQL
generated by the SQL request. ACCESS PLAN failure while
System action: updating SystemID list members,
The PCLASS Manager stops processing. RC=xxxxxx.
User response:

Explanation User response:
The Managed Systems Manager was unable to perform Contact IBM Software Support.
a create SQL access plan request in order to update KCPPL1286E The Managed Systems Manager
the regions in a SystemID list, where: experienced a DROP SQL REQUEST
xxxxxx failure while updating SystemID
Is the return code generated by the SQL request. list members, RC=xxxxxxxx.
System action: Explanation:
The Managed Systems Manager stops processing. The Managed Systems Manager could not drop an SQL
request after updating the regions in a SystemID list.
User response: The xxxxxxxx value is the return code generated by the
Contact IBM Software Support. SQL request.
KCPPL1282E The Managed Systems Manager System action:
experienced a CREATE SQL The Managed Systems Manager stops processing.
SystemID list members, User response:
RC=xxxxxxxx. Contact IBM Software Support.
Explanation: KCPPL1287E The Managed Systems Manager
The Managed Systems Manager could not create an experienced a DROP SQL
SQL request so it could update the regions in a ACCESS PLAN failure while
SystemID list. The xxxxxxxx value is the return code updating SystemID list members,
The Managed Systems Manager stops processing. The Managed Systems Manager could not drop an SQL
access plan after updating the regions in a SystemID
User response: list. The xxxxxxxx value is the return code generated by
Contact IBM Software Support. the SQL request.
experienced an OPEN SQL The Managed Systems Manager stops processing.
The Managed Systems Manager could not open an SQL experienced a CREATE SQL
request so it could update the regions in a SystemID ACCESS PLAN failure while
list. The xxxxxxxx value is the return code generated by deleting region names from a
the SQL request. SystemID list, RC=xxxxxxxx.
The Managed Systems Manager stops processing. The Managed Systems Manager could not create an
SQL access plan request so it could delete CICS region
User response: names from a SystemID list. The xxxxxxxx value is the
Contact IBM Software Support. return code generated by the SQL request.
experienced a CLOSE SQL The Managed Systems Manager stops processing.
The Managed Systems Manager could not close an SQL experienced a CREATE SQL
request after updating the regions in a SystemID list. REQUEST failure while deleting
The xxxxxxxx value is the return code generated by the region names from a SystemID
SQL request. list, RC=xxxxxxxx.
The Managed Systems Manager stops processing. The Managed Systems Manager could not create an
SQL request so it could delete CICS region names from

a SystemID list. The xxxxxxxx value is the return code PLAN failure while deleting region
generated by the SQL request. names from a SystemID list,
RC=xxxxxxxx.
System action:
The Managed Systems Manager stops processing. Explanation:
The Managed Systems Manager could not drop an SQL
User response:
access plan after deleting CICS region names from a
SystemID list. The xxxxxxxx value is the return code
KCPPL1303E The Managed Systems Manager generated by the SQL request.
System action:
REQUEST failure while deleting
region names from a SystemID
list, RC=xxxxxxxx. User response:
Explanation:
The Managed Systems Manager could not open an SQL KCPPL1311E THE PCLASS MANAGER
request so it could delete CICS region names from a EXPERIENCED A RELEASE
SystemID list. The xxxxxxxx value is the return code CONNECTION FAILURE WHILE
generated by the SQL request. RETRIEVING PAGPREFS
RECORDS, RC=xxxxxxxx.
System action:
The Managed Systems Manager stops processing. Explanation:
The PCLASS Manager could not release the connection
User response:
used to retrieve the PAGPREFS definitions. The
KCPPL1305E The Managed Systems Manager request.
System action:
region names from a SystemID
list, RC=xxxxxxxx. User response:
Explanation:
The Managed Systems Manager could not close an KCPPL1320E PAGPREFS INPUT SQLDA error,
SQL request after deleting CICS region names from a expected number is 8, SQLDA
SystemID list. The xxxxxxxx value is the return code columns = columns
Explanation:
System action: The PCLASS Manager encountered an error while
The Managed Systems Manager stops processing. updating the PAGPREFS table. The number of columns
read does not equal 8. The SQLDA columns count
User response:
shows the number of columns contained in the SQLDA
input buffer.
System action:
failure while deleting region
names from a SystemID list, User response:
Explanation: KCPPL1331E THE PCLASS MANAGER
The Managed Systems Manager could not drop an EXPERIENCED A CREATE
SQL request after deleting CICS region names from a SQL ACCESS PLAN FAILURE
SystemID list. The xxxxxxxx value is the return code WHILE RETRIEVING PAGPREFS
generated by the SQL request. RECORDS, RC=xxxxxxxx.
The Managed Systems Manager stops processing. The PCLASS Manager could not create an SQL access
plan request so it could retrieve records from the
User response:
PAGPREFS table. The xxxxxxxx value is the return code
System action:

User response: The PCLASS Manager could not drop an SQL request
Contact IBM Software Support. after retrieving records from the PAGPREFS table. The
request.
EXPERIENCED A CREATE
SQL REQUEST FAILURE System action:
WHILE RETRIEVING PAGPREFS The PCLASS Manager stops processing.
User response:
Explanation: Contact IBM Software Support.
The PCLASS Manager could not create an SQL request
so it could retrieve records from the PAGPREFS table.
EXPERIENCED A DROP SQL
ACCESS PLAN FAILURE
SQL request.
WHILE RETRIEVING PAGPREFS
System action: RECORDS, RC=xxxxxxxx.
Explanation:
User response: The PCLASS Manager could not drop an SQL access
Contact IBM Software Support. plan after retrieving records from the PAGPREFS table.
SQL request.
EXPERIENCED AN OPEN
User response:
The PCLASS Manager could not open an SQL request
to retrieve records from the PAGPREFS table. The
request.
INITIALIZING THE PAGPREFS
System action: TABLE, RC=xxxxxxxx.
Explanation:
User response: The PCLASS Manager could not create an SQL access
Contact IBM Software Support. plan request to initialize the PAGPREFS table. The
request.
EXPERIENCED A CLOSE
User response:
The PCLASS Manager could not close an SQL request
after retrieving records from the PAGPREFS table. The
request.
System action: TABLE, RC=xxxxxxxx.
Explanation:
User response: The PCLASS Manager could not create an SQL request
Contact IBM Software Support. to initialize the PAGPREFS table. The xxxxxxxx value is
EXPERIENCED A DROP System action:
SQL REQUEST FAILURE The PCLASS Manager stops processing.
WHILE RETRIEVING PAGPREFS
User response:
Explanation:

KCPPL1343E THE PCLASS MANAGER The Managed Systems Manager stops processing.
EXPERIENCED AN OPEN SQL User response:
REQUEST FAILURE WHILE Contact IBM Software Support.
TABLE, RC=xxxxxxxx. KCPPL1352E The Managed Systems Manager
Explanation:
REQUEST failure while Function,
The PCLASS Manager could not open an SQL request RC=xxxxxxxx.
to initialize the PAGPREFS table. The xxxxxxxx value is
the return code generated by the SQL request. Explanation:
System action: a CREATE SQL request in order to perform the
The PCLASS Manager stops processing. indicated function. The xxxxxxxx value is the return
User response: code generated by the SQL request.
Contact IBM Software Support. System action:
EXPERIENCED A DROP SQL User response:
REQUEST FAILURE WHILE Contact IBM Software Support.
Explanation: REQUEST failure while Function,
The PCLASS Manager could not drop an SQL request
RC=xxxxxxxx.
after initializing the PAGPREFS table. The xxxxxxxx
value is the return code generated by the SQL request. Explanation:
System action:
an OPEN SQL request in order to perform the indicated
function. The xxxxxxxx value is the return code
User response: generated by the SQL request.
System action:
EXPERIENCED A DROP SQL User response:
ACCESS PLAN FAILURE WHILE Contact IBM Software Support.
Explanation:
The PCLASS Manager could not drop an SQL access
RC=xxxxxxxx.
plan after initializing the PAGPREFS table. The
xxxxxxxx value is the return code generated by the SQL Explanation:
request. The Managed Systems Manager was unable to perform
a CLOSE SQL request in order to perform the indicated
System action: function. The xxxxxxxx value is the return code
The PCLASS Manager stops processing. generated by the SQL request.
User response: System action:
Contact IBM Software Support. The Managed Systems Manager stops processing.
KCPPL1351E The Managed Systems Manager User response:
experienced a CREATE SQL Contact IBM Software Support.
Function, RC=xxxxxxxx. KCPPL1356E The Managed Systems Manager
experienced a DROP SQL
Explanation:
RC=xxxxxxxx.
a CREATE SQL ACCESS PLAN request in order to
perform the indicated function. The xxxxxxxx value is Explanation:
the return code generated by the SQL request. The Managed Systems Manager was unable to perform
a DROP SQL request in order to perform the indicated
System action:

function. The xxxxxxxx value is the return code PLAN failure while Function,
The Managed Systems Manager stops processing. The Managed Systems Manager was unable to perform
a DROP SQL ACCESS PLAN request in order to perform
User response:
the indicated function. The xxxxxxxx value is the return
System action:
User response:

Chapter 16. KCPPR messages
This information lists all the KCPPR messages that are produced when you add, delete, or update a
CICSplex classification rule or agent preferences.
If there are any incorrect values in the input fields, the messages attempt to provide enough information
to correct the error. If errors are found, no rules or preferences are updated.
KCPPR0000E The first character in fieldname Explanation
cannot be a number.
You failed to supply a value for the identified field
name when defining a new CICSplex classification
Explanation rule.
You entered a number as the first character of field
name. The first character should not be a number. System action
This error message is displayed on the Add a
System action new CICSplex Classification Rule panel within the
The error message is displayed on the Add a new OMEGAMON enhanced 3270 user interface where you
CICSplex Classification Rule panel of the OMEGAMON are entering your input for the CICSplex classification
enhanced 3270 user interface where you are entering rule.
input for the classification rule.
User response
User response Supply a value for fieldname.
Correct the input in the field with a valid entry. KCPPR0003E Internal error. Required variables
KCPPR0001E There are invalid characters in the are missing.
fieldname value: fieldvalue
Explanation
Explanation The processing for adding a new CICSplex
You entered invalid characters for the CICSplex rule classification rule failed because the required internal
field identified by the fieldname value. The valid variables were not available. This might indicate a
characters are alphanumeric, the asterisk wildcard problem with IBM Z OMEGAMON for CICS or might
character (*) and the national characters #, $, and @. occur with the path navigation for defining a CICSplex
The field for the CICSplex name itself has a further classification rule, rather than selecting a row in the
restriction that the asterisk wildcard character (*) summary panel for CICSplex classification rules.
cannot not be used.
System action
System action This error message is displayed on the Add a
This error message is displayed on the Add a new CICSplex Classification Rule panel within the
new CICSplex Classification Rule panel within the OMEGAMON enhanced 3270 user interface where you
OMEGAMON enhanced 3270 user interface where you are entering your input for the CICSplex classification
are entering your input for the CICSplex classification rule.
rule.
User response
User response Navigate to the panel for defining a new classification
Correct the input in the field with valid entries. rule, or contact IBM Software Support if the message
is encountered after you have finished the proper
KCPPR0002E A value for the fieldname is navigation.
required, but is missing.
KCPPR0004E The CICSplex record key: seqnum
is not valid.

Explanation KCPPR0007E The first character in the CICSplex
Name cannot be a hash sign (#).
The processing for adding or deleting a new CICSplex
classification rule failed because the internal field
in the CICSplex classification rule was invalid. The Explanation
internal field has the value specified by the seqnum You entered a hash sign (#) as the first character of the
value. CICSplex name. The first character cannot be a hash
sign (#).
System action
The error message is displayed on the Delete System action
this CICSplex Classification Rule panel within the The error message is displayed on the Add a new
OMEGAMON enhanced 3270 user interface where you CICSplex Classification Rule or the Add Preferences
are verifying a classification rule deletion or entering for a CICSplex Agent panel of the OMEGAMON
input for a new classification rule in the Add a new enhanced 3270 user interface where you are entering
CICSplex Classification Rule panel. the CICSplex name for the classification rule or
preference.
User response
KCPPR0005E The default OMEGPLEX rule Correct the CICSplex name. The name can include
cannot be deleted. characters A-Z, 0-9, @, # or $, but cannot start with
a number or the hash sign (#).
Explanation KCPPR0009E The default OMEGPLEX rule
cannot be updated.
You attempted to delete the IBM-supplied OMEGPLEX
CICSplex classification rule. Explanation:
You attempted to update the default OMEGPLEX rule,
which cannot be updated.
System action
System action:
The error message is displayed on the Delete
this CICSplex Classification Rule panel within the
OMEGAMON enhanced 3270 user interface where you User response:
are verifying a classification rule deletion. Create a new set of CICSplex classification rules, using
a different name.
User response KCPPR0010E The CICSplex agent timeout value:
nn, must be between 0 and 30
Do not delete the default OMEGPLEX classification
minutes or NO.
rule.
Explanation:
KCPPR0006E Reply Y to confirm delete. A number greater than 30 or a non-numeric value
besides NO was entered as the CICSplex agent timeout
Explanation value.
You entered an invalid character on the panel where System action:
a classification rule deletion is being verified. The only The command is not processed.
accepted value is Y (for YES).
User response:
Enter the correct value.
System action
KCPPR0011E The CICSplex agent XM number
The error message is displayed on the Delete value: nn must be either * or a
this CICSplex Classification Rule panel within the number between 00 and 15.
OMEGAMON enhanced 3270 user interface where you
Explanation:
are verifying your input in the field.
A value other than * or the numbers 0 through 15 was
entered as the agent XM number.
User response
System action:
Reply Y to delete the rule or exit the deletion panel. The command is not processed.

User response: KCPPR1302E The parameter pppp provided with
Enter the correct value. the PLXU command is invalid.
KCPPR0012E There are invalid characters in the
fieldname, value: vvvvvvvv. Explanation
Explanation: The CICSplex Rules Update function detected an
An invalid value was entered for fieldname (one invalid parameter with the PLXU command. The pppp
of: CICSplex name, agent SMF identifier, agent XM value is not a valid parameter.
number, agent timeout value).
System action: System action
The command is discarded; system processing
User response: continues.
Enter an appropriate value.
KCPPR0015E The default *DFLT preferences User response
cannot be deleted.
Explanation:
KCPPR1303E The command did not include a
You attempted to delete the default agent preferences
value for the ffffffffffff .
named *DFLT.
System action: Explanation
No value for ffffffffffff was provided with the PLXU
User response:
command, where ffffffffffff is one of: Job Name,
None.
SYSplex Name, SMF Identifier, VTAM Applid, VTAM
KCPPR1300E The cccc command received is GApplid or XCF Group.
invalid.
System action
Explanation
The CICSplex Rules Update function received an continues.
unrecognized command.
User response
System action
None.
KCPPR1304E The DELETE command did not
continues.
include a valid SEQNUM.
User response Explanation:

You attempted to delete a CICSplex rule, but the
If the problem persists, contact IBM Software Support. internal sequence number (the record key) is not
included as input to the command.
KCPPR1301E The PLXU command did not
contain any valid parameters. System action:
This message is displayed in the Delete this CICSplex
Explanation Classification Rule panel at the point within the
OMEGAMON enhanced 3270 user interface where you
The CICSplex Rules Update function did not detect any are attempting to delete a classification rule. The
valid parameters with the PLXU command. command is rejected.
User response:
The command is discarded; system processing KCPPR1305E The SEQNUM ssss for the DELETE
continues. command is invalid.
User response
Chapter 16. KCPPR messages 177

The processing for adding or deleting a new CICSplex
classification rule failed because the internal field in
the CICSplex classification rule is invalid. The internal KCPPR1310E The SEQNUM ssss for the
field has the value specified by the ssss value. command is invalid.
Note: This is the same as message “KCPPR0004E ” on
page 175. KCPPR0004E is issued by the EXEC in the Explanation
e3270ui, whereas KCPPR1305E is issued by the agent.
The sequence number designated by the ssss value
If for some reason KCPPR0004E doesn't show, then
that is provided with the ADD command is not
the code in the agent itself will reject the command.
numeric, or more than four digits.
System action:
The error message is displayed on the Delete this
System action
CICSplex Classification Rule panel at the point within
the OMEGAMON enhanced 3270 user interface where The command is discarded; system processing
you are deleting a classification rule or entering input continues.
for a new classification rule in the Add a New CICSplex
Classification Rule panel. User response
User response:
KCPPR1311E The command did not include valid
KCPPR1306E The default OMEGPLEX rule
information beyond the SEQNUM.
cannot be deleted.
You attempted to delete the IBM-supplied OMEGPLEX The CICSplex Rules Update function did not detect
CICSplex classification rule. any valid parameters after the sequence number. All of
the following are required: CICSplex Name, Job Name,
Note: This is the same as message “KCPPR0004E ”
SYSplex Name, SMF Identifier, VTAM Applid, VTAM
on page 175. KCPPR0005E is issued by the EXEC in
Gapplid or XCF group.
the e3270ui. KCPPR1306E is issued by the agent. If
for some reason KCPPR0005E doesn't show, then the
code in the agent itself will reject the command. System action
System action: The command is discarded; system processing
The error message is displayed on the Delete This continues.
CICSplex Classification Rule panel at the point within
the OMEGAMON enhanced 3270 user interface where User response
you are attempting to delete a classification rule.
User response:
Do not delete the default OMEGPLEX classification KCPPR1312E The first character in the CICSplex
rule. name can only be A through Z, @,
# or $.
KCPPR1307E The number of columns to be
inserted in the PCLASS table is
incorrect. Explanation
The CICSplex Rules Update function detected an
Explanation invalid first character as the in the CICSplex name.
The CICSplex Rules Update function detected a
discrepancy between the number of columns expected System action
in the PCLASS table.
The command is not processed; system processing
continues.
System action
The command is discarded; system processing User response
continues.
None.

KCPPR1313E The fieldname must have a length through Z, @, #, $, * or 0 through
of up to 8 characters and contain 9.
only A through Z, @, #, $ or 0
through 9. Explanation
The parameter fieldname is either too long or contains
Explanation invalid characters. The fieldname value is one of: Job
The CICSplex Rules Update function found invalid Name, SYSplex Name, SMF Identifier, VTAM Applid,
characters in the field named fieldname (one of: VTAM GApplid or XCF group. 1-n will be 1-8 for all
CICSplex name, jobname, sysplex name, VTAM applid, these fields except for the SMF Identifier, which can
generic VTAM applid, or XCF group). Note that an consist of 1-4 characters.
asterisk (*) cannot be part of the CICSplex name.
System action
System action The command is not processed; system processing
The command is not processed; system processing continues.
continues.
User response
User response Enter the correct fieldname value.
Enter the correct fieldname value.
KCPPR1323E The CICSplex Rules Update
KCPPR1314E The fieldname must have a function received null data when
numeric value. fetching table tttttttt.
Explanation:
fieldname (one of Agent XM Number or Agent Timeout) Explanation
was found to have a non-numeric value. The table named in the tttttttt value had no data.
System action:
The command is not processed. System action
User response: The command is not processed; system processing
For Agent XM Number, specify either * or a number continues.
between 0 and 15. For Agent Timeout, specify either a
number between 0 and 30, or NO.
User response
KCPPR1320E The first character in the fieldname
can only be the A through Z, @, # None.
or $, or * characters. KCPPR1324E The CICSplex Rules Update
function was unable to acquire
Explanation storage for resequencing, length
nnnnnnnn.
The CICSplex Rules Update function detected an
invalid character in the field depicted by the fieldname
value. The value field can be the Job Name, SYSplex Explanation
Name, SMF Identifier, VTAM Applid, VTAM GApplid, or No storage is available for the CICSplex Rules Update
XCF group. function to resequence the PCLASS table.

The command is not processed; system processing The command is not processed; system processing
continues. continues.

Enter the correct fieldname value. If other agent functions issue messages regarding
KCPPR1321E The fieldname may be 1 through n storage unavailability, it will be necessary to recycle
characters long and contain only A the address space.

KCPPR1330E The CICSplex Rules Update System action
function experienced a CONNECT
failure while reading the PCLASS The command is discarded; system processing
table to add a rule, RC=xxxxxxxx. continues.

The CICSplex Rules Update function was unable to Contact IBM Software Support.
connect to the hub server and perform an SQL create KCPPR1333E The CICSplex Rules Update
path request in order to add a CICSplex classification function experienced an OPEN SQL
rule. The xxxxxxxx value is the return code generated REQUEST failure while reading
by the SQL request. the PCLASS table to add a rule,
RC=xxxxxxxx.
System action
The command is discarded; system processing Explanation
continues. The CICSplex Rules Update function was unable to
perform an open SQL request in order to read the
User response PCLASS table. The xxxxxxxx value is the return code
function experienced a CREATE
SQL ACCESS PLAN failure while The command is discarded; system processing
reading the PCLASS table to add continues.
a rule, RC=xxxxxxxx.
User response
The CICSplex Rules Update function was unable to KCPPR1334E The CICSplex Rules Update
perform a create SQL access plan request in order function experienced a FETCH
to read the PCLASS table. The xxxxxxxx value is the SQL DATA failure while reading
return code generated by the SQL request. the PCLASS table to add a rule,
RC=xxxxxxxx.
System action Explanation:
The command is discarded; system processing The CICSplex Rules Update function was unable to
continues. perform a fetch SQL request in order to read the
PCLASS table. The xxxxxxxx value is the return code
User response
KCPPR1332E The CICSplex Rules Update The command is discarded; system processing
function experienced a CREATE continues.
reading the PCLASS table to add
a rule, RC=xxxxxxxx .
User response
Explanation KCPPR1335E The CICSplex Rules Update
The CICSplex Rules Update function was unable to function experienced a CLOSE SQL
perform a create SQL request in order to read the REQUEST failure while reading
PCLASS table. The xxxxxxxx value is the return code the PCLASS table to add a rule,

The CICSplex Rules Update function was unable to failure while inserting the PCLASS
perform a close SQL request in order to read the table row, RC=xxxxxxxx .
PCLASS table. The xxxxxxxx value is the return code
Explanation
System action The CICSplex Rules Update function was unable to
connect to the hub server and perform an SQL create
The command is discarded; system processing path request in order to add a CICSplex classification
continues. rule. The xxxxxxxx value is the return code generated
by the SQL request.
User response
function experienced a DROP SQL continues.
REQUEST failure while reading
the PCLASS table to add a rule, User response
RC=xxxxxxxx.
The CICSplex Rules Update function was unable to SQL ACCESS PLAN failure while
perform a drop SQL request in order to read the inserting a row in the PCLASS
PCLASS table. The xxxxxxxx value is the return code table, RC=xxxxxxxx.
Explanation
System action
The CICSplex Rules Update function was unable to
The command is discarded; system processing perform a create SQL access plan request in order to
continues. add a CICSplex classification rule. The xxxxxxxx value
User response
function experienced a DROP continues.
SQL ACCESS PLAN failure while
reading the PCLASS table to add User response
a rule, RC=xxxxxxxx.
The CICSplex Rules Update function was unable to SQL REQUEST failure while
perform a drop SQL access plan request in order to inserting a row in the PCLASS
read the PCLASS table. The xxxxxxxx value is the table, RC=xxxxxxxx.
Explanation
System action
The command is discarded; system processing perform a create SQL request in order to add a
continues. CICSplex classification rule. The xxxxxxxx value is the
User response

continues. perform a drop SQL request in order to add a CICSplex
classification rule. The xxxxxxxx value is the return
User response code generated by the SQL request.

System action
function experienced an OPEN SQL continues.
REQUEST failure while inserting
a row in the PCLASS table,
Explanation
The CICSplex Rules Update function was unable to function experienced a DROP
perform an open SQL request in order to add a SQL ACCESS PLAN failure while
CICSplex classification rule. The xxxxxxxx value is the inserting a row in the PCLASS
return code generated by the SQL request. table, RC=xxxxxxxx.

continues. perform a drop SQL access plan request in order to
add a CICSplex classification rule. The xxxxxxxx value
User response is the return code generated by the SQL request.

System action
function experienced a CLOSE SQL continues.
RC=xxxxxxxx . User response
Explanation
The CICSplex Rules Update function was unable to function experienced a CONNECT
perform a close SQL request in order to add a failure while reading the PCLASS
CICSplex classification rule. The xxxxxxxx value is the row to be deleted, RC=xxxxxxxx.
Explanation
System action
The command is discarded; system processing connect to the hub server and perform an SQL create
continues. path request in order to read a CICSplex classification
rule to be deleted. The xxxxxxxx value is the return

System action

KCPPR1351E The CICSplex Rules Update User response
SQL ACCESS PLAN failure while Contact IBM Software Support.
reading the PCLASS row to be KCPPR1354E The CICSplex Rules Update
deleted, RC=xxxxxxxx. function experienced a FETCH
Explanation: SQL DATA failure while reading
The CICSplex Rules Update function could not create the PCLASS row to be deleted,
an SQL access plan so it could delete a CICSplex RC=xxxxxxxx.
classification rule. The xxxxxxxx value is the return
code generated by the SQL request. Explanation
System action: The CICSplex Rules Update function was unable
The command is discarded; system processing to perform a fetch SQL request in order to read
continues. a CICSplex classification rule to be deleted. The
User response: xxxxxxxx value is the return code generated by the SQL
Contact IBM Software Support. request.

System action
SQL REQUEST failure while The command is discarded; system processing
reading the PCLASS row to be continues.
deleted, RC=xxxxxxxx.
User response
Explanation
The CICSplex Rules Update function was unable
to perform a create SQL request in order to read KCPPR1355E The CICSplex Rules Update
a CICSplex classification rule to be deleted. The function experienced a CLOSE SQL
xxxxxxxx value is the return code generated by the SQL REQUEST failure while reading
request. the PCLASS row to be deleted,
RC=xxxxxxxx.
System action
Explanation
continues. The CICSplex Rules Update function was unable
to perform a close SQL request in order to read
a CICSplex classification rule to be deleted. The
User response xxxxxxxx value is the return code generated by the SQL
Contact IBM Software Support. request.

function experienced an OPEN SQL
System action
REQUEST failure while reading The command is discarded; system processing
the PCLASS row to be deleted, continues.
RC=xxxxxxxx.
User response
Explanation
The CICSplex Rules Update function was unable
to perform an open SQL request in order to read KCPPR1356E The CICSplex Rules Update
a CICSplex classification rule to be deleted. The function experienced a DROP SQL
xxxxxxxx value is the return code generated by the SQL REQUEST failure while reading
request. the PCLASS row to be deleted,
RC=xxxxxxxx.
System action
continues.

The CICSplex Rules Update function was unable Contact IBM Software Support.
to perform a drop SQL request in order to read
a CICSplex classification rule to be deleted. The
request.
deleting a PCLASS table row,
RC=xxxxxxxx.
System action
continues.
perform a create SQL request in order to delete a
User response CICSplex classification rule. The xxxxxxxx value is the
Contact IBM Software Support. return code generated by the SQL request.

System action
function experienced a DROP
reading the PCLASS row to be continues.
deleted, RC=xxxxxxxx.
User response
Explanation
perform a drop access plan SQL request in order to KCPPR1363E The CICSplex Rules Update
read a CICSplex classification rule to be deleted. The function experienced an OPEN SQL
xxxxxxxx value is the return code generated by the SQL REQUEST failure while deleting a
request. PCLASS table row, RC=xxxxxxxx.

continues. perform an open SQL request in order to delete a
CICSplex classification rule. The xxxxxxxx value is the
User response
deleting a PCLASS table row, User response
RC=xxxxxxxx.
The CICSplex Rules Update function was unable to function experienced a CLOSE SQL
perform a create access plan SQL request in order REQUEST failure while deleting a
to delete a CICSplex classification rule. The xxxxxxxx PCLASS table row, RC=xxxxxxxx.
value is the return code generated by the SQL request.
Explanation
The command is discarded; system processing perform a close SQL request in order to delete a
continues. CICSplex classification rule. The xxxxxxxx value is the

continues. perform a create access plan SQL request in order to
retrieve the INTERVAL table row. The xxxxxxxx value is
User response the return code generated by the SQL request.

System action
REQUEST failure while deleting a
PCLASS table row, RC=xxxxxxxx.
User response
perform a drop SQL request in order to delete a function experienced a CREATE
CICSplex classification rule. The xxxxxxxx value is the SQL REQUEST failure while
return code generated by the SQL request. retrieving the INTERVAL row,
RC=xxxxxxxx.
System action
Explanation
perform a create SQL request in order to retrieve the
User response INTERVAL table row. The xxxxxxxx value is the return
function experienced a DROP The command is discarded; system processing
SQL ACCESS PLAN failure while continues.
deleting a PCLASS table row,
RC=xxxxxxxx.
User response
perform a drop access plan SQL request in order to function experienced an OPEN SQL
delete a CICSplex classification rule. The xxxxxxxx REQUEST failure while retrieving
value is the return code generated by the SQL request. the INTERVAL row, RC=xxxxxxxx.

continues. perform an open SQL request in order to retrieve the
INTERVAL table row. The xxxxxxxx value is the return

System action
retrieving the INTERVAL row,

KCPPR1374E The CICSplex Rules Update User response
function experienced a FETCH SQL
DATA failure while retrieving the Contact IBM Software Support.
INTERVAL row, RC=xxxxxxxx. KCPPR1377E The CICSplex Rules Update
Explanation SQL ACCESS PLAN failure while
retrieving the INTERVAL row,
The CICSplex Rules Update function was unable to RC=xxxxxxxx.
perform a fetch SQL request in order to retrieve the
System action perform a drop SQL access plan request in order to
retrieve the INTERVAL table row. The xxxxxxxx value is
The command is discarded; system processing the return code generated by the SQL request.
continues.
System action
User response
Contact IBM Software Support. continues.
function experienced a CLOSE SQL User response
the INTERVAL row, RC=xxxxxxxx. Contact IBM Software Support.
Explanation function experienced a CREATE
The CICSplex Rules Update function was unable to deleting the INTERVAL row,
perform a fetch SQL request in order to retrieve the RC=xxxxxxxx.
Explanation
perform a create access plan SQL request in order to
The command is discarded; system processing delete the INTERVAL table row. The xxxxxxxx value is
continues. the return code generated by the SQL request.

Contact IBM Software Support. The command is discarded; system processing
KCPPR1376E The CICSplex Rules Update continues.
function experienced a DROP SQL
REQUEST failure while retrieving User response
the INTERVAL row, RC=xxxxxxxx.

The CICSplex Rules Update function was unable to SQL REQUEST failure while
perform a drop SQL request in order to retrieve the deleting the INTERVAL row,
INTERVAL table row. The xxxxxxxx value is the return RC=xxxxxxxx.
Explanation
System action
The command is discarded; system processing perform a create SQL request in order to delete the
continues.

INTERVAL table row. The xxxxxxxx value is the return Explanation
perform a drop SQL request in order to delete the
System action INTERVAL table row. The xxxxxxxx value is the return
The command is discarded; system processing code generated by the SQL request.
continues.
System action
User response The command is discarded; system processing
Contact IBM Software Support. continues.

User response
REQUEST failure while deleting Contact IBM Software Support.
Explanation SQL ACCESS PLAN failure while
The CICSplex Rules Update function was unable to deleting the INTERVAL row,
perform an open SQL request in order to delete the RC=xxxxxxxx.
System action perform a drop access plan SQL request in order to
The command is discarded; system processing delete the INTERVAL table row. The xxxxxxxx value is
continues. the return code generated by the SQL request.

Contact IBM Software Support. The command is discarded; system processing
continues.
function experienced a CLOSE SQL
User response
the INTERVAL row, RC=xxxxxxxx. Contact IBM Software Support.
KCPPR1390I The rule for CICSplex cccccccc was
Explanation successfully deleted.
perform a close SQL request in order to delete the Explanation
code generated by the SQL request. A request to delete a CICSplex classification rule
was fulfilled. The cccccccc value is the name of the
CICSplex whose rule was deleted.
System action
The command is discarded; system processing System action
continues.
User response
User response
None.
function experienced a DROP SQL KCPPR1391I The rule for CICSplex cccccccc was
REQUEST failure while deleting successfully added.

A request to add a rule for CICSplex named in the An error condition was detected while reading the
value cccccccc was fulfilled. PCLASS table.

System processing continues. The command is discarded; system processing
continues.
User response
User response
None.
None.
KCPPR1392E The request to delete the
rule for CICSplex cccccccc KCPPR1395E The delete command was
encountered SQL error xxxxxxxx unsuccessful due to unexpected
while processing the rrrrrrrrrrrrrrrr mismatched data detailed in
function. RKLVLOG.
While processing a request to delete a classification The CICSplex Rules Update function encountered
rule for the CICSplex named in the cccccccc value , mismatched data in the rule to be deleted, when
the CICSplex Rules Update function encountered an compared to the rule in the PCLASS table. This
SQL error, with the return code xxxxxxxx. The function message is displayed on the OMEGAMON enhanced
being performed is described by the rrrrrrrrrrrrrrrr 3270 user interface, and further data about the
value. mismatched data is displayed in the agent's RKLVLOG,
and in messages KCPPR1396I and KCPPR1397I.
System action
System action
continues. The command is discarded; system processing
continues.
User response
User response
None.
None.
KCPPR1393I The rule with SEQNUM ssss for
CICSplex cccccccc does not exist KCPPR1396I The existing values are CICSplex
and cannot be deleted. name=pppppppp, Job Name=jjjjjjjj,
SYSplex Name=ssssssss,
Explanation SMF Identifier=ffff, VTAM
Applid=aaaaaaaa, VTAM
The CICSplex Rules Update function attempted to GApplid=gggggggg, XCF
delete the PCLASS table row for the CICSplex with Group=xxxxxxxx.
name cccccccc and sequence number ssss, but the row
does not exist.
Explanation
System action The contents of the rule depicted by the values in
the PCLASS table whose deletion was attempted are
The command is discarded; system processing described by this message; it is displayed in the
continues. agent's RKLVLOG and provides additional information
regarding the cause of error message KCPPR1395E.
User response
System action
None.
KCPPR1394E The FETCH request for the PCLASS
continues.
table resulted in null data.

User response Collect the RKLVLOG from the OMEGAMON for CICS on
z/OS agent, and contact IBM Software Support.
None.
KCPPR1397I The delete values are function experienced a CREATE
CICSplex name=pppppppp, SQL ACCESS PLAN failure while
Job Name=jjjjjjjj, SYSplex inserting the INTERVAL row,
Name=ssssssss, SMF Identifierffff, RC=xxxxxxxx .
VTAM Applid=aaaaaaaa,
VTAM GApplid=gggggggg, XCF
Group=xxxxxxxx. Explanation
Explanation perform a create access plan SQL request in order to
insert the INTERVAL table row. The xxxxxxxx value is
The contents of the command to delete a CICSplex the return code generated by the SQL request.
rule are described by this message. This is displayed in
the agent's RKLVLOG to provide additional information
regarding the cause of error message KCPPR1395E. System action
System action continues.

continues. User response
User response KCPPR1402E The CICSplex Rules Update
None. function experienced a CREATE
KCPPR1398I The rule for CICSplex cccccccc was inserting the INTERVAL row,
successfully updated. RC=xxxxxxxx .
Explanation:
The monitoring environment for the CICSplex named Explanation
cccccccc was updated correctly.
User response: perform a create SQL request in order to insert the
None; this is a status message only. INTERVAL table row. The xxxxxxxx value is the return
KCPPR1399I The agent preferences code generated by the SQL request.
for CICSplex cccccccc
were successfully added|deleted| System action
updated.
Explanation: continues.
The preferences for the agent monitoring the CICSplex
named cccccccc were successfully added, deleted, or
updated.
User response
User response:
None; this is a status message only. KCPPR1403E The CICSplex Rules Update
KCPPR1400E Internal error. The value: xxxx in function experienced an OPEN SQL
the Origin field of the preferences REQUEST failure while inserting
is invalid. the INTERVAL row, RC=xxxxxxxx .
Explanation:
Internal error: Origen should always have the value
Explanation
OMEG or CPSM, but it is neither. The CICSplex Rules Update function was unable to
System action: perform an open SQL request in order to insert the
The command is not executed. INTERVAL table row. The xxxxxxxx value is the return
User response:

continues. perform a drop access plan SQL request in order to
insert the INTERVAL table row. The xxxxxxxx value is
User response the return code generated by the SQL request.

System action
function experienced a CLOSE SQL continues.
the INTERVAL row, RC=xxxxxxxx .
User response
perform a close SQL request in order to insert the function experienced a CONNECT
INTERVAL table row. The xxxxxxxx value is the return failure while counting rows in the
code generated by the SQL request. PCLASS table, RC=xxxxxxxx .

continues. connect to the hub and perform an SQL create path
request in order to count the rows in the PCLASS table.
User response The xxxxxxxx value is the return code generated by the
SQL request.
function experienced a DROP SQL The command is discarded; system processing
REQUEST failure while inserting continues.
the INTERVAL row, RC=xxxxxxxx .
User response
Explanation
perform a drop SQL request in order to insert the KCPPR1411E The CICSplex Rules Update
INTERVAL table row. The xxxxxxxx value is the return function experienced a CREATE
code generated by the SQL request. SQL ACCESS PLAN failure while
counting rows in the PCLASS
System action table, RC=xxxxxxxx .

Explanation
continues.
User response perform an SQL create access plan request in order
to count the rows in the PCLASS table. The xxxxxxxx
Contact IBM Software Support. value is the return code generated by the SQL request.
function experienced a DROP System action
inserting the INTERVAL row, continues.
RC=xxxxxxxx .
User response

counting rows in the PCLASS continues.
table, RC=xxxxxxxx .
User response
perform an SQL create request in order to count the function experienced a DROP SQL
rows in the PCLASS table. The xxxxxxxx value is the REQUEST failure while counting
return code generated by the SQL request. rows in the PCLASS table,
RC=xxxxxxxx .
System action
perform a drop SQL request in order to count the rows
User response in the PCLASS table. The xxxxxxxx value is the return
REQUEST failure while counting The command is discarded; system processing
rows in the PCLASS table, continues.
RC=xxxxxxxx .
User response
perform an open SQL request in order to count the function experienced a DROP
rows in the PCLASS table. The xxxxxxxx value is the SQL ACCESS PLAN failure while
return code generated by the SQL request. counting rows in the PCLASS
System action
perform a drop access plan SQL request in order to
User response count the rows in the PCLASS table. The xxxxxxxx
function experienced a FETCH
SQL DATA failure while counting The command is discarded; system processing
rows in the PCLASS table, continues.
RC=xxxxxxxx .
User response
perform a fetch SQL plan request in order to count the function experienced a CREATE
rows in the PCLASS table. The xxxxxxxx value is the SQL ACCESS PLAN failure while
return code generated by the SQL request. reading all rows from the PCLASS

The CICSplex Rules Update function was unable to REQUEST failure while reading
perform a create access plan SQL request in order to all rows from the PCLASS table,
read all rows in the PCLASS table. The xxxxxxxx value RC=xxxxxxxx .
Explanation
System action
The command is discarded; system processing perform a drop SQL request in order to read all rows
continues. in the PCLASS table. The xxxxxxxx value is the return
User response
reading all rows from the PCLASS User response
perform a create SQL request in order to read all rows reading all rows from the PCLASS
in the PCLASS table. The xxxxxxxx value is the return table, RC=xxxxxxxx .
Explanation
System action
The command is discarded; system processing perform a drop access plan SQL request in order to
continues. read all rows in the PCLASS table. The xxxxxxxx value
User response
REQUEST failure while reading
all rows from the PCLASS table, User response
RC=xxxxxxxx .
perform an open SQL request in order to read all rows deleting all rows from the PCLASS
in the PCLASS table. The xxxxxxxx value is the return table, RC=xxxxxxxx .
Explanation
System action
The command is discarded; system processing perform a create access plan SQL request in order
continues. to delete all rows in the PCLASS table. The xxxxxxxx
User response

continues. perform a drop SQL request in order to delete all rows
in the PCLASS table. The xxxxxxxx value is the return

System action
deleting all rows from the PCLASS
table, RC=xxxxxxxx . User response
Explanation
The CICSplex Rules Update function was unable to function experienced a DROP
perform a create SQL request in order to delete all SQL ACCESS PLAN failure while
rows in the PCLASS table. The xxxxxxxx value is the deleting all rows from the PCLASS
return code generated by the SQL request. table, RC=xxxxxxxx .

continues. perform a drop access plan SQL request in order to
delete all rows in the PCLASS table. The xxxxxxxx
User response value is the return code generated by the SQL request.

System action
all rows from the PCLAS S table,
Explanation
The CICSplex Rules Update function was unable to function experienced a CREATE
perform an open SQL request in order to delete all SQL ACCESS PLAN failure while
rows in the PCLASS table. The xxxxxxxx value is the resequencing the PCLASS table,
return code generated by the SQL request. RC=xxxxxxxx .

continues. perform a create access plan SQL request in order to
resequence all rows in the PCLASS table. The xxxxxxxx

System action
all rows from the PCLASS table,

resequencing the PCLASS table, continues.
RC=xxxxxxxx .
User response
perform a create SQL request in order to resequence function experienced a DROP
all rows in the PCLASS table. The xxxxxxxx value is the SQL REQUEST failure while
return code generated by the SQL request. resequencing the PCLASS table,
RC=xxxxxxxx .
System action
perform a drop SQL request in order to resequence all
User response rows in the PCLASS table. The xxxxxxxx value is the
function experienced an OPEN
RC=xxxxxxxx .
User response
perform an open SQL request in order to resequence function experienced a DROP
all rows in the PCLASS table. The xxxxxxxx value is the SQL ACCESS PLAN failure while
return code generated by the SQL request. resequencing the PCLASS table,
RC=xxxxxxxx .
System action
perform a drop access plan SQL request in order to
User response resequence all rows in the PCLASS table. The xxxxxxxx
function experienced a CLOSE
RC=xxxxxxxx .
User response
perform a close SQL request in order to resequence all function experienced a CONNECT
rows in the PCLASS table. The xxxxxxxx value is the failure while updating the PCLASS
return code generated by the SQL request. Table, RC=xxxxxxxx.
Explanation:

The CICSplex Rules Update function could not connect The command is discarded; system processing
to the hub server and create an SQL path request so it continues.
could add a CICSplex classification rule to the PCLASS
User response:
by the SQL request.
System action:
function experienced a CLOSE
continues.
updating a CICSplex member row,
User response: RC=xxxxxxxx.
Explanation:
KCPPR1471E The CICSplex Rules Update The CICSplex Rules Update function could not close an
function experienced a CREATE SQL request after updating a CICSplex member row.
SQL ACCESS PLAN failure while The xxxxxxxx value is the return code generated by the
updating a CICSplex member row, SQL request.
RC=xxxxxxxx.
System action:
Explanation: The command is discarded; system processing
The CICSplex Rules Update function could not create continues.
an SQL access plan so it could update a CICSplex
User response:
member row. The xxxxxxxx value is the return code
System action:
continues.
Explanation:
KCPPR1472E The CICSplex Rules Update The CICSplex Rules Update function could not drop an
function experienced an CREATE SQL request after updating a CICSplex member row.
SQL REQUEST failure while The xxxxxxxx value is the return code generated by the
updating a CICSplex member row, SQL request.
RC=xxxxxxxx .
System action:
an SQL request so it could update a CICSplex member
User response:
row. The xxxxxxxx value is the return code generated
by the SQL request.
System action:
continues.
Explanation:
KCPPR1473E The CICSplex Rules Update The CICSplex Rules Update function could not drop
function experienced an OPEN an SQL access plan request after updating a CICSplex
SQL REQUEST failure while member row. The xxxxxxxx value is the return code
updating a CICSplex member row, generated by the SQL request.
RC=xxxxxxxx.
System action:
The CICSplex Rules Update function could not open continues.
an SQL request so it could update a CICSplex member
User response:
row. The xxxxxxxx value is the return code generated
by the SQL request.
System action:

failure while adding CICSplex table. The xxxxxxxx value is the return code generated
agent preferences, RC=xxxxxxxx. by the SQL request.
Explanation: System action:
The CICSplex Rules Update function could not connect The command is discarded; system processing
to the hub server and create an SQL path request so it continues.
could add CICSplex agent preferences to the PCLASS
User response:
by the SQL request.
System action:
function experienced a CLOSE SQL
continues.
a row in the PAGPREFS table,
Explanation:
KCPPR1481E The CICSplex Rules Update The CICSplex Rules Update function could not close
function experienced a CREATE an SQL request after inserting a row in the PAGPREFS
SQL ACCESS PLAN failure while table. The xxxxxxxx value is the return code generated
inserting a row in the PAGPREFS by the SQL request.
table, RC=xxxxxxxx.
System action:
an SQL access plan so it could update a row in the
User response:
System action:
continues.
a row in the PAGPREFS table,
Explanation:
KCPPR1482E The CICSplex Rules Update The CICSplex Rules Update function could not drop
function experienced a CREATE an SQL request after inserting a row in the PAGPREFS
SQL REQUEST failure while table. The xxxxxxxx value is the return code generated
inserting a row in the PAGPREFS by the SQL request.
System action:
an SQL request so it could insert a row in the
User response:
System action:
continues.
inserting a row in the PAGPREFS
User response: table, RC=xxxxxxxx.
Explanation:
KCPPR1483E The CICSplex Rules Update The CICSplex Rules Update function could not drop an
function experienced an OPEN SQL SQL access plan request after inserting a row in the
REQUEST failure while inserting PAGPREFS table. The xxxxxxxx value is the return code
a row in the PAGPREFS table, generated by the SQL request.
RC=xxxxxxxx.
System action:
The CICSplex Rules Update function could not open an continues.
SQL request so it could insert a row in the PAGPREFS
User response:

Contact IBM Software Support. The CICSplex Rules Update function could not create
an SQL request so it could delete a row from the
KCPPR1489E The add command for the
cccccccc CICSplex preferences
was unsuccessful, because the
record already exists. System action:
Explanation:
continues.
You attempted to add preferences for CICSplex named
cccccccc, but the preferences already exist. User response:
System action:
The command is discarded; system processing KCPPR1493E The CICSplex Rules Update
continues. function experienced an OPEN
User response:
deleting a PAGPREFS table row,
Either update the existing CICSplex preferences or add
RC=xxxxxxxx.
a new one, using a different name.
Explanation:
The CICSplex Rules Update function could not open
an SQL request so it could delete a row from the
failure while deleting a PAGPREFS
table row, RC=xxxxxxxx.
Explanation:
System action:
The CICSplex Rules Update function could not connect
to the hub server and create an SQL path request so
continues.
it could delete a row from the PAGPREFS table. The
xxxxxxxx value is the return code generated by the SQL User response:
request. Contact IBM Software Support.
System action: KCPPR1495E The CICSplex Rules Update
The command is discarded; system processing function experienced a CLOSE
continues. SQL REQUEST failure while
User response:
RC=xxxxxxxx.
Explanation:
The CICSplex Rules Update function could not close an
SQL request after deleting a row from the PAGPREFS
by the SQL request.
RC=xxxxxxxx.
System action:
Explanation:
The CICSplex Rules Update function could not create
continues.
an SQL access plan so it could delete a row from the
PAGPREFS table. The xxxxxxxx value is the return code User response:
generated by the SQL request. Contact IBM Software Support.
System action: KCPPR1496E The CICSplex Rules Update
The command is discarded; system processing function experienced a DROP
continues. SQL REQUEST failure while
User response:
RC=xxxxxxxx.
Explanation:
The CICSplex Rules Update function could not drop an
SQL request after deleting a row from the PAGPREFS
by the SQL request.
RC=xxxxxxxx .
System action:
Explanation:

The command is discarded; system processing SQL REQUEST failure while
continues. updating CICSplex agent
preferences, RC=xxxxxxxx .
User response:
Contact IBM Software Support. Explanation:
an SQL request so it could update CICSplex agent
preferences. The xxxxxxxx value is the return code
RC=xxxxxxxx. System action:
Explanation:
continues.
The CICSplex Rules Update function could not drop an
SQL access plan request after deleting a row from the User response:
PAGPREFS table. The xxxxxxxx value is the return code Contact IBM Software Support.
System action: function experienced an OPEN SQL
The command is discarded; system processing REQUEST failure while updating
continues. CICSplex agent preferences,
RC=xxxxxxxx.
User response:
The CICSplex Rules Update function could not open
an SQL request so it could update CICSplex agent
failure while updating CICSplex
agent preferences, RC=xxxxxxxx.
System action:
Explanation:
The CICSplex Rules Update function could not connect
continues.
to the hub server and create an SQL path request
so it could update CICSplex agent preferences. The User response:
xxxxxxxx value is the return code generated by the SQL Contact IBM Software Support.
request.
System action: function experienced a CLOSE SQL
RC=xxxxxxxx.
User response:
The CICSplex Rules Update function could not
close an SQL request after updating CICSplex agent
while updating CICSplex agent
preferences, RC=xxxxxxxx. System action:
Explanation:
continues.
an SQL access plan so it could update CICSplex agent User response:
preferences. The xxxxxxxx value is the return code Contact IBM Software Support.
System action: function experienced a DROP SQL
RC=xxxxxxxx.
User response:
The CICSplex Rules Update function could not
drop an SQL request after updating CICSplex agent

preferences. The xxxxxxxx value is the return code while updating CICSplex agent
generated by the SQL request. preferences, RC=xxxxxxxx.
The command is discarded; system processing The CICSplex Rules Update function could not drop
continues. an SQL access plan request after updating CICSplex
agent preferences. The xxxxxxxx value is the return
User response:
System action:
continues.
User response:

Chapter 17. KCPSB messages
This information is a listing of the KCPSB messages which are generated from OMEGAMON for CICS on
z/OS for the SLA Batch Utility (kcp_slabatch) while it inputs and outputs definitions. These messages
are in the kcp_slabatch_<yyyymmddhhmm>.log file, where <yyyymmddhhmm> is a timestamp value that
represents when the utility was called. The utility attempts to write the log file to the logs folder, which
is found where IBM Tivoli Monitoring is installed (typically denoted by the CANDLE_HOME environment
variable). If the location is not found, the log file is written to your current working folder. If the SLA Batch
Utility does not have permission to write to the file system, the output of the log file is written to the
console.
KCPSB1001I Starting export of existing SLA User response
definitions.
None, the message is informational.
Explanation KCPSB1004I Using input file: {0}.
An export of the current SLA definitions has been

requested. Explanation
The absolute path specified by {0} is used as the input
System action file to make updates to the SLA definitions.
System action

User response
KCPSB1002I Starting update of SLA definitions.
Explanation KCPSB1005I Writing XML document out to file:

{0}.
The current SLA definitions are updated according to
the input XML file
Explanation
System action The absolute path specified by {0} is used as the
location of the exported SLA definition output file.
System action
User response
KCPSB1003I Attempting to make connection to User response
TEPS.
Explanation KCPSB1006E The input command was not

recognized.
The SLA Batch Utility attempts to connect to the Tivoli
Enterprise Portal Service at the specified hostname
and port location. Explanation
The input command is not recognized by the SLA
System action Batch Utility. These are the valid values: input, export
or help.
System action
The SLA Batch Utility stops processing.

Correct the input command argument specified and All logging information is written to the console.
restart the utility.
KCPSB1007I Disconnecting from TEPS. User response
Verify that the location directory for the log file exists
Explanation and that the user invoking the user ID running the SLA
Batch Utility has authority to write to this location.
The SLA Batch Utility disconnects from the Tivoli
Enterprise Portal Server because processing of the KCPSB1011E Unable to read or write to XML file:
updates has completed. {0}

Processing continues. The SLA Batch Utility was unable to either read from or
write to the location directory specified by {0}.
User response
System action
KCPSB1008I The SLA Batch Utility has
completed. Return code: {0}
User response
Explanation Check the location directory for the XML file and the
user invoking the user ID and verify that this user ID
The SLA Batch Utility has stopped processing. has authority to write to this location. If the problem
indicates that the DTD file is not found, verify that the
System action file is in the correct location as specified within the
XML file.
None.
KCPSB1012I Exporting {0} definitions.
User response
Explanation
Check the return code to determine the success of the
operation. The SLA Batch Utility begins exporting all the
definitions of the type specified by {0}.
KCPSB1009E Required parameter missing: {0}
System action
Explanation
The argument specified by {0} is required for the
command that is being performed by the SLA Batch
Utility, but has not been supplied. User response
None, the message is informational
System action
KCPSB1013I The export of {0} completed
The SLA Batch Utility stops processing. successfully.

Correct for the parameter argument specified and start The SLA Batch Utility completed exporting all the
the SLA Batch Utility again. definitions of the type specified by {0} .
KCPSB1010W Unable to create log file: {0}
System action
Explanation Processing continues.
An attempt to create a log file was made but the
location specified by {0} failed.

None, the message is informational The exporting of an individual definition type{0} file is
attempted. The name of the definition is specified by
KCPSB1014E The SLA Batch Utility is unable to {1}.
create an internal XML document.
System action
Explanation
An internal error occurred while creating an XML
parser.
User response
System action None, the message is informational.
The SLA Batch Utility stops processing. KCPSB1018W No Base Goal was found for
Service Class element {0}.
User response
Explanation
Verify that the version of Java is a supported version. If
problems persist, contact IBM Software Support. While exporting, no Base Goal element was found
for the Service Class element specified by {0}. This
KCPSB1015E Unable to transform internal XML
represents a severe problem because every Service
document to file: {0}
Class element must have a Base Goal element.

The SLA Batch Utility was unable to write to the
Processing continues. This is flagged as an error during
location specified by {0}.
processing

Check the status of the Service Class element using
the Tivoli Enterprise Portal. If problems persist,
User response the Service Class element should be deleted and
recreated.
Verify that location directory for the XML file exists
and that the user invoking the user ID running the SLA KCPSB1019E No Collection Interval or Workload
Batch Utility has the authority to write to this location. Manager definitions found.
KCPSB1016I Log file written to: {0}
Explanation
Explanation A severe error occurred because no Control or Interval
setting was found. The values need to be indicated
Detailed logging information is written to the file at the
for these settings. The CICS SLA tables might be
location specified by {0}.
corrupted.


Export any CICS SLA definitions that you want to
KCPSB1017I Writing {0} to XML document use. Install the OMEGAMON for CICS Tivoli Enterprise
(Name: {1}). Monitoring Server application support to rebuild the
tables and import the saved definitions back to the
tables. If problems persist, contact IBM Software
Support.
Chapter 17. KCPSB messages 203

KCPSB1020I No instances of type {0} were last Service Policy of all these request sis applied. All
found to import. other requests are ignored.

There were no elements of the type specified by {0} The utility discards all Active Service Policy requests,
found in the import file. but the final Active Service Policy request and applies
that one.
System action
User response
Because there should not be multiple Active Service
Policy definitions within the import file, review the
User response
import file and see how it was created to avoid this
None, the message is informational. Verify that the scenario reoccurring.
import file definitions of the specified type were
KCPSB1029E Unable to parse the input XML file:
expected to be found.
{0}
KCPSB1025I Update of {0} definitions starting.
Explanation
Explanation
The SLA Batch Utility was unable to parse the XML
The utility begins importing all the definitions of the document contained within the import file. This is due
type specified by {0}. to an invalid XML document.

Processing continues. The SLA Batch Utility stops processing.

None, the message is informational. Correct the syntax errors within the XML document
and restart the utility.
KCPSB1026I Update of {0} definitions
completed. KCPSB1030W More than one update to the
Control Interval was found. The
last update will be applied.
Explanation
The SLA Batch Utility completed importing all the Explanation
definitions of the type specified by {0}.
The Control Interval is a single setting across all
CICS SLA definitions. Multiple instances of requests
System action
to change the Control Interval setting have been found
Processing continues. in the import file. The values in the final request is
applied. All other requests are ignored.
User response
System action
The SLA Batch Utility discards all the requests, but the
KCPSB1028W More than one Active Service
final Control Interval element request and applies that
Policy request was found. The last
request.
Active Service Policy request will
be applied.
User response
Explanation Because there should not be multiple Control Interval
definitions within the import file, review the import
Only one Service Policy element may be active at any
file and see how it was created to avoid this scenario
one time. Multiple instances of requests to activate a
reoccurring.
Service Policy have been found in the import file. The

KCPSB1031W More than one instance of Control Explanation
Interval was found. The first will
be exported. The SLA Batch Utility was unable to make a successful
connection to the remote Tivoli Enterprise Portal
Server process. The hostname was found, but no
Explanation process was listening on the specified Port: {0}.
The Control Interval is a single setting across the
whole CICS SLA definitions; multiple instances have System action
been found within the current definitions. The values
in the first instance are exported. All other instances The SLA Batch Utility stops processing.
are ignored and not exported.
User response
System action Verify that the port defined for the connection is
The utility exports the Control Interval data from the correct and that the Tivoli Enterprise Portal Server is
first instance that was found. started and waiting for requests.
KCPSB1053E Connection to TEPS failed. TEPS is
User response unavailable or did not respond.
Verify the values in the exported XML file to ensure

they match the expected value. Explanation
KCPSB1050I Attempting to establish The SLA Batch Utility was unable to make a successful
connection to TEPS at hostname: connection to the remote Tivoli Enterprise Portal
{0}, port: {1}. Server process. The process listening on the specified
port did not respond in the necessary time.
Explanation
System action
The SLA Batch Utility is attempting to communicate
with the Tivoli Enterprise Portal Server located at the The SLA Batch Utility stops processing.
hostname/IP address specified by {0} on port number
{1}. User response
Verify that the hostname and port defined for the
System action connection is correct and that the Tivoli Enterprise
Processing continues. Portal Server is started and waiting for requests.
KCPSB1054E Connection to TEPS failed.
User response Unknown or nonexistent
hostname, Hostname: {0}.
KCPSB1051I Connection to TEPS successful Explanation
The SLA Batch Utility was unable to make a successful
Explanation connection to the remote Tivoli Enterprise Portal
The SLA Batch Utility made a successful connection to Server process. The specified hostname could not be
the remote Tivoli Enterprise Portal Server process. found.

Processing continues. The SLA Batch Utility stops processing.

None, the message is informational. Verify that the hostname that is defined for the
connection is correct and that there are no network
KCPSB1052E Connection to TEPS failed. No connectivity issues.
process listening on specified port,
Port: {0}.

KCPSB1055E Connection to TEPS failed. KCPSB1058E Could not obtain User Name: {0}
Exception thrown during from TEPS.
connection attempt: {0}.
Explanation
Explanation
The username specified by the {0} value is not
The SLA Batch Utility was unable to make a successful registered on with Tivoli Enterprise Portal Server .
Server process. The exception thrown during the System action
connection attempt is specified by {0}.
Enterprise Portal Server and stops processing.
System action
The SLA Batch Utility stops processing. User response
Check that the specified username is correct and that
User response
the user has been defined on the connected Tivoli
Verify that the hostname that is defined for the Enterprise Portal Server.
connection is correct and that there are no network
connectivity issues. KCPSB1060I Successfully verified TEPS
version: {0}.
KCPSB1056I Attempting to get User Name: {0}
from TEPS. Explanation
The level of the connected Tivoli Enterprise Portal
Explanation
Server is specified by {0}.
The SLA Batch Utility is trying to determine if the
username specified by {0} is registered with the Tivoli System action
Enterprise Portal Server.
System action
User response
User response KCPSB1061I Attempting to authorize User
None, the message is informational. Name: {0}.
KCPSB1057E Unsupported TEPS version found. Explanation

Cannot support communication
with ITM 6.1 TEPS. The SLA Batch Utility is trying to determine if the
username specified by {0} is registered with the
Tivoli Enterprise Portal Server and is authorized.
Explanation
The password credentials are sent, if specified, and
The version of the Tivoli Enterprise Portal Server the security is set.
utility is attempting to connect to is ITM 6.1. This is not
a supported level of Tivoli Enterprise Portal Server. System action
System action
The SLA Batch Utility disconnects from the Tivoli User response
User response KCPSB1062I User credentials successfully
You need to upgrade the Tivoli Enterprise Portal Server authorized against TEPS.
to a supported level in order to use this utility

The username specified by {0} is an authorized user on The SLA Batch Utility was unable to authorize the
the Tivoli Enterprise Portal Server. user with the connected Tivoli Enterprise Portal
Server process. The exception thrown during the
System action authorization attempt is specified by error code, {0}.
System action
User response The SLA Batch Utility disconnects from the Tivoli
KCPSB1063E User authorization failed. TEPS is User response
unavailable or did not respond. Verify that the specified username and password are
correct and that the user has been defined on the
Explanation connected Tivoli Enterprise Portal Server.
The SLA Batch Utility was unable to authorize the KCPSB1066I Attempting to verify user has
user with the connected Tivoli Enterprise Portal Server permission to view or modify SLA
process. The Tivoli Enterprise Portal Server did not definitions.
respond in time.
Explanation
System action
The SLA Batch Utility is trying to determine if the user
The SLA Batch Utility disconnects from the Tivoli has permission to access the SLA definitions. The user
Enterprise Portal Server and stops processing. must be allocated permission to the CICS SLA view
as part of their Tivoli Enterprise Portal Server user
User response credentials.
Verify that the hostname and port defined for the

System action
connection is correct. Verify that the Tivoli Enterprise
Portal Server is started and that there are no network Processing continues.
connectivity issues.
KCPSB1064E User authorization failed. User response
Password was rejected.
Explanation KCPSB1067I User has CICS SLA privileges

granted.
The SLA Batch Utility was unable to authorize the
user with the connected Tivoli Enterprise Portal
Explanation
Server process. The password that was supplied was
incorrect. The user has permission to access the SLA definitions
by being given CICS SLA view user credentials to either
System action make updates or export current definitions.

System action
User response
User response
Verify that the specified username and password are
correct and that the user has been defined on the None, the message is informational.
connected Tivoli Enterprise Portal Server.
KCPSB1068I User has permission to view or
KCPSB1065E User authorization failed. modify SLA definitions.
Credentials authorization request
failed with error code: {0}.

The user has permission to access the SLA definitions The action that was performed to update the SLA
to either make updates or export current definitions. definitions completed without error.

Processing continues. Processing continues.

None, the message is informational. None, the message is informational.
KCPSB1069E User not authorized to make SLA KCPSB1073E Request [{0}] - Request failed to
updates. complete successfully.
The user does not have permission to access the SLA The action that was performed to update the SLA
definitions. definitions failed to complete and reported an error.
This is recorded as an unsuccessful request.
System action
System action
Enterprise Portal Server and stops processing. Processing continues.

Verify that the specified username is correct and that None, the message is informational.
the user has been allocated access to the CICS SLA
view within the Tivoli Enterprise Portal. KCPSB1074W Request [{0}] - No action was
specified for {1}, Name: {2}.
KCPSB1071I Request [{0}] - Calling {1} on {2}, Element will be ignored.
Name: {3}.
Explanation
Explanation
There was no action attribute supplied with the
An action is about to be performed that updates the element named {2} and of {1} type. This request is
SLA definitions on the connected system. These are ignored and make no changes to the SLA definitions.
the values:
• {1} indicates the action being performed (Create, Edit System action
or Delete)
• {2} indicates the element type (for example,
Workload or Service Class)
User response
• {3} is the name of the element.
If this is an unexpected warning, check the input XML
file for any errors and start the SLA Batch Utility again.
System action
KCPSB1075E Request [{0}] - Error occurred
Processing continues. during update: {1}.

None, the message is informational. An error was reported while processing the request;
KCPSB1072I Request [{0}] - Request completed detailed information about this error is provided by the
successfully. {1} value.

If an error is reported and the -failOnFirstError setting Processing continues.
is set, the error is logged and the SLA Batch Utility
stops processing. User response
User response
Review the additional message provided in the log and KCPSB1083I Request [{0}] - Request is to edit
correct the input XML document and start the SLA an existing Workload.
Batch Utility again.
Explanation
KCPSB1080E Request [{0}] - Input error:
Workload must have a single The next request the SLA Batch Utility processes
Name element. describes the update of an existing Workload element.

The Workload element that is processed as part of the Processing continues.
request either is missing a Name element or has more
than one Name element specified. User response
System action
KCPSB1084I Request [{0}] - Request is to delete
This request fails to process.
an existing Workload.
User response
Explanation
Correct the input XML document with the correct
The next request the SLA Batch Utility processes
format and start the utility again.
describes the deletion of an existing Workload
KCPSB1081E Request [{0}] - Input error: element.
Workload cannot have more than
one Description element. System action
Explanation
The Workload element that is processed as part of User response
the request has more than one Description element
specified. None, the message is informational.
KCPSB1085I Request [{0}] - Workload input
System action variables validated correctly.
Explanation
User response The supplied elements for an update to the Workload
element definitions have been successfully validated.
Correct the input XML document with the correct
format and start the utility again.
System action
KCPSB1082I Request [{0}] - Request is to create
a new Workload. Processing continues.

The next request the SLA Batch Utility processes None, the message is informational.
describes the creation of a new Workload element.
KCPSB1086I Request [{0}] - Workload
validation error: {1}.

There was an error with at least one of the supplied The result of the query to delete an existing Workload
elements for the request to update the Workload definition for this request is provided by the {1} value.
definitions. The detailed reason for this error is
described in the {1} value. System action
Processing continues. If an error is reported and the
System action
-failOnFirstError setting is set, the error is logged and
This request fails to process. the SLA Batch Utility stops processing.

Correct the input XML document for the Workload The message is informational. If an error occurs, check
element and start the SLA Batch Utility again. the input XML file for errors and start the SLA Batch
Utility again.
KCPSB1087I Request [{0}] - Result of insert
Workload query: {1}. KCPSB1090E Request [{0}] - Input error: Service
Class must have a single Name
Explanation element.
The result of the query to create a new Workload

Explanation
definition for the request is provided by the {1} value.
The Service Class element that is processed for the
System action request has no Name element or has more than one
Name element specified.
System action
the SLA Batch Utility stops processing.
User response
User response
The message is informational. If an error occurs, check
the input XML file for errors and start the SLA Batch Check the input XML file for the incorrect or missing
Utility again. elements and start the SLA Batch Utility again.
KCPSB1088I Request [{0}] - Result of update KCPSB1091E Request [{0}] - Input error: Service
Workload query: {1}. Class cannot have more than one
Base Goal element.
Explanation
Explanation
The result of the query to update an existing Workload
definition for this request is provided by the {1} value. The Service Class element that is processed for
the request has more than one Base Goal element
System action specified.

System action
the SLA Batch Utility stops processing. This request fails to process.

The message is informational. If an error occurs, check Check the input XML file for the incorrect or missing
the input XML file for errors and start the SLA Batch elements and start the SLA Batch Utility again.
Utility again.
KCPSB1092I Request [{0}] - Request is to create
KCPSB1089I Request [{0}] - Result of delete a new Service Class.
Workload query: {1}.

The next request the SLA Batch Utility is about to None, the message is informational.
process describes the creation of a new Service Class
KCPSB1096E Request [{0}] - Service Class
element.
validation error: {1} .
System action
Explanation
There was an error for at least one of the supplied
elements for the request to update the Service Class
User response definitions. The detailed reason for this error is
None, the message is informational. described in the {1} value.
KCPSB1093I Request [{0}] - Request is to edit

System action
an existing Service Class.
Explanation
User response
The next request the SLA Batch Utility is about to
process describes the update of an existing Service Check the input XML file for the incorrect or missing
Class element. elements and start the SLA Batch Utility again.
KCPSB1097E Request [{0}] - Input error:
System action Associated Workload not defined.
Explanation
User response For the request to update a Service Class definition,
None, the message is informational. the required Associated Workload parameter element
was not found in the input file.
an existing Service Class.
System action
Explanation This request fails to process.

User response
process describes the deletion of an existing Service
Class element. Check the input XML file for the incorrect or missing
element and start the SLA Batch Utility again.
System action KCPSB1098E Request [{0}] - Input error: Base
Processing continues. Goal element not defined.

None, the message is informational. For the request to update a Service Class definition,
the required Base Goal parameter element was not
KCPSB1095I Request [{0}] - Service Class input found in the input file.
variables validated correctly.
System action
Explanation
The supplied elements for an update to the Service
Class definitions have been successfully validated.
User response
System action Check the input XML file for the incorrect or missing

KCPSB1099E Request [{0}] - Result of insert Explanation
Service Class query: {1} .
An internal error has occurred; no Base Goal element
was found for the Service Class name: {1} . The CICS
Explanation SLA tables might be corrupted.
The result of the query to create a new Service Class
definition for the request is provided by the {1} value. System action
System action
If an error is reported and the -failOnFirstError setting User response
is set, the error is logged and the SLA Batch Utility
stops processing. Delete the Service Class element and recreate it. A
new associated Base Goal element should be created
automatically.
User response
KCPSB2003I Request [{0}] - Result of delete
Check the input XML file for errors and start the SLA current Goals query: {1} .
KCPSB2000I Request [{0}] - Result of insert Explanation
Base Goal query: {1} .
The result of the query to delete a Goal definition for
the request is provided by the {1} value.
Explanation
The result of the query to create a new Base Goal System action
System action the SLA Batch Utility stops processing.
-failOnFirstError setting is set, the error is logged and User response
the SLA Batch Utility stops processing.
The message is informational. Check the input XML file
for errors and start the SLA Batch Utility again.
User response
KCPSB2004I Request [{0}] - Result of delete
The message is informational. Check the input XML file current Service Class query: {1} .
for errors and start the SLA Batch Utility again.
KCPSB2001E Request [{0}] - Input error: Service Explanation
Class, Name: {1} does not exist.
The result of the query to delete an existing Service
Class definition for the request is provided by the {1}
Explanation value.
The Service Class element to be updated for the
request does not exist in the current definitions. System action
System action -failOnFirstError setting is set, the error is logged and
This request fails to process. the SLA Batch Utility stops processing.

Check the input XML file to verify that the correct The message is informational. Check the input XML file
Service Policy element is defined and start the SLA for errors and start the SLA Batch Utility again.
Batch Utility again. KCPSB2005E Request [{0}] - Input error: Service
KCPSB2002E Request [{0}] - Internal error: No Policy must have a single Name
current Base Goal could be found element.
for Service Class, Name: {1} .

The Service Policy element that is processed for the Processing continues.
request has no Name element specified or has more
than one Name element specified. User response
System action
This request fails to process. KCPSB2009I Request [{0}] - Request is to delete
an existing Service Policy.
User response
Explanation
Check the input XML file for the incorrect or missing
elements and start the SLA Batch Utility again. The next request the SLA Batch Utility is about to
process describes the deletion of an existing Service
KCPSB2006E Request [{0}] - Input error: Service Policy element.
Policy cannot have more than one
Description element. System action
Explanation
The Service Policy element that is processed for User response
the request cannot have more than one Description
element specified for the Name element. None, the message is informational.
KCPSB2010I Request [{0}] - Service Policy input
System action variables validated correctly.
Explanation
User response The supplied elements for an update to the
Service Policy definitions for the request have been
successfully validated.
KCPSB2007I Request [{0}] - Request is to create System action
a new Service Policy.
Explanation
User response
process describes the creation of a new Service Policy None, the message is informational.
element.
KCPSB2011E Request [{0}] - Service Policy
System action
Processing continues. Explanation
There was an error with at least one of the supplied
User response elements for the request to update the Service Policy
definitions. The detailed reason for this error is
described in the {1} value.
KCPSB2008I Request [{0}] - Request is to edit
an existing Service Policy. System action
Explanation
The next request the SLA Batch Utility is about to User response
process describes the edit of an existing Service Policy
element. Check the input XML file for the incorrect or missing

KCPSB2012E Request [{0}] - Input Error: Service KCPSB2015E Request [{0}] - Input error: Service
Policy, Name: {1} already defined. Policy, Name: {1} not defined.
A Service Policy element with the same name defined The Service Policy element that is being to updated for
in the request already exists in the current definitions. the request does not exist in the current definitions.

This request fails to process. No new Service Policy This request fails to process.
element is created.
User response
User response
Check the input XML file for the incorrect element and element and start the SLA Batch Utility again.
start the SLA Batch Utility again.
KCPSB2016I Request [{0}] - Result of update
KCPSB2013I Request [{0}] - Result of insert Service Policy query: {1}.
Service Policy query: {1}.
Explanation
Explanation
The result of query to update the existing Service
The result of the query to create a new Service Policy Policy definition for the request is provided by the {1}
definition for the request is provided by the {1} value. value.


None. The message is informational.
KCPSB2014I Connection to TEPS failed. No KCPSB2017E Request [{0}]- Cannot delete active
TEPS found on target system, Service Policy, Name: {1}.
Hostname: {0}.
Explanation
Explanation
The Service Policy element to be deleted is the current
The SLA Batch Utility was unable to make a successful Active Service Policy element and cannot be deleted.
Server (TEPS) process. An IBM Tivoli Monitoring System action
process was listening on the specified port, but a TEPS
was not found. This might have to do with the SLA This request fails to process; the Service Policy
Batch Utility connecting to a host running the Hub element remains active.
Tivoli Enterprise Monitoring Server (TEMS) and not the
TEPS. User response
Deactivate the Service Policy element before
System action
submitting a request to delete it.
The SLA Batch Utility stops.
KCPSB2018I Request [{0}] - Result of insert
Override Goal query: {1}.
User response
Check that the hostname defined to the connection Explanation
is correct and that the TEPS is installed, started, and
The result of the query to create a new Override Goal
waiting for requests.

System action KCPSB2022E Request [{0}] - Input error:
Override Goal must have a single
Processing continues. Service Class element.

The message is informational. The Override Goal element processed as part of this
KCPSB2019I Request [{0}] - Result of delete request either has no Service Class Name element
Override Goal query: {1}. specified or has more than one Service Class Name
element specified.
Explanation
System action
The result of the query to delete an existing Override
Goal definition for the request is provided by the {1} This request fails to process.
value.
User response
System action Check the input XML file for the incorrect or missing
Processing continues. elements and start the SLA Batch Utility again.
KCPSB2023E Request [{0}] - Input error: Cannot
User response have more than one Collection
Interval specified.
The message is informational.
KCPSB2020I Request [{0}] - Request is to create Explanation
a new Override Goal.
The Control element processed for the request has
more than one Collection Interval element specified.
Explanation
The next request the SLA Batch Utility is about to System action
process describes the creation of a new Override Goal
element. This request fails to process.

Processing continues. Check the input XML file for the incorrect or missing
elements and start the SLA Batch Utility again.
User response KCPSB2024E Request [{0}] - Input error: Cannot
have more than one WLM type
specified.
an existing Override Goal. Explanation
The Control element that is processed for the request
Explanation has more than one WLM element specified.
process describes the deletion of an existing Override System action
Goal element.
System action
User response
User response
KCPSB2025E Request [{0}] - Control/Interval

There was an error with at least one of the supplied This request fails to process.
elements for the request to update the Control Interval
definitions. The detailed reason for this error is User response
described in the {1} value.
System action
This request fails to process. KCPSB2029E Request [{0}] - Internal Error:
Unable to find currently active
Service Policy to deactivate.
User response
Check the input XML file for the incorrect or missing Explanation
A severe error has occurred because no current Active
KCPSB2026I Request [{0}] - Result of update Service Policy was found to deactivate. There should
Control/Interval query: {1}. always be one active Service Policy element at any
given time. The CICS SLA tables might be corrupted.
Explanation
System action
The result of the query to update the Control Interval
definition for the request is provided by the {1} value. This request fails to process. If an error is reported and
the -failOnFirstError setting is set, the error is logged
System action and the SLA Batch Utility stops processing.
User response
User response Export any CICS SLA definitions you want to keep, then
reinstall the OMEGAMON for CICS TEMS application
The message is informational. support to rebuild the tables. Import the saved
definitions back into the tables. If problem persists,
KCPSB2027E Request [{0}] - Active Service
Policy validation error: {1}.
KCPSB2030I Request [{0}] - Result of update
Explanation Active Service Policy query: {1}.
There was an error with at least one of the supplied

Explanation
elements for the request to update the Active Service
Policy. The detailed reason for this error is described in The result of the query to update the Active Service
the {1} value. Policy for the request is described by the {1} value.

This request fails to process. Processing continues.

Check the input XML file for the incorrect or missing The message is informational.
KCPSB2031IE Request [{0}] - Exception when
KCPSB2028E Request [{0}] - Service Policy to updating key 9060 value: {1}.
activate, Name: {1} is not defined.
Explanation
Explanation
An error was reported by the SLA Batch Utility when
The Service Policy element to be activated is not issuing a query to update the internal key 9060 value.
defined in the current Service Policy definitions. The current value is provided by {1} .

This request fails to process. If an error is reported and This request fails to process. No new Service Class
the -failOnFirstError setting is set, the error is logged Name is created.
and the SLA Batch Utility stops processing.
User response
User response
Check the input XML file for the incorrect element and
Check the input XML file for errors and start the SLA start the SLA Batch Utility again.
KCPSB2035E Request [{0}] - Input Error: Unable
KCPSB2032I Request [{0}] - Successfully to validate Goal: {1}.
updated key 9060 value: New
value: {1}. Explanation
The Goal element that is specified as part of the
Explanation
Service Class or Service Policy element is defined
The result of query to update the internal key 9060 incorrectly. A detailed description is provided by the
value was successful. The new value is provided by {1}. {1} value.

Processing continues. This request fails to process.

None. Check the input XML file for the incorrect element and
start the SLA Batch Utility again.
KCPSB2033E Request [{0}] - Input Error:
Workload Name: {1} already KCPSB2040E XML Validation Error at line: {0}.
defined. Message: {1}.
A Workload element with the same name that was While parsing the imported XML document, a
defined in this request already exists in the current formatting error was discovered. The line and type of
definitions. error is provided in the message text.

This request fails to process. No new Workload Name The SLA Batch Utility stops following the parsing of the
is created. file; no update requests are done.

Check the input XML file for the incorrect element and Check the input XML file for formatting issues against
start the SLA Batch Utility again. the supplied DTD file and start the SLA Batch Utility
again.
KCPSB2034E Request [{0}] - Input Error: Service
Class Name: {1} already defined. KCPSB2041E XML Validation Fatal Error at line:
{0}. Message: {1}
Explanation
Explanation
A Service Class element with the same name that was
defined in this request already exists in the current While parsing the imported XML document, a fatal
definitions. error was discovered. The line and type of error is
provided in the message text.

The SLA Batch Utility stops following the parsing of the The processing of the definition from the import XML
file; no update requests are done. file is aborted. The likely cause is that one request
has reported an error and the -failOnFirstError flag has
User response been set.
Check the input XML file for formatting issues against

System action
the supplied DTD file and start the SLA Batch Utility
again. The SLA Batch Utility disconnects from the Tivoli
KCPSB2042W XML Validation Warning at line:
{0}. Message: {1}.
User response
Explanation None.
While parsing the imported XML document, a warning KCPSB2045E Input file does not exist on target
was discovered. The line and type of the warning is system: {0}.
provided in the message text.
Explanation
System action
The XML file that is used as the input for the definition
The SLA Batch Utility stops following the parsing of the updates was not found at the specified location.
file; no update requests are done.
System action
User response
Check the input XML file for formatting issues against
the supplied DTD file and start the SLA Batch Utility User response
again.
Check the value of the input parameter supplied and
KCPSB2043W No ITMHOME/CANDLE_HOME/ start the SLA Batch Utility again.
CANDLEHOME directory found.
Using current working folder: {1}. KCPSB2046E Security exception when trying to
access file system: {0}.
Explanation
Explanation
By default, the log file produced by the SLA Batch
Utility is written to a subfolder of the IBM Tivoli The SLA Batch Utility was unable to read or write
Monitoring installation. No environment variable was to the files system at the location due to a security
set to indicate the IBM Tivoli Monitoring installation exception.
location. The current working folder as indicated by
the {1} value is used. System action
System action
The log file is written to the current working folder. User response
Check that the user ID that is running the SLA Batch
User response
Utility has permission to read and write to the target
If this is an unexpected issue, check the installation file system.
location of IBM Tivoli Monitoring installation and set
KCPSB2047I Output file already exists on
the ITMHOME environment variable to this value.
the file system and will be
KCPSB2044W Import of definitions aborted. overwritten: {0}.

The targeted output file for the exported XML Processing continues.
definitions already exists. The file is overwritten by the
new provided definitions. User response
None.
System action
The existing XML file on the file system is removed and KCPSB2051W Invalid Service Class found. Name
replaced by a new output file. {0}.

None. The Service Class name was missing a corresponding
rule.
KCPSB2048I Creating target output directory:
{0}. System action
Explanation
The folder specified by the {0} value is created. User response
To correct the problem, review the Service Class name
System action
entry and create a valid classification rule.
KCPSB2052I Attempting to delete the invalid
Service Class found. Name {0}.
User response
None. Explanation
KCPSB2049E Unable to create target output The Service Class name has been found to be missing
folders. a corresponding rule.

The SLA Batch Utility was unable to the create the The SLA Batch Utility attempts to delete the Service
targeted output folders. The likely cause is the utility Class name from the list of current definitions.
does not have permission to write to the file system.
User response
System action
None.
The SLA Batch Utility stops processing; no output XML
file is written. KCPSB2053I The Service Class is valid. Name:
{0}, Rule: {1}.
User response
Explanation
Verify that the user ID that is running the SLA Batch
Utility has permission to read and write to the targeted The Service Class has passed the validation test
file system. because it has a corresponding rule entry definition.
KCPSB2050I Starting validation of existing System action

Service Class definitions.
Explanation
User response
A validation test of the existing Service Class
definitions has been requested. None.
KCPSB2054I All current Service Class
definitions are valid.

The SLA Batch Utility has completed all tests of the Any Service Class definitions that failed the validation
current Service Class definitions and no errors were test are deleted from the list of current definitions.
found.
System action
System action
User response
User response
None.
None.
KCPSB2057I Review the entries and either
KCPSB2055I The following Service Class correct the Service Class rule or
definitions were found to be delete the Service Class.
invalid:
Explanation
Explanation
Verify that the list of Service Class definitions in
The following list is all the Service Class definitions the KCPSB2055I message have corresponding rule
that failed the validation test. definitions.


None. Either create a classification rule for the Service Class
definition in the list or delete the Service Class.
KCPSB2056I All the invalid Service Class
definitions have been deleted.

Chapter 18. KCPSP messages
This information is a listing of the KCPSP messages generated by the processes that retrieve the service
policy, and the interval and service class definitions used for SLA collection and reporting. They are
displayed in the RKLVLOG output.
KCPSP0300E The Service Policy Thread Explanation
while retrieving the INTERVAL The Service Policy thread was unable to perform
record, RC=xxxxxxxx. a create SQL request in order to retrieve
the OMEGAMON SLA interval and service policy
information. The xxxxxxxx value is the return code
Explanation generated by the SQL request.
The Service Policy thread was unable to connect to the
hub and perform the SQL create path request in order System action
to retrieve the OMEGAMON SLA interval and service
policy information. The xxxxxxxx value is the return The Service Policy Thread stops processing.
User response
The Service Policy Thread stops processing. KCPSP0303E The Service Policy Thread
User response REQUEST failure while
retrieving the INTERVAL record,
Contact IBM Software Support. RC=xxxxxxxx.
KCPSP0301E The Service Policy Thread
experienced a CREATE SQL Explanation
retrieving the INTERVAL record, The Service Policy thread was unable to perform an
RC=xxxxxxxx. open SQL access plan request in order to retrieve
Explanation generated by the SQL request.
The Service Policy thread was unable to perform a
create SQL access plan request in order to retrieve System action
information. The xxxxxxxx value is the return code The Service Policy Thread stops processing.
User response
The Service Policy Thread stops processing. KCPSP0304E The Service Policy Thread
experienced a FETCH SQL DATA
User response failure while retrieving the
INTERVAL record, RC=xxxxxxxx.
KCPSP0302E The Service Policy Thread Explanation
REQUEST failure while The Service Policy thread was unable to perform
retrieving the INTERVAL record, a fetch SQL data request in order to retrieve
RC=xxxxxxxx. the OMEGAMON SLA interval and service policy

The Service Policy Thread stops processing. The Service Policy thread was unable to perform a
drop SQL access plan request in order to retrieve
User response the OMEGAMON SLA interval and service policy
Contact IBM Software Support. generated by the SQL request.
experienced a CLOSE SQL System action
REQUEST failure while The Service Policy Thread stops processing.
retrieving the INTERVAL record,
RC=xxxxxxxx.
User response
The Service Policy thread was unable to perform a KCPSP0321E The Service Policy Thread
close SQL request in order to retrieve the OMEGAMON experienced a CREATE SQL
SLA interval and service policy information. The ACCESS PLAN failure while
xxxxxxxx value is the return code generated by the SQL retrieving the SVPOL record,
request. RC=xxxxxxxx.

The Service Policy Thread stops processing. The Service Policy thread was unable to perform a
create SQL access plan request in order to retrieve
User response the OMEGAMON service policy definition. The xxxxxxxx
KCPSP0306E The Service Policy Thread System action
experienced a DROP SQL REQUEST The Service Policy Thread stops processing.
failure while retrieving the
INTERVAL record, RC=xxxxxxxx.
User response
The Service Policy thread was unable to perform a KCPSP0322E The Service Policy Thread
drop SQL request in order to retrieve the OMEGAMON experienced a CREATE SQL
SLA interval and service policy information. The REQUEST failure while retrieving
xxxxxxxx value is the return code generated by the SQL the SVPOL record, RC=xxxxxxxx.
request.
Explanation
System action
The Service Policy thread was unable to perform
The Service Policy Thread stops processing. a create SQL request in order to retrieve the
OMEGAMON service policy definition. The xxxxxxxx

System action
KCPSP0307E The Service Policy Thread The Service Policy Thread stops processing.
PLAN failure while retrieving the
INTERVAL record, RC=xxxxxxxx. User response

REQUEST failure while retrieving KCPSP0326E The Service Policy Thread
the SVPOL record, RC=xxxxxxxx. experienced a DROP SQL REQUEST
failure while retrieving the SVPOL
Explanation record, RC=xxxxxxxx.
The Service Policy thread was unable to perform an

open SQL request in order to retrieve the OMEGAMON
Explanation
service policy definition. The xxxxxxxx value is the The Service Policy thread was unable to perform a
return code generated by the SQL request. drop SQL request in order to retrieve the OMEGAMON
service policy definition. The xxxxxxxx value is the
System action return code generated by the SQL request.
The Service Policy Thread stops processing.

System action
User response The Service Policy Thread stops processing.

User response
experienced a FETCH SQL DATA
failure while retrieving the SVPOL KCPSP0327E The Service Policy Thread
record, RC=xxxxxxxx. experienced a DROP SQL ACCESS
PLAN failure while retrieving the
Explanation SVPOL record, RC=xxxxxxxx.
The Service Policy thread was unable to perform

a fetch SQL data request in order to retrieve the
Explanation
OMEGAMON service policy definition. The xxxxxxxx The Service Policy thread was unable to perform a
value is the return code generated by the SQL request. drop SQL access plan request in order to retrieve the
OMEGAMON service policy definition. The xxxxxxxx
System action value is the return code generated by the SQL request.

System action
User response The Service Policy Thread stops processing.

User response
REQUEST failure while retrieving KCPSP0341E The Service Policy Thread
the SVPOL record, RC=xxxxxxxx. experienced a CREATE SQL
Explanation retrieving the SCLASS records,
RC=xxxxxxxx.
close SQL request in order to retrieve the OMEGAMON
service policy definition. The xxxxxxxx value is the
Explanation
return code generated by the SQL request. The Service Policy thread was unable to perform a
create SQL access plan request in order to retrieve the
System action OMEGAMON service class definitions. The xxxxxxxx
System action
User response
Chapter 18. KCPSP messages 223

KCPSP0342E The Service Policy Thread KCPSP0346E The Service Policy Thread
REQUEST failure while retrieving failure while retrieving the
the SCLASS records, RC=xxxxxxxx. SCLASS records, RC=xxxxxxxx.
The Service Policy thread was unable to perform The Service Policy thread was unable to perform a
a create SQL request in order to retrieve the drop SQL request in order to retrieve the OMEGAMON
OMEGAMON service class definitions. The xxxxxxxx service class definitions. The xxxxxxxx value is the
value is the return code generated by the SQL request. return code generated by the SQL request.

The Service Policy Thread stops processing. The Service Policy Thread stops processing.

REQUEST failure while retrieving PLAN failure while retrieving the
the SCLASS records, RC=xxxxxxxx. SCLASS records, RC=xxxxxxxx.
The Service Policy thread was unable to perform an The Service Policy thread was unable to perform a
open SQL request in order to retrieve the OMEGAMON drop SQL access plan request in order to retrieve the
service class definitions. The xxxxxxxx value is the OMEGAMON service class definitions. The xxxxxxxx
return code generated by the SQL request. value is the return code generated by the SQL request.


experienced a CLOSE SQL experienced a CREATE SQL
REQUEST failure while retrieving ACCESS PLAN failure while
the SCLASS records, RC=xxxxxxxx. retrieving the GOAL records,
RC=xxxxxxxx.
Explanation
Explanation
close SQL request in order to retrieve the OMEGAMON The Service Policy thread was unable to perform a
service class definitions. The xxxxxxxx value is the create SQL access plan request in order to retrieve the
return code generated by the SQL request. OMEGAMON SLA goal definitions. The xxxxxxxx value
System action


REQUEST failure while retrieving failure while retrieving the GOAL
the GOAL records, RC=xxxxxxxx. records, RC=xxxxxxxx.
The Service Policy thread was unable to perform The Service Policy thread was unable to perform a
a create SQL request in order to retrieve the drop SQL request in order to retrieve the OMEGAMON
OMEGAMON SLA goal definitions. The xxxxxxxx value SLA goal definitions. The xxxxxxxx value is the return
is the return code generated by the SQL request. code generated by the SQL request.


REQUEST failure while retrieving PLAN failure while retrieving the
the GOAL records, RC=xxxxxxxx. GOAL records, RC=xxxxxxxx.
The Service Policy thread was unable to perform an The Service Policy thread was unable to perform a
open SQL request in order to retrieve the OMEGAMON drop SQL access plan request in order to retrieve the
SLA goal definitions. The xxxxxxxx value is the return OMEGAMON SLA goal definitions. The xxxxxxxx value
code generated by the SQL request. is the return code generated by the SQL request.


experienced a CLOSE SQL experienced a RELEASE
REQUEST failure while retrieving CONNECTION failure while
the GOAL records, RC=xxxxxxxx. retrieving the GOAL records,
RC=xxxxxxxx.
Explanation
Explanation
close SQL request in order to retrieve the OMEGAMON The Service Policy thread was unable to release the
SLA goal definitions. The xxxxxxxx value is the return connection in order to retrieve the OMEGAMON SLA

goal definitions. The xxxxxxxx value is the return code Explanation
The Object Status Manager was unable to perform a
create SQL request in order to retrieve managed object
System action status data. The xxxxxxxx value is the return code
The Service Policy Thread stops processing. generated by the SQL request.

Contact IBM Software Support. The Object Status Manager stops processing.
KCPSP0380E The Object Status Manager

User response
while retrieving rows from the Contact IBM Software Support.
MOSTATUS table, RC=xxxxxxxx.
Explanation REQUEST failure while retrieving
The Object Status Manager was unable to connect to rows from the MOSTATUS table,
the hub and perform the SQL path request in order RC=xxxxxxxx.
to retrieve managed object status data. The xxxxxxxx
value is the return code generated by the SQL request. Explanation
The Object Status Manager was unable to perform an
System action open SQL request in order to retrieve managed object
The Object Status Manager stops processing. status data. The xxxxxxxx value is the return code
User response
System action
The Object Status Manager stops processing.
User response
retrieving rows from the Contact IBM Software Support.
The Object Status Manager was unable to perform a rows from the MOSTATUS table,
create SQL access plan request in order to retrieve RC=xxxxxxxx.
managed object status data. The xxxxxxxx value is the
return code generated by the SQL request. Explanation
System action close SQL request in order to retrieve managed object
The Object Status Manager stops processing. status data. The xxxxxxxx value is the return code
User response
System action
User response
rows from the MOSTATUS table, Contact IBM Software Support.
RC=xxxxxxxx.

failure while retrieving rows KCPSP0401E The Object Status Manager
from the MOSTATUS table, experienced a CREATE SQL
RC=xxxxxxxx. ACCESS PLAN failure while
retrieving rows from the
Explanation WORKLOAD table, RC=xxxxxxxx.

drop SQL request in order to retrieve managed object
Explanation
status data. The xxxxxxxx value is the return code The Object Status Manager was unable to perform a
generated by the SQL request. create SQL access plan request in order to retrieve
workload definitions. The xxxxxxxx value is the return
System action code generated by the SQL request.

System action
User response The Object Status Manager stops processing.

User response
PLAN failure while retrieving KCPSP0402E The Object Status Manager
rows from the MOSTATUS table, experienced a CREATE SQL
RC=xxxxxxxx. REQUEST failure while retrieving
rows from the WORKLOAD table,
The Object Status Manager was unable to perform

a drop SQL access plan request in order to retrieve
Explanation
managed object status data. The xxxxxxxx value is the The Object Status Manager was unable to perform
return code generated by the SQL request. a create SQL request in order to retrieve workload
definitions. The xxxxxxxx value is the return code
System action generated by the SQL request.

System action
User response The Object Status Manager stops processing.

User response
KCPSP0399I The Service Policy thread
successfully updated the Service
Level Analysis definitions. KCPSP0403E The Object Status Manager
Changes to the policy, workloads, or service classes RC=xxxxxxxx.
used by Service Level Analysis were successfully
processed and activated by the Service Policy thread.
Explanation
System action The Object Status Manager was unable to perform
an open SQL request in order to retrieve workload
Processing continues. definitions. The xxxxxxxx value is the return code
User response
System action

experienced a CLOSE SQL User response
RC=xxxxxxxx. KCPSP0421E The Object Status Manager
Explanation
retrieving rows from the IBMSC
The Object Status Manager was unable to perform table, RC=xxxxxxxx.
a close SQL request in order to retrieve workload
definitions. The xxxxxxxx value is the return code Explanation
create SQL access plan request in order to retrieve
System action
MVS WLM service class definitions. The xxxxxxxx value
The Object Status Manager stops processing. is the return code generated by the SQL request.

experienced a DROP SQL REQUEST User response
failure while retrieving rows Contact IBM Software Support.
from the WORKLOAD table,
Explanation
rows from the IBMSC table,
The Object Status Manager was unable to perform RC=xxxxxxxx.
a drop SQL request in order to retrieve workload
definitions. The xxxxxxxx value is the return code Explanation
a create SQL request in order to retrieve MVS WLM
System action
service class definitions. The xxxxxxxx value is the
The Object Status Manager stops processing. return code generated by the SQL request.

experienced a DROP SQL ACCESS User response
PLAN failure while retrieving Contact IBM Software Support.
Explanation
The Object Status Manager was unable to perform RC=xxxxxxxx.
a drop SQL access plan request in order to retrieve
workload definitions. The xxxxxxxx value is the return

Explanation rows from the IBMSC table,
RC=xxxxxxxx.
open SQL request in order to retrieve MVS WLM service
class definitions. The xxxxxxxx value is the return code Explanation
generated by the SQL request. The Object Status Manager was unable to perform a
drop SQL access plan request in order to retrieve MVS
System action WLM service class definitions. The xxxxxxxx value is
System action
User response
KCPSP0425E The Object Status Manager User response
rows from the IBMSC table, KCPSP0441E The Object Status Manager
Explanation deleting rows from the IBMSC
table, RC=xxxxxxxx.
a close SQL request in order to retrieve MVS WLM
service class definitions. The xxxxxxxx value is the Explanation
return code generated by the SQL request. The Object Status Manager was unable to perform a
create SQL access plan request in order to delete the
System action rows from the IBMSC table. The xxxxxxxx value is the
System action
User response
failure while retrieving rows from Contact IBM Software Support.
the IBMSC table, RC=xxxxxxxx. KCPSP0442E The Object Status Manager
Explanation REQUEST failure while deleting
The Object Status Manager was unable to perform a RC=xxxxxxxx.
drop SQL request in order to retrieve MVS WLM service
class definitions. The xxxxxxxx value is the return code
System action create SQL request in order to delete the rows from
the IBMSC table. The xxxxxxxx value is the return code
The Object Status Manager stops processing. generated by the SQL request.

PLAN failure while retrieving

REQUEST failure while deleting Contact IBM Software Support.
rows from the IBMSC table, KCPSP0461E The Object Status Manager
Explanation updating the MOSTATUS table,
RC=xxxxxxxx.
open SQL request in order to delete the rows from the
IBMSC table. The xxxxxxxx value is the return code Explanation
generated by the SQL request. The Object Status Manager was unable to perform a
create SQL access plan request in order to update the
System action managed object status table. The xxxxxxxx value is the
System action
User response
failure while deleting rows from Contact IBM Software Support.
the IBMSC table, RC=xxxxxxxx. KCPSP0462E The Object Status Manager
Explanation REQUEST failure while
updating the MOSTATUS table,
The Object Status Manager was unable to perform a RC=xxxxxxxx.
drop SQL request in order to delete the rows from the
IBMSC table. The xxxxxxxx value is the return code
System action create SQL request in order to update the managed
object status table. The xxxxxxxx value is the return
The Object Status Manager stops processing. code generated by the SQL request.

PLAN failure while deleting
rows from the IBMSC table, Contact IBM Software Support.
Explanation failure while updating the
drop SQL access plan request in order to delete the
rows from the IBMSC table. The xxxxxxxx value is the Explanation
return code generated by the SQL request. The Object Status Manager was unable to perform a
drop SQL request in order to update the managed
System action object status table. The xxxxxxxx value is the return

System action status information. The xxxxxxxx value is the return
System action
User response
PLAN failure while updating the Contact IBM Software Support.
MOSTATUS table, RC=xxxxxxxx. KCPSP0486E The Object Status Manager
Explanation failure while inserting rows in the
drop SQL access plan request in order to update the
managed object status table. The xxxxxxxx value is the Explanation
return code generated by the SQL request. The Object Status Manager was unable to perform
a drop SQL request in order to add managed object
System action status information. The xxxxxxxx value is the return
System action
User response
ACCESS PLAN failure while Contact IBM Software Support.
inserting rows in the MOSTATUS KCPSP0487E The Object Status Manager
table, RC=xxxxxxxx. experienced a DROP SQL ACCESS
PLAN failure while inserting
Explanation rows in the MOSTATUS table,
RC=xxxxxxxx.
a create SQL access plan request in order to add
managed object status information. The xxxxxxxx Explanation
value is the return code generated by the SQL request. The Object Status Manager was unable to perform a
drop SQL access plan request in order to add managed
System action object status information. The xxxxxxxx value is the
System action
User response
REQUEST failure while inserting Contact IBM Software Support.
rows in the MOSTATUS table, KCPSP0501E The Object Status Manager
Explanation updating the situation table,
RC=xxxxxxxx.
create SQL request in order to add managed object

The Object Status Manager was unable to perform a The Object Status Manager was unable to perform
create SQL access plan request in order to update the a drop SQL request in order to update the situation
situation table. The xxxxxxxx value is the return code table. The xxxxxxxx value is the return code generated
generated by the SQL request. by the SQL request.

The Object Status Manager stops processing. The Object Status Manager stops processing.

KCPSP0502E The Object Status Manager KCPSP0507E The Object Status Manager
experienced a CREATE SQL experienced a DROP SQL ACCESS
REQUEST failure while updating PLAN failure while updating the
the situation table, RC=xxxxxxxx. situation table, RC=xxxxxxxx.
The Object Status Manager was unable to perform a The Object Status Manager was unable to perform a
create SQL request in order to update the situation drop SQL access plan request in order to update the
table. The xxxxxxxx value is the return code generated situation table. The xxxxxxxx value is the return code
by the SQL request. generated by the SQL request.

The Object Status Manager stops processing. The Object Status Manager stops processing.

KCPSP0503E The Object Status Manager KCPSP0512E The Object Status Manager
experienced an OPEN SQL experienced a RELEASE
REQUEST failure while updating CONNECTION failure while
the situation table, RC=xxxxxxxx. updating the situation table,
RC=xxxxxxxx.
Explanation
Explanation
an open SQL request in order to update the situation The Object Status Manager was unable to release the
table. The xxxxxxxx value is the return code generated connection used to update the situation table. The
by the SQL request. xxxxxxxx value is the return code generated by the SQL
request.
System action
System action
User response
User response
experienced a DROP SQL REQUEST KCPSP0520E THE MVS WLM SERVICE CLASSES
failure while updating the FUNCTION EXPERIENCED A
situation table, RC=xxxxxxxx. CONNECT FAILURE WHILE

ADDING ROWS TO THE IBMSC System action
TABLE, RC=xxxxxxxx.
The MVS WLM Service Classes function stops
processing.
Explanation
The MVS WLM Service Classes function was unable to User response
connect to the hub and perform the SQL create path
request in order to update the MVS WLM service class Contact IBM Software Support.
definitions in the OMEGAMON repository. The xxxxxxxx KCPSP0523E THE MVS WLM SERVICE CLASSES
value is the return code generated by the SQL request. FUNCTION EXPERIENCED AN
OPEN SQL REQUEST FAILURE
System action WHILE ADDING ROWS TO THE
IBMSC TABLE, RC=xxxxxxxx.
processing.
Explanation
User response The MVS WLM Service Classes function was unable to
perform an open SQL request in order to update the
Contact IBM Software Support. MVS WLM service class definitions in the OMEGAMON
KCPSP0521E THE MVS WLM SERVICE CLASSES repository. The xxxxxxxx value is the return code
FUNCTION EXPERIENCED A generated by the SQL request.
CREATE SQL ACCESS PLAN
FAILURE WHILE ADDING ROWS System action
TO THE IBMSC TABLE,
RC=xxxxxxxx. The MVS WLM Service Classes function stops
processing.
Explanation
User response
The MVS WLM Service Classes function was unable
to perform a create SQL access plan request in order Contact IBM Software Support.
to update the MVS WLM service class definitions in KCPSP0526E THE MVS WLM SERVICE CLASSES
the OMEGAMON repository. The xxxxxxxx value is the FUNCTION EXPERIENCED A DROP
return code generated by the SQL request. SQL REQUEST FAILURE WHILE
ADDING ROWS TO THE IBMSC
System action TABLE, RC=xxxxxxxx.
processing. Explanation
The MVS WLM Service Classes function was unable to
User response perform a drop SQL request in order to update the
MVS WLM service class definitions in the OMEGAMON
Contact IBM Software Support. repository. The xxxxxxxx value is the return code
KCPSP0522E THE MVS WLM SERVICE CLASSES generated by the SQL request.
FUNCTION EXPERIENCED A
CREATE SQL REQUEST FAILURE System action
WHILE ADDING ROWS TO THE
IBMSC TABLE, RC=xxxxxxxx. The MVS WLM Service Classes function stops
processing.
Explanation
User response
The MVS WLM Service Classes function was unable to
perform a create SQL request in order to update the Contact IBM Software Support.
MVS WLM service class definitions in the OMEGAMON KCPSP0527E THE MVS WLM SERVICE CLASSES
repository. The xxxxxxxx value is the return code FUNCTION EXPERIENCED A DROP
generated by the SQL request. SQL ACCESS PLAN FAILURE

WHILE ADDING ROWS TO THE System action
IBMSC TABLE, RC=xxxxxxxx.
processing.
Explanation
The MVS WLM Service Classes function was unable User response
to perform a drop SQL access plan request in order
to update the MVS WLM service class definitions in Contact IBM Software Support.
the OMEGAMON repository. The xxxxxxxx value is the KCPSP0540W The specified interval of 0006 is
return code generated by the SQL request. invalid. The 15 minute default will
be used.
System action
The MVS WLM Service Classes function stops Explanation
processing. An interval other than 1, 5, 15, 30, 60 minutes was
detected by the service policy thread.
User response
KCPSP0532E THE MVS WLM SERVICE CLASSES System processing continues; the workload analysis
FUNCTION EXPERIENCED A subtask will use the default interval length of 15
RELEASE CONNECTION FAILURE minutes.
WHILE ADDING ROWS TO THE
IBMSC TABLE, RC=xxxxxxxx. User response
You can optionally use the SLA view in the Tivoli
Explanation Enterprise Portal to change the interval to a length
The MVS WLM Service Classes function was unable to other than 15 minutes if you require.
release the connection used to update the MVS WLM
service class definitions in the OMEGAMON repository.
SQL request.

Chapter 19. KCPUI messages
This information is a listing of the KCPUI messages generated by the OMEGAMON enhanced 3270 user
interface for OMEGAMON for CICS on z/OS.
KCPUI0001E Unable to locate KCPUI0005I Task History is not active for this
CICSManagedSystemName within region.
a CICSplex.
Explanation:
Explanation: You attempted to navigate to task history for a region
No CICSplex Managed System List was found that that does not have task history enabled.
contained the specified CICSManagedSystemName.
System action:
The feature is unable to determine which CICSplex this
Navigation to view trace data stops.
CICS region is part of.
User response:
System action:
Information only.
Navigation to the target CICS region stops.
KCPUI0006E No workspace exists for this file
User response:
type.
Check that the address space is still active: From
the Tools menu on the toolbar for the enhanced Explanation:
3270 interface, select Registry refresh; then try the You attempted to navigate for a file type that is not
navigation again. supported.
KCPUI0002E Selection selectioncharacter is not System action:
supported by xxxxxxxx exec. Navigation to the target workspace stops.
Explanation: User response:
There is a mismatch in the menu options on the Contact IBM Software Support.
previous workspace and the xxxxxxxx EXEC.
KCPUI0008E Maximum number of filters
System action: allowed is n.
Explanation:
User response: More than the maximum allowed number of task
Contact IBM Software Support. history filter parameters, indicated by n in the
message, was entered.
KCPUI0003E Zoom column columnname is not
supported by xxxxxxxx exec. System action:
The filter values are not saved.
Explanation:
There is a mismatch in the menu options on the User response:
previous workspace and the xxxxxxxx EXEC. Remove one or more filter parameters until the
number of filters on the task history filters popup
System action:
workspace is not greater than the maximum number
allowed.
User response:
KCPUI0009E Filter initialization failed. RC=n.
KCPUI0004I Trace data is not available for this Explanation
task.
Task history filter processing was unable to initialize
Explanation: correctly, where:
You made a selection to view trace data, but the n
workspace indicated no trace data is available. Is either 4 or 8 and indicates the source of the
System action: message within the code.
Navigation to view trace data stops. System action:
User response: Task history filters cannot be set.
Select to view trace data only for those tasks that User response:
indicate trace data is available. Contact IBM Software Support.

KCPUI0010E Filter processing failed. RC=8. mm
Is the number of minutes.
Explanation:
An error occurred while saving task history filters. ss
Is the number of seconds.
System action:
t
Task history filters cannot be set.
Is tenths of a second.
User response:
System action:
KCPUI0011E * must be the last character in a
User response:
generic filter.
Correct the filter value in the indicated field, and
Explanation: submit the filter value again.
A generic filter is defined with an asterisk (*) in the
KCPUI0014E Input must be of the form n, nK,
last character position A generic task history filter was
n.nK, nM or n.nM
defined with an asterisk in a position other than the
last character position. Explanation:
An invalid filter string was entered in a field that
System action:
accepts decimal notation in the format n, nK,
n.nK, nM, n.nM.
User response:
System action:
submit the filter value again.
User response:
KCPUI0012E Input must be numeric digits only.
Explanation: submit the filter value again.
Some task history filter fields accept only numeric
KCPUI0018I The requested task could not be
input. A filter field that contained non-numeric
characters was entered when the task history filter located in Task History.
field expected only numeric input. Explanation:
Navigation to display the details of a specific task
System action:
was requested, however the specific task could not
be located in the entire task history data store. This is
User response: most likely due to the task history data store having
Correct the filter value in the indicated field, and wrapped and the task data is no longer available.
submit the filter value again.
User response:
KCPUI0013E Input must be a valid time of the None required.
form mm:ss.t
Explanation
A time filter with an invalid format was entered. The
expected format is mm:ss.t, where:

Chapter 20. KCPZZ messages
This information is a listing of the KCPZZ messages related to offloading OMEGAMON for CICS on z/OS
workloads to a zIIP processor. They are displayed in the z/OS console.
KCPZZ0900E API TTTTTTTT INTERFACE ERROR through a SDUMP. The return code from the SDUMP
- SC=XXXX, RC=YYYY, RSN=ZZZZ indicated an error. The nnnnnnnnnn value represents
the original abend code. The XX value is the SDUMP
return code and the YY value is the SDUMP reason
Explanation
code.
This message is a generic API failed error message.
The TTTTTTTT value represents the service or macro System action
instruction that failed. The XXXX value is the system
code returned by the API to the caller. The YYYY SRB processing stops.
value is the return code from the service or macro
instruction, and the ZZZZ value is the associated User response
reason code.
System action KCPZZ0998I DAE SUPPRESSED DUMP FOR
ABEND nnnnnnnnnn
System processing continues; no zIIP processing takes
place.
Explanation
User response The API Functional Recovery Routine intercepted an
ABEND in SRB processing. The FRR module attempted
to generate diagnostics through the SDUMP. The return
KCPZZ0902E WLM TTTTTTTT INTERFACE code from the SDUMP indicated that the system
ERROR - SC=XXXX, RC=YYYY, dump was suppressed by DAE. The nnnnnnnnnn value
RSN=ZZZZ represents the original abend code.

This message is a generic WLM request failed error SRB processing stops.
message. The TTTTTTTT value represents the service
or macro instruction that failed. The XXXX value is the User response
system code returned by the API. The YYYY value is
the return code from the service or macro instruction, If the problem persists, contact IBM Software Support.
and the ZZZZ value is the associated reason code.
KCPZZ0999E XXXXXXXX YYYYYYYY
SSSSSSSSSSSSSSSSSSSSSSS
System action ABEND \\ nnnnnnnnnn
System processing continues; no zIIP processing takes
place. Explanation
The API Functional Recovery Routine intercepted an
User response ABEND in SRB processing; this message indicates
the nature of the ABEND. The XXXXXXXX value
is the job or started task name where the SRB
KCPZZ0997E SDUMP FAILED FOR ABEND failed. The YYYYYYYY value is the failing component.
nnnnnnnnnn, RC=XX, RSN=YY The SSSSSSSSSSSSSSSSSSSSSSS value is the failing
subcomponent and the nnnnnnnn value is the ABEND
code.
Explanation
The API Functional Recovery Routine intercepted an System action
ABEND in Service Request Block (SRB) processing.
The FRR module attempted to generate diagnostics SRB processing stops.

User response

Chapter 21. KGW messages
This information is a listing of the KGW messages that are generated from OMEGAMON for CICS TG on
z/OS component. These messages are displayed in the RKGWSLOG output of the monitoring agent or
Tivoli Enterprise Monitoring Server address space.
The statistics component, SAPI, of OMEGAMON for CICS TG on z/OS provides its own messages. Standard
messaging can be displayed through the WTO and LOG parameters. The SAPI messages are logged in the
RKGWSLOG file.
KGW0001E GWSAA UNABLE TO ACQUIRE Explanation
SESSION ACCOUNTING AREA
This informational message is written to the RKLVLOG
when an agent is first invoked. It lists the agent name,
Explanation most recently applied PTF, the load point, and date
Locate or build of a session accounting area could not and time of assembly.
be attempted due to insufficient storage.
System action
System action None.
The function is bypassed.
User response
User response None, the message is informational.
Check the RKLVLOG output for additional messages KGW0007E XAM INVALID PARAMETERS
that may indicate storage-related problems. If SPECIFIED
KGW0004E subtask CANNOT COMMUNICATE Explanation
WITH XMI
The parameter specified on the start command for the
exception analysis manager (XAM) subtask is invalid.
Explanation
The system was unable to locate the address of the System action
XMI communication control block using TMS:Engine
services. The exception analysis manager continues processing.

The subtask identified by the subtask value stops Specify a valid parameter.
processing. KGW0009E ADDRESS OF GW CVT IS MISSING

Confirm that XMI successfully started as a subtask The Product Communication Vector Table (CVT) could
of the Tivoli Enterprise Monitoring Agent address not be located.
Tivoli Enterprise Monitoring Agent CONFIG file that
automatically starts XMI. If problems persist, contact System action
IBM Software Support. Statistics API subtask fails to start.
KGW0005I AGENT module PTF ptfno @
address ASSEMBLY date time User response
Try to start the Statistics API component again. If

KGW0017E UNABLE TO ALLOCATE XCB System action
CONTROL BLOCK
If the error occurs during initialization, the exception
analysis subtask stops processing. Otherwise, XAM
Explanation continues processing with a decreased ability to
The cross-memory interface (XMI) subtask was unable compute rates.
to allocate one of its primary communications control
blocks from subpool 251 storage. User response
Consider increasing the region size of the address
System action space in which XMI is started.
The cross-memory interface task stops processing. KGW0028E XAM PROGRAM CHECK RECOVERY
FOR CICS TG: region
User response
Consider increasing the region size of the address Explanation
space in which XMI is started. The exception analysis manager (XAM) subtask
KGW0022I XAM EXCEPTION ANALYSIS encountered a program. Check in one of its cross-
MANAGER IS TERMINATING memory mode collection routines while attempting to
monitor the CICS TG denoted by the region value.
Explanation
System action
The Exception Analysis Manager (XAM) received a
request to stop processing. The XAM continues processing; no memory dump is
produced.
System action
User response
None.
This might be the result of corrupted storage in the
CICS TG address space. If problems persist, contact
User response IBM Software Support.
None. KGW0103I agent UNABLE TO MONITOR CICS
KGW0023I XAM EXCEPTION ANALYSIS TG region: RC=rc
MANAGER IS ACTIVE
Explanation
Explanation IBM Z OMEGAMON for CICS TG is unable to monitor
The Exception Analysis Manager (XAM) completed CICS TG region. The return code rc value indicates the
initialization. type of error. These are the return codes:
Table 7. Return codes when IBM Z OMEGAMON for

System action CICS TG cannot monitor a CICS region.
None. Return Code Description
00 CICS TG region
User response is monitored by
None. OMEGAMON for CICS TG
on z/OS.
KGW0027E XAM UNABLE TO ACQUIRE
TABLE STORAGE: LENGTH=length, 04 XMI did not register the
ID=table XCB address.
08 CICS TS or CICS TG
Explanation region could not be
found.
The exception analysis manager (XAM) subtask was
unable to allocate length bytes of private storage for
table identified by table value.

Table 7. Return codes when IBM Z OMEGAMON for KGW0301E SPI ANCHOR VALIDATION FAILED
CICS TG cannot monitor a CICS region. (continued)
Return Code Description Explanation
The Statistics API subtask has failed to validate
0C Specified region does not
component anchor.
belong to CICS TS or
CICS TG.
System action
10 CICS TS release is
not supported by The subtask stops processing.
OMEGAMON for CICS TG
on z/OS. User response
14 CICS TS or CICS TG job is If problem persists, contact IBM Software Support.
swapped out.
KGW0302E SPI STATUS_CLIENT_MANAGER
18 ESTAEX macro failed. FAILURE. REASON=rc
1C Cross memory error
occurred during CICS TS Explanation
or CICS TG validation.
The Statistics API component received a non zero
20 CICS TS or CICS return code when attempting to display component
TG initialization is not status.
complete.
28 Unable to obtain memory System action
required to build TDA.
None.
2C Session Accounting Area
build error occurred. User response
30 Module load error See RKGWSLOG for further messages. If problem
occurred (see console for persists, contact IBM Software Support.
message KGW0760E).
KGW0303E SPI START_CLIENT_MANAGER
FAILURE. REASON=rc
System action
No data is collected for all return codes except 00'. Explanation
User response return code when attempting to start this component.
For return code x'04', make sure that XMI (cross
memory interface task) is an active subtask of the System action
Tivoli Enterprise Monitoring Agent address space. If
The subtask stops processing.
KGW0300I SPI STATISTICS COMPONENT IS User response
ACTIVE
See the RKGWSLOG output for further messages.
If attempts to restart the subtask fail, contact IBM
Explanation
Software Support.
The Statistics task is now active.
KGW0304E SPI MODIFY_CLIENT_MANAGER
FAILURE. REASON=rc
System action
None. Explanation
User response return code when attempting to process the MODIFY
None. command.
Chapter 21. KGW messages 241

System action KGW0308E SPI MODIFY LOOPINV INVALID
VALUE
None.
Explanation
User response
An invalid value was specified for the MODIFY
See the RKGWSLOG output for further messages. If command.
KGW0305E SPI MODIFY ADDICLD INVALID System action
SERVER OR PORT
Explanation
User response
command. Specify a valid value for the LOOPINV keyword and
System action KGW0309E SPI MODIFY CTGTRAC INVALID
VALUE
Explanation
User response
Specify a valid value for the ADDICLD keyword and command.
KGW0306E MODIFY DELICLD INVALID System action
SERVER OR PORT
Explanation
User response
command. Specify a valid value for the CTGTRAC keyword and
System action KGW0310I SPI STOP STATISTICS API CLIENT
MANAGER TASK IN PROGRESS
Explanation
User response
The Statistics API component is stopping.
Specify a valid value for the DELICLD keyword and
System action
KGW0307E SPI MODIFY CLININV INVALID
VALUE The Statistics API component stops processing.

An invalid value was specified for the MODIFY None.
command. KGW0311E SPI STOP_CLIENT_MANAGER
FAILURE. REASON=rc
System action
The command is ignored. Explanation
User response return code when attempting to stop this component.
Specify a valid value for the CLININV keyword and

System action KGW0603I XTR Transaction Retriever is
terminating.
Explanation
User response
The cross memory CICS TG transaction summarizer
See RKGWSLOG for further messages. If attempting subtask is being stopped.
to restart the subtask and restart fails, contact IBM
Software Support.
System action
KGW0312I SPI TASK RESOURCE CLEANUP IS
COMPLETE The end of processing continues.

All resources owned by the Statistics API component None. Information only message.
have been successfully released. KGW0604I XTR Task resource cleanup is
complete.
System action
None. Explanation
Cross memory CICS TG transaction summarizer
User response subtask resource cleanup is complete.
None.
System action
KGW0313E SPI INTERFACE TASK HAS
ABENDED WITH S0Cx Termination continues.

The Statistics API component recovery routine was None. Information only message.
invoked due to a system abend, where the fourth KGW0605E XTR Transaction Retriever is
character x value is a generic substitute for 0-9, A-F. active.

The component stops processing. The cross memory CICS TG transaction summarizer
subtask cannot communicate with XMI.
User response
See RKGWSLOG for further messages. If problem System action
persists, contact IBM Software Support. The transaction summarizer subtask does not start.
KGW0601I XTR Transaction Retriever is
active. User response
Ensure that the OMEGAMON region's Cross memory
Explanation component or XMI is activated during Agent startup.
The cross memory CICS TG transaction summarizer Verify that the KGW0800I message is issued in the job
subtask is currently active. log for the agent.
KGW0613E XTR ESTAEX macro failure.
System action RC=hhhhhhhh.
The processing continues.
Explanation
User response The recovery environment could not be established
during cross memory CICS TG transaction summarizer
None. Information only message. subtask initialization.

The transaction summarizer subtask does not start. During an OPEN, CLOSE, FIND, or parsing of
configuration parameters an error was detected on
User response member KGWSAPIP in the RKANPARU data set.
• rrrrrrrr is the reason for the error.
KGW0623W XTR unable to retrieve data from System action
aaaaaaaa with ASID bbbb.
Processing continues with default configuration
settings. No regions are included for monitoring.
Explanation
During a retry recovery routine, previously monitored User response
region aaaaaaaa with ASID bbbb was not responding,
where: Check the reason code to determine the corrective
action.
• aaaaaaaa is the CICS Transaction Gateway or
WebSphere Application Server jobname. KGW0762E HOLD COUNT DISPLACEMENT
• bbbb is the CICS Transaction Gateway or WebSphere VALIDATION FAILED
Application Server address space ID, in hexadecimal
format. Explanation
OMEGAMON was unable to verify the location of the
System action hold count field in the OUCB.
The subtask abend continues with percolation.
System action
User response The XMIT stops processing because OMEGAMON
Contact IBM Software Support with the following components are unable to verify target address spaces
information: if they might be swapped out.
• MCS console log when the incident occurred

User response
• JCL and JESLOG of product JOB environment
• Output of any dumps produced (SYSDUMP,
SYSMDUMP) KGW0764E TAI DETECTED AN INCORRECT
WORK AREA LENGTH
KGW0760E LOAD OF module FAILED:
CODE=abend, REASON=reason
Explanation
Explanation The size of the extended common service area
(ECSA) allocated by the TAM module differs from that
The load module module value could not be loaded.
expected by the TAI module.
The abend value is the abend code, and the reason
value indicates the reason code associated with the
abend. System action
System action stops processing with a U0764 ABEND.
User response
Locate the abend code in the IBM System Codes KGW0765E TAF DETECTED AN INCORRECT
manual, correct the cause of the load failure, and WORK AREA LENGTH
KGW0761W Configuration file processing error:
Reason: rrrrrrrr

The size of the ECSA work area allocated by TAM Either use an XM=nn statement in the configuration
differs from that expected by module TAF. file to start another cross memory interface task, or
stop the agent address space in which the active task
System action is running.
The cross memory interface (XMI) abnormally stops KGW0810I XMI CROSS MEMORY COMPONENT
processing with a U0765 ABEND. IS TERMINATING

Contact IBM Software Support. The Cross Memory Interface task is shutting down.
KGW0766E TAG DETECTED AN INCORRECT

System action
WORK AREA LENGTH
The XMI task stops processing.
Explanation
User response
The size of the ECSA work area allocated by TAM
differs from that expected by module TAG. None.
KGW0811E XMI CROSS MEMORY COMPONENT
System action HAS ABENDED
stops processing with a U0766 ABEND. Explanation
The cross memory interface task abended.
User response
KGW0800I XMI CROSS MEMORY COMPONENT The XMI task stops processing.
IS ACTIVE
User response
Explanation
Generate a system memory dump and contact IBM
The Cross Memory Interface task is now active. Software Support.
KGW0812I XMI CROSS MEMORY COMPONENT
System action RESOURCE CLEANUP IS
None. COMPLETE

None. The cross memory interface task has completed
resource cleanup.
KGW0808I XMI TASK id ALREADY ACTIVE IN
job
System action
Explanation The XMI task stops processing.
A second cross memory interface task was started

User response
while another one is still active. The XM=nn number
is denoted by the id value and the job running the None.
interface task is identified by the job value.
KGW0813E subtask ESTAEX MACRO FAILURE.
RC=rc
System action

The subtask denoted by subtask received a non zero The component stops processing.
return code from the ESTAEX macro; this is usually
caused by a lack of local system queue area (LSQA). User response
See RKGWSLOG for further messages. If problems
System action
KGW0828I XMI task with XM=nn already
active in UNKNOWN. Reconfigure
User response with different agent XMIT number.
The return code (rc) for the ESTAEX macro is described
in the IBM Macro Reference manual. If the error was Explanation
caused by a shortage of available storage, decrease
the agent address space region size and restart the The cross memory component for this XM number
subtask. If problems persist, contact IBM Software has already been activated. Concurrent execution of
Support. cross memory component with the same XMIT is not
permitted.
KGW0818I CLIENT MANAGER TASK
TERMINATION COMPLETE System action
Only one cross memory component may be active
Explanation
in the agent address space. Therefore, creation of
The statistics API component stops processing. concurrent subtasks is prevented.

None. None. Information only message.
KGW0946E module(nnn) AND module(nnn)
User response INCOMPATIBLE
None.
Explanation
KGW0820E SESSION MANAGER TASK
ENVIRONMENT SETUP FAILED The versions of the module value and the module it is
RESPONSE(EINVAL) attempting to load (module) are incompatible.

The statistics API component failed to establish the The loading of the module value and its invoking
session manager task. facility fail.

The component stops processing. Verify that the product installation process completed
successfully, and that module value is in the Tivoli
User response Enterprise Monitoring Agent library.
See RKGWSLOG for further messages. If problems KGW0980E SDWA @ address

Explanation
KGW0821E SESSION MANAGER TASK
ENVIRONMENT SETUP FAILED An abend has occurred, and has been trapped by
RESPONSE(EPERM) OMEGAMON. The MVS Software Diagnostic Area has
been passed to the recovery routine at the location
Explanation displayed.
The statistics API component failed to establish the

session manager task.

System action 15 at the time of the abend; this is shown in
hexadecimal format.
The abend activity continues.
System action
User response
The abend activity continues.
Forward the diagnostic information to IBM Software
Support.
User response
KGW0981E Abend Sxxx Uxxxx has occurred in
modname, Section sectname PSW Forward the diagnostic information to IBM Software
XXXXXXXX XXXXXXXX Support.
KGW0984E Abend location address - adjacent
Explanation storage:
An abend has occurred, and has been trapped by

OMEGAMON. The MVS System and User Completion Explanation
Codes are displayed along with the name of the An abend occurred, and the abend location is shown in
Module and control section (CSECT) where the abend the message. The adjacent storage is in the immediate
occurred and the failing Program Status Word (PSW). vicinity of the abend location identified in the message.

The abend activity continues. The abend activity continues.

Forward the diagnostic information to IBM Software Forward the diagnostic information to IBM Software
Support. Support.
KGW0982E R0-R7 XXXXXXXX XXXXXXXX KGW0985E aaaaaaaa XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX |
XXXXXXXX XXXXXXXX XXXXXXXX cccccccccccccccc|
An abend occurred, and was trapped by OMEGAMON. An abend occurred, and was trapped by OMEGAMON.
The contents of General Purpose Registers 0 through 7 The contents of the 16 bytes at storage location
at the time of the abend; this is shown in hexadecimal aaaaaaaa are displayed in hexadecimal and character
format. format.
If the storage area for display is not accessible in the
System action agent address space, then this line displays aaaaaaaa
The abend activity continues. Not displayable (Protected) |cccccccccccccccc|.
If the storage area for display is not accessible in the
User response target address space, then this line displays aaaaaaaa
Not displayable (TARGET) |cccccccccccccccc|.
Support.
System action
KGW0983E R8-R15 XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX The abend recovery continues.
XXXXXXXX XXXXXXXX XXXXXXXX
User response
Explanation Forward the diagnostic information to IBM Software
An abend occurred, and was trapped by OMEGAMON. Support.
The contents of General Purpose Registers 8 through KGW0986E Storage addressed by GPR xx

An abend occurred, and has been trapped by None.
OMEGAMON. The data at the location addressed
KGW9004I IRA REGISTRATION THREAD IS
by the specified general register are about to be
NOT ACTIVE
displayed.

The abend recovery continues. An attempt was made to stop the IBM Z OMEGAMON
for CICS TG agent thread, but it is not active.
User response
System action
Support. None.
KGW9000I ROUTINE rrrrrrrr INITIALIZATION User response

HAS STARTED
None.
Explanation KGW9005I IRA REGISTRATION THREAD IS
Routine rrrrrrrr has started initialization of IBM Z TERMINATING
OMEGAMON for CICS TG.
Explanation
System action The IBM Z OMEGAMON for CICS TG agent has received
None. a request to stop processing.

None. None.
KGW9002I IRA REGISTRATION THREAD IS User response

ACTIVE
None.
Explanation KGW9006E IRA REGISTRATION THREAD IS
The IBM Z OMEGAMON for CICS TG agent is active. NOT RESPONDING

None. The IBM Z OMEGAMON for CICS TG agent failed to
stop processing within 30 seconds after being notified
to stop.
User response
None. System action
KGW9003I IRA REGISTRATION THREAD After the IBM Z OMEGAMON for CICS TG agent detects
ALREADY ACTIVE the shutdown request, it stops processing.

An attempt was made to start a another IBM Z None.
OMEGAMON for CICS TG agent.
KGW9007I MODULE CSECT ADDRESS DATE
TIME SYSMOD
System action
None.

The message is the header line produced in response The command stops processing.
to a GW DISPLAY MODULES command.
User response
System action
None.
None.
KGW9011E ATC UNABLE TO OBTAIN COMMON
WORK AREA STORAGE
User response
None. Explanation
KGW9008I module csect address date time The OMEGAMON for CICS TG attach controller could
sysmod not acquire its work area.

This message is generated for each CSECT on the None of the OMEGAMON for CICS TG collection
MVS load list in response to a GW DISPLAY MODULES routines function.
command. The six values displayed in this message
include the module, csect, address, date, time, and User response
sysmod associated with each IBM Z OMEGAMON for
CICS TG module loaded from STEPLIB. Increase the amount of memory available to the
agent address space. If problems persist, contact IBM
Software Support.
System action
KGW9012 pthread_create() error
None.

The thread used to monitor active CICS TG regions
None.
could not be started.
KGW9009I phase INITIALIZATION HAS
ENDED System action
None of the OMEGAMON for CICS TG reports or
Explanation
situations function.
The OMEGAMON for CICS TG initialization phase
identified by the phase value has finished. User response
Inspect the logs for a message that might indicate why
System action
the thread failed to start. If problems persist, contact
None. IBM Software Support.
KGW9013E ATC UNABLE TO OBTAIN GWCVT
User response STORAGE
None.
Explanation
KGW9010I ATC NO CICS TG MODULES
APPEAR ON LOAD LIST The system was unable to allocate the IBM Z
OMEGAMON for CICS TG vector table.
Explanation
System action
The GW DISPLAY MODULES command found no
programs on the MVS load list that contained a prefix None of the OMEGAMON for CICS TG collection
of KGW. routines function.

User response KGW9017 IRA MANAGER COMMAND
OPERATOR MISSING
Increase the amount of memory available to the
agent address space. If problems persist, contact IBM
Software Support. Explanation
KGW9014 pthread_detach() error The IRAMAN KGWAGENT modify command directed to
the Tivoli Enterprise Monitoring Agent did not include
an argument.
Explanation
Unused resources associated with the subnode System action
monitoring thread could not be freed.
System action
User response
Resources remain allocated until IBM Z OMEGAMON
for CICS TG stops processing. Enter the correct IRAMAN KGWAGENT aaaaaaaa
modify command.
User response KGW9018 IRA_Subnode_Register ERROR:
RC=aa, Node=bbbbbbbb
None.
KGW9015E ATC entry_point ROUTINE ENTRY Explanation
POINT NOT FOUND
The function used to register CICS TG bbbbbbbb as
online failed with a return code denoted by the aa
Explanation value.
The program used by the attach controller to
start subtasks contains an invalid entry point. The System action
entry_point value denotes the entry point that could
not be located. The CICS TG subnode is not available for situations
and reports.
System action
User response
None of the IBM Z OMEGAMON for CICS TG collection
routines are functioning. Contact IBM Software Support.
KGW9019I ATC INITIALIZATION RTN
User response DIAGNOSTIC DUMP
Explanation
KGW9016 IRA MANAGER COMMAND
UNKNOWN: aaaaaaaa This message provides a heading for work area
displays shown in the RKLVLOG output.
Explanation
System action
The IRAMAN KGWAGENT modify command directed
to the Tivoli Enterprise Monitoring Agent specified an None.
invalid argument as denoted by the aaaaaaaa value.
User response
System action None.
The command is ignored. KGW9021 IRA_Subnode_Deregister ERROR:
RC=aa, Node=bbbbbbbb
User response
Enter the correct IRAMAN KGWAGENT aaaaaaaa
modify command.

The function used to register CICS TG bbbbbbbb as Examine the RKLVLOG output for messages that
offline failed with a return code denoted by the aa can indicate a problem with the register/deregister
value. functions. If problems persist, contact IBM Software
Support.
System action KGW9025 Agent agent WAS UNABLE TO
The CICS TG subnode continues to reflect an online OBTAIN WORK AREA STORAGE
status regardless of it actual state.
Explanation
User response The agent agent value was unable to allocate main
Contact IBM Software Support. memory.
KGW9022E ATC START COMMAND FAILED.

System action
SEE PRIOR MESSAGES
Explanation
User response
The attach controller was unable to start an IBM Z
OMEGAMON for CICS TG function. Consider increasing the agent address space region
size.
System action KGW9026I ATC UNABLE TO DISPLAY CICS TG
The function does not initiate. AGENT DETAIL

Consult the RKLVLOG output for additional messages. The GW DISPLAY command was not able to display
IBM Z OMEGAMON for CICS TG agent detail
KGW9023I ATC COMMAND FORMAT INVALID. information.
SEE PRIOR MESSAGES
System action
Explanation
None.
The attach controller detected a command with invalid
syntax.
User response
System action None.
The command is not processed. KGW9030I ATC PROCESSING THE

FOLLOWING COMMAND:
User response
Explanation
Consult RKLVLOG for additional messages.
This message precedes any command received by the
KGW9024 IRA_Subnode_SendRequest CALL attach controller.
RETURNED WITH aa
System action
Explanation
None.
The function used to submit CICS TG subnode status
has failed with a return code denoted by the aa value.
User response
System action None.
The CICS TG subnode does not reflect the true state of KGW9038E ATC STOP COMMAND FAILED
the region. RC=rc

A GW STOP command could not be processed. A program could not be initiated due to a dispatch
queue problem.
System action
System action
The task is not stopped.
User response
User response
KGW9039E ATC STOP COMMAND FAILED.
INTERNAL ERROR KGW9070I CICS TG/CICS JOBNAME
PARAMETER IS MISSING OR
Explanation INVALID
A GW STOP command could not be processed.

Explanation
System action A GW START, ID=TDA,CICSTG=, or GW START
ID=TDA,CICS= command requires a CICS TG or CICS
The task is not stopped. TS job name, but the job name was not specified.

Contact IBM Software Support. The task does not start.
KGW9040I ATC STATUS COMMAND BEING
PROCESSED User response
Ensure that a valid CICS TG or CICS TS name is passed
Explanation on to the START command.
A request for status has been received. KGW9198I ATC INITIALIZATION FAILED TO
COMPLETE SUCCESSFULLY
System action
Explanation
None.
The IBM Z OMEGAMON for CICS TG attach controller
User response failed to initialize.
None.
System action
KGW9060I ATC THREAD START COMPLETED
None of the IBM Z OMEGAMON for CICS TG collection
SUCCESSFULLY
routines were functioning.

An IBM Tivoli Monitoring Services:Engine thread was
initiated.
None. KGW9199I ATC OPERATOR INTERFACE
DISABLED, RESTART REQUIRED
User response
None.
Explanation
An error caused the attach controller to fail.
KGW9069E ATC TASK START FAILED ON
$DISP ERROR

None of the IBM Z OMEGAMON for CICS TG operator Increase the amount of storage available to the agent
commands works under IBM Tivoli Monitoring address space.
Services:Engine.
KGW9300I ATC STATUS – module; entry_point
User response
Explanation
would explain why the attach controller could not This message displays the entry point of the module
initialize. If problems persist, contact IBM Software module value in response to a GW STATUS,DEBUG
Support. command.
KGW9200E ATO OPERATOR INTERFACE NOT System action

INSTALLED
None.
Explanation
User response
The operator interface was not initialized during IBM
Tivoli Monitoring Services:Engine initialization. None.
KGW9311I ATC STATUS – ATC GW$ATCWK:
System action address
Explanation
User response This message displays the address of the attach
Contact IBM Software Support. parameter list used by the attach controller in
response to a GW STATUS,DEBUG command.
KGW9201E ATO OPERATOR INTERFACE
DISPATCH FAILURE System action
None.
Explanation
The system encountered an internal error when User response
attempting to dispatch the work required to process
an operator command. None.
KGW9312I ATC STATUS – ATC GW$CVT:
System action address
Explanation
User response This message shows the address of the OMEGAMON
Contact IBM Software Support. for CICS Transaction Gateway CVT when a GW
STATUS,DEBUG command is entered.
KGW9202E ATO UNABLE TO OBTAIN
COMMAND PLIST STORAGE System action
None.
Explanation
Memory could not be acquired for the operator User response
command parameter list.
None.
System action KGW9313I ATC STATUS – ATC GW$APARM:
The command is ignored. address

This message displays the attach controller anchor None.
control block address in response to the GW
KGW9317I ATC STATUS – MODULE: module
STATUS,DEBUG command.
ENTRY PT: entry_point
System action
Explanation
None.
This message displays the name and entry point
of each module loaded by the attach controller in
User response response to the GW STATUS,DEBUG command.
None.
System action
KGW9314I ATC STATUS – TASK ID: task_id
None.
Explanation
User response
This message displays the task ID of the active task
started by the attach controller in response to the GW None.
KGW9318I ATC STATUS – TCB: address EOT
ECB: address
System action
None. Explanation
This message displays the address of each TCB
User response (address value) and its corresponding end of task ECB
None. (address value) created by the attach controller in
response to the GW STATUS,DEBUG command.
KGW9315I ATC STATUS – TASK: task_id
System action
Explanation
None.
This message displays the task ID for the active task
started by the attach controller in response to the GW
User response
None.
System action KGW9398I ATC STATUS – NO TASKS
None. CURRENTLY ACTIVE

None. The attach controller could not find any active tasks in
response to a status request.
KGW9316I ATC STATUS – APARM; address
TYPE: type
System action
Explanation None.
This message displays the address and type of attach

User response
parameter lists created by the attach controller in
response to the GW STATUS,DEBUG command. None.
KGW9399I ATC STATUS – NO TASKS STARTED
System action YET
None.

The attach controller has not processed a START See the CICS TG documentation for the correct syntax.
command in response to a status request.
KGW9403I ATC MODIFY – INVALID PORT
NUMBER
System action
None. Explanation
The attach controller has processed a MODIFY ID=SPI
User response command, but an invalid port number was detected.
None.
System action
KGW9400I ATC req_type – SPI SUBTASK NOT
STARTED YET The command stops processing.

A GW MODIFY ID=SPI or GW STATUS ID=SPI See the CICS TG documentation for the correct syntax.
command was issued, but the SPI subtask has not
KGW9405I ATC MODIFY – PORT NUMBER NOT
been started.
NUMERIC
System action
Explanation
None.
command, but the specified port number was not
User response numeric.
None.
System action
KGW9401I ATC MODIFY – INVALID KEYWORD
SPECIFIED The command stops processing.

The attach controller has processed a MODIFY ID=SPI See the CICS TG documentation for the correct syntax.
command, but an invalid keyword was detected.
KGW9406I ATC MODIFY – INTERVAL VALUE
NOT NUMERIC
System action
The command stops processing. Explanation
User response command, but the specified interval value was not
See the CICS TG documentation for available numeric.
keywords for this command.
System action
KGW9402I ATC MODIFY – INVALID SERVER
NAME The command stops processing.

command, but no server name was specified.
KGW9407I ATC MODIFY – INTERVAL VALUE
NOT SPECIFIED
System action

command, but the interval value was not specified.
KGW9411I ATC MODIFY – CICS TG
STATISTICS API DLL TRACING
System action REQUESTED FOR ALL SERVERS
Explanation
User response The attach controller has processed a MODIFY
See the CICS TG documentation for the correct syntax. ID=SPI,CTGTRAC= command to activate the CICS TG
API DLL trace for all monitored daemons.
KGW9408I ATC MODIFY – INTERVAL OF ZERO
NOT VALID
System action
Explanation The command is processed.

User response
command that specifies a zero interval.
To avoid performance degradation, consider enabling
System action the trace for the specific gateway daemon; this can be
achieved by adding the CICS TG job name as the third
The command stops processing. keyword to the MODIFY command.
For example:
User response
GW MODIFY ID=SPI,CTGTRAC=(n,jjjjjjjj)
See the CICS TG documentation for the correct syntax.
Where n is the trace level and jjjjjjjj is the name of the
KGW9409I ATC MODIFY – TRACE OPTION
CICS TG daemon.
NOT SPECIFIED
KGW9700I ATI SUBTASK INITIALIZATION
Explanation TDA NOT FOUND
The attach controller has processed a MODIFY

ID=SPI,CTGTRAC= command, but no tracing option
Explanation
was specified. The system was unable to locate the target descriptor
area used to monitor a CICS TG region.
System action
System action
User response
See the CICS TG documentation for the correct syntax.
User response
KGW9410I ATC MODIFY – TRACE LEVEL NOT
NUMERIC KGW9701E ATI SUBTASK MODULE E.P.
MISSING OR INVALID
Explanation
The attach controller has processed a MODIFY
Explanation
ID=SPI,CTGTRAC= command, but the trace level was The program entry point of a module to be started is
not numeric. zero.

The command stops processing. The task does not start.

Contact IBM Software Support. The OMEGAMON for CICS Transaction Gateway attach
controller has acknowledged a request to stop
KGW9889I ATC S0C4 MESSAGES ARE suppressing S0C4 log messages.
ALREADY SUPPRESSED
System action
Explanation
A message is written to the RKLVLOG when CICS TG
The OMEGAMON for CICS Transaction Gateway attach agents experience S0C4 ABEND codes.
controller has received a request to suppress S0C4
log messages, but message suppression is already
enabled. User response
None.
System action
KGW9893I ATC INVALID S0C4 MESSAGE
The GW SUPRS0C4 command is ignored. OPTION SPECIFIED

None. The OMEGAMON for CICS Transaction Gateway attach
controller did not recognize the S0C4 log message
KGW9890I ATC S0C4 MESSAGE suppression option specified in the GW SUPRS0C4
SUPPRESSION ACTIVATED command.

The OMEGAMON for CICS Transaction Gateway attach The GW SUPRS0C4 command is ignored.
controller has acknowledged a request to suppress
S0C4 log messages.
User response
System action Reenter the command with an ON or OFF option.
Messages are not written to the RKLVLOG when a CICS KGW9900I ATC TERMINATION HAS STARTED
TG agent abnormally ends with a S0C4 ABEND code.
Explanation
User response
The OMEGAMONfor CICS Transaction Gateway
None. termination routine now has control.
KGW9891I ATC S0C4 MESSAGE
SUPPRESSION NOT ACTIVE System action
None.
Explanation
The OMEGAMON forCICS Transaction Gateway attach User response
controller received a request to suppress S0C4 None.
log messages, but message suppression was never
enabled. KGW9921I ATC START REJECTED. TASK
ID=task_id CURRENTLY RUNNING.
ONLY ONE COPY PERMITTED AT A
System action
TIME
The GW SUPRS0C4 command is ignored.
Explanation
User response
The OMEGAMON for CICS Transaction Gateway attach
None. controller found an active copy of the task_id value
running in the agent address space.
KGW9892I ATC S0C4 MESSAGE
SUPPRESSION DEACTIVATED

System action KGW9941I function MVS VERSION UNKNOWN
The START command is ignored.
Explanation
User response The subroutine used to determine the operating
system release detected an unsupported release of
None. MVS when called by the function value.
KGW9922E ATC UNABLE TO ATTACH
PARAMETER LIST STORAGE System action
The function identified by the function value does not
Explanation start.
controller could not acquire memory for the ATTACH User response
macro.
System action KGW9942I function GWVRSN FAILURE,
R1=r1, R15=r15
Explanation
User response
The subroutine used to determine the operating
Increase the amount of memory available to the system release failed with the r1 value when called
agent address space. If problems persist, contact IBM by the function value.
Software Support.
KGW9924I ATC FREEMAIN FAILURE FOR IBM System action
Tivoli Monitoring Services:Engine
STORAGE The task does not start.

The system was unable to execute a $FMEM request Contact IBM Software Support.
to release IBM Tivoli Monitoring Services:Engine KGW9943I ATC NO TABLE ENTRY FOR task
managed storage.
Explanation
System action
The attach controller was unable to locate the task
None. value.

None. The task does not start.
KGW9925I ATC TASK-START RESOURCE
ALREADY FREED User response
Verify that you are specifying the correct task name
Explanation (SPI, XMI, XAM, or XTR). If the problem persists,
The system has released resources associated with a contact IBM Software Support.
task. KGW9945I ATC $LOAD ERROR FOR MODULE:
module
System action
None. Explanation
The IBM Tivoli Monitoring Services:Engine service
User response used to load a program failed; the module value is
found.
None.

The task is not started. The attached controller loaded program program.

Contact IBM Software Support. None.
KGW9947E ATC ID= PARM NOT SPECIFIED OR
INVALID User response
None.
Explanation
KGW9989I ATC TRACING HAS BEEN
The ID keyword on the GW command specifies an ACTIVATED
incorrect value.
Explanation
System action
The task does not start. controller has acknowledged a request to turn on
trace.
User response
System action
Correct the task name on the ID parameter and
reenter the command. Tracing of OMEGAMON for CICS Transaction Gateway
is initiated.
KGW9948E ATC ID= PARM LENGTH ERROR
User response
Explanation
None.
The ID keyword on the GW command specifies an
incorrect value. KGW9990I ATC INITIALIZATION HAS ISSUED
ADDITIONAL ERROR MESSAGES
System action
Explanation
User response controller has failed to initialize.
Correct the task name on the ID parameter and

System action
reenter the command.
None of the OMEGAMON for CICS Transaction
KGW9949E ATC INVALID HEADER FORMAT IN Gateway collection routines function.
program
User response
Explanation
The internal module header in program program would explain why the attach controller could not
cannot be validated. initialize. If problems persist, contact IBM Software
Support.
System action
KGW9991I ATC TRACING IS NOT CURRENTLY
The task does not start. ACTIVE

Contact IBM Software Support. The OMEGAMON for CICS Transaction Gateway attach
controller received a request to turn tracing off but
KGW9950I ATC HAS LOADED MODULE:
tracing was never turned on originally.
program

System action KGW9995I ATC TEST REJECTED, XDC(Y) NOT
IN KDSSYSIN
The GW TRACE command is ignored.
Explanation
User response
None. controller has received a TEST command but found
KGW9992I ATC TRACING HAS BEEN that the XDC environment had not been established
DEACTIVATED under the Engine.

The OMEGAMON for CICS Transaction Gateway attach The GW TEST command is ignored
controller has acknowledged a request to turn off
tracing. User response
Place an XDC(Y) control card in the KDSSYSIN
System action member of TLVPARM and restart the Tivoli Enterprise
Tracing of OMEGAMON for CICS Transaction Gateway Monitoring Server address space.
discontinues. KGW9996I ATC NOW INOPERATIVE. RESTART
REQUIRED.
User response
None. Explanation
KGW9993E ATC INVALID TRACE OPTION In order for OMEGAMON for CICS Transaction Gateway
SPECIFIED to collect data, the error that caused the attach
controller to fail must be corrected and the agent
address space restarted.
Explanation
The OMEGAMON for CICS Transaction Gateway System action
attach controller did not recognize the tracing option
specified in the GW TRACE command. This message is for informational purposes only.

The GW TRACE command is ignored. Consult the console log for additional messages that
User response Support.
Reenter the command with an ON or OFF option.
KGW9997E ATC INITIALIZATION CANNOT BE
KGW9994I ATC TRACING IS ALREADY ACTIVE COMPLETED
The OMEGAMON for CICS Transaction Gateway attach An error caused the attach controller to fail.
controller has received a request to activate tracing,
but tracing is already active. System action
System action Gateway collection routines function.
The GW TRACE command is ignored.
User response
User response Consult the console log for additional messages that
None. would explain why the attach controller could not
Support.

KGW9998I ATC OPERATOR INTERFACE IS Explanation
NOW DISABLED
A general environment error occurred during
Intelligent Remote Agent processing.
Explanation
An error caused the attach controller to fail. System action
Operation continues with the next monitored region if
System action appropriate.
Gateway operator commands work under the Tivoli User response
Enterprise Monitoring Agent.
User response KGWAG0102E pppppppp Session locate failed for

jjjjjjjj ASID hhhh with RC=xx
Support. The monitored region's session locate operation failed
KGW9999I ATC TERMINATION HAS ENDED upon return from KGWSAPI Table Services.
Module pppppppp failed to locate address space jjjjjjjj
Explanation with ASID hhhh in the session table. Return code xx
can have one of the following values:
controller has terminated. • 04 = Address space jjjjjjjj with ASID hhhh was not in
the session table.
System action • 08 = The request failed.

• 0C = the request abended.
None.
System action
User response
Operation continues with the next monitored region.
None.
KGWAG0100E cccccccc Extract transaction User response
summary records failed in routine
cccccccc with RC=nn. Return code 04 might occur while a monitored region
is being initialized. If this condition continues, contact
IBM Software Support. If the return code is 08 or 0C,
Explanation contact IBM Software Support.
A failure has occurred during extraction of the KGWAG0103E cccccccc Active Transaction AR
transaction summary records. collector failed in routine cccccccc
with RC=nn.
System action
Extraction of transaction summary records for the Explanation
monitored region is bypassed. Operation continues A failure has occurred upon return from the active
with the next monitored region. transaction AR collector.

Contact IBM Software Support. Extraction of the active transaction information for
KGWAG0101E IRA collection environment the monitored region is bypassed. Operation continues
error routine=cccccccc.cccccccc with the next monitored region.
reason=cccccccc.

Contact IBM Software Support. None. Information only message.
KGWDIO00E Data set I/O error detected - KGWNTR09E cccccccc received return
SYNAD message: codes hhhhhhhh, SYNCHCOMP
hhhhhhhh, SYNCHCODE
Explanation hhhhhhhh, SYNCHRSN hhhhhhhh
from IEAMSCHD.
During a READ operation, a permanent I/O error
was detected on the configuration source member
Explanation
KGWSAPIP in the RKANPARU data set.
IEAMSCHD macro failure.
System action
System action
Processing continues with default configuration
settings. No regions are included for monitoring. The Agent address space was not able to retrieve the
home level name and token, which may have been
User response previously established through the OMEGAMON's user
exit in the monitored region.
The SYNAD message buffer describes the source of
the problem. Take the appropriate action to ensure the
User response
success of I/O operations on the data set.
Ensure that each CICS TG monitored region has been
KGWDMP01I Dump of area at x"xxxxxxxx" with correctly configured to enable the monitoring user
length x"nnnn" follows. exits.
Explanation KGWRDR01I RDR for session ssssssss ASID

aaaa at x"xxxxxxxx_xxxxxxxx".
When preceded by the error message KGWTMI09E,
this message displays a memory dump of a work area,
Explanation
which belongs to the home level name and token
retriever routine (NTR) for OMEGAMON. If preceded The Raw Data Repository for session ssssssss with
by the warning message KGWXTR05W, this message ASID aaaa is located at address xxxxxxxx_xxxxxxxx,
displays the contents of a transaction record and the where:
first flow of that transaction.
• ssssssss is the CICS Transaction Gateway or
WebSphere Application Server jobname.
System action • aaaa is the CICS Transaction Gateway or WebSphere
None. Normal operation continues. Application Server address space ID, in hexadecimal
format.
User response • xxxxxxxx_xxxxxxxx is the address of the Raw Data
Repository in the monitored region.
For possible actions, refer to the text for message
KGWTMI09E or KGWXTR05W.
System action
KGWDMP09I End of dump at x"xxxxxxxx" with
length x"nnnn". None. Informational only message.

This indicates the end of display for a memory location None. Informational only message.
being dumped. KGWRDR02I module The Raw Data Repository
(RDR) for session jjjjjjjj is no longer
System action available.
None. Normal operation continues.

Explanation KGWRTA02E Return code=rrrrrrrr received from
qqqqqqqq request.
The Raw Data Repository for the jjjjjjjj monitored
region is no longer available, possibly due to an error
situation in the monitored region. The issuing module Explanation
is module. A request to expand a cell or expand an extent more
than the bar was unsuccessful.
System action
None. Information only message. System action
Cross memory CICS TG transaction summarizer
User response subtask is not activated.
Review messages in the monitored region to
determine the source of this condition. A likely User response
reason is a mismatch between the components of To accommodate the number of megabytes segments
the transaction monitoring exit, described by message requested, increase the MEMLIMIT= JCL parameter
KGWRM0039E. for the job and/or the SMFPRMxx specification in
KGWRTA00I RTA control area for jjjjjjjj has been SYS1.PARMLIB.
allocated at xxxxxxxx_xxxxxxxx. KGWSPI00I Client Manager Status is
Terminating or Client Manager
Explanation Status is Active
The RTA control area for the jjjjjjjj monitored region
was allocated at the address xxxxxxxx_xxxxxxxx. Explanation
SAPI Client Manager Information message.
System action
None. Information only message. System action
System is either terminating or is active.
User response
None. Information only message. User response
KGWRTA01E Return code=rrrrrrrr and reason None. Information only message.
code=ssssssss received from KGWSPI01I Server=ssssssss, Bind=bbbbbbbb ,
IARV64 REQUEST=GETSTOR for Port=pppp Added to Included
gggggggg segments. Sessions
A request for storage higher than the bar was A request to INCLUDE CICS TG server sssssssss with
unsuccessful. This could be due to a site limitation on port pppp and Bind bbbbbbbb has been serviced.
the amount of storage that can be allocated more than Only the first 32 characters of the Bind address are
the bar. displayed.

Cross memory CICS TG transaction summarizer Request is included.
subtask is not activated.
User response
User response
None. Information only message.
To accommodate the number of megabytes segments
requested, increase the MEMLIMIT= JCL parameter KGWSPI02I Server=ssssssss Port=pppp
for the job and/or the SMFPRMxx specification in Deleted from Included Sessions
SYS1.PARMLIB.

Explanation Could not be opened where dddddddd is the DDName
and mmmmmmmm is a member of the dataset
A request to DELETE CICS TG server ssssssss with in KGWSAPIP. Execution will continue using default
port pppp has been serviced. settings.

Request deletes server from included sessions. System uses default configuration

None. Information only message. None. Information only message.
KGWSPI03I Client=cccccccc SAPI Session KGWSPI05I Anchor_Name=aaaaaaaaaaaaaaa
aaaaaaaaaaa with CICS a Anchor_Token= tttttttttttttttt
TG Server=ssssssss Port=pppp
Bind=bbbbbbb Token=xtttttttt
Explanation
Explanation Status of the client's identifiers where:
The status request information for the SAPI • Anchor_Name is the Name of the token of the IBM Z
connection. These are the values: OMEGAMON for CICS TG Client.
• cccccccc is the OMEGAMON for CICS TG Client name • Anchor_Token is the Contents of the token that
identifies the IBM Z OMEGAMON for CICS TG Client.
• aaaaaaaaaaa states if the connection is established
or terminated
System action
• ssssssss is the CICS TG SAPI Server name
• pppp is the CICS TG SAPI Server Port number Status is shown.
• bbbbbbb is the CICS TG SAPI Bind address.

User response
• tttttttt is 4 hex bytes of the CICS TG statistics API
token. None. Information only message.
The status request information for SAPI connection, KGWSPI06I Client_Interval=iiiii seconds
where only the first 16 characters of the Bind address Client_Loop_Detect= lllll
are displayed.
Explanation
System action
Value of the interval and loop detection limit where:
System shows status information.
• iiiii is the Value of the interval at which the CICS TG
statistics API are interrogated.
User response • lllll is the Number of seconds that triggers loop
None. Information only message. recovery.
KGWSPI04I dddddddd(mmmmmmmm) not

accessible, default options will be System action
used. System shows interval and seconds.

The parameter member used to determine: None. Information only message.
• SAPI_CLIENT_INTERVAL KGWSPI07I Maximum Sessions=sssss
• SAPI_CLIENT_LOOP_DETECT
• SAPI_CLIENT_SESSIONS Explanation
• SAPI_CLIENT_SESSIONS_TIMEOUT Maximum number of sessions to monitor CICS TG,
• SAPI_CLIENT_CLIENT_MESSAGES where sssss is the number of sessions specified.

System action – Pending
System shows maximum sessions. – Unknown

None. Information only message. System displays the session attributes.
KGWSPI08I Include Server=ssssssss

User response
Port=pppp Bind=bbbbbbbb
None. Informational only message.
Explanation KGWSPI10I Server=ssssssss ASID=aaaa
A request to include CICS TG server ssssssss with port Port=ppppp Deleted from
pppp and bind bbbbbbbb was detected. The include monitored sessions
request can be issued with a parameter at initialization
time, or through a MODIFY command. Explanation
• ssssssss is the CICS TG server name. A request to DELETE CICS TG Server ssssssss with port
• pppp is the CICS TG statistics API port number. ppppp has been serviced, where:
• bbbbbbbb is the CICS TG bind address as specified • ssssssss is the CICS TG Server name.
in the CICS TG configuration file (ctg.ini). If omitted, • aaaa is the address space identification number, in
LOCALHOST is assumed. hexadecimal format.
• ppppp is the CICS TG statistics API port number.
System action
System processes request. System action
System deletes the specified monitored session.
User response
None. Information only message. User response
KGWSPI09I Session Name=ssssssss None. Informational only message.
ASID=aaaa Port Number=ppppp
KGWSPI20E Client=cccccccc SAPI session with
Sysname=yyyy Jobname=jjjjjjjj
CICS TG Server ssssssss number
Token=x"tttttttt" Status=uuuuuuuu
of CICS TS regions APPLIDS nnnn
exceeds maximum of mmmm
Explanation
This is an informational message. It displays the Explanation
attributes of a session, where:
The number of CICS APPLIDS returned by the CICS
• ssssssss is the CICS TG server name. TG statistics API exceeds the storage capacity of
• aaaa is the address space identification number, in the requesting client. Processing continues, and the
hexadecimal format. excess APPLIDS are discarded where:
• ppppp is the CICS TG statistics API port number. • cccccccc is the OMEGAMON for CICS TG Client
• yyyy is the SMF ID of the z/OS system where the Name.
CICS TG server runs. • ssssssss is the CICS TG Server name.
• jjjjjjjj is the JOBNAME of the CICS TG server. • nnnn is the number of CICS TS regions APPLIDS
• tttttttt is the token that identifies the connections (CS_LCLIST).
between IBM Z OMEGAMON for CICS TG and the • mmmm is the maximum capacity of the client to
CICS TG server. store APPLIDS.
• uuuuuuuu is the status of the connection, which can
be: System action
– Active The system discards the excess APPLIDS.
– Terminating

User response • oooooooo is the name of the IBM Z OMEGAMON for
CICS TG client attempting to connect to the CICS TG
Contact IBM Software Support with the following: server
• MCS console log when incident occurred • vvvvvvv is the Protocol Version of the IBM Z
• JCL and JESLOG of product JOB environment OMEGAMON for CICS TG Client
• Output of any dumps produced
System action
KGWSPI21E Failed to connect to CICS
TG Server=ssssssss Port=pppp System does not produce statistics for the server.
Bind= bbbbbbb Received Return
Code=x"rrrrrrrr". User response
Contact IBM Software Support with the following:
Explanation
• MCS console log when incident occurred
The CICS TG statistics API server returned a non
zero code in response to the openGatewayConnection • RKGWSLOG contents when incident occurred
request. No statistics are available for the server. • JCL and JESLOG of product JOB environment
These are the values: • Output of any dumps produced
• ssssssss is the CICS TG SAPI server name. KGWSPI23I Trace level n has been ttttttt for
• pppp is the CICS TG statistics API port number. Server=ssssssss Port=pppp.
• bbbbbbb is the CICS TG Bind address.
• rrrrrrrr is the return code received from the server. Explanation
Only the first 16 characters of the Bind address are IBM Z OMEGAMON for CICS Transaction Gateway has
displayed. requested that the CICS TG statistics API at server
ssssssss port pppp start tracing at level n or that
tracing be stopped at CICS TG server ssssssss port
System action number pppp.
System returns a non-zero code.
System action
User response System either stops or starts a trace, tttttttt.
• MCS console log when incident occurred User response
• RKGWSLOG contents when incident occurred None. This is an information message.
• JCL and JESLOG of product JOB environment KGWSPI24W Unexpected return code=xrrrrrrrr
• Output of any dumps produced and reason code=xeeeeeeee
received for function=xff
KGWSPI22E Protocol mismatch CICS object=xoo Server=ssssssss
TG Server=ssssssss Port=pppp port=pppp.
Protocol version=vvvvvvv
Client=ooooooo Protocol
Version=mmmmmmm. Explanation
A non zero return and reason code were received when
Explanation attempting to update the statistics repository for a
CICS TG server where:
The CICS TG statistics API server returned a
protocol version that is incompatible with the IBM • rrrrrrrr is the return code from object manager
Z OMEGAMON for CICS TG version. No statistics are • eeeeeeee is the reason code from object manager
available for the server where:
• ff is the function
• ssssssss is the CICS TG SAPI server name • oo is the type of object
• pppp is the CICS TG statistics API port number • pppp is the CICS TG statistics API port number
• vvvvvvv is the Protocol Version of the CICS TG server

Statistical information for the server are not updated. The system returned a CICS TG statistics API
server return code -132 in response to the
User response openRemoteGatewayConnection request.

User response
Correct the hostname or IP address and restart the
• RKGWSLOG contents when incident occurred agent.
KGWSPI27E The connection attempt was
• Output of any dumps produced refused, Return Code -135.
Bind=bbbbbbbb
KGWSPI25E Unexpected return
code=x"rrrrrrrr" received
from StatsAPI Explanation
function=fffffffffffffffffffffffff
The CICS TG statistics API server returned
server=sssssssss port=pppp.
code -135 was issued in response to the
openRemoteGatewayConnection request. No statistics
Explanation are available for the server. The bbbbbbb value is the
Bind address. Only the first 32 characters of the Bind
A request issued to the CICS TG StatsAPI was
address are printed.
unsuccessful, and returned a non-zero return code
where:
System action
• rrrrrrrr is the return code from StatsAPI server
• ffffffff is the function attempted The system returned a CICS TG statistics API
server return code -135 in response to the
• ssssssss is the CICS TG SAPI server name openRemoteGatewayConnection request.
• pppp is the CICS TG statistics API port number
User response
System action
Correct the hostname or IP address and restart the
System returns a non-zero code. agent.
KGWSPI39I SESSION table element added
User response for Server=ssssssss ASID=aaaa
Port=ppppp Table=tttttttt
CSECT=cccccccc.
• RKGWSLOG contents when incident occurred Explanation
• JCL and JESLOG of product JOB environment A session monitored for statistics or transaction
• Output of any dumps produced activity was added to the SESSION table, where:
KGWSPI26E The hostname was not resolved • ssssssss is the CICS Transaction Gateway or
to a valid IP address Return Code WebSphere Application Server jobname.
132. Bind=bbbbbbbb • aaaa is the CICS Transaction Gateway or WebSphere
Explanation format.
The CICS TG statistics API server returned • ppppp is the CICS TG statistics API port number, or
code -132 was issued in response to the zeros for a WebSphere Application Server.
openRemoteGatewayConnection request. No statistics • tttttttt is the name of the table.
are available for the server. The bbbbbbb value is the • cccccccc is the name of the CSECT issuing the
Bind address. Only the first 32 characters of the Bind message.
address are printed.

Processing continues. If the problem persists, contact IBM Software Support.
KGWSPI76W KGWSAPI Sample Request Failed
User response routine=cccccccc.
Explanation
KGWSPI40I Server=ssssssss ASID=x"aaaa"
may be swapped out or An attempt to obtain CICS TG statistics failed with
terminating. System=x"yyyy" routine cccccccc was not successful.
User=x"uuuu" Reason=x"rrrrrrrr"
System action
Explanation
The current operation failed; the system will attempt
A monitored address space may be swapped out or subsequent operations normally.
terminating, where:
• ssssssss is the CICS Transaction Gateway or User response
• aaaa is the CICS Transaction Gateway or WebSphere
Application Server address space ID, in hexadecimal KGWSPI77I SAPI Object Element data.
format.
• yyyy is the System ABEND Code in hexadecimal Explanation
format. Prints the content of a SAPI Object Element in memory
• uuuu is the user ABEND Code in hexadecimal format. dump format. Each line starts with an offset followed
• rrrrrrrr is the ABEND Reason Code in hexadecimal by hexadecimal data and ends with data in character
format. format.
System action
System action
System prints content in memory dump format.
User response
User response
KGWSPI78I Unable to locate TDA/CET for
KGWSPI73E KGWSAPI Get Keyed cccccccc routine=rrrrrrrr
Sample Request Failed,
routine=aaaaaaaa.bbbbbbbb,
RC=xxxxxxxx RS=yyyyyyyy.
Explanation
The Target Descriptor Area (TDA) or the Exception
Explanation Table entry for a CICS TG region (CET) cannot be
located. This condition occurs when a previously
An attempt to obtain CICS TG statistics has failed. The monitored CICS TG region is no longer active. where:
aaaaaaaa.bbbbbbbb value is the name and label of
the failed routine. The xxxxxxxx value is the return • cccccccc is the name of the CICS TG region (Gateway
code received from the Statistics API. The yyyyyyyy daemon or WebSphere Application Server).
value is the reason code received from the Statistics • rrrrrrrr is the name of the routine where this
API. message was issued.

The current operation failed; attempt subsequent System continues processing, but the CICS TG region
operations normally. identified by the message is no longer monitored.

None. This is an information message. Contact IBM Software Support with the following:
KGWSPI79I Client Manager Task termination in • MCS console log when incident occurred
progress. • RKGWSLOG contents when incident occurred
Explanation
The Client Manager Task is terminating. This is due
KGWSPI83W cccccccc parameter unknown
to a shutdown request, or an error condition. If an
<text>
error condition, check for error messages prior to
KGWSPI79I.
Explanation
System action Unknown keyword parameter specified, where
cccccccc is the Parmfile name and <text> describes the
System shuts down the client manager task.
keyword specification record.
User response
System action
None. This is an information message.
The specification is ignored.
KGWSPI81E 1-115 bytes CTG SAPI Error
Message text User response
None. Keyword specification ignored.
Explanation
KGWSPI84E CEEPIPI cccccccccccccccccccc
SAPI error message produced.
request failed rc=x"xxxx "
subretc=x"xxxx" subrsnc=x"xxxx"
System action subfbc=x"xxxxxxxxxxxxxxxxxxxx"
Error message is displayed as text.
Explanation
User response An LE Environment Request failed. Processing stops
None. Error information message. where:
• ccccccc is the request description
KGWSPI82E Failed to disconnect from CICS
TG Server=ssssssss Port=pppp • rc is the return code from request
Received Return Code=x"rrrrrrrr" • retc is the LE environment return code
• rsnc is the LE environment reason code
Explanation • fbc is the LE environment feedback code
The CICS TG statistics API server returned a non-
zero code in response to the closeGatewayConnection System action
request where:
The processing stops.
• ssssssss displays a return code from StatsAPI server
name
User response
• pppp is the CICS TG statistics API port number
• rrrrrrrr is the return code received from the server Contact IBM Software Support with the following:
Session termination continues. • MCS console log when incident occurred

System action • Output of any dumps produced
System continues shutting down session. KGWSPI85E ccccc error processing ddname
CSECT=cccccccc

Explanation • CSECT is the name of the CSECT issuing message.
Error occurred processing a DDNAME file where: • rc is the return code from Name Token Service.
• ccccccc is the error type OPEN|CLOSE|READ|WRITE|

LOCATE.
System action
• ddname is the name of the allocated file. Processing stops.
• CSECT is where the CSECT error occurred.
User response
System action Contact IBM Software Support with the following:
Processing stops. • MCS console log when incident occurred
User response • Output of any dumps produced
Contact IBM Software Support with the following: KGWSPI88E Unable to Allocate Table=cccccccc
• MCS console log when incident occurred CSECT=cccccccc rc=x"hhhh"
rs=x"hhhh"
Explanation
KGWSPI86E cccccccc entry point failed Unable to Allocate Table Resources where:
EP=cccccccc CSECT=cccccccc
rc=x"hhhh" • Table is the name of Table (SESSION|INCLUDE|
RESGRPID|STATID).
Module Loader system service failed, where: • rc is the return code from the SESSION/INCLUDE/
RESGRPID/STATID table allocate request.
• cccccccc is the service request
• rs is the reason code from the SESSION/INCLUDE/
– LOAD RESGRPID/STATID table allocate request.
– IDENTIFY
• EP is the Entry Point name System action
• CSECT is the name of the CSECT issuing message Processing stops.
• rc is the return code from service
User response
System action Contact IBM Software Support with the following:
Processing stops. • MCS console log when incident occurred
User response • Output of any dumps produced
Contact IBM Software Support with the following: (SYSDUMP,SYSMDUMP)
• MCS console log when incident occurred KGWSPI89S Unable to Deallocate

Table=cccccccc CSECT=cccccccc
rc=x"hhhh" rs=x"hhhh"
KGWSPI87E Name Token Service Failed Explanation
Request=cccccccc CSECT=cccccccc
rc=x"hhhh" Unable to Deallocate Table Resources where:
• Table is the name of Table (SESSION|INCLUDE|
Explanation RESGRPID|STATID).
• CSECT is the name of the CSECT issuing message.
A Name Token Service Request failed where:
• rc is the return code from the deallocate request.
• Request is the Name Token Service Request Type.

• rs is the reason code from the table deallocate User response
request.
information:
System action
• MCS console log when the incident occurred
System cannot deallocate the table resources.
User response
SYSMDUMP)
KGWSPI91W Delete failed for server=ssssssss
• MCS console log when incident occurred ASID=aaaa Port=ppppp
• JCL and JESLOG of product JOB environment Table=tttttttt CSECT=cccccccc
rc=x"hhhh" rs=x"yyyy"
(SYSDUMP,SYSMDUMP)
Explanation
KGWSPI90W Locate failed for server=ssssssss
ASID=aaaa Port=ppppp The DELETE_ELEMENT function of the
Table=tttttttt CSECT=cccccccc KGWSAPI_TABLE_SERVICES failed, where:
rc=x"hhhh" rs=x"yyyy" • ssssssss is the CICS Transaction Gateway or
Explanation • aaaa is the CICS Transaction Gateway or WebSphere
The LOCATE_ELEMENT function of the Application Server address space ID, in hexadecimal
KGWSAPI_TABLE_SERVICES failed, where: format.
• ppppp is the CICS TG statistics API port number, or
zeros for a WebSphere Application Server.
• tttttttt is the name of one of the following tables
where the data is stored:
format. – SESSION
• ppppp is the CICS TG statistics API port number, or – INCLUDE
zeros for a WebSphere Application Server. – RESGRPID
• tttttttt is the name of one of the following tables – RESID
– STATID
– SESSION
• cccccccc is the name of the CSECT issuing the
– INCLUDE message.
– RESGRPID • hhhh is the return code from the delete request in
– RESID hexadecimal format.
– STATID • yyyy is the reason code from the delete request in
hexadecimal format.
• cccccccc is the name of the CSECT issuing the
message.
• hhhh is the return code from the locate request in
System action
hexadecimal format. System will no longer monitor the region identified by
• yyyy is the reason code from the locate request in ASID.
hexadecimal format.
User response
System action Contact IBM Software Support with the following
System will no longer monitor the region identified by information:
ASID. • MCS console log when the incident occurred
SYSMDUMP)

KGWSPI92W Add failed for server=ssssssss • ssssssss is the CICS Transaction Gateway or
ASID=aaaa Port=ppppp WebSphere Application Server jobname.
Table=tttttttt CSECT=cccccccc • aaaa is the CICS Transaction Gateway or WebSphere
rc=x"hhhh" rs=x"yyyy" Application Server address space ID, in hexadecimal
format.
Explanation • ppppp is the CICS TG statistics API port number, or
The ADD_ELEMENT function of the zeros for a WebSphere Application Server.
KGWSAPI_TABLE_SERVICES failed, where: • cccccccc is the name of the CSECT issuing the
message.
System action
Application Server address space ID, in hexadecimal System continues to process, but the region identified
format. by ASID is no longer monitored.
• ppppp is the CICS TG statistics API port number, or
zeros for a WebSphere Application Server. User response
• tttttttt is the name of one of the following tables None. Informational only message.
KGWSPI94E CICS TG discovery failed for
– SESSION
Server=cccccccc CSECT=cccccccc
– INCLUDE rc=x"hhhh" rs=x"hhhh"
– RESGRPID
– RESID Explanation
– STATID Gateway daemon discovery failed where:
• cccccccc is the name of the CSECT issuing the • Server is the name of Server or ALL.
message.
• hhhh is the return code from the add request in
• rc is the return code from CICS TG discovery routine.
hexadecimal format.
• rs is the reason code from CICS TG discovery
• yyyy is the reason code from the add request in
routine.
hexadecimal format.

Processing stops.
System will no longer monitor the region identified by
ASID.
User response
User response Contact IBM Software Support with the following:
Contact IBM Software Support with the following • MCS console log when incident occurred
information: • JCL and JESLOG of product JOB environment
• MCS console log when the incident occurred • Output of any dumps produced
• JCL and JESLOG of product JOB environment (SYSDUMP,SYSMDUMP)
• Output of any dumps produced (SYSDUMP, KGWSPI95E ALESERV failed Request=cccccccc
SYSMDUMP) CSECT=cccccccc rc=x"hhhh"
KGWSPI93I SESSION table element deleted
for Server=ssssssss ASID=aaaa Explanation
Port=ppppp Table=SESSION
An ALESERV request failed, where:
CSECT=cccccccc
• Request is the ALESERV Request type.
The region, identified by ASID, was successfully • rc is the return code from ALESERV.
removed from being monitored. Where:

Processing stops. Contact IBM Software Support with the following:
User response • JCL and JESLOG of product JOB environment
Contact IBM Software Support with the following: • Output of any dumps produced
• MCS console log when incident occurred (SYSDUMP,SYSMDUMP)
• JCL and JESLOG of product JOB environment KGWSPI99E ESTAEX Failed CSECT=cccccccc
• Output of any dumps produced rc=x"hhhh" .
KGWSPI97E ESTAEX Recovery

Explanation
entered CSECT=cccccccc
System=x"hhhh" User=x"hhhh" Unable to set ESTAEX Recovery Environment, where:
Reason=x"hhhhhhhh"
• rc is the return code from ESTAEX.
Explanation
An abend was detected while recovery was active. The System action
following information is provided:
Processing stops.
• CSECT is the name of the CSECT issuing message
• System is the system ABEND Code User response
• User is the user ABEND Code
• Reason is the ABEND Reason Code
System action • JCL and JESLOG of product JOB environment
ESTAE recovery activates.
KGWXTR01E fff failed for
User response cccccccc CtgCorr=x"hhhhhhhhh"
Topology=x"hhhh",
Contact IBM Software Support with the following: Table=cccccccc, rc=x"hhhh"
• MCS console log when incident occurred rs=x"hhhh" CSECT=cccccccc.

Explanation
(SYSDUMP,SYSMDUMP) CICS TG is unable to add an element to the named
table.
KGWSPI98E SDUMPX Failed during Recovery
entered CSECT=cccccccc rc=x"hh"
rs=x"hh" SVCDUMP Diagnostics System action
unavailable. None. Normal operation continues.

SDUMPX Failed during recovery processing, where: Contact IBM Software Support with the following:
• CSECT is the name of the CSECT issuing message. • MCS console log when incident occurred
• rc is the return code from SDUMPX. • JCL and JESLOG of product JOB environment
• rs is the reason code from SDUMPX. • Output of any dumps produced
(SYSDUMP,SYSMDUMP)
System action KGWXTR02I Marker in RDR for session ssssssss
Processing stops. ASID aaaa reset to nnnn.

The Raw Data Repository for session ssssssss ASID No FLOW data is retrieved.
aaaa was successfully reset to match this agent's XM
number, where: User response
Verify that a single CICS TG or WebSphere
Application Server region is not monitored by multiple
• aaaa is the CICS Transaction Gateway or WebSphere OMEGAMON agents.
format. KGWXTR05W Transaction with nnnn flows
from session ssssssss ASID aaaa
• nnnn is the cross memory number, in the format exceeds storage capacity.
XMnn, where nn is the number specified in the
START ID=XMI,XM=nn command for this agent.
Explanation
System action A transaction with nnnn flows cannot be processed
in its entirety. Only the first 54 flows are processed.
None. Informational only message. Where:
• nnnn is the number of flows in the transaction.
User response
• ssssssss is the CICS Transaction Gateway (CICS TG)
None. Informational only message. or WebSphere Application Server jobname.
KGWXTR03W Unable to retrieve data from • aaaa is the CICS Transaction Gateway or WebSphere
INCLUDEd session ssssssss ASID Application Server address space ID, in hexadecimal
aaaa marked with xxxx. This agent format.
is using yyyy.
System action
Explanation
Processing continues. The excess flow records are
The Raw Data Repository for session ssssssss with discarded. A memory dump of the transaction data is
ASID aaaa is marked with the XM number xxxx, but produced following this message.
this agent has been started with XM number yyyy,
where: User response
• ssssssss is the CICS Transaction Gateway (CICS TG)
or WebSphere Application Server jobname.
information:
Application Server address space ID, in hexadecimal • MCS console log when the incident occurred
format. • RKGWSLOG contents when the incident occurred
• xxxx is the XMnn mark in the session's RDR. • JCL and JESLOG of product JOB environment
• yyyy is the cross memory number, in the format • Output of any dumps produced (SYSDUMP,
XMnn, where nn is the number specified in the SYSMDUMP)
START ID=XMI,XM=nn command for this agent.

Chapter 22. KGWRM messages
This information lists the KGWRM messages that are issued within the address space of the monitored
CICS TG for the OMEGAMON for CICS TG on z/OS component.
The OMEGAMON for CICS TG on z/OS component monitoring exit (TxnMonitor) provides its own set of log
and trace messages. If this is a Gateway daemon, the messages are written to the STDERR file by default.
If this is a WebSphere Application Server instance, the messages are written to the SYSPRINT file of the
SERVANT region by default.
KGWRM0003E XWR unable to initialize the trace System action
DCB.
The transaction monitoring exit stops processing.
Explanation
User response
This message is displayed in the MVS system
console. The non-Java component of the transaction Contact IBM Software Support.
monitoring exit was unable to initialize the message KGWRM0031E rrrrrrrr length x"hhhhhhhh"
environment. detected in transaction data,
excess ignored.
System action
Processing continues, however no messages are Explanation
displayed. Routine rrrrrrrr detected a flow record with (hex)
length hhhhhhhh. The maximum length processed is
User response (hex) 00000248, (decimal) 584. The excess data are
discarded.
KGWRM0007E rrrrrrrr ESTAEX macro failure, System action
RC=x"hhhhhhhh".
Explanation
User response
Routine rrrrrrrr received a non-zero return code from
the ESTAEX macro. This is usually caused by a lack of If problems persist, contact IBM Software Support.
LSQA. KGWRM0032E rrrrrrrr unable to obtain record
cell, data lost.
System action
The transaction monitoring exit stops processing. Explanation
Routine rrrrrrrr was unable to allocate storage for a
User response flow record, and the record are discarded.
Increase the amount of CSA available to the system

and restart the session. If problems persist, contact System action
IBM Software Support. Processing continues.
KGWRM0029E rrrrrrrr name/token creation
failed, RC=x"hhhhhhhh". User response
Explanation
KGWRM0033E rrrrrrrr nnnnnnnn records in the
Routine rrrrrrrr attempted to create a name/token ACTIVE queue, mmmmmmmm
entry, but the request failed with (hex) return code records in the READY queue.
hhhhhhhh.

Routine rrrrrrrr displays this message after message The OMEGAMON monitoring exit (TxnMonitor)
KGWRM0032E. It describes how many records remain discovered that the level of the Java component as
in the ACTIVE queue, nnnnnnnn, and how many specified in the CLASSPATH environment variable does
records remain in the READY queue, mmmmmmmm. not match the level of KGWMONxx modules in the
STEPLIB concatenation (&thilev.TKANMODP).
System action
System action
TxnMonitor will no longer process transaction data.
User response
User response
Verify that CLASSPATH and &thilev.TKANMODP are at
KGWRM0034E rrrrrrrr writeDataToStorage called, the same level, then restart the address space.
but name/token was not found.
KGWRM0040I rrrrrrrr trace level nn has been
Explanation requested.
Routine rrrrrrrr was invoked to write a record to the

Explanation
RawDataRepository, but the name/token entry was not
found. The rrrrrrrr routine detected a request to set the trace
level at the nn value.
System action
System action
Processing by the transaction monitoring exit stops.
User response
User response
None, this is an informational message.
KGWRM0036E rrrrrrrr no matching RequestEntry
FLOW found for x"hhhhhhhh", at KGWRM0070E RETRY will attempt cleanup.
x"hhhhhhhh_hhhhhhhh".
Explanation
Explanation
The non-Java component of the transaction
The rrrrrrrr routine received a ResponseExit flow monitoring exit intercepted an abnormal termination.
with the CtgCorrelator (hex) hhhhhhhh value at It will attempt to cleanup resources and exit.
the hhhhhhhh_hhhhhhhh address (hex). However,
the matching RequestExit flow was not previously System action
received.
Processing by the transaction monitoring exit stops.
System action
User response
The ResponseExit flow is discarded. Processing
continues. If problems persist, contact IBM Software Support.
KGWRM0092E rrrrrrrr IARV64 DETACH
User response request failure, RC=x"hhhhhhhh",
If problems persist, contact IBM Software Support. RS=x"hhhhhhhh".
KGWRM0039E Version mismatch. The expected Explanation

Java level is aaaa but the actual
level detected is jjjj. During termination, routine rrrrrrrr attempted to
release the RawDataRepository but received (hex)
return code hhhhhhhh and (hex) reason code
hhhhhhhh.

The transaction monitoring exit stops processing. Processing continues.

If problems persist, contact IBM Software Support. None. This is an informational message.
KGWRM0095I The rrrrrrrr routine was unable to KGWRM0114I The number of transactions swept
verify program name for JOBSTEP this cycle from the RDR is
TCB at x"hhhhhhhh". nnnnnnn.
During termination, the rrrrrrrr routine could not verify nnnnnnn transactions were removed from the
the name of the JOBSTEP TCB program. OMEGAMON active queue during this sweep cycle.

Termination completes without releasing resources. Processing continues

If problems persist, contact IBM Software Support. None.
KGWRM0096I The rrrrrrrr shutdown request will KGWRM1000I OMEGAMON for CICS TG
not be processed. monitoring exit initialization
complete.
Explanation
Explanation
Routine rrrrrrrr displays this message after
KGWRM0095I. The OMEGAMON monitoring exit (TxnMonitor) has
completed the initialization steps and is ready to
System action receive and process flow requests.
No resources are released.

System action
User response Control is returned to CICS TG to allow normal
operations to commence.
KGWRM0100I Initializing module GWXWR at User response
hhhhhhhh, Vvvv ssssssss level L. None. Information only message.
Explanation KGWRM1001E Monitored CICS TG is not running

on z/OS. Disabling TxnMonitor.
The GWXWR component of the CICS TG monitoring
exit is initializing, where:
Explanation
hhhhhhhh
The OMEGAMON for CICS TG TxnMonitor is supported
Is the storage address of GWXWR.
on the z/OS operating system only.
vvv
Is the three-digit version number, such as 510 or
530. System action
ssssssss The TxnMonitor is disabled. The CICS TG continues
Is the sysmod. running.
L
Is the component level, which should be the same
as the level displayed in message KGWRM1998I.
Chapter 22. KGWRM messages 277

User response any one time during the operation of the OMEGAMON
TxnMonitor.
None. The CICS TG TxnMonitor is not compatible with
the operating system this CICS TG is running on.
System action
KGWRM1002E Severe error while registering
TxnMonitor exit. RC = {0}. None.
TxnMonitor will be disabled.
User response
Explanation If the high water mark matches the length of the
An unrecoverable error occurred during the internal queue, there is a chance that flow requests
initialization of the OMEGAMON monitoring exit. may have been lost due to insufficient capacity. In this
For example, load modules were not found or the case or if the high water mark is close to the internal
monitoring exit was unable to acquire the necessary queue length, consider increasing the length of the
resources to run correctly. The supplied return code internal queue.
provides details of the error reported. KGWRM1005E Severe error reported whilst
writing exit data to storage. RC =
System action <return code>. TxnMonitor will be
disabled.
The TxnMonitor is disabled. The CICS TG continues
running.
Explanation
User response An unrecoverable error occurred while the
OMEGAMON monitoring exit was processing data. The
Check the return code and correct the reported supplied return code provides details of the error
problem. The CICS TG needs to be restarted to register reported.
the exit.
KGWRM1003W Non-severe error reported whilst System action
registering TxnMonitor exit. RC
= <return code>. TxnMonitor will The TxnMonitor is disabled. The CICS TG continues
continue. running.

A minor error occurred during the initialization of the Check the return code and correct the reported
OMEGAMON monitoring exit. The supplied return code problem. The CICS TG needs to be restarted to register
provides details of the error reported. the exit.
KGWRM1006W Non-severe error reported whilst
System action registering TxnMonitor exit. RC
= <return code>. TxnMonitor will
The TxnMonitor continues to run. continue.

Check the return code to determine the problem. A minor error occurred while the OMEGAMON
This problem should not affect the operation of the monitoring exit was processing data. The supplied
TxnMonitor. However, if problems persist, correct the return code provides details of the error reported.
configuration. If the settings are changed, start CICS
TG again to register the exit.
System action
KGWRM1004I TxnMonitor internal queue high
water mark was {0} records. The TxnMonitor continues running.

The internal queue high water mark indicates the Check the return code to determine the problem;
greatest amount of flow requests that were stored at this problem should not affect the overall collection
of data. However, if problems persist, correct the

configuration. If settings are changed, start CICS TG System action
again to register the exit.
The length of the internal queue is set as specified by
KGWRM1007E Severe error reported whilst the {0} value.
writing exit data to storage. RC =
<return code>. TxnMonitor will be
disabled.
User response
Explanation KGWRM1010I TxnMonitor internal queue sleep
An unrecoverable error occurred during the shutdown time set to {0} ms.
of the OMEGAMON monitoring exit. The supplied
return code provides details of the error reported. Explanation
The internal queue sleep time represents a value in
System action milliseconds of how often the queue processing thread
The TxnMonitor is disabled. The CICS TG continues checks the internal queue to see if there are any
running. requests to process. If the queue is empty, it waits for
this period of time before testing again.
User response
System action
Check the return code and correct the reported
problem. Start CICS TG again to register the exit. The sleep time of the internal queue monitor is set to
the value as specified by {0}.
KGWRM1008W Non-severe error reported whilst
registering TxnMonitor exit. RC
= <return code>. TxnMonitor will
User response
continue. None. Information only message.
KGWRM1011I KGWRM Trace level set to {0}.
Explanation
A minor error occurred while the OMEGAMON Explanation
monitoring exit was processing data. The supplied
return code provides details of the error reported. This indicates the trace level of the OMEGAMON
request exit. Trace level 4 indicates the most
detailed level of trace. All OMEGAMON monitoring exit
System action messages are prefixed KGWRM.
The TxnMonitor continues to run.
System action
User response The trace level is set to the value as specified by {0}.
Check the return code to determine the problem.
This problem should not affect the overall shutdown User response
process. However, if problems persist, correct the
configuration. If settings are changed, the CICS TG None. Information only message.
needs to be restarted to register the exit. KGWRM1012W TxnMonitor internal queue is full.
KGWRM1009I TxnMonitor internal queue length Exit data will be discarded.
set to {0}.
Explanation
Explanation The internal queue is now full. Any requests that are
The internal queue represents how many unprocessed received are discarded until the queue monitor starts
request flows can be stored at any one moment in processing requests, thereby freeing up space at the
time. If the queue becomes full, then request may be end of the queue.
discarded. The queue length must set to a value that
adequately holds requests relative to the workload of System action
CICS TG.
The latest flow request is discarded by TxnMonitor.

If this persists, consider allocating a larger internal None. You need to upgrade CICS TG to take advantage
queue size to handle this amount of requests. Other of this facility.
arguments that could be changed are decreasing the
KGWRM1016E Attempted to add data to internal
internal queue sleep time or decreasing the internal
queue that is nonexistent or has
queue depth trigger. If settings are changed, the CICS
been closed.
TG will need to be restarted to register the exit.
KGWRM1013I OMEGAMON for CICS TG Explanation
monitoring exit has been stopped.
A flow request was received by the TxnMonitor.
However, the internal queue has either been closed
Explanation
as part of a shutdown or has not yet been created; this
Shutdown of the OMEGAMON request exit data is discarded.
(TxnMonitor) has been completed.
System action
System action
The latest flow request is discarded by TxnMonitor.
Control returns to CICS TG to complete the shutdown.
User response
User response
Verify if the TxnMonitor initialized correctly. If settings
None. Information only message. are changed, the CICS TG needs to be restarted to
register the exit.
KGWRM1014W Unable to parse startup property
{0}. KGWRM1017E Unknown RequestEvent received.
Event will be discarded.
Explanation
Explanation
The startup property specified by the {0} value was
expecting an integer value. The value that was read The RequestEvent sent by the CICS TG is not
was not the correct form. supported by the OMEGAMON monitor. A likely reason
for this is a new version of CICS TG has introduced a
System action new flow type.
This startup property is ignored and the default value

System action
is used.
The request is ignored. The TxnMonitor continues to
User response run.
Check and correct the argument supplied. If settings

User response
are changed, the CICS TG needs to be restarted to
register the exit. Check for any updates to the product that may enable
support for this RequestEvent type.
KGWRM1015W RequestEvent Command is not
supported. Event will be ignored. KGWRM1018I Request received to shut
down OMEGAMON for CICS TG
Explanation monitoring exit.
The "Command" RequestEvent type was introduced in

Explanation
CICS TG V7.2; this version of CICS TG cannot process
the event. The monitoring exit received a request from the
monitored CICS TG to shut down. Typically, this is
System action because the CICS TG itself is shutting down.
The RequestEvent is ignored.

System action Table 8. Return codes for Message KGWRM1019E
The TxnMonitor performs it's normal shutdown (continued)
procedure. Return
code Explanation
User response information. If problems persist, contact
None. Information only message. IBM Software Support.
KGWRM1019E Severe error reported whilst 28 An abend occurred within the native code
setting trace level. RC = {0}. of the OMEGAMON transaction monitoring
TxnMonitor will be disabled. exit when trying to write data. Check
the configuration and the logs for further
information. If problems persist, contact
Explanation IBM Software Support.
An unrecoverable error occurred during the 32 An abend occurred within the native code
configuration of the OMEGAMON monitoring exit. The of the OMEGAMON transaction monitoring
supplied return code provides details of the error exit when trying to acquire storage. Check
reported, where {0} is one of the following: the configuration and the logs for further
Table 8. Return codes for Message KGWRM1019E information. If problems persist, contact
Return
code Explanation 36 An abend occurred within the native code
of the OMEGAMON transaction monitoring
1 There was a problem loading the exit when trying to write data. Check
native code library of the OMEGAMON the configuration and the logs for further
transaction monitoring exit. Check the information. If problems persist, contact
library has been added to the STEPLIB IBM Software Support.
of the monitored CICS TG or WebSphere.
See the "Post installation configuration for 40 An abend occurred within the native code
transaction monitoring support" section of the OMEGAMON transaction monitoring
in the product planning and configuration exit when trying to write data. Check
guide for more details. the configuration and the logs for further
3 An unspecified abend occurred within IBM Software Support.
the native code of the OMEGAMON
transaction monitoring exit. Check the 50 An abend occurred within the native code
configuration and the logs for further of the OMEGAMON transaction monitoring
information. If problems persist, contact exit when trying to write data. Check
IBM Software Support. the configuration and the logs for further
16 An abend occurred within the native code IBM Software Support.
exit when trying to write data. Check 54 There is a version mismatch between
the configuration and the logs for further components that make up the
information. If problems persist, contact OMEGAMON transaction monitoring exit.
IBM Software Support. Check the configuration in both the
CLASSPATH and STEPLIB of the
20 An abend occurred within the native code monitored CICS TG or WebSphere so
of the OMEGAMON transaction monitoring the correct level of kgw_monitor.jar
exit when trying to acquire 64-bit storage. and native libraries are used. See
Check the configuration and the logs for the "Post installation configuration for
further information. If problems persist, transaction monitoring support" section
contact IBM Software Support. in the product planning and configuration
guide for more details.
22 An abend occurred within the native code
exit when trying to write data. Check

System action configuration. If settings are changed the CICS TG
needs to be restarted to register the exit.
The TxnMonitor is disabled. The CICS TG continues
running. KGWRM1021I Ignoring KGW Command: {0}.

Check the return code and correct the reported All OMEGAMON CICS TG commands are prefixed with
problem. The CICS TG needs to be restarted to register KGW. The command in this message is being ignored
the exit. because it is attempting to set properties to the same
value as is currently in use, or because the value
KGWRM1020W Non-severe error reported whilst supplied is not permitted. For example, turning trace
setting trace level. RC = {0}. to level 4 when the trace level is already set to 4
TxnMonitor will continue. would produce this message, as would setting the
orphaned transaction timeout to a value greater than
Explanation 1440 minutes (24 hours).
A minor error occurred during the configuration of the
OMEGAMON monitoring exit. The supplied return code System action
provides details of the error reported, where {0} is one Command is ignored. The TxnMonitor continues
of the following: running.
Table 9. Return codes for Message KGWRM1020W
User response
Return
code Explanation If applicable, correct the value in the command. and
submit the command request again.
4 The repository for storing transaction
records is full. This record will be KGWRM1022W Error reported whilst converting
discarded. Calculations on transaction data. Exit data will be discarded.
performance may be affected due to less Message = {0}.
accurate data to work with. Check to
see if the Active Transaction workspaces Explanation
show a large number of old transaction
and consider adjusting the transaction An unexpected error occurred while processing
sweep policy to remove old transactions. request exit data. Because the state of the data is
unknown and the accuracy not guaranteed, it will be
8 The repository for storing transactions discarded.
was unable to delete a record from
storage. This should have minimal effect
however if occurring persistently may System action
result in loss of storage to write new The exit data supplied by the CICS TG at this exit point
transaction records. is discarded and will not be processed by OMEGAMON
12 The repository for storing transactions for CICS TG.
was unable to delete a record from 64
bit storage. This should have minimal User response
effect however if occurring persistently
may result in loss of storage to write new Check the supplied message for suggestions on how to
transaction records. fix the problem. If settings are changed, the CICS TG
needs to be restarted to register the exit. If problems
persist, contact IBM Support.
System action
KGWRM1023W Unexpected non-numeric value
The TxnMonitor continues running. when converting CICS Return
Code. Value will be reset to 0.
User response
Check the return code to determine the problem.
This problem should not affect the overall collection
of data. However, if problems persist, correct the

CICS return codes should be numeric. There is an CICS TG return codes should be numeric. There is
unlikely chance that a non-numeric value may be an unlikely chance that a non-numeric value may be
returned. In this case, the value was reset to 0. returned. In this case, the value is reset to 0.

The CICS return code is reset to 0 and processing of The CICS TG return code is reset to 0 and processing
this request continues. of this request continues.

Check the flow of data back from CICS is not being Check the flow of data back from CICS TG is not being
corrupted in any way. If problems persist, contact IBM corrupted in any way. If problems persist, contact IBM
Support. Support.
KGWRM1024W Unknown flow type supplied by KGWRM1027W Requested EBCDIC codepage is
monitored CICS TG. unsupported on this system.
The flow type sent by the CICS TG is not supported The OMEGAMON monitoring exit attempted to convert
by the OMEGAMON monitor. A likely reason for this is data into the IBM-1047 EBCDIC codepage but was
a new version of CICS TG has introduced a new flow unable to find the encoding. Data may appear
type. corrupted in the output as codepage conversion has
not taken place.
System action
System action
The flow type is set to "Unknown".
Processing continues using the default codepage for
User response the monitored system.
Check for any updates to the product that may enable

User response
support for this flow type.
If data appears corrupted in the log or on the client
KGWRM1025I TxnMonitor internal queue depth output, such as the Tivoli Enterprise Portal, consult
trigger set to {0}. your system administrator to install the IBM-1047
EBCDIC codepage.
Explanation
KGWRM1028I Orphaned transaction sweep
The depth trigger is a value that, when the internal timeout set to {0} minutes.
queue length reaches, sends a signal to the queue
processor to prompt the processing of data. This
Explanation
happens to avoid the internal queue becoming full and
potentially losing data. The value shown in {0} represents the maximum time
that a transaction is permitted to remain listed on the
System action active transaction table without a flow passing through
this CICS TG instance. This is a configurable value,
The internal queue depth trigger is set to the value as set to {0} minutes by default. When this timeout value
specified by {0}. is exceeded, the "orphaned" transaction is removed
on the next sweep interval. This value, along with
User response the transaction sweep timeout value, provides for the
removal of transaction records that may have become
None. Information only message. orphaned.
KGWRM1026W Unexpected non-numeric value
when converting CICS TG Return
Code. Value will be reset to 0.

The timeout value for orphaned transactions An unrecoverable error occurred while the
remaining on the active transaction table is set to the OMEGAMON monitoring exit was performing an
value specified by {0}. orphaned transaction sweep. The supplied return code
provides details of the error reported. RC can be one of
User response the following:
If the timeout value needs to be changed because Table 10. Return codes for Message KGWRM1031E
the timeout to too long or too short, see the product Return
configuration guide for details. code Explanation
KGWRM1029I Orphaned transaction sweep 1 There was a problem loading the
interval set to {0} minutes. native code library of the OMEGAMON
transaction monitoring exit. Check the
Explanation library has been added to the STEPLIB
of the monitored CICS TG or WebSphere.
The time shown in {0} represents the frequency at See the "Post installation configuration for
which a sweep of the active transaction table is made. transaction monitoring support" section
This value, along with the transaction sweep timeout in the product planning and configuration
value, provides for the removal of transaction records guide for more details.
that may have become orphaned.
3 An unspecified abend occurred within
the native code of the OMEGAMON
System action
transaction monitoring exit. Check the
The interval value for processing a sweep of the active configuration and the logs for further
transaction table is set to the value specified by {0}. information. If problems persist, contact
User response 16 An abend occurred within the native code
If the timeout value needs to be changed because of the OMEGAMON transaction monitoring
the timeout to too long or too short, see the product exit when trying to write data. Check
configuration guide for details. the configuration and the logs for further
KGWRM1030W Unable to parse command value: IBM Software Support.
{0}
Explanation exit when trying to acquire 64-bit storage.
The value specified in the command {0} should be an Check the configuration and the logs for
integer value. The value that was read was not the further information. If problems persist,
correct format. contact IBM Software Support.
System action of the OMEGAMON transaction monitoring
exit when trying to write data. Check
This command request is ignored, and the value for the the configuration and the logs for further
property is unchanged. information. If problems persist, contact
User response
Correct the value in the command and submit the of the OMEGAMON transaction monitoring
command request again. exit when trying to write data. Check
KGWRM1031E Severe error whilst performing information. If problems persist, contact
transaction sweep. RC = {0}. IBM Software Support.
TxnMonitor will be disabled.

Table 10. Return codes for Message KGWRM1031E KGWRM1032W Non-severe error whilst
(continued) performing transaction sweep. RC
= {0}. TxnMonitor will continue.
Return
code Explanation
Explanation
A minor error occurred while the OMEGAMON
monitoring exit was performing an orphaned
exit when trying to acquire storage. Check
transaction sweep. The supplied return code provides
details of the error reported. RC can be one of the
following:
36 An abend occurred within the native code Table 11. Return codes for Message KGWRM1032W
of the OMEGAMON transaction monitoring Return
exit when trying to write data. Check code Explanation
information. If problems persist, contact 4 The repository for storing transaction
IBM Software Support. records is full. This record will be
discarded. Calculations on transaction
40 An abend occurred within the native code performance may be affected due to less
of the OMEGAMON transaction monitoring accurate data to work with. Check to
exit when trying to write data. Check see if the Active Transaction workspaces
the configuration and the logs for further show a large number of old transaction
information. If problems persist, contact and consider adjusting the transaction
IBM Software Support. sweep policy to remove old transactions.
50 An abend occurred within the native code 8 The repository for storing transactions
of the OMEGAMON transaction monitoring was unable to delete a record from
exit when trying to write data. Check storage. This should have minimal effect
the configuration and the logs for further however if occurring persistently may
information. If problems persist, contact result in loss of storage to write new
IBM Software Support. transaction records.
54 There is a version mismatch between 12 The repository for storing transactions
components that make up the was unable to delete a record from 64
OMEGAMON transaction monitoring exit. bit storage. This should have minimal
Check the configuration in both the effect however if occurring persistently
CLASSPATH and STEPLIB of the may result in loss of storage to write new
monitored CICS TG or WebSphere so transaction records.
the correct level of kgw_monitor.jar
and native libraries are used. See
the "Post installation configuration for System action
transaction monitoring support" section
The TxnMonitor continues running.
in the product planning and configuration
guide for more details.
User response
System action Check the return code to determine the problem.
This problem should not affect the overall collection
The TxnMonitor is disabled, and no data is sent to the of data. However, if problems persist, correct the
OMEGAMON monitoring agent. The CICS TG continues configuration. If the settings are changed, start CICS
to run. TG again to register the exit.
KGWRM1998I Build: build_version, TxnMonitor
User response Level: API_level
Check the return code, and correct the reported Explanation:
problem. The CICS TG will need to be restarted to Provides version information about the OMEGAMON
register the exit. XE for CICS TG Request Exit.
System action:

None. System action
User response: The TxnMonitor initializes all defined settings and
For information only. These values should be quoted acquire storage needed for processing of CICS TG flow
as part of any service request made to IBM. requests.
KGWRM1999I Starting OMEGAMON for CICS TG
monitoring exit initialization. User response
Explanation
The OMEGAMON monitoring exit (TxnMonitor) has
been loaded into the CICS TG and starts the
initialization process.

Chapter 23. KGWRM messages
This information lists the KGWRM messages that are issued within the address space of the monitored
CICS TG for the OMEGAMON for CICS TG on z/OS component.
The OMEGAMON for CICS TG on z/OS component monitoring exit (TxnMonitor) provides its own set of log
and trace messages. If this is a Gateway daemon, the messages are written to the STDERR file by default.
If this is a WebSphere Application Server instance, the messages are written to the SYSPRINT file of the
SERVANT region by default.
KGWRM0003E XWR unable to initialize the trace DCB.
Explanation
This message is displayed in the MVS system console. The non-Java component of the transaction monitoring
exit was unable to initialize the message environment.
System action
Processing continues, however no messages are displayed.
User response

Chapter 24. KGWUI messages
This information is a listing of the KGWUI messages generated by the OMEGAMON enhanced 3270 user
interface for the CICS Transaction Gateway component of OMEGAMON for CICS on z/OS.
KGWUI0001I This workspace is available only Explanation
for Gateway daemons.
The CICS TG or WAS regions monitored by
Explanation: OMEGAMON XE for CICS TG on z/OS with version
The CICS TS Regions Overview workspace is not previous to 5.3.0 are shown in the first workspace of
available for WebSphere Application Server regions. the enhanced 3270UI (KOBSTART). However, they are
System action: not supported and you will be unable to navigate to
Navigation to the target CICS region stops. other workspaces.
User response:
System action
Navigation returns to the originating workspace.
KGWUI0002I Address space jjjjjjjj is being
monitored by OMEGAMON for
CICS TG on z/OS Version User response
vv.rr.mm. No further navigation is
supported.

Chapter 25. BG messages
The BG Messages are generated from the OMEGAMON II for CICS component.
BG0001 {BATCH DRIVER|LOGGER|POST BG0007 {BATCH DRIVER|LOGGER|POST
PROCESSOR} ACTIVE PROCESSOR} SWITCH PENDING
The message logging facility is active. The background reporting facility is in the process of
switching recording from one log file to another.
System action
System action
The background reporting facility continues switch
None.
User response
BG0002 {BATCH DRIVER|LOGGER|POST
None.
PROCESSOR} FILE ACTIVATED:
dataset_name BG0008 {BATCH DRIVER|LOGGER|POST
PROCESSOR}MESSAGE LOG FILES
Explanation UNAVAILABLE
This message identifies the data set to which the

Explanation
background reporting facility is writing records.
No log files are available to record messages. Either
System action no valid log files are allocated or all allocated log files
contain old records.
System action
User response
Logging is suspended until one or more allocated log
None. files are cleared with the post processor program
(OCBGUTIL) in the archive procedure.
PROCESSOR} SWITCH ACCEPTED
User response
Explanation Process the filled log files with the OCBGUTIL
procedure. After the logs are cleared, resume
The background reporting facility accepted a request
recording messages by issuing a RESUME or SWITCH
to switch files, and is attempting to switch recording to
request.
another file.
System action PROCESSOR} FLUSH TERMINATED
If one or more empty log files are available, the

Explanation
background reporting facility switches recording to the
file with the lowest ddname. If no empty log files are The background reporting facility rejected a request to
available, message logging is suspended until one or flush buffers because recording was suspended at the
more files are cleared. time the request was made.

None. The request is rejected.

Use the RESUME command to resume recording The background reporting facility received a request
messages. to flush I/O buffers and it has completed flush
processing.
PROCESSOR} FLUSH ACCEPTED
System action
The background reporting facility received a request to
flush buffers. User response
None.
System action
The current I/O buffers are flushed. PROCESSOR} STARTUP COMPLETE

None. The background reporting facility completed start-up
processing and is logging messages.
PROCESSOR} FLUSH PENDING
System action
Explanation The background reporting facility begins to log
messages.
The background reporting facility is in the process of
flushing I/O buffers.
User response
System action None.
Flush processing continues. BG0021 {BATCH DRIVER|LOGGER|POST
PROCESSOR} STOP ACCEPTED
User response
Explanation
None.
BG0013 {BATCH DRIVER|LOGGER|POST stop processing and is terminating.
PROCESSOR} INVALID FLUSH
INTERVAL IGNORED
System action
Explanation The background reporting facility begins shutdown
processing.
The background reporting facility received an invalid
automatic flush interval parameter. The flush interval
should be in the form hh:mm:ss. User response
None.
System action
Automatic flush processing stops processing. PROCESSOR} STOP PENDING

Correct the parameter and restart the background The background reporting facility is in the process of
reporting facility. stopping.
PROCESSOR} LOG FILE FLUSHED System action
The background reporting facility continues shutdown
processing.

User response BG0037 {BATCH DRIVER|LOGGER|POST
PROCESSOR} SUSPEND PENDING
None.
BG0024 {BATCH DRIVER|LOGGER|POST Explanation
PROCESSOR} SHUTDOWN
COMPLETE The background reporting facility is in the process of
suspending message logging.
Explanation
System action
The background reporting facility has completed
shutdown processing. The background reporting facility continues suspend
processing.
System action
User response
The background reporting facility stops processing
normally. None.
User response PROCESSOR} MESSAGE LOGGING
ALREADY SUSPENDED
None.
PROCESSOR} ALREADY
SUSPENDED The background reporting facility received a request
to suspend message logging, but logging was already
suspended.
Explanation
The background reporting facility rejected a request to System action
suspend message logging because logging was already
suspended. The background reporting facility rejects the suspend
request and issues message BG0035.
System action
User response
The background reporting facility rejects the suspend
request. None.
SUSPENDED
None.
PROCESSOR} SUSPEND
ACCEPTED The background reporting facility is not logging
messages.
Explanation
System action
suspend message logging. The background reporting facility accumulates records
until its buffers are depleted, then records are lost.
System action
User response
The background reporting facility suspends message
logging until it receives a request to resume or If logging was suspended because the log files are
switch processing. The background reporting facility full, process the log files with OCBGUTIL. After one or
accumulates messages until its buffers are depleted. more log files are clear, issue the RESUME or SWITCH
command to begin logging again. If the logging was
suspended because a SUSPEND command was issued,
User response issue the RESUME (to use the active file) or SWITCH
None.
Chapter 25. BG messages 293

(to activate a new file) command to begin logging User response
again.
None.
PROCESSOR} RESUME IGNORED BG0043 {BATCH DRIVER|LOGGER|POST
PROCESSOR} MESSAGE LOGGING
NOT SUSPENDED
Explanation
The background reporting facility rejected a request Explanation
to resume message logging (because logging was not
suspended). The background reporting facility received a request to
resume message logging, but message logging was not
suspended.
System action
The background reporting facility rejects the request System action
to resume.
The background reporting facility rejects the resume
request and issues the BG0040 message
User response
None. User response
BG0041 {BATCH DRIVER|LOGGER|POST None.
PROCESSOR} RESUME ACCEPTED
Explanation RESUMED
resume message logging. Explanation
The background reporting facility resumed message
System action logging after being suspended.
The background reporting facility attempts to resume
message logging. If logging was suspended due to System action
a suspend request, the background reporting facility
resumes message logging to the active message log The background reporting facility resumes message
file. If logging was suspended because the active log logging.
file was full, the background reporting facility attempts
to activate a log file. If it successfully activates a log User response
file, logging resumes with the selected file. If it cannot
activate a log file, recording remains suspended. None.
FACILITY FORCED SHUTDOWN
None. COMPLETE
PROCESSOR} RESUME PENDING Explanation
The background reporting facility has completed
Explanation forced shutdown processing. Forced shutdown occurs
The background reporting facility is in the process of as a result of a severe error.
resuming message logging.
System action
System action The background reporting facility stops processing.
The background reporting facility continues
processing. User response
None.

BG0070 {BATCH DRIVER|LOGGER|POST System action
PROCESSOR} SHUTDOWN
REQUESTED WHILE SUSPENDED The background reporting facility reissues the WTOR.

The user is unable to stop the message logging Correct the response.
facility because logging is suspended and messages BG0078 {BATCH DRIVER|LOGGER|POST
are queued. PROCESSOR} STATUS AS OF
yy,ddd hh:mm:ss
System action
The background reporting facility issues this message Explanation
in conjunction with the BG0071 message to prompt This is the start of the background reporting facility
the operator for a decision. status display.

Determine why logging is suspended, and respond to The background reporting facility produces several
the BG0071 message. additional messages which describe its status.
BG0071 REPLY “WRITE” TO RECOVER
RECORDS, OR “QUIT” TO BYPASS User response
None.
Explanation
This message is issued in conjunction with the BG0070 PROCESSOR} END OF STATUS
message.
Explanation
System action
This messages marks the end of the background
If the user responds “WRITE,” the background reporting facility status display.
reporting facility attempts to recover any queued
records prior to shutdown. If the user responds
“QUIT,” the background reporting facility bypasses System action
attempts to recover queued records, and those Processing continues.
records are lost. Any other response causes
theBG0072 message to be issued.
User response
User response None.
If logging was suspended due to log file depletion, BG0080 {BATCH DRIVER|LOGGER|POST
run the archive utility. After it completes, respond PROCESSOR} LOG FILE
“WRITE.” If logging was suspended due to the REACTIVATED
SUSPEND command, reply “WRITE” to resume
recording and shutdown. If immediate shutdown Explanation
is required and the loss of queued records is
unimportant, only respond with “QUIT.” This message displays the name of the data set
to which the background reporting facility is writing
BG0072 {BATCH DRIVER|LOGGER|POST records. The data set identified contains some records
PROCESSOR} INVALID and was the last active log file.
RESPONSE: nnnn
System action
Explanation
The data set becomes the active message log file
The user made an invalid response, nnnn, to an again.
operator request (WTOR).

None. OCBGUTIL does not initialize the specified file.
PROCESSOR} EXPANDING User response
MESSAGE QUEUE. INCREMENT: nn Ensure that LABEL=SUL is on the DD statement when
you allocate the log file.
Explanation
BG0084 LOGGER PHASE: nn
The background reporting facility is expanding its
internal message buffer queue; this message is for Explanation
diagnostic purposes only.
This message indicates an internal error in the
background reporting facility; this is a diagnostic
System action
message.
The background reporting facility increments its
internal message queue by the number indicated in System action
the message.
The background reporting facility stops processing.
User response
User response
None.
PROCESSOR} MESSAGE QUEUE BG0085 LOGGER LOGICAL LOGGER TASK
EXPANSION FAILED. RC: nn NOT RESPONDING
The background reporting facility tried to expand its The background reporting facility accumulation task is
internal message buffer queue but could not. not responding. This is a diagnostic message.

The internal message queue is not expanded. Processing continues.
Messages are lost.
User response
User response
If you get RC=04, you might want to increase the
BG0086 LOGGER PHYSICAL LOGGER TASK
region size. If you get RC=08, summary records are
NOT RESPONDING
logged for the records that would have been lost.
If RC=08, a severe internal problem exists. If an
RC=08 appears or any other code persists, contact Explanation
The background reporting facility recording task is not
BG0083 {BATCH DRIVER|LOGGER|POST responding. This may happen in the event of severe
PROCESSOR} USER HEADER DASD problems. This is a diagnostic message.
LABEL ERROR ON FILE:
dataset_name System action
The background reporting facility switches message
Explanation logging to another log file. The old log file is disabled.
Log file initialization was unable to output a user
header label for the specified log file. This probably User response
happened because LABEL=SUL did not appear on the
DD statement when the log file was allocated. If this problem persists and is not due to DASD
errors or contention problems, contact IBM Software
Support.

BG0087 {BATCH DRIVER|LOGGER|POST FILE SERIALIZATION FAILED:
PROCESSOR} LOG FILE UNKNOWN dataset_name
ERROR: dataset_name
Explanation
Explanation When attempting to activate a message log file, the
An internal error occurred during the selection background reporting facility or post processor was
processing of the specified file by the background unable to obtain an enqueue for the file indicated. This
reporting facility and/or the post processor. happens when the post processor is processing the log
file at the same time the background reporting facility
attempts to activate it or when the post processor
System action
attempts to process an active message log file. This
Processing of this file stops processing. The named file might also happen if multiple collectors attempt to use
is disabled; processing continues with the next file. the same log file at the same time.

Contact IBM Software Support. If the background reporting facility tries to activate
the file while the post processor is processing it,
BG0088 {BATCH DRIVER|LOGGER|POST the background reporting facility disables the file and
PROCESSOR} VARIABLE MESSAGE selects another file. If the post processor tries to
TEXT process an active message log file, processing for that
file stops.
Explanation
This message contains free form diagnostic text. User response
None.
System action
Processing continues. PROCESSOR} MESSAGE LOG
FILE UNAVAILABLE FOR USE:
User response dataset_name

Explanation
The background reporting facility or post processor
PROCESSOR} ABEND: routine1
attempted an enqueue for the indicated file which
routine2 ABEND code
failed. This may also happen if multiple collectors are
using the same log file.
Explanation
The background reporting facility or the post processor System action
has encountered severe problems. This is a diagnostic
The background reporting facility disables the
message where routine1 is the name of the parent
indicated file or the post processor stops processing
task, routine2 is the name of the subtask, and ABEND
that file.
code is the abend code in decimal.
User response
System action
Ensure that only one message logger or post processor
has the data set allocated.
attempts to recover. If recovery is not successful,
processing stops. BG0093 {BATCH DRIVER|LOGGER|POST
PROCESSOR} MESSAGE LOG FILE
User response ATTRIBUTE ERROR: dataset_name

Explanation
During the file selection processing in the background
PROCESSOR} MESSAGE LOG
reporting facility and/or the post processor, the

message log file indicated was found to have invalid BG0096 {BATCH DRIVER|LOGGER|POST
DCB attributes. The log file attributes must be PROCESSOR} LOG FILE REQUIRES
DSORG=PS, RECFM=FB, and BLKSIZE must be a INITIALIZATION: dataset_name
multiple of LRECL.
Explanation
System action
During file selection processing in the background
The background reporting facility disables the reporting facility or the post processor, the indicated
indicated file or the post processor stops processing message log file was not initialized.
that file.
System action
User response
The file is disabled by the background reporting
Ensure that the DCB characteristics of the data set are facility. The post processor automatically initializes the
valid. file.
PROCESSOR} MESSAGE LOG FILE User response
I/O ERROR dataset_name
If this message was issued by the background
reporting facility, you must initialize the file.
Explanation
An I/O error occurred on the log file indicated. PROCESSOR} LOG FILE FORMAT
ERROR: dataset_name
System action
If the background reporting facility issued the
Explanation
message, the file is disabled and message logging is During file selection processing in the background
switched to another file. If the post processor issued reporting facility or the post processor, the indicated
the message, processing stops. message log file was not properly initialized by the
post processor.
User response
Ensure that the DASD media is usable. Delete the
System action
current dataset_name and allocate a new one with the The file is disabled by the background reporting facility
same attributes. or it is initialized by the post processor.
PROCESSOR} LOG FILE VOLUME User response
ERROR: nn
If this message was issued by the background
reporting facility, process the file with the post
Explanation processor to initialize it.
During the background reporting facility or post BG0098 {BATCH DRIVER|LOGGER|POST
processor selection processing, the message log PROCESSOR} ERROR: nn
file indicated was found to have multiple volumes
assigned to it. The background reporting facility does
Explanation
not support multivolume data sets.
System action encountered a severe error. This is a diagnostic
message.
The background reporting facility disables the
indicated file or the post processor stops post
System action
processing of that file.
User response attempts to recover. If it cannot recover, processing
stops.
Ensure that log files are not multivolume data sets.

User response BG0102 GRAPH AND MAXSCALE ARE
INVALID FOR THIS REPORT
FACILITY TERMINATED. REASON This report type does not support the graph or
CODE: nnnn maxscale options.

The background reporting facility is terminating The historical reporter stops processing the current
abnormally. This is a diagnostic message. command and starts to scan for the next valid
command.
System action
User response
The background reporting facility stops.
Correct the command and resubmit the job.
User response BG0103 REPORT TYPE MISSING
Explanation
BG0100 ONLY ONE REPORT TYPE
ALLOWED Report type is required for REPORT command.

REPORT command only supports one report type at a The historical reporter stops processing the current
time. command and starts to scan for the next valid
command.
System action
User response
The historical reporter stops processing the current
command and starts to scan for the next valid Correct the command and resubmit the job.
command. BG0104 xxxxxxxx INVALID WITH xxxxxxxx
REPORT
User response
Correct the command and resubmit the job. Explanation
BG0101 COMBINE KEYWORD NOT VALID The specified option is invalid with selected report.
WITH GRAPH
System action
Explanation The historical reporter stops processing the current
For the daily graph, the value is combined at hourly command and starts to scan for the next valid
intervals. For the weekly graph, the value is combined command.
every 8 hours. For the monthly graph, the value is
combined every 24 hours. User response
System action
BG0105 INVALID KEYWORD FOR CONTROL
The historical reporter stops processing the current COMMAND
command and starts to scan for the next valid
command.
Explanation
User response An invalid keyword was entered with the CONTROL
command.

System action BG0201 GROUP MEMBER NAME OR
SUBNAME IS INCORRECT LENGTH
The historical reporter stops processing the current IN COLUMN n
command.
Explanation
User response The string for the member name was too long for this
group type.
Correct the keyword and resubmit the job.
BG0106 DAILY, WEEKLY, AND MONTHLY System action
ARE MUTUALLY EXCLUSIVE
Command processing stops.
Explanation
User response
You can only use one of the daily, weekly, or monthly
keywords at a time. Correct the command and resubmit the job.
BG0202 TERMINAL GROUP MEMBER NAME
System action MISSING REQUIRED SUBNAME
command and starts to scan for the next valid Explanation
command. A member definition for a terminal group consists of
the originating network name, originating VTAM applid,
User response the VTAM network name, and the CICS terminal ID.
One of these was omitted.
BG0107 MERGE AND NOSORT OPTIONS System action
ARE MUTUALLY EXCLUSIVE
Explanation command.
The combination of the MERGE and NOSORT keywords
is not allowed. User response
System action
BG0210 CANNOT REPORT - NO DEFINED
The historical reporter bypasses processing this GROUPS FOR THE TYPE IN
report. COLUMN n

Change MERGE to NOMERGE, or change NOSORT to A report was requested for a group type which has no
SORT, and rerun the reporter for the bypassed report. groups defined.
BG0200 GROUP ID EXCEEDS 8
CHARACTERS IN COLUMN n System action
Explanation command and starts to scan for the next valid
The name for the group exceeds eight characters. command.

Command processing stops. Use the SET command to define the group before
reporting on it.
User response BG0211 CANNOT REPORT - UNDEFINED
GROUP IN COLUMN n

A report was requested for a group which was not Command processing stops.
defined, although there are some groups defined in
this group type. User response
Correct the group or the group type to show which
System action
group should be cleared.
command and starts to scan for the next valid BG0300 INTERNAL ERROR - ELB
command. CONTAINS INVALID DATA

Use the SET command to define the group before A control block relating to exception filtering was
reporting on it or change the name of the group to one overlaid.
that has been defined.
System action
BG0212 GROUP ID NOT PROVIDED IN
COLUMN n Command processing stops.

A report was requested for a group type, but not a Contact IBM Software Support.
specific group.
BG0301 STORAGE EXCEPTION LIMIT
REQUIRES UNITS IN K IN COLUMN
System action n
The background reporting facility ignores the
command. Explanation
Storage exception criteria must be defined in
User response megabytes or kilobytes.
Correct the command to show the group or groups that
should go into the report. System action
BG0220 CANNOT CLEAR - NO GROUPS OF Command processing stops.
THIS TYPE ARE DEFINED
User response
Explanation
A request was made to clear a group or groups for a
BG0302 THIS EXCEPTION LIMIT
group type in which no groups have been defined.
REQUIRES A UNIT OF TIME IN
COLUMN n
System action
Command processing stops. Explanation
You must specify the limit for this exception criterion in
User response some unit of time (S for seconds, M for minutes, and H
Correct the command to show the group or groups for hours).
which should be cleared.
System action
BG0221 CANNOT CLEAR - UNDEFINED
GROUP IN COLUMN n Command processing stops.

A request was made to clear a group which was not Correct the command and resubmit the job.
defined for this group type.

BG0303 THIS EXCEPTION LIMIT System action
REQUIRES NO UNITS INDICATION
IN COLUMN n Report processing is bypassed.

This exception criterion should be specified as a pure Contact IBM Software Support.
count. BG0403 DECOMPRESSION ERROR IN
BGPREP - TERMINATING REPORT
System action
Command processing stops. Explanation
The reporter encountered an internal error while
User response decompressing data records.

System action
BG0400 ERROR IN PREPROCESS SORT/
COPY - TERMINATING REPORT Report processing is bypassed.

An internal error occurred in building the data for the Contact IBM Software Support.
report. BG0500 UNABLE TO OPEN FILE DDNAME
cccccccc
System action
Report processing stops. Explanation
The file specified could not be opened for processing.
User response
BG0401 I/O ERROR IN PREPROCESS - Report processing stops.
TERMINATING REPORT
User response
An I/O error occurred in building the data for the BG0501 UNABLE TO CLOSE FILE DDNAME
report. cccccccc

Report processing stops. The file specified could not be closed.

Contact IBM Software Support. Report processing stops.
BG0402 COMPRESSION ERROR IN BGPREP
- TERMINATING REPORT User response
Explanation
BG0502 UNABLE TO READ FROM FILE
The reporter encountered an internal error while DDNAME cccccccc
compressing data records.

Explanation BG0599 REPORT CANCELLED DUE TO
UNRECOVERABLE ERROR - SEE
While reading from the specified file, an error was JOBLOG
encountered.
Explanation
System action
An unrecoverable error occurred during report
Report processing stops. processing.

Contact IBM Software Support. Report processing stops.
BG0503 UNABLE TO WRITE TO FILE
DDNAME cccccccc User response
Save the job log, report contents, and any system
Explanation messages. More explanatory error messages will be
While writing to the specified file, an error was written on the job log.
encountered. BG0600 UNRECOVERABLE ERROR WHILE
PROCESSING REPORT cccccccc
System action
An unrecoverable error occurred during report
System action
BG0504 UNABLE TO READ THE INPUT FILE
Report processing stops.
Explanation
User response
An I/O error occurred while the reporter was reading
the input file. Save joblog, report contents, and any system
messages. Contact IBM Software Support.
System action BG0601 INTERNAL ERROR OCCURRED
CODE= xxx
The historical reporter closes the file and continues to
process any other available input files.
Explanation
User response An unrecoverable error occurred during report
processing.
BG0510 DD STATEMENT MISSING FOR System action
FILE cccccc
Explanation
User response
A DD statement is missing in the JCL for the specified
file. Save joblog, report contents, and any system
messages. Contact IBM Software Support.
System action BG0700 ERROR IN SORT PROCESS -
TERMINATING REPORT
User response

An internal error occurred in sorting the data for the Contact IBM Software Support.
report.
BG0705 DECOMPRESSION ERROR IN
BGSORT - TERMINATING REPORT
System action
The historical reporter encountered an internal error
User response while decompressing data records.
Examine the error log for system messages and
contact IBM Software Support. System action
BG0701 I/O ERROR IN SORT PROCESS - Report processing is bypassed.
TERMINATING REPORT
User response
Explanation
An I/O error occurred in sorting the data for the report.
BG0708 FATAL ERROR IN SORT PROCESS -
TERMINATING REPORT
System action
An internal error occurred in sorting the data for the
User response report.
contact IBM Software Support. System action
BG0702 ERROR BGNSORT TERMINATING Report processing stops.
REPORT
User response
Explanation
This error occurs if you included the NOSORT option contact IBM Software Support.
on a REPORT command and an internal error occurred
while processing the REPORT command. BG0750 DATA DECOMPRESSION ERROR
OCCURRED DURING EXIT 15
PROCESSING
System action
Report processing stops. The system generates Explanation
message BG0600 after this message.
One or more errors occurred when the historical
reporter attempted to decompress data records.
User response
Take the actions suggested by message BG0600. System action
BG0704 DECOMPRESSION ERROR IN BGSORT15 continues until all records have been
BGNSORT - TERMINATING processed, at which time messages BG0751 and
REPORT BG0752 are written to the log.

The historical reporter encountered an internal error A small quantity of error records may be acceptable to
while decompressing data records. you. If not, contact IBM Software Support.
BG0751 RECORDS PROCESSED = nnnnnn
System action
Report processing is bypassed.

Explanation processed, at which time return code 16 and
messages BG0761 and BG0762 are written to the log.
Message indicates the total number of records
processed by BGSORT15. This message is written
when a data compression error occurs. Message System action
BG0752 will also appear. Processing continues.

Processing continues. A small quantity of error records may be acceptable to
you. If not, contact IBM Software Support.
User response BG0761 RECORDS PROCESSED = nnnnnn
A small quantity of error records may be acceptable to
you. If not, contact IBM Software Support Explanation
BG0752 RECORDS WITH DECOMPRESSION nnnnnn is the total number of records processed
ERRORS = xxxxxx by BGSORT35. This message is written when a
data compression error occurs. Return code 16 and
Explanation message BG0762 will also appear.
Message indicates the total number of records in

which decompression errors occurred. System action
System action
A small quantity of error records may be acceptable
User response to you. If not, you may want to contact IBM Software
Support.
A small quantity of error records may be acceptable to
you. If not, contact IBM Software Support. BG0762 RECORDS WITH COMPRESSION
ERRORS = nnnnnn
BG0753 UNRECOVERABLE ERROR
OCCURRED IN SORT EXIT 15
PROCESSING Explanation
The total number of records for which compression
Explanation errors occurred. Return code 16 and message BG0761
will also appear.
BGSORT15 was unable to continue processing.
System action
System action
Processing stops with abend U1500, and a dump is
produced.
User response
Contact IBM Software Support. BG0763 UNRECOVERABLE ERROR

OCCURRED IN SORT EXIT 35
BG0760 DATA COMPRESSION ERROR PROCESSING
OCCURRED DURING EXIT 35
PROCESSING
Explanation
Explanation BGSORT35 was unable to continue processing.
One or more errors occurred when the historical

reporter attempted to compress data records.
BGSORT35 continues until all records have been

System action BG0903 NO MATCHING SYSTEM RECORDS
FOUND
Processing stops with abend U3500 and a dump is
produced.
Explanation
User response No records processed in the input file match the report
request.
BG0900 NO TRANSACTION DATA WAS System action
PROCESSED
No system reports are processed.
Explanation
User response
No data fit the specified report type and data selection
criteria. None.
System action PROCESSOR} LOG FILE
AVAILABLE: dataset_name
No report is produced and the job output reflects zero
records selected.
Explanation
User response The indicated log file is empty. No further processing is
done for this file.
Change the report type and/or data selection criteria.
BG0901 NO SYSTEM DATA WAS System action
PROCESSED
The background reporting facility bypasses processing
for this file.
Explanation
No system records were present in the input file. User response
None.
System action
No system data will be printed on this report. PROCESSOR} LOG FILE INPUT
DSN: dataset_name
User response
None. System records were not present in the input Explanation
file. The post processor selects the indicated log file for
BG0902 NO MATCHING DATA RECORDS processing.
FOUND
System action
Explanation The post processor copies the data to the archive file,
There were no records processed in the input stream clears the file by writing null records, and updates the
that match the report request. header label to indicate the file was processed.

No records are processed. None.
User response PROCESSOR} ARCHIVE OUTPUT
DSN: dataset_name
Verify that data exists for this report or modify the
report request.

Explanation message to the data set identified in the BG1102
message.
The post processor uses the indicated output file to
archive (copy) the log file.
System action
System action The post processor initializes the log file.
The post processor selects the indicated file for

processing. User response
None.
None. PROCESSOR} LOG FILE RESET
COMPLETE
PROCESSOR} LOG FILE COPY IN
PROGRESS Explanation
The post processor completed the process of clearing
Explanation records from the data set identified in the BG1101
message.
The post processor is starting the process of copying
data records from the data set identified in the
BG1101 message to the data set identified in message System action
BG1102. The post processor proceeds to the next file.

The post processor begins the copying process. None.
User response PROCESSOR} LOG FILE RESET
None. DSN: dataset_name

PROCESSOR} LOG FILE RESET IN Explanation
PROGRESS The post processor is about to clear the log file
indicated.
Explanation
The post processor is starting the process of clearing System action
the data set identified in the BG1110 message. The post processor clears the log file.

The post processor begins the log file initialization None.
process.
PROCESSOR} LOG FILE ACTIVE,
User response COPY TERMINATED
None.
PROCESSOR} LOG FILE COPY The logging facility is currently using this log file.
COMPLETE Therefore, the post processor cannot copy records
from it.
Explanation
The post processor completed the process of copying
records from the data set identified in the BG1101

The post processor stops the copying process; this is a Ensure that only one post processor procedure is
normal situation. active with the archive file data set name.
User response PROCESSOR} LOG FILE I/O
None. This is an informational message only. ERROR, COPY TERMINATED

Explanation
PROCESSOR} LOG FILE ACTIVE,
RESET TERMINATED The post processor is terminating the process of
copying records from the data set indicated in the
Explanation BG1101 message because of an I/O error on the input
log file.
The background reporting facility is currently using this
log file. Therefore, the post processor cannot clear it.
System action
System action The post processor stops processing.
The post processor stops the clearing process.

User response
User response Check the job log and SYS1.LOGREC for I/O errors. If
you find errors, delete, reallocate, and initialize the log
None. file. If you find no error, contact IBM Software Support.
BG1114 {BATCH DRIVER|LOGGER|POST BG1122 {BATCH DRIVER|LOGGER|POST
PROCESSOR} OUTPUT DDNAME PROCESSOR} OUTPUT FILE I/O
ABSENT, PROCESSING ERROR, COPY TERMINATED
TERMINATED
Explanation
Explanation
The post processor is terminating the process of
The post processor is terminating because it cannot copying records to the data set indicated in the
find an output (archive) ddname file. BG1102 message because of an I/O error on the
output (archive) log file.
System action
System action
The post processor stops processing.
User response
User response
Check the post processor JCL to ensure that the
ARCHIVE DD statement is present. Ensure that the output media is valid. A return code
of 04 is a warning that a log file was active when
the archive job ran. This is a normal situation. If the
PROCESSOR} OUTPUT FILE
ACTIVE, PROCESSING
TERMINATED BG1124 {BATCH DRIVER|LOGGER|POST
PROCESSOR} OUTPUT FILE SPACE
Explanation EXHAUSTED, COPY TERMINATED
The post processor is terminating because an enqueue

Explanation
for the output (archive) file failed.
The post processor is terminating the process of
System action copying records to the data set indicated in the
BG1102 message because the output (archive) file is
The post processor stops processing. out of space.

The post processor stops processing. Delete and reallocate the log file. If the problem
persists, contact IBM Software Support.
Allocate another archive file. PROCESSOR} NO FULL OR
PARTIALLY FULL LOG FILE EXISTS
PROCESSOR} LOG FILE COPY
Explanation
FAILED. REASON CODE: nn
The post processor found no data in any of the log
Explanation files.
The process of copying records to the data set

System action
indicated in the BG1101 message has failed.
System action
User response
The post processor does not initialize the log file.
None.
Examine any previous messages to determine why PROCESSOR} UNABLE TO OPEN
processing terminated. A return code of 04 is a ARCHIVE FILE. PROCESSING
warning that a log file was active when the archive job TERMINATED.
ran; this is a normal situation. If the problem persists,
contact IBM Software Support. Explanation
BG1128 {BATCH DRIVER|LOGGER|POST The post processor was unable to open the output
PROCESSOR} LOG FILE RESET (archive) file.
FAILED. REASON CODE: nn
System action
Explanation
The process of clearing the data set indicated in the
BG1101 message failed. User response
Check the JCL. If it is correct, delete and reallocate
System action
the archive file. If the problem persists, contact IBM
The post processor stops processing. Software Support.
User response PROCESSOR} ARCHIVE FILE
Delete and reallocate the log file. If the problem ATTRIBUTE ERROR. PROCESSING
persists, contact IBM Software Support. TERMINATED.

Explanation
PROCESSOR} LOG FILE RESET
BYPASSED. REASON CODE: nn The output (archive) file had invalid DCB attributes.
The DCB attributes must be DSORG=PS, RECFM=FB,
Explanation and BLKSIZE a multiple of LRECL.
The process of clearing the data set indicated in the

System action
BG1101 message failed.
System action

PROCESSOR} DATA
Ensure that the DCB characteristics of the archive file COMPRESSION HAS BEEN
are valid. SUPPRESSED
PROCESSOR}WARNING: ARCHIVE Explanation
FILE IS NOT A GENERATION DATA
GROUP This message indicates that data compression was
suppressed via parm options; records written to the
archive file will not be compressed.
Explanation
The output archive file is not a generation data group. System action
System action
Processing continues; the archive file is used. User response
None.
User response
Use generation data groups for the output archive files. PROCESSOR} DATA
BG1201 {BATCH DRIVER|LOGGER|POST COMPRESSION IS ACTIVE
PROCESSOR} RECORDS READ: nn
Explanation
Explanation This message indicates that records written to the
This message indicates the total number of records archive file are compressed.
read from all processed log files by the post processor.
System action
System action Processing continues.
User response
User response None.
None. BG1205 {BATCH DRIVER|LOGGER|POST
BG1202 {BATCH DRIVER|LOGGER|POST PROCESSOR}% DATA
PROCESSOR} RECORDS WRITTEN: COMPRESSED: nn
nn
Explanation
Explanation This message indicates the percentage of savings
This message indicates the total number of records achieved due to data compression on the archive file.
written to the output (archive) file by the post
processor. System action
System action
None.
User response
Ensure that the number of records written equals the PROCESSOR} COPIES
number of records read (see the BG1201 message). ATTEMPTED: nn
If it does not, examine the previous messages to
determine the source of the discrepancy. See also the
BG1212 message to check if any copies were ended.

This message indicates the total number of log files If the number of copies terminated is greater than
which were selected for copy to the output (archive) zero, examine the previous messages to determine the
file by the post processor. reason the copies were terminated.
System action PROCESSOR} COPIES BYPASSED:
Processing continues. nn

Ensure that the number of copies attempted equals This message indicates the total number of log files
the number of copies completed (see the BG1211 for which copies to the output (archive) file were
message). If it does not, examine the previous bypassed by the post processor.
messages to determine the source of the discrepancy.
See also the BG1212 message to check if any copies System action
were ended.
PROCESSOR} COPIES User response
COMPLETED: nn
If the number of copies bypassed is greater than zero,
examine the previous messages to determine why the
Explanation
copies were bypassed.
This message indicates the total number of log files
which were successfully copied to the output (archive)
PROCESSOR} RESETS
file.
ATTEMPTED: nn
System action
Explanation
This message indicates the total number of log files
that were selected to be cleared by the post processor.
User response
Ensure that the number of copies completed equals System action
the number of copies attempted (see the BG1210
message). If it does not, examine the previous
messages to determine the source of the discrepancy.
See the BG1212 message to check if any copies were User response
terminated.
Ensure that the number of resets attempted equals
BG1212 {BATCH DRIVER|LOGGER|POST the number of resets completed (see the BG1221
PROCESSOR} COPIES message). If it does not, examine the previous
TERMINATED: nn messages to determine the source of the discrepancy.
See message BG1222 to check if any resets were
terminated.
Explanation
This message indicates the total number of log files BG1221 {BATCH DRIVER|LOGGER|POST
for which copies to the output (archive) file were PROCESSOR} RESETS
unsuccessfully terminated by the post processor. COMPLETED: nn

Processing continues. This message indicates the total number of log files
which were reset successfully by the post processor.

Processing continues. The historical reporter continues to the next record.

Ensure that the number of resets completed equals If the number of unusable records is significant,
the number of resets attempted (see the BG12220 contact IBM Software Support.
message). If it does not, examine the previous
messages to determine the source of the discrepancy. BGSMF015 CSRCESRV QUERY ERROR - xx
See also message BG1222 to check if any resets were
terminated. Explanation
BG1222 {BATCH DRIVER|LOGGER|POST The KOCSMF31 program received an unexpected
PROCESSOR} RESETS (non-zero) return code from the z/OS Data
TERMINATED: nn Compression and Expansion service CSRCESRV
FUNCTION=QUERY.
Explanation For more information on the return codes issued by
the CSRCESRV service, see the z/OS MVS Assembler
This message indicates the total number of log files for
Services Reference ABE-HSP.
which resets were unsuccessfully terminated by the
post processor.
System action
System action Conversion processing terminates, producing a return
code of 8.
User response
User response
If the problem cannot be resolved using the
Examine the previous messages to determine the
information on the CSRCESRV service return codes,
reason the resets were terminated.
BGSMF016 CSRCESRV EXPAND ERROR - xx
PROCESSOR} RESETS BYPASSED:
nn
Explanation
Explanation The KOCSMF31 program was unable to expand
the compressed data section for a CICS SMF 110
This message indicates the total number of log files for
monitoring record. This error is issued when the z/OS
which resets were bypassed.
Data Compression and Expansion service CSRCESRV
FUNCTION=EXPAND is unable to expand the data
System action section in the SMF record.
Processing continues. For more information on the return codes issued by
the CSRCESRV service, see the z/OS MVS Assembler
User response Services Reference ABE-HSP.
Examine the previous messages to determine why

System action
resets were bypassed.
Conversion processing terminates; this message is
BG801 nn INVALID RECORDS FOUND -
followed by a z/OS abend U0016 with a dump.
PERFORMANCE DATA FOR NON-
NUMERIC TASK NUMBERS ARE
NOT PROCESSED. User response
Explanation information: JCL and JESLOG of the job, and the
U0016 dump.
Unusable records were found in the log file.

Chapter 26. KC2 messages
This information is a listing of the KC2 messages, which are generated from OMEGAMON II for CICS
component.
KC2EXP Dataset name must not be blank User response
or KLVTBULD rc=rc reason=reason
or member dsn (member) could not None. This is an informational message only.
be opened. rc=rc or member name KC2IMP KLVTBULD failed with rc=rc,
must not be blank or Profile name reason=reason or Member dsn
must not be blank or Profile profile member could not be found or
does not exist. Member dsn member could not
be opened. rc=rc or Member dsn
Explanation member is not a valid profile or
Profile name must not be blank.
A variable message that appears with, and
immediately after the KC2EXPFF message; it explains
the cause of the failure. Explanation
A variable message that appears with, and
System action immediately after, the KC2IMPFF message. It explains
the cause of the failure.
The export fails.
System action
User response
The import fails.
Correct the problem indicated by the message and
retry.
User response
Severity Correct the problem indicated by the message and
retry.
This is a critical error message.
KC2IMPFF Import failed for profile profile.
KC2EXPFF Export failed for profile profile.
Explanation
Explanation
See message KC2IMP.
See message KC2EXP.
System action
System action
See message KC2IMP.
See message KC2EXP.
User response
User response
See message KC2IMP.
See message KC2EXP.
KC2IMP00 Profile profile was imported
KC2EXP00 Profile profile was exported successfully.
successfully.
Explanation
Explanation
The requested profile was imported successfully.
The requested profile was exported successfully.
System action
System action
Profile is imported from the dataset specified in the
Profile is exported to the dataset specified in the command parameter list.
command parameter list.

None. This is an informational message only. Messages prefixed with KC2LG are self-explanatory.
If you are unable to resolve the problem, contact IBM
KC2LG000 -
Software Support.
KC2LG999

Chapter 27. KOCJ messages
This information is a listing of the KOCJ messages which are generated from the OMEGAMON II for CICS
component.
KOCJO001 INITIALIZE COMPLETED User response
NORMALLY.
None.
Explanation
Severity
This facility has initialized successfully.
Confirmation.
System action KOCJO004 INTERFACE SUSPEND

REQUESTED.
Processing continues normally.
Explanation
User response
A request to suspend the facility is being processed.
None.
System action
Severity
The facility stops operations and returns to a
Confirmation. suspended state.
KOCJO002 INTERFACE SHUTDOWN
REQUESTED. User response
None.
Explanation
A request to shut down is being processed. Severity
Confirmation.
System action
KOCJO005 INTERFACE INITIALIZED STATUS:
The facility stops all processing. SUSPENDED.

None. This facility has partially initialized to a suspended
state.
Severity
Confirmation. System action
KOCJO003 INTERFACE SHUTDOWN The facility remains in a suspended state until a
COMPLETED. resume request is processed.

This facility was in a suspended state when a None.
shutdown was requested. The shutdown request has
completed termination of this facility. Severity
Confirmation.
System action
KOCJO006 INTERFACE RESUMED
All processing is stopped. SUCCESSFULLY.

Explanation Severity
A request to resume operations has been processed. User or internal error.
KOCJO009 KOCPLT00 NOT LOCATED. CHECK
System action LINKEDIT.
The facility is now fully initialized and continues
processing normally. Explanation
The facility could not locate entry point KOCPLT00
User response during execution.
None.
System action
Severity The program stops without taking any action.
Confirmation.
User response
KOCJO007 ASSEMBLED AGAINST DIFFERENT
CICS RELEASE. Check that module KOCFI200 that was available
during linkedit of the module; link the module again
Explanation using the supplied JCL.
Initialization failed because the facility determined

Severity
that it was not assembled using the correct CICS
macro libraries. User error.
KOCJO010 FAILURE IN CICS INQUIRE.
System action
Processing stops. Explanation
An unexpected response code was received from an
User response EXEC CICS INQUIRE.
Assemble the facility using the correct CICS macro
libraries. System action
The program stops processing without taking any
Severity action.
User error.
User response
KOCJO008 UNABLE TO DETERMINE START
TYPE. Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is
Explanation in this facility, contact IBM Software Support.
The facility was unable to determine how it was

Severity
invoked. This can occur if the facility was invoked using
a mechanism other than those documented. Internal error.
KOCJO011 KEYWORD UNSUPPORTED,
System action PLEASE REENTER.
action. Explanation
A keyword was entered which is not supported.
User response
Determine how the program was invoked. If this System action
seems to be an error in the facility, contact IBM
Software Support. The program stops without taking any action.

Refer to the documentation for a list of supported Determine why the background transaction is not
keywords. active. If you determine the error is in this facility,
Severity
Severity
User error.
User or internal error.
KOCJO012 JOURNAL NUMBER ERROR.
KOCJO015 INTERFACE ALREADY
Explanation SUSPENDED.
The journal specified in the JOURNUM parameter

Explanation
could not be located in the CICS region.
An attempt was made to suspend this facility when it
System action was already in a suspended state.
The program stops without taking any action.

System action
User response The program stops without taking any action.
Correct the JOURNUM parameter or the Journal

User response
Control Table.
None.
Severity
Severity
User error.
Information.
KOCJO013 OMEGAMON IS ALREADY ACTIVE.
KOCJO016 JOURNAL OPEN ERROR.
Explanation
Explanation
This facility detected that IBM Z OMEGAMON for CICS
was already initialized in this CICS region. An error was detected when attempting to open the
CICS journal.
System action
System action
User response action.
Code the facility program before KOCOME00 in the PLT

User response
or start this facility before an OMEG INIT is issued.
Use AUXTRACE or CEDF to determine the cause of the
Severity unexpected return code. If you determine the error is
in this facility, contact IBM Software Support.
User error.
KOCJO014 SUSPEND TRANSACTION Severity
INACTIVE. User or internal error.
Explanation KOCJO017 INTERFACE ALREADY ACTIVE.
An attempt to suspend the facility was made and the

Explanation
background transaction was not active.
An attempt to initialize or resume this facility was
System action made when it was already active.
Chapter 27. KOCJ messages 317

The program stops without taking any action. An error was detected when attempting to obtain
storage for use as a buffer.
User response
System action
None.
Severity action.
Information.
User response
KOCJO018 EXIT ENABLE ERROR. Check the size of the ECDSA or EDSALIM to ensure
there is enough space for the buffers specified.
Explanation
An error was detected when attempting to enable the Severity
CICS global user exit. User or internal error.
System action KOCJO021 EXIT START FAILURE.

Explanation
action.
An error was detected when attempting to start the
User response CICS global user exit.

System action
in this facility, contact IBM Software Support. The program stops without taking any action.
Severity User response

User or internal error. Use AUXTRACE or CEDF to determine the cause of the
KOCJO019 EXIT EXTRACT ERROR. in this facility, contact IBM Software Support.
An error was detected when attempting to extract User or internal error.
information relating to the CICS global user exit.
KOCJO022 EXIT STOP FAILURE.
Explanation
Explanation
An error was detected when attempting to stop the
User response CICS global user exit.

System action
in this facility, contact IBM Software Support. The program stops processing without taking any
action.
Severity
User response
KOCJO020 GETMAIN FAILURE. unexpected return code. If you determine the error is

User or internal error. Use AUXTRACE or CEDF to determine the cause of the
KOCJO023 FREEMAIN FAILURE.
An error was detected when attempting to release Internal error.
buffer storage.
KOCJO026 TRANSACTION START FAILURE.
System action
Explanation
An error was detected when attempting to start the
User response background transaction.

System action
in this facility, contact IBM Software Support. The program stops processing without taking any
action.
Severity
User response
Internal error.
Ensure that the transaction named in the TRANSID
KOCJO024 EXIT DISABLE FAILURE. keyword is defined to CICS. Use AUXTRACE or CEDF to
determine the cause of the unexpected return code. If
Explanation you determine the error is in this facility, contact IBM
Software Support.
An error was detected when attempting to disable the
CICS global user exit.
Severity
System action User or internal error.
The program stops processing without taking any KOCJO027 INTERFACE INACTIVE.
action.
Explanation
User response
An attempt was made to suspend or shut down this
Use AUXTRACE or CEDF to determine the cause of the feature when it was not active in the system.
System action
Severity The program stops without taking any action.

User response
KOCJO025 FAILURE IN CICS ASSIGN. None.
An error was detected during the processing of an Information.
EXEC CICS ASSIGN command.
KOCJO028 INITIALIZE IS ALREADY IN
System action PROCESS.

Explanation
A request has been issued and an initialization request
is currently in process.

The program stops without taking any action. The program stops without taking any action.

Retry the request at a later time. Retry the request at a later time.
Severity Severity
Information. Information.
KOCJO029 RESUME IS ALREADY IN KOCJO032 UNKNOWN FUNCTION IN
PROCESS. PROCESS.
A request has been issued while a resume request is A request was issued and an unknown function was in
currently in process. progress.


Retry the request at a later time. Contact IBM Software Support.
Severity Severity
Information. Internal error.
KOCJO030 SUSPEND IS ALREADY IN KOCJO033 ERROR OCCURRED DURING
PROCESS. CLEANUP DISABLE.
A request has been issued while a suspend request is An error occurred while attempting to disable the CICS
currently in progress. global user exit after a previous error had occurred.


Retry the request at a later time. Contact IBM Software Support.
Severity Severity
Information. Internal error.
KOCJO031 SHUTDOWN IS ALREADY IN KOCJO034 ERROR OCCURRED DURING
PROCESS. CLEANUP FREEMAIN.
A request has been issued while a shutdown request is An error occurred while attempting to release buffer
currently in process. storage after a previous error had occurred.

The program stops without taking any action. An error was detected when processing an EXEC CICS
WAIT command.
User response
System action
The background task stops.
Severity
User response
Internal error.
KOCJO035 HANDLE ABEND FAILURE. unexpected error. If you determine the error is in this
facility, contact IBM Software Support.
Explanation
An error was detected when processing an EXEC CICS Severity
HANDLE ABEND command. Internal error.
System action KOCJO038 ERROR RECEIVED DURING

FREEMAIN PROCESSING.
Explanation
User response
An error was detected when attempting to release
Use AUXTRACE or CEDF to determine the cause of the buffer storage.
unexpected error. If you determine the error is in this
System action
Severity The background task stops.
Internal error.
User response
KOCJO036 EXIT WORK AREA NOT LOCATED. Use AUXTRACE or CEDF to determine the cause of the
Explanation facility, contact IBM Software Support.
The background transaction was unable to locate the
global user exit work area for this facility. Severity
Internal error.
System action
KOCJO039 JOURNAL WRITE FAILURE.
Explanation
User response
An error was detected while attempting to write a
Use AUXTRACE or CEDF to determine the cause of the completed buffer to the CICS journal.
System action
Severity The background task stops.
Internal error.
User response
KOCJO037 ERROR RECEIVED DURING WAIT Use AUXTRACE or CEDF to determine the cause of the
PROCESSING. unexpected error. If you determine the error is in this

User or internal error. Ensure that MCT field 001, TRAN, is not excluded from
performance records.
KOCJO040 INTERFACE TRANSACTION HAS
ABENDED.
Severity
Explanation User error.
The background task has abended. KOCJO043 TASK NUMBER NOT PRESENT IN
DICTIONARY.
System action
Explanation
The global user exit has determined that the task
User response number field is not present in the dictionary.

System action
facility, contact IBM Software Support. The exit ceases processing.

Internal error. Ensure that MCT field 031, TRANNUM, is not excluded
from performance records.
KOCJO041 RTYPE NOT PRESENT IN
DICTIONARY.
Severity
The global user exit has determined that the RTYPE KOCJO044 NETNAME NOT PRESENT IN
field is not present in the dictionary. DICTIONARY.

The exit ceases processing. The global user exit has determined that the network
name field is not present in the dictionary.
User response
System action
Ensure that MCT field 112, RTYPE, is not excluded
from performance records. The exit ceases processing.

User error. Ensure that MCT field 097, NETNAME, is not excluded
from performance records.
KOCJO042 TRANSID NOT PRESENT IN
DICTIONARY.
Severity
The global user exit has determined that the KOCJO045 UOWID NOT PRESENT IN
transaction ID field is not present in the dictionary. DICTIONARY.

The exit ceases processing. The global user exit has determined that the unit-of-
work ID field is not present in the dictionary.

The exit ceases processing. The exit ceases processing.

Ensure that MCT field 098, UOWID, is not excluded Ensure that the OMEGBSC EMP is defined in the MCT
from performance records. as described in the IBM Software Support. You cannot
change the name of this field when using this facility.
Severity
Severity
User error.
User error.
KOCJO046 OMEGBSC NOT PRESENT IN
DICTIONARY.
Explanation
The global user exit has determined that the
OMEGBSC field is not present in the dictionary.

Chapter 28. OC messages
This information is a listing of the OC Messages, which are generated from OMEGAMON II for CICS
component.
OC0001 ESAA UNABLE TO ACQUIRE System action
SESSION ACCOUNTING AREA
The IBM Z OMEGAMON for CICS subtask in the CICS
region stops processing. Components that depend on
Explanation the data provided by the subtask, such as response
The GETMAIN for an IBM Z OMEGAMON for CICS time collector and ONDV collector, do not function.
control block in CSA (subpool 241) failed.
User response
System action Decrease the region available to the CICS address
The IBM Z OMEGAMON for CICS subtask in the CICS space.
region stops processing. Components that depend on OC0004 SUPR UNABLE TO CONNECT TO
the data provided by the subtask, such as response KOCCInn
time collector and ONDV collector, do not function.
Explanation
User response
An attempt to connect to the IBM Z OMEGAMON for
Increase the amount of CSA available to the system CICS entry table failed.
and restart the session.
OC0002 SUPR UNABLE TO OBTAIN WORK System action
AREA
IBM Z OMEGAMON for CICS subtask in the CICS region
stops processing. Components that depend on the
Explanation data provided by the subtask, such as response time
Communication between CICS and the common collector and ONDV collector, do not function.
interface could not be established due to a work area
GETMAIN failure. User response
Ensure that the cross memory interface task (XMIT) is
System action active as a subtask of the common interface.
The IBM Z OMEGAMON for CICS subtask in the CICS OC0005 SUPR XMIT HAS NOT SET SPACE
region stops processing. Components that depend on SWITCH PC
the data provided by the subtask, such as response
Explanation
User response The cross memory interface task (XMIT) running under
the common interface did not format the program call
Increase the region available to the CICS address necessary for setting up communication between CICS
space. and the KOCCInn address space.
OC0003 SUPR UNABLE TO ESTABLISH
RECOVERY System action
Explanation region stops processing. Components that depend on
The module that sets up communication between the data provided by the subtask, such as response
CICS and KOCCInnn received a non-zero return code time collector and ONDV collector, do not function.
from the ESTAEX macro. This is usually caused by a
lack of LSQA. User response
Ensure that the cross memory interface task (XMIT) is
active as a subtask of the common interface.

OC0006 SUPR UNABLE TO RESERVE OC0009 SUPR UNABLE TO DISCONNECT
LINKAGE INDEX FROM OCCI nn
An attempt to reserve a non-system linkage index with An attempt to disconnect from the IBM Z OMEGAMON
the LXRES macro failed. for CICS entry table failed.

The IBM Z OMEGAMON for CICS subtask in the CICS The IBM Z OMEGAMON for CICS subtask in the CICS
region stops processing. Components that depend on region stops processing. Components that depend on
the data provided by the subtask, such as response the data provided by the subtask, such as response
time collector and ONDV collector, do not function. time collector and ONDV collector, do not function.

OC0007 SUPR UNABLE TO CREATE ENTRY OC0010 SUPR IBM Z OMEGAMON for CICS
TABLE PC CREATE FAILED
An error occurred during the attempt to build a An abend occurred when IBM Z OMEGAMON for CICS
program cal entry table. attempted to establish a cross memory environment
between the common interface and CICS.
System action
System action
region stops processing. Components that depend on The IBM Z OMEGAMON for CICS subtask in the CICS
the data provided by the subtask, such as response region stops processing. Components that depend on
time collector and ONDV collector, do not function. the data provided by the subtask, such as response
User response
User response
OC0008 SUPR UNABLE TO CONNECT
ENTRY TABLE OC0011 XMCR UNABLE TO OBTAIN WORK
AREA
Explanation
Explanation
The ETCON macro generated a nonzero return code
when trying to connect a program call in the CICS Communication between CICS and the common
address space. interface could not be established due to a work area
GETMAIN failure.
System action
System action
region stops processing. Components that depend on The IBM Z OMEGAMON for CICS subtask in the CICS
the data provided by the subtask, such as response region stops processing. Components that depend on
time collector and ONDV collector, do not function. the data provided by the subtask, such a response
User response
User response
Increase the region available to the CICS address
space, or decrease the DSA size.

OC0012 XMCR UNABLE TO ESTABLISH System action
RECOVERY
The oldest records in the buffer are over laid and the
information they contain is lost. The component that
Explanation is losing data is denoted by the aaa value. The display
The module that sets up communication between of this message is limited to a maximum of once every
CICS and KOCCI nn received a nonzero return code five minutes.
from the ESTAEX macro. This is usually caused by a
lack of LSQA. User response
Check that the common interface is running at a
System action dispatching priority greater than that of CICS to ensure
The IBM Z OMEGAMON for CICS subtask in the CICS that records are pulled from the buffer in a timely
region stops processing. Components that depend on manner. The size of the buffer can be increased,
the data provided by the subtask, such as response if necessary, using the XM_BUFFER_RECORDS=
time collector and ONDV collector, do not function. parameter of the KOCGLOB macro in the Global
module.
User response OC0015 XMCR COMPONENT AUTO START

FAILURE
Decrease the region available to the CICS address
space.
Explanation
OC0013 XMCR CROSS MEMORY
INTERFACE TASK INACTIVE One or more of the components marked for auto start
in the Global module could not be initiated.
Explanation
System action
The module that sets up communication between
CICS and KOCCI nn found that the cross memory The auto start logic is not completed.
interface task (XMIT) is not active.
User response
System action Check that the cross memory interface task is active
The IBM Z OMEGAMON for CICS subtask in the CICS under the common interface. Also, examine the
region stops processing. Components that depend on console log for any messages that might indicate why
the data provided by the subtask, such as response the auto starts failed.
time collector and ONDV collector, do not function. OC0016 XMCR UNABLE TO RETRIEVE DATA
FROM KOCGLB
User response
This message could occur if there is an inconsistency Explanation
between the common interface and the monitor. For Data from the Global module could not be moved from
example, the monitor is using a load library with a the KOCCI nn address space to CICS.
different version of IBM Z OMEGAMON for CICS than
the one used by the common interface. Another reason
could be that XMIT (cross memory interface task) is System action
not running as a subtask of the common interface. The IBM Z OMEGAMON for CICS logic that runs in the
OC0014 XMCR COMMUNICATION BUFFER CICS region will not honor the values set in the Global
HAS WRAPPED FOR: aaa module.

Insufficient space was available in the communication Check that the cross memory interface task is active
buffer used to send response time collector and ONDV under the common interface. Also, examine the
collector data from the CICS to the Common Interface. console log for any messages that might indicate why
the data extraction failed.
Chapter 28. OC messages 327

OC0017 XMCR UNABLE TO CROSS User response
MEMORY POST XMIT
Check for messages on the system console. If
Explanation
OC0020 XMST UNABLE TO ALLOCATE
The cross memory communication subtask running in COMMUNICATION BUFFER
the CICS region was unable to POST a task running in
the common interface.
Explanation
System action The GETMAIN macro used to allocate the cross
memory communication buffer more the line in the
The POST failure means that some desired request CICS region returned a non-zero return code.
is not performed by a task running in the common
interface. Such requests include auto starts, Global
data extraction, and notifying either the response time System action
collector or ONDV collector that there is transaction The communication buffer is not allocated.
data to process. Consequently, components that depend on the data
sent via the communication buffer, such as response
User response time collector and ONDV collector, do not function.
Ensure that XMIT is running as a subtask of the

common interface address space. User response
OC0018 XMST CROSS MEMORY SUBTASK Either increase the CICS region size, or decrease the
ABEND: CODE=aaaaaaaa amount of storage required for the communication
buffer by changing the number of records the buffer
holds using the XM_BUFFER_RECORDS= operand of
Explanation the KOCGLOB macro in the Global module.
The subtask used to coordinate communication OC0021 XMST CONNECT TO
between CICS and the common interface has KOCCIaaaaaaaa FAILED.
abnormally terminated with the completion code
denoted by the aaaaaaaa value.
Explanation
System action An attempt to establish communication between CICS
and the OMEGAMON for CICS (3270) interface failed.
Components that depend on the data provided by the The jobname is denoted by the aaaaaaaa value.
subtask, such as response time collector and ONDV
collector, do not function.
System action
User response Components that depend on the communication link
between CICS and the OMEGAMON for CICS (3270)
Inspect the console log for messages that may provide interface, such as the response time collector and
a clue as to why the abend occurred. If problems ONDV collector, do not function.
OC0019 XMST ATTACH FAILED: SYSTEM User response
ERROR
Check the console for any messages that might
explain why CICS and CANSOCnn are unable to
Explanation communicate with one another. Ensure that the
The ATTACH macro used to create the cross memory cross memory interface task (XMIT) is active as a
communication subtask in the CICS region failed. subtask of the OMEGAMON for CICS (3270) interface
jobnameaaaaaaaa.
System action OC0022 XMST COMMON INTERFACE

UNAVAILABLE
Components that depend on the data provided by the
subtask, such as response time collector and ONDV
collector, do not function.

An attempt to establish communication between CICS Initialization continues. Results are unpredictable.
and the OMEGAMON for CICS (3270) interface failed
and the JOBNAME was unavailable. User response
Ensure that the global data area module was
System action
assembled using the same service level as the IBM
Components that depend on the communication link Z OMEGAMON for CICS code within the CICS region.
will not function.
OC0025 XMST PTF aaaaaaa
INCOMPATIBLE WITH XMST PTF
User response bbbbbbb
Verify that the interface is active; see the OC0021
message. Explanation
OC0023 XMCR OMEGAMON-TO-CICS During initialization, IBM Z OMEGAMON for CICS
CONNECTION IN PROGRESS, detected that the service level aaaaaaa of the IBM Z
REPLY CANCEL TO SKIP OMEGAMON for CICS code in the CICS address space
CONNECTION was different from the service level 123 bbbbbbb of
the KOCCInn address space.
Explanation
System action
During CICS initialization, OMEGAMON has waited
more than 30 seconds for a response from the Initialization continues. Results are unpredictable.
OMEGAMON XMIT address space.
If a significant number of CICS systems initialize at User response
the same time, it may take the OMEGAMON XMIT
Ensure that both the CICS address space and the
address space more than 30 seconds to respond
KOCCInn address space are at the same service level.
to some of the initialization requests. This might
cause the OC0023 message to be issued. You can OC0026 OCXMST CICS, KOCCInn AND
circumvent the contention by staggering the CICS GLOBALS MUST BE AT THE SAME
initialization requests so that fewer initializations SERVICE LEVEL
occur simultaneously.
Explanation
System action
This message follows message OC0024 or OC0025.
OMEGAMON waits for an operator response.
System action
User response
Initialization continues. Results are unpredictable.
A reply of cancel will allow CICS initialization to
continue without the cross-memory connection to
User response
OMEGAMON. You can establish this at a later time by
issuing an OMEG INIT from a CICS terminal. See the user response for the preceding OC0024 or
OC0025 messages.
OC0024 XMST KOCGLBcc PTF aaaaaaa
INCOMPATIBLE WITH XMST PTF OC0030 XMCR UNABLE TO PROCESS CICS
bbbbbbb RKC2XM DD STATEMENT
During initialization, IBM Z OMEGAMON for CICS This is an internal error.
detected that the global data area module with the
suffix cc was assembled with PTF aaaaaaa, whereas System action
the cross memory communication code was using PTF
bbbbbbb. Processing stops.

Contact IBM Software Support. An error occurred while IBM Z OMEGAMON for CICS
attempted to read the state management record
OC0031 XMCR WILL USE DEFAULT CICS from the CAVM control file. The function being
RKC2XM NUMBER 00 performed when the error occurred is aaaaaaaaaaa;
the reason code, if any, is only used for dynamic
Explanation allocation. It is a combination of the error reason code
and the information reason code. These codes are
The system uses a default DD of RKC2XM00.
documented in the IBM System Macros Manual. The
return code is dependent on the function encountering
System action the error.
None.
System action
User response The XRF command does not display information
contained in the state management record.
None.
OC0032 XMCR CICS RKC2XM NUMBER User response
INVALID
Check the console to determine whether or not the
dataset is experiencing I/O errors. If problems persist,
An invalid RKC2XM DD card was found in the CICS
OC0063 INPUT NOT NUMERIC
JCL. The CICS RKC2XM number must be blank or a
two-digit number from 00 through 15.
Explanation
System action An invalid character was found where a numerical
value is expected.
The system uses the default CICS RKC2XM number,
00.
System action
User response The command stops processing.
None.
User response
OC0033 XMCR CICS IS USING
RKC2XMnnDD NAME Enter the correct command input.
OC0066 INTERNAL ERROR: UCB/DEV
Explanation POINTERS MISSING
The OMEG INIT has found an RKC2XMnn DD card
defined in the CICS JES JCL deck when it was Explanation
processing.
The exception analysis routine, which looks for
devices that are not responding (DNRS and TNRS),
System action encountered an internal error.
The system uses nn as the RKC2XM number.
System action
User response DNRS and TNRS displays are invalid.
None.
User response
OC0061 XRFD ERROR ENCOUNTERED
DURING ACCESS TO CAVM Contact IBM Software Support.
FILE FUNCTION=aaaaaaaaaaa,
OC0068 GLOBAL AREA (KOCGLB) NOT
REASON=bbbbbbbb, RC=cccccccc
ACCESSIBLE

The GRPS command requires access to the global Specify the requested parameters.
module but was unable to locate it.
OC0073 MODIFY TEXT EXCEEDS
MAXIMUM ALLOWABLE LENGTH
System action
The GRPS command fails. Explanation
The CICM command only accepts a modify command
User response that is 115 characters or less in length.
System action
OC0070 INVALID GROUP SPECIFICATION
Explanation
User response
The affected command expects a group identifier but
found an invalid value. The value must be in the Reduce the length of the modify text and enter the
range 1-maxgrp (maxgrp is the value specified in the command.
KOCGLOB macro).
OC0076 CSWP INVALID OPERAND
SPECIFIED
System action
The CSWP command encountered an invalid keyword.
User response
Correct the group specification and enter the System action
command.
OC0071 INVALID OPTION SPECIFIED, RE-
ENTER User response
Correct the input, and issue the command.
Explanation
The option specified with the command was an invalid OC0082 VALID RANGE FOR VBS IS
keyword. 0-32767

No output is produced by the command. When setting the DEXAN Variable Bucket limit an
invalid value was entered.
User response
System action
Enter the valid command options.
None.
OC0072 NULL INPUT
User response
Explanation
Reenter with a valid value (0-32767).
The affected command is expecting input, but none
OC0083 VALID RANGE FOR THRESH IS 0–
was provided.
99
System action
Explanation
A value for the THRESH operand on the DEX command
has been entered that is outside the acceptable range.

The DEX command ignores the new value. Correct the value and enter it again.
OC0099 INVALID VALUE FOR SPECIFIED
User response PARAMETER
Decide what value in the range 0–99 is required for
the bottleneck analysis display threshold, and enter it Explanation
again
The value provided for a keyword was incorrect.
OC0084 VALID RANGE FOR SHORT IS 0–
LONG TERM, OR CLEAR System action
No output is produced by the command.
Explanation
An invalid SET value for the bottleneck analysis short User response
interval was entered.
Enter the valid keyword values.
System action OC0104 DL/I NOT IN SYSTEM
The command displays the current values for the
bottleneck analysis subtask. Explanation
The DLI or DL1 command was executed and the
User response system was not connected to DL/I. If you are using
Correct the value and enter it again. DBCTL, the region has not attached to DBCTL yet. If
you are using local DL/I support, the CICS you are
OC0085 VALID RANGE FOR LONG IS monitoring does not have DLI=YES in the SIT.
SHORT-TERM-999, OR 0, OR
CLEAR System action
The DLI command fails.
Explanation
An invalid SET value for the bottleneck analysis long User response
interval was entered.
Determine if the system you are monitoring should
have local DL/I support. Determine if you are
System action
connected to DBCTL. If DL/I support does exist, either
The command displays the current values for the local or DBCTL, contact IBM Software Support.
bottleneck analysis subtask.
OC0112 DL/I REMOTE SUPPORT ONLY
User response
Explanation
Correct the value and enter it again.
The DLI or DL1 command was executed and the DL/I
OC0086 CYCLE VALUE MUST BE IN THE support was remote only. Under these circumstances
RANGE 0.1–9.9 SECONDS the DLI command cannot provide any information,
since DL/I is not installed in the region being
Explanation monitored.
An invalid SET value for the bottleneck analysis cycle

System action
timer was entered.
System action
User response
The command displays the current values for the
bottleneck analysis subtask. You may use the TABL PDIR SEL=REM command to
determine the CICS SYSID that owns your PSBs. You
can then monitor DL/I activity by monitoring that CICS.

OC0113 DB STATISTICS BLOCK NOT User response
PRESENT
Check the system log for messages related to a load
failure and determine the release of DLI you are
Explanation running. Then contact IBM Software Support.
The DLI DBD= command was entered and there were OC0117 UNKNOWN CALL TYPE PASSED TO
no DB statistics blocks found. This usually means DL/I DLIC
is not local to the CICS you are monitoring.
Explanation
System action
An internal error has occurred in the IMS collector.
The DLI DBD= command fails.
System action
User response
Enter the DL/I command by itself. If the output is
for DBCTL then no statistics are kept by CICS. If you
receive either message OC0104 or OC0112, then DL/I User response
is not local in this CICS, and no statistics are kept by Contact IBM Software Support.
CICS. If DL/I is local, contact IBM Software Support.
OC0118 DB STATISTICS BLOCK ENTRY NOT
OC0114 DB STATISTICS BLOCK SEARCH FOUND
ERROR
Explanation
Explanation
The DLI DBD=cccccccc command was entered and the
An error occurred while trying to find the DB statistics DB statistics block you requested was not found.
block.
System action
System action
User response
User response
Enter the DLI DBD=* command. This will list the DB
Determine if any storage violations have occurred statistics blocks available. The statistics blocks listed
in your CICS that might have corrupted you DB are the only statistics blocks available.
statistics blocks. Use the STOR VIOLATION command
to determine this. If none have occurred contact IBM OC0119 LOAD FAILED FOR DB2
Software Support. COLLECTOR
OC0115 LOAD FAILED FOR IMS COLLECTOR

Explanation
Explanation A load was attempted for module KOCB nn 0 y where
nn is the release of DB2 you are running (13, 21, or 22)
A load was attempted for module KOCM nnxy where and y is an MVS indicator. The load failed. Please verify
nn is the release of IMS you are running (13, 21, 22, that you are running a supported release of DB2.
or 31), x is a CICS indicator, and y is an MVS indicator.
The load failed. Verify that you are running a supported
release of IMS. The supported releases are release System action
1.3, 2.1, 2.2, and 3.1. The DB2 command fails.

The DLI command fails. Check the system log for messages related to a load
failure and determine the release of DB2 you are
running, then contact IBM Software Support.

OC0132 INVALID KEYWORD SPECIFIED, Explanation
RE-ENTER
The LSR command could not find any LSR pools
allocated to this CICS.
Explanation
An invalid keyword was specified for the affected System action
command.
The LSR command fails.
System action
User response
Verify that you have LSR pools allocated for this CICS
and that they are open. If both of these conditions are
User response true, then contact IBM Software Support.
Correct the keyword and enter the keyword value OC0136 IMS REQUESTED BUT NO IMS/DLI
again. IN THE SYSTEM
OC0133 POOL KEYWORD SPECIFIED
WITHOUT NUMBER Explanation
The LSR command could not find any IMS LSR pools
Explanation allocated to this CICS. When the IMS keyword is
The LSR POOL command was entered without specified for the LSR command, only IMS pools are
specifying a pool number. shown.

The LSR command fails. The LSR command fails.

If you want a summary display for all LSR pools, or Verify that you have IMS LSR pools allocated for
you are not certain which pools are available, enter the this CICS and that they are open. If both of these
LSR command without an argument. If you would like conditions are true, then contact IBM Software
to see details for a specific LSR pool, enter the LSR Support.
command in this format: LSR POOL=1. OC0137 KEYWORD SPECIFIED WITHOUT
OC0134 INVALID LSR POOL ID SPECIFIED ARGUMENT
The LSR POOL requested does not exist for your A keyword of the affected command is expecting an
combination of CICS and IMS. argument, but none was provided.

The LSR command fails. The command stops processing.

If the available LSR pools are used, or you are Supply an argument for the keyword.
not certain which pools are available, enter the LSR OC0138 NO CICS LSR POOLS HAVE BEEN
command without an argument. If you would like to OPENED
see details for a specific LSR pool, enter the LSR
command in this format: LSR POOL=1.
Explanation
OC0135 NO VSAM LSR IN THE SYSTEM
The LSR command could not find any CICS LSR pools
allocated to this CICS. When the CICS keyword is

specified for the LSR command only CICS pools are Explanation
shown.
The argument supplied with the keyword is too
long. For example: the VOLSER is greater than
System action six characters; the ddname is greater than eight
The LSR command fails. characters; or TRANID is greater than four characters.

Verify that you have CICS LSR pools allocated for The command fails.
this CICS and that they are open. If both of these
conditions are true, then contact IBM Software User response
Support.
Enter argument within the valid length limitations.
OC0139 NO IMS LSR POOLS HAVE BEEN
OPENED OC0144 INVALID SELECTION OPTION
SPECIFIED
Explanation
Explanation
The LSR command could not find any IMS LSR pools
allocated to this CICS. When the IMS keyword is The selection criteria specified are invalid. For
specified for the LSR command only IMS pools are example, SELECT=ABCXYZ or SELECT=ACQUIRED on
shown. the TABL command when the table specified is not the
TCT.
System action
System action
The LSR command fails.
The command fails.
User response
User response
Verify that you have IMS LSR pools allocated for
this CICS and that they are open. If both of these Enter a valid (or applicable) criterion.
conditions are true, then contact IBM Software OC0145 ARGUMENT SUPPLIED IS INVALID
Support.
OC0142 NO INDEX COMPONENT LSR Explanation
SUBPOOL
The argument supplied with the keyword is invalid. For
example, DISP=BAD on the FILE command, since BAD
Explanation is not a valid disposition.
The index component for the LSR pool was requested
and there was no index subpool for the LSR pool. System action
The command fails.
System action
The LSR command fails. User response
Enter a valid argument.
User response
OC0146 SPECIFY LIBRARY NUMBER
Verify that you have an index pool allocated for the LSR INSTEAD OF OFFSET
pool. If the LSR pool is allocated with an FCT SHRCNTL
macro rather than CEDA, the index pool option is not
available. If the LSR pool was created using CEDA, Explanation
and index buffers were specified, then contact IBM The data set name specified on the FILE command
Software Support. includes a “+” character directly after the ddname.
OC0143 ARGUMENT SPECIFIED IS TOO Library offsets are not supported but relative library
LONG numbers are.

System action OC0165 XRF IS NOT VALID FOR CICS 1.7
The command fails.
Explanation
User response The XRF command has been issued while monitoring
a CICS 1.7 region. CICS does not support XRF in
Enter the desired file name again, and specify the releases prior to CICS 2.1.
relative library number after the file name, separated
by a comma. If DFHRPL+3 was originally entered,
specify DFHRPL,4 instead. System action
OC0160 TEMPORARY STORAGE The XRF command fails.
COLLECTION ERROR, CODE=nnnn
User response
Explanation None.
An error occurred while the TMPS command was OC0166 PROGRAM CHECK ABEND TRACE
collecting data about temporary storage. TABLE NOT FOUND

The TMPS command fails. The TRAC command was entered with an operand of
PCATT and the Program Check/Abend Trace table base
User response address is zero, but neither exists in CICS/ESA.
System action
OC0163 TRANSIENT DATA COLLECTION
ERROR, CODE= nnnn The command fails.

An error occurred while the TRND command was None.
collecting data about transient data. OC0167 REQUEST IS NOT VALID FOR
CICS/ESA
System action
The TRND command fails. Explanation
The TRAC command was entered with an operand of
User response TRTAB (CICS Trace Table) or PCATT (Program Check/
Abend Trace Table), but neither exists in CICS/ESA.
OC0164 DBCTL IS NOT VALID FOR CICS 1.7 System action
AND 2.1
The command fails.
Explanation
User response
The DLI command with operand of DBCTL has been
issued while monitoring a CICS 1.7 or a CICS 2.1 None.
region. CICS does not support DBCTL in releases prior OC0168 CICS TRACE TABLE NOT FOUND
to CICS 3.1.
Explanation
System action
The TRAC command was entered with an operand of
The DLI command fails. TRTAB, but the CICS internal trace table base address
is zero.
User response
None.

The command fails. The connection to DBCTL has not yet finished, and for
that reason the control blocks associated with DBCTL
User response are not yet fully initialized.
None.
System action
OC0169 INVALID OPERAND FOR THE DLI The DLI command fails.
COMMAND
User response
Explanation
Determine if the connection to DBCTL is waiting for
The keyword specified was not valid for the DLI DBCTL, or if there is another problem. If so correct the
command. problem. Then enter the DLI DBCTL command.
System action OC0176 CICS HAS NOT CONNECTED TO

DBCTL YET
Explanation
User response
This indicates that CICS is not yet connected to
Correct the keyword and enter the command. DBCTL. Either the DBCTL keyword was entered
incorrectly, or CICS is not yet connected to DBCTL.
OC0170 DB2ENTRY NOT FOUND OR NOT
CURRENTLY IN-USE
Explanation
Explanation The EXIT EPB command was entered and no exit
program blocks (EPBS) were found.
The DB2 SELECT DB2ENTRY ID=xxxxxxxx command
was entered with an undefined DB2ENTRY (xxxxxxxx)
specified. System action
System action
None. System action
The EXIT command fails.
User response
Reenter the DB2 command with a valid DB2ENTRY User response
specified.
If you intended to display DBCTL information, use the
OC0173 IMS RELEASE NOT SUPPORTED CDBC transaction to connect to DBCTL. Then enter
the DLI DBCTL command. OC0177 NO EXIT PROGRAM
BLOCKS WERE FOUND
Explanation
The release of IMS you are executing is not supported User response
by IBM Z OMEGAMON for CICS.
Verify that EPBs exist in your system. If there are
EPBs, and EXIT is not displayed, then contact IBM
System action Software Support.
OC0177 NO EXIT PROGRAM BLOCKS
FOUND
User response
None. Explanation
OC0175 CICS CONNECTION TO DBCTL IS The Exit command was entered to display exit
NOT READY information but no Exit Program Blocks were found.

None. While processing the DB2 command, a valid
DB2ENTRY token was not located.
User response
System action
None.
The DB2 command does not display information
OC0178 DB2 RELEASE NOT SUPPORTED regarding this DB2ENTRY.

The release of DB2 you are executing is not supported This implies a problem with the CICS region. Check
by IBM Z OMEGAMON for CICS. the CICS log for messages to make the appropriate
corrections.
System action
OC0183 NO GLOBAL USER EXITS FOUND
The DB2 command fails.
Explanation
User response
The EXIT command was entered and no global user
None. exits were found.
OC0179 CICS-DB2 STATIC STORAGE NOT
AVAILABLE System action
The EXIT command fails.
Explanation
The CICS static storage area was not located. User response
Verify that you have global user exits installed in your
System action CICS. If there are global user exits and the EXIT
command is not displayed, then contact IBM Software
CICS/DB2 interface information will not be available.
Support.
User response OC0184 DB2 SUBSYSTEM NOT UP
This implies a problem with the CICS region. Check

Explanation
the CICS log for messages to make the appropriate
corrections. The DB2 command has been issued before the DB2
subsystem has been started.
OC0180 CICS-DB2 ATTACH GLOBAL BLOCK
NOT PRESENT
System action
Explanation The DB2 command fails.
While processing the DB2 command the CICS-DB2
Attach Global Block was not located. User response
If required, arrange for the DB2 subsystem to be
System action started and issue the command again.
CICS/DB2 interface information will not be available. OC0185 DB2 RESOURCE CONTROL TABLE
NOT PRESENT
User response
Explanation
This implies a problem with the CICS region. Check
the CICS log for messages to make the appropriate The Resource Control Table (RCT) was not found in
corrections. CICS. Generally this means that CICS has not yet been
connected to DB2 or that CICS has been disconnected
OC0181 CICS-DB2 DIRECTORY TOKEN
from DB2.
INVALID

The DB2 command fails. Determine why entry length was invalid, correct, and
then retry the command
User response OC0189 XRF IS NOT ACTIVE FOR THIS
Verify that you have connected CICS to DB2. If you are CICS
connected and the DB2 command still produces this
error, then contact IBM Software Support. Explanation
OC0186 TRANSACTION NOT FOUND IN XRF=NO was coded in the SIT.
RCT
System action
Explanation
IBM Z OMEGAMON for CICS ignores the command.
The specified transaction was not found in the RCT.
User response
System action
None.
The DB2 command fails.
OC0190 LU GROUP INVALID FOR THIS
FUNCTION
User response
Verify that the transaction-ID you specified is in the Explanation
RCT. If it is in the RCT and the DB2 command
still produces this error, then contact IBM Software The requested function does not support VTAM Logical
Support. Unit (LU) group.
OC0187 FILE NOT FOUND OR IS NOT OPEN System action

Explanation
The VSAM command was entered with an operand of User response
a file name, but the file specified could not be located
internally with CICS’s VSAM control blocks. The file None.
may not be VSAM, may not be allocated to CICS, or
OC0196 GROUP TYPE INVALID. USE TX,
may not have been opened by CICS.
TR, PG
System action
Explanation
The command fails.
The RSP command or one of the minor commands
(either TIME or CNT) was specified with an invalid
User response group type suffix.
None.
System action
OC0188 INVALID TABLE ENTRY LENGTH
Explanation
User response
A table entry (such as FCT, PCT, or PPT) was found
with an entry length of over 1,000 bytes. The length of Correct the group type suffix, specifying either TX
the entry was determined to be invalid. (transactions), TR (terminals) or PG (programs), and
enter the command
System action OC0201 COLLECTOR NOT ACTIVE,
The command is terminated. REQUEST IGNORED

The bottleneck analysis collector subtask is not active. Contact IBM Software Support.
OC0205 COLLECTOR ESTAE, SDWA NOT
System action AVAILABLE, CODE=aaaaaaaa
Explanation
User response This message is produced by the DEX DEBUG
Start the collector and issue the command again. command. The bottleneck analysis collector subtask
has abended, but system recovery did not have
OC0202 COLLECTOR IS BUSY, TRY AGAIN enough storage to obtain an SDWA (System Diagnostic
Work Area) to save the status at the time of abend.
Explanation aaaaaaaa indicates the cause of the abend.
The bottleneck analysis collector is currently analyzing

System action
the CICS environment. The display command cannot
access the collection data until the collector finishes. None.

The command stops processing. Contact IBM Software Support.
OC0207 COLLECTOR DETACHED DUE TO
User response TOO MANY PROGRAM CHECKS
Issue the command again.
Explanation
OC0203 COLLECTOR SUSPENDED, VALUES
SHOWN NOT CURRENT The bottleneck analysis collector was detached due an
excessive number of program checks.
Explanation
System action
The bottleneck analysis collector is suspended and is
not sampling data. Only the values accumulated up to The command stops processing.
the time of suspend are displayed by the command.
User response
System action
The command continues running.
OC0208 COLLECTOR START ERROR, CODE=
nnnnnn
User response
Resume the bottleneck analysis collector and issue the Explanation
command again.
The bottleneck analysis collector failed to START
OC0204 BOTTLENECK ANALYSIS successfully. The code indicates the reason for the
COLLECTOR HAS ABENDED, error.
CODE=ssuuu
System action
Explanation
The bottleneck analysis collector does not initialize.
The bottleneck analysis subtask abnormally stopped
processing. The abend code is the ssuuu value.
User response
None. OC0209 COLLECTOR NOT ACTIVE,

STORAGE SHORTAGE, CODE=
nnnnnn

The bottleneck analysis collector could not obtain The command stops processing; IPRO PDEX only
storage for the analysis work area. nnnnnn indicates honors the display request if 25 or more samples
how much storage is needed. are collected and there are wait reasons (other than
RUNNING) that exceed the threshold value set by the
System action TPCT command.
The bottleneck analysis collector stops processing.

User response
User response Allow IBM Z OMEGAMON for CICS some time for data
capture. Use the PDEX command to observe tasks
Increase available virtual storage by the amount counted thus far.
indicated, by reducing the number of tasks running in
the interface address space or by increasing the region OC0217 BUCKET SET ADDRESS DOES NOT
size. CORRESPOND TO BUCKET ID
OC0210 VARIABLE BUCKET SET STORAGE

Explanation
ERROR, OVERFLOW USED
An internal error was detected in the bottleneck
Explanation analysis bucket structure.
This message is used for debugging purposes by IBM

System action
Tivoli support.
System action
User response
None.
User response OC0218 WAIT REASON ID NOT FOUND BY
Contact IBM Software Support. ZOOM FUNCTION
OC0214 BOTTLENECK ANALYSIS

Explanation
COLLECTOR HAS ABENDED (LOOP)
An internal error was detected in the bottleneck
Explanation analysis bucket structure.
The bottleneck analysis collector’s cycle took longer

System action
than expected.
System action
User response
The bottleneck analysis collector abnormally stops
processing. Contact IBM Software Support.
OC0219 WAIT REASON ID NOT FOUND IN
User response BUCKET
Explanation
OC0215 OCTB INSUFFICIENT DATA
The bottleneck analysis buckets were searched but no
Explanation match was found for the wait reason ID entered with
the command.
The IPRO PDEX command determined that an
insignificant amount of degradation data was collected
System action
for meaningful display.

Enter the command with a valid wait reason ID. Bottleneck analysis collection is started.
OC0224 COLLECTOR ATTACHED, REQUEST
IGNORED User response
None.
Explanation
OC0233 COLLECTOR DETACHED
This message is in response to a DEX START
command. The subtask is already attached. Explanation
This message is in response to a DEX STOP command.
System action
The subtask was terminated and detached.
System action
User response
None.
None.
OC0225 COLLECTOR NOT ATTACHED, User response
REQUEST IGNORED None.
OC0234 SHORT TERM BUCKETS WILL BE
Explanation
RESET
This message is in response to a DEX STOP command.
The subtask is not attached. Explanation
This message is in response to a DEX SET
System action
SHORT=CLEAR command.
System action
User response
The bottleneck analysis short term counters are set to
None. zero.
OC0226 INTERVAL SPECIFICATION MUST
BE NUMERIC User response
None.
Explanation
OC0235 LONG TERM BUCKETS WILL BE
This message is in response to a bottleneck analysis RESET
sample time interval set request. The value entered is
not numeric. Explanation
This message is in response to a DEX SET
System action
LONG=CLEAR command.
The command stops processing .
System action
User response
The bottleneck analysis long term counters are set to
Correct the input, and enter the correct value. zero.
OC0232 COLLECTOR ATTACHED
User response
Explanation None.
This message is in response to a DEX START OC0236 COLLECTOR NOT ATTACHED
command. The bottleneck analysis collector was
successfully attached.

This is a status message, the collector is not attached. This message provides information on a specific
condition. None of the wait reasons documented in the
System action CICS Transaction Server Problem Determination Guide
should appear in this message; if one wait reason does
None. appear, contact IBM Software Support and provide any
necessary logs.
User response OC0252 INVALID BUCKET SET NAME, USE
None. BLST COMMAND FOR LIST
OC0237 COLLECTOR NOT ACTIVE

Explanation
Explanation An invalid ID was entered with the BLST command.
The bottleneck analysis collector was not activated

System action
(DEX START command).
System action
User response
None.
Use the BLST command without operands to list all
User response IDs.
None. OC0253 BOTTLENECK ANALYSIS

INTERFACE BUSY; TRY AGAIN
OC0245 BOTTLENECK ANALYSIS
INTERFACE IS BUSY, TRY AGAIN
Explanation
Explanation The bottleneck analysis subtask is updating its
collection buckets, so they are temporarily unavailable
A PDEX command was entered while bottleneck to the display components.
analysis was busy performing its analysis.
System action
System action
The command does not execute.
User response
User response
Enter the command.
Enter the command again.
OC0260 INTR INVALID VALUE SPECIFIED
OC0251I UNKNOWN WAIT RESOURCE FOR aa. RANGE=b-c
tttttttt/nnnnnnnn FOR CICS TS
rrrrr.
Explanation
Explanation This message is in response to an INTR SET command.
The value specified for the keyword denoted by aa is
The Bottleneck Analysis data collector has not in the proper range (between the values indicated
encountered an unknown wait resource with type. by b and c inclusive).
The tttttttt value is the wait resource type and the
nnnnnnnn value is the resource type name. The rrrrr
System action
value is the release level of CICS Transaction Server in
use. The command is ignored.

A collection bucket for the unknown wait resource will Correct the value and enter the command again.
be added to the UNKNOWN bucket set.

OC0261 INTR ERROR RETURN specify the Global Data Area suffix list for the
FROM SMFRTEST MACRO, OMEGAMON for CICS (3270) component..
CODE=aaaaaaaa
OC0264 INTR PROGRAM CHECKS = aa
The SMFRTEST macro, used by the interval record
This message is displayed by the INTR DEBUG
collector to determine whether records can be written
command if one or more program checks are
to the SMF dataset, returned a non zero return code.
encountered by the interval record collector.

The interval record collection stops processing.
None. The interval record collector continues to
process normally.
User response
Find the meaning of the return code denoted by the User response
aaaaaaa value in the IBM SMF manual. Correct the
A small number of recoverable program checks might
cause of the error and restart the interval record
be considered normal. They may be the result of
collector.
chains being altered in CICS while the interval record
OC0262 INTR UNABLE TO OBTAIN collector is attempting to collect CICS data. If the
WORK AREA. LENGTH=aaaaaaaa, number of program checks is large, then something
SP=bbb could be wrong with the interval record collector’s
data collection mechanism. Contact IBM Software
Support.
Explanation
OC0265 INTR INVALID CALL MADE TO
A GETMAIN request for aaaaaa bytes from subpool
OCEP
bbb could not be satisfied.

The interval record collection component has received
an invalid request, such as a request to record data
before it has been initialized.
User response
Increase the region size for the interface and restart System action
the interval record collector.
The interval record collector stops processing.
OC0263 INTR KOCGLB MODULE DOES NOT
CONTAIN KOCINTR MACRO User response
Explanation
OC0266 INTR ERROR COLLECTING
The Global Data Area does not contain the
BOTTLENECK DATA
communications area for the Interval Recording
function.
Explanation
System action The bottleneck data collection within interval
recording has too much data to fit into one SMF record.
This indicates a problem either in the bottleneck
analysis buckets or in the interval record collection of
User response the bottleneck data.
Verify that the correct Global Data Area has been built
using PARMGEN. The KC2_ CLASSIC_KC2GLB_SRCLIB System action
parameter is used to specify the library which
stores the global data area, and the KC2_
CLASSIC_KC2GLB_SUFLISTn parameter is used to

Contact IBM Software Support. The SMFWTM macro, used by the interval record
collector to write records to SMF, returned a code in
OC0267 INTR ERROR IN RECORDING, register 15 denoted by aaaaaaaa.
THERE ARE LOST RECORDS
System action
Explanation
Interval recording expects to be driven every minute.
In this case the recorder detects that it has been more
than one minute since the last collection. User response
Locate the meaning of the SMFWTM return code in the
System action IBM SMF manual. Correct the cause of the problem
and restart the interval record collector.
OC0270 INTR MONITOR ESTAEX SDWA
User response NOT AVAILABLE, CODE=aaaaaaaa
Check to see if there is some reason why the collector

Explanation
is not getting driven at the expected time, such as MVS
system hang. If no reason can be found, contact IBM This message is produced by the INTR DEBUG
Software Support. command. The bottleneck analysis collector subtask
has abended while it is driving interval record
OC0268 INTR TOO MANY IDS FOR RTA collection, but system recovery did not have enough
SMF RECORD, SOME DATA MAY BE storage to obtain an SDWA (System Diagnostic Work
LOST Area) to save the status at the time of abend.
aaaaaaaaindicates the cause of the abend.
Explanation
The interval record collector has detected that there System action
is too much response time data to fit in one SMF None.
record. The interval record collector is able to hold
the response times for approximately one thousand
transactions, programs, terminals, or LUs in one SMF User response
record. Contact IBM Software Support.
OC0271 INTR MONITOR HAS NOT
System action
ABENDED
The interval record collector collects only data for the
transactions, programs, terminals, or LUs that it can fit Explanation
in one SMF record.
This message is issued in response to an INTR DEBUG
command. The collector did not abend, therefore no
User response
abend information is available.
Using the response time analysis displays, determine
if there really have been intervals of one minute System action
that contain so many different transactions, programs,
terminals, or LUs. If not, contact IBM Software None.
Support.
OC0269 INTR ERROR RETURN User response
FROM SMFWTM MACRO, None.
CODE=aaaaaaaa
OC0272 INTR I/O ANALYSIS FAILED, I/O
INFORMATION IS NO LONGER
BEING RECORDED

The interval record collector has failed to load the None.
required RMF module KOCRcc0 a, where cc is an RMF
indicator and a is an MVS indicator. User response
None.
System action
The interval record collector no longer collects I/O OC0276 INTR INTERVAL RECORDING
analysis information. DEACTIVATED

Check the system operator console for loader This message is in response to an INTR STOP
messages to see why the load failed (CSVnnnn). If command. The collector was successfully stopped.
possible, correct the problem and restart the interval
record collector. Otherwise, contact IBM Software System action
Support.
None.
OC0273 INTR INTERVAL RECORDING
ALREADY ACTIVE User response
None.
Explanation
OC0277 INTR ABEND DIAGNOSTICS ARE
This message is in response to an INTR START
UNAVAILABLE
command. The collector is already active.

This message is in response to an INTR DEBUG
command. Diagnostic information for the interval
record collector has been overwritten by a subsequent
User response bottleneck analysis collector abend.
None.
System action
OC0274 INTR INTERVAL RECORDING IS
NOT ACTIVE None.

This message is in response to an INTR STOP Contact IBM Software Support.
command. The collector was already stopped.
OC0278 The INTERVAL RECORD
COLLECTOR FOR cicsjobn HAS
System action ABENDED
Explanation
User response Interval record collection is abnormally terminated.
None.
System action
OC0275 INTR INTERVAL RECORDING
ACTIVATED The interval record collector is terminated.

This message is in response to an INTR START Contact IBM Software Support.
command. The collector was successfully started.
OC0279 INTR HAS IDENTIFIED RMF
VERSION: nnn

Explanation Table 12. Return codes when INTR has encountered
This message is in response to an INTR START an unrecoverable initialization error.
command. INTR has determined the current RMF level Return Code Description
to be nnn.
20 Level of RMF (or
equivalent) is not known.
System action
24 RMF Supervisor Control
None. Table main memory is
invalid (for RMF level
User response greater than 4.3.0).
None. 28 RMF Supervisor Control
Table main memory is
OC0281 INTR LOAD FAILED FOR RMF
invalid (for RMF level less
ANALYSIS MODULE KOCRcc0a,
than or equal to 4.3.0).
ABEND CODE=nnnnnnnn, REASON
CODE=rrrrrrrr 30 RMF Supervisor Control
Table not resident.
Explanation 34 Unallocated RMF ASCB.
This message is in response to an INTR START 38 RMF is inactive.
command. INTR has failed to load the required RMF
module KOCRcc0a, where cc is an RMF indicator and a
is an MVS indicator. Abend code nnnnnnnn and reason System action
code rrrrrrrr make up the MVS Contents Supervisor
The interval recorder no longer collects I/O analysis
return code information returned when an MVS LOAD
information.
is issued for the module. These values may occur in
MVS system console messages issued by the loader
(CSVnnnn). User response
Ensure that RMF is available and correct any problem
System action it is experiencing. Restart interval recording. If the
problem persists contact IBM Software Support.
information. OC0283 INTR RMF ANALYSIS MODULE,
KOCRcc0a, IS IN ERROR. RETURN
User response CODE=nnnnnnnn
If possible, ensure that module KOCRcc0a is available

and correct the problem. Then attempt to restart the
Explanation
interval recorder. Otherwise, contact IBM Software This message is in response to an INTR START
Support. command. INTR has encountered an unrecoverable
initialization error related to the use of loaded module
OC0282 INTR RMF ANALYSIS
KOCRcc0 a where cc is an RMF indicator and a is an
INITIALIZATION FAILED. RETURN
MVS indicator. These are the possible return codes:
CODE= nnnnnnnn
Table 13. Return codes when INTR has encountered
Explanation an unrecoverable initialization error.
This message is in response to an INTR START Return Description

command. INTR has encountered an unrecoverable Code
initialization error identified by return code nnnnnnnn. 8 Module length is zero.
These are the possible return codes:
12 Module address is zero.
System action
information.

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

If the OC0272 message follows this message, contact
None.
OC0302 RTA INITIALIZING SO CANNOT
OC0285 RMF VERSION CANNOT BE
ACCEPT STOP COMMANDS
DETERMINED; VERSION nnn
PRESUMED
Explanation
Explanation This message is in response to an RTA STOP
command. The response time collector is in the
INTR has been unable to confirm the RMF level in use
process of initializing.
in your system. A level compatible with the level of
MVS in use has been presumed (nnn).

The request is ignored, and the response time None.
OC0306 RTA SCALE= VALUE INVALID,
MUST BE 0.1–9.9 SECS
User response
Once the response time collector is initialized, enter Explanation
the RTA STOP command again.
This message indicates that the SCALE= parameter of
OC0303 RTA START REQUEST IGNORED - the response time collector command is invalid. The
RTA IS INITIALIZING valid range for the SCALE parameter is 0.1–9.9.

This message is in response to an RTA START The command stops processing.
command. The response time collector is in the
process of initializing. User response
Correct the value, and enter the command again.
System action
OC0307 RTA NOT ACTIVATED - ALL
GROUPS EMPTY

A request was made to start the response time
None.
collector. The request is not completed because all the
OC0304 RTA MONITOR ACTIVE, REQUEST defined groups are empty.
IGNORED
System action
Explanation
The request is ignored.
This message is in response to an RTA START
command. The response time collector is already User response
active.
Use the GRPS command to list the currently defined
groups and their entries. Modify the current groups
System action
and retry the request.
OC0308 ETE NO LU MEETS SELECTION
CRITERIA
User response
Explanation
None.
The ETE command could not find a defined Logical
OC0305 RTA COLLECTOR ACTIVATE Unit to satisfy the selection criteria specified on the
REQUEST ACCEPTED command.

This message is in response to an RTA START None.
command. It acknowledges the request to activate the
response time collector. User response
None.
System action
OC0309 ETE NO LUS ARE BEING
The response time collector is started.
MONITORED

Explanation OC0313 ETE SPECIFIED GROUP IS NOT LU
TYPE
No VTAM Logical Unit names have been assigned to an
LU group.
Explanation
System action The GROUP= operand of the ETE command specified a
non-LU type group. ETE can only process Logical Unit
None. groups.

None. The command stops processing.
OC0310 RTA DATA MODULE MISSING
User response
Explanation Specify a group that has been defined for LUs.
A request was made to start the response time OC0314 RTA NOT STARTED, OMEGAMON
collector, or a response time collector command was INITIALIZATION WAS NOT DONE
entered, however the response time collector portion FOR THIS CICS REGION
of KOCGLBcc cannot be located.
Explanation
System action
A request was made to start the response time
The command stops processing. collector, however the CICS transaction OMEG INIT
was not entered.
User response
OC0311 ETE INTERVAL= PARM INVALID, The request fails.
MUST BE 1–7200 MINS
User response
Explanation Issue the OMEG INIT transaction to initialize IBM Z
The valid range for the INTERVAL parameter is 1–7200 OMEGAMON for CICS. You can initialize automatically
minutes inclusive (1 minute to 5 days). by including the KOCOME00 program in the PLT. Refer
to the IBM Z OMEGAMON for CICS Configuration and
Customization Guide for more information.
System action
OC0315 RTA NOT STARTED, XMEM
RECEIVE NOT AVAILABLE

Enter the command again and specify a valid value.
This message occurs when the response time collector
OC0312 RTA WINDOW= VALUE INVALID, is unable to obtain response time information because
MUST BE 1–10 MINUTES it cannot locate the IBM Z OMEGAMON for CICS cross
memory communication buffer.
Explanation
System action
The valid range for the SCALE parameter is 1 - 10.
The response time collector subtask stops processing.
System action
User response
Check that KOCOME00 successfully ran under CICS
either at PLTPI time or via an OMEG INIT transaction.
User response Also, make sure that the XM_BUFFER_RECORDS=
Correct the value, and enter the command again. parameter of the KOCGLOB macro does not

specify a value of zero in the Global module. If User response
XM_BUFFER_RECORDS=0, then the communication
buffer will never be allocated. This message may Contact IBM Software Support.
appear if CICS is in the process of termination at the OC0321 LU RESPONSE TIME
time the response time collector tries to extract data. FACILITY FAILED DURING
OC0316 RTA HAS ISSUED A MISMATCHING c-c REASON=nnnnnnnn
XMEM RECEIVE FOR DATA LU=mmmmmmmm
The response time collector subtask supplied an area An error occurred in the response time collector’s LU
that is too small to accommodate the response time Response Time Facility. The variable c-c is replaced by
information collected by IBM Z OMEGAMON for CICS one of the following RTA internal call types: INSTALL,
code running under CICS. ADD, EXTRACT, or REMOVE. LU=mmmmmmmm is
displayed for ADD request errors, and is replaced by
the Logical Unit ID of the device for which the ADD
System action request was issued.
The response time collector subtask abnormally stops The variable nn is a hexadecimal return code (for a
processing with a U0316 abend. Contact IBM Software complete description, see the End-to-End Response
Support. Time Feature (ETE) Reference Manual) and is replaced
OC0320 LU RESPONSE TIME FACILITY by a decimal return code.
FAILED DURING cc-cc RC=nn
System action
Explanation The response time collector does not collect LU
An error occurred in the response time collector’s LU response time data for some or all of your defined LUs.
Response Time Facility. The variable cc-cc is replaced
by one of the following response time analysis internal User response
call types: INSTALL, ADD, EXTRACT, or REMOVE.
The variable nn is a hexadecimal return code (for a
complete description, see the End-to-End Response OC0322 RTA COLLECTOR START ERROR,
Time Feature (ETE) Reference Manual) and is replaced RC=nn
by one of the following decimal return codes:
Explanation
Table 15. Decimal return codes that replace a
hexadecimal return code for the LU Response Time This message is in response to an RTA START
Facility. command. IBM Z OMEGAMON for CICS was unable to
start the response time collector subtask.
Return
Code Description
System action
00 request was successful
04 not APF authorized collector status is displayed. The response time
collector does not start.
08 handle invalid
10 ZAPLOG does not match User response
14 request failed Note the return code that accompanies this message
18 RTINSTAL module LOAD failed and call IBM Software Support.
OC RSP1 not installed OC0330 RTA COLLECTOR NOT ACTIVE
Explanation
System action
One of the response time collector commands was
The response time collector does not collect LU
entered (CRSP, CSLT, RSP or ETE) but the response
response time data for some or all of your defined LUs.
time collector was not active.

System action • The ONDV data set must have a secondary extent of
1 cylinder.
• A mismatch in maintenance has occurred.
User response A return code of 34 indicates that an error occurred

during dynamic allocation.
Use the RTA START command to activate the response
time collector. The ONDV collector abnormally stops.
OC0380 RTA - NO WORKING STORAGE If you have a return code of 10, stagger the start
AVAILABLE up of the CICS regions or issue the command OMEG
SHUT followed by the command OMEG INIT in the
CICS region where initialization failed. If you have
Explanation a return code of 20, verify that your ONDV dataset
There is insufficient virtual storage for the RSP has been allocated and initialized properly. If you
command’s work area. have recently applied maintenance, verify OMEG
REMOVE/ OMEG INIT has been issued, or recycle all
the CICS regions to activate the new maintenance in
System action all regions.
The RSP command stops processing. If you receive a return code of 34, look
for accompanying OC040x messages containing
User response additional return codes. In these messages, the
return and reason codes are the same as those
Increase the region for the interface. produced by DYNALLOC SVC (SVC99). For a
OC0390 RTA DATA AREA BUSY - RETRY complete description of these return codes, see
the IBM documents MVS/XA System Programming
Library: System Macros and Facilities Vol I. or
Explanation MVS/ESA Application Development Guide: Authorized
A GRPS or RTA command issued by another IBM Z Assembler Language Programs.
OMEGAMON for CICS session is currently modifying OC0401 ONDV WAITING FOR OMEGAMON
the thresholds, SCALE or WINDOW in the response TO INITIALIZE
time collector data area.
Explanation
System action
The ONDV collector is waiting for initialization in CICS
The command stops processing. to complete.

Enter the command. The collector waits for 20 seconds and then stops
OC0400 ONDV COLLECTOR HAS ENDED processing.
DUE TO AN ERROR, RC=nn
User response
Explanation Start the collector manually with the ONDV START
The ONDV collector abnormally terminated. command in an IBM Z OMEGAMON for CICS session. If
the collector still does not start, see if there are any
A return code of 10 may occur if multiple CICS regions problems in CICS preventing the OMEG transaction
are started and OMEGAMON is not given enough from completing. If OMEG is not present, this indicates
cycles to complete the cross memory initialization a problem with IBM Z OMEGAMON for CICS. Perform
within 30 seconds. a system dump and send in the dump and DEBUG
A return code of 20 may indicate one of the following: screens to IBM Software Support.
• The ONDV data set does not exist. OC0402 ONDV ERROR FROM DSPSERV,
RC=nn, REASON=00yyyy00
• The ONDV data set is not initialized.
• The ONDV data set is corrupted.

The ONDV collector encountered an error from the The ONDV collector could not allocate the historical
DSPSERV macro; this is an IBM macro for using data file you specified in the KOCONDV macro in KOCGLB.
space services.
System action
System action
The collector stops processing.
The collector stops processing.
User response
User response
Make sure the dataset you specified exists and is a
Consult the IBM Application Development Macro linear dataset. The return codes in the error message
Reference manual for the cause of the error. are based on the SVC 99 call. Consult the IBM SPL
Application Development Guide for a description of the
OC0403 ONDV DATA SPACE SIZE EXCEEDS return codes.
INSTALLATION LINIT, DEFAULT
SIZE USED OC0406 ONDV UNABLE TO DEALLOCATE
HISTORICAL DATA FILE, RC=nn
Explanation ERROR=eeee INFO=iiii
The size of the data space for the ONDV collector

Explanation
exceeded the limit defined by your installation as set
by the SMF user exit IEFUSI or by the IBM default size. The ONDV collector could not deallocate the historical
file as it was terminating.
System action
System action
The collector reduces the size of the data space to the
installation default size. The collector continues termination, but the data set
may still be allocated to the interface address space.
User response
User response
Check that the size of the data space you specified in
the KOCONDV macro in KOCGLB does not exceed any The return codes in the error message are based on
limit defined at your installation. the SVC 99 call. Consult the IBM SPL Application
Development Guide for a description of the return
OC0404 ONDV ERROR FROM ALESERV, codes.
RC=nn
OC0407 ONDV UNABLE TO MAP
Explanation HISTORICAL DATA FILE, RC=nn
REASON=yyyy
The ONDV collector encountered an error from the
ALESERV macro. This is an IBM macro for using
Explanation
address space control services.
The ONDV collector encountered an error from the DIV
System action macro while trying to map the linear data set to a data
space. The DIV macro is an IBM macro for using the
The collector stops processing. Data-In-Virtual facility of MVS.

Consult the IBM Application Development Macro The collector stops processing.
Reference manual for a description of the return codes.
OC0405 ONDV UNABLE TO ALLOCATE User response
HISTORICAL DATA FILE,
Consult the IBM Application Development Macro
RC=nn ERROR=eeee I= iiii
Reference manual for a description of the return codes.
NAME=dataset_name

OC0408 ONDV HISTORICAL DATA FILE OC0411 ONDV COMPONENT IS NOT
WILL BE CLEARED AVAILABLE UNDER MVS/XA
The ONDV collector detected invalid control The ONDV subtask cannot be used in an MVS/XA
information while initializing the historical data file. environment.

All data in the historical data file is erased. The command is ignored.

Make sure that the collector used the allocated None.
data set. If this occurs again, contact IBM Software
Support. OC0412 ONDV GENERIC DATASET NAME
TOO LONG
OC0409 ONDV NOT STARTED, OMEGAMON
INITIALIZATION WAS NOT DONE Explanation
FOR THIS CICS REGION
The name of the VSAM linear dataset used to store
task history (which is specified on the KOCONDV
Explanation
macro of the global data area module) contains the
A request was made to start the ONDV collector, but asterisk “wildcard” character. When the ONDV subtask
the CICS transaction OMEG INIT was not entered or was started, the asterisk was replaced by the job name
the KOCOME00 program was not run in the PLT during of the CICS region being monitored. (This allows a
CICS initialization. global data area module to be shared by several CICS
regions even though each region requires its own task
System action history dataset.) After the job name was substituted
for the asterisk, the resulting dataset name exceeded
The request fails. the maximum of 44 characters.

Issue the OMEG INIT transaction to initialize Tivoli The subtask is terminated with a return code of 100,
OMEGAMON II in CICS. You can automatically initialize (x64).
by including the KOCOME00 program in the PLT. Refer
to the IBM Z OMEGAMON for CICS Configuration and
User response
Customization Guide for more information.
Correct the filename field on the KOCONDV macro so
OC0410 ONDV HISTORICAL DATA FILE TOO that, after CICS job name substitution, it specifies the
SMALL name you assigned to the task history dataset when it
was allocated. Then reassemble the global data area
Explanation module and recycle the interface address space.
The size of the historical data file was less than 8K and OC0413 REDEFINE THE VSAM DATASET
therefore could not be used. WITH SHAREOPTIONS(3,3)

The ONDV collector stops processing. While attempting to access the linear VSAM task
history dataset, it was found that the dataset
User response was not defined with SHAREOPTIONS(3,3). These
SHAREOPTIONS are required to enable the ONDV
Make sure that historical data file is at least 8K collector to provide its own serialization of the dataset
and that the data file is initialized according to the rather than let VSAM control it.
procedure described in the IBM Z OMEGAMON for
CICS Configuration and Customization Guide.

System action OC0416 ONDV HISTORICAL DATA FILE HAS
BEEN ERASED DUE TO THE ABOVE
The collector stops processing with a return code of 56 ERROR
(x38). This message is preceded by messages, OC0407
and IEC161I 052-084.
Explanation
User response The ONDV collector has erased the data in the
historical file due to the error previously reported.
Use PARMGEN to delete and redefine the historical
data set. When allocated, restart the ONDV subtask
from an IBM Z OMEGAMON for CICS session or System action
through the console Modify command. The collector stops processing. The next restart
OC0414 ONDV SEVERE LOGIC ERROR IN causes the file to be re initialized. Processing then
HISTORICAL DATA FILE INDEX begins again normally.
STRUCTURE
User response
Explanation From the KOCCInn console log, determine the reason
The ONDV collector detected an index pointer that was for the collector failure.
not valid within the historical data file. OC0417 INCOMPATIBLE ONDV
COLLECTOR/DATASTORE -
System action CICSJOBN. ERASE DATASTORE?
REPLY Y OR N.
The collector issues an ABENDU414 and stops
processing; this message should be followed by the
OC0416 message. Explanation
The ONDV collector has been started for the specified
User response CICS region, but on the KOCONDV macro in the global
data area module used by that region, one of the
Keep the dump and make a copy of the historical following occurred:
data file, then contact IBM Software Support. If this
message is not followed by the OC0416 message, re • STORE=(FILEONLY,LINEAR.*.DATASET) has been
initialize your historical data file prior to starting ONDV. specified and the data set is formatted for the
FILEOCMP version of the collector, or
OC0415 ONDV SEVERE LOGIC ERROR IN
HISTORICAL DATA FILE DATA • STORE=(FILEOCMP,LINEAR.*.DATASET) has been
STRUCTURE specified and the data set is formatted for the
FILEONLY version of the collector.
Explanation Suspends collector initialization pending operator

response.
The ONDV collector detected an invalid data pointer
within the historical data file. Enter Y to continue initialization and erase current
data or N to terminate collector without affecting
current datastore contents.
System action
OC0418 ONDV COLLECTOR WAITING FOR
The collector issues an ABENDU415 and stops CONSOLE RESPONSE
processing; this message should be followed by the
OC0416 message.
Explanation
User response An attempt has been made to stop or start the
collector from an OMEGAMON session while the
Keep the dump and make a copy of the historical data collector status is REPLY. The ONDV collector is
file and contact IBM Software Support. If this message waiting for a response to WTOR OC0417.
is not followed by the OC0416 message, re initialize
your historical data file prior to starting ONDV.
System action

See the accompanying OC0417 message, check the None.
log, and respond Y or N from the console.
OC0424 COLLECTOR START REQUEST
OC0420 INVALID PARAMETER SPECIFIED ACCEPTED
An invalid parameter was specified in the ONDV This is an informational message in response to a
command. START request.

The command is ignored. None.

Correct the syntax of the command. None.
OC0421 COLLECTOR NOT ACTIVE OC0425 COLLECTOR STOP REQUEST
REJECTED
Explanation
Explanation
The ONDV collector is not running.
A request was made to start the ONDV collector
System action through a MVS command but that command was
rejected by MVS.
No records are displayed.
System action
User response
The collector is not started.
You must start the collector in order to view records.
OC0422 COLLECTOR STOP REQUEST User response
ACCEPTED Check the SYSLOG interface job for more information.
Explanation OC0426 NO STATUS INFORMATION

AVAILABLE
This is an informational message in response to a
STOP request.
Explanation
System action Status information on the ONDV collector is not
available because the collector is not active.
None.
System action
User response
None.
OC0423 COLLECTOR ALREADY ACTIVE User response
Make sure the collector is active.
Explanation
OC0427 INTERNAL ERROR, RC=yy
A request was made to start the ONDV collector but
the collector is already active.
Explanation
System action The ONDV collector detected an internal error in
processing the request.

The request is ignored. No display is produced.

Contact IBM Software Support. The record number corresponds to the entry number
of the record that appears on the screen. The first
OC0428 INSUFFICIENT LINES FOR THE
record is 1, the second 2, and so on. Issue the ONDV
DISPLAY
command again with a valid record number.
Explanation OC0431 ERROR IN RETRIEVING RECORDS,

RC=nn
The ONDV command did not have enough lines on the
terminal to produce a display.
Explanation
System action The ONDV collector has encountered an internal error
in processing the request.
No display is produced.
System action
User response
When entering the ONDV command, make sure at least
six lines are available at the end of the screen to
User response
account for titles, headings, and so on. ONDV does not
write records past the physical end of the screen. Contact IBM Software Support with the return code.
OC0429 NO RECORDS TO DISPLAY OC0432 NO DETAILED STATISTICS ARE
AVAILABLE
Explanation
Explanation
The ONDV collector is active but there are no records
to display. A request was made to display detailed file or
database statistics for a transaction but no statistics
System action are available.
System action
User response No display is produced.
Enter CICS transactions and try the command over. If

User response
this condition persists, verify the following tasks:
Verify that collect is active for the file or database
• Use the CEMT INQ MON transaction in CICS to verify
using the COLL command and that a KOCDBCOL macro
that CICS monitoring is active (for CICS 3.x).
was used in KOCGLB to define the parameters for the
• Verify that the status of the collector is active using file or database. Also verify that the transaction carried
the ONDV STATUS command. out file or database operations from the task level
• Contact IBM Software Support for additional statistics.
assistance.
OC0434 DETAILED STATISTICS HAVE BEEN
OC0430 INVALID RECORD NUMBER TO DELETED FROM ONDV BUFFER
DISPLAY
Explanation
Explanation A request was made to display detailed file or
An invalid record number was entered with the ONDV database statistics for a transaction but the statistics
command. were deleted from the ONDV collector data store. The
statistics are saved in a wraparound table. Statistics
on a file level are saved separately from statistics

on a task level. Therefore, file-level statistics might System action
be overwritten while task-level statistics are still
available. The ONDV collector stops.

No display is produced. Make sure that multiple ONDV subtasks are not
attempting to share the same historical dataset.
User response OC0438 ONDV CLOSE ERROR DETECTED

ON PREVIOUS EXECUTION
You can set the size of the buffer area for task- an file- AGAINST THIS LINEAR DATASET.
level statistics with the KOCONDV macro in KOCGLB.
See the IBM Z OMEGAMON for CICS Configuration and
Customization Guide for more information. Explanation
OC0435 TOP OF FILE << This is an informational message indicating that the
previous ONDV subtask to use this historical dataset
did not terminate correctly. No status information was
Explanation recorded and therefore the data contained within this
IBM Z OMEGAMON for CICS displays this message file will be erased.
on the command line when the first record in the
datastore is displayed. When scrolling backwards System action
in IBM Z OMEGAMON for CICS, the task history
component needs to determine the first record in the This message is followed by the OC0408 message and
datastore to prevent any further scrolling. initialization continues.

None. None.
OC0441I ONDV FOR CICS JOB XXXXXXXX
User response IS SHUTTING DOWN.
None.
Explanation
OC0436 ONDV FOR CICS JOB cicsjobn
USING xxxxxxxx ONDV for CICS XXXXXXXX is terminating.

This is an informational message indicating the name Processing continues.
of the ONDV historical dataset in use for this ONDV
subtask. User response
None.
System action
OC0490 TIME VALUE MUST BE <= STALL
None. INTERVAL

None. A request was made to change the system region exit
OC0437 ONDV UNABLE TO ALLOCATE TIME to a value greater than the current STALL time
LINEAR DATASET. IT IS ALREADY interval.
IN USE.
System action
Explanation The CMT command fails.
ONDV has detected that the linear dataset is currently
in use by another ONDV subtask.

Correct the value and enter the CMT command. A CMT keyword was entered that was unrecognized by
the command for the current CICS release.
OC0491 STALL INTERVAL MUST BE >=
TIME VALUE
System action
A request was made to change the STALL time interval
to a value less than the current region exit TIME. User response
Verify the input keywords and parameters for the
System action current CICS release.
The CMT command fails. OC0500 INVALID FUNCTION REQUEST

Correct the value and enter the CMT command. A CMT keyword was entered that was unrecognized by
the command.
OC0492 MAX TASKS MUST BE >= ACTIVE
MAX TASKS
System action
A request was made to set max tasks less than the
current value for active max tasks. User response
Verify the input keywords and parameters.
System action
OC0501 UNABLE TO VALID VALUE IN CICS
The CMT command fails.
Explanation
User response
IBM Z OMEGAMON for CICS was unable to verify that
Correct the value and enter the CMT command. the correct data would be changed in CICS, because
the command was not run properly.
OC0493 MAX TASKS MUST BE > ALL CLASS
MAX TASKS
System action
A request was made to set max tasks less than the
current value for class max tasks for one of the ten User response
transaction classes. Determine if CICS has had a storage violation. If not,
System action
OC0502 TIME VALUE MUST BE GREATER
The CMT command fails. THAN SCANDELAY VALUE

Correct the value and enter the CMT command again. A request was made to change the TIME to a value
less than the current SCANDELAY value.
OC0495 INVALID MAIN TERMINAL
REQUEST FOR THIS CICS
RELEASE System action

Correct the value and enter the CMT command again. The CMT command fails.
OC0503 CMT REQUIRES A KEYWORD
PARAMETER User response
Enter the CMT command again and specify the class
Explanation ID for the class that you want to change in the CMXT.
The CMT command requires a keyword as an OC0507 CLASS ID MUST BE 1–10
argument.
Explanation
System action
The only valid class IDs are the values of 1–10.
System action
User response
Enter the correct keyword (and optional argument)
after the CMT command. User response
OC0504 VALUE TOO LOW Enter the CMT command again and specify the correct
class ID for the class that you want to change in the
Explanation CMXT.
The value for an argument to a CMT keyword was less OC0508 ACTIVE MAX TASKS MUST BE <=
than the minimum value for that keyword. MAX TASKS

The CMT command fails. An attempt was made to set active max tasks less than
the current value for max tasks.
User response
System action
Correct the argument value and enter the CMT
command again The CMT command fails.
OC0505 VALUE TOO HIGH
User response
Explanation Enter the CMT command specifying a value for active
max tasks greater than or equal to max tasks.
The value for an argument to a CMT keyword exceeded
the maximum value for that keyword. OC0509 CLASS MAX TASKS MUST BE <
MAX TASKS
System action
Explanation
An attempt was made to set class max tasks higher
User response than the current value for max tasks.
Correct the argument value and enter the CMT

System action
command again.
OC0506 CLASS ID MUST BE SPECIFIED
User response
Explanation
Enter the CMT command specifying a value for class
When changing the class max tasks, as class ID must max tasks less than max tasks.
be specified.

OC0510 SCANDELAY VALUE MUST BE <= Explanation
TIME VALUE
A task was selected with the KILL command, but the
task is already being cancelled.
Explanation
An attempt was made to set the SCANDELAY value to System action
a value greater than the time value. The SCANDELAY
value must be less than or equal to the TIME value. The KILL command fails.

The CMT command fails. None.
OC0522 INVALID CONTROL BLOCKS WERE
User response DETECTED IN THE TASK TO BE
KILLED
Enter the CMT command specifying a value for
SCANDELAY less than or equal to the TIME value.
Explanation
OC0515 KILL NOT POSSIBLE, OMEG INIT
WAS NOT DONE FOR THIS CICS The task selected with the KILL command did not have
a valid TCA or DCA (for CICS/MVS) or TQE (CICS/ESA).
This may indicate the task is already being purged by
Explanation CICS.
The KILL command was issued, but the IBM Z
OMEGAMON for CICS interface is not active in the System action
CICS region or the interface was activated after the
task you are attempting to kill was started. The KILL command fails.

The KILL command fails. None.
OC0523 NO KILL PERFORMED, THE TASK
User response IS IN A DL/I REQUEST
Ensure that the OMEG transaction and the KOCOME00

program are defined to CICS and that the OMEG Explanation
transaction has been successfully run in CICS. The task selected with the KILL command has issued
OC0520 PROGRAM CHECK DURING KILL a DL/I request that has not yet finished processing. To
PROCESSING avoid data integrity exposures, no KILL is attempted.

The KILL command program checked during The KILL command fails.
processing because of a no longer valid CICS pointer.
User response
System action None.
The KILL command fails. OC0524 NO KILL PERFORMED, DFHKCP IS
IN CONTROL, TRY AGAIN
User response
Enter the command. Explanation
OC0521 SELECTED TASK ALREADY DFHKCP is in control in the CICS address space before
MARKED FOR CANCEL a KILL is attempted. To avoid CICS integrity exposure,
the KILL command does not complete process.

The KILL command fails. An SQA getmain issued in behalf of the KILL command
was unsuccessful because not enough SQA storage
User response was available in the system.
None.
System action
OC0525 NO KILL PERFORMED, LIFO STACK The KILL command fails.
ERROR IN TASK TO BE KILLED
User response
Explanation
Increase the amount of SQA available to the system
When checking the LIFO stack of the task to be killed, and restart the session.
an error was found.
OC0529 KILL PROCESSING COMPLETE
System action
Explanation
The KILL command fails.
The KILL command was successful.
User response
System action
None.
This is an informational message.
OC0526 NO KILL PERFORMED, SELECTED
TASK IS KCP
User response
Explanation None.
The task selected with the KILL command represents OC0530 NO KILL PERFORMED, SYSEVENT
the CICS Task Control Program (KCP). FAILURE -CODE: X yy

The KILL command fails. A SYSEVENT macro issued in behalf of the KILL
command was unsuccessful. CODE: 08 indicates that
User response the DONTSWAP count of the CICS address space
has reached its maximum. CODE: 04 indicates that
None. the CICS address space was not the current address
space.
OC0527 NO KILL PERFORMED, SELECTED
TASK IS TCP
System action
Explanation The KILL command fails.
The task selected with the KILL command represents
the CICS Terminal Control Program (TCP). User response
System action
ATTENTION: This applies to messages OC0538
The KILL command fails. through OC0546: The KILL command and the KILL
FORCE command attempt to remove a task from your
CICS region. There are circumstances, however, in
User response
which this is not possible. The integrity of CICS and
None. its associated data cannot be guaranteed when either
of these commands is used. They should be used only
OC0528 NO KILL PERFORMED, GETMAIN
as a last resort.
FAILURE

OC0531 KILL HAS REQUESTED AN ABEND Explanation
OCKC PRIOR TO A FIRST
DISPATCH The purge task action was selected for a task from the
OMEGAMON Tasks panel.
Explanation
System action
An attempt to Kill a transaction failed because the
transaction had not yet been dispatched. OMEGAMON for CICS attempts to purge the task.

None. None.
OC0535 KILL HAS MARKED THE TASK FOR
User response ABEND S0C6 IN FILE CONTROL
Issue the Kill command again. If the task is still not

dispatched investigate the CICS region to determine Explanation
why the transaction is not being dispatched. A task was selected to be killed, but the task is running
OC0532 NO KILL PERFORMED, under CICS File Control.
OMEGAMON in CICS NOT
RESPONDING System action
The kill will be attempted once control of the task is
Explanation returned to CICS.
An attempt to kill a task with the Kill command failed
because CICS was not responding. User response
None.
System action
None. ABEND S0C6

Check the CICS logs to determine why the CICS region A currently dispatched task was selected to be killed.
is not responding.
OC0533 NO KILL PERFORMED, TASK System action
ALREADY MARKED FOR KILL
The task is killed by forcing a S0C6 abend.
Explanation
User response
A task was marked to be killed, but an attempt to kill
None.
the task had already been issued.
System action ABEND EIKI
None.
Explanation
User response A task which is not currently dispatched was selected
to be killed.
Wait for the initial kill to take effect.
OC0534 KILL HAS REQUESTED System action
OMEGAMON IN CICS TO PURGE
The task is killed with an EIKI abend once the task is
THE TASK
dispatched again.

None. IBM Z OMEGAMON for CICS issued a deferred KILL
request for a task. CICS rejected that request.
OC0538 KIL1 TASK NO. xxxxx: ABOUT TO
ISSUE PURGE REQUEST
System action
Explanation None. The selected task is not processed.
IBM Z OMEGAMON for CICS has determined that
the selected task exists and is able to request CICS User response
services to KILL the task. Check the system log for other messages from the
KILL process. These messages indicate what caused
System action the request to be rejected.
CICS will process the KILL request. OC0542 KIL1 TASK NO. xxxxx: TASK NOT
FOUND
User response
Explanation
Check the system log for further messages. These
messages will indicate the result of KILL processing. The selected task either had finished running or had
been processed by a previous KILL command.
OC0539 KIL1 TASK NO.xxxxx: DEFERRED
KILL ISSUED
System action
Explanation None. This is an informational message only.
OMEGAMON has requested CICS services to KILL the
selected task. The task is marked Cancel Inhibited or User response
Nonpurgeable. A deferred KILL request is issued to Ensure that the correct task was selected for KILL
attempt to KILL the task later in its processing. processing.
OC0543 KIL1 TASK NO. xxxxx: TASK
System action
ALREADY ABENDING
An attempt to KILL the task is made at an appropriate
time. Explanation
The selected task is already marked as abending. The
User response
task is processed by subsequent KILL commands.
Wait for CICS to process the KILL request.
OC0540 KIL1 TASK NO. xxxxx: TASK IN System action
VSAM I/O None. This is an informational message only.

The selected task is in a file control wait. It is not None. The abending task should complete abend
possible to KILL a task in this state and guarantee the processing.
integrity of CICS and its associated data.
OC0544 KIL1 TASK NO. xxxxx: THIS IS A
SYSTEM TASK
System action
The KILL request is not processed. Explanation
The selected task is a CICS System task. Such tasks
User response
are not eligible for KILL processing.
None. The task is not purged.
OC0541 KIL1 TASK NO. xxxxx: TASK System action
PURGE FAILED None. This is an informational message only.

Ensure that the correct task was selected for KILL The task requested with the CMQM command could
processing. not be found.
OC0545 KIL1 TASK NO. xxxxx: TASK
PURGE REQUESTED System action
The command stops processing normally after issuing
Explanation this error message.
IBM Z OMEGAMON for CICS has requested CICS
services to purge the selected task. User response
Make sure that the correct task was selected for the
System action CMQM command.
CICS purges the task. OC0592 INVALID VALUES SPECIFIED FOR
THE DUMP KEYWORD
User response
Explanation
None. The task should be purged by CICS.
The DUMP= keyword was specified with the TASK
OC0546 KIL1 TASK NO. xxxxx: INVALID command, but the values after the equal sign were not
TASK CONTROL BLOCKS valid.

During KILL processing, the control block structure of
The TASK command fails.
the selected task is verified. An error was detected;
therefore, the request cannot be processed.
User response
System action Review the command keywords and enter it again.
None. The task cannot be processed by the KILL OC0593 INVALID VALUES SPECIFIED FOR
command. THE DETAIL KEYWORD

Investigate the task in question. You should attempt The DETAIL= keyword was specified with the TASK
to ensure that CICS has not suffered a storage command, but the values after the equal sign were not
corruption that has damaged task-related control valid.
block structures.
OC0549 KILL PROCESSING ERROR System action
DURING OTE TCB PROCESSING The TASK command fails.

An error occurred while trying to kill a task running on Review the command keywords and enter it again.
an Open Transaction Environment TCB.
OC0595 INVALID KEYWORD FOR THIS
CICS RELEASE
System action
The task is not killed. Explanation
A keyword entered for the TASK command is not
User response
appropriate for the CICS release being monitored.
OC0590 Requested task(s) not found System action
The TASK command fails.

Review the command keywords and enter it again. While gathering information on tasks using TCP/IP
sockets an unidentified error occurred.
OC0600 TCP/IP SOCKET INTERFACE IS
NOT ACTIVE
System action
Explanation TCP/IP Sockets information is not displayed.
The TCPT command was entered to display CICS
TCP/IP socket information, but the CICS TCP/IP User response
Sockets interface has not been enabled. Contact IBM Software Support.
OC0604 WEB INTERFACE UNAVAILABLE
System action
PRIOR TO TS 1.2
None.
Explanation
User response
This message refers to an unsupported version of CICS
Enable the CICS TCP/IP Sockets interface and retry the and is obsolete.
command.
OC0601 UNABLE TO LOCATED TCP/IP System action
GLOBAL WORK AREA None.

A request to display CICS TCP/IP sockets information None.
failed because the TCP/IP Global Work Area was not
found in the CICS region. OC0605 INVALID WEB REQUEST FOR THIS
CICS RELEASE
System action
Explanation
TCP/IP Sockets information is not displayed.
and is obsolete.
User response
OC0602 TCP/IP SUPPORT UNAVAILABLE None.
PRIOR TO TS 1.2
User response
Explanation
None.
and is obsolete. OC0606 NO OPEN CICS INTERNAL
SOCKETS WERE FOUND
System action
Explanation
None.
A request to display TCP/IP service information failed
because no available TCP/IP Service sockets were
User response
located.
None.
OC0603 ERROR ENCOUNTERED DURING System action
TCP/IP TASK SCAN None.
CODE=(YES,HEX)

None. The CICS jobname parameter for a monitoring session
is invalid or omitted.
OC0607 UNSUPPORTED RELEASE OF
TCP/IP FOUND
System action
Explanation The session is not initiated.
A request to display TCP/IP Sockets interface
information failed because an unsupported release of User response
TCP/IP was detected. Restart the session using a valid CICS jobname
parameter.
System action
OC0701 OCRO SEARCH FAILED: aaaaaaaa
None.
Explanation
User response
An address space with a jobname of aaaaaaaa cannot
None. be found in the system.
OC0624 SSCVT CHAIN IS EMPTY
System action
Explanation The session is not initiated.
IBM Z OMEGAMON for CICS was unable to locate an
SSCVT chain for scanning. User response
Restart the session using a valid CICS jobname
System action parameter.
The command fails. OC0702 OCRO VALIDATION ABORTED;
TARGET IS SWAPPED OUT:
User response aaaaaaaa
The SSCVT chain should not be empty; there is a

Explanation
possibility that your MVS has been corrupted. If your
system appears to be running properly, contact IBM CICS validation for the target address space with
Software Support. jobname aaaaaaaa cannot be completed because the
address space was swapped out for longer than two
OC0625 INVALID SSCVT FOUND ON CHAIN minutes.

IBM Z OMEGAMON for CICS found an invalid entry in The session is not initiated.
the SSCVT chain during scanning.
User response
System action
Restart the session when the target address space is
The command fails. swapped in or ensure that the target it nonswappable.
User response OC0703 OCRO CICS VALIDATION FAILED:

aaaaaaaa
The SSCVT chain should not contain invalid entries,
there is a possibility that your MVS has been
Explanation
corrupted. If your system appears to be running
properly, contact IBM Software Support. The IBM Z OMEGAMON for CICS validation routine
could not determine that the target address space is
OC0700 OCRO CICS JOBNAME CICS.
PARAMETER IS MISSING OR
INVALID

The session is not initiated. The mode parameter for a monitoring session is invalid
or was omitted.
User response
System action
Restart the session after ensuring that the target
address space is CICS and that the CICS step is The session is not initiated.
currently running.
OC0704 OCRO UNSUPPORTED CICS User response
RELEASE RUNNING Restart the session using a valid mode parameter.
OC0708 OCXI CICS aaaaaaaa HAS
Explanation
ABENDED; CODE:Sbbb Ucccc
The version of CICS running is not supported by this
release of IBM Z OMEGAMON for CICS. Explanation
The CICS with job name aaaaaaaa abnormally
System action
terminated. The system and user codes are denoted
The session is not initiated. by bbb and cccc, respectively.

None. The session stops processing.
OC0705 OCXI CICS HAS TERMINATED:
aaaaaaaa User response
None.
Explanation
OC0709 OCXI INSUFFICIENT STORAGE TO
The target CICS with jobname aaaaaaaa stopped. START SESSION

The session stops processing. There is not enough virtual storage available to start a
session.
User response
System action
None.
The session is not initiated.
OC0706 OCRO CICS SWAPPED OUT:
aaaaaaaa
User response
Explanation Increase the available region.
The target CICS with jobname aaaaaaaa swapped out OC0710 OCXI INVALID PARAMETER LIST
at a point in IBM Z OMEGAMON for CICS’s processing PASSED TO OMEGAMON
where the session cannot continue.
Explanation
System action
The parameter string passed to IBM Z OMEGAMON for
The session stops processing. CICS is in error.

None. The session is not initiated.
OC0707 OCRO MODE PARAMETER IS
MISSING OR INVALID

Verify that such entries as the ROWS/COLS parameters An IBM Z OMEGAMON for CICS monitoring session
are correctly specified. detected the termination of the cross memory
interface task.
OC0711 OCXI OMEGAMON INIT FAIL -
CODE: aaaaaaaa
System action
Explanation The session stops processing.
IBM Z OMEGAMON for CICS initialization cannot
continue due to an error in the start-up environment. User response
Restart the session after first restarting the cross
System action memory interface task.
The session is not initiated. OC0716 OCRO VALIDATION ABORTED;
TARGET HAS TERMINATED:
User response aaaaaaaa
Check the system console log for any other messages.

Explanation
The target address space with jobname aaaaaaaa
OC0712 OCXI ERROR LOADING PRODUCT terminated while IBM Z OMEGAMON for CICS was
MODULE aaaaaaaa performing CICS validation.

The product module could not be loaded successfully.

IBM Z OMEGAMON for CICS stops processing.
None.
User response OC0718 OCXI CICS TO BE MONITORED IS

AN XRF ALTERNATE
Check that the named module is in the product library.
If it is not in the product library, contact IBM Software
Explanation
Support.
An attempt was made to start an IBM Z OMEGAMON
OC0713 OCXI TARGET CICS STALLED IN
for CICS session against a standby CICS region in an
INITIALIZATION
XRF configuration.

While waiting for CICS initialization, an IBM Z
IBM Z OMEGAMON for CICS stops processing the
OMEGAMON for CICS monitoring session is timed out.
session.

Start a session against the active CICS region.
User response OC0719 OCRO KOCCInn AND

CICS RKC2XM NUMBERS
Restart the session after CICS is initialized. INCOMPATIBLE
OC0714 OCXI CROSS MEMORY INTERFACE
TASK HAS TERMINATED Explanation
The RKC2XMnn DD statements in the KOCCInn and
CICS JCL procedures do not have the same numeric
suffix (denoted by nn). The suffix for the RKC2XMnn

DD statement must be a two-digit number from 00– User response
15. The default is 00.
System action OC0724 OCRO INSUFFICIENT MEMORY TO

INITIATE SESSION
Explanation
User response
There is not enough private storage less than the line
Match the RKC2XMnn DD statement in the JCL for the data areas and control blocks necessary to
procedure for KOCCInn to the one in the JCL for CICS. operate a monitoring session or subtask.
Restart the session.
OC0720 IBM Z OMEGAMON for CICS System action
LINKAGE STACK ERROR
Explanation
User response
The linkage stack maintained by IBM Z OMEGAMON
for CICS either ran out of available entries or an Increase the available region, or use the UMAX
attempt was made to pop the stack when the stack parameter to limit the number of users that might log
was empty. on.
OC0750 PWAI INSUFFICIENT MEMORY
System action FOR IBM Z OMEGAMON for CICS
PRODUCT WORK AREA IN CSA
Explanation
User response
The GETMAIN for a monitoring session product work
Contact IBM Software Support. area failed.
OC0721 OCRO UNABLE TO OBTAIN
MVS/XA LINKAGE STACK System action
Explanation
An attempt to allocate the IBM Z OMEGAMON for User response
CICS linkage stack in the beginning part of the private
storage has failed. Increase the amount of CSA available to the system
System action OC0752 PWAI INSUFFICIENT MEMORY

FOR DYNAMIC LOAD AREA
Explanation
User response
Session initialization has failed to allocate a required
Increase the amount of CSA available to the system internal work area due to insufficient storage
OC0723 OCRO UNABLE TO PROCESS CICS System action
RKC2XM DD STATEMENT
The session fails to initialize.
Explanation
User response
This is an internal error.
System action
Processing stops.

OC0753 PWAI INSUFFICIENT MEMORY OC0760 mmmm LOAD OF aaaaaaaa
FOR IBM Z OMEGAMON for CICS FAILED: CODE= bbbbbbbb
CROSS MEMORY WORK AREA REASON=cccccccc
The GETMAIN for an IBM Z OMEGAMON for CICS mmmm attempted to load the module identified by
session cross memory work area failed. aaaaaaaa and failed. The CODE=bbbbbbbb value
represents the return code and the ccccccccvalue is
System action the reason code associated with the LOAD failure.

System action
User response When mmmm is OCRO, the session is not initiated.
When mmmm is OCPR, processing continues; however,
Increase the amount of CSA available to the system some product functions will be unavailable.
OC0755 OCRO OCVRSN VALIDATION User response
FAILURE Locate the failure return code bbbbbbbb in the MVS
System Codesguide, correct the cause of the load
Explanation failure, and restart the session.
An attempt was made to start a version of IBM Z OC0761 OCRO ESTAEX PC FAILURE
OMEGAMON for CICS that does not recognize either
the release of the CICS region or the MVS operating
Explanation
system.
The IBM Z OMEGAMON for CICS session received a
System action nonzero return code from the ESTAEX macro. This is
usually caused by a lack of LSQA.
System action
User response
Ensure that the session is being started for an
operating system and CICS release that is supported
User response
by IBM Z OMEGAMON for CICS. If problems persist,
contact IBM Software Support. Increase the amount of CSA available to the system
and restart the session. If problems persist, contact
OC0759 OCRO LINK TO aaaaaaaa FAILED;
CODE=bbbbbbbb
OC0762 OCPR HOLD COUNT
Explanation DISPLACEMENT VALIDATION
FAILED
the load module identified by aaaaaaaa could not be
loaded. The ABEND code is represented by bbbbbbbb.
Explanation
System action IBM Z OMEGAMON for CICS was unable to verify the
location of the hold count field in the OUCB.
System action
User response
XMIT stops processing because IBM Z OMEGAMON for
Locate the ABEND code (bbbbbbbb) in the IBM System CICS components are unable to verify target address
Codes manual; correct the cause of the failure; and spaces if the CICS region is swappable.
User response

OC0763 OCPR(Vnnn) AND aaaaaaaa(Vyyy) OC0766 OCPR KOCGLBcc PTF aaaaaaa
INCOMPATIBLE INCOMPATIBLE WITH KOCCInn
PTF bbbbbbb
Explanation
Explanation
IBM Z OMEGAMON for CICS found a discrepancy in the
versions of modules OCPR (XMIT) and aaaaaaaa. During the load of a global data area module, IBM
Z OMEGAMON for CICS detected that the module
System action with the suffix cc was assembled with PTF aaaaaaa,
whereas the KOCCInn was using PTF bbbbbbb.
Further processing is stopped.
System action
User response
Initialization continues. Results are unpredictable.
Verify that all IBM Z OMEGAMON for CICS modules
are of the same version and restart the cross memory
User response
interface task.
OC0764 OCPR MAINTENANCE LEVEL assembled using the same service level as the IBM
MISMATCH BETWEEN CICS AND Z OMEGAMON for CICS code within the CICS region.
KOCCInn STEPLIB DATASETS
OC0767 OCPR KOCCInn AND GLOBALS
Explanation MUST BE AT THE SAME SERVICE
LEVEL
IBM Z OMEGAMON for CICS found a discrepancy in the
lengths of data areas in CICS and the equivalent area
Explanation
in the KOCCInn address space. IBM Z OMEGAMON
for CICS did not successfully copy all of the product This message follows message OC0766.
control data from the Global Data Area to the region.
This indicates that the version of the code in CICS is System action
different from what is running in the KOCCI.
The load of the global data area module continues.
Results are unpredictable.
System action
Further processing is stopped. User response
User response
assembled using the same service level as the IBM
Verify that all IBM Z OMEGAMON for CICS xKANMODR Z OMEGAMON for CICS code within the CICS region.
libraries in the CICS Library definition and the
OC0795 OCRO ERROR DURING CASB
xKANMOD datasets allocated to the KOCCI STEPLIB
INITIALIZATION
are at the same level
OC0765 OCPR EXTRACT AREA LENGTHS Explanation
DIFFERENT -- CICS (xxxx) and
KOCCInn (yyyy) An unexpected error occurred while building the CICS
Architecture Summary Block (CASB). The CASB is an
internal IBM Z OMEGAMON for CICS control block that
Explanation
is required for session start-up.
See message OC0764.
System action
System action
See message OC0764.
User response
User response
See message OC0764. Please quote the two data area
lengths if you contact IBM Software Support.

OC0796 OCRO UNABLE TO OBTAIN THE MVS LEVEL IT IS RUNNING
STORAGE FOR CASB ON
The first session or subtask initialized against a An attempt was made to execute a monitoring module
particular CICS was unable to obtain a CASB work area in an incompatible operating system.
that is required for monitoring of that CICS region.
System action
System action The session does not initiate.
The session or subtask fails to initialize. Further
sessions or subtasks initialized against the same CICS User response
region are also likely to fail.
Verify that the correct version of IBM Z OMEGAMON
for CICS is installed.
User response
OC0802 OCRO OCSS SSCVT NOT FOUND
ON CHAIN
OC0799 OCRO APF AUTHORIZATION Explanation
CHECK FAILED
The monitor was unable to locate the SSCVT control
block.
Explanation
An IBM Z OMEGAMON for CICS session is not running System action
APF authorized.
System action
User response
The session stops processing.
This message could occur if XMIT (cross memory
interface task) is not running as a subtask of the
User response interface. If this is not the case, contact IBM Software
Verify that all IBM Z OMEGAMON for CICS Support.
modules reside in authorized libraries. The IBM Z
OC0803 OCPR SSCVT CHAIN IS EMPTY
OMEGAMON for CICS Configuration and Customization
Guide contains additional information about APF
authorization. Explanation
OC0800 OCPR ENVIRONMENT MISMATCH, The SSCVT chain was scanned, and was found to be
SYSTEM MUST BE MVS/ESA OR empty.
HIGHER
System action
Explanation The session does not initiate and a user abend U0803
An attempt was made to execute at an operating occurs with a dump.
system level prior to MVS/ESA.
User response
System action If problems persist, contact IBM Software Support.
OC0804 OCPR INVALID SSCVT FOUND ON
CHAIN
User response
None. Explanation
OC0801 OCRO ENVIRONMENT MISMATCH, While searching through the Subsystem
THE MVS LEVEL DOES NOT MATCH Communication Vector Table chain for the element

belonging to the OMEGAMON for CICS (3270) components in the CICS address space must be
interface, IBM Z OMEGAMON for CICS encountered an initialized manually at a terminal through the "OMEG
improperly formatted SSCVT. INIT" transaction. Start the XMIT subtask by issuing
the modify command:
System action /F CIjobname,START XMIT
IBM Z OMEGAMON for CICS abends with a U0804
completion code. Once the interface task is active, reply to the OC0806
message.
User response • RETRY - The SSCVT chain will be searched again for
Indicates that main storage was overlaid. If problems the subtask. If active, initialization will proceed. If
persist, contact IBM Software Support. not, the WTOR message will be reissued.
OC0805 OCRO CROSS MEMORY INTERFACE OC0807 ARINIT UNABLE TO GETMAIN

TASK IS NOT ACTIVE STORAGE FOR AR$WORK
An initializing IBM Z OMEGAMON for CICS session IBM Z OMEGAMON for CICS attempted to GETMAIN
found that the cross memory interface task (XMIT) is storage for a required control block. The GETMAIN was
not active. unsuccessful. IBM Z OMEGAMON for CICS is unable to
continue without this storage.
System action
System action
The subtask, either an IBM Z OMEGAMON for CICS
session, KOCRTA, KOCDEX, or ONDC, ends with a
User response U0807 abend code.
Ensure that the cross memory interface task is running
as a subtask of the interface, then restart the session. User response
OC0806 XMCR OCCIREQ SPECIFIED IN Increase the amount of CSA available to the system
STARTUP JCL BUT RKC2XM NOT and restart the session.
ACTIVE. REPLY ABEND, IGNORE
OR RETRY. OC0808 OCPR XM INTERFACE TASK
ALREADY ACTIVE
Explanation
Explanation
The //OCCIREQ DD statement was included in the
CICS start-up JCL but no entry could be found in A second cross memory interface task was started
the subsystem communication vector table (SSCVT) while another one is still active.
for the cross memory interface task (XMIT) with the
specified suffix. System action
The task stops processing.
System action
CICS initialization is suspended until the operator User response
responds to the console message.
None.
User response OC0809 OCPR XM INTERFACE TASK IS

ACTIVE
Enter one of the following replies:
• ABEND - The CICS address space is abended with a Explanation
U0806 code
The cross memory interface task completed
• IGNORE - The OCCIREQ requirement is overridden initialization and is waiting for work.
and CICS initialization continues. When IBM Z
OMEGAMON for CICS becomes available, support

None. The cross memory interface task received a nonzero
return code from the ESTAEX macro. This is usually
User response caused by a lack of LSQA.
None.
System action
OC0810 OCPR XM INTERFACE TASK IS The cross memory interface task stops processing.
TERMINATING
User response
Explanation
Decrease the amount of CSA available to the system
The cross memory interface task received a request to and restart the session. If problems persist, contact
terminate. IBM Software Support.
System action OC0814 ARINIT ALESERV MACRO

FAILURE: CODE=rc
None.
Explanation
User response
An attempt to add an entry for the monitored CICS
None. region to an access list failed.
OC0811 OCPR XM INTERFACE TASK HAS
ABENDED System action
Processing continues, but cross-memory code will not
Explanation be executed optimally.
The cross memory interface task error exit intercepted
an abnormal termination. User response
Review the return code, referring to the MVS
System action Assembler Services Reference Manual.
The cross memory interface task attempts resource OC0815 OCPR SUBSYSTEM TABLE BUILD
cleanup before continuing with termination. FUNCTION WAS UNABLE TO
CREATE ITS TABLES
User response
Explanation
Restart XMIT, and contact IBM Software Support.
An internal error occurred during the attempt to create
OC0812 OCPR XM INTERFACE TASK
the IBM Z OMEGAMON for CICS SSCVT and related
RESOURCE CLEANUP IS
control blocks.
COMPLETE
System action
Explanation
The cross memory interface task stops processing.
The cross memory interface task successfully
completed resource cleanup.
User response
System action Ensure that the interface is active in the system and
that no other attempt is being made to start the cross
None.
memory interface task. Then attempt to start the cross
memory interface task again.
User response
OC0816 OCPR ENTRY TABLE CREATE
None. FAILED
OC0813 OCPR ESTAEX MACRO FAILURE

An error occurred during the attempt to build a Processing continues unless the CICS job has the
program call-entry table. OCCIREQ DD statement in the JCL stream, indicating
that the interface is required. If the OCCIREQ card is
System action present, the OMEGAMON code in CICS gives the user a
message to ABEND, IGNORE, or RETRY.
The cross memory interface task (XMIT) stops
processing with a U0816 abend code.
User response
User response Verify that the cross memory interface task (XMIT)
is active as a subtask of the OMEGAMON for CICS
Contact IBM Software Support. (3270) interface job aaaaaaaa, and that you are using
compatible product releases.
OC0817 OCPR LINKAGE INDEX RESERVE
FAILED OC0820 OCPR KOCCInn RKC2XM NUMBER
INVALID
Explanation
Explanation
An attempt to reserve a linkage index failed.
An invalid RKC2XM DD card was found in the KOCCInn
System action JCL. The RKC2XM number must be blank or a two-digit
number from 00–15.
The cross memory interface task (XMIT) stops
processing with a U0817 abend code.
System action
User response The system uses the default RKC2XM number, 00.

User response
OC0818 OCRO aaaaaaaa IS NOT A VALID
None.
PROGRAM NAME
OC0821 OCPR UNABLE TO PROCESS
Explanation KOCCInn RKC2XM DD STATEMENT
An invalid program name was requested in a START

Explanation
command. For valid program names, see the IBM Z
OMEGAMON for CICSConfiguration and Customization This is an internal error.
Guide.
System action
System action
Processing stops.
START processing ends.
User response
User response
Correct the START command and enter it again.
OC0822 OCPR WILL USE DEFAULT
OC0819 WARNING: CONNECT TO OCCI KOCCInn RKC2XM NUMBER 00
aaaaaaaa FAILED
Explanation
Explanation
The system uses a default DD of RKC2XM00.
An attempt to connect to OMEGAMON for CICS (3270)
interface entry table failed. The jobname of the
System action
interface is denoted by aaaaaaaa.
None.

User response OC0830 OCRO CAUTION - CICS
DISPATCHING PRIORITY
None. GREATER THAN 239
OC0823 OCPR KOCCInn IS USING
RKC2XMnn DD NAME Explanation
The dispatching priority of the target CICS is greater
Explanation than 239. A missing data situation, in which response
The OCPR KOCCInn has found an RKC2XMnn DD card time collector and historical task display data are lost,
defined in the KOCCInn JES JCL deck when it was might result if the interface runs at a priority less than
initializing. CICS.

The system uses nn as the RKC2XM number. Processing continues.

None. Determine why the CICS dispatching priority has been
set so high, and reset it to a less priority if possible.
OC0824 OCRO ALESERV MACRO FAILURE:
CODE=rc OC0831 DL/I COLLECTOR NOT STARTED;
NO DL/I PROCESSING PRESENT
Explanation
Explanation
An attempt to delete an entry for the monitored CICS
region from an access list failed. IBM Z OMEGAMON for CICS has been started up in
a CICS region that does not have DL/I present but is
using a global module with the DLI collector activated.
System action
Task continues terminating normally. System action
The DLI collector will not collect DLI clocks and
User response counters.
Review the return code, referring to the MVS
Assembler Services Reference Manual. User response
OC0827 OCRO TASK STARTUP FAILED -- Code and assemble a GLOBAL module without DLI
XMIT RESIDES IN A DIFFERENT collection. Add an KOCGLBxx DD card to the CICS job
ADDRESS SPACE and the next restart of the CICS region will not put out
this message.
Explanation OC0832 DL/I COLLECTOR NOT STARTED;
An attempt was made to start an IBM Z OMEGAMON DFHCMP VALIDATION FAILED
for CICS component in an address space other than
the one in which XMIT is running. Explanation
IBM Z OMEGAMON for CICS has detected an error in
System action its validation of the DFHCMP module that is addressed
IBM Z OMEGAMON for CICS abends the task. by the CSA address in the CSATRNAC field.

Verify that the interface has XMIT running for the CICS The DLI collector stops collecting DLI clocks and
region to be monitored. TSO and SPF users must use counters.
the VTM1 component, rather than attempting to run
IBM Z OMEGAMON for CICS within the TSO address
space.

Ensure that KOCOME00 is the first entry in the PLTPI IBM Z OMEGAMON for CICS has detected an error
table. that previously caused termination of DLI collector
processing and therefore prevents the restart.
OC0833 DL/I COLLECTOR NOT STARTED;
OMOCMP NOT FOUND
System action
Explanation The DLI collector does not start.
The load of the DLI collector load module has failed.
User response
System action Check to see if there were errors the last time that the
collector processing terminated; if not, contact IBM
The DLI collector stops collecting DLI clocks and Software Support.
counters.
OC0837 DL/I COLLECTOR NOT FOUND,
User response DISABLE REQUEST IGNORED
Check the associated loader messages in the CICS job

Explanation
log (CSVxxxxx) and fix the indicated problem.
An attempt has been made to stop the collector when
OC0834 DL/I COLLECTOR DISABLE
it was not active.
PROCESSING COMPLETE
System action
Explanation
None.
This message is issued by CCDI when the DLI collector
is turned off.
User response
System action None.
None. OC0838 OCRO FAILURE TO LINK
TO KOCDGS00, BLST BUCKET
User response OVERRIDES HAVE NOT BEEN
DONE
None.
OC0835 DL/I COLLECTOR NOT STARTED; Explanation
CSATRNAC PROCESSING FAILED
An attempt to link to the KOCDGS00 modules has
failed.
Explanation
IBM Z OMEGAMON for CICS has detected that the System action
CSATRNAC field in the CICS CSA has changed while
The bottleneck analysis buckets are not overridden
DLI collection is active.
by the settings coded on the KOCBLST macros in the
global assembly. If no KOCBLST macros are coded,
System action this has no effect.
The DLI collector stops collecting DLI clocks and
counters. User response
Look on the system log for messages from the MVS
User response loader (CSVxxxx) to discover why the link failed. The
bucket settings can be changed online using the BLST
Verify that the KOCOME00 program is the first entry in
command. These settings remain in effect until the
the PLTPI table.
common interface is recycled.
OC0836 DL/I COLLECTOR NOT STARTED
OC0839 DL/I COLLECTOR SUCCESSFULLY
DUE TO PREVIOUS ERROR
ENABLED
TERMINATION

IBM Z OMEGAMON for CICS has enabled the DLI None.
collection mechanism in CICS.
OC0853 OCPR MONITORING ENDED FOR
cicsname
System action
The DLI collector can now be started in order to collect Explanation
DLI clocks and counters.
The OMEGAMON for CICS menu system address space
has detected that it is no longer monitoring the
User response CICS region cicsname. This means that Task History,
None. Bottleneck Analysis, and Response Time Analysis have
shut down for this region and that no users are logged
OC0850 OCPR TARGET CICS FOR KOCGLB on to the menu system for this region.
DELETE NOT FOUND
System action
Explanation
The XMIT Global module delete command specified a
CICS jobname that was not found in the system.
User response
System action None.
The modify command is ignored. OC0910 UNABLE TO LOCATE CSECTS IN

aaaaaaaa
User response
Explanation
Enter the modify command using a valid CICS jobname
parameter. The VALV routine has been called to verify that a load
module has the correct version for the product that is
OC0851 OCPR COMMAND FORMAT IS running but the load module contains no CSECTS.
INVALID
System action
Explanation
The calling routine fails and then issues a message
An unacceptable modify command was sent to the indicating the results of the failure.
XMIT subtask.
User response
System action
Check the load module aaaaaaaa to see if it is in
The modify command is ignored. error. If you can find no obvious problem, contact IBM
Software Support.
User response OC0940 MVSDRV WORK AREA GETMAIN
Enter the modify command after correcting the syntax. FAILURE
OC0852 OCPR KOCGLBcc USED BY

Explanation
aaaaaaaa HAS BEEN DELETED
Not enough storage was available for the work area
Explanation used to load an MVS, CICS, IMS, or DB2 version
dependent module.
The request that XMIT subtask delete an KOCGLB
module was successfully processed for the CICS job
System action
identified by aaaaaaaa.
The load, and its invoking facility, fail.
System action
None.

User response OC0944 MVSDRV ERROR LOADING
aaaaaaaa
Explanation
OC0941 MVSDRV MVS VERSION
UNKNOWN An error occurred when loading aaaaaaaa, an MVS,
CICS, IMS or DB2 version dependent module.
Explanation
System action
When attempting to load an MVS, CICS, IMS or DB2
version dependent module, MVSDRV was unable to The load fails.
verify the MVS version in the system.
User response
System action Verify that the IBM Z OMEGAMON for CICS installation
The load fails. process completed successfully and that module
aaaaaaaa is in the IBM Z OMEGAMON for CICS
common interface library.
User response
OC0945 MVSDRV INVALID HEADER
After obtaining a dump of the CVT, contact IBM FORMAT IN aaaaaaaa
Software Support.
OC0942 MVSDRV KOCVRS00 FAILURE Explanation
An error has been encountered with verifying load
Explanation module aaaaaaaa for a correct internal header.
When attempting to load an MVS, CICS, IMS or
DB2 version dependent module, the link to module System action
KOCVRS00 failed.
The load of aaaaaaaa fails.
System action
User response
The link fails and the invoking facility stops processing.
User response OC0946 MVSDRV(Vnnn) AND
aaaaaaaa(Vyyy) INCOMPATIBLE
process completed successfully and that KOCVRS00 is
in the IBM Z OMEGAMON for CICS common interface Explanation
library. The version of module MVSDRV and the module it is
OC0943 MVSDRV NO TABLE ENTRY FOR attempting to load are incompatible.
aaaaaaaa
System action
Explanation The load and its invoking facility fail.
MVSDRV was invoked to load an MVS, CICS, IMS or
DB2 version dependent module but the module is User response
unknown to MVSDRV.
process completed successfully and that module
System action aaaaaaaa is in the IBM Z OMEGAMON for CICS
The load and its invoking facility fail. common interface library.
OC0960 OCDB UNABLE TO OBTAIN WORK
User response AREA

Insufficient storage was available for the internal work Check the console for messages that may explain the
area obtained by the OCDB command. cause of the load failure. If problems persist, contact
System action OC0964 OCDBHD MISSING MODULE NAME
Explanation
User response A request for module header data could not be
Increase the region size for the IBM Z OMEGAMON for satisfied because a module name was not supplied.
CICS common interface address space.
System action
OC0961 OCDB PARAMETER SCAN ERROR
Explanation
User response
An internal error occurred while attempting to process
the OCDB parameter list. Provide the name of the module and enter the
command.
System action OC0965 OCDBHD UNABLE TO LOCATE
The command stops processing. aaaaaaaa

Check that all operands of OCDB are correct, make The module aaaaaaaa could not be found on the load
any necessary changes and enter the command. If list of either CICS or the common interface.
System action
OC0962 OCDB INVALID CONTROL
PARAMETER aaaaaa The command stops processing.

The operand aaaaaa is not recognized by OCDB. Check that the module name is correct. If an error
is found, correct the module name and enter the
System action command. If the name is correct, use the PEEK
command to inspect the load lists of both the CICS
The command stops processing. and KOCCInn address spaces. If the module was
not loaded into storage, then its header cannot be
User response displayed by OCDB.
Use a valid control operand in the OCDB command. OC0966 OCDBHD MODULE aaaaaaaa NOT
Obtain a list of available options by entering OCDB VALID FOR SEARCH
without operands.
Explanation
OC0963 OCDB ERROR LOADING aaaaaaaa
Module aaaaaaaa does not conform to the naming
Explanation convention associated with programs that contain a
diagnostic header. The module name must be eight
The module identified by aaaaaaaa could not be characters long and begin with the letters KOC.
brought into virtual storage by OCDB.
System action
System action

Correct the module name and enter the command. An attempt was made to load the default global
module, but that module is not available.
OC0967 OCDBHD MODULE aaaaaaaa DOES
NOT HAVE A HEADER
System action
Explanation The requested session with OMEGAMON for CICS is
not started.
The specified module, aaaaaaaa, was not link-edited
with a diagnostic header.
User response
System action Make sure that the default global module is in the
OMEGAMON load library.
None.
OC0998 OCRO LOAD OF GLOBAL MODULE
User response aaaaaaaa FAILED, DEFAULT
KOCGLB UNAVAILABLE
None.
OC0970 MAXR UNABLE TO LOCATE Explanation
OCEXEC INTERFACE
An attempt was made to load a suffixed global module,
but that module is not available. The default (non
Explanation suffixed) module is also unavailable.
The CPU limiting function has been unable to locate
the required IBM Z OMEGAMON for CICS control System action
blocks in the CICS region.
The requested session with OMEGAMON for CICS is
not started.
System action
The MAXR exception is not available. User response
Make sure that the user-suffixed module is in the
User response OMEGAMON load library. You should also ensure that
the default module is available.
Check the messages on the CICS job log when IBM
Z OMEGAMON for CICS is started in the CICS region. OC0999 INTERNAL ERROR - CALL CANDLE
If you can find no obvious problem, contact IBM CUSTOMER SUPPORT
Software Support.
OC0972 OCPR INTERNAL ERROR, Explanation
CONTACT IBM CUSTOMER
IBM Z OMEGAMON for CICS detects an internal
SUPPORT SERVICES
sequence that should not occur.

An internal logic error has been detected while IBM Z OMEGAMON for CICS executes an ABEND 1,
processing session initialization. DUMP for the task.

The session fails to initialize. Contact IBM Software Support.
User response OC1000 OCOMEG INQUIRE TRANSACTION

FAILED WITH cccccccccc
OC0997 OCRO LOAD OF GLOBAL MODULE
KOCGLB FAILED

Explanation Guide for more information regarding changes to the
CICS PLT.
During OMEGAMON shutdown processing, a response
of cccccccccc was returned in EIBRESP for an INQUIRE OC1003 LOAD FAILED FOR MODULE
TRANSACTION command issued by KOCOME00. aaaaaaaa

KOCOME00 stops processing but OMEGAMON service OMEGAMON II could not load a required program from
tasks remain active. DFHRPL.

If INQUIRE TRANSACTION failed with NOTAUTH, OMEGAMON II does not supply the response time
make sure the user who initiated the OMEGAMON collector, ONDV collector, or interval record collector
or the CICS shutdown process is also authorized to with data.
issue an INQUIRE TRANSACTION command against
the transaction being entered. User response
OC1001 OMEG DEFINED WITH Make sure the dataset containing all the modules from
TRANSACTION CLASS - the distribution tape is present in DFHRPL.
PROCESSING STOPPED
OC1004 LINK FAILED FOR MODULE
aaaaaaaa
Explanation
Transaction OMEG is defined with TCLASS=nn, where Explanation
nn is 1 through 10. It should be defined with
TCLASS=NO. OMEGAMON II could not find a required program from
DFHRPL.
System action
System action
IBM Z OMEGAMON for CICS does not supply the
response time collector, ONDV collector and interval OMEGAMON II does not supply the response time
record collector with data. The service task is not collector, ONDV collector, or interval record collector
started. with data.

Define transaction OMEG with TCLASS=NO. Make sure the data set containing all the modules from
the distribution tape is present in DFHRPL.
OC1002 KOCOME00 PHASE 2 PLT
PROCESSING IGNORED OC1005 NEW VERSION OF KOCOME00
NEEDED TO SUPPORT RELEASE
Explanation
Explanation
The KOCOME00 program could not run because it was
not entered in the PLT in the correct position for phase OMEGAMON II found a back level version of a module.
2 processing.
System action
System action OMEGAMON II does not supply the response time
The KOCOME00 program does not run. collector, ONDV collector, or interval record collector
with data.
User response
User response
Verify that the entry for the KOCOME00 program
appears in the PLT after DFHDELIM. See the IBM Z Make sure the data set containing all the modules from
OMEGAMON for CICS Configuration and Customers the distribution tape is present in STEPLIB. Delete any
modules from prior releases of OMEGAMON II.

OC1006 COMMAND PROCESSING TABLE IS User response
MISSING
Explanation OC1010 KOCOME00 INCORRECTLY

DEFINED AS RELOAD=YES
This is an internal error with Tivoli OMEGAMON II.
Explanation
System action
The program KOCOME00 was defined as RELOAD=YES
Tivoli OMEGAMON II does not supply the response when it must be RELOAD=NO.
time collector, ONDV collector, or interval record
collector with data.
System action
User response Tivoli OMEGAMON II does not supply the response
Contact IBM Software Support. collector with data.
OC1007 DEBUG CHAIN ANCHOR IS 0
User response
Explanation Use CEDA to change the definition for KOCOME00 and
This is an internal error with Tivoli OMEGAMON II. retry.
OC1011 CICS LOAD FAILED FOR
System action KOCOME00
The DEBUG command is ignored.

Explanation
User response The program KOCOME00 could not be loaded from the
RPL library.
OC1008 cccccccc IS AN INVALID System action
FUNCTION REQUEST
Tivoli OMEGAMON II does not supply the response
Explanation collector with data.
The option specified with OMEG is incorrect.
User response
System action Make sure the program KOCOME00 is present in an
The OMEG transaction is ignored. RPL library.
OC1012 AUTHORIZATION FAILED WHEN
User response LOADING KOCOME00
Make sure the option on the OMEG transaction is valid.
Explanation
OC1009 CANNOT FIND MODULE LIST TO
LOAD FROM STEPLIB CICS prevented Tivoli OMEGAMON II from loading
KOCOME00.
Explanation
System action
This is an internal error with Tivoli OMEGAMON II.
System action collector with data.

Make sure OMEG and KOCOME00 are defined without This is an informational message in response to a
security as described in the IBM Z OMEGAMON for debug request.
CICS Configuration and Customization Guide.
OC1013 COMMON AREA VERSION cccccccc System action
DETECTED Processing continues.

Tivoli OMEGAMON II found a back level version of a None.
module.
OC1017 LINK FAILED FOR MODULE
cccccccc DURING COMMAND
System action
PROCESSING
time collector, ONDV collector, or interval record Explanation
User response
System action
Make sure the dataset containing all the modules from
the distribution tape is present in STEPLIB. Delete any Processing continues.
modules from prior releases of Tivoli OMEGAMON II.
OC1014 BYPASS IS SET, KOCOME00 User response
PROCESSING TERMINATING Contact IBM Software Support.
OC1018 INITIALIZATION HAS ALREADY
Explanation
COMPLETED, INIT IGNORED
Explanation
System action
OMEG INIT was entered, but initialization was already
Tivoli OMEGAMON II does not supply the response performed.
collector with data. System action
User response
OC1015 COMMAND PROCESSING NOT None.
AVAILABLE, INIT NOT COMPLETE
OC1019 Tivoli IBM Z OMEGAMON for
CICS on z/OS INITIALIZATION
Explanation
COMPLETE
An OMEG INIT was not done.
Explanation
System action
The IBM Z OMEGAMON for CICS on z/OS initialization
The command is ignored. is complete.

Perform an OMEG INIT and enter the command. None.
OC1016 (The text varies.)

None. IBM Z OMEGAMON for CICS will load its modules from
the RKANMOD data set.
OC1020 IBM Z OMEGAMON for CICS
TERMINATION IS COMPLETE
System action
Explanation None.
The IBM Z OMEGAMON for CICS termination is
complete. User response
None.
System action
None. TERMINATION IN PROGRESS

None. IBM Z OMEGAMON for CICS termination is in progress.
OC1021 MVS nnn AND CICS yyy:
UNSUPPORTED ENVIRONMENT System action
None.
Explanation
The versions of MVS and CICS that are currently User response
running are displayed in this message. One version, None.
normally CICS, is not supported by this release of IBM
Z OMEGAMON for CICS. OC1025 IBM Z OMEGAMON for CICS
RESTART IN PROGRESS
System action
Explanation
IBM Z OMEGAMON for CICS fails to initiate.
IBM Z OMEGAMON for CICS restart is in progress.
User response
System action
See the Program Directory for IBM Z OMEGAMON
for CICS for versions supported at your release level None.
and the current Preventive Service Planning (PSP)
information for versions supported in subsequent User response
maintenance.
None.
SUCCESSFULLY DE-INSTALLED OC1026 IBM Z OMEGAMON for CICS
INITIALIZATION IN PROGRESS
Explanation
Explanation
IBM Z OMEGAMON for CICS has been de installed
from the CICS region. IBM Z OMEGAMON for CICS initialization is in
progress.
System action
System action
None.
None
User response
User response
None.
None.
OC1023 RKANMOD IS IN USE FOR
PROGRAM LOADING

OC1027 ALTERNATIVE TRANSACTION ID Explanation
tttt WILL BE USED
For CICS/MVS users only, this message indicates
that IBM Z OMEGAMON for CICS was previously
Explanation deinstalled and that to permit reinstallation the
During PLTPI processing, a transaction ID of tttt, rather program KOCOME00 must be refreshed.
than the default of the OMEG transaction, was found.
System action
System action The command is rejected.
Processing continues. Tivoli OMEGAMON II will run
under the alternative transaction ID. User response
Issue the CEMT SET PROG(KOCOME00) NEW
User response command and retry the original command.
None. OC1031 DE-INSTALL HALTED BECAUSE
OC1028 INQUIRE TRAN RESP nnnnnnnn, CROSS-MEMORY CONNECTION
OMEG DEFAULT USED NOT ESTABLISHED
During PLTPI processing, a response of nnnnnnnn was IBM Z OMEGAMON for CICS de-install processing
returned in EIBRESP for an INQUIRE TRANSACTION stopped. The OMEG REMOVE command was rejected
command issued by KOCOME00. because the OMEGAMON cross-memory connection
was not established before the command was issued.
System action
System action
KOCOME00 will use the default transaction ID of
OMEG. If transaction OMEG is not defined, Tivoli The command is rejected.
OMEGAMON II processing within CICS will not start.
User response
User response The OMEGAMON cross-memory interface task should
Contact IBM Software Support. be active and connected to the common interface.
Make sure the IBM Z OMEGAMON for CICS address
OC1029 PCT ENTRY NOT FOUND FOR space is active and OMEGAMON has been fully
MODULE KOCOME00 initialized in the CICS region before you issue the
OMEG REMOVE command.
Explanation OC1032 DE-INSTALL HAS ALREADY
During PLTPI processing, no transaction ID that BEEN PERFORMED; NOTHING TO
specified the KOCOME00 module was found. REMOVE

OMEGAMON does not supply the response time IBM Z OMEGAMON for CICS de-install processing
collector, the ONDV collector, or interval record has completed on prior execution of OMEG REMOVE
collector with data. command. However, this command was issued again,
but there is nothing to de-install or remove.
User response
System action
Define the transaction that initiates the OMEGAMON-
to-CICS interface (that is, OMEG or an alternative ID). The command is rejected.
OC1030 OMEG REMOVE HAS BEEN DONE,

NEWCOPY KOCOME00 AND RETRY
User response
None.

OC1033 DE-INSTALL HALTED BECAUSE System action
OMEGAMON INITIALIZATION NOT
COMPLETED The initialization of the OMEGAMON program in the
CICSPlex SM address space is ignored.
Explanation
User response
IBM Z OMEGAMON for CICS de-install processing or
OMEG REMOVE command cannot continue because None.
either OMEGAMON has not been fully initialized in the OC1036 THE OMEGAMON IS NOT BEING
CICS address space or the common interface is not LOADED FROM AN AUTHORIZED
active. LIBRARY

The command is rejected. The library concatenation that OMEGAMON is being
loaded from in the CICS address space is not APF
User response authorized.
The IBM Z OMEGAMON for CICS address space must

be active and OMEGAMON must be fully initialized in System action
the CICS region before de-install processing can be OMEGAMON II for CICS did not initialize in the CICS
initiated. region.
OC1034 EXEN MODULE KOCOME00
WILL RUN IN (THREADSAFE | User response
QUASIREENTRANT) MODE
Verify that all the libraries in the RKANMOD
concatenation are APF authorized.
Explanation
The KOCOME00 module will run in threadsafe or RECYCLE START FAILURE
quasireentrant mode. If KOCOME00 is defined to CICS
with CONCURRENCY(THREADSAFE), the module will
execute in threadsafe mode; otherwise, the module Explanation
will execute in quasireentrant mode. EXEN refers to During the recycle processing for OMEGAMON II for
the OMEGAMON CICS EXit ENabling code. CICS there was a failure in starting the OMEGAMON
transaction to re initialize in the CICS region.
System action
None. System action
OMEGAMON II for CICS did not initialize in the CICS
User response region.
This is an informational message that only applies to

CICS/ TS 2.2 with Version 520 of IBM Z OMEGAMON User response
for CICS. Attempt to manually restart the OMEGAMON using
the OMEG INIT transaction. Contact IBM Software
OC1035W OMEGAMON II FOR CICS CANNOT
Support.
BE INITIALIZED IN A CMAS
REGION. OC1099 DEBUG LIST COMPLETE. SEE
CONSOLE LOG FOR OUTPUT
Explanation
The OMEGAMON program, transactions, and CICS Explanation
Exits cannot be initialized in a CICSPlex SM address The output in response to an OMEG DEBUG command
space. is complete.
System action
None.

None. In addition to the usual documentation, send an
assembled listing of the MCT and KOCGLB to IBM
OC1100 QRYC COULD NOT BE LOCATED OR
Software Support.
WAS NOT LOADED
OC1130 DICTIONARY ENTRY FOR RTYPE
Explanation IN THE MCT IS MISSING
Tivoli OMEGAMON II could not load a program it

Explanation
required for monitoring CICS transactions.
Tivoli OMEGAMON II could not find the field RTYPE in
System action the CICS monitoring record.
Support for umbrella services, MAXR processing and

System action
file and database statistics is disabled.
Tivoli OMEGAMON II does not write umbrella, DL/I
User response or DB2 data to CMF. In addition, the response
time collector and ONDV collector contain only one
Enter the CICS transaction OMEG DEBUG and send in a record per transaction regardless of the number of
copy of the CICS SYSLOG to IBM Software Support. conversations.
OC1101 EVENT MONITORING POINT NOT
DEFINED IN THE MCT User response
Modify your MCT to include field 112 (RTYPE).
Explanation See the CICS Resource Definition (MACRO) for more
information.
An event monitoring point (EMP) was defined to Tivoli
OMEGAMON II in the KOCEPOPT macro in KOCGLB, OC1131 DICTIONARY ENTRY FOR BASIC
but the EMP was not defined in theCICS Monitor USER DATA IN THE MCT IS
Control Table. MISSING

Tivoli OMEGAMON II does not write umbrella, DL/I or Tivoli OMEGAMON II could not find the entry in
DB2 data to CMF. the CICS monitoring control table for the user event
monitoring point that matches the one specified in the
User response KOCEPOPT macro in KOCGLB.
Make sure the MCT contains the EMP definitions. See

System action
the IBM Z OMEGAMON for CICS Configuration and
Customization Guide for more details. Tivoli OMEGAMON II does not write umbrella data to
CMF.
OC1102 EXEC CICS MONITOR POINT
FAILED
User response
Explanation Make sure you have an event monitoring point defined
in the MCT and that the entry name and field name for
An error occurred as Tivoli OMEGAMON II tried to
this point match the name in the KOCEPOPT macro.
write data to CMF.
If this problem persists, send an assembled listing
of your KOCGLB and a CICS system dump to IBM
Tivoli OMEGAMON II does not write umbrella, DL/I or OC1132 DICTIONARY ENTRY FOR DL/I
DB2 data to CMF. USER DATA IN THE MCT IS
MISSING

Tivoli OMEGAMON II could not find the entry in Contact IBM Software Support.
the CICS monitoring control table for the user event
OC1135 AUTHORIZATION FAILED FOR SMF
WRITE, LOGGING STOPPED
KOCEPOPT macro in KOCGLB.

Tivoli OMEGAMON II does not write DL/I data to CMF. Tivoli OMEGAMON II attempted to write an SMF record
containing transaction related data for a CICS V 1.7
or 2.1 system, but was not authorized for the SMF
Make sure you have an event monitoring point defined
in the MCT and that the entry name and field name for System action
If this problem persists, send an assembled listing Tivoli OMEGAMON II does not log any transaction
of your KOCGLB and a CICS system dump to IBM related monitoring data to SMF.
Software Support.
User response
OC1133 DICTIONARY ENTRY FOR DB2
USER DATA IN THE MCT IS Contact IBM Software Support.
MISSING
OC1136 DICTIONARY ENTRY FOR WLM
USER DATA IN THE MCT IS
Explanation MISSING
Tivoli OMEGAMON II could not find the entry in
the CICS monitoring control table for the user event Explanation
IBM Z OMEGAMON for CICS could not find the entry
KOCEPOPT macro in KOCGLB.
for the user event monitoring point CANWLMSC in the
CICS monitoring control table. (MVS 5.1/CICS 4.1 and
System action higher only)
Tivoli OMEGAMON II does not write DB2 data to CMF. This message only applies if you are using the Tivoli
Enterprise Monitoring Server for CICS and want to
User response collect this data. Otherwise, you can ignore this
message.
Make sure you have an event monitoring point defined
in the MCT and that the entry name and field name for
System action
If this problem persists, send an assembled listing IBM Z OMEGAMON for CICS does not write WLM data
of your KOCGLB and a CICS system dump to IBM to CMF.
Software Support.
OC1134 WORK AREA FOR TRUE IS User response
MISSING
If you want to collect this data, make sure you have
an event monitoring point defined in the MCT and
Explanation that the entry name and field name for this point are
CANWLMSC.
Tivoli OMEGAMON II could not locate the work area
for its task related user exit program. OC1137 DUPLICATE DATA FOR CANDLE
BASIC SEGMENT WILL BE
System action COLLECTED
Tivoli OMEGAMON II does not write umbrella data,

DL/I data, or DB2 data to CMF.
Explanation
Both the OMEGBSC EMP and one or more individual
fields that make up the segment have been used.

System action OC1143 OCEXEN NOT AUTHORIZED FOR
cccccccccccccccc
IBM Z OMEGAMON for CICS writes duplicate data to
CMF.
Explanation
User response Tivoli OMEGAMON II could not enable a program it
Choose either the OMEGBSC or selective method of
collecting the data, not both.
System action
OC1140 OCEXEN INSUFFICIENT WORK
AREA FOR EXIT ENABLEMENT No data is collected for the response time collector or
ONDV collector
Explanation
User response
Tivoli OMEGAMON II could not enable CICS global
exits due to an insufficient work area. Make sure the transaction OMEG is defined with
no resource security (RESSEC(NO)) or command
security (CMDSEC=NO). Also make sure the group
System action DFHEXEC is installed. You should also check the CICS
No data is collected for the response time collector or system log for messages from the External Security
ONDV collector. Manager, which will give additional information. If
this condition persists change the resource security
number for the program KOCOME00 to PUBLIC
User response (RESSECNUM(PUBLIC)).
OC1144 OCEXEN PROCESS
OC1141 OCEXEN TRUE COULD NOT BE cccccccccccccccc ERROR nnnn
LOCATED OR WAS NOT LOADED
Explanation
Explanation Tivoli OMEGAMON II encountered an error issuing an
Tivoli OMEGAMON II could not load a program it EXEC CICS command.
System action
System action No data is collected for the response time collector or
No data is collected for the response time collector or ONDV collector.
ONDV collector.
User response
User response Send the message to IBM Software Support.
OC1145 OCEXEN PGMIDERR DURING
OC1142 OCEXEN GLUE COULD NOT BE ccccccccccc
Explanation
Explanation Tivoli OMEGAMON II encountered an error issuing an
Tivoli OMEGAMON II could not load a program it EXEC CICS command.
System action
System action No data is collected for the response time collector or
No data is collected for the response time collector or ONDV collector.
ONDV collector.
User response

OC1146 OCEXEN QRYC COULD NOT BE Explanation
Tivoli OMEGAMON II enabled CICS exits for data
collection.
Explanation
Tivoli OMEGAMON II could not load a program it System action
None.
System action
User response
No data is collected for the response time collector or
ONDV collector. None.
OC1150 OCEXEN EXIT RESTART
User response COMPLETED

Explanation
OC1147 OCEXEN CICS MONITORING IS
BEING TURNED ON Tivoli OMEGAMON II re-enabled CICS exits for data
collection.
Explanation
System action
Tivoli OMEGAMON II has detected that CICS
monitoring is off. Tivoli OMEGAMON II is turning CICS None.
monitoring on since it is required for the response time
collector and ONDV collector (for CICS 3.x). User response
None.
System action
OC1151 INSUFFICIENT STORAGE FOR THE
CICS monitoring is activated. SMF BUFFER

None. Tivoli OMEGAMON II was not able to acquire a buffer
OC1148 OCEXEN PERFORMANCE CLASS IS of approximately 32K from CICS OSCOR less than
BEING TURNED ON 16M.

Tivoli OMEGAMON II has detected that the Tivoli OMEGAMON II does not log any transaction
performance class of CICS monitoring is off. Tivoli related monitoring data to SMF.
OMEGAMON II is turning it on since it is required for
the response time collector and ONDV collector. User response
Increase OSCOR in your CICS region so that at least
System action 32K of contiguous storage is available.
CICS monitoring for the performance class is OC1152 UNABLE TO LOCATE OCA
activated. RESOURCE MANAGER

None. Tivoli OMEGAMON II could not find the umbrella
OC1149 OCEXEN EXIT INITIALIZATION services exit module.
COMPLETED

System action OC1156 INVALID RLIM DATA FOUND, RLIM
NOT ACTIVATED
Tivoli OMEGAMON II for CICS initialization continues
in CICS. Transactions that use umbrella services will
fail with a return code of 8. Explanation
During OMEGAMON initialization under CICS, it was
User response detected that there was no valid resource limiting data
present.
OC1153 OCA RESOURCE MANAGER ERROR System action
The RLIM and RLMU commands will not function.
Explanation
Tivoli OMEGAMON II for CICS could not initialize the User response
umbrella services exit module.
The most likely cause of this error is that the global
data area module is out of step with the runtime code.
System action Reassemble the global data area module and retry. If
Tivoli OMEGAMON II for CICS initialization continues the problem persists, contact IBM Software Support.
in CICS. Transactions that use umbrella services will OC1160 OCSETI INSUFFICIENT WORK
fail with a return code of 8. AREA FOR OCEXEC PROCESSING

Contact IBM Software Support. Tivoli OMEGAMON II could not process its internal
OC1154 EXEN GLUE RESTART COMPLETED monitoring of CICS OCEXEC level calls due to an
insufficient work area.
Explanation
System action
This is an informational message indicating that the
Tivoli OMEGAMON II global user exits have been re- Support for database statistics and MAXR is disabled.
enabled.
User response
None. OC1161 OCSETI OCEXEC COULD NOT BE
User response
None. Explanation
OC1155 EXEN GLUE SHUTDOWN Tivoli OMEGAMON II could not load a program it
COMPLETED required for monitoring CICS OCEXEC level calls.

This is an informational message indicating that the Support for database statistics and MAXR is disabled.
Tivoli OMEGAMON II global user exits have been
disabled. User response
System action
OC1162 OCSETI VALIDATION FAILED FOR
None. OCEXEC ENVIRONMENT
User response
None.

Tivoli OMEGAMON II detected that internal addresses None.
in CICS were changed, which prevents Tivoli
OC1166 OCSETI OCEXEC INTERFACE HAS
OMEGAMON II from monitoring CICS OCEXEC level
BEEN RESTARTED
calls.

Support for database statistics and MAXR is disabled. Tivoli OMEGAMON II restarted its support for
monitoring CICS OCEXEC level calls.
User response
System action
None.
OC1163 OCSETI OCEXEC MODULE IS NOT
IN LOW PRIVATE User response
None.
Explanation
Tivoli OMEGAMON II detected an error in loading a OC1167 EXEC VALIDATION NOTED
program required for monitoring CICS OCEXEC level ALTERED CICS ENTRY
calls.
Explanation
System action Tivoli OMEGAMON II initialization processing validates
Support for database statistics and MAXR is disabled. certain pointers in CICS. The validation expects
certain conditions but allows for some variations. This
message indicates such a variation was found at the
User response CICS Command Level entry points. This condition may
Contact IBM Software Support. occur in conjunction with some other vendor product.
OC1164 OCSETI OCEXEC INTERFACE IS

System action
NOW INSTALLED IN CICS
Explanation
User response
Tivoli OMEGAMON II installed its support for
monitoring CICS OCEXEC level calls. None.
OC1168 OCSETI EXEC MODULE IS NOT IN
System action LOW PRIVATE
None.
Explanation
User response An error has been encountered in the loading of a
None. module required for monitoring EXEC level calls, it
must reside in low private storage.
OC1165 OCSETI OCEXEC INTERFACE HAS
BEEN DISABLED
System action
Explanation Support for database statistics and MAXR is disabled.
Tivoli OMEGAMON II removed its support for

User response
monitoring CICS OCEXEC level
System action OC1169 EXEC VALIDATION NOTED
None. UPDATED CICS POINTERS

Explanation calls. The user has applied a special zap to force the
installation at this point. This condition happens only
Tivoli OMEGAMON II initialization processing validates in conjunction with another product installed in CICS.
certain pointers in CICS. The validation expects
certain conditions but allows for some variations. This
message indicates such a variation had been found System action
at the CICS Command Level CSA anchor point. This Processing continues.
condition may occur in conjunction with some other
vendor product.
User response
System action None.
Processing continues. OC1173 OCSETI KOCDIN COULD NOT BE

User response
Explanation
None.
An internal error has occurred.
OC1170 STARTING IBM Z OMEGAMON for
CICS OCEXEC PROCESSING
System action
Explanation IBM Z OMEGAMON for CICS will not initialize.
Identifies the part of the Tivoli OMEGAMON II

initialization in process. User response
System action OC1174 OCSETI KOCDBP COULD NOT BE
Processing continues. LOCATED OR WAS NOT LOADED

None. An internal error has occurred.
OC1171 OCSETI FEATURE NOT AVAILABLE

UNTIL CICS RESTART - System action
ffffffffffffffffffff IBM Z OMEGAMON for CICS will not initialize.

IBM Z OMEGAMON for CICS feature Contact IBM Software Support.
ffffffffffffffffffff was added in maintenance,
but cannot be activated until this CICS region restarts. OC1175 OCSETI KOCDBT COULD NOT BE
System action
Explanation
IBM Z OMEGAMON for CICS continues without the
feature. An internal error has occurred.

This feature will be available when this CICS region IBM Z OMEGAMON for CICS will not initialize.
restarts.
OC1172 USER MODIFIED PCN ENTRY User response
Explanation OC1176 OCSETI xxxxxx COULD NOT BE
The Tivoli OMEGAMON II EXEC interface was unable LOCATED OR WAS NOT LOADED
to determine the proper entry point for CICS PCN

An internal error has occurred. File level monitoring was specified for a product in
KOCGLB that is not supported by Tivoli OMEGAMON II.
System action
System action
IBM Z OMEGAMON for CICS will not initialize.
Tivoli OMEGAMON II continues processing other
User response products.

User response
OC1177 OCSETI KOCPGM INTERFACE IS The invalid product name is specified in the
NOW INSTALLED IN CICS KOCDBCOL macro in KOCGLB. Correct the macro,
reassemble KOCGLB and restart CICS in order to
Explanation prevent occurrence of this message.
IBM Z OMEGAMON for CICS installed its support for OC1182 OCDBIN INVALID GLOBAL
Program Tracking. EXTRACT AREA, FILE LEVEL
MONITORING DISABLED
System action:
None.
Explanation
User response Tivoli OMEGAMON II detected an internal error in
attempting to activate file level monitoring.
None required.
OC1178 OCSETI KOCPGM INTERFACE HAS System action
BEEN DISABLED
Tivoli OMEGAMON II does not monitor file usage.
Explanation
User response
IBM Z OMEGAMON for CICS removed its support for
Program Tracking. Contact IBM Software Support.
System action: OC1183 IBM Z OMEGAMON for CICS
None. COLLECTION IS NOT ACTIVE

None required. The data collection component of Tivoli OMEGAMON II
that runs in CICS is not active.
OC1179 OCSETI KOCPGM INTERFACE HAS
BEEN RESTARTED
System action
Explanation A display of file level collectors is not produced.
IBM Z OMEGAMON for CICS restarted its support for
Program Tracking. User response
System action: Make sure the data component of Tivoli OMEGAMON II
None. 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
User response Customization Guide for more information. If this
None required. problem persists, contact IBM Software Support.
OC1180 OCDBIN cccccccc IS AN OC1184 NO STORAGE AVAILABLE, FILE
UNSUPPORTED PRODUCT LEVEL MONITORING DISABLED

IBM Z OMEGAMON for CICS was unable to acquire a Tivoli OMEGAMON II attempted to acquire
64K buffer in the extended private region of CICS for authorization to write a system record to SMF.
collecting file clock and counter statistics.
System action
System action
Tivoli OMEGAMON II does not write system
IBM Z OMEGAMON for CICS does not collect file clock initialization or system termination records to SMF.
and counter statistics for CICS tasks.
User response
User response
Make sure 64K of storage is available in the extended
private region of CICS. OC1193 OCSYSI INVALID GLOBAL
EXTRACT AREA. SYSTEM RECORD
OC1190 UNABLE TO OBTAIN WORK NOT WRITTEN.
AREA FOR SYSTEM RECORDS.
LENGTH=nnnnnn Explanation
Tivoli OMEGAMON II has detected an internal error
Explanation
when attempting to write a system record to SMF.
Tivoli OMEGAMON II was not able to acquire a work
area from OSCOR to send system initialization or System action
system termination records to SMF. The number of
bytes requested is given in the message. Tivoli OMEGAMON II does not write system
initialization or system termination records to SMF.
System action
User response
initialization or system termination records to SMF. Contact IBM Software Support.
OC1200 ddname DD MISSING
User response
Increase the amount of OSCOR in your region and Explanation
No ddname DD statement was found during the
OC1191 INVALID TCB ADDRESS, SYSTEM running of the KOCSMFDI job.
RECORDS NOT WRITTEN TO SMF
System action
Explanation
Processing stops.
Tivoli OMEGAMON II attempted to determine the TCB
under which it was running in order to write to SMF. User response
Correct the ddname DD statement and run the
System action
KOCSMFDI job again.
OC1201 MCT PARAMETER IS INVALID AND
initialization or system termination records to SMF.
IS IGNORED
User response
Explanation
An input card contained an MCT parameter, which
OC1192 AUTHORIZATION FAILED, NO is invalid for pre-ESA CICS, during execution of job
SYSTEM RECORDS WRITTEN KOCSMFDI.
System action
Processing continues and the next input card is read.

None. An input card contained an invalid value in the DATE
field during execution of the KOCSMFDI job.
OC1201 PRECEDING INPUT IS INVALID,
PROCESSING STOPPED
System action
Explanation Processing stops.
An input card was blank or contained no equal sign
during execution of the KOCSMFDI job. User response
Correct the input card using a valid date (YYDDD.) and
System action rerun the KOCSMFDI job.
Processing stops. OC1208 THE SERVICE TASK IS ALREADY
RUNNING, CANNOT START A NEW
User response ONE
Correct the input card and run the KOCSMFDI job

Explanation
again.
OMEG SRVINIT was issued but the service task is
OC1202 PRECEDING INPUT HAS
already running.
AN INVALID FIELD NAME,
PROCESSING STOPPED
System action
Explanation None.
An input card contained an invalid field name during
execution of the KOCSMFDI job. User response
If you wish to re initialize the service task, issue OMEG
System action SRVSHUT first, then OMEG SRVINIT.
Processing stops. OC1209 THE SERVICE TASK WAS
SUCCESFULLY SHUTDOWN
User response
Explanation
Correct the input card and rerun the KOCSMFDI job.
Valid field names are: APPLID, SYSID, DATE, TIME, and The service task shutdown process finished.
SMFID.
OC1203 INVALID VALUE FOR TIME, System action
PROCESSING STOPPED None.

An input card contained an invalid value in the TIME None.
field during execution of the KOCSMFDI job.
OC1210 UNABLE TO SHUTDOWN THE
SERVICE TASK
System action
Processing stops. Explanation
Either at PLTSD or as a result of the OMEG SRVSHUT
User response
transaction, exceptional conditions were encountered.
Correct the input card using a valid time (HHMMSS) These conditions are described by messages KOC1217
and rerun the KOCSMFDI job. and KOC1218.
OC1204 INVALID VALUE FOR DATE,
PROCESSING STOPPED System action
None.

Refer to messages KOC1217 and KOC1218. Processing stops.
OC1211 SERVICE TASK INITIALIZATION
GETMAIN FOR nnnnx FAILED User response
Explanation
OC1215 SERVICE TASK START aaaaaaaa
The GETMAIN issued for nnnnb (bytes) or nnnnk FAILURE
(kilobytes) failed.
Explanation
System action
CICS returned aaaaaaaa when a START command for
Service task initialization is not performed. the service task was issued.

Increase the size of the CICS address space by nnnnb Processing stops.
or nnnnk.
OC1212 TEMPORARY STORAGE LIMIT User response
(nnn) EXCEEDS AVAILABLE If aaaaaaaa is NOTAUTH, make sure the transaction
STORAGE OMEG is defined with no resource security
(RESSEC(NO)) or command security (CMDSEC=NO).
Explanation Also make sure the group DFHEXEC is installed. If
this condition persists, change the resource security
This is an internal error. number for the KOCOME00 program to PUBLIC
(RESSECNUM(PUBLIC)). For other values in aaaaaaaa
System action contact IBM Software Support.
Processing stops. OC1216 TSBROWSE ENTRY IN SERVICE
LIMITS TABLE COULD NOT BE
User response LOCATED

Explanation
OC1213 SERVICE TASK INITIALIZATION
COMPLETED
System action
Explanation
Processing stops.
Initialization of the service task is complete.
User response
System action
None.
OC1217 PURGE OF SECONDARY SERVICE
User response TASK FAILED WITH aaaaaaaa
None.
Explanation
OC1214 SECONDARY TASK LIMIT (nnn)
The SET TASK command for one of the secondary
EXCEEDS AVAILABLE STORAGE
tasks failed. The aaaaaaaa value is the exceptional
condition raised for the EXEC CICS SET TASK
Explanation command. This message is only applicable to CICS/
ESA.


None. Refer to the CICS/ESA System Programming None.
Reference, command SET TASK.
OC1225 SECONDARY SERVICE TASK NOT
OC1218 PURGE OF SERVICE TASK FAILED STARTED BECAUSE OF MAXTASKS
WITH aaaaaaaa LIMIT
The SET TASK command for the service task failed. Starting a new secondary task would put CICS in
The aaaaaaaa value is the exception condition raised a MAXTASKS condition; therefore, the task is not
for the EXEC CICS SET TASK command. This message started.
is only applicable to CICS/ESA.
System action
System action
User response
User response
Revise the MXT SIT parameter.
None. Refer to the CICS/ESA System Programming
Reference, command SET TASK. OC1226 SECONDARY SERVICE TASK
NOT STARTED BECAUSE OF
OC1223 SECONDARY SERVICE TASK AMAXTASKS LIMIT
START aaaaaaaa FAILURE
Explanation
Explanation
Starting a new secondary task would put CICS in
CICS returned the aaaaaaaa value when the service an AMAXTASKS condition; therefore, the task is not
task attempted to start a secondary task. started.


If aaaaaaaa is NOTAUTH, make sure the transaction Revise the AMXT SIT parameter.
OMEG is defined with no resource security
(RESSEC(NO)) or command security (CMDSEC=NO). OC1227 UNABLE TO SETUP PARAMETERS
Also, make sure the group DFHEXEC is installed. FOR THE SECONDARY TASK
If this condition persists, change the resource
security number for the KOCOME00 program to Explanation
PUBLIC (RESSECNUM(PUBLIC)). For any other value of
aaaaaaaa, contact IBM Software Support.
OC1224 FIRST SECONDARY SERVICE TASK System action
FAILED TO INITIALIZE
Processing stops.
Explanation
User response
The service task started a secondary task which failed
to respond. Contact IBM Software Support.

OC1228 FIRST SECONDARY SERVICE TASK Explanation
ABENDED
The service task has initialized successfully and is
waiting for work. This is an informational message
Explanation only.
The first secondary task started by the service task
abended. System action
None.
System action
None.
User response
OC1240 SECONDARY TASK GETMAIN FOR
None. nnnnx FAILED
OC1229 RM CALL WAS UNSUCCESSFUL -
RETURN CODE = cc Explanation
One of the secondary tasks failed when issuing a
Explanation GETMAIN for nnnnx, where nnnn is a number, b is for
The service task or one of the secondary tasks failed bytes or k is for kilobytes.
with return code cc when trying to establish its
umbrella transaction or program ID. System action
The secondary task does not initialize.
System action
Further requests issued by the AIDK command will
User response cause a new secondary task to initialize. If the
Please refer to the IBM Z OMEGAMON for CICS situation persists, increase the CICS region size.
Configuration and Customization Guide for an OC1241 ABEND aaaa DETECTED -
explanation of the return code and contact IBM SECONDARY SERVICE TASK IS
Software Support. TERMINATING
OC1230 ABEND aaaa DETECTED - SERVICE
TASK IS TERMINATING Explanation
Abend aaaa was detected by the secondary service
Explanation task. It is terminating.
The service task abended with abend code aaaa and is
terminating. System action
The main service task remains available.
System action
The service task is no longer available. User response
None.
User response
OC1242 OCSR2 SECONDARY SERVICE
Issue the transaction OMEG SRVSHUT to terminate TASK WAITING FOR WORK
any secondary service tasks, then issue OMEG
SRVINIT to make the service task available again.
Explanation
OC1231 OCSRV SERVICE TASK WAITING
FOR WORK The secondary service task has initialized successfully
and is waiting for work. This is an informational
message only.

System action OC1246 OCSR2 CICS MONITORING
TURNED ON
None.
Explanation
User response
This is an informational message indicating that CICS
None. global and performance monitoring have been turned
OC1243 OCSR2 SMF DATA COLLECTION on.
QUIESCED
System action
Explanation None.
This is an informational message. For CICS/MVS users
it indicates that Tivoli OMEGAMON II will no longer User response
write SMF records. For CICS/ESA users it indicates that
CICS will no longer write SMF records. None.
OC1247 RECYCLE TASK START aaaa
System action FAILURE
None.
Explanation
User response CICS returned a abend code of aaaa when
OMEGAMON II for CICS attempted to start a
None. transaction to recycle OMEGAMON in the CICS region.
OC1244 OCSR2 SMF DATA COLLECTION
INITIATED System action
The recycle of OMEGAMON in the CICS region did not
Explanation occur.
This is an informational message. For CICS/MVS users
it indicates that Tivoli OMEGAMON II will start writing User response
SMF records. For CICS/ESA users it indicates that CICS
will start writing SMF records. Investigate the possible cause of the abend codeaaaa
and contact IBM Software Support.
System action OC1401 SHOULD IBM Z OMEGAMON for
CICS PURGE CONVERSATIONS?
None. REPLY YES OR NO.

None. This is the text of a Write To Operator with Reply
OC1245 OCSR2 CICS MONITORING (WTOR). It is issued when SHUTOPT=OPER has been
TURNED OFF specified and Tivoli OMEGAMON II has found a task to
purge. This process happens only at CICS termination.
Explanation
System action
This is an informational message indicating that CICS
performance monitoring has been turned off. The SHUTOPT process of OCSHUT waits for a reply.

None. Only the first character of the reply is checked. If you
specify NO, SHUTOPT processing stops immediately.
The rest of Tivoli OMEGAMON II PLTSD processing
User response continues. If you specify YES, the processing operates
None. as though you had specified SHUTOPT=PURGE; all
tasks waiting for terminal I/O are purged.

OC1402 IBM Z OMEGAMON for CICS HAS OC1405 START OF SHUTOPT=PURGE
PURGED nnnn TASKS PROCESSING
After completing the SHUTOPT=PURGE cycle (or after CICS termination has been detected. Your GLOBAL
a user reply of YES to message OC1401), SHUTOPT assembly has requested Tivoli OMEGAMON II to purge
processing tells you how many tasks have been all tasks waiting in terminal control program.
purged. For CICS 1.7/2.1, this is the number of tasks
canceled, whether or not the cancel was successful. System action
For CICS 3.1.1 and higher, this is the number of tasks
canceled and CICS return codes indicated success. Task purging immediately follows. Message OC1402
follows the purge process.
System action
User response
SHUTOPT processing ends. Tivoli OMEGAMON II
processing continues. None.
OC1406 START OF SHUTOPT=OPER
User response PROCESSING
None.
Explanation
OC1403 PROCESS cccccccccccccccc ERROR
nnnn CICS termination has been detected. Your GLOBAL
assembly has requested Tivoli OMEGAMON II to check
for tasks waiting in terminal control. If any are found,
Explanation
confirm permission to cancel the tasks (message
SHUTOPT processing has reached an error state. This OC1401).
message is issued from a subroutine, and ccc identifies
the process that invoked the error routine. nnnn is the System action
value from an EXEC CICS request (EIBRESP).
Tivoli OMEGAMON II waits for response to message
OC1401.
System action
SHUTOPT processing ends. Tivoli OMEGAMON II PLT User response
shutdown processing does not continue.
None.
User response OC2001 INVALID KEYWORD SPECIFIED,
RE-ENTER
OC1404 OCSHUT INSUFFICIENT WORK Explanation
AREA FOR TASK PURGE
The ENQ command was entered with an invalid
keyword.
Explanation
The Tivoli OMEGAMON II PLT shutdown program could System action
not purge tasks due to an insufficient work area.
The command fails.
System action
User response
The Tivoli OMEGAMON II PLT shutdown program stops
without purging all tasks waiting for terminal input. Correct the keyword, and enter the ENQ command.
OC2002 KEYWORD SPECIFIED WITHOUT
User response ARGUMENT

The ENQ RESOURCE command was entered without The ENQ command has found no tasks waiting on
a resource argument or the ENQ QEA command was enqueues (for a list of all enqueues in the system,
entered without a QEA address argument. enter ENQ RESOURCE=*).

The command fails. The ENQ command stops processing.

Use the zoom key to select an enqueue resource None.
from the ENQ display, or specify a resource or a QEA
address and enter the ENQ command. OC2020I xxxxx yyy GLUE CODE HAS BEEN
ENABLED
OC2003 SPECIFIED ARGUMENT IS NOT
HEXADECIMAL Explanation
OMEGAMON II for CICS has enabled or disabled
Explanation
it GLUE code for the feature yyy, where yyy can
The ENQ QEA command argument was not be ATF, MQ or DLI. xxxxx will be set to EXEN or
hexadecimal. OCSR2, depending on the module which has issued
the request.
System action
System action
The command fails.
The messages are informational and may be used to
User response verify which exits are affected by the command(s) that
you have issued.
Use the zoom key to select an enqueue resource from
The GLUE code will run at the following exit points:
the ENQ display, or specify a valid QEA address and
enter the ENQ command. • ATF uses XRMIOUT and XPCABND
OC2004 SPECIFIED ARGUMENT IS TOO • MQ uses XRMIOUT
LONG • DLI uses XDLIPRE and XDLIPOST
Additional Documentation: You can now control
Explanation which GLUEs are enabled (or disabled) in a monitored
The ENQ RESOURCE command argument was more CICS region by choosing the appropriate values in
than 16 characters, or the ENQ QEA command QEA your global source, or issuing the equivalent online
address was more than 8 hexadecimal digits. commands. Be aware that the exit code running at
XEIOUT and XMNOUT is essential to the operation
of OMEGAMON II for CICS so these exits will not be
System action disabled unless an OMEG SHUT / REMOVE command
The command fails. is issued.
In the DATABASE_COLLECTION section coding
User response
<<MQ>>
Use the zoom key to select an enqueue resource from AUTO_START=NO
the ENQ display, or specify a valid resource argument
or QEA address and enter the ENQ command. will not enable the GLUE code at XDLIPRE
OC2005 NO TASKS WAITING ON <<DLI>>

ENQUEUES 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 ENABLE EXIT REQUEST EIBRCODE 800800
ENABLE EXIT REQUEST EIBRCODE 800400
to ensure that the DLI exits are not enabled. DISABLE EXIT REQUEST EIBRCODE 808000
<<TRACE>> DISABLE EXIT REQUEST EIBRCODE 804000
AUTO_START=NO DISABLE EXIT REQUEST EIBRCODE 802000
DISABLE EXIT REQUEST EIBRCODE 801000
If you do not use the Application Trace Facility, ATF, DISABLE EXIT REQUEST EIBRCODE 800800
you will not enable code at XPCABND or XRMIOUT
(although XRMIOUT code will be active if you enable The EIBRCODES are documented in the CICS System
the MQ clocks and counters.) Programming Reference under ENABLE PROGRAM
and DISABLE PROGRAM. If you receive any of these
Excluding the entries is equivalent to coding messages you should determine the cause of the error
AUTO_START=NO in the Global Data Area. using the CICS documentation and correct the error
You can use the OMEGAMON for CICS (3270) before reissuing the command.
command COLL (fastpath= O.P) to turn the collection
on or off, and the exits will be turned on or off User response
accordingly.
None.
The OMEGAMON II File/Database collection and
Application Trace Facility panels can also be used to OC2021I OCSR2 yyy GLUE CODE HAS BEEN
control the data collection. The exits will be enabled or DISABLED
disabled as appropriate.
The OMEGAMON for CICS (3270) command EXIT Explanation
(fastpath=CI) will display the exits that are currently OMEGAMON II for CICS has enabled or disabled
active. it GLUE code for the feature yyy, where yyy can
The OMEGAMON II Global User Exits panel be ATF, MQ or DLI. xxxxx will be set to EXEN or
(fastpath=CE) will display the exits that are enabled OCSR2, depending on the module which has issued
in CICS. the request.
In summary you can now expect to see GLUE code at

the following exit points activated.
System action
The messages are informational and may be used to
Exit Point Name DLI= MQ= ATF=
verify which exits are affected by the command(s) that
YES YES YES
you have issued.
XMNOUT Y Y Y
XEIOUT Y Y Y The GLUE code will run at the following exit points:
As mentioned earlier, XMNOUT and XEIOUT will be • ATF uses XRMIOUT and XPCABND
activated when an OMEG INIT transaction is run, or • MQ uses XRMIOUT
the KOCOME00 program executes in the PLT
• DLI uses XDLIPRE and XDLIPOST
XRMIOUT N Y Y Additional Documentation: You can now control
XPCABND N N N which GLUEs are enabled (or disabled) in a monitored
XDLIPRE Y N N CICS region by choosing the appropriate values in
XDLIPOST Y N N your global source, or issuing the equivalent online
In a CICS region with DLI, MQ and ATF active you can commands. Be aware that the exit code running at
expect to see all of the exit points active whereas a XEIOUT and XMNOUT is essential to the operation
region with only DB2 (no DLI, no MQ, and no ATF) of OMEGAMON II for CICS so these exits will not be
would only have XMNOUT and XEIOUT active. disabled unless an OMEG SHUT / REMOVE command
is issued.
The OMEGAMON for CICS (3270) COLL command can
display one of the following messages, if a non zero In the DATABASE_COLLECTION section coding:
return code is received during an attempt to enable or <<MQ>>
disable an exit: AUTO_START=NO
ENABLE EXIT REQUEST EIBRCODE 808000 will not enable the GLUE code at XDLIPRE
ENABLE EXIT REQUEST EIBRCODE 802000 <<DLI>>
ENABLE EXIT REQUEST EIBRCODE 801000 AUTO_START=NO

will not enable the GLUE code at XDLIPRE or ENABLE EXIT REQUEST EIBRCODE 800800
XDLIPOST. In addition you must also code the ENABLE EXIT REQUEST EIBRCODE 800400
parameter, DISABLE EXIT REQUEST EIBRCODE 808000
DLI_CLOCKS_AND_COUNTERS=NO DISABLE EXIT REQUEST EIBRCODE 802000
to ensure that the DLI exits are not enabled. DISABLE EXIT REQUEST EIBRCODE 801000
<<TRACE>>
AUTO_START=NO The EIBRCODES are documented in the CICS System
Programming Reference under ENABLE PROGRAM
If you do not use the Application Trace Facility, ATF, and DISABLE PROGRAM. If you receive any of these
you will not enable code at XPCABND or XRMIOUT messages you should determine the cause of the error
(although XRMIOUT code will be active if you enable using the CICS documentation and correct the error
the MQ clocks and counters.) before reissuing the command.
Excluding the entries is equivalent to coding
AUTO_START=NO in the Global Data Area. User response
You can use the OMEGAMON for CICS (3270) None.
command COLL (fastpath= O.P) to turn the collection
OC2022I xxxxx Unable to activate ATF due
on or off, and the exits will be turned on or off
to KOCCI level
accordingly.
The OMEGAMON II File/Database collection and
Explanation
Application Trace Facility panels can also be used to
control the data collection. The exits will be enabled or OMEGAMON for CICS was unable to activate
disabled as appropriate. Application trace in this CICS region due to the
OMEGAMON KOCCI address space not having the
The OMEGAMON II Global User Exits panel
required maintenance to process the produced trace.
(fastpath=CE) will display the exits that are enabled
xxxxx will be set to EXEN or OCSR2, depending on the
in CICS.
module which has issued the request.
In summary you can now expect to see GLUE code at
the following exit points activated. System action
Exit Point Name DLI= MQ= ATF= Processing continues. Application trace is not enabled.
YES YES YES
XMNOUT Y Y Y
XEIOUT Y Y Y User response
Ensure the KOCCI address space has the same level of
As mentioned earlier, XMNOUT and XEIOUT will be
maintenance as the CICS region for OMEGAMON CICS.
activated when an OMEG INIT transaction is run, or
the KOCOME00 program executes in the PLT OC2051 INVALID KEYWORD SPECIFIED,
RE-ENTER
XRMIOUT N Y Y
XPCABND N N N
XDLIPRE Y N N Explanation
XDLIPOST Y N N
The STOR command was entered with an invalid
In a CICS region with DLI, MQ and ATF active you can keyword.
expect to see all of the exit points active whereas a
region with only DB2 (no DLI, no MQ, and no ATF) System action
would only have XMNOUT and XEIOUT active.
The command fails.
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 User response
disable an exit: Correct the keyword, and enter the STOR command.
ENABLE EXIT REQUEST EIBRCODE 808000 OC2053 INVALID GROUP SPECIFIED, RE-
ENABLE EXIT REQUEST EIBRCODE 804000 ENTER

The STOR GROUP command was entered with an The command fails.
invalid group argument.
User response
System action
Use the zoom key to select the required page from
The command fails. the STOR or PAMEDSA display, or check the number of
pages in the DSA/EDSA and enter the STOR PAMDSA
User response or PAMEDSA command.
Use the zoom key to select the required group from OC2071 INVALID STOR REQUEST FOR THIS
the STOR GROUP=ALL display. Correct the group CICS RELEASE
argument, and enter the STOR GROUP command.
Explanation
OC2054 SPECIFIED ARGUMENT IS TOO
LONG A STOR keyword was entered that was unrecognized
by the command for the current CICS release.
Explanation
System action
The STOR PAMDSA or PAMEDSA command page
number was greater than 8 digits. The STOR command stops processing.

The command fails. Verify the input keywords for the current CICS release.
OC2072 PROGRAM COMPRESSION DATA
User response NOT CURRENT
Use the zoom key to select the required page from the
STOR or PAMEDSA display, or specify a page number Explanation
with 8 or fewer digits and enter the STOR PAMDSA or
PAMEDSA command. The STOR command has detected that the program
compression data has not been updated in the last
OC2055 SPECIFIED ARGUMENT IS NOT AN minute. This probably means that CICS is not being
INTEGER dispatched.

The STOR PAMDSA or PAMEDSA command page The STOR command stops processing.
number was not a decimal integer.
User response
System action
Investigate why CICS is not being dispatched. If CICS
The command fails. is being dispatched, contact IBM Software Support.
OC2073 PROGRAM COMPRESSION DATA
User response NOT AVAILABLE, ISSUE OMEG
Use the zoom key to select the required page from the INIT
STOR or PAMEDSA display, or specify a decimal page
number and enter the STOR PAMDSA or PAMEDSA Explanation
command.
Display of program compressions using the STOR
OC2060 SPECIFIED PAGE NOT IN DSA/ command with the COMPRESSIONS keyword requires
EDSA that Tivoli OMEGAMON II be initialized in the CICS
region being monitored.
Explanation
System action
The STOR PAMDSA or PAMEDSA command page
number was not in the current DSA/EDSA. The command fails.

Issue an OMEG INIT in the required CICS region. The call is rejected.
OC2074 PROGRAM COMPRESSION ACCESS
ERROR User response
Review existing RLIM definitions and free up space
Explanation through the RLMU DEL command.
Display of program compressions using the STOR OC2203 INITIALIZATION IN PROGRESS
command with the COMPRESSIONS keyword has
failed to locate a required Tivoli OMEGAMON II control Explanation
block (SVCOM) in the CICS region.
An RLMU ADD|DEL command has been issued while
another user is initializing the resource limiting
System action
environment.
The command fails.
System action
User response
The call is rejected.
OC2200 INVALID CALL TYPE User response
Retry the command. If this incurs the same response,
An invalid call has been generated by the RLMU OC2204 RLIMDATA IS IN AN
command processor. INCONSISTENT STATE

The call is rejected. The RLMU command processor has detected a
problem with the data that it is managing.
User response
System action
OC2201 ENTRY NOT FOUND
User response
Explanation
An RLMU DEL command has been issued and the item
to be processed cannot be found. OC2205 EXPANSION AREA GETMAIN
FAILURE
System action
Explanation
The first RLMU command issued caused a GETMAIN
User response attempt that has incurred a bad response.
None.
System action
OC2202 NO SPACE FOR REQUESTED The RLMU command will be unavailable during this
ADDITION OCCI session.

An RLMU ADD command has been issued and there is Review your OCCI region size.
insufficient room to perform the addition.
OC2206 SYSTEM BUSY, PLEASE RETRY

An RLMU call has coincided with a call from another There has been a failure in the serialization of access
OCCI user. to OMEGAMON's resource limiting data.

The call is rejected. The RLMU command will no longer function.

Retry the command. If this incurs the same response, Contact IBM Software Support.
OC2210 RESOURCE LIMITS REFRESHED
OC2207 RESOURCE LIMITING IS
UNAVAILABLE Explanation
An RLMU command has successfully executed.
Explanation
During OMEGAMON initialization under CICS, it was System action
detected that there was no valid resource limiting data
present. None.

The RLIM and RLMU commands will not function. None.
OC2220 OPERATION ERROR - USE ADD,
User response DEL OR REFRESH
The most likely cause of this error is that the global
data area module is out of step with the runtime code. Explanation
Reassemble the global data area module and retry. If
An invalid RLMU call has been generated.
OC2208 INVALID RLIMDATA FOUND IN System action
GLOBAL DATA AREA MODULE
The command will be rejected.
Explanation
User response
While attempting to either display or update resource
limits, it was detected that the RLIMDATA present in Refer to the documentation for details for the syntax of
the global data area module was invalid. the RLMU command.
OC2221 FUNCTION ERROR - USE INC OR
System action EXC
The GLOB RLIM command and the RLMU command
will not function. Explanation
User response
The most likely cause of this error is that the global System action
data area module is out of step with the runtime code.
Reassemble the global data area module and retry. If
User response
OC2209 LOCKING ERROR
Refer to the documentation for details for the syntax of
the RLMU command.

OC2222 RESOURCE ERROR - SEE KOCRLIM User response
MACRO FOR VALID NAMES
Refer to the documentation for details for the syntax of
the RLMU command.
Explanation
OC2226 INTERVAL ERROR - USE
An invalid RLMU call has been generated. TIME=nnnnnnnn IN SECONDS

The command will be rejected. The RLMU INT,TIME= command was entered without a
valid interval.
User response
Refer to the documentation for details for the syntax of System action
the RLMU command. The command will be rejected.
OC2223 TRANSACTION ERROR - USE
Tarantula User response
Follow the TIME=keyword with the number of seconds
Explanation (1 through 604800).
An invalid RLMU call has been generated. OC2227 INTERVAL ERROR - USE
EXEC=nnnnnnnn AND/OR
System action NDB=nnnnnnnn

Explanation
User response The RLMU INT,EDXEC= or RLMU INT,NDB= or RLMU
INT,EXEC=nnnnnnnn,NDB=nnnnnnnn command was
Refer to the documentation for details for the syntax of entered without a valid number for EXEC and/or NDB.
the RLMU command.
OC2224 LIMIT ERROR - System action
USE KILL=nnnnnnnn OR
WARN=nnnnnnnn The command will be rejected.

An invalid RLMU call has been generated. Follow the EXEC= and NDB= keywords with a number
from 1 to 99999999.
System action OC2228 INTERVAL ERROR - MAXIMUM

TIME VALUE IS 604800 SECONDS
Explanation
User response
The RLMU INT,TIME= command was entered with a
Refer to the documentation for details for the syntax of value greater than 604800.
the RLMU command.
OC2225 INCOMPLETE COMMAND - REFER System action
TO DOCUMENTATION FOR SYNTAX
Explanation
User response
Specify a value of 9 through 604800.
System action OC2229 INTERVAL ERROR - MAXIMUM

NUMBER OF EXEC/NBD is
The command will be rejected. 99999999

The RLMU INT,EXEC= or RLMU INT,NDB= or RLMU Issue the OMEG INIT transaction to initialize Tivoli
INT,EXEC=nnnnnnnn,NDB=nnnnnnnncommand was OMEGAMON II in CICS.
entered with a value greater than 99999999.
OC3003 SHUTDOWN OPTION ACCESS
ERROR, CODE=nn
System action
The command will be rejected. Explanation
An internal error occurred in the OPT command when
User response accessing the PLT shutdown option.
Correct the value and reenter.
System action
OC2300 CEMT COMMAND SUCCESSFULLY
EXECUTED The OPT command fails.

This message is in response to a CMT SET command. Contact IBM Software Support.
OC3051 UNABLE TO FORMAT SIT,
System action CODE=aaaaaaaa
The CICS value was successfully set.
Explanation
User response The SIT command was unable to format the SIT. The
None. length of the SIT is denoted by aaaaaaaa. The most
likely explanation is that the user has applied IBM
OC3001 INVALID KEYWORD SPECIFIED, maintenance to CICS.
RE-ENTER
System action
Explanation
The SIT command fails.
The OPT command was entered with an invalid
keyword.
User response
Command OPT is displayed. OC3052 UNABLE TO DUMP SIT,

CODE=aaaaaaaa
User response
Explanation
Correct the keyword, and enter the OPT command.
The SIT command was unable to display the SIT in
OC3002 UNABLE TO ACCESS SHUTDOWN hexadecimal dump format. The length of the SIT is
OPTION, ISSUE OMEG INIT denoted by aaaaaaaa.

The OPT command was entered before OMEG INIT The SIT command fails.
was issued in the CICS address space. The shutdown
option can only be used during PLT shutdown after
User response
Tivoli OMEGAMON II has been initialized in CICS.
System action OC3053 INVALID KEYWORD SPECIFIED,
The OPT command fails. RE-ENTER

An invalid keyword was specified as an argument to Enter the appropriate argument for the specified
the SIT command. keyword.
OC3403 INVALID AID ADDRESS
System action SPECIFIED
The SIT command fails.
Explanation
User response The AID address must be eight characters or less and
Correct the keyword and enter the SIT command. must be hexadecimal.
OC3054 KEYWORK SPECIFIED WITHOUT

System action
ARGUMENT
The AIDS command fails.
Explanation
User response
A keyword was specified for the SIT command but no
argument was specified for the keyword. Enter an eight character hexadecimal address as an
argument to the ADDRESS keyword.
System action OC3404 INVALID ENTRY LENGTH
The SIT command fails. SPECIFIED

Enter the appropriate argument for the specified The argument for the AIDS keyword must be 4 bytes or
keyword. less.
OC3401 INVALID KEYWORD SPECIFIED,

System action
RE-ENTER
Explanation
User response
An invalid keyword was specified as an argument to
the AIDS command. Enter a four byte (or less) argument for the AIDS
keyword.
System action OC3405 NO AIDS FOUND IN CICS
Explanation
User response CICS was searched for Automatic Initiate Descriptors
Correct the keyword and enter the AIDS command. and none were found.

System action
ARGUMENT
The AIDS does not produce output.
Explanation
User response
A keyword was specified for the AIDS command but no
argument was specified for the keyword. This is a normal response if no AIDs currently exist in
CICS.
System action OC3406 NO MATCHING AIDS FOUND IN
The AIDS command fails. CICS

CICS was searched for Automatic Initiate Descriptors The ICES command fails.
and none matched the specified keyword arguments.
User response
System action
Enter the appropriate argument for the specified
The AIDS command fails. keyword.
OC3413 INVALID ICE ADDRESS SPECIFIED
User response
Use the AIDS command without keywords to Explanation
determine if the AID you are looking for exists. If the
AID is displayed by the AIDS command, and you have The ICE address must be eight characters or less and
entered the keyword=cccc argument correctly, contact must be hexadecimal.
System action
OC3407 REQUESTED AID NOT FOUND IN
CICS The ICES command fails.

CICS was searched for an Automatic Initiate Enter an eight character hexadecimal address as an
Descriptor and none matched the specified address. argument to the ADDRESS keyword.
OC3414 INVALID ENTRY LENGTH
System action SPECIFIED
Explanation
User response The argument for this ICES keyword must be 4 bytes
or less.
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 System action
entered the ADDRESS=cccccccc argument correctly,
The ICES command fails.
OC3411 INVALID KEYWORD SPECIFIED, User response
RE-ENTER
Enter a four byte (or less) argument for the ICES
keyword.
Explanation
OC3415 NO ICES FOUND IN CICS
An invalid keyword was specified as an argument to
the ICE command.
Explanation
System action CICS was searched for Interval Control Elements and
none were found.
The ICES command fails.

The ICES command does not produce output.
Correct the keyword and enter the ICES command.
OC3412 KEYWORD SPECIFIED WITHOUT User response
ARGUMENT
None.
Explanation OC3416 NO MATCHING ICES FOUND IN
CICS
A keyword was specified for the ICES command but no
argument was specified for the keyword.

CICS was searched for Interval Control Elements and None.
none matched the specified keyword arguments.
OC3423 KILL PROCESSING WAS
BYPASSED FOR 1 OR MORE AIDS
System action
The ICES command fails. Explanation
The AIDs was no longer in the AID chain. It (they) had
User response already been killed or processed by CICS.
None.
System action
OC3417 REQUESTED ICE NOT FOUND IN
CICS The AIDK command fails.

CICS was searched for an Interval Control Element None.
and none matched the specified address.
OC3430 ICEK MUST BE QUALIFIED BY
TERM, TRAN OR ADDRESS
System action
The ICES command fails. Explanation
When killing an ICE, the ICE must be qualified with
User response either a TERM, TRAN, or ADDRESS argument.
None.
System action
OC3420 AIDK MUST BE QUALIFIED BY
TERM, TRAN OR ADDRESS The ICEK command fails.

When killing an AID, the AID must be qualified with Enter the appropriate keyword with argument and
either a TERM, TRAN, or ADDRESS argument. enter the command.
OC3432 KILL PROCESSING WAS
System action BYPASSED FOR THIS ICE
Explanation
User response The ICE is no longer in the ICE chain. It has either
Enter the appropriate keyword with argument and already been killed, or has completed processing and
enter the command. has been de chained by CICS. Kill processing is also
bypassed if the ICE type is Wait or Post or if the ICE is
OC3422 KILL PROCESSING WAS a DWE.
BYPASSED FOR THIS AID
System action
Explanation
The ICEK command fails.
The AID was no longer in the AID chain. It was either
already killed, or had completed processing and was
User response
dechained by CICS.
None.
System action OC3433 KILL PROCESSING WAS
The AIDK command fails. BYPASSED FOR 1 OR MORE ICES

Explanation Table 16. The possible values for the service task that
The ICEs was no longer in the ICE chain. It (they) was not able to perform the service. (continued)
had either already been killed, or had completed Value Description
processing and was dechained by CICS.
that recorded by the AIDK command. The
aid is not killed.
System action
0000004 The AID was located by the service task
The ICEK command fails. 6 but its transaction ID was not the same as
that recorded by the AIDK command. The
User response aid is not killed.
None. 0000004 The AID was located by the service task
7 but its request ID was not the same as
OC3434 KILL BYPASSED, SERVICE TASK that recorded by the AIDK command. The
RETURNED = cccccccc AID is not killed.
Explanation 000000F The service task is not responding. The

0 AID is not killed.
This message is issued in response to an AIDK
command, and indicates that the service task was not 000000F There are no available work elements to
able to perform the service. The possible values for 1 use for this request. The AID is not killed.
cccccccc are: 000000F The service task is not available. The AID
2 is not killed.
Table 16. The possible values for the service task that
was not able to perform the service. 000000F The service task work area could not be
3 found. The AID is not killed.
Value Description
000000F OMEG INIT was not issued. The AID is not
0000000 10 secondary tasks are already started. 4 killed.
1 No more are allowed.
0000000 Invalid request (internal error).
2
System action
None.
0000000 The secondary task is not responding.
3
User response
0000000 The secondary task abended.
4 Action:
0000000 A new secondary task was started during Table 17. User Actions
5 the last second.
Value Description
0000000 No room is available in the secondary
6 tasks table. 0000000 Retry the command later.
1
0000000 Unable to start a new secondary task.
b 0000000 Contact IBM Software Support.
2
0000000 Unable to start a new secondary task due
c to MXT or AMXT. 0000000 Due to activity in the CICS region, the
3 service task did not complete the request
0000004 The service task could not find the AID to in the allotted time. Check whether the
2 be killed. AID still exists and, if so, enter the
command again. If the situation persists,
0000004 A task was already started for the AID to
shut down and initialize the service task
3 be killed.
by issuing the OMEG transaction with the
0000004 The AID was unchained, but its storage SRVSHUT and SRVINIT keywords.
4 could not be freed.
0000004 The AID was located by the service task
5 but its terminal ID was not the same as

Table 17. User Actions (continued) Table 17. User Actions (continued)
Value Description Value Description
0000000 Issue OMEG SRVSHUT to finish the and that transaction OMEG has been
4 service task processing. Then, issue successfully executed in CICS.
OMEG SRVINIT to initialize it and reenter
the command. OC3460 INVALID USER TCA ADDRESS
SPECIFIED
0000000 Retry the command later.
5
Explanation
0000000 Contact IBM Software Support.
6 The address specified for the TCA keyword is invalid.
This keyword must contain an existing User TCA
0000000 Contact IBM Software Support. address. Either the address was entered incorrectly or
b the task has already ended.
0000000 Increase the MXT and AMXT SIT values.
c System action
0000004 Correct the AID address entered with the The EIB command stops processing.
2 command and reenter the command.
0000004 None. User response
3
Specify a valid User TCA address for the task you are
0000004 None. inquiring about if the transaction has not yet ended.
4
OC3461 POINTER TO EXEC INTERFACE
0000004 Due to CICS activity, data for the AID has STRUCTURE NOT AVAILABLE
5 changed. Verify that the AID still exists
for the terminal, and, if so, reenter the Explanation
command.
During EIB command processing, the control block
0000004 Due to CICS activity, data for the AID has structure of the specified task is verified. An error was
6 changed. Verify that the AID still exists for detected; therefore, the request cannot be processed.
the transaction ID, and, if so, reenter the
command.
System action
0000004 Due to CICS activity, data for the AID
7 has changed. Verify that the AID with the The EIB command stops processing.
REQID exists and reenter the command.
User response
000000F The service task is taking longer
0 than expected to perform the request, Investigate the task in question. Make sure that the
probably due to high activity in CICS. If transaction has not ended yet or CICS has not suffered
the marked AIDs were not killed, issue the a storage corruption, damaging task-related control
request again. block structures.
000000F Issue the OMEG SRVSHUT transaction, OC3462 POINTER TO EXEC INTERFACE
1 then OMEG SRVINIT to reinitialize the BLOCK NOT AVAILABLE
service task.
000000F Issue the OMEG SRVINIT transaction to Explanation
2 initialize the service task. During EIB command processing, the control block
000000F Issue the OMEG SRVSHUT transaction, structure of the specified task is verified. An error was
3 then OMEG SRVINIT to reinitialize the detected; therefore the request cannot be processed.
service task.
000000F Ensure that transaction OMEG and System action
4 program KOCOME00 are defined to CICS The EIB command terminated.

User response OC3501 TABL ENTRY CONFLICTS WITH
CICS TABLE SPECIFIED
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 Explanation
control block structures. The table name is incompatible with the entry name
OC3463 PLEASE SPECIFY USER TCA specified.
ADDRESS WITH KEYWORD TCA=
System action
The EIB command was entered without the TCA
keyword. User response
Use the proper entry name/number keyword for the
System action desired file, or use the generic ID= keyword operand to
The EIB command terminated. specify an entry.
OC3502 TABL INVALID SELECTION
User response OPTION SPECIFIED
The User TCA address must be specified with keyword
TCA= for the EIB command to furnish the request. Explanation
To view the format of the EIB command, enter '/' in The selection criteria specified are unsupported.
column one followed by EIB.
OC3464 EIB COMMAND DOES NOT System action
SUPPORT CICS SYSTEM TASKS
Explanation
User response
The specified User TCA address belongs to a CICS
system task. Such tasks are not eligible for the EIB Correct the arguments of the SELECT= keyword and
command processing. enter the command.
OC3503 TABL SELECTION INVALID FOR
System action CICS TABLE SPECIFIED
None, this is only an informational message.
Explanation
User response The selection criteria specified are not compatible with
the table name entered.
Ensure that the correct User TCA address was
specified for other than CICS system tasks.
System action
OC3500 TABL Invalided ENTRY SUPPLIED
Explanation
User response
The entry name/number specified for the table
identified by aaa. Correct the arguments of the SELECT= keyword and
enter the command.
System action OC3504 TABL SELECTION CRITERIA

INVALID WITH SPECIFIC ENTRY
Explanation
User response
Selection criteria and a specific entry name/number
Correct the table entry name/number and enter the were specified as operands of the TABL command.
command.

The command stops processing. A parameter is missing for a keyword on the GRPS
command.
User response
System action
Change the entry name/number to specify a generic
value (using wild card characters) or choose either the The command stops processing.
selection criteria or an entry name/number (but not
both), for the table search. User response
OC3505 TABL DISPLAY OPTIONS ONLY Correct the input, and enter the command.
VALID FOR SINGLE TABLE ENTRY
OC4004 GRPS GROUP MUST BE NUMERIC
IN THE RANGE 1–MAXGRPS OR *
Explanation
The DUMP option was specified for a generic table Explanation
search.
The GRPS command expects a group identifier but
finds an invalid value. The value must be in the range
System action
1–maxgrps inclusive, where maxgrps is the value
The command stops processing. specified in the KOCGLOB macro, or the wildcard value
* representing all groups must be specified.
User response
System action
Limit the table search to a specific entry or remove the
DUMP operand from the TABL command. The command stops processing.
OC4001 GRPS INVALID GROUP KEYWORD
SPECIFIED, RE-ENTER User response
Correct the input, and enter the command.
Explanation
OC4005 GRPS GROUP NUMBER WAS NOT
The command encountered an invalid keyword. SUPPLIED

The command stops processing. The GRPS command expects a group identifier but
finds none.
User response
System action
OC4002 GRPS EXCESS KEYWORDS
IGNORED
User response
Explanation Correct the input, and enter the command.
Extra keywords were specified in the GRPS command. OC4006 GRPS GROUP=* IS INVALID
WITHOUT SPECIFYING ELEMENTS
System action
Explanation
The command ignores the additional keywords.
The generic group identifier may only be used if
User response specific group elements are included (TERM=, TRAN=,
PROG=).
None.
OC4003 GRPS KEYWORD SPECIFIED System action
WITHOUT ARGUMENT The command stops processing.

Correct the input, and enter the command. The command stops processing.
OC4007 GRPS GROUP TYPE NOT
SPECIFIED User response
Explanation
OC4011 GRPS NO GROUPS DEFINED
A requested group change could not be made because
the group type was not included in the command. Explanation
There are no groups currently defined to Tivoli
System action
OMEGAMON II.
System action
User response
None.
OC4008 GRPS INVALID GROUP TYPE. User response
SPECIFY TRAN, PROG OR TERM None.
OC4012 GRPS REQUESTED GROUP WAS
Explanation
NOT FOUND
The GRPS command specified an unrecognized group
type. Explanation
The specified group does not exist.
System action
The command stops processing. System action
None.
User response
Correct the input, and enter the command. User response
OC4009 GRPS GROUP TYPE AND ELEMENT None.
TYPE CONFLICT
OC4013 GRPS REQUESTED GROUP HAS NO
ELEMENTS DEFINED
Explanation
The TYPE= keyword parameter of GRPS does not Explanation
agree with the type of elements specified.
The specified group is empty.
System action
System action
None.
User response
User response
None.
OC4010 GRPS INVALID ELEMENTS
SPECIFIED OC4014 GRPS GROUP IS NOT DEFINED
The group elements were improperly formatted or The specified group is not currently defined to Tivoli
have an invalid length. OMEGAMON II.

None. Add an element keyword and argument and re-issue
the command.
User response OC4020 GRPS WARNING: GROUP NAME
None. TRUNCATED TO 12 BYTES
OC4015 GRPS GROUP IS ALREADY

Explanation
DEFINED
The group name exceeds the twelve character limit.
Explanation
System action
An attempt was made to add a group that already
exists. The group’s name includes the first twelve characters
specified.
System action
User response
None.
User response OC4021 GRPS WARNING: GROUP NAME
Specify a group that is not already created. DEFAULTED TO GROUP NUMBER
OC4016 GRPS RTA MONITOR ACTIVE,

Explanation
REQUEST IGNORED
A group name was not specified when creating a
Explanation group.
Groups cannot be modified while the response time

System action
collector is active.
The group number will be assigned as the name of the
System action group. For example, if group one is defined, it will have
the name GROUP 01.
User response
User response
None.
Use the RTA STOP command to terminate the
response time collector. Then enter the GRPS OC4023 GRPS INVALID CRITICAL
command, followed by the RTA START command, to THRESHOLD SPECIFIED, RE-
reactivate the response time collector ENTER
OC4017 GRPS ELEMENT THRESHOLD

Explanation
REQUIRES AN ELEMENT NAME
The interval record collector (critical) threshold
Explanation specified is not valid.
The GRPS command has been issued with the RESP,

System action
HOST, or NET threshold setting keyword, but no
element has been specified. These keywords are The command stops processing.
applicable only to elements.
User response
System action
Correct the threshold, and enter the command.
The update or add fails.
OC4024 GRPS INVALID RESPONSE
THRESHOLD SPECIFIED, RE-
ENTER

The response time threshold specified is not valid. None.
OC4031 GRPS NO SPACE REMAINING THE
System action GROUPS ID TABLE
Explanation
User response An attempt to add an element to the group table failed
Correct the threshold, and enter the command. due to a lack of available space.
OC4026 GRPS WARNING: GROUP

System action
CRITICAL THRESHOLD DEFAULT
IS 2 SECS The command stops processing.

No critical threshold was specified on the GRPS The maximum number of IDs that can be supported
command, so a default value of two seconds was via the GRPS facility is defined on the KOCGLOB
assumed. MAXIDS=nnn parameter. Increase the value and
reassemble the GLOBAL module.
System action OC4040 GRPS GROUP=* IS INVALID ON
None. UPDATE

None. A generic group identifier may not be used when
performing an update.
OC4027 GRPS WARNING: RESPONSE
THRESHOLD DEFAULT IS 1 SEC
System action
No response time threshold was specified on the

User response
GRPS command, so a default value of one second was
assumed. Correct the input, and enter the command.
OC4041 GRPS GROUP UPDATES INVALID
System action WHEN ELEMENTS SPECIFIED
None.
Explanation
User response The UPD operand of GRPS cannot be used with a
None. specific group identifier when elements are specified
on the command.
OC4030 GRPS INVALID ADD, ELEMENTS
ALREADY DEFINED IN GROUP
System action
The specified group already contains the element

User response
being added.
System action OC4042 GRPS GROUP TYPE CANNOT BE
The request is ignored. UPDATED UNTIL GROUP IS EMPTY

Groups containing entries cannot have their type Add keywords for the UPDATE request that is required
changed until all elements are deleted from the group. and issue the command again.
OC4050 GRPS INVALID DELETE, NO
System action ELEMENTS SPECIFIED
Explanation
User response The elements to be deleted by GRPS were not
Correct the input, and enter the command. specified.
OC4043 GRPS INVALID UPDATE,

System action
ELEMENTS NOT DEFINED
Explanation
User response
An attempt was made to update a group element
which could not be found in the group table. Correct the input, and enter the command.
OC4051 GRPS INVALID DELETE,
System action ELEMENTS NOT DEFINED IN
The command stops processing. GROUP

Correct the input, and enter the command. The elements to be deleted by GRPS do not belong to
the group specified.
OC4044 GRPS THRESHOLD MUST BE
SUPPLIED WHEN UPDATING
System action
ELEMENTS
Explanation
User response
A request to update one or more group elements did
not include a threshold value. Correct the input, and enter the command.
OC4060 GRPS GROUP=* IN INVALID ON
System action CLEARANCE
Explanation
User response A generic group identifier may not be used when
Correct the input, and enter the command. performing a clear operation.
OC4045 GRPS INVALID UPDATE, NO

System action
CHANGES SPECIFIED
Explanation
User response
The GRPS command has been issued with the UPDATE
keyword but other keywords are missing. Correct the input, and enter the command.
OC4061 GRPS ELEMENT LIST IS INVALID
System action ON CLEARANCE
The update fails.

An element list may not be specified when performing Use an argument for the SELECT keyword that is valid
a clear. Clear will remove ll elements from a given and enter the command again.
group. Use the DEL operand of GRPS to selectively
remove entries from a group.
LONG
System action
Explanation
The TSQ command has been entered with an ID that is
longer than eight characters.
User response
Correct the input, and enter the command. System action
OC4101 INVALID KEYWORD SPECIFIED, The command fails.
RE-ENTER
User response
Explanation
Change the ID argument to be eight or fewer
The TSQ command has been entered with an invalid characters and enter the command again.
keyword.
OC4105 INVALID HEXADECIMAL VALUE,
RENTER
System action
The command fails. Explanation
An invalid hexadecimal value was detected where a
User response hexadecimal value is expected.
Correct he keyword and enter the command. Use the
help facility to determine valid keywords. System action
OC4102 KEYWORD SPECIFIED WITHOUT The command stops processing.
ARGUMENT
User response
Explanation
Reenter the command using an even number of
The TSQ command has been entered without an ID or characters 0-9 or A-F.
SEL argument.
OC4106 ID PARAMETER NOT SPECIFIED
System action
Explanation
The command fails.
The TSQD detected that the required ID parameter
was not specified.
User response
Add an ID argument or valid select criteria to the System action
requisite keyword and enter the command.
OC4103 INVALID SELECT CRITERIA, USE
HELP FOR A VALID LIST User response
Reenter the command specifying the ID parameter.
Explanation
OC4107 TSMODEL NOT FOUND
The TSQ command has been entered with an invalid
argument for the SELECT keyword.
System action
The command fails.

The TSMD was entered with MODEL=xxxxxxxx The command fails.
parameter specified. The specified Temporary Storage
model was not detected in the CICS region. User response
Correct the keyword and enter the command. Use the
System action
help facility to determine valid keywords.
ARGUMENT
User response
Reenter the command specifying a model that exists in Explanation
CICS.
The RESP command has been entered without an ID or
OC4108 MISSING KEYWORD. SPECIFY NUM argument.
QUEUE=NAME,OWNER or WAITER
System action
Explanation
The command fails.
The TSWD was entered without one of the required
parameters. User response
Add an ID argument or a group number to the requisite
System action
keyword and re-enter the command.
OC4153 GROUP NUMBER MUST BE
BETWEEN 1 AND 30
User response
Reenter the command specifying one of the required Explanation
parameters. Enter a slash "/" before the command to
obtain detailed help. The TSQ command has been entered with an argument
for the NUM keyword that is not in the valid range.
OC4109 REQUESTED QUEUE OWNER OR
WAITER NOT FOUND System action
The command fails.
Explanation
The TSWD was could not detect any owner or waiter User response
for the specified Temporary Storage queue. This could
be either the queue does not exist or because no Change the group number to be in the range 1–30 and
owner or waiter could be located. enter the command again.
System action LONG
Explanation
User response The RESP command has been entered with an ID that
None. is longer than 8 characters.
OC4151 INVALID KEYWORD SPECIFIED, System action

RE-ENTER
The command fails.
Explanation
User response
The RESP command has been entered with an invalid
keyword. Change the ID argument to be 8 or fewer characters
and enter the command again.

OC4200 INTERNAL ERROR, RC=nn System action
The command stops processing normally after issuing
Explanation this error message.
Collector of information about the CICS dump
component has detected an internal error in User response
processing the request.
Contact IBM Software Support for assistance with this
problem.
System action
OC4230 Subroutine IGGCSI00 was not
The request is ignored. loaded at startup

Contact IBM Software Support. IBM Z OMEGAMON for CICS uses the IBM subroutine
OC4210 INVALID INTERNAL SPECIFIED. IGGCSI00 to collect VSAM details. The subroutine is
MUST BE 1 TO 60 loaded during OMEGAMON startup.

The DUMP command detected that the None.
INTERVAL=parameter was specified with a value that
was outside the acceptable range. User response
Review the OMEGAMON log for any messages which
System action may indicate why the module was not loaded. Contact
The command stops processing. IBM Software Support for further assistance.
OC4231 FCT error received from
User response IGGCSI00: RC=04, Reason
code=xxxx
Enter the command again and specify an interval value
between 1 and 60..
Explanation
OC4221 Invalid control block structure
detected 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
Explanation code.
IBM Z OMEGAMON for CICS is unable to process the
MQ control blocks detected in CICS. System action
None.
System action
The command stops processing normally after issuing User response
this error message.
See the response and reason codes for the IGGCSI00
subroutine, which are listed in the IBM manual Catalog
User response Search Interface User’s Guide in the section "Managing
Contact IBM Software Support for assistance with this Catalogs". Contact IBM Software Support for further
problem. assistance.
OC4222 Unknown version of MQ detected OC4232 FCT error received from

IGGCSI00: RC=08, Reason
code=xxxx
Explanation
The version/release of MQ you executing is not
supported by OMEGAMON II for CICS.

IBM Z OMEGAMON for CICS uses the IBM IGGCSI00 The DB2 command was entered with the SEL=TCBS
subroutine to collect VSAM details. The subroutine parameter. OMEGAMON was unable to locate any DB2
returned a response code 8, with the specified reason TCBs in this CICS region.
code.
System action
System action
None.
User response
User response
Use this command only on CICS regions that have
See the response and reason codes for the IGGCSI00 active DB2 TCBs.
subroutine, which are listed in the IBM manual Catalog
Search Interface User’s Guide in the section "Managing OC5000 UNABLE TO OBTAIN WORK AREA
Catalogs". Contact IBM Software Support for further STORAGE
assistance.
Explanation
OC4233 FCT error received from
IGGCSI00: RC=xx Insufficient storage was available to allocate a work
area.
Explanation
System action
IBM Z OMEGAMON for CICS uses the IBM IGGCSI00
subroutine to collect VSAM details. The subroutine The Global Maintenance Program stops processing.
returned a response code 12 or 16.
User response
System action
Increase the region size of the job used to run the
None. Global Maintenance Program.
OC5001 UNABLE TO OPEN DATASET WITH
User response DDNAME= aaaaaaaa
See the response and reason codes for the IGGCSI00
subroutine, which are listed in the IBM manual Catalog Explanation
Search Interface User’s Guide in the section "Managing
A nonzero return code was detected by the OPEN
Catalogs". Contact IBM Software Support for further
macro when attempting to open the dataset denoted
assistance.
by aaaaaaaa.
OC4401 THE DISPATCHER SUBTASK
ANCHOR WAS NOT LOCATED System action
For a read request, the default copy of the global
Explanation
module is used. All other functions stop without
The DB2 command was unable to locate the CICS further processing.
Dispatcher Anchor block; this indicates an internal
OMEGAMON error. User response
Verify that the KOC2GLBL ddname is properly
System action
specified in the JCL.
OC5002 GMP WILDCARDS ONLY ALLOWED
WITH VERIFY, REFORMAT, AND
User response NOREFORMAT FUNCTIONS
Explanation
OC4402 NO CICS TCBS MEET THE
SELECTION CRITERIA A wildcard character (*) was included in the suffix of
either a read, write, or test function.

System action without reformatting (N), verify with reformatting (R),
or build sample default global source members (S).
further processing. System action
User response
Remove the wildcard character from the global User response
module suffix. Correct the function code on the EXEC card and rerun
OC5003 UNABLE TO OBTAIN GLOBAL I/O the job.
BUFFERS, LENGTH= aaaaaaaa OC5006 RKC2GLBL DATASET NOT
ALLOCATED WITH LRECL=80
Explanation
Insufficient storage was available less than the line for Explanation
the I/O buffers used to process the global source file. The RKC2GLBL ddname points to a dataset that has
The amount of storage that could not be allocated is not been allocated with an 80 byte logical record
denoted by aaaaaaaa. length.

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

Increase the region size available to the Global Allocate the RKC2GLBL dataset with an LRECL of 80
Maintenance Program. bytes.
OC5004 PARM NOT SPECIFIED AS OC5007 CLOSE MACRO FAILED FOR
FUNCTION, SUFFIX=XX DDNAME aaaaaaaa
When the Global Maintenance Program is run as a The ddname identified by aaaaaaaa could not be
batch job, an 11–byte parameter must be passed on closed.
the EXEC card that includes a single character function
followed by the global suffix.
System action
System action For a read request, the default copy of the global
The request is ignored. further processing.

Correct the PARM operand on the EXEC card and rerun Check the operator console for messages that may
the job. indicate why the dataset failed to close properly.
OC5005 GMP FUNCTION CODE IS NOT T, V, OC5008 ESTAE MACRO FAILED WITH
N, R, OR S RC=aaaaaaaa
When the Global Maintenance Program is run as a Recovery could not be established using the ESTAE
batch job, only five function codes are permitted to macro.
either test (T), verify without reformatting (V), verify

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

Look up the ESTAE return code in the IBM Application Consult the operator console for previous messages
Development Macro Reference manual, correct the that indicate why the global function failed. Correct the
problem and submit the job again. cause of the errors and retry the request.
OC5009 DEQ MACRO FAILED WITH OC5012 NOT AUTHORIZED, UNABLE TO
RC=aaaaaaaa LOAD DEFAULT GLOBAL
The ENQ used to serialize access to the global source The default copy of the global module could not be
dataset could not be released with a corresponding brought into memory using a directed load because
DEQ. the job does not have APF authorization.

The resource remains enqueued until the job stops The global request is not honored.
processing. This may result in an ENQ failure if another
global maintenance request is made before the job User response
completes.
The default module is used only when an error is
encountered during processing of the global source
User response
dataset. Inspect the operator console for previous
Look up the DEQ return code in the IBM Application errors and make any necessary changes. To ensure
Development Macro Reference manual, correct the that the default is available on a failed read request,
problem and submit the job again. change the job to run with APF authorization.
OC5010 PROCESSING SUCCESSFUL FOR OC5013 ABNORMAL TERMINATION
GLOBAL aaaaaaaa DETECTED DURING I/O
OPERATION, CODE=Sxxx
Explanation
Explanation
The global module identified by aaaaaaaa was
processed without error. Either an x13 or x37 ABEND was encountered while
trying to access the global source dataset.
System action
System action
None.
User response module is used; no other global request functions are
honored.
None.
OC5011 PROCESSING FAILED FOR GLOBAL User response
aaaaaaaa Refer to the IBM System Codes manual for a
description of the ABEND code identified by the Sxxx
Explanation value. Correct the cause of the error and retry the
request.
The global module identified by aaaaaaaa
encountered problems. OC5014 DEFAULT COPY OF GLOBAL HAS
BEEN SELECTED

Due to an error during global processing, the Global A database control statement was found, however, no
Maintenance Program has loaded a default copy of the sub component header was active at the time.
global module.
System action
System action
The control card is not processed. For a read request,
The default copy of the global module is returned, a default copy of the global module is returned to the
rather than the source member requested by the caller. All other functions fail to complete successfully.
caller.
User response
User response
Database sub components are coded within << >>
Refer to the operator console for errors that might characters. For example, the DLI database must be
explain why the Global Maintenance Program had to specified as <<DLI>>. Ensure one of the database sub
resort to loading a default copy of the global module. components is properly specified for the control card
in error.
OC5020 GVR CARD 0255: GROUP_TYPE=LU
OC5023 UNABLE TO OPEN RKC2GLBL
Explanation DATASET FOR INPUT
A syntax error has been found in a global control card.

Explanation
This message displays the card in error.
The OPEN macro used to gain access to RKC2GLBL has
System action returned a non-zero completion code.

System action
a default copy of the global module is returned to the
caller. All other functions fail to complete successfully. For a read request, a default copy of the global module
User response complete successfully.
Refer to the operator console for an associated error

User response
message that details the syntactical problem with the
control statement. Check the operator console for messages that may
indicate why the RKC2GLBL dataset could not be
OC5021 CONVERSE_TIME OPERAND NOT
opened. Correct the cause of the error and retry the
RECOGNIZED
request.
Explanation OC5024 UNABLE TO LOCATE GLOBAL

SOURCE MEMBER aaaaaaaa
The CONVERSE_TIME operand is neither, IRWAIT,
IOWAIT, NOIRWAIT, nor NOIOWAIT.
Explanation
System action The FIND macro could not locate the global member
denoted by the aaaaaaaa value.
a default copy of the global module is returned to the
System action
caller. All other functions fail to complete successfully.
User response is returned to the caller. All other functions fail to
Specify a valid CONVERSE_TIME operand.
OC5022 NO DATABASE SUB-COMPONENT User response
SPECIFIED
Verify that the specified global member appears in the
partitioned dataset pointed to by the RKC2GLBL DD
statement.

OC5025 UNABLE TO OBTAIN User response
GLOBAL MODULE STORAGE,
LENGTH=aaaaaaaa Ensure that the component heading is bracketed by <
> characters.
Explanation OC5028 COMPONENT HEADING NOT

RECOGNIZED
Insufficient memory was available to store the symbol
table used to harbor global settings. The value
aaaaaaaa indicates the number of bytes requested on Explanation
the failed GETMAIN attempt. 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 System action
is returned to the caller. All other functions fail to For a read request, a default copy of the global module
complete successfully. is returned to the caller. All other functions fail to
User response
Increase the region size available to the job. User response
OC5026 NO COMPONENT HEADING Ensure that the component heading is properly
SPECIFIED FOR KEYWORD specified.
OC5029 SYNTAX ERROR DETECTED IN
Explanation CONTROL STATEMENT
A control card was encountered for which no

component heading could be found. Explanation
The control card does not have an equals sign (=)
System action separating the keyword from its operand.

is returned to the caller. All other functions fail to System action
complete successfully. For a read request, a default copy of the global module
Component headings are enclosed in < > characters.

They are necessary to indicate which section of a User response
global module a particular control card is intended to Ensure that an equals sign is used to delimit a control
effect. Verify that a component heading precedes the keyword.
control card in error and retry the request.
OC5030 CONTROL STATEMENT NOT
OC5027 SYNTAX ERROR DETECTED IN RECOGNIZED FOR COMPONENT
COMPONENT HEADING
Explanation
Explanation
The control card does not belong to the list of
A control card was encountered whose first non-blank acceptable statements for the active component
character was a ’<’ indicating a component heading. header.
However, a trailing ’>’ character was not found.
System action
System action

Check the previous component header, enclosed in < For a read request, a default copy of the global module
> characters, to ensure that it accepts the specified is returned to the caller. All other functions fail to
control card. If not, place the control card under its complete successfully.
proper component heading.
OC5031 SYNTAX ERROR DETECTED IN User response
SUB-COMPONENT STATEMENT Ensure that the operand is completed with either a
blank, or in the case of a sub list, a trailing ' ) '
Explanation parenthesis.
A subcomponent was indicated by the presence of ’<<’ OC5034 UNABLE TO CLOSE RKC2GLBL
characters in the first non-blank positions of the DATASET
control card. No trailing ’>>’ characters were found for
the subcomponent. Explanation
The CLOSE macro used to release access to the
System action
KOC2GLBL data set returned a non-zero completion
For a read request, a default copy of the global module code.
complete successfully. System action
User response
will be returned to the caller. All other functions will
Ensure that subcomponents are enclosed in << >> fail to complete successfully.
characters.
OC5032 SUB-COMPONENT STATEMENT User response
NOT RECOGNIZED Check the operator console for messages that might
explain why the data set could not be closed. Correct
Explanation the error and retry the request.
A subcomponent, enclosed in << >> characters, does OC5035 NUMERIC OPERAND NOT WITHIN
not appear in the translation tables for the currently RANGE aa – bb
active component heading.
Explanation
System action
The control card operand is not a numeric value that
For a read request, a default copy of the global module falls within the range denoted by aa–bb.
User response
Ensure that the subcomponent reflects a valid name, fail to complete successfully.
and that it appears under the proper component
heading. User response
OC5033 INVALID CONTROL STATEMENT Change the operand to a valid numeric setting.
OPERAND
OC5036 SYNTAX ERROR DETECTED IN
SUBLIST
Explanation
Either the control statement operand is not the correct Explanation
style, or it begins with a parenthesis character ’(’
to indicate a sub list, but does not end with a A sub list was specified, enclosed in parentheses,
corresponding parenthesis ’)’ sub list trailer. that either contains null values or an extraneous
parenthesis.

For a read request, a default copy of the global module Change the operand to a valid option.
OC5040 CPU_THRESHOLDING MUST BE
ENABLE/DISABLE/AUTO
User response
Explanation
Ensure that the sub list is delimited by a single set of
parentheses and that no null values are specified. CPU_THRESHOLDING does not specify a valid operand
option.
OC5037 SHUT_OPTIONS MUST BE PURGE/
NOPURGE/OPER System action
Explanation
The SHUT_OPTIONS keyword specifies an operand complete successfully.
that is not valid option.
User response
System action
Change the operand to a valid option.
is returned to the caller. All other functions fail to OC5041 DLI_CLOCKS_AND_COUNTERS
complete successfully. MUST BE AUTO/NOAUTO/NO

Change the operand to a valid option. The specified keyword does not indicate a valid option.
OC5038 OPERAND MUST BE YES/NO System action

Explanation
The specified keyword does not have an operand of complete successfully.
YES or NO.
User response
System action
Change the operand to a valid option.
is returned to the caller. All other functions fail to OC5043 TRANSACTION ID HAS ILLEGAL
complete successfully. FORMAT

Change the operand to a valid option. The transaction identifier exceeds four bytes in length.
OC5039 OPERAND MUST BE AUTO/ System action

NOAUTO
Explanation
fail to complete successfully.
The specified keyword does not have an operand of
AUTO or NOAUTO. User response
Specify a valid transaction ID. Note that for the
System action
EXCLUDED_TRANS keyword, an asterisk (*) wildcard
For a read request, a default copy of the global module may only appear at the end of the transaction ID.
will be returned to the caller. All other functions will That is, the EXCLUDED_TRANS control may not include
fail to complete successfully. embedded asterisk (*) wildcards.

OC5044 ENTRY NAME EXCEEDS EIGHT Explanation
CHARACTER LIMIT
Control cards that define an OMEGAMON group
were found without a corresponding <<GROUP>>
Explanation subcomponent header.
The name is greater than eight bytes, not including any
MCT suffix. System action
complete successfully. User response
Include a <<GROUP>> subcomponent header to
User response properly isolate the different group definitions.
Specify an entry name that is not greater than eight OC5048 GROUP NAME EXCEEDS TWELVE
bytes in length. CHARACTERS
OC5045 GLOBAL USER EXIT NAME NOT
RECOGNIZED Explanation
The group name is too long.
Explanation
The exit name does not appear in the global System action
translation tables.
System action complete successfully.
is returned to the caller. All other functions fail to User response
Reduce the length of the group name to 12 bytes or
less.
User response
OC5049 DUPLICATE GROUP_NAME
Specify a valid global user exit name. DETECTED
OC5046 EXCLUDE LIST EXCEEDS 63
TRANSACTION IDS Explanation
The group name is not unique.
Explanation
The sub list contains more entries than can be System action
accommodated in the fixed portion of the global
module. For a read request, a default copy of the global module
System action
For a read request, a default copy of the global module User response
complete successfully. Select a group name that has not already been
defined.
User response OC5050 GROUP NAME CONTAINING

LEADING BLANKS IS INVALID
Reduce the number of IDs to 63 or less.
OC5047 NO <<GROUP>> SUB-COMPONENT Explanation
HEADER ACTIVE
The group name starts with a blank.

For a read request, a default copy of the global module Include a GROUP_NUMBER keyword in the group
is returned to the caller. All other functions fail to definition.
OC5054 GROUP_NAME NOT SPECIFIED
FOR GROUP
User response
Begin the group name with a non-blank character. Explanation
OC5051 GROUP_NAME=(*) IS INVALID A group name was never assigned to a group
definition; every group must have a unique name.
Explanation
System action
The group name is set to a single wildcard character.
User response
Include a GROUP_NAME keyword in the group
User response definition.
Select another group name. OC5055 UNABLE TO OBTAIN GROUP TABLE

STORAGE
OC5052 GROUP TYPE IS NOT TRAN, TERM,
PROG, OR LU
Explanation
Explanation Insufficient storage was available to store group
definitions.
The group type keyword specifies an operand that is
not valid.
System action
User response
User response Increase the region size available to the job.
Choose one of the four valid group types. OC5056 NO <<ID>> SUB-COMPONENT
ACTIVE
OC5053 GROUP_NUMBER NOT SPECIFIED
FOR GROUP
Explanation
Explanation Control cards that define an OMEGAMON group
element were found without a corresponding <<ID>>
A group number was never assigned to a group subcomponent header.
definition. Every group must have both a numeric
setting and a name.
System action

User response OC5060 TASKREQ INVALID ID SPECIFIED
Include an <<ID>> subcomponent header to properly
isolate the different group element definitions. Explanation
OC5057 OPERAND MUST BE 1–4 The TASKREQ operand is not one of the permissible
CHARACTERS values described in the OMEGAMON II configuration
guide. These are the valid options:
Explanation • #PAn (n=1–3)
The specified keyword operand is too long. • #Fnn (nn=01–36)

• #LPA, #MAG
System action • #OCD.
is returned to the caller. All other functions fail to System action
complete successfully. For a read request, a default copy of the global module
Limit the operand to a maximum length of four
characters. User response
OC5058 OPERAND MUST BE 1–8 Change the operand to specify a valid TASKREQ ID.
CHARACTERS OC5061 GROUP ELEMENT NAME IS
MISSING
Explanation
The specified keyword operand is too long. Explanation
A group element definition does not include the name
System action of the corresponding transaction, terminal, program, or
logical unit.
Limit the operand to a maximum length of eight
characters.
User response
OC5059 GENERIC LU IDS ARE NOT
SUPPORTED Supply one of the four permissible element types.
OC5062 ELIGIBLE_GROUPS NOT
Explanation SPECIFIED FOR ID
A logical unit group element contains wildcard (*)
characters. Explanation
A group element was never assigned to one or more
System action groups.
will be returned to the caller. All other functions will System action
fail to complete successfully. For a read request, a default copy of the global module
Remove the wildcard characters from the logical unit
definition.

User response OC5067 NO RESOURCE SUB-COMPONENT
SPECIFIED
Specify the groups to which the element belongs.
OC5064 NUMBER OF IDS EXCEEDS LIMIT Explanation
OF 2000
Control cards that define resource limiting were found
without a corresponding resource sub-component
Explanation header.
More than 2000 groups elements have been defined.
System action
For a read request, a default copy of the global module will be returned to the caller. All other functions will
is returned to the caller. All other functions fail to fail to complete successfully.
User response
User response Include a resource header, enclosed in << >>
Reduce the number of group elements to a maximum characters, that indicates the name of the resource to
of 2000. be monitored.
OC5065 DATA_STORE_TYPE MUST BE OC5068 TRANSACTION COUNT FOR

DSPACE OR FILEOCMP OR AUTO RESOURCE EXCEEDS LIMIT OF
999 ENTRIES
Explanation
Explanation
An invalid operand was specified for the Online Data
Viewing storage medium. The number of either included or excluded
transactions for a given resource is too large.
System action
System action
will be returned to the caller. All other functions will For a read request, a default copy of the global module
fail to complete successfully. is returned to the caller. All other functions fail to
User response
User response
Select a valid operand for the DATA_STORE_TYPE.
Limit the size of the transaction lists to 999 or less.
OC5066 FILE NAME EXCEEDS 44
CHARACTERS IN LENGTH OC5069 RTA INTERVAL NOT OF FORM
(X,Y,Z)
Explanation
Explanation
The DATA_STORE_FILE_NAME operand is longer than
the maximum length permitted for IBM data sets. The TIME_INTERVALS operand does not contain three
sub list values.
System action
System action
User response
User response
Choose a valid dataset name for the Online Data
Viewing facility. Provide three intervals as described in the
OMEGAMON II configuration guide.

OC5070 RTA INTERVALS ARE NOT PROPER Explanation
MULTIPLES
The TIME_SLOT operand has not been specified as a
sub list with two entries.
Explanation
The TIME_INTERVALS operand does not specify either System action
a second value that is a multiple of the first, or a third
value that is a multiple of the second. For a read request, a default copy of the global module
System action
complete successfully. Specify an operand that includes both the start and
end times.
User response OC5074 UNIT_ADDRESS IS MISSING
Supply an operand in the form (x,y,z), where y is a

multiple of x, and z is a multiple of y. Explanation
OC5071 TIME_SLOT END TIME BEFORE A dedicated session definition does not specify the
START TIME requisite unit address.

The second TIME_SLOT sub list element is less than or For a read request, a default copy of the global module
equal to the first sub list element. is returned to the caller. All other functions fail to
System action
User response
is returned to the caller. All other functions fail to Include a UNIT_ADDRESS keyword for each dedicated
complete successfully. session.
OC5075 UNIT_ADDRESS MUST BE 3 OR 4
User response CHARACTERS
Select an ending time that is greater than the start

time. Explanation
OC5072 MORE THAN 48 TIME_SLOT The dedicated session unit address has an length that
DEFINITIONS USED is not valid.

Too many time slots have been defined. For a read request, a default copy of the global module
System action
fail to complete successfully. Specify a proper three- or four-character unit address.
OC5076 USER_PROFILE MUST BE TWO
User response CHARACTERS
Limit the number of time slot definitions to a maximum

of 48. Explanation
OC5073 RTA TIME_SLOT NOT OF FORM The user profile suffix has an invalid length.
(HHMM,HHMM)

will be returned to the caller. All other functions will is returned to the caller. All other functions fail to
fail to complete successfully. complete successfully.

Select a suffix that is two characters long. Ensure that the count of sublist entries does not
exceed the limit.
OC5077 NO <<UNIT>> SUB-COMPONENT
HEADER ACTIVE OC5080 INCLUDED AND EXCLUDED
TRANSACTIONS ARE MUTUALLY
Explanation EXCLUSIVE
Control cards that define a dedicated session

Explanation
were found without a corresponding <<UNIT>>
subcomponent header. A resource limiting definition contains both included
and excluded transaction names.
System action
System action
User response
User response
Include a <<UNIT>> subcomponent header to
properly isolate the different session definitions. Separate the included and excluded transactions for
a given resource by placing them under their own
OC5078 UNABLE TO OBTAIN STORAGE FOR resource subcomponent ID.
SYMBOL TABLE
OC5100 I/O ERROR DETECTED - SYNAD
Explanation MESSAGE:
Insufficient memory was available to build the variable

Explanation
lists that are contained within the global control block
definition. During a READ or WRITE operation, a permanent I/O
error was detected on the global source dataset. The
System action data from the SYNAD message buffer is sent to the
operator console.
System action
Increase the region size of the job.
OC5079 TOO MANY SUBLIST ENTRIES User response
SPECIFIED, LIMIT=aa The SYNAD message buffer describes the source of
the problem. Take the appropriate action to ensure
Explanation the success of I/O operations on the global source
dataset.
The operand, enclosed in parenthesis, contains more
than the maximum number of sub list elements OC5101 UNABLE TO OBTAIN
allowed, as denoted by the aa value. GLOBAL MODULE STORAGE,
LENGTH=aaaaaaaa

Insufficient memory was available to build the global The bottleneck analysis clear intervals are improperly
data area in private storage more than the 16MB line. set.


Increase the region size of the job. Alter the bottleneck analysis intervals.
OC5102 INTERVAL_RECORDING=AUTO OC5105 GROUP DEFINITION EXCEEDS
REQUIRES MAX_GROUPS LIMIT
BOTTLENECK_ANALYSIS=AUTO
Explanation
Explanation
A GROUP_NUMBER keyword specifies an operand that
Two keywords in the global source file are is higher than the MAX_GROUPS setting.
inconsistent.
System action
System action
User response
User response
Either increase the MAX_GROUPS limit, or eliminate
Change one of the keyword operands to resolve the the group definitions that are beyond the acceptable
conflict. range.
OC5103 WARNING, OC5106 IMPROPER GROUP ASSIGNMENT
DLI_CLOCKS_AND_COUNTERS=NO FOR ID=aaaaaaaa
SPECIFIED, NO DLI
STATISTICSWILL BE PRODUCED Explanation
A group element of a particular type has been
Explanation
assigned to a group with a different type. For example,
Database collection was defined for DLI. However, no a transaction element includes an eligible group that is
clocks and counters have been requested. defined as containing programs.

No DLI statistics are produced. For a read request, a default copy of the global module
This message serves only as a warning and does not

User response
interfere with the creation of the global data area.
Ensure that group elements defined under the
OC5104 CLEAR_INTERVAL_LONG MUST <<ID>> subcomponent all specify eligible groups with
BE GREATER THAN matching types.
CLEAR_INTERVAL_SHORT
OC5107 FILE NAME NOT SPECIFIED FOR
DATA_STORE_TYPE=xxxxx

The DATA_STORE_FILE_NAME keyword was not The resource denoted by the aaaa value contains
included for Online Data Viewing. The file type of an EXCLUDED_TRANSACTION keyword in addition to
xxxxx, where xxxxx is FILEOCMP or AUTO, requires a either KILL or WARN limits.
valid dataset name be provided.
System action
System action
User response
User response
Remove the KILL_LIMIT and WARN_LIMIT keywords
Provide a file name for use by the Online Data Viewing from resource definitions that exclude transactions.
facility.
OC5111 WARN_LIMIT NOT LESS THAN
OC5108 RTA TIME_SLOT OVERLAP HAS KILL_LIMIT FOR RESOURCE
BEEN DETECTED aaaaaaaa
Two or more time slots share a common period. The limiting thresholds are not properly synchronized.

is returned to the caller. All other functions fail to will be returned to the caller. All other functions will
complete successfully. fail to complete successfully.

Revise the slot definitions to ensure they do not Alter the limits to ensure a warning happens prior to a
overlap. kill.
OC5109 LIMIT NOT SPECIFIED FOR OC5112 NUMBER OF IDS EXCEEDS
RESOURCE aaaaaaaa MAX_IDS LIMIT
The resource denoted by the aaaaaaaa value does not Too many group elements have been defined.
include either a KILL or WARN limit.
System action
System action
User response
User response
Either increase the MAX_IDS limit, or eliminate
Specify a limit that will act as a resource threshold. enough group elements to satisfy the ID constraints.
OC5110 LIMITS MAY NOT BE USED WITH OC5115I GBR PROGRAM CALLS WILL
EXCLUDED TRANSACTIONS FOR NOT BE TRACED BECAUSE
RESOURCEaaaa NOAUTO WAS SPECIFIED FOR
ENABLE_APPLICATION_TRACE.

Explanation RLCT
Container HWM
The TRACE_ALL_PROGRAM_CALLS=YES was specified
with ENABLE_APPLICATION_TRACE=NOAUTO. This RLDB
message informs the user that program trace setting DB2 requests
will be ineffective until application trace is activated. RLDC
DATACOM requests
System action RLDL
DL/I requests
System processing of the GLOBAL continues.
RLDS
DSA HWM storage
User response
RLED
For tracing of all program calls to be effective, EDSA HWM storage
the Application Trace Facility must also be enabled; RLEL
as below: ENABLE_APPLICATION_TRACE=AUTO elapsed time
TRACE_ALL_PROGRAM_CALLS=YES.
RLFC
OC5117E GWR FIND THE SHARE OPTIONS file requests
DO NOT ALLOW ACCESS TO
RLGD
datasetname(global)
GDSA HWM storage
RLID
Explanation IDMS requests
OMEGAMON for CICS needs to expand Global global RLMQ
but was unable to because the datasetname (specified MQ requests
in RKC2GLBL DD) is already allocated to another job or
RLSU
task.
SUPRA requests
RLU1
System action USREVNT1 requests
Processing will fail for Global global.
System action
User response Prior to issuing the message, RLIM stops the exceeded
When generating a sample Global, the original threshold to prevent the reissuing of identical
member can be deleted; otherwise ensure that messages. All remaining thresholds are kept intact and
datasetname is not already allocated to another job active. The transaction reverts to normal execution.
or task. Re-run this job.
OC8900 RESOURCE LIMIT EXCEEDED: tttt User response
RLaa - xxxxxxxxxxxxxxxx Correct the application, or increase the limit value in
the global definition, if appropriate.
Explanation OC8902 HH:MM:SS WARNING LIMIT
The CICS transaction tttt has exceeded either the EXCEEDED FOR xxxxxxxxxxxxxxxx:
xxxxxxxxxxxxxxxx resource warning threshold or the TRANS=ttttt, TASKNO=nnnnnnnn,
kill threshold, and the transaction was running under USER=UNKNOWN
CEDF. To stop a transaction with abend code RLaa,
specify a KILL limit in the resource limiting definition Explanation
in the global definition member. The xxxxxxxxxxxxxxxx
value is a text string explaining the reason for the The CICS transaction tttt has exceeded the
abend code. These are the abend codes and their xxxxxxxxxxxxxxxx resource warning threshold. The
associated texts: xxxxxxxxxxxxxxxx value is a text string explaining the
reason for the abend code. These are the abend codes
RLAD and their associated texts:
ADABAS requests
RLAD
RLCP
ADABAS requests
CPU time usage

RLCP Thexxxxxxxxxxxxxxxx value is a text string explaining
CPU time usage the reason for the abend code. These are the abend
RLCT codes and their associated texts:
Container HWM RLAD
RLDB ADABAS requests
DB2 requests RLCP
RLDC CPU time usage
DATACOM requests RLCT
RLDL Container HWM
DL/I requests RLDB
RLDS DB2 requests
DSA HWM storage RLDC
RLED DATACOM requests
EDSA HWM storage RLDL
RLEL DL/I requests
elapsed time RLDS
RLFC DSA HWM storage
file requests RLED
RLGD EDSA HWM storage
GDSA HWM storage RLEL
RLID elapsed time
IDMS requests RLFC
RLMQ file requests
MQ requests RLGD
RLSU GDSA HWM storage
SUPRA requests RLID
RLU1 IDMS requests
USREVNT1 requests RLMQ
MQ requests
System action RLSU
SUPRA requests
Prior to issuing the message, RLIM stops the exceeded
threshold to prevent the reissuing of identical RLU1
messages. All remaining thresholds are kept intact and USREVNT1 requests
active. The transaction reverts to normal processing.
System action
User response Prior to issuing the message, RLIM stops the exceeded
Correct the application, or increase the limit value in threshold to prevent the reissuing of identical
the global definition, if appropriate. messages. All remaining thresholds are kept intact and
active. The transaction is abended.
OC8903 HH:MM:SS ABEND “RLaa” ISSUED
DUE TO xxxxxxxxxxxxxxxx:
TRANS= ttttt, TASKNO=nnnnnnnn, User response
USER=UNKNOWN Correct the application, or increase the limit value in
the global definition, if appropriate.
Explanation
The CICS transaction tttt has exceeded
the xxxxxxxxxxxxxxxx resource kill threshold.

Chapter 29. CI0410-LSCX messages
The CI0410-LSCX message group documents the messages issued by these IBM Tivoli components:
OMEGAMON Subsystem, CSA Analyser, DEXAN and SAS/C.
CI0410 INVALID COMMAND - ENTER ‘?’ Explanation
FOR LIST
A STOP command was entered without specifying an
ID.
Explanation
The command you entered is not an Interface System action
command.
OMEGAMON ignores the command.
System action
User response
Enter the command, specifying the correct ID.
User response CI0414 MISSING TASK TYPE TO START
Enter a proper Interface command.

Explanation
CI0411 PARM MEMBER NAME MISSING
A START command was entered without specifying a
task, such as KOBCICS or OMVTAM.
Explanation
An EXEC command was issued but the member name System action
was omitted.
System action
User response
Enter the command, specifying the correct task.
User response CI0415 EXPECTED TASKID MISSING -

REENTER
Enter the command, specifying the correct member
name.
Explanation
CI0412 ‘ID=’ MISSING - REENTER
A common interface command requiring a task ID was
entered without the task ID.
Explanation
A STOP command was issued but did not specify an System action
ID, or had the wrong MODIFY ID to stop a subtask.
System action
User response
Re-enter the command, specifying the task ID.
User response CI0416 ‘=’ MISSING - REENTER
Enter the command, specifying the correct ID.

Explanation
CI0413 TASK ID TO STOP OR MODIFY
MISSING - REENTER A parameter that requires a value was entered with the
value omitted, for example:
START KOBCICS,ROWS,COLS=80,...
rather than

START KOBCICS,ROWS=24,COLS=80,... CI0420 SYSTEM ID MISSING - REENTER
Explanation
System action
A common interface start command with a SYS
OMEGAMON ignores the command. keyword was issued without the required system ID.

Enter the command with an = and a value after the OMEGAMON ignores the command.
parameter name.
CI0417 CUU ADDRESS MISSING - User response
REENTER
Enter the command with a system ID.
Explanation CI0421 SYSTEM MODE MISSING -
REENTER
A common interface start command with a unit
keyword was issued without the required unit address.
Explanation
System action A common interface start command with a MODE
keyword was issued without the required ID.
System action
User response
Re-enter the command with a unit address.
CI0418 VALUE MISSING - OR INVALID User response
Re-enter the command with a system mode.
Explanation
CI0425 YES OR NO REQUIRED - REENTER
A parameter requires a valid value which was not
supplied.
Explanation
System action YES or NO was not specified in a parameter where it is
required.
System action
User response
Enter the command, specifying a valid value.
CI0419 USER DATA NAME MISSING - User response
REENTER
Enter the command, specifying YES or NO.
Explanation CI0510 ATTACH PROCESSING - TASK
ID=cccccccc
A common interface start command with a user
keyword was issued without the required user module
suffix. Explanation
A common interface EXEC or START command has
System action initiated a process to start a new task. The task
identifier is the cccccccc value.
System action
User response
Attach processing continues.
Re-enter the command with a user module suffix.

User response CI0533 REQUESTED LOAD MODULE NOT
FOUND - cccccccc
None. This message is informational only.
CI0530 DUPLICATE TASK ID - TASK NOT Explanation
STARTED
Module cccccccc was not found in a JOB, STEP, or LPA
library.
Explanation
This message follows the CI0510 message. It System action
indicates that a task with the identifier named in the
CI0510 message is already active. The ID associated Attach processing stops.
with a common interface task must be unique.
User response
System action Place a copy of the appropriate module in a JOB, STEP,
Attach processing for the new task stops. or LPA library. An IPL with CLPA is required for LPA
library placement to activate the module.
User response CI0534 ATTACH FAILED FOR TASK
cccccccc
Add the ID keyword to the task’s START command, or
stop the processing task and start the new task again.
Explanation
CI0531 ID=cccccccc PROGRAM=aaaaaaaa
This message follows CI0510. Attach processing failed
for the cccccccc task.
Explanation
The common interface also issued the CI0530 System action
message. This message displays the task ID (cccccccc)
and program name (aaaaaaaa) associated with the Attach processing for the new task stops.
CI0530 message.
User response
None. CI0535 DUPLICATE ID - TASK NOT
STARTED
User response
Use this task ID (cccccccc) to STOP the task. Explanation
CI0532 TASK AREA NOT AVAILABLE - An attempt was made to start a task with an ID
TASK NOT STARTED identical to that of another task already running under
Explanation
System action
This message follows the CI0510 message. It
indicates that memory is not available to build a work The new task does not start.
area needed by the common interface to start a new
task. User response
Enter the command with a unique task ID.
System action
CI0536 ID=cccccccc PROGRAM=aaaaaaaa
Attach processing for the new task stops.
Explanation
User response
The common interface also issued message CI0535.
If the problem persists, restart the common interface This message displays the task ID (cccccccc) and
with a larger REGION size, or eliminate any currently program name (aaaaaaaa) associated with message
executing tasks that are no longer needed. CI0535.
Chapter 29. CI0410-LSCX messages 445

System action CI0544 JSCB BUILD FAILED - TASK NOT
STARTED
The new task does not start.
Explanation
User response
This message follows the CI0510 message. A JSCB
Re-enter the command with a unique task ID. control block needed by the common interface to start
CI0537 Common Interface - UNABLE TO a new task could not be built.
OBTAIN TASK AREA
System action
Explanation Attach processing for the new task stops.
There is insufficient storage for the Interface to obtain
a work area for the starting task. User response
Check the system console for related error messages
System action and contact IBM Software Support.
OMEGAMON ignores the common interface start CI0545 CSCB BUILD FAILED - TASK NOT
command. STARTED

Check for error messages on the system console that This message follows CI0510. A CSCB control block
might provide a reason for the failure. Once the source needed by the common interface to start a new task
of the storage constraint is corrected, retry the START could not be built.
command. If this problem persists, increase the region
size.
System action
CI0542 STOP ID NOT FOUND
Attach processing for the new task stops.
Explanation
User response
The STOP command specified an ID that is not active.
Check the system console for related error messages
and contact IBM Software Support.
System action
CI0546 GETMAIN FAILED FOR SP230
Processing stops. PARAMETER WORK AREA

Use the DISPLAY or LIST command to display the The common interface was unable to acquire a
active task IDs. parameter work area in subpool 230 that is used by
CI0543 THE FOLLOWING TASK IDS ARE subtasks attached with a system key specification.
ACTIVE:
System action
Explanation The subtask creation request is ignored.
The DISPLAY or LIST command shows which tasks are
active. User response
System action
CI0550 TASK BUSY - MODIFY MESSAGE
None. NOT SENT TO TASK
User response
None. This is an informational message only.

Explanation Note that the common interface only uses dynamic
allocation for the response time collector SNAP file in
A request was made to the common interface to issue the absence of a DSNAPDD data definition statement.
an MVS modify command to a subtask, but the subtask
is not currently accepting modify commands.
System action
System action The response time collector SNAP debugging file does
not allocate or open.
OMEGAMON ignores the modify request.
User response
User response
The error, reason, and return codes in this message are
Retry the command. described in the IBM MVS Job Management Manual.
CI0551 MODIFY MESSAGE SENT TO TASK Correct the source of the error message and retry the
allocation. Alternatively, a DSNAPDD data definition
statement can be included in the common interface
Explanation JCL stream, thereby avoiding the need to use dynamic
The common interface honored a MODIFY command. allocation.
CI0560 RKANPAR DATASET OPEN ERROR
System action
The common interface issues the modify command to Explanation
the subtask. The rhilev.RKANPAR dataset could not be opened.

None. This is an informational message only. EXEC processing stops.
CI0552 TASK TO MODIFY NOT FOUND
User response
Explanation Check that the RKANPAR DD statement is in the
A request was made to the common interface to issue JCL for this region. Check that the dataset has the
a modify command to a subtask whose ID (specified proper attributes (see the installation documentation).
in the MODIFY command) cannot be found among the Contact IBM Software Support for assistance.
currently active sub tasks. CI0561 INVALID LRECL OF RKANPAR -
NOT LRECL=80
System action
OMEGAMON ignores the modify request. Explanation
The rhilev.RKANPAR dataset does not have an LRECL
User response of 80.
Use the LIST command to determine which tasks are
active to the common interface. Correct the task ID System action
and reissue the MODIFY command. EXEC processing stops.
CI0553 DYNAMIC ALLOCATION FOR SNAP
FILE FAILED, ERROR=aaaaa, User response
REASON=bbbbb, RI5=ccccc.
Check and correct the LRECL of the rhilev.TOBDATA
dataset.
Explanation
CI0562 MEMBER NOT FOUND IN DATASET
When the DSNAPON command is presented to the
common interface, it attempts to dynamically allocate
the response time collector SNAP debugging file.
Should an error occur during the allocation process,
this message is displayed and shows the error
codes returned by the supervisor allocation routines.

A member name was specified in the EXEC command, Check that the EXEC members do not cause EXEC
but that member does not exist in the rhilev.RKANPAR loops. Reorganize the commands to be executed to
dataset. fewer than ten members total.
CI0567 KEY VALUE OUT OF RANGE, MUST
System action BE 0–7
EXEC processing stops.
Explanation
User response The KEY= keyword may only specify keys 0–7. Key 8
Check the member name entered and enter the is used by V=V problem programs and keys 9–15 are
correct name. reserved for V=R problem programs.
CI0563 ERROR OBTAINING A BUFFER FOR

System action
READING RKANPAR
OMEGAMON ignores the request.
Explanation
User response
The common interface was unable to obtain an I/O
buffer for reading the rhilev.RKANPAR dataset. This is Specify a valid KEY= keyword value.
probably the result of a severe storage shortage in the
CI0580 *** NO TASKS ARE ACTIVE ***
system.

OMEGAMON issues this message in response to a
DISPLAY or LIST command when no tasks are active.
User response
System action
Try the command later when storage use lessens.
None.
Increase the region size if this condition persists.
CI0564 ERROR OBTAINING AN INPUT User response
AREA FOR RECORD
Explanation CI0585 ERROR READING RKANPAR
MEMBER - SYNAD MESSAGE:
The command processor could not obtain an input cell
for a record from the rhilev.RKANPAR dataset. EXEC
processing stops. Explanation
A system error occurred while processing a member
User response of the hilev.RKANPAR dataset. A SYNAD message
follows.
Try the command later when core use lessens.
Increase the region size if this condition persists.
System action
CI0565 EXEC LIMIT EXCEEDED
Explanation
User response
You reached the limit of ten EXEC members to
be processed per command invocation. This limit Check the SYNAD message for cause of the error.
prevents a possible loop in the EXEC process where
CI0586 FREEMAIN FAILED FOR SP230
member A EXECs B and member B EXECs A.
PARAMETER WORK AREA
FOLLOWING ATTACH FAILURE
System action

The common interface was unable to freemain the None. This is an informational message only.
parameter work area in subpool 230 that is used by
CI0593 TASK ID=XXXXXXXX HAS BEEN
subtasks attached with a system key specification.
STOPPED VIA DETACH (STAE=YES)
This occurred after the subtask attach attempt failed.

None. The common interface processed a STOP command
where the DETACH=Y parameter was specified.
User response
System action
The common interface detaches the subtask which
CI0587 FAILURE TO FREE CSCB may result in an ABEND 33E.

The command scheduling control block used by tasks None. This is an informational message only.
that run under the common interface could not be
unallocated. CI0594 ID=cccccccc PROGRAM=aaaaaaaa

The CSCB storage, if any, is not freed. The common interface also issued message CI0592.
This message displays the task ID (cccccccc) and
program name (aaaaaaaa) associated with message
User response CI0592.
System action
CI0588 FAILURE TO FREE JSCB
None.
Explanation
User response
The job step control block acquired by the common
interface on behalf of one of its subtasks could not be None. This is an informational message only.
released.
CI0603 SYMBOL NOT DEFINED: cccccccccc
System action
Explanation
The JSCB storage, if any, is not freed.
The symbol displayed is not known to the command
processor.
User response
None. This is an informational message only. System action
CI0592 TASK ID=XXXXXXXX HAS BEEN Command processing stops.
STOPPED VIA POST
User response
Explanation
Check the input for spelling.
The common interface honored a STOP command.
CI0604 AMBIGUOUS SYMBOL: ccccccccccc
System action
Explanation
The common interface requests the subtask to stop.
The symbol entered cannot be uniquely identified.

Command processing stops. The parser had an error trying to free an input
command cell.
User response
System action
Spell out the command operand more fully.
Processing stops.
CI0605 INVALID INPUT VALUE:
User response
Explanation
Contact IBM Software Support for assistance.
The input value received is not valid for the symbol.
CI0609 ERROR IN FREE POOL ROUTINE
System action
Explanation
The parser had an error trying to free the input
User response command pool.
Check to see if the value is correct or specify it

System action
differently, for example, as 43 instead of 0043 in
number of ROWS on the terminal screen. Processing stops.
CI0606 EXPECTED CONTINUATION NOT
RECEIVED User response
Explanation
CI0700 OMEGAMON Common Interface
An input statement had a continuation indication READY FOR COMMANDS
but was the last statement input to the command
processor. Explanation
The Interface enters a WAIT state to wait for
System action
commands to process.
This command processing stops.
System action
User response
The Interface waits.
Add a continuation statement or remove the
continuation indicator. User response
CI0607 EXPECTED INPUT NOT RECEIVED The Interface is now ready to accept commands via
MODIFY.
Explanation
CI0715 MODIFY IGNORED
A command is expecting some input options but they
were not specified (for example, ROWS=). Explanation
The Interface is not in a state where it accepts the
System action
MODIFY command.
System action
User response
Specify the required options.
CI0608 ERROR IN FREE CELL ROUTINE User response
Reissue the command.

CI0720 PROCESS MESSAGES FOLLOW Explanation
The subtask specified by the task ID (cccccccc)
Explanation and program name (aaaaaaaa) is scheduled for
Informational and error messages generated during termination because of a suspected looping condition.
command processing follow. This message accompanies CI0723.

None. Processing continues.

None. This is an informational message only. This is an informational message only. See
accompanying message CI0723.
CI0722 SUBTASK LOOP IDENTIFICATION
AND ANALYSIS IN PROGRESS CI0725 ZERO POINTER TO CIB FOUND
The common interface detected a looping condition in An unexpected condition occurred and an abend may
one of its subtasks. result.

The common interface attempts to identify the looping Processing tries to continue.
subtask. The common interface will not accept
any commands while task-level loop checking is in User response
progress.
If an abend occurs, let the Interface retry. Contact IBM
Software Support for assistance.
User response
Determine why the subtask was looping. Correct the AND ANALYSIS COMPLETED
problem and restart the subtask. SUCCESSFULLY
CI0723 LOOPING Common Interface
SUBTASK SCHEDULED FOR Explanation
TERMINATION
The common interface completed its analysis of
subtask CPU utilization. Commands will now be
Explanation accepted normally.
The common interface identified a looping subtask
and scheduled it for termination. Message CI0724 System action
accompanies this one.
None.
System action
User response
OMEGAMON forcibly detaches the looping subtask and
generates a SNAP dump (ddname: SNAPFILE). None. This is an informational message only.
User response AND ANALYSIS TERMINATED
WITHOUT RESOLUTION
See accompanying message CI0724 for the name and
ID of the looping program. Examine the SNAP dump
to determine why the subtask was looping. Correct the Explanation
problem and restart the subtask. If necessary, contact The common interface terminated its analysis of
IBM Software Support with the dump information. subtask CPU utilization. This occurred because a
CI0724 ID=cccccccc PROGRAM=aaaaaaaa subtask terminated (normally or abnormally), or the

common interface was unable to isolate the errant CI0734 FREE INPUT POOL CRITICAL
subtask. ERROR

None. Command processing is complete but the Interface
was unable to release the input message pool.
User response
System action
Command processing continues.
CI0730 TERMINATION REQUEST
ACKNOWLEDGED
User response
Explanation Contact IBM Software Support for assistance.
The common interface acknowledges the user stop CI0735 KOBCIIPn LOAD ERROR
command.
Explanation
System action
The common interface was unable to load the parser
The common interface begins termination processing. and command processing routines. n is an operating
system identifier from 1–4.
User response
System action
The common interface stops the command.
CI0731 COMMAND PARSE COMPLETED
WITH CRITICAL ERRORS
User response
Explanation Make sure KOBCIIPn is in a load library accessible to
The parsing of the command results in a failure of the
parser. CI0736 FREE MESSAGE CELL CRITICAL
ERROR
System action
Explanation
Command processing is complete but the Interface is
User response unable to release the output message cell.
Contact IBM Software Support for assistance and have

a copy of the input available.
System action
Command processing continues.
CI0732 FREE INPUT CELL CRITICAL
ERROR
User response
Explanation Contact IBM Software Support for assistance.
Command processing is complete but the Interface is CI0738 FREE MESSAGE POOL CRITICAL
unable to release the input message cell. ERROR

Processing continues. Command processing is complete but the Interface is
unable to release the output message pool.
User response

Command processing continues. An attach of a common interface subtask failed.

Contact IBM Software Support for assistance. None.
CI0740 UNABLE TO OBTAIN STORAGE FOR
COMMAND User response
Check for messages on the system console, and
common interface is unable to obtain the storage CI0759 TASK-LEVEL LOOP CHECKING IN
required to process a command. PROGRESS

None. The common interface is monitoring individual
subtasks for excessive CPU utilization. No commands
User response will be accepted while task-level loop checking is in
progress.
Increase the region available to the common interface.
CI0741 PROCESS GET CELL ERROR: CMD System action
IGNORED OMEGAMON ignores the request.

The Interface is unable to get an input command cell Retry the request after task-level loop checking has
in which to place the command to process. completed.
System action CI0760 PROCESSING COMMAND

Explanation
User response The processing of the command entered using the
MODIFY begins.
The lack of available virtual storage may cause the
error. Reissue the command when storage usage
System action
lessens. If the problem persists, increase the region
size. Contact IBM Software Support for assistance. Command processing starts.
CI0750 MESSAGES PRIOR TO ERROR
User response
After an error is detected and retry started, the CI0762 FREE MESSAGE CELL CRITICAL
messages that resulted appear. ERROR

None. Cleanup routine after an error is unable to free up
message cells.
User response
System action
Note which processes completed. Contact IBM
Software Support for assistance. Cleanup continues.
CI0756 ATTACH FAILED

Contact IBM Software Support for assistance. Contact IBM Software Support for assistance.
CI0764 FREE MESSAGE POOL CRITICAL CI0787 FAILURE TO FREE CSCB
ERROR
Explanation
Explanation
This message indicates either an internal error or
Cleanup routine after an error is unable to free up storage corruption.
message pool.
System action
System action
The subtask termination cleanup continues.
Cleanup continues.
User response
User response
Contact IBM Software Support for a problem
Contact IBM Software Support for assistance. number and instructions for forwarding the following
documentation: a log of the debug screen space
CI0770 INPUT AT TIME OF ERROR **
sequence and any dumps produced by the common
interface address space or related TSO address space.
Explanation
CI0788 FAILURE TO FREE JSCB
OMEGAMON displays the command processing at the
time of the error.
Explanation
System action This message indicates either an internal error or
storage corruption.
Cleanup continues.
System action
User response
The subtask termination cleanup continues.
CI0772 FREE MESSAGE CELL CRITICAL User response
ERROR Follow the instructions given in the Preface, then
Explanation
CI0789 FREEMAIN FAILED FOR
The input message cells could not be freed. SP230 PARAMETER WORK
AREA FOLLOWING SUBTASK
System action TERMINATION
Cleanup continues.
Explanation
User response The common interface was unable to freemain the
parameter work area in subpool 230 that is used by
Contact IBM Software Support for assistance. subtasks attached with a system key specification.
This occurred after the subtask terminated normally
CI0774 FREE MESSAGE POOL CRITICAL
or abnormally.
ERROR

None.
The input message pool could not be freed.

Cleanup continues.

CI0798 INVALID RETURN FROM System action
TERMINATION CALL
The common interface stops.
Explanation
User response
Internal error. This message should be accompanied
by abend U798. Contact IBM Software Support.
CI0931 SUBTASK ERROR RECOVERY
System action DETECTED INVALID ISDA
The common interface abnormally stops.

Explanation
User response This error is caused either by an internal error or by the
corruption of virtual storage.
Follow the instructions given in the Preface, then
System action
CI0799 UNABLE TO LOCATE RECOVERY
HEADER The subtask stops.

Internal error. This message should be accompanied Follow the instructions given in the Preface, then
by abend U799. contact IBM Software Support.
CI0935 RETRY FROM Interface A ERROR
System action RECOVERY

Explanation
User response Interface D abnormally terminated and control has
passed back to Interface A.
System action
CI0900 Common Interface
INITIALIZATION System action is dependent on the response made to
message CI0995, which always immediately follows
this message.
Explanation
The common interface is beginning initialization. User response
Respond to message CI0995.
System action
CI0938 ERROR ENCOUNTERED
Initialization continues. ATTEMPTING TO SERIALIZE NON-
SWAPPABILITY
User response
None. This is an informational message only. Explanation
CI0901 GLOBAL ADDRESS SPACE VECTOR The common interface was unable to successfully
TABLE BUILD FAILED enqueue upon a step-level resource used to regulate
non swapability.
Explanation
System action
The GETMAIN for the LSQA to hold the vector table
failed. The common interface stops.
User response

CI0940 MODULE KOBCIIDn NOT FOUND System action
Interface retries, or termination of the common
Explanation interface, depending on the response to the message.
The common interface could not find module
KOBCIIDn. n is an operating system identifier from 1– User response
4.
A response of GO retries initiation of the Interface.
Precede this response with corrective action to
System action address the cause of the problem, such as placing a
The common interface does not initialize. new, good copy of a program in a library. The STOP
response stops processing the common interface. The
HELP response produces an explanatory message and
User response reissues the WTOR.
Verify that KOBCIIDn is installed in the common CI0960 ENVIRONMENT MISMATCH,
interface’s JOBLIB/STEPLIB, and restart the common SYSTEM MUST BE MVS/SP 1.3 OR
interface. HIGHER
CI0941 LINK FAILED - Interface D
Explanation
Explanation The common interface was started in an operating
The link to OBCIID was unsuccessful. system that does not support its functions.

The common interface stops. The common interface does not initialize.

Check the JES job log for messages. The most None. This is an informational message only.
Common reason for this failure is that OBCIID is not CI0961 ENVIRONMENT MISMATCH, 370
available from the STEPLIB of the common interface. VERSION IN XA, OR XA VERSION
CI0951 PLACE MODULE cccccccc IN A IN 370
JOB/STEP/LPA LIBRARY
Explanation
Explanation The common interface was started in an incompatible
An error (that was logged in a message preceding this operating system.
one) is caused by the absence of the indicated module.
System action
System action The common interface does not initialize.
It depends on the error logged in the previous
message. User response
Verify that the correct version of the common interface
User response is installed.
Respond as indicated in the previous message. CI0968 Common Interface REQUIRES
CI0952 REPLY GO, STOP (TERMINATES APF-AUTHORIZATION
Common Interface OPERATION),
OR HELP Explanation
The common interface determined that it did not
Explanation possess APF authorization.
See System Action and User Response.

The common interface stops with a U0968 abend. This message follows CI0970 when a subtask abend
occurs, and identifies the program that was given
User response control when the subtask was started.
Make sure the common interface load modules reside

System action
in an APF-authorized library.
The subtask abnormally stops.
CI0969 Common Interface MUST EXECUTE
AS PRIMARY NON-SYSTEM JOB
STEP TASK User response
Restart the failing subtask.
Explanation
CI0985 SUBTASK ID=XXXXXXXX
The common interface must run as the primary FORCIBLY DETACHED
non-system job step task in the address space.
Typically, this requirement is satisfied when the Explanation
common interface is attached by IEESB605 (started
task control) when run as a started task, or by IEFIIC A common interface module (KOBCIRT0) detected
(initiator Interface control) when run as a batch job. that a subtask of the common interface was detached
The common interface is not designed to run in a by its mother task while the subtask was still active.
TSO environment under the TMP (terminal monitor
program). System action
None.
System action
The common interface stops. User response
This may or may not be an error. If the subtask’s
User response
mother task was requested to stop, then no error
Contact IBM Software Support. occurred.
CI0970 OMEGAMON SUBTASK CI0995 Interface A ERROR RECOVERY
ABEND CODE=cccccccc RETRY - ENTER ‘GO’, ‘STOP’, OR
PSW=aaaaaaaaaaaaaaaa ‘HELP’
TCB=bbbbbbbb
Explanation
Explanation
The common interface has abended and requests a
A subtask of the common interface abended. This response from the operator.
message displays the abend code, the PSW at time
of abend, and the address of the abending task’s TCB System action
display.
The Interface restarts or the common interface stops,
depending on the response to the message.
System action
The subtask produces a system termination dump. User response
User response
CI0997 INVALID RETURN FROM
CI0971 PROGRAM NAME=cccccccc TERMINATION CALL
Explanation
by abend U997.

System action CNDL002I CANDLE SUBSYSTEM V999
TERMINATED - SSID = cccc
Explanation
User response
The Candle subsystem address space termination
Follow the instructions given in the Preface, then processing has completed. The subsystem version
contact IBM Software Support. number is “999”, and the MVS subsystem identifier is
CI0998 UNABLE TO LOCATE RECOVERY the cccc value.
HEADER
System action
Explanation The Candle subsystem address space stops.
by abend U998. User response
System action
CNDL003A CANDLE SUBSYSTEM
The common interface abnormally stops. INITIALIZATION FAILED - REGION
TOO SMALL
User response
Follow the instructions given in the Preface, then Explanation
contact IBM Software Support. The Candle subsystem address space could not obtain
CI0999 LOAD OF OBCIGL FAILED enough private-area storage to complete initialization.

The common interface was unable to load the global The Candle subsystem address space stops.
address space vector table service routine.
User response
System action Increase the REGION specification included in the
The common interface stops. address space start-up JCL.
CNDL004A CANDLE SUBSYSTEM REQUIRES
User response APF AUTHORIZATION
Make sure OBCIGL is in a load library accessible to the
common interface. Explanation
CNDL001I Candle Subsystem V999” The Candle subsystem address space must execute
INITIALIZATION - SSID = cccc from an APF-authorized library.

Candle subsystem address space initialization The Candle subsystem address space stops.
processing has begun. The subsystem version number
is “999”, and the MVS subsystem identifier is cccc. User response
APF-authorize the Candle subsystem’s load library.
System action
CNDL005A CANDLE SUBSYSTEM RECEIVED
Candle subsystem processing continues. CONTROL IN AN AUTHORIZED
KEY
User response

The Candle subsystem address space received control The SSCVT chain entry at storage location X’xxxxxxxx’
in execution key 0–7. The Subsystem must be installed is not formatted correctly. During initialization, the
to receive control in a non-authorized key. Only APF- subsystem found the invalid entry while looking for
authorization is required. its own SSCVT entry. The Subsystem cannot complete
initializing without its SSCVT entry.
System action
System action
The Candle subsystem address space stops.
The subsystem address space stops.
User response
User response
Use the correct procedure to install the Candle
subsystem. Correct the cause of the SSCVT entry formatting error
and correct the entry.
CNDL006A cccccccc KEYWORD VALUE
INVALID CNDL010A CANDLE SUBSYSTEM IS NOT
DEFINED - SSID = cccc
Explanation
Explanation
The value of the cccccccc keyword is not valid.
The subsystem identifier cccc has not been defined
System action as an MVS subsystem. The identifier must be defined
to MVS during Subsystem installation. A system IPL is
The request associated with the keyword is rejected. required before the new definition becomes effective.
The nature of the request determines the action taken.
For example, if a subsystem start parameter is found
System action
in error, the Subsystem address space stops. If an
operator command keyword is in error, the command The subsystem address space stops.
is rejected.
User response
User response
Review the subsystem installation procedures. Verify
Correct the keyword specification. that subsystem definition statements have been
added to the appropriate IEFSSNcc member in
CNDL007A cccccccc KEYWORD OCCURS SYS1.PARMLIB.
MULTIPLE TIMES
CNDL013I CANDLE SUBSYSTEM INITIALIZED
Explanation WITH “RESTART=FORCE”
The cccccccc keyword occurs multiple times in a single

Explanation
Subsystem request.
The subsystem address space start parameter
System action included the keyword RESTART=FORCE. This keyword
causes Subsystem initialization to continue even
The request associated with the keyword is rejected. if another subsystem address space is active.
The nature of the request determines the action taken. RESTART=FORCE should not be used unless repeated
For example, if a subsystem start parameter is found attempts to start the Subsystem result in message
multiple times, the Subsystem address space stops. CNDL018I and it is known that no other subsystem
If an operator command keyword is found multiple address space is active.
times, the command is rejected.
System action
User response
The subsystem address space remains active.
Correct the keyword specification.
CNDL009I SSCVT CHAIN ENTRY INVALID - User response
ADDRESS X’xxxxxxxx’ None. This message is informational only.

CNDL014A SUBSYSTEM INITIALIZATION the value of the REGION parameter for the subsystem
MODULE KCNDLINT DID NOT RUN address space.
SUCCESSFULLY
CNDL020A START PARAMETER STRING
SYNTAX ERROR
Explanation
The subsystem initialization module KCNDLINT did not Explanation
run successfully during the system IPL.
The syntax of the parameter string passed to the
subsystem during initialization is in error.
System action
The subsystem address space stops. System action
The subsystem address space stops.
User response
An IPL is needed to complete the installation of the User response
subsystem. If an IPL was done, check the SYSLOG
Correct the parameter string error and restart the
for messages to determine why KCNDLINT did not
subsystem address space.
execute. Make sure you complete all subsystem
installation steps and perform an IPL before starting CNDL021I RKANPAR FILE OPEN ERROR - RC
the subsystem address space. = X’xxxxxxxx’.
CNDL018I CANDLE SUBSYSTEM ALREADY
ACTIVE - nnnnnnnn iiiiiiii Explanation
The RKANPAR file failed to open. The error code
Explanation returned by IBM OPEN processing was X’xxxxxxxx’.
The address space producing this message has
determined that the subsystem address space is System action
already active. The name of the already-active address
space is nnnnnnnn; its address space identifier is iiiiiiii.
Depending on the severity of the error, additional
subsystem messages may appear.
System action
The address space producing this message stops. User response
Check the console for any additional Subsystem or
User response IBM-component messages. If the error’s cause cannot
be determined, contact IBM Software Support.
CNDL022I RKANPAR FILE FAILED TO OPEN
CNDL019W CONDITIONAL STORAGE REQUEST
FAILED - cccccccc
Explanation
Explanation The RKANPAR file failed to open. There was no error
code returned by IBM OPEN processing.
The subsystem has attempted and failed to obtain
private-area storage. The name of the requesting
routine is cccccccc. System action
System action Depending on the severity of the error, additional
subsystem messages may appear.

Check the console for any additional Subsystem or
No immediate action is necessary. However, other
IBM-component messages. If the cause of the error
messages requiring specific action may appear as a
cannot be determined, contact IBM Software Support.
result of the failed storage request. If this message
appears frequently, it may be necessary to increase

CNDL024I cccccccc MEMBER mmmmmmmm System action
NOT FOUND
Explanation
User response
The mmmmmmmm PDS member could not be found.
The ddname associated with the PDS is cccccccc. None. This message is informational only.
CNDL034I SUBSYSTEM START MEMBER

Explanation
User response The RKANPAR member cccccccc was used as the
subsystem initialization member during subsystem
Verify that the PDS member name was specified startup.
correctly and retry the subsystem request.
CNDL027I FUNCTION cccccccc STARTED System action
Explanation
Function cccccccc has been started by the subsystem. User response
The function is now available for use by other IBM
products. None. This message is informational only.
CNDL100I I/O SERVICES NOT AVAILABLE
System action
The subsystem address space remains active. Explanation
An error has occurred causing the termination
User response of the dynamic I/O configuration subsystem. This
message should be accompanied by another message
None. This message is informational only. explaining the error.
CNDL030I FUNCTION cccccccc STOPPED
System action
Explanation The routine stops.
Function cccccccc has been stopped by a user request.
The function is no longer available for use by other User response
IBM products.
Follow the response for the accompanying message.
Contact IBM Software Support if necessary.
System action
CNDL101A UNABLE TO OBTAIN PRIVATE
The subsystem address space remains active. STORAGE, DYNAMIC I/O
SERVICES NOT AVAILABLE
User response
None. This message is informational only. Explanation
CNDL032I FUNCTION cccccccc STOPPED BY The dynamic I/O configuration monitor initialization
THE SUBSYSTEM routine was unable to obtain private area storage for
its work area.
Explanation
System action
Function cccccccc has been stopped by the subsystem.
The function is no longer available for use by The routine stops without initializing dynamic I/O
other IBM products. The subsystem has stopped the monitoring.
function as a result of an error or Subsystem address
space termination.

Contact IBM Software Support. The routine attempts to recover from the abend. If
more than one abend has occurred, then the routine
CNDL102A DSPSERV RC = X’xx’ REASON
will terminate.
CODE = yyyyyyyy
User response
Explanation
Retain the dump. Contact IBM Software Support.
The dynamic I/O configuration monitor initialization
routine was unable to create a SCOPE=COMMON CNDL105I DYNAMIC I/O CONFIGURATION
dataspace for its use. The return code from the UNABLE TO OBTAIN CSA STORAGE
DSPSERV macro invocation was X’xx’, the reason code
was yyyyyyyy. Explanation
An attempt to obtain CSA failed.
System action
The routine stops without initializing dynamic I/O System action
monitoring.
The dynamic I/O configuration monitor will function
without I/O configuration change exits.
User response
Check the return codes for the DSPSERV macro User response
create function to determine if the failure was due
to an installation option. If not, contact IBM Software Contact IBM Software Support.
Support.
CNDL106W UNABLE TO INSTALL I/O
CNDL103A ALESERV RC = X’xx’ RECONFIGURATION COMPLETION
EXIT, RC=X’xx’
Explanation
Explanation
The dynamic I/O configuration monitor initialization
routine was unable to add an entry for a An attempt to install an I/O reconfiguration completion
SCOPE=COMMON data space to all PASN-ALs in the exit failed with return code X’xx’.
system. The return code from the ALESERV macro
invocation was X’xx’. System action
The dynamic I/O configuration monitor will function
System action
without the I/O configuration completion exit.
The routine stops without initializing dynamic I/O
monitoring. User response
User response
CNDL107W UNABLE TO INSTALL I/O
Check the return codes for the ALESERV macro
RECONFIGURATION REQUEST
add function to determine if the failure was due to
EXIT, RC=X’xx’
an installation option. If not, contact IBM Software
Support.
Explanation
CNDL104I SVC DUMP TAKEN FOR DYNAMIC
I/O CONFIGURATION SUBSYSTEM An attempt to install an I/O reconfiguration request
exit failed with return code X’xx’.
Explanation
System action
An abend has occurred and an SVC dump has been
successfully produced. The dynamic I/O configuration monitor will function
without the I/O configuration request exit.

Contact IBM Software Support. The dynamic I/O configuration exit stops.
CNDL108A UNABLE TO BUILD UCB TABLE, RC
= X’xx’ User response
Explanation
CNDL151A INVALID ALET, UNABLE TO
An attempt to build a table of UCB addresses failed ACCESS DATA SPACE, DYNAMIC
with return code X’xx’. I/O RECONFIGURATION EXIT
INOPERATIVE
System action
Explanation
The dynamic I/O configuration monitor will terminate.
The ALET for the SCOPE=COMMON data space has
User response been found to be invalid.

System action
CNDL109A UCBSCAN RETURN CODE = X’xx’
The dynamic I/O configuration exit stops.

An invocation of the UCBSCAN macro service failed Contact IBM Software Support.
with return code X’xx’.
CNDL152A INVALID DATA SPACE, DYNAMIC
System action I/O RECONFIGURATION EXIT
INOPERATIVE
The dynamic I/O configuration monitor will terminate.
Explanation
User response
The ALET for the SCOPE=COMMON data space has
Contact IBM Software Support. accessed a data space that can not be validated.
CNDL110A UCB TABLE REBUILD FAILED
WITH RC = X’xx’ System action
Explanation
An attempt to rebuild the UCB address table failed User response
with return code X’xx’. Contact IBM Software Support.
System action CNDL153A UNEXPECTED FUNCTION

ENCOUNTERED BY I/O REQUEST
The dynamic I/O configuration monitor will terminate. EXIT

Contact IBM Software Support. The dynamic I/O configuration request exit has
encountered an unknown function code.
CNDL150A UNABLE TO OBTAIN STORAGE,
DYNAMIC I/O RECONFIGURATION
EXIT INOPERATIVE System action
Explanation
An I/O reconfiguration exit attempted to obtain private User response
storage and failed. Contact IBM Software Support.

CNDL154A I/O aaaaaaaaaa EXIT UNABLE Explanation
TO ACCESS DATA SPACE IN
RECOVERY ROUTINE. An abend has caused entry to the recovery routine
and an SVC dump was produced. The aaaaaaaa value
identifies the exit as either request or completion.
Explanation
An abend has caused entry to the recovery routine, System action
and the data space cannot be accessed to notify
potential users that the exit has abended. aaaaaaaa The dynamic I/O configuration exit stops.
identifies the exit as either request or completion.
User response
System action Retain the SVC dump. Contact IBM Software Support.
The dynamic I/O configuration exit stops. CNDL175W UNABLE TO OBTAIN
PRIVATE STORAGE, SUBSYSTEM
User response INITIALIZATION ROUTINE
TERMINATING
CNDL155A I/O aaaaaaaaaa EXIT ALET Explanation
INVALID
The subsystem initialization KCNDLINT routine cannot
obtain working storage.
Explanation
An abend has caused entry to the recovery routine and System action
the data space cannot be accessed to notify potential
users that the exit has abended due to an invalid The routine stops without performing any functions.
ALET. aaaaaaaa identifies the exit as either request
or completion. User response
System action
CNDL176W UNABLE TO ESTABLISH
The dynamic I/O configuration exit stops. RECOVERY, SUBSYSTEM
INITIALIZATION ROUTINE
User response TERMINATING

Explanation
CNDL156A I/O aaaaaaaaaa EXIT UNABLE
TO ACCESS WORK AREA IN The subsystem initialization KCNDLINT routine cannot
RECOVERY ROUTINE establish a recovery environment.

An abend has caused entry to the recovery routine The routine stops without performing any functions.
and the exit work area cannot be accessed. The
aaaaaaaa value identifies the exit as either request User response
or completion.
System action CNDL177W aaaa SUBSYSTEM UNABLE TO

OBTAIN ECSA STORAGE RC=X’xx’
Explanation
User response
The subsystem initialization KCNDLINT routine cannot
Contact IBM Software Support. obtain ECSA storage for subsystem aaaa.
CNDL157I SVC DUMP TAKEN FOR I/O aaaa
aaaaaaaaaa ROUTINE name of the subsystem

X’xx’ User response
return code from the STORAGE macro
Correct the parameter string in the appropriate
IEFSSNcc member of SYS1.PARMLIB.
System action
CNDL180A aaaa SUBSYSTEM INPUT
The routine stops without obtaining or formatting the PARAMETER bbbbbbbb OCCURS
control block anchor for the subsystem. MULTIPLE TIMES

If you cannot address the problem indicated by the The subsystem initialization routine KCNDLINT found
return code, contact IBM Software Support. a keyword parameter to have been entered more
CNDL178W aaaa SUBSYSTEM UNABLE than once in the input parameters obtained from the
TO START ADDRESS SPACE IEFSSNcc member of SYS1.PARMLIB.
bbbbbbbb, RETURN DATA = xxyy aaaa
name of the subsystem.
Explanation bbbbbbbb
keyword parameter occurring multiple times.
The subsystem initialization KCNDLINT routine failed
to start the subsystem address space.
aaaa
System action
name of the subsystem The routine stops without starting the subsystem
bbbbbbbb address space.
name of the procedure specified by the SSPROC
keyword User response
X’xx’ Correct the parameter string in the appropriate
return code from the ASCRE macro IEFSSNcc member of SYS1.PARMLIB.
yy
reason code from the ASCRE macro CNDL181I SVC DUMP TAKEN FOR CANDLE
SUBSYSTEM aaaa
System action
Explanation
The routine stops without starting the subsystem
address space. The subsystem initialization KCNDLINT routine
abended and an SVC dump was produced to gather
diagnostic information. aaaa is the name of the
User response subsystem.
If the return information does not indicate an
installation addressable problem, contact IBM System action
Software Support.
The routine stops.
CNDL179A INVALID PARAMETER STRING FOR
SUBSYSTEM aaaa
User response
Explanation Retain the dump and contact IBM Software Support.
The subsystem initialization routine KCNDLINT routine CNDL182A CANDLE SUBSYSTEM aaaa, VALUE
found a syntax error in the parameter string passed to FOR KEYWORD SSPROC IS
it using the IEFSSNcc member of SYS1.PARMLIB. aaaa INVALID
is the name of the subsystem.
Explanation
System action The subsystem initialization KCNDLINT routine has
The routine stops without starting the subsystem determined that the value coded for keyword SSPROC
address space. in the IEFSSNcc member of SYS1.PARMLIB is invalid.
aaaa is the name of the subsystem.

The routine stops without attempting to start the The initialization routine specified in the IEFSSNcc
Candle subsystem address space. member of SYS1.PARMLIB for subsystem aaaa has
successfully recovered from an abend. aaaa is the
User response name of the subsystem.
Start the subsystem address space manually, or

System action
correct the appropriate member of SYS1.PARMLIB and
re-IPL. The initialization routine stops cleanly and returns
control to the system.
CNDL183A CANDLE SUBSYSTEM aaaa, VALUE
FOR RKANPAR KEYWORD MUST
BE 2 BYTES LONG User response
None. This message is informational only. However,
Explanation there should be other messages which will require
action.
The subsystem initialization routine KCNDLINT has
determined that the value coded for keyword CNDL189W SUBSYSTEM ADDRESS SPACE
RKANPAR in the IEFSSNcc member of SYS1.PARMLIB INITIALIZATION ROUTINE
is not 2 bytes long. aaaa is the name of the VALIDATION FAILURE
subsystem.
Explanation
System action
The subsystem routine that runs during subsystem
The routine stops without attempting to start the address space initialization did not complete
Candle subsystem address space. successfully.

Start the subsystem address space manually, or The subsystem address space continues processing;
correct the appropriate member of SYS1.PARMLIB and however, the console operator command D A,L will not
re-IPL. display the subsystem address space as an active job
on the system. To display the job, you must use the
CNDL184I CANDLE SUBSYSTEM aaaa command D A,ssssssss, where ssssssss is the name of
INITIALIZATION ROUTINE the subsystem started task.
COMPLETED
User response
Explanation
Gather SYSLOG and possible SVC dump information,
The initialization routine specified in the IEFSSNcc and contact IBM Software Support.
member of SYS1.PARMLIB for subsystem aaaa has
completed successfully. aaaa is the name of the CS075 UNABLE TO ESTABLISH VIRTUAL
subsystem. SESSION FOR sid. MAKE SURE
THE SPECIFIED APPLICATION
System action IS AVAILABLE AND A VALID
LOGMODE IS BEING USED.
The routine has successfully completed without error.
Explanation
User response
An attempt was made to establish a session using the
None. This message is informational only. identified session ID, but the attempt failed.
CNDL185I CANDLE SUBSYSTEM aaaa
INITIALIZATION ROUTINE System action
RECOVERY SUCCESSFUL None.

Follow the message instructions. The input parameters for the CSAA subsystem ended
before expected.
CSAA000I CSAA SUBSYSTEM
INITIALIZATION IN PROGRESS
System action
Explanation The CSAA subsystem stops.
The CSA Analyzer (CSAA) subsystem initialization
started. User response
Check the input parameters for proper syntax.
System action
CSAA210E INPUT PARAMETER SYNTAX
Initialization processing continues. ERROR AT POSITION xx

None. CSAA detected an error at the specified position of the
input parameter.
CSAA001I CSAA SUBSYSTEM
INITIALIZATION COMPLETED
SUCCESSFULLY System action
The CSAA subsystem stops.
Explanation
The CSAA subsystem initialization processing User response
completed successfully. Check the input parameters for proper syntax.
CSAA299E CSAA SUBSYSTEM TERMINATING
System action
DUE TO PARAMETER ERROR.
The CSAA subsystem is ready to capture and report
common storage usage. Explanation
CSAA detected an error in the input parameter.
User response
None. System action
CSAA100E CSAA SUBSYSTEM ALREADY The CSAA subsystem stops.
RUNNING
User response
Explanation
Check the input parameters for proper syntax; then
The CSAA subsystem was already running when this restart the CSAA subsystem.
CSAA subsystem address space tried to initialize. Only
one CSAA subsystem address space can be active at a CSAA300E UNABLE TO LOAD CSAA MODULE
time. cccccccc, ABEND=xxxx RC=yyyy

The second CSAA subsystem address space stops. The CSA Analyzer™ could not load the specified CSAA
module cccccccc into virtual storage.
User response
System action
Stop the CSAA subsystem before starting another
CSAA subsystem. The CSAA subsystem stops.
CSAA200E PREMATURE END OF INPUT
PARAMETERS

Ensure that the CSA Analyzer can access the CSAA Job trend processing routine encountered an error.
load modules through LPALST, LINKLST, JOBLIB or
STEPLIB concatenation. System action
CSAA320E UNABLE TO ATTACH CONSOLE The CSAA subsystem stops.
COMMUNICATION TASK
User response
Explanation
Call IBM Software Support.
The CSA Analyzer could not attach the console
communication subtask. CSAA350E UNABLE TO START ORPHAN
PROCESSING TIMER
System action
Explanation
The orphan processing routine timer could not be
started.
User response
Ensure that the CSA Analyzer can access the System action
KCSCOMM load module through LPALST, LINKLST,
JOBLIB or STEPLIB concatenation. The CSAA subsystem stops.
CSAA330E UNABLE TO ATTACH SYSTEM
TREND TASK User response
Explanation
CSAA351E ORPHAN PROCESSING ERROR
The CSA Analyzer could not attach the system trend
subtask. Explanation
Orphan processing routine encountered an error.
System action
The CSAA subsystem stops. System action
User response
Ensure that the CSA Analyzer can access the KCSSTRN User response
load module through LPALST, LINKLST, JOBLIB or
STEPLIB concatenation. Call IBM Software Support.
CSAA340E UNABLE TO START JOB TREND CSAA352E UPDATE PROCESSING ERROR;

TIMER CSAA SUBSYSTEM SUSPENDED
The CSA Analyzer could not start the job trend timer. The CSA Analyzer has experienced an error while
processing.
System action
System action
The CSAA subsystem is suspended from collecting
new data and a system dump is produced.
User response
Call IBM Software Support. User response
CSAA341E JOB TREND PROCESSING ERROR Save the system dump and SYSLOG and contact IBM
Software Support for assistance.

CSAA399E UNABLE TO LOCATE AND/OR LOAD System action
ALL MODULES
Explanation
User response
During CSAA initialization, the CSA Analyzer could not
locate or load one or more CSAA load modules into The CSA Analyzer cannot co-exist with some common
virtual storage. storage monitors from other vendors. Call IBM
Software Support.
System action CSAA730E CSAA EXTRACTOR IN ERROR,

EXTRACTOR REMOVED
Explanation
User response
The CSAA data extraction routine encountered an
Ensure that the CSA Analyzer can access the CSAA error. The CSA Analyzer removes the extraction routine
load modules through LPALST, LINKLST, JOBLIB or from the system.
STEPLIB concatenation.
CSAA700E SSCVT CHAIN IS INVALID, System action
UNABLE TO ADD CSAA SSCVT
Explanation
User response
The CSA Analyzer encountered an error while trying to
add the CSAA SSCVT dynamically to the SSCVT chain. Call IBM Software Support.
CSAA740E UNABLE TO LOCATE THE DATA
System action BUFFER

Explanation
User response The CSA Analyzer could not locate the CSAA extraction
routine’s data buffer.
Define the CSAA subsystem in the
SYS1.PARMLIB(IEFSSNxx) and IPL the system.
System action
CSAA710E UNABLE TO ESTABLISH ERROR
RECOVERY ENVIRONMENT The CSAA subsystem stops.

The CSA Analyzer could not establish the CSAA Call IBM Software Support.
subsystem error recovery environment. CSAA800E UNABLE TO OBTAIN FIXED ECSA
STORAGE FOR SSCVT
System action
The CSAA subsystem stops. Explanation
The CSA Analyzer could not obtain storage for the
User response CSAA SSCVT from extended CSA.

System action
CSAA720E UNABLE TO INSTALL THE
EXTRACTOR The CSAA subsystem stops.

The CSA Analyzer could not install its extraction Check if all of extended CSA is in use. If not call IBM
routine. Software Support.

CSAA801E UNABLE TO OBTAIN FIXED ECSA System action
STORAGE FOR CSAAVT
Explanation
User response
The CSA Analyzer could not obtain storage for the
CSAA vector table from extended CSA. Call IBM Software Support.
CSAA810E UNABLE TO OBTAIN PAGABLE
System action ECSA STORAGE

Explanation
User response The CSA Analyzer could not obtain storage for the
CSAA data areas from extended CSA.
Check if all of extended CSA is in use. If not call IBM
Software Support.
System action
CSAA802E UNABLE TO OBTAIN FIXED ECSA
STORAGE FOR CACHE BUFFER The CSAA subsystem stops.

The CSA Analyzer could not obtain storage for the Check if all of extended CSA is in use. If not call IBM
cache buffer from extended CSA. Software Support.
CSAA811E UNABLE TO OBTAIN DATA
System action ELEMENT STORAGE IN PAGABLE
ECSA
Explanation
User response
The CSA Analyzer could not obtain storage for the data
Check if all of extended CSA is in use. If not call IBM elements from extended CSA.
Software Support.
CSAA804E UNABLE TO OBTAIN FIXED ECSA System action
STORAGE FOR DATA BUFFER
Explanation
User response
The CSA Analyzer could not obtain storage for the data
buffer from extended CSA. Increase the value for the PAGE= parameter. If the
problem persists, call IBM Software Support.
System action CSAA820E UNABLE TO OBTAIN EXTENDED

PRIVATE STORAGE
Explanation
User response
The CSA Analyzer could not obtain extended private
Check if all of extended CSA is in use. If not call IBM storage.
Software Support.
CSAA805E UNABLE TO OBTAIN ESQA System action
STORAGE FOR SRB
Explanation
User response
The CSA Analyzer was unable to obtain storage for an
SRB. Increase the region size for the CSAA address space. If
the problem persists, call IBM Software Support.

CSAA850I MONITORING ACTIVE FOR aaa/ Explanation
aaaa
The CSAA program pppppppp is at version vvvvvvvv.
The current maintenance level is mmmmmmmm.
Explanation
The CSA Analyzer found that the MVS Common System action
Storage Tracking function has been enabled and
monitoring is now active for the indicated Common This diagnostic message may be issued with other
Storage Areas. The possible values for aaa/aaaa are CSAA messages.
• CSA/ECSA - Common Service Area and Extended

Common Service Area
User response
• SQA/ESQA - System Queue Area and Extended See other CSAA messages for further information. This
System Queue Area diagnostic message may provide useful information in
determining current maintenance level.
System action CSAA860E MVS COMMON STORAGE
TRACKING LEVEL NOT
The CSAA subsystem is available to report on common SUPPORTED - nnnn
storage usage.
Explanation
User response
The CSA Analyzer found that the MVS Common
None. Storage Tracking function is at LEVEL nnnn, a level
CSAA851I MONITORING INACTIVE FOR aaa/ that is not supported due to maintenance or release
aaaa level. The MVS Common Storage Tracking function is at
LEVEL nnnn. All common storage usage information is
unavailable.
Explanation
The CSA Analyzer found that the MVS Common System action
Storage Tracking function has been disabled and
common storage usage information is unavailable for The CSAA subsystem address space stops.
the indicated Common Storage Areas. The possible
values for aaa/aaaa are: User response
• CSA/ECSA - Common Service Area and Extended Contact IBM Software Support.
Common Service Area
CSAA861E FAILURE DETECTED IN MVS
• SQA/ESQA - System Queue Area and Extended
COMMON STORAGE TRACKING
System Queue Area
Explanation
System action
The CSA Analyzer found that the MVS Common
The indicated common storage area will not be
Storage Tracking function has been disabled due
reported on.
to internal problems with the IBM virtual storage
management component. All common storage usage
User response information is unavailable.
Enable the MVS Common Storage Tracking function.
See the MVS Initialization and Tuning Reference for System action
further information on enabling the MVS Common
The CSAA subsystem address space stops.
Storage Tracking function.
CSAA852I PROGRAM - pppppppp VERSION User response
- vvvvvvvv MAINTENANCE -
mmmmmmmm Contact your system programmer. If an SVC dump
was produced by the CSAA address space, this
may provide additional diagnostics for IBM support
personnel.

CSAA890E USE THE STOP COMMAND User response
TO TERMINATE THE CSAA
SUBSYSTEM Ensure that all CSAA load modules are of the same
version. Check the LPALST and LINKLST concatenation
for duplicate modules. If the problem cannot be
Explanation resolved, call IBM Software Support.
The CSA Analyzer has experienced an error, described CSAA901E CSAA SUBSYSTEM VERSION DOES
by a previous message. The MVS STOP command NOT MATCH KCSEXTR VERSION
should be issued to stop the CSAA address space.
Explanation
System action
The CSAA subsystem version does not match the
The CSAA subsystem is suspended from collecting extraction routine version.
new data.
System action
User response
Examine the CSAA message which appears before this
message in the SYSLOG; it will describe the reason the
CSAA has been suspended. OMEGAMON commands User response
may be used before the CSAA is stopped to examine Ensure that all CSAA load modules are of the same
the current CSAA data. The MVS STOP command version. Check the LPALST and LINKLST concatenation
should then be issued to stop the CSAA address space. for duplicate modules. If the problem cannot be
The MVS START command can then be issued to resolved, call IBM Software Support.
restart the CSAA address space.
CSAA902E CSAA SUBSYSTEM VERSION DOES
CSAA899E CSAA SUBSYSTEM TERMINATED NOT MATCH KCSMGR VERSION
DUE TO INSUFFICIENT STORAGE
Explanation
Explanation
The CSAA subsystem version does not match the
The CSA Analyzer could not obtain the storage CSAA manager version.
required by the CSAA subsystem. The accompanying
CSAA8xxE message identifies the type of storage that
could not be obtained. System action
System action
The CSAA subsystem terminated. User response
Ensure that all CSAA load modules are of the same
User response version. Check the LPALST and LINKLST concatenation
for duplicate modules. If the problem can not be
Follow the directions in the accompanying CSAA8xxE resolved, call IBM Software Support
messages.
CSAA910W CSAA via WILL EXPIRE ON
CSAA900E CSAA SUBSYSTEM VERSION DOES mm/dd/yy
NOT MATCH KCSEXTR VERSION
Explanation
Explanation
This message indicates the expiration date of the
The CSAA subsystem version does not match the CSAA product. It displays each time you start the
initialization routine version. CSAA subsystem, 30 days prior to the actual expiration
date.
System action
The CSAA subsystem stops. System action

Call IBM Software Support. None.
CSAA911E CSAA vvvv HAS EXPIRED, CALL DX0000 Vvvv running. Cycles= cccSTIM=ii
IBM CORPORATION Elap=ss SEC (or mm:ss MN)
The specified version of the CSAA expired. You have issued BEGN to start the DEXAN collector
(version vvv). STIM (sample time) shows the sample
System action interval (i.i) in seconds and tenths. Cycles (ccc) shows
how long (in STIM intervals) the collector has been
The CSAA subsystem is terminated. running. Elap shows the total elapsed collection time
in seconds (ss) or minutes and seconds (mm:ss).
User response
System action
Call IBM Corporation to order the latest version of the
CSA Analyzer. None.
CSAA997E CSAA SUBSYSTEM ABNORMAL
TERMINATION User response
None.
Explanation
DX0001 Collector has not been started
The CSAA subsystem encountered an error and stops
abnormally.
Explanation
System action You have issued the DEX command, but have not
started the DEXAN data collector.
System action
User response
None.
CSAA998I CSAA STOP COMMAND ACCEPTED User response
Issue the BEGN command to start the collector.
Explanation
DX0002 Collector being suspended
The CSAA subsystem accepted the stop command.
Explanation
System action
You have suspended data collection without losing any
The CSAA subsystem stops. data that DEXAN has already collected.

None. None.
CSAA999I CSAA SUBSYSTEM TERMINATION
IN PROGRESS User response
None.
Explanation
DX0003 Collector being resumed
The CSAA subsystem is terminating.
Explanation
System action
You have resumed data collection after suspending it.

None. You have requested that DEXAN remove a job or
address space (STC name or TSO user ID) from job
User response analysis.
None.
System action
DX0004 Collector suspended since None.
hh:mm:ss Cycles=nnn Elap=mm:ss
MN
User response
Explanation None.
You suspended data collection by issuing the SUSP DX1060 Deletion pending
command. If you want to resume data collection, issue
the RESM command. Cycles (nnn) shows how long (in Explanation
sample intervals) the collector has been running. Elap
shows the total elapsed collection time in minutes and After requesting that DEXAN remove a job or address
seconds. space (STC name or TSO user ID) from job analysis,
you have tried to display that job while the collector is
still monitoring it.
System action
None. System action
None.
User response
None. User response
DX1000 The data collector started None.
Workarea size= nnnnnn bytes.
(Also displays, for MVS SP4 or DX1100 DEXAN to support up to nnn
later, either) Collector monitoring address space analyses
devices defined as dynamic (or)
Collector not monitoring latest I/O Explanation
configuration
You have specified a maximum of nnn address spaces
for DEXAN analysis.
Explanation
You have started data collection. DEXAN has allocated System action
nnnnnn bytes of storage for its collector tables. For
MVS SP4 or later, the collector can gather data from None.
dynamic I/O devices that your site has defined to the
subsystem. User response
None.
System action
DX1200 Collector to monitor period 1 of up
None.
to nnn performance groups

None.
You have specified a maximum of nnn performance
DX1050 Entry will be deleted groups for DEXAN period one monitoring.
System action
None.

None. None.
DX1300 Collector to collect data on up to
nnn performance groups User response
None.
Explanation
DX1700 No active entries
You have specified a maximum of nnn performance
groups for DEXAN monitoring. Explanation
You have not selected any job, address space (STC
System action
name or TSO user ID), or DEXAN slot number, for
None. DEXAN analysis.

None. None.
DX1500 Collection has not yet started
User response
Explanation None.
One of the following entities is not yet available for DX1800 Entry added
DEXAN analysis:
• a job Explanation
• an address space (STC name or TSO user ID) You have selected a job, address space (STC name
• the period one performance groups or TSO user ID), or DEXAN slot number, for DEXAN
analysis.
When the entity becomes active, DEXAN will start to
analyze it.
System action
System action None.
None.
User response
User response None.
None. DX1900 COMMAND NOT APPLICABLE IN

GOAL MODE
DX1600 Collection started hhhh, elap=ss,
items=nn
Explanation
Explanation The system is currently running in Work Load Manager
goal mode and the entered command is a compatibility
DEXAN has started to analyze one of the following mode oriented command and therefore not applicable
entities that has become active: to goal mode. Generally, DEXAN does not support
• a job Workload Manager goal mode.
• an address space (STC name or TSO user ID)
• the period one performance groups
System action
The command stops completely.
DEXAN started data collection at hhhh hours.
Collection has been running for ss seconds or
mm:ss minutes and seconds. DEXAN has made nn User response
observations. Elap shows the total elapsed collection
None.
time in seconds (ss) or minutes and seconds (mm:ss)

DX2000 Command valid only when System action
collector not running
None.
Explanation
User response
You have issued a command that is not valid while the
collector is running. After stopping the collector, specify a larger maximum
by using one of the following commands:
System action • NUMAnnn for more address spaces

• NUMFnnn for more period one performance groups
None.
• NUMPnnn for more performance groups
User response For more information, see the OMEGAMON Command
Language Reference Manual.
Either stop the collector or issue a command that is
valid while the collector is running. DX2050 Period one monitoring inactive
DX2010 Entry busy; retry later
Explanation
Explanation You have set NUMF to zero.
You have tried to delete from analysis a job or address
space (STC name or TSO user ID) for which DEXAN is System action
processing an earlier request. None.

None. None.
DX2060 Entry inactive
User response
Try deleting the job or address space later. Explanation
DX2020 Entry already exists in table You have tried to display a job in a job table for which
no job has been selected.
Explanation
You have tried to select a job or address space (STC System action
name or TSO user ID) that DEXAN is already analyzing. None.

None. None.
DX2065 Performance group not selected
User response
for collection
Select a different job or address space.
DX2040 No room in table to add entry Explanation
You have tried to display or plot wait reasons for a
Explanation performance group that DEXAN has not selected for
data collection.
You have tried to select a new address space (STC
name or TSO user ID) for analysis while DEXAN is
already monitoring its maximum specified number of System action
address spaces. None.

Use the PONnnnn command to force DEXAN to None.
select a performance group for collection. Collection
starts at the next interval. If you want collection to User response
start immediately, issue the CLR command. For more
information, see OMEGAMON Command Language Enter a non-zero operand.
Reference Manual.
DX2110 Operand must be numeric
DX2070 Address space monitoring inactive
Explanation
Explanation
You have entered a non-numeric operand.
You have set NUMA to zero.
System action
System action
None.
None.
User response
User response
Enter a numeric operand.
None.
DX2120 Operand must be “on,” “off,” or
DX2080 Valid range for period one entry “null”
number is 1 thru nn
Explanation
Explanation
You have entered an operand that is not on, off, or null.
You have tried to display a period one table entry that
is greater than NUMF. System action
None.
System action
None. User response
Enter an on, off, or null operand.
User response
DX3000 Collection counters will be cleared
Plot a valid performance group.
DX2090 Valid range for address space Explanation
entry is 1 thru nn
You have requested that DEXAN clear its data
collection counters.
Explanation
You have tried to display a period one table entry that System action
is greater than NUMA.
None.
System action
User response
None.
None.
User response DX3001 The collection counter for aaa is
now on
Plot a valid job.
DX2100 Value cannot be 0 Explanation
You have added a collection counter to the displayed
Explanation
list of collection counters.
You have tried to enter zero where DEXAN prohibits it.

None. You have disabled enqueue wait collection.

None. None.
DX3002 The collection counter for aaa is
now off User response
None.
Explanation
DX4002 Value must be between 0 and 10
You have removed a collection counter from the
displayed list of collection counters. Explanation
You cannot specify taking enqueue samples less often
System action
than every 10 sampling cycles.
None.
System action
User response
None.
None.
DX3003 Invalid counter ID (see BLST help User response
for valid IDs) Enter an nn value between 1 and 10.
DX4100 Reserve data collection disabled/
Explanation
enabled
You have used an invalid collection counter ID while
trying to add a counter to or remove a counter from the Explanation
displayed list of collection counters.
You have enabled or disabled reserve data collection
on a pre-SP2 system.
System action
None. System action
None.
User response
Use a valid collection counter ID. For more User response
information, see the OMEGAMON Command Language
Reference Manual. None.
DX4000 Enqueue data collection enabled, DX5000 Offset table cccccccc loaded
CYCLE= nn
Explanation
Explanation
You have loaded JES2 offset table cccccccc.
You have enabled enqueue wait collection to take
samples every nn cycles. System action
None.
System action
None. User response
None.
User response
DX5001 Offset table cccccccc has invalid
None.
format
DX4001 Enqueue data collection disabled

You have tried to load a JES2 offset table that has an None.
invalid format.
User response
System action
None.
None.
DX5200 JES2 analysis active, offset table –
cccccccc
User response
Use the J2LD command to load an offset table that Explanation
has a valid format. For more information, see the
OMEGAMON Command Language Reference Manual. You have requested JES2 service status while it is on.
DX5002 Offset table cccccccc initialization System action

failed
None.
Explanation
User response
You have loaded a JES2 offset table that could not
initialize. None.
DX5201 JES2 analysis inactive
System action
None. Explanation
You have turned off JES2 analysis.
User response
Use the J2LD command to load an offset table that can System action
initialize. For more information, see the OMEGAMON
None.
Command Language Reference Manual.
DX5003 Offset table cccccccc not available User response
None.
Explanation
DX6001 Performance groups for forced
You have tried to load a JES2 offset table that has not
selection
been installed at your site.

DEXAN will start analyzing the displayed performance
None.
groups at the next collection interval.
User response
System action
Install the JES2 offset table at your site, then use
None.
the J2LD command to load that offset table. For more
Reference Manual. User response
DX5100 JES2 service analysis active None.
suppressed
DX6002 Performance groups for forced
rejection
Explanation
You have turned off JES2 service analysis. Explanation
DEXAN will not analyze the displayed performance
groups at the next collection interval.

None. None.
DX6006 Forced selections exceed available
User response entries
None.
Explanation
DX6003 Performance groups for first
period forced rejection You have not defined enough table space for all period
one performance groups that you have identified for
Explanation analysis.
DEXAN will not analyze the displayed period one

System action
performance groups at the next collection interval.
None.
System action
User response
None.
Use the NUMFnnn command to specify a larger
User response maximum number of period one performance groups.
For more information, see the OMEGAMON Command
None. Language Reference Manual.
DX6004 Performance groups for first DX6007 Forced selections exceed available
period forced selection entries
DEXAN will start analyzing the displayed period one You have not defined enough table space for all
performance groups at the next collection interval. performance groups that you have identified for
analysis.
System action
System action
None.
None.
User response
User response
None.
Use the NUMPnnn command to specify a larger
DX6005 Performance groups for inclusion
maximum number of performance groups. For more
in cross-system table
Reference Manual.
Explanation
DX6100 Performance groups selected:
You have displayed a list of performance groups for
forced inclusion in the cross-system table by doing
Explanation
either of the following:
This is the list of performance groups that DEXAN is
• adding a performance group to the cross-system
monitoring currently.
table
• removing a performance group from the cross-
system table System action
None.
System action
None. User response
None.

DX6101 Performance groups for inclusion System action
in cross-system table
None.
Explanation
User response
This is the list of performance groups that appear in
the XPG display. None.
DX7003 Collection counters will be cleared
System action at every RMF interval
None.
Explanation
User response You have synchronized the DEXAN data collector clear
interval with the RMF interval.
None.
DX7000 Collection counter clearing System action
interval is every nnn minutes
None.
Explanation
User response
You have displayed the DEXAN data collector clear
interval. None.
DX7004 No clearing interval in effect
System action
None. Explanation
You have tried to reset the DEXAN data collector clear
User response interval without first turning off the synchronization
between the DEXAN data collector clear interval and
None. the RMF interval.
DX7001 Sync with RMF collection is turned
on System action
None.
Explanation
You have synchronized the DEXAN data collector clear User response
interval with the RMF™ interval.
None.
System action DX7100 The data collector sample time =

n.n
None.
Explanation
User response
You have done either of the following:
None.
• displayed the current DEXAN data collector sample
DX7002 Sync with RMF collection is turned time
off
• reset the DEXAN data collector sample time

You have turned off the synchronization between the
None.
DEXAN data collector clear interval and the RMF
interval, and reset the DEXAN data collector clear
interval to 30 minutes. User response
None.

DX7200 Plot percentage threshold is n % System action
None.
Explanation
The DEXAN plot percentage threshold limits plot User response
output to the most important wait reasons. You have
done either of the following: None.
• displayed the current threshold DX9005 Request ignored — collector has

terminated. Completion code =
• reset the threshold cxxx

None. You have tried to suspend or resume data collection
after DEXAN has failed.
User response
None. System action
DX9000 Collector has terminated. None.
Completion code = cxxx
User response
Explanation None.
The collector has failed. DX9800 Collector has not abended (ABND)

None. You can issue ABND only after DEXAN has abended.

Issue ABND to log the problem, then issue END and None.
BEGN to restart DEXAN.
DX9002 Request ignored — suspend User response
operation pending
For more information, see the OMEGAMON Command
Language Reference Manual.
Explanation
DX9999 The data collector ended
You have tried to suspend or resume data collection
after DEXAN has already suspended data collection.
Explanation
System action You have stopped DEXAN data collection.
None.
System action
User response None.
None.
User response
DX9003 Request ignored — resume
operation pending None.
IA0001 INVALID DELIMITER
Explanation
You have tried to resume or suspend data collection Explanation
while DEXAN is already waiting to resume data The IANL command was entered with incorrect syntax.
collection.

The command is commented out. The command is commented out.

Correct the syntax error and enter the command again. Correct the syntax error and enter the command again.
IA0002 WORKLOAD NAME MUST BE 8 IA0005 PERFORMANCE GROUPS MUST BE
CHARACTERS OR LESS SPECIFIED BY NUMBER
A workload name exceeding eight characters was User attempted to select a performance group as a
entered. monitored workload (using the PG=performance group
command) but entered a non-numeric name for the
System action performance group. The performance group must be
specified by number.
The command is commented out.
System action
User response
Command is commented out.
Correct the workload name and enter the command
again.
User response
IA0003 VALID FORMATS ARE: Correct the syntax error and enter the command again.
workload,LIST workload,DELETE
GROUP,LIST IA0006 GROUP NAMES CANNOT BE
NUMERIC
Explanation
Explanation
Review the appropriate explanation for your product.
The user attempted to select a group workload
to be monitored (using the GROUP={Groupname}
The IANL LIST or the DELETE command was
command), but entered a numeric name for the
entered with incorrect syntax.
group. The group workload must be specified by a
All other products nonnumeric name.
User entered an IANL command with incorrect
usage of the comma. Correct syntax is displayed.
System action
System action The command is commented out.

User response
User response Correct the syntax error and enter the command again.
Correct the syntax error and enter the command again. IA0007 VALID FORMAT FOR LIST IS:
cccccccc
IA0004 VALID FORMATS ARE:
GROUP=groupnamePG=nnnn (*
not applicable to IBM Z OMEGAMON
Explanation
for CICS) LIST=ALL The IANL LIST command was entered incorrectly.

An IANL command was entered with incorrect use of The command is commented out and a model of the
the equal sign. The correct syntax is displayed. correct syntax is shown.

Correct the syntax error and enter the command again. The user attempted to select a group workload
to be monitored (using the command IANL
IA0008 FORMAT FOR DEFINING A GROUP GROUP=Groupname), but the group has not been
IS: defined.

GROUP=Groupname=(Member1,Member2,...) The command is ignored.

The user attempted to define a group workload, but Define the group workload using the command
did not use the correct syntax. GROUP=Groupname=(member list) and re-enter the
group selection command.
System action
IA0012 VALID PREFIXES FOR IANL
The command is commented out and a model of the COMMAND ARE: S - Summary level
correct syntax is shown. display D - Detail level display

Correct the syntax error and enter the command again. The IANL command was entered with an invalid prefix.
IA0009 GROUPS CANNOT CONTAIN BOTH
TASK NAMES AND PG NUMBERS System action
Explanation
The user attempted to define a group workload, but User response
mixed task names and PG numbers in the member list. Correct the syntax and enter the command again.
System action IA0013 VALID SUFFIXES FOR IANL

COMMAND ARE: P - Show
The command is commented out. impactors by Performance group
PD - Show impactors by
User response Performance group detailed by job
Correct the syntax error and enter the command again.

Explanation
IA0010 GROUP MEMBER NAMES MUST BE
The IANL command was entered with an invalid suffix.
1 TO 8 CHARACTERS
System action
Explanation
The user attempted to define a group workload, but
entered a member name greater than eight characters.
The correct syntax is: GROUP=Groupname=(member User response
list). Correct the syntax and enter the command again.
System action IA0014 GROUPS MUST CONTAIN AT LEAST

1 MEMBER
Explanation
User response
The user attempted to define a group workload, but
Correct the syntax error and enter the command again. did not include any members in the member list. The
correct syntax is: GROUP=Groupname=(member list).
IA0011 GROUP (name) IS NOT DEFINED

The command is commented out. The command is ignored.

Correct the syntax error and enter the command again. Stop data collection and enter the command again.
IA0015 MAXIMUM NUMBER OF IA0102 ENTRY NOT FOUND
CONTENTION ANALYSES IS 5
Explanation
Explanation
The IANL LIST or DELETE command was entered for a
The user attempted to set the number of workloads to workload that was not being monitored.
be monitored at more than five. The maximum number
of workloads to be monitored is five. System action
The command is ignored and commented out.
System action
The IANC command is rejected and commented out. User response
Correct the workload name and re-enter the
User response
command.
Review the appropriate user response for your
product. IA0103 NO ROOM IN TABLE TO ADD
ENTRY
Enter a number from 1 to 5.
Explanation
All other products
None. The user attempted to start monitoring a workload and
exceeded the maximum number of workloads that can
IA0100 COLLECTOR HAS NOT BEEN be monitored.
STARTED
System action
Explanation
Certain commands require active data collection when
they are issued. Such a command was entered before
data collection was started. User response
Delete a workload from monitoring or increase
System action the maximum number of workloads with the IANC
command.
IA0104 COLLECTOR HAS ABENDED
User response
Explanation
Start data collection and enter the command again.
The collector module has abended, and therefore
IA0101 COMMAND NOT VALID ONCE the workloads under analysis are no longer being
COLLECTOR STARTED monitored.

Certain commands (such as IANQ, which changes the Diagnostic information is displayed.
enqueue sampling interval, and IANC, which sets the
number of workloads that can be monitored) require
that data collection be stopped when they are issued. User response
Such a command was entered while data collection Log the diagnostic information; issue the.MOD
was active. command and log the additional diagnostic
information; exit using the IANL END command;

contact IBM Software Support. For a definition of the System action
user ABEND codes, see the EB, EP, and EU Abend
Codes appendix. The IACL command is rejected.
IA0105 JOB HAS ENDED

User response
Explanation Correct the entry and enter the command again.
Review the appropriate explanation for your product. IA0110 JOB IS NOT A CICS REGION

Impact analysis (OMEGAMON II for DB2) is not Explanation
monitoring the workload because the workload is The monitoring of a job was requested for a region that
no longer running. is not in CICS.
All other products
Monitoring of the workload has stopped because System action
the workload is no longer running.
System action
User response
Enter the command again with a CICS job.
User response IA0111 AT LEAST ONE MEMBER IS NOT A
CICS REGION
None.
IA0107 NO CONTENTION TO REPORT Explanation
The group was monitored, but one or more group
Explanation members may be incorrect.
Review the appropriate explanation for your product.
IBM Z OMEGAMON for CICS System action
OMEGAMON II for DB2 continues to monitor the None.
workload, but not enough contention data has
been collected to form a display.
User response
All other products
Monitoring of the workload is continuing, but not Verify that all group members are correct.
enough contention data has been collected to form
IA0112 INTERNAL ERROR IN CVAL
a display.
ROUTINE

None.
This message is the result of an internal error or the
corruption of virtual storage.
User response
Retry the request later, after enough data has been System action
collected.
OMEGAMON II for DB2 attempts to continue
IA0109 NO MORE THAN 5 SHORT TERM command processing.
INTERVALS PER LONG TERM
INTERVAL User response
Explanation
IA0113 MAXIMUM VALUE IS 10
The user attempted to define the long-term interval
but entered a number larger than five.

The user attempted to set the value of the enqueue Review the appropriate system action for your product.
sampling interval (which is defined by multiples of the
normal sampling interval) but entered a value greater
OMEGAMON II for DB2 processes the command,
than 10. (Such values result in a sampling interval
and comments it out.
that is too infrequent to be significant.) The maximum
number of intervals is 10. All other products
Command is accepted and commented out.
System action
User response
The IANQ command is rejected and commented out.
None.
User response IA0203 LONG TERM DISPLAY WILL
REPRESENT nn SHORT-TERM
Correct the entry and enter the command again.
INTERVALS
IA0200 COLLECTOR HAS ENDED
Explanation
Explanation Informs the user of the long term interval.
The data collector stopped in response to a user
command. System action
The IACL command is accepted and commented out.
System action
Review the appropriate system action for your product. User response
IBM Z OMEGAMON for CICS This is an informational message only.
OMEGAMON II for DB2 processes the command,
and comments it out. IA0204 SHORT TERM DISPLAY WILL BE
All other products CLEARED EVERY nn MINUTES
Explanation
User response Informs the user of the short-term interval.
This is an informational message only.
System action
IA0201 WORKLOAD HAS BEEN ADDED
The IACS command is accepted and commented out.
Explanation
User response
Monitoring of the workload has begun.
System action IA0205 THE DATA COLLECTOR SAMPLE
None. TIME = n.n SECONDS

This is an informational message only. Informs the user of the sampling interval (in seconds).
IA0202 WORKLOAD HAS BEEN DELETED System action

The IAST command is accepted and commented out.
Explanation
The workload has been deleted in response to a user User response
command.

IA0206 PLOT PERCENTAGE THRESHOLD System action
IS nn%
Explanation
User response
Informs the user of the plot threshold. (Contending
workloads comprising less than nn% of the contention This is an informational message only.
will not be displayed). IA0215 NO WORKLOADS UNDER
ANALYSIS
System action
The command is accepted. Explanation
The user entered the IANL LIST=ALL command but
User response all workloads have been deleted from analysis. (The
collector is still running.)
IA0207 IA TO SUPPORT UP TO n System action
CONTENTION ANALYSES
None.
Explanation
User response
Informs the user of the maximum number of
workloads that can be monitored. This is an informational message only.
IA0216 NO GROUPS ARE DEFINED
System action
The IANC command is accepted and commented out. Explanation
The user entered the command IANL GROUP,LIST but
User response no group workloads have been defined. (The collector
is still running.)
IA0208 ENQUEUE DATA COLLECTION System action
ENABLED/DISABLED {CYCLE = nn}
None.
Explanation
User response
Informs the user whether enqueue data collection is
enabled or disabled. If enqueue collection is enabled, Review the appropriate user response for your
the message also shows the frequency with which product.
enqueue data is collected (as a multiple of sampling IBM Z OMEGAMON for CICS
intervals). Define the workloads and restart.
All other products
System action None.
The IANQ command is accepted and commented out. IA0217 IA COLLECTION TASK TIMES OUT
AFTER n MINUTES
User response
Explanation
Informs the user of the current time-out interval. If the
IA0209 GROUP HAS BEEN DEFINED time-out facility has been turned off, the message is IA
COLLECTION TASK WILL NOT TIME OUT.
Explanation
The user successfully defined a group workload. System action
The IATO command is accepted.

None. Review the appropriate system action for your product.
IA0301 PERFORMANCE GROUP IBM Z OMEGAMON for CICS
OPERANDS UNACCEPTABLE IN OMEGAMON II for DB2 processes the command,
GOAL MODE and comments it out.
All other products
Explanation Command is accepted and commented out.
Performance group information is not available under

the Work Load Manager goal mode. User response
None.
System action IA0203 LONG TERM DISPLAY WILL
The command stops. REPRESENT nn SHORT-TERM
INTERVALS
IA0200 COLLECTOR HAS ENDED
Explanation
Explanation
Informs the user of the long term interval.
The data collector stopped in response to a user
command.
System action
System action The IACL command is accepted and commented out.
Review the appropriate system action for your product.

User response
OMEGAMON II for DB2 processes the command, This is an informational message only.
and comments it out. IA0204 SHORT TERM DISPLAY WILL BE
All other products CLEARED EVERY nn MINUTES
Explanation
User response Informs the user of the short-term interval.
IA0201 WORKLOAD HAS BEEN ADDED System action
The IACS command is accepted and commented out.
Explanation
Monitoring of the workload has begun. User response
System action IA0205 THE DATA COLLECTOR SAMPLE
None. TIME = n.n SECONDS

This is an informational message only. Informs the user of the sampling interval (in seconds).
IA0202 WORKLOAD HAS BEEN DELETED

System action
Explanation The IAST command is accepted and commented out.
The workload has been deleted in response to a user

command. User response

IA0206 PLOT PERCENTAGE THRESHOLD System action
IS nn%
Explanation
User response
Informs the user of the plot threshold. (Contending
workloads comprising less than nn% of the contention This is an informational message only.
will not be displayed). IA0215 NO WORKLOADS UNDER
ANALYSIS
System action
The command is accepted. Explanation
The user entered the IANL LIST=ALL command but
User response all workloads have been deleted from analysis. (The
collector is still running.)
IA0207 IA TO SUPPORT UP TO n System action
CONTENTION ANALYSES
None.
Explanation
User response
Informs the user of the maximum number of
workloads that can be monitored. This is an informational message only.
IA0216 NO GROUPS ARE DEFINED
System action
The IANC command is accepted and commented out. Explanation
The user entered the command IANL GROUP,LIST but
User response no group workloads have been defined. (The collector
is still running.)
IA0208 ENQUEUE DATA COLLECTION System action
ENABLED/DISABLED {CYCLE = nn}
None.
Explanation
User response
Informs the user whether enqueue data collection is
enabled or disabled. If enqueue collection is enabled, Review the appropriate user response for your
the message also shows the frequency with which product.
enqueue data is collected (as a multiple of sampling IBM Z OMEGAMON for CICS
intervals). Define the workloads and restart.
All other products
System action None.
The IANQ command is accepted and commented out. IA0217 IA COLLECTION TASK TIMES OUT
AFTER n MINUTES
User response
Explanation
Informs the user of the current time-out interval. If the
IA0209 GROUP HAS BEEN DEFINED time-out facility has been turned off, the message is IA
COLLECTION TASK WILL NOT TIME OUT.
Explanation
The user successfully defined a group workload. System action
The IATO command is accepted.

None. The command does not execute.
IA0301 PERFORMANCE GROUP
OPERANDS UNACCEPTABLE IN User response
GOAL MODE Enter the correct the command.
IN0007 ‘)’ MISSING AFTER FIRST
Explanation
PARAMETER
Performance group information is not available under
the Work Load Manager goal mode. Explanation
A ‘)’ was expected after the first parameter and was
System action
not found.
The command stops.
System action
User response
Enter the correct the command.
IN0004 THE KEYWORD FLAGGED ABOVE User response
IS UNKNOWN Correct the command format and retry.
IN0050 datasetname FAILED TO ALLOCATE
Explanation
A keyword operand was misspelled or is not valid on Explanation
this command.
An error occurred during dynamic allocation of the
dataset name specified in the MLIB DSN list.
System action
The command does not execute. System action
The command continues if there are other dataset
User response
names in the MLIB DSN list.
Enter the correct the command.
IN0005 PARAMETER WAS EXPECTED BUT User response
NOT FOUND Check the reason for the dynamic allocation error
and correct accordingly. Message IN0051 might
Explanation accompany this message.
A keyword with a parameter list was specified, but the IN0051 DAIR CODE = rc
parameter list did not contain enough parameters.
Explanation
System action
The Dynamic Allocation Interface Routine (DAIR)
The command does not execute. return code is displayed.

Enter the correct the command. Same as message IN0050.
IN0006 THIS PARAMETER MUST BE
NUMERIC User response
Same as message IN0050.
Explanation
IN0060 datasetname FAILS MLIB
A parameter was specified which must be numeric but REQUIREMENTS
is not.

The dataset failed the MLIB requirement because The command continues if there are other data set
it neither has a Format 1 DSCB nor is in a load names in the MLIB DSN list.
module format. Message IN0061 or IN0062 gives
more information on the error. User response
Make sure that OMEGAMON is authorized to use the
System action
specified data set.
The command continues if there are other dataset
names in the MLIB DSN list. IN0080 datasetname IS NOT OPEN

Make sure the correct data set name was specified. OMEGAMON tried to close a data set that was not
open.
IN0061 DATASET IS NOT LOAD MODULE
FORMAT System action
CLOSE processing continues for remaining data sets.
Explanation
The MLIB failure was due to the data set not being in a User response
load module format.
Call IBM Software Support for assistance.
System action IN0081 datasetname FAILED TO CLOSE
The command continues if there are other data set
names in the MLIB DSN list. Explanation
The data set cannot be closed.
User response
Only load data sets can be specified on the MLIB System action
command.
CLOSE processing continues for the remaining data
IN0062 FORMAT1 DSCB COULD NOT BE sets.
LOCATED
User response
Explanation
Investigate why the data set failed to close. If
The dataset specified in message IN0060 was not necessary, call IBM Software Support for assistance.
found.
IN0082 datasetname FAILED TO
DEALLOCATE
System action
The command continues if there are other data set Explanation
names in the MLIB DSN list.
The data set cannot be deallocated.
User response
System action
Make sure that the data set exists on the volume
Deallocate processing continues for remaining data
as indicated by the system catalog and retry the
sets.
command.
IN0070 datasetname FAILED TO OPEN User response
Investigate why the data set failed to deallocate by
Explanation
examining the accompanying DAIR code in message
The OPEN failed for the data set. IN0083.
IN0083 DAIR CODE = rc

The Dynamic Allocation Interface Routine (DAIR) None.
return code is displayed with message IN0082.
IN0100 ccccccc HAS A HIGHER PRIORITY
THAN OMEGAMON
System action
See message IN0082. Explanation
The address space dispatching priority of job ccccccc,
User response which is being monitored by INSP, is running at a
Refer to the appropriate IBM manual for a description higher priority than OMEGAMON. This is the jobname
of the return codes. specified by the JOB( ) keyword.
IN0090 ADD AND DEL MUST NOT BE

System action
ISSUED TOGETHER
INSP attempts to take samples, but will probably
Explanation detect very little activity in the monitored address
space. Any results are incorrect.
The ADD and DEL parameters cannot be issued
together in the same MLIB command.
User response
System action Run OMEGAMON as a performance group which
has a higher priority than the address space being
The commands do not execute. monitored.
IN0101 ccccccc IS NO LONGER RUNNING
User response
Issue ADD and DEL separately. Explanation
IN0091 datasetname IS NOT IN THE MLIB INSP was monitoring an address space when the
DSN LIST jobname ccccccc changed. The ccccccc value is the
name specified by the JOB( ) keyword.
Explanation
System action
The data set specified with the delete option of the
MLIB minor of INSP was not found in the MLIB list Sampling stops.
because it was never added or was already deleted.
User response
System action
If you want more data, rerun the job and use a shorter
The operation is ignored. sampling period.
IN0102 START INVALID, ALREADY
User response SAMPLING
Specify the correct data set name for the delete.
Explanation
IN0092 PREVIOUS LINE WAS TRUNCATED
The START keyword was specified on the INSP
Explanation command when sampling of the target address space
was already in progress.
The previous display line has been truncated because
the line length was exceeded.
System action
System action The START keyword is ignored.
None.
User response
None required.

IN0103 STOP INVALID, NOT SAMPLING User response
Record the diagnostic information and call IBM
The STOP keyword was specified on the INSP IN0900 $GMEM FAILED FOR INSP
command when sampling of the target address space WORKAREA
was not in progress.
Explanation
System action
OMEGAMON was unable to obtain memory for the
The STOP keyword is ignored. INSP work area.

None required. The command does not execute.
IN0104 ATTACH FAILED
User response
Explanation Increase the OMEGAMON region size to correct the
This is an internal error message. problem.
IN0901 RETURN CODE rc FROM OMPBM
System action INITIALIZATION
Sampling does not start.

Explanation
User response An error occurred during INSP initialization.
Call IBM Software Support for assistance.

System action
IN0105 ccccccc NOT FOUND
Explanation
User response
No job with the name ccccccc specified is currently
active. The jobname is the name specified by the Call IBM Software Support for assistance.
JOB( ) keyword. IN0902 INSPECT REQUIRES DEXAN

The new jobname specification is not used. To run INSP, the DEXAN® product is required.

Use the JOB( ) keyword to specify the name of a The command does not execute.
running job. If necessary, use OMEGAMON commands
such as ALLJ to determine a valid jobname.
User response
IN0106 SAMPLER TASK HAS ABENDED
None.
Explanation IN0903 LOAD MACRO FAILED FOR OMPBM

WITH ABEND=nnn
This is an internal error message.
Explanation
System action
INSP module OMPBM could not be loaded.
Sampling stops and diagnostic information appears.

The command does not execute. Call IBM Software Support for assistance.
LSCX* (message text varies)
User response
Refer to the IBM system codes manual for an Explanation
explanation of the abend code.
SAS/C generates messages that have LSCX prefixes.
IN0904 INSPECT ERROR CODE nn
System action
Explanation
None.
An internal error occurred on the INSP command. The
error code is nn. User response
System action

Chapter 30. OB0101-OB9269 messages
This information is a listing of the OB0101-OB9269 messages issued by these components:
• DEXAN
• OMNIMON Base
• OMEGAMON for CICS (3270)
OB0101 INVALID FIELD DETECTED, INPUT User response
IGNORED
Restart OMEGAMON in dedicated mode, or do not
attempt to run this command.
Explanation
OB0106 keyword KEYWORD VALUE cc
The cursor was placed on a field which the command INVALID
processor determined to be invalid.
Explanation
System action
The color or highlighting value entered for
Processing continues as determined by the particular the specified keyword is not valid. When
command. the Display=BASIC paramter is used, the valid
keyword values are HI and LO. When the
User response Display=COLORparamter is used, the valid keyword
values are any of the seven color names available on
Make corrections as determined by the particular terminals that support the extended data stream.
command.
OB0102 THIS PRODUCT EXPIRES ON System action
mm/dd/yy
The command execution stops.
Explanation
User response
The current product expires on the date displayed.
Correct the appropriate keyword value and retry.
System action OB0107 MAJOR NOT FOUND
The command execution continues.

Explanation
User response The major command name supplied during a help
request was not found.
Install a new version of OMEGAMON. If you have not
received a new version, contact IBM Software Support.
System action
OB0104 .MFY ONLY WORKS IN DEDICATED
MODE The command execution stops.

The OMEGAMON session is not in the proper mode. Correct the major command name and enter it again.
The .MFY command only works in dedicated mode. OB0108 COMMAND IS NOT A MINOR OF
THIS MAJOR
System action
The command stops. Explanation
The major command name supplied during a help
request exists, but the minor supplied is not valid for
this major.

The command execution stops. The command execution stops.

Correct the minor command name and enter it again. Correct the name and retry the command.
OB0109 MAXIMUM MESSAGE LENGTH IS OB0113 STRING TOO LONG
60 CHARACTERS
Explanation
Explanation
The length of the replacement string set with .VAR can
An attempt has been made to specify an XTXT be no larger than 64 characters.
message greater than 60 characters.
System action
System action
The string is not installed.
The command stops.
User response
User response
Supply a shorter string and retry the command.
Specify the message again using less than 60
characters. OB0114 VARIABLE cccccccc HAS BEEN SET
OB0110 INVALID .VAR OPTION - ccccccc Explanation

The requested variable cccccccc has been updated in
Explanation
the table.
The option ccccccc is unknown to the .VAR command.
System action
System action
The command executes successfully.
User response
User response
Correct the option and retry the command.
OB0115 VARIABLE NAME NOT FOUND IN
OB0111 INVALID VARIABLE NAME - TABLE
cccccccc
Explanation
Explanation
The requested name could not be located.
The name cccccccc contains invalid characters.
System action
System action
The command stops.
User response
User response
Correct the command and retry. To see a list of the
Correct the name and retry the command. values in the table, issue the .VAR command.
OB0112 VARIABLE NAME TOO LONG OB0116 VARIABLE TABLE IS EMPTY
Explanation
The variable name exceeds 8 characters.

The user attempted to list variables with the .VAR Enter the minor command after a major command and
command, however there were no variables in the retry.
table.
OB0121 NO WAIT INDICATED
System action
Explanation
The command stops.
The .WAT command requires a numeric argument. No
numeric argument was supplied.
User response
OB0117 NO ENTRIES FOUND ON STACK Command execution stops.

The .DSE command determined that no stack entries Enter the command, specifying a wait value.
exist.
OB0122 nn SECOND WAIT COMPLETED
System action
Explanation
The .DSE command stops normally and waits for the
next user request. OMEGAMON completed the requested wait.

None. This is an informational message only. Command execution completes normally.
OB0119 VARIABLE NAME IS RESERVED, User response

CANNOT BE SET
Explanation OB0123 NO MINOR COMMAND NAME
The variable name on a .VAR SET operation is GIVEN
reserved. Either the full name as entered is reserved,
or the format is reserved. For example, the exception Explanation
analysis format (ZX....) is reserved.
This command expects you to supply a minor
command name as an argument.
System action
OMEGAMON suppresses the .VAR SET function. System action
The command stops.
User response
Change the variable name to a valid name and enter User response
the command.
Enter a valid minor name.
OB0120 CANNOT LOCATE PREVIOUS
OB0124 MINOR COMMAND NAME TOO
MAJOR COMMAND
LONG
Explanation
Explanation
OMEGAMON could not locate the major command
The user entered a minor command name longer than
associated with this minor command.
4 characters.
System action
OMEGAMON does not execute the minor command.
Chapter 30. OB0101-OB9269 messages 499

The command stops. An invalid relational keyword has been entered. Valid
relational keywords are EQ, LT, LE, NE, GT, GE, and the
User response equal (=) sign.
Correct the entry and retry.

System action
OB0125 NO MAJOR COMMAND HAS A The screen is not fetched.
MINOR WITH THIS NAME
User response
Explanation
Correct the keyword and re-enter it.
The user entered an invalid minor command name.
OB0129 INVALID CONDITIONAL SYNTAX
System action
Explanation
The command stops.
An invalid conditional syntax has been entered. The
User response valid syntax is:
Enter a different minor command. condition relation condition
OB0126 STATUS MODE ccc

System action
Explanation The screen is not fetched.
Status mode has been turned ON or OFF.
User response
System action Correct the keyword and re-enter.
The command executes. OB0130 DEFINITION MODE {ENABLED|
HELD|DISABLED}
User response
OB0127 INVALID LENGTH FOR KEYWORD - OMEGAMON set definition mode to ENABLED, HELD,
cccccccc or DISABLED.

A keyword that is too long has been entered. The The command completes processing.
value cccccccc is the first 8 characters of the keyword
specified with the invalid length. The maximum length User response
for a conditional keyword is 8; the maximum length for
a relational keyword is 2 characters. None. This is an informational message only.
OB0131 DELETE FAILED - cccccccc NOT
System action FOUND IN PROCSAVE
The screen is not fetched.

Explanation
User response Member cccccccc, the member to delete, was not
found.
Correct the keyword and re-enter it.
OB0128 INVALID RELATIONAL KEYWORD System action
The command stops.

Correct the name and retry the command. You can The requested name change was made.
issue the SCRN command to display a list of screens
in RKOMPCSV. You cannot use DELT to delete screens System action
from the OBOMPROC dataset.
The command stops normally.
OB0132 DIRECTORY UPDATE FAILED,
CODE = xx
User response
An attempt to modify the RKOMPCSV directory failed; OB0136 PROCSAVE MEMBERNAME
the return code (from STOW) is the xx value. The cccccccc DELETED
explanation of the return code is found in the IBM
MVS Data Administration Macro Instruction Reference Explanation
manual (STOW macro).
The named member was deleted.
System action
System action
The command stops.
The command completes.
User response
User response
Examine the return code and take appropriate action.
OB0133 ENTER MEMBER NAME TO BE
DELETED OB0137 RENAME FAILED - cccccccc
ALREADY EXISTS IN PROCSAVE
Explanation
Explanation
The DELT command requires a member name; no
member name was found. The screen space name already exists in the
RKOMPCSV dataset.
System action
System action
The command stops.
The rename process stops.
User response
User response
Enter a member name and retry the command.
Either delete or rename the member in RKOMPCSV, or
OB0134 MEMBER NAME LENGTH GREATER specify another name and retry.
THAN 8 BYTES
OB0138 RENAME FAILED - cccccccc NOT
FOUND IN PROCSAVE
Explanation
The member name exceeds the maximum length of 8 Explanation
bytes.
The member to be renamed is not in the RKOMPCSV
dataset.
System action
The command stops. System action
OMEGAMON stops the command.
User response
Correct the member name and retry the command. User response
OB0135 PROCSAVE MEMBERNAME You can issue the SCRN command to list screens.
cccccccc CHANGED TO aaaaaaaa Correct the name and retry the command.

OB0139 RENAME FAILED - PROCSAVE User response
DIRECTORY FULL
Specify the correct collector ID and retry.
Explanation OB0143 SESSION NOT FOUND. NO LINES

TRANSFERRED
An attempt to update the directory failed.
Explanation
System action
The target ID is not an active session.
System action
User response
Increase the size of the directory or delete members,
then retry the command.
User response
OB0140 DIR ABORT NOT ALLOWED FROM
DIRECTOR SESSION Specify the correct collector ID and retry.
OB0144 PROCSAVE DATASET
Explanation CONCATENATED, UPDATE
REQUESTS IGNORED
The ABORT function can only be performed from a
collector.
Explanation
System action The RKOMPCSV data set cannot be concatenated. Use
OBPROC to concatenate data sets for updating screen
OMEGAMON stops the command. spaces.

If you want to abort the collector, enter the command The command stops.
in the collector segment and retry.
OB0141 NO SYSTEM ID SPECIFIED. NO User response
LINES TRANSFERRED.
Correct the starting PROC or JCL, and restart
OMEGAMON.
Explanation
OB0145 ENTER FROM AND TO MEMBER
The /GIVE command requires a target collector. NAMES FOR RENAME REQUEST

OMEGAMON stops the command. The user did not specify the old and new names
required for the RENM command.
User response
Add the required collector ID and retry. System action
OB0142 SAME SESSION SPECIFIED. NO OMEGAMON stops the command.
LINES TRANSFERRED
User response
Explanation Supply the required parameters and retry the
The target and source for /GIVE are the same. command.
OB0146 {1st|2nd} MEMBER NAME IS
System action INVALID

The indicated name (from or to) is invalid for Specify a unique name and retry.
OMEGAMON.
OB0151 LOG RESET REQUIRED.
USE .LOGOUT
System action
OMEGAMON stops the command. Explanation
Issue the .LOGOUT command to activate the changes
User response made to the log file.
Correct the indicated name and retry the command.
System action
OB0147 SCREEN SPACE NAME MISSING
The command continues.
Explanation
User response
No screen space name was supplied, or an undefined
variable was used. This message usually occurs with Reset the LOG as indicated.
the .SGO command.
OB0152 SYNONYM NAME NOT SPECIFIED
System action
Explanation
A name is required for this function.
User response
System action
Enter a valid screen space name or variable and retry
the command. OMEGAMON ignores the request.
OB0148 MODIFY REJECTED - NO WAIT User response

DETECTED ON INTERFACE ECB
Reissue the command and specify a synonym name.
Explanation OB0153 SYNONYM VALUE NOT SPECIFIED
The modify feature (.MFY) is only available for those
dedicated OMEGAMON sessions begun with a startup Explanation
parameter of MODE=CN (not MODE=CN1).
You must supply an OMEGAMON command name for
the synonym to represent.
System action
OMEGAMON stops the command. System action
OMEGAMON stops the request.
User response
Issue .MFY in sessions started with MODE=CN User response
parameter.
Supply a value for the synonym.
OB0150 DUPLICATE NAME
OB0154 UNKNOWN REQUEST
Explanation
Explanation
The command synonym already exists.
An invalid function was specified.
System action
System action
OMEGAMON cancels the request.
OMEGAMON stops the request.

Specify a valid function (for example, ADD, DELETE). The screen space processor suspends processing
(delayed) until the count in the label field reaches 0.
OB0155 THIS COMMAND WORKS IN TSO The screen space is scheduled for fetch (pending).
MODE ONLY
System action
Explanation
OMEGAMON execution continues.
The command is reserved for use in the TSO
environment.
User response
System action None. This is an informational message only.
OMEGAMON stops the command. OB0162 SCREEN SPACE NOT FETCHED

Execute this command only in a TSO environment. The screen space was not fetched because the
specified condition was not met.
OB0156 VALID ONLY IN DIRECTOR OR
COLLECTOR MODE
System action
Explanation OMEGAMON execution continues.
The .DIR command allows execution of director or
collector commands from within a screen space; it User response
only works in director or collector mode. None. This is an informational message only.
OB0163 NOT A VALID KEYWORD
System action
The command does not run. Explanation
Conditional screen space fetch processing detected a
User response
keyword not contained in its tables.
Execute this command only in a cross memory or cross
system environment. System action
OB0160 .FGO LOOP DETECT HAS BEEN The command stops.
RESET
User response
Explanation
Correct the keyword and retry the command.
OMEGAMON processed the RESET=YES parameter
of the .FGO command which reset the loop detect OB0164 .FGO LOOP DETECT, NO FAST GO
function.
Explanation
System action
There are too many .FGOs in a row (64) without
OMEGAMON execution continues. an intervening display. The .FGO assumes that
OMEGAMON is in a loop.
User response
System action
OMEGAMON disables the .FGO function and changes it
OB0161 SCREEN SPACE FETCH {DELAYED| to .SGO.
PENDING}

Correct the screen space loop and reset the .FGO The condition set with the .VAR immediate command
command. tested not true.
OB0165 .FGO LOOP DETECT SWITCH SET
System action
Explanation OMEGAMON does not set the variable.
OMEGAMON processed the TEST=YES parameter of
the .FGO command which set the loop detect function. User response
System action
OB0201 INVALID COMMAND OPTION
OMEGAMON execution continues. OMEGAMON SPECIFIED
continues to treat .FGO as .SGO until you reissue
the .FGO command with the RESET=YES keyword. Explanation
An incorrect option was specified for the /DEF
User response
command. The valid options are ON and OFF.
OB0170 n OF m MINOR COMMANDS System action
GENERATED FOR cccc The command stops.

The user issued the .EXM immediate command with Correct the error and retry.
parameters. The variable m is the total number of
minor commands associated with major command OB0202 MEMBER NAME TOO LONG
cccc and the variable n is the number of minors
that .EXM displays for this request. Explanation
The member name exceeds 8 characters.
System action
Command execution continues. System action
The command stops.
User response
None. This is an informational message only. User response
OB0171 NO MINOR COMMANDS Correct the name and retry.
AVAILABLE
OB0203 MEMBER ALREADY EXISTS, TO
REPLACE, USE /REP
Explanation
The user issued the .EXM immediate command with Explanation
parameters. However, there are no minors associated
with this major command. The user attempted to save a screen space with the /
SAVE command, but a member with the same name
already exists.
System action
The command executes. System action
The command stops.
User response
None. This is an informational message only. User response
OB0172 CONDITIONAL TEST FAILED - Use the /REP command or enter a new name and retry.
VARIABLE NOT SET

OB0204 MEMBER NOT FOUND - USE /SAVE User response
Increase the size of the directory and restart
Explanation OMEGAMON, use an existing name, or delete entries.
A replace was attempted but no corresponding OB0208 I/O ERROR
member was found in the dataset.
Explanation
System action
An I/O error has occurred. See other accompanying
The command stops. messages.

Correct the name or use the /SAVE command. The command stops.
OB0205 OBPROC DD MISSING
User response
Explanation This is a generic message. Examine the specific error
OMEGAMON could not find the OBPROC DD statement messages and take appropriate action.
and could not open the file. OB0209 PROGRAM ERROR, CONTACT IBM
CORP
System action
An internal error has occurred.
User response
Allocate the proper file and restart OMEGAMON. System action
OB0206 PDS IS BUSY (ENQUEUE FAILED) The command stops.

An attempt to access the dataset failed because it was Contact IBM Software Support.
in use by another job. OB0210 NO PFKS SAVED BECAUSE NONE
MODIFIED
System action
No PF keys were modified, so OMEGAMON did not
User response save them in the OBPROC file.
Wait a few moments and retry the command.

System action
OB0207 NO SPACE IN DIRECTORY
The command stops.
Explanation
User response
The directory is full. There is no room to add additional
members. None. This is an informational message only.
OB0211 /PWD SUPPRESSED BY SECURITY
System action
The user security verification routine has permanently
assigned a security level. This command is therefore
disabled.

The command stops. An attempt was made to set the automatic update
interval less than 5 seconds in VTAM auto update
User response mode.

System action
OB0212 LOGGED The request is denied. An interval of less than 5
seconds is invalid in this mode.
Explanation
The screen space was logged to the report dataset. User response
Set a valid time and retry.
System action
OB0219 COLLECTOR ATTACHED
The command continues.
Explanation
User response
The requested collector is attached to this director.
OB0213 REPORT FILE NOT AVAILABLE System action
Explanation
The allocation of a report file has failed. User response
System action
OB0220 MEMBER NAME IS INVALID
The command stops.
Explanation
User response
The name is specified incorrectly; it must begin with an
Check the minors of the OUTP major command: alpha national character.
DDNM, DEST, DSTU, and FORM.
OB0214 INVALID ARGUMENT System action
The command stops.
Explanation
An operand was found which was not valid for the User response
specified command. Correct the name and retry.
System action OB0221 RKOMPCSV DD STATEMENT

MISSING
The command stops.
Explanation
User response
A DD statement that allocates a user PROCFILE library
See the help entry for the specified command to was not present in the JCL. Therefore, the screen
determine the correct operands. Correct the operand space cannot be saved or replaced.
and retry.
OB0215 VTAM MINIMUM WAIT IS 5 System action
SECONDS OMEGAMON does not make the screen space available
to the user.

Supply a DD statement that points to a PROCFILE The /STK command successfully placed the screen
library. space cccccccc on the stack; this message appears on
the INFO-line.
OB0222 ARGUMENT NOT ALLOWED ON /
RETURN
System action
Explanation The /STK command stops and waits for the next user
request.
The /RETURN command (alias /R) does not allow an
argument. /R is often mistaken as an alias for /REP,
which does allow an argument. User response
This is an informational message only. Enter the next
OMEGAMON ignores the command. OB0226 cccccccc RECALLED

Correct the command and retry. The /STK command successfully retrieved the screen
space cccccccc from the stack; this message appears
OB0223 INVALID STACK ENTRY NUMBER on the INFO-line.

OMEGAMON attempted to recall an invalid stack entry. The /STK command stops and waits for the next user
A valid stack entry number is greater than 0 but less request.
than the number of entries in the stack.
User response
System action
This is an informational message only. Enter the next
OMEGAMON ignores the command. command.
User response OB0227 STACK ENTRY nnnn DELETED
Correct the stack entry number. Use the .DSE

Explanation
command to display the entries on the stack.
The user successfully deleted the stacked screen entry
OB0224 REQUIRED MEMORY FOR ccc NOT nnnn from the stack; this message appears on the
AVAILABLE INFO-line.

OMEGAMON is unable to allocate storage for the stack The /STK command stops and waits for the next user
work area, where the ccc value is either SIA or SIB. request.

The /STK command stops normally and waits for the This is an informational message only. Enter the next
next user request. command.
User response OB0228 STACK EMPTIED
Increase the region size.

Explanation
OB0225 cccccccc STACKED The user cleared all stack entries. OMEGAMON freed
all GETMAINed storage for the stack; this message
appears on the INFO-line.

The /STK command stops and waits for the next user The cccc command name is not a valid 3 or 4
request. alphanumeric character name.

This is an informational message only. Enter the next The command stops.
command.
OB0229 INVALID KEYWORD cccccccc User response
Correct the command name and retry.
Explanation
OB0233 INCORRECT OPTIONAL
The user entered an invalid keyword cccccccc; this PARAMETER - cccccccc
message appears on the INFO-line.
Explanation
System action
The optional parameter for the /ZOOM INFO-line
The /STK command stops and waits for the next user command is not valid; it is not 4 characters long, or
request. it contains characters that are not valid.

Correct the keyword and retry. The command stops.
OB0230 INVALID CURSOR LOCATION
User response
Explanation Correct the parameter and retry.
The cursor must not be in row 0 or in the first or last OB0234 THERE ARE NO PFK
column of a row. ASSIGNMENTS AT THIS TIME

The command stops. The user has not issued any .PFK immediate
commands to assign screen spaces or INFO-line
User response commands to PF keys.
Place the cursor in the proper position and retry.

System action
OB0231 UNABLE TO LOCATE GENERATING OMEGAMON waits for the next user request.
COMMAND
User response
Explanation
Use the .PFK immediate command to assign screen
The backscan for a nonblank in column 2 failed. The spaces or INFO-line commands to PF keys.
scanner backed into the INFO-line; this most likely
occurred if there were only comments on the screen. OB0235 PFK nn NOT CURRENTLY
ASSIGNED
System action
Explanation
The command stops.
The user pressed PF key nn to execute a screen space
User response or an INFO-line command, but a screen space or
INFO-line command is not assigned to PF key nn. This
Correct the screen and retry. message appears on the INFO-line.
OB0232 INVALID COMMAND NAME FOUND
- cccc

System action OB0239 EXTERNAL SECURITY ROUTINE
CANNOT BE FOUND
OMEGAMON waits for the next user request.
Explanation
User response
An attempt has been made to enter a new user ID
Use the .PFK immediate command to assign a screen via the /PWD command. However, the user’s external
space or an INFO-line command to PF key nn, or try security routine cannot be located.
another PF key.
OB0236 RECALL DENIED - AT cccccc OF System action
STACK
The command is terminated.
Explanation
User response
The user entered a /STK U or /STK D command and the
stack entry pointer is currently at the top or bottom of Contact your security administrator to verify that an
the stack; this message appears on the INFO-line. external security routine has been properly installed.
OB0240 INVALID LENGTH FOR USERID
System action
The /STK command stops and waits for the next user Explanation
request. An attempt has been made to enter a new user ID via
the /PWD command that is more than 8 characters.
User response
Enter the next command. System action
OB0237 MAXIMUM STACK ENTRIES The command is terminated.

There is currently a maximum of 999 stacked screens; Correct the user ID and retry.
the user cannot save another screen; this message OB0241 RELOGON NOT ALLOWED IN TSO
appears on the INFO-line. OR SPF MODE

The /STK command stops and waits for the next user An attempt has been made to enter a new user ID via
request. the /PWD command while in TSO or ISPF mode. The
relogon function is not allowed in these modes.
User response
Keep the number of stacked screens under 999. System action
OB0238 ERROR IN $SQZ The command is terminated.

There is an error in the $SQZ routine. Log off from TSO and logon with the new user ID and
password.
System action OB0242 RELOGON REQUEST DENIED - NO
PASSWORD
The /STK command stops.
Explanation
User response
An attempt was made to relogon via the /PWD
Contact IBM Software Support. command, but no password was entered.

System action • U#CHRESP indicates that a message is pending
(U@CHMSHO).
OB0245 INVALID RETURN CODE nn FROM
EXTERNAL SECURITY EXIT
User response
To relogon, re-execute the command and enter a Explanation
password. If you want to reset the security level,
enter /PWD without a user ID. An invalid return code nn was passed from the external
security exit.
OB0243 RELOGON SUCCESSFUL
System action
Explanation
OMEGAMON terminated the command and disallowed
Relogon via the /PWD command was successful. This execution of EXTERNAL=YES commands.
is the default message.
User response
System action
Correct the external security exit to issue only these
The command executes. valid return codes: 0, 4, 8, and 12.
OB0246 /AUPON NOT ALLOWED IN TSO OR
User response SPF MODE
None. This is an informational message only. If you
have customized your own message and it failed to Explanation
display in place of the default message, verify the
following information: Automatic update is not allowed under the VTM1
interface.
• The message has no more than 60 characters.
• U#CHMSGL contains the message’s length.
System action
• U#CHMSG contains the message.
OMEGAMON terminated the command.
• U#CHRESP indicates that a message is pending
(U@CHMSHO).
User response
OB0244 RELOGON REQUEST DENIED
If you want to update automatically, use VTAM or
dedicated mode.
Explanation
OB0247 RELOGON NOT ALLOWED UNDER
The logon through the /PWD command was not OLD EXIT
successful; this is the default message. The user
security exit did not return a message and message
length, or returned an invalid message length. Explanation
Therefore, OMEGAMON issued this default message. The re log on feature is not available with this version
of the user exit.
System action
OMEGAMON terminated the command.
User response
None. This is an informational message only. If you User response
have customized your own message and it failed to Upgrade the user exit to the current version.
display in place of the default message, verify the
following information: OB0248 INTERVAL NOT EFFECTIVE IN ccc
MODE
• The message has no more than 60 characters.
• U#CHMSGL contains the message’s length.
• U#CHMSG contains the message.

The interval that was set cannot take effect in the The value associated with the keyword parameter is
mode in which the user is operating, because the incorrect.
current mode does not support automatic updating.
System action
System action
OMEGAMON bypasses the parameter.
The interval value set is retained. If the value is saved
in a user profile, it may be used in dedicated or VTAM User response
mode.
Correct the parameter and retry.
User response OB0311 PARAMETER keyword value DATA
None. This is an informational message only. IS NOT UNIQUE
OB0249 EFFECTIVE INTERVAL IN ccc Explanation

MODE IS nn.n SECONDS
The value associated with the keyword parameter
is incorrect. The data does not uniquely distinguish
Explanation
between entries.
The interval that was set cannot take effect in the
mode in which the user is operating. The current mode System action
has a minimum interval of nn.n seconds.
System action
User response
The interval value set is retained, however the
minimum of nn.n seconds becomes the effective Correct the parameter and retry.
interval in the current mode of operation. If the value
OB0312 UNKNOWN KEYWORD
is saved in a user profile, it may be effective in other
PARAMETER - cccccccccccc
modes.

The indicated parameter is not in any of the tables
associated with this command.
OB0308 INVALID KEYWORD, EXCESSIVE
LENGTH - cccccccccccc System action
Explanation
The character string is longer than OMEGAMON allows User response
(maximum 12 characters).
System action OB0315 PARAMETER cccccccccccc
(nnnnnnnnnnnn) MAX DECIMALS =
OMEGAMON bypasses the string. It makes no attempt
nn
to validate the string against the internal tables.

The data nnnn associated with parameter cccc
contains too many significant digits to the right of the
OB0310 PARAMETER keyword value DATA decimal point.
IS INVALID
System action

Correct the parameter and retry. The data nnnn associated with parameter cccccccc
must be a numeric value. Only the digits 0–9 and a
OB0316 KEYWORD FORMAT ERROR - decimal point are allowed.
cccccccccccc
System action
Explanation
The parameter was specified in the wrong format. It
must either be specified as a single word or as a
keyword followed by an equal sign (=) and a data User response
value. Correct the parameter and retry.
OB0320 PARAMETER cccccccccccc
System action
(aaaaaaaaaaaa)
Explanation
User response
The data aaaaaaaa associated with parameter
Correct the parameter and retry. cccccccc is in error. This message will be followed by
additional messages explaining the error.
(xxxxxxxxxxxx) MUST BE HEX DATA
System action
Explanation OMEGAMON bypasses the parameter.
The data xxxx associated with parameter cccccccc
must contain only hex digits (0–9 and A–F). User response
System action
OB0321 LENGTH MUST BE GE xxxxxxxx
OMEGAMON bypasses the parameter. AND LE yyyyyyyy

Correct the parameter and retry. The length of the character or hex string data must be
within the bounds xxxxxxxx and yyyyyyyy.
(aaaaaaaaaaaa) MUST BE
bbbbbbbb OR dddddddd System action
Explanation
The data aaaaaaaaaaaa associated with parameter User response
cccccccccccc must be either bbbbbbbbb or Correct the parameter and retry.
ddddddddd. No other values are allowed.
OB0322 VALUE MUST BE GE cccccccc AND
LE aaaaaaaa
System action
OMEGAMON bypasses the parameter. Explanation
The value of the number in message OB0320 must be
User response
within the bounds cccccccc and aaaaaaaa.
OB0319 PARAMETER cccccccccccc System action
(nnnnnnnnnnnn) MUST BE OMEGAMON bypasses the parameter.
NUMERIC

Correct the parameter and retry. The command stops.
OB0323 EXCESSIVE DATA LENGTH, MUST
BE LE 12 User response
Enter a value that is 5 seconds or more.
Explanation
OB0411 $DFNEXC MISSING - CALL IBM
The length of the data is too long. The maximum CORPORATION
length of any data string is 12 characters.
Explanation
System action
An internal exception analysis table is missing from the
OMEGAMON bypasses the parameter. OMEGAMON module.

Correct the parameter and retry. Exception analysis initialization stops.
OB0408 EXCEPTION NOT FOUND; CALL
IBM CORPORATION User response
Explanation
OB0412 NEED nnnK MORE TO INITIALIZE
An exception in the OBUSER module could not be EXCEPTION ANALYSIS
processed because of an error in the exception
analysis tables. Explanation
OMEGAMON requires the nnnK value with more
System action
storage to initialize exception analysis.
Exception analysis initialization stops.
System action
User response
The command stops.
OB0409 MAXIMUM BELL INTERVAL IS 99 User response
SECONDS Run OMEGAMON in a larger region.
OB0418 EXCEPTION ANALYSIS NOT
Explanation
INITIALIZED
An attempt has been made to set the bell interval to
more than 99 seconds. Explanation
Exception analysis has not been initialized.
System action
None.
User response
Enter a value that is less than 99 seconds. User response
OB0410 MINIMUM BELL INTERVAL IS 5 Contact IBM Software Support.
SECONDS
OB0419 GROUP ID IS INVALID
Explanation
An attempt has been made to set the bell interval to
less than 5 seconds.

OMEGAMON does not recognize the group ID supplied Determine the correct exception to be deleted.
as a valid group ID.
OB0423 GROUP ID MUST BE PRESENT
System action
Explanation
OMEGAMON ignores the request.
The GROUP= keyword was not entered.
User response
System action
Enter a defined group ID or define the group to
OMEGAMON. The command stops.
OB0420 EXCEPTION LIMIT OF 25 ENTRIES User response

Enter the GROUP= keyword along with the desired
Explanation
group ID.
A user attempted to enter more than 25 exceptions
OB0424 DELETE PARAMETER IS INVALID
into this group; it is not possible to have more than 25
exceptions in a single user exception group.
Explanation
System action The DELETE= keyword does not have GROUP or
The command stops. EXCEPTION specified.

Create a group of 25 or less exceptions. The command stops.
OB0421 LIST KEYWORD HAS NO User response

EXCEPTIONS
Enter the DELETE= keyword with either GROUP or
EXCEPTION as the option.
Explanation
A user entered the keyword LIST= without any OB0425 INVALID KEYWORD SPECIFIED
exceptions. FOR COMMAND

The command stops. An undefined keyword was specified for this
command.
User response
System action
Enter the desired exceptions for the group.
The command stops.
OB0422 cccc ENTRY NON EXISTENT NOT
DELETED User response
Correct the keyword and retry.
Explanation
OB0426 LAST, WORST, AND CUMULATIVE
A user requested the deletion of an exception from a
group that does not have that exception assigned. VALUES HAVE BEEN RESET

Exception group trip statistics were reset.
The command stops.

Last, worst, and cumulative counters were set to zero. OMEGAMON deleted exception group cc from
exception group table.
User response
System action
The command stops.
OB0427 STATE OPTION IS INVALID
User response
Explanation
A user entered an option for an exception state other
than NULL, NDSP, TEST, ON, or OFF. OB0431 EXCEPTION cccc DELETED FROM
EXCEPTION GROUP aa
System action
Explanation
The command stops.
OMEGAMON deleted exception cccc from exception
User response group aa. It is now available for assignment to another
exception group.
Enter a valid option.
OB0428 GROUP CHANGED FROM cc TO aa System action
FOR EXCEPTION bbbb The command stops.

Exception bbbb was previously in exception group cc This is an informational message only.
before being assigned to group aa.
OB0432 cccccccc - INVALID COLOR,
System action PLEASE RE-ENTER
None.
Explanation
User response The color entered was not a valid color.

System action
OB0429 DELETE INVALID, GROUP NOT IN The command stops.
TABLE
User response
Explanation
Enter a valid color (red, yellow, green, blue, turquoise,
Requested delete for exception group not processed, pink, or white).
exception group is not in the table.
OB0433 EXCEPTION NAME cccc IS
System action INVALID
The command stops.

Explanation
User response The exception name specified was not defined.
Correct the exception group code and retry.

System action
OB0430 EXCEPTION GROUP cc DELETED The command stops.
User response
Enter a defined exception name.

OB0434 SEQUENCE NUMBER IS INVALID User response
Enter a value within the table range.
Explanation
OB0439 NAME KEYWORD PARAMETER IS
A non-numeric sequence was entered for the INVALID
exception.
Explanation
System action
The exception group NAME is null.
The command stops.
System action
User response
The command stops.
Enter a numeric sequence number.
OB0435 GROUP ID cc IS INVALID User response
Enter a valid name for the exception group.
Explanation
OB0440 MORE THAN GROUP ID REQUIRED
The GROUP= parameter for the XACB command was TO ADD ENTRY
not specified or was specified incorrectly.
Explanation
System action
An undefined group ID was entered with no other
The XACB command stops. parameters.

Enter a valid group identification code. The command stops.
OB0437 POSITION KEYWORD HAS NO
ENTRY User response
Enter the group ID, name, and list of desired
Explanation exceptions to add a new entry to the table.
The POSITION= keyword was entered with no value OB0441 cccccccc IS AN INVALID KEYWORD
following it.
Explanation
System action
An undefined keyword was entered.
The command stops.
System action
User response
The command stops.
Enter a correct POSITION= value.
OB0438 POSITION nnn IS INVALID User response
Correct the spelling of the keyword.
Explanation
OB0442 KEYWORDS ALL/LIST/GROUP ARE
OMEGAMON received a POSITION=nnn request that is MUTUALLY EXCLUSIVE
greater than the number of entries in the table that
was specified.
Explanation
System action The XACB command uses the ALL, LIST, and GROUP
keywords to select exceptions for display. Only one of
The command stops. these selection options may be specified at a time.

System action OB0510 USER PROFILE cc ADDED TO
LIBRARY
XACB output is suppressed.
Explanation
User response
The user added a new profile cc to the profile library.
Enter only one of the three keywords.
OB0443 VERBOSE AND TERSE ARE System action
MUTUALLY EXCLUSIVE
The command executes.
Explanation
User response
The XACB command produces either a VERBOSE or
TERSE display. The presence of both keywords creates None. This is an informational message only.
a conflict. OB0515 USER PROFILE cc DELETED FROM
LIBRARY
System action
XACB output is suppressed. Explanation
The user deleted profile cc from the profile library.
User response
Select either VERBOSE or TERSE. System action
OB0444 GROUP cc HAS NO EXCEPTIONS The command executes.
ASSIGNED TO IT
User response
The XACB command was used to select exception OB0520 USER PROFILE cc REPLACED IN
group cc for display. There are no exceptions currently LIBRARY
assigned to group cc.
Explanation
System action
The user replaced existing profile cc in the profile
The command is ignored. library.

Select another exception group for display. The command executes.
OB0445 THERE ARE NO EXCEPTIONS
AVAILABLE FOR DISPLAY User response
Explanation
OB0525 USER PROFILE cc NOT IN LIBRARY
The XACB command did not find any exceptions that
met the selection criteria specified. This could have
happened because the LIST= parameter was specified Explanation
without any exception name. The user attempted to delete profile cc which does not
exist in the library.
System action
The command is ignored. System action
The command stops.
User response
Enter a valid group identifier or exception name.

Correct the profile ID and retry. The user issued a profile command with an invalid
profile keyword.
OB0526 OMEGAMON WILL EXECUTE
USING IBM DEFAULTS
System action
Explanation The command stops.
This message indicates which profile defaults will
execute for this session. User response
Enter the profile keyword SAVE or DELETE.
System action
OB0535 INSTALLATION PROFILE cc
The command completes processing. DELETED FROM LIBRARY

None. This is an informational message only. The installer deleted the installation profile from the
library.
OB0527 OMEGAMON WILL EXECUTE
USING YOUR INSTALLATION
PROFILE System action
The command stops.
Explanation
This message indicates which profile defaults will User response
execute for this session. None. This is an informational message only.
OB0540 INSTALLATION PROFILE ADDED
System action
TO LIBRARY
Explanation
User response
The installer added a new installation profile to the
None. This is an informational message only. profile library.
OB0530 USER PROFILE ID cc IS NOT VALID
System action
Explanation The command stops.
The user issued a profile command with an invalid
profile identifier (suffix). User response
System action
OB0544 INSTALLATION PROFILE DELETED
The command stops. FROM LIBRARY

Enter a valid two character profile identifier. Use the The installer deleted the existing installation profile
PPRF LIST command to list valid identifiers at your from the profile library.
installation.
OB0532 USER PROFILE KEYWORD cccccccc System action
IS INVALID The command stops.
User response

OB0545 INSTALLATION PROFILE System action
REPLACED IN LIBRARY
The command stops.
Explanation
User response
The installer replaced the existing installation profile in
the profile library. Add a comment that is a maximum of 18 characters
and retry the command.
System action OB0590 PROFILE SERVICE REQUEST

FAILED - {reason}
The command stops.
Explanation
User response
A user profile request failed for the specified reason.
OB0546 INSTALLATION PROFILE System action
IDENTIFIER NOT ALLOWED
The request is terminated.
Explanation
User response
The user entered a profile identifier for the installation
profile command. It does not accept an identifier. The reasons that appear follow. Take the appropriate
action for the reason displayed with this message.
System action OB0590 ABEND X13 OCCURRED IN cccc
The command stops.

Explanation
User response An X13 abend occurred when the specified routine
(cccc) tried to open the profile dataset.
Either use the PPRF command for a user profile, or
delete the identifier on the IPRF command for the
installation profile. System action
OB0547 INSTALLATION PROFILE NOT IN The request is terminated.
LIBRARY
User response
Explanation Check the SYSLOG for the X13 abend and correct the
The installer attempted to delete or replace a problem.
nonexistent installation profile from the profile library. OB0590 ABEND X14 OCCURRED IN cccc

The command stops. An X14 abend occurred attempting to close the profile
dataset from routine cccc.
User response
OB0580 COMMENT ccccccccccccccccccc IS The request is terminated.
MORE THAN 18 CHARACTERS
LONG User response
Check the SYSLOG for the X'14' abend and correct the
Explanation problem.
A comment was added with the PPRF command that is OB0590 ABEND X'37' OCCURRED IN cccc
longer than the maximum allowed.

An X'37' abend occurred while processing the profile Increase the region parameter on the EXEC statement
dataset from routine cccc. or job card of the OMEGAMON session.
OB0590 INPUT DCB OPEN FAILED
System action
The request is terminated. Explanation
An attempt to open the input profile dataset was not
User response successful.
Compress and/or reallocate the dataset as required.
System action
OB0590 ABEND 913, SECURITY
VIOLATION The request is terminated.

An abend 913 occurred attempting to access a profile Make sure that the input profile dataset is properly
data set. defined. Contact IBM Software Support.
OB0590 INPUT FILE NOT AVAILABLE
System action
The request is terminated. Explanation
A prior error occurred during user profile facility
User response processing and the input file was flagged as
Contact the person in charge of system security at your unavailable to this OMEGAMON session.
installation.
System action
OB0590 FILE NOT AVAILABLE
Explanation
User response
processing and the file was flagged as unavailable to Another OB0590 message with a different reason
this OMEGAMON session. was issued prior to this one. Follow the procedure to
correct the first error.
System action OB0590 INTERNAL ERROR, cccccc
Explanation
User response Routine cccccc has detected an OMEGAMON internal
There should be a prior error message. Follow the error.
instructions to correct the first error.
System action
OB0590 GETMAIN FAIL, INCREASE
REGION The request is terminated.

An attempt to GETMAIN storage failed with a nonzero Contact IBM Software Support.
return code.
OB0590 INTERNAL PROFILE HEADER
ERROR
System action

The user profile header record about to be written to The requested profile member contains no records.
the output data set has an error.
System action
System action
User response
User response
Delete or replace the empty profile.
OB0590 nnnnnnnn NOT FOUND
OB0590 INVALID DDNAME IN cccc
Explanation
Explanation
Member nnnnnnnn was not found in the profile data
An internal OMEGAMON error has occurred. set.

The request is terminated. The request is terminated.

Contact IBM Software Support. Insure that the proper member name was requested.
Use the PPRF LIST command to see what profiles are
OB0590 INVALID SERVICE REQUEST TYPE available and what profile data sets are allocated.
Explanation OB0590 OPEN FAILURE IN cccc
An invalid parameter type was presented to the user

Explanation
profile facility I/O driver.
An attempt to open a profile data set in routine cccc
System action was not successful.

System action
User response The request is terminated.

User response
OB0590 IOWA NOT AVAILABLE Insure that the profile data sets are properly defined.
If you still cannot open the data set, contact IBM
The user profile I/O work area is not available. OB0590 OUTPUT DCB OPEN FAILED

The request is terminated. An attempt to open the output profile data set was not
successful.
User response
System action
OB0590 MEMBER IS EMPTY

User response OB0590 SEQUENCE ERROR IN cccc
Make sure that the output profile data set is properly
defined. Contact IBM Software Support. Explanation
OB0590 OUTPUT FILE NOT AVAILABLE An internal error occurred during user profile facility
processing in routine cccc.
Explanation
System action
processing and the output file was flagged as The request is terminated.
unavailable to this OMEGAMON session.
User response
System action Another OB0590 message with a different reason was
The request is terminated. issued prior to this one. Follow the procedure to
correct the first error.
User response OB0590 SERVICE NOT AVAILABLE
Another OB0590 message with a different reason
was issued prior to this one. Follow the procedure to Explanation
correct the first error. An invalid parameter was presented to the user profile
OB0590 OUTPUT TEMPORARILY facility I/O driver.
UNAVAILABLE
System action
Explanation The request is terminated.
The output profile data set is being used by another
OMEGAMON session. User response
System action
OB0590 SPANNED RECORD ERROR
Explanation
User response
A profile being read for input was found to have an
Once the output profile data set is free, you can enter invalid value in the spanned record field.
the command again. If the condition persists, contact
System action
OB0590 PROFILE DATASETS NOT
ALLOCATED The request is terminated.

The OBPROF and OBPROFSV data sets are not Attempt to recreate the profile and if the problem still
allocated. exists, contact IBM Software Support.
OB0800 INFORMATION UNAVAILABLE
System action - NOT A MULTI-USER
ENVIRONMENT
The request is terminated. Profile services are not
available.
Explanation
User response In response to the .VTM command, OMEGAMON
determined that the current environment does not
Allocate the OBPROF and OBPROFSV data sets by DD support multiuser sessions. There is no meaningful
statements or CLIST as appropriate for the session information for the .VTM command to display. Valid
mode. If the problem persists, contact IBM Software multiuser environments are VTM, VTS, and VTT.
Support.

The command stops. Try the command again. If this message persists,
User response OB0900 COMMAND cccc IS NOT A VALID
Use this command only in a valid multiuser COMMAND
environment controlled by OBVTAM.
Explanation
OB0801 INFORMATION UNAVAILABLE -
INTERNAL ERROR The command cccc is not a minor of the current
major command or is not itself a major or immediate
Explanation command.
In response to the .VTM command, OMEGAMON

System action
attempted to display multi-session status information.
However, OMEGAMON detected one or more problems OMEGAMON bypasses this line.
in the internal subtask configuration for OBVTAM.
This problem may be caused by transitory changes in User response
OBVTAM subtask structures, which could result in a
program check. Correct the command and retry.
OB0901 COMMAND SUPERSEDED BY cccc
System action
OMEGAMON no longer supports the specified
User response command. Command cccc now performs a similar
function.
Reissue the command. If this message persists,
System action
OB0802 NO DATA ONLY SPACES ARE
OWNED BY THIS ADDRESS SPACE OMEGAMON selects the new version of the command.

No tasks within the address space specified by the None. In the future, use command cccc.
PEEK major command own any data-only spaces.
OB0902 COMMAND INVALID UNDER nnn
System action
Explanation
The command stops.
This command is not valid with the MVS version you
are running (nnn).
User response
OB0803 ERROR DETECTED IN INTERNAL OMEGAMON selects the next command.
SCAN ROUTINE
User response
Explanation
Use this command with the correct version of MVS.
An internal subroutine detected an error while
OB0903 INVALID INFO-LINE COMMAND
collecting information on data-only spaces for the
specified address space.
Explanation
System action The INFO-line command entered does not exist.
The command stops.

The command is not executed. A pattern-controlled operation was requested, but the
pattern was not defined.
User response
System action
Correct the command and retry.
Operation is ignored.
OB0906 COMMAND DISABLED
User response
Explanation
Set a proper pattern using the .SPT command.
The specified command was disabled by user security
processing. OB0917 PATTERN ARGUMENT MUST BE
NUMERIC
System action
Explanation
OMEGAMON bypasses this line.
The command requires a pattern that only has numeric
User response values.
Issue another command.

System action
OB0910 PROGRAM CHECK - RECOVERY Pattern operation is ignored.
SUCCESSFUL - xxxxxxxx
User response
Explanation
An OMEGAMON command terminated abnormally due
to a program check at location xxxxxxxx. OB0918 NO PATTERN EXISTS

OMEGAMON aborts the command. No pattern exists for the requested pattern number.

Retry the command. If the problem persists, follow Pattern operation is ignored.
the instructions given in the Preface, then contact IBM
Software Support. User response
OB0915 CROSS MEMORY ERROR, Correct the command or assign a pattern.
ADDRESS SPACE SWAPPED OUT
OB0919 PATTERN NUMBER MUST BE 0
THROUGH 9
Explanation
Cross memory operations were attempted to an Explanation
address space that was swapped out.
Invalid pattern number.
System action
System action
Program recovery is successful, although the operation
is suppressed. Pattern operation is ignored.

None. This is an informational message only. Correct the command and retry.
OB0916 PATTERN MUST BE SET BY .SPT OB0920 COMMAND LOOP—RECOVERY
COMMAND SUCCESSFUL

OMEGAMON built-in loop detection encountered a The command is not executed.
possible loop in an OMEGAMON command processor.
User response
System action
Correct the command syntax and retry.
OB0925 LOOP IN OMEGAMON BASE
User response
Explanation
Use the .SET command to increase the LOOPTIME
and/or LOOPCOUNT values. If the problem persists OMEGAMON’s built-in loop detection encountered a
after setting these values to the maximum, follow possible loop in an OMEGAMON service module.
the instructions given in the Preface and contact IBM
Software Support. System action
OB0921 SECURITY CHECK FAILED OMEGAMON stops with a user ABEND 0925.
(INTERNAL)
User response
Explanation
Use the .SET command to increase the LOOPTIME
A password was not supplied for the security level and/or LOOPCOUNT values. If the problem persists
associated with this command. after setting these values to the maximum, follow
the instructions given in the Preface and contact IBM
Software Support.
System action
OB0926 LOOP IN OMEGAMON BASE
OMEGAMON suppresses the command.
TERMINATION
User response
Explanation
Supply a valid password, or see your security
A loop was detected while termination operations
administrator.
were under way.
OB0922 SECURITY CHECK FAILED
(EXTERNAL) System action
Termination operations are suspended and
Explanation
OMEGAMON abends.
The OMEGAMON external security interface
determined that the command is not authorized for User response
execution.
System action OB0930 UNEXPECTED PROGRAM CHECK -
xxxxxxxx
OMEGAMON suppresses the command.

OMEGAMON abend protection (ESTAE) processing
See your security administrator.
detected a program check error in a module at location
OB0924 cccc COMMAND NOT VALID WITH xxxxxxxx.
cc ARGUMENT
System action
Explanation
This command does not support a .D or a .R argument.

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

version level, the integrity of some OMEGAMON data OB0939 STORAGE UNAVAILABLE FOR
may be compromised. COWA

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

The system prompts you on whether you want to If you need to display more than 7 cross memory
continue initialization. If you continue to run an collectors on this system, start another OMEGAMON
OMEGAMON version that does not match the MVS director.
version level, the integrity of some OMEGAMON data
OB0942 COLLECTOR AT WRONG VERSION:
may be compromised.
CONNECTION FAILED
User response
Upgrade your MVS version.

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

OMEGAMON cancels the request. If you need to display more than 7 collectors on this
system, start another OMEGAMON director.
User response OB0952 COLLECTOR ID ALREADY ACTIVE
Correct the COLS= value at either the collector or
director and restart the session. Explanation
OB0949 DIRECTOR AT WRONG VERSION: The /ATTACH command generates this message. While
CONNECTION FAILED (RC=40) trying to bring up a cross system collector session,
OMEGAMON detected that this collector was already
Explanation in session with a director.
A cross memory collector tried to start a cross memory

System action
session with an OMEGAMON director of a different and
incompatible release level. OMEGAMON cancels the request.

OMEGAMON cancels the request. Specify the correct collector ID.
OB0953 DDNAME MISSING
User response
Bring up the director and cross memory collector using Explanation
the same (or compatible) version of OMEGAMON.
This message may be issued in either of two
OB0950 DISK DATASET AT WRONG situations:
VERSION - REFORMAT (RC=40)
• When the /ATTACH command is issued and
OMEGAMON did not find the correct DD statement
Explanation for the cross system dataset.
This session’s cross system dataset was formatted • When attempting to start a collector and
with an incompatible version of the format program. OMEGAMON did not find the correct DD statement
for the cross system dataset.
System action
System action
User response
User response
Reformat the cross system dataset with the current
version of the KOBXDSK program. To correct the error, check the following:
OB0951 ONLY EIGHT SEGMENTS ALLOWED • A collector system ID for the session that matches
the name specified on the SYS= start-up parameter.
Explanation • A missing or incorrect DD statement in the director
start-up JCL or EXEC file to point to the cross system
The /ATTACH command generates this message. dataset.
OMEGAMON allows no more than 7 collectors plus
• A missing or incorrect DD statement in the collector
the director segment at the director screen for cross
start-up JCL or EXEC file to point to the cross system
memory/cross system mode terminal input/output
dataset.
processing.
When you have corrected the error, restart the
System action OMEGAMON director.
OMEGAMON cancels the request. OB0954 COLLECTOR ID REQUIRED

Explanation OMEGAMON console failed because it was not
initiated as an OMEGAMON director.
The /ATTACH command generates this message. An /
ATTACH INFO-line command was entered without a
collector ID. System action
System action
OMEGAMON cancels the request. User response
Restart OMEGAMON, specifying the proper parameter
User response for director mode.
Re-enter the /ATTACH command and specify a valid OB0958 ENQUEUE ALREADY
collector ID. OUTSTANDING. QNAME: cccc
OB0955 DATASET AT WRONG LEVEL -

REFORMAT Explanation
An enqueue attempt by the director controller failed.
Explanation
The /ATTACH command generates this message. A System action
different release level format program was used to The attach is suppressed.
format the cross system data set for this cross system
session and its director.
User response
System action If this problem persists, contact IBM Software
Support.
OB0959 DEQUEUE ATTEMPTED FOR
RESOURCE NOT OWNED.
User response QNAME:cccc
Reformat the cross system data set with the current
version of the KOBXDSK program. Explanation
OB0956 DATASET HAS WRONG NUMBER A dequeue attempt by the director controller failed.
OF COLUMNS - REFORMAT
System action
Explanation
The detach is suppressed.
The /ATTACH command generates this message. The
cross system data set used for cross system session
initialization was formatted for a different screen size User response
(via the COLS= parameter) than that of the director If this problem persists, contact IBM Software
terminal. Support.
OB0960 BASE(Vnnnccc) AND
System action INIT(Vnnnccc) VERSIONS ARE
OMEGAMON cancels the request. NOT COMPATIBLE

Reformat the cross system dataset with KOBXDSK and You are using two incompatible levels of OMEGAMON
specify the proper COLS= value. load modules.
OB0957 DIRECTOR MODE IS REQUIRED

System action
Explanation OMEGAMON does not start.
The /ATTACH command generates this message. The

attempt to attach a cross system collector at an

Verify that the proper libraries are in use. If Specify MODE=LS when starting OMEGAMON at this
necessary, reinstall OMEGAMON using the appropriate device.
distribution tape.
OB0965 WARNING: NUMBER OF ROWS
OB0962 UNABLE TO OPEN PRIMARY REQUESTED DOES NOT MATCH
CONSOLE YOUR TERMINAL SIZE
OMEGAMON could not bring up the requested The value specified for the ROWS= start-up parameter
dedicated OMEGAMON session because the does not match the actual size of the OMEGAMON
OMEGAMON console (specified by the UNIT= start-up terminal screen.
keyword) is not available.
System action
System action
OMEGAMON changes ROWS to match the terminal
If this is the first OMEGAMON console session in size; initialization continues.
the address space, OMEGAMON stops. Otherwise, the
particular OMEGAMON console session stops. User response
Specify a ROWS= value that matches your terminal’s
User response
physical characteristics at OMEGAMON start-up.
Check to see whether the terminal address is attached
OB0966 RKOMPCSV DD CONCATENATED,
to another user or owned by VTAM. Specify an
UPDATES IGNORED
available console and retry.
OB0963 cc MODE INVALID: NOT A TSO Explanation
SESSION
The RKOMPCSV DD statement consists of more than
one dataset.
Explanation
You can only specify TS or LS mode at OMEGAMON System action
start up when OMEGAMON is running under a TSO
session. MVS data management constraints prevent
OMEGAMON from performing any PDS updates to
RKOMPCSV. OMEGAMON ignores requests by the /
System action
SAVE and /REP INFO-line commands and the DELT
OMEGAMON stops. and RENM immediate commands.

Correct the MODE= parameter and restart Remove the concatenated datasets from the
OMEGAMON. RKOMPCSV DD statement and restart OMEGAMON.
OB0964 TS CHANGED TO LS AS THIS IS OB0967 xxPROCSV PRIOR SECURITY
NOT A SCREEN DEVICE VIOLATION xxPROC —ABEND
SX13
Explanation
Explanation
An OMEGAMON TSO session was altered to low-speed
mode, since the OMEGAMON terminal is not a display A /SAVE or /REP command failed due to a security
device. problem.

TS mode becomes LS mode. The command stops.

User response • PARM FIELD SYNTAX ERROR
Consult your security coordinator to gain access to the • PARAMETERS MUST BE SEPARATED BY A COMMA
data sets in the xxPROC DD statement. • KEYWORD MUST END IN EQUAL SIGN
OB0969 INSUFFICIENT MEMORY TO • UNKNOWN KEYWORD PARAMETER
INITIALIZE • PARAMETER STRING TOO SHORT
• PARAMETER STRING TOO LONG
Explanation • PARAMETER NOT VALID HEXADECIMAL VALUE
OMEGAMON was unable to GETMAIN enough virtual • PARAMETER VALUE TOO LOW
storage to complete initialization.
• PARAMETER VALUE TOO HIGH
• THIRD CHARACTER MUST BE NUMERIC
System action
• FIRST PARAMETER LENGTH ERROR
The startup fails.
• UNABLE TO ACQUIRE STORAGE FOR PARAMETER
TABLES
User response • UNIT SAME AS EXISTING TASK
Increase the region size address space and restart • OMEGAMON HAS PROBABLY BEEN ENTERED AS A
OMEGAMON. (See message OB0970). TSO COMMAND
OB0970 INCREASE REGION SIZE BY nnnK • UNSUPPORTED MODE - BASE
AND RERUN • UNSUPPORTED MODE - OMEGAMON
• UNSUPPORTED MODE - NO IC DRIVER
Explanation
OB0972 (USER INPUT APPEARS HERE)
Initialization failed because OMEGAMON needed
additional virtual storage.
Explanation
System action OMEGAMON issues this message with the OB0971
message.
OMEGAMON stops processing.
System action
User response
OMEGAMON stops.
Increase the REGION= parameter by the amount that
this message indicates and restart OMEGAMON. (See
message OB0969.) User response
OB0971 ......+....1....+....2....+....3....+....4 See the error code for the OB0971 message.
OB0973 WARNING -- RUNNING nnn
Explanation OMEGAMON ON yyy SYSTEM
This ruler appears less than the OB0972 message to

help you locate PARM line errors. Additional message Explanation
text appears under the ruler line, followed by the This level of OMEGAMON (nnn) is incompatible with
column location of the error, except when the error is this level of VM (yyy).
in column 1.
System action
System action
OMEGAMON initialization continues, but with
The OMEGAMON session stops. unpredictable results.

Examine the message text and make suitable If OMEGAMON did not terminate itself, stop it,
corrections. Additional message text: install the correct OMEGAMON level, and restart
• OMEGAMON STARTUP PARAMETER ERROR OMEGAMON.

OB0974 aaaaaaaa LOADER ERROR System action
The command stops.
Explanation
OMEGAMON attempted to load module aaaaaaaa, but User response
could not find it in the load library.
System action OB0978 SECURITY ROUTINE HAS

ABORTED STARTUP
The load fails and OMEGAMON issues an abend code
0974.
Explanation
User response An external security routine passed back a nonzero
return code to initialization.
Check that module aaaaaaaa is in the load library.
OB0975 aaaaaaaa MODULE HAS System action
REENTRANT LINKAGE EDITOR
ATTRIBUTE OMEGAMON stops.

OMEGAMON could not update the module aaaaaaaa See your security officer.
because it resides in a store-protected subpool. OB0979 ERROR LOADING PRODUCT
MODULE cccccccc
System action
OMEGAMON stops. Explanation
The product module could not be loaded successfully.
User response
Re link the aaaaaaaa module without the RENT System action
linkage editor parameter. OMEGAMON stops.
OB0976 RMF ASCB NOT FOUND
User response
Explanation Be sure the named module is in the product library.
OMEGAMON was unable to locate proper ASCB during See accompanying MVS system messages and take
RMF search. appropriate action. If it is not in the product library,
System action OB0980 SAVE STACK RECOVERY

SUCCESSFUL
The process stops.
Explanation
User response
The save area stack overflowed.
OB0977 {SMF|WTO} AUDITING IS BEING System action
SUPPRESSED FOR THIS SESSION
The command stops.
Explanation
User response
The user security exit has explicitly requested that
SMF and/or WTO auditing be suppressed for this Contact IBM Software Support.
session; this request is made at initialization and/or OB0981 COMMAND TABLE ERROR cccc
relogon time. This message only appears once.

A validation error occurred while loading the command OMEGAMON stops.
table module.
User response
System action
OMEGAMON stops.
OB0985 SAVE STACK RECOVERY
SUCCESSFUL
User response
OB0982 ERROR DETECTED IN COMMAND Invalid stack release by a command.
TABLES
System action
Explanation
OMEGAMON stops the command execution.
An error occurred while loading the command tables.
User response
System action
This is an internal error. Contact IBM Software
This is a secondary message. It follows messages that Support.
contain validation error information.
OB0986 GETMAIN FAILED FOR COMMAND
TABLES
User response
Examine the previous errors and follow the Explanation
recommended user responses.
The request for storage for a copy of the command
OB0983 CANNOT LOCATE COMMAND module failed.
TABLE MODULE, ABEND=cccc,
RC=cc System action
OMEGAMON stops.
Explanation
The usual cause of this message is insufficient region User response
size for OMEGAMON to load the command table
module. Increase the region size for OMEGAMON.
OB0987 PRODUCT INITIALIZATION
System action FAILED, RC=nnn
OMEGAMON aborts the session start.
Explanation
User response The product initialization routines have returned an
See your installer to increase the region size. For other error code which is non-zero.
possible causes, look up the abend code in the IBM
System Codes manual for your system. You may also System action
need to refer to the IBM System Messages manual.
OMEGAMON stops.
OB0984 NO COMMAND TABLE MODULE
NAME User response
Read any other messages that accompany this
Explanation
message. If unable to find the problem, contact IBM
An error occurred in command table processing. Software Support.

OB0988 PRODUCT LEVEL nnn OB0991 DYNAMIC ALLOCATION ERROR:
INCOMPATIBLE WITH DRIVER ERROR=cccc, INFO=cccc
LEVEL mmm
Explanation
Explanation
A dynamic allocation request failed with the ERROR
The base driver module cannot service the current and INFO codes indicated.
product.
System action
System action
The allocation process stops.
OMEGAMON initialization stops.
User response
User response
Examine the error and information codes in the
Use a base driver which is at the same or greater level message and take appropriate action.
than the product you are trying to initialize. Retry using
this new driver. OB0992 aaUSERbb VALIDATION FAILED.
RC=n
OB0989 OBUSERcc MUST BE
REASSEMBLED; IT IS NOT Explanation
COMPATIBLE WITH THIS RELEASE
OF OMEGAMON The user profile aaUSERbb did not pass product
validation.
Explanation
System action
The user assembled an old OBUSER module that is
incompatible with the current release of OMEGAMON. Session initialization stops.

OMEGAMON initialization stops. If other messages were issued previously, take the
action suggested for those messages. If no other
messages were issued, contact IBM Software Support.
User response
OB0993 NO ARGUMENT HAS BEEN
Obtain the current OBUSER from the product tape and
SUPPLIED
reassemble.
OB0990 SECURITY LOGGING, userid, Explanation
cccccccc, ACCESS(aaaaaaaa)
A valid argument was not supplied for the command.
Explanation
System action
The security settings of the command table produce
this security logging message. The variable cccccccc The command stops.
is the command being validated and aaaaaaa is
the result. The userid is displayed if AUDIT=WTO is User response
specified.
Supply a valid argument and reissue the command.
System action OB0994 NO VALID PATTERN HAS BEEN
SUPPLIED
OMEGAMON stops the running of any command to
which it denies access.
Explanation
User response A valid pattern was not supplied for the command.

System action audit activity will be directed to the console for the
duration of the session.
The command stops.
System action
User response
A WTO is issued to the console with audit information.
Supply a valid pattern and reissue the command.
OB0995 UNABLE TO LOG AUDIT RECORD User response
TO SMF, RC=cc
Use the Security Update Program to specify a valid
SMF record ID.
Explanation
OB0998 EXTERNAL SECURITY IS
A non-zero return code was received from SVC UNAVAILABLE
83 while attempting to track an audited command.
These codes are documented in the IBM System
Programming Library: System Management Facilities Explanation
(SMF) manual for your system. OMEGAMON could not locate the user security routine
to process a command for which external security was
System action requested. Internal security was not invoked because
the command did not have a security level associated
A WTO is issued to the console with audit information. with it.

Consult the appropriate IBM documentation for an OMEGAMON suppresses command execution.
explanation and interpretation of the non-zero return
code. This return code may indicate a serious problem
with SMF. User response
OB0996 APF AUTHORIZATION REQUIRED Determine why the user security routine is missing.
FOR SMF LOGGING Make sure it is in a link-list library or in the
OMEGAMON STEPLIB.
Explanation OB1112 DATA COLLECTOR IS NOT ACTIVE
OMEGAMON cannot write SMF records unless it is

APF-authorized. This message will appear only once; Explanation
thereafter, all audit activity will be directed to the The requested collector is not currently active.
console for the duration of the session.
System action
System action
The IPRO command processor suppresses the display.
A WTO is issued to the console with audit information.
User response
User response
Start the collector and retry the command.
Determine whether OMEGAMON should be authorized.
This is an installation decision. OB1116 REQUEST NOT SUPPORTED
OB0997 RECORD NUMBER MUST BE

BETWEEN 128 AND 255 Explanation
(INCLUSIVE) FOR SMF LOGGING The request is not supported by the target collector.

OMEGAMON detected a request to write an SMF The IPRO command processor suppresses the display.
record with an invalid record ID. User SMF records
must use a record ID between 128 and 255, inclusive.
This message will appear only once; thereafter, all

Correct the parameters and retry the request. An error occurred in the IPRO data display extractor.
No presentation is made during this cycle.
OB1120 REQUESTED DATA NOT VALID
System action
Explanation
The IPRO collector’s data is currently statistically
invalid. Sufficient data has not yet accumulated for a
meaningful display. User response
System action
OB1191 UNABLE TO LOAD IANL
The IPRO command processor suppresses the display PROCESSOR MODULE
until enough samples have accumulated.
Explanation
User response
OMEGAMON could not find the Impact Analysis
Wait for sufficient time to gather data. This is an processor module to load.
informational message only.
OB1124 REQUESTED DATA NOT AVAILABLE System action
Explanation
The requested data is not being collected at this time. User response
If this module should be available, contact IBM
The IPRO command processor suppresses the display. OB1195 MISSING EXTRACTOR NAME

Stop and restart the collector requesting the required No extractor identification was given to the IPRO
data, or correct the collector startup parameters and command processor. Either this is the first time the
retry the request. command was used, or it was cleared by the first
extractor and there are no new operands.
OB1140 REQUEST INCONSISTENT OR
UNDEFINED
System action
Explanation The IPRO command processor suppresses the display.
The IPRO display parameters are not valid, so the
processor suppresses the display. User response
Supply a proper extractor ID.
System action
OB1196 DATA EXTRACTOR ADDRESS = 0 -
The extractor was unable to process the parameters xxxx
successfully.
Explanation
User response
The IPRO display processor for xxxx could not be
Correct the parameters and retry. located in this set of OMEGAMON modules.
OB1148 SUCCESSFUL ABEND RECOVERY
IN EXTRACTOR System action

Contact IBM Software Support. Look for other messages and take appropriate action.
OB1197 UNKNOWN RETURN CODE FROM OB1201 TSO SERVICE ERROR RETURN
EXTRACT - cc CODE nnn
The IPRO display processor returned the code cc , The TSO service task has returned the error code
which is unknown to the IPRO command. indicated.

The IPRO command processor suppresses the display. The ISPF session stops.

Contact IBM Software Support. Examine the error code and take appropriate action.
Refer to the IBM manual, TSO Extensions User’s Guide.
OB1198 INVALID PARAMETER - cccc
OB1202 ATTACH FAILED FOR MONITOR
Explanation TASK
The first 4 characters (cccc) of the operand are invalid.

Explanation
System action ISPF issued a nonzero return code in response to /
ATTACH.
System action
User response
The ISPF session stops.
Specify a valid IPRO collector and retry.
OB1199 IPRO COMMAND NOT SUPPORTED User response
Examine the return code and take appropriate action.
Explanation
OB1203 MONITOR TASK COMPLETE,
The IPRO command is not supported at this product RETURN CODE = cc
level.
Explanation
System action
The monitor task (OMEGAMON) terminated with the
The IPRO command processor suppresses the display. indicated return code.

Contact IBM Software Support. The task stops.
OB1200 SEVERE ISPF ERROR DETECTED
User response
ISPF has returned a severe error condition code to the OB1204 MONITOR TASK ABENDED,
OMEGAMON ISPF driver. COMPLETION CODE = cc

The ISPF session stops. The monitor task (OMEGAMON) terminated with the
indicated abend code.

The task stops. The OMSPFD variable was not in the panel.

OB1210 PARM STRING LENGTH ERROR
User response
Explanation Make sure that the correct panel is installed and that
user changes have not caused this field to be omitted.
The PARM string entered was too long, causing
internal buffer overflow. OB1214 INSUFFICIENT SPACE FOR
PQUERY FUNCTION
System action
Explanation
The task stops.
ISPF indicated a short-on-storage condition.
User response
System action
Shorten the PARM string and retry the command.
The task stops.
OB1211 UNABLE TO LOAD ISPLINK
MODULE
User response
Explanation Increase the TSO address space region and retry.
The ISPF driver module was unable to load ISPLINK, OB1215 DATA TRUNCATION HAS
the ISPF interface. OCCURRED

The task stops. Internal data truncation occurred within a panel
variable.
User response
System action
Make sure a copy is available to the ISPF driver.
The task stops.
OB1212 PANEL OMSPF01 NOT FOUND
User response
Explanation
Make sure that the variable lengths shown in the panel
The SPF driver module could not find the OMSPF01 have not been changed.
panel.
OB1216 VARIABLE NOT FOUND
System action
Explanation
The task stops.
A variable that the ISPF driver requires could not be
User response found in the ISPF subpools.
Be sure the panel is in the correct ISPF library and

System action
retry.
The task stops.
OB1213 VARIABLE OMSPFD NOT IN PANEL
OMSPF01
User response
This is an internal error. Contact IBM Software
Support.

OB1217 INVALID SCREEN SIZE User response
Examine the error code and call your systems support.
Explanation If the problem persists, contact IBM Software Support.
The screen parameters are invalid for ISPF mode. OB1252 MODULE ABENDED, COMPLETION
COLS and ROWS must match the TSO specification for CODE = xxx
the device.
Explanation
System action
The module abended with the indicated return code.
The task stops.
System action
User response
The application using the module is terminated.
Correct the screen specification parameters (COLS and
ROWS) and restart.
User response
OB1220 UNKNOWN RETURN CODE FROM
ISPLINK Examine the abend code and call your systems
support. If the problem persists, contact IBM Software
Support.
Explanation
OB1253 SET STFSMODE ON FAILED AT
ISPLINK returned a code 20 or higher to the calling INITIALIZATION
task.
Explanation
System action
OMEGAMON could not set full-screen mode on as
The task stops. requested for TSO mode.

OB1250 cccccccc STORAGE REQUEST
FAILED User response
Explanation
OB1254 SET STTMPMD OFF FAILED AT
The request for storage for the module cccccccc failed. INITIALIZATION

The TSO or ISPF mode task stops. OMEGAMON could not set display manager off as
requested for TSO mode.
User response
Increase the region size for the TSO address space. System action
OB1251 ATTACH FAILED FOR cccccccc, The task stops.
RETURN CODE = xx
User response
A non-zero return code from ATTACH of module OB1255 SET STFSMODE OFF FAILED AT
cccccccc was received. TERMINATION
System action
The TSO or ISPF mode task stops.

Explanation OB1259 LOAD cccccccc FAILED
OMEGAMON could not set full-screen mode off as
requested for TSO mode. Explanation
The load request for module cccccccc has failed.
System action
The task stops. System action
The task stops.
User response
OB1256 SET STTMPMD ON FAILED AT Examine the error code in the SYSLOG. Ensure that
TERMINATION load module cccccccc is in the proper load library. If
Explanation OB1260 DELETE cccccccc FAILED
OMEGAMON could not set display manager on as
requested for TSO mode. Explanation
The delete request for module cccccccc has failed.
System action
The task stops. System action
The task stops.
User response
OB1257 {TSO|ISPF} MODE TASK Contact IBM Software Support.
TERMINATED OB1261 GTTERM FAILED
The task completed its processing with a normal The request to get terminal attributes has failed.
termination.
System action
System action
The task stops.
The TSO or ISPF mode task stops.
User response
User response
OB1401 MISSING USER ID
OB1258 cccccccc FREE STORAGE REQUEST
FAILED
Explanation
Explanation The user ID field in the logon panel is missing.
The free storage request has failed in module cccccccc.

System action
System action OMEGAMON redisplays the logon panel.
The task stops.

User response
User response Enter the required user ID.
Examine the error code in the SYSLOG. If the problem OB1402 MISSING PASSWORD
persists, contact IBM Software Support.

The password field in the logon panel is missing. Enter appropriate data in the command argument
field.
System action OB1502 INSUFFICIENT MEMORY FOR
OMEGAMON redisplays the logon panel. SCRN COMMAND

Enter your password. OMEGAMON does not have sufficient memory to
build the screen member name lists from the various
OB1404 RE-ENTER NEW PASSWORD FOR sources (main storage, OBPROC, and RKOMPCSV) that
VERIFICATION the SCRN command displays.

The system asks the user to re-enter the new OMEGAMON does not process the command.
password.
User response
System action
Provide additional storage resources for the executing
The system waits for the user to re-enter the new OMEGAMON.
password to verify that the new password is correct.
OB1503 DATASET EMPTY
User response
Explanation
Enter the new password in the new password field.
There were no members in the indicated OBPROC data
OB1405 VERIFICATION OF NEW set for the SCRN command to display.
PASSWORD FAILED
System action
Explanation
The SCRN command displays member names in the
When the password was entered a second time for other OBPROC datasets.
verification, it did not match the new password.
User response
System action
The system waits for the user to attempt another
logon. OB1504 NO MEMBERS FOUND WITHIN
RANGE (cccccccc THRU cccccccc)
User response
Explanation
Enter the correct password.
OMEGAMON found no screen names within the from/
OB1501 INVALID ARGUMENT: cc through range specified by the SCRN command.

The argument field contains invalid data for the None.
command that appears for this message on the screen.
User response
System action
Enter a different from/through selection range.
OMEGAMON does not process the command.
OB1505 TOO MANY MEMBERS SPECIFIED

There are too many screen space members for The command executes.
the LSCR command to load into main storage. The
maximum number is 62. User response
System action
OMEGAMON does not load the screen spaces into OB1509 ENTER MEMBER NAMES TO LOAD
main storage.
Explanation
User response The LSCR command attempted to load screen spaces
Reduce the number of members to load. to main storage, but there were no member names
specified.
OB1506 INVALID MEMBER NAME cccccccc
System action
Explanation
The command stops.
The LSCR command detected a screen member name
that is too long or that contains invalid characters. User response
Enter member names following the LSCR command.
System action
OMEGAMON does not load the screen into main OB1521 MEMBER cccccccc DELETED
storage. BOTH IN-STORAGE AND FROM
RKOMPCSV
User response
Explanation
Correct the screen member name on the LSCR
command. The user specified screen space cccccccc with a DELTB
command, and OMEGAMON successfully deleted it
OB1507 LOAD FAILED - MEMBER cccccccc from main storage (in-storage) and RKOMPCSV.
NOT FOUND
System action
Explanation
The user specified screen space cccccccc with an LSCR
command; OMEGAMON did not find it in the OBPROC User response
library.
System action OB1522 MEMBER NAME - cccccccc NOT
OMEGAMON ignores specification of screen space FOUND IN-STORAGE
cccccccc and loads any other specified screen spaces.
Explanation
User response The user specified screen space cccccccc with a DELTI
Make sure that the specified screen space exists or DELTB command; OMEGAMON did not find it in
in OBPROC or RKOMPCSV library. Check OBPROC main storage (in-storage).
concatenation.
System action
OB1508 nnn MEMBERS LOADED
None.
Explanation
User response
The LSCR command successfully loaded nnn screen
spaces to main storage. Verify that the screen space name is correct.

OB1523 MEMBER cccccccc DELETED IN- renamed it to newname in main storage (in-storage)
STORAGE and in RKOMPCSV.

OMEGAMON successfully deleted screen space The command executes.
cccccccc from main storage (in-storage) as a result of
DELTB or DELTI command. User response
System action
OB1532 MEMBER NAME - cccccccc NOT
FOUND IN-STORAGE
User response
Explanation
The user specified screen space cccccccc with a
OB1524 MEMBER cccccccc DELETED FROM RENMI or RENMB command; OMEGAMON did not find
RKOMPCSV it in main storage (in-storage).

OMEGAMON successfully deleted screen space None.
cccccccc from RKOMPCSV as a result of DELTB or
DELTD command. User response
Verify that the screen space name is correct.
System action
OB1533 MEMBER oldname RENAMED TO
newnameIN-STORAGE
User response
Explanation
OMEGAMON successfully renamed screen space
OB1525 DELETE FAILED - cccccccc NOT oldname to newname in main storage (in-storage) as
FOUND IN RKOMPCSV a result of RENMI or RENMB command.

The user specified screen space cccccccc with a DELTB The command executes.
or DELTD command, and OMEGAMON did not find it in
RKOMPCSV. User response
System action
OB1534 MEMBER oldname RENAMED TO
None.
newname IN RKOMPCSV
User response
Explanation
OMEGAMON successfully renamed screen space
OB1531 MEMBER oldname RENAMED TO oldname to newname in RKOMPCSV as a result of a
newname BOTH IN-STORAGE AND RENMD or RENMB command.
IN RKOMPCSV
System action
Explanation The command executes.
The user specified screen space oldname with a
RENMB command, and OMEGAMON successfully

None. This is an informational message only. The user issued a RENMD or RENMB command with
a screen space name cccccccc that already exists in
OB1535 RENAME FAILED - cccccccc NOT RKOMPCSV and cannot be renamed.
FOUND IN RKOMPCSV
System action
Explanation
OMEGAMON does not change the original screen
The user specified screen space cccccccc on a RENMD space name.
or RENMB command, and OMEGAMON did not find it in
main storage (in-storage).
User response
System action Correct the new screen space name and retry the
command.
None.
OB2001 DATA-ONLY SPACE cccccccc DOES
User response NOT EXIST

Explanation
OB1537 RENAME FAILED - cccccccc The data-only space cccccccc specified in the
DIRECTORY FULL command cannot be found. cccccccc is the name of
the data-only space or the first 1–7 characters of the
Explanation data-only space name. If cccccccc is displayed in the
message as less than 8 characters, it means that there
The PDS directory for file cccccccc is full and cannot
were no data-only spaces found beginning with the
contain additional screen space names.
characters cccccccc.

OMEGAMON does not rename the screen space in
RKOMPCSV.
User response
User response
Correct the data-only space name and reissue the
Compress the PDS library or provide additional
command. The PEEK command may be used to find
directory space.
the names of data-only spaces owned by a job.
OB1538 RENAME FAILED - cccccccc
OB2002 DATA-ONLY SPACE cccccccc IS
ALREADY EXISTS IN-STORAGE
NOT OWNED BY JOB aaaaaaaa
The user issued a RENMI or RENMB command with
Job aaaaaaaa is not the owner of data-only space
a screen space name cccccccc that already exists in
cccccccc. aaaaaaaa is the jobname given in the
main storage (in-storage) and cannot be renamed.
command or the name of the job identified by the
ASID.
System action
OMEGAMON does not change the original screen System action
space name.
The command stops.

Correct the new screen space name and retry the
Correct the data-only space name, the jobname, or
command.
ASID and reissue the command. The PEEK command
OB1539 RENAME FAILED - cccccccc may be used to find the names of data-only spaces
ALREADY EXISTS IN RKOMPCSV owned by a job’s TCBs. The OSPC command may be

used to find the jobname and ASID of the owning TCB Explanation
of a data-only space.
A data-only space command (e.g., SLST, SZAP) was
OB2003 aaaaaaaa cccccccc HAS BEEN issued without the name of a data-only space as input.
DELETED
System action
Explanation
The command stops.
The TCB owning data-only space aaaaaaaa of type
cccccccc has deleted the space or has itself been
terminated. The space no longer exists.
User response
Correct the command input by supplying a data-only
System action space name as the second parameter. The OSPC
command may be issued to obtain the name of all
The command is terminated. data-only spaces in the system.
OB2008 ALESERV ADD NON-ZERO RETURN
User response CODE, RC = nn
None.
OB2005 DATA-ONLY SPACE PROCESSING
Explanation
UNAVAILABLE - RC=nnnn An attempt to obtain addressability to a data space
failed with return code nn.
Explanation
Due to an internal OMEGAMON error, OMEGAMON is
System action
unable to perform data-only space processing. The command stops.

The command stops. Ensure that the data space input to the affected
command has not been deleted. If the data space still
User response exists, contact IBM Software Support.
Contact IBM Software Support with the return code. OB2009 HSPSERV return code, RC = xx
OB2006 DATA-ONLY SPACE NAME MUST BE

8 CHARACTERS OR LESS
Explanation
An attempt to access a Hiperspace™ failed with the xx
Explanation return code.
A data-only space name of greater than 8 characters

was entered as input.
System action
The command stops.
System action
The command stops.
User response
User response OB2010 ACCESS TO aaaaaaaaaa cccccccc
Correct the name of the data-only space. The OSPC IS NOT AUTHORIZED
command may be issued to obtain the name of all
data-only spaces in the system. Explanation
OB2007 DATA-ONLY SPACE NAME IS A An attempt was made to access a nonshareable
REQUIRED PARAMETER data-only space aaaaaaaa of type cccccccc without
authorization.

The command stops. Check to make sure that the correct RMF level is
entered on the input screen. If it is entered correctly
User response but OMEGAMON does not recognize it, contact IBM
Software Support. You may need to receive support for
Authorization may be obtained to non-shareable data- a new level of RMF.
only spaces by issuing the command .DSAON.
OB2102 INPUT MUST BE EITHER nnn OR
OB2011 ACCESS TO DATA SPACE aaaaaaaa n.n.n
DENIED, SCOPE UNKNOWN
Explanation
Explanation
The operand on the RMFS command must have the
An attempt was made to access data space aaaaaaaa, format nnn or n.n.n.
but OMEGAMON was not able to determine the SCOPE
of the data space.
System action
System action The command stops.
The command stops.

User response
User response Correct the input to the RMFS command and press
ENTER.
OB2103 RMF LEVEL HAS BEEN
OB2100 RMF SUBROUTINE LOAD MODULE DYNAMICALLY DETERMINED -
OBRMFSnn NOT AVAILABLE COMMAND INVALID
OMEGAMON attempted to access module OBRMFSnn OMEGAMON determined the level of RMF dynamically.
but failed. RMFS cannot be used to override the RMF level in this
situation.
System action
System action
The command stops.
The command stops.
User response
User response
Check to make sure that the OBRMFSnn modules were
copied from the OMEGAMON distribution tape. If the None. This is an informational message only.
modules are in the OMEGAMON load library, contact
IBM Software Support. OB2104 RMF LEVEL UNCHANGED -
UNABLE TO LOAD MODULE
OB2101 RMF LEVEL nnnnn IS NOT IN nnnnnnnn
TABLE
Explanation
Explanation
An attempt was made to change to a new level of RMF,
An attempt was made to set the RMF level to a level however, the required load module was not available.
that OMEGAMON did not recognize.
System action
System action
The command stops. The RMF level stays unchanged.
The command stops.

Make sure that the load module is copied from the Activate the subsystem.
installation tape. If the module is not on the tape,
OB2202 CN SUBSYSTEM NOT DEFINED.
STATIC DEVICE TABLE IS USED
OB2200 SUBSYSTEM aaaa REQUEST
RETURNED RC=bbbb AND Explanation
ERRCODE cccccccc
The interface to the subsystem determined that the
subsystem is not defined.
Explanation
A call to the subsystem has resulted in a non-zero System action
return code.
The interface to the subsystem returns the address of
aaaa
the static device table that might be obsolete.
Identifies the type of request: INIT or REQ.
bbbb
Identifies the return code.
User response
4 Define the Candle Subsystem.
Internal error OB2203 SSCVT CHAIN NOT VALID. STATIC
A common cause of this return code is a version DEVICE TABLE IS USED
or maintenance level mismatch between the running
subsystem and the product issuing the message. If Explanation
you have multiple SMP/E environments make sure
that all have the same Candle subsystem FMID and The interface to the subsystem determined that the
maintenance installed. SSCVT chain is not valid.
8
Subsystem not active System action
20 The interface to the subsystem returns the address of
Subsystem module not found the static device table that might be obsolete.
cccccccc
Identifies the error code. User response
Define the subsystem and IPL the system.
System action
OB2204 CNSS INTERFACE MODULE NOT
The interface to the subsystem returns the address of FOUND. STATIC DEVICE TABLE IS
the static device table that might be obsolete. You may USED
also need a later version of the subsystem.
Explanation
User response
The interface to the subsystem cannot load the
Contact IBM Software Support. subsystem interface module (KCNDLI).
OB2201 CN SUBSYSTEM INACTIVE. STATIC
DEVICE TABLE IS USED System action
Explanation the static device table that might be obsolete.
subsystem is inactive. User response
Ensure that OMEGAMON can access the subsystem
System action interface module through STEPLIB, JOBLIB, LINKLST
or LPALST concatenation.
the static device table that might be obsolete. OB2205 CONFIGURATION CHANGE
PENDING

The interface to the subsystem determined that The command stops.
configuration change is pending.
User response
System action
Increase the region size and retry.
dynamic device table. OB4222 UNABLE TO LOCATE REQUIRED
LEVEL-DEPENDENT BASE MODULE
KOBASnnn
User response
None. Explanation
OB2206 DYNAMIC DEVICE TABLE IS OMEGAMON attempted to locate the corresponding
OBSOLETE base module required for the current operating system
level. The required module could not be found.
Explanation
System action
dynamic device table is obsolete. OMEGAMON stops.

The interface to the subsystem returns the address of Make sure that OMEGAMON is executed at the
the dynamic device table. operating system level for which your installation is
licensed. Contact IBM Corporation for licensing and
User response sales information.
Reissue command causing such a message. OB4223 CURRENT OPERATING SYSTEM

LEVEL NOT SUPPORTED
OB2207 FUNCTION aaaa IS NOT
AVAILABLE RC=bbbb
Explanation
Explanation OMEGAMON has determined that the current
operating system level is not supported. Only MVS/SP™
A call to a function residing in the subsystem resulted 1, 2, and 3 are supported; earlier versions are not
in nonzero return code. supported. (SP™ 1 support is further limited to SP 1.3
and higher.)
aaaa
Identifies the function: DIOC.
bbbb System action
Identifies the return code. OMEGAMON stops.

The interface to the subsystem returns the address of Run OMEGAMON only on those systems with
the static device table that might be obsolete. supported operating system levels.
OB7001 OVUSERcc DATA FILE NOT FOUND
User response
OB4101 MEMORY FOR USER PROFILE The OVUSERcc DATA file specified by USER xx in the
TABLES NOT AVAILABLE startup parms or the .USR command was not found.

There is not enough memory available for the user OMEGAMON uses all default values for execution
profile tables. parameters. The default OVUSER DATA file is 99.

Continue with OMEGAMON initialization or restart An invalid character was found in the input stream.
OMEGAMON specifying the correct USER startup
parameter value, or reissue the .USR command System action
specifying the correct parameter.
The character is assumed to be a delimiter.
OB7002 INVALID SWITCH SETTING - MUST
BE ON OR OFF
User response
Explanation Enter a valid character if a delimiter was not intended.
The indicated parameter must be specified as either OB7006 INVALID KEYWORD
ON or OFF.
Explanation
System action
The indicated word is not a valid keyword for the
OMEGAMON uses the default value. current parameter group being processed.

Correct the parameter value to specify ON or OFF at OMEGAMON ignores the keyword.
next execution.
OB7003 INVALID PARAMETER User response
Check for possible spelling or continuation errors.
Explanation
OB7007 INVALID KEYWORD VALUE
The indicated word is not a valid OMEGAMON startup
parameter. Explanation
The value specified for the indicated parameter
System action
keyword is invalid.
OMEGAMON ignores the entire parameter group
(including any possible subordinate keywords). System action
OMEGAMON ignores the keyword.
User response
Check for spelling problems. Check to make sure that User response
a previous parameter was not continued incorrectly.
Specify the keyword value as required.
OB7004 INVALID SYNTAX
OB7008 INVALID HEX DATA
Explanation
Explanation
The format of the indicated input stream is invalid.
EBCDIC characters were specified for a keyword
requiring hexadecimal data.
System action
OMEGAMON ignores either all or part of the current System action
parameter group.
User response
User response
Correct the formatting error. Ensure that all required
delimiters (commas, parentheses, and so on) are Correct the keyword value.
entered correctly.
OB7009 INVALID NUMERIC DATA
OB7005 INVALID CHARACTER - ACCEPTED
AS DELIMITER

EBCDIC characters were specified for a keyword Remove or correct the duplicate keyword.
requiring numeric data.
OB7013 MISSVM LIMIT EXCEEDED
System action
Explanation
The internal buffers required to hold the data specified
by the OVUSER MISSVM parameter have overflowed.
User response
Correct the keyword value. System action
OB7010 KEYWORD VALUE OR LENGTH The MISSVM keyword specifications that will fit in
BELOW ALLOWED MIN storage will be accepted with the remainder ignored.

The value specified for the indicated keyword is either Increase the virtual storage size of the OMEGAMON for
too short (character) or too small (integer or hex). VM virtual machine or specify few MISSVM keyword
values.
System action OB7014 MISSDA LIMIT EXCEEDED
Explanation
User response The internal buffers required to hold the data specified
Check the minimum that can be specified for the by the OVUSER MISSDA parameter have overflowed.
keyword and correct the keyword value.
System action
OB7011 KEYWORD VALUE OR LENGTH
ABOVE ALLOWED MAX The MISSDA keyword specifications that will fit in
storage will be accepted with the remainder ignored.
Explanation
User response
The value specified for the indicated keyword is either
too long (character) or too large (integer or hex). Increase the virtual storage size of the OMEGAMON
for VM virtual machine or specify few MISSDA keyword
System action values.
OMEGAMON ignores the keyword. OB7017 USERID OR ACCOUNT NOT

SPECIFIED
User response
Explanation
Check the maximum that can be specified for the
keyword and correct the keyword value. For the PGNAMES parameter a USERID= or
ACCOUNT= keyword was expected and not found.
OB7012 DUPLICATE PARAMETER
System action
Explanation
OMEGAMON ignores the entire PGNAMES parameter
A duplicate keyword has been found in the input group.
stream.
User response
System action
Check for a spelling error to ensure that either a
OMEGAMON ignores the duplicate parameter. USERID= or an ACCOUNT= keyword is specified.
OB7018 UNEXPECTED END-OF-FILE
RECEIVED

While processing a continuation, the end of the Remove less important performance groups so that
OVUSERcc DATA file was reached. the maximum will not be exceeded.
OB7022 INVALID cccccccc THRESHOLD
System action GROUP KEYWORD
OVUSERcc parameter processing stops.
Explanation
User response A keyword for the DEFVMTG, DASDTG, or RSCSTG
Check to see if the OVUSER DATA file is complete. If parameter was entered that is not a valid exception
not, enter the missing parameter keyword(s). override name.
OB7019 NAME= KEYWORD MISSING

System action
Explanation OMEGAMON ignores the keyword.
The NAME keyword was not specified on the PGNAME

User response
statement.
Check for a possible spelling error. For DEFVMTG,
System action ensure that the exception name entered is a valid VM
exception and not a SYSTEM exception. For DASDTG,
OMEGAMON ignores the entry. ensure that the exception name entered is one of
the DASD exceptions. For RSCSTG, ensure that the
User response exception name entered is RSCA or RSCQ.
The PGNAME statement requires a name for each OB7023 ON/OFF EXPECTED, ON ASSUMED
group being defined. Specify a name.
Explanation
OB7020 UNBALANCED OR INVALID USE OF
PARENTHESES The indicated parameter must be specified as either
ON or OFF.
Explanation
System action
Either an unexpected parenthesis was detected or an
expected parenthesis was not detected. The keyword value defaults to ON.

OMEGAMON ignores either the current keyword or the Correct the parameter value to specify ON or OFF.
remaining parameter keywords.
OB7024 EXPECTED PARENTHESIS NOT
FOUND
User response
Add or remove parentheses as required. Explanation
OB7021 MAXIMUM 64 PERFORMANCE A parenthesis was expected at or near the column
GROUP NAMES ALLOWED indicated by an asterisk.

For the PGNAMES parameter group more than 64 OMEGAMON ignores the current keyword.
performance groups were specified.
User response
System action
Check the format for the keyword and make the
OMEGAMON ignores the remaining performance appropriate corrections.
groups.

OB7025 EXPECTED ON OR AUTO, AUTO Explanation
ASSUMED
An invalid keyword was received for the TSF parameter
group. The only valid keywords are TIME=, and either
Explanation SS= or SL=.
The indicated parameter must be specified as either
ON or AUTO. System action
OMEGAMON ignores the remaining TSF keywords.
System action
Missing VM analysis for this VM user ID defaults to User response
AUTO.
Check for possible spelling problems.
User response OB7029 BOX= KEYWORD INVALID FOR

VM EXCEPTIONS. ENTER OK TO
Correct the parameter value to specify ON or AUTO. CONTINUE OR C TO CANCEL.
OB7026 THRESHOLD EXCEEDS THE
MAXIMUM ALLOWED, MAXIMUM Explanation
WILL BE USED
The BOX= keyword was specified and is not valid for a
VM exception.
Explanation
The value specified for the THRESH= keyword is larger System action
than the value allowed for an exception name.
OMEGAMON ignores the BOX= keyword.
System action
User response
OMEGAMON uses the maximum value allowed.
Reply OK or C, then remove the BOX= keyword from
this exception.
User response
OB7030 CHNM CPUID INVALID
Check the maximum value for this exception name and
correct the keyword value.
Explanation
OB7027 THRESHOLD LESS THAN
MINIMUM ALLOWED, MINIMUM The value specified for the CPUID= keyword is invalid
WILL BE USED (must be between 0 and 15) for the CHNM parameter
group.
Explanation
System action
The value specified for the THRESH= keyword is less
than the value allowed for an exception name. OMEGAMON skips the CPUID= keyword and
subsequent CHANNELS= keywords.
System action
User response
OMEGAMON uses the minimum value allowed.
Specify the correct CPU identification.
User response OB7031 CHNM CHANNEL NUMBER

INVALID
Check the minimum value for this exception name and
correct the keyword value.
Explanation
OB7028 EXPECTED TIME=SS OR SL=
KEYWORD NOT RECEIVED One of the values specified for the CHANNELS=
keywords is invalid for the CHNM parameter group
(must be between 0 and 31).

OMEGAMON ignores the channel ID value. OMEGAMON requires either an INCLUDE or EXCLUDE
list to be specified with the FORCE parameter in
User response OVUSER.
Specify the correct channel ID.

System action
OB7032 CPUID= KEYWORD MISSING OMEGAMON displays the message and asks if you
wish to continue.
Explanation
The CPUID= keyword for the CHNM parameter group User response
was expected and not received. Reply OK to continue processing and ignore the error
or type C to cancel and correct the OVUSER file.
System action
OB7038 FORCE PARAMETER VALID ONLY
OMEGAMON ignores the subsequent CHANNELS= FOR VM EXCEPTIONS
parameter.
Explanation
User response
OMEGAMON encountered the FORCE parameter on
Check for spelling errors or enter a CPUID= keyword an exception that is not VM user-related. Force
preceding the CHANNELS= keyword. processing is not valid for other than user-related
exceptions.
OB7033 CHANNELS= KEYWORD MISSING
System action
Explanation
OMEGAMON displays the message and asks if you
The CHANNELS= keyword for the CHNM parameter
wish to continue.
group was expected and not received.
User response
System action
Reply OK to continue processing and ignore the error
OMEGAMON ignores the current CPUID= value.
User response OB7039 SCREEN SPACE NOT FOUND
Check for spelling errors or enter a CHANNELS=

Explanation
keyword following the CPUID= keyword.
The indicated screen space name (with file type
OB7036 DUPLICATE KEYWORD FOUND
PROCFILE) was not found on any accessed CMS disk.

OMEGAMON encountered a duplicate keyword in
The screen space name is accepted. The error
OVUSER.
message displays as a warning.

OMEGAMON displays the message and asks if you
Correct the screen space name or create a new screen
wish to continue.
space with this name.
User response OB7040 TABLE WORK AREA OVERFLOW
Reply OK to continue processing and ignore the error

Explanation
An internal storage buffer overflowed processing the
OB7037 INCLUDE OR EXCLUDE NOT
indicated parameter or keyword.l
SPECIFIED

Processing stops for the current parameter. OMEGAMON deleted the user table.

Increase your virtual storage size or decrease the Processing continues.
number of operands of this parameter.
OB7041 INTERNAL ERROR OBTAINING User response
WORK BUFFERS None. This is an informational message only.
OB7103 NAME NOT IN TABLE
Explanation
An internal error occurred attempting to acquire Explanation
storage.
The requested name cannot be found in the tables.
System action
System action
OVUSERcc processing stops.
The command stops.
User response
User response
Call IBM Software Support Services.
Correct the name and retry the command.
OB7042 KEYWORD DOES NOT APPLY TO
THIS EXCEPTION OB7104 cccccccc HAS BEEN DELETED
The indicated keyword does not pertain to the current The indicated memory location symbol was deleted
exception name being processed. from the symbolic address table.

OMEGAMON ignores the keyword. Processing continues.

Remove the keyword from this exception parameter. None. This is an informational message only.
OB7101 ERROR, COMMAND ARGUMENT OB7105 cccccccc HAS BEEN ADDED TO THE
UNKNOWN TABLE
An invalid operand was given to the command. The indicated memory location symbol was added to
the symbolic address table.
System action
System action
The command stops.
User response
User response
For the proper operands, see the extended help
(;commandname) for the command. Correct the None. This is an informational message only.
operand and retry.
OB7106 TABLE DOES NOT EXIST
OB7102 USER TABLE HAS BEEN DELETED

No entries have been defined in the table. OMEGAMON successfully executed the MZAP
command.
System action
System action
The command stops.
User response
User response
OB7107 WORKAREA OVERFLOW
OB7111 VERIFY REJECT - MEMORY NOT
Explanation ZAPPED
The internal work area for string manipulation has

Explanation
overflowed.
The verify data in the command does not match the
System action data in storage.
The command stops.

System action
User response The command stops.
Use shorter strings to define the storage locations.

User response
OB7108 PLPA MZAP CANNOT CROSS PAGE Correct the data and retry.
BOUNDARY
OB7112 SCAN DATA NOT FOUND
Explanation
Explanation
The zap would cross a page boundary and this is not
allowed. The requested data could not be found within the scan
limits.
System action
System action
Command stops.
The command stops.
User response
User response
OB7109 PLPA PAGES FIXED
OB7113 DYNAMIC ADDRESS NOT
Explanation RESOLVED
OMEGAMON fixed PLPA pages as requested.

Explanation
System action A symbol in a dynamic address string could not be
resolved.
System action
User response
The command stops.
OB7110 MEMORY ZAP SUCCESSFUL User response
Correct the symbol and retry the command.

OB7114 MODULE NOT AVAILABLE User response
Correct the name and retry.
Explanation
OB7119 REGION DOES NOT BELONG
An OMEGAMON module address was found to be 0, TO CL/SUPERSESSION and
indicating that it is not available for this command. CL\GATEWAY

The command stops. A cross-memory zap was attempted on an
unauthorized region.
User response
OB7115 OMEGAMON NAME INVALID IN The command stops.
CROSS MEMORY
User response
Explanation Make sure that the zap is being applied to the correct
The cross memory commands are not allowed against region.
this address space. OB7120 USE cccc FOR OMEGAMON
PRIVATE AREA
System action
A cross memory command was used where a local
User response command is appropriate.
Use the appropriate local commands.

System action
OB7117 INDIRECT ADDRESS IS 0
The command stops.
Explanation
User response
The address pointer value was 0 when an indirect
request (? or %) was encountered while interpreting Use the local command format.
the address string. OB7121 ADDRESS IN COMMON AREA - USE
cccc
System action
A cross memory command was used where a local
User response command is appropriate.
None. This is not necessarily an error.

System action
OB7118 JOB NOT FOUND
The command stops.
Explanation
User response
The requested address space or jobname cannot be
found. Use the local command format.
OB7122 GENERATED ADDRESS INVALID -
System action xxxxxxxx
The command stops.

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

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

OB8115 WARNING - INVALID RETURN User response
CODE - RC = nn
Explanation OB8121 CHANNEL SET NOT DEFINED
The SRB routine returned a nonstandard code.

Explanation
System action The user requested an invalid channel set.
The PEEK process stops.

System action
User response Command processing stops.
If the error persists, contact IBM Software Support.

User response
OB8116 DANGER - INSUFFICIENT SQA,
COMMAND ABORTED Correct command parameters and retry.
OB8130 COMMAND TEXT IS TOO LONG
Explanation
There is insufficient SQA. Explanation
The command text can be a maximum of 126
System action characters.
The command aborts.

System action
User response The command is not executed.
Try the command later when more SQA is available.

User response
OB8117 INSUFFICIENT MEMORY FOR SRB
SAVE AREA Specify the command text so that it is no more than
126 characters.
Explanation OB8131 INVALID CHARACTER AFTER

SYSTEM NAME
There is insufficient memory for the save area.
Explanation
System action
The system name was not followed by a blank space or
The command stops. by a comma.

Try the command later when there is more memory The command is not executed.
available.
OB8118 SRBD - SRB FAILED DURING User response
INITIALIZATION
Supply a system name followed by a blank space or a
comma.
Explanation
OB8132 SYSTEM NAME IS TOO LONG,
The SRB failed during initialization. MUST BE 1–8 CHARS

The command stops. System names must be from 1–8 characters in length.

The command is not executed. An invalid device class was entered as input to the
GLST command.
User response
System action
Supply a valid system name.
The GLST command is terminated.
OB8202 CPU NOT DEFINED
User response
Explanation
Correct the invalid input parameter. The help text
The CPU is not defined in the PCCA. for the GLST command displays the valid input
parameters.
System action
OB8206 PROCESSING ERROR, DEVICE
None. CLASS aaaa, RC=nn

Specify a CPU that is defined to your system (see The EDTINFO interface routine used by the GLST
the IBM OS/VS2 System Programming Library or MVS/ command returned with a non-zero return code, nn,
Extended Architecture Debugging Handbooks for a processing device class aaaa.
CPU definition).
OB8203 NO CHANNEL AVAILABILITY System action
TABLE
Processing continues, but that device class will not be
displayed.
Explanation
The specified channel does not exist. User response
System action
OB8207 SUBSYSTEM RETURN CODE
None. aaaaaaaa bbbbbbbb cccccccc
dddddddd
User response
Explanation
Specify a channel number that exists on the system.
A call to the subsystem has resulted in a nonzero
OB8204 LINK ERROR, CODE = {8|12}
return code during execution of the GDEV command.
aaaaaaaa
Explanation
Identifies the Subsystem return code.
The external routine for GDEV encountered a link error. bbbbbbbb
Identifies the function return code.
The command stops processing. Identifies the subroutine invocation return code.
dddddddd
User response Identifies the subroutine invocation reason code.

System action
OB8205 INVALID INPUT -
The GDEV command continues to process, however,
aaaaaaaaaaaaaaa
there will be no data for devices defined as dynamic.
User response

OB8208 CN SUBSYSTEM NOT INITIALIZED OB8280 CONSOLE NOT FOUND
A contact to the subsystem cannot be made because The console ID or device address specified located a
the subsystem has not been initialized by this type of device other than a console.
OMEGAMON session.
System action
System action
None.
The GDEV command continues to process, however,
there will be no data for devices defined as dynamic. User response
Specify a valid console ID or device address.
User response
OB8281 HARDCOPY DEVICE
Check to see that the subsystem is running on the
system. If it is not running, start it. If it is running,
contact IBM Software Support. Explanation
OB8209 UCB INFORMATION UNAVAIABLE. The console specified in the CONS command is a
RC=xxxxxxxx yyyyyyyy zzzzzzzz hardcopy device and therefore cannot be monitored.

A call to internal OMEGAMON service to obtain UCB The command stops processing.
information resulted in a nonzero return code.
xxxxxxxx User response
Register 15 contains the return code. Select a non-hardcopy device to monitor.
yyyyyyyy
Register 0 contains the reason code. OB8282 INVALID CONSOLE NAME, MUST
BE 2–8 CHARS
zzzzzzzz
Register 1 contains the associated reason code.
Explanation
System action Console names must be from 2–8 characters. The first
character must be A–Z, @, #, or $, and subsequent
The OMEGAMON command is terminated. characters must be A–Z, @, #, $, or 0–9.

Contact IBM Software Support. The command is not executed.
OB8277 SYNTAX ERROR NEAR COLUMN
FLAGGED ABOVE User response
Supply a valid console name or console ID number.
Explanation
OB8283 INVALID CONSOLE ID NUMBER,
A syntax error was found in the input command line. MUST BE 1–99
An asterisk (*) marks the start of the invalid field.
Explanation
System action
Console ID numbers must be from 1–99.
None.
System action
User response
The command is not executed.
Verify the command syntax, correct the input as
needed, and retry the command.

Supply a valid console ID number or console name. The command stops processing.
OB8284 MISSING CONSOLE VALUE
User response
Explanation Increase the number of slots to more than nnnnn.
Either a console name or console ID number must be OB8288 NO ONLINE DEVICES FOUND
supplied after the CONS= keyword. WITH THIS GENERIC

The command is not executed. No online devices match the generic name specified.

Supply a valid console name or console ID number. The command stops processing.
OB8285 INVALID CHARACTER AFTER
CONSOLE VALUE User response
Try another generic name.
Explanation
OB8289 DLIST OFFSET GREATER THAN
The console name or console ID number was not DLIST TABLE
followed by a blank space or by a comma.
Explanation
System action
The DLIST offset calculation is greater than that
The command is not executed. allowed in the DLIST table.

Supply a valid console name or console ID number, The command stops processing.
followed by a blank space or a comma.
OB8286 CONSOLE DOES NOT EXIST OR IS User response
INACTIVE Contact IBM Software Support.
OB8290 NO GENERIC DEVICE NAME
Explanation
SUPPLIED
The console specified is not defined to the operating
system, or is defined but not active. Explanation
A generic device name was expected.
System action
The command is not executed. System action
User response
Supply a valid console name or console ID number. User response
OB8287 INCREASE GDEV UCB SLOTS TO Enter a generic device name. Use the GLST device
MORE THAN nnnnn major command to list valid generic names for your
site.
Explanation
OB8291 NO GENERIC DEVICES DEFINED
OMEGAMON needs more than nnnnn slots for GDEV FOR THIS NAME
command UCBs.

No devices were defined for the generic name Specify an online disk or tape.
specified.
OB8295 IGNORED - DEVICE IS
PERMANENTLY RESIDENT
System action
An attempt was made to deallocate a permanently
User response resident volume.
Enter a different generic device name.
System action
OB8292 GENERIC DEVICE NAME TOO
LONG None.

A generic device name must be 8 characters or less. Specify a volume that is not permanently resident.
OB8296 IGNORED - DEVICE NOT
System action PERMANENTLY RESIDENT
Explanation
User response An attempt was made to mark a device reserved that
Enter a valid device name with 8 characters or less. was not permanently resident.
OB8293 NO MATCH FOUND FOR THIS

System action
GENERIC NAME
None.
Explanation
User response
The generic device name specified is not defined at
your installation. Specify a volume that is permanently resident.
OB8310 JOB NOT FOUND
System action
The requested jobname could not be found in the
User response queue of currently running jobs.
Use the GLST device major command to list all defined
generic device names. System action
OB8294 IGNORED - DEVICE NOT The PEEK command is suppressed.
ALLOCATED, ONLINE DASD OR
TAPE User response
Correct the jobname.
Explanation
OB8312 “PEEK” COMMAND NOT
An attempt was made to deallocate a device that was
either offline or was not a disk/tape. SUCCESSFULLY EXECUTED

An error prevented the PEEK command from
None.
executing.

The PEEK command is suppressed. The indicated DD statement is missing from the job’s
JCL.
User response
System action
Observe prior error messages and take appropriate
action. The command stops processing.
OB8313 NO cccc INFORMATION
AVAILABLE FOR *MAIN* User response
ADDRESS SPACE Add the statement and restart OMEGAMON.
OB8323 NOT IN AUTOMATIC MODE -
Explanation
RETURN IGNORED
The control blocks necessary to map virtual storage
for the *MAIN* address space using the cccc minor of Explanation
PEEK are incomplete or absent.
The command is valid only in automatic mode.
System action
System action
The command stops processing without taking action.
User response
User response
None. These commands are not supported for the
*MAIN* address space. Correct the command or use only in automatic mode.
OB8320 RETURN FETCH DELAYED OB8324 NO TARGET SCREEN SPACE
The return was delayed due to a cycle count in the The target screen space name is missing.
command label.
System action
System action
The command continues normally.
User response
User response
Supply a correct name and retry the command.
OB8325 ENTRY DOES NOT EXIST - MUST
OB8321 RETURN FETCH PENDING BE ADDED TO OBUSERcc
A return is scheduled for the next cycle. A search of the currently active OBUSER module failed
to find the required entry.
System action
System action
None.
User response
User response
Check the name and verify the libraries.
OB8322 PROCFILE DD STATEMENT
MISSING OB8326 SCREEN SPACE cccccccc NOT
FOUND

The specified screen space name was not in OBPROC. To activate the new parameters, reset the log as
Either it is missing or the name is incorrect. indicated.
OB8601 LOG RESET FAILED. INVALID
System action cccccccc FIELD.
Explanation
User response The log reset failed because of the invalid field.
Correct the screen space name and verify the libraries.
Retry the command. System action
OB8327 INVALID VALUE cccccc FOR The log is not available.
KEYWORD aaaaaaSPECIFIED,
INPUT IGNORED User response
Look up dynamic allocation in the appropriate IBM
Explanation
manual and retry the reset command.
The value cccccc supplied for keyword aaaaaa is not
OB8602 LOG RESET FAILED. CODE
valid.
cccccccc,nnnn,xxxx
System action
Explanation
OMEGAMON ignores the invalid input and continues
processing. The log reset failed because of a bad return code from
the dynamic allocation routine. The variable cccccccc
is a return code. The variable nnnn is an error code.
User response The variable xxxx is an error reason code.
Correct the keyword value and retry the command.
System action
OB8501 XLF/TSF FUNCTIONS DISABLED
The log is not available.
Explanation
User response
The XLF/TSF functions are not available with this level
of OMEGAMON. Look up the dynamic allocation return code in the
appropriate IBM manual and retry the reset command.
System action OB8603 DDNAME NOT AVAILABLE.
The associated commands are inoperative. SYSOUT USED

Use a level of OMEGAMON that has these functions. The ddname specified is not allocated or is in use by
another session.
OB8551 LOG RESET REQUIRED.
USE .XLFOUT.
System action
Explanation The system used SYSOUT.
Changes made to the log file require that it be reset.

User response
System action If the ddname is not being used by another session,
correct the spelling or allocate the intended ddname
The command continues. and retry the reset command. If it is in use by
another session, use another ddname, wait for the
other session to be done, or accept the system use
of SYSOUT.

OB8604 LINE COUNT MUST BE NUMERIC User response
Remove the blank record from control record input.
Explanation Verify that the record was intentionally blank.
An attempt was made to enter a non-numeric line OB9004 INVALID CONTROL STATEMENT
count. FORMAT

The command stops processing. The syntax or the spelling of the control statement was
incorrect.
User response
Correct the line count value and reissue the command. System action
OB8605 LINE COUNT GREATER THAN 255 OMEGAMON ignores the control statement and
continues the edit and update.
Explanation
User response
An attempt was made to enter a line count greater
than the maximum of 255. Correct the syntax or spelling and resubmit the
statement.
System action OB9005 INVALID LEVEL NUMBER

SPECIFIED. PASSWORD IGNORED
Explanation
User response
OMEGAMON allows only level number 1, 2, or 3 as
Correct the line count value and reissue the command. valid level numbers for passwords.
OB9001 BAD OPEN ON CONTROL
STATEMENT FILE (SYSIN) System action
OMEGAMON ignores the control statement and
Explanation continues the edit and update.
This is probably the result of a missing SYSIN DD
statement in the JCL. User response
Correct the level number and resubmit the statement.
System action
OB9006 INVALID LEVEL NUMBER.
The update stops processing. OMEGAMON does not DEFAULT OF 0 ASSIGNED
process any updates.
Explanation
User response
You specified an invalid level number for a command.
Include a SYSIN DD statement in the job’s JCL and Valid level numbers are 0, 1, 2, or 3.
resubmit the job.
OB9003 BLANK CARD - IGNORED System action
OMEGAMON assigns a default level of 0 to the
Explanation command in question. OMEGAMON continues the edit
OMEGAMON encountered a blank card in the input and update.
stream.
User response
System action Correct the level number in the control statement and
OMEGAMON ignores the blank card and continues the resubmit it if it is other than 0.
edit and update. OB9007 INVALID KEYWORD SPECIFIED

Explanation OB9010 INVALID EXTERNAL VALUE
SPECIFIED. DEFAULT OF NO
The keyword specified does not exist or is not valid on ASSIGNED
this statement. (For example, VOLUME= is invalid on
a COMMAND statement, and LEVEL= is invalid on an
AUTHLIB statement.) Explanation
The security installation utility detected an invalid
System action value for the EXTERNAL= keyword.
continues the edit and update. System action
OMEGAMON assumes EXTERNAL=NO on this
User response statement and continues the edit and update.
Verify the keywords on the control statement to
make sure that they belong together. When you find User response
the error, correct it and resubmit the new control Correct the value of the EXTERNAL keyword, and
statements. resubmit the statement.
OB9008 LEVEL KEYWORD MUST BE OB9011 INTERNAL ERROR IN MESSAGE
SPECIFIED WITH PASSWORD. PROCESSING ROUTINE. NOTIFY
PASSWORD IGNORED CANDLE CORPORATION
OMEGAMON did not find the LEVEL= keyword. The OMEGAMON encountered an error in the message
PASSWORD statement requires a LEVEL= parameter to processing routine.
specify the password level.
System action
System action
The job stops processing.
User response
User response Record any console messages and contact IBM
Software Support.
Add a LEVEL= keyword to all PASSWORD= statements
and resubmit the job. OB9012 PASSWORD IS OF AN INVALID
LENGTH. MUST BE BETWEEN 1
OB9009 INVALID COMMAND LENGTH. AND 8 CHARACTERS
INFO-LINE COMMANDS MUST BE 1
THROUGH 8 CHARACTERS PLUS A
SLASH Explanation
The security installation utility detected a password
Explanation that is not 1–8 characters long.
The security installation utility detected an INFO-line
command that was longer than eight characters, not System action
including the slash (/). OMEGAMON ignores the control statement and
System action
OMEGAMON ignores the control statement and User response
continues the edit and update. Correct the length of the password and resubmit the
statement.
User response OB9013 IMPROPER LENGTH FOR DSNAME
Correct the command name and resubmit it.

The security installation utility detected a dataset You can only specify one password for a specific level
name of improper length. The dataset name for the number.
AUTHLIB keyword must follow the standard rules
for dataset names (no imbedded blanks or special System action
characters, and 44 or less characters in length).
System action
Make sure that you specified the correct level number
for this password. Correct and resubmit if necessary.
User response
Correct the dataset name and resubmit the statement. OB9017 INTERNAL ERROR DETECTED IN
UPDATE PROCESS. CONTACT IBM
OB9014 MAJOR AND MINOR COMMANDS CORP.
MUST BE 3 TO 4 CHARACTERS
LONG. STATEMENT IGNORED Explanation
OMEGAMON encountered an error in the security
Explanation
update program.
The security installation utility detected a major or
minor command that was not 3–4 characters long. System action
System action
User response OB9018 COMMAND NOT DEFINED
Correct the major or minor command name and
resubmit it. Explanation
OB9015 AUTHLIB ALREADY SPECIFIED. You specified an invalid major, minor, or INFO-line
STATEMENT IGNORED command name, or a command not supported under
this operating system.
Explanation
System action
The security installation utility detected more than
one AUTHLIB statement in this run. OMEGAMON only OMEGAMON ignores the control statement and
allows one AUTHLIB statement per update run. continues the edit and update.

OMEGAMON ignores the control statement and Check for spelling errors. Correct the command and
continues the edit and update. resubmit it.
OB9019 *** WARNING *** - UPDATE
User response CANCELLED
Make sure that the AUTHLIB statements OMEGAMON
found did not have conflicting information. Remove Explanation
extra AUTHLIB statements and resubmit if necessary.
This is usually the result of processing the
OB9016 PASSWORD FOR THIS LEVEL UPDATE=NO control statement. The message appears
NUMBER ALREADY SPECIFIED. after the end of the control statement input. If you
THIS PASSWORD IGNORED specified LIST=YES, the listing reflects the contents of

the security file as if the changes have already taken System action
place.
System action
User response
OMEGAMON cancels the update.
Verify that you are using a current level of
OMEGAMON.
User response
OB9023 INTERNAL ERROR IN LIST
None. This is an informational message only. ROUTINE. CONTACT IBM
OB9020 INVALID VOLUME SERIAL CORPORATION
NUMBER FORMAT
Explanation
Explanation OMEGAMON encountered an error in the security
OMEGAMON found an invalid volume serial number. update program.
A valid volume serial number or the characters
NOVOLUME are the only values OMEGAMON allows. System action
System action
User response OB9024 MULTIPLE UPDATE STATEMENTS

ENCOUNTERED. UPDATE
Correct the volume serial number and resubmit the CANCELLED
statement.
OB9021 INVALID VALUE SPECIFIED FOR Explanation
AUDIT KEYWORD. MUST BE “YES”
OR “NO” The security update utility found more than one
update control statement in this run. OMEGAMON only
allows one UPDATE= statement per run.
Explanation
The security installation utility detected an invalid System action
value for the AUDIT keyword. The AUDIT keyword only
accepts the values YES or NO. OMEGAMON continues the edit but cancels the
update.
System action
User response
continues the edit and update. Remove the extra update statements from the control
statement input.
User response OB9025 INVALID KEYWORD VALUE.

ACCEPTABLE VALUES ARE “YES”
Resubmit the statement specifying a valid value for the OR “NO”
AUDIT= keyword.
OB9022 WARNING—INVALID LEVEL Explanation
NUMBER FOUND IN COMMAND
TABLE FOR THIS COMMAND OMEGAMON received an invalid value for a specified
keyword. OMEGAMON only accepts the values YES or
NO.
Explanation
Security update was attempted on an OMEGAMON System action
version that does not support external security.

User response OB9029 “VOL=” KEYWORD MUST BE
SPECIFIED FOR AUTHLIB. ENTER
Correct the keyword value and resubmit the “VOL=NOVOLUME” IF NO VOLUME
statement. SERIAL NUMBER IS TO BE USED
OB9026 “LIST” STATEMENT ALREADY
SPECIFIED. STATEMENT IGNORED Explanation
OMEGAMON found no keyword for VOL=.
Explanation
The security update utility found more than one LIST System action
statement in this run.
System action
Resubmit with a volume serial number or
VOL=NOVOLUME if you do not want OMEGAMON to
User response perform volume serial number checking.
Remove the extra LIST= statements from the control OB9030 COMMAND TABLE IS INVALID.
statement input. SECURITY UPDATE PROGRAM
OB9027 ALIASES OF INFO-LINE (SLASH) TERMINATED
COMMANDS CANNOT BE
UPDATED. ACTUAL COMMAND Explanation
NAME MUST BE SPECIFIED
A security update was attempted on an OMEGAMON
version that does not support external security.
Explanation
When you protect an INFO-line command, System action
OMEGAMON also protects its aliases. You cannot
protect only an alias. The security file listing identifies The job stops processing.
the aliases.
User response
System action Verify that you are using a current level of
OMEGAMON ignores the control statement and OMEGAMON.
continues the edit and update. OB9031 RESET KEYWORD VALUE MUST
END WITH A BLANK
User response
Resubmit with the actual command name. Explanation
OB9028 INTERNAL ERROR DETECTED A nonblank character terminated the reset operand.
IN INFO-LINE COMMAND TABLE
SEARCH. CONTACT IBM CORP. System action
OMEGAMON suppresses the operation.
Explanation
OMEGAMON encountered an error in the security User response
update program.
System action OB9032 UNKNOWN RESET KEYWORD

VALUE
Explanation
User response
The reset keyword operand is not valid.

OMEGAMON suppresses the operation. None. This is an informational message only.
OB9036 PASSWORDS AND AUTHLIB WILL
User response BE RESET
Correct the keyword value and retry.
Explanation
OB9033 MAJOR COMMAND TABLES WILL
BE RESET The passwords and the authorized dataset will be
cleared.
Explanation
System action
The security level, audit, and external switches will be
cleared for all major and immediate commands. These Processing continues.
commands will be unprotected unless you specify new
settings and rerun the update program. User response
Specify new settings and rerun the update program to
System action
reset these fields.
OB9037 ONLY SECURITY LEVEL 0
ALLOWED FOR /PWD LEVEL 0
User response ASSIGNED
Explanation
OB9034 MINOR COMMAND TABLES WILL
BE RESET OMEGAMON allows a security level 0 only for
the /PWD INFO-line command.
Explanation
System action
The security level, audit, and external switches will be
cleared for all minor commands. These commands will OMEGAMON assigns security level 0.
be unprotected unless you specify new settings and
rerun the update program. User response
System action
Processing continues. OB9038 INVALID SMF RECORD NUMBER
SPECIFIED
User response
Explanation
Installer specified an invalid parameter for the
OB9035 INFO-LINE COMMANDS WILL BE SMFNUM control statement. Valid SMF record
RESET numbers are 128 through 255.

The security level, audit, and external switches will be The security update program ignored the statement.
cleared for all INFO-line commands. These commands
will be unprotected unless you specify new settings User response
and rerun the update program.
Correct the SMF record number to a number between
128 and 255 and resubmit.
System action
Processing continues. OB9039 SMFNUM ALREADY SPECIFIED.
STATEMENT IGNORED.

Installer specified the SMFNUM parameter in the None. This is an informational message only.
security update program more than once.
OB9043 SMF RECORD NUMBER
SPECIFICATION WILL BE RESET
System action
The security update program ignored the statement. Explanation
Installer executed security update program to reset
User response the indicated SMF record number.
Submit a new SMFNUM statement.
System action
OB9040 MODULE ALREADY SPECIFIED.
STATEMENT IGNORED. The security update program will reset the SMF record
number.
Explanation
User response
Installer specified the MODULE parameter in the
security update program more than once. None. This is an informational message only.
OB9044 EXTERNAL SECURITY MODULE
System action NAME SPECIFICATION WILL BE
The security update program ignored the statement. RESET

Submit a new MODULE statement. The installer executed the security update program
to clear the indicated module name. The external
OB9041 MODULE LENGTH IS INVALID; security exit routine will not be accessible unless you
MUST BE BETWEEN 1 AND 8 specify a new setting and rerun the security update
CHARACTERS program.

The security installation utility detected a name The security update program will clear the name.
specified for the MODULE control statement that was
not 1—8 characters.
User response
System action If you want to use external security specify a valid
module name for the security exit and rerun the
The security update program ignored the statement. security update program.
OB9045 ***WARNING*** - UPDATE
User response DENIED BY CONSOLE OPERATOR
Submit a new MODULE statement.
Explanation
OB9042 PASSWORD SPECIFICATION WILL
BE RESET This message appears on the security update report.
The console operator replied NO to a request to
Explanation update the security tables, so the request was denied.
The installer executed the security update program to

System action
reset the indicated password.
The update is cancelled.
System action
User response
The security update program will reset the password.
If appropriate, provide information on authorization to
the console operator.

OB9089 UPDATE OF OMEGAMON Explanation
SECURITY TABLES HAS BEEN
REQUESTED BY jobname This is an informational message returned from
running the security update program. The variable
cccccccc is the security table.
Explanation
This message appears on the operator console to System action
advise the operator that a job is attempting to update
the security tables. The security update program continues processing.

None. None.
OB9146 LOAD MODULE TEXT
User response SUCCESSFULLY READ
None.
Explanation
OB9090 REPLY “Y” TO ALLOW OR “N” TO
DISALLOW UPDATE PROCESSING This is an informational message returned from
running the security update program.
Explanation
System action
This message appears on the operator console
following message OB9089. It prompts the operator The security update program continues processing.
to allow or disallow updating.
User response
System action None.
The update job waits for the operator’s reply. OB9147 LOAD MODULE TEXT
SUCCESSFULLY UPDATED
User response
Respond Y or N. Explanation
OB9144 OBSELR00 CALLED TO READ This is an informational message returned from
cccccccc running the security update program. Message
OB9158 accompanies this message.
Explanation
System action
This is an informational message returned from
running the security update program. The variable The security update program completes.
cccccccc is the security table.
User response
System action None.
The security update program completes. OB9148 SYSLIB DCB {OPENED|CLOSED}
SUCCESSFULLY
User response
None. Explanation
OB9145 OBSELW00 CALLED TO WRITE This is an informational message returned from
cccccccc running the security update program.
System action
Security update program continues processing.

None. The job stops processing.
OB9149 LIBRARY DSNAME IS: cccccccc
User response
This is an informational message returned from OB9153 BLDL MACRO FAILED WITH
running the security update program. It provides the RETURN CODE nnnn/nnnn
library dataset name cccccccc.
Explanation
System action
OMEGAMON cannot find the command table. The
Security update program continues processing. variable nnnn/nnnn is an IBM return code.

None. The job stops processing.
OB9150 SYSLIB DCB CLOSED
User response
Explanation Verify that the job specifies the correct load library.
This is an informational message returned from OB9154 FIND MACRO FAILED WITH
running the security update program. RETURN CODE nnnn/nnnn

The security update program completes. OMEGAMON cannot find the command table. The
variable nnnn/nnnn is an IBM return code.
User response
System action
None.
OB9151 SYSLIB DCB FAILED TO OPEN
User response
Explanation
Verify that the job specifies the correct load library.
OMEGAMON encountered an error opening the dataset
specified in the SYSLIB DD statement. OB9155 TEXT READ OVERFLOWS
DIRECTORY SIZE INDICATION
System action
Explanation
An error occurred during the security update
User response program’s processing.
Verify that the SYSLIB DD statement specifies a valid

System action
and correctly spelled dataset.
OB9152 SYNADAF ERROR MESSAGE
User response
Explanation
An error occurred during a read/write of a file by the
security update program. OB9156 UNEXPECTED END-OF-FILE
WHILE READING cccccccc

An error occurred during the security update None.
program’s processing.
OB9262 LOAD MODULE ccccccc RETURN
CODE IS nnnn
System action
The job stops processing. Explanation
The variable ccccccc is READ, UPDATE, or REWRITE.
User response This is an informational message returned from
Contact IBM Software Support. running the security update program.
OB9157 RDJFCB MACRO FAILED WITH

System action
RETURN CODE nnnn
The security update program continues processing.
Explanation
User response
An error occurred during the security update
program’s processing. If return code nnnn is other than 0, contact IBM
Software Support.
System action OB9263 KOBSUPDT LISTING FILE FAILED
The job stops processing. TO OPEN

Contact IBM Software Support. The attributes of the SYSPRINT file are wrong.
OB9158 LOAD MODULE ID: cccccccc

System action
Explanation The job stops processing.
This message accompanies OB9146. The list that

User response
follows contains information on:
Verify that the file is a SYSOUT dataset, or that the file
• An internal module name
has the following attributes: RECFM=FBA, LRECL=133,
• An internal version identifier DSORG=PS, and BLKSIZE is a multiple of 133.
• An internal date and time stamp
OB9269 KOBSUPDT ENDED

The security update processing completes.
This is an informational message returned from
running the security update program.
User response
OB9261 KOBSUPDT BEGUN The security update program completes.

This is an informational message generated at the None.
start of the security update program.
System action
The security update program continues processing.

Chapter 31. OBV101-OMV9991 messages
This information documents messages OBV101-OMV9991.

OBV101 VTPRELOG MODULE ENTERED System action
Explanation
This message is issued after the VTM1WK workarea is User response
initialized.
System action OBV105 OPEN ACB SUCCESSFUL, NOW

ISSUE SETLOGON
Explanation
User response
This message is issued before the VTAM SETLOGON
None. This is an informational message only. instruction.
OBV102 USER INIT EXIT BEING CALLED
System action
This message is issued before the exit is called.
User response
Processing continues. OBV106 SETLOGON SUCCESSFUL, NOW
ISSUE REQSESS
User response
OBV103 USER INIT EXIT NOT BEING This message is issued before the VTAM REQSESS
CALLED instruction.

The initiation exit is optional. This message indicates Processing continues.
that the user did not supply the exit.
User response
Processing continues. OBV107 REQSESS SUCCESSFUL, NOW
ISSUE STIMER
User response
OBV104 OPEN ACB BEING ISSUED This message is issued before the MVS STIMER
instruction.
Explanation
System action
VTM1 must open an ACB that points to an applid. This
message is issued before every attempt to open an Processing continues.
ACB.

None. This is an informational message only. Processing continues.
OBV108 STIMER SUCCESSFUL, NOW ISSUE
WAIT User response
Explanation
OBV112 BIND RECEIVED FROM PLU
This message is issued before the MVS WAIT
instruction. VTM1 will wait for one of two ECBs to Explanation
be posted. This will either be the STIMER ECB (from
STIMER) or SCIP exit ECB (from REQSESS). The BIND RU was received by the VTAM SCIP exit. A
previous REQSESS macro resulted in this BIND.
System action
System action
User response
User response
OBV109 WAIT POPPED, BRANCH TO
VTENVIR OBV113 MODULE VTCOMM ENTERED
One of the two ECBs named in OBV108 has been This message is issued upon entry to module
posted. VTM1 branches to module VTENVIR. VTCOMM.


None. This is an informational message only. None. This is an informational message only.
OBV110 MODULE VTENVIR ENTERED OBV114 UNBIND DETECTED
This message is issued upon entry to module The UNBIND RU was received by the VTAM SCIP exit.
VTENVIR.
System action
System action
Processing ends.
User response
User response
OBV115 CALLING ROUTINE TO CREATE
OBV111 SCIP ECB POSTED RPL FOR RECEIVE
The VTAM SCIP exit was scheduled due to the receipt The VTAM GENCB macro is issued to create an RPL
of an SC RU. It posted the SCIP ECB. which a later RECEIVE macro uses.


None. This is an informational message only. None. This is an informational message only.
OBV116 RECEIVE ISSUED AND COMPLETE OBV120 CALLING USER GET EXIT
The VTAM RECEIVE macro has completed. This message is issued just before the user exit is
called.
System action
System action
User response
User response
OBV117 UNBIND DETECTED
OBV121 CALLING ROUTINE TO CREATE
Explanation RPL FOR SEND
The UNBIND RU was received by the VTAM SCIP exit.

Explanation
System action The VTAM GENCB macro is issued to create a RPL
which a later SEND macro uses.
Processing ends.
System action
User response
OBV118 SENT DEFINITE RESPONSE User response
Explanation
OBV122 CALLING ROUTINE TO ISSUE
The VTAM SEND macro, used to send a definite SEND
response, has completed. The return code from the
SEND has not yet been checked.
Explanation
System action This message is issued before the VTAM SEND
instruction is used.
System action
User response
OBV119 CALLING USER PUT EXIT User response
Explanation
OBV123 MODULE VTTERM ENTERED
This message is issued just before the user exit is
called.
Explanation
Issued upon entry to module VTTERM.
Chapter 31. OBV101-OMV9991 messages 581

Processing continues. This message is issued upon entry to the VTAM SCIP
exit for VTM1.
User response
System action
OBV124 CALLING USER TERM EXIT
User response
Explanation
This message is issued just before the user exit is
called. OBV128 VTSCIP RECEIVES UNBIND
REQUEST
System action
Explanation
The VTAM SCIP exit for VTM1 received an UNBIND

System action
OBV125 VTAM LOSTTERM EXIT ENTERED Processing continues.
FOR VTM1
User response
Explanation
This message is issued upon entry to the VTAM
LOSTTERM exit for VTM1. OBV129 VTSCIP RECEIVES BIND REQUEST

Processing continues. The VTAM SCIP exit for VTM1 received a BIND request.

OBV126 VTAM TPEND EXIT ENTERED FOR
VTM1 User response
Explanation
OBV130 RECEIVED FIRST SDT REQUEST
This message is issued upon entry to the VTAM TPEND
exit for VTM1. Explanation
The VTAM SCIP exit for VTM1 received its first Start
System action
Data Traffic request.
System action
User response
OBV127 VTAM SCIP EXIT ENTERED FOR User response
VTM1 None. This is an informational message only.
OBV131 RECEIVED SECOND SDT REQUEST

Explanation OBV135 VTM1 USER cccccccc LOGGING ON
TO aaaaaaaa
The VTAM SCIP exit for VTM1 received its second Start
Data Traffic request.
Explanation
System action This message is issued via WTO after a user logs onto
a VTAM application through VTM1. The fields cccccccc
Processing continues. and aaaaaaaa are filled in with the user ID and system
name of the PLU, respectively.
User response
OBV132 RECEIVED CLEAR REQUEST Processing continues.

The VTAM SCIP exit for VTM1 received a CLEAR None. This is an informational message only.
request. OBV136 VTLOGON MODULE ENTERED

Processing continues. The module VTLOGON was entered.

OBV133 VTSCIP POSTING ECB
User response
The VTAM SCIP exit for VTM1, an OMNIMON base OBV201 ERROR WITH IDENTIFY MACRO
program, posted its ECB to notify the mainline VTM1 USED TO LOCATE MODULE
code. VTPRELOG

Processing continues. An attempt to locate VTM1 module VTPRELOG failed.

None. This is an informational message only. Processing ends with an error.
OBV134 MVS STIMER EXIT ENTERED FOR
VTM1 User response
Explanation
OBV202 GETMAIN FAILED FOR ATTACH
The MVS STIMER issued previously has popped, and MACRO WORKAREA
its exit is being driven.
Explanation
System action
Storage request for the ATTACH macro’s workarea, as
Processing continues. defined by the list form of ATTACH, failed. This area is
needed to make the attach request reentrant.
User response

System action OBV206 GETMAIN FAILED FOR MAIN VTM1
WORKAREA - VTM1WK
Processing ends with an error.
Explanation
User response
The storage request for the main VTM1 workarea
Increase the region size. failed.
OBV203 ATTACH OF MAIN VTM1 MODULE
VTPRELOG FAILED System action
Explanation
The ATTACH macro, used to create the main VTM1 User response
task that ran the VTPRELOG module, failed.
System action OBV207 GETMAIN FAILED FOR VTALTER
Explanation
User response The storage request for the VTM1 workarea failed.
This workarea holds information describing the VTM1
Contact IBM Software Support. processing environment.
OBV204 DETACH OF MAIN VTM1 MODULE
VTPRELOG FAILED System action
Explanation
The detach of the VTM1 module VTPRELOG failed. User response
Note that when this message is issued, regular VTM1
processing was already completed. Increase the region size.
OBV208 GETMAIN FAILED FOR VTM1 USER
System action WORKAREA
Explanation
User response The storage request for the VTM1 workarea failed. This
workarea is for the VTM1 user.
OBV205 FREEMAIN FAILED FOR ATTACH System action
MACRO WORKAREA
Explanation
User response
Storage request for the ATTACH macro’s workarea, as
defined by the list form of ATTACH, failed. When this Increase the region size.
message is issued, regular VTM1 processing is already OBV209 ERROR SETTING ESTAE
completed.
Explanation
System action
The MVS ESTAE macro that is used to trap VTM1
Processing ends with an error. processing errors failed.

Contact IBM Software Support. Processing ends with an error.

OBV210 ERROR CREATING NIB CB OBV214 USER INIT EXIT RETURNS WITH
ERROR
Explanation
Explanation
The VTAM GENCB macro that is used to create an NIB
control block failed. After issuing this message, VTM1 begins termination
processing. The message is not passed back to the
System action VTM1 user.

System action
User response Processing ends with an error.

User response
OBV211 ERROR CREATING RPL CB Contact IBM Software Support.
Explanation OBV215 ERROR CREATING RPL CB FOR

OPNSEC
The VTAM GENCB macro that is used to create an RPL
control block failed.
Explanation
System action The VTAM GENCB macro that is used to create a RPL
control block failed. The RPL was to be used by the
Processing ends with an error. VTAM OPNSEC macro in the SCIP exit.

Contact IBM Software Support. Processing ends with an error.
OBV212 ERROR CREATING ACB CB
User response
The VTAM GENCB macro that is used to create an ACB OBV216 OPEN ACB FAILED, NONSPECIFIC
control block failed.
Explanation
System action
An attempt to open an ACB using one of the applids in
Processing ends with an error. the pool failed. This message is not passed back to the
user.
User response
System action
Processing continues; VTM1 tries the next applid in the
OBV213 ERROR CREATING EXLST CB
pool.

The VTAM GENCB macro that is used to create an
None.
EXLST control block failed.
OBV217 OPEN ACB FAILED, APPLID
System action ALREADY IN USE

An attempt to open an ACB using one of the applids in Processing ends with an error.
the pool failed. This message is not passed back to the
user. User response
Verify that the VTAM major node definition of the
System action
virtual terminal pool, KOBVTPL, is active to VTAM.
Processing continues; VTM1 tries the next applid in the Also, verify that at least one minor node within the
pool. major node has a VTAM status of CONCT.
OBV221 SETLOGON FAILED
User response
None. Explanation
OBV218 OPEN ACB FAILED, APPLID INACT The VTAM SETLOGON macro failed.
OR UNKNOWN
System action
Explanation
An attempt to open an ACB using one of the applids in
the pool failed. This message is not passed back to the User response
user.
System action OBV222 REQSESS FAILED
Processing continues; VTM1 tries the next applid in the
pool. Explanation
The VTAM REQSESS macro failed.
User response
None. System action
OBV219 NO LOGON MODE ENTRY Processing ends with an error.
AVAILABLE
User response
Explanation
The user-supplied table was searched, but no logmode
OBV223 STIMER FAILED
entry was found that matched the VTALTER fields.

The MVS STIMER macro failed.

Check the CALLVT macro parameter VTNAME. Make
sure that there is a logon mode table entry specified
for the given environment. User response
OBV220 SESSION CANNOT START - NO Contact IBM Software Support.
VIRTUAL TERMINAL AVAILABLE
OBV224 SESSION REQUEST TIMEOUT
The VTM1 virtual terminal pool was searched, but
VTM1 has not received a response to a session request
none of the virtual terminals was available for use.
sent to KOBVTAM. The cause of the failure is not

known, but the nature of the problem is probably User response
temporary.
System action OBV229 GETMAIN FOR PBUFF FAILED
The VTM1 session request stops processing.

Explanation
User response The storage request for the VTM1 put buffer area
failed.
Try starting another session at a later time. If the
condition persists, contact IBM Software Support.
System action
OBV225 UNBIND REQUEST RECEIVED
Explanation
User response
An unexpected UNBIND request was received.
System action OBV230 UNABLE TO DETERMINE THE

USERID
Explanation
User response
The VTM1 code that examines the ASCB in order to
Check the application system that VTM1 was logged determine user ID encountered an error.
onto. Try to logon again. If the error persists, contact
System action
OBV226 UNKNOWN ERROR ENCOUNTERED
WHILE EXAMINING THE VTM1 Processing ends with an error.
ECB LIST
User response
There is an unclear reason for the transfer of control OBV231 RECEIVE FAILED, NONSPECIFIC
within VTM1. Neither the STIMER or SCIP ECB was REASON
posted.
Explanation
System action
The VTAM RECEIVE macro failed.
System action
User response
VTM1 abends with user abend code U231. This
Contact IBM Software Support. message is seen only by the internal VTM1 trace
OBV228 GETMAIN FOR GBUFF FAILED routine.

The storage request for the VTM1 get buffer area Contact IBM Software Support.
failed. OBV232 SENDING OF DEFINITE
RESPONSE FAILED
System action
Processing ends with an error. Explanation
The VTAM SEND macro that is issued to send a definite
response failed.

System action OBV236 ERROR CREATING RPL CB FOR
RECEIVE
message is seen only by the internal VTM1 trace
routine. Explanation
User response control block failed.
System action
OBV233 USER PUT EXIT RETURNS WITH
ERROR VTM1 abends with user abend code U236. This
routine.
Explanation
After issuing this message, VTM1 begins termination User response
processing. The message is not passed back to the
VTM1 user. Contact IBM Software Support.
OBV237 TESTCB FAILED
System action
The VTAM TESTCB macro failed.
User response
OBV234 USER GET EXIT RETURNS WITH VTM1 abends with user abend code U237. This
ERROR message is seen only by the internal VTM1 trace
routine.
Explanation
User response
After issuing this message, VTM1 begins termination
processing. The message is not passed back to the Contact IBM Software Support.
VTM1 user. OBV238 ERROR CREATING RPL CB FOR
SEND
System action
User response control block failed.
System action
OBV235 SEND FAILED, NONSPECIFIC
REASON VTM1 abends with user abend code U238. This
routine.
Explanation
The VTAM SEND macro failed. User response
System action
OBV239 OPNSEC FAILED
routine. Explanation
The VTAM OPNSEC macro that is issued from the SCIP
User response exit failed. This message is seen only by the internal
VTM1 trace routine.

Processing ends as if an UNBIND had been received. Activate the proper network definition and start
KOBVTAM. If KOBVTAM is a cross-domain resource,
User response verify that the VTM1 host has a cross-domain resource
definition active for KOBVTAM.
OBV303 VTM1 APPL cccccccc NOT ACTIVE
OBV300 VTM1 LOGMODE cccccccc ERROR -
FM/TS nnnnNOT SUPPORTED
Explanation
Explanation The VTM1 appl cccccccc is not active.
VTAM logmode cccccccc specifies FM/TS profile nnnn,

System action
which VTM1 does not support. VTM1 requires a
logmode with FM/TS profile “0202”. The session ends.

The session ends. Make sure that the VTM1 appls have been properly
defined and are active.
User response OBV304 OPEN ERROR cc DETECTED FOR
Correct the KOBVTPL definitions to specify an APPL aaaaaaaa
appropriate VTAM logmode, and retry.
Explanation
OBV301 OMEGAMON SESSION REQUEST
FAILED - OBVTAM APPL NOT OPEN failed to complete successfully for APPL
SPECIFIED aaaaaaaa, due to error condition cc.

A null (blank) applid has been specified. The session ends.

The session ends. Contact IBM Software Support.
OBV305 TEMPORARY VTAM ERROR. RETRY
User response LATER
Verify that the applid has been properly supplied by all
clists, panels, or procedures, and retry. Explanation
OBV302 SESSION REQUEST FAILED - VTAM is temporarily short on storage.
OBVTAM APPL cccccccc NOT
DEFINED System action
The session ends.
Explanation
VTM1 requested a session with the KOBVTAM User response
application specified. VTAM does not have a network
definition for the KOBVTAM APPL. Retry later. If the problem persists, contact your
Network Support group.
System action OBV306 VIRTUAL TERMINAL POOL
The VTM1 session request stops processing. cccccccc IS NOT DEFINED TO
VTAM

Explanation OBV310 SESSION REQUEST FAILED -
ERROR cccc DETECTED
No match was found in VTAM’s configuration tables for
the VTM1 virtual terminal pool cccccccc.
Explanation
System action REQSESS failed to complete successfully, due to error
condition cccc.
The session ends.
System action
User response
The session ends.
Verify that the VTM1 application major node is
properly defined in SYS1.VTAMLST, and active.
User response
OBV307 VIRTUAL TERMINAL POOL
cccccccc DEFINITION ERROR Contact IBM Software Support.
OBV311 SESSION REQUEST FAILED -
Explanation OBVTAM APPL cccccccc NOT
AVAILABLE
cccccccc is not a valid APPL entry.
Explanation
System action
The KOBVTAM appl cccccccc is not active, or is
The session ends. terminating.

Correct the entry and retry. The session ends.
OBV308 NO APPL AVAILABLE IN VIRTUAL
TERMINAL POOL cccccccc User response
Be sure that the KOBVTAM appl is active, and retry.
Explanation
OBV312 SESSION REQUEST REJECTED -
All cccccccc virtual terminals are currently in use. VTAM REASON CODE xxxx yyyy

The session ends. The session request initiated by VTM1 was rejected
by VTAM. The reason code is described as follows:
User response xxxx is the VTAM Request Parameter List return code/
feedback information, and yyyy is the SNA System
Retry later.
Sense information associated with the request.
OBV309 VIRTUAL TERMINAL POOL
cccccccc IS NOT ACTIVE TO VTAM System action
The VTM1 session request stops processing.
Explanation
VTAM cannot access the specified virtual terminal User response
pool.
Refer the VTAM reason code information to your
network support group or contact IBM Software
The session ends.
OBV313 SESSION REJECTED - OBVTAM
APPL cccccccc AT MAX USERS
User response
Activate the VTM1 application major node.

Explanation session for the specified SLU. This message is output
only if the TRACE keyword is specified on the LOGON
The session request initiated by VTM1 was rejected by command.
KOBVTAM APPL cccccccc because KOBVTAM reached
its active session limit. The limit was established with
the UMAX parameter when KOBVTAM was started. System action
System action
The VTM1 session request stops processing. User response
User response OBV317 SLU(sluname) MATCH(match#)
Try starting another session at a later time, or increase PLU(pluname) LENGTH(block
the value of the KOBVTAM start-up parameter UMAX. length) SEQ(block seq#)
OBV314 SESSION REJECTED FAILED -

LOGMODE cccccccc IS INVALID Explanation
VTM1 full-duplex communications has sent or
Explanation received a block for the specified match on the session
for the specified SLU. Block length and sequence
The session request initiated by VTM1 failed because number are given. This message accompanies either
VTAM rejected the logmode name cccccccc as invalid. message OBV315 or OBV316. This message is output
only if the TRACE keyword is specified on the LOGON
VTM1 session request is terminated.
System action
Verify the logmode name definitions in KOBVTPL. If
they are correct, it may be necessary to update VTAM’s User response
logmode tables. None. The message is informational.
OBV315 VTM1 SLU(sluname) OBV318 VTM1 FDX RECEIVE PROCESS
MATCH(match#) BLOCK SENT STARTED FOR luname
VTM1 full-duplex communications has sent a block for VTM1 full-duplex communications has started
the specified match on the session for the specified receiving from its session partner on the session for
SLU. This message is output only if the TRACE keyword the specified SLU. This message is output only if the
is specified on the LOGON command. TRACE keyword is included on the LOGON command.


None. The message is informational. None. The message is informational.
OBV316 VTM1 SLU(sluname) OBV319 SESSION ENDED. LU(luname)
MATCH(match#) BLOCK RECEIVED REASON(text)
RECEIVE BLOCK QUEUED
Explanation
Explanation
A VTM1 full-duplex communications session has
VTM1 full-duplex communications has either received ended for the specified reason.
or queued a block for the specified match on the

System action OBV320 VTM1 SLU(sluname)
MATCH(match#) SEND BLOCK
The session ends, and VTM1 cleans up associated DEQUEUED.
session resources.
Explanation
User response
VTM1 full-duplex communications has dequeued a
The following table lists each reason text and block from the outbound send queue to send it to the
describes the response which should be taken: partner PLU for the session with the specified SLU.
Reason Description and User This message is output only if the TRACE keyword is
Response specified on the LOGON command.
LOGOFF COMMAND The logoff command was

ISSUED issued to intentionally
System action
terminate the session. Processing continues.
UNBIND RECEIVED The session partner has
terminated the session. User response
Inspect the job log of
the partner component for
messages explaining the OBV321 SLU(sluname) MATCH(match#)
reason for the session LENGTH(block length) SEQ(block
termination. seq#)
COMMUNICATIONS Inspect the message log
ERROR for message OBV322, which Explanation
documents the cause of the
This message gives detailed information on the block
communications error.
associated with message OBV320, including block
INVALID SEQUENCE The session partner has length and sequence number. This message is output
NUMBER transmitted an invalid only if the TRACE keyword is specified on the LOGON
sequence number. Contact command.
RPL CREATION VTAM was unable to generate System action
ERROR an RPL control block. Contact
RECEIVE QUEUE The session has terminated. User response
CLOSED Determine why the session
has terminated before None. The message is informational.
expected data block(s) from
OBV322 VTAM ERROR, LU(luname)
the session partner were
REQ(request) RCFB(rrff)
received.
SEND QUEUE Session termination is in
Explanation
CLOSED progress so no data blocks
can be dequeued from the VTM1 has encountered an error on a VTAM request.
outbound send queue for The request name (such as send or receive) and RPL
the session. If the session return code and feedback information are returned.
has terminated prematurely
inspect the log for further System action
messages documenting the
reason for the session The session is terminated.
termination.
UNKNOWN ERROR Contact IBM Software User response
Support. The associated Look up the return code and feedback information
return code is unknown. then correct the problem, given the cause of the
communications error.

OBV323 VTAM ERROR, LU(luname) Explanation
SSENSE(request)
The procedure to install command level security has
not been run.
Explanation
This message accompanies message OBV322 and System action
documents the system sense for the VTAM request
error described in that message. OMEGAMON does not start.

The session is terminated. Refer to the documentation about installing command
level security.
User response OM20001 OM2INIT HAS BEEN ENTERED
Look up the sense code and correct the problem, given

the cause of the communications error. Explanation
OM0904 OMSR24 OPEN FUNCTION Informational message concerning the progress of
REQUEST PARAMETER ERROR initialization.

An attempt to open the specified LPAM dataset failed. None.

The command ends. None.
OM20002 OM2CVT ADDRESS = hhhhhhhh
User response
Check the spelling and existence of the dataset. Make Explanation
sure you are authorized to open the dataset. Informational message displaying the address of the
OM0905 INTERNAL ERROR DURING communications vector table.
INITIALIZATION
System action
Explanation None.
The security work area could not be found during
OMEGAMON initialization. User response
None.
System action
OM20003 MODULE FAILED LOAD modname
OMEGAMON does not start.
Explanation
User response
During initialization, a number of functions must be
Call IBM Software Support. loaded into storage. The message indicates that the
OM0906 COMMAND LEVEL SECURITY module modname was not loaded into storage.
NOT INSTALLED. PLEASE
RUN JOB KOMSUPD IN System action
RHILEV.RKANSAM. FOR MORE
OMEGAMON II for MVS cannot proceed without
INFORMATION, PLEASE REFER
all functions available; therefore, the initialization is
TO THE DOCUMENTATION ABOUT
canceled.
ACTIVATING COMMAND LEVEL
SECURITY.

This is probably an installation problem. Review the Informational message indicating the storage address
installation process for errors. that has been assigned to a rule.
OM20004 KM2RULE MODULE FAILED RC = rc
System action
Explanation None.
The rules database must be loaded into storage during
installation. The message indicates that the function User response
responsible for KM2RULE failed and gave a return code None.
of rc.
OM20008 OM2_DEFINE FAILED, RC= rcADDR
RULE= hhhhhhhh
System action
OMEGAMON II for MVS cannot proceed without all Explanation
data available; therefore, the initialization is canceled.
The rule at address hhhhhhhhcould not be defined,
and the error return code was rc.
User response
This is probably an installation problem. Review the System action
installation process for errors.
The initialization has been canceled due to insufficient
OM20005 RULES TABLE ADDR = hhhhhhhh data.

Informational message indicating the address of the This is probably an installation problem. Review the
rules table. installation process for errors.
OM20009 OM2INIT COMPLETE
System action
None. Explanation
Informational message concerning the progress of
User response
initialization.
None.
OM20006 GLOBAL DATA ARRAY ADDR = System action
hhhhhhhh None.

Informational message indicating the address of the None.
global data area.
OM20010 OM2OPEN HAS BEEN ENTERED
System action
Explanation
None.
initialization.
User response
None. System action
OM20007 RULE DEFINED TO OM2ROUTER, None.
ADDR= hhhhhhhh NAME=
rulename
User response
None.

OM20011 OM2SCVT ADDR = hhhhhhhh Explanation
Explanation initialization.
Informational message indicating the address of the
secondary communications vector table. System action
None.
System action
None. User response
None.
User response
OM20017 SESSION NO LONGER ACTIVE
None. WITH luname
OM20012 VTAM FAILURE SENSE CODE= xxx
Explanation
Explanation The user is logging off the session. The connection to
OMEGAMON II for MVS needs to logon to the real time the real time collector must also be closed. luname is
collector. The message indicates that the connection the VTAM application name of the realtime collector.
was not successful. VTAM provides a sense code which
can help diagnose the problem. System action
None.
System action
The session ends. User response
None.
User response
OM20018 OM2CLOSE HAS COMPLETED
This is most often a setup problem. Check to make
sure that the realtime collector is running and that
the VTAM controls are properly activated. The sense Explanation
code ’100A0000’ indicates that the VTAM name of the Informational message concerning the progress of
collector (luname) is missing or inactive. initialization.
Note: See message KLVVT251 for complete return
code information. System action
Refer to the IBM Systems Network Architecture Format None.
and Protocol Reference Manual for further information.
OM20013 OM2OPEN HAS COMPLETED User response
None.
Explanation
OM22001 M2SESS HAS BEEN ENTERED
initialization.
Explanation
System action Informational message concerning the progress
of initialization. Module M2sess routine has been
None. entered.

None. None.
OM20016 M2CLOSE HAS BEEN ENTERED
User response
None.

OM22002 NOW USING PROFILE pp Explanation
This is an informational message indicating that
Explanation M2SESS successfully established a purge exit to keep
This is an informational message indicating that the track of cases when the terminal is lost.
user requested an alternate collector profile using the
Signon Panel logon options (F11). System action
None.
System action
None. User response
None.
User response
OM22006 OMEGAMON COPYRIGHT SCREEN
Check to make sure that the correct profile is being RECEIVE FAILURE
used.
OM22003 COLLECTOR SESSION Explanation
ESTABLISHMENT FAILURE
M2SESS failed to read the first screen (a copyright
notice).
Explanation
M2SESS attempted to connect to each of the three System action
lunames specified in rhilev.RKANPAR(KM2IPARM)
None were successful. The attempt to logon to the realtime collector has
ended. After the error message is displayed, the user
is terminated.
System action
The attempt to logon to the realtime collector has User response
is terminated. Check to see if your VTAM parameters have been set
up correctly.
User response OM22007 LOGON SCREEN SEND FAILURE
Determine if the rhilev.RKANPAR(KM2IPARM) lunames

are spelled correctly. If so, determine if the required Explanation
applications have been started and the application M2SESS attempted to send the logon commands to
names have been varied active. the realtime collector. The send did not complete
OM22004 PURGE EXIT CREATION FAILURE successfully.

M2SESS failed to establish a purge exit to keep track of The attempt to logon to the realtime collector has
cases when the terminal is lost. ended. After the error message is displayed, the user
is terminated.
System action
User response
The attempt to logon to the realtime collector has
ended. After the error message is displayed, the user Check to see if your VTAM parameters have been set
is terminated. up correctly.
OM22008 LOGON SCREEN RECEIVE FAILURE
User response
This is an internal error. Notify IBM Software Support. Explanation
OM22005 PURGE EXIT CREATED FOR M2SESS attempted to read a realtime collector screen.
PHYSICAL DEVICE The receive did not complete successfully.

The attempt to logon to the realtime collector has M2SESS attempted to send the LOG command to the
ended. After the error message is displayed, the user realtime collector, to turn on screen logging. The send
is terminated. did not complete successfully.

Check to see if your VTAM parameters have been set The attempt to logon to the realtime collector has
up correctly. ended. After the error message is displayed, the user
is terminated.
OM22009 OMEGAMON REJECTED USERS
LOGON ATTEMPT
User response
Explanation Check to see if your VTAM parameters have been set
up correctly.
M2SESS attempted to understand a realtime collector
screen. OM22014 LOG RECEIVE FAILURE

The attempt to logon to the realtime collector has M2SESS attempted to receive the screen following
ended. After the error message is displayed, the user the LOG command. The receive did not complete
is terminated. successfully.

Check that rhilev.RKANPAR(KM2IPARM) specifies a The attempt to logon to the realtime collector has
correct realtime collector. If not, it may be a ended. After the error message is displayed, the user
communications error. Additionally, the failure may is terminated.
be due to insufficient authority to logon OMEGAMON;
check with your security administrator. Also, check User response
the RKLVSNAP dataset for additional diagnostic
information. Check to see if your VTAM parameters have been set
up correctly.
OM22010 COLLECTOR PROFILE(pp)
REQUESTED(qq) OM22015 COMMAND SEND FAILURE
M2SESS determined that the realtime collector profile M2SESS attempted to send a command to the realtime
is different from the one requested. collector. The send did not complete successfully.

The attempt to logon is continued. The attempt to logon to the realtime collector has
is terminated.
User response
Check that DATA=YES is specified for the realtime User response
collector. DATA=NO would cause the requested profile
to be ignored. Check also if the profile exists in the real Check to see if your VTAM parameters have been set
time collector profile libraries. up correctly.
OM22013 LOG SEND FAILURE OM22016 COMMAND RECEIVE FAILURE

M2SESS attempted to read the screen following a The attempt to logon to the realtime collector has
command to the realtime collector. The receive did not ended. After the error message is displayed, the user
complete successfully. is terminated.

The attempt to logon to the realtime collector has Correct the LROWS value in
ended. After the error message is displayed, the user rhilev.RKANPAR(KM2IPARM).
is terminated.
OM22020 KM2SESS: LROWS(xx) IS TOO
SMALL AND MINIMUM IS 99;
User response SESSION TERMINATED
Check to see if your VTAM parameters have been set
up correctly. Explanation
OM22017 SESSION ESTABLISHED WITH M2SESS determined that the LROWS parameter was
luname FOR USER userid invalid.

Informational message concerning progress of the The attempt to logon to the realtime collector has
initialization. luname is the realtime collector luname ended. After the error message is displayed, the user
and userid is the userid which has been used to logon is terminated.
to the realtime collector.
User response
System action
Correct the LROWS value in
None. rhilev.RKANPAR(KM2IPARM).
OM22021 OMEGAMON COPYRIGHT SCREEN
User response TOO SMALL, DATA(xxxx)
None.
Explanation
OM22018 M2SESS ROUTINE COMPLETE
The expected OMEGAMON copyright screen was not
Explanation received.
The connection between OMEGAMON for MVS and

System action
OMEGAMON II for MVS has completed.
System action ended. After the error message is displayed, the user
is terminated.
None.
User response
User response
Check to see if your VTAM parameters have been set
None. up correctly.
OM22019 M2SESS: LROWS(xxxx) INVALID; OM22022 LOGMODE xxxxxxxx INVALID.
SESSION TERMINATED MUST NOT BE QUERIABLE.
M2SESS determined that the LROWS parameter was The expected OMEGAMON copyright screen was not
invalid. received.

The attempt to logon to the realtime collector has Call IBM Software Support and have the RKLVLOG
ended. After the error message is displayed, the user messages available.
is terminated.
OM22031 SESSION ESTABLISHED WITH
OMEGAMONSUBTASK FOR USER
User response userid
The LOGMODE for the terminal being used must not be
queriable. Explanation
OM22023 LOGON FAILED, OM SECURITY Informational message concerning progress of the
NOT INSTALLED initialization. userid is the userid which has been used
to logon to the realtime collector.
Explanation
System action
The logon to OMEGAMON failed.
None.
System action
User response
ended. After the error message is displayed, the user None.
is terminated.
OM22032 OMEGAMON SUBTASK
TERMINATED FOR USER userid
User response
Refer to the OMEGAMON II for MVS Configuration and Explanation
Customization Guide for how to install command level
security. Informational message indicating that the connection
between OMEGAMON and Tivoli OMEGAMON II has
OM22024 LOGON TO OMEGAMON FAILED; been terminated for userid.
SEE RKLVSNAP
System action
Explanation
None.
The logon to OMEGAMON failed.
User response
System action
None.
ended. After the error message is displayed, the user OM22033 $OMON START RETURNED RC=nn,
is terminated. R0=nn

Check the RKLVSNAP dataset for diagnostic A session with the OMEGAMONSUBTASK could not be
information. started.
OM22030 SUBTASK COLLECTOR SESSION System action

ESTABLISHMENT FAILURE
The user is terminated.
Explanation
User response
The attempt to establish a session with the
OMEGAMON subtask realtime collector failed. Call IBM Software Support and have the RKLVLOG
messages available.
System action OM22034 $OMON RCV RETURNED RC=nn
The user is terminated.

Explanation OM7104 WPF NOT ACTIVE; REQUEST
IGNORED
A receive from the OMEGAMON SUBTASK failed.
Explanation
System action
WPF STOP was issued, but WPF was not active.
User session is terminated.
System action
User response
WPF STOP request is ignored.
This is an internal error. Notify IBM Software Support.
OM22035 $OMON SEND RETURNED RC=nn User response
None.
Explanation
OM7120 INVALID KEYWORD SPECIFIED:
A send to the OMEGAMON SUBTASK failed. cccccccc

User session is terminated. Invalid keyword cccccccc was specified on the WPF
command.
User response
This is an internal error. Notify IBM Software Support. System action
OM22036 WARNING - PUTVAR FOR The WPF command is ignored.
KM2DEHDL RETURNED RC=nn
User response
Explanation Correct the error and reissue the WPF command.
The user’s session identification for the OMEGAMON OM7121 WPF IS ACTIVE; START OPERAND
SUBTASK could not be saved. INVALID

User session is terminated. WPF START was issued, but WPF was already active or
initializing.
User response
This is an internal error. Notify IBM Software Support. System action
OM22037 SESSION TERMINATED WITH WPF START request is ignored.
applid FOR USER userid
User response
Explanation None.
Informational message indicating that the connection OM7122 DEFAULT RKM2PRDS NOT
between OMEGAMONand Tivoli OMEGAMON II has FOUND, SPECIFY THE RKM2PRDS
been terminated for userid. KEYWORD

None. The name of the EPILOG Profile datastore was not
found in the user profile, and WPF START was issued
User response without specifying the RKM2PRDS or DSN operand.
None.

WPF START request is ignored. Attempt to determine and correct the error associated
with return code nn as documented by the LOAD
User response System Macro Service, and restart WPF. If the error
persists, call IBM Software Support.
Use the RKM2PRDS operand to specify the dataset
name of the EPILOG Profile datastore on the WPF OM7126 XLONG OR XSHORT KEYWORD NO
START command. LONGER VALID; IGNORED
OM7123 RKM2PRDS NAME MISSING

Explanation
Explanation The XLONG or XSHORT keyword was specified on the
WPF command. These keywords are no longer valid for
The RKM2PRDS or DSN operand was specified, but the WPF.
name of the EPILOG profile datastore was omitted.
System action
System action
The specified keyword is ignored.
The WPF command is ignored.
User response
User response
None.
Include the name of the dataset following the
RKM2PRDS or DSN operand and reissue the WPF OM7130 INITIALIZATION GETMAIN
command. FAILED WITH RC=nn
OM7124 PROFILE COLLECTOR ATTACH

Explanation
FAILED WITH RC=nn
The GETMAIN for WPF work areas failed with return
Explanation code nn.
The ATTACH for the WPF profile collector failed with

System action
return code nn.
WPF initialization is terminated.
System action
User response
Attempt to determine and correct the error associated
User response with return code nn as documented by the GETMAIN
System Macro Service, and restart WPF. If the error
Attempt to determine and correct the error associated persists, call IBM Software Support.
with return code nn as documented by the ATTACH
System Macro Service, and restart WPF. If the error OM7150 WPF RKM2PRDS READ ERROR,
persists, call IBM Software Support. RPL code=nn
OM7125 PROFILE COLLECTOR LOAD

Explanation
FAILED WITH RC=nn
An error occurred reading the EPILOG Profile
Explanation datastore. The RPL error code is nn.
The LOAD for the WPF profile collector failed with

System action
return code nn.
WPF is terminated.
System action
User response
Correct the VSAM read error associated with RPL
code nn. Make sure you have used the EPILOG
PROFILE command to create the profiles for selected

workloads. Then restart WPF. If the error persists, call System action
WPF is terminated.
OM7151 WPF TIMER TASK ABENDED
User response
Explanation
The WPF timer subtask has terminated abnormally. with return code nn as documented by the ATTACH
System Macro Service, and restart WPF. If the error
System action persists, call IBM Software Support.
WPF is terminated. OM7155 WPF UNABLE TO VALIDATE

EPILOG INSTALLATION
User response
Explanation
Restart WPF. If the error persists, call IBM Software
Support. EPILOG routines required for WPF are not available.
OM7152 WPF PROFILE COLLECTOR

PROTOCOL ERROR
System action
The WPF profile collector is terminated.
Explanation
There is a WPF internal error in the profile collector.
User response
If EPILOG is installed on your system, make sure that
System action the dataset name for the EPILOG load library has
been correctly specified on the STEPLIB or JOBLIB
WPF is terminated. statements of the OMEGAMON-invoking JCL. Either
the dataset specified may be available only to a
User response different CPU, the user may not have security access
to it, or the dataset may not be cataloged. Correct the
Restart WPF. If the error persists, call IBM Software situation and restart WPF. If EPILOG is not installed on
Support. your system, call IBM Software Support.
OM7153 WPF PROFILE COLLECTOR OM7156 WPF PROFILE COLLECTOR ESTAE
GETMAIN FAILED WITH RC=nn FAILED WITH RC=nn
The GETMAIN for WPF work areas in the profile The ESTAE in the profile collector failed with return
collector failed with return code nn. code nn.

WPF is terminated. WPF is terminated.

Attempt to determine and correct the error associated Attempt to determine and correct the error associated
with return code nn as documented by the GETMAIN with return code nn as documented by the ESTAE
System Macro Service, and restart WPF. If the error System Macro Service, and restart WPF. If the error
persists, call IBM Software Support. persists, call IBM Software Support.
OM7154 WPF TIMER TASK ATTACH FAILED OM7157 WPF RKM2PRDS ALLOCATION
WITH RC=nn FAILED, SVC 99 xxxx ERROR=xxxx
INFO=xxxx
Explanation
The ATTACH for the timer task in the profile collector
failed with return code nn.

The dynamic allocation request for the EPILOG Profile A key length error occurred attempting to read the
datastore failed with error code xxxx and information Profile datastore.
code xxxx.
System action
System action
WPF is terminated.
WPF is terminated.
User response
User response
Restart WPF. If the error persists, call IBM Software
Attempt to determine and correct the error associated Support.
with the ERROR and INFO codes as documented by
the Dynamic Allocation(SVC 99) System Service, and OM7161 WPF VSAM LOGICAL ERROR, RPL
restart WPF. If the error persists, call IBM Software CODE=nn
Support.
Explanation
OM7158 WPF RKM2PRDS GENCB FAILED
WITH RC=nn A VSAM logical error occurred while attempting to read
the EPILOG Profile datastore. The error code from the
VSAM RPL is nn.
Explanation
GENCB failure in the profile collector. The GENCB System action
return code is nn.
WPF is terminated.
System action
User response
WPF is terminated.
Attempt to determine and correct the VSAM read error
associated with RPL code nn, and restart WPF. If the
User response
error persists, call IBM Software Support.
OM7162 WPF RKM2PRDS CLOSE FAILED
with return code nn of the VSAM GENCB Macro
WITH RC=nn
Service, and restart WPF. If the error persists, call IBM
Software Support.
Explanation
OM7159 WPF RKM2PRDS OPEN FAILED
WITH ACB ERROR=nn The CLOSE for the EPILOG Profile datastore failed with
return code nn.
Explanation
System action
The OPEN for the EPILOG Profile datastore failed with
return code nn. WPF is terminated, however, the Profile datastore may
still be open.
System action
User response
WPF is terminated.
If the Profile datastore is still open, a VERIFY
operation may be required to CLOSE it.
User response
Attempt to determine and correct the error associated OM7163 WPF REQUIRES EPILOG Vnnn OR
with ACB ERROR code nn of the VSAM OPEN Macro LATER, Vxxx FOUND
Service, and restart WPF. If the error persists, call IBM
OM7160 WPF INVALID RKM2PRDS KEY WPF requires EPILOG Version nnn, or a later version
LENGTH for successful operation, but Vxxx was found.

The WPF profile collector is terminated. Give the WPF user authorization to read the Profile
datastore and restart WPF.
User response OM7168 WPF RKM2PRDS PROCESSING
Make sure that the EPILOG Version nnn load library, or ERROR
a later version of EPILOG, is available to OMEGAMON
and restart WPF. Explanation
OM7164 WPF PROFILE COLLECTOR STCK An undeterminable error occurred attempting to read
FAILED WITH RC=nn the EPILOG Profile datastore.

A store clock operation failed in WPF profile collector. The WPF profile collector is terminated.

WPF is terminated. Restart WPF. If the problem persists, call IBM
Software Support.
User response OM7180 WPF WORKLOAD PROFILE ENTRY
Attempt to determine and correct the error associated NOT FOUND
with condition code nn of the STCK instruction as
documented in the IBM Principles of Operation, and Explanation
restart WPF. If the error persists, call IBM Software
Support. A DWPF or JWPF was issued for a specific profile entry,
but that profile entry could not be found.
OM7165 WPF PROFILE COLLECTOR
ABENDED System action
None.
Explanation
The WPF profile collector has abended. User response
Specify the correct profile identifier via the JOB, STC,
System action
PGN, or PGP operands and reissue the command. If
WPF is terminated. The abend code, PSW, and general the DWPF or JWPF commands are specified without
registers at the time of the abend are printed following any operands, they display a full list of all profile
the message text. entries.
OM7181 WPF INVALID JOB OR STC NAME
User response SPECIFIED
Restart WPF. If the problem persists, call IBM
OM7167 WPF USER IS NOT AUTHORIZED An invalid jobname or started task name was specified
TO READ THE RKM2PRDS with the JOB or STC operand of a DWPF or JWPF
command. The jobname or started task name must not
Explanation exceed eight characters in length, and it must contain
those characters defined as acceptable by system JCL
The address space in which OMEGAMON is executing syntax.
is not authorized to read the EPILOG Profile datastore.
System action
System action
None.
The WPF profile collector is terminated.

Specify the jobname or started task name and reissue Specify the correct operands and reissue the
the command. command.
OM7182 WPF INVALID PERFORMANCE OM7185 PGN OR PGP INVALID FOR JWPF
GROUP OR PERIOD NUMBER
SPECIFIED Explanation
The PGN and/or PGP operands have been specified on
Explanation
a JWPF command. PGN or PGP operands are valid only
An invalid performance group or period was specified for DWPF.
with the PGN or PGP operand of a DWPF command.
The performance group must be numeric, between 1 System action
and 999. The period must be numeric, between 1 and
9. None.

None. Specify the correct operands and reissue the
command.
User response OM7198 WPF INVALID PARMLIST PASSED
TO PROFILE GET
Specify the correct performance group and/or period
number and reissue the command.
Explanation
OM7183 WPF PARAMETER ERROR; PGN
REQUIRED WITH PGP An error occurred attempting to obtain a profile entry
on a DWPF or JWPF command.
Explanation
System action
The performance group number must be specified
with the period number. The PGP operand was None.
specified without the PGN operand on a DWPF
request. User response
Make sure that the operands for the DWPF or JWPF
System action
command have been specified correctly and reissue
None. the command if necessary. If this does not rectify the
error, then STOP and restart WPF. If the error still
persists then call IBM Software Support.
User response
OM7199 WPF INVALID RETURN CODE
Specify the correct performance group using the PGN
FROM PROFILE GET, RC=xxxxxxxx
operand, and reissue the command.
OM7184 WPF CONFLICTING PARAMETERS Explanation
SPECIFIED
An error occurred while attempting to obtain a profile
entry on a DWPF or JWPF command. The return code
Explanation
from the profile get routine is xxxxxxxx.
Mutually exclusive operands have been specified on
a DWPF command. PGN or PGP operands cannot be System action
specified along with JOB or STC.
None.
System action
User response
None.
Make sure that the operands for the DWPF or JWPF
command have been specified correctly and reissue
the command if necessary. If this does not rectify the

error, then STOP and restart WPF. If the error still User response
persists then call IBM Software Support.
Specify a new volume for this system.
OM8100 VOLUME NOT FOUND
OM8104 VOLUME IS NOT MOUNTED (FROM
SVOL COMMAND)
Explanation
The volume you specified was not found on this Explanation
system.
The volume you specified was not mounted on this
system.
System action
The running of the command ends. System action
The running of this command ends.
User response
Specify a volume attached to this system. User response
OM8101 DATASET IS NOT CATALOGED Specify a volume attached to this system.
OM8112 DEVICE INVALID OR OFFLINE
Explanation
The data set you specified was not found in the system Explanation
catalog.
The specified device either was not found in the UCB
lookup table, or was found to be marked offline.
System action
The running of this command ends.
User response
Catalog the data set or specify a data set that is User response
cataloged.
Specify a valid volume or vary the volume online.
OM8102 DATASET IS NOT ON VOLUME
OM8113 WARNING; cccc FAILED VALIDITY
CHECK
Explanation
The data set that you requested was not found on the Explanation
volume specified.
The specified control block (ASCB, TCB, DSAB, JFCB,
or JFCX) failed validation in the SRB routine for FNDU.
System action
FNDU does not collect dataset information for the
User response address space which has failed validation.
Specify the volume that the data set resides on.
OM8103 VOLUME NOT ON SYSTEM (FROM
User response
SVOL COMMAND) This is an informational message only.
OM8115 WARNING INVALID RETURN CODE
Explanation - cc = xx (FROM PEEK, FNDU
The volume you specified was not found on this COMMANDS)
system.
Explanation
System action The SRB to collect data failed to complete its task and
The running of the command ends. returned an invalid return code to the user.

System action OM8122 PARTE NOT IN USE
The running of the command ends.
Explanation
User response You attempted to display a PARTE that is not currently
in use.
Call IBM Software Support to report a possible
problem.
System action
OM8116 WARNING SQA WORKAREA AT
ADDR=xxxx SIZE=yyyyDANGER The running of the command ends.
INSUFFICENT SQA - COMMAND
ABORTED WARNING (from PEEK, User response
FNDU commands)
Specify a PARTE that is in use.
Explanation OM8123 RMF NOT ACTIVE
The SRB to collect data failed to complete its task due

to a SQA shortage. Explanation
The command requires the Resource Management
System action Facility (RMF) or a specific RMF report to be active.
None.
System action
User response The running of the command ends.

problem. User response
OM8120 CHANNEL SET NOT VALID Modify RMF to add the required report for collection or
start RMF.
Explanation OM8124 CPU NOT DEFINED
An attempt was made to find the channel set in the

CST but it was not found. Explanation
You attempted to list channel sets from a CPU that is
System action not currently available.
None.
System action
Specify a valid channel set.

User response
OM8121 CHANNEL SET NOT DEFINED
(FROM DEV COMMAND) Select a CPU that is currently available.
OM8125 COMMAND NOT AVAILABLE IN
Explanation GOAL MODE
The channel set you entered is not defined to the
system. Explanation
You attempted to execute a command that is not valid
System action in goal mode.
None.
System action
Specify a channel set defined to this system.

Try a different command, or switch to compatibility In processing the GRS command, the address of the
mode. GRS Vector Table was not found.
OM8126 IWMRCOLL FAILED, CODE=nn
System action
Explanation The running of the command ends.
Indicates a failure in an MVS service which provides
information for some of the commands. User response
Activate GRS before you issue the GRS command.
System action
OM8140 TSO NOT AVAILABLE IN xxxx
The running of the command ends. MODE

Contact IBM Software Support. The TSO command is not available in this mode, where
the xxxx value indicates the mode.
OM8127 CONTROL BLOCK DOES NOT EXIST
IN SP5 OR HIGHER SYSTEMS
System action
The control block being accessed does not exist in
MVS/SP™ V5.1 or higher. User response
Issue the TSO command only in TS or LS modes.
System action
OM8141 STAX FAILED; RC=nn
Explanation
User response
A STAX SVC was unsuccessful. The nn value is the
Try running a different version of MVS. STAX SVC return code.
OM8128 DMDT DOES NOT EXIST IN SP5 OR
HIGHER SYSTEMS IN WLM GOAL System action
MODE The running of the command ends.

The DMDT, the Domain Descriptor Table, does not exist Issue the command again. If the problem persists, call
in MVS/SP V5.1 or higher of MVS running in Workload IBM Software Support.
Manager goal mode. The domain construct has no
meaning in goal mode. OM8142 IKJSCAN FAILED; RC=nn

The running of the command ends. A nonzero return code was issued by the IKJSCAN
routine, where the nn value is a two digit number.
User response
System action
Try using an MVS/SP V5.1 or higher goal mode
compatible command. The running of the command ends.
OM8130 WARNING NO GRS VECTOR TABLE
User response
Issue the command again. If the problem persists, call

OM8143 ATTACH FAILED; RC=nn User response
Issue a command other than this command.
Explanation
OM8147 INVALID COMMAND NAME
A nonzero return code was issued by the ATTACH SVC, SYNTAX
where the nn value is a two digit number.
Explanation
System action
There is an invalid command syntax in the TSO
The running of the command ends. command.

Issue the command again. If the problem persists, call The running of the command ends.
OM8144 COMMAND cccccccc ENDED - NON- User response
ZERO RETURN CODE is nn
Correct and issue the TSO command again.
Explanation OM8148 COMMAND cccccccc NOT FOUND
The command cccccccc ended with a four digit (nnnn)

non-zero return code. Explanation
OMEGAMON cannot find command cccccccc.
System action
User response
Use the return code to diagnose the error. Correct and User response
run the TSO command again. Correct and issue the cccccccc command again.
OM8145 TEST COMMAND NOT SUPPORTED OM8149 COMMAND cccccccc ENDED DUE
UNDER OMEGAMON TO ATTENTION
The TSO command does not support the TEST The command cccccccc ended due to depression of
command. the ATTN/PA1 key.

The running of the command ends. The running of the command ends.

Issue a command other than the TEST command. None.
OM8146 NO INFORMATION AVAILABLE OM8150 COMMAND cccccccc ENDED DUE
TO ERROR - COMPLETION CODE IS
Explanation Snnnn|Unnnn
No second level message chain exists for the

command. Explanation
The command cccccccc ended abnormally with the
System action System/User abend code displayed.

The running of the command ends. Install the yyy level of OMEGAMON and then start
OMEGAMON again.
User response OM8210 DATASET NAME LENGTH GREATER
Use the completion code to diagnose the error; correct THAN 44 (FROM LOC COMMAND)
and run the command again.
Explanation
OM8201 NO SUCH ADDRESS SPACE
THRESHOLD GROUP DEFINED The data set name that you entered was greater than
44 characters in length.
Explanation
System action
You entered a command to list an address space
threshold group that was not defined. The running of the command ends.

The running of the command ends. Enter a valid data set name.
OM8211 GQSCAN FAILURE, R/C = nn
User response
Enter an address space threshold group that is coded Explanation
in your profile or use the ASG command to add this
address space threshold group to your profile. The GQSCAN command returned an invalid return
code nn.
OM8203 NO CHANNEL AVAILABILITY
TABLE System action
Explanation
No Channel Availability Table was found for the User response
channel identifier entered.
Look for a description of the return code in the
Supervisor SPL. If problem persists call IBM Software
System action
Support.
None.
OM8212 MAJOR ENQUEUE NAME LENGTH
ERROR (MAX = 8)
User response
Correct and issue the command again, with a valid Explanation
channel identifier.
The major enqueue name that you entered was greater
OM8204 WARNING–RUNNING xxx than eight characters in length.
OMEGAMON ON yyy SYSTEM TYPE
OK (AND HIT ENTER TO CONTINUE System action
OR C TO CANCEL)
Explanation
User response
OMEGAMON is built for xxx operating system and
is running on the yyy operating system; this causes Enter a valid enqueue name.
functions and commands to fail.
OM8213 MINOR ENQUEUE NAME LENGTH
ERROR (MAX = 44)
System action
The startup continues, if you enter OK.

The minor enqueue name that you entered was greater Correct the enqueue name and enter the enqueue
than 44 characters in length. name again.
OM8217 ERROR GQSCAN ABEND S09A
System action
The running of the command ends. Explanation
The GQSCAN command encountered an unrecoverable
User response error.
Enter a valid minor enqueue name.
System action
OM8214 INVALID GENERIC MINOR
ENQUEUE NAME REQUEST The running of the command ends.

You placed an asterisk (*) in a position other than the Try the function again. If problem persists call IBM
end of the enqueue name. Software Support.
OM8218 ERROR GQSCAN RETURN CODE -
System action nn
Explanation
User response The GQSCAN command returned an invalid return
Delete all characters to the right-hand side of the code nn.
asterisk and retry the command.
System action
OM8215 INVALID HEX CHARACTER
STRING None.

You entered hex data that contained characters that Look for a description of the return code in the
are not the hex format. Supervisor SPL. If problem persists call IBM Software
Support.
System action OM8230 GREATER THAN MAX PERF GROUP
Explanation
User response You requested a performance group that was greater
Correct the enqueue name and enter the enqueue than the highest performance group specified in the
name again. system.
OM8216 SYNTAX ERROR

System action
An invalid hex entry was specified for the enqueue

User response
name.
Enter a performance group that is valid for your
System action system.
The running of the command ends. OM8231 F IS INVALID WITH THIS

COMMAND

Explanation OM8243 DEVICES NOT BEING MONITORED
BY RMF
No fixed frames exist for the region being displayed.
Explanation
System action
The command requires RMF Device reporting of tape
The running of the command ends. or DASD to be active and it is not.

Correct and issue the command again without the F None.
argument.
OM8240 STAT WORKAREA NOT AVAILABLE User response
Modify RMF to add the required report option for
Explanation collection.
An internal work table was invalidated. OM8244 RMF NOT COLLECTING DATA FOR
THIS DEVICE CLASS
System action
No RMF data is being collected for the device class
User response selected.
Ensure that RMF is still active in the system. If the
problem persists call IBM Software Support. System action
OM8241 RMF ROUTINE NOT ACTIVE (RC = The running of the command ends.
nn)
User response
Explanation Correct and issue the command again specifying a
You entered a command which requires data from RMF different device class.
and RMF is not running on this system. OM8245 INTERNAL ERROR (RC=nn)

None. An OMEGAMON logic error was detected.

Start RMF and enter the command again after RMF The running of the command ends.
initializes.
OM8242 RMF NOT ACTIVE (RC = nn) User response
Explanation
OM8246 CHANNEL PATH WORK AREA NOT
You entered a command which requires data from RMF AVAILABLE
and RMF is not running on this system.
Explanation
System action
A channel path work area was not available.
System action
User response
Start RMF and enter the command again after RMF has
initialized.

Issue the command again. If the problem persists, call The OMEGAMON program name was not found in the
IBM Software Support. list of APF programs available to the TSO user.
OM8247 RMF DEVICE STATISTICS NOT
AVAILABLE (RC=nn) System action
Explanation
No RMF statistics are available for the device you User response
selected. Add OMEGAMON to the TSO authorization list and
reassemble.
System action
OM8271 MODULE DID NOT COME FROM AN
The running of the command ends. APF LIBRARY

Correct and issue the command again specifying a Module was loaded from a library that is not APF
different device. authorized or that lost APF authorization.
OM8248 DATA NOT AVAILABLE FOR DEVICE
(RC=nn) System action
The command processing continues.
Explanation
There is no data available for the logical control unit User response
you selected. Ensure that STEPLIB references are APF authorized in
all libraries.
System action
OM8272 MODULE WAS NOT FOUND
The running of the command ends. MARKED AC=1

Correct and issue the command again specifying a The module was not link edited with AC=1 in the link
different LCU. edit PARM.
OM8260 MEMORY AT xxxxxx IS FETCH
(STORE)-PROTECTED (FROM System action
MZAP, MLST COMMANDS) The command processing continues.

The memory at the xxxxxx value cannot be fetched or You must re link the module.
stored into because it is fetch protected.
OM8273 MODULE WAS FOUND IN THE
TCB/RB CHAIN
System action
No zap applied. Explanation
An unexpected module was found in the TCB/RB
User response
chain; this might be why OMEGAMON is not
Add the authorized character to override the authorized.
protection.
OM8270 MODULE WAS NOT FOUND IN TSO System action
AUTHORIZATION LIST The command processing continues.

See the OMEGAMON II for MVS Configuration and A syntax error was found in validating information
Customization Guide for ways to install OMEGAMON about a library.
authorized.
OM8274 ENTRY NOT FOUND IN THE APF System action
LIST The running of the command ends.

You requested to delete a data set from the APF list; Ensure proper specification of DSN and volser, then
the data set was not in the APF list. retry the command.
OM8278 DATASET NAME OR VOLUME
System action
SERIAL NOT SUPPLIED
Explanation
User response
You did not enter the data set name and volume serial
Retry the command with a data set that is in the APF number required for the command.
LIST.
OM8275 ENTRY ALREADY EXISTS IN THE System action
APF LIST The running of the command ends.

You attempted to add a data set to the APF list; the Ensure that you specify all required fields (DSN, VOL).
data set was already in the APF list.
OM8279 NEW VOLUME SERIAL NOT
SUPPLIED
System action
You attempted to catalog a volume serial number of a
User response
data set in the APF list and you did not supply a new
Retry the command with a data set that is not in the volume serial number.
APF list.
OM8276 GETMAIN FAILED FOR NEW APF System action
LIST The running of the command ends.

There was not enough SQA storage available to get an Specify the NVOL operand with the new volume serial
area for the new APF list. number.
OM8280 CONSOLE NOT FOUND
System action
The console specified could not be found in the
User response
system.
Call IBM Software Support, if the command repeatedly
fails. System action
OM8277 SYNTAX ERROR NEAR COLUMN None.
FLAGGED ABOVE

Specify a valid console number. The running of the command ends.
OM8281 CSVAPF FAILED FOR DYNAMIC
APF LIST, RC=nn REAS=mmmm User response
Specify a module name that is not in the FLPA.
Explanation
OM8286 MODULE NOT CURRENTLY IN
The CSVAPF service returned a nonzero return code. MODIFIED LPA

The system ends the running of the command. You attempted to delete a module that was not found
in the MLPA.
User response
System action
See IBM Application Development Reference manual
for CSVAPF return codes and reason codes. The running of the command ends.
OM8283 SVC TABLE UPDATE ERROR - RC =
nnnn User response
Specify a module that is in the MLPA.
Explanation
OM8287 MODULE NOT FOUND IN THE LPA
An error occurred updating the SVC table. The return
code nnnn value is from the SVCUPDTE macro. Explanation
You attempted to list a module that is not in the LPA.
System action
The LPAM adds the module, but the SVC table is not System action
updated.
User response
User response
Specify the name of a module that is currently in LPA.
OM8284 INVALID LPAM MODIFY REQUEST
- PROGRAM IS A TYPE 1, 2, OR 6 OM8288 LPAM FAILED - MODULE ALREADY
SVC ON ACTIVE LPA QUEUE
You cannot use LPAM to process SVC type 1, 2, and 6 The LPAMM command is already on the active LPA
modules. queue. The LPAMM command cannot modify a module
previously placed in this state.
System action
System action
User response
User response
See the OM8307 message.
To modify the module again, first delete the entry
OM8285 MODULE FOUND IN FIXED LPA, using the LPAMD command and add the new module
NOT DELETED using the LPAMM command.
OM8289 MODULE NOT FOUND IN cccccccc
Explanation
You cannot delete a module that exists in the FLPA.

A search of the directory of data set cccccccc was The LPAM command stops processing.
made, but the module was not found.
User response
System action
Verify that the data set name specified on the DSN
The running of the command ends. parameter is correct and that the specified data set
is accessible to the system on which the OMEGAMON
User response session is running.
Ensure that the specified module exists in the data set OM8293 GLOBAL LOAD FAILED - ABEND
specified. CODE = xxx
OM8290 PROGRAM NAME NOT SUPPLIED -

Explanation
ENTER (PGM=)
An attempt to load the LPAMLIB failed; the xxx value is
Explanation the load return code.
The LPAM command was issued without the required

System action
operand. You did not specify the required PGM
keyword on the LPAMM or LPAMD command. The running of the command ends.

The running of the command ends. See IBM Supervisor Services SPL manual for load
return codes.
User response OM8297 JOBNAME cccccccc NOT FOUND
Specify the command again with the program name
that you want to list. Explanation
OM8291 LOAD LIBRARY NAME NOT You attempted to cancel jobname ccccccc, which was
SUPPLIED - ENTER (DSN=) not running on the system.

The LPAMA and LPAMM commands require a library The running of the command ends.
name to get the module from.
User response
System action
Specify a currently active job.
OM8298 ASID nnn REPRESENTS JOB
cccccccc
User response
Specify the data set name for the library that contains Explanation
the module.
You attempted to cancel job cccccccc where the ASID
OM8292 LOAD LIBRARY ALLOCATION nnn did not match the jobname specified.
FAILURE - RC=nn ERROR=cc
INFO=cc System action
Explanation
An attempt to allocate the specified library failed. User response
The RC=nn, ERROR=cc, and INFO=cc values are
the dynamic allocation return, error, and information Verify that the jobname/ASID combination is correct.
reason codes.
OM8299 CALLRTM FAILED - RC = nn

Explanation was unavailable, retry with OMEGAMON running in a
larger region.
The RTM service returned a nonzero return code.
OM8306 PRIMARY LOAD MODULE NOT
FOUND
System action
You specified an alias name in the PGM= parameter
User response and the primary load module was not found in the load
See IBM Supervisor Services SPL manual for the library.
CALLRTM return codes.
OM8300 NO ASCBCHAP ROUTINE System action
Explanation
The address of the CHAP routine was not found in the User response
CVT. In post SE1 systems, this is a trivial problem since Determine the cause of the problem. A possible
CHAP does not affect most address spaces. MVS has solution would be to re-linkedit or re-copy the load
lost its ability to address IEVEACO. module and all of its aliases and retry the command.
OM8307 cccccccc REPLACES A TYPE 1, 2, or
System action 6 SVC
Explanation
User response You attempted to issue LPAM to replace a module
If problem persists call IBM Software Support. that is a type 1, 2, or 6 SVC. LPAM does not support
replacement of type 1, 2, or 6 SVCs.
OM8305 aaa/ccc - STORAGE UNAVAILABLE
System action
Explanation
The aaa/ccc value can be one of the following
variables:
User response
CSA/MOD
CSA storage unavailable for module. See IBM SPL: System Generation Reference for
instructions to replace the SVC.
SQA/CDE
SQA storage unavailable to build CDEs. OM8308 REQUEST TERMINATED DUE TO
SQA/SMF PREVIOUS ERRORS
SQA storage unavailable for SMF tables.
PVT/MOD Explanation
Private area storage unavailable for module. There were errors during the LPAM processing.
PVT/DEL
Private area storage unavailable for DELETE list. System action
(Needed for internal processing of a DELETE
request.) The running of the command ends.

The LPAM command stops processing. See the error preceding the messages to determine
whether you can resolve the problems and then retry
the command.
User response
If CSA or SQA was unavailable, retry the request at a OM8309 cccccccc INVALID FOR EXTENDED
time when more area is available. If the private area SVC ROUTER TABLE

An SVC router (IGX00ccc) module is being processed The running of the command ends.
and the SVC router code (nnn) is higher than the
system allows. User response
Correct the command and enter it again.
System action
The running of the command ends. OM8315 SMF EXIT TABLE ID NOT FOUND:
cccc
User response
Explanation
See the OM8307 message.
The SMF subsystem ID specified by the SMFSYS=
OM8310 SVC VALUE CONFLICTS WITH parameter was not found in the system.
PGM=cccccccc
System action
Explanation
The value of the SVC parameter does not match the
SVC number indicated by the PGM name. User response
Specify the correct SMF system ID.
System action
The running of the command ends. OM8323 NOT IN AUTOMATIC MODE -
RETURN IGNORED
User response
Explanation
Verify that the PGM name is correct. If so, the SVC
parameter value must equal the SVC indicated by OMEGAMON received a .RTN command.
the PGM name. Note that you do not need the SVC
parameter in this situation. System action
OM8313 cccccccc IS IN OVERLAY OMEGAMON ignores the command.
STRUCTURE
User response
Explanation
None.
You attempted to process load module cccccccc, which
OM8324 WARNING: NEW SVC MODULE
is link-edited in an overlay structure. LPAM does not
cccccccc BEING ADDED
support modules that are link-edited in an overlay
structure.
Explanation
System action The SVC to be added by LPAMM has no LPDE and
its current SVC table entry point is IGCERROR. A
subsequent LPAMD deletion of the SVC returns it to
its original state.
User response
See IBM SPL: System Generation Reference for System action
instructions to replace the module.
The command continues normally.
OM8314 SYNTAX ERROR NEAR COLUMN
FLAGGED ABOVE User response
Note, that if you issue the SVC after deleting it with
Explanation
LPAMD, the system abends the issuing task.
A syntax error was found, and the command could not
OM8324 (IMS) NO TARGET SCREEN SPACE
be interpreted. The asterisk (*) indicates where the
error was.

Explanation M
Modify
OMEGAMON found a syntax error in the .RTN
command. D
Delete
(blank)
System action
List
System action
User response
Correct the .RTN command, save the screen space,
and invoke the screen space again. User response
OM8325 NEW SVC cccccccc HAS Use the appropriate argument for the LPAM command.
UNEXPECTED SVC TABLE ENTRY
POINT OM8328 LPDE AND SVC TABLE ENTRY
POINT MISMATCH
Explanation
Explanation
The SVC to be added by LPAMM has no LPDE, but the
SVC table entry point is not IGCERROR as expected. The entry point in the LPDE entry for this module does
A subsequent LPAMD deletion of the SVC does not not match that in the SVC table.
restore it to its original state.
System action
System action
User response
User response
This operation is very likely to compromise system
If you still want to add the SVC, use the FORCE integrity. Retry the operation specifying the FORCE
operand of the LPAMM command. Note, that if you operand of the LPAMM command only if you are
issue the SVC after deleting it with LPAMD, the system absolutely sure of the result of this operation. Also
abends the issuing task. note that the LPAMD command is not able to restore
the original status of the system.
OM8326 cccccccc INVALID FOR LPAM
OM8329 APF LIST IS FULL, CANNOT ADD
Explanation
Explanation
You cannot use the LPAM command to load module
cccccccc. The APF list has the maximum number of entries (that
is, 255); you cannot add any more.
System action
System action
User response
User response
None.
To add another entry, first delete one of the current
OM8327 INVALID ARGUMENT. USE M, D, entries.
OR BLANK.
OM8330 UNABLE TO OPEN LIBRARY
Explanation
Explanation
The LPAM command allows only the following
arguments: The OPEN failed for the data set specified in the DSN
parameter for the LPAM command.

The running of the command ends. The LPAMM command allows only 16 aliases for a
module.
User response
System action
Make sure that the correct data set name has been
specified and that the OMEGAMON session has read The LPAM command stops processing.
access authority to the data set.
OM8331 cccccccc IS NOT EXECUTABLE User response
If none of the aliases are needed, use LPAMM
Explanation command with the NOALIAS parameter to add the
module.
The directory entry for the module specified with the
LPAMM command was marked nonexecutable. OM8335 MORE THAN 49 ALIASES; ONLY
FIRST 49 DELETED
System action
Explanation
The LPAM command stops processing.
The LPAMD command can only delete up to 49 aliases
User response of a module.
Do not attempt to add modules which are marked

System action
nonexecutable.
The module and its first 49 aliases are deleted.
OM8332 ALIAS AND MAJOR MODULE TTR Additional aliases remain on the active LPA queue.
MISMATCH - cccccccc Programs attempting to access the deleted module
with any of the remaining aliases may abend.
Explanation
The module has an alias whose TTR does not match User response
the TTR for the main module. Schedule an IPL to remove the remaining aliases from
the active LPA queue.
System action
OM8336 TOO MANY SMFSYS NAMES
The LPAM command processing for that alias is SPECIFIED
ignored. The new module added through the LPAMM
command cannot be referenced using the ignored
Explanation
alias.
The SMFSYS parameter of the LPAM command allows
User response only 7 SMF subsystem names to be specified.
If the alias should have been assigned to the load

System action
module, follow these steps:
The LPAM command ends.
1. Reassign the alias in the data set specified by the
DSN operand of the LPAM command to correct the
TTR. User response
2. Use the D option of the LPAM command to delete If you want the exit to be added for all SMF
the module just loaded with the LPAMM command. subsystems, omit the SMFSYS parameter.
3. Reload the module with the corrected alias using OM8339 MODULE LOGICALLY DELETED;
the LPAMM command. CSA NOT FREED
OM8333 MODULE HAS MORE THAN 16
ALIASES - CANNOT LPAM Explanation
The specified SMF exit has been logically removed
from the subsystems specified on the SMFSYS
parameter. However, the exit is still in use by other

SMF subsystems. The module storage in CSA is not System action
freed.
System action
User response
The LPAMD command is successful for the specified
subsystems. If you have an Amdahl MDF system, specify the
MDF=ON parameter.
User response OM8349 DOMAIN AUTHORIZED TO OBTAIN

DATA ONLY FOR DOMAIN n
OM8342 LOAD LIBRARY UNALLOCATION Explanation
FAILURE - RC=nn ERROR=cc
INFO=cc The current Amdahl™ domain is only authorized to
collect data for itself. The current domain number is
given in the message.
Explanation
An attempt to unallocate the specified library has System action
failed. The RC=nn, ERROR=cc, and INFO=cc values are
the dynamic allocation return, error, and information The command continues to display data only for
reason codes. current domain.

The LPAM command stops processing. To avoid this message either specify the current
domain number as an argument to the command, or
authorize the domain to collect data for all domains
User response (set authorization level 2 through hardware frame).
If the data set is still allocated by the OMEGAMON OM8350 COMMAND ONLY VALID FOR
session, and it is preventing other users from AMDAHL MDF SYSTEM
accessing the data set, you might need to stop and
restart the OMEGAMON session to free the allocation.
Explanation
OM8343 cccccccc CURRENTLY IN USE
This command pertains specifically to an Amdahl MDF
system and does not function on another system.
Explanation
The LPAMD command was requested for a module that System action
is currently being used.
System action
User response
The LPAM command request stops processing.
None.
User response OM8351 DOMAIN NOT AUTHORIZED FOR

DATA COLLECTION; RC=nn
Issue the LPAMD command again, when the module is
no longer in use.
Explanation
OM8348 MDF PROCESSING DISABLED. USE
POPT COMMAND TO RESET. The current Amdahl domain is not authorized (through
the hardware CA frame) to collect data requested
about MDF.
Explanation
This command has been disabled because the System action
MDF=OFF parameter was specified in the POPT
command. The command discontinues attempts to collect data.

The authorization level on the Amdahl CA frame Record the message number and return code (RC) and
should be 2 to collect data for all domains or 1 call IBM Software Support.
to collect data for only the current domain. For
OM8355 MDF RMI MDFWATCH INTERFACE
full OMEGAMON functionality with respect to MDF
ERROR OCCURRED; RC=nn
support, the authorization level should allow all
domain data collection (2).
Explanation
OM8352 MDF IIC MRSD INTERFACE ERROR
OCCURRED; RC=nn A problem occurred while using the Amdahl MDF RMI
interface.
Explanation
System action
A problem occurred while using the Amdahl MDF IIC
interface. The command discontinues attempts to collect MDF
data.
System action
User response
The command discontinues attempts to collect MDF
data. Record the message number and return code (RC) and
call IBM Software Support.
User response OM8356 MDF INTERFACE/OMEGAMON
INTERNAL ERROR; RC=nn
Record the message number and return code (RC) and
Explanation
OM8353 MDF IIC MDFWATCH INTERFACE
ERROR OCCURRED; RC=nn An internal error occurred while using the Amdahl MDF
interface.
Explanation
System action
A problem occurred while using the Amdahl MDF IIC
interface. The command discontinues attempts to collect MDF
data.
System action
User response
data. Record the message number and return code and call
User response OM8357 MDF INTERFACE NOT SUPPORTED
IN THIS ENVIRONMENT
Record the message number and return code (RC) and
Explanation
OM8354 MDF RMI MRSD INTERFACE
ERROR OCCURRED; RC=nn The Amdahl MDF interface is not supported in the
current system environment, for example, in PMA or
guest mode environments.
Explanation
A problem occurred while using the Amdahl MDF RMI System action
interface.
System action
User response
data. None.
OM8358 COMMAND REQUIRES APF
AUTHORIZATION

OMEGAMON must be authorized for this command to The command stops processing.
operate.
User response
System action
Restart OMEGAMON. If the problem persists, call IBM
The command stops processing. Software Support.
OM8362 INVALID DATA FROM THE PR/SM
User response LPAR INTERFACE
Authorize OMEGAMON and see OMEGAMON II for MVS
Configuration and Customization Guide). Explanation
OM8359 UNABLE TO ALLOCATE 4K There was invalid data returned from the interface
WORKAREA; RC=nn so the LPAR command could not provide valid logical
partitioning data.
Explanation
System action
OMEGAMON failed while trying to allocate a 4k page-
fixed workarea. These are the possible meanings of The command stops processing.
the return code:
24 User response
GETMAIN failed.
Try the LPAR command again. If the problem persists,
28 call IBM Software Support.
Page fix failed.
OM8363 LPAR COMMAND INTERNAL
ERROR
System action
An internal error has occurred in the LPAR command.
User response
Increase the region size and try again. If the problem System action
OM8360 COMMAND ONLY VALID FOR
PR/SM LPAR MODE OPERATIONS
User response
Explanation Call IBM Software Support.
This command is valid only when operating under OM8370 INVALID PARAMETER FOR CHNM
logical partitioning mode (PR/SM™).
Explanation
System action An unrecognized parameter was entered for the CHNM
The command stops processing. command.

None. The command stops processing.
OM8361 PR/SM LPAR INTERFACE FAILURE

User response
Explanation Check the command syntax and specify the command
again with the correct parameter.
The interface needed to gather the logical partitioning
data has failed, and OMEGAMON is unable to provide
the logical partitioning data.

OM8371 CHANNEL PATH ID NOT System action
SPECIFIED FOR ADD OR DELETE
FUNCTION The command stops processing.

The ADD or DELETE keyword was specified without a Check the command syntax and specify the command
channel path ID. again with the correct parameter.
OM8377 CPU ID NOT SPECIFIED FOR ADD
System action OR DELETE FUNCTION

Explanation
User response The ADD or DELETE keyword was specified without a
CPU ID.
Specify the channel paths to be added or deleted.
OM8372 CHANNEL PATH ID MUST BE System action
BETWEEN 00 THRU ff
Explanation
User response
The channel path ID specified was outside of the valid
range. Specify the CPU IDs to be added or deleted for the
keywords.
System action OM8378 CPU ID MUST BE BETWEEN 0

THRU 15
Explanation
User response
The CPU ID specified was outside of valid range.
Specify the channel path (00 through ff).
OM8373 CHANNEL SET ID MUST BE System action
SPECIFIED
Explanation
User response
The channel set ID was not specified in MVS/370
mode. Specify the CPU ID between 0 through 15 (decimal).
OM8380 NOT ADDED. USE * ONLY IN LAST
System action POSITION OF GROUP NAME.

Explanation
User response The input group mask gggggggg is not acceptable
since the mask character with the asterisk (*) occurred
Specify the channel set ID required for MVS/370 before the last character.
mode.
OM8376 INVALID PARAMETER FOR CPUM System action
Explanation
An unrecognized parameter was entered for the CPUM User response
command.
Correct the input group name mask.

OM8381 NOT ADDED. gggggggg Explanation
DUPLICATES USERS IN GROUP
hhhhhhhh The group mask gggggggg was successfully added for
monitoring.
Explanation
System action
The input group mask gggggggg cannot coexist with
the group mask hhhhhhhh; the hhhhhhhh value None.
specifies a subset of the gggggggg value.
User response
System action None.
The command stops processing. OM8385 DELETED. gggggggg IS NO LONGER
BEING MONITORED.
User response
Correct the input group mask gggggggg value or delete Explanation
the hhhhhhhh value. The group mask gggggggg was successfully deleted
OM8382 NOT ADDED. gggggggg IS from monitoring.
CURRENTLY MONITORED IN
GROUP hhhhhhhh System action
None.
Explanation
The input group mask gggggggg cannot coexist User response
with the group mask hhhhhhhh; the gggggggg value
None.
specifies a subset of the hhhhhhhh value.
OM8386 NOT FOUND. gggggggg IS NOT
System action CURRENTLY BEING MONITORED.

Explanation
User response The group mask gggggggg does not exist for deletion.
Correct the input group mask gggggggg value or delete

the hhhhhhhh value. System action
OM8383 NOT ADDED. gggggggg IS
ALREADY BEING MONITORED.
User response
Explanation Correct the input group mask.
The input group mask gggggggg value already exists. OM8387 KEYWORD IGNORED. kkkkkkkk IS
INVALID; VERIFY SYNTAX.
System action
The keyword specified with the command is not valid.
User response
Specify the input group mask again. System action
OM8384 ADDED. gggggggg IS NOW BEING
MONITORED.
User response
Correct the keyword for the function to be performed.

OM8388 INVALID PARAMETER. RE OM8391 RTA NOT AVAILABLE. LOAD
SPECIFY kkkkkkkk KEYWORD ABEND=xxx-yy FOR OMRTASSS.
PARAMETER.
Explanation
Explanation
The RTA command load module (system level sss)
The parameter specified with keyword kkkkkkkk is not could not be loaded for the reason indicated by the
valid. ABEND code xxx and reason code yy.

The command does not process the parameter. The command does not operate.

Enter an allowable parameter for the keyword. Correct the situation indicated by the ABEND and
reason codes. These codes are documented in IBM
OM8389 RTA NOT OPERATIONAL. System Messages and Codes.
INSUFFICIENT PRIVATE REGION.
RTA NOT OPERATIONAL. OM8392 RTA WILL NOT UPDATE USER
INSUFFICIENT ECSA. RTA NOT PROFILE FOR THIS SESSION
OPERATIONAL. VTAM INTERNAL
TRACE INACTIVE. RTA NOT Explanation
OPERATIONAL. VTAM NOT AT
SUPPORTED LEVEL. RTA NOT The RTA command encountered an unexpected
OPERATIONAL. RC= xx SC= situation during initialization with the User Profile
xxxxxxxx; CALL CANDLE CORP. Facility, and subsequent RTA updates to the profile
during the session are not effective.
Explanation
System action
The RTA™ command cannot initialize. The message
indicates the required action or, in some cases, gives The command continues as normal. Any changes
the failure return code and sense code. made (that is, group additions or deletions) are not
reflected in a User Profile saved during the current
OMEGAMON session.
System action
The command does not operate. User response
None.
User response
Follow the suggestion given in the message text. OM8400 ENTRY NOT FOUND: cccc
OM8390 TSO RESPONSE TIME ANALYZER Explanation

NOT INSTALLED; CALL CANDLE
CORP. The entry requested does not exist.

The RTA command has not been installed in the load None.
library currently being used.
User response
System action
Check to make sure that the request is valid.
The command does not operate.
OM8401 INVALID PARAMETER SPECIFIED:
cccc
User response
Call IBM Software Support to order the RTA command.

The error might be due to an invalid keyword or label. An error occurred while processing the command. The
reason for the error is listed.
System action
System action
None.
The command does not run.
User response
User response
Correct the problem and retry.
Correct the error, if possible, or call IBM Software
OM8402 INVALID KEYWORD VALUE: cccc Support.
Explanation OM8410 ERROR STORING INTO MEMORY-

RESIDENT PROFILE OPTIONS
The error is due to an invalid value for keyword cccc. TABLE

None. An error occurred while OMEGAMON attempted to
update the profile options.
User response
System action
Correct problem and retry.
The user request cannot be completed.
OM8403 ERROR DURING UPF
INITIALIZATION
User response
Explanation Further updates might fail; restart OMEGAMON, if
immediate resolution is required. If the problem
An internal error occurred during User Profile Facility
initialization.
OM8411 ERROR READING FROM THE
System action MEMORY-RESIDENT PROFILE
OPTIONS TABLE
OMEGAMON continues its initialization processing, but
all User Profile Facility initialization related functions
Explanation
are disabled for this session.
An error occurred while OMEGAMON attempted to
User response read the profile options.

System action
OM8406 SYNTAX ERROR: reason
The user request can not be completed.

A syntax error occurred. The reason for the error is
Further profile commands might fail; restart
listed.
OMEGAMON, if immediate resolution is required. If the
System action
OM8420 ERROR UPDATING ASTG TABLE
The command does not run.
Explanation
User response
Correct the error and retry. update the memory-resident Address Space Threshold
Group table.
OM8407 COMMAND ERROR: reason

The user request can not be completed. Further PGN updates might fail; restart OMEGAMON,
if immediate resolution is required. If the problem
User response persists, call IBM Software Support.
Further ASG updates probably fail; restart OM8500 CSAF EXECUTES ONLY ONCE PER
OMEGAMON, if immediate resolution is required. If the CYCLE
Explanation
OM8421 ASTG TABLE INTERNAL ERROR
Only one CSAF command can be displayed on the
Explanation screen at the same time.
An error occurred in the memory-resident Address

System action
Space Threshold Group table.
The CSA Analyzer ignores all subsequent CSAF
System action commands on the screen.

User response
User response Enter only one CSAF command on the screen.
Further ASG commands fail; restart OMEGAMON, OM8501 SUBPOOL nnn IS NOT IN <CSA|
if immediate resolution is required. If the problem ECSA|SQA|ESQA >
Explanation
OM8430 ERROR UPDATING DMN TABLE
Subpool number nnn is not in the common storage
Explanation area specified by the AREA keyword.

System action
update the memory-resident Domain Name table.
The CSA Analyzer ignores the command.
System action
User response
Correct the value of the SUBPOOL keyword or the
User response AREA keyword.
Further DMN updates might fail; restart OMEGAMON, OM8502 RANGE DOES NOT OVERLAP CSA
if immediate resolution is required. If the problem OR SQA
Explanation
OM8440 ERROR UPDATING PGN TABLE
The address range specified does not fall into any
Explanation common storage area.

System action
update the memory-resident Performance Group
Name table. The CSA Analyzer ignores the command.

The user request can not be completed. Correct the address range values specified in the
RANGE keyword.
OM8503 SYSTEM AND JOB KEYWORDS ARE
MUTUALLY EXCLUSIVE

You cannot specify both SYSTEM and JOB keywords. CSAA has no information for the command request.

The CSA Analyzer ignores the command. None.

Enter only the SYSTEM or JOB keyword. None.
OM8504 PARAMETER FOR KEYWORD OM8511 CSAA IS NOT ACTIVE
xxxxxxxx IS INVALID
Explanation
Explanation
The CSAA manager address space is not running.
An invalid value for keyword xxxxxxxx was entered.
System action
System action
User response
User response
Start the CSAA Manager address space and retry the
Enter the keyword again and specify a valid value. command. See OMEGAMON II for MVS Configuration
and Customization Guide for details.
OM8505 JOB REQUIRED. ENTER COMMAND
WITH JOB PARAMETER OM8512 LOAD OF CSAA SUPPORT MODULE
FAILED
Explanation
Explanation
The CSA Analyzer requires a JOB keyword for the
command. The CSA Analyzer did not find a required module for
the operation of CSAA.
System action
System action
User response
User response
Enter the command again and specify a JOB keyword.
Ensure that all CSAA modules reside in the
OM8506 ONLY KEY ZERO IS VALID FOR OMEGAMON for MVS load library. See OMEGAMON
(E)SQA II for MVS Configuration and Customization Guide for
details.
Explanation
OM8513 CSAA REPORTER INTERNAL
You specified a nonzero storage key for SQA or ESQA LOGIC ERROR
storage.
Explanation
System action
The CSAA reporter module abended.
System action
User response
Enter the command again and specify KEY(0).
OM8510 NO DATA AVAILABLE

Call IBM Software Support. The CSA Analyzer ignores the command.
OM8514 CSAA MANAGER BUSY. TRY AGAIN
User response
Explanation When the CSAA address space is next started, specify
trending for SYSTEM or job. Refer to the OMEGAMON
The CSAA reporter could not process the command
II for MVS Configuration and Customization Guide for
request because the CSAA manager was busy.
details.
System action OM8518 VERSION MISMATCH. MANAGER

Vmmm. REPORTER Vnnn
Explanation
User response
The CSA Analyzer Manager’s version, mmm, does not
Retry the command. match the Reporter’s version, nnn.
OM8515 CSAA REPORTER ERROR.
RC=nnnnnnnn System action
Explanation
The CSAA reporter encountered an error. User response
Ensure that all CSAA modules are at the same version.
System action
OM8519 FREEMAIN EVENTS MISSED
Explanation
User response
The CSA Analyzer was unable to record some freemain
Call IBM Software Support. events due to a buffer full condition.
OM8516 <CSA|ECSA|SQA|ESQA>
MONITORING IS NOT ACTIVE System action
Explanation
CSAA is not monitoring the area specified in the AREA User response
keyword. When you next start CSAA, increase its amount of
available fixed storage. Refer to the OMEGAMON II for
System action MVS Configuration and Customization Guide for details.
The CSA Analyzer ignores the command. OM8520 CSAA UPDATE PROCESSING
SUSPENDED AT mm/dd/yy hh:mm
User response
Explanation
When you next start the CSAA address space, specify
monitoring for the given area. See OMEGAMON II for The CSA Analyzer stops processing.
MVS Configuration and Customization Guide for details.
OM8517 <SYSTEM|JOB> TRENDING IS NOT System action
ACTIVE The system does not process the command.

CSAA did not gather the necessary trending data. Verify that the CSA Analyzer started task is running.

OM8521 OPERAND <operand> NOT Explanation
PERMITTED
You have not declared a required operand and no
substitute value assignment is available. The JOB
Explanation adverb and the AREA operand both lack default
The keyed parameter has been recognized but you assignment values.
used it incorrectly as an operand.
System action
System action When a specific OMCSAA command argument requires
The OMCSAA command processing edits the second a particular operand that you have not supplied, the
and subsequent keyed parameters following the OMCSAA command processing attempts to provide
command. Those parameters must be operands an assignment value for the missing operand in the
which must be syntactical elements of the OMCSAA following manner:
command argument being processed. 1. The inherited value, the last value assigned to
Note: The OMCSAA/CSAA arguments that use the JOB that operand when an OMCSAA command was
and SYSTEM adverbs to distinguish different report processed successfully, is assigned to the current
processing requirements use two specific sets of operand.
operands which are similar but not identical. 2. When an inheritable assignment value is a null
value, the operand’s default value is assigned.
User response 3. When the result is still a null value, a violation
occurs and this message is issued.
Make the following changes:
1. Remove or correct the indicated operand. User response
2. Remove the command inhibit character (>).
3. Resubmit the command.
1. Provide the missing operand and value assignment.
OM8522 VALUE <value> NOT PERMITTED 2. Remove the command inhibit character (>).
Explanation
OM8525 <operand> VALUE NOT NAME
Some of the OMCSAA keyed parameter specifications
are keywords (for example, they are unique names
without an associated assignment value). The Explanation
OMCSAA/CSAA arguments and the SYSTEM adverb are The operand assignment value is not a name.
always keywords. They neither require nor permit an
associated assignment value.
System action
System action A name value begins with an alphabetic character
(A–Z).The JOB adverb and the AREA operand are
Each keyed parameter is edited and evaluated associated with alphabetic assignment values.
syntactically. Whenever a specification violates a
syntax rule, the appropriate OMCSAA diagnostic
message is issued. User response
User response 1. Correct the value assignment.
Make the following changes: 2. Remove the command inhibit character (>).
1. Correct the command syntax. 3. Resubmit the command.
2. Remove the command inhibit character (>). OM8526 <operand> VALUE NOT NUMERIC
OM8523 <operand> IS REQUIRED Explanation
The operand assignment value is not a number.

A numeric value begins with the decimal digits (0–9) Make the following changes:
or with hexadecimal digits (A–F). The ASID, SUBPOOL,
1. Correct the command specifications.
BOUNDS, MINSIZE, and RANGE operands are all
associated with numeric assignment values. 2. Remove the command inhibit character (>).
User response OM8531 OPERAND <text> NOT
Make the following changes: RECOGNIZED
1. Correct the value assignment.

Explanation
Each operand is a keyword which must be entered
as documented. Each operand is associated with a
OM8527 <operand> VALUE LIST NOT specific abbreviation.
PERMITTED
System action
Explanation
Operand specifications that are neither the acceptable
OMEGAMON does not directly support lists of full text nor the acceptable abbreviation are rejected.
assignment values.
User response
System action
The (*) assignment value is a quasi-list list assignment.
1. Correct the command specifications.
You may specify only the ASID and SUBPOOL
operands with the (*) assignment value. 2. Remove the command inhibit character (>).
User response OM8540 INSUFFICIENT MEMORY.
Make the following changes: REQUEST NOT PROCESSED
1. Correct the value assignment.

Explanation
The OMCSAA/CSAA DETAIL command might generate
a significant number of CSA Events Extract Records.
OM8530 ARGUMENT <text> NOT The nominal OMCSAA CSA Events Extraction Work
RECOGNIZED Area is only 5120 bytes. OMCSAA has logic that
acquires a larger Extraction Work Area, but that logic is
Explanation conditional.
Each argument is a keyword which must be specified

System action
immediately after the command on the command line.
The keyed parameter is not recognized as a valid OMCSAA command logic inhibits the automatic
OMCSAA command specification if an argument is acquisition of a larger Extraction Work Area in order
required. to minimize the overhead generated by continually
issuing GETMAIN requests to the operating system.
System action
User response
The OMCSAA command processing edits the first
keyed parameter following the command. That Either restrict the scope of the request or resubmit
parameter must be an argument. the command with the OMEGAMON action character in
column 1.
Note: The OMCSAA/CSAF command is an exception to
this rule. OM8541 INSUFFICIENT MEMORY. <xxxxxx>
KB ADDITIONAL MEMORY
REQUIRED

The OMCSAA/CSAA Events Extract Work Area may Increase the region size of the address space by a
be expanded but the expansion requires allocatable minimum of nnnK. Alternatively, use the DATA minor of
memory in SUBPOOL (0). SEEK to decrease the work size area by nnnK.
OM8551 WARNING WSIZ TOO SMALL -
System action ADDR= xxxxxxxx SIZE= nnnn
OMCSAA command processing has attempted to USED= nnnn.
acquire the memory required to support the Extract
Work Area. There is not enough memory available in Explanation
SUBPOOL (0).
The SEEK SRB to collect data failed to complete its
task because the data area it needed was small.
User response
Either restrict the scope of the OMCSAA/CSAA DETAIL System action
command or re-initialize a new OMEGAMON session
with a larger REGION size. None.
OM8542 SCREEN OUTPUT EXCEEDS User response

LROWS LIMIT
Use the DATA minor of SEEK to increase the work area.
Explanation OM8552 DEVICE INVALID OR OFFLINE
Irrespective of the size of the OMCSAA/CSAA Events
Extract Work Area, the ultimate limit upon the ability Explanation
of OMEGAMON to display the CSA Analyses is the
The specified device either was not found in the UCB
number of logical lines of display.
lookup table, or was found to be marked offline.
System action
System action
There are more lines of data to be displayed than
OMEGAMON can support.

Specify a valid volume or vary volume online.
Either restrict the scope of the OMCSAA/CSAA DETAIL
command or re-initialize a new OMEGAMON session OM8553 WARNING; cccc FAILED VALIDITY
with a larger LROWS size. CHECK
Note: The additional memory required to support a
larger number of logical lines of display may reduce Explanation
the ability to extract the analytical data from the CSA
The specified control block (ASCB, TCB, DSAB, JFCB,
Events Database.
or JFCX) failed validation in the SRB routine for DATA
OM8550 NOT ENOUGH MEMORY FOR minor of SEEK.
WORKAREA - nnnnnnK NEEDED.
System action
Explanation
DATA minor of SEEK does not collect dataset
The specified command could not obtain a work area. information for the address space which has failed
validation.
System action
User response
The command terminates.
OM8555 WARNING INVALID RETURN CODE
= xxxxxxxx (FROM DATA minor of
SEEK COMMAND)

The SRB to collect data failed to complete its task and This is an informational message only.
returned an invalid return code to the user.
OM8559 WARNING INVALID INTERVAL
TIME SPECIFIED.
System action
The specified sample interval must be between 5 and
User response 500 milliseconds.
problem. System action
OM8556 INVALID PARAMETER SPECIFIED. Processing continues with the default of 5
milliseconds assumed.
Explanation
User response
An invalid parameter was encountered on the SEEK or
DATA command line. This is an informational message only.
OM8560 WARNING INVALID SAMPLE
System action COUNT SPECIFIED.
Explanation
User response The specified sample count was greater than 100.
Check the syntax and re specify with the correct
parameter. System action
OM8557 VOLSER OR DEVICE PARAMETER Processing continues with the maximum of 1000
REQUIRED. samples assumed.

The volser or device address required by SEEK has not This is an informational message only.
been specified.
OMV001I OBVTAM VERSION Vnnn
INITIALIZATION
System action
None. Explanation
The OBVTAM support program, version nnn, is
User response initializing.
Specify the Volser or device address and reissue the
command. System action
OM8558 SPECIFIED ITEM NOT FOUND. OBVTAM processing continues.

A seek operation was not observed on the sample None.
number specified in the ITEM parameter, or no seek
OMV002I APPL applid OPENED
operations were observed for the specified jobname.
SUCCESSFULLY
System action
Explanation
No detail data items are displayed.
The OPEN macro for the VTAM ACB was successful.

System action OMV003I APPL IS IN CLEANUP
Initialization processing continues.
Explanation
User response VTAM has not completed recovery processing after an
OBVTAM failure.
None. OBVTAM is ready to accept a log on.
OMV003I APPL cccccccc FAILED TO OPEN - System action
reason
Once VTAM processing is complete, the network APPL
becomes available to OBVTAM automatically.
Explanation
OBVTAM attempted to open an ACB to VTAM with the User response
identifier cccccccc. The attempt failed for the reason
specified. None. This is an informational message only.
OMV003I APPL NOT DEFINED
System action
If the reason is a condition that can be retried Explanation
(for example, if the network APPL is inactive at The OBVTAM APPL was not defined to VTAM.
the time OBVTAM attempts access), OBVTAM retries
the operation for up to 30 minutes. Otherwise, the
OBVTAM network APPL stops processing. System action
OBVTAM terminates.
User response
The reasons that appear follow. Take the appropriate User response
action for the reason that appears with this message. Contact the VTAM systems programmer at your
OMV003I APPL ALREADY OPEN installation to define an APPL to VTAM for OBVTAM.
Start the OBVTAM again.
Explanation OMV003I VTAM ERROR CODE nn
Another MVS job or started task has the OBVTAM

network APPL allocated. Explanation
The error code associated with the VTAM OPEN ACB
System action process was nn.
The OBVTAM stops processing.

System action
User response If the error code is 14, OBVTAM retries the operation
for up to 30 minutes. Otherwise, OBVTAM stops
Contact the VTAM systems programmer at your processing.
installation.
OMV003I APPL IS INACTIVE User response
Write down the VTAM error code and contact the VTAM
Explanation systems programmer at your installation, or contact
OBVTAM attempted to open an ACB to VTAM for an IBM Software Support.
network APPL that was inactive. OMV003I VTAM IS NOT ACTIVE

OBVTAM attempts access again for up to 30 minutes. OBVTAM was started before VTAM.
User response
Activate the network APPL.

OBVTAM attempts to open the network APPL for up to OBVTAM processing continues; initialization starts for
30 minutes. an OMEGAMON session.

Start VTAM, then restart OBVTAM. None.
OMV004I OBVTAM MUST BE APF OMV007I SESSION INITIATION FAILED FOR
AUTHORIZED TO BE NON- aaaaaaaa/bbbbbbbb: cc dddd eeee
SWAPPABLE ffff
The OBVTAM start parameter included SWAP=N, but The initiation of a session between OBVTAM (network
OBVTAM cannot mark itself non-swappable without identifier aaaaaaaa) and Secondary Logical Unit
APF authorization. bbbbbbbb failed. These are the VTAM status values
associated with the request:
System action cc
VTAM request code
OBVTAM processing continues, but OBVTAM remains
swappable. dddd
VTAM return code information
User response eeee
SNA system sense field
If you want OBVTAM to be non-swappable, restart it
from an APF-authorized library. ffff
SNA user sense field
OMV005I cccccccc FM/TS PROFILE nnnn
NOT SUPPORTED System action
OBVTAM rejects the session request from SLU
Explanation
bbbbbbbb.
Secondary Logical Unit cccccccc tried to establish
a session using a VTAM Logmode that specifies an User response
FM/TS session profile of nnnn. OBVTAM supports
FM/TS profiles 0303 and 0202 only. Refer the VTAM status information to your Network
Support group or contact IBM Software Support for
assistance.
System action
OBVTAM rejects the session request from SLU ccccccc. OMV008I KOBDSQZ MODULE NOT FOUND.
NO DATA COMPRESSION
User response
Explanation
Select a VTAM Logmode which specifies a supported
FM/TS profile, or select an alternate device. The program module KOBDSQZ was not found in the
OBVTAM program library.
OMV006I SESSION ESTABLISHED FOR
aaaaaaaa/bbbbbbbb System action
OBVTAM processing continues, but the 3270 data
Explanation
stream created by OMEGAMON is not compressed for
A VTAM session was established between OBVTAM those sessions that requested data compression.
(network identifier aaaaaaaa) and Secondary Logical
Unit bbbbbbbb. User response

OMV009I ROWS/COLS IN CONFLICT WITH OMV013I WSF (QUERY) TIMEOUT - cccccccc
VTAM LOGMODE cccccccc
Explanation
Explanation
Terminal cccccccc has not replied to the WSF (Query)
The ROWS= and/or COLS= OMEGAMON startup sent by OBVTAM.
parameter does not match VTAM’s definition for the
terminal. The VTAM logmode used to start the session System action
was cccccccc.
OBVTAM ends the session with terminal cccccccc.
System action
User response
OBVTAM displays the OBUSRMSG panel and then
terminates. Configure terminal cccccccc to support WSF (Query)
or select a VTAM logmode that does not indicate that
WSF (Query) is supported.
User response
OMV980I SESSION REQUEST FAILED
Correct the values of the OBVTAM startup parameter
FOR cccccccc/aaaaaaaa -
or select another VTAM logmode that is the same as
INSUFFICIENT MEMORY
the OBVTAM startup parameter.
OMV010I TIMEOUT KEYWORD VALUE Explanation
INVALID - SET TO 0
OBVTAM (application cccccccc) failed to obtain
enough memory to establish a session with terminal
Explanation
aaaaaaaa.
The value of the OBVTAM start parameter keyword
TIMEOUT was not in the range 0–99. System action
OBVTAM rejects the session request from terminal
System action
aaaaaaaa.
User response
User response
It might be possible to start a session by using a
OBVTAM sets the TIMEOUT value to 0, and idle terminal with a smaller screen size, or by eliminating
OMEGAMON sessions are not subject to timeout the use of 3270 data stream compression. Specify
cancellation. the DC=N parameter as part of the OBVTAM startup
parameter to eliminate data compression. If the
User response session still cannot be started, it might be necessary
to increase the value of the MVS REGION SIZE to make
Correct the TIMEOUT value and restart OBVTAM. more memory available to OBVTAM.
OMV012I OMEGAMON SESSION TIMEOUT - OMV981I DEVICE ERROR aaaaaaaa
cccccccc DETECTED FOR bbbbbbbb/
cccccccc
Explanation
Explanation
The OMEGAMON session with terminal cccccccc was
idle for the length of time specified on the TIMEOUT OBVTAM (network identifier bbbbbbbb) received
parameter. device status information from Secondary Logical Unit
cccccccc. The information aaaaaaaa is the status
System action value received in an SNA LUSTAT command.
OBVTAM cancels the idle session.

System action
User response OBVTAM stops the session with SLU cccccccc.
You may start another session.

Refer the LUSTAT information to your Network Support Verify that the terminal supports extended attributes
group or contact IBM Software Support for assistance. and is properly defined to VTAM. If the terminal does
not support extended color, the OMEGAMON session
OMV982I GETMAIN FAILED - INCREASE
cannot be used with extended color support turned
REGION SIZE
on. If the problem persists, refer the VTAM status
information to your Network Support group or contact
Explanation IBM Software Support for assistance.
There is insufficient region size for OMEGAMON to OMV986I SESSION ERROR aa bbbb cccc
obtain buffers. dddd FOR eeeeeeee/ffffffff

OMEGAMON aborts the session start. An error occurred on the session between OBVTAM
(network identifier eeeeeeee) and Secondary Logical
User response Unit ffffffff. These are the VTAM status values
associated with the error:
See your installer to increase the region size.
aa
OMV983I OM= KEYWORD INVALID - VTAM request code
MODULE aaaaaaaa NOT FOUND bbbb
bbbbbbbb/cccccccc VTAM return code information
cccc
Explanation SNA system sense field
The module specified by the OM session start dddd
parameter could not be found by OBVTAM (network SNA user sense field
identifier bbbbbbbb). Module aaaaaaaa was specified
explicitly or by default.
System action
System action OBVTAM stops the session with SLU ffffffff.
OBVTAM stops the session with SLU cccccccc.

User response
User response Refer the VTAM status information to your Network
Support group or contact IBM Software Support for
Include module aaaaaaaa in the OBVTAM runtime assistance.
program library or specify a different module with the
OM session start parameter. OMV987I VTAM ACB CLOSE FAILED;
RETURN CODE=rc, REASON
OMV984I EXTENDED ATTRIBUTE ERROR CODE=rs
aaaa bbbbDETECTED FOR cccccccc
Explanation
Explanation
VTAM close processing failed as indicated.
Secondary Logical Unit cccccccc rejected a screen sent
to it by OMEGAMON. The screen might have contained
System action
extended color or highlighting attributes. The VTAM
status associated with the error is: aaaa - SNA system OBVTAM stops.
sense field and bbbb - SNA user sense field.
User response
System action
OBVTAM stops the session with SLU cccccccc.
OMV988I UNABLE TO START OBVTAM
SESSION (REASON CODE rs)

An error occurred while trying to start the VTAM OBVTAM stops processing
session, possibly because of lack of storage.
User response
System action
Record the message and contact IBM Software
OBVTAM stops processing Support. You may restart the session.
OMV994I TERMINATION REQUESTED BY
User response bbbbbbbb - REASON CODE xx
Try to increase region size in the startup JCL. If failure
recurs, contact IBM Software Support. Explanation
OMV989I TPEND EXIT-code DRIVEN FOR The Secondary Logical Unit bbbbbbbb requested
applid to terminate the VTAM session between itself and
OBVTAM. The VTAM reason code was xx.
Explanation
System action
Either a network shutdown is in progress, or the user
has varied the OBVTAM network APPL inactive. OBVTAM stops processing the OMEGAMON session
and then ends the VTAM session.
System action
User response
Normally none.
This might indicate a problem. If the message persists,
User response refer the VTAM reason code information to your
Network Support group or contact IBM Software
If this message recurs, contact IBM Software Support. Support for assistance.
OMV990I INVALID LOGON PASSWORD FOR OMV996I SESSION TERMINATED FOR
applid/sluname aaaaaaaa/bbbbbbbb
The password specified in the LOGON DATA parameter The VTAM session between OBVTAM (network
does not match the password in the PARM string. identifier aaaaaaaa) and Secondary Logical Unit
bbbbbbbb ended.
System action
System action
OBVTAM stops processing the log on process.
OBVTAM processing continues; OBVTAM accepts a
User response new session request from any SLU.
Determine the correct password and retry.

User response
OMV992I SESSION cccccccc - PGM CHK xxxx
None.
yyyyyyyy, aaaa + bbbb
OMV997I SESSION TERMINATION FAILED
Explanation FOR aaaaaaaa/bbbbbbbb: cc dddd
eeee ffff
OBVTAM encountered a program error while
processing the session with terminal cccccccc. The
Explanation
xxxx value is the program check interrupt code, the
yyyyyyyy value is the address where the program Session termination processing between OBVTAM
check occurred, the aaaa value is the module name (network identifier aaaaaaaa) and Secondary Logical
where the program check occurred, and the bbbb Unit bbbbbbbb failed. These are the VTAM status
value is the module offset where the program check values associated with the request:
occurred.

cc OMEGAMON sessions that are currently active beneath
VTAM request code it.
dddd
VTAM return code information System action
eeee OBVTAM begins termination processing.
SNA system sense field
ffff User response
SNA user sense field
None. This is an informational message about a normal
OBVTAM condition.
System action
OMV999I OBVTAM ENDED
OBVTAM stops servicing the session with SLU
bbbbbbbb.
Explanation
User response The OBVTAM support program ended.
Refer the VTAM status information to your Network
Support group or contact IBM Software Support for System action
assistance.
OMEGAMON stops processing.
OMV998I STOP COMMAND CAUSES
TERMINATION FOR applid User response
None. This is an informational message about a normal
Explanation OBVTAM condition.
The MVS operator issued an MVS STOP console
command, instructing OBVTAM to stop and all

Appendix A. Abend codes
The following information lists OMEGAMON for CICS KILL Services Transaction abend codes and
Resource Limiting abend codes which are generated from OMEGAMON for CICS.
KILL Services Transaction abend codes

OCKC System action
A dump is produced
Explanation
KILL/KILS/KILU/KILX/KILR commands terminate User response
transactions with an OCKC transaction abend code.
None
System action EIKI
A dump is produced
Explanation
User response As a result of a KILL/FORCE command, an EXEC CICS
ABEND has been issued against the task.
None
OCSD System action
A dump is produced
Explanation
If SHUTOPT=PURGE is specified on the KC2GLOB User response
macro in the KC2GLBcc module, OMEGAMON for CICS
purges user transactions waiting for terminal control None
input. This abend code is produced at CICS shutdown
time.
Resource Limiting abend codes

This information lists the OMEGAMON for CICS resource limiting abend codes.
Each of these codes indicates that the transaction exceeded the resource threshold specified in the
KOCRLIM macro of the global module and that ACTION=KILL was specified (or was the default). The task
is abended when the transaction exceeds the resource limit and ACTION=KILL is specified, unless the
transaction is executing under CEDF. In this case a message is issued to the terminal, ACTION=KILL is
ignored, and the transaction continues normal execution.
RLAD
ADABAS requests exceeded.
RLCG
CPU time on General Processor exceeded.
RLCP
CPU utilization exceeded.
RLCQ
CPU time on QR TCB exceeded.
RLDB
Db2 requests exceeded.
RLDC
DATACOM requests exceeded.

RLDL
DL/I requests exceeded.
RLDS
DSA storage utilization exceeded.
RLED
EDSA storage utilization exceeded.
RLEL
Elapsed time exceeded.
RLFC
File control requests exceeded.
RLID
IDMS requests exceeded.
RLMQ
MQ requests exceeded.
RLRN
RUNTIME threshold exceeded (time for tasks held due to MXT or Class maximum). This is the time the
task actually ran excluding time spent waiting for MXT or Class max tasks.
RLSU
SUPRA requests exceeded.

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following
ways for you to obtain the support you need:
Online
The following sites contain troubleshooting information:
• Go to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and
follow the instructions.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability workbench that helps you
resolve questions and problems with IBM software products. The ISA provides quick access to
support-related information and serviceability tools for problem determination. To install the ISA
software, go to http://www.ibm.com/software/support/isa.
Troubleshooting Guide
For more information about resolving problems, see the product's Troubleshooting Guide.

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can
send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases
payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be
the same on generally available systems. Furthermore, some measurement may have been estimated
through extrapolation. Actual results may vary. Users of this document should verify the applicable data
for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without
notice, and represent goals and objectives only.
This information is for planning purposes only. The information herein is subject to change before the
products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform
for which the sample programs are written. These examples have not been thoroughly tested under
all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright
notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. ©
Copyright IBM Corp. 2022. All rights reserved.
If you are viewing this information in softcopy form, the photographs and color illustrations might not
display.
Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies
or other technologies to collect product usage information, to help improve the end user experience,
to tailor interactions with the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings can help enable you
to collect personally identifiable information. If this Software Offering uses cookies to collect personally
identifiable information, specific information about this offering’s use of cookies is set forth below.
Depending upon the configurations deployed, this Software Offering may use session cookies that
collect each user’s user name for purposes of session management, authentication, and single sign-on
configuration. These cookies cannot be disabled.
If the configurations deployed for this Software Offering provide you as customer the ability to collect
personally identifiable information from end users via cookies and other technologies, you should seek

your own legal advice about any laws applicable to such data collection, including any requirements for
notice and consent.
For more information about the use of various technologies, including cookies, for these purposes,
See IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://
www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and Other Technologies”
and the “IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/
software/info/product-privacy.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Intel, Intel logo, and Intel Xeon, are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or
both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
Notices 647
Index
A BG0099 299
BG0100 299
abend codes 49 BG0101 299
adding CTG DLL library 19 BG0102 299
BG0103 299
BG0104 299
B BG0105 299
Basic System Services (BSS1) 10 BG0106 300
BG messages 291 BG0107 300
BG0001 291 BG0200 300
BG0002 291 BG0201 300
BG0006 291 BG0202 300
BG0007 291 BG0210 300
BG0008 291 BG0211 300
BG0010 291 BG0212 301
BG0011 292 BG0220 301
BG0012 292 BG0221 301
BG0013 292 BG0300 301
BG0014 292 BG0301 301
BG0019 292 BG0302 301
BG0021 292 BG0303 302
BG0022 292 BG0400 302
BG0024 293 BG0401 302
BG0035 293 BG0402 302
BG0036 293 BG0403 302
BG0037 293 BG0500 302
BG0038 293 BG0501 302
BG0039 293 BG0502 302
BG0040 294 BG0503 303
BG0041 294 BG0504 303
BG0042 294 BG0510 303
BG0043 294 BG0599 303
BG0044 294 BG0600 303
BG0059 294 BG0601 303
BG0070 295 BG0700 303
BG0071 295 BG0701 304
BG0072 295 BG0702 304
BG0078 295 BG0704 304
BG0079 295 BG0705 304
BG0080 295 BG0708 304
BG0081 296 BG0750 304
BG0082 296 BG0751 304
BG0083 296 BG0752 305
BG0084 296 BG0753 305
BG0085 296 BG0760 305
BG0086 296 BG0761 305
BG0087 297 BG0762 305
BG0088 297 BG0763 305
BG0089 297 BG0900 306
BG0091 297 BG0901 306
BG0092 297 BG0902 306
BG0093 297 BG0903 306
BG0094 298 BG1100 306
BG0095 298 BG1101 306
BG0096 298 BG1102 306
BG0097 298 BG1103 307
BG0098 298 BG1105 307
Index 649
BG1107 307 CI0545 446
BG1109 307 CI0546 446
BG1110 307 CI0550 446
BG1111 307 CI0551 447
BG1113 308 CI0552 447
BG1114 308 CI0553 447
BG1120 308 CI0560 447
BG1121 308 CI0561 447
BG1122 308 CI0562 447
BG1124 308 CI0563 448
BG1126 309 CI0564 448
BG1128 309 CI0565 448
BG1129 309 CI0567 448
BG1130 309 CI0580 448
BG1131 309 CI0585 448
BG1132 309 CI0586 448
BG1133 310 CI0587 449
BG1201 310 CI0588 449
BG1202 310 CI0592 449
BG1203 310 CI0593 449
BG1204 310 CI0594 449
BG1205 310 CI0603 449
BG1210 310 CI0604 449
BG1211 311 CI0605 450
BG1212 311 CI0606 450
BG1213 311 CI0607 450
BG1220 311 CI0608 450
BG1221 311 CI0609 450
BG1222 312 CI0700 450
BG1223 312 CI0715 450
BG801 312 CI0720 451
BGSMF015 312 CI0722 451
BGSMF016 312 CI0723 451
bss1 command 10 CI0724 451
CI0725 451
CI0726 451
C CI0727 451
CEE3501S 19 CI0730 452
CI0410 443 CI0731 452
CI0410-LSCX messages 443 CI0732 452
CI0411 443 CI0734 452
CI0412 443 CI0735 452
CI0413 443 CI0736 452
CI0414 443 CI0738 452
CI0415 443 CI0740 453
CI0416 443 CI0741 453
CI0417 444 CI0750 453
CI0418 444 CI0756 453
CI0419 444 CI0759 453
CI0420 444 CI0760 453
CI0421 444 CI0762 453
CI0425 444 CI0764 454
CI0510 444 CI0770 454
CI0530 445 CI0772 454
CI0531 445 CI0774 454
CI0532 445 CI0787 454
CI0533 445 CI0788 454
CI0534 445 CI0789 454
CI0535 445 CI0798 455
CI0536 445 CI0799 455
CI0537 446 CI0900 455
CI0542 446 CI0901 455
CI0543 446 CI0931 455
CI0544 446 CI0935 455

CI0938 455 CNDL176W 464
CI0940 456 CNDL177W 464
CI0941 456 CNDL178W 465
CI0951 456 CNDL179A 465
CI0952 456 CNDL180A 465
CI0960 456 CNDL181I 465
CI0961 456 CNDL182A 465
CI0968 456 CNDL183A 466
CI0969 457 CNDL184I 466
CI0970 457 CNDL185I 466
CI0971 457 CNDL189W 466
CI0985 457 commands
CI0995 457 RAS1 10
CI0997 457 service console 10
CI0998 458 communication tracing 12
CI0999 458 CPU usage
CICS regions do not display 18 long response time 43
CICS TG cross-product 29
dynamically controlling OMEGAMON monitoring exit CS075 466
(TxnMonitor) trace 13 CSAA000I 467
CICSplex configuration CSAA001I 467
OC commands 23 CSAA100E 467
CICSTG_Health_Critical situation 19 CSAA200E 467
CNDL001I 458 CSAA210E 467
CNDL003A 458 CSAA300E 467
CNDL019W 460 CSAA710E 469
CNDL103A 462 CSAA850I 471
CNDL104I 462 CSAA851I 471
CNDL105I 462 CSAA852I 471
CNDL152A 463 CSAA910W 472
CNDL157I 464
CNDL175W 464
Index 651
D DX6006 480
DX6007 480
data collection problems 37 DX6100 480
data not showing 41 DX6101 481
data store DX7000 481
full 37 DX7001 481
data warehouse queries 35 DX7002 481
debugging DX7003 481
communication 12 DX7004 481
default location 27 DX7100 481
degraded performance DX7200 482
historical data unavailable 45 DX9000 482
diagnostic data 4 DX9002 482
DTD file 26 DX9003 482
DUMP command 43 DX9005 482
DX0000 473 DX9800 482
DX0001 473 DX9999 482
DX0002 473
DX0003 473
DX0004 474
E
DX1000 474 EIKI 641
DX1050 474
DX1060 474
DX1100 474 F
DX1200 474
FFDC
DX1300 475
improvement 43
DX1500 475
fixpacks 1
DX1600 475
DX1700 475
DX1800 475 H
DX1900 475
DX2000 476 historical collection 21
DX2010 476
DX2020 476 I
DX2040 476
DX2050 476 IA0001 482
DX2060 476 IA0002 483
DX2065 476 IA0003 483
DX2070 477 IA0004 483
DX2080 477 IA0005 483
DX2090 477 IA0006 483
DX2100 477 IA0007 483
DX2110 477 IA0008 484
DX2120 477 IA0009 484
DX3000 477 IA0010 484
DX3001 477 IA0011 484
DX3002 478 IA0012 484
DX3003 478 IA0013 484
DX4000 478 IA0014 484
DX4001 478 IA0015 485
DX4002 478 IA0100 485
DX4100 478 IA0101 485
DX5000 478 IA0102 485
DX5001 478 IA0103 485
DX5002 479 IA0104 485
DX5003 479 IA0105 486
DX5100 479 IA0107 486
DX5200 479 IA0109 486
DX5201 479 IA0110 486
DX6001 479 IA0111 486
DX6002 479 IA0112 486
DX6003 480 IA0113 486
DX6004 480 IA0200 487, 489
DX6005 480 IA0201 487, 489

IA0202 487, 489 KC2EXPFF 313
IA0203 487, 489 KC2IMP 313
IA0204 487, 489 KC2IMP00 313
IA0205 487, 489 KC2IMPFF 313
IA0206 488, 490 KC2LG000 - KC2LG999 314
IA0207 488, 490 KCP message 51
IA0208 488, 490 kcp_slabatch utility 26
IA0209 488, 490 KCP0001E 51
IA0215 488, 490 KCP0002 51
IA0216 488, 490 KCP0003 51
IA0217 488, 490 KCP0004 51
IA0301 489, 491 KCP0005 51
IBM Software Support 5 KCP0006 52
IBM Support Assistant 3, 643 KCP0007 52
IBM Tivoli Distributed Monitoring and Application KCP0008 52
Management Wiki 643 KCP0009 52
ICE Chain member 35 KCP0010 52
import, export 27 KCP0011 52
IN0004 491 KCP0012 53
IN0005 491 KCP0013E 53
IN0006 491 KCP0014 53
IN0007 491 KCP0016 53
IN0050 491 KCP0017 53
IN0051 491 KCP0018 53
IN0060 491 KCP0019 54
IN0061 492 KCP0020 54
IN0062 492 KCP0021 54
IN0070 492 KCP0022 54
IN0080 492 KCP0023 54
IN0081 492 KCP0024 54
IN0082 492 KCP0025 54
IN0083 492 KCP0026 55
IN0090 493 KCP0027 55
IN0091 493 KCP0028 55
IN0092 493 KCP0029 55
IN0100 493 KCP0030 55
IN0101 493 KCP0031 56
IN0102 493 KCP0032 56
IN0103 494 KCP0032E 56
IN0104 494 KCP0033E 57
IN0105 494 KCP0034I 57
IN0106 494 KCP0040E 57
IN0900 494 KCP0051E 57
IN0901 494 KCP0070 57
IN0902 494 KCP0100 58
IN0903 494 KCP0101 58
IN0904 495 KCP0102 58
installation and configuration problems 15 KCP0103 58
integrated cryptographic service facility 29 KCP0104 59
introduction to troubleshooting 1 KCP0105 59
ISA 643 KCP0106 59
KCP0107I 59
KCP0108I 59
J KCP0109 59
Java version needed 27 KCP0110 60
KCP0111 60
KCP0112 60
K KCP0113 60
KCP0114E 60
KBB library service 7
KCP0190 60
KBBENV member 12
KCP0201 61
KC2 messages 313
KCP0202 61
KC2EXP 313
KCP0203 61
KC2EXP00 313
KCP0207 61
Index 653
KCP0210 61 KCP0758I 73
KCP0211 61 KCP0759E 73
KCP0212 62 KCP0760 73
KCP0213 62 KCP0761I 73
KCP0214 62 KCP0762 73
KCP0215 62 KCP0764 73
KCP0215 message 33 KCP0765W 73
KCP0216 62 KCP0803 74
KCP0217 63 KCP0804 74
KCP0218 63 KCP0807I 74
KCP0219E 63 KCP0808 74
KCP0220 63 KCP0809 74
KCP0222 63 KCP0810 74
KCP0223 63 KCP0811 74
KCP0224 63 KCP0812 75
KCP0225 64 KCP0813 75
KCP0226 64 KCP0815 75
KCP0229W 64 KCP0816 75
KCP0230E 64 KCP0817 75
KCP0231E 64 KCP0818 75
KCP0233W 64 KCP0819 76
KCP0241 65 KCP0920 76
KCP0242 65 KCP0946 76
KCP0243 65 KCP0980 76
KCP0244 65 KCP0981 76
KCP0246 66 KCP0982 76
KCP0247 66 KCP0983 76
KCP0248 66 KCP0984 77
KCP0249 66 KCP0985 77
KCP0251 66 KCP0986 77
KCP0252 67 KCP0999 77
KCP0253 67 KCP1040I 77
KCP0254 67 KCP1041I 78
KCP0255 67 KCP1042I 78
KCP0256 67 KCP1043I 78
KCP0257 67 KCP1044I 78
KCP0258 68 KCP1045E 78
KCP0260 68 KCP1046I 79
KCP0261 68 KCP1047E 79
KCP0262 68 KCP1050I 79
KCP0263I 68 KCP1051I 79
KCP0264I 69 KCP1101I 79
KCP0268 69 KCP1102I 79
KCP0269 69 KCP1103E 80
KCP0270W 69 KCP1104I 80
KCP0271W 69 KCP1120I 80
KCP0272W 70 KCP1121I 80
KCP0280 70 KCP1122I 80
KCP0281 70 KCP1123I 80
KCP0282 70 KCP1124W 80
KCP0283 70 KCP1125E 81
KCP0284 70 KCP1126E 81
KCP0285 71 KCP1127I 81
KCP0287 71 KCP1128I 81
KCP0288 71 KCP1129I 81
KCP0289 71 KCP1130I 82
KCP0290 71 KCP1131I 82
KCP0291 71 KCP1132E 82
KCP0295I 71 KCP1133I 82
KCP0296I 72 KCP1201E 82
KCP0330 72 KCP1202I 82
KCP0731I 72 KCP1203I 83
KCP0740I 72 KCP1204I 83
KCP0757I 72 KCP1205E 83

KCP1207E 83 KCP4252E 93
KCP1214E 83 KCP4253E 93
KCP1220I 83 KCP4254E 94
KCP1221I 83, 84 KCP4255E 94
KCP1256E 84 KCP4256E 94
KCP1259E 84 KCP4257E 94
KCP1260E 84 KCP4258W 94
KCP1261I 84 KCP4259E 94
KCP1262I 84 KCP4260E 95
KCP1263I 85 KCP4261E 95
KCP1264I 85 KCP4262W 95
KCP1265I 85 KCP4263W 95
KCP1270E 85 KCP4264E 95
KCP1271I 85 KCP4265I 95
KCP1272E 85 KCP4266E 96
KCP1273I 86 KCP4267E 96
KCP1274I 86 KCP4268E 96
KCP1275I 86 KCP4269E 96
KCP1276I 86 KCP4270E 96
KCP1278I 86 KCP4271I 96
KCP1300E 86 KCP4272I 97
KCP1301E 86 KCP4273E 97
KCP1302E 87 KCP4274I 97
KCP1303E 87 KCP4275I 97
KCP1304E 87 KCP4276E 97
KCP1305E 87 KCP4277I 97
KCP2455E 87 KCP4278I 97
KCP4000E 87 KCP4280E 98
KCP4001E 88 KCP4281E 98
KCP4003E 88 KCP4282E 98
KCP4004E 88 KCP4283E 98
KCP4005E 88 KCP4285E 98
KCP4007I 88 KCP4286E 98
KCP4008W 88 KCP5096I 99
KCP4009W 88 KCP5097E 99
KCP4010E 89 KCP5099I 99
KCP4012I 89 KCP5104E 99
KCP4013W 89 KCP5105E 99
KCP4014W 89 KCP5106E 99
KCP4015E 89 KCP5107E 100
KCP4016I 89 KCP5108E 100
KCP4017E 90 KCP5109E 100
KCP4018I 90 KCP5110E 100
KCP4020I 90 KCP5111E 100
KCP4021E 90 KCP5112E 100
KCP4022E 90 KCP5401I 101
KCP4023E 90 KCP5403E 101
KCP4024E 91 KCP5404E 101
KCP4025I 91 KCP5405E 101
KCP4026I 91 KCP5406E 101
KCP4027I 91 KCP5407E 102
KCP4028E 91 KCP5408E 102
KCP4029E 92 KCP5409I 102
KCP4030I 92 KCP5410I 102
KCP4031I 92 KCP5411I 102
KCP4032I 92 KCP5412I 102
KCP4033I 92 KCP5413I 102
KCP4151 92 KCP5414I 103
KCP4153 92 KCP5415I 103
KCP4247E 93 KCP5416I 103
KCP4248E 93 KCP5417I 103
KCP4249E 93 KCP5418I 103
KCP4250E 93 KCP5419I 103
KCP4251I 93 KCP5423I 103
Index 655
KCP5424I 104 KCP9200 114
KCP5425I 104 KCP9201 114
KCP5426I 104 KCP9202 114
KCP5428I 104 KCP9300 114
KCP5429I 104 KCP9311 115
KCP5430I 104 KCP9312 115
KCP5432I 104 KCP9313 115
KCP5433I 105 KCP9314 115
KCP5436I 105 KCP9315 115
KCP5437I 105 KCP9316 115
KCP5438I 105 KCP9317 115
KCP5439I 105 KCP9318 116
KCP5440I 105 KCP9320I 116
KCP5441I 106 KCP9321I 116
KCP5442I 106 KCP9322I 116
KCP5443I 106 KCP9323I 116
KCP5445I 106 KCP9324I 116
KCP5500E 106 KCP9325I 116
KCP5501E 106 KCP9326I 117
KCP5502E 106 KCP9327E 117
KCP5520E 107 KCP9328I 117
KCP8903I 107 KCP9329I 117
KCP8904I 107 KCP9330I 118
KCP8906I 108 KCP9331I 118
KCP9000 108 KCP9332I 118
KCP9001 108 KCP9333I 118
KCP9002 108 KCP9334I 118
KCP9003 109 KCP9335I 118
KCP9004 109 KCP9336I 119
KCP9005 109 KCP9337I 119
KCP9006 109 KCP9338I 119
KCP9007 109 KCP9339I 119
KCP9008 109 KCP9398 119
KCP9009 109 KCP9399 119
KCP9010 110 KCP9700 119
KCP9011 110 KCP9701 120
KCP9012 110 KCP9889 120
KCP9013 110 KCP9890 120
KCP9014 110 KCP9891 120
KCP9015 110 KCP9892 120
KCP9016 111 KCP9893 120
KCP9017 111 KCP9900 121
KCP9018 111 KCP9920 121
KCP9019 111 KCP9921 121
KCP9021 111 KCP9922 121
KCP9022 111 KCP9924 121
KCP9023 111 KCP9925 121
KCP9024 112 KCP9941 121
KCP9025 112 KCP9942 122
KCP9030 112 KCP9943 122
KCP9038 112 KCP9945 122
KCP9039 112 KCP9947 122
KCP9040 112 KCP9948 122
KCP9060 112 KCP9949 122
KCP9069 112 KCP9950 122
KCP9070 113 KCP9989 122
KCP9180W 113 KCP9990 123
KCP9181W 113 KCP9991 123
KCP9182I 113 KCP9992 123
KCP9183I 113 KCP9993 123
KCP9184E 113 KCP9994 123
KCP9185E 114 KCP9995 123
KCP9198 114 KCP9996 124
KCP9199 114 KCP9997 124

KCP9998 124 KCPEC4009E 125
KCP9999 124 KCPEC4010E 126
KCPAC messages 131 KCPEC4011I 126
KCPAC0580E 131 KCPEC4012I 126
KCPAC0584E 131 KCPFH messages 141
KCPAC4300I 132 KCPFH0001W 141
KCPAC4301I 132 KCPFH0002I 141
KCPAC4302I 132 KCPFH0003I 141
KCPAC4303I 132 KCPFH0004E 141
KCPAC4304I 132 KCPFH0005E 141
KCPAC4305E 132 KCPFH0009E 142
KCPAC4306E 132 KCPFH0010I 142
KCPAC4307E 133 KCPFH0011I 142
KCPAC4308E 133 KCPOC0001E 127
KCPAC4310E 133 KCPOC1038I 127
KCPAC4311E 133 KCPOC1049W 128
KCPAC4315E 134 KCPPA messages 143
KCPAC4316E 134 KCPPA0010E 143
KCPAC4319W 134 KCPPA0026E 143
KCPAC4323E 135 KCPPA0054I 144
KCPAC4355I 137 KCPPA0214W 146
KCPAC4375E 131, 138 KCPPA0226E 147
KCPAC4401I 138 KCPPA0227E 147
KCPDB001I 124 KCPPA0247E 148
KCPEC4000I 124 KCPPA0252E 148
KCPEC4004I 125, 126 KCPPA0262E 149
KCPEC4005W 125 KCPPA0263E 149
Index 657
KCPPA0265E 149 KCPPA1010E 161
KCPPA0286E 151 KCPPA7080I 163
KCPPA0287E 151 KCPPL messages 165
KCPPA0292E 151 KCPPL1205E 165
KCPPA0302I 152 KCPPL1207E 165
KCPPA0556E 157, 158 KCPPL1331E 170

KCPPL1357E 173 KCPPR1374E 186
KCPPR messages 175 KCPPR1375E 186
KCPPR0000E 175 KCPPR1376E 186
KCPPR0009E 176 KCPPR1390I 187
Index 659
KCPPR1489E 197 KCPSB1074W 208
KCPPR1490E 197 KCPSB1075E 208
KCPPR1493E 197 KCPSB1082I 209
KCPSB messages 201 KCPSB1093I 211
KCPSB1001I 201 KCPSB1094I 211
KCPSB1003I 201 KCPSB1096E 211
KCPSB1006E 201 KCPSB1099E 212
KCPSB1010W 202 KCPSB2003I 212
KCPSB1011E 202 KCPSB2004I 212
KCPSB1018W 203 KCPSB2011E 213
KCPSB1062I 206 KCPSB2031IE 216
KCPSB1069E 208 KCPSB2042W 218
KCPSB1071I 208 KCPSB2043W 218
KCPSB1072I 208 KCPSB2044W 218

KCPSB2046E 218 KCPSP0427E 229
KCPSB2047I 218 KCPSP0441E 229
KCPSB2049E 219 KCPSP0443E 230
KCPSB2051W 219 KCPSP0447E 230
KCPSG0001E 128 KCPSP0486E 231
KCPSG0004W 129 KCPSP0502E 232
KCPSP messages 221 KCPSP0503E 232
KCPSP0300E 221 KCPSP0506E 232
KCPSP0323E 222 KCPSP0540W 234
KCPSP0324E 223 KCPUI messages 235
KCPSP0325E 223 KCPUI0001E 235
KCPSP0341E 223 KCPUI0004I 235
KCPSP0367E 225 KCPXP001E 129
KCPSP0372E 225 KCPXP002W 129
KCPSP0380E 226 KCPXP003W 129
KCPSP0385E 226 KCPZZ messages 237
KCPSP0386E 226 KCPZZ0900E 237
KCPSP0399I 227 KCPZZ0997E 237
KCPSP0401E 227 KCPZZ0998I 237
KCPSP0403E 227 KDC_DEBUG environment variable 12
KCPSP0405E 228 KDSENV member 12
KCPSP0406E 228 KFWITM0831E
KCPSP0407E 228 link target not found 35
KCPSP0421E 228 KGW messages 239
KCPSP0422E 228 KGW0001E 239
KCPSP0423E 228 KGW0004E 239
KCPSP0425E 229 KGW0005I 239
KCPSP0426E 229 KGW0007E 239
Index 661
KGW0009E 239 KGW9014 250
KGW0017E 240 KGW9015E 250
KGW0022I 240 KGW9016 250
KGW0023I 240 KGW9017 250
KGW0027E 240 KGW9018 250
KGW0028E 240 KGW9019I 250
KGW0103I 240 KGW9021 250
KGW0300I 241 KGW9022E 251
KGW0301E 241 KGW9023I 251
KGW0302E 241 KGW9024 251
KGW0303E 241 KGW9025 251
KGW0304E 241 KGW9026I 251
KGW0305E 242 KGW9030I 251
KGW0306E 242 KGW9038E 251
KGW0307E 242 KGW9039E 252
KGW0308E 242 KGW9040I 252
KGW0309E 242 KGW9060I 252
KGW0310I 242 KGW9069E 252
KGW0311E 242 KGW9070I 252
KGW0312I 243 KGW9198I 252
KGW0313E 243 KGW9199I 252
KGW0601I 243 KGW9200E 253
KGW0603I 243 KGW9201E 253
KGW0604I 243 KGW9202E 253
KGW0605E 243 KGW9300I 253
KGW0613E 243 KGW9311I 253
KGW0623W 244 KGW9312I 253
KGW0760E 244 KGW9313I 253
KGW0761W 244 KGW9314I 254
KGW0762E 244 KGW9315I 254
KGW0764E 244 KGW9316I 254
KGW0765E 244 KGW9317I 254
KGW0766E 245 KGW9318I 254
KGW0800I 245 KGW9398I 254
KGW0808I 245 KGW9399I 254
KGW0810I 245 KGW9400I 255
KGW0811E 245 KGW9401I 255
KGW0812I 245 KGW9402I 255
KGW0813E 245 KGW9403I 255
KGW0818I 246 KGW9405I 255
KGW0820E 246 KGW9406I 255
KGW0821E 246 KGW9407I 255
KGW0828I 246 KGW9408I 256
KGW0946E 246 KGW9409I 256
KGW0980E 246 KGW9410I 256
KGW0981E 247 KGW9411I 256
KGW0982E 247 KGW9700I 256
KGW0983E 247 KGW9701E 256
KGW0984E 247 KGW9889I 257
KGW0985E 247 KGW9890I 257
KGW0986E 247 KGW9891I 257
KGW9000I 248 KGW9892I 257
KGW9002I 248 KGW9893I 257
KGW9003I 248 KGW9900I 257
KGW9004I 248 KGW9921I 257
KGW9005I 248 KGW9922E 258
KGW9006E 248 KGW9924I 258
KGW9007I 248 KGW9925I 258
KGW9008I 249 KGW9941I 258
KGW9009I 249 KGW9942I 258
KGW9010I 249 KGW9943I 258
KGW9011E 249 KGW9945I 258
KGW9012 249 KGW9947E 259
KGW9013E 249 KGW9948E 259

KGW9949E 259 KGWRM1024W 283
KGW9950I 259 KGWRM1025I 283
KGW9989I 259 KGWRM1026W 283
KGW9990I 259 KGWRM1027W 283
KGW9991I 259 KGWRM1028I 283
KGW9992I 260 KGWRM1029I 284
KGW9993E 260 KGWRM1030W 284
KGW9994I 260 KGWRM1031E 284
KGW9995I 260 KGWRM1032W 285
KGW9996I 260 KGWRM1998I 285
KGW9997E 260 KGWRM1999I 286
KGW9998I 261 KGWRTA00I 263
KGW9999I 261 KGWRTA01E 263
KGWAG0100E 261 KGWRTA02E 263
KGWAG0101E 261 KGWSPI messages 239
KGWAG0102E 261 KGWSPI00I 263
KGWAG0103E 261 KGWSPI01I 263
KGWDIO00E 262 KGWSPI02I 263
KGWDMP01I 262 KGWSPI03I 264
KGWDMP09I 262 KGWSPI04I 264
KGWNTR09E 262 KGWSPI05I 264
KGWRDR01I 262 KGWSPI06I 264
KGWRDR02I 262 KGWSPI07I 264
KGWRM messages 275, 287 KGWSPI08I 265
KGWRM0003E 275, 287 KGWSPI09I 265
KGWRM0007E 275 KGWSPI10I 265
KGWRM0029E 275 KGWSPI20E 265
KGWRM0034E 276 KGWSPI24W 266
KGWRM0040I 276 KGWSPI27E 267
KGWRM0096I 277 KGWSPI76W 268
KGWRM0100I 277 KGWSPI77I 268
KGWRM1003W 278 KGWSPI83W 269
KGWRM1006W 278 KGWSPI86E 270
KGWRM1009I 279 KGWSPI89S 270
KGWRM1012W 279 KGWSPI92W 272
KGWRM1019E 281 KGWTRACE 13
KGWRM1020W 282 KGWUI messages 289
KGWRM1021I 282 KGWUI0001I 289
KGWRM1022W 282 KGWUI0002I 289
KGWRM1023W 282 KGWXTR01E 273
Index 663
KGWXTR02I 273 log files (continued)
KGWXTR03W 274 started procedure 47
KGWXTR05W 274 logon 29
Kill Ice command 35 LSCX* 495
KILL ICE command 35
KLVIN411 message 12
KM5ENV member 12
M
known problems 3 message codes 49
KOCJ messages 315 message log location 47
KOCJO001 315 message prefixes 48
KOCJO002 315 messages
KOCJO003 315 KLVIN411 12
KOCJO004 315 Miscellaneous problems 35
KOCJO005 315 monitoring agent
KOCJO006 315 running out of storage 38
KOCJO007 316 multiple hub servers
KOCJO008 316 data not found 18
KOCJO009 316 multiple servers 18
KOCJO010 316
KOCJO011 316
KOCJO012 317 N
KOCJO013 317
navigation tree 18
KOCJO014 317
no data 21
KOCJO015 317
KOCJO016 317
KOCJO017 317 O
KOCJO018 318
KOCJO019 318 OB0101 497
KOCJO020 318 OB0101-OB9269 messages 497
KOCJO021 318 OB0102 497
KOCJO022 318 OB0104 497
KOCJO023 319 OB0106 497
KOCJO024 319 OB0107 497
KOCJO025 319 OB0108 497
KOCJO026 319 OB0109 498
KOCJO027 319 OB0110 498
KOCJO028 319 OB0111 498
KOCJO029 320 OB0112 498
KOCJO030 320 OB0113 498
KOCJO031 320 OB0114 498
KOCJO032 320 OB0115 498
KOCJO033 320 OB0116 498
KOCJO034 320 OB0117 499
KOCJO035 321 OB0119 499
KOCJO036 321 OB0120 499
KOCJO037 321 OB0121 499
KOCJO038 321 OB0122 499
KOCJO039 321 OB0123 499
KOCJO040 322 OB0124 499
KOCJO041 322 OB0125 500
KOCJO042 322 OB0126 500
KOCJO043 322 OB0127 500
KOCJO044 322 OB0128 500
KOCJO045 322 OB0129 500
KOCJO046 323 OB0130 500
KOCOME00 program OB0131 500
OPENAPI parameter 43 OB0132 501
OB0133 501
OB0134 501
L OB0135 501
OB0136 501
link fails 30
OB0137 501
Log Analyzer tool 4
OB0138 501
log file 26, 27
OB0139 502
log files

OB0140 502 OB0243 511
OB0141 502 OB0244 511
OB0142 502 OB0245 511
OB0143 502 OB0246 511
OB0144 502 OB0247 511
OB0145 502 OB0248 511
OB0146 502 OB0249 512
OB0147 503 OB0308 512
OB0148 503 OB0310 512
OB0150 503 OB0311 512
OB0151 503 OB0312 512
OB0152 503 OB0315 512
OB0153 503 OB0316 513
OB0154 503 OB0317 513
OB0155 504 OB0318 513
OB0156 504 OB0319 513
OB0160 504 OB0320 513
OB0161 504 OB0321 513
OB0162 504 OB0322 513
OB0163 504 OB0323 514
OB0164 504 OB0408 514
OB0165 505 OB0409 514
OB0170 505 OB0410 514
OB0171 505 OB0411 514
OB0172 505 OB0412 514
OB0201 505 OB0418 514
OB0202 505 OB0419 514
OB0203 505 OB0420 515
OB0204 506 OB0421 515
OB0205 506 OB0422 515
OB0206 506 OB0423 515
OB0207 506 OB0424 515
OB0208 506 OB0425 515
OB0209 506 OB0426 515
OB0210 506 OB0427 516
OB0211 506 OB0428 516
OB0212 507 OB0429 516
OB0213 507 OB0430 516
OB0214 507 OB0431 516
OB0215 507 OB0432 516
OB0219 507 OB0433 516
OB0220 507 OB0434 517
OB0221 507 OB0435 517
OB0222 508 OB0437 517
OB0223 508 OB0438 517
OB0224 508 OB0439 517
OB0225 508 OB0440 517
OB0226 508 OB0441 517
OB0227 508 OB0442 517
OB0228 508 OB0443 518
OB0229 509 OB0444 518
OB0230 509 OB0445 518
OB0231 509 OB0510 518
OB0232 509 OB0515 518
OB0233 509 OB0520 518
OB0234 509 OB0525 518
OB0235 509 OB0526 519
OB0236 510 OB0527 519
OB0237 510 OB0530 519
OB0238 510 OB0532 519
OB0239 510 OB0535 519
OB0240 510 OB0540 519
OB0241 510 OB0544 519
OB0242 510 OB0545 520
Index 665
OB0546 520 OB0970 533
OB0547 520 OB0971 533
OB0580 520 OB0972 533
OB0590 520 OB0973 533
OB0590 (cont.) 520–523 OB0974 534
OB0800 523 OB0975 534
OB0801 524 OB0976 534
OB0802 524 OB0977 534
OB0803 524 OB0978 534
OB0900 524 OB0979 534
OB0901 524 OB0980 534
OB0902 524 OB0981 534
OB0903 524 OB0982 535
OB0906 525 OB0983 535
OB0910 525 OB0984 535
OB0915 525 OB0985 535
OB0916 525 OB0986 535
OB0917 525 OB0987 535
OB0918 525 OB0988 536
OB0919 525 OB0989 536
OB0920 525 OB0990 536
OB0921 526 OB0991 536
OB0922 526 OB0992 536
OB0924 526 OB0993 536
OB0925 526 OB0994 536
OB0926 526 OB0995 537
OB0930 526 OB0996 537
OB0931 527 OB0997 537
OB0932 527 OB0998 537
OB0933 527 OB1112 537
OB0934 527 OB1116 537
OB0935 527 OB1120 538
OB0936 527 OB1124 538
OB0937 528 OB1140 538
OB0938 528 OB1148 538
OB0939 528 OB1191 538
OB0940 528 OB1195 538
OB0941 528 OB1196 538
OB0942 528 OB1197 539
OB0943 529 OB1198 539
OB0944 529 OB1199 539
OB0945 529 OB1200 539
OB0946 529 OB1201 539
OB0947 529 OB1202 539
OB0948 529 OB1203 539
OB0949 530 OB1204 539
OB0950 530 OB1210 540
OB0951 530 OB1211 540
OB0952 530 OB1212 540
OB0953 530 OB1213 540
OB0954 530 OB1214 540
OB0955 531 OB1215 540
OB0956 531 OB1216 540
OB0957 531 OB1217 541
OB0958 531 OB1220 541
OB0959 531 OB1250 541
OB0960 531 OB1251 541
OB0962 532 OB1252 541
OB0963 532 OB1253 541
OB0964 532 OB1254 541
OB0965 532 OB1255 541
OB0966 532 OB1256 542
OB0967 532 OB1257 542
OB0969 533 OB1258 542

OB1259 542 OB7010 552
OB1260 542 OB7011 552
OB1261 542 OB7012 552
OB1401 542 OB7013 552
OB1402 542 OB7014 552
OB1404 543 OB7017 552
OB1405 543 OB7018 552
OB1501 543 OB7019 553
OB1502 543 OB7020 553
OB1503 543 OB7021 553
OB1504 543 OB7022 553
OB1505 543 OB7023 553
OB1506 544 OB7024 553
OB1507 544 OB7025 554
OB1508 544 OB7026 554
OB1509 544 OB7027 554
OB1521 544 OB7028 554
OB1522 544 OB7029 554
OB1523 545 OB7030 554
OB1524 545 OB7031 554
OB1525 545 OB7032 555
OB1531 545 OB7033 555
OB1532 545 OB7036 555
OB1533 545 OB7037 555
OB1534 545 OB7038 555
OB1535 546 OB7039 555
OB1537 546 OB7040 555
OB1538 546 OB7041 556
OB1539 546 OB7042 556
OB2001 546 OB7101 556
OB2002 546 OB7102 556
OB2003 547 OB7103 556
OB2005 547 OB7104 556
OB2006 547 OB7105 556
OB2007 547 OB7106 556
OB2008 547 OB7107 557
OB2009 547 OB7108 557
OB2010 547 OB7109 557
OB2011 548 OB7110 557
OB2100 548 OB7111 557
OB2101 548 OB7112 557
OB2102 548 OB7113 557
OB2103 548 OB7114 558
OB2104 548 OB7115 558
OB2200 549 OB7117 558
OB2201 549 OB7118 558
OB2202 549 OB7119 558
OB2203 549 OB7120 558
OB2204 549 OB7121 558
OB2205 549 OB7122 558
OB2206 550 OB7123 559
OB2207 550 OB7125 559
OB4101 550 OB7126 559
OB4222 550 OB7127 559
OB4223 550 OB7128 559
OB7001 550 OB7129 559
OB7002 551 OB7130 559
OB7003 551 OB7131 560
OB7004 551 OB8110 560
OB7005 551 OB8111 560
OB7006 551 OB8112 560
OB7007 551 OB8113 560
OB7008 551 OB8114 560
OB7009 551 OB8115 561
Index 667
OB8116 561 OB9015 570
OB8117 561 OB9016 570
OB8118 561 OB9017 570
OB8121 561 OB9018 570
OB8130 561 OB9019 570
OB8131 561 OB9020 571
OB8132 561 OB9021 571
OB8202 562 OB9022 571
OB8203 562 OB9023 571
OB8204 562 OB9024 571
OB8205 562 OB9025 571
OB8206 562 OB9026 572
OB8207 562 OB9027 572
OB8208 563 OB9028 572
OB8209 563 OB9029 572
OB8277 563 OB9030 572
OB8280 563 OB9031 572
OB8281 563 OB9032 572
OB8282 563 OB9033 573
OB8283 563 OB9034 573
OB8284 564 OB9035 573
OB8285 564 OB9036 573
OB8286 564 OB9037 573
OB8287 564 OB9038 573
OB8288 564 OB9039 573
OB8289 564 OB9040 574
OB8290 564 OB9041 574
OB8291 564 OB9042 574
OB8292 565 OB9043 574
OB8293 565 OB9044 574
OB8294 565 OB9045 574
OB8295 565 OB9089 575
OB8296 565 OB9090 575
OB8310 565 OB9144 575
OB8312 565 OB9145 575
OB8313 566 OB9146 575
OB8320 566 OB9147 575
OB8321 566 OB9148 575
OB8322 566 OB9149 576
OB8323 566 OB9150 576
OB8324 566 OB9151 576
OB8325 566 OB9152 576
OB8326 566 OB9153 576
OB8327 567 OB9154 576
OB8501 567 OB9155 576
OB8551 567 OB9156 576
OB8601 567 OB9157 577
OB8602 567 OB9158 577
OB8603 567 OB9261 577
OB8604 568 OB9262 577
OB8605 568 OB9263 577
OB9001 568 OB9269 577
OB9003 568 OBV101 579
OB9004 568 OBV101-OMV9991 messages 579
OB9005 568 OBV102 579
OB9006 568 OBV103 579
OB9007 568 OBV104 579
OB9008 569 OBV105 579
OB9009 569 OBV106 579
OB9010 569 OBV107 579
OB9011 569 OBV108 580
OB9012 569 OBV109 580
OB9013 569 OBV110 580
OB9014 570 OBV111 580

OBV112 580 OBV301 589
OBV113 580 OBV302 589
OBV114 580 OBV303 589
OBV115 580 OBV304 589
OBV116 581 OBV305 589
OBV117 581 OBV306 589
OBV118 581 OBV307 590
OBV119 581 OBV308 590
OBV120 581 OBV309 590
OBV121 581 OBV310 590
OBV122 581 OBV311 590
OBV123 581 OBV312 590
OBV124 582 OBV313 590
OBV125 582 OBV314 591
OBV126 582 OBV315 591
OBV127 582 OBV316 591
OBV128 582 OBV317 591
OBV129 582 OBV318 591
OBV130 582 OBV319 591
OBV131 582 OBV320 592
OBV132 583 OBV321 592
OBV133 583 OBV322 592
OBV134 583 OBV323 593
OBV135 583 OC DISPLAY, PLEX=cicsplex, command 23
OBV136 583 OC DISPLAY, PLEXRULES command 23
OBV201 583 OC DISPLAY,PLEX=cicsplex command 24
OBV202 583 OC DISPLAY,PLEXRULES command 24
OBV203 584 OC DISPLAY,PREFERENCES command 25
OBV204 584 OC messages 325
OBV205 584 OC STATUS, CICSPLEX, command 23
OBV206 584 OC STATUS,CICSPLEX command 23
OBV207 584 OC0001 325
OBV208 584 OC0002 325
OBV209 584 OC0003 325
OBV210 585 OC0004 325
OBV211 585 OC0005 325
OBV212 585 OC0006 326
OBV213 585 OC0007 326
OBV214 585 OC0008 326
OBV215 585 OC0009 326
OBV216 585 OC0010 326
OBV217 585 OC0011 326
OBV218 586 OC0012 327
OBV219 586 OC0013 327
OBV220 586 OC0014 327
OBV221 586 OC0015 327
OBV222 586 OC0016 327
OBV223 586 OC0017 328
OBV224 586 OC0018 328
OBV225 587 OC0019 328
OBV226 587 OC0020 328
OBV228 587 OC0021 328
OBV229 587 OC0022 328
OBV230 587 OC0023 329
OBV231 587 OC0024 329
OBV232 587 OC0025 329
OBV233 588 OC0026 329
OBV234 588 OC0030 329
OBV235 588 OC0031 330
OBV236 588 OC0032 330
OBV237 588 OC0033 330
OBV238 588 OC0061 330
OBV239 588 OC0063 330
OBV300 589 OC0066 330
Index 669
OC0068 330 OC0207 340
OC0070 331 OC0208 340
OC0071 331 OC0209 340
OC0072 331 OC0210 341
OC0073 331 OC0214 341
OC0076 331 OC0215 341
OC0082 331 OC0217 341
OC0083 331 OC0218 341
OC0084 332 OC0219 341
OC0085 332 OC0224 342
OC0086 332 OC0225 342
OC0099 332 OC0226 342
OC0104 332 OC0232 342
OC0112 332 OC0233 342
OC0113 333 OC0234 342
OC0114 333 OC0235 342
OC0115 333 OC0236 342
OC0117 333 OC0237 343
OC0118 333 OC0245 343
OC0119 333 OC0251I 343
OC0132 334 OC0252 343
OC0133 334 OC0253 343
OC0134 334 OC0260 343
OC0135 334 OC0261 344
OC0136 334 OC0262 344
OC0137 334 OC0263 344
OC0138 334 OC0264 344
OC0139 335 OC0265 344
OC0142 335 OC0266 344
OC0143 335 OC0267 345
OC0144 335 OC0268 345
OC0145 335 OC0269 345
OC0146 335 OC0270 345
OC0160 336 OC0271 345
OC0163 336 OC0272 345
OC0164 336 OC0273 346
OC0165 336 OC0274 346
OC0166 336 OC0275 346
OC0167 336 OC0276 346
OC0168 336 OC0277 346
OC0169 337 OC0278 346
OC0170 337 OC0279 346
OC0173 337 OC0281 347
OC0175 337 OC0282 347
OC0176 337 OC0283 347
OC0177 337 OC0284 348
OC0178 338 OC0285 348
OC0179 338 OC0300 348
OC0180 338 OC0301 348
OC0181 338 OC0302 348
OC0183 338 OC0303 349
OC0184 338 OC0304 349
OC0185 338 OC0305 349
OC0186 339 OC0306 349
OC0187 339 OC0307 349
OC0188 339 OC0308 349
OC0189 339 OC0309 349
OC0190 339 OC0310 350
OC0196 339 OC0311 350
OC0201 339 OC0312 350
OC0202 340 OC0313 350
OC0203 340 OC0314 350
OC0204 340 OC0315 350
OC0205 340 OC0316 351

OC0320 351 OC0523 361
OC0321 351 OC0524 361
OC0322 351 OC0525 362
OC0330 351 OC0526 362
OC0380 352 OC0527 362
OC0390 352 OC0528 362
OC0400 352 OC0529 362
OC0401 352 OC0530 362
OC0402 352 OC0531 363
OC0403 353 OC0532 363
OC0404 353 OC0533 363
OC0405 353 OC0534 363
OC0406 353 OC0535 363
OC0407 353 OC0536 363
OC0408 354 OC0537 363
OC0409 354 OC0538 364
OC0410 354 OC0539 364
OC0411 354 OC0540 364
OC0412 354 OC0541 364
OC0413 354 OC0542 364
OC0414 355 OC0543 364
OC0415 355 OC0544 364
OC0416 355 OC0545 365
OC0417 355 OC0546 365
OC0418 355 OC0549 365
OC0420 356 OC0590 365
OC0421 356 OC0592 365
OC0422 356 OC0593 365
OC0423 356 OC0595 365
OC0424 356 OC0600 366
OC0425 356 OC0601 366
OC0426 356 OC0602 366
OC0427 356 OC0603 366
OC0428 357 OC0604 366
OC0429 357 OC0605 366
OC0430 357 OC0606 366
OC0431 357 OC0607 367
OC0432 357 OC0624 367
OC0434 357 OC0625 367
OC0435 358 OC0700 367
OC0436 358 OC0701 367
OC0437 358 OC0702 367
OC0438 358 OC0703 367
OC0441I 358 OC0704 368
OC0490 358 OC0705 368
OC0491 359 OC0706 368
OC0492 359 OC0707 368
OC0493 359 OC0708 368
OC0495 359 OC0709 368
OC0500 359 OC0710 368
OC0501 359 OC0711 369
OC0502 359 OC0712 369
OC0503 360 OC0713 369
OC0504 360 OC0714 369
OC0505 360 OC0716 369
OC0506 360 OC0718 369
OC0507 360 OC0719 369
OC0508 360 OC0720 370
OC0509 360 OC0721 370
OC0510 361 OC0723 370
OC0515 361 OC0724 370
OC0520 361 OC0750 370
OC0521 361 OC0752 370
OC0522 361 OC0753 371
Index 671
OC0755 371 OC0963 381
OC0759 371 OC0964 381
OC0760 371 OC0965 381
OC0761 371 OC0966 381
OC0762 371 OC0967 382
OC0763 372 OC0970 382
OC0764 372 OC0972 382
OC0765 372 OC0997 382
OC0766 372 OC0998 382
OC0767 372 OC0999 382
OC0795 372 OC1000 382
OC0796 373 OC1001 383
OC0799 373 OC1002 383
OC0800 373 OC1003 383
OC0801 373 OC1004 383
OC0802 373 OC1005 383
OC0803 373 OC1006 384
OC0804 373 OC1007 384
OC0805 374 OC1008 384
OC0806 374 OC1009 384
OC0807 374 OC1010 384
OC0808 374 OC1011 384
OC0809 374 OC1012 384
OC0810 375 OC1013 385
OC0811 375 OC1014 385
OC0812 375 OC1015 385
OC0813 375 OC1016 385
OC0814 375 OC1017 385
OC0815 375 OC1018 385
OC0816 375 OC1019 385
OC0817 376 OC1020 386
OC0818 376 OC1021 386
OC0819 376 OC1022 386
OC0820 376 OC1023 386
OC0821 376 OC1024 386
OC0822 376 OC1025 386
OC0823 377 OC1026 386
OC0824 377 OC1027 387
OC0827 377 OC1028 387
OC0830 377 OC1029 387
OC0831 377 OC1030 387
OC0832 377 OC1031 387
OC0833 378 OC1032 387
OC0834 378 OC1033 388
OC0835 378 OC1034 388
OC0836 378 OC1035W 388
OC0837 378 OC1036 388
OC0838 378 OC1037 388
OC0839 378 OC1099 388
OC0850 379 OC1100 389
OC0851 379 OC1101 389
OC0852 379 OC1102 389
OC0853 379 OC1130 389
OC0910 379 OC1131 389
OC0940 379 OC1132 389
OC0941 380 OC1133 390
OC0942 380 OC1134 390
OC0943 380 OC1135 390
OC0944 380 OC1136 390
OC0945 380 OC1137 390
OC0946 380 OC1140 391
OC0960 380 OC1141 391
OC0961 381 OC1142 391
OC0962 381 OC1143 391

OC1144 391 OC1230 401
OC1145 391 OC1231 401
OC1146 392 OC1240 401
OC1147 392 OC1241 401
OC1148 392 OC1242 401
OC1149 392 OC1243 402
OC1150 392 OC1244 402
OC1151 392 OC1245 402
OC1152 392 OC1246 402
OC1153 393 OC1247 402
OC1154 393 OC1401 402
OC1155 393 OC1402 403
OC1156 393 OC1403 403
OC1160 393 OC1404 403
OC1161 393 OC1405 403
OC1162 393 OC1406 403
OC1163 394 OC2001 403
OC1164 394 OC2002 403
OC1165 394 OC2003 404
OC1166 394 OC2004 404
OC1167 394 OC2005 404
OC1168 394 OC2020I 404
OC1169 394 OC2021I 405
OC1170 395 OC2022I 406
OC1171 395 OC2051 406
OC1172 395 OC2053 406
OC1173 395 OC2054 407
OC1174 395 OC2055 407
OC1175 395 OC2060 407
OC1176 395 OC2071 407
OC1177 396 OC2072 407
OC1178 396 OC2073 407
OC1179 396 OC2074 408
OC1180 396 OC2200 408
OC1182 396 OC2201 408
OC1183 396 OC2202 408
OC1184 396 OC2203 408
OC1190 397 OC2204 408
OC1191 397 OC2205 408
OC1192 397 OC2206 408
OC1193 397 OC2207 409
OC1200 397 OC2208 409
OC1201 397, 398 OC2209 409
OC1202 398 OC2210 409
OC1203 398 OC2220 409
OC1204 398 OC2221 409
OC1208 398 OC2222 410
OC1209 398 OC2223 410
OC1210 398 OC2224 410
OC1211 399 OC2225 410
OC1212 399 OC2226 410
OC1213 399 OC2227 410
OC1214 399 OC2228 410
OC1215 399 OC2229 410
OC1216 399 OC2300 411
OC1217 399 OC3001 411
OC1218 400 OC3002 411
OC1223 400 OC3003 411
OC1224 400 OC3051 411
OC1225 400 OC3052 411
OC1226 400 OC3053 411
OC1227 400 OC3054 412
OC1228 401 OC3401 412
OC1229 401 OC3402 412
Index 673
OC3403 412 OC4061 422
OC3404 412 OC4101 423
OC3405 412 OC4102 423
OC3406 412 OC4103 423
OC3407 413 OC4104 423
OC3411 413 OC4105 423
OC3412 413 OC4106 423
OC3413 413 OC4107 423
OC3414 413 OC4108 424
OC3415 413 OC4109 424
OC3416 413 OC4151 424
OC3417 414 OC4152 424
OC3420 414 OC4153 424
OC3422 414 OC4154 424
OC3423 414 OC4200 425
OC3430 414 OC4210 425
OC3432 414 OC4221 425
OC3433 414 OC4222 425
OC3434 415 OC4230 425
OC3460 416 OC4231 425
OC3461 416 OC4232 425
OC3462 416 OC4233 426
OC3463 417 OC4401 426
OC3464 417 OC4402 426
OC3500 417 OC5000 426
OC3501 417 OC5001 426
OC3502 417 OC5002 426
OC3503 417 OC5003 427
OC3504 417 OC5004 427
OC3505 418 OC5005 427
OC4001 418 OC5006 427
OC4002 418 OC5007 427
OC4003 418 OC5008 427
OC4004 418 OC5009 428
OC4005 418 OC5010 428
OC4006 418 OC5011 428
OC4007 419 OC5012 428
OC4008 419 OC5013 428
OC4009 419 OC5014 428
OC4010 419 OC5020 429
OC4011 419 OC5021 429
OC4012 419 OC5022 429
OC4013 419 OC5023 429
OC4014 419 OC5024 429
OC4015 420 OC5025 430
OC4016 420 OC5026 430
OC4017 420 OC5027 430
OC4020 420 OC5028 430
OC4021 420 OC5029 430
OC4023 420 OC5030 430
OC4024 420 OC5031 431
OC4026 421 OC5032 431
OC4027 421 OC5033 431
OC4030 421 OC5034 431
OC4031 421 OC5035 431
OC4040 421 OC5036 431
OC4041 421 OC5037 432
OC4042 421 OC5038 432
OC4043 422 OC5039 432
OC4044 422 OC5040 432
OC4045 422 OC5041 432
OC4050 422 OC5043 432
OC4051 422 OC5044 433
OC4060 422 OC5045 433

OC5046 433 OM20008 594
OC5047 433 OM20009 594
OC5048 433 OM20010 594
OC5049 433 OM20011 595
OC5050 433 OM20012 595
OC5051 434 OM20013 595
OC5052 434 OM20016 595
OC5053 434 OM20017 595
OC5054 434 OM20018 595
OC5055 434 OM22001 595
OC5056 434 OM22002 596
OC5057 435 OM22003 596
OC5058 435 OM22004 596
OC5059 435 OM22005 596
OC5060 435 OM22006 596
OC5061 435 OM22007 596
OC5062 435 OM22008 596
OC5064 436 OM22009 597
OC5065 436 OM22010 597
OC5066 436 OM22013 597
OC5067 436 OM22014 597
OC5068 436 OM22015 597
OC5069 436 OM22016 597
OC5070 437 OM22017 598
OC5071 437 OM22018 598
OC5072 437 OM22019 598
OC5073 437 OM22020 598
OC5074 437 OM22021 598
OC5075 437 OM22022 598
OC5076 437 OM22023 599
OC5077 438 OM22024 599
OC5078 438 OM22030 599
OC5079 438 OM22031 599
OC5080 438 OM22032 599
OC5100 438 OM22033 599
OC5101 438 OM22034 599
OC5102 439 OM22035 600
OC5103 439 OM22036 600
OC5104 439 OM22037 600
OC5105 439 OM7104 600
OC5106 439 OM7120 600
OC5107 439 OM7121 600
OC5108 440 OM7122 600
OC5109 440 OM7123 601
OC5110 440 OM7124 601
OC5111 440 OM7125 601
OC5112 440 OM7126 601
OC5115I 440 OM7130 601
OC5117E 441 OM7150 601
OC8900 441 OM7151 602
OC8902 441 OM7152 602
OC8903 442 OM7153 602
OCKC 641 OM7154 602
OCSD 641 OM7155 602
OM0904 593 OM7156 602
OM0905 593 OM7157 602
OM0906 593 OM7158 603
OM20001 593 OM7159 603
OM20002 593 OM7160 603
OM20003 593 OM7161 603
OM20004 594 OM7162 603
OM20005 594 OM7163 603
OM20006 594 OM7164 604
OM20007 594 OM7165 604
Index 675
OM7167 604 OM8270 613
OM7168 604 OM8271 613
OM7180 604 OM8272 613
OM7181 604 OM8273 613
OM7182 605 OM8274 614
OM7183 605 OM8275 614
OM7184 605 OM8276 614
OM7185 605 OM8277 614
OM7198 605 OM8278 614
OM7199 605 OM8279 614
OM8100 606 OM8280 614
OM8101 606 OM8281 615
OM8102 606 OM8283 615
OM8103 606 OM8284 615
OM8104 606 OM8285 615
OM8112 606 OM8286 615
OM8113 606 OM8287 615
OM8115 606 OM8288 615
OM8116 607 OM8289 615
OM8120 607 OM8290 616
OM8121 607 OM8291 616
OM8122 607 OM8292 616
OM8123 607 OM8293 616
OM8124 607 OM8297 616
OM8125 607 OM8298 616
OM8126 608 OM8299 616
OM8127 608 OM8300 617
OM8128 608 OM8305 617
OM8130 608 OM8306 617
OM8140 608 OM8307 617
OM8141 608 OM8308 617
OM8142 608 OM8309 617
OM8143 609 OM8310 618
OM8144 609 OM8313 618
OM8145 609 OM8314 618
OM8146 609 OM8315 618
OM8147 609 OM8323 618
OM8148 609 OM8324 618
OM8149 609 OM8324 (IMS) 618
OM8150 609 OM8325 619
OM8201 610 OM8326 619
OM8203 610 OM8327 619
OM8204 610 OM8328 619
OM8210 610 OM8329 619
OM8211 610 OM8330 619
OM8212 610 OM8331 620
OM8213 610 OM8332 620
OM8214 611 OM8333 620
OM8215 611 OM8335 620
OM8216 611 OM8336 620
OM8217 611 OM8339 620
OM8218 611 OM8342 621
OM8230 611 OM8343 621
OM8231 611 OM8348 621
OM8240 612 OM8349 621
OM8241 612 OM8350 621
OM8242 612 OM8351 621
OM8243 612 OM8352 622
OM8244 612 OM8353 622
OM8245 612 OM8354 622
OM8246 612 OM8355 622
OM8247 613 OM8356 622
OM8248 613 OM8357 622
OM8260 613 OM8358 622

OM8359 623 OM8541 632
OM8360 623 OM8542 633
OM8361 623 OM8550 633
OM8362 623 OM8551 633
OM8363 623 OM8552 633
OM8370 623 OM8553 633
OM8371 624 OM8555 633
OM8372 624 OM8556 634
OM8373 624 OM8557 634
OM8376 624 OM8558 634
OM8377 624 OM8559 634
OM8378 624 OM8560 634
OM8380 624 OMEGAMON for CICS on z/OS 41
OM8381 625 OMEGAMON for CICS TG on z/OS 41
OM8382 625 OMEGAMON II for CICS abend codes 641
OM8383 625 OMV001I 634
OM8384 625 OMV002I 634
OM8385 625 OMV003I 635
OM8386 625 OMV003I (cont.) 635
OM8387 625 OMV004I 636
OM8388 626 OMV005I 636
OM8389 626 OMV006I 636
OM8390 626 OMV007I 636
OM8391 626 OMV008I 636
OM8392 626 OMV009I 637
OM8400 626 OMV010I 637
OM8401 626 OMV012I 637
OM8402 627 OMV013I 637
OM8403 627 OMV980I 637
OM8406 627 OMV981I 637
OM8407 627 OMV982I 638
OM8410 627 OMV983I 638
OM8411 627 OMV984I 638
OM8420 627 OMV986I 638
OM8421 628 OMV987I 638
OM8430 628 OMV988I 638
OM8440 628 OMV989I 639
OM8500 628 OMV990I 639
OM8501 628 OMV992I 639
OM8502 628 OMV994I 639
OM8503 628 OMV996I 639
OM8504 629 OMV997I 639
OM8505 629 OMV998I 640
OM8506 629 OMV999I 640
OM8510 629 orphaned transactions
OM8511 629 defined 19
OM8512 629
OM8513 629
OM8514 630
P
OM8515 630 pdcollect tool 4
OM8516 630 performance problems 43
OM8517 630 permission 27
OM8518 630 post installation configuration 19
OM8519 630 problem determination
OM8520 630 communication 12
OM8521 631 pruning agent failure 36
OM8522 631 PSP bucket 1
OM8523 631 PTFs 1
OM8525 631
OM8526 631
OM8527 632 R
OM8530 632
RAS1 5, 7
OM8531 632
RAS1 command 10
OM8540 632
Index 677
RAS1 traces tracing
KBB library service 7 communication 12
levels 8 dynamically controlling OMEGAMON monitoring exit
output, redirecting 12 (TxnMonitor) trace 13
redirecting output 12 KBB library service 7
syntax 11 levels 8
unit 8 output, redirecting 12
RAS1 tracing 4 redirecting output 12
region status syntax 11
CICSplex region overview 18 unit 8
reporting problems 49 troubleshooting 1, 15, 23, 37, 43
Resource-Limiting abend codes 641 troubleshooting checklist 1
return data to table 44 troubleshooting process 1
RKANPARU data set 8, 12
RKGWSLOG file 47
RKLVLOG 4
U
RKLVLOG file 47 U200 port 21
unit traces 8
S usage problems 23
screen logging
OMEGAMON for CICS (3270) 37
W
script fails 30 warehousing
Self describing agent monitoring agent 44
bad installation 15 remote procedure calls 44
installation record 17 WLM sub task 33
Java root directory not valid 15
prior versions 17
TEMS_JAVA_BINPATH parameter 15 X
Service Console
XML file 26
commands 10
defined 8
enhanced 3270UI 9
OMEGAMON enhanced 3270 user interface 9
starting 9
Service Level Analysis configuration 33
SLA Batch Utility 27
SLA Batch Utility, problems 26
SLA definitions 26, 27
Software Support 643
SQL queries 35
STDERR 7
summarization
pruning 36
Summarization and Pruning 35
support assistant 643
sweep policy updates 19
sweepInterval parameter 19
sweepTimeout parameter 19
symptom catalog 4
syntax, RAS1 traces 11
T
terminal emulator 29
terminal emulator session 30
Tivoli Enterprise Portal 29
Tivoli Enterprise Portal Server
CICS region is not listed 18
RKCPXM DD card 18
Tivoli Enterprise Portal workspace 41
TnxMonitor 7
traces 7

IBM®
Product Number: 5698-T07

Omcics Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Omcics Troubleshooting

Uploaded by

Copyright:

Available Formats

IBM Z OMEGAMON for CICS

Chapter 1. Troubleshooting Guide.......................................................................... 1

Chapter 2. Setting up traces...................................................................................7

Chapter 3. Troubleshooting installation and configuration problems..................... 15

Chapter 4. Troubleshooting usage problems......................................................... 23

Chapter 5. Tivoli Enterprise Portal - based issues................................................. 29

Chapter 6. Problems with Service Level Analysis.................................................. 33

Chapter 7. Miscellaneous problems...................................................................... 35

Chapter 8. Troubleshooting data collection problems............................................37

Chapter 9. Troubleshooting performance problems...............................................43

Chapter 10. Messages overview........................................................................... 47

Chapter 11. KCP messages.................................................................................. 51

Chapter 12. KCPAC messages.............................................................................131

Chapter 13. KCPFH messages............................................................................ 141

Chapter 14. KCPPA messages............................................................................ 143

Chapter 15. KCPPL messages.............................................................................165

Chapter 17. KCPSB messages............................................................................ 201

Chapter 18. KCPSP messages............................................................................ 221

Chapter 19. KCPUI messages............................................................................. 235

Chapter 20. KCPZZ messages.............................................................................237

Chapter 21. KGW messages............................................................................... 239

Chapter 22. KGWRM messages...........................................................................275

Chapter 23. KGWRM messages...........................................................................287

Chapter 24. KGWUI messages............................................................................289

Chapter 25. BG messages.................................................................................. 291

Chapter 26. KC2 messages.................................................................................313

Chapter 27. KOCJ messages...............................................................................315

Chapter 28. OC messages.................................................................................. 325

Chapter 29. CI0410-LSCX messages.................................................................. 443

Chapter 30. OB0101-OB9269 messages............................................................. 497

Chapter 31. OBV101-OMV9991 messages.......................................................... 579

Appendix A. Abend codes.................................................................................. 641

Support information.......................................................................................... 643

1. Locations of log and trace information for z/OS components......................................................................7

3. Standard messages and abend codes........................................................................................................ 49

4. Collecting memory dumps.......................................................................................................................... 50

6. SMFEWTM return code values.................................................................................................................. 101

8. Return codes for Message KGWRM1019E............................................................................................... 281

9. Return codes for Message KGWRM1020W.............................................................................................. 282

10. Return codes for Message KGWRM1031E............................................................................................. 284

11. Return codes for Message KGWRM1032W............................................................................................ 285

17. User Actions............................................................................................................................................ 415

© Copyright IBM Corp. 2004, 2022 1

What are the symptoms of the problem?

Where does the problem occur?

When does the problem occur?

2 IBM Z OMEGAMON for CICS: Troubleshooting Guide

Under what conditions does the problem occur?

Can the problem be reproduced?

Tools for troubleshooting

Finding information about known problems

Chapter 1. Troubleshooting Guide 3

Using the pdcollect tool

4 IBM Z OMEGAMON for CICS: Troubleshooting Guide

Submitting problems to IBM Software Support

Chapter 1. Troubleshooting Guide 5

Setting up RAS1 tracing for OMEGAMON for CICS

Table 1. Locations of log and trace information for z/OS components

© Copyright IBM Corp. 2004, 2022 7

Setting trace levels by editing RKANPARU(KppENV)

KBB_RAS1=ERROR (UNIT:KGW ALL)

KBB_RAS1=ERROR (UNIT:KCP ALL) (UNIT:KCE ALL)

8 IBM Z OMEGAMON for CICS: Troubleshooting Guide