Candle Products Messages Manual, Vol 5publib.boulder.ibm.com/tividd/td/ITCPMess/GC32... · an IMS...

Candle Products Messages ManualVolume 5

(ODC–VEB and Appendixes)

GC32-9174-00

March 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245-9796

2 Candle Products Messages Manual (ODC–VEB and Appendixes)

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/REMOTE, Availability Command Center, Candle, Candle CIRCUIT, Candle Command Center, Candle Direct logo, Candle eDelivery, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleLight, CandleNet, CandleNet Command Center, CandleNet eBusiness Platform, CandleNet Portal, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, DEXAN, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness at the speed of light, eBusiness Assurance, eBusiness Institute, ELX, EPILOG, ESRA, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAMON Monitoring Agents, OMEGAVIEW, OMEGAVIEW II, PQEdit, Response Time Network, Roma, SitePulse, Solutions for Networked Applications, Solutions for Networked Businesses, TMA2000, Transplex, and Volcano.Trademarks and service marks of Candle Corporation: AF/Advanced Notification, AF/PERFORMER, Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Business Services Composer, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle eSupport, Candle Insight, Candle InterFlow, Candle Managing what matters most, Candle Service Suite, Candle Technologies, CandleNet, CandleNet 2000, CandleNet Conversion, CandleNet eBP, CandleNet eBP Access for S.W.I.F.T., CandleNet eBP Administrator, CandleNet eBP Broker Access for Mercator or MQSI, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, Candle Vision, CCC, CCP, CCR2, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, e2e, eBA*SE, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBX, End-to-End, eNotification, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, ER+, ERPNet, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, Managing what matters most, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NC4, NetGlue, NetGlue Extra, NetMirror, NetScheduler, New Times, New Team, New Readiness, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON/e, OMEGAMON Management Center, OSM, PathWAI, PC COMPANION, Performance Pac, Powered by Roma Technology, PowerQ, PQConfiguration, PQScope, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, Tracer, Unified Directory Services, WayPoint, and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. Citrix, WinFrame, and ICA are registered trademarks of Citrix Systems, Inc. Multi-Win and MetaFrame are trademarks of Citrix Systems, Inc. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective owners.

Copyright © March 2004, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

3

Chapter 1. ODC001–OIA97Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. OIB010–OM8299. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 3. OM8300–VEBXM099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Appendix A. AO/OG for MVS User Abend Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Appendix B. EB, EP, and EU Abend Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Appendix C. End-to-End Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Appendix D. End-to-End Sense Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Appendix E. CT/Engine Abend and Snap Dump Codes . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Appendix F. CT/Engine Message Route Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Appendix G. CT/Engine Sense Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Appendix H. OMEGAMON II for CICS KILL Services Transaction Abend Codes . . . . . . . . 217

Appendix I. OMEGAMON II for CICS Resource-Limiting Abend Codes . . . . . . . . . . . . . . 219

Appendix J. OMEGAMON II for SMS User Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . 221

Appendix K. OMEGAMON II for VTAM NCP Data Manager Task Return & Sense Codes .223

Appendix L. Problem Determination for OMEGAMON XE for IMS and IMSplex Products.225

Appendix M. Viewing the Windows NT Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Contents

ODC001–OIA97Y 5

ODC001–OIA97Y

ODC001 DATA COLLECTION ESTAE SUCCESSFULLY ISSUEDExplanation: RTA data collection recovery is in effect.System Action: None.User Response: None. This is an informational message only.

ODC002 DATA COLLECTION INITIALIZATION COMPLETEDExplanation: Data collection has finished all start-up requirements.System Action: None.User Response: None. This is an informational message only.

ODC003 INPUT QUEUE MANAGER ATTACHED SUCCESSFULLYExplanation: Data collection has successfully started the input queue manager task.System Action: None.User Response: None. This is an informational message only.

ODC004 DATA COLLECTION TERMINATINGExplanation: Data collection is terminating as a result of a successful request to the OMEGAMON interface or IMS termination.System Action: Data collection terminates.User Response: None. This is an informational message only.

ODC903 DATA COLLECTION FAILED TO OBTAIN THE DCWAExplanation: RTA data collection work area GETMAIN failed.System Action: RTA data collection does not function.User Response: An insufficient region size was specified in the start-up JCL. Increase the region size to at least 4096K.

ODC905 DATA COLLECTION UNABLE TO ESTABLISH ESTAE - ABENDINGExplanation: RTA data collection recovery ESTAE failed.System Action: RTA data collection does not function.User Response: Contact Candle Support Services.

1


ODC907 DATA COLLECTION TASK CANNOT BEGIN WHILE ANOTHER DATACOLLECTOR IS RUNNING OR UNTIL RTA TERMINATESExplanation: OMEGAMON allows only one data collection task per OMEGAMON interface environment.System Action: A new data collector does not start. An old data collection task, if up, remains in place.User Response: If you want to start a new data collection task, you must stop the old data collector with a MODIFY command to the OMEGAMON interface. If you tried to start data collection while an old RTA task was active, you must stop the old RTA task before you restart data collection.

ODC909 DATA COLLECTION TASK ALREADY INITIATED FOR THIS EMExplanation: OMEGAMON allows only one data collection task per OMEGAMON interface environment.System Action: A new data collector does not start. An old data collection task, if up, remains in place.User Response: If you want to start a new data collection task, you must stop the old data collector with a F EMxxxx, P DATACOL command to the OMEGAMON interface.

ODC911 DATA COLLECTION FAILED TO LOCATE OISS SSCVTExplanation: Data collection failed to find an OMEGAMON system control block.System Action: Data collection terminates.User Response: Contact Candle Support Services.

ODC912 DATA COLLECTION UNABLE TO LOAD KEILExM.Explanation: The data collector was unable to find module KEILExM.System Action: KRIDCxy terminates.User Response: Verify that OMEGAMON was installed correctly. Check to see that the KEILExyM load module was successfully unloaded from the installation tape into the OMEGAMON load library.

ODC913 DATA COLLECTION TASK ACTIVE DEQUEUE FAILUREExplanation: Data collection suffered an internal error when OMEGAMON tried to release from an internal block.System Action: Data collection terminates.User Response: Contact Candle Support Services.

ODC915 MODULE KRIQMAM NOT FOUND BY DATA COLLECTION - TERMINATINGExplanation: Data collection could not load module KRIQMAM.System Action: Data collection terminates.User Response: Unload module KRIQMAM from the distribution tape (if you haven’t already) into the appropriate load library where other RTA for IMS modules reside.

ODC001–OIA97Y 7

ODC917 INPUT QUEUE MANAGER ATTACH FAILED - TERMINATINGExplanation: Data collection failed while attaching the input queue manager task.System Action: Data collection terminates.User Response: Contact Candle Support Services.

ODC919 DATA COLLECTION ESTAE CANCELLATION UNSUCCESSFUL - TERMINATING WITH DUMPExplanation: Data collection suffered an internal error when it tried to cancel an outstanding recovery environment. Data collection produces a dump if you specify a system dump card on the OMEGAMON start-up JCL.System Action: Data collection terminates with a user dump.User Response: Contact Candle Support Services.

ODC921 DATA COLLECTION TERMINATING WITH DUMP - RECOVERY SUCCESSFULExplanation: Data collection suffered an unexpected internal error during processing which did not seriously impair data collection.System Action: Data collection terminates with a user dump if you specify a system dump card on the OMEGAMON start-up JCL.User Response: Contact Candle Support Services.

ODC923 DATA COLLECTION UNABLE TO LOAD MODULE KRIPCxy. DATA COLLECTION TERMINATING.Explanation: Data collection could not load module KRIPCxy. Data collection terminates.User Response: Unload module KRIPCxy from the distribution tape (if you haven’t already) into the appropriate load library where other RTA for IMS modules reside.

ODC925 DATA COLLECTION INITIATED FOR UNKNOWN IMS - DATA COLLECTION TERMINATINGExplanation: Data collection determined that OMEGAMON wants to monitor an IMS which terminated.System Action: Data collection terminates.User Response: If IMS terminates, you may have to restart it. If the EMPROC JCL specified an invalid IMSID, you must supply the ID of the active IMS to monitor.

ODC927 GETMAIN FAILURE CAUSES TERMINATION FOR DATA COLLECTIONExplanation: Data collection could not GETMAIN storage for critical internal control blocks in CSA.System Action: Data collection terminates. If you specified a system dump card on the start-up procedure and data collection terminates with message ODC933, a user abend dump occurs.User Response: Relieve CSA storage constraint. Contact Candle Support Services and forward any associated dumps.


ODC928 GETMAIN FAILURE CAUSES TERMINATION FOR DATA COLLECTIONExplanation: See message ODC927.System Action: See message ODC927.User Response: See message ODC927.

ODC929 FREEMAIN FAILURE OCCURRED DURING RECOVERY PROCESSING FOR DATA COLLECTIONExplanation: During internal recovery processing, data collection tried an invalid FREEMAIN.System Action: Recovery continues until data collection terminates.User Response: Contact Candle Support Services and forward any user abend dumps that data collection takes.

ODC935 FREEMAIN FAILURE CAUSES TERMINATION FOR DATA COLLECTIONExplanation: During the FREEMAIN of an internal control block, data collection encountered a system FREEMAIN error.System Action: Data collection cleans up and terminates with a user abend.User Response: Contact Candle Support Services and forward the user abend dump.

ODC937 FREEMAIN FAILURE OCCURRED DURING RECOVERY PROCESSING FOR DATA COLLECTIONExplanation: See message ODC929.System Action: See message ODC929.User Response: See message ODC929.

ODC939 DATA COLLECTION CLEANUP UNABLE TO FREE SOME AREASExplanation: Data collection could not clean up some of its internal work areas.System Action: Depending on the severity of the failure, data collection either continues running or terminates with a user abend.User Response: Contact Candle Support Services and forward any user abend dumps.

ODC941 GETMAIN/FREEMAIN FAILURE IN RECOVERY CAUSES TERMINATION WITH DUMP FOR DATA COLLECTIONExplanation: Data collection could not GETMAIN or FREEMAIN a work area when processing in its recovery routines. A user dump occurs if you specify a system dump card on the OMEGAMON JCL.System Action: Data collection terminates with a user dump after cleaning up all task resources.User Response: The most probable cause of this problem is insufficient region size. Check your OMEGAMON start-up JCL to be sure the region parameter is at least REGION=4096K. If the REGION= parameter is already set at 4096K, you may need to increase the REGION parameter further and restart data collection. If the problem persists, contact Candle Support Services and forward the user dump.

ODC001–OIA97Y 9

ODC942 GETMAIN/FREEMAIN FAILURE IN RECOVERY CAUSES TERMINATION WITH DUMP FOR DATA COLLECTIONExplanation: See message ODC941.System Action: See message ODC941.User Response: See message ODC941.







ODC951 KRIDCxyUNABLE TO ACQUIRE SUFFICIENT LOG BUFFER CELLSExplanation: See message ODC941.System Action: See message ODC941.User Response: See message ODC941.


OEC003 EPILOG/IMS COLLECTOR INITIALIZATION COMPLETEExplanation: The task that periodically gathers IMS resource information for EPILOG has been successfully started.System Action: EPILOG now collects IMS resource information.User Response: None.

OEC005 EPILOG/IMS COLLECTOR TERMINATINGExplanation: The task that periodically gathers IMS resource information forEPILOG has been stopped.System Action: EPILOG no longer collects IMS resource information.User Response: None. This message indicates a normal termination of the EPILOG resource collector.

OEC901 INVALID SCD ADDRESS FOUNDExplanation: The EPILOG resource collector task was given an SCD address which is invalid. This may be caused by IMS being in the process of termination.System Action: No IMS resource information is collected.User Response: If IMS is not in the process of terminating, call Candle Support Services.

OEC902 INVALID ESCD ADDRESS FOUNDExplanation: The EPILOG resource collector task was given an invalid ESCD address. This may be caused by IMS being in the process of termination.System Action: No IMS resource information is collected.User Response: If IMS is not in the process of terminating, call Candle Support Services.

OEC903 EPILOG/IMS COLLECTOR FAILED TO OBTAIN TASK WORK AREA - TERMINATINGExplanation: The EPILOG collector task that gathers IMS resource information was unable to GETMAIN sufficient virtual storage for a work area.System Action: The EPILOG collector task terminates.User Response: Stop the EPILOG address space and restart it with a larger region size.

OEC905 EPILOG/IMS COLLECTOR UNABLE TO ESTABLISH ESTAE ABENDINGExplanation: The resource collector task was unable to establish an ESTAE routine for error recovery.System Action: The EPILOG collector task terminates with an abend.User Response: Call Candle Customer Support.

OEC906 EPILOG/IMS COLLECTOR HAS INSUFFICIENT STORAGE FOR ERROR CELLSExplanation: The resource collector task was unable to GETMAIN sufficient virtual storage for an enhanced debugging facility work area.System Action: The collector task continues to run as normal, but some Candle debugging facilities are disabled.User Response: Increase the region size for the EPILOG address space prior to the next time it is brought up.

ODC001–OIA97Y 11

OEC908 EPILOG/IMS COLLECTOR REQUIRES RKEISNAP DD CARD - TERMINATINGExplanation: The EPILOG feature of OMEGAMON II for IMS requires that a DD JCL control statement named RKEISNAP be allocated at EPILOG startup to capture diagnostic information provided by EPILOG.System Action: The startup of the EPILOG feature is terminated.User Response: If the EPILOG feature is to be started, add the RKEISNAP DD statement to the OMEGAMON II for IMS started task JCL.

OEC909 EPILOG/IMS COLLECTOR UNABLE TO OBTAIN STACK AREA - TERMINATINGExplanation: The resource collector task was unable to acquire a work area.System Action: The EPILOG collector task terminates.User Response: Stop the EPILOG address space and restart it with a larger region size. If the problem persists, call Candle Customer Support.

OEC911 EPILOG/IMS COLLECTOR FAILED TO OBTAIN RESOURCE STATISTICS DATA AREA - TERMINATINGExplanation: The resource collector task was unable to GETMAIN sufficient virtual storage for a statistics collection area.System Action: The EPILOG collector task terminates.User Response: Stop the EPILOG address space and restart it with a larger region size.

OEC912 EPILOG/IMS COLLECTOR, RESOURCE STATISTICS WORK AREA OVERFLOWExplanation: A work area used by the EPILOG resource collector task was too small.System Action: The EPILOG collector task terminates.User Response: This is an EPILOG internal error. Call Candle Customer Support.

OEC913 EPILOG/IMS COLLECTOR FAILED TO OBTAIN EISR DATA AREA - TERMINATINGExplanation: The resource collector task was unable to GETMAIN sufficient virtual storage for a work area.System Action: The EPILOG collector task terminates.User Response: Stop the EPILOG address space and restart it with a larger region size.

OEC915 EPILOG/IMS COLLECTOR FAILED FREEING ITS IPAGESExplanation: The resource collector task was unable to FREEMAIN one of its storage areas at task termination time.System Action: The collector task terminates with a user abend.User Response: Call Candle Customer Support.


OEC917 EPILOG/IMS COLLECTOR FAILED FREEING PST TABLEExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC919 EPILOG/IMS COLLECTOR FAILED FREEING PST SAVE AREAExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC921 EPILOG/IMS COLLECTOR FREEMAIN OF PST STATISTICS AREA FAILEDExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC924 EPILOG/IMS COLLECTOR FREEMAIN OF EISR DATA AREA FAILED AT TASK TERMINATIONExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC925 EPILOG/IMS COLLECTOR FREEMAIN OF RESOURCE STATISTICS DATA AREA FAILEDExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC927 EPILOG/IMS COLLECTOR STACK RELEASE FAILURE AT TERMINATIONExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC931 EPILOG/IMS COLLECTOR MAIN ESTAE CANCEL FAILEDExplanation: The resource collector task was unable to cancel its ESTAE routine for error recovery at task termination time.System Action: The EPILOG collector task terminates with a user abend.User Response: Call Candle Customer Support.

OEC933 EPILOG/IMS COLLECTOR FREEMAIN OF MAIN TASK WORK AREA FAILEDExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

ODC001–OIA97Y 13

OEC935 EPILOG/IMS COLLECTOR ABENDING AT TERMINATIONExplanation: The resource collector task was unable to perform its normal cleanup activities at task termination time, so it terminates with an abend instead of a normal termination. Another OEC9xx message is displayed prior to this message to indicate the type of problem encountered during task termination.System Action: The EPILOG collector task terminates with an abend.User Response: Call Candle Customer Support.

OEC940 EPILOG/IMS COLLECTOR DETECTED A ZERO LENGTH OF VSP DATA AREA AT TERMINATIONExplanation: The resource collector detected a work area with a zero length at task termination time.System Action: The collector task terminates with a user abend.User Response: Call Candle Customer Support.

OEC943 EPILOG/IMS COLLECTOR FAILED FREEING VSP DATA AREAExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC945 EPILOG/IMS COLLECTOR DETECTED A ZERO LENGTH OF OSP DATA AREA AT TERMINATIONExplanation: The resource collector detected a work area with a zero length at task termination time.System Action: The collector task terminates with a user abend.User Response: Call Candle Customer Support.

OEC947 EPILOG/IMS COLLECTOR FAILED FREEING OSP DATA AREAExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC950 EPILOG/IMS COLLECTOR FAILED TO FREE DASD STATISTICS TABLEExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC951 EPILOG/IMS COLLECTOR FAILED TO FREE DEVICE ADDRESS TABLEExplanation: See message OEC915.System Action: See message OEC915.User Response: See message OEC915.

OEC981 Rxxx RESOURCE COLLECTOR DISABLEDExplanation: The EPILOG resource collector task has determined the resource collector Rxxx has been disabled using the NORESC initialization parameter.System Action: None.User Response: None.


OEF901 EPILOG/IMS FREEMAIN ERROR, PROCESSING CONTINUINGExplanation: The EPILOG collector was unable to FREEMAIN one of its work areas.System Action: The collector continues processing as normal.User Response: If this message occurs often, call Candle Customer Support.

OEF902 EPILOG/IMS FREEMAIN ERROR, PROCESSING CONTINUINGExplanation: See message OEF901.System Action: See message OEF901.User Response: See message OEF901.




OEI003 EPILOG/IMS GLOBAL RESOURCE CLEANUP COMPLETEExplanation: During recovery from an abend in EPILOG, it was determined that no retry was possible, and CSA storage was freed.System Action: Termination continues.User Response: None.

OEI005 EPILOG/IMS INITIALIZATION COMPLETEExplanation: This message is issued when the EPILOG main control task has been successfully started.System Action: EPILOG is now collecting data.User Response: None.

OEI007 EPILOG/IMS CONTROL TASK TERMINATION REQUESTEDExplanation: This message is issued when the EPILOG control task has been told to terminate. This can be the result of IMS terminating, one of EPILOG’s collectors abending, or a user request.System Action: The EPILOG control task writes out its current data and then begins to terminate all the EPILOG collectors.User Response: None.

ODC001–OIA97Y 15

OEI009 EPILOG/IMS CONTROL TASK TERMINATEDExplanation: This message is issued when the EPILOG main control task is terminated.System Action: EPILOG has stopped collecting data.User Response: None.

OEI800 EPILOG/IMS HAS DETERMINED THAT RMF IS STOPPED. EPILOG INTERVAL CHANGED TO 15 MINUTES.Explanation: EPILOG has had its collection interval set to synchronize with RMF, but RMF has stopped.System Action: EPILOG writes out the current unfinished RMF interval data, and begins cycling on a 15-minute interval instead.User Response: If this is expected, no response is necessary. If not, call Candle Customer Support.

OEI801 EPILOG/IMS HAS DETERMINED THAT DATA COLLECTION STOPPED DURING THE CURRENT EPILOG INTERVALExplanation: This is a warning message to the user that response time data for this collection interval is unreliable due to an abend in RTA.System Action: EPILOG restarts the OMRIDC and OMRIRI tasks a maximum of five times after stopping OMRIRI.User Response: None.

OEI802 EPILOG/IMS HAS DETERMINED THAT RMF IS RE-STARTED. EPILOG INTERVAL RE-SYNCHRONIZED WITH RMFExplanation: EPILOG has had its collection interval set to synchronize with RMF, but RMF stopped. It has been detected that RMF is restarted.System Action: EPILOG writes out the current 15 minute interval based on OEI800 and re-sychronizes with RMF.User Response: If this is expected, no response is necessary. If not, call Candle Customer Support Services.

OEI803 RESPONSE TIME DATA FOR THIS INTERVAL IS AT LEAST PARTLY INVALIDExplanation: See message OEI801.System Action: See message OEI801.User Response: See message OEI801.

OEI805 EPILOG/IMS HAS DETERMINED THAT SOFT QUIESCE OCCURRED DURING THE CURRENT EPILOG INTERVALExplanation: See message OEI801.System Action: See message OEI801.User Response: See message OEI801.

OEI807 EPILOG/IMS HAS DETERMINED THAT RESPONSE TIME ANALYSIS STOPPED DURING THE EPILOG INTERVALExplanation: See message OEI801.System Action: See message OEI801.User Response: See message OEI801.


OEI808 RESPONSE TIME DATA FOR THIS INTERVAL IS AT LEAST PARTLY INVALIDExplanation: See message OEI801.System Action: See message OEI801.User Response: See message OEI801.

OEI809 EPILOG/IMS RESTARTS THE RESPONSE TIME ANALYZERExplanation: See message OEI801.System Action: See message OEI801.User Response: See message OEI801.

OEI811 EPILOG/IMS HAS DETERMINED THAT DEGRADATION ANALYSIS STOPPED DURING THE EPILOG INTERVALExplanation: This is a warning message to the user that degradation data for this collection interval is unreliable due to an abend in DEXAN.System Action: EPILOG restarts the OMRIDC and OMRIRI tasks a maximum of five times after stopping OMRIRI.User Response: None.

OEI813 EPILOG/IMS WILL NOT USE THE CORRECT INTERVAL DEGRADATION DATAExplanation: See message OEI811.System Action: See message OEI811.User Response: See message OEI811.

OEI815 EPILOG/IMS WILL RESTART THE DEGRADATION ANALYZERExplanation: See message OEI811.System Action: See message OEI811.User Response: See message OEI811.

OEI817 EPILOG/IMS MUST TERMINATE KRIRIxy TO START DATA COLLECT IONExplanation: In preparing to start the data collection task, EPILOG determined that the RTA analysis task (KRIRIxy) was already active. The EPILOG control task must stop the KRIRIxy task before it can start the data collection task.System Action: The command P ID=RT is issued to stop the RTA analysis task.User Response: None.

OEI819 EPILOG/IMS WILL START DATA COLLECTIONExplanation: EPILOG must start the data collection task as part of its initialization.System Action: A START DATAC command is issued to start the Data Collection task.User Response: None.

ODC001–OIA97Y 17

OEI831 RESPONSE TIME DATA COLLECTION HAS ABENDED FIVE (05) TIMESExplanation: The OMRIDC task has suffered five abends during the time EPILOG has been active, indicating there is a severe internal error.System Action: EPILOG stops the OMRIDC and OMRIRI tasks and does not restart them. Consequently, RTA collection also stops.User Response: Call Candle Customer Support and send all dumps generated.

OEI833 EPILOG WILL NOT RESTART DATA COLLECTIONExplanation: The OMRIDC task has suffered five abends during the time EPILOG has been active, indicating there is a severe internal error. EPILOG stops its sister task OMRIRI and does not restart it.System Action: Tasks OMRIDC and OMRIRI are stopped by EPILOG and are not restarted. This also means that RTA collection stops.User Response: Call Candle Customer Support and send all dumps generated.

OEI835 EPILOG WILL STOP THE RESPONSE TIME ANALYZERExplanation: See message OEI833.System Action: See message OEI833.User Response: See message OEI833.

OEI841 RESPONSE TIME DATA ANALYZER HAS ABENDED FIVE TIMES THIS EPILOG SESSIONExplanation: The OMRIRI task has suffered five abends during the time EPILOG has been active, indicating there is a severe internal error. EPILOG does not restart the OMRIRI task again.System Action: EPILOG stops the OMRIRI task and does not restart it. Consequently, RTA collection also stops.User Response: Call Candle Customer Support and send all dumps generated.

OEI843 EPILOG WILL NOT RESTART THE DATA ANALYZERExplanation: See message OEI841.System Action: See message OEI841.User Response: See message OEI841.

OEI845 EPILOG/IMS CONTROL TASK UNABLE TO LOCATE DEGRADATION ANALYSIS WORK AREA--ABENDINGExplanation: EPILOG cannot find the main DEXAN work area, possibly due to DEXAN abending, or its task scheduling being interrupted.System Action: EPILOG terminates with an abend for diagnostics.User Response: Call Candle Customer Support and send the dump generated.

OEI847 THE DEGRADATION ANALYZER HAS ABENDED FIVE TIMES THIS EPILOG SESSIONExplanation: The KOIDXxy task has suffered five abends during the time EPILOG has been active, indicating there is a severe internal error. EPILOG does not restart the DEXAN task again.System Action: The KOIDXxy task is stopped by EPILOG and is not restarted. This also means that DEXAN collection stops.User Response: Call Candle Customer Support and send all dumps generated.


OEI849 EPILOG WILL NOT RESTART THE DEGRADATION ANALYZERExplanation: See message OEI847.System Action: See message OEI847.User Response: See message OEI847.

OEI851 EPILOG/IMS HAS DETERMINED THAT AN RIDC TASK IS ACTIVE, BUT WITH AN INCOMPATIBLE VERSION NUMBERExplanation: EPILOG is compatible with only certain releases of RTA, and has discovered that an active RTA task is incompatible with EPILOG data collection.System Action: EPILOG stops the RIDC task and does not collect response time data. All IMS and bottleneck data continue to be collected.User Response: Unload all modules from the most recent tape from which EPILOG modules originated. Then restart EPILOG and RTA. If this does not solve the problem, call Candle Customer Support.

OEI853 EPILOG/IMS HAS DETERMINED THAT AN RIRI TASK IS ACTIVE, BUT WITH AN INCOMPATIBLE VERSION NUMBERExplanation: EPILOG is compatible with only certain releases of RTA, and has discovered that an active RTA task is incompatible with EPILOG data collection.System Action: EPILOG stops the RIRI task and does not collect response time data. All IMS and bottleneck data continues to be collected.User Response: Unload all modules from the most recent tape from which EPILOG modules originated. The restart EPILOG and RTA. If this does not solve the problem, call Candle Customer Support.

OEI855 EPILOG/IMS HAS DETERMINED THAT AN OIDX TASK IS ACTIVE, BUT WITH AN INCOMPATIBLE VERSION NUMBERExplanation: EPILOG is compatible with only certain releases of DEXAN, and has discovered that an DEXAN task is incompatible with EPILOG data collection.System Action: EPILOG stops the OIDX task and does not collect bottleneck data. All IMS and response time data continues to be collected.User Response: Unload all modules from the most recent tape from which EPILOG modules originated. Then restart EPILOG and DEXAN. If this does not solve the problem, call Candle Customer Support.

OEI903 EPILOG/IMS CONTROL TASK FAILED TO OBTAIN A WORK AREA - TERMINATINGExplanation: The EPILOG main control task was unable to GETMAIN sufficient virtual storage for a work area.System Action: The EPILOG control task terminates.User Response: Stop the EPILOG address space and restart it with a larger region size.

OEI905 EPILOG/IMS CONTROL TASK UNABLE TO ESTABLISH ESTAE - ABENDINGExplanation: The EPILOG main control task was unable to establish an ESTAE routine for error recovery.System Action: The EPILOG main control task terminates with an abend.User Response: Call Candle Customer Support.

ODC001–OIA97Y 19

OEI907 EPILOG/IMS CONTROL TASK HAS DETERMINED THAT ANOTHER EPILOG IS MONITORING THE SPECIFIED IMSExplanation: During initialization the EPILOG control task has discovered that another EPILOG address space is already monitoring the specified IMS system.System Action: The EPILOG control task terminates.User Response: Determine which other EPILOG address space is monitoring the specified IMS system.

OEI909 EPILOG/IMS TASK ALREADY INITIATED FOR THIS EMExplanation: The EPILOG control task has discovered during initialization that it is already active in the specified address space.System Action: The new EPILOG task does not start.User Response: None. EPILOG is already active.

OEI910 MODULE KEIPRxy NOT FOUND BY EPILOG/IMS CONTROL TASK - TERMINATINGExplanation: The EPILOG control task has discovered during initialization that the KEIPRxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KEIPRxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI911 EPILOG/IMS TERMINATING DUE TO INITIALIZATION FAILURE PROCESSING OPTION MEMBERExplanation: The EPILOG main control task was unable to process the collector options contained in the specified member of the RKANPAR dataset.System Action: The EPILOG control task terminates.User Response: Correct the errors in the collector options member of the RKANPAR dataset.

OEI913 MODULE KEIDTAxy NOT FOUND BY EPILOG/IMS CONTROL TASK - TERMINATINGExplanation: The EPILOG control task has discovered during initialization that the KEIDTAxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KEIDTAxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI915 EPILOG/IMS DEGRADATION TIMER SUBTASK ATTACH FAILED - TERMINATINGExplanation: The EPILOG control task was unable to successfully ATTACH the subtask which causes DEXAN information to be captured on a periodic basis for EPILOG.System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.


OEI917 MODULE KEIICxy NOT FOUND BY EPILOG/IMS CONTROL TASK - TERMINATINGExplanation: The EPILOG control task has discovered during initialization that the KEIICxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KEIICxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI919 EPILOG/IMS RESOURCE COLLECTION ATTACH FAILED - TERMINATINGExplanation: The EPILOG control task was unable to successfully ATTACH the subtask which gathers IMS resource information.System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.

OEI920 EPILOG/IMS X-MEMORY WORK AREA GETMAIN FAILED - TERMINATINGExplanation: The EPILOG collector task that gathers IMS resource information was unable to GETMAIN sufficient virtual storage for a work area in CSA.System Action: The EPILOG collector task terminates.User Response: Call Candle Customer Support.

OEI921 MODULE KEICWxy NOT FOUND BY EPILOG/IMS - EPILOG TERMINATINGExplanation: The EPILOG control task has discovered during initialization that the KEICWxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KEICWxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI923 EPILOG/IMS COMMON WRITE TASK ATTACH FAILED - TERMINATINGExplanation: The EPILOG control task was unable to successfully ATTACH the subtask that writes the EPILOG data records to the SMF and Epilog Datastore (EDS) datasets.System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.

OEI925 EPILOG/IMS CONTROL TASK UNABLE TO LOCATE DEGRADATION ANALYSIS WORK AREA - TERMINATINGExplanation: The EPILOG control task was unable to locate an internal control block used by the bottleneck analysis subtask (DEXAN).System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.

ODC001–OIA97Y 21

OEI926 EPILOG/IMS RESOURCE COLLECTOR DETACH FORCED TO LOOPExplanation: EPILOG detected a loop in the resource collector.System Action: EPILOG remains in a loop.User Response: Restart EPILOG. If the problem persists, call Candle Customer Support.

OEI927 EPILOG/IMS UNABLE TO LOAD MODULE KEISRxy - TERMINATINGExplanation: The EPILOG control task was unable to successfully LOAD the KEISRxy module.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KEISRxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI928 EPILOG/IMS UNABLE TO LOAD MODULE KEIEMxy - TERMINATINGExplanation: The EPILOG control task was unable to successfully LOAD the KEIEMxy module.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KEIEMxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI929 EPILOG/IMS RESOURCE COLLECTOR HAS ENDEDExplanation: The task that collects IMS resource information has ended.System Action: EPILOG is in the process of terminating.User Response: None.

OEI930 EPILOG/IMS DEGRADATION TIMER SUBTASK HAS ABENDEDExplanation: The task that causes bottleneck information to be collected has abended. System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.

OEI931 EPILOG/IMS COMMON WRITE TASK HAS ABENDEDExplanation: The task that writes the EPILOG data records to the SMF and EPILOG data store (EDS) datasets has abended.System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.

OEI932 EPILOG/IMS UNABLE TO LOCATE DATA COLLECTION CONTROL BLOCKS - EXIT NOT INSTALLEDExplanation: The data collector task (OMRIDC) probably terminated, and EPILOG is unable to connect with it to process Fast Path log records.System Action: EPILOG does not collect Fast Path dependent region statistics for the current interval. EPILOG attempts to restart the data collector at the expiration of the current interval (to a maximum of five times), and then collect Fast Path information.User Response: Call Candle Customer Support and send all documentation (dump, syslog, etc.).


OEI933 EPILOG/IMS UNABLE TO LOCATE LOG EXIT MODULE - EXIT NOT INSTALLEDExplanation: EPILOG was unable to locate module KEILExyM.System Action: EPILOG does not collect Fast Path dependent region statistics.User Response: Use the unload JCL in the first dataset of the Candle installation tape to unload ALL load modules.

OEI933 EPILOG/IMS MAJOR ERROR USING GQSCAN, ABENDINGExplanation: The EPILOG control task encountered an error in the GQSCAN MVS service. System Action: The EPILOG control task terminates.User Response: Call Candle Customer Support.

OEI934 EPILOG/IMS DETECTED INVALID DATA COLLECTION CONTROL BLOCKS - EXIT NOT INSTALLEDExplanation: EPILOG detected invalid internal control blocks.System Action: EPILOG abends with a user 41 abend.User Response: Call Candle Customer Support and send all documentation (dump, syslog, etc.).

OEI935 EPILOG/IMS CONTROL TASK ESTAE CANCELLATION UNSUCCESSFUL - TERMINATING WITH A DUMPExplanation: The EPILOG control task was unable to cancel its ESTAE routine (error recovery) at task termination time.Explanation: The EPILOG control task terminates with an abend.User Response: Call Candle Customer Support.

OEI936 EPILOG/IMS UNABLE TO LOCATE DATA COLLECTORExplanation: The data collector task (OMRIDC) probably terminated, and EPILOG is unable to connect with it in order to process Fast Path log records. System Action: EPILOG does not collect Fast Path statistics for the current interval. It attempts to restart the data collector at the expiration of the current interval (to a maximum of five times), and then collects Fast Path information.User Response: Call Candle Customer Support and send all documentation (dump, syslog, etc.).

OEI937 EPILOG/IMS DETECTED ABEND IN MODULE KEIPRxy - NEW OPTIO NS NOT IN EFFECTExplanation: An abend occurred in the module that examines the collector option values contained in the RKANPAR dataset.System Action: If the abend occurs when the collector options are being examined at initial start-up, the EPILOG control task terminates with an abend. If the abend occurs after start-up, when a new options member is being examined for a new EPILOG interval, the new options request is ignored and the EPILOG collector continues to use the current collection options. User Response: Call Candle Customer Support.

ODC001–OIA97Y 23

OEI938 EPILOG/IMS HAS DETECTED EPILOG LOG RECORD MODULE ABEND - TERMINATINGExplanation: While processing a Fast Path log record in module KEILExyM, the data collector abended.System Action: EPILOG terminates. After the data collector (RIDC) task terminates, EPILOG produces a dump of the problem.User Response: Call Candle Customer Support and send all documentation (dump, syslog, etc.).

OEI939 EPILOG/IMS HAS DETERMINED THAT RMF IS NOT ACTIVE AND WILL USE 15 MINUTES AS INTERVALExplanation: The EPILOG control task has determined that RMF is not active, so no synchronization can be done on RMF interval. Instead, EPILOG maintains its own 15 minute interval.System Action: EPILOG writes out its data every 15 minutes.User Response: None.

OEI940 EPILOG/IMS FOUND MODULE KDIDXxy WITH INCOMPATIBLE VERSION NUMBERExplanation: The KDIDXxy load module contained in the EPILOG load library is not compatible with the version of EPILOG being started.System Action: The EPILOG collector task terminates.User Response: Verify that the product installation was done properly. The latest version of the KDIDXxy load module may not have been unloaded from the installation tape.

OEI941 YOU MUST UNLOAD THE KDIDXxy MODULE FROM THE SAME TAPE A S YOU DID KEIEIxy.Explanation: This is a companion message to message OEI940.System Action: The EPILOG collector task terminates.User Response: See message OEI940.

OEI942 EPILOG/IMS UNABLE TO LOCATE MODULE KDIDXxy. TERMINATING.Explanation: During initialization, the EPILOG control task has discovered that the KDIDXxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KDIDXxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI943 EPILOG/IMS FOUND MODULE KRIDCxy WITH AN INCOMPATIBLE VERSION NUMBERExplanation: The KRIDCxy load module contained in the EPILOG load library is not compatible with the version of EPILOG being started.System Action: The EPILOG collector task terminates.User Response: Verify that the product installation was done properly. The latest version of the KRIDCxy load module may not have been unloaded from the installation tape.


OEI944 YOU MUST UNLOAD THE KRIDCxy MODULE FROM THE SAME TAPE AS YOU DID KEIEIxy.Explanation: See message OEI943.System Action: See message OEI943.User Response: See message OEI943.

OEI945 EPILOG/IMS UNABLE TO LOCATE MODULE KRIDCxy, TERMINATING.Explanation: During initialization, the EPILOG control task has discovered that the KRIDCxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KRIDCxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI946 EPILOG/IMS FOUND MODULE OMRIRI WITH AN INCOMPATIBLE VERSION NUMBERExplanation: The OMRIRI load module contained in the EPILOG load library is not compatible with the version of EPILOG being started.System Action: The EPILOG collector task terminates.User Response: Verify that the product installation was done properly. The latest version of the OMRIRI load module may not have been unloaded from the installation tape.

OEI947 YOU MUST UNLOAD THE KRIRIxy MODULE FROM THE SAME TAPE AS YOU DID KEIEIxy.Explanation: See message OEI946.System Action: See message OEI946.User Response: See message OEI946.

OEI948 EPILOG/IMS UNABLE TO LOCATE MODULE KRIRIxy, TERMINATING.Explanation: During initialization, the EPILOG control task has discovered that the KRIRIxy load module is not present in the JOBLIB or STEPLIB datasets allocated to the EPILOG address space or in the link pack area.System Action: The EPILOG control task terminates.User Response: Verify that the EPILOG installation was done correctly. Check to see that the KRIRIxy load module was successfully unloaded from the installation tape into the EPILOG load library.

OEI951 EPILOG/IMS FOUND DEXAN TASK ACTIVE IN THE SAME ADDRESS SPACE AS EPILOG/IMSExplanation: During initialization, the EPILOG control task has discovered that the DEXAN collector is active, but is using an incompatible version of the KDIDXxy load module.System Action: The EPILOG control task terminates.User Response: Stop the active DEXAN collector with a STOP ID=DX command and then restart EPILOG after moving the new version of the KDIDXxy module into the EPILOG load library.

ODC001–OIA97Y 25

OEI953 EPILOG/IMS FOUND A RIDC TASK ACTIVE IN THE SAME ADDRESS SPACE AS EPILOG/IMSExplanation: The EPILOG control task has discovered during initialization that the data collector is active, but is using an incompatible version of the KRIDCxy load module.System Action: The EPILOG control task terminates.User Response: Stop the active data collector with a STOP ID=DC command and then restart EPILOG after moving the new version of the KRIDCxy module into the EPILOG load library.

OEI955 EPILOG/IMS FOUND A RIRI TASK ACTIVE IN THE SAME ADDRESS SPACE AS EPILOG/IMSExplanation: During initialization, the EPILOG control task has discovered that the RTA collector is active, but is using an incompatible version of the KRIRIxy load module.System Action: The EPILOG control task terminates.User Response: Stop the active RTA collector with a STOP ID=RT command and then restart EPILOG after moving the new version of the KRIRIxy module into the EPILOG load library.

OEI956 SVC DUMP REQUEST FAILED. RETURN CODE: nn, REASON CODE: nnExplanation: The SDUMP macro failed when EPILOG issued an SVC dump request. EPILOG issued messages prior to this message indicating the reason for the dump request.System Action: None.User Response: See your IBM MVS Authorized Assembler Reference for a complete description of SDUMP return codes and reason codes. See message OEI957 for the header ID associated with this dump request.

OEI957 HDR=ccccccccccccccccccccccccccccExplanation: EPILOG issues this message in conjunction with message OEI956. This message gives you the header ID associated with the failed SVC dump request.System Action: None.User Response: None.

OEI96x EPILOG/IMS CONTROL TASK ESTAI FAILEDExplanation: During normal or abnormal EPILOG recovery processing EPILOG attempted to get an ESTAI work area and the GETMAIN failed due to insufficient storage. System Action: EPILOG ESTAI processing is aborted, but EPILOG continues processing.User Response: Increase region’s size specified on the started task PROC, stop and then restart the interface and EPILOG. If the problem persists, call Candle Customer Support.


OEI965 ESTAIE ENTERED WITH INVALID RECOVERY WORK AREAExplanation: During normal or abnormal EPILOG recovery processing EPILOG determined that the recovery area passed was invalid, possibly due to a module overwriting its contents.System Action: EPILOG abends immediately.User Response: Call Candle Customer Support.

OEI970 EPILOG/IMS ETE INITIALIZATION COMPLETEExplanation: The system establishes the ETE environment and adds the nodes you listed in the start-up parameters to ETE for collection.System Action: NoneUser Response: None

OEI971 EPILOG/IMS ETE INSTALL FAILED, ETE IS NOT ACTIVEExplanation: This message means one of the following:

® The ETE INSTALL process encountered an error.

® After you installed ETE, you issued a MODIFY command to use the new start-up parameters and:

– The ETE REMOVE process encountered an error, or

– ETE initialization timed out attempting to obtain the ETE bucket lock.

System Action: None.User Response: Make sure the ETE address space is active.

OEI972 EPILOG/IMS ETE GROUP STATISTICS TRUNCATED.Explanation: The number of nodes included in the current group has exceeded the EDS record size.System Action: The system writes the record with the current statistics.User Response: Limit the number of nodes (or generic nodes) per group specification.

OEI980 EPILOG/IMS UNABLE TO ALLOCATE STORAGE FOR RESOURCE COLLECTOR DISABLE FUNCTIONExplanation: The EPILOG main control task was unable to GETMAIN sufficient virtual storage for a work area.System Action: The EPILOG will continue to initialize, but Resource Collectors will not be disabled.User Response: Stop the EPILOG address space and restart it with a larger region size.

OES901 PST COUNT EXCEEDS 255Explanation: The EPILOGEPILOG task that gathers information about IMS resources found an invalid PST count in an IMS control block. This should only occur if IMS was in the process of terminating.System Action: The EPILOG resource collector terminates with an abend.User Response: If IMS is not in the process of terminating, call Candle Customer Support.

ODC001–OIA97Y 27

OES903 ESTAE ENTERED WITH INVALID RECOVERY WORK AREAExplanation: The error recovery routine for the task that collects IMS resource information was entered with an invalid recovery work area address.System Action: The EPILOG resource collector terminates with an abend.User Response: Call Candle Customer Support.

OES905 EPILOG/IMS UNABLE TO ACQUIRE STORAGE FOR DEBUGGING ANALYSISExplanation: The error recovery retry routine for the task that collects IMS resource information was entered and it attempted to acquire a save area for error information, but was unable to GETMAIN sufficient virtual storage. System Action: The retry routine attempts to recover anyway.User Response: Allocate a larger region size for the EPILOG address space.

OES908 EPILOG/IMS COLLECTOR RECOVERY DETERMINED THAT IMS IS TERMINATINGExplanation: During recovery from an abend in EPILOG, it was determined that IMS was terminating and that no retry is possible.System Action: The EPILOG collector terminates.User Response: Restart EPILOG when IMS is active.

OGN001R ENTER RELEASE OF VM TO BE SUPPORTEDExplanation: The release of VM is required.System Action: The system displays a list of supported systems and waits for input.User Response: Reply with the level of VM that you want to run OMEGAMON on. This is necessary to ensure that the version of OMEGAMON is synchronized with the level of VM, due to changes in control block structure from release to release. For example:

OGN004E RELEASE ccc IS NOT SUPPORTED BY THIS VERSION OF OMEGAMON/VMExplanation: The specified release of VM was not recognized as being supported by this version of OMEGAMON.System Action: The OMGEND EXEC terminates.User Response: Rerun OMGEND using only a supported version of VM.

Enter: For Release:

E230 VM/ESA release 2.3.0




OGN010R DO YOU WISH TO BUILD THE OPTIONAL SHARED SEGMENT? (Y/N)Explanation: OMEGAMON asks if you want to create or rebuild the shared segment. System Action: The system waits for a response.User Response: Enter Y to build the shared segment or N to bypass. See the OMEGAMON and EPILOG for VM Installation and Customization Guide for information regarding the use of shared segments.

OGN016R ENTER NAME OF SYSTEM TO BE SAVED (OMEGAMON)Explanation: The system allows you to enter an optional name for the shared segment. OMEGAMON is the default.System Action: The system waits for a response.User Response: Enter the name by which the system is to be saved. For SP and HPO systems, this name must correspond to the SYSNAME entry in the NAMESYS macro of DMKSNT.

OGN022R SEGMENT: HAS NOT BEEN DEFINED YETTHE DEFAULT ORIGIN FOR CREATING THIS SEGMENT IS: DO YOU WISH TO CHANGE THE SEGMENT ADDRESS FOR ?(Y/N)Explanation: The segment identified by does not exist. The address is where the new segment will be loaded. The system gives you the opportunity to change the address of where the segment will be loaded.System Action: The system waits for a response.User Response: Enter a Y if you wish to change the default address for the segment.

OGN024R ENTER NEW SEGMENT ORIGIN NUMBER (1-nnn):Explanation: The system is requesting that you enter the starting hexadecimal address for the segment. A value of 1 represents virtual address X’00100000’, a value of 7FE represents the address X’7FE00000’.System Action: The system waits for a response.User Response: Enter the starting segment number.

OGN030I TERMINATING OMGEND AS REQUESTEDExplanation: A response other than Y was given, which causes the execution of the OMGEND EXEC to terminate.System Action: The installation EXEC terminates. The OMEGAMON module is NOT created.User Response: None. This is an informational message only.

OGN032E ERROR ON INPUT (cccccccc)THE ADDRESS MUST BE A VALID HEXADECIMAL NUMBER(ALL CHARACTERS IN THE RANGE OF 0-9, AND A-F)Explanation: The string entered contains invalid characters, the field must contain only numeric values or contain the letters A through F.System Action: The system requests that you re-enter the address.User Response: Correct the value and enter it again.

ODC001–OIA97Y 29

OGN034E ERROR ON INPUT (cccccccc)THE VALID RANGE OF VALUES ARE 1 THROUGH nnnA VALUE OF 1 CORRESPONDS TO X’00100000’ (1MB)A VALUE OF nnn CORRESPONDS TO THE LASTMEGABYTE OF YOUR CURRENT VIRTUAL MACHINE SIZEExplanation: The string entered contains a value outside the allowed range. The valid range is specified in the error text.System Action: The system requests that you re-enter the address.User Response: Correct the value and enter it again.

OGN040R BUILD OMEGAMON/VM FOR cccccccc RELEASE AND GENERATEOPTIONAL SAVED SYSTEM cccccc AT ORIGINxxxxxx? (Y/N)Explanation: The system is asking for verification to continue processing. Once verification is given, OMEGAMON will be generated and optionally saved in a DCSS.System Action: The system waits for your response.User Response: Enter Y to continue or N to terminate the OMGEND procedure.

OGN042I cccccccc ALREADY DEFINED AND WILL NOT BE RE-DEFINED(TO RE-DEFINE cccccccc, PURGE THE EXISTINGcccccccc NSS ENTRY AND RE-RUN OMGEND)Explanation: The system found the OMEGAMON data segment in the NSS queue and is informing you that this segment will not be generated and saved.System Action: None.User Response: None. This is an informational message only.

OGN044R DO YOU WISH TO BUILD THE cccccccc DATA SEGMENT? (Y/N)Explanation: The system is asking if the data segment used for bottleneck analysis, cache, LPAR, and response commands should be built.System Action: The system waits for your response.User Response: Enter Y to build the data segment.

OGN046I A DISCONTIGUOUS SAVED SEGMENT OF CVOVDATA WAS FOUND IN THE CURRENT SET OF NAMED SYSTEMS. OMEGAMON NO LONGER USES THIS SEGMENT NAME. YOU MAY PURGE THIS NSS IF IT IS LEFT OVER FROM A PREVIOUS VERSION OF OMEGAMON.Explanation: The system detected that the name of the old data segment used by previous releases of OMEGAMON still exists. The message is intended to notify you that the segment may be deleted. Before deleting, make sure that no other application such as OfficeVision™ is using this segment.System Action: None.User Response: No required action.


OGN048I PURGING OLD cccccccc, SPOOLID nnnnExplanation: This is a notification that the old OMEGAMON code segment is being purged prior to generating a new one.System Action: None.User Response: This is an informational message only.

OGN050I GENERATION COMPLETEExplanation: This is the normal completion message.System Action: The OMGEND EXEC terminates.User Response: None.

OGN052W * * * WARNING * * *cccccccc will not be defined. Certain performance related OMEGAMON commands will not function. Please refer to the Installation and Customization Guide for more information.Explanation: You have answered NO to the command prompt:"OGN044R Do you wish to build the cccccccc data segment (Y/N)?"System Action: None.User Response: Rerun the OMGEND exec if you want use the OMEGAMON commands.

OGN104E DCSS LOAD FAILED FOR cccccccc RC=nnExplanation: An error occurred during the linking of the OMEGAMON module. Possible causes are missing TEXT files or insufficient main memory.System Action: The OMGEND EXEC terminates.User Response: Contact Candle Customer Support Services.

OGN105E SAVESYS FAILED FOR cccccccc RC=nnExplanation: An error occurred during the SAVESYS command.System Action: The OMGEND EXEC terminates.User Response: See the IBM VM/SP System Programmer’s Guide for more information on SAVESYS.

OGN106E LOAD FAILED FOR MODULE cccccccc RC=nnExplanation: An error occurred during the link-edit for the named OMEGAMON module.System Action: The OMGEND EXEC terminates.User Response: Contact Candle Customer Support Services.

OGN107E GLOBAL TXTLIB cccccccc FAILED RC=nnExplanation: An error occurred while trying to reference the named TXTLIB.System Action: The OMGEND EXEC terminates.User Response: Contact Candle Customer Support Services.

OGN108E GENMOD FAILED FOR MODULE cccccccc RC= nnExplanation: An error occurred during the execution of the GENMOD command for the named module.System Action: The OMGEND EXEC terminates.User Response: Check the console messages or load map for errors.

ODC001–OIA97Y 31

OGN109E PURGE FAILED FOR cccccccc RC= nnExplanation: The EXEC was unable to purge the NSS for the named segment. Possibly the privilege class is insufficient.System Action: The OMGEND EXEC terminates.User Response: Verify the authority of your virtual machine.

OGN110E DEFSEG FAILED FOR cccccccc RC= nnExplanation: The EXEC was unable to define the segment. Possibly the privilege class is insufficient.System Action: The OMGEND EXEC terminates.User Response: Verify the authority of your virtual machine.

OGN111E UNABLE TO LOCATE ANY OMEGAMON TXTLIBSPLEASE RUN THE OVINSTAL EXEC TO INSTALL OMEGAMONExplanation: OMGEND was unable to find any of the required TXTLIB files for generating the system.System Action: The OMGEND EXEC terminates.User Response: Verify that OVINSTAL was run and that the OMEGAMON 193 disk is accessed.

OGN112E UNABLE TO LOCATE cccccccc TXTLIBPLEASE RUN THE OVINSTAL EXEC TO INSTALL OMEGAMONExplanation: OMGEND was unable to find the named TXTLIB files for generating the system.System Action: The OMGEND EXEC terminates.User Response: Verify that OVINSTAL was run and that the OMEGAMON 193 disk is accessed.

OGN113E QUERY NSS COMMAND FAILED RC=nnExplanation: Unable to find the list of named segments. Most likely, the privileged class is insufficient to issue the Q NSS command.System Action: The OMGEND EXEC terminates.User Response: Verify the authority of your virtual machine.

OGN114E SEGMENT cccccccc DOES NOT EXIST. VERIFY DMKSNTExplanation: The EXEC was unable to locate the named segment in the system.System Action: The OMGEND EXEC terminates.User Response: Verify that the named segment was properly built in DMKSNT and that the VM system was regenned with it.

OGN115E SEGMENT ADDRESS EXCEEDS VIRTUAL STORAGE SIZEExplanation: The defined segment in DMKSNT has an assigned address range which will not fit into your current virtual memory.System Action: The OMGEND EXEC terminates.User Response: Increase the size of virtual machine and run OMGEND again.


OGN116E DEFSEG FOR cccccccc FAILED RC=nnnExplanation: The system attempted to define the specified segment and got a non-zero return code. This could be due to insufficient authority to issue the DEFSEG command.System Action: The system continues with the generation of OMEGAMON. The collector data DCSS will not be defined and may have to be created manually.User Response: Determine the actual error from the DEFSEG command by looking up the return code displayed in the message.

OGN117E SAVESYS FOR cccccccc FAILED RC=nnnExplanation: The system attempted to save the specified segment and got a non-zero return code. This could be due to insufficient authority to issue the SAVESYS command.System Action: The system continues with the generation of OMEGAMON. The collector data DCSS will not be saved and may have to be created manually.User Response: Determine the actual error from the SAVESYS command by looking up the return code displayed in the message.

OGN118E Unable to locate OMGEND EXEC, Candle DIAGNOSE not installed. RC=28Explanation: OMGEND was unable to locate the disk upon which it is installed, so that it can correctlly install the code for the Candle DIAGNOSE.System Action: The OMGEND EXEC terminates.User Response: Ensure that OMGEND is on an accessed disk and has not been renamed.

OI050 COMMAND FAILED TO ACQUIRE STORAGE--COMMAND TERMINATEDExplanation: There was insufficient CSA storage to acquire a work area to dump the SVTD. This error occurred when the SVTD minor of the DUMP major command was issued.System Action: The command terminates.User Response: Relieve CSA storage constraint. If this fails to solve the problem, contact Candle Support Services.

OI054 UPPER VALUE MUST BE GREATER THAN LOWER VALUEExplanation: You entered an upper threshold value which is smaller than the lower threshold value.System Action: OMEGAMON does not modify the threshold values.User Response: Enter an upper threshold value which is greater than the lower threshold value.

OI055 MAX SCALE VALUE MUST BE GREATER THAN THRESHOLD VALUESExplanation: You entered an upper or lower threshold value which is greater than the maximum scale value entered.System Action: OMEGAMON does not modify the threshold values.User Response: Enter a maximum scale value which is greater than the upper threshold.

ODC001–OIA97Y 33

OI056 LOWER THRESHOLD VALUE IS INVALIDExplanation: The lower threshold value you entered is not a valid number.System Action: OMEGAMON does not modify the threshold values.User Response: Verify that the value you entered for the lower threshold is a valid number.

OI057 UPPER THRESHOLD VALUE IS INVALIDExplanation: The upper threshold value you entered is not a valid number.System Action: OMEGAMON does not modify the threshold values.User Response: Verify that the value you entered for the upper threshold is a valid number.

OI058 MAX SCALE VALUE IS INVALIDExplanation: The maximum Y-axis scale value you entered is not a valid number.System Action: OMEGAMON does not modify the threshold values.User Response: Verify that the value you entered for the maximum scale value is a valid number.

OI059 PLOT RESOURCE NAME NOT DEFINEDExplanation: The PLOT resource name you entered is not defined within OMEGAMON.System Action: None.User Response: Verify the spelling of the resource name. You can use the.MIN minor command of the PSET major command to list the valid resource names. If the name appears to be valid, log the current screen and contact Candle Support Services.

OI061 BROKEN CONTROL BLOCK CHAIN TERMINATED COMMAND - TRY AGAINExplanation: While OMEGAMON II was scanning the IRLM or Program Isolation control blocks, it encountered an error.System Action: The command terminates with this message.User Response: Retry the command. This is usually the result of IMS altering the control blocks while OMEGAMON II is scanning them. The retry of the command should occur sufficiently later than the previous try that IMS will have had a chance to complete the updates to these control blocks.

OI062 NO DATA AVAILABLEExplanation: No data was found for display.System Action: The command terminates.User Response: None.

OI063 INPUT NOT NUMERICExplanation: The command expected numeric data but found non-numeric data instead. System Action: None.User Response: Enter the numeric data.


OI064 Enter: “ON”, “OFF”, or “?”Explanation: The command expected a value in the argument field (columns 6 & 7) telling it to turn a facility or option on or off, or to display the current status.System Action: None.User Response: Enter one of the following values in the command argument field:

OI065 KOIGBL MODULE IS INCORRECT VERSION LEVEL - REASSEMBLEExplanation: The version level of the KOIGBL module you specified for this session does not match the version level of the KOIOIxy load module. None of the commands function which require use of the KOIGBL and the transaction group facility.User Response: Use the GLBL command to determine the suffix value of the KOIGBL module in use. Reassemble this module, using the TKANMAC dataset that corresponds to the version level of OMEGAMON running (the level number displays on the INFO line). Be sure that the version level specified on the $OMVER macro in the KOIGBL module is correct before you assemble the module.

OI067 SPECIFIED GROUP CONTAINS NO ENTRIESExplanation: OMEGAMON tried to display information about items in a transaction group which is undefined (contains no members). System Action: No information displays for the specified transaction group.User Response: Use the SETG99 command to determine which transaction groups are defined.

OI068 NO NODE ENTRIES DEFINEDExplanation: RTA found no node related groups.System Action: The command terminates.User Response: Create a node group by using the SETG command or by re-assembling the KOIGBLxx module.

OI069 ERROR - SPECIFIED GROUP IS NOT NODE RELATEDExplanation: An action against a node group was requested, but the given group was not a node group.System Action: The command terminates.User Response: Reissue the command using a node group.

ON Turns the facility or option on.

OF Turns the facility or option off.

? Displays the current status.

ODC001–OIA97Y 35

OI070 GROUP ID INVALID; REENTERExplanation: You entered an incorrect transaction group number in the command argument field.System Action: None.User Response: Correct the transaction group number. Use the MAXG command to determine the maximum group number allowed.

OI071 INVALID OPTION SPECIFIED; REENTERExplanation: You entered an incorrect option for this command.System Action: None.User Response: Check the spelling of each keyword you entered. Use the HELP facility (/ in column 1) for a description of all valid keywords and options for the command.

OI072 TERM=, TRAN=, PSB=, or CLASS= REQUIRED; REENTERExplanation: The entry-type keyword was missing for the SETG command.System Action: None.User Response: Enter the appropriate entry-type keyword.

OI073 UNABLE TO BUILD TRANSACTION GROUP TABLE, RC=000000nnExplanation: A command which requires use of the transaction group tables was unable to build the tables using the data supplied in the KOIGBL module. The reason code indicates the nature of the error:

System Action: None of the commands which require use of the transaction group tables will run.User Response: Contact Candle Support Services if unable to correct the error.

OI074 ERROR IN TRANSACTION GROUP TABLEExplanation: OMEGAMON found an internal error while attempting to change or display the transaction group definitions.System Action: All commands which require use of the transaction group tables may produce incorrect results.User Response: Contact Candle Support Services.

08 insufficient virtual storage for tables

0C unable to locate the KOIGBL module

10 error attempting to load the KOIGBL module

14 generic name table full

18 error loading transaction group routine

1C the KOIGBL module is wrong version level


OI075 NO ROOM IN TRANSACTION GROUP TABLEExplanation: The user tried to add an additional entry to the transaction group table but it is full.System Action: None.User Response: Increase the value of the MAXIDS parameter (or MAXTERM parameter if you were adding a terminal name) on the $OIGROUP INITIAL macro in the KOIGBL module and reassemble it. Use the GLBL command to load the new KOIGBL module dynamically.

OI076 INVALID KEYWORD SPECIFIEDExplanation: The user entered an incorrect keyword for this command.System Action: None.User Response: Check the spelling of each keyword you entered. Use the HELP facility (/ in column 1) for a description of all valid keywords and options for the command.

OI082 ERROR IN GENERIC NAME TABLEExplanation: OMEGAMON found an internal error in the table the generic name option of the transaction group facility uses.System Action: None.User Response: Contact Candle Support Services.

OI083 ERROR - SPECIFIED GROUP IS TERMINAL RELATEDExplanation: The user tried to add a transaction related entry (TRAN=, PSB=, or CLASS= parameter) to a workload group which was previously defined for terminal names.System Action: OMEGAMON ignores the update request.User Response: To create a different workload group number or override the current group’s contents, place a C in column 1. To delete the previous group definition, place an X in column 1.

OI084 ERROR - SPECIFIED GROUP IS TRANSACTION RELATEDExplanation: The user tried to add a terminal name entry (TERM= parameter) to a transaction group which was previously defined for transaction related entries (TRAN=, PSB=, or CLASS= parameter).System Action: OMEGAMON ignores the update request.User Response: To create a different workload group number or override the current group’s contents, place a C in column 1. To delete the previous group definition, place an X in column 1.

OI085 ERROR IN GROUP ID TABLEExplanation: OMEGAMON found an internal error in a table the transaction group facility uses.System Action: None.User Response: Contact Candle Support Services.

ODC001–OIA97Y 37

OI086 STORAGE SHORTAGE, UNABLE TO ENLARGE GROUP TABLEExplanation: The user tried to increase the number of transaction groups the MAXG command allows. However, there was not enough virtual storage available to create a larger group table.System Action: OMEGAMON does not increase the maximum group number.User Response: Increase virtual storage available, if possible, via the REGION parameter, or try again later when storage usage decreases.

OI087 NAME ENTERED EXCEEDS 8 CHARACTER MAXIMUM LENGTHExplanation: The user entered a group or group item name which exceeds the 8-character maximum.System Action: None.User Response: Correct the name value.

OI088 ARGUMENT MUST BE “X” OR “T” Explanation: The user entered an incorrect character in the fifth position.System Action: The AUTO command does not process.User Response: Correct the fifth character. You can follow the AUTO command only with an X or T (AUTOX/AUTOT). X establishes automatic transaction groups. T establishes automatic terminal groups.

OI089 ACTION NOT RECOGNIZEDExplanation: The AUTO command did not recognize the specified action. The actions you can specify are: SET, RESET, CLEAR, LIST, OFF, ‘’, ?, or TEST.System Action: The AUTO command does not process.User Response: Specify the action keyword for the AUTO command again.

OI090 RESPECIFY NUMBER OF GROUPSExplanation: The AUTO SET command did not contain the number of groups to define. The SET variation of the AUTO command requires a numeric parameter specifying the number of groups to define.System Action: The AUTO command does not process.User Response: Specify the number of automatic groups to define within the range of 1 to 30.

OI091 GROUP IS IN USE. MUST CLEAR FIRST.Explanation: The group numbers you specified in the AUTO SET command are currently assigned.System Action: The AUTO command does not completely process.User Response: Use the AUTO SET command FORCE option to forcefully reassign groups.

OI092 AUTOMATIC GROUPS NEED TO BE ESTABLISHED. USE THE SET COMMAND FIRST.Explanation: The RESET, CLEAR, LIST, and OFF options apply to groups the AUTO SET command establishes.System Action: The AUTO command does not process.User Response: Use the AUTO SET command to establish automatic groups.


OI093 NUMBER ENTERED EXCEEDS MAXIMUM GROUPS DEFINEDExplanation: There is a limit on the number of monitoring groups which you can define. The MAXG command sets the limit.System Action: The AUTO command does not process.User Response: Use the MAXG command to increase the number of groups, within the range 1 to 30.

OI094 PLEASE ENTER RESOURCE NAME OF PLOTS TO DISPLAYExplanation: You did not enter a resource name. The PLOT command displays from 1 to 3 graphical displays based on resource name.System Action: PLOT processing does not occur.User Response: Specify the names of each plot you desire as an argument of the PLOT command. Refer to the PLOT screen space for a list of all values which this command plots.

OI095 PLOT RESOURCE NAME IS LONGER THAN 4 CHARACTERS. PLEASE REENTER.Explanation: The resource name you entered was longer than 4 characters. The PLOT command presents graphical displays, based on 4-character resource names.System Action: PLOT processing does not occur for the specified name.User Response: Change the resource name to one of the 4-character plot names the PLOT command supports. Refer to the PLOT screen space for a list of all resources which this command plots.

OI096 GROUP NAME NOT DEFINEDExplanation: You entered a group name which is not defined.System Action: None.User Response: Verify the spelling of the group name you entered. Use the LSETG99 command to list all group names which are defined.

OI097 DEXAN/IMS DOES NOT SUPPORT GROUP OTHERExplanation: DEXAN for IMS does not support the OTHER group.System Action: None.User Response: None. This is an informational message only.

OI098 MAXIMUM VALUE IS TOO LARGE - MAX = nnnnExplanation: You entered a value greater than the maximum allowed.System Action: None.User Response: Specify a maximum value less than or equal to the maximum value allowed (nnnn).

OI099 MAXIMUM SCALE VALUE MUST BE EQUAL TO OR GREATER THAN 8Explanation: A value less than 8 was entered for the maximum scale value. The maximum scale value must be equal to or greater than 8.System Action: None.User Response: None. This is an informational message only.

ODC001–OIA97Y 39

OI100 ENTRY NOT FOUNDExplanation: OMEGAMON did not find a table entry for the name given.System Action: None.User Response: Check the spelling of the name.

OI101 NO ENTRIES FOUNDExplanation: OMEGAMON did not find any table entries for the name given.System Action: None.User Response: None. This is an informational message only.

OI102 NULL INPUTExplanation: You did not enter any input data for the command.System Action: None.User Response: Enter the required input data.

OI108 ENTRY SELECTED IS OUTSIDE THE TABLE - MAX = nnnnExplanation: The table entry number exceeds the number of entries (nnnn) in the table.System Action: None.User Response: Select an entry number within the range of the table.

OI109 ARGUMENT MUST BE GREATER THAN ZEROExplanation: A value of zero is in the command argument field (columns 6 and 7): the command requires a value of 1 or more.System Action: None.User Response: Enter a valid number in the command argument field.

OI200 USE “-” IN COLUMN 1 TO ATTACH THE DEXAN COLLECTORExplanation: The DEXAN collector was not attached.System Action: DEXAN ignores all IDEG minor commands.User Response: To attach the DEXAN collector, enter a hyphen (-) in column 1 to the left of the IDEG command.

OI201 COLLECTOR NOT ACTIVE, REQUEST IGNOREDExplanation: You tried to stop, suspend, or resume a DEXAN collector that is not active.System Action: DEXAN ignores the request.User Response: None. This is an informational message only.

OI202 COLLECTOR IS BUSY, TRY AGAINExplanation: The MDEX or PDEX command found that the DEXAN collector was in the process of updating the bottleneck analysis buckets, and therefore does not display the bucket data.System Action: OMEGAMON does not format the MDEX or PDEX display.User Response: Execute the command again.


OI203 COLLECTOR SUSPENDED, VALUES SHOWN NOT CURRENTExplanation: DEXAN received an IDEG SUSP command. The DEXAN collector suspended, and is no longer collecting information. The collector displays the data that was available at the time it suspended.System Action: None.User Response: To restart the collector, enter the IDEG minor command RESM.

OI204 DEXAN COLLECTOR ABORTED, ERROR CODE= 00000nnnnExplanation: The DEXAN collector detected an error condition and forced itself to end abnormally (abend).System Action: None.User Response: Issue the IDEG minor command ABCD to get the abend information and contact Candle Support Services. To restart the collector, follow these steps: 1. Either enter the -IDEG command with a hyphen (-) in column 1, or enter the

interface command START DEXAN and then enter the IDEG command.2. Enter the BEGN minor command to begin sampling.

OI205 COLLECTOR ESTAE, SDWA NOT AVAILABLE 00xxxnnnnExplanation: The DEXAN collector abended with system code xxx or user code nnnn; no system diagnostic work area (SDWA) was available with abend register information.System Action: None.User Response: Contact Candle Support Services. To restart the collector, issue the interface command START DEXAN and the IDEG minor command BEGN.

OI206 COLLECTOR HAS NOT ABENDEDExplanation: The user tried to display DEXAN collector abend information via the ABCD command, but the DEXAN collector had not abended.System Action: None.User Response: None. This is an informational message only.

OI207 DEXAN COLLECTOR IS BEING ATTACHEDExplanation: The action character (-) was entered with the IDEG command to attach the DEXAN collector.System Action: The DEXAN collector attaches.User Response: None. This is an informational message only.

OI210 DEXAN CYCLE RATE MUST BE 01-99Explanation: The user entered an invalid number for the DEXAN sampling rate.System Action: None.User Response: Enter a value from 1 (.1 seconds) to 99 (9.9 seconds).

ODC001–OIA97Y 41

OI214 DEXAN COLLECTOR HAS ABENDED, SYSTEM CODE= 00xxx000Explanation: The DEXAN collector terminated with a system abend code of xxx.System Action: None.User Response: Issue the ABCD minor command of IDEG to get the abend information and contact Candle Support Services. To restart the collector, follow these steps:1. Either enter the -IDEG command with a hyphen (-)in column 1, or enter the

interface command START DEXAN and then enter the IDEG command.2. Enter the BEGN minor command to begin sampling.

OI215 INVALID GROUP NUMBER. VALID GROUPS ARE 1-nn.Explanation: You entered an invalid group number. The variable nn. represents the maximum group number allowed.System Action: None.User Response: Enter the MAXG command to determine the valid group number range.

OI217 “BMP” ACTIVITY ALREADY BEING RECORDED; REQUEST IGNOREDExplanation: You entered a BMPXOF command when the BMP exclusion option was already turned off.System Action: None.User Response: None. This is an informational message only.

OI218 “BMP” ACTIVITY ALREADY BEING IGNORED; REQUEST IGNOREDExplanation: You entered a BMPXON command when the BMP exclusion option was already turned on.System Action: None.User Response: None. This is an informational message only.

OI221 COLLECTOR SUSPENDED, REQUEST IGNOREDExplanation: The user tried to start (BEGN command) or suspend (SUSP command) the DEXAN collector when it was already suspended.System Action: None.User Response: Enter the IDEG minor command RESM to cause the collector to resume recording.

OI222 COLLECTOR NOT SUSPENDED, REQUEST IGNOREDExplanation: The user tried to resume the DEXAN collector (RESM command) but it was not suspended.System Action: None.User Response: None. This is an informational message only.

OI225 COLLECTOR NOT ATTACHED, REQUEST IGNOREDExplanation: The DTCH minor command of IDEG was entered, but the collector was not attached.System Action: DEXAN ignores the command.User Response: None. This is an informational message only.


OI241 COLLECTOR ALREADY ACTIVE, “BEGN” IGNOREDExplanation: You tried to start (BEGN command) the DEXAN collector when it was already active.System Action: None.User Response: None. This is an informational message only.

OI254 “DBSW” ALREADY ON; REQUEST IGNOREDExplanation: You entered a DBSWON command when the database I/O by database name exclusion option was already turned on.System Action: None.User Response: None. This is an informational message only.

OI255 “DBSW” ALREADY OFF; REQUEST IGNOREDExplanation: You entered a DBSWOF command when the database I/O by database name exclusion option was already turned off.System Action: None.User Response: None. This is an informational message only.

OI258 DEXAN COLLECTOR ACTIVE; REQUEST IGNOREDExplanation: You tried to change the database I/O by database name recording option while the DEXAN collector was active.System Action: None.User Response: To change the database I/O recording option, first stop the collector. To do this, enter the IDEG minor command END. After you change the database I/O option (via the DBSW command), you can restart the collector by entering the IDEG minor command BEGN.

OI259 STORAGE SHORTAGE; I/O ANALYSIS CANNOT BE DONE BY DATABASEExplanation: The DEXAN collector attempted to gather database I/O wait information by individual database name, but there is not enough virtual storage available for the DEXAN collector to acquire the necessary bucket areas.System Action: The DEXAN collector only collects total database I/O wait statistics; it does not display statistics by individual database name.User Response: If possible, make more virtual storage available to the address space in which the DEXAN collector is running.

OI271 EPILOG/IMS ACTIVE - ALL TRANSACTIONS RECORDEDExplanation: While EPILOG is active, all transactions are monitored by DEXAN.System Action: Transaction activity is monitored by DEXAN.User Response: None.

OI272 EPILOG/IMS ACTIVE - BMPS CANNOT BE E

Candle Products Messages Manual, Vol 5publib.boulder.ibm.com/tividd/td/ITCPMess/GC32... · an IMS...

Documents

Transcript of Candle Products Messages Manual, Vol 5publib.boulder.ibm.com/tividd/td/ITCPMess/GC32... · an IMS...