Candle Products Messages Manual, Vol 2 - IBMpublib.boulder.ibm.com/tividd/.../GC32-9171-00/en_US/PDF/GC32-9171-00.pdf · Candle Products Messages Manual Volume 2 (EU–KLVGM) GC32-9171-00

Candle Products Messages ManualVolume 2

(EU–KLVGM)

GC32-9171-00

March 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245-9796

2 Candle Products Messages Manual (EU–KLVGM)

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 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 eDelivery, 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. EU001–KAO09998 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. KAT0001E–KCFCM091E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 3. KCG0000I–KDFCT003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Chapter 4. KDFD001I–KLGLM027 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Chapter 5. KLGOP011–KLVGM006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Contents


EU001–KAO09998 5

EU001–KAO09998

EU001 TAPE ARCHIVE FAILEDExplanation: Due to a previous error, the EVTDUMP function terminated.System Action: EVTDUMP processing terminates.User Response: Correct the error(s), and rerun the EVTDUMP EXEC.

EU002 INVALID TAPn PARAMETER: xxxxExplanation: An invalid value was specified as the tape drive address.System Action: EVTDUMP terminates with a return code of 12.User Response: Correct the error(s), and rerun the EVTDUMP EXEC.

EU003 DATE SPECIFIED: date IS INVALID, MAXIMUM LENGTH IS 6Explanation: An invalid parameter was specified for the date.System Action: EVTDUMP terminates with a return code of 12.User Response: Correct the error(s), and rerun the EVTDUMP EXEC.

EU004 DATE SPECIFIED: date IS INVALID, MUST BE NUMERICExplanation: The date specified by the user is invalid.System Action: EVTDUMP terminates with a return code of 12.User Response: Rerun the EVTDUMP EXEC with the proper date.

EU005 PARAMETER parm IS INVALID AS SPECIFIED,OPTIONS MUST BE SPECIFIED AFTER AN OPEN PARENTHESISExplanation: The indicated parameter was entered incorrectly.System Action: EVTDUMP terminates with a return code of 12.User Response: Delete the extraneous argument, or insert an open (left) parenthesis.

EU006 TAPE REWIND COMMAND FAILED. RETURN CODE: rcExplanation: The TAPE command returned a non-zero return code. This problem could be caused by not attaching a tape drive.System Action: EVTDUMP waits 15 seconds and retries the command.User Response: Verify that the tape drive is attached properly.

1


EU007 OPERATION WILL BE RETRIED IN 15 SECONDSEXEC EXECUTION WILL BE ABORTED AFTER n MORE ATTEMPTSExplanation: This message appears with message EU006 to indicate that the command will be retried again.System Action: None.User Response: Verify that the tape drive is attached properly.

EU008 fn ft fm WOULD HAVE BEEN processedExplanation: This message appears when the LIST and NODUMP options are specified on the EVTDUMP EXEC. The processed portion of the message will say either ’dumped to tape’ or ’copied to disk’, depending on the options specified on the EVTDUMP EXEC.System Action: None.User Response: None. This is an informational message only.

EU009 TAPE DUMP|COPYFILE COMMAND FAILED. RETURN CODE: rc,WHILE DUMPING|COPYING fn ft fm, DASD BLOCKS: nnnn FILES DUMPED|COPIED SO FAR, TAKING UP nn DASD BLOCKSExplanation: The CMS TAPE DUMP or COPYFILE command terminated with a non-zero return code.System Action: EVTDUMP terminates with a return code of 12.User Response: Look up the specified return code under the CMS TAPE or COPYFILE command. Refer to IBM System Messages and Codes Reference manual for return code information.

EU010 NO FILES HAVE BEEN ERASEDExplanation: The TAPE command terminated with a non-zero return code, and no files have been erased.System Action: EVTDUMP terminates with a return code of 12.User Response: Look up the return code under the CMS TAPE command.

EU011 TAPE WTM COMMAND FAILED. RETURN CODE: rcExplanation: The TAPE command terminated with a non-zero return code while it was attempting to write a tapemark onto the tape.System Action: EVTDUMP terminates with a return code of 12.User Response: Look up the specified return code under the CMS TAPE command.

EU012 TRYING TO ERASE FILE: fn ft fmEVTDUMP ABORTED, NO MORE FILES WILL BE ERASEDExplanation: EVTDUMP was unable to erase the specified file.System Action: EVTDUMP terminates with a return code of 8.User Response: Look up the return code under the CMS ERASE command, if appropriate.

EU001–KAO09998 7

EU013 RETURN CODE: rcExplanation: The ERASE command terminated with a non-zero return code.System Action: The system prints message EU012.User Response: Look up the specified return code under the CMS ERASE command.

EU014 DISK c NOT ACCESSEDExplanation: The indicated disk is not currently accessed.System Action: EVTDUMP terminates with a return code of 12.User Response: Correct the error(s), and rerun the EVTDUMP EXEC.

EU015 EVTDUMP OPTIONS: TO=TAPn FROM=c IPREFIX=xx, COLLID=xxxxxxxxoptionsExplanation: This message displays the values used for the EVTDUMP options.System Action: None.User Response: None. This is an informational message only.

EU016 IF YOU CONTINUE, nn FILE(S) WILL BE ERASEDWITHOUT BEING DUMPED TO TAPE.DO YOU WISH TO CONTINUE? (Y/N) (N IS THE DEFAULT)Explanation: This message appears if the ERASE and NODUMP options are specified on the EVTDUMP EXEC.System Action: The system waits for a user response.User Response: Reply Y to continue processing, or N to abort processing.

EU017 NO FILES ON DISK diskmode WERE SELECTED FOR PROCESSINGExplanation: This message is issued when no files have met the selection criteria.System Action: EVTDUMP terminates with a return code of 12.User Response: Verify that the minidisk containing the EPILOG datastore is accessed properly and that the selection criteria are entered correctly.

EU018 EVTDUMP STATISTICS FOLLOW:nn FILES HAVE BEEN PROCESSEDnn (nnnn BYTE) BLOCKSAPPROXIMATELY nn% OF DISKuserid diskmode-DISK IS NOW APPROXIMATELY nn% FULLExplanation: This message is issued after processing is complete.System Action: None.User Response: None. This is an informational message only.

EU019 RC=rc ON LINE nnnerror messageline containing the syntax errorExplanation: This message is issued if there is a syntax error in the EVTDUMP EXEC.System Action: EVTDUMP terminates with a return code of 999.User Response: Contact your Candle Customer Support Services representative with the information provided in the error message.


EU020 xx IS AN INVALID option PARAMETERExplanation: An invalid parameter was specified on an EVTDUMP option.System Action: EVTDUMP terminates with a return code of 12.User Response: Correct the error(s), and rerun the EVTDUMP EXEC.

EU021 option IS AN UNKNOWN EVTDUMP OPTIONExplanation: An invalid EVTDUMP option was specified.System Action: EVTDUMP terminates with a return code of 12.User Response: Correct the error(s), and rerun the EVTDUMP EXEC.

EU022 EVTDUMP invocation parmsExplanation: These are the parameters that invoke the EVTDUMP EXEC.System Action: None.User Response: None. This is an informational message only.

EU023 RETURN CODE=rc, ATTEMPTING TO LOCATE USERID: collid==> messageExplanation: EVTDUMP was unable to locate the VM user ID of the COLLECT server specified by the user.System Action: The EVTDUMP EXEC terminates with a return code of 12.User Response: Make sure that the ID specified is logged onto the system.

EU024 DATASTORE IS ACCESSED R/O, WILL ERASE FILES VIA collidExplanation: This message tells you that EPILOG datastore files will be erased via SMSGing the collector virtual machine.System Action: None.User Response: None. This is an informational message only.

EU025 RETURN CODE=rc, WHILE COMMUNICATING WITH collid==> messageExplanation: The EVTDUMP EXEC was unable to SMSG the collector virtual machine to perform an ERASE. The message text is returned by CP and will only appear if rc = 57.System Action: EVTDUMP will print message EU012.User Response: Consult the IBM System Messages and Codes Reference for the CP return code, CP text, and take appropriate action.

EU026 BAD time VALUE: nnn.MUST BE A NUMBER FROM 1 TO nnn.Explanation: The data type or value range for the specified time unit is invalid. Time unit will be either days or months.System Action: EVTDUMP stops processing.User Response: Correct the time value according to the specified range and run EVTDUMP again.

EU001–KAO09998 9

EU027 DISK SPECIFIED ON TO PARAMETER IS NOT READ/WRITEExplanation: The target disk specified on the TO parameter of the EVTDUMP EXEC is not linked in READ/WRITE mode.System Action: EVTDUMP stops processing.User Response: Gain READ/WRITE access to the target disk and run EVTDUMP again.

EU028 RETURN CODE= rc, WHILE COMMUNICATING WITH collid ==>messageExplanation: THE EVTDUMP EXEC was unable to SMSG the collector virtual machine to perform an ERASE. The message text is returned by CP and will appear if rc = 57.System Action: EVTDUMP prints message EU029 and retries the SMSG ERASE.User Response: None. This is an informational message only. Consult the IBM System Messages and Codes Reference for the CP return code and CP text.

EU029 TRYING TO ERASE FILE: fn ft fmOPERATION WILL BE RETRIED IN n SECONDSEXEC EXECUTION WILL ABORT AFTER n MORE ATTEMPTSExplanation: The EVTDUMP EXEC was unable to SMSG the collector virtual machine to perform an ERASE and is attempting to retry the ERASE.System Action: EVTDUMP retries the SMSG ERASE in n seconds and continues to retry the failing SMSG ERASE command for n more attempts.User Response: None. This is an informational message only.

EU101 TAPE LOAD FAILEDExplanation: Due to a previous error, the EVTLOAD function terminated.System Action: EVTLOAD terminates.User Response: Correct the error(s), and rerun the EVTLOAD EXEC.

EU102 INVALID TAPn PARAMETER: xxxxExplanation: An invalid value was specified as the tape drive address.System Action: EVTLOAD terminates.User Response: Correct the error(s), and rerun the EVTLOAD EXEC.

EU103 INVALID PARAMETER: date. MAXIMUM LENGTH IS 6Explanation: An invalid parameter was specified for the date.System Action: EVTLOAD terminates.User Response: Correct the error(s), and rerun the EVTLOAD EXEC.

EU106 TAPE REWIND COMMAND FAILED. RETURN CODE: rcExplanation: A non-zero return code was returned from the TAPE command. This problem can be caused by not attaching a tape drive.System Action: EVTLOAD waits 1 minute to see if the tape drive appears.User Response: Verify that the tape drive is attached properly.


EU107 OPERATION WILL BE RETRIED IN 15 SECONDSExplanation: This message is used with EU106 to inform the user that the command will be retried again.System Action: None.User Response: Verify that the tape drive is attached properly.

EU108 EXEC EXECUTION WILL BE ABORTED AFTER n MORE ATTEMPTSExplanation: This message is used with EU106 and EU107 to indicate the number of command retries to be performed.System Action: None.User Response: Verify that the tape drive is attached properly.

EU115 TAPE LOAD COMMAND FAILED. RETURN CODE: retcodeExplanation: The TAPE command terminated with a non-zero return code while attempting to load data to disk.System Action: EVTLOAD terminates.User Response: Look up the return code under the CMS TAPE command that describes the reason for the failure.

EU116 NO FILES HAVE BEEN LOADEDExplanation: Due to previous errors, no files were loaded from the tape.System Action: None.User Response: Correct the error(s), and rerun the EVTLOAD EXEC.

EU120 parm IS AN INVALID EVTLOAD OPTIONExplanation: An invalid EVTLOAD parameter was specified.System Action: EVTLOAD terminates.User Response: Correct the error(s), and rerun the EVTLOAD EXEC.

EU121 parm IS AN UNKNOWN EVTLOAD OPTIONExplanation: An invalid EVTLOAD parameter was specified.System Action: EVTLOAD terminates.User Response: Correct the error(s), and rerun the EVTLOAD EXEC.

EU122 EVTLOAD invocation parmsExplanation: These are the parameters that invoke the EVTLOAD EXEC.System Action: None.User Response: None. This is an informational message only.

EU125 EVTLOAD REQUIRES DISK n TO LOAD THE REQUESTED DATASTOREExplanation: EVTLOAD is trying to restore a datastore to its original minidisk, and that disk cannot be accessed.System Action: None.User Response: Access the required disk, and run the EVTLOAD utility again.

EU201 THE EVACCUM FUNCTION FAILEDExplanation: Due to a previous error, the ACCUM function terminated.System Action: EVACCUM terminates.User Response: Correct the error(s), and rerun the EVACCUM EXEC.

EU001–KAO09998 11

EU220 parm IS AN INVALID EVACCUM OPTIONExplanation: The user specified an invalid parameter for an option.System Action: EVACCUM terminates.User Response: Correct the error(s), and rerun the EVACCUM EXEC.

EU221 parm IS AN UNKNOWN EVACCUM OPTIONExplanation: The user specified an invalid or unknown option.System Action: EVACCUM terminates.User Response: Correct the error(s), and rerun the EVACCUM EXEC.

EU222 EVACCUM invocation parmsExplanation: These are the parameters that invoke the EVACCUM EXEC.System Action: None.User Response: None. This is an informational message only.

EU230 UNABLE TO LOCATE THE EPILOG DATASTOREExplanation: The EVACCUM command was unable to locate one of the EPILOG for VM datastore control files.System Action: The EVACCUM command terminates.User Response: Ensure that the CMS minidisk that contains the EPILOG datastore is properly accessed.

EU231 ACCUM CONTROL FILE: fn ft fm, RESIDES ON A R/O DISKExplanation: The ACCUM control file is on a disk that is not READ/WRITE.System Action: The EVACCUM command terminates.User Response: Move the ACCUM control file to a READ/WRITE disk, and rerun the EVACCUM command.

EU232 UNABLE TO LOCATE ACCUM CONTROL FILE: fn ft fmExplanation: The ACCUM control file could not be located.System Action: The EVACCUM command terminates.User Response: Verify that you have specified the correct name for the ACCUM control file and that the disk is accessed properly.

EV100 ONLY ONE REPORT TYPE ALLOWEDExplanation: The REPORT command only supports one report type at a time.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the command and restart the reporter.

EV102 GRAPH AND MAXSCALE ARE INVALID FOR THIS REPORTExplanation: This report type does not support the GRAPH or MAXSCALE options. System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the command and restart the reporter.


EV103 REPORT TYPE IS MISSINGExplanation: The REPORT command requires a report type keyword.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the command and restart the reporter.

EV104 cccccccc INVALID WITH cccc REPORTExplanation: The specified option is invalid on the selected report.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the command and restart the reporter.

EV105 INVALID KEYWORD FOR PRTCNTL COMMANDExplanation: An invalid keyword was selected for the PRTCNTL command.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the keyword and restart the reporter.

EV106 REPORT TYPE IS INVALIDExplanation: The report type selected is invalid.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the command and restart the reporter.

EV107 INVALID LINE VALUE ON PRTCNTL COMMANDExplanation: The value specified in the line parameter is invalid.System Action: The reporter stops processing the PRTCNTL command and starts processing the next command.User Response: Correct the line value and restart the reporter.

EV110 SPECIFIED GRAPH ELEMENT IS INVALID FOR THIS REPORTExplanation: The element specified for GRAPH is invalid with the current report.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the graph element and restart the reporter.

EV111 SPECIFIED GRAPH ELEMENT IS NOT GRAPHABLEExplanation: The element specified for GRAPH is not graphable.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the graph element and restart the reporter.

EV112 GRAPH TYPE (VBAR OR LINE) WAS NOT SPECIFIEDExplanation: The graph type is either invalid or missing for the GRAPH parameter.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the graph type and restart the reporter.

EU001–KAO09998 13

EV113 INVALID FIELD NAME ON GRAPH OPTIONExplanation: The element specified for GRAPH does not exist.System Action: Processing for the current command is stopped and the next command is started.User Response: Correct the graph element and restart the reporter.

EV114 INVALID FIELD NAME ON SORTBY OPTIONExplanation: The element specified for SORTBY does not exist.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SORTBY element and restart the reporter.

EV115 SPECIFIED SORTBY ELEMENT IS INVALID FOR THIS REPORTExplanation: The element specified for SORTBY is invalid with the current report.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SORTBY element and restart the reporter.

EV116 SPECIFIED SORTBY ELEMENT IS NOT SORTABLEExplanation: The element specified for SORTBY is not sortable.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SORTBY element and restart the reporter.

EV117 SORTBY CANNOT BE SPECIFIED FOR THIS REPORTExplanation: The SORTBY keyword cannot be used with the GRAPH keyword.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Delete SORTBY from the command and restart the reporter.

EV118 NUMBER OF SORTBY ELEMENTS EXCEEDS MAXIMUM ALLOWEDExplanation: You have specified too many elements on the SORTBY keyword.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Delete some entries from the SORTBY keyword and restart the reporter.

EV119 INVALID SEQUENCE SPECIFIED (MUST BE A OR D)Explanation: The SORTBY sequence specified was not A or D.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SORTBY sequence and restart the reporter.


EV120 MAXSCALE IS INVALID WITHOUT GRAPHExplanation: MAXSCALE was specified without GRAPH.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Either delete MAXSCALE or add GRAPH and restart the reporter.

EV121 MAXSCALE UNIT IS INVALID FOR GRAPH ELEMENTExplanation: The MAXSCALE unit specified is invalid for the specified graph element.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Change either the MAXSCALE unit or the graph element and restart the reporter.

EV122 INVALID FIELD NAME ON SELECTIF OPTIONExplanation: The element specified for SELECTIF does not exist.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SELECTIF element and restart the reporter.

EV123 SPECIFIED SIF ELEMENT IS INVALID FOR THIS REPORTExplanation: The element specified for SELECTIF is invalid with the current report.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SELECTIF element and restart the reporter.

EV124 SPECIFIED SELECTIF ELEMENT IS NOT SELECTABLEExplanation: The element specified for SELECTIF is not selectable.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the SELECTIF element and restart the reporter.

EV125 INVALID UNIT OF STORAGE FOR EXCEPTION LIMITExplanation: The value specified for a storage element has an invalid suffix.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the value for the storage element and restart the reporter.

EV126 INVALID QUOTED CHARACTER STRINGExplanation: The value specified within quotes is invalid.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the value within quotes and restart the reporter.

EU001–KAO09998 15

EV127 THE MINIMUM COMBINE INTERVAL ALLOWED IS 15 MINUTESExplanation: The combine interval selected is less than the minimum allowable (15 minutes).System Action: The reporter stops processing the current command and starts processing the next command.User Response: Increase the combine interval and restart the reporter.

EV128 SUMMARY AND GRAPH CANNOT BE SPECIFIED TOGETHERExplanation: The two keywords, SUMMARY and GRAPH, cannot be specified on the same reporter command.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Modify the report request and restart the reporter.

EV200 GROUP ID EXCEEDS 8 CHARACTERSExplanation: The group ID specified is longer than the maximum 8-character limit.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the group ID keyword and restart the reporter.

EV201 GROUP MEMBER NAME OR SUBNAME IS INCORRECT LENGTHExplanation: A member in the specified group ID exceeds the maximum 8-character limit.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Correct the group ID member name and restart the reporter.

EV202 GROUPS CAN NOT BE SPECIFIED FOR THIS REPORTExplanation: A group was specified and the current report is not a workload report.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Either delete the group selection or change the report type and restart the reporter.

EV210 NO GROUPS WERE PREVIOUSLY DEFINEDExplanation: No group was defined previously for this group selection.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Either delete the group selection or add a SET command to define this group prior to starting the REPORT command.


EV211 GROUP SPECIFIED COULD NOT BE FOUNDExplanation: Group selected in REPORT command could not be found as a previously defined group definition.System Action: The reporter continues processing current command with default values.User Response: Either delete the group selection or add a SET command to define this group prior to starting the REPORT command.

EV212 GROUPID NOT SPECIFIED ON REPORT COMMANDExplanation: Group name was not specified on report command.System Action: The reporter continues processing current command with default values.User Response: Specify a group name on the report command or remove the group option from the report command.

EV220 NO GROUP FOUND FOR SET COMMANDExplanation: Group name was not specified for SET command.System Action: Processing for the current command is continued and this option is ignored.User Response: Specify a group name to be cleared by the SET command or remove group option.

EV221 CANNOT LOCATE GROUP TO BE CLEAREDExplanation: Group name to be cleared with SET command cannot be located as a defined group.System Action: Processing for the current command is continued and this option is ignored.User Response: Remove SET command which is attempting to clear group.

EV222 HEX CONVERSION ERROR ENCOUNTEREDExplanation: The value specified for a hexadecimal field has invalid characters.System Action: Processing for the current command is stopped and the next command is started.User Response: Correct the entry for the hexadecimal data and restart the reporter.

EV260 INCONSISTENT LRECL FOR EPILOG DATA FILESExplanation: Data file for the same report have different logical record lengths and therefore are considered invalid.System Action: Data processing terminates.User Response: Contact Candle Customer Support Services and report the exact text of the message and include the code number.

EV261 EPILOG DATA MISSING FOR FILETYPE ccccccExplanation: Data file for the EPILOG reporter could not be found.System Action: Processing terminates.User Response: Make sure the LINK and ACCESS to the datastore are correct, and check and see if the collector is writing data to the datastore.

EU001–KAO09998 17

EV270 UNABLE TO COLLECT DATASTORE STATISTICSExplanation: An error occurred while the reporter was gathering datastore percent full data.System Action: Processing continues and no database statistics are reported.User Response: Contact Candle Customer Support Services and report the exact text of the message, including the code number.

EV271 INVALID MODE SPECIFIED FOR DATASTORE STATISTICSExplanation: Filemode of datastore that the collector is currently writing to is either invalid or is not passed as the first parameter to the EPILOG module.System Action: Processing continues and no datastore statistics are reported.User Response: Check that the correct filemode is passed to the EPILOG module.

EV300 REPORTER Vnnn IS INCOMPATIBLE WITH COLLECTOR VnnnExplanation: The EPILOG reporter release is incompatible with the release of the collector.System Action: The reporter terminates.User Response: Reinstall both the collector and the reporter to ensure compatibility.

EV301 THE EPILOG STARTUP FILE COULD NOT BE FOUNDExplanation: The collector either did not write a start-up file to the EPILOG datastore or it was inadvertently erased. The start-up file has a file type of Start-up.System Action: The reporter continues to run with unpredictable results.User Response: Start the collector and check to see if a start-up file is generated. If not, call Candle Customer Support.

EV350 NON-VM/HPO DATA WAS DETECTED FOR REPORT RSWAPExplanation: The RSWAP report was requested and non-VM/HPO data was detected in the database. The RSWAP report is only valid for VM/HPO.System Action: The report continues in case VM/HPO data also exists in the database.User Response: This is an informational message. Do not request RSWAP for a non-VM/HPO database.

EV352 nnnnnn RECORDS REJECTED DUE TO ccccccccccccccExplanation: This is an informational message that records the number of records which were not selected for the report and why they were not selected. Possible reasons are:

System Action: The reporter continues to run.User Response: None. This is an informational message only.

Selection Criteria Did not pass SIF processing.

Short interval Insufficient samples in a collection interval.

Conversion errors Records rejected due to bad input data.

Report requirements Redundant data removed for accuracy.


EV360 VM DATA INCOMPATIBLE WITH THIS REPORT REQUESTExplanation: The report requested does not support your version of VM data.System Action: The reporter stops processing the current command and starts processing the next command.User Response: Modify the report request and restart the reporter.

EV401 ACCUMCTL FILE MUST BE ON A WRITABLE DISKExplanation: The control file containing the ACCUM command must be placed on a READ/WRITE CMS minidisk.System Action: The ACCUM function terminates.User Response: Place the ACCUM control file on a CMS minidisk that has READ/WRITE access.

EV402 UNABLE TO OPEN FILE: filename filetype filemodeExplanation: The ACCUM function was unable to open the specified file.System Action: ACCUM processing continues.User Response: None. This is an informational message only.

EV403 WARNING, NO FILES QUALIFIED FOR THE ACCUM PROCESSExplanation: The ACCUM function was unable to find any files to process.System Action: ACCUM processing terminates normally.User Response: Verify that disks are accessed properly.

EV404 INVALID COMBINE INTERVAL SPECIFIEDExplanation: The ACCUM control file created by the user contains an invalid COMBINE specification.System Action: The ACCUM function terminates.User Response: Edit the ACCUM control file, and alter the COMBINE parameter. Valid COMBINE periods are: 1H, 24H, or 1D.

EV405 RC=nnnn UNABLE TO READ OR WRITE DATA TO FILE: fn ft fmExplanation: The ACCUM function was unable to read or write data to the specified file.System Action: The ACCUM function terminates.User Response: The return code in the message text is the CMS return code from the CMS FSREAD or FSWRITE macro.

EV406 NO COMBINE SPECIFIEDExplanation: The ACCUM control file created by the user contains no COMBINE specification.System Action: The ACCUM function terminates.User Response: Edit the ACCUM control file, and add a COMBINE keyword followed by one of the following options: 1H, 24H, or 1D.

EV407 UNABLE TO LOCATE DDNAME: EVSYSINExplanation: The ACCUM function was unable to locate the CMS FILEDEF for the EVSYSIN. System Action: The ACCUM function terminates.User Response: Verify that the CMS FILEDEF for EVSYSIN has been issued.

EU001–KAO09998 19

EV408 UNABLE TO ALLOCATE STORAGEExplanation: The ACCUM function attempted to allocate more storage than was available.System Action: The ACCUM function terminates.User Response: Define additional memory, and rerun EVACCUM EXEC.

EV410 UNABLE TO OPEN THE ACCUM CONTROL FILEExplanation: The ACCUM function failed to open the ACCUM control file.System Action: The ACCUM function terminates.User Response: Verify that the ACCUM control exists on a writable disk, and rerun EVACCUM EXEC.

EV411 UNABLE TO COPY filename Start-up, RC=retcodeExplanation: The ACCUM function was unable to copy the specified EPILOG control file.System Action: The ACCUM function continues with the next file.User Response: The specified EPILOG control file is not accessible. Check to see that all the EPILOG for VM minidisks are accessed properly.

EV414 UNABLE TO LOCATE DDNAME: EVACCLOGExplanation: The ACCUM function was unable to locate the CMS FILEDEF for EVACCLOG. This file contains the pointer to the location of the ACCUM log file being created.System Action: The ACCUM function terminates.User Response: Ensure that the CMS FILEDEF for EVACCLOG has been issued and that it points to an existing CMS file. It is preferable for this file to be located on the same disk as the ACCUM control file.

EV415 UNABLE TO WRITE TO THE LOG FILE, RC=retcodeExplanation: The ACCUM function was unable to write data to the ACCUM log file.System Action: The ACCUM function terminates.User Response: The retcode in the message text is the CMS return code from the CMS FSWRITE macro. Check the return code with those specified for the CMS FSWRITE macro.

EV416 UNABLE TO WRITE TO filename FILE, RC=retcodeExplanation: The ACCUM function was unable to write data to the specified file.System Action: The ACCUM function terminates.User Response: The retcode in the message text is the CMS return code from the CMS FSWRITE macro. Check the return code with those specified for the CMS FSWRITE macro.

EV419 FIELD fldname IN RECORD recname HAS INVALID DATAExplanation: An invalid data value was detected for the field name and record specified.System Action: ACCUM bypasses the field and continues processing.User Response: If the problem persists, notify Candle Customer Support.


EV800 THE LINES VALUE IS TOO SMALL TO PRODUCE A GRAPHExplanation: The lines parameter value you specified is too small to allow a graph to be printed. The minimum value is 24.System Action: The REPORT GRAPH command is not processed.User Response: Increase the lines value to 24 or longer.

EV810 LINES COUNT RESET TO 24, THE VALUE IS TOO LOW IN COLUMN nnExplanation: The lines parameter value you selected is below the minimum value allowed. The minimum value is 24.System Action: The lines value is set to 24.User Response: Either accept the minimum value (24) or increase the lines value to 24 or larger.

EVS000 EPILOG/IMS WILL NOT COLLECT VSAM SUBPOOL STATISTICSExplanation: EPILOG found that no VSAM subpools were defined to the IMS system.System Action: EPILOG will not collect VSAM subpool statistics.User Response: None.

EVS001 EPILOG/IMS EDS OPENEDExplanation: EPILOG has been started, and the EDS has been opened successfully.System Action: Processing continues.User Response: None.

EVS003 EPILOG/IMS EDS CLOSEDExplanation: The EDS has been closed.System Action: Processing continues.User Response: None.

EVS901 RKEIEDS SHOWCB ERROR - EPILOG/IMS IS TERMINATINGExplanation: An error occurred during OPEN processing of the EPILOG datastore.System Action: The EPILOG write subtask terminates. A U0303 abend accompanies this message, because the dump from the U0303 abend is needed to determine the SHOWCB feedback code.User Response: Call Candle Support Services.

EVS903 EPILOG/IMS FAILED TO OBTAIN VSAM ACB STORAGE - TERMINATINGExplanation: Not enough storage was available to build an ACB for the EPILOG datastore, pointed to by the RKEIEDS DD statement.System Action: The EPILOG collector terminates.User Response: See the Configuration and Customization Guide, for region size needed. If the region size is sufficient and the problem persists, call Candle Support Services.

EU001–KAO09998 21

EVS905 RKEIEDS GENCB ERROR - EPILOG/IMS IS TERMINATINGExplanation: An error occurred during OPEN processing of the EPILOG datastore.System Action: The EPILOG write subtask terminates. A U0303 abend accompanies this message. User Response: See the Configuration and Customization Guide, for region size needed. If the region size is sufficient and the problem persists, call Candle Support Services.

EVS907 RKEIEDS OPEN ERROR - EPILOG/IMS IS TERMINATINGExplanation: An error occurred during OPEN processing of the EPILOG datastore (EDS).System Action: The EPILOG write subtask terminates. A U0334 abend accompanies this message.User Response: See the product installation documentation, for defining and initializing the EPILOG dataset. If the EPILOG dataset is defined and initialized correctly and the problem persists, call Candle Support Services.

EVS909 RKEIEDS CLOSE ERROR - EPILOG/IMS IS TERMINATINGExplanation: An error occurred during CLOSE processing of the EPILOG datastore (EDS).System Action: EPILOG terminates immediately. A U0334 abend accompanies this message. User Response: Call Candle Support Services.

EVS911 RKEIEDS MODCB ERROR - EPILOG/IMS IS TERMINATINGExplanation: An error occurred during MODCB processing of the EPILOG datastore (EDS).System Action: EPILOG terminates immediately. A U0332 abend accompanies this message. User Response: Call Candle Support Services.

EVS913 EPILOG/IMS FAILED TO OBTAIN VSAM RPL STORAGE - TERMINATINGExplanation: EPILOG attempted to acquire private storage for the EDS VSAM RPL but was unable to do so.System Action: EPILOG terminates immediately. A U0333 abend accompanies this message. User Response: See the Configuration and Customization Guide for region size needed. If the region size is sufficient and the problem persists, call Candle Support Services.

EVS921 RKEIEDS ERROR RELEASING DATA RECORD STORAGE- EPILOG/IMS TERMINATINGExplanation: EPILOG attempted to release private storage but was unable to do so.System Action: EPILOG terminates immediately. A U0338 abend accompanies this message. User Response: Call Candle Support Services.


EVS923 RKEIEDS ERROR RELEASING RPL MESSAGE STORAGE - EPILOG/IMS TERMINATINGExplanation: EPILOG attempted to release private storage but was unable to do so.System Action: EPILOG terminates immediately. A U0339 abend accompanies this message. User Response: Call Candle Support Services.

EVS925 RKEIEDS ERROR RELEASING RPL POINTER STORAGE - EPILOG/IMS TERMINATINGExplanation: EPILOG attempted to release private storage but was unable to do so.System Action: EPILOG terminates immediately. A U0340 abend accompanies this message. User Response: Call Candle Support Services.

EVS927 RKEIEDS ERROR RELEASING ACB STORAGE - EPILOG/IMS TERMINATINGExplanation: EPILOG attempted to release private storage but was unable to do so.System Action: EPILOG terminates immediately. A U0341 abend accompanies this message. User Response: Call Candle Support Services.

EVS929 RKEIEDS UNABLE TO INSERT DATA RECORD TO EPILOG/IMS EDSExplanation: EPILOG attempted to insert a data record into the EDS but was unable to do so.System Action: EPILOG terminates immediately. A U0344 abend accompanies this message.User Response: Run an IDCAMS LISTCAT against the EDS cluster to determine if the EDS has run out of space. If the HIGH-USED-RBA is equal to the HIGH-ALLOC-RBA, then the dataset is full. See the OMEGAMON II for IMS Historical Component (EPILOG) Reference Manual, for the JCL necessary to increase the size of the EDS. If the problem persists, call Candle Support Services.

EVS931 RKEIEDS UNABLE TO INSERT POINTER RECORD TO EPILOG/IMS EDSExplanation: EPILOG attempted to insert a data record into the EDS but was unable to do so.System Action: EPILOG terminates immediately. A U0347 abend accompanies this message. User Response: Run an IDCAMS LISTCAT against the EDS cluster to determine if the EDS has run out of space. If the HIGH-USED-RBA is equal to the HIGH-ALLOC-RBA, then the dataset is full. See the OMEGAMON II for IMS Historical Component (EPILOG) Reference Manual, for the JCL necessary to increase the size of the EDS. If the problem persists, call Candle Support Services.

EVS932 ERROR ON PUT OR MODCB RETURN CODE=8 REASON CODE=156Explanation: The AMS return code and reason code are given in the text of the message. Refer to your System Messages Manual, message IDC3351I, to

EU001–KAO09998 23

determine the meaning of the return and reason codes and the recommended action.System Action: EPILOG terminates immediately. A U0347 abend accompanies this message.User Response: Run an IDCAMS LISTCAT against the EDS cluster to determine if the EDS has run out of space. If the HIGH-USED-RBA is equal to the HIGH-ALLOC-RBA, then the dataset is full. See the OMEGAMON II for IMS Historical Component (EPILOG) Reference Manual, for the JCL necessary to increase the size of the EDS. If the problem persists, call Candle Support Services.

EVS941 RKEIEDS DATASET NUMBER OF EXTENTS IS HIGH - WARNINGExplanation: EPILOG has determined that the number of extents that the EDS has is high. If the cluster has been defined UNIQUE, this message displays for 15 or more extents. If the cluster has been SUB-ALLOCATED, this message displays for 120 or more extents.System Action: EPILOG collection continues. A U0310 abend will occur if the EDS runs out of extents.User Response: See the OMEGAMON II for IMS Historical Component (EPILOG) Reference, for information concerning EDS maintenance.

EXnnn Exception message textExplanation: OMEGAMON II for VTAM exceptions are prefixed with EX. They are issued by the exception analysis feature of OMEGAMON II for VTAM. For more information, see the OMEGAMON II for VTAM User’s Guide.

H2C0351 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO LOCATE RKD2PAR DATASETExplanation: OMEGAMON II cannot locate the RKD2PAR dataset. The dataset specified probably does not exist.System Action: Processing terminates.User Response: Check the dataset specified for RKD2PAR and make sure that it is allocated.

H2C0352 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO OPEN RKD2PAR DATASETExplanation: OMEGAMON II cannot open the RKD2PAR dataset. The dataset specified probably does not exist.System Action: Processing terminates.User Response: Check the dataset specified for RKD2PAR and make sure that it is allocated.


H2C0353 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO LOCATE RKD2PAR MEMBER SPECIFIEDExplanation: OMEGAMON II cannot locate the RKD2PAR member. The member specified probably does not exist.System Action: Processing terminates.User Response: Check the dataset specified for RKD2PAR and make sure that the member is allocated.

H2C0354 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO ACQUIRE SUFFICIENT STORAGE TO READ RKD2PAR DATASETExplanation: OMEGAMON II cannot obtain sufficient storage to read the RKD2PAR dataset.System Action: Processing terminates.User Response: Contact Candle Customer Support.

H2C0355 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO ACQUIRE BUFFER STORAGE TO READ RKD2PAR DATASETExplanation: OMEGAMON II cannot acquire buffer storage to read the RKD2PAR dataset.System Action: Processing terminates.User Response: Contact Candle Customer Support.

H2C0356 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO ACQUIRE SUFFICIENT STORAGE FOR PARM PROCESSINGExplanation: OMEGAMON II cannot acquire sufficient storage for parameter processing.System Action: Processing terminates.User Response: Contact Candle Customer Support.

H2C0357 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED WORD WITH NON-ALPHANUMERIC CHARACTER IN THE RKD2PAR RECORD: recordExplanation: OMEGAMON II detected a word with a non-alphanumeric character in the RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0358 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INSUFFICIENT PARMS IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected insufficient parameters for the keyword in this RKD2PAR RECORD.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

EU001–KAO09998 25

H2C0359 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED UNBALANCED PARENTHESIS IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected an unbalanced parenthesis for the keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0360 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED KEYWORD/PARAMETER GREATER THAN 27 CHARACTERS OR INVALID KEYWORD IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected a keyword or parameter greater than 27 characters or an invalid keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0361 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID NON-NUMERIC CHARACTER IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected an invalid non-numeric character for the keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0362 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED ALPHA CHARACTERS WHERE NUMBER REQUIRED IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected an alphanumeric character; this RKD2PAR keyword requires a numeric value.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0363 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID NUMERIC CHARACTER IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected an invalid numeric character for the keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0364 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED TOO MANY PARMS IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected too many parameters for the keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.


H2C0365 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID PARM FOR KEYWORD IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected an invalid parameter for the keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0366 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID PARM OUT OF NUMERIC RANGE IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected a parameter out of numeric range in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0367 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INSUFFICIENT PARMS IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected insufficient parameters for the keyword in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0369 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED KEYWORD IMPROPERLY INVOKED TWICE IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected a keyword improperly invoked twice in this RKD2PAR record.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0370 OMEGAMON II/DB2 HISTORICAL FEATURE READ ERROR FROM RKD2PAR DATASET, SYNTAX MESSAGE FOLLOWS:Explanation: OMEGAMON II encountered an error while reading the RKD2PAR dataset.System Action: Processing terminates.User Response: Check the RKD2PAR dataset. If a partitioned dataset is used, make sure the member name is specified.

H2C0375 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID PARAMETER FOR KEYWORD keyword IN THIS RKD2PAR RECORD: recordExplanation: OMEGAMON II detected an invalid parameter specified for the keyword DSNZPARM. Valid options are YES or NO.System Action: Processing terminates.User Response: Check the RKD2PAR member and make sure that the DSNZPARM option is specified correctly.

EU001–KAO09998 27

H2C0380 OMEGAMON II/DB2 HISTORICAL FEATURE NOT USING ANY NEW PARMS FROM RKD2PAR MEMBERExplanation: OMEGAMON II will not use any new parameters from RKD2PAR member because an error was detected.System Action: Processing terminates.User Response: Check the RKD2PAR member and correct the error encountered.

H2C0382 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID DB2 TABLE SPECIFIEDExplanation: OMEGAMON II detected the specification of an invalid DB2 table.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0391 OMEGAMON II/DB2 HISTORICAL FEATURE CANNOT LOCATE THE PROCESSING ROUTINE FOR KEYWORDExplanation: OMEGAMON II cannot locate the processing routine for the keyword.System Action: Processing terminates.User Response: Contact Candle Customer Support.

H2C0392 OMEGAMON II/DB2 HISTORICAL FEATURE UNABLE TO PROCESS FILTERING OPTIONS DUE TO WORK AREA TOO SMALLExplanation: OMEGAMON II cannot process filtering options because the work area was too small.System Action: Processing terminates.User Response: Contact Candle Customer Support.

H2C0393 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID TABLE NAME/SYNONYM SPECIFIED IN THIS RKD2PAR RECORD:Explanation: OMEGAMON II detected the specification of an invalid table name or synonym.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0394 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID QUALIFIER SPECIFIED IN THIS RKD2PAR RECORD:Explanation: OMEGAMON II detected the specification of an invalid qualifier.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.


H2C0395 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID FILTERING VALUE SPECIFIED IN THIS RKD2PAR RECORD:Explanation: OMEGAMON II detected the specification of an invalid filtering value.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0398 OMEGAMON II/DB2 HISTORICAL FEATURE DETECTED INVALID PARAMETER FOR KEYWORD COMMIT IN THIS RKD2PAR RECORD:Explanation: OMEGAMON II detected the specification of an invalid parameter for the COMMIT keyword. Valid options are 1–9999999.System Action: Processing terminates.User Response: Check the RKD2PAR record following this message and make the correction in the RKD2PAR member.

H2C0399 OMEGAMON/DB2 HISTORICAL FEATURE - DETECTED THAT THE REQUIRED KEYWORD DB2SYS IS NOT SPECIFIEDExplanation: OMEGAMON II detected that the DB2SYS keyword was not specified. This is required for the online collector, data summarization, and data extraction if LOAD(NO) is specified.System Action: Processing terminates.User Response: Check the keywords specified and make the necessary changes. Resubmit request.

H2C0401 OMEGAMON/DB2 HISTORICAL FEATURE - SORT OR SCAN OPTION IS SPECIFIED BUT NOT ACCOUNTING CLASSExplanation: OMEGAMON II detected that SORT or SCAN data was requested but accounting data is not being collected.System Action: Processing terminates.User Response: Check the keywords specified and make the necessary changes. Resubmit request.

H2C0402 OMEGAMON/DB2 HISTORICAL FEATURE - H2DATASET MUST BE SPECIFIED IF VSAM WRITE OPTION SELECTEDExplanation: OMEGAMON II detected that VSAM was selected as the output destination but the keyword H2DATASET was not specified.System Action: Processing terminates.User Response: Check the keywords specified and make the necessary changes. Resubmit request.

H2C0403 OMEGAMON/DB2 HISTORICAL FEATURE - WRITE OPTION OF DB2 OR VSAM IS REQUIREDExplanation: OMEGAMON II detected that an invalid value was specified for the WRITEOPTION keyword. Only DB2 or VSAM may be specified.System Action: Processing terminates.User Response: Check the keywords specified and make the necessary changes. Resubmit request.

EU001–KAO09998 29

H2C0404 OMEGAMON/DB2 HISTORICAL FEATURE - WRITEOPTION(NONE) SPECIFIED BUT NO STATISTICS DATA COLLECTEDExplanation: OMEGAMON II detected that WRITEOPTION(NONE) was specified, but statistics data was not being collected.System Action: Processing terminates.User Response: Check the keywords specified and make the necessary changes. Resubmit request.

H2C0405 OMEGAMON/DB2 HISTORICAL FEATURE - KEYWORDS DYNAMICSQL/LOCKCONT/ LOCKSUSP ARE ONLY VALID IF VSAM WRITE OPTION SELECTEDExplanation: Keywords SYNAMICSQL, LOCKCONT, and LOCKSUSP are only valid if the VSAM write option is selected.System Action: The historical collector terminates.User Response: None.

H2IN0001 DB2 aaaaaaaaaa DB2 cccc IS NOT ACTIVE. WAIT FOR ACTIVATION, OR REPLY ANOTHER DB2 ID OR REPLY STOP.Explanation: The DB2 subsystem identified by cccc is not active at this time. aaaaaaaaaa = COLLECTION, if this is the DB2 for which historical data is to be collected, or aaaaaaaaaa = INSERTION, if this is the DB2 to which the historical data is to be written.System Action: Waits for a reply from the operator and then takes the requested action.User Response: Perform one of the following actions:® Wait for the DB2 subsystem to become active and do not give a reply. This

WTOR message is automatically cancelled when the DB2 becomes active.

® Reply with the ID of another DB2 subsystem to be used in place of the inactive DB2.

® Reply STOP to terminate the attempted data collection for this DB2 subsystem.

H2IN0002 DB2 IS ALREADY BEING MONITORED, REPLY ANOTHER DB2 ID.Explanation: The historical collector has been started, and has determined that the requested DB2 subsystem is already being monitored.System Action: Waits for a reply from the operator, then takes the requested action.User Response: Review the specified options to ensure that they are correct. Then perform one of the following actions:® Stop the historical collector currently monitoring the desired DB2 subsystem

and reply GO.

® Reply with the correct DB2 subsystem ID.

® Reply STOP to terminate collection.


H2IN0003 aaaaaaaaaa DB2 cccc IS NOT VALID. REPLY ANOTHER DB2 ID OR REPLY STOP.Explanation: The DB2 identified by cccc is not valid on this system. aaaaaaaaaa = COLLECTION, if this is the DB2 subsystem for which historical data is to be collected, or aaaaaaaaaa = INSERTION, if this is the DB2 to which the historical data is to be written.System Action: Waits for a reply from the operator, and then takes requested action.User Response: Perform one of the following actions:® Wait for the DB2 subsystem to become active and do not give a reply. This

WTOR message is automatically cancelled when the DB2 becomes active.

® Reply with the ID of another DB2 subsystem to be used in place of the invalid DB2.

® Reply STOP to terminate the attempted data collection for this DB2 subsystem.

H2S0001 INITIALIZATION SUCCESSFULLY COMPLETEDExplanation: The data summarization function has successfully initialized all data areas and is continuing execution.System Action: Processing continues.User Response: None. This is an informational message only.

H2S0100 CONTROL OPTIONS SELECTED ARE AS FOLLOWSExplanation: The data summarization function displays all control options specified via the RKD2PAR DD statement in the execution JCL.System Action: Processing continues.User Response: None. This is an informational message only.

H2S0200 CONNECT COMPLETED TO DB2ID=ccccExplanation: The data summarization function has successfully established a connection with the DB2 subsystem cccc.System Action: Processing continues.User Response: None. This is an informational message only.

H2S0210 CREATE THREAD COMPLETED USING PLAN=H2cccPLNExplanation: The data summarization function has successfully established a thread to DB2 using PLAN H2cccPLN.System Action: Processing continues.User Response: None. This is an informational message only.

H2S0250 SQL STATEMENT FOR STATISTICS/ACCOUNTING TABLE HAS THE FOLLOWING MODELExplanation: The data summarization function displays a model SQL SELECT statement generated from the control options specified in the RKD2PAR DD statement in the execution JCL.System Action: Processing continues.User Response: None. This is an informational message only.

EU001–KAO09998 31

H2S0290 DB2 CONNECT FAILED, MAX CONNECTIONS HAVE BEEN REACHEDExplanation: The data summarization function was unable to successfully connect to the target DB2 subsystem because the maximum number of batch connections (IDBACK) was reached.System Action: Processing terminates.User Response: Evaluate the number of active batch connections using OMEGAMON II for DB2. If necessary increase the number of IDBACK or wait for an active background connection to terminate.

H2S0291 DB2 CONNECT FAILED, DB2 SUBSYSTEM ID SPECIFIED IS INVALIDExplanation: The data summarization function was unable locate an active DB2 subsystem matching the target DB2 subsystem name provided.System Action: Processing terminates.User Response: Determine if the job was executed on the same processor on which the DB2 subsystem normally executes. Run the job on the processor on which the target DB2 subsystem executes or correct the specified DB2 subsystem ID.

H2S0292 DB2 NOT ACTIVE OR IN PROCESS OF TERMINATINGExplanation: The data summarization function was unable to connect because DB2 is not active or DB2 termination is in progress.System Action: Processing terminates.User Response: Run the data summarization function with the target DB2 subsystem becomes available.

H2S0293 DB2 CONNECT FAILED, USER NOT AUTHORIZEDExplanation: The data summarization function was unable to connect to DB2 because the DB2 connect security in use rejected the connect request.System Action: Processing terminates.User Response: Determine the authorization ID needed to be allowed to connect to DB2. Contact the security administrator so that connect authority can be provided. Refer to the OMEGAMON II for DB2 Configuration and Customization Guide for more information.

H2S0294 DB2 CONNECT FAILED, DB2 RELEASE LEVEL MISMATCHExplanation: The data summarization function was unable to connect to DB2 due to a release level mismatch between the target DB2 subsystem and the release level of the DSNLOAD dataset concatenated to the H2 extractor STEPLIB ddname.System Action: Processing terminates.User Response: Determine the level of the target DB2 subsystem. Alter the STEPLIB concatenation to use the same level of the DSNLOAD library as the target DB2 subsystem.


H2S0295 DB2 CREATE THREAD FAILED, PLAN NOT FOUND OR NOT AUTHORIZEDExplanation: The planname H2nnnPLN (where nnn is the OMEGAMON II for DB2 version number) was not found or not authorized for use by the data summarization function.System Action: Processing terminates.User Response: Determine if the planname exists on the target DB2 subsystem. If necessary BIND the plan and grant necessary DB2 authority. Refer to the OMEGAMON II for DB2 Configuration and Customization Guide for more information on bind and authorization requirements.

H2S0296 DB2 CREATE THREAD FAILED, PLAN NOT AUTHORIZED FOR USEExplanation: The data summarization function has not been granted the required DB2 authorization to use planname H2nnnPLN (where nnn is the OMEGAMON II for DB2 version number).System Action: Processing terminates.User Response: Determine the authorization ID being used by the summarization function. Grant the necessary DB2 authority. See the OMEGAMON II for DB2 Configuration and Customization Guide for more information on DB2 authorization requirements.

H2S0551 ACCESS TO TABLE(S) DENIED, USER NOT AUTHORIZEDExplanation: User is not authorized to access table.System Action: Processing terminates.User Response: Grant user the necessary DB2 authority. See the OMEGAMON II for DB2 Configuration and Customization Guide for more information on DB2 authorization requirements.

H2S0700 DB2 TERMINATION HAS BEEN DETECTEDExplanation: The data summarization function has determined that DB2 is terminating.System Action: Processing terminates.User Response: The data summarization function can be restarted upon DB2 availability.

H2S0710 TERMINATION PROCESSING BEING ENTEREDExplanation: The data summarization function has determined that DB2 is terminating.System Action: Processing terminates.User Response: The data summarization function can be restarted upon DB2 availability.

H2S0800 END OF STATISTICS/ACCOUNTING TABLESExplanation: The data summarization function has reached the end of the historical tables. Termination processing begins at this point.System Action: Processing continues.User Response: None.

EU001–KAO09998 33

H2S0810 INSERT FAILED, TABLE NOT DEFINED TO DB2, TABLE=12345678.123456789012345678Explanation: The data summarization function has attempted to insert a row into a table that has not been defined to DB2.System Action: Processing terminates.User Response: Determine the name of the correct table to use and supply that table name in the RKD2PAR DD statement, then restart the data summarization function.

H2S0815 DBRM 123456 NOT FOUND IN KO2270HPExplanation: The data summarization function has attempted to execute SQL from a DBRM that was not included when the plan was bound.System Action: Processing terminates.User Response: Bind the online collector plan (with the REPLACE option), including all DBRMs that will be used by the online collector, the extractor, and the data summarization function.

H2S0899 SQL CALL FAILED, SQL RETURN CODE=xxxx; SQL MESSAGE AREA FOLLOWSExplanation: The data summarization function has determined that a DB2 SQL request has not completed successfully. A SNAP dump is taken for the SQL Communications Area and a user abend follows.System Action: Processing terminates with a user abend.User Response: Determine from the SQLCA SNAP DUMP the probable cause of failure. If no determination can be made, contact Candle Customer Support.

H2S0900 TERMINATION SUCCESSFULLY COMPLETEDExplanation: The data summarization function has successfully completed termination processing.System Action: The data summarization function terminates successfully.User Response: None. This is an informational message only.

H2S0904 SQL CALL FAILED, RESOURCE NOT AVAILABLEExplanation: The DB2 resource connected to OMEGAMON II for DB2 is not available.System Action: Processing terminates.User Response: Examine the specified DB2 resource for the cause of failure.

H2S0911 SQL CALL FAILED, TIMEOUT/DEADLOCK HAS OCCURREDExplanation: The SQL call failed due to a time-out or deadlock.System Action: Processing terminates.User Response: Examine the specified DB2 resource for the cause of the time-out or deadlock.


H2S1008 LOAD OF MODULE KO2MI00B HAS FAILEDExplanation: Data summarization was not able to load module KO2MI00B, because the module was not found in the STEPLIB concatenation.System Action: Processing terminates.User Response: Determine if the correct load library was specified in the JCL stream. Correct the JCL, then resubmit.

Note: The following messages are displayed as a group.

H2S1100 TABLE TYPE MISMATCH BETWEEN ACCOUNTING, ACCOUNTING DDF, AND ACCOUNTING BP TABLES

H2S1101 ACCOUNTING TABLES MUST MATCH IN TYPE, EITHER ALL DETAIL OR ALL SUMMARY

H2S1102 SPECIFY CORRECT TABLES USING ACCTTAB, ACDDFTAB, AND ACBPTAB KEYWORDS

H2S1110 ACCOUNTING SUMMARIZATION BEING BYPASSED DUE TO THE ABOVE ERRORExplanation: The detail and summary tables contain different columns in the accounting, accounting DDF, and accounting buffer pool tables. You are not allowed to use a combination of detail and summary tables as input to data summarization.System Action: Data summarization terminates accounting summarization.User Response: Specify the correct table pairs in the RKD2PAR dataset using the ACCTTAB, ACDDFTAB, and ACBPTAB keywords.

H2X0002 EOF LOCATED FOR INPUT DATASETExplanation: The end of file for the SMF dataset has been reached.System Action: Processing continues.User Response: None required. This is an informational message only.

H2X0050 DB2 CONNECT FAILED, MAX CONNECTIONS HAVE BEEN REACHEDExplanation: The historical extractor was unable to successfully connect to the target DB2 subsystem because the maximum number of batch connections (IDBACK) was reached.System Action: Processing terminates.User Response: Evaluate the number of active batch connections using OMEGAMON II for DB2. If necessary, increase the number of IDBACK or wait for an active background connection to terminate.

H2X0051 DB2 CONNECT FAILED, DB2 SUBSYSTEM ID IS INVALIDExplanation: The historical extractor was unable locate an active DB2 subsystem matching the target DB2 subsystem name provided.System Action: Processing terminates.User Response: Determine if the extractor executed on the same processor on which the DB2 subsystem normally executes. Run the historical extractor on the processor on which the target DB2 subsystem executes or correct the specified DB2 subsystem ID.

EU001–KAO09998 35

H2X0052 DB2 NOT ACTIVE OR IN PROGRESS OF TERMINATINGExplanation: The historical extractor was unable to connect because DB2 is not active or DB2 termination is in progress.System Action: Processing terminates.User Response: Run the historical extractor when the target DB2 subsystem becomes available.

H2X0053 DB2 CONNECT FAILED, USER NOT AUTHORIZEDExplanation: The historical extractor was unable to connect to DB2 because the DB2 connect security in use rejected the connect request.System Action: Processing terminates.User Response: Determine the authorization ID needed to be allowed to connect to DB2. Contact the security administrator for connect authority. Refer to the OMEGAMON II for DB2 Configuration and Customization Guide for additional information.

H2X0054 DB2 CONNECT FAILED, DB2 RELEASE LEVEL MISMATCHExplanation: The historical extractor was unable to connect to DB2 due to a release level mismatch between the target DB2 subsystem and the release level of the DSNLOAD dataset concatenated to the H2 extractor STEPLIB ddname.System Action: Processing terminates.User Response: Determine the level of the target DB2 subsystem. Alter the historical extractor STEPLIB concatenation to use the same level of the DSNLOAD library as the target DB2 subsystem.

H2X0060 DB2 CREATE THREAD FAILED, PLAN NOT FOUND OR NOT AUTHORIZEDExplanation: The historical extractor planname H2nnnPLN (where nnn is the OMEGAMON II for DB2 version number) was not found or not authorized for use by the historical extractor.System Action: Processing terminates.User Response: Determine if the planname exists on the target DB2 subsystem. If necessary BIND the plan and grant necessary DB2 authority. Refer to the OMEGAMON II for DB2 Configuration and Customization Guide for further information on bind and authorization requirements.

H2X0061 DB2 CREATE THREAD FAILED, PLAN NOT AUTHORIZED FOR USEExplanation: The historical extractor has not been granted the required DB2 authorization to use planname H2nnnPLN (where nnn is the OMEGAMON II for DB2 version number).System Action: Processing terminates.User Response: Determine the authorization ID being used by the historical extractor. Grant the necessary DB2 authority. See the OMEGAMON II for DB2 Configuration and Customization Guide for more information on historical extractor DB2 authorization requirements.


H2X0070 SMF INPUT OUT OF SEQUENCE, PROCESSING TERMINATEDExplanation: Trace records in the input dataset are out of date/time sequence.System Action: The data extractor discontinues processing. All records up to the record out of sequence have been processed.User Response: Check the datasets specified in the H2XINPUT DD card and ensure that they are specified in ascending order. Note that when using GDG datasets, if the dataset name is specified WITHOUT the generation specification, all generations will be used in DESCENDING sequence; this is the reverse order that the extractor requires. If you want to process the last six generations, specify ds(-5),ds(-4),ds(-3),ds(-2),ds(-1),ds(0).If you want to process data from different systems concurrently, or if the records are out of sequence, the dataset must be sorted before it can be used by the data extractor. rhilev.RKD2SAM(KO2JSMFS) contains a sample sort job.

H2X0074 UNSUPPORTED DB2 RECORDS FOUND nnnnnnnnExplanation: nnnnnnnn unsupported DB2 records were found in the SMF dataset. If no unsupported records were found, 00000000 will be displayed.System Action: Processing continues.User Response: None required. This is an informational message only.

H2X0080 INSERT FAILED, TABLE NOT DEFINED TO DB2, TABLE=nameExplanation: The historical extractor was unable to insert into the specified table name.System Action: Processing terminates.User Response: Determine whether the correct name has been supplied or whether the table needs to be created.User Response: If necessary, correct the table name or refer to the OMEGAMON II for DB2 Configuration and Customization Guide for information about how to create the OMEGAMON II for DB2 historical tables.

H2X0088 SQL CALL FAILED, RETURN CODE=n, SQLCA HAS BEEN SNAPPEDExplanation: The historical extractor has determined that a DB2 SQL request has not completed successfully.System Action: Processing terminates and a SNAP dump of SQLCA is taken.User Response: Refer to the IBM DB2 Messages and Codes manual to determine reason for SQL failure. If needed, locate SQLCA in the SNAP dataset.

H2X0110 NO RECORDS SATISFIED SELECTION CRITERIAExplanation: No records matched the selection criteria that were specified by the user.System Action: Processing terminates with return code 16.User Response: None required. This is an informational message only.

EU001–KAO09998 37

H2X1007 H2XINPUT DATASET SPECIFICATION INVALIDExplanation: Multiple GTF datasets were specified for H2XINPUT, but the extractor only allows a single GTF dataset. This restriction is made to allow for handling of wrapped datasets.System Action: The data extractor discontinues processing. No records are processed.User Response: Run separate extractor jobs for each dataset OR sort and merge desired datasets in date/time sequence. rhilev.RKD2SAM(KO2JGTFS) contains a sample sort job.

Note: Sort is only possible if GTF was started with the parameter TIME=YES.

IA0001 INVALID DELIMITERExplanation: The IANL command was entered with incorrect syntax.System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0002 WORKLOAD NAME MUST BE 8 CHARACTERS OR LESSExplanation: A workload name exceeding eight characters was entered.System Action: The command is commented out.User Response: Correct the workload name and re-enter the command.

IA0003 VALID FORMATS ARE:workload,LISTworkload,DELETEGROUP,LIST

Explanation: Review the appropriate explanation for your product.

System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0004 VALID FORMATS ARE:GROUP=groupnamePG=nnnn (* not applicable to OMEGAMON II for CICS)

LIST=ALLExplanation: An IANL command was entered with incorrect use of the equal sign. The correct syntax is displayed.System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

OMEGAMON II for CICS The IANL LIST or the DELETE command was entered with incorrect syntax.

All other products User entered an IANL command with incorrect usage of the comma. Correct syntax is displayed.


IA0005 PERFORMANCE GROUPS MUST BE SPECIFIED BY NUMBERExplanation: User attempted to select a performance group as a monitored workload (using the PG=performance group command) but entered a non-numeric name for the performance group. The performance group must be specified by number.System Action: Command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0006 GROUP NAMES CANNOT BE NUMERICExplanation: The user attempted to select a group workload to be monitored (using the GROUP={Groupname} command), but entered a numeric name for the group. The group workload must be specified by a non-numeric name.System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0007 VALID FORMAT FOR LIST IS: ccccccccExplanation: The IANL LIST command was entered incorrectly.System Action: The command is commented out and a model of the correct syntax is shown.User Response: Correct the syntax error and re-enter the command.

IA0008 FORMAT FOR DEFINING A GROUP IS: GROUP=Groupname=(Member1,Member2,...)Explanation: The user attempted to define a group workload, but did not use the correct syntax.System Action: The command is commented out and a model of the correct syntax is shown.User Response: Correct the syntax error and re-enter the command.

IA0009 GROUPS CANNOT CONTAIN BOTH TASK NAMES AND PG NUMBERSExplanation: The user attempted to define a group workload, but mixed task names and PG numbers in the member list.System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0010 GROUP MEMBER NAMES MUST BE 1 TO 8 CHARACTERSExplanation: The user attempted to define a group workload, but entered a member name greater than eight characters. The correct syntax is: GROUP=Groupname=(member list).System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0011 GROUP (name) IS NOT DEFINEDExplanation: The user attempted to select a group workload to be monitored (using the command IANL GROUP=Groupname), but the group has not been defined.System Action: The command is ignored.User Response: Define the group workload using the command GROUP=Groupname=(member list) and re-enter the group selection command.

EU001–KAO09998 39

IA0012 VALID PREFIXES FOR IANL COMMAND ARE:S - Summary level displayD - Detail level display

Explanation: The IANL command was entered with an invalid prefix.System Action: The command is ignored.User Response: Correct the syntax and re-enter the command.

IA0013 VALID SUFFIXES FOR IANL COMMAND ARE:P - Show impactors by Performance groupPD - Show impactors by Performance group detailed by job

Explanation: The IANL command was entered with an invalid suffix.System Action: The command is ignored.User Response: Correct the syntax and re-enter the command.

IA0014 GROUPS MUST CONTAIN AT LEAST 1 MEMBERExplanation: The user attempted to define a group workload, but did not include any members in the member list. The correct syntax is: GROUP=Groupname=(member list).System Action: The command is commented out.User Response: Correct the syntax error and re-enter the command.

IA0015 MAXIMUM NUMBER OF CONTENTION ANALYSES IS 5Explanation: The user attempted to set the number of workloads to be monitored at more than five. The maximum number of workloads to be monitored is five.System Action: The IANC command is rejected and commented out.User Response: Review the appropriate user response for your product.

IA0100 COLLECTOR HAS NOT BEEN STARTEDExplanation: Certain commands require active data collection when they are issued. Such a command was entered before data collection was started.System Action: The command is ignored.User Response: Start data collection and re-enter the command.

IA0101 COMMAND NOT VALID ONCE COLLECTOR STARTEDExplanation: Certain commands (such as IANQ, which changes the 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. Such a command was entered while data collection was active.System Action: The command is ignored.User Response: Stop data collection and re-enter the command.

OMEGAMON II for CICS Enter a number from 1 to 5.

All other products None.


IA0102 ENTRY NOT FOUNDExplanation: The IANL LIST or DELETE command was entered for a workload that was not being monitored.System Action: The command is ignored and commented out.User Response: Correct the workload name and re-enter the command.

IA0103 NO ROOM IN TABLE TO ADD ENTRYExplanation: The user attempted to start monitoring a workload and exceeded the maximum number of workloads that can be monitored.System Action: The command is ignored.User Response: Delete a workload from monitoring or increase the maximum number of workloads with the IANC command.

IA0104 COLLECTOR HAS ABENDEDExplanation: The collector module has abended, and therefore the workloads under analysis are no longer being monitored.System Action: Diagnostic information is displayed.User Response: Log the diagnostic information; issue the.MOD command and log the additional diagnostic information; exit using the IANL END command; contact Candle Customer Support. For a definition of the user ABEND codes, see the EB, EP, and EU Abend Codes appendix.

IA0105 JOB HAS ENDEDExplanation: Review the appropriate explanation for your product.

System Action: The command is commented out.User Response: None.

IA0107 NO CONTENTION TO REPORTExplanation: Review the appropriate explanation for your product.

System Action: None.User Response: Retry the request later, after enough data has been collected.

OMEGAMON II for CICS Impact analysis (OMEGAMON II for DB2) is not monitoring the workload because the workload is no longer running.

All other products Monitoring of the workload has stopped because the workload is no longer running.

OMEGAMON II for CICS OMEGAMON II for DB2 continues to monitor the workload, but not enough contention data has been collected to form a display.

All other products Monitoring of the workload is continuing, but not enough contention data has been collected to form a display.

EU001–KAO09998 41

IA0109 NO MORE THAN 5 SHORT TERM INTERVALS PER LONG TERM INTERVALExplanation: The user attempted to define the long-term interval but entered a number larger than five.System Action: The IACL command is rejected.User Response: Correct the entry and re-enter the command.

IA0110 JOB IS NOT A CICS REGIONExplanation: The monitoring of a job was requested for a region that is not in CICS.System Action: The command is ignored.User Response: Re-enter the command with a CICS job.

IA0111 AT LEAST ONE MEMBER IS NOT A CICS REGIONExplanation: The group was monitored, but one or more group members may be incorrect.System Action: None.User Response: Verify that all group members are correct.

IA0112 INTERNAL ERROR IN CVAL ROUTINEExplanation: This message is the result of an internal error or the corruption of virtual storage.System Action: OMEGAMON II for DB2 attempts to continue command processing.User Response: Contact Candle Support Services.

IA0113 MAXIMUM VALUE IS 10Explanation: The user attempted to set the value of the enqueue sampling interval (which is defined by multiples of the normal sampling interval) but entered a value greater than 10. (Such values result in a sampling interval that is too infrequent to be significant.) The maximum number of intervals is 10.System Action: The IANQ command is rejected and commented out.User Response: Correct the entry and re-enter the command.

IA0200 COLLECTOR HAS ENDEDExplanation: The data collector stopped in response to a user command.System Action: Review the appropriate system action for your product.

User Response: This is an informational message only.

IA0201 WORKLOAD HAS BEEN ADDEDExplanation: Monitoring of the workload has begun.System Action: None.User Response: This is an informational message only.

OMEGAMON II for CICS OMEGAMON II for DB2 processes the command, and comments it out.

All other products Command is accepted and commented out.


IA0202 WORKLOAD HAS BEEN DELETEDExplanation: The workload has been deleted in response to a user command.System Action: Review the appropriate system action for your product.

User Response: None.

IA0203 LONG TERM DISPLAY WILL REPRESENT nn SHORT-TERM INTERVALSExplanation: Informs the user of the long term interval.System Action: The IACL command is accepted and commented out.User Response: This is an informational message only.

IA0204 SHORT TERM DISPLAY WILL BE CLEARED EVERY nn MINUTESExplanation: Informs the user of the short-term interval.System Action: The IACS command is accepted and commented out.User Response: This is an informational message only.

IA0205 THE DATA COLLECTOR SAMPLE TIME = n.n SECONDSExplanation: Informs the user of the sampling interval (in seconds).System Action: The IAST command is accepted and commented out.User Response: This is an informational message only.

IA0206 PLOT PERCENTAGE THRESHOLD IS nn%Explanation: Informs the user of the plot threshold. (Contending workloads comprising less than nn% of the contention will not be displayed).System Action: The command is accepted.User Response: This is an informational message only.

IA0207 IA TO SUPPORT UP TO n CONTENTION ANALYSESExplanation: Informs the user of the maximum number of workloads that can be monitored.System Action: The IANC command is accepted and commented out.User Response: This is an informational message only.

IA0208 ENQUEUE DATA COLLECTION ENABLED/DISABLED {CYCLE = nn}Explanation: Informs the user whether enqueue data collection is enabled or disabled. If enqueue collection is enabled, the message also shows the frequency with which enqueue data is collected (as a multiple of sampling intervals).System Action: The IANQ command is accepted and commented out.User Response: This is an informational message only.

IA0209 GROUP HAS BEEN DEFINEDExplanation: The user successfully defined a group workload.System Action: The command is commented out.User Response: This is an informational message only.

OMEGAMON II for CICS OMEGAMON II for DB2 processes the command, and comments it out.

All other products Command is accepted and commented out.

EU001–KAO09998 43

IA0215 NO WORKLOADS UNDER ANALYSISExplanation: The user entered the IANL LIST=ALL command but all workloads have been deleted from analysis. (The collector is still running.)System Action: None.User Response: This is an informational message only.

IA0216 NO GROUPS ARE DEFINEDExplanation: The user entered the command IANL GROUP,LIST but no group workloads have been defined. (The collector is still running.)System Action: None.User Response: Review the appropriate user response for your product.

IA0217 IA COLLECTION TASK TIMES OUT AFTER n MINUTESExplanation: Informs the user of the current time-out interval. If the time-out facility has been turned off, the message is IA COLLECTION TASK WILL NOT TIME OUT.System Action: The IATO command is accepted. User Response: None.

IA0301 PERFORMANCE GROUP OPERANDS UNACCEPTABLE IN GOAL MODEExplanation: Performance group information is not available under the Work Load Manager goal mode.System Action: The command terminates.User Response: None.

ICFCC001 I/CF VECTOR TABLE NOT FOUND.Explanation: I/CF could not initialize.System Action: The system does not create the I/CF console.User Response: Review the RLVLOG for other error messages.

ICFCC002 I/CF IN SHUTDOWN MODEExplanation: Someone has started to shutdown the CUA address space while attempting to define an I/CF console.System Action: The CUA address space will shut down.User Response: None.

ICFCC003 I/CF CONSOLE ALLOCATION FAILURE. SIZE= ########Explanation: Unable to obtain storage for the console definition. This occurs when trying to acquire 1600 bytes of extended private storage.System Action: The system does not create the I/CF console.User Response: Restart the job with a larger region size.

OMEGAMON II for CICS Define the workloads and restart.

All other products None.


ICFCC007 I/CF UNABLE TO CREATE VIEW QUEUE FOR CONSOLE xxxxxxxxExplanation: An internal error occurred while trying to create a viewable console.System Action: I/CF console is not viewable.User Response: Contact the Candle Support Services

ICFCC009 I/CF UNABLE TO CREATE LOG QUEUE FOR CONSOLE xxxxxxxxExplanation: The system specified logging, but an internal error occurred.System Action: Logging is not available for the I/CF console.User Response: Contact the Candle Support Services

ICFCC039 I/CF ICFCONSL COMMAND FORMAT ERRORExplanation: This is a user definition error.System Action: The system does not create the I/CF console.User Response: Review the I/CF console definition and correct any errors. Resubmit.

ICFCC041 I/CF DATASET LOGGING REQUIRES LOGDSN1 AND LOGDSN2 DATASETS BE DEFINED.Explanation: You specified dataset logging, but did not define either LOGDSN1 or LOGDSN2.System Action: The system does not create the I/CF console.User Response: Verify the LOGDSN1 and LOGDSN2 dataset definition. Resubmit.

ICFCC042 I/CF DATASET LOGGING REQUIRES LOGARCH1 AND LOGARCH2 ARCHIVING JOBS BE DEFINED.Explanation: You specified dataset logging, but did not define either LOGARCH1 or LOGARCH2 (archiving jobs).System Action: The system does not create the I/CF console.User Response: Verify the LOGARCH1 and LOGARCH2 archiving jobs definition. Resubmit.

ICFCC044 I/CF REQUIRES IMSID OR ACBNAMEExplanation: You did not specify either the IMSID or the ACB name.System Action: The system does not create the I/CF console.User Response: Specify the IMSID or the ACB name. Resubmit.

ICFCC047 I/CF REQUIRES IMS VTAM APPLIDExplanation: The system did not find the VTAM APPLID.System Action: The system does not create an I/CF console.User Response: Specify the VTAM APPLID and resubmit.

ICFCC089 I/CF UNABLE TO CREATE COMMAND QUEUE FOR CONSOLE xxxxxxxxExplanation: The system defined the console as a Master, but an internal error occurred.System Action: The system does not accept commands from the I/CF console.User Response: Contact the Candle Support Services.

EU001–KAO09998 45

ICFCQ004 I/CF NO MVS COMMAND ENTERED.Explanation: MVS command prefix of "-" is entered and no MVS command follows.System Action: This is an informational message.User Response: Reissue the command with a valid MVS console command.

ICFIM001 I/CF VECTOR TABLE NOT FOUND.Explanation: I/CF could not initialize.System Action: The system does not create the I/CF consoles.User Response: Review the rLVLOG for other error messages.

ICFIM002 I2DC VECTOR TABLE NOT FOUND.Explanation: I2DC could not initialize.System Action: Subsystem interface is not available. DBCTL I/CF consoles will not be created. MVS responses will not be provided.User Response: Review the RLVLOG for other error messages.

ICFIM020 IMS CONTROL REGION FOR IMSID zzzzzzz IS NOT FOUND OR IMS SCD NOT VALIDExplanation: The IMS subsystem is not active.System Action: I/CF attempts to connect to IMS at 10 second intervals until it is successful.User Response: Investigate why IMS is not active.

ICFIM024 I/CF WILL NOT PROVIDE ANY CONSOLE FOR xxxxxxxxExplanation: This is an informational message xxxxxxxx is the console ACB name.System Action: The system did not create the specified I/CF console.User Response: Review the RLVLOG for other error messages.

ICFIM095 I/CF WILL RETRY EVERY 10 SECONDSExplanation: I/CF is not connected to the IMS subsystem.System Action: I/CF attempts to connect to IMS at 10 second intervals until it is successful.User Response: Investigate why IMS is not active.

ICFJB001 I/CF VECTOR TABLE NOT FOUND.Explanation: I/CF could not initialize.System Action: The system does not create the I/CF consoles.User Response: Review the RLVLOG for other error messages.

ICFJB002 I2DC VECTOR TABLE NOT FOUND.Explanation: I2DC could not initialize.System Action: Subsystem interface is not available. DBCTL I/CF consoles will not be created. MVS responses will not be provided.User Response: Review the RLVLOG for other error messages.


ICFJB020 JOB ADDRESS SPACE FOR zzzzzzzz IS NOT FOUND.Explanation: The system did not start the job.System Action: I/CF attempts to connect to the address space at 10 second intervals until successfully connected.User Response: Investigate why the system did not start the job.

ICFJB024 I/CF WILL NOT PROVIDE ANY CONSOLE FOR xxxxxxxxExplanation: This is an informational message xxxxxxxx is the console ACB name.System Action: The system did not create the specified I/CF console.User Response: Review the RLVLOG for other error messages.

ICFJB038 I/CF JOB zzzzzzzz CONSOLE IS UNABLE TO START. NO SYSTEM BLOCKS AVAILABLE.Explanation: The system defined more than 16 I/CF consoles to the CUA address space zzzzzzzz is the job name.System Action: The system does not create DBCTL I/CF consoles nor does it provide MVS responses.User Response: Contact Candle Support Services

ICFJB095 I/CF WILL RETRY EVERY 10 SECONDSExplanation: I/CF is not connected to the address space.System Action: I/CF attempts to connect to the address space at 10 second intervals until successfully connected.User Response: Investigate why the system did not start the job.

ICFSC005 I/CF COMMAND NOT PROCESSED. CONSOLE xxxxxxxx IS NOT ACTIVE.Explanation: You issued the command to an inactive console.System Action: The system does not execute the command.User Response: Investigate why the console is not active.

ICFSC016 COMMAND CHARACTER (X) NOT RECOGNIZED. VALID CHARACTERS ARE (/) = IMS, (.) = VTAM, (-) = MVS.Explanation: You entered an invalid command character.System Action: The system does not execute the command.User Response: Select the appropriate command character. Re-issue the command.

ICFSC017 COMMAND AUTHORIZATION FOR USER xxxxxxxx FAILED.Explanation: You are not authorized to issue the command you entered xxxxxxxx is the userid.System Action: The system does not execute the command.User Response: Contact your system administrator to gain the appropriate authorization.

EU001–KAO09998 47

ICFSC018 cccccccc COMMAND AUTHORIZATION FOR USER xxxxxxxx FAILED.Explanation: You are not authorized to issue the ICF command you entered. xxxxxxxx is the userid.System Action: The system does not execute the command.User Response: Contact your system administrator to gain the appropriate authorization.

ICFSC117 COMMAND ENTRY NOT AVAILABLE FOR THIS CONSOLEExplanation: You cannot enter commands from this console. You can only enter commands from an I/CF Master Console.System Action: The system does not execute the command.User Response: None

ICFSF001 I/CF VECTOR TABLE NOT FOUND.Explanation: I/CF could not initialize.System Action: The system does not create the I/CF consoles.User Response: Review the RLVLOG for other error messages.

ICFSF121 I/CF UNABLE TO OBTAIN COMMAND ENTRY VALIDATION STORAGE. COMMAND FAILED. CCB ADDRESS = yyyyyyyyExplanation: The system could not get 56 bytes of extended private storage for an internal command validation control block.System Action: The system does not validate the command. Command authorization fails.User Response: Restart the address space with a larger region size.

ICFVR001 I/CF VECTOR TABLE NOT FOUND.Explanation: I/CF could not initialize.System Action: The system does not create I/CF consoles.User Response: Review RLVLOG for other error messages.

ICFVR003 I/CF VTAM RECEIVE PROCESSING STARTED FOR CONSOLE xxxxxxxx CCB ADDRESS yyyyyyyyExplanation: This is an informational message xxxxxxxx is the console ACB name yyyyyyyy is the CCB address.System Action: NoneUser Response: None

ICFVR005 I/CF VTAM RECEIVE PROCESSING TERMINATED FOR CONSOLE xxxxxxxx CCB ADDRESS yyyyyyyyExplanation: This is an informational message xxxxxxxx is the console ACB name yyyyyyyy is the CCB address.System Action: I/CF console is put in a waiting status. I/CF attempts to reconnect to IMS.User Response: Investigate the cause of the disconnection.


ICFWT001 I/CF VECTOR TABLE NOT FOUND.Explanation: I/CF could not initialize.System Action: The system does not create I/CF consoles.User Response: Review the RLVLOG for other error messages.

ICFWT002 I2DC VECTOR TABLE NOT FOUND.Explanation: I2DC could not initialize.System Action: Subsystem interface is not available. DBCTL I/CF consoles will not be created. MVS responses will not be provided.User Response: Review the RLVLOG for other error messages.

ICFWT003 I/CF WTO RECEIVE PROCESSING STARTED FOR CONSOLE xxxxxxxx CCB ADDRESS yyyyyyyyExplanation: This is an informational message xxxxxxxx is the console ACB name yyyyyyyy is the CCB address.System Action: None.User Response: None.

ICFWT005 I/CF WTO RECEIVE PROCESSING TERMINATED FOR CONSOLE xxxxxxxx CCB ADDRESS yyyyyyyyExplanation: This is an informational message xxxxxxxx is the console ACB name yyyyyyyy is the CCB address.System Action: I/CF console is put in a pending status. I/CF attempts to reconnect to IMS.User Response: Investigate the cause of the disconnection.

IN0004 THE KEYWORD FLAGGED ABOVE IS UNKNOWN Explanation: A keyword operand was misspelled or is not valid on this command.System Action: The command does not execute.User Response: Correct the command and re-enter.

IN0005 PARAMETER WAS EXPECTED BUT NOT FOUNDExplanation: A keyword with a parameter list was specified, but the parameter list did not contain enough parameters.System Action: The command does not execute.User Response: Correct the command and re-enter.

IN0006 THIS PARAMETER MUST BE NUMERICExplanation: A parameter was specified which must be numeric but is not.System Action: The command does not execute.User Response: Correct the command and re-enter.

IN0007 ‘)’ MISSING AFTER FIRST PARAMETERExplanation: A ‘)’ was expected after the first parameter and was not found.System Action: The command does not execute.User Response: Correct the command format and retry.

EU001–KAO09998 49

IN0050 datasetname FAILED TO ALLOCATEExplanation: An error occurred during dynamic allocation of the dataset name specified in the MLIB DSN list.System Action: The command continues if there are other dataset names in the MLIB DSN list.User Response: Check the reason for the dynamic allocation error and correct accordingly. Message IN0051 might accompany this message.

IN0051 DAIR CODE = rcExplanation: The Dynamic Allocation Interface Routine (DAIR) return code is displayed.System Action: Same as message IN0050.User Response: Same as message IN0050.

IN0060 datasetname FAILS MLIB REQUIREMENTSExplanation: The dataset failed the MLIB requirement because it neither has a Format 1 DSCB nor is in a load module format. Message IN0061 or IN0062 gives more information on the error.System Action: The command continues if there are other dataset names in the MLIB DSN list.User Response: Make sure the right dataset name was specified.

IN0061 DATASET IS NOT LOAD MODULE FORMATExplanation: The MLIB failure was due to the dataset not being in a load module format.System Action: The command continues if there are other dataset names in the MLIB DSN list.User Response: Only load datasets can be specified on the MLIB command.

IN0062 FORMAT1 DSCB COULD NOT BE LOCATEDExplanation: The dataset specified in message IN0060 was not found.System Action: The command continues if there are other dataset names in the MLIB DSN list.User Response: Make sure that the dataset exists on the volume as indicated by the system catalog and retry the command.

IN0070 datasetname FAILED TO OPENExplanation: The OPEN failed for the dataset.System Action: The command continues if there are other dataset names in the MLIB DSN list.User Response: Make sure that OMEGAMON is authorized to use the specified dataset.

IN0080 datasetname IS NOT OPENExplanation: OMEGAMON tried to close a dataset that was not open.System Action: CLOSE processing continues for remaining datasets.User Response: Call Candle Customer Support for assistance.


IN0081 datasetname FAILED TO CLOSEExplanation: The dataset cannot be closed.System Action: CLOSE processing continues for the remaining datasets.User Response: Investigate why the dataset failed to close. If necessary, call Candle Customer Support for assistance.

IN0082 datasetname FAILED TO DE-ALLOCATEExplanation: The dataset cannot be de-allocated.System Action: Deallocate processing continues for remaining datasets.User Response: Investigate why the dataset failed to de-allocate by examining the accompanying DAIR code in message IN0083.

IN0083 DAIR CODE = rc Explanation: The Dynamic Allocation Interface Routine (DAIR) return code is displayed with message IN0082.System Action: See message IN0082.User Response: Refer to the appropriate IBM manual for a description of the return codes.

IN0090 ADD AND DEL MUST NOT BE ISSUED TOGETHERExplanation: The ADD and DEL parameters cannot be issued together in the same MLIB command.System Action: The commands do not execute.User Response: Issue ADD and DEL separately.

IN0091 datasetname IS NOT IN THE MLIB DSN LISTExplanation: The dataset specified with the delete option of the MLIB minor of INSP was not found in the MLIB list because it was never added or was already deleted.System Action: The operation is ignored.User Response: Specify the correct dataset name for the delete.

IN0092 PREVIOUS LINE WAS TRUNCATEDExplanation: The previous display line has been truncated because the line length was exceeded.System Action: None.User Response: None.

IN0100 ccccccc HAS A HIGHER PRIORITY THAN OMEGAMONExplanation: The address space dispatching priority of job ccccccc, which is being monitored by INSP, is running at a higher priority than OMEGAMON. This is the jobname specified by the JOB( ) keyword.System Action: INSP attempts to take samples, but will probably detect very little activity in the monitored address space. Any results are incorrect.User Response: Run OMEGAMON as a performance group which has a higher priority than the address space being monitored.

EU001–KAO09998 51

IN0101 ccccccc IS NO LONGER RUNNINGExplanation: INSP was monitoring an address space when the jobname ccccccc changed. ccccccc is the name specified by the JOB( ) keyword.System Action: Sampling terminates.User Response: If you want more data, rerun the job and use a shorter sampling period.

IN0102 START INVALID, ALREADY SAMPLINGExplanation: The START keyword was specified on the INSP command when sampling of the target address space was already in progress.System Action: The START keyword is ignored.User Response: None required.

IN0103 STOP INVALID, NOT SAMPLINGExplanation: The STOP keyword was specified on the INSP command when sampling of the target address space was not in progress.System Action: The STOP keyword is ignored.User Response: None required.

IN0104 ATTACH FAILEDExplanation: This is an internal error message.System Action: Sampling does not start.User Response: Call Candle Customer Support for assistance.

IN0105 ccccccc NOT FOUNDExplanation: No job with the name ccccccc specified is currently active. <jobname> is the name specified by the JOB( ) keyword.System Action: The new jobname specification is not used.User Response: Use the JOB( ) keyword to specify the name of a running job. If necessary, use OMEGAMON commands such as ALLJ to determine a valid jobname.

IN0106 SAMPLER TASK HAS ABENDEDExplanation: This is an internal error message.System Action: Sampling terminates and diagnostic information appears. User Response: Record the diagnostic information and call Candle Customer Support.

IN0900 $GMEM FAILED FOR INSP WORKAREAExplanation: OMEGAMON was unable to obtain memory for the INSP workarea.System Action: The command does not execute.User Response: Increase the OMEGAMON region size to correct the problem.

IN0901 RETURN CODE rc FROM OMPBM INITIALIZATIONExplanation: An error occurred during INSP initialization.System Action: The command does not execute.User Response: Call Candle Customer Support for assistance.


IN0902 INSPECT REQUIRES DEXANExplanation: To run INSP, the DEXAN® product is required.System Action: The command does not execute.User Response: None.

IN0903 LOAD MACRO FAILED FOR OMPBM WITH ABEND=nnnExplanation: INSP module OMPBM could not be loaded.System Action: The command does not execute.User Response: Refer to the IBM system codes manual for an explanation of the abend code.

IN0904 INSPECT ERROR CODE nnExplanation: An internal error occurred on the INSP command. The error code is nn.System Action: The command does not execute.User Response: Call Candle Customer Support for assistance.

KAM0000I KAM STARTINGExplanation: This informational message is issued to indicate that the alert adapter has been started.System Action: Alert adapter initialization proceeds.User Response: None.

KAM0001I SUBSYS=subsys SYSNAME=sysname SLUAPPLID=sluapplidExplanation: This informational message is issued to indicate that an AF/OPERATOR (AO) or OMEGACENTER Gateway (OG) subsystem has successfully established a connection to the alert adapter. The subsystem ID of the AO or OG address space is specified by subsys. The system name on which the AO or OG address space is executing is specified by sysname. The secondary logical unit application ID used by the AO or OG connection is specified by sluapplid.System Action: An alert adapter and alert emitter are registered with the CMS for the AO or OG subsystem.User Response: None.

KAM0010S INVALID ARGUMENTS. SYNTAX: IRAMAN KAM START PLUAPPLIDExplanation: This severe error message is issued when an incorrectly formatted IRAMAN command is found in the hilev.rte.RKANCMD(KAMAGST) member.System Action: The alert adapter startup is aborted.User Response: Use the Candle installation software, CICAT, to correctly configure the alert adapter runtime parameters. Avoid manually changing the startup command unless directed by Candle Customer Support.

EU001–KAO09998 53

KAM0020E IPC CREATE QUEUE ERROR=rcExplanation: This error message is issued when an attempt to inter-process the communication queue for an alert adapter has failed. The return code from the IPC queue create service is specified by rc.System Action: The alert adapter startup is aborted.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0030E UNABLE TO START KAM EVENT THREAD ERROR=rcExplanation: This error message is issued when an attempt to start a long running thread to listen for console events has failed to start. The return code for the thread creation service call is specified by rc.System Action: The alert adapter startup is aborted.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0100S UNABLE TO REGISTER PLUAPPLID=pluapplid RC=rcExplanation: This error message is issued when an attempt to register and open the primary logical unit (PLU) for the alert adapter has failed. The PLU APPLID is specified by pluapplid. The return code from the PLU APPLID registration service is specified by rc. A PLU application ID (PLU APPLID) must have been predefined with VTAM for the register and open operation to succeed.System Action: The alert adapter startup is aborted.User Response: Ensure that a valid PLU APPLID has been defined and varied active. A sample major node name in the hilev.rte.RKANSAM dataset is created by the Candle installation software, CICAT. Ensure that the major node is copied to SYS1.VTAMLST and the major node varied active before the alert adapter is started.

KAM0101I IPC DEQUEUE ERROR=rcExplanation: This informational message is issued when an attempt to read a message from an inter-process communication queue has failed. The return code from the IPC queue dequeue service is specified by rc.System Action: The alert adapter assumes an end of queue condition and assumes a shutdown of the alert adapter has been initiated. The alert adapter proceeds to terminate.User Response: None.

KAM0102W INVALID IPC MESSAGE TYPE RECEIVED=msgtypeExplanation: This warning message is issued when an invalid inter-process queue message is read. The invalid message type is specified by msgtype.System Action: The alert adapter ignores the message and continues to process other messages from the inter-process queue.User Response: This is a recoverable error condition. If this message continues to be issued, collect the messages from the RKLVLOG and contact Candle Customer Support.


KAM0103W INVALID IPC MESSAGE RECEIVED SIZE=size VERIFY=vidExplanation: This warning message is issued when an invalid length inter-process message is read. The invalid message size in number of bytes is specified by size. The verification indicator is specified by vid, which is invalid if it is non-zero.System Action: The alert adapter ignores the message and continues to process other messages from the inter-process queue.User Response: This is a recoverable error condition. If this message continues to be issued, collect the messages from the RKLVLOG and contact Candle Customer Support.

KAM0106E UNABLE TO ALLOCATE LOGICAL RESOURCEExplanation: This error message is issued when an attempt to acquire a global address space lock has failed.System Action: The alert adapter startup is aborted.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0110E UNABLE TO REGISTER ALERT ADAPTER=aaname RC=rcExplanation: This error message is issued when an attempt to register an OG/MVS session with the Candle Management Server (CMS) has failed. The name of the managed system to be registered is specified by aaname in the form subsysid:smfid:OGAlerts. The return code from the registration operation is specified by rc.System Action: The alert adapter registration is aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0111E UNABLE TO REGISTER ALERT EMITTER=aename RC=rcExplanation: This error message is issued when an attempt to register an OG/MVS session with the Candle Management Server (CMS) has failed. The name of the managed system to be registered is specified by aename in the form subsysid:smfid:OGActions. The return code from the registration operation is specified by rc.System Action: The alert emitter registration is aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0112E UNABLE TO SEND REGISTER REQUEST TO PROXY RC=%ldExplanation: This error message is issued when an attempt to register an OG/MVS session with the Candle Management Server (CMS) has failed. The return code from the registration send operation is specified by rc.System Action: The alert adapter and emitter registration requests are aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

EU001–KAO09998 55

KAM0120E UNABLE TO DEREGISTER ALERT ADAPTER=aaname RC=rcExplanation: This error message is issued when an attempt to deregister an OG/MVS session with the Candle Management Server (CMS) has failed. The name of the managed system to be deregistered is specified by aaname in the form subsysid:smfid:OGAlerts. The return code from the deregistration operation is specified by rc.System Action: The alert adapter deregistration is aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0121E UNABLE TO DEREGISTER ALERT EMITTER=%s RC=%ldExplanation: This error message is issued when an attempt to deregister an OG/MVS session with the Candle Management Server (CMS) has failed. The name of the managed system to be deregistered is specified by aename in the form subsysid:smfid:OGActions. The return code from the deregistration operation is specified by rc.System Action: The alert emitter deregistration is aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0122E UNABLE TO SEND DEREGISTER REQUEST TO PROXY RC=rcExplanation: This error message is issued when an attempt to deregister an OG/MVS session with the Candle Management Server (CMS) has failed. The return code from the registration send operation is specified by rc.System Action: The alert adapter and emitter deregistration requests are aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0130I IPC DEQUEUE STATUS=Rc BUF=Buf BUFL=Bufl MSG=MsgtypeExplanation: This informational message is issued when tracing has been enabled. A read operation on an inter-process message queue completed. Rc specifies the return code of the operation. Buf specifies the address of the input buffer. Bufl specifies the length of the message read. Msgtype specifies the message identifier.System Action: The alert adapter execution continues.User Response: None.

KAM0140I FOUND SUBNODE=subnode IPCHDL=lrhdlExplanation: This informational message is issued when tracing has been enabled. A search operation has found a subnode from the internal list of active subnodes for the agent. The subnode name is specified by subnode. The logical resource handle return by the search is specified by lrhdl.System Action: The alert adapter execution continues.User Response: None.


KAM0150E UNABLE TO REDISTRIBUTE SITUATIONS TO subnode RC=rcExplanation: This error message is issued when an attempt to distribute a situation to a newly arrived subnode has failed. The name of subnode is specified by sitname. The return code from the failed situation distribution operation is specified by rc.System Action: The alert emitter registration is aborted and the session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0200I LU0 SESSION SLUAPPLID=sluapplid STARTINGExplanation: This informational message is issued when a new LU0 session with an OG/MVS subsystem is established. The secondary logical unit application identifier of the OG/MVS subsystem is specified by sluapplid.System Action: The alert adapter execution continues.User Response: None.

KAM0201E UNABLE TO ALLOCATE OG PARMSExplanation: This error message is issued when an attempt to allocate a control block for a new OG/MVS session has failed.System Action: The LU0 session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0202S ALERT ADAPTER NOT ACTIVE. IPC SEND RC=rcExplanation: This severe error message is issued when an send an inter-process registration request message has failed for a new OG/MVS LU0 session. The return code issued by the failing IPC send operation is specified by rc.System Action: The LU0 session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0203I USERDATA=udataExplanation: This informational message is issued when tracing has been enabled. A new LU0 session with an OG/MVS subsystem has started. The userdata parameter passed during the session logon operation is specified by udata.System Action: The alert adapter execution continues.User Response: None.

KAM0204E INVALID USERDATA OPTION “badparm”Explanation: This error message is issued when an unknown parameter is found in the userdata passed by OG/MVS during session logon. The bad parameter is specified by badparm.System Action: The LU0 session with OG/MVS is terminated.User Response: Ensure that the proper REXX exec is used to establish the LU0 session between OG/MVS and the alert adapter.

EU001–KAO09998 57

KAM0205E MISSING reqparm IN USERDATAExplanation: This error message is issued when a required parameter is not found in the userdata passed by OG/MVS during session logon. The missing parameter is specified by reqparm.System Action: The LU0 session with OG/MVS is terminated.User Response: Ensure that the proper REXX exec is used to establish the LU0 session between OG/MVS and the alert adapter.

KAM0206E MAINTENANCE LEVEL MISMATCH: OGLVL=oglvl AMLVL=amlvlExplanation: This error message is issued when a maintenance mismatch between OG/MVS and the alert adapter has been detected. The mismatched levels of maintenance are specified by oglvl and amlvl.System Action: The LU0 session with OG/MVS is terminated.User Response: Ensure that the proper REXX exec is used to establish the LU0 session between OG/MVS and the alert adapter.

KAM0207I SUBSYS=subsys SYSNAME=Sysname RUSIZE=rusize MATCHNO=matchno MAINTLVL=MainlvlExplanation: This informational message is issued when tracing has been enabled. A new LU0 session with an OG/MVS subsystem has started. The parameters parsed from the userdata specified in the LU0 session logon are dumped by this message. Subsys is the OG/MVS subsystem ID. Sysname is the system name where the OG/MVS subsystem originates. rusize is the maximum LU0 packet size acceptable by OG/MVS. matchno specifies the match number (OG/MVS thread ID) which issued the LU0 logon request. Maintlvl is the maintenance level reported by OG/MVS at LU0 session logon.System Action: The alert adapter execution continues.User Response: None.

KAM0208E UNABLE TO CREATE IPC QUEUE FOR SUBNODE ERROR=rcExplanation: This error message is issued when an attempt to create an inter-process message queue for a new OG/MVS session has failed. The return code from the IPC message queue create operation is specified by rc.System Action: The LU0 session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0209E UNABLE TO ALLOCATE msgtype SUBNODE MSGExplanation: This error message is issued when an attempt to create an inter-process message has failed. The message type that failed is indicated by msgtype.System Action: The LU0 session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.


KAM0210I INBOUND LU0 PACKET (STATUS=rc)Explanation: This informational message is issued when tracing has been enabled. A new packet has been received from an LU0 session with an OG/MVS subsystem. The return code issued by the receive operation is specified by rc.System Action: The alert adapter execution continues.User Response: None.

KAM0213I USERDATA BUF=buf USERDATA LEN=buflExplanation: This informational message is issued when tracing has been enabled. A new LU0 session with an OG/MVS subsystem has started. The address of the buffer containing the userdata parms is specified by buf. The length of the data in the buffer is specified by bufl.System Action: The alert adapter execution continues.User Response: None.

KAM0218E SUBNODE FOR SUBSYS= subsys SYSNAME=sysname ALREADY ONLINEExplanation: This error message is issued when an attempt to create a new inter-process message queue has determined that the queue already exists. This indicates that new subnode for the OG/MVS is already active and an attempt to start a redundant session to the same OG/MVS subsystem was made. The name of the OG/MVS subsystem is specified by subsys. The MVS system name on which the OG/MVS subsystem originates is specified by sysname.System Action: The redundant LU0 session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0220E INVALID LU0 PACKET SEQUENCE NUMBER=seqno EXPECT=expectedExplanation: This error message is issued when an invalid sequence number is received in a packet from an LU0 session with OG/MVS. The sequence number received is specified by seqno. The expected sequence number is specified by expected.System Action: The LU0 packet is ignored and the LU0 session with OG/MVS is terminated.User Response: Ensure that the proper startup routines are used to establish the LU0 session from OG/MVS. Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0230E INVALID FORMAT LU PACKET LENGTH=lenExplanation: This error message is issued when an invalid length message is received in a packet from an LU0 session with OG/MVS. The invalid length in bytes is specified by len.System Action: The LU0 packet is ignored and the LU0 session with OG/MVS is terminated.User Response: Ensure that the proper startup routines are used to establish the LU0 session from OG/MVS. Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

EU001–KAO09998 59

KAM0240E INVALID LU0 PACKET HEADER LENGTH=lenExplanation: This error message is issued when an incorrectly formatted message is received in a packet from an LU0 session with OG/MVS. The packet header length in bytes is specified by len.System Action: The LU0 packet is ignored and the LU0 session with OG/MVS is terminated.User Response: Ensure that the proper startup routines are used to establish the LU0 session from OG/MVS. Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0250E UNABLE TO START OGSENDER THREAD ERROR=rcExplanation: This error message is issued when an attempt to create an LU0 session thread has failed to start. The return code from the thread create operation is specified by rc.System Action: The LU0 session with OG/MVS is terminated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0260I LU0 SESSION SHUTDOWN REQUESTEDExplanation: This informational message is issued when tracing has been enabled. A session shutdown has been requested by either an alert adapter shutdown or a subnode registration failure.System Action: The LU0 session between the alert adapter and OG/MVS is terminated.User Response: None.

KAM0270W ALERT EMITTER NOT ACTIVE. IPC SEND RC=rcExplanation: This warning message is issued when an attempt to send an inter-process alert emitter event message to an OG/MVS LU0 session has failed. The return code from the send operation is specified by rc. This error can occur when alert emitter events are raised during LU0 session termination or alert adapter shutdown.System Action: The deliver of the alert emitter event is aborted and normal processing continues.User Response: None.

KAM0280E UNABLE TO ALLOCATE msgExplanation: This error message is issued when an attempt to allocate and initialize a control block fails in response to an event arriving from OG/MVS. The name of the control block is specified by msg. This error can occur when virtual storage is constrained.System Action: The alert adapter ignores the event from OG/MVS and continues execution.User Response: Determine why virtual storage is constrained and relieve the condition. If the cause of the constraint cannot be determined collect the messages issued in the RKLVLOG and contact Candle Customer Support.


KAM0285I EVENTARV PDU STRING d BUF=x BUFL=lExplanation: This informational message is issued when tracing has been enabled. The contents of the protocol data units (PDUs) in an event packet from OG/MVS are indexed for debugging purposes. The PDU number within the packet is specified by d. The address of the PDU buffer and PDU length are specified by x and l, respectively.System Action: The alert adapter continues to monitor events from OG/MVS.User Response: None.

KAM0290W ALERT ADAPTER NOT ACTIVE. IPC SEND RC=ldExplanation: This warning message is issued when an attempt to transfer an event from OG/MVS to the alert adapter has failed. This can occur during startup or shutdown of the alert adapter when events cannot be accepted. The return code issued by the failing send operation is specified by ld.System Action: The alert adapter ignores the event from OG/MVS and continues execution.User Response: None.

KAM0295E ALERT ADAPTER ROW COULD NOT BE ALLOCATEDExplanation: This error message is issued when an attempt to allocate and initialize a row to be emitted by the alert adapter fails in response to an event arriving from OG/MVS.System Action: The alert adapter ignores the event from OG/MVS and continues execution.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0299I LU0 SESSION WITH SLUAPPLID=s TERMINATINGExplanation: This informational message is to signal the termination of an LU0 session with OG/MVS. The secondary logical unit application ID (SLUAPPLID) of the session is specified by s, to identify the OG/MVS subsystem that has been disconnected.System Action: The alert adapter proceeds to terminate the session monitoring thread and deregisters the OG/MVS subnode from CMS.User Response: None.

KAM0310I n:x*s*Explanation: This informational message is issued to dump the contents of a packet from OG/MVS in both hexadecimal and character format. The offset from the base address of the packet is specified by n. The contents of the packet are shown in hex format, x, and in character format, s.System Action: The alert adapter proceeds to process the packet.User Response: None.

EU001–KAO09998 61

KAM0401E IPC DEQUEUE ERROR=ldExplanation: The outbound OG/MVS sender thread has detected an error while attempting to read a message from its inter-process message queue. The return code issued by the read operation is specified by ld. This error can occur during uncontrolled shutdown of the alert adapter.System Action: The sender thread terminates and assumes that either the OG/MVS session has terminated or alert adapter shutdown has been initiated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0403W INVALID IPC MESSAGE RECEIVED SIZE=sz VERIFY=vExplanation: This error message is issued when an incorrectly formatted inter-process queue message is received by the OG/MVS sender thread for an LU0 session. The message size in number of bytes is specified by sz. The message verification indicator is specified by v.System Action: None.User Response: None.

KAM0410I OUTBOUND LU0 PACKET:Explanation: This informational message is issued when tracing has been enabled and precedes message KAM0310I to dump the contents of an output LU0 packet to an OG/MVS subsystem.System Action: The alert adapter proceeds to dump the contents of the output packet.User Response: None.

KAM0420E VTAM SEND ERROR RC=ldExplanation: This error message is issued when an attempt to send a packet to an OG/MVS subsystem has failed. The return code issued by the send operation is specified by ld. This error can occur if the LU0 session between the alert adapter and OG/MVS has terminated.System Action: The sender thread terminates and assumes that either the OG/MVS session has terminated or alert adapter shutdown has been initiated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0430E PACKET FORMATTING ERROR (process)=ldExplanation: This error message is issued when an attempt to format an output LU0 session packet has failed. The format process is specified by process and indicates formatting operation that has failed. The format return code is specified by ld.System Action: The sender thread terminates and assumes that either the OG/MVS session has terminated or alert adapter shutdown has been initiated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.


KAM0500E INVALID PDU RECEIVEDExplanation: This error message is issued when an attempt to parse a protocol data unit in an input LU0 session packet has failed.System Action: The listen thread terminates and assumes that either the OG/MVS session has terminated or alert adapter shutdown has been initiated.User Response: Collect the messages issued in the RKLVLOG and contact Candle Customer Support.

KAM0510I OG SUBNODE=s STARTED ON MATCH=mExplanation: This informational message is issued to indicate that a START packet has been received from a new LU0 session with OG/MVS. The subnode name registered with the Candle Management Server (CMS) is specified by s. The match number in OG/MVS which sent the START packet is specified by m.System Action: None.User Response: None.

KAM0520E s PDU FORMAT ERRORExplanation: This error message is issued when an error is detected in the format of an input LU0 packet. The packet type is specified by s. One or more KAM0310I messages follow this message to dump the contents of the input LU0 packet from OG/MVS.System Action: The alert adapter proceeds to dump the contents of the output packet.User Response: None.

KAM1001I GETFILTERINFO CALLED STATUS=ldExplanation: This informational message is issued when tracing has been enabled and indicates the GetFilterInfo service routine has been called to parse a situation predicate. The return code issued by the routine is specified by ld.System Action: The alert adapter proceeds to translate predicates into a REXX logical expression.User Response: None.

KAM1002I PREDICATE: op, col, relop, valueExplanation: This informational message is issued when tracing has been enabled and dumps a situation predicate. The logical conjunction operator of the predicate is specified by op. The column name to be compared is specified by col. The relational operator is specified by relop. The value to be used for the comparison is specified by value.System Action: The alert adapter proceeds to translate predicates into a REXX logical expression.User Response: None.

EU001–KAO09998 63

KAM1003I REXX EXPRS=exExplanation: This informational message is issued when tracing has been enabled and lists the REXX expression created by translating the predicates of a situation. The REXX expression is specified by ex.System Action: The alert adapter proceeds to transmit the translated situation predicates to all OG/MVS subnodes that are specified by the situation distribution list.User Response: None.

KAM1004E INVALID PREDICATES SPECIFIED FOR SITUATION=sExplanation: This error message is issued when the predicates for a situation have not included the required Message_ID attribute comparison. The situation name is specified by s. Every OR clause in a situation for the alert adapter must include at least one predicate specifying a value for the Message_ID attribute. This requirement limits the number of WTO message that may be accepted by the situation and prevents the Candle Management Server from being overloaded with WTO events.System Action: The situation is abnormally terminated without returning any data.User Response: Correct the situation predicates and ensure that at a predicate is specified for the Message_ID attribute.

KAM1008E TRAPADD SEND ERROR STATUS=rcExplanation: This error message is issued when an attempt to send a TRAPADD message to an OG/MVS subnode has failed. The return code of the send operation is specified by rc. This error can occur when a situation is started at the same time an OG/MVS session is terminated.System Action: The situation is abnormally terminated without returning any data.User Response: Verify that the LU0 session with OG/MVS was terminated at the same time the situation was being started. If this error continues to occur, collect messages from the RKLVLOG and contact Candle Customer Support.

KAM1009E UNABLE TO ALLOCATE s ALERT ADAPTER MSGExplanation: This error message is issued when inter-process queue message cannot be allocated and initialized. The message type is specified by s. This error can occur when available virtual storage is limited.System Action: The situation is abnormally terminated without returning any data.User Response: Determine if virtual storage has been constrained in the alert adapter address space and relieve the constraint as necessary. If this error continues to occur, collect messages from the RKLVLOG and contact Candle Customer Support.


KAM1010I PREDICATE: FUNC=fd COL=cs RELOP=relop VALUE=vx VALEN=vl TYPE=td LOGOP=ldExplanation: This informational message is issued when tracing has been enabled and indicates the GetFilterInfo service routine has been called to parse a situation predicate. The internal data returned by the GetFilterInfo service routine is dumped for the current predicate.System Action: The alert adapter proceeds to translate predicates into a REXX logical expression.User Response: None.

KAM1040E PREDICATE VALUE EXCEEDS MAXIMUM FOR SITUATION=sExplanation: This error message is issued when the buffer used to hold the translated predicates is too small to contain the comparison value for a single predicate. The situation name is specified by s.System Action: The situation is abnormally terminated without returning any data.User Response: Update the situation to reduce the size and number of predicates for the situation. Using a wildcard (“*”) may be an alternative to specifying the entire message text.

KAM1050E LENGTH OF PREDICATES EXCEEDS MAXIMUM SITUATION=sExplanation: This error message is issued when the buffer used to hold the translated predicates is too small to hold all the predicates of a situation. The situation name is specified by s.System Action: The situation is abnormally terminated without returning any data.User Response: Update the situation to reduce the size and number of predicates for the situation. Using a wildcard (“*”) may be an alternative to specifying the entire message text.

KAM2000E UNABLE TO GET RESPONSE FOR AE REQUEST=rid STATUS=rcExplanation: This error message is issued when an attempt to read a reply for an alert emitter action has failed. The alert emitter request ID is specified by rid. The return code from the inter-process queue read is specified by rc. The error can occur when an alert emitter action is requested at the same time an LU0 session is being terminated with the target OG/MVS session for the action or when the alert adapter is being shutdown.System Action: The alert emitter action request fails and no response is returned for the action request.User Response: If a session is not being terminated or an alert emitter shutdown is not in progress when this error message was issued, collect messages from the RKLVLOG and contact Candle Customer Support.

EU001–KAO09998 65

KAM2001I GETFILTERINFO CALLED STATUS=ldExplanation: This informational message is issued when tracing has been enabled and indicates the GetFilterInfo service routine has been called to parse an alert emitter action request. The return code issued by the routine is specified by ld.System Action: The alert emitter proceeds to issue a REXX exec call at the OG/MVS subsystem specified as the subnode for the action request.User Response: None.

KAM2002E UNABLE TO CREATE IPC QUEUE FOR AE REQUEST=rid STATUS=rcExplanation: This error message is issued when an attempt to create an inter-process message queue to receive replies for an alert emitter action has failed. The alert emitter request ID is specified by rid. The return code from the inter-process queue create operation is specified by rc. The error can occur when an alert emitter action is request at the same time an LU0 session is being terminated with the target OG/MVS session for the action or when the alert adapter is being shutdown.System Action: The alert emitter action request fails and no response is returned for the action request.User Response: If a session is not being terminated or an alert emitter shutdown is not in progress when this error message was issued, collect messages from the RKLVLOG and contact Candle Customer Support.

KAM2008E CALLEXEC SEND ERROR TO s STATUS=rcExplanation: This error message is issued when an attempt to send an alert emitter action to an OG/MVS subsystem has failed. The name of the target OG/MVS subnode name is specified by s. The return code issued by the send operation is specified by rc. The error can occur when an alert emitter action is request at the same time an LU0 session is being terminated with the target OG/MVS session for the action or when the alert emitter is being shutdown.System Action: The alert emitter action request fails and no response is returned for the action request.User Response: If a session is not being terminated or an alert adapter shutdown is not in progress when this error message was issued, collect messages from the RKLVLOG and contact Candle Customer Support.

KAM2009E UNABLE TO ALLOCATE s ALERT EMITTER MSGExplanation: This error message is issued when an attempt to allocate an action request message for an OG/MVS subsystem has failed. The type of message is specified by s. The error can occur when available virtual storage is limited.System Action: The alert emitter action request fails and no response is returned for the action request.User Response: Determine why virtual storage is constrained and relieve the condition. If the cause of the storage constraint cannot be determined, collect messages from the RKLVLOG and contact Candle Customer Support.


KAM2010I COMMAND=sExplanation: This informational message is issued when tracing has been enabled to display the formatted alert emitter command to be issued at a target OG/MVS subsystem. The formatted command is specified by s and includes substituted text from situation attributes.System Action: The alert emitter proceeds to issue a REXX exec call at the OG/MVS subsystems specified as the targets for the action request.User Response: None.

KAM2011I REQUESTID=idExplanation: This informational message is issued when tracing has been enabled to display the REQUESTID value specified for an alert emitter action. The request ID is specified by id.System Action: The alert emitter proceeds to parse the remainder of values of the current action request.User Response: None.

KAM2012I CALLTYPE=dExplanation: This informational message is issued when tracing has been enabled to display the CALLTYPE value specified for an alert emitter action. The call type is specified by id.System Action: The alert emitter proceeds to parse the remainder of values of the current action request.User Response: None.

KAM2013I ORIGINNODE=sExplanation: This informational message is issued when tracing has been enabled to display the ORIGINNODE value specified for an alert emitter action. The OG/MVS subsystem node is specified by s.System Action: The alert emitter proceeds to parse the remainder of values of the current action request.User Response: None.

KAM2020E INVALID IPC MESSAGE RECEIVED FOR REQUESTID=idExplanation: This error message is issued when an invalid inter-process queue message is received in response to an alert emitter action request. The request ID associated with the action is specified by id.System Action: The alert emitter action request fails and no response is returned for the action request. The delivery of the alert emitter action cannot be verified.User Response: Collect messages from the RKLVLOG and contact Candle Customer Support.

EU001–KAO09998 67

KAM2030W ALERT EMITTER RESPONSE TIMEOUT REQUESTID=idExplanation: This warning message is issued when a response to an alert emitter action request is not received within the time limit allotted. The default time limit is 60 seconds. The request ID associated with the action is specified by id. This error can occur when the OG/MVS subsystem is not responding to alert emitter actions or when the requested action takes longer than 60 seconds to complete.System Action: The alert emitter action request fails and no response is returned for the action request. The delivery of the alert emitter action cannot be verified.User Response: Determine why the action request is being delayed.

KAM2040E INVALID DESTNODE=s SPECIFIED FOR EMITTERExplanation: This error message is issued when a destination node for an alert emitter action request cannot be found. The destination node is specified by s. This error may occur if the alert adapter is specified for the target action. You must specify the node name of an alert emitter which is normally suffixed with “:OGActions”.System Action: The alert emitter action request fails and the action request is aborted.User Response: Review the entry associated with this alert emitter action in the KFAASITR member or file. Ensure that the DESTNODE value specifies an alert emitter node name.

KAM3010E UNABLE TO FIND TABLE MANAGER FOR KAM ALERT ADAPTERExplanation: This error message is issued when tracing has been enabled to report an internal error.Explanation: A new OG/MVS subsystem has been registered but the agent framework table manager cannot be located to determine if existing situations need to be distributed to the new subsystem.System Action: Redistribution of situations to the newly arrived OG/MVS is aborted.User Response: None.

KAM3020E UNABLE TO FIND REMOTE MANAGER FOR KAM ALERT ADAPTERExplanation: This error message is issued when tracing has been enabled to report an internal error.Explanation: A new OG/MVS subsystem has arrived, but the agent framework remote manager cannot be located to determine if existing situations need to be distributed to the new subsystem.System Action: Redistribution of situations to the newly arrived OG/MVS is aborted.User Response: None.


KAM3030E UNABLE TO LOCATE SUBNODE s ACCESS RC=rcExplanation: This error message is issued to report that an attempt to distribute a situation to an OG/MVS subnode has failed because the inter-process queue (IPC) for the subnode cannot be found. The subnode is specified by s. The return code from the IPC queue access operation is specified by rc.System Action: The distribution of situations is aborted.User Response: Collect messages from the RKLVLOG and contact Candle Customer Support.

KAM9000I IPC MESSAGE VERIFY=d MSGTYPE=typeExplanation: This informational message is issued when tracing is enabled to dump the common components of an interprocess queue message. The message verification indicator is specified by d. The integer value indicating the message type is specified by type.System Action: Normal processing continues.User Response: None.

KAM9001I TRAPADD SITNAME=s, QUERYHDL=xExplanation: This informational message is issued when tracing is enabled to dump the components of a TRAPADD type interprocess queue message. The situation name associated with the TRAPADD request is specified by s. The unique query handle is specified by x in hexadecimal format.System Action: Normal processing continues.User Response: None.

KAM9002I TRAPADD REXXEXPS=sExplanation: This informational message is issued when tracing is enabled to dump the components of a TRAPADD type interprocess queue message. The REXX expression sent in the TRAPADD request is specified by s.System Action: Normal processing continues.User Response: None.

KAM9003I TRAPDEL SITNAME=s, QUERYHDL=xExplanation: This informational message is issued when tracing is enabled to dump the components of a TRAPDEL type interprocess queue message. The situation name associated with the TRAPADD request is specified by s. The unique query handle is specified by x in hexadecimal format.System Action: Normal processing continues.User Response: None.

KAM9004I EVENTARRIVED ROW=xExplanation: This informational message is issued when tracing is enabled to dump the components of a EVENTARRIVED type interprocess queue message. The address of the buffer containing the event row is specified by x in hexadecimal format.System Action: Normal processing continues.User Response: None.

EU001–KAO09998 69

KAM9005I CALLEXEC CMD=sExplanation: This informational message is issued when tracing is enabled to dump the components of a CALLEXEC type interprocess queue message. The REXX command string specified in the message is specified by s.System Action: Normal processing continues.User Response: None.

KAM9006I CALLEXEC IPCHDL=x REQUESTID=dExplanation: This informational message is issued when tracing is enabled to dump the components of a CALLEXEC type interprocess queue message. The unique interprocess message queue handle is specified by x in hexadecimal format. The unique identifier assigned to the CALLEXEC request is specified by d.System Action: Normal processing continues.User Response: None.

KAM9007I CALLEXECRESPONSE RC=d TIMESTAMP=s RESPONSE=rExplanation: This informational message is issued when tracing is enabled to dump the components of a CALLEXECRESPONSE type interprocess queue message. The return code after execution of a REXX expression requested in a CALLEXEC request is specified by d. The time at which the REXX exec completed execution is specified by s in cYYMMDDHH:MM:SSm format. An optional response string returned by the REXX expression is specified by r.System Action: Normal processing continues.User Response: None.

KAM9008I REGISTERSUBNODE NAME=sExplanation: This informational message is issued when tracing is enabled to dump the components of a REGISTERSUBNODE type interprocess queue message. The new OG/MVS subnode name to be registered is specified by s.System Action: Normal processing continues.User Response: None.

KAM9009I DEREGISTERSUBNODE NAME=sExplanation: This informational message is issued when tracing is enabled to dump the components of a DEREGISTERSUBNODE type interprocess queue message. The OG/MVS subnode name to be deregistered is specified by s.System Action: Normal processing continues.User Response: None.

KAM9030I IPC QUEUE STATUS=rc BUF=x BUFL=l MSG=xExplanation: This informational message is issued when tracing is enabled to report the status of an interprocess message queue send operation. The status of the send operation is specified by rc. The address of the buffer containing the message send is specified by x in hexadecimal format. The buffer length is specified by l. The first four bytes of the message are displayed by x in hexadecimal format.System Action: Normal processing continues.User Response: None.


KAM9999I KAM TERMINATINGExplanation: This informational message is issued to indicate that the alert adapter has completed termination and cleanup operations.System Action: Alert adapter terminates.User Response: None.

KAO00000 ’CALENDAR initialization failed with reason code: ’ p1 ’result =’ p2Explanation: Reason code indicates CALENDAR module and reason for failure to initialize. Failure of CALENDAR is catastrophic to AF/OPERATOR and appropriate actions must be taken to resolve conditions leading to failure prior to restarting.System Action: Review reason code.User Response: Review reason codes for CALENDAR manager and respond accordingly.

KAO01000 ’AF/OPERATOR Version’ p1 ’Resource Manager successfully initialized’ p2Explanation: This message indicates that the product has successfully initialized.System Action: None. Informational only. System will now process events.User Response: None.

KAO01001 ’AF/OPERATOR Resource Manager is already initialized.’Explanation: A request to initialize was received after the product was already up.System Action: None.User Response: None. This message is informational only.

KAO01002 ’AF/OPERATOR Resource Manager failed to initialize’Explanation: EV processing failed to initialize. This indicates an internal problem with the product and must be reported to Candle.System Action: The product will not accept events.User Response: Contact Candle Customer Support.

KAO01003 ’A message ID could not be determined for subsystem’ p1 ’function’ p2 ’ status code’ p3 ’reason code’ p4Explanation: An error message that needed to be issued on behalf of a subsystem could not be determined.System Action: Message is ignored.User Response: This indicates an internal problem with the product. Contact Candle Customer Support.

KAO01004 ’The parameter string variable for this trap could not be obtained’Explanation: An event was passed without an associated parameter variable. This indicates an internal error with the product.System Action: The event is deleted. The system continues to run.User Response: Contact Candle Customer Support.

EU001–KAO09998 71

KAO01005 ’AF/OPERATOR Resource Manager is not initialized or is refreshing. Event ignored.’Explanation: An event was initiated but the product is not up and running.System Action: The product was not initialized so the event was ignored.User Response: This may indicate an internal problem. Contact Candle Customer Support.

KAO01006 ’The’ p1 ’parameter field for the event is invalid’Explanation: An unrecognizable value in the parameter string for an event was passed. This indicates an internal problem with the product.System Action: The event is ignored. System continues to run.User Response: Contact Candle Customer Support.

KAO01008 ’The update to the EV block, with parameter information, failed.’Explanation: An attempt to update the EV block with the parameters of the event failed. This indicates an internal problem with the product.System Action: The event is rejected. The system continues to run.User Response: Contact Candle Customer Support.

KAO01009 ’Request to call subsystem failed. Invalid subsystem name. SUBSYSTEM=’ p1Explanation: An internal call to a subsystem could not be honored because the subsystem name is invalid. This indicates an internal problem with the product.System Action: The request is rejected. The system continues to run.User Response: Contact Candle Customer Support.

KAO01010 ’Requested service invalid. SERVICE=’ p1Explanation: A request for EV services contained an unrecognizable service name. This indicates an internal problem with the product.System Action: The request is rejected. The system continues to run.User Response: Contact Candle Customer Support.

KAO01011 ’AF/OPERATOR Resource Manager now draining in-progress events.’Explanation: The product has gone into drain mode on behalf of a refresh request. The currently running events are allowed to complete. New events are not accepted while in drain mode. Once the events complete the user definitions are refreshed.System Action: The in-progress events are allowed to complete.User Response: This message is informational only.

KAO01012 ’User definitions could not be refreshed due to error. Reason code=’ p1Explanation: During a refresh operation the product failed to re-initialize. This indicates an internal problem with the product.System Action: The product is shutdown and needs to be manually restarted.User Response: Contact Candle Customer Support.


KAO01013 ’Invalid profile name for REFRESH. Requested profile=’ p1Explanation: A refresh request to EV specified an inactive profile name.System Action: An attempt to refresh a non-active profile was rejected.User Response: Correct the profile name and reissue the refresh command.

KAO01014 ’AF/OPERATOR Resource Manager REFRESH initiated.’Explanation: The refresh request was accepted and is now in progress.System Action: The refresh request starts executing.User Response: This message is informational only.

KAO01015 ’AF/OPERATOR Resource Manager REFRESH FORCE initiated.’Explanation: The refresh force request was accepted and execution has began.System Action: A refresh force request has started executing.User Response: This message is informational only.

KAO01016 ’AF/OPERATOR Initializing Resource Manager’ p1 ’with Profile’ p2’.’Explanation: Initialization has begun with either a Warm or Cold Start.System Action: Initialization has started.User Response: This message is informational only.

KAO01018 ’A Cold Start is being performed because the current Profile does not match previous Profile(’p1’).’Explanation: A Warm Start was requested either explicitly or by default, but the Profile being Initialized was not the Profile that was last active. A Cold Start will be performed instead.System Action: Initialization with Cold Start will be performed.User Response: This message is informational only.

KAO01019 ’A Cold Start is being performed because information required for a Warm Start was not available.’Explanation: A Warm Start was requested either explicitly or by default, but the information required for a Warm Start was not available. A Cold Start will be performed instead.System Action: Initialization with Cold Start will be performed.User Response: Check that Checkpointing is active and that you have RELOAD(RSVS) or RELOAD(ALL).

KAO01100 ’AF/OPERATOR Resource Manager definitions now refreshed.’Explanation: The requested REFRESH operation successfully completed.System Action: The refresh has completed. Normal processing continues.User Response: This message is informational only.

KAO01101 ’AF/OPERATOR Resource Manager draining. Event ignored.’Explanation: An event request was issued to EV while EV was in drain mode. EV will reject all events during its drain process.System Action: The event is rejected. Draining continues.User Response: This message is informational only.

EU001–KAO09998 73

KAO01102 ’AF/OPERATOR Resource Manager failed to refresh.’Explanation: During the refreshing of data, a subcomponent failed to restart and caused the REFRESH operation to fail.System Action: The product is terminated and will not accept events.User Response: Check any error messages that preceded this one. This is probably an internal problem with the product. Contact Candle Customer Support.

KAO01103 ’Event’ p1 ’does not exist.’Explanation: A request to process an existing event was rejected because the event could not be found.System Action: Request to process existing event rejected.User Response: This message may occur after a REFRESH FORCE. If this message did not occur after a REFRESH FORCE was executed, then search the SYSLOG for other error messages that indicate why the event was deleted.

KAO01104 p1 ’performed for’ p2 ’Resource(s).’Explanation: An RCF command such as SCHEDULE, CHECK, etc. has been performed. The message shows the number of Resources affected by the action.System Action: RCF command performed.User Response: None.

KAO01105 A’ p1 ’Event for Resource’ p2 ’ has been created because’ of an RCF SCHEDULE command.’Explanation: A Start or Stop for a Resource has been initiated to bring the Resource to the current Scheduled Status.System Action: Resource Start or Stop performed.User Response: None.

KAO01999 ’AF/OPERATOR Version’ p1 ’Resource Manager has terminated successfully ’Explanation: The product terminated without failure. This message is informational only.System Action: None.User Response: None.

KAO02000 ’RS request’ p1 ’was passed an invalid number of parameters’Explanation: The RS service requested by the caller contained an invalid number of parameters.System Action: The request is rejected. The system continues to run.User Response: This indicates a problem with the code. Contact Candle Customer Support.

KAO02001 ’RS has not initialized a resource list. The RS request for’ p1 ’is rejected.’Explanation: RS builds and maintains a resource name list during initialization. This list was not found and was needed in order to service the request.System Action: The request is rejected. The system continues to run.User Response: This message indicates an internal problem with the product. Contact Candle Customer Support.


KAO02002 ’The resource named’ p2 ’passed to RS for request’ p1 ’is invalid’Explanation: An incorrect resource name was entered either in the user interface definitions or in an RCF command.System Action: The request is rejected. The system continues to run.User Response: Correct the resource name and refresh the definitions.

KAO02003 ’A request to turn RS recovery’ p2 ’was incorrect for resource’ p1Explanation: A caller of RS services attempted to set the recovery into an invalid state.System Action: The request is rejected. The system continues to run.User Response: This message indicates an internal problem with the product. Contact Candle Customer Support.

KAO02004 ’A request for RS service’ p1 ’attempted to pass a table name (’ p2 ’) containing a period.’Explanation: A caller of RS services passed a stem name containing a period. This is incorrect.System Action: The request is rejected. The system continues to run.User Response: This message indicates an internal problem with the product. Contact Candle Customer Support.

KAO02005 ’The users check exit’ p1 ’returned an invalid state of’ p2 ’for the resource’ p3Explanation: The user-coded check exit attempted to return a state that is not recognized. The valid values to return are START and STOP. START indicates the resource is up and running. STOP indicates the resource is down. The events attempting to use this check exit are now lost.System Action: The state of the resource remains unchanged.User Response: Correct the check exit.

KAO02006 ’The !RESULT field in the EV block is invalid. !RESULT=’ p1 ’!SOURCE= ’ p2Explanation: EV passed an event block to RS containing an invalid value for !RESULT. This value is supplied by the requester of the event. The source in the text of the error message identifies the requester.System Action: The event is deleted by RS. The system continues to run.User Response: This message indicates an internal problem with the product. Contact Candle Customer Support.

KAO02007 ’The ISPF tables from the user interface could not be read. RS failed to initialize’Explanation: A problem was encountered in component RS during initialization. An attempt to read the ISPF tables from the user interface failed.System Action: The product fails to initialize.User Response: This indicates an internal problem with the product. Contact Candle Customer Support.

EU001–KAO09998 75

KAO02008 ’A request to’ p1 ’field’ p2 ’in the RS block is invalid’Explanation: A caller of RS services attempted to pass an invalid field name.System Action: The request is rejected. The system continues to run.User Response: This message indicates an internal problem with the product. Contact Candle Customer Support.

KAO02009 ’The retry period has expired for resource’ p1 ’. The retry count is now reset to 1.’Explanation: The retry period specified by the user has expired, and recovery will again be allowed for the resource. The retry count is reset.System Action: The period threshold for retries has expired. Recovery is allowed.User Response: This is informational and does not necessarily indicate a problem. If the retry period is too short, it may not limit the recovery on a resource. In that case, the user should increase the retry period for that resource.

KAO02010 ’The retry limit for resource’ p1 ’has been reached.’Explanation: The number of recovery retries for this resource has been exceeded. Recovery is turned off for the resource until the retry period has expired.System Action: Recovery is shut off for this resource.User Response: This message is informational and indicates a problem only with the resource itself.

KAO02011 ’Invalid service requested from RS. SERVICE=’ p1Explanation: A caller of RS services requested an invalid service.System Action: The request is ignored. The system continues to run.User Response: This message indicates an internal problem with the product. Contact Candle Customer Support.

KAO02012 ’RECOVERY is being attempted for resource’ p1Explanation: A resource, for which the user has defined recovery, has failed, and the product is attempting to recover it.System Action: The product is attempting to recover a resource.User Response: This message is informational, but the underlying resource may have problems.

KAO02013 ’Request ’p1’ ignored. Resource ’p2’ is unrecoverable and must be reset.’Explanation: A request to RS was issued against an unrecoverable resource. The resource became unrecoverable when the number of recovery retries exceeded the user specified limit.System Action: The request is rejected. The system continues to run.User Response: Reset the resource by issuing the appropriate RCF command.


KAO02014 ’Check exit ’p1’ could not be loaded for resource’ p2Explanation: During check exit processing, the user-defined check exit could not be loaded. The resource is marked as having a bad check exit and will report it as an error each time the product attempts to use the check exit.System Action: The user defined a check exit module that failed to load.User Response: The check exit module specified by the user is probably named incorrectly or is not available in the AOCMDLIB concatenation. Either change the definition to the correct name and refresh the product, or include the proper library in the AOCMDLIB concatenation.

KAO02015 ’Check exit failed on unknown reason code ’p1’ for resource ’p2Explanation: A call to the check exit returned an unknown reason code. This indicates an internal problem with the product.System Action: The event is rejected. The system continues to run.User Response: Contact Candle Customer Support.

KAO02016 ’A recovery event failed for resource’ p1’.’Explanation: A recovery event has failed, probably because of a bad check exit.System Action: The event is rejected. The system continues to run.User Response: Check for error messages during product initialization on the check exit routine. These messages will give specific information on what failed.

KAO02017 ’Resource’ p1 ’already in’ p2 ’state. Event cancelled.’Explanation: An event attempting to execute an activity to bring the target resource into the desired state was cancelled because the resource was already in that state.System Action: The event is rejected. The system continues to run.User Response: If this was not the expected state of the resource, check your definitions for that resource to ensure that the success message has the correct pattern. You may need to check the SYSLOG to see if the resource failed.

KAO02018 ’Recovery for’ p1 ’terminated because resource is still ACTIVE.’Explanation: Recovery has started for a resource, but the resource still shows ACTIVE in the system. Either the resource has hung during abnormal termination, or there is another task of the same name ACTIVE in the system.System Action: The resource is marked UNRECOVERABLE. The system continues to run.User Response: Check, then reset the resource by issuing the appropriate RCF commands.

KAO03001 ’Invalid or unrecognized arguments.’Explanation: An invalid argument list was presented to the specified AC function.System Action: AC terminates the request.User Response: This is an internal logic error in the product. Contact Candle Customer Support.

EU001–KAO09998 77

KAO03004 ’Shared variable’ p1 ’function failed. RC:’ p2’. Pool:’ p3 ’Variable:’ p4’.’Explanation: An error was detected while processing a REXX shared variable.System Action: Event is terminated.User Response: This indicates a problem with the OG/MVS product. Contact Candle Customer Support.

KAO03100 ’The AC component failed to process the activity for resource’ p1Explanation: The activity component (AC) of the product failed to process the event. This indicates an internal problem with the product.System Action: The activity is not executed. The event is rejected.User Response: Contact Candle Customer Support.

Note: The AOMSGLOG will contain a "percolation string" associated with this error. It can be identified in the log by searching for "percolation string." You will need to have this when you contact Candle Customer Support.

KAO03101 ’The activity requested is not defined for resource ’p1Explanation: The requested activity was not defined for this resource.System Action: The event is rejected. The system continues to run.User Response: Either add the activity to the resource definitions and refresh the product definitions or remove any scheduled events for that activity.

KAO03900 p1’ will be ’p2’ at ’p3’. Reply: OK, NOW, EXTEND(1-60), or CANCEL.’Explanation: The resource specified will be started or stopped at the time shown. This is an informational message that will allow the operator to modify the actual stop or start time of the resource.System Action: If no operator reply is received, OK is generated.User Response: Valid responses are listed in the message. Responding OK will release the resource event at the specified time. NOW will start or stop the resource immediately. EXTEND(n) will lengthen the specified time by 1 to 60 minutes. CANCEL will bypass the stop or start. All other responses will have no effect on processing. If no response is detected before the designated time, an OK will be generated.

KAO04001 ’Incorrect number of parms passed to EQ’Explanation: An incorrect number of parameters were passed to the EQ function.System Action: Action is bypassed.User Response: None. This is an internal error. Call Candle Customer Support for assistance in running diagnostics.

KAO04002 ’Invalid function call passed to EQ.’Explanation: Functions supported are ’init’, ’event’, ’list’, or ’term’. These are used internally, and they must be specified by the caller of EQ.System Action: Action is bypassedUser Response: None. This is an internal error. Call Candle Customer Support for assistance in running diagnostics.


KAO04003 ’Incorrect or null parm passed to EQ.’Explanation: An incorrect or null parameter was passed to the EQ function.System Action: Action is bypassedUser Response: None. This is an internal error. Call Candle Customer Support for assistance in running diagnostics.

KAO04004 ’Error obtaining predecessor table for profile ’p1’.’Explanation: During initialization of the EQ component, an error occurred when attempting to get predecessor data.System Action: Initialization of EQ component is bypassed.User Response: None. This is an internal error. Call Candle Customer Support for assistance in running diagnostics, if required.

KAO04005 ’Error saving predecessor or successor data for profile ’p1’.’Explanation: An error has occurred while attempting to save predecessor or successor data in REXX shared variables.System Action: Initialization for the EQ component is bypassed.User Response: Verify that there is no problem with REXX shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for assistance in running diagnostics.

KAO04006 ’The’ p1 ’for Resource’ p2 ’has either timed out or ended unsuccessfully.’Explanation: A Start or Stop for a Resource has ended unsuccessfully, either because a Failure Message was detected or because the activity timed out. This message is issued after any retry attempts have been carried out, and just before the Failure Process, if any, is executed.System Action: Initialization for the EQ component is bypassed.User Response: Check Syslog or other logs to see whether the Resource did actually Start or Stop. If it did, then check whether the Success Message(s) for this activity are defined correctly.

KAO04007 ’Resource’ p1 ’on ’ p2 ’waiting for Predecessor’ p3 to Start on’ p4 ’.’Explanation: A Start for a Resource could not proceed because a Predecessor Resource is not active. The Start will continue as soon as the Resource being waited for starts. This request remains on the active wait queue until the predecessor starts or the request is purged manually.System Action: The Resource Manager continues with other work.User Response: None.

KAO04008 ’Resource’ p1 ’on ’ p2 ’waiting for Successor’ p3 to Stop on’ p4 ’.’Explanation: A Stop for a Resource could not proceed because a Successor Resource is still active. The Stop will continue as soon as the Resource being waited for stops. This request remains on the active wait queue until the successor stops or the request is purged manually.System Action: The Resource Manager continues with other work.User Response: None.

EU001–KAO09998 79

KAO04009 ’Predecessor’ p1 ’to resource’ p2 ’is not valid on this system....ignoring.’Explanation: The named predecessor resource was not defined to run on the current MVS system, and thus, is ignored.System Action: The Resource Manager continues with other work.User Response: None.

KAO04010 ’Successor’ p1 ’to resource’ p2 ’is not valid on this system....ignoring.’Explanation: The named successor resource was not defined to run on the current MVS system, and thus, is ignored.System Action: The Resource Manager continues with other work.User Response: None.

KAO04011 ’Resource’ p1 ’Purged from’ p2 ’wait queue.’Explanation: A requested START or STOP activity for the named resource was purged from activity wait queue.System Action: The Resource Manager continues with other work.User Response: None.

KAO04012 ’The’ p1 ’for Resource’ p2 ’was successful on’ p3 ’.’Explanation: A requested START or STOP activity for the named resource was successful on the specified MVS system.System Action: The Resource Manager continues with other work.User Response: None.

KAO04013 ’Return code (’p1’) while trying to lock (’p2’).’Explanation: The RSM was unable to obtain a lock on the named resource. The return code indicates the reason.System Action: The Resource Manager continues with other work.User Response: Notify Candle - please provide the return code.

KAO04014 ’Resource’ p1 ’already on’ p2 ’wait queue.’Explanation: A START or STOP request for the named resource already exists on the activity wait queue.System Action: The Resource Manager continues with other work.User Response: Issue an "RCF SHOW resource S=*" command to determine the names of the predecessors or successors that the named resource is waiting on. If you want to purge the existing request and re-submit the failing START or STOP request, you can supply the optional PURGE keyword on the RCF START or RCF STOP command.

KAO04015 ’Resource’ p1 ’launch failure - reason code’ p2 ’.’Explanation: A START or STOP request for the named resource failed. Make a note of the reason code.System Action: The Resource Manager continues with other work.User Response: Call Candle and please supply the reason code.


KAO04401 ’EQ LIST specified ’p1’, either PRED or SUCC must be specified.’Explanation: Incorrect required parm was specified for LIST.System Action: LIST function is bypassed.User Response: Recode the call to EQ LIST using PRED or SUCC as the third parameter.

KAO04402 ’Error processing predecessor or successor list for resource ’p1’.’Explanation: An error was encountered when either obtaining or saving the requested list of predecessors or successors.System Action: LIST function is bypassed.User Response: Verify that there is no problem with REXX shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for assistance in running diagnostics.

KAO04403 ’Warning, termination in progress, LIST is bypassed.’Explanation: Termination was initiated at the time a LIST function was attempted.System Action: LIST function is bypassed.User Response: None. This message is informational only.

KAO04501 ’Termination in progress for profile ’p1’, event ’p2’ bypassed.’Explanation: Termination has been initiated for the EQ component. No new processes will be started. Ongoing work will be completed before termination continues.System Action: No new activities will be started, existing activities will complete.User Response: None. This message is informational only.

KAO04502 ’Error obtaining predecessor wait flag for event ’p1’.’Explanation: An error occurred attempting to access a REXX shared variable used in EV processing.System Action: Event is bypassed.User Response: Check to be sure that REXX shared variables have not been incorrectly deleted. Verify that there is no problem with these variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for assistance with running diagnostics.

KAO04503 ’Error obtaining event fields for event ’p1’.’Explanation: An error was encountered obtaining fields in the event block. These fields are required to continue processing the event.System Action: Event is bypassed.User Response: None. This is an internal error. Save your message log. Call Candle Customer Support for help with running diagnostics.

EU001–KAO09998 81

KAO04504 ’Invalid activity field detected for resource ’p1’.’Explanation: The EQ component was passed an activity field that did not contain either ’start’ or ’stop’. One of these is a required value.System Action: Event is bypassed.User Response: None. This is an internal error. Save your message log for reference. Call Candle Customer Support for help with running diagnostics.

KAO04505 ’Error obtaining predecessor table for resource ’p1’.’Explanation: An error occurred while attempting to get REXX shared variables containing predecessor data.System Action: The event is bypassed.User Response: Check to be sure that REXX shared variables have not been incorrectly deleted. Verify that there is no problem with these variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics.

KAO04506 ’Invalid result field for resource ’p1’.’Explanation: An invalid ’result’ field was passed to the EQ component for an event.System Action: The event is bypassed.User Response: None. This is an internal error. Save your message log for reference. Call Candle Customer Support for help with running diagnostics.

KAO04507 ’Resource ’p1’ received invalid state for predecessor/successor ’p2’.’Explanation: The predecessor or successor ’actual’ state field did not contain either ’start’ or ’stop’. One of these is required.System Action: The event is bypassed.User Response: None. This is an internal error. Save your message log for reference. Call Candle Customer Support for help with running diagnostics.

KAO04508 p2 ’error accessing status for predecessor or successor, ’p1’.’Explanation: An error occurred attempting to obtain data from the Resource Block for the predecessor of the resource being run.System Action: Event is bypassed.User Response: None. This is an internal error. Save your message log for reference. Call Candle Customer Support for help with running diagnostics.

KAO04509 ’Resource ’p1’ error accessing predecessor/successor data for ’p2’.’Explanation: An error occurred getting REXX shared variables containing predecessor/successor data.System Action: Event is bypassed.User Response: Check that REXX Shared Variables have not been incorrectly deleted. Verify that there is no problem with these variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics.


KAO04510 ’Error in storing ’p1’ in wait list of predecessor or successor ’p2’.’Explanation: The EQ function found that a resource was required to wait for a predecessor or successor before continuing. An error was encountered in REXX shared variable processing while attempting to update the wait list.System Action: Event is bypassed.User Response: Verify that there is no problem with REXX shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics.

KAO04511 ’Error saving predecessor or successor wait time for resource ’p1’.’Explanation: An error occurred in REXX shared variable processing while attempting to save the timeout value required to initiate predecessor or successor wait.System Action: Event processing is bypassed.User Response: Verify that there is no problem with REXX shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics.

KAO04512 ’Error saving trap name ’p1’ for later cleanup of event ’p2’.’Explanation: An error occurred while attempting to save a trap name in RESS shared variables. This will be required for later cleanup at event end.System Action: Processing continues.User Response: Show the named trap and delete it manually, if necessary, after the current event has finished processing.

KAO04513 ’Error creating predecessor timeout for resource ’p1’.’Explanation: During setup for a predecessor or successor wait the resource experienced an error.System Action: Event is bypassed.User Response: None. This is an internal error. Contact Candle Customer Support for help with running diagnostics.

KAO04601 ’Error obtaining current state of resource ’p1’.’Explanation: While determining if the resource activity was successful, an error occurred when checking for status of started or stopped.System Action: Event completion process is bypassed.User Response: None. This is an internal error. Call Candle Customer Support for help with running diagnostics, if required.

KAO04602 ’Error obtaining names of waiting resources for resource ’p1’.’Explanation: The resource listed is the predecessor or successor of waiting resources. An error in REXX shared variable processing occurred when attempting to obtain the names of the waiting resources, so they cannot be released.System Action: Waiting resources will not be started or stopped.User Response: Verify that there is no problem with REXX shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics. You may need to manually start or stop dependent resources.

EU001–KAO09998 83

KAO04603 ’Error attempting to release resources waiting for ’p1’.’Explanation: The resource listed is the predecessor or successor of a waiting resource(s). An internal error occurred when attempting to release the waiting resource(s).System Action: Waiting resources will not be started or stopped.User Response: None. This is an internal error. Call Candle Customer Support for help with running diagnostics, if required. You may need to manually start or stop dependent resources.

KAO04604 ’Warning, resource ’p1’ not removed from list waiting on ’p2’.’Explanation: The resource timed out while waiting for a predecessor or successor. An error occurred while attempting to remove the resource’s name from the list of resources waiting for that predecessor or successor.System Action: Normal ’FAIL’ processing continues.User Response: None. This is a warning message. The product may attempt to start or stop the waiting resource an additional time. You may want to investigate the condition of the predecessor or successor, or re-check predecessor and predecessor timeout definitions.

KAO04605 ’Warning, event ID ’p1’ not deleted’.’Explanation: The event ID specified encountered an error during normal event exit. The ID will not be removed until the product is recycled.System Action: Processing continues.User Response: None. This is an internal error which should not affect product performance adversely. If this occurs frequently or repeatedly, contact Candle Customer Support for help with running diagnostics.

KAO04606 ’Resource ’p1’ timed out waiting for predecessor or successor ’p2’.’Explanation: A ’start’ or ’stop’ process did not begin for the resource because a predecessor or successor was not in the required state. The wait was ended by the specified timeout value, and normal fail processing continues.System Action: Event ’FAIL’ processing continues.User Response: Check to see why the predecessor was not started or the successor was not stopped, or review predecessor definitions for accuracy. Restart the resource when prerequisite conditions are correct.

KAO04701 ’Error obtaining activity data for event ID ’p1’.’Explanation: An error occurred while attempting to access the Event Block for the listed event.System Action: Event is bypassed.User Response: None. This is an internal error. Call Candle Customer Support for help with running diagnostics, if required.


KAO04702 ’Error obtaining success or fail text for resource ’p1’.’Explanation: An error occurred while attempting to get the text specified to indicate success or failure of this resource’s start or stop activity.System Action: Event is bypassed.User Response: This is probably an internal error, but it may be related to problems with REXX shared variables. Verify that there is no problem with shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics.

KAO04703 ’Invalid process type passed for resource ’p1’.’Explanation: An error occurred while attempting to execute a start or stop process for the resource.System Action: Event processing is bypassed.User Response: None. This is an internal error. Call Candle Customer Support for help with running diagnostics, if required.

KAO04704 ’Warning, error saving trap name(s) for later ’p1’ event cleanup.’Explanation: Traps and REXX shared variables were created on behalf of the event currently being processed. An error was encountered while attempting to save a list of these, so that they could be deleted at event end.System Action: Processing continues.User Response: Verify that there is no problem with REXX shared variables in your system. Save your message log for reference. If necessary, call Candle Customer Support for help with running diagnostics.

KAO04705 ’Warning, resource ’p1’ success or fail trap not using jobname.’Explanation: Success or fail messages for this process may match on similar text from other resources. That is because the trap created on behalf of the resource does not contain the ’jobname’ parameter.System Action: Processing continues.User Response: None. This message is informational only. If problems are suspected due to matching on incorrect resources, call Candle Customer Support for help with running diagnostics.

KAO04801 ’EQ termination for profile ’p1’ rejected due to busy condition.’Explanation: The EQ component could not obtain it’s termination flag. This is due probably to busy system conditions; however, it may be caused by an internal error.System Action: Termination of EQ component is not carried out.User Response: Retry termination, or use the FORCE parameter on the call to EQ.

KAO04802 ’Warning, termination flag for profile ’p1’ not found.’Explanation: A termination flag was not found as expected by EQ.System Action: Termination FORCE assumed, processing continues.User Response: None. This message is informational only. The required REXX shared variables may have been deleted unintentionally, but this should not affect processing, since they would be deleted during termination in any case.

EU001–KAO09998 85

KAO04803 ’Termination incomplete for profile ’p1’.’Explanation: An error occurred in REXX shared variable processing during EQ normal termination.System Action: Termination of the EQ component is aborted.User Response: Retry termination of EQ using the FORCE parameter.

KAO05000 ’Internal Trap Class Error:’ p1 ’. Error String:’ p2’.’Explanation: During processing, the internal Trap Class Manager, which handles the creation and deletion of Traps for AO internal components, experienced a critical failure. This message will be followed by a component level failure message to indicate the AO function not completed.System Action: The Trap Class Manager did not perform the requested internal function.User Response: This is an internal failure. Contact Candle Customer Support.

KAO08000 ’AF/OPERATOR Resource Manager Reply with Scheduler Startup Option (NOW, OK, datetime, HELP)’Explanation: This message is issued during a Cold Start only. The reply to this message controls how the Scheduler determines the current Scheduled Status for each Resource during Initialization (Resources may be started or stopped to bring them to this Status). This reply does not affect future Scheduled Events.

System Action: If no operator reply is received, OK is generated.User Response: Reply with one of three choices above or reply HELP.

KAO08001 ’The Scheduler’’’’s last event time was not found. Using current time.’Explanation: The Scheduler checkpoints the date and time of the last event it issues and attempts to use that date and time when performing initialization. The checkpointed variable was not available for initialization; therefore, the current date and time were used for KAO08000 startup message.System Action: The current date and time are used for Scheduler start.User Response: See message KAO08000, which follows this message.

KAO08002 ’System environment via profile’ p1 ’restarting’ p2’.’Explanation: The profile’s resource list will be used to restart the system environment. A ’WARM’ start places resources in the state which was last desired. A ’COLD’ start places resources in the last known scheduling state. This message is immediately followed by action message KAO08000.System Action: System will perform a COLD or WARM restart of the system environment.User Response: Respond to message KAO08000.

OK Scheduled Status will be determined from the defined Schedules.

NOW No Resources will be started or stopped during Initialization (Schedule starts from NOW).

yyyymmddhhmmss Scheduled Status will be the most recent Scheduled Start/Stop since date/time.


KAO08003 ’Invalid response (’p1’) - issue the ’’RCF HELP KAO08000’’ command for more information’Explanation: The response to message KAO08000 was incorrect. More information is available by issuing the above command.System Action: The KAO08000 WTOR is displayed again.User Response: Issue the RCF HELP KAO08000 command or reply to the WTOR.

KAO08004 ’Reply to message KAO08000 was’ p1’.’Explanation: This shows the reply to the WTOR issued during a Cold Start.System Action: Cold Start Initialization continues.User Response: None.

KAO08005 ’Trap Add function to re-invoke the Schedule Driver failed. Scheduler is terminating. RC =’ p1’.’Explanation: At the end of Schedule initialization and at each subsequent event time, the Scheduler Driver issues a Trap Add command to set the time for its next wakeup. This attempt failed. The Scheduler is not able to continue processing.System Action: Scheduling component terminates.User Response: If the MAXTRAP value has been exceeded, increase this value and restart the OG/AO environment. If no other cause can be determined, contact Candle Customer Support.

KAO08006 ’Shared variable error’ p1 ’attempting to’ p2 ’variable’ p3 ’. Schedule build terminated.’Explanation: During a schedule build (either initialization or extend) an attempt to delete from, read from, or write to the shared variable pool failed for a critical value. The shared variable return code is provided. For variable deletion, a not-found condition is not an error.System Action: Schedule build (Init or Extend) is terminated.User Response: Verify that the shared variable listed was not previously deleted in error by a non-AO function. All other problems are internal and should be reported to Candle Customer Support.

KAO08007 ’Please issue the ’’RCF HELP KAO08000’’ command for more information’Explanation: The reply to the KAO08000 WTOR issued during a Cold Start was HELP. Help information in the standard format is available by issuing the above command.System Action: The KAO08000 WTOR is displayed again.User Response: Issue the RCF HELP KAO08000 command or reply to the WTOR.

KAO08009 ’Scheduler component terminating due to error(s).’Explanation: Due to errors, the scheduling component is terminating.System Action: Scheduler component terminates.User Response: Refer to the preceding and following messages.

EU001–KAO09998 87

KAO08010 ’Scheduler restarting from last known Event at’ p1’.’Explanation: This message is issued during a Warm Start and shows the date and time of the last known Scheduled Event. The Scheduler will now check for any Scheduled Starts or Stops that should have occurred since that time. The User’s Guide contains more information about Warm Start processing.System Action: Warm Start processing continues.User Response: None.

KAO08012 ’Scheduled Status will be determined from saved status information plus Scheduled Events since’ p1’.’Explanation: This message is issued during a Warm Start and shows how the Scheduled Status for each resource will be determined.System Action: Warm Start processing continues.User Response: None.

KAO08013 ’Scheduled Status will be determined from’ Scheduled Events since’ p1’.’Explanation: This message is issued during a Cold Start if the reply to the KAO08000 message is date/time. It shows how the current Scheduled Status for each Resource will be determined.Explanation: This message is issued during a Cold Start and shows how the Scheduled Status for each resource will be determined.System Action: Cold Start processing continues.User Response: None.

KAO08014 ’Scheduled Status will be determined from the current Schedule.’Explanation: This message is issued during a Cold Start if the reply to the KAO08000 message is OK. It shows how the current Scheduled Status for each Resource will be determined.System Action: Cold Start processing continues.User Response: None.

KAO08015 ’Trap Add function to invoke shared variable cleanup failed. RC =’ p1’.’Explanation: An attempt was made to add a TOD(*) trap to perform cleanup of Scheduler shared variables from previous days’ schedules. The attempt failed. Another attempt will be made after the next schedule EXTEND.System Action: The cleanup function will not be performed at this time.User Response: The failure may have occurred because the MAXTRAP value had been exceeded. If so, increase this value and restart the OG/AO environment. If no other reason can be found, contact Candle Customer Support.

KAO08016 ’Shared variable error’ p1 ’attempting to’ p2 ’variable’ p3 ’during schedule processing.’Explanation: During the normal processing of the Scheduler component, a shared variable error occurred on a critical value. The Scheduler could not continue processing.System Action: Scheduler component terminates abnormally.User Response: Verify that another process has not deleted the shared variables reserved for the Scheduler component. Contact Candle Customer Support.


KAO08017 ’Initial Scheduled Status will be determined only for Always Active Resources.’Explanation: This message is issued during a Cold Start if the reply to the KAO08000 message is NOW. A current Scheduled Status for each Resource will not be determined, but future Scheduled Events will occur normally.System Action: Cold Start processing continues.User Response: None.

KAO08018 ’Now searching Schedule definitions for last Scheduled Event for each Resource.’Explanation: This message is issued during a Cold Start if the reply to the KAO08000 message is OK. The most recent Scheduled Start or Stop will determine the current Scheduled Status for each Resource.System Action: Cold Start processing continues.User Response: None.

KAO08020 ’Schedule component EXTEND function invoked.’Explanation: The scheduling component has exhausted all events for the current calendar day and is attempting to extend the schedule through tomorrow.System Action: The scheduling component has begun to extend the schedule to tomorrow.User Response: None.

KAO08021 ’Schedule EXTEND function complete.’Explanation: The scheduling component has extended the schedule through tomorrow.System Action: Scheduling component has completed EXTEND processing.User Response: None.

KAO08023 ’Event scheduled for ’p1’ at ’p2’ has been reset.’Explanation: The RSM re-established the scheduler event trap.System Action: The Resource Manager continues with other work.User Response: None.

KAO08029 ’Schedule EXTEND ended with errors. Schedule component terminated.’Explanation: An error was detected attempting to EXTEND the schedule until tomorrow. The message reflecting that error precedes this message.System Action: The schedule could not be extended. The schedule component terminates.User Response: If the error reported can be corrected, make corrections and either REFRESH the AO250 application or terminate and re-initialize the AO250 application. Otherwise, contact Candle Customer Support.

EU001–KAO09998 89

KAO08035 ’Trap Add function to invoke resource’ p1 ’scheduling failed. RC=’ p2 ’.’Explanation: During normal scheduling, program KAORRSC5 could not be invoked to schedule events for the listed resource at this time. It is possible that the installation’s maximum number of traps has been reached.System Action: The Trap Add function to invoke resource processing fails.User Response: If the maximum number of traps (MAXTRAPS) has been reached, increase this value and restart. Manually schedule the missed events or re-initialize the AO250 environment. Other trap errors are internal failures which should be reported to Candle Customer Support.

KAO08036 ’Shared variable error’ p1 ’attempting to’ p2 ’variable’ p3 ’ during scheduling.’Explanation: During schedule processing for catch-up or normal scheduling, an attempt was made to retrieve critical values from the shared variable pool. The attempt did not succeed. The shared variable program return code is provided.System Action: No events for the time listed in the variable will be scheduled.User Response: No events at the time listed in the variable name will be scheduled. The schedule and desired attributes of any potentially affected resources will not be changed. Review the schedule for events which should have occurred at this time. Use the RCF command to make the events occur. Verify that a non-AO process did not delete the variables in error. This is an internal error. Contact Candle Support.

KAO08039 ’One or more resources failed during schedule processing for time: ’ p1’.’Explanation: During catch-up or normal scheduling processing, one or more resources could not be processed. Messages KAO05000, KAO08056, and/or KAO08350 will precede this message.System Action: Specific messages for each resource follow.User Response: Follow the instructions for the specific additional message(s) displayed.

KAO08055 ’Trap Add function to schedule an event failed. RC=’ p1 ’. Event string:’ p2Explanation: During normal schedule event processing, an attempt to add a trap for the event failed. The event represented by the string is not executed. It is possible that the system’s maximum number of traps has been exceeded.System Action: The event represented by the string is not executed.User Response: If the maximum number of traps has been exceeded, increase the MAXTRAPS option and restart the OG or AF environment. For any other reason, this error represents an internal problem. Contact Candle Customer Support.


KAO08056 ’Shared variable error’ p1 ’attempting to’ p2 ’variable’ p3 ’ during scheduling.’Explanation: During scheduling, an attempt to read from the shared variable pool failed for a critical value. The shared variable program return code is provided.System Action: Events for the resource listed in the variable name are not issued.User Response: Verify that a non-AO process is not deleting the listed shared variables in error. All other problems are internal and should be reported to Candle Customer Support.

KAO08057 ’No action because Scheduling not Enabled for Resource. Scheduled Status updated.’Explanation: A Start or Stop was Scheduled to occur but Scheduling was disabled for the Resource. The Scheduled Status has been updated and the Resource can later be brought to the required status with the command RCF SCHEDULE res YES, which enables Scheduling and brings the Resource back under Scheduler control.System Action: None.User Response: If Scheduling should be enabled, issue the command RCF SCHEDULE res YES.

KAO08058 ’’Scheduled Event:’ p1 ’for Resource’ p2’.’Explanation: A Start or Stop has occurred for Resource. This is an informational message.System Action: The Start or Stop is performed.User Response: None.

KAO08059 ’During schedule processing, one or more events for resource’ p1 ’were not processed for date/time’ p2’.’Explanation: During catch-up schedule processing, error(s) occurred in processing which prevented the SCHEDULE state of a resource from being updated. During normal schedule processing error(s) occurred in processing which prevented the SCHEDULE and/or DESIRE state of a resource from being updated or prevented the event from being issued. Previously issued messages describe the specific error(s) encountered.System Action: Events scheduled to occur at the date and time are bypassed.User Response: See the user response for the messages reflecting the specific errors.

KAO08076 ’Shared variable error’ p1 ’attempting to’ p2 ’variable’ p3 ’ during schedule cleanup.’Explanation: During a schedule variable cleanup an attempt to read from or write to the shared variable pool failed. The shared variable error code is provided.System Action: Schedule cleanup is terminated.User Response: Verify that the shared variable listed was not previously deleted in error by a non-AO function. All other problems are internal and should be reported to Candle Customer Support.

EU001–KAO09998 91

KAO08096 ’Shared variable error’ p1 ’attempting to’ p2 ’variable’ p3 ’during schedule termination.’Explanation: During schedule termination, an attempt was made to delete the listed variable. The shared variable service routine returned the error. The variable may still exist in the shared variable pool. A not-found condition is not considered an error.System Action: The variable listed may not be deleted.User Response: This is an internal product error. Contact Candle Customer Support.

KAO08100 ’Invalid function request’ p1 ’to the scheduling initialization program.’Explanation: An invalid function or service was requested of the scheduling initialization program.System Action: Scheduling initialization program terminates.User Response: This is an internal error. Contact Candle Customer Support.

KAO08101 ’No events generated for’ p1’. Dummy event generated for’ p2 ’to extend the schedule.’Explanation: During the schedule build (INIT or EXTEND) for the date indicated, no events were scheduled. A dummy event has been placed in the schedule, so that the Schedule component can awaken and extend the schedule again.System Action: A dummy event will be generated to invoke the Schedule Extend function.User Response: None.

KAO08102 ’Resource Actual Action Reason’Explanation: This is a heading line for a log message generated during a Cold Start, which documents the Actual State of each Resource, and if the Resource is Started or Stopped during Initialization, the reason for that Start or Stop (For example, previous RCF START, Scheduled Start at ....).System Action: Initialization continues.User Response: None.

KAO08103 p1Explanation: This is a data line for a log message generated during a Cold Start, which documents the Actual State of each Resource, and if the Resource is Started or Stopped during Initialization, the reason for that Start or Stop (For example, previous RCF START, Scheduled Start at ....).System Action: Initialization continues.User Response: None.

KAO08104 ’Resource Actual Sched Action Reason’Explanation: This is a heading line for a log message generated during a Warm Start, which documents the Actual State of each Resource, and if the Resource is Started or Stopped during Initialization, the reason for that Start or Stop (For example, previous RCF START, Scheduled Start at ....).System Action: Initialization continues.User Response: None.


KAO08105 p1Explanation: This is a data line for a log message generated during a Warm Start, which documents the Actual State of each Resource, and if the Resource is Started or Stopped during Initialization, the reason for that Start or Stop (For example, previous RCF START, Scheduled Start at ....).System Action: Initialization continues.User Response: None.

KAO08110 ’Schedule initialization detected an invalid profile’ p1’.’Explanation: The schedule initialization program detected an invalid profile name.System Action: Schedule initialization program terminates.User Response: This is an internal error. Contact Candle Customer Support.

KAO08200 ’Schedule Report’Explanation: This a multi-line message which lists all Scheduled Events in the currently built Schedule. When the Scheduler gets to the end of the list, it builds a Schedule for the next day. The Scheduler creates a ’Dummy Event’ if there are no Scheduled Events.System Action: None.User Response: None.

KAO08300 ’Error’ p1 ’retrieving attributes for resource:’ p2 ’for schedule build. Resource skipped.’Explanation: During schedule build (INIT and EXTEND) processing, an error was detected while attempting to retrieve information about the listed resource. The resource retrieval error code is provided. This resource’s scheduling directives are skipped.System Action: Schedule build skips this resource.User Response: This is an internal product error. Contact Candle Customer Support.

KAO08350 ’Error updating the Schedule state for resource:’ p1’. String:’ p2’.’Explanation: During schedule processing, either in catch-up or normal scheduling mode, an attempt was made to update the scheduled state attribute of the listed resource. The attempt failed with the listed error code, and the scheduled state of the resource was not updated.System Action: Resource does not reflect the correct schedule status.User Response: This is an internal error. Contact Candle Customer Support. If the error occurred during catch-up processing for a "COLD" start, the resource listed will not be put in the scheduled state. In addition, for a "WARM" start, it is possible that this event would have been issued by the restart processor if this update had succeeded. Use the string listed to issue an RCF command to perform the event manually.

EU001–KAO09998 93

KAO08355 ’Error updating the Schedule and Desire state of resource:’ p1’. String:’ p2’.’Explanation: During schedule processing, an attempt was made to update the scheduled and desired state attributes of the listed resource. The attempt failed with the listed error code, and the scheduled and desired states of the resource were not updated.System Action: Event represented by the listed string is not executed.User Response: This is an internal error. Contact Candle Customer Support. Use the string listed to issue an RCF command to perform the event manually.

KAO08500 ’Calendar termination error’ p1’. Error string:’ p2’.’Explanation: During termination processing for the scheduling component, a call to the calendar component was made for the termination function. The calendar component returned an error code and diagnostic string.System Action: Calendar function was not fully terminated.User Response: This is an internal error. Contact Candle Customer Support.

KAO08700 ’During Schedule initialization processing table’ p1 ’could not be read. Error return code:’ p2’.’Explanation: During the initialization of the schedule, the user interface tables could not be read. The error return code from the table reading program is reported.System Action: Scheduler process fails, and the scheduling component terminates.User Response: Verify that the correct table library is specified in the configuration and that the table named in the message is present. If both are valid, contact Candle Customer Support.

KAO08900 ’The Resource Manager is currently active on System(’p1’) with Subsystem(’p2’).’Explanation: During startup, KAORSTRT detected that the CACHE specified in the OG/MVS RKANPAR startup parameter, is currently in use on the current MVS system. Although the CACHE buffer is shared by multiple MVS systems, it cannot be shared within an MVS system.System Action: KAORSTRT terminates although OG/MVS remains active. Each copy of the RSM on a given MVS system, must use a unique CACHE buffer for Sysplex support. This CACHE buffer is shared by each MVS system participating in the Sysplex.

KAO08901 ’Resource Manager startup for Subsystem(’p1’) on System(’p2’) is cancelled.’"Explanation: During startup, KAORSTRT detected that an error that terminated the startup process. Generally, another message preceded this one.System Action: KAORSTRT terminates although OG/MVS remains active.User Response: Examine the message that preceded this one and then take the suggested action.


KAO09000 ’Verify’ p1 ’action to ALL resources.’Explanation: A request to START or STOP all resources has been detected. The next WTOR requests a verification of this action.System Action: Issue WTOR KAO09001.User Response: Reply to message KAO09001.

KAO09001 ’Reply Y to continue or N to abort. The default is Y.’Explanation: Verify a START or STOP of all resources.System Action: Wait for reply. The default is used after the WTOR timeout period.User Response: Reply to message. Y to continue or N to abort.

KAO09002 ’Execution of KAORRCFF accepts only one parameter.’Explanation: The user has called KAORRCFF passing more than one parameter. The only parm accepted is the name to be used for the RCF command trap.System Action: Execution of KAORRCFF ends.User Response: Correct the call to KAORRCFF.

KAO09003 ’First 8 characters of’ p1 ’used for RCF trap name.’Explanation: The call to KAORRCFF to create the RCF command trap has passed a name that is greater than 8 characters in length. The value has been truncated to 8 characters.System Action: This is a warning message.User Response: Correct the call to KAORRCFF.

KAO09004 ’Function Code Missing.’Explanation: An RCF command has been detected but no function code was entered.System Action: The RCF command terminates.User Response: Correct the RCF command and reissue.

KAO09005 ’Resource String Missing.’Explanation: An RCF command was detected, but no resource string can be found.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09006 ’Function’ p1 ’not found.’Explanation: An RCF command has been detected, but the function string is not a valid function.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09007 ’Function’ p1 ’is not unique.’Explanation: An RCF command has been detected, but the function string given matches more than one valid function.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

EU001–KAO09998 95

KAO09008 ’Value’ p1 ’is not valid.’Explanation: An RCF command has been detected. The given value is invalid.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09009 ’The RCF INITIATE must be issued first.’Explanation: An RCF command has been detected; however, the first command was not an INITIATE.System Action: RCF command ends.User Response: Issue the ’RCF INITIATE profile opt’ command to start AFX.

KAO09010 ’Requested resource’ p1 ’not found.’Explanation: The message can be issued for either of two reasons:® The named resource or group does not exist.

® The named resource or group was not defined to run on the specified SMFID.

System Action: RCF command is rejected.User Response: First of all, make sure that the specified resource name was spelled correctly on your RCF command. Secondly, make sure that the resource was defined to run on the specified SMFID. Make the necessary corrections and reissue the RCF command.

KAO09011 ’Value’ p1 ’is not unique.’Explanation: An RCF command has been detected, but the given value is not unique.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09012 ’Recursive loop detected’Explanation: While processing predecessors or successors, a recursive loop has been detected.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09013 ’Missing’ p1 ’in RCF command input.’Explanation: An RCF command has been detected which contains a mismatched parenthesis.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09014 ’Invalid use of parentheses.’Explanation: An RCF command has been detected but the use of parentheses is not clear. The RCF command requires a single set of parentheses around the activity parm string. The left and right parentheses must be in the correct order and only one set may be used.System Action: RCF command ends.User Response: Correct the RCF command and reissue.


KAO09015 ’Requested action terminated.’Explanation: A request to START or STOP all resources has been terminated by the user.System Action: RCF command ends.User Response: No response is indicated.

KAO09016 ’TRAPNAME is a required parameter.’Explanation: The required TRAPNAME parameter was not passed.System Action: KAORSTRT terminates without call to define the RCF command.User Response: Correct the execution of KAORSTRT and reissue.

KAO09017 ’OPTION must be COLD or WARM.’Explanation: The value of the initiate option must be either COLD or WARM.System Action: KAORSTRT terminates without call to define the RCF command.User Response: Correct the execution of KAORSTRT and reissue.

KAO09018 p1 ’is invalid with multiple resources.’Explanation: An RCF command has been detected for a START or STOP of multiple resources. The third parameter field is invalid. You may only request starting or stopping of predecessors or successors, request the FORCE option, or enter an Activity parm when acting on a single resource.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09019 ’CHECK OPTION(’p1’) is invalid.’Explanation: The option specified on an RCF CHECK command is invalid.System Action: RCF command is rejected.User Response: Correct the RCF command and reissue.

KAO09020 ’INITIATE OPTION (’p1’) is invalid.’Explanation: The option specified on an RCF INITIATE command is invalid. System Action: RCF command is rejected.User Response: Correct the RCF command and reissue.

KAO09021 ’Internal error calling’ p1’. Reason code=’p2’.’Explanation: An internal error has occurred while processing the RCF command. The subroutine (and function) returned the given reason code.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09022 ’Invalid number of parameters for RS’ p1 ’request.’Explanation: The RCF command process has passed an invalid number of parameters to KAORRRSF for the given request.System Action: RCF command ends.User Response: Contact Candle Customer Support.

EU001–KAO09998 97

KAO09023 ’Resource list is unavailable for RS’ p1 ’request.’Explanation: RCF has made the given request of the RS service. The system resource list is unavailable.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09024 ’Invalid resource’ p2 ’passed to RS’ p1 ’request.’Explanation: The RCF command process has passed an invalid resource name to the given RS request.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09025 ’Invalid field name’ p2 ’passed to RS’ p1 ’request.’Explanation: The RCF command process passed an invalid field name to the given RS request. System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09026 ’Resource list not initialized.’Explanation: The RCF command process has requested a list of resources, but the list has not been initialized or is not available.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09027 ’Check exit’ p1 ’returned’ p2 ’for resource’ p3’.’Explanation: An RCF command has been detected for CHECK. The user’s check exit has returned a value other than START or STOP.System Action: RCF command continues.User Response: Correct the check exit and reissue the RCF command.

KAO09028 ’Resource’ p1 ’internal error processing PREDS/SUCCS in EQ.’Explanation: An RCF command has been detected that needs predecessors or successors, and an internal error has occurred in the EQ service.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09029 p1 ’for variable=’p3 ’ended with RC=’p2’.’Explanation: The RCF command process has encountered an error with shared variables. The requested function returned the given return code when acting on the given variable.System Action: RCF command ends.User Response: Contact Candle Customer Support.

KAO09030 ’Invalid use of quote in column’ p1’.’Explanation: An RCF command has been detected that uses a quote outside of parentheses.System Action: RCF command ends.User Response: Correct the RCF command and reissue.


KAO09031 ’Profile=’p1 ’not found in profile table.’Explanation: The given profile can not be found in the profile table. Either the profile has not been defined, or the profile table is empty.System Action: RCF command ends.User Response: Define the profile and reissue the RCF command.

KAO09032 ’Profile=’p1 ’is not valid for TERM or REFRESH.’Explanation: An RCF command has been detected to TERMINATE or REFRESH a profile which is not the profile that has been INITIATED.System Action: RCF command ends.User Response: Correct the RCF command and reissue.

KAO09033 ’System draining. Only RCF command allowed is REFRESH profile FORCE.’Explanation: An RCF command has been detected while the system is being drained. The only command allowed at this time is REFRESH profile FORCE.System Action: RCF command ends.User Response: Wait for the DRAIN to finish or issue REFRESH profile FORCE if the draining condition continues.

KAO09034 p1 ’action cancelled for’ p2 ’because of recovery failure.’Explanation: An RCF command has been detected for SCHEDULE, ACTIVATE, INACTIVATE, or RECOVERY. This action could not be performed because an unrecoverable condition has occurred in recovery that has set the value of scheduling and recovery.System Action: RCF command continues to operate.User Response: Correct the problem with the user CHECK exit and use the ’RECOVERY resource RESET’ command to restore scheduling and recovery processing.

KAO09035 ’CHECK processing for resource’ p1 ’bypassed.’Explanation: An RCF CHECK command has been detected. The given resource is bypassed because an error has been detected in the user check exit.System Action: RCF command continues.User Response: Correct the check exit problem or add the proper library to AOCMDLIB and refresh the system.

KAO09036 p1 ’action not taken for’ p2 ’because the resource is locked.’Explanation: An RCF command has been detected to START or STOP resource. The action has been bypassed for the given resource as it is locked. This can occur if the resource is currently waiting for a reply to a start warning message.System Action: RCF continue to execute.User Response: If a wto is outstanding, reply to it and then reissue the command. If no wto is outstanding reissue the command. If the problem persists contact Candle Customer Support.

EU001–KAO09998 99

KAO09037 ’Could not access’ p2’.’ p1 ’action not taken.’Explanation: A request to START or STOP the given resource could not be taken as the resource could not be accessed.System Action: RCF command continue to run.User Response: Verify this is a valid resource for the current system. This may occur when trying to take action on a resource and it preds/succs if the predecessor is not defined on the current system. This is a warning message only.

KAO09038 ’Invalid number of parameters on KAORSTRT. RCF trap not added.’Explanation: An incorrect number of parameters was specified on the call to function KAORSTRT. The correct format is: KAORSTRT ds_name rcf_command profile COLD|WARM. Where "ds_name" is the definition PDS data set name that is populated by the user interface. "rcf_command" is the user chosen spelling for the RCF command and "profile" and "COLD|WARM" are optional parameters used to initiate the product from KAORSTRT.System Action: An incorrect number of parameters was specified on the KAORSTRT cmd.User Response: Correct the parameters on the call to KAORSTRT and re-execute the exec that calls KAORSTRT.

KAO09039 ’Profile table is from a previous version of the product.’Explanation: The Profile Table was created by an early release of AO250 which did not provide a version stamp for each table.System Action: Processing terminates.User Response: If you received an early (pre-GA) release of AO250, then run the supplied conversion utility. Otherwise, please contact Candle.

KAO09040 ’SET:’ p1 ’setting is already’ p2’.’Explanation: The SET command was issued to change the value of a Global Preference, but it was already set to that value.System Action: None.User Response: None.

KAO09041 ’SET:’ p1 ’setting changed to’ p2’.’Explanation: The SET command was issued to change the value of a Global Preference, and it has been changed successfully. This setting will remain until the next Warm or Cold Start.System Action: Global Preference setting changed.User Response: None.

KAO09042 ’SET: Error changing’ p1 ’setting.’Explanation: The SET command was issued to change the value of a Global Preference, but the action could not be completed.System Action: Global Preference setting not changed.User Response: Check Msglog.


KAO09043 ’SET:’ p1 ’is not a valid option for’ p2’.’Explanation: The SET command was issued to change the value of a Global Preference, but the Global Preference or the new value is not valid.System Action: Global Preference setting not changed.User Response: Check Msglog.

KAO09044 ’Global Preference Report’Explanation: This is an MLWTO which lists the current Global Preference settings.System Action: None.User Response: None.

KAO09045 p1 ’Option must be included’Explanation: An RCF command was issued, and one of the required options was missing from the command.System Action: RCF command is not executed.User Response: Check command format and reissue.

KAO09046 ’Profile or Sysplex Name is missing or invalid.’Explanation: An RCF INIT command was issued, but the specified profile or sysplex name cannot be located.System Action: RCF command is rejected.User Response: Make sure that the profile or sysplex named in the RCF command has been defined. Correct the RCF command and reissue.

KAO09047 ’SMFID is missing or invalid.’Explanation: This message can be issued for any of the following reasons:® An RCF INITIATE command was issued for a sysplex that was not defined to

run on the specified SMFID.

® An RCF command (other than INITIATE) was issued for an SMFID not defined for the active sysplex.

System Action: RCF command is rejected.User Response: Examine the sysplex definition with the User Interface to determine the SMFID names that were defined. Then reissue the RCF command with the proper SMFID. If you wish to direct the RCF command to all MVS systems defined in the sysplex, specify SMFID=*.

Note: You must define all smfids through the user interface prior to starting the RSM via KAORSTRT.

KAO09048 ’Resource/Group name(’p1’) is invalid.’Explanation: No resources were selected for the group or resource name mask supplied in the RCF command.System Action: RCF command is rejected.User Response: Specify the correct resource or group name and reissue the RCF command.

EU001–KAO09998 101

KAO09049 ’Function ’p1’ Failed with return code (’p2’).’Explanation: This is an internal error condition in the RSM.System Action: RSM attempts to continue.User Response: Call Candle and please provide the function and return code from this message.

KAO09050 ’Error reading System Definition table KAOKXSYT.’Explanation: This is an internal error condition in the RSM.System Action: RSM attempts to continue.User Response: Call Candle and please provide the full text of this message.

KAO09051 ’Error retrieving System Definition table variables.’Explanation: This is an internal error.System Action: RSM attempts to continue.User Response: Call Candle and please provide the full text of this message.

KAO09052 ’The SMFID for this system (’p1’) has not been defined in the System Definition table.’"Explanation: The specified SMFID was not defined through the user interface (option 6).System Action: Request is rejected.User Response: If the specified SMFID is supposed to be valid, then you must enter a system definition in the user interface (option 6). Once this has been done, you can use it.

KAO09053 ’Error (’p1’) occurred while attempting to start a session with linkid (’p2’).’Explanation: An XCF LINK START failed for the specified linkid. The return code (p1) indicates the reason for the failure.System Action: The link is not established.User Response: Please refer to the AF/OPERATOR Command Reference Manual section on the LINK START command for an explanation on of the various return codes you might receive.

KAO09054 ’Error (’p1’) occurred while sending ’p2’ command to linkid (’p3’).’Explanation: An XCF COMSDRCV failed for the specified linkid. The return code (p1) indicates the reason for the failure.System Action: The COMSDRCV did may not have completed successfully.User Response: Please refer to the AF/OPERATOR Command Reference Manual section on the COMSDRCV command for an explanation on of the various return codes you might receive.


KAO09055 ’Could not locate an XCF linkid for smfid(’p1’).Explanation: This indicates an internal error in the RSM.System Action: The XCF request is not completed.User Response: During the RSM startup (KAORSTRT), XCF links are established for the various smfids defined in the system definitions through the User Interface.

Note: It is important to remember that all system definitions must be present when you start the RSM via KAORSTRT, you cannot add them after the RSM is active. In most cases, you will receive the KAO09047 message instead of KAO09055.

KAO09056 ’Another profile named (’p1’) is currently active on (’p2’) INITIATE rejected.’Explanation: Another profile (p1) is already active on the SMFID where you are trying to INITIATE profile named (p2).System Action: RCF command is rejected.User Response: Terminate profile name (p1) on the SMFID and then reissue the RCF INITIATE command.

KAO09057 ’PLEX= cannot be specified because Sysplex is not supported on the current MVS system.’Explanation: The current SMFID does not support sysplex, thus, you cannot use the PLEX= keyword to INITIATE a sysplex.System Action: RCF command is rejected.User Response: None.

KAO09058 ’SMFID option ignored without Sysplex support.’Explanation: You cannot specify the SMFID keyword on an RCF command without Sysplex support.System Action: RCF command is rejected.User Response: None.

KAO09059 ’Sysplex name (’p1’) not found in Sysplex Definition Table.’" Explanation: An "RCF INIT PLEX=plexname" command was issued for a Sysplex name (plexname) that was not defined through the user interface.System Action: RCF command is rejected.User Response: If the plexname was specified incorrectly, then make the required correction and reissue the RCF command. If the plexname was specified correctly, then it was not defined with the user interface. Thus, you must define the Sysplex entry through the user interface (option 8).

KAO09060 ’Error (’p1’) while reading table named (’p2’).’Explanation: An error was detected while reading the named (p2) table.System Action: The function named in the message text terminates abnormally.User Response: Call Candle and please provide the entire text of the message.

EU001–KAO09998 103

KAO09061 ’Error (’p1’) while reading ROW/COL variable.’Explanation: An error was detected while reading the named (p2) table.System Action: The function named in the message text terminates abnormally.User Response: Call Candle and please provide the entire text of the message.

KAO09062 ’SMFID requires a Sysplex (PLEX=) specification.’Explanation: An RCF INITIATE command was issued with an SMFID and without a PLEX=plexname specification.System Action: The RCF command is rejected.User Response: Correct the RCF command and reissue.

KAO09063 ’No profile is currently active - ’p1’ command rejected.’Explanation: An RCF REFRESH or RCF TERMINATE command was issued without a profile having been initiated.System Action: The RCF command is rejected.User Response: You cannot issue a REFRESH or TERMINATE without an active profile (for example, an RCF INITIATE must be issued first).

KAO09064 ’Profile (’p1’) specified on REFRESH/TERMINATE does not match the current active profile named (’p2’).’"Explanation: An RCF REFRESH or RCF TERMINATE command was issued with a profile name that does not match the current active (p2) profile.System Action: The RCF command is rejected.User Response: You can reissue the REFRESH or TERMINATE with the current active profile (p2) name, or *.

KAO09065 ’SMFID ignored for REFRESH or TERMINATE because profile name ’p1’ not INITIATED within a Sysplex.’Explanation: An RCF REFRESH or RCF TERMINATE command was issued with an SMFID, and the profile was not initiated with the PLEX= keyword.System Action: The RCF command is rejected.User Response: You can reissue the REFRESH or TERMINATE command without the SMFID keyword.

KAO09066 'The PLEX= keyword is restricted to the INITIATE' command.’' Explanation: Only the RCF INITIATE command can use the PLEX=keyword. System Action: The RCF command is rejected.User Response: Reissue the RCF command without the PLEX= keyword.

KAO09067 'Errors detected while trying to load global' preference table.'"Explanation: An error occurred while trying to load the global preference table.System Action: The requesting function fails.User Response: Call Candle and please provide the full text of this message.


KAO09068 ’SHARVGET error (’p1’) while reading ’p2’ variables.’Explanation: An internal error occurred.System Action: The requesting function fails.User Response: Call Candle and please provide the full text of this message.

KAO09069 ’ABOVE and BELOW cannot be specified together because’ they are conflicting.’"Explanation: You cannot specify ABOVE and BELOW on the same RCF command. System Action: The RCF command is rejected.User Response: Correct the RCF command and then reissue.

KAO09070 ’Trap Group Action’ p1 ’is missing or invalid.’Explanation: The trap group action (p1) specified is invalid.System Action: The RCF command is rejected.User Response: Correct the RCF command and then reissue.

KAO09071 ’Cannot lock the resource wait queue.’Explanation: An internal error was detected.System Action: The requesting function fails.User Response: Call Candle and please provide the full text of this message.

KAO09072 ’SHARVPUT error (’p1’) while writing ’p2’ variables.’Explanation: An internal error occurred.System Action: The requesting function fails.User Response: Call Candle and please provide the full text of this message.

KAO09073 ’Resource name (’p1’) is under control of the ARM, ’ request ignored.’"Explanation: Certain RCF commands cannot be issued for a resource currently under ARM control.System Action: The RCF command is rejected.User Response: If the resource is under ARM control, then you cannot issue the RCF command that was rejected unless you issue an RCF RESET first. However, you should exercise caution when doing this, as you might start working at cross purposes with the ARM, and the results could be unpredictable.

KAO09074 ’INITIATE or REFRESH already in-progress’Explanation: An INITIATE or REFRESH command is currently running, thus, the current request is rejected.System Action: The RCF command is rejected.User Response: None.

EU001–KAO09998 105

KAO09075 The RKANISP table (xxxx) is active.Explanation: This message is issued in conjunction with the KAO09076 message, whenever an RCF INIT PLEX= command is issued and the RSM detects that the XCF data structure is still actively using the xxxx version of RKANISP.

Note: This condition can occur when all copies of a plexname profile were not terminated properly on every MVS system participating in the sysplex, and KAORSTRT is started with a different (yyyy) RKANISP table.

System Action: The RCF INITIATE command is rejected.User Response: You have one of the following three choices:® Proceed with the new RKANISP table by resubmitting the RCF command as

follows:

RCF INIT PLEX=plexname COLD S=*

This will initialize the plexname profile on every MVS system named in the sysplex, using the yyyy version of the RKANISP named in the KAO09076 message.

® Resubmit the RCF command as follows:

RCF INIT profile COLD

This will initialize the named profile from the new RKANISP (yyyy) table on the local MVS system only, without using the sysplex.

® Terminate AF/OPERATOR and then restart KAORSTRT with the previous (xxxx) RKANISP table.

KAO09076 New RKANISP table (yyyy) cannot be used.Explanation: This message is always issued in conjunction with message KAO09075.System Action: See message KAO09075 for details.User Response: See message KAO09075 for details.

KAO09077 ’Data version xx not compatible with data version yy found on ssss - request terminated.’Explanation: Internal control data compatibility issues exist between various active versions of the RSM. Version xx pertains to the data version of the AF/OPERATOR issuing the message. Version yy pertains to the data version found on the AF/OPERATOR running on the ssss system. All AF/OPERATOR systems intended to share the same active profile (for example, RCF INIT PLEX=plexname) must be at the same maintenance level in terms of data compatibility. AO320 and AO340 are not run-time data compatibile.If yy or ssss contain question (??) marks, this indicates the presence of an AO320 system not possessing data compatibility information.


System Action: The request is rejected.User Response: Each user-defined Sysplex group must be at the same AO320 or AO340 maintenance level in terms of data compatibility. For example, GROUPA might consist of AO320 running on SYSA and SYSB, and GROUPB might consist of AO340 running on SYSC and SYSD.You might consider running your AO340 profile in system mode (for example, RCF INIT profname), thus restricting its affect to a single MVS system.

KAO09800 ’Resource Status Report’Explanation: This is an MLWTO which lists information about Resources controlled by the Resource Manager.System Action: None.User Response: None.

KAO09801 ’Response to RCF HELP Command’Explanation: This is an MLWTO which displays Help information.System Action: None.User Response: None.

KAO09998 ’A Serious Problem Occurred During Message Processing - Please Check AO Msglog (KAORHMSG)’Explanation: The Resource Manager attempted to issue a message and encountered an error in the process. The AO message log should contain one of the following explanations:

Unable to find message variablesInvalid Message Type detectedSHARVGET failed for Message Destination valueWTO/LOGMSG command failedSHARVGET failed for Global TPUT variableDefault reply was not specified for WTORSHARVGET failed for Global WTOR Timeout variableWTOR command failedSHARVPUT failed for message variables in KAOMSGTBSHARVPUT failed for MessageLoaded variableSHARVPUT failed for newly created message

System Action: The Resource Manager cannot issue the requested message and processing continues.User Response: Contact Candle Customer Support, and be sure to provide the AO message log explanation text.

KAT0001E–KCFCM091E 107

KAT0001E–KCFCM091E

KAT0001E ’ADDRESS command failed for OMEGAMON system’ p1 ’Return code:’ p2Explanation: The AF ADDRESS command failed to access the OMEGAMON system.System Action: The module which issued the message is terminated.User Response: Examine the RKOGLOGM to determine why the OMEGAMON system is not available.

KAT0001I ’No response to Incident’ p1 ’Escalation completed’Explanation: The end of the escalation chain has been reached by the notify program, and all users in the list have been notified.System Action: The Notify program continues; no action is taken.User Response: None. This is an informational message only.

KAT0001W msgparmsExplanation: This message indicates that an invalid parameter has been passed to the module issuing the message.System Action: Processing continues.User Response: None. This is a warning message only.

KAT0002E ’Invalid argument string:’ p1Explanation: The system variable name is invalid.System Action: The program terminates.User Response: Look for more messages in the RKOGLOGM.

KAT0002W ’Status item’ p1 ’is not numeric. Current value:’ p2Explanation: The status item text field must be numeric for the specified status item.System Action: The program terminates.User Response: Examine the probe and, if appropriate, the data manager which update the status item value to determine the cause of the incorrect value.

KAT0003E ’Log Routine failure for Probe:’ p1 ’Return code:’ p2Explanation: The program was unable to write to the OSM/MVS log.System Action: The program terminates.User Response: Examine the RKOGLOGM to determine the cause of the log file failure. Correct the problem and run the program again. If the problem persists, call Candle Customer Support.

2


KAT0003I ’More than 24 problems encountered in OSM/MVS’Explanation: OSM/MVS allows for only 24 problems to be managed on the OSM/MVS exception and worklog panels of OMEGAVIEW. This limit has been exceeded, and the remaining problems are ignored.System Action: Processing continues.User Response: None. This is an informational message only.

KAT0004E ’OSM/MVS Data Manager:’ p1 ’failed.’Explanation: The Data Manager program encountered a problem which caused it to be terminated.System Action: The Data Manager program terminates.User Response: Examine the RKOGLOGM for messages from the same match to determine the cause of the problem.

KAT0004I ’Data manager’ module ’starts at --’ p1 ’and ends at --’ p2Explanation: The message shows the start and end times for a data manager program.System Action: Processing continues.User Response: None. This is an informational message only. The start and end times can be used to determine response from the OMEGAMON systems which the specified data manager supports.

KAT0005I ’OMEGAMON/CICS RTA collector not active’Explanation: The OMEGAMON/CICS Response Time Analyzer has not been configured on the OMEGAMON system being used by the Data Manager which issued the message. Consequently, no RTA data is collected.System Action: The RTA data is not collected. Processing continues.User Response: Issue the SHOW LOGONS command to determine which OMEGAMON/CICS is being used by the Data Manager. Configure that system for the RTA data that the Data Manager requires.

KAT0006E ’Follow-up routine’ p1 ’failure for status item:’ p2 ’Return Code:’ p3Explanation: The follow-up routine has been executed, because the status item has changed color, and the routine ended with a non-zero return code.System Action: Processing continues.User Response: Examine the RKOGLOGM for any messages which may have been issued by the follow-up routine.

KAT0006I ’Starting’ p1 ’List initialization’Explanation: The Work List or Exception List manager is initializing the OMEGAVIEW panels.System Action: Processing continues.User Response: None. This is an information only message.


KAT0007E ’Notify routine failure for Status Item:’ p1 ’Return code:’ p2Explanation: The system notify routine has been invoked for the status item, and it has ended with a non-zero return code.System Action: Processing continues.User Response: Examine the RKOGLOGM to determine the reason for the routine’s failure.

KAT0007I p1 ’List initialization is complete’Explanation: The Work List or Exception List manager has initialized the OMEGAVIEW panels.System Action: Processing continues.User Response: None. This is an information only message.

KAT0008E ’Recommend routine failure for Status Item:’ p1 ’Return code:’ p2Explanation: The recommend routine was invoked because the status item has changed color. The routine ended with a non-zero return code.System Action: Processing continues.User Response: Examine the RKOGLOGM to determine the cause of the recommend routine’s failure.

KAT0008I ’Please respond to Incident’ p1 ’Probe’ p2 ’Status Item’ p3Explanation: The notify program issues this message when a status changes and the activity requests that Notification Text be sent. It will contain the Incident Number or "Non-Incident Notify", depending on whether the activity requires an Incident to be created or not.System Action: Processing continues.User Response: For an Incident notification, use the Receive function of OSM/MVS to respond to the notification, prevent further escalation, and begin work on the problem. Use the Resolve function to remove the Incident from the system when the problem has been corrected. For a Non-Incident Notification, no response is necessary, but be aware of the Notification Text sent along with this message.

KAT0009E ’OSM/MVS Activity manager failure for status item:’ p1 ’Return code:’ p2Explanation: An error occurred while processing the activities for the status item.System Action: Processing continues with the next status item for the probe.User Response: Examine the RKOGLOGM to determine the cause of the activity failure.

KAT0009I ’Escalation for Incident’ p1 ’was successful’Explanation: The OSM/MVS Notify Escalation routine has successfully escalated the problem to the next level.System Action: Processing continues.User Response: None. This is an information only message.


KAT0010E ’Action routine failure for status item:’ p1 ’Return code:’ p2Explanation: The action routine has been invoked because the status item has changed color. The routine ended with a non-zero return code.System Action: Processing continues.User Response: Examine the RKOGLOGM to determine the cause of the action routine’s failure.

KAT0010I ’Cannot find Incident on Active Status Items’ p1 ’Status Item:’ p2Explanation: The OSM/MVS Notification Incident Resolution program has found that the incident is not on the user’s incident list.System Action: Processing continues.User Response: None. This is an information only message.

KAT0011E ’Worklist and Exception list manager has failed for panel:’ p3 ’ Probe:’ p1 ’Return code:’ p2Explanation: The list manager has encountered a program error.System Action: Processing continues.User Response: Examine the RKOGLOGM for messages which were issued by the list manager. Call Candle Customer Support.

KAT0011I p1 ’OMEGACENTER Status Manager for MVS’Explanation: The OSM/MVS process (start, stop or full refresh) has begun.System Action: Processing continues.User Response: None. This is an information only message.

KAT0012I ’************* OSM/MVS Statistical Summary *************’Explanation: This is a header message that precedes the statistical summary for the OSM/MVS startup, shutdown, and refresh functions.System Action: Processing continues.User Response: None. This is an information only message.

KAT0013I ’* ---------------------------------------------’Explanation: This message forms part of the OSM/MVS startup or shutdown summary.System Action: Processing continues.User Response: None. This is an informational message.

KAT0014E ’Logging routine is unable to write to log file:’ p1 ’Return code:’ p2Explanation: The OSM/MVS logging routine received an error from the WRITE command.System Action: The log record is discarded and the logging routine is cancelled.User Response: Make sure the log file is open. Examine the RKOGLOGM for related messages.


KAT0014I ’OSM/MVS’ p1 ’completed successfully’Explanation: The OSM/MVS process (startup, refresh, or shutdown) has completed successfully.System Action: Processing continues.User Response: None. This is an information only message.

KAT0015E ’System variable SYSVPUT of’ p1 ’failed’Explanation: The REXX SYSVPUT function was not able to put the named variable in the system variable pool.System Action: The module which issued the message is cancelled.User Response: There may be a problem with the name of the variable. If that is not the case, call Candle Customer Support.

KAT0015I ’OG/OS2 Console’ p1 ’is not active’Explanation: The console that has been defined to OSM/MVS as a gateway to distributed OSM systems is not active and could not be varied online.System Action: Processing continues.User Response: Examine the system log to determine the reason why the console could not be activated. Rectify the problem and vary the console online manually.

KAT0016E ’Logging routine is unable to allocate log file:’ p1 ’,’ p2 ’Return code:’ p3Explanation: The ALLOCATE command failed for the specified OSM/MVS log.System Action: The OSM/MVS log is not allocated, and the routine is cancelled.User Response: Investigate the reason for the allocation failure.

KAT0016I ’Probe’ p1 p2 p3 ’ignored. Unknown Probe Type’ p4Explanation: The probe has been ignored, because the probe type is not valid. This may be caused by invalid data in the OSM/MVS ISPF tables.System Action: Processing continues.User Response: Examine the OSM/MVS probe definition and correct the probe type.

KAT0017E ’Logging routine is unable to’ p1 ’log file:’ p2 ’Return code:’ p3Explanation: The OPEN, CLOSE, or FREE command failed for the specified OSM/MVS log file.System Action: The routine is cancelled.User Response: Investigate the cause of the command failure.

KAT0017I ’Initialization Probe’ p1 ’executed. Return code:’ p2Explanation: The initialization probe (probe type ’A’) has been invoked by the OSM/MVS startup routine.System Action: Processing continues.User Response: This is an informational message. Examine the return codes for the probe to determine whether the return code indicates an error.


KAT0018I ’Event Probe’ p1 ’executed, Return Code:’ p2Explanation: An Event has triggered the execution of an "Event" probe. The return code is displayed to aid in diagnostics if necessary.System Action: Processing continuesUser Response: This is an informational message, no response is necessary. However, if the probe fails, check the return code.

KAT0019I ’OMEGAVIEW Probe’ p1 ’executed, Return Code:’ p2Explanation: An OMEGAVIEW Probe was executed, during OSM/MVS startup or refresh, and the return code is being displayed.System Action: Processing continues.User Response: No response is required. However, if the return code is not zero, the reason should be investigated.

KAT0020I ’*************** Notification Refresh Summary *************’Explanation: A header line for statistics detailing the results of a Notification Refresh request.System Action: Processing continues.User Response: No response is necessary.

KAT0021E ’Log process stopped, due to error.’Explanation: An error occurred during OSM/MVS logging procedures. Messages destined to go to an OSM/MVS log were not written.System Action: System has halted logging, other processing continues.User Response: Check the OSM/MVS started task logs for additional information. The problem must be resolved before logging can continue.

KAT0021I ’Notification System Refresh is complete’Explanation: The requested Notification Refresh has completed.System Action: Processing continues.User Response: This is an informational message, no response is necessary.

KAT0022E ’OMEGAVIEW access function’ p1 ’failed for’ p2 ’ Return Code:’ p3Explanation: An error occurred while OSM/MVS was preparing to update an OMEGAVIEW Status Item.System Action: Processing continues, but an update to OMEGAVIEW has failed.User Response: Check the return code and additional messages to determine the problem.

KAT0024I ’*******************************************************’Explanation: This is simply a line used for formatting and separating messages.System Action: Processing continues.User Response: No response is necessary.


KAT0025E ’** OMEGAVIEW Update failed for’ p1 ’ Return Code:’ p2Explanation: An error occurred during an update to OMEGAVIEW. The Probe ID and return code are displayed.System Action: Processing continues, but an update to OMEGAVIEW has failed.User Response: Check the Log datasets for additional information about the failure. OMEGAVIEW might be unavailable, or some system information may be missing.

KAT0025I ’OSM/MVS Recommendation:’Explanation: A Status Item has changed to a status whose activity specifies that a recommend message should be sent to the operators. This is the header message preceding the actual recommend message text.System Action: Processing continues.User Response: Read the following recommend message.

KAT0026E ’System Variable’ p1 ’not found, Return Code: ’ p2Explanation: An error occurred while attempting to access a system variable. The return code will add further information.System Action: Program processing terminates.User Response: Determine if the problem can be resolved by your actions. If you cannot determine the cause of the problem, or you cannot resolve it, restart OSM/MVS.

KAT0026I ’Probe:’ p1 ’Status Item:’ p2Explanation: Identifier for the source of a recommend message. This message appears on each recommend message after the header line. It indicates the Probe ID and Status Item which requested the recommend message.System Action: Processing continues.User Response: Read the messages containing the recommend message.

KAT0027I p1Explanation: This message contains the Notification Text specified on an activity record. The content of the message is user defined.System Action: Processing continues.User Response: Response is dependent on the message text and the circumstances of the Notification Message.

KAT0028E ’Password returned -1 from OMEGAMON Signon.’Explanation: An error occurred while signing on to OMEGAMON.System Action: Processing terminates; no connection to OMEGAMON was established.User Response: Check OMEGAMON availability and that the proper password was specified for OSM/MVS to sign on to OMEGAMON.


KAT0028I ’Notification previously issued for Probe:’ p1 ’Status Item:’ p2Explanation: This message indicates that an incident currently exists for this probe and status item, but the status for this status item has changed again and requested notification. This message will only be issued if the Incident Priority for this Status Item/Activity is not "Always Notify".System Action: Processing continues.User Response: No response is necessary, this is only an informational message to aid in incident resolution.

KAT0029E ’** OSM/MVS OMEGAMON logon for’ p1 ’failed **’Explanation: An error occurred when OSM/MVS was attempting to sign on to OMEGAMON. The VTAM name of the OMEGAMON is displayed to aid in error determination.System Action: Processing terminates, and connection to OMEGAMON is not established.User Response: This message may be accompanied by other messages to aid in problem determination. Use this information to determine why OSM/MVS could not log on to OMEGAMON.

KAT0030E ’Cannot LOGON to’ p1 p2 p3 p4Explanation: An error occurred while logging on to the specified VTAM application. The VTAM name, user ID, and return code is displayed. This message may be accompanied by other messages to aid in problem determination.System Action: Processing continues, OSM/MVS has not logged on to specified VTAM ID.User Response: Read any accompanying messages to determine why OSM/MVS could not log on to the specified VTAM ID. A trap has been created to try the logon again every 5 minutes, until the logon is successful.

KAT0030I ’Notification Initialization in progress. Check Log’ ’for Status Item: ’ p1Explanation: A Status Item has changed to a status that requests notification. However, the notification processes have not fully initialized. The message directs the user to the Notification Log for the status item, where the complete Notification Message is preserved.System Action: Processing continues, notification initialization continues.User Response: Browse the Notification Log for this system. Notification information is recorded there for this Status Item.

KAT0031E ’OMEGAVIEW panel’ p1 ’is locked. Update failed’Explanation: A Work List, Exception List, or the Notify OMEGAVIEW screen is locked by another process. An update to the specified screen has failed.System Action: Processing continues.User Response: The lock should resolve itself. If the lock is not resolved within a few minutes, then restart OSM/MVS.


KAT0032I ’Re-Notification for Incident ’p1’ is successful’Explanation: Notification was requested for a status item that already has an active incident. However, the incident priority was specified as "Always Notify", so another Notification Message was sent to the current member of the "Notification Chain" associated to this incident.System Action: Processing continues.User Response: No response is necessary. The message was issued only to aid in incident resolution.

KAT0033E ’** Recommendation for Probe:’ p1 ’failed. Return Code:’ p2Explanation: An error occurred while OSM/MVS was trying to send recommend messages to the Operator. Additional messages may accompany this message.System Action: Processing continues, but a recommendation message has failed.User Response: Review any accompanying messages and the return code specified to determine the cause of the failure.

KAT0033I ’Non-Incident Notification for ’p1’ is successful’Explanation: A Notification Message has been sent for a status item/activity that specifies not to create an incident.System Action: Processing continues.User Response: No response is necessary. This is only an informational message.

KAT0034E ’OSM/MVS Spikes Routine Failure for’ p1 ’Return code:’ p2Explanation: An error occurred during the evaluation of spike specifications for this status item.System Action: Processing continues, but evaluation of this status item has failed.User Response: Review the spike specifications entered for this status item. If the specification is correct, contact Candle Customer Support.

KAT0034I ’OMEGAVIEW Notification Initialization is complete’Explanation: The Notification Panel on OMEGAVIEW has successfully initialized.System Action: Processing continues.User Response: This is an informational message. No response is necessary.

KAT0035E ’Status Item’ p1 ’has invalid spike periods’ p2Explanation: The number of spike periods is not a whole number. The spike periods must be entered as a whole number using the ISPF interface.System Action: Processing continues.User Response: Using the ISPF interface, change the number of spike periods to a whole number. Then refresh the status item to update the running OSM/MVS system.


KAT0035I msgparmsExplanation: This message contains the Recommend Text as entered on the Recommend panel and specified on an activity record; or this message contains a Log message when the Log code for this status item or activity specifies the message to be routed to the Syslog.System Action: Processing continues.User Response: User response is dependent on the content of the message.

KAT0036I ’* Total table records read:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0037E ’OSM/MVS Status is incorrect for’ p1 ’Expected value:’ p2 ’Current value’ p3 p4 p5Explanation: The OSM/MVS startup or shutdown program cannot continue, because the status of the system is incorrect. For startup to occur, the status must be NO. For shutdown to occur, the status must be YES. This error may be caused by attempting to start or stop OSM/MVS while a start or stop program is in progress.System Action: The program terminates with an error code.User Response: Check the value of the @ACCRUN system variable. If its value is incorrect for the startup or shutdown, you should investigate the cause by examining the RKOGLOGM before running the program again.

KAT0037I ’* VTAM Application Records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0038E ’OSM/MVS Status has been changed since’ p1 ’began. Expected value =’ p2 ’Current value =’ p3Explanation: @ACCRUN value has been changed since startup began.System Action: OSM/MVS System startup/refresh is terminated.User Response: Examine why the value of @ACCRUN changed after OSM/MVS startup, then you can manually change the value back and start the system again.

KAT0038I ’* *** Status Item related records ***’Explanation: This message forms part of the OSM/MVS record summary which is displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.


KAT0039E ’Error from ISPF Table read, Return code:’ p1Explanation: An error has occurred during the ISPF Table reading.System Action: OSM/MVS System startup/refresh is terminated.User Response: Check the return code and the availability of the ISPF table, then try again.

KAT0039I ’* Total ===>’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0040I ’* Status Item records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0041I ’* Activity (Status None) records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0042E ’Log Start failure for Log Code’ p1 ’,Return code:’ p2Explanation: An error occurred during OSM/MVS logging procedures.System Action: The routine is cancelled.User Response: Investigate the cause of the command failure.

KAT0042I ’* Activity (Status OK) records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0043E ’Error Writing to Log, Log Code’ p1 ’,Return code:’ p2Explanation: An error occurred during OSM/MVS logging procedures. Messages destined to go to an OSM/MVS log were not written.System Action: The routine is cancelled.User Response: Investigate the cause of the command failure.

KAT0043I ’* Activity (Status Warning) records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.


KAT0044I ’* Activity (Status Critical) records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0045I ’* DAS records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0046I ’* Situation records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0047E ’DD name:’ p1 ’DSN:’ p2 ’free error, Return code:’ p3Explanation: An error occurred while ISPF tried to free an allocated dataset.System Action: The program is terminated.User Response: Check the RKOGLOGM and the system log for more messages, then contact Candle Customer Support.

KAT0047I ’* Recommend records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0048E ’DD name:’ p1 ’DSN:’ p2 ’allocate error, Return code:’ p3Explanation: An error occurred while ISPF tried to allocate a specified dataset.System Action: The routine is cancelled.User Response: Check the RKOGLOGM and the system log for more messages. Make sure that no one has exclusive use of the file.

KAT0048I ’* Notify Group User rows:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0049E ’DD name:’ p1 ’DSN:’ p2 ’open error, Return code:’ p3Explanation: An error occurred while ISPF tried to open an allocated dataset.System Action: The routine is cancelled.User Response: Check the RKOGLOGM and the system log for more messages. Contact Candle Customer Support if necessary.


KAT0049I ’* Notify Users:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0050E ’DD name:’ p1 ’DSN:’ p2 ’read error, Return code:’ p3Explanation: An error occurred while ISPF tried to read a specified file.System Action: The program is terminated.User Response: Check the RKOGLOGM and the system log for more messages. Contact Candle Customer Support if necessary.

KAT0050I ’* Rotation Lists:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0051E ’DD name:’ p1 ’DSN:’ p2 ’close error, Return code:’ p3Explanation: An error occurred while ISPF tried to close an open file.System Action: The program terminates.User Response: Check the RKOGLOGM and the system log for more messages. Contact Candle Customer Support if necessary.

KAT0051I ’* Distributed Gateways:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0052E ’Resource Node’ p1 ’is invalid.’Explanation: The resource node is not defined in VTAM.System Action: Processing continues.User Response: Make sure the node is defined in VTAM.

KAT0052I ’* *** Probe related records ***’Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0053I ’* Initialization probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.


KAT0054I ’* OMEGAMON Data Manager probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0055E ’Invalid Problem Action code, must be A or D. Probe Name =’ p1 ’Key = ’ p2 ’Act =’ p3 ’Text =’ p4Explanation: The Problem Action code is neither A (add text) nor D (delete text).System Action: The program terminates.User Response: Investigate the activity of the specified status item.

KAT0055I ’* OMEGAVIEW System Manager probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0056E ’Log Archive invoked without Log DDName’Explanation: The calling module did not pass any ddname to the program when the Log Archive was invoked.System Action: The program terminates.User Response: Check the OSM/MVS log for more messages.

KAT0056I ’* Heartbeat probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0057E ’Log Archive invoked without Log DSName’Explanation: The Log Archive program was started but did not have the Log Dataset name to archive.System Action: The program terminated.User Response: Look for additional messages to aid in problem determination.

KAT0057I ’* Query probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0058E ’Log Archive unable to allocate input JCL file.’Explanation: An error occurred during allocation of a JCL dataset.System Action: Program terminates.User Response: Review the message, and look for more messages to aid in problem determination.


KAT0058I ’* Situation probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0059E ’Log Archive unable to find DSName for file’ p1Explanation: The Log Archive was unable to locate the specified dataset name for the Log Datasets to be copied to.System Action: Program terminates.User Response: Validate the existence of the dataset and re-specify if necessary.

KAT0059I ’* DAS Data Manager probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0060E ’Log Archive unable to open input JCL file.’Explanation: The Log Archive function could not open the necessary JCL for copying the dataset.System Action: Program terminates.User Response: Verify the existence of the dataset, and re-specify if necessary.

KAT0060I ’* Availability probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0061E ’Log Archive unable to open internal reader.’Explanation: The Log Archive was unable to submit the JCL through the internal reader.System Action: Program terminates.User Response: Validate that the internal reader is allocated to the output DD name.

KAT0061I ’* Inactive probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.


KAT0062E ’Data manager:’ p1’, Probe:’ p2 ’not supported.’Explanation: Data Managers require the specification of the supported probes. Each Data Manager will then support a specific list of probes. This message was issued when a probe ID encountered for service was not one of the specific supported probes.System Action: Processing continues, but a specified supporting probe not evaluated.User Response: Either remove this probe from the supported probes list, or add support for this probe to the Data Manager program code.

KAT0062I ’* Total Probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0063E ’Data Manager not requesting OMEGAMON data.’Explanation: When a Data Manager designed to get OMEGAMON data, does not receive instructions to access OMEGAMON (from dependent probes and status items) then this message is returned.System Action: Processing continues.User Response: No response is necessary; however, to keep this message from being displayed, either inactivate this Data Manager or add OMEGAMON support code.

KAT0063I ’* Total Probe traps created:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0064I ’* Incidents:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0065I ’* System records:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.

KAT0066I ’* System Messages:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup or shutdown.System Action: Processing continues.User Response: None. This is an informational message.


KAT0067E ’Illegal task for Data Manager’ p1 p3Explanation: A Distributed Data Manager probe is called with specific tasks. A non-recognized task was passed to the Distributed Data Manager.System Action: Data Manager program terminates.User Response: Determine if a program naming conflict has occurred.

KAT0068E ’Distributed Data Manager found no systems to monitor.’Explanation: At startup, the Distributed Data Manager determined that no distributed system had been specified for it to monitor.System Action: Program terminates.User Response: If you are not monitoring any Distributed Systems, then no action is necessary. However, if you want to monitor Distributed Systems, check the Systems Environments and DAS specifications.

KAT0069E ’Distributed System monitoring Start failed, System:’ p1Explanation: An error occurred during the monitoring initialization for the specified system.System Action: Distributed System monitoring for the specified system terminates.User Response: Check the connection and availability for the Distributed System.

KAT0070E ’Probe Program not found for:’ p4Explanation: When starting a Distributed Systems Probe, the actual probe program name was not found.System Action: Probe initialization fails.User Response: Determine if the specified program is correct and available.

KAT0073E ’OMEGAVIEW update failure for Probe:’ p5 ’Return code:’ p6Explanation: The OMEGAVIEW update program has returned a non-zero return code.System Action: Processing continues, but an update to OMEGAVIEW has failed.User Response: Review accompanying messages to aid in problem determination.

KAT0074E ’Initial retrieve of OMEGAVIEW Status data failed for:’ p4Explanation: When the System Maintained Data Manager first starts, it tries to get the initial value of the Status Item from OMEGAVIEW. The initial read failed.System Action: System Maintained Data Manager terminates.User Response: Review the Status Item name and the availability of OMEGAVIEW.

KAT0076E ’Notification Evaluation program did not complete, Return code:’ p1Explanation: The Notification Evaluation program has returned a non-zero return code.System Action: Notification processing for this Status Item terminates.User Response: Check the return code and any accompanying messages to aid in problem determination.


KAT0077E ’Error reading’ p1 ’shared variable, Return code:’ p2Explanation: The OSM/MVS variable was not found in the REXX shared variable pool. The return code from the SHARVGET function is shown in the message text.System Action: The program terminates.User Response: Determine the module which issued the message.

KAT0078E ’Error updating’ p1 ’ shared variable ,Return Code:’ p2Explanation: An error occurred while updating the specified REXX Shared variable. Use the return code and program ID from the message to determine the cause of the error.System Action: Program terminates.User Response: Use the specified variable name, return code, and program name to determine the cause of the problem.

KAT0079E ’Invalid Notify Type’ p1 ’Incident’ p2Explanation: The notification method is not supported by the Notify program. Valid notification methods are SEND, BEEP, and WTO.System Action: The Notify routine is cancelled.User Response: Determine which status item is associated with the incident by examining the RKOGLOGM. Change the notify type for the status item using the OSM/MVS ISPF panels.

KAT0080E ’Resolution routine could not delete trap’ p1 ’Return code:’ p2Explanation: The Notification Resolution program received a non-zero return code when trying to delete an escalation trap or an auto-resolve trap.System Action: Processing continues.User Response: Examine the RKOGLOGM to determine the cause of the TRAP DELETE failure If necessary, re-issue the TRAP DELETE command from the console.

KAT0081E ’Invalid Notification Priority’ p1Explanation: The notification priority is invalid.System Action: Notification for the incident is cancelled.User Response: Correct the notification priority using the OMV/MVS ISPF panels.

KAT0082E ’Notification failed’ p1Explanation: The Notification routine failed to notify the user. This may be caused by the failure of the notification type (BEEP, SEND, or WTO). The message contains the notification data.System Action: The notify data is logged in the OSM/MVS Notification Log.User Response: Examine the RKOGLOGM to determine the type of notification failure.


KAT0083E ’Error deleting shared variable’ p1 ’SHARVDEL Return code:’ p2Explanation: The variable could not be deleted from the REXX shared variable pool.System Action: The program is cancelled.User Response: Determine the cause of the error from the SHARVDEL return code.

KAT0084E ’Error routine called from line’ p1’. An error occurred during ’ p2 p3 p4 p5Explanation: The error program routine was called after an irrecoverable error. The message shows the REXX program line which issued the CALL, SIGNAL, or SIGNAL ON ERROR instruction. The program line is derived from the REXX special variable SIGL which gives the absolute line number in the program.System Action: The program is cancelled.User Response: Examine the program which failed and find the line which called the error routine. Call Candle Customer Support.

KAT0085E ’Invalid Notification Broadcast function’ p1 ’passed from program’ p2Explanation: The function is invalid for the Notification Broadcast program. The message shows the program which called the Notification Broadcast program. System Action: The program terminates with an error code.User Response: Correct the Notification Broadcast parameters in the calling program.

KAT0086E ’No OG/OS2 sessions found.’Explanation: There are no OG/OS2 sessions defined to OSM/MVS.System Action: The program terminates with an error code.User Response: Use the OSM/MVS ISPF interface to define an OG/OS2 session and restart OSM/MVS.

KAT0087E ’Invalid Shared variable List function passed’ p1Explanation: An invalid parameter has been passed to the program.System Action: The program terminates with an error code.User Response: Find the program which called the List Processing program and correct the parameter which is in error.

KAT0088E ’OSM/MVS shutdown errors.’Explanation: Errors have occurred during the processing of this program.System Action: The program terminates with an error code.User Response: Examine the RKOGLOGM for any messages from the same match.

KAT0089E ’Invalid Availability Status detected:’ p1 ’Reset to initial’Explanation: The status of the Peer link has been found to be invalid. Valid statuses are: INITIAL, STARTUP, ACTIVE, SHUTDOWN, and NOT_MSMF.System Action: Processing continues.User Response: The status of the peer link will be set to INITIAL.


KAT0090E ’Data Manager Shared variable’ p1 ’contains invalid data:’ p2 p3 p4Explanation: The probe has retrieved the data that the Data Manager placed in the REXX shared variable, but the data is in an unexpected format.System Action: The program is cancelled.User Response: Check the probe program and the data manager that supports the probe to ensure that they are compatible.

KAT0091E ’Diagnostic routine failure for Status Item’ p1 ’Module’ p2 ’Return code:’ p3Explanation: The diagnostic routine for the status item has ended with an error return code. The message shows the module in error and the return code from that module.System Action: Processing continues.User Response: Examine the RKOGLOGM for any messages which may have been issued by the diagnostic routine.

KAT0092E ’Probe’ p1 ’Status Item’ p2 ’is mismatched with’ ’OMEGAVIEW name’ p3Explanation: The OSM/MVS status item name does not match the OMEGAVIEW status item name for the OMEGAVIEW Data Manager probe.System Action: The program is cancelled.User Response: Check that the OMEGAVIEW status item is defined to OSM/MVS.

KAT0093E ’Status Item’ p1 ’does not exist in list variable’ p2Explanation: The OMEGAVIEW status item does not exist in the OSM/MVS variable which contains a list of all the status items supported by the OMEGAVIEW Data Manager.System Action: The program is cancelled.User Response: Check that the status item is defined to OSM/MVS.

KAT0094E ’No Rule sets for Situation’ p1Explanation: No situation rules have been defined for the situation status item.System Action: Processing continues with the next situation.User Response: Enter the OSM/MVS Situation Manager and check that situation rules have been defined. Contact Candle Customer Support.

KAT0095E ’Cannot find Situation Object’ p1 ’for Situation’ p2Explanation: A status item is defined as the object of a situation rule, but the status item is not defined to OSM/MVS.System Action: Processing continues with the next situation.User Response: Define the status item to OSM/MVS. If the error recurs, contact Candle Customer Support.

KAT0097E ’Error Translating SYSNAME to System ID, SYSNAME = ’ p1Explanation: The program was unable to determine the OSM/MVS system name from its linkid.System Action: The program terminates with an error code.User Response: Make sure that the OSM/MVS system definitions are correct. If the error recurs, contact Candle Customer Support.


KAT0098E ’Data Collection Failure: Probe ’p1’ Status Item’ p2 ’Program’ p3 ’ return code’ p4Explanation: The probe user exit program has returned a negative return code to the probe manager.System Action: Processing continues.User Response: Examine the probe program to determine the meaning of the return code.

KAT0100E ’One or more OMEGAMON commands failed in’ p1Explanation: The Data Manager has issued an OMEGAMON command which failed to return any data.System Action: The program is cancelled.User Response: Check the Data Manager program to determine what commands it issues. Ensure that these commands are valid for OMEGAMON.

KAT0101E ’Unable to retrieve LINE#, Return Code:’ p1Explanation: This message is displayed after a program fails to read data from a sequential file allocated to OSM/MVS. The Global Variable LINE# indicates the number of lines to be read from the file.System Action: The program terminates.User Response: Validate the existence of the data to the file, and check accompanying messages to aid in problem determination.

KAT0102E ’No Available OG/OS2 systems were found.’Explanation: This message is issued from the Notification Beep processing. No OG/OS2 systems are currently available to perform a Beep request.System Action: Beep processing terminates.User Response: Ensure that the OG/OS2 system is available and defined to the OSM/MVS tables.

KAT0103E ’Non-Incident Notify Failure for Probe:’ p1 ’Return Code:’ p2Explanation: A failure occurred while trying to issue Notification Messages for a Status Item/Activity which specified not to create an incident.System Action: Notification processing for this Status Item terminates.User Response: Check the return codes and accompanying messages to aid in problem determination.

KAT0104E ’Error Translating System ID to SYSNAME, System = ’ p1Explanation: The program was unable to determine the linkid of another system from its OSM/MVS system name.System Action: The program terminates with an error code.User Response: Make sure that the OSM/MVS system definitions are correct. If the error recurs, contact Candle Customer Support.

KAT0105E ’Error Routing OMEGAVIEW Text to Focal System’ p1Explanation: OSM/MVS was unable to route the command to the focal system.System Action: Processing terminates.User Response: Check that the connection to the focal system is correctly established, then retry the command.


KAT0106E p1 ’data not numeric (’ p2 ’) for Probe’ p3Explanation: A non-numeric value was detected when numeric data was expected.System Action: The probe turns on the NO_DATA light.User Response: Check the arguments passed to the probe to ensure it receives the correct data.

KAT0107E ’Table’ p1 ’cannot be refreshed.’Explanation: The refresh function has been invoked for an OSM/MVS table which cannot be refreshed.System Action: The refresh request is ignored, and the refresh program terminates.User Response: Determine the reason that the refresh program was invoked and determine the name of the table which was to be refreshed. Call Candle Customer Support.

KAT0108E ’Required parameter missing in refresh arguments:’ p1Explanation: An OSM/MVS update request has been requested, but one of the parameters is missing. When an update request is passed to the refresh program, the name of the table and the table key are required parameters.System Action: The refresh request is ignored, and the refresh program terminates.User Response: Change the refresh request to the correct parameters.

KAT0109E ’Refresh action’ p1 ’is invalid.’Explanation: The refresh program has been invoked with an invalid action. Valid actions are: All, Update or Delete.System Action: The refresh request is ignored, and the refresh program terminates.User Response: Change the refresh request to the correct parameters.

KAT0110E ’Schedule for probe’ p1 ’cannot be resolved. Start time:’ p2 ’Stop time:’ p3Explanation: The probe scheduler routine could not resolve the probe’s start and stop times relative to the current time of day.System Action: Processing continues without scheduling the probe.User Response: Check the start and stop times in the OSM tables to determine whether they are valid. If necessary, correct the times; otherwise call Candle Customer Support.

KAT0111E ’OG/OS2 session was not found for System:’ p1Explanation: The OG/OS2 session defined for the specified system could not be located in the System Identifiers variable.System Action: Beep processing terminates with error.User Response: Review the OG/OS2 specifications in the ISPF User Interface.


KAT0112E ’*** Distributed Data Manager ended abnormally ***’Explanation: This message is a confirmation that the Distributed Data Manager ended abnormally. See preceding messages for details.System Action: The Distributed Data Manager is in error. Correct problem and rerun.User Response: See preceding messages for more information.

KAT0113E ’Critical ISPF table’ p1 ’is empty.’Explanation: A critical ISPF table was read and found to be empty; it contains no rows of data. KATKAMSG is the messages table. KATKAPRE is the preferences table.System Action: OSM/MVS system startup/refresh terminates.User Response: Run the Customizer to repopulate the empty table and restart OSM/MVS.

KAT0113I ’ISPF table’ p1 ’is empty.’Explanation: An ISPF table was read and found to be empty; it contains no rows of data.System Action: OSM/MVS system startup/refresh continues.User Response: None. This is an informational message only.

KAT0114E ’Unable to find message ID’ p1 ’in table’ p2’.’Explanation: An attempt to locate the requested message ID in the message table has failed.System Action: Message ID is not added or updated to the OSM/MVS runtime environment.User Response: Check the message in the user interface to ensure the message was added in the message table.

KAT0114I ’Message ID’ p1 ’has been added or updated.’Explanation: A message refresh request has been processed. The new or altered message text is immediately effective.System Action: Processing continues.User Response: None. This is an informational message.

KAT0115E ’The’ p1 ’request type parameter is missing.’Explanation: The program that updates the OSM/MVS status variable was terminated because one of the required parameters was missing.System Action: Program terminates.User Response: Examine the RKOGLOGM to determine the request type (OSM/MVS refresh, startup, or shutdown) that caused this error message to occur. Gather the information and contact Candle customer support staff.


KAT0116E ’An invalid’ p1 ’request type’ p2 ’was specified.’Explanation: The program that updates the OSM/MVS status variable was terminated because an invalid parameter was passed to the program.System Action: Program terminates.User Response: Examine the RKOGLOGM to determine the request type (OSM/MVS refresh, startup, or shutdown) that caused this error message to occur. Gather the information and contact Candle customer support staff.

KAT0117I p1 ’status variable is deleted.’Explanation: The OSM/MVS product status variable was successfully deleted.System Action: Program continues.User Response: None. This is an informational message.

KAT0118E ’The’ p1 ’state’ p2 ’for the’ p3 ’request is invalid.’Explanation: The program that updates the OSM/MVS status variable was terminated because one of the input values was invalid.System Action: Program terminates.User Response: Examine the RKOGLOGM to determine the request type (OSM/MVS refresh, startup, or shutdown) that caused this error message to occur. Gather the information and contact Candle customer support staff.

KAT0119I ’OSM/MVS status variable’ p1 ’does not exist, rc=’p2’.’Explanation: OSM/MVS was not able to retrieve the product status variable for the DISPLAY request.System Action: Processing continues.User Response: None. This is an informational message.

KAT0120E ’Only a’ p1 ’request can correct a’ p1 ’ABEND.’ p2 ’denied.’Explanation: A startup, shutdown, or refresh request was submitted after the status variable was set to the ABENDED state. Only request of the same type that caused the ABEND can resolve the problem.System Action: Program terminates.User Response: Resubmit the appropriate startup, shutdown, or refresh request.

KAT0121E ’The matnum parameter is missing.’Explanation: The program that updates the OSM/MVS status variable has terminated because the match number was not passed to the program.System Action: Program terminates.User Response: Examine the RKOGLOGM to determine the request type (OSM/MVS refresh, startup, or shutdown) that caused this error message to occur. Gather the information and contact Candle customer support staff.

KAT0122E p1 ’is not a valid match number.’Explanation: The match number was not a numeric value.System Action: Program terminates.User Response: Examine the RKOGLOGM to determine the request type (OSM/MVS refresh, startup, or shutdown) that caused this error message to occur. Gather the information and contact Candle customer support staff.


KAT0123E p1 ’request (’p2’) denied. There is already a’ p3 ’request (’p4’) in progress.’Explanation: OSM/MVS detects there is already an OSM/MVS startup, shutdown, or refresh request in progress. Thus, any subsequent startup, or shutdown request will be denied until the original match has completed.System Action: Program terminates.User Response: Verify the in-flight request is actively running. If the match is running, wait for it to complete before resubmitting your request. If the match is hanging, examine the RKOGLOGM to determine the cause of the problem. A recycle of the OG/MVS address space might be required to correct the problem. Contact the Candle customer support staff for assistance.

KAT0124W ’Invalid output option’ p1 ’specified.’ p1 ’ignored.’Explanation: An invalid output option was specified. OSM/MVS will reroute the intended messages to the console.System Action: Program continues.User Response: Notify the Candle customer support staff.

KAT0125E ’Invalid reported/desired states’ p1’/’p2 ’for a’ p3 ’request.’Explanation: Invalid combination of the reported and desired states were specified for either a STARTUP, SHUTDOWN, or REFRESH request. Because of the mismatch, the product status variable was not updated.System Action: Program terminates.User Response: Contact Candle customer support staff.

KAT0126E ’A single probe refresh cannot be performed if the’ p1 ’reported state is not equal to STARTED.’Explanation: A single probe refresh cannot be performed if OSM/MVS has not been STARTED or if a global request (startup, shutdown, or refresh) is in progress.System Action: Program terminates.User Response: If a global request is being processed, wait until that request is finished before resubmitting the single probe refresh request. If no global request was in progress when the single probe refresh request was made, display the contents of the product status variable and verify the reported state is set to STARTED.

KAT0127I ’No data found to display. The OSM/MVS product status variable does not exist.’Explanation: OSM/MVS tried to retrieve the contents of the product status variable. However, the shared variable that normally contains the information did not exist.System Action: Program continues.User Response: None. This is an informational message.

KAT0128I ’* Event probes:’ Right(p1,5)Explanation: This message forms part of the OSM/MVS record summary displayed at OSM/MVS startup, shutdown, or refresh.System Action: Processing continues.User Response: None. This is an informational message.


KAT0129I ’* Reported(’p1’) Desired(’p2’) Curr_act(’p3’)’Explanation: This is part of the text from the OSM/MVS status control block display request.System Action: Processing continues.User Response: None. This is an informational message.

KAT0130I ’* Last_update(’p1 p2 p3’)’Explanation: This is part of the text from the OSM/MVS status control block display request.System Action: Processing continues.User Response: None. This is an informational message.

KAT0131I ’*-- Current’ p1 ’product status information --*’Explanation: This is part of the text from the OSM/MVS status control block display request.System Action: Processing continues.User Response: None. This is an informational message.

KAT0132I ’*------------------------------------------------*’Explanation: This is part of the text from the OSM/MVS status control block display request.System Action: Processing continues.User Response: None. This is an informational message.

KAT0133E ’The’ p1 p2 ’parameter for the’ p3 ’request is missing.’ p4 ’denied.’Explanation: One of the required parameters is not being passed to the program that updates the product status variable.System Action: Program terminates.User Response: Contact Candle customer support staff.

KAT0134I p1 ’has already been’ p2’.’ p3 ’request denied.’Explanation: OSM/MVS will disallow a STARTUP request if it detects the product has already been STARTED. Similarly, it will disallow a SHUTDOWN request if it detects the product has already been STOPPED.System Action: Program terminates.User Response: None. This is an informational message.

KAT0135E p1 ’cannot be performed if’ p2 ’has not been’ p3’.’Explanation: A refresh request can only be processed if the product has already been STARTED.System Action: Program terminates.User Response: Submit an OSM/MVS startup request.

KAT0136E ’The’ p1 p2 ’parameter for the’ p3 ’request is missing.’Explanation: One of the required parameters is not being passed to the program that verifies the product reported state.System Action: Program terminates.User Response: Contact Candle customer support staff.


KAT0137E ’OMEGAVIEW session is not available.’Explanation: OSM/MVS is unable to update OMEGAVIEW status items or text because no OMEGAVIEW logon session has been established successfully.System Action: Program terminates.User Response: Verify the correct (SDM) APPLID is specified for the OMEGAVIEW logon APPLID. Verify OMEGAVIEW is active. Verify the OG/MVS virtual terminals for OMEGAVIEW support are configured correctly.

KAT0138I ’There is a shutdown request (’p1’) in the queue. Suspending’ p2 ’refresh request processing.’Explanation: A shutdown request was received and queued while OSM/MVS was servicing a single probe or global refresh request. The single probe refresh processing will be suspended and shutdown processing will be initiated.System Action: Suspend refresh and initiate shutdown processing.User Response: None. This is an informational message.

KAT0139I ’There is a global refresh request queued (’p1’). Single probe refresh will be suspended.’Explanation: A global refresh request was received and queued while OSM/MVS was servicing a single probe refresh request. Single probe refresh processing will be suspended and global refresh processing will be initiated.System Action: Suspend single probe refresh and initiate global refresh processing.User Response: None. This is an informational message.

KAT0140I p1 ’global refresh request (’p2’) has completed, rc=’p3’.’Explanation: Global refresh request has ended.System Action: Program terminates.User Response: None. This is an informational message.

KAT0141I ’Restarting single probe refresh queue.’Explanation: The global refresh request has ended. OSM/MVS detects there are new requests in the refresh queue. OSM/MVS restarts the single refresh queue processing.System Action: Program continues.User Response: None. This is an informational message.

KAT0142I ’There is a shutdown request (’p1’) in the queue. Initiating shutdown processing.’Explanation: A shutdown request was received and queued while OSM/MVS was servicing a single probe refresh or a global refresh request. Since the refresh request has ended, OSM/MVS will initiate shutdown processing.System Action: Suspend refresh and initiate shutdown processing.User Response: None. This is an informational message.

KAT0143I p1 ’probe’ p2’.’Explanation: This message indicates a probe has been refreshed.System Action: Program continues.User Response: None. This is an informational message.


KAT0144I p1 ’status item or situation’ p2’.’Explanation: This message indicates a status item or situation has been refreshed.System Action: Program continues.User Response: None. This is an informational message.

KAT0145I ’The addition/update request for’ p1 ’will be processed by the global refresh request.’Explanation: The probe update request has been deleted in the refresh queue. Since the global refresh program has to read the probe and probe related tables and process them, the single probe update requests in the queue will be indirectly serviced by the global refresh request. Consequently, the update request is removed from the queue.System Action: Program continues.User Response: None. This is an informational message.

KAT0146I ’Queuing request’ p1’.’Explanation: The single probe refresh request has been queued because there is already single probe refresh or a global refresh request in progress.System Action: Queue single probe refresh request and exit program.User Response: None. This is an informational message.

KAT0147I ’There is a single probe refresh request (’p1’) in progress.’ p2 p3 ’is queued.’Explanation: A global refresh or a shutdown request was received while a single probe refresh request was running. The request has been queued.System Action: Queue request and terminate program.User Response: None. This is an informational message.

KAT0148I ’There is a global refresh running.’ p1 ’will be queued.’Explanation: A single probe refresh request was receive and queued while OSM/MVS was processing a global refresh request.System Action: Queue request and terminate program.User Response: None. This is an informational message.

KAT0149E ’Status Item Refresh is ending due to an invalid current status.’Explanation: The OSM has found that the current status of the product is not appropriate for carrying out a Status Item Refresh. This is caused by the OSM not reporting a Status of STARTED. This circumstance can be caused by a STARTUP or STOP request.System Action: Processing ends.User Response: If the product is starting or stopping this message can be ignored. However if this message occurs as a result of a Refresh request during normal processing call Candle Customer support.


KAT0150I ’Status Items refresh is starting’Explanation: KATRAF17 is starting to refresh the OMEGAVIEW Status items for this Domain.System Action: None.User Response: None.

KAT0151I ’Status Items refresh completed’Explanation: The OSM has completed refreshing the OMEGAVIEW Status Items for this Domain.System Action: None.User Response: None.

KAT0152E ’Unable to read the Probe Names Table ’p1Explanation: When attempting to carry out a Status Item refresh the OSM was unable to retrieve the probes that are kept in the Probe Names Table.System Action: Processing ends.User Response: From the Controls Pull Down Refresh the product. This will rebuild the Probe Names Table. If the problem persists, call Candle Customer Support.

KAT0153E ’Error retrieving Domain information for Probe: ’p1Explanation: The OSM is trying to build Status Item information for the named Probe but has encountered a problem. Processing continues with the next Probe in the list.System Action: Processing continues for the next probe.User Response: Refresh the Probe listed and its associated Status Items.

KAT0154I ’Status Items Refresh is already in progress. Terminating’Explanation: The OSM has detected that a Refresh of Status Items is already in progress. This will be the case if there are more than 1 OMEGAVIEW sessions assigned to this OSM. This process only needs to run once for all Status Items in this OSM to be updated.System Action: Processing ends.User Response: None.

KAT0157E ’Error retrieving Spike Check information for probe ’p1Explanation: A probe has the SPIKE Check FLag set to Y but there are no SPIKE percentages set. SPIKE check information is set in the STATUS MANAGER.System Action: Processing terminates.User Response: Edit the Status Item via the STATUS MANAGER panel in the ISPF interface. If the spike check flag is set to Y input the percentage figures required and refresh the Status Item.


KAT0158E ’The Table ’p1’ Is empty. The requested actions will end’Explanation: An attempt has been made to run an action against an empty table. As the table is empty the action can not be carried out. System Action: Processing ends.User Response: If other requests were queued then issue the following command: subsys EX KATRAU04 ’RESTART’ Where subsys is the subsystem name. Alternatively issue a REFRESH request from the controls pull-down.

KAT0159I ’Warning: No Notification Log has been defined’Explanation: No Notification Log data set has been defined. Notification processing will still take place, but no notification activity will be logged.System Action: Processing continues.User Response: If notification logging is desired define a Notification (code N) log using the OSM/MVS ISPF panels. Restart or refresh OSM/MVS.

KAT0160E ’Distributed Data Manager found no active Distributed probes’Explanation: At startup, the Distributed Data Manager found no active distributed probes for which to gather data.System Action: Program terminates.User Response: If you are not monitoring any Distributed systems, then no action is necessary. If you wish to monitor distributed systems make sure at least one distributed probe is active.

KAT0161I ’SHOWOSM’ p1Explanation: This message is issued in response to the SHOWOSM command. It echoes the command back and indicates the beginning of the command response.System Action: Processing continues.User Response: None. This is an informational message only.

KAT0162I ’SHOWOSM display complete’Explanation: This message is issued in response to the SHOWOSM command. It indicates the end of the command display.System Action: Processing continues.User Response: None. This is an informational message only.

KAT0163I ’SHOWOSM extraneous parameters ignored:’ p1Explanation: A SHOWOSM command was issued. The command contained extra parameters which were not part of the SHOWOSM syntax.System Action: Processing continues. The SHOWOSM command is executed.User Response: None. This is an informational message only.

KAT0164E ’SHOWOSM invalid syntax:’ p1Explanation: A SHOWOSM command was issued. The command contained invalid parameters which could not be processed.System Action: Processing continues. The SHOWOSM command is not executed.User Response: Reissue the SHOWOSM command with valid syntax.


KAT0165I ’SHOWOSM - OSM/MVS is not currently active, no data to display’Explanation: A SHOWOSM command was issued. OSM/MVS was not active, therefore there was no data to display showing the current status. OSM/MVS must be active in order to execute the SHOWOSM command.System Action: Processing continues.User Response: Start OSM/MVS, then reissue the SHOWOSM command.

KAT9991E ’No ISPF table name was passed.’Explanation: OSM/MVS was unable to process the runtime table because no table name was passed to the table read program.System Action: Table read program terminates.User Response: This is an internal OSM/MVS problem. Contact Candle Customer support staff.

KAT9992E ’The variable for the table library name cannot be found.’Explanation: An internal variable that stores the OSM/MVS runtime table library name was not set.System Action: Table read program terminates.User Response: This is an internal OSM/MVS problem. Contact Candle Customer support staff.

KAT9993E ’Unable to allocate ISPF table file’ p1’.’Explanation: The runtime table processing failed because OSM/MVS was unable to allocate the runtime table file.System Action: Table read program terminates.User Response: This is an internal OSM/MVS problem. Contact Candle Customer support staff.

KAT9994E ’Unable to open ISPF table file’ p1’.’Explanation: The runtime table processing failed because OSM/MVS was not able to open the runtime table.System Action: Table read program terminates.User Response: Verify the OSM/MVS runtime table library is populated (see OG/MVS Customization and Configuration Guide). Verify the table members are not empty.

KAT9995E ’Table ended unexpectedly’ p1’.’Explanation: While processing the runtime tables, an unexpected table termination was encountered.System Action: Table read program terminates.User Response: Verify if the runtime table in request is corrupted.

KAT9996E ’Error detected during execution.’Explanation: An unexpected I/O error was encountered when OSM/MVS was processing the runtime tables.System Action: Table read program terminates.User Response: Examine the RKOGLOGM to get problem description.


KAT9997E ’Column length (’p1’) > 80 characters.’Explanation: An unexpected field length is detected for the OSM/MVS runtime table library. System Action: Table read program terminates.User Response: Verify the field length for the OSM/MVS runtime table library and contact Candle Customer Support staff.

KBBCM001 COM1ERROR:rtncd1, rtncd2, rcpri, rcsec, snsi, rplreq, qualify,rpl6what, luname, mode, convidExplanation: An APPCCMD command was not completed by VTAM®, or VTAM conditionally completed the command. This data is displayed:

System Action: Depends on the error. The request may continue processing or may be terminated by VTAM.User Response: If rtncd1 is 0 and rtncd2 is ”B”, conditional completion is indicated for the APPCCMD command. This may or may not indicate an error. The rcpri and rcsec must then be checked to determine if an error occurred. A rcpri value of zero indicates that no error occurred. The rcsec field contains a non-zero value that contains the information about the processing of the macro. For example, a successful CNOS request may complete without error, but be negotiated by the partner LU. In such cases rcsec is set to X’2’ to indicate that negotiation took place.A non-zero value for rcpri indicates abnormal completion of an APPCCMD macro. The rcpri and rcsec fields contain the information needed to determine the error.If rtncd1 has a value greater than zero (usually X’4’), then that indicates a logic error in the application.Refer to the IBM manual, VTAM Programming for LU 6.2, for an explanation of the values and codes displayed in the KBBCM001 message, and recommended actions.

rtncd1 The general return code provided in R15.

rtncd2 The conditional completion return code or recovery action return code provided in R0.

rcpri The primary extended return code.

rcsec The secondary extended return code.

snsi The inbound sense data.

rplreq The APPCCMD CONTROL= value.

qualify The APPCCMD QUALIFY= value.

rpl6what The VTAM what data received flag.

luname The destination logical unit name.

mode The associated logmode.

convid The conversation id created by VTAM.


Review the associated product’s installation and customization manuals. Ensure the correct logmode and LU name have been specified, and that they have the appropriate definitions.If the product fails to function contact Candle Customer Support. Message Type: This message is directed either to RKLVLOG or the MVS console. If directed to the MVS console it is assigned a WTO route code of 11, and has no descriptor codes. If directed to the RKLVLOG the message type is LOG.

KC2EXP Dataset name must not be blank. or

KLVTBULD rc=rc reason=reason or

Member dsn(member) could not be opened. rc=rc or

Member name must not be blank. or

Profile name must not be blank. or

Profile profile does not exist.Explanation: A variable message that appears with, and immediately after, message KC2EXPFF. It explains the cause of the failure.System Action: The export fails.User Response: Correct the problem indicated by the message and retry.Severity: This is a critical error message.

KC2EXPFF Export failed for profile profile.Explanation: See message KC2EXP.System Action: See message KC2EXP.User Response: See message KC2EXP.

KC2EXP00 Profile profile was exported successfully.Explanation: The requested profile was exported successfully.System Action: Profile is exported to the dataset specified in the command parameter list.User Response: None. This is an informational message only.

KC2IMP KLVTBULD failed with rc=rc reason=reasonor

Member dsn(member) could not be found.or

Member dsn(member) could not be opened. rc=rcor

Member dsn(member) is not a valid profile.or


Profile name must not be blankExplanation: A variable message that appears with, and immediately after, message KC2IMPFF. It explains the cause of the failure.System Action: The import fails.User Response: Correct the problem indicated by the message and retry.

KC2IMPFF Import failed for profile profile.Explanation: See message KC2IMP.System Action: See message KC2IMP.User Response: See message KC2IMP.

KC2IMP00 Profile profile was imported successfully.Explanation: The requested profile was imported successfully.System Action: Profile is imported from the dataset specified in the command parameter list.User Response: None. This is an informational message only.

KC2LG000 - KC2LG999Explanation: Messages prefixed with KC2LG are self-explanatory. If you are unable to resolve the problem, contact Candle Support Services.

KCF0002E A duplicate global variable name was found.Explanation: The global variable editor detected a duplicate variable name.User Response: Rename the variable to give it a unique name.

KCF0003E An unknown error was detected.Explanation: An undefined discrepancy type was received from the CMS.User Response: Collect the CMS and CMW log files. Call Candle Customer Support.

KCF0004I There are no more discrepancies to display.Explanation: You have resolved the last of the discrepancies shown in the Discrepancy Display.User Response: Close the Discrepancy Display window.

KCF0005S An exception was caught in CreateDiscrepancyReport. System is now very unstable. Please save all work.Explanation: A fatal error has been detected at the workstation attempting to create the Discrepancy Display report.User Response: Restart the CMW. Collect the CMS and CMW log files. Call Candle Customer Support.

KCF0006E Source object @1 is locked by another user @2.Explanation: You copied or moved configuration object @1, but the object is currently being used by user @2.User Response: Wait until user @2 is done with the configuration object.

KCF0007E Target object @1 is locked by another user @2.Explanation: You are attempting to perform an action against configuration object @1, but the object is currently being used by user @2.User Response: Wait until user @2 is done with the configuration object.


KCF0008E The source object @1 has been altered. A refresh of the object is recommended.Explanation: The configuration object @1 has recently been altered. The information contained in your workstation about the object may be inaccurate.User Response: Right click on the object, and select the Refresh option from the pop-up menu, or select the Refresh now option from the View pull-down menu.

KCF0009E The target object @1 has been altered. A refresh of the object is recommended.Explanation: The configuration object @1 has recently been altered. The information contained in your workstation about the object may be inaccurate.User Response: Right click on the object, and select the Refresh option from the pop-up menu, or select the Refresh now option from the View pull-down menu.

KCF0010E Not authorized to access target object.Explanation: You are attempting to create a scheduled action, but you are not authorized to access one or more of the target objects.User Response: Ensure that you are authorized to access the targets of the scheduled action.

KCF0011S A program exception occurred in Configuration Manager within the Candle Management Server.Explanation: A fatal error has been detected at the Candle Management Server. The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0012S A severe error has occurred attempting to update configuration data base within the Candle Management Server.Explanation: A fatal error has been detected within the Configuration database manager. The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0013S The Configuration Manager is unavailable within the Candle Management Server.Explanation: The Configuration Manager has shut itself down because of a prior error. Your request cannot be processed.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0014E Source @2 and target @1 are incompatible types for move/copy request.Explanation: Your have requested that configuration object @2 be moved or copied to configuration object @1; however, object @2 cannot exist within object @1.User Response: Ensure that the source and target objects of a drag/drop operation are compatible.


KCF0015S The Configuration Manager within the Candle Management Server was unable to create database work unit.Explanation: Your request cannot be processed, because the configuration data base manager within the CMS was unable to create an internal resource.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0016E The selected object is unavailable because it is scheduled for action @1.Explanation: You have attempted to access an object in the configuration; however, this object is the target of scheduled action @1, and the "Prevent updates if enabled" option is selected for the scheduled action.User Response: Wait until the scheduled action @1 has completed execution; If you cannot wait, you must either disable the scheduled action, or reset the "Prevent updates if enabled" option.

KCF0017E You cannot do this because you are not currently in update mode.Explanation: You are attempting to modify the configuration data; however, your session is not currently in update mode.User Response: Select Update mode from the Configuration Manager pull-down menu on the Configuration Manager - Icons window.

KCF0018E The Configuration Manager was unable to locate or create the default resource group for configured system @1. Possible authorization problem.Explanation: You attempted a Discovery or Update Defined from Actual operation against configured system @1; however, the Configuration Manager was unable to create the default resource group. Or you attempted a Copy to Database operation, which cannot be done because the default resource group does not exist and you do not have sufficient authority for the queue manager.User Response: Verify that you have sufficient authority to perform the operation on the queue manager. If the problem persists, collect the CMS log files and call Candle Customer Support.

KCF0019E The update actual from defined cannot be performed because of a validation failure. Select the validate option for the object.Explanation: You requested an Update Actual from Defined operation; however, the Configuration Manager detected a validation error in the target defined configuration object.User Response: You should right click on the configuration object, and select the Validate option to view the validation error(s). Correct the error(s) and re-try the Update Actual from Defined operation.


KCF0020S The Configuration Manager was unable to build the resource name for the object.Explanation: The Configuration Manager was unable to determine the name of a resource contained within a resource group for an Update or View discrepancies request.User Response: Ensure that each resource contained within each targeted resource group has a valid name. If necessary, collect the CMS log files. Call Candle Customer Support.

KCF0021S The Configuration Manager was unable to locate the configured system for the object.Explanation: The Configuration Manager was unable to locate the configured system associated with the target object.User Response: Collect the CMS log files. Call Candle Customer Support.

KCF0022S The Configuration Manager was unable to create a handle set for selection group.Explanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0023E The selection group is empty. No action taken.Explanation: You have attempted to access one or more objects which no longer exist within the configuration.User Response: Select the Refresh now option from the View pull-down menu, then retry the original request.

KCF0024E The object cannot be deleted because it is in use.Explanation: The object that you are attempting to delete is currently in use and cannot be deleted.User Response: Wait until the object is no longer being used and re-try.

KCF0025E The prototype @1 cannot be deleted because it is in use.Explanation: You have requested that prototype object @1 be deleted; however, this prototype is currently referenced by one or more defined objects and/or prototype reference objects.User Response: Right-click on prototype object @1, and select the Disinherit objects option. This breaks the link between defined and prototype objects. After this, re-try the Delete request.

KCF0026E The configuration is not owned by the user session. No action taken.Explanation: You have requested that ownership of the entire configuration be released; however, your session does not currently own the entire configuration.User Response: None. There is no need to release ownership of the configuration if you do not own it.


KCF0027E Your request failed because the entire configuration is owned by user @1.Explanation: You attempted to access one or more configuration objects; however, you cannot do this at this time because another user @1 currently owns the entire configuration.User Response: Wait until user @1 is done with the entire configuration.

KCF0028E Configuration ownership cannot be obtained because other work is in progress.Explanation: You cannot obtain ownership of the entire configuration while other work (such as other sessions, or scheduled actions) is being processed.User Response: Re-attempt this request when there is no other work being performed by the Configuration Manager.


KCF0030E One or more selected objects no longer exist.Explanation: You have attempted to access one or more objects which no longer exist within the configuration.User Response: Select the Refresh now option from the View pull-down menu, then retry the original request.


KCF0032S One or more of the selected objects has been altered. A refresh is recommended.Explanation: One or more of the selected objects has recently been altered. The information contained in your workstation about the object(s) may be inaccurate.User Response: Select the Refresh now option from the View pull-down menu.

KCF0033S The Configuration Manager within the Candle Management Server is quiescing.Explanation: The Configuration Manager cannot process your request because it is in the process of shutting down.User Response: You must end the CMW and wait until the CMS has been restarted, before restarting the CMW and re-attempting the operation.


KCF0034S The requested variable cannot be updated or deleted because it is not global.Explanation: You have attempted to modify a global variable that is not a User or Product variable.User Response: Ensure that the variable that you are trying to modify is not a System variable.

KCF0039S The Configuration Manager encountered a severe error opening the file @1.Explanation: You entered a command requiring the Configuration Manager to open an external file; however, the file could not be opened.User Response: Ensure that the file name specified is valid. On MVS, the file must be a pre-existing data set. Ensure that there is sufficient disk space available to write into this file.

KCF0041S Dynamic allocation of the output file failed.Explanation: While performing an Export or Backup command, the requested output file could not be allocated.System Action: The requested action is terminated. User Response: If the allocation is being attempted on OS/390 or z/OS, then the requested file must be pre-allocated. For all platforms, ensure that the name specified is a valid file name for that platform and that you have the appropriate authority to access that file.

KCF0043E One of the objects using the prototype is being used by another user.Explanation: You attempted a Disinherit operation; however, the defined object cannot be disinherited from the prototype because it is currently in use.User Response: Wait until all defined objects associated with the prototype are no longer in use before attempting a Disinherit operation.

KCF0044S An invalid action request was sent to the Configuration Manager by the workstation.Explanation: The workstation sent a request to the CMS which is not supported by the Configuration Manager.User Response: Collect the CMS log files. Call Candle Customer Support.

KCF0045E The requested object does not exist in the configuration database. Explanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource is not defined in the configuration database.System Action: The attempted action cannot be completed.User Response: From OMEGAMON XE for WebSphere MQ Configuration, first ensure that the queue manager that owns the resource you selected is defined in the configuration database. If it is not, use the Discover feature to add the queue manager definition into the configuration database. If the owning queue manager is defined, next ensure that the WebSphere MQ resource you selected is defined in the configuration database. If it is not, select the queue manager and use the Discover New Resources feature to add the resource to the database. Note


that permanent dynamic queue definitions are not created in the database unless you have enabled that option in the Auto Start section of the queue manager settings.

KCF0046I The validation request completed successfully. No validation errors were detected.Explanation: You requested a Validate operation, and the Configuration Manager did not find any validation errors in the select object(s).User Response: None.

KCF0047I The view discrepancies request completed successfully. No discrepancies were detected.Explanation: You requested a View discrepancies operation, and the Configuration Manager did not find any discrepancies between the defined and actual object(s).User Response: None.

KCF0048E The request to move or copy the selected object failed because of a failure moving or copying another selected object.Explanation: You attempted to more or copy two or more objects. The request could not be processed on the second or subsequent objects because of a failure moving or copying a prior selected object.User Response: Determine why the move or copy of the prior object in the group failed. Correct the problem and re-try the request.

KCF0049E The Configuration Manager did not recognize your session. Please restart the Candle Management Workstation.Explanation: Because of a probable communications or other workstation problem, the Configuration Manager in the CMS no longer recognizes your session.User Response: Restart the CMW. Collect the CMS and CMW log files. If necessary, call Candle Customer Support.

KCF0051E The Configuration Agent @5 is not at the proper version to process this request.Explanation: You have entered a request requiring processing by Configuration Agent @5; however, this agent is running a back-level version, and is unable to perform your request.User Response: Ensure that the Configuration Agent is running at the most current level of Candle software.

KCF0052S Your request failed because the Configuration Manager was unable to create an internal SQL request.Explanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.


KCF0053S Your request failed because the Configuration Manager was unable to open an internal SQL request.Explanation: The Configuration Manager was unable to open the internal request required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0054E Your request failed because the Configuration Manager received a bad return code @1 from Configuration Agent @5.Explanation: Your request was sent to Configuration Agent @5; however, the agent was unable to process the request and returned a code of @1.User Response: Collect the CMS and agent log files. Call Candle Customer Support.

KCF0055E Your request failed because the Configuration Manager did not receive requested configuration data from Configuration Agent @5.Explanation: A request for actual configuration information was sent to Configuration Agent @5; however, the agent did not provide the requested data; the reason for this is unknown.User Response: Collect the CMS and agent log files. Call Candle Customer Support.

KCF0056S Your request failed because the Configuration Agent @1 reported an undefined Application Name @2.Explanation: The Configuration Agent @1 reported that it was associated with application name @2. This application name is unknown or unsupported.User Response: Ensure that the proper Configuration Agent is running. If you cannot see any problem, collect the CMS and agent log files. Call Candle Customer Support.

KCF0057E Your request failed because the configured system required to communicate with the target configured system is not currently defined.Explanation: The definition for the targeted configured system indicates that the Configuration Agent must communicate through an intermediate configured system; however, the intermediate system is not currently defined within the configuration.User Response: Ensure that the intermediate system is defined correctly within the configuration.

KCF0058E Your request failed because the configured system required to communicate with the target configured system is an indirect connection.Explanation: The definition for the targeted configured system indicates that the Configuration Agent must communicate through an intermediate configured system; however, the intermediate system is also defined as requiring an intermediate system. This is not supported.User Response: Ensure that the definition of the intermediate system does not itself require an intermediate system.


KCF0059E Your request failed because the Configuration Agent @5 does not exist in the Managed Systems folder.Explanation: The targeted configured system is defined with Configuration Agent @5; however, this Configuration Agent does not exist in the CCC Managed Systems folder.User Response: Ensure that the Configuration Agent is properly installed and is communicating with the CMS. Also, ensure that the name of the agent in the Managed Systems folder matches the name defined for the configured system.

KCF0060E Your request failed because the Configuration Agent @5 is offline.Explanation: The targeted configured system is defined with Configuration Agent @5; however, this Configuration Agent is not online in the CCC Managed Systems folder.User Response: Ensure that the Configuration Agent is properly installed and is communicating with the CMS. Also, ensure that the name of the agent in the Managed Systems folder matches the name defined for the configured system.

KCF0061E Your request failed because the configured system required to communicate with the target configured system @4 is not currently online.Explanation: The definition for the targeted configured system indicates that the Configuration Agent must communicate through an intermediate configured system; however, the intermediate system is not currently online.User Response: Ensure that the intermediate system is defined correctly and is running. Also ensure that the Configuration Agent associated with the intermediate configured system is online within the CCC Managed Systems folder.

KCF0062E Your request failed because the Configuration Agent @5 cannot connect with Configured System @4. The configured system may not be started.Explanation: Configuration agent @5 was unable to communicate with configured system @4. This may be because the configured system is not started, and the auto-start option is not selected for the configured system.User Response: Ensure that configured system is started. If you want the Configuration Agent to automatically start the system, select the auto-start option in the configured system definition. Check the agent and CMS logs for more details as to why the agent was unable to communicate with the configured system.

KCF0063E Your request failed because the Configuration Agent @5 was unable to start Configured System @4.Explanation: You have the auto-start option enabled for configured system @4, but the Configuration Agent was unable to start the configured system.User Response: Ensure that configured system is defined. If you want the Configuration Agent to automatically define the system, select the auto-create option in the configured system definition. Check the agent and CMS logs for more details as to why the agent was unable to start the configured system.


KCF0064E Your request failed because the Configuration Agent @5 was unable to create Configured System @4.Explanation: You have the auto-create option enabled for configured system @4, but the Configuration Agent was unable to create the configured system.User Response: Check the agent and CMS logs for more details as to why the agent was unable to create the configured system. If necessary, attempt to define the configured system manually.

KCF0065E Your request failed because the Configuration Manager received invalid data from agent @5.Explanation: A request for actual configuration information was made to Configuration Agent @5; however, the agent returned invalid data to the Configuration Manager.User Response: Collect the CMS and agent log files. Call Candle Customer Support.

KCF0066E Your request failed because the Configuration Manager did not receive all requested data from Configuration Agent @5 quickly enough. Possible agent time-out.Explanation: A request for actual configuration information was made to Configuration Agent @5; however, the agent did not return the requested information within the required time period.User Response: This problem can be caused by communication problems, or by poor performance by either the Configuration Agent or the configured system. You can increase the amount of time allowed for the return of configuration data from the Configuration Manager Option.

KCF0067S The Configuration Manager did not recognize your session. Please restart the Candle Management Workstation.Explanation: Because of a probable communications or other workstation problem, the Configuration Manager in the CMS no longer recognizes your session.User Response: Restart the CMW. Collect the CMS and CMW log files. If necessary, call Candle Customer Support.

KCF0068S Your request failed because the Configuration Manager was unable to recognize session affinity @1.Explanation: The Configuration Manager did not recognize the CCC affinity associated with your Candle Management Workstation.User Response: Restart the CMW. Collect the CMS and CMW log files. If necessary, call Candle Customer Support.

KCF0069E You do not have authority to perform this operation on @1.Explanation: Your workstation does not have the proper affinity to access configuration object @1.User Response: Ensure that you are using a workstation in which the proper CMW product(s) have been installed. If so, restart the CMW. Collect the CMS and CMW log files. If necessary, call Candle Customer Support.


KCF0070E Your request failed because the actual resource does not exist.Explanation: You have requested to view or modify an actual configuration object; however, the object does not exist.User Response: Perform an Update Actual from Defined operation against the appropriate defined in order to create the actual resource.

KCF0071S Your request failed because a required configuration property could not be located.Explanation: Your request to view an actual object failed because a required property was not present in the defined configuration object.User Response: Collect the CMS log files. If necessary, call Candle Customer Support.

KCF0072E You cannot enable the scheduled action because of a conflicting scheduled action.Explanation: You have attempted to create or modify a scheduled action with the ’Prevent updates if enabled’ option. However, one or more of the target configuration objects are already the target of another scheduled action with the ’Prevent updates if enabled’ option.User Response: Use the Scheduling View option to find the conflicting scheduled action. Wait until the conflicting scheduled action completes before defining or enabling the new scheduled action.

KCF0073I Your update request was successfully performed.Explanation: Your request to Update actual from defined or Update defined from actual was completed successfully.User Response: None.

KCF0074E You cannot copy selected objects that are not owned by the same application.Explanation: You have attempted an operation on multiple selected objects; however, the request cannot be processed because the objects are associated with different configuration application.User Response: Ensure that all selected configuration objects are associated with the same configuration application.

KCF0075E Your request failed. The copy target object @1 belongs to a different application than source object @2.Explanation: You have requested that one or more configuration objects be moved or copied to a new target object; however, the target object is associated with an different configuration application.User Response: Ensure that the target object is associated with a compatible configuration application to the object(s) being moved or copied.


KCF0080E Your request failed because the configured system @4 cannot be started on the platform it resides on.Explanation: You have selected the auto-start option for configured system @4; however, the configured system is not currently running, and it cannot be automatically started on this platform.User Response: You must manually start the configured system on this platform.

KCF0081E Your request failed because the configured system @4 cannot be created on the target platform type.Explanation: You have selected the auto-create option for configured system @4; however, the configured system does not exist, and it cannot be automatically created on this platform.User Response: You must manually create the configured system on this platform.

KCF0082S Your request failed because an exception occurred on Configuration Agent @5 RC = @1 Reason = @2.Explanation: A request for actual configuration information was sent to Configuration Agent @5; however, a program exception occurred on the agent. The RC and Reason fields provide more detailed information.User Response: Collect the agent log files, and restart the agent. If necessary, call Candle Customer Support.

KCF0084E Configured system could not be discovered because it is already defined.Explanation: A configured system was discovered by a Configuration Agent, but the configured system name already exists within the defined configuration. No action was taken.User Response: None. If you wish to obtain the resource information for this configured system, select the Update defined from actual option from the pop-up menu for the configured system.

KCF0085W Configured system @1 defined but its resources could not be discovered.Explanation: Configured system @1 was discovered and has been added to the defined configuration; however, the Configuration Agent was unable to obtain any information from the configured system on its subordinate resources. This may be because the configured system was not active.User Response: If you want to obtain information on the resources subordinate to the configured system, you can set the auto-start option for the configured system, and select the Update defined from action option from the pop-up menu.

KCF0086W The Configuration Manager did not discover any configured systems.Explanation: You selected the Discover option for a configured system group, but no configured systems were detected.User Response: Ensure that your Configuration Agent(s) are online by checking the CCC Managed Systems folder.


KCF0087E The copy/move request is not allowed because a circular prototype reference was detected between target @1 and source @2.Explanation: You are trying to create a reference to a prototype within another prototype that would result in a circular set of prototype references. This is not supported.User Response: Ensure that the prototype that you are dragging does not contain a reference (either directly or indirectly) to the prototype you are dropping on.

KCF0088E The copy/move request is not allowed because target @1 is a descendant of the source @2.Explanation: You are trying to move or copy an object to a new target, but the target object is a direct or indirect descendant of the object being moved or copied. This is not supported.User Response: Ensure that the object that you are dragging does not contain (either directly or indirectly) the object you are dropping on.

KCF0089I The configured system and all resources were added to configuration.Explanation: The configured system and all of it’s subordinate resources were successfully added to the defined configuration.User Response: None.

KCF0090E The Configuration Manager was unable to authorize your session with the System Authorization Facility.Explanation: The Configuration Manager was unable to define your session because of a RACROUTE REQUEST=VERIFY failure. This could indicate a problem with the definition of your user id to RACF (or other equivalent service).User Response: Check the CMS log to determine the exact cause of the failure. If RACF is being used for authorization checking, consult IBM documentation.

KCF0091E The Configuration Manager was unable to terminate your session with the System Authorization Facility.Explanation: The Configuration Manager was unable to terminate your session because of a RACROUTE REQUEST=VERIFY failure. This could indicate a problem with the definition of your user id to RACF (or other equivalent service).User Response: Check the CMS log to determine the exact cause of the failure. If RACF is being used for authorization checking, consult IBM documentation.

KCF0092E You are not authorized to access configuration object @1.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to configuration object @1.User Response: Contact your local security administrator to provide you with access to this configuration object.


KCF0094E You are not authorized to delete object @2 from its parent @1.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to delete object @2 from it’s parent object @1.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the parent object.

KCF0095E You are not authorized to rename object @1 with new name @2.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to rename configuration object @1 with the new name @2.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have ALTER access to the object under both the old and new names.

KCF0096E You are not authorized to update the actual resource.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to update the actual resource associated with the defined resource.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have CONTROL access to the defined object.

KCF0097E You are not authorized to update the defined resource.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to update the defined resource from the defined resource.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the defined object.

KCF0098E You are not authorized to modify the target object @1.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to the target object of the move/copy request.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the defined object.

KCF0099E You are not authorized to modify the parent object @1.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to create a new defined object within configured system @1.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the configured system.


KCF0101E You are not authorized to create this object.Explanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to create a new defined object with name @1.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have ALTER access to the new object name.

KCF0102E Your request failed because the audit log is not available.Explanation: The Configuration Manager was unable to write to or receive messages from the audit log because it is currently unavailable.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0103E Your request failed because the requested audit log record was not found.Explanation: You made a request to obtain the detailed information for a record in the audit log; however, the specified audit log record could not be found.User Response: Recreate the Audit Log details report and re-try. If necessary, collect the CMW and CMS log files and call Candle Customer Support.

KCF0104E Your request failed because the requested audit log record has an invalid type.Explanation: You made a request to obtain the detailed information for a record in the audit log; however, the specified audit log record has an invalid type.User Response: Recreate the Audit Log details report and re-try. If necessary, collect the CMW and CMS log files and call Candle Customer Support.

KCF0105W No audit records were found in requested time period.Explanation: You made a request to view all the audit log records within a specified time span; however, no audit records were found which were created within the time span.User Response: Retry the request, specifying a different time span.

KCF0106S Your request failed because of a failure writing to the audit log.Explanation: A failure was encountered writing a record to the audit log.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0107E Your request cannot be processed because the Configuration Manager was shut down.Explanation: The Configuration Manager is not available within the CMS because it has been shut down. This could be because of a normal shutdown request for the CMS, or because of a previously-detected error.User Response: Unless you know that a normal shutdown was requested, you should collect the CMS log files, restart the CMS and the CMW and call Candle Customer Support.


KCF0108S Your request cannot be processed because the Configuration Manager shut down due to a data base error.Explanation: The Configuration Manager is not available within the CMS because it has been shut down due to a database failure.User Response: Collect the CMS log files, restart the CMS and the CMW and call Candle Customer Support.

KCF0109S Your request cannot be processed because the Configuration Manager shut down due to a program exception.Explanation: The Configuration Manager is not available within the CMS because it has been shut down due to a fatal program exception.User Response: Collect the CMS log files, restart the CMS and the CMW and call Candle Customer Support.

KCF0110S Your request cannot be processed because the Configuration Manager is not currently active.Explanation: The Configuration Manager is not available within the CMS because it has been shut down or was never started. The shutdown could be due to a normal shutdown request for the CMS, or because of a previously-detected error.User Response: Unless you know that a normal shutdown was requested, or that the Configuration Manager was never started, you should collect the CMS log files, restart the CMS and the CMW and call Candle Customer Support.

KCF0111S Your request cannot be processed because the CMS was unable to start the Configuration Manager.Explanation: The Configuration Manager is not available within the CMS because it was not successfully started.User Response: Collect the CMS log files, restart the CMS and the CMW and call Candle Customer Support.

KCF0112S Your request cannot be processed because the Configuration Manager was shut down. No applications were installed.Explanation: The Configuration Manager shut itself down at startup time because it did not detect the installation of any configuration applications.User Response: Ensure that the appropriate configuration applications are installed at the Hub CMS.

KCF0113S Your request cannot be processed because the Configuration Manager was shut down. The Managed Systems list could not be updated.Explanation: The Configuration Manager is not available within the CMS because it has been shut down due to a problem updating the CCC Managed Systems folder. This could be due to the fact that the Hub CMS is configured for hot standby, and a Hub switch has taken place.User Response: The Configuration Manager will not run in a backup CMS. Ensure that the Configuration Manager is only running on a primary Hub CMS.


KCF0114W Actual resource does not exist.Explanation: On a View Discrepancies request, this resource was found in the defined configuration, but not in the actual configuration.User Response: Right click on the resource type in the left-hand column, and select either the ’Build actual’ option (to create the actual resource) or the ’Delete from database’ option (to delete the defined resource from the configuration).

KCF0115W Defined resource does not exist.Explanation: On a View Discrepancies request, this resource was found in the actual configuration, but not in the defined configuration.User Response: Right click on the resource type in the left-hand column, and select either the ’Copy to database’ option (to create the defined resource from the actual definition) or the ’Delete actual’ option (to delete the actual resource).

KCF0117S A severe error has occurred attempting to update configuration data base within the Candle Management Server.Explanation: A fatal error has been detected within the Configuration database manager. The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0118E A duplicate resource name was found in @1.Explanation: The validation request against the configured system has encountered two subordinate resources which are duplicately-named.User Response: Rename or delete one of the duplicate resources.

KCF0119E The Configuration Manager did not receive an acknowledgment from the agent indicating that the update for resource @3 completed successfully.Explanation: The Configuration Manager sent a request to Configuration Agent to modify actual configuration data. The agent did not send back an acknowledgement that the request was processed successfully. The status of the update request is unknown.User Response: Collect the CMS and agent log files. Restart the agent. Call Candle Customer Support.

KCF0120E Your request failed. Configured system @4 is not online.Explanation: Configured system @4 is not currently active, or some other problem is preventing the Configuration Agent from contacting it.User Response: If the configured system is currently active, you can either start the system manually, or you can indicate that you want the Configuration Agent to start the system for you. To do this, select the auto-start option for the configured system.

KCF0121S Your request failed because of an internal error within the Configuration Manager.Explanation: An unanticipated condition occurred within the Configuration Manager, causing your request to fail.User Response: Collect the CMS log files and call Candle Customer Support.


KCF0122S Your request failed because of an error on configured system @4 RC=@1 [email protected]: An error on configured system @4 caused your request to fail. The RC and Reason fields provide additional information.User Response: Collect the agent and CMS log files, and restart the agent. If necessary, call Candle Customer Support.

KCF0123E Your Update Actual from Defined request failed because the defined object was not successfully validated. Select the Validate option for the object to fix the problem.Explanation: You requested an Update Actual from Defined operation; however, the Configuration Manager detected a validation error in the target defined configuration object.User Response: You should right click on the configuration object, and select the Validate option to view the validation error(s). Correct the error()s, and re-try the Update Actual from Defined operation.

KCF0124S The request action is not applicable for this type of object.Explanation: The requested action is not application to this type of object.User Response: Collect the CMS log files. If necessary, call Candle Customer Support.

KCF0125E Your request failed because the Configuration Agent @5 does not exist in the Managed Systems folder.Explanation: The targeted configured system is defined with Configuration Agent @5; however, this Configuration Agent does not exist in the CCC Managed Systems folder.User Response: Ensure that the Configuration Agent is properly installed and is communicating with the CMS. Also, ensure that the name of the agent in the Managed Systems folder matches the name defined for the configured system.

KCF0126S Your request failed because the Configuration Manager was unable to create an internal SQL request RC=@1 [email protected]: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0127S The Configuration Manager was unable to obtain configuration data from the agent RC=@1 [email protected]: A request for actual configuration information was sent to the Configuration Agent; however, the agent did not provide the requested data; the RC and Reason fields may provide additional information.User Response: Collect the CMS and agent log files. Call Candle Customer Support.


KCF0128S Your request failed because the Configuration Manager was unable to open an internal SQL request RC=@1 [email protected]: The Configuration Manager was unable to open the internal request required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0129E Your request failed because the configured system required to communicate with the target configured system @4 is not currently defined.Explanation: The definition for the targeted configured system indicates that the Configuration Agent must communicate through an intermediate configured system; however, the intermediate system is not currently defined within the configuration.User Response: Ensure that the intermediate system is defined correctly within the configuration.

KCF0130E Your request failed because the configured system required to communicate with the target configured system @4 is an indirect connection.Explanation: The definition for the targeted configured system indicates that the Configuration Agent must communicate through an intermediate configured system; however, the intermediate system is also defined as requiring an intermediate system. This is not supported.User Response: Ensure that the definition of the intermediate system does not itself require an intermediate system.

KCF0131E Your request failed because the configured system required to communicate with the target configured system @4 is not currently online.Explanation: The definition for the targeted configured system indicates that the Configuration Agent must communicate through an intermediate configured system; however, the intermediate system is not currently online.User Response: Ensure that the intermediate system is defined correctly and is running. Also ensure that the Configuration Agent associated with the intermediate configured system is online within the CCC Managed Systems folder.

KCF0132E Your request failed because the Configuration Manager did not receive all requested data from Configuration Agent @5 quickly enough. Possible agent time-out.Explanation: A request for actual configuration information was made to Configuration Agent @5; however, the agent did not return the requested information within the required time period.User Response: This problem can be caused by communication problems, or by poor performance by either the Configuration Agent or the configured system. You can increase the amount of time allowed for the return of configuration data from the Configuration Manager Option.


KCF0133S Your request failed because the Configuration Manager could not create a new internal identifier for the object.Explanation: The Configuration Manager was unable to create the internal identifier for the new configuration object.User Response: Collect the CMS log files. Call Candle Customer Support.

KCF0134S Your request failed because the Configuration Manager was unable to create the new object.Explanation: The Configuration Manager was unable to create the new configuration object.User Response: Collect the CMS log files. Call Candle Customer Support.

KCF0136S Because of an internal error, no objects were replicated.Explanation: An internal error occurred within the Configuration Manager, and your replication request failed.User Response: Collect the CMS log files. Call Candle Customer Support.

KCF0138S Your request failed because the Configuration Manager was unable to create an action set.Explanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0139S Your request failed because the Configuration Manager was unable to create an action request.Explanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0140S Your request failed because of an averted deadlock condition at the Candle Management Server.Explanation: A potential deadlock condition within the Configuration Manager was averted by cancelling your request.User Response: Retry the request. If the problem persists, collect the CMS log files, restart the CMS and the CMW, and call Candle Customer Support.

KCF0141S Your request failed because of storage shortage at the Candle Management Server.Explanation: A storage shortage condition was detected within the Candle Management Server. Your request was not processed.User Response: If possible, increase the amount of storage available to the CMS. Otherwise, collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.


KCF0142S Your request failed because of RW storage shortage at the Candle Management Server.Explanation: A storage shortage condition was detected within the Candle Management Server. Your request was not processed.User Response: If possible, increase the amount of storage available to the CMS. Otherwise, collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0144E The Discover New Resources request is not supported for this type of object.Explanation: The workstation has made a ’Discover new resources’ request to the Configuration Manager for an object other than a configured system.User Response: Collect the CMS and CMW log files. Restart the CMW. Call Candle Customer Support.

KCF0145W No new resources were discovered for configured system @1.Explanation: A "Discover new resources’ request was made for configured system @1, but the Configuration Manager did not detect any actual resource which were not already defined.User Response: None.

KCF0146S Your request failed because the Configured System for the target object does not exist.Explanation: The Configuration Manager was unable to locate the configured system for the target object.User Response: Collect the CMS and CMW log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0147S Your request failed because no return code from Configuration Agent @5 was received.Explanation: A request was sent to the Configuration Agent, but the agent responded with a null return code.User Response: Collect the CMS and agent log files. Restart the agent. Call Candle Customer Support.

KCF0151E The scheduled action was disabled because of a prior execution failure.Explanation: The scheduled action became disabled because of a failure during it’s execution.User Response: Navigate to the Scheduled Action Status report for the scheduled action to determine what caused the problem. Correct the error and re-enable the scheduled action.

KCF0152E You are not authorized to alter or delete global variables.Explanation: You attempted to delete or modify a global variable; however, based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the ADMIN.GLVAR security profile.


KCF0153E You are not authorized to access audit log.Explanation: You attempted to access the audit log; however, based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the ADMIN.AUDIT security profile.

KCF0158S Your request failed because the Configuration Manager cannot write to the data base log file.Explanation: The configuration data base manager encountered an error writing to the data base log file; your request could not be processed, and the Configuration Manager is shut down.User Response: This problem can be occur if an out of space condition occurs for the data base log file. If the CMS is running on MVS, check for errors on the data set referred to by the RKCFDLOG DD statement in the CMS Started Task JCL. If the CMS is running on a distributed platform, ensure that there is sufficient disk space for the data base log file.

KCF0160S Your request failed because the base object could not be located.Explanation: The operation you request could not be performed. The base object associated with the target object could not be located.User Response: Collect the CMS and CMW log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0162E The scheduled action detected a validation error.Explanation: The Configuration Manager found a validation error while perform a scheduled validate action.User Response: Navigate to the Scheduled Action Status report for the scheduled action to determine what caused the problem. Correct the validation error and re-enable the scheduled action.

KCF0163I Your validation request was scheduled the scheduled action name is @1.Explanation: You requested that a validation operation be performed in the background. The Configuration Manager has created a scheduled action with the name @1 to perform this operation.User Response: You can track the progress of the scheduled action by viewing the ’Scheduled Action Summary’ report for the target object.

KCF0164I Your View Discrepancies request was scheduled the scheduled action name is @1.Explanation: You requested that a View Discrepancies operation be performed in the background. The Configuration Manager has created a scheduled action with the name @1 to perform this operation.User Response: You can track the progress of the scheduled action by viewing the ’Scheduled Action Summary’ report for the target object.


KCF0165I Your Update request was scheduled the scheduled action name is @1.Explanation: You requested that an Update Actual from Defined or an Update Defined from Actual operation be performed in the background. The Configuration Manager has created a scheduled action with the name @1 to perform this operation.User Response: You can track the progress of the scheduled action by viewing the ’Scheduled Action Summary’ report for the target object.

KCF0166I Your Delete request was scheduled the scheduled action name is @1.Explanation: You requested that an Delete operation be performed in the background. The Configuration Manager has created a scheduled action with the name @1 to perform this operation.User Response: You can track the progress of the scheduled action by viewing the ’Scheduled Action Summary’ report for the target object.

KCF0167E You cannot copy a prototype @1 that is directly descended from another prototype object @2.Explanation: You attempted to copy a prototype that is directly descended from another prototype into the defined tree. This is not supported.User Response: You can only copy prototype objects into the defined tree which are descended directly from Configured System Prototypes, Resource Group Prototypes, or Resource Prototypes.

KCF0168S The Configuration Manager cannot navigate to the object because the navigation path is empty.Explanation: You requested that the configuration product either select or open the settings for another object in the configuration. This could be the base object for the currently selected object, or it could be an object identified in the Validation report.User Response: The currently selected object may have been deleted or altered. Refresh the current tree using the Refresh pop-up menu option (for CMW, the Refresh now option from the View pull-down menu), and re-try the operation. If you are displaying the Validation report, close the report window and re-execute the Validate request.

KCF0169S An exception has been caught in DisplayValidationFor. System is now very unstable. Please save all work and restart CMW.Explanation: A fatal error has been detected at the workstation attempting to create the Validation report.User Response: Restart the CMW. Collect the CMS and CMW log files. Call Candle Customer Support.

KCF0170E Group name is invalid.Explanation: You entered an invalid resource or configured system group name.User Response: The group name must consist of between 1 to 48 characters. The following characters are allowed: Uppercase A-Z; Lowercase a-z; Numerics 0-9; Period (.); Forward slash (/); Underscore (_); Percent sign (%).


KCF0171E Prototype name is invalid.Explanation: You entered an invalid prototype name.User Response: The prototype name must consist of between 1 to 48 characters. The following characters are allowed: Uppercase A-Z; Lowercase a-z; Numerics 0-9; Period (.); Forward slash (/); Underscore (_); Percent sign (%).

KCF0172E Parameter list is invalid.Explanation: The symbolic parameter definitions field contains an invalid entry.User Response: The symbolic parameter definitions field must consist of zero or more entries in the form <keyword>=<value>, separated by commas. The <keyword> portion consists of 1 to 48 alphanumeric characters. The <value> portion contains 1 or more non-blank character.

KCF0173E Invalid start hour.Explanation: The Hour field within Start Time contains an invalid value.User Response: Enter a number between 0 and 23 which indicates the hour in which the scheduled action should start.

KCF0174E Invalid start minute.Explanation: The Minute field within Start Time contains an invalid value.User Response: Enter a number between 0 and 59 which indicates the minute within the hour in which the scheduled action should start.

KCF0175E Invalid start month.Explanation: The Month field within Start Time contains an invalid value.User Response: Enter a number between 1 and 12 which indicates the month within the year in which the scheduled action should start.

KCF0176E Invalid start day.Explanation: The Day field within Start Time contains an invalid value.User Response: Enter a number between 1 and 31 which indicates the day within the month in which the scheduled action should start.

KCF0177E Invalid start year.Explanation: The Year field within Start Time contains an invalid value.User Response: Enter a 4 digit number which indicates the year in which the scheduled action should start.

KCF0178E Invalid last hour.Explanation: The Hour field within Last Start Time contains an invalid value.User Response: Enter a number between 0 and 23 which indicates the last hour in which the scheduled action should start.

KCF0179E Invalid last minute.Explanation: The Minute field within Last Start Time contains an invalid value.User Response: Enter a number between 0 and 59 which indicates the last minute within the hour in which the scheduled action should start.


KCF0180E Invalid last month.Explanation: The Month field within Last Start Time contains an invalid value.User Response: Enter a number between 1 and 12 which indicates the last month within the year in which the scheduled action should start.

KCF0181E Invalid last day.Explanation: The Day field within Last Start Time contains an invalid value.User Response: Enter a number between 1 and 31 which indicates the last day within the month in which the scheduled action should start.

KCF0182E Invalid last year.Explanation: The Year field within Start Time contains an invalid value.User Response: Enter a 4 digit number which indicates the last year in which the scheduled action should start.

KCF0183E Invalid reschedule hours.Explanation: The Reschedule Hours entry field contains an invalid value.User Response: Enter a numeric value which indicate how often the scheduled action should be rescheduled.

KCF0184I Are you sure you wish to delete this object?.Explanation: You have asked to delete a configuration object. The configuration product requires a confirmation from you before proceeding.User Response: Select the ’Yes’ button to confirm the delete; select ’No’ if you don’t wish to delete the object.

KCF0185I Are you sure you wish to delete the selected objects?.Explanation: You have asked to delete one or more configuration objects. The configuration product requires a confirmation from you before proceeding.User Response: Select the ’Yes’ button to confirm the delete; select ’No’ if you don’t wish to delete the object.

KCF0186I Update defined database from actual resources?.Explanation: You have selected the Update Defined from Actual option. The configuration product requires a confirmation from you before proceeding.User Response: Select the ’Yes’ button to confirm the update request; select ’No’ if you don’t wish to perform the update.

KCF0187I Update actual resources from defined database?.Explanation: You have selected the Update Actual from Defined option. The configuration product requires a confirmation from you before proceeding.User Response: Select the ’Yes’ button to confirm the update request; select ’No’ if you don’t wish to perform the update.

KCF0188I Discover new resources?.Explanation: You have selected the Discover new resources option. The configuration product requires a confirmation from you before proceeding.User Response: Select the ’Yes’ button to confirm the discover request; select ’No’ if you don’t wish to perform the discover.


KCF0189E Last run time must be at least 15 minutes later than start time.Explanation: The Last Start Time for a scheduled action must be at least 15 minutes past the Start Time.User Response: Modify either the Last Start Time or the Start Time to ensure that there is at least 15 minutes difference between them.

KCF0190E The Configuration Manager did not send a response to the last request.Explanation: A request was sent to the Configuration Agent, but no response was received. The status of the request is unknown.User Response: Collect the CMS and CMW log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0191I Do you wish to connect these two objects?.Explanation: You have dragged and dropped one object on top of another, indicating that you want to build a connection between the two object. The configuration product requires a confirmation from you before proceeding.User Response: Select the ’Yes’ button to confirm the connection request; select ’No’ if you don’t wish to perform the connection request.

KCF0193E A time-out occurred waiting for a response from the Configuration Manager Do you want to continue to wait?.Explanation: The workstation has sent a request to the Configuration Manager, but did not receive a response within the required time period.User Response: Select the ’Yes’ button to continue waiting for the response; select ’No’ to stop waiting and cancel the last request.

KCF0194E Background request aborted.Explanation: The workstation has sent a request to the Configuration Manager, but did not receive a response within the required time period. You indicated that you did not want to continue waiting for the response.User Response: Re-try the request. If the problem persists, collect the CMS and CMW log files, restart the CMS and the CMW, and call Candle Customer Support.

KCF0195E Last operation did not complete. Please retry.Explanation: A program exception occurred in the workstation during the processing of the last request. The request was not processed.User Response: Re-try the request. If the problem persists, collect the CMS and CMW log files, restart the CMS and the CMW, and call Candle Customer Support.

KCF0196E Window operation did not complete. Please retry.Explanation: A program exception occurred in the workstation during the processing of the last request. The request was not processed.User Response: Re-try the request. If the problem persists, collect the CMS and CMW log files, restart the CMS and the CMW, and call Candle Customer Support.

KCF0197I You have the requested access.Explanation: You selected the ’Check authorization for’ option for a configuration object. The Configuration Manager has confirmed that you have sufficient authorization to the object and all of it’s subordinate objects.User Response: None.


KCF0198E This is an invalid name for this type of object.Explanation: You have requested that a new configuration object be created; however, you provided an invalid name for the object.User Response: Re-try the request, and provide a valid name. Most valid configuration names must consist of between 1 to 48 characters. The following characters are allowed: Uppercase A-Z; Lowercase a-z; Numerics 0-9; Period (.); Forward slash (/); Underscore (_); Percent sign (%).

KCF0199S A Version mismatch was detected between the CMW and the Configuration Manager.Explanation: The version of the Configuration Manager software running in the CMS is incompatible with the configuration software running in your workstation.User Response: Ensure that compatible version of the configuration product are installed in both the CMS and the CMW. A software upgrade of one of these components may be required.

KCF0200S The Configuration Manager CMS component is either missing or is an earlier version which is incompatible with the Configuration Manager CMW component.Explanation: The version of the Configuration Manager software running in the CMS is incompatible with the configuration software running in your workstation.User Response: Ensure that compatible version of the configuration product are installed in both the CMS and the CMW. A software upgrade of one of these components may be required.

KCF0201S The Configuration Manager CMS component needs to be at the same level as the CMW component.Explanation: The version of the Configuration Manager software running in the CMS is incompatible with the configuration software running in your workstation.User Response: Ensure that compatible version of the configuration product are installed in both the CMS and the CMW. A software upgrade of one of these components may be required.

KCF0202S An unknown error code was received during initialization:.Explanation: The workstation received an unanticipated response from the CMS when it attempted to make contact.User Response: Ensure that the Configuration Manager is correctly installed at the CMS. If the problem persists, collect the CMS and CMW log files and call the Candle Customer Support.


KCF0203S Your request failed because the navigation path to base object was not found.Explanation: You requested that the configuration product either select or open the settings for another object in the configuration. This could be the base object for the currently selected object, or it could be an object identified in the Validation report.User Response: The currently selected object may have been deleted or altered. Refresh the current tree using the Refresh pop-up menu option (for CMW, the Refresh now option from the View pull-down menu), and re-try the operation. If you are displaying the Validation report, close the report window and re-execute the Validate request.

KCF0204E The base object exists in the other tree. Open the other tree, then retry the operation.Explanation: You requested that the configuration product either select or open the settings for another object in the configuration; however, the other object exists within a configuration tree (defined or prototype) that is not currently open. The request cannot be processed.User Response: Open up the other tree from the Configuration Manager - Icons window and re-try the request.

KCF0205I Do you want to run this action in the background?.Explanation: You have requested that an Update, View Discrepancies, Discovery, Validate, or Delete action be performed. Because this is potentially a long-running activity, it is possible to run this action as a background task so that you workstation is not locked.User Response: Select ’Yes’ to run this action in the background. The Configuration Manager will automatically create a scheduled action and return the name of this action to you. The action will be run as a background task, and your workstation will be freed up.

KCF0206I The requested action was completed successfully.Explanation: The action that you requested was run successfully.User Response: None.

KCF0207E Your request failed because the specified file @1 cannot be opened.Explanation: You attempted to import or export configuration data to file @1; however, the file could not be opened, and your request could not be processed.User Response: Determine why the file could not be opened. For export requests, ensure that you have the proper authorities to create and/or write to the file, and that adequate disk space is available. For import requests, ensure that the file exists and that you have the authority to read the file.

KCF0208I Configuration data successfully exported to file @1.Explanation: Your data was successfully exported to file @1.User Response: None.

KCF0209I Configuration data successfully imported from file @1.Explanation: Your data was successfully imported from file @2.User Response: None.


KCF0210E The Configuration Manager cannot create this resource because it is dynamic.Explanation: You requested that an actual resource be created from the a defined resource. However, the defined resource is dynamic, and an actual dynamic resource cannot be created by the Configuration Manager.User Response: None.

KCF0211E The requested configuration object was not found.Explanation: You entered a search request; however, there were no objects in the configuration which matched your search criteria.User Response: Reenter your search request, specifying a different search criteria.

KCF0212E Your request failed. A backup request is already in process.Explanation: You requested that a backup copy of the configuration database be made; however, another backup request is currently being processed.User Response: Wait until the other backup request is complete, then re-enter your request.

KCF0213E Your request failed. The Configuration Manager was unable to create a cursor for the database. Status = @1.Explanation: You requested that a backup copy of the configuration database be made; however, the Configuration Manager was unable to open a cursor to read the contents of the database.User Response: Re-try the request. If the problem persists, collect the CMS log file, restart the CMS and the CMW, and call Candle Customer Support.

KCF0214E Your request failed. The Configuration Manager was unable to write the data to the backup file. SAMRC = @1.Explanation: You requested that a backup copy of the configuration database be made; however, the Configuration Manager was unable to write the contents of the database to the backup file.User Response: Ensure that there is sufficient disk space for the backup file.

KCF0215E Your request failed. The Configuration Manager was unable to read the database. Status = @1.Explanation: You requested that a backup copy of the configuration database be made; however, the Configuration Manager was unable to read the contents of the database.User Response: Re-try the request. If the problem persists, collect the CMS log file, restart the CMS and the CMW, and call Candle Customer Support.

KCF0216I The configuration data base was successfully backed up to @1.Explanation: A backup copy of the configuration data base was successfully written to the file.User Response: None.


KCF0217E You do not have the proper authorization to backup the configuration database.Explanation: You made a request to backup the configuration database; however, your userid does not have the proper authority to perform this operation.User Response: Check with your security administrator. Your userid must have at least ’Update’ access to the ADMIN.BACKUP security profile in order to backup the configuration database.

KCF0218E Symbolic parameter is invalid.Explanation: You attempted to create or replace the symbolic variable associated with this object; however, either the symbolic variable name or it’s value is not valid.User Response: The variable name must consist of between 1 to 48 characters. The following characters are allowed: Uppercase A-Z; Lowercase a-z; Numerics 0-9; Period (.); Forward slash (/); Underscore (_); Percent sign (%).

KCF0219E You must select a relationship for the attribute.Explanation: You selected the name of an attribute on the Advanced tab of the Search configuration dialog; however, you didn’t select a valid entry from the relationship drop-down list.User Response: Select a relationship and a value to be used for searching. In order for a configuration object to match your search criteria, the value of the attribute for the object must be consistent with the selected relationship and value.

KCF0220E Selected value is invalid.Explanation: You selected the name of an attribute on the Advanced tab of the Search configuration dialog; however, you didn’t key in a valid value to compare with the attribute. This can occur when you specify an attribute that only takes numeric values, and you provided a non-numeric value.User Response: Correct the value field and re-issue the request.

KCF0221E Date is invalid.Explanation: You entered an invalid date in either the ’Last modified’ page of the ’Find’ notebook or the ’Date’ field of the ’Column filter’ dialog.User Response: Correct the date and re-issue the request.

KCF0222E Resource name mask @1 is too long or invalid.Explanation: You entered a resource name mask on the ’Column filter’ dialog box that is either invalid, too long, or too complex.User Response: Correct the resource name mask and re-issue the request.

KCF0223E Userid mask @1 is too long or invalid.Explanation: You entered a userid mask on the ’Column filter’ dialog box that is either invalid, too long, or too complex.User Response: Correct the userid mask and re-issue the request.


KCF0224E Name mask is too long or invalid.Explanation: You entered a name mask on the ’Name’ page of the ’Find’ notebook that is either invalid, too long, or too complex.User Response: Correct the name mask and re-issue the request.

KCF0225E Database backup operation could not be completed because the Configuration Manager is being quiesced.Explanation: You requested a backup operation of the configuration database; however, the backup operation could not be completed, because the Configuration Manager is quiescing.User Response: Restart the Configuration Manager on the CMS, and re-enter your request to backup the configuration database.

KCF0226S A fatal exception has occurred. A Configuration Manager thread has attempted to acquire too many locks.Explanation: During the processing of your last request, a thread running in the Configuration Manager attempted to acquire more locks than is supported.User Response: Collect the CMS log files. Restart the CMS and the CMW. Call Candle Customer Support.

KCF0227E Cannot Create Resource in Database, Type=@1, Resource=@2, Code=@3 Import Stopped.Explanation: None.User Response: None.

KCF0228E Internal Error @1 Processing Resource @2 Import Stopped.Explanation: None.User Response: None.

KCF0229E Unknown Attribute Name=@1, Value=@2 Import Stopped.Explanation: None.User Response: None.

KCF0230E Unknown Data Type=@1, Level=@2 Import Stopped.Explanation: None.User Response: None.

KCF0231E Data out of Sequence, Type=@1, Level=@2 Import Stopped.Explanation: None.User Response: None.

KCF0232E Unknown @1 Tag @2 Found Import Stopped.Explanation: None.User Response: None.

KCF0233E Your request failed. Object @1 is not based on a prototype.Explanation: You selected the "Revert to Base Object" for the specified object; however, the object is not based on a prototype.User Response: None - the "Revert to Base Object" is not applicable to an object which is not based on a prototype.


KCF0234W No action performed. Object @1 has no overriding attributes.Explanation: You selected the "Revert to Base Object" for the specified object; however, no action was required because the object did not contain any overriding properties.User Response: None.

KCF0235I Revert to base object successful.Explanation: Your request to "Revert to Base Object" was successfully processed. All overriding properties contained within the object were deleted, and the object now inherits all of it’s properties from the prototype it is based on.User Response: None.

KCF0236E Your request failed because the specified file @1 is too large to be imported.Explanation: You attempted to import configuration data from file @1; however, the file could not be imported because it is too large.User Response: Specify a smaller import file. The file can be no larger than 2GB in size.

KCF0237E Invalid resource group limit @1.Explanation: You entered an invalid value for the "Limit number resources to" field in the Product Options area of the Configuration workspace (for CMW, the Configuration options page of the Configuration Manager settings.) The value must be numeric and at least 20.User Response: Correct the "Limit number resources to" field.

KCF0238E The import file contains an invalid attribute value @2 for tag @1 Import request not processed.Explanation: You attempted to import a file into the configuration; however, there is an XML tag in the import file which contains an invalid value. The import file is not processed.User Response: Correct the import file and re-enter the Import request.

KCF0239E The import file contains an invalid type of object or object hierarchy. Import request not processed.Explanation: You attempted to import a file into the configuration; however, the type of object specified within the import file is not valid for the target object. For example, an attempt was made to import a resource directly within a configured system group.User Response: Correct the import file and re-enter the Import request.

KCF0240E Invalid replication count @1.Explanation: You specified that you want to replicate a configuration object. However, you entered a invalid numeric value as the replication count.User Response: Specify a numeric value for the replication count.

KCF0241E Invalid Import File XML has missing tags.Explanation: You attempted to import a file into the configuration; however, the XML file has an invalid structure (possibly missing end tags).User Response: Correct the import file and re-enter the Import request.


KCF0242W Imported attribute @1 is not valid for object type.Explanation: You attempted to import a file into the configuration; however, the XML file included a tag that was inappropriate for the type of object being imported.User Response: Correct the import file and re-enter the Import request.

KCF0244E Export of Attribute @1 failed, XML Size exceeds maximum. Export Stopped Explanation: The attribute identified by @1 could not be exported.System Action: The export process terminates.User Response: Contact Candle Customer Service and Satisfaction.

KCF0245E Export of Resource @1 failed,MQSC Command Size exceeds maximum. Export StoppedExplanation: The resource identified by @1 could not be exported.System Action: The export process terminates.User Response: Contact Candle Customer Service and Satisfaction.

KCF1001E Host name column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.

KCF1002E Queue manager name column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.

KCF1003E Queue name column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.


KCF1004E Queue type column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.

KCF1006E Channel name column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.

KCF1007E Channel type column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.

KCF1008E Namelist column is not present in the viewExplanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration but the selected WebSphere MQ resource could not be found.System Action: The attempted action cannot be completed.User Response: Open the Properties page for the view and use the Query Editor to add the column to the view. Save the workspace and then try again.

KCFCM001I Candle Configuration Manager startup completeExplanation: The Configuration Manager has completed initialization successfully.System Action: None.User Response: None.

KCFCM002E Unable to open configuration databaseExplanation: The Configuration Manager was unable to open the RKCFAPLD file containing the configuration data.System Action: The Configuration Manager terminates.User Response: Search the CMS log, looking for other messages relating to this file, to determine the exact reason that the file could not be opened. Verify the presence of the file. If necessary, contact Candle Customer Support.


KCFCM003E Unable to load DLL for @1Explanation: The Configuration Manager was unable to load the application-specific library identified by @1.System Action: The Configuration Manager cannot manage configuration data associated with this application without loading this library. If this is the only application-specific library associated with the configuration product, the Configuration Manager terminates.User Response: Search the CMS log, looking for other messages relating to this library, to determine the exact reason that the library could not be loaded. Verify the presence of the library. If necessary, contact Candle Customer Support.

KCFCM004E Internal Error @1- Function @2 - RC @3Explanation: An internal error has occurred in the Configuration Manager. The internal error type is @1; the function that the error was detected in is @2; the return code is @3.System Action: The currently active function ends prematurely.User Response: Contact Candle Customer Support.

KCFCM005E Error from RCA. Function = @1 RC @2 Reason @3 Name =@4Explanation: An error was detected from a Configuration Agent. The function that detected the error is @1. The return code and reason code are @2 and @3, respectively. The name of the Configuration Agent is @4.System Action: The currently active function ends prematurely.User Response: If the return code and reason code represent an application-specific return code (such as from MQSeries), then look them up in the IBM-provided manual.

KCFCM006E Unsupported managed system type @1 received from RCA @2 - ignoredExplanation: The Configuration Agent @2 has reported it’s configured system type as @1 - this type is ignored and unsupported.System Action: The Configuration Agent is ignored.User Response: Make sure that the Configuration Agent identified by @2 is fully supported by the configuration applications you have installed in the CMS.

KCFCM008E Database version @1 incompatible with Configuration ManagerExplanation: The configuration database has been altered by a more recent version (@1) of the Configuration Manager, which is not compatible with the version of the product you are now trying to run.System Action: The Configuration Manager cannot continue initialization.User Response: You must either run the more recent version of the Configuration Manager, or you must restore the configuration data base files from a backup copy that was created prior to being touched by the more recent version.

KCFCM009I Configuration database successfully loadedExplanation: The configuration database has been successfully loaded into storage.System Action: The configuration product is now ready for use.User Response: None.


KCFCM012I Unable to delete resource group prototype @1 - it is in useExplanation: A user made an attempt was made to delete resource group prototype identified by @1; however, it cannot be deleted because it is in use.System Action: The object is not deleted.User Response: Make sure that the prototype is not in using prior to attempting to delete it.

KCFCM013I Unable to delete resource prototype @1- it is in useExplanation: A user made an attempt was made to delete resource prototype identified by @1; however, it cannot be deleted because it is in use.System Action: The object is not deleted.User Response: Make sure that the prototype is not in using prior to attempting to delete it.

KCFCM014I Unable to delete configured system prototype @1 - it is in useExplanation: A user made an attempt was made to delete the configured system prototype identified by @1; however, it cannot be deleted because it is in use.System Action: The object is not deleted.User Response: Make sure that the prototype is not in using prior to attempting to delete it.

KCFCM015E RCA Request Retry Timeout for function %sExplanation: A request was sent to a Configuration Agent, but the agent did not respond with the requested data within the current agent timeout limit.System Action: The currently active function ends prematurely.User Response: Examine the CMS and agent logs to determine why the Configuration Agent did not respond.

KCFCM016E Cannot bring sys @1 online; thru sys @2 not foundExplanation: The Configuration Manager cannot bring configured system @1 online, because the ’through’ configured system, @2, cannot be located.System Action: The currently active function ends prematurely.User Response: Correct the definition of the configured system to reference a valid ’through’ configured system.

KCFCM017E Cannot bring sys @1 online; thru sys @2 not onlineExplanation: The Configuration Manager cannot bring configured system @1 online, because the ’through’ configured system, @2, is not online.System Action: The currently active function ends prematurely.User Response: Ensure that the ’through’ configured system is active and available.


KCFCM018E Cannot bring sys @1 online; thru sys @2 not direct attachExplanation: The Configuration Manager cannot bring configured system @1 online, because the ’through’ configured system, @2, is not defined as directly attached.System Action: The currently active function ends prematurely.User Response: Change the definition of configured system @1 so that is either directly attached, or is attached ’through’ a configured system which is directly attached.

KCFCM019E Cannot bring sys @1 online; required RCA @2 not availableExplanation: The Configuration Manager cannot bring configured system @1 online, because the Configuration Agent @2 is not active.System Action: The currently active function ends prematurely.User Response: Start the Configuration Agent @2.

KCFCM020E Unable to connect with configured system %sExplanation: The Configuration Agent was unable to connect with the configured system identified by @1.System Action: The currently active function ends prematurely.User Response: Examine the agent log to determine why the agent was unable to connect with the configured system.

KCFCM021I Successfully connected to configured system @1Explanation: The Configuration Agent has established a connection with the configured system @1.System Action: None.User Response: None.

KCFCM022I Successfully started and connected to configured system @1Explanation: The Configuration Agent has started configured system @1 and established a connection with it.System Action: None.User Response: None.

KCFCM023E Unable to start configured system @1Explanation: The Configuration Agent was unable to start the configured system identified by @1.System Action: The currently active function ends prematurely.User Response: Examine the agent log to determine why the agent was unable to start the configured system.

KCFCM024I Successfully created and connected to configured system @1Explanation: The Configuration Agent has created and started configured system @1 and established a connection with it.System Action: None.User Response: None.


KCFCM025E Unable to create configured system %sExplanation: The Configuration Agent was unable to create the configured system identified by @1.System Action: The currently active function ends prematurely.User Response: Examine the agent log to determine why the agent was unable to create the configured system.

KCFCM026I Successfully discovered configured system @1Explanation: As a result of a Discover request, the Configuration Manager discovered the configured system identified by @1.System Action: A definition for the configured system is added to the configuration database.User Response: None.

KCFCM027I Discovered duplicate system @1 - ignoredExplanation: As a result of a Discover request, the Configuration Manager discovered the configured system identified by @1; however, a definition for this configured system already exists in the configuration database.System Action: The discovered configured system definition is ignored.User Response: None.

KCFCM028E Maximum number of @1 objects generated, cannot create new objectExplanation: The maximum number of objects of the type specified by @1 has been created.System Action: The new object cannot be created.User Response: Contact Candle Customer Support.

KCFCM030W KEY1 @1 Failed Function:@2 File=@3 Status=@4 Reason=@5Explanation: The KEY1 service detected an error in the processing of one of the configuration files. @1 identifies the attempted operation; @2 identifies the function which detected the error; @3 contains the name of the file, @4 and @5 contain the status and reason.System Action: The currently active function ends prematurely. Under many circumstances, the Configuration Manager may be shut down.User Response: Contact Candle Customer Support.

KCFCM031E DataBase Bad Work Unit Status @1Explanation: In attempting to migrate a pre-Version 350 configuration database, the Configuration Manager detected a database work unit with bad status @1.System Action: Initialization of the Configuration Manager is ended abnormally.User Response: Contact Candle Customer Support.


KCFCM032E Handle@1 from selection group no longer found in configurationExplanation: A user requested an action against a set of configuration objects, however one of the members of the set, identified by @1, could not be located in the configuration.System Action: The currently active function ends prematurely.User Response: Re-execute the requested action, specifying only existing configuration objects.

KCFCM033I Candle Configuration Manager shutdown startedExplanation: The Configuration Manager has begun the process of shutting itself down.System Action: Shutdown of the Configuration Manager proceeds. The KCFCM034I message should follow shortly, indicating that shutdown has completed.User Response: None.

KCFCM034I Candle Configuration Manager shutdown completeExplanation: The Configuration Manager has completed shutdown processing.System Action: None - the Configuration Manager is no longer running.User Response: None.

KCFCM035I Configuration Agent@1 is now onlineExplanation: The Configuration Agent identified by @1 is now connected to the Configuration Manager.System Action: None.User Response: None.

KCFCM036I Configuration Agent @1 is now offlineExplanation: The Configuration Agent identified by @1 is no longer connected to the Configuration Manager.System Action: None.User Response: If the Configuration Agent was not taken down deliberately, you should scan the agent log to determine why it is no longer communicating with the CMS. If necessary, contact Candle Customer Support.

KCFCM037E @1 Exception caught in Unit @2 Function @3Explanation: A program exception identified by @1 was detected in the Configuration Manager, within unit @2 and function @3.System Action: Diagnostic information is written to the CMS log. The Configuration Manager is shutdown.User Response: Contact Candle Customer Support.


KCFCM038I Configuration quiesce startedExplanation: The Configuration Manager has started to quiesce itself in preparation for a shutdown. The shutdown was either requested, or resulted from an unrecoverable error condition.System Action: The Configuration Manager quiesces all activity in preparation for a shutdown. The KCFCM033I message should soon appear, indicating that shutdown processing has begun.User Response: If you believe that the Configuration Manager is shutting down because of an error, search through the prior entries in the CMS log, looking for other messages indicating the nature of the error.

KCFCM040I Successfully loaded application library @1 for @2 Address = @3Explanation: This message indicates that the Configuration Manager has successfully loaded the application-specific library identified by @2.System Action: None.User Response: None.

KCFCM041I Database error detected - configuration quiesce initiatedExplanation: The Configuration Manager has detected an unrecoverable database error.System Action: The Configuration Manager is shutdown.User Response: Contact Candle Customer Support.

KCFCM042I Auto Import successful for file @1Explanation: At startup time, the Configuration Manager detected the presence of the configuration import file @1, and has read and imported the data.System Action: The data from the import file was read and saved in the configuration data base.User Response: None.

KCFCM043E Error @1 locating import filesExplanation: At startup time, the Configuration Manager was unable to locate the configuration import files.System Action: Initialization of the Configuration Manager proceeds without the import data.User Response: If your CMS is running on OS/390, ensure that the RKANDATV DD statement is present in the started task JCL, and that it identifies a proper Partitioned Data Set; On distributed platforms, ensure that the RKCFCDI sub-directory is defined.

KCFCM044E Unable to open import file @1 - error code @2Explanation: At startup time, the Configuration Manager detected the presence of the configuration import file @1; however, it encountered a problem attempting to read the data.System Action: The import file is ignored.User Response: Determine why the Configuration Manager was unable to open the import file. Restart the Configuration Manager in order to re-initiate the import process.


KCFCM051I @1 configured systems autodiscovered from agent @2Explanation: Auto-discovery processing was performed for the Configuration Agent identified by @2. @1 new configured systems were discovered.System Action: The autodiscovered configured systems were added to the configuration database.User Response: None.

KCFCM052E Exception Type = @1Explanation: This message is produced after an exception condition has occurred within the Configuration Manager. This message indicates the type of exception.System Action: None - this is one of several diagnostic messages that appear in the CMS log after an exception.User Response: Contact Candle Customer Support.

KCFCM053E Exception Address = @1Explanation: This message is produced after an exception condition has occurred within the Configuration Manager. This message indicates the memory address where the exception took place.System Action: None - this is one of several diagnostic messages that appear in the CMS log after an exception.User Response: Contact Candle Customer Support.

KCFCM054E Storage Access Address = @1Explanation: This message is produced after an exception condition has occurred within the Configuration Manager. This message indicates the address of the memory being accessed if a storage access violation is detected.System Action: None - this is one of several diagnostic messages that appear in the CMS log after an exception.User Response: Contact Candle Customer Support.

KCFCM055E Configuration Agent did not provide requested data for configured system @1 - probable timeoutExplanation: A request was sent to a Configuration Agent for the configured system identified by @1, but the agent did not respond with the requested data.System Action: The currently active function ends prematurely.User Response: This was likely caused by a timeout condition in the communication between the agent and the CMS. Examine the CMS and agent logs to determine why the Configuration Agent did not respond.

KCFCM056I Configuration Manager External security is disabledExplanation: At startup time, the Configuration Manager determined that the external security feature is disabled.System Action: No security validation checks will be performed by the Configuration Manager.User Response: None.


KCFCM057I Configuration Manager External security is enabledExplanation: At startup time, the Configuration Manager determined that the external security feature is enabled, using the OS/390 System Authorization Facility (SAF).System Action: Access to configuration objects by users of the configuration product will be subject to security checks.User Response: None.

KCFCM058E Persistent Data Store Failure in function @1 - Error Code @2Explanation: An error status was returned from the CMS Persistent Data Store facility. @1 identifies the function that detected the error. @2 indicates the error code that was returned from the PDS facility.System Action: Audit log records cannot be read from or written to the Persistent Data Store.User Response: Investigate why the PDS is having problems by examining the log. If necessary, contact Candle Customer Support.

KCFCM059E Unable to open Audit Log file @1Explanation: The Configuration Manager was unable to open the audit log file identified by @1.System Action: Audit log records cannot be read from or written to the audit log file.User Response: Investigate why the Configuration Manager is having problems accessing the log file by examining the log. If necessary, contact Candle Customer Support.

KCFCM060E Error writing to Audit Log file @1Explanation: The Configuration Manager was unable to write to the audit log file identified by @1.System Action: Audit log records cannot be written to the audit log file.User Response: Investigate why the Configuration Manager is having problems accessing the log file by examining the log. If necessary, contact Candle Customer Support.

KCFCM062I Candle Configuration Manager Starting up. Entry = @1 Object = @2 Build date/time = @3Explanation: This message is written when the Configuration Manager is started within the CMS.System Action: Initialization of the Configuration Manager proceeds.User Response: None. Note - this message contains diagnostic information that may be of value to Candle Customer Support.

KCFCM063E Candle Configuration Manager Shutting down - no configuration applications definedExplanation: At startup time, the Configuration Manager detected that there were no valid configuration application libraries to load.System Action: The Configuration Manager shuts down.User Response: Examine the CMS log to determine why no configuration application libraries were available to the Configuration Manager.


KCFCM064E Unable to open database log file RC = @1Explanation: The configuration application was unable to open the database log file RKCFDLOG.System Action: The Configuration Manager shuts down.User Response: Determine why the Configuration Manager was unable to open the RKCFDLOG file. If necessary, contact Candle Customer Support.

KCFCM065E Failure writing to database log file RC = @1Explanation: The configuration application was unable to open the database log file RKCFDLOG.System Action: The Configuration Manager shuts down.User Response: Determine why the Configuration Manager was unable to open the RKCFDLOG file. If necessary, contact Candle Customer Support.

KCFCM066E Failure recovering configuration database RC = @1Explanation: At startup time, an error occurred while attempting to recover interrupted database work units.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.

KCFCM067I Database work unit recovery started for @1Explanation: At startup time, the Configuration Manager has found a database work unit in a semi-committed status.System Action: The Configuration Manager attempts to recover and commit the work unit. The KCFCM068I message should follow in the CMS log at some point, indicating that recovery for all work units has completed.User Response: None.

KCFCM068I Database work unit recovery completed for all work unitsExplanation: The Configuration Manager has completed recovery processing for all semi-committed work units.System Action: None - initialization of the Configuration Manager proceeds.User Response: None.

KCFCM069E Database work unit recovery failed - return code = @1Explanation: The Configuration Manager was unable to perform recovery processing on the semi-committed work unit identified by @1.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.

KCFCM070I Database successfully migrated from pre-V350 systemExplanation: Version 350 of the Configuration Manager is being run for the first time, and has successfully migrated the configuration data in Version 350 format.System Action: None.User Response: None.


KCFCM071E Failure migrating database from pre-V350 system - return code = @1Explanation: An error has occurred migrating the data from a pre-Version 350 configuration database.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.

KCFCM072E Unable to repair configuration database RC = @1Explanation: The KCF_REPAIR environmental variable was set to a value of YES, indicating that the Configuration Manager should repair the configuration database; however, an error was encountered, and the database could not be repaired.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.

KCFCM073I Configuration database successfully repairedExplanation: The KCF_REPAIR environmental variable was set to a value of YES, indicating that the Configuration Manager should repair the configuration database; the database was successfully repaired.System Action: Initialization continues.User Response: None.

KCFCM074E Duplicate Key detected in configuration databaseExplanation: The Configuration Manager has encountered a duplicate key in the configuration data base.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support. If you have a recent backup of the configuration database, you might consider restoring from this backup.

KCFCM075E Unable to open backup file @1 return code = @2Explanation: You requested that a backup of the configuration database be taken. However, the Configuration Manager was unable to open the backup file.System Action: The request to backup the configuration database is not completed.User Response: On OS/390, the backup file must refer to a pre-defined, sequential data set. Ensure that this data set exists. Otherwise, ensure that a valid file name is specified.

KCFCM076E Unable to open backup secondary cursor. Status = %IExplanation: The user has requested that a backup of the configuration database be taken. However, the Configuration Manager was unable to create a KEY1 cursor for reading the configuration data base.System Action: The request to backup the configuration database is not completed.User Response: Contact Candle Customer Support.


KCFCM077E Browse for backup failed. Status = @1Explanation: The user has requested that a backup of the configuration database be taken. However, the Configuration Manager was unable to read the configuration data base.System Action: The request to backup the configuration database is not completed.User Response: Contact Candle Customer Support.

KCFCM078I Backup successful to file @1Explanation: The requested backup operation was completed successfully.System Action: None.User Response: None.

KCFCM079E Memory quiesce mode enteredExplanation: The amount of heap storage used by the Configuration Manager has exceeded the value of the KCF_HEAP_QUIESCE_VALUE environmental variable.System Action: The Configuration Manager will attempt to release storage associated with inactive configuration objects - this could cause response time delays in servicing future requests, as those configuration objects will have to be loaded back in from the database.User Response: Ensure that the KCF_HEAP_QUIESCE_VALUE is set to an appropriate value - if it too small, it can cause response time problems.

KCFCM080I Memory quiesce mode exitedExplanation: The amount of heap storage used by the Configuration Manager is now less than the value of the KCF_HEAP_QUIESCE_VALUE environmental variable, indicating that the Configuration Manager is no longer in memory quiesce mode.System Action: Configuration storage management resumes normal mode.User Response: None.

KCFCM081E Unable to create cursor for alternate index. Code = @1Explanation: The Configuration Manager was unable to create a KEY1 cursor for accessing the RKCFAPLA file.System Action: The Configuration Manager reconstructs the contents of the RKCFAPLA file.User Response: Contact Candle Customer Support.

KCFCM082E Unable to create sequential cursor for data base. Code = @1Explanation: The Configuration Manager was unable to create an alternate KEY1 cursor for accessing the configuration data base.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.


KCFCM083E Unable to do sequential read from data base. Code = @1Explanation: The Configuration Manager was unable to read from the configuration database in an effort to create the RKCFAPLA file.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.

KCFCM084I Alternate index RKCFAPLA was successfully builtExplanation: The RKCFAPLA alternate index file was successfully built.System Action: None.User Response: None.

KCFCM085E Alternate index RKCFAPLA could not be rebuilt - status = @1Explanation: The Configuration Manager failed in it’s attempt to rebuild the RKCFAPLA file.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support.

KCFCM086I @1records in alternate index RKCFAPLA were successfully deletedExplanation: In preparation for rebuilding the RKCFAPLA file, @1 records were deleted from the file.System Action: None - this is a normal part of rebuilding this file.User Response: None.

KCFCM087E Missing Key detected in configuration databaseExplanation: The Configuration Manager has encountered a missing record in the configuration data base.System Action: The Configuration Manager shuts down.User Response: Contact Candle Customer Support. If you have a recent backup of the configuration database, you might consider restoring from this backup.

KCFCM088I Prototype usage data successfully rebuild for all objectsExplanation: The KCF_REBUILD_PROTO_REFS environmental variable was set to a value of YES, indicating that prototype usage information should be rebuild. The Configuration Manager has successfully completed rebuilding prototype usage information.System Action: None.User Response: None.

KCFCM089E Configuration Name Service KEY1 error. Status = @1 Reason = @2Explanation: A KEY1 error was encountered by the configuration name service. @1 and @2 indicate the status and reason codes, respectively.System Action: The configuration name service is shutdown - the Configuration Manager proceeds without it, but with possibly degraded performance.User Response: Ensure that the RKCFAPLN file is defined and available to the CMS. If necessary, contact Candle Customer Support.


KCFCM090E Configuration Name Service shutdown abnormallyExplanation: The configuration name service was shutdown abnormally.System Action: The configuration name service is shutdown - the Configuration Manager proceeds without it, but with possibly degraded performance.User Response: Scan the CMS log, looking for other messages indicating why the name service has shut down. If necessary, contact Candle Customer Support.

KCFCM091E Configuration Name Service KEY1 open failureExplanation: The configuration name service was unable to open the RKCFAPLN file.System Action: The configuration name service is shutdown - the Configuration Manager proceeds without it, but with possibly degraded performance.User Response: Ensure that the RKCFAPLN file is defined and available to the CMS. If necessary, contact Candle Customer Support.

KCG0000I–KDFCT003 187

KCG0000I–KDFCT003

KCG0000I KCG STARTINGExplanation: The agent to monitor cryptographic coprocessors and services has been started.System Action: Agent initialization proceeds.User Response: None required.Message Type: Informational.

KCG0002F UNABLE TO ACQUIRE AGENT LOCKExplanation: A serialization lock could not be acquired.System Action: The monitoring agent fails initialization and terminates execution.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Fatal error.

KCG0003F UNABLE TO INITIALIZE LOCK WORD ERRNO = return_codeExplanation: An attempt to initialize a serialization lock failed.System Action: The monitoring agent fails initialization and terminates execution.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Fatal error.

KCG0005F UNABLE TO INITIALIZE CONDITION WORD ERRNO = return_codeExplanation: An attempt to initialize a condition word (ECB) failed.System Action: The monitoring agent fails initialization and terminates execution.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Fatal error.

3


KCG0006F UNABLE TO START MONITORING THREAD ERRNO = return_codeExplanation: An attempt to start a monitor thread failed.System Action: The monitoring agent fails initialization and terminates execution.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Fatal error.

KCG0007E iNVALID WAIT SECONDS = invalid_value. DEFAULTING TO default_maximum.Explanation: The maximum wait time specified in the IRAMAN KCG START command of the hilev.rte.RKANCMD(KCGAGST) member is invalid.System Action: The default value for the maximum wait time is used and agent initialization continues.User Response: Update the hilev.rte.RKANCMD(KCGAGST) member to specify a valid value for the maximum wait time in seconds.Message Type: Error.

KCG0010W UNABLE TO ACCESS ICSF ADDRESS SPACE (control_block_name)Explanation: The monitoring agent failed to access data in a control block of the Integrated Cryptographic Service Facility (ICSF) address.System Action: The data sample returns incomplete information, and data collection processing continues.User Response: Verify that the ICSF subsystem is running. If it has not been started, was stopped, or has abnormally terminated, restart the ICSF subsystem address space.Message Type: Warning.

KCG0020I CONNECTION TO ICSF ESTABLISHEDExplanation: The monitoring agent successfully established a cross-memory connection to the ICSF subsystem address space.System Action: The agent proceeds to sample data and inspect ICSF control blocks to satisfy monitoring queries.User Response: None required.Message Type: Informational.

KCG0021W ICSF (CCVT) NOT FOUNDExplanation: An attempt to query the contents of the cryptographic services communications vector (CCVT) failed. This global control block could not be located in common storage.System Action: The agent proceeds to sample data and inspect ICSF control blocks to satisfy monitoring queries.User Response: None required.Message Type: Warning.


KCG0022W KCGEXIT3 NOT INSTALLED IN ICSFExplanation: An attempt to query cryptographic activity failed. Candle control blocks and service call exits installed by load module KCGEXIT3 could not be located. This failure to access control blocks indicates that the ICSF initialization exit KCGEXIT3 has not been installed in the ICSF subsystem.System Action: The agent continues to execute, and periodically tries to monitor cryptographic activity in the ICSF subsystem.User Response: Review the CSFPARM input parameters for the ICSF subsystem to ensure that the KCGEXIT3 exit is specified. Recycle the ICSF subsystem to install the required Candle control blocks and service call exits.Message Type: Warning.

KCG0023W INVALID CSFINSW2, EXPECTED KCGCVTExplanation: An attempt to query cryptographic activity failed. Candle control blocks and service call exits installed by load module KCGEXIT3 could not be located. This failure to access control blocks indicates that the ICSF initialization exit KCGEXIT3 has not been installed in the ICSF subsystem.System Action: The agent continues to execute, and periodically tries to monitor cryptographic activity in the ICSF subsystem.User Response: Review the CSFPARM input parameters for the ICSF subsystem to ensure that the KCGEXIT3 exit is specified. Recycle the ICSF subsystem to install the required Candle control blocks and service call exits.Message Type: Warning.

KCG0024W VERSION MISMATCH KCGEXIT3 = version_level KCG AGENT = version_level

Explanation: An attempt to query cryptographic activity failed. Candle control blocks and service call exits were installed correctly by load module KCGEXIT3, but the KCGEXIT3 load module and the KCG agent originate from incompatible releases or maintenance levels.System Action: The agent continues to execute, and periodically tries to monitor cryptographic activity in the ICSF subsystem.User Response: Ensure that the agent and the KCGEXIT3 load module are at the same maintenance level. Verify that the copy of the KCGEXIT3 load module loaded by the ICSF subsystem is up-to-date. If KCGEXIT3 has been updated recently, recycle the ICSF subsystem to reload the updated version. If the agent has been updated, you must also recycle the agent.Message Type: Warning.

KCG0025W MONITORING IS DISABLED IN ICSFExplanation: An attempt to query cryptographic activity failed. Candle control blocks and service call exits were installed correctly by load module KCGEXIT3, but monitoring is disabled.System Action: The agent continues to execute, and periodically tries to monitor cryptographic activity in the ICSF subsystem.User Response: Refer to messages issued from the ICSF subsystem to determine the cause of the error. If necessary, recycle the ICSF subsystem to clear the error and restart monitoring.Message Type: Warning.


KCG0030W UNABLE TO CONNECT TO ICSF STATUS = reason_codeExplanation: An attempt to query cryptographic activity failed. A cross-memory ALET could not be established with the ICSF subsystem, indicating that the subsystem was stopped or has terminated abnormally. A positive value for the reason code indicates an error as documented for ALESERV ADD macro return codes. A value of -99 indicates that the ICSF subsystem could not be found.System Action: The agent continues to execute, and periodically tries to monitor cryptographic activity in the ICSF subsystem.User Response: Verify that the ICSF subsystem is running. If it has not been started, was stopped, or has terminated abnormally, restart the ICSF subsystem address space.Message Type: Warning.

KCG0040E CANNOT FIND KCG ANCHOR. ICSF QUERY CANCELLED.Explanation: An internal error occurred during a query for ICSF subsystem data. An attempt to access a global anchor block within the agent address space failed.System Action: The agent aborts the query and continues to monitor cryptographic activity.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.

KCG0041E CANNOT FIND KCG ANCHOR. SVCDET QUERY CANCELLED.Explanation: An internal error occurred during a query for service call performance data. An attempt to access a global anchor block within the agent address space failed.System Action: The agent aborts the query and continues to monitor cryptographic activity.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.

KCG0042E CANNOT FIND KCG ANCHOR. TOPUSER QUERY CANCELLED.Explanation: An internal error occurred during a query for top user performance data. An attempt to access a global anchor block within the agent address space failed.System Action: The agent aborts the query and continues to monitor cryptographic activity.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.


KCG0043E CANNOT FIND KCG ANCHOR. ICSF ACCESS CANCELLED.Explanation: An internal error occurred during an attempt to access data in the ICSF subsystem.System Action: The agent aborts cross-memory access and continues to monitor cryptographic activity.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.

KCG0044F CANNOT FIND KCG ANCHOR. AGENT SHUTDOWN INITIATED.Explanation: An internal error occurred during startup of the main performance monitoring thread.System Action: The agent initiates termination of monitoring.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Fatal error.

KCG0060F CANNOT ACQUIRE SHUTDOWN LOCK. ERRNO = error_numberExplanation: An internal error occurred while attempting to acquire a serialization lock used for shutdown detection.System Action: The agent initiates termination of monitoring.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Fatal error.

KCG0061E CANNOT ACQUIRE SVCDET LOCK. ERRNO = error_numberExplanation: An internal error occurred while attempting to acquire a serialization lock used for temporary suspension of data collection during a service call performance query.System Action: The agent initiates termination of monitoring.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.

KCG0062E CANNOT ACQUIRE TOPUSER LOCK. ERRNO = error_numberExplanation: An internal error occurred while attempting to acquire a serialization lock used for temporary suspension of data collection during a query for top user performance.System Action: The agent initiates termination of monitoring.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.


KCG0070E UNABLE TO CONVERT TIME UNITS STATUS = reason_codeExplanation: An internal error occurred while attempting to convert a CPU clock word to the Greenwich Mean Time (GMT) associated with a service call observation.System Action: The agent ignores the service call observation and proceeds to the next observation.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.

KCG0071E UNABLE TO DETERMINE SERVICE INDEX, EXIT = service_call_exit_nameExplanation: An internal error occurred while attempting to determine the service call index number.System Action: The agent ignores the performance call observation and proceeds to the next observation.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Error.

KCG0073W SERVICE TIME TOO LARGE SVC = service_call_exit_name TIME = number_of_millisecondsExplanation: A service call ran longer than the maximum time that can be recorded in a 32-bit word.System Action: The agent ignores the performance call observation and proceeds to the next observation.User Response: Contact Candle Customer Support and report the error. Provide the output of RKLVLOG.Message Type: Warning.

KCG0080W OVERRUN DETECTED CSR = %x STATUS = %y ISNO = %dExplanation: An overrun condition has been detected. The address of the current internal queue cursor is %x, the queue element status is %y, and the observation sequence number is %d.System Action: The potentially corrupted observation is ignored.User Response: No response is required. This warning message indicates a recoverable condition, but you should be concerned if a large number of these overruns are detected. If this message is issued frequently, call Candle Customer Support for further assistance.Message Type: Warning.

KCG9999I KCG TERMINATINGExplanation: The agent to monitor cryptographic coprocessors and services is being terminated.System Action: Agent termination proceeds.User Response: None required.Message Type: Informational.


KCGX030I CRYPTOGRAPHY MONITORING STARTEDExplanation: During ICSF startup, Candle monitoring exits have been installed, and control blocks required for monitoring of cryptographic activity have been established.System Action: ICSF initialization completes.User Response: None required.Message Type: Informational.

KCGX031E ANCHOR ALLOCATION FAILEDExplanation: An attempt to allocate memory for control blocks in the ICSF address space failed. These control blocks must be allocated to record real-time service call performance data.System Action: The KCGEXIT3 load fails to establish a performance monitoring environment and disables monitoring. The agent’s attempt to query performance information will fail, and reported data will be incomplete.User Response: Determine why the control blocks could not be allocated. Verify that sufficient extended virtual storage (above the 16MB line) is available for the ICSF subsystem. Recycle the ICSF subsystem after removing memory constraints.Message Type: Error.

KCGX034F ICSF EXIT TABLE IS EMPTYExplanation: An attempt to read the ICSF exit table (CSFENT) failed because no entries were found in the table. This unexpected condition might be caused by corruption of the internal ICSF subsystem control block.System Action: The KCGEXIT3 exit fails to install the service call exits. Performance monitoring is disabled.User Response: Apply the latest level of maintenance and recycle the ICSF subsystem with an updated KCGEXIT3 load module. Determine why the exit table is empty. Contact Candle Customer Support to report the error and receive further assistance.Message Type: Fatal error.

KCGX035W EXIT = exit_name NOT FOUNDExplanation: The specified service call exit could not be found. Service call exits are installed by the KCGEXIT3 load module during ICSF subsystem startup to capture performance data whenever service calls are issued. The error can occur when IBM removes support for a specific service call exit.System Action: Performance monitoring for the associated service call is ignored. Installation of other service call exits proceeds.User Response: Verify that the current level of product maintenance has been applied. Contact Candle Customer Support and provide the text of the message indicating the missing service call exit.Message Type: Warning.


KCGX036W EXIT = cccccccc REPLACEDExplanation: A user-defined ICSF exit has been found and replaced by a Candle performance monitoring exit. The name of the user-defined exit load module is cccccccc. OMEGAMON XE for IBM Cryptographic Coprocessors requires the use of ICSF service call exits, CSFEXIT3 and CSFEXIT4, for monitoring of service call performance.System Action: The user-defined exit is replaced by the Candle exit.User Response: Determine whether you can use an alternative ICSF exit for your purpose. If so, update the ICSF startup parameters to redirect the exit to one of the exits not used by the Candle monitoring agent, and recycle the ICSF address space. You may need to reprogram the exit. Consult the ICSF documentation for further details.Message Type: Warning.

KCGX051I CRYPTOGRAPHY MONITORING TERMINATEDExplanation: During termination of the ICSF subsystem, Candle monitoring exits have been removed and memory used for control blocks has been released.System Action: ICSF termination proceeds.User Response: None required.Message Type: Informational.

KCNCA001E UNABLE TO OBTAIN PRIVATE STORAGE, COUPLING FACILITY COLLECTION NOT AVAILABLEExplanation: This message comes from the Candle Subsystem’s attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). It indicates that working storage for this subtask cannot be obtained. Data collection is terminated.System Action: None.User Response: Recycle the Candle Subsystem associated with this message. If the problem persists, call Candle Customer Support for further assistance.

KCNCA002E SUBTASK PARMS INVALID, COLLECTION TERMINATEDExplanation: This message comes from the Candle Subsystem's attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). A parameter area passed to the collection subtask does not have the correct identification text (eyecatcher). The subtask must assume the parameters area has been corrupted. Data collection is terminated.System Action: None.User Response: Recycle the Candle Subsystem associated with this message. If the problem persists, call Candle Customer Support for further assistance.


KCNCA003E IXCQUERY XXX_ALLDATA FAILED RC(XXXXXXXX),REASON(XXXXXXXX)Explanation: This message comes from the Candle Subsystem’s attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). The XXX in "XXX_ALLDATA" may be either STR or CF. This message indicates that a severe error occurred while trying to get IXCQUERY data. The return code (RC) and reason code (REASON) from the attempt are documented and can be found in the IBM manual MVS Programming: Sysplex Services Reference under Return and Reason Codes for IXCQUERY. This message may appear up to 6 times if the problem persists. After 6 attempts the Candle Subsystem will stop trying to get this data.System Action: None.User Response: Verify that the authorized Candle Subsystem is running and that the Coupling Facility Resource Management (CFRM) dataset is accessible from this LPAR. If the problem persists, call Candle Customer Support for further assistance. If it is running and the problem persists, contact Candle Customer Support for further assistance.

KCNCA004E UNABLE TO OBTAIN LARGER XXX_ALLDATA ANSWER AREA,SIZE(XXXXXXXX). COLLECTION NOT AVAILABLEExplanation: This message comes from the Candle Subsystem’s attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). The XXX in "XXX_ALLDATA" may be either STR or CF. The value following "SIZE" is the storage area size, in hexadecimal, that is needed. Subtask collection is terminated. System Action: None.User Response: Recycle the Candle Subsystem associated with this message. If the problem persists, call Candle Customer Support for further assistance.

KCNDR001E UNABLE TO OBTAIN PRIVATE STORAGE, COUPLING, FACILITY COLLECTION NOT AVAILABLEExplanation: This message comes from the client application using the Candle Subsystem for Coupling Facility data collection (KCNCFDR). The driver routine that connects to the Candle Subsystem cannot obtain working storage. The client will not be able to report on Coupling Facility information. System Action: None.User Response: Recycle the client application associated with this message. If the problem persists, call Candle Customer Support for further assistance.

KCNDR002W KXCQUERY HAS RESUMED USING THE CANDLE SUBSYSTEMExplanation: This message comes from the client application using the Candle Subsystem for Coupling Facility data collection (KCNCFDR). This application had lost contact with that subsystem but has now regained contact. Processing is continuing normally. System Action: None.User Response: None. If this message appears frequently, call Candle Customer Support for further assistance.


KCNDR003W KXCQUERY HAS LOST USE OF THE CANDLE SUBSYSTEM,RESORTING TO LOCAL COLLECTIONExplanation: This message comes from the client application using the Candle Subsystem for Coupling Facility data collection (KCNCFDR). This application has lost contact with the Candle Subsystem. It has begun collection the data itself. System Action: None.User Response: Recycle the Candle Subsystem associated with this application. If message KCNDR002W is not received after several minutes have elapsed, call Candle Customer Support for further assistance.

KCNCI001E UNABLE TO OBTAIN PRIVATE STORAGE, COUPLING FACILITYCOLLECTION NOT AVAILABLE.Explanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). Work area storage for this module could not be obtained. The module is terminating and will not be available to support Coupling Facility collection. System Action: None.User Response: Recycle the Candle Subsystem associated with this message. If the message is seen again, call Candle Customer Support for further assistance.

KCNCI002W COUPLING FACILITY DATA COLLECTION SUBTASKTERMINATED UNEXPECTEDLY, RESTARTINGExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). The collection subtask terminated unexpectedly. The main task is attempting to restart it. System Action: None.User Response: None. If this message appears frequently, call Candle Customer Support for further assistance.

KCNCI003E COUPLING FACILITY DATA COLLECTION SUBTASK STARTFAILED, RELINQUISHING COLLECTOR STATUSExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). The collection subtask attach failed. This address space will stop trying to collect Coupling Facility data. It will participate as a receiver when another Candle Subsystem takes over the collection function. System Action: None.User Response: None. If this message appears frequently, call Candle Customer Support for further assistance.

KCNCI004E ERROR: KCNDLCF FUNCTION PARMS NOT FOUNDExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). This is a severe internal error for this function and it cannot continue. System Action: None.User Response: Recycle the Candle Subsystem associated with this message. If this message appears again, call Candle Customer Support for further assistance.


KCNCI005I COUPLING FACILITY COLLECTOR SUBTASK STARTEDExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). It indicates that this Candle Subsystem is collecting Coupling Facility data for the Sysplex. System Action: None.User Response: None. This is an informational message.

KCNCI006W COUPLING FACILITY COLLECTOR STARTING LOCAL COLLECTIONExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). The Candle Subsystem associated with this message has stopped receiving coupling facility data from the Sysplex collector. It has started collecting data itself for the Candle products on this MVS image. System Action: None.User Response: This message may appear occasionally if the XCF message processing facility is heavily burdened, or if the collecting Candle Subsystem has stalled or failed. If neither message KCNCI007W nor message KCNCI008W is seen shortly, try cancelling the last known collecting Candle Subsystem (see message KCNCI005I). If the problem persists, call Candle Customer Support for further assistance.

KCNCI007I COUPLING FACILITY COLLECTOR RESUMING PLEX RECEPTIONExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). This message indicates that the problem, wich caused message KCNCI006W to appear, has been resolved. Another Candle Subsystem has begun sending Coupling Facility data and this address space is receiving that data.System Action: None.User Response: None. This message indicates that a problem state has been resolved. It may also indicate that one of the Candle Subsystems in the Sysplex has failed and some action should be taken for that address space.

KCNCI008I COUPLING FACILITY COLLECTOR RESUMING PLEX COLLECTIONExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). This message indicates that the problem, which caused message KCNCI006W to appear, has been resolved. This Candle Subsystem has begun collecting Coupling Facility data and is sending data to other Candle Subsystems in its XCF group. System Action: None.Message Type: None. This message indicates that a problem state has been resolved. It may also indicate that one of the Candle Subsystems in the Sysplex has failed and some action should be taken for that address space.


KCNCI009E ERROR JOINING XCF GROUP TYPE=XXXXXXXXXXXXXXXX. FUNCTION TERMINATING.Explanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). The Coupling Facility collection function tried to join the XCF group to determine the identity of other group members. A problem occurred while trying to perform this task. The specific condition is given by the text following the “TYPE=” phrase, where XXXXXXXXXXXXXXXX is® “QUERY GROUP RC>4” – the IXCQUERY for group information ended

with a return code greater than 4

® “QUERY GROUP NOT4” – the IXCQUERY for group information ended with a return code 4 but the reason code was not also 4. When both return and reason codes are 4, it is just a matter of resizing the answer area. Otherwise, some serious error has occurred.

® “QUERY GROUP LNG<” – the IXCQUERY for group information ended with indication that we should resize. However, the buffer area we used is already big enough for the complete data. This contradiction cannot be resolved.

® “QUERY GROUP REPT” – Attempts to resize and get group information have failed repeatedly.

® “XCF JOIN FAILED” – The IXCJOIN to join the XCF group failed. Check the group name for valid characters.

System Action: None.User Response: Recycle the Candle Subsystem associated with this message. If this message appears again, call Candle Customer Support for further assistance.

KCNCI010i COUPLING FACILITY COLLECTION PARMS IN EFFECT ARE: XCF GROUP NAME=XXXXXXXX ADDRESS=XXXXXXXXREFRESH INTERV=XXXXXXXX ADDRESS=XXXXXXXXWTO MESSAGES=XXXXX ADDRESS=XXXXXXXXPLEX COLLECT=XXX ADDRESS=XXXXXXXXExplanation: This message comes from the main module supporting Coupling Facility data collection in the Candle Subsystem (KCNCFIN). This message documents the collection parameters in effect for this address space, as follows:® XCF Group Name - specifies the XCF group name we are using to pass

Coupling Facility data from the collecting Candle Subsystem to the receiving Candle Subsystems. The name must be common to all participating Candle Subsystems in the Sysplex. The name should be unique from any other XCF group names used in this Sysplex.

® REFRESH INTERV – shows the refresh interval in effect. The value is in seconds. This interval tells you how frequently we are refreshing Coupling Facility data in this address space. All Candle Subsystems that are part of the same XCF group should have the same refresh interval.


® WTO MESSAGES – indicates the level of message logging used. There are 3 levels:

– NO - no messages at all

– ERROR - error, warning and informational messages that give key status indications for the service. ERROR is the default.

– ALL - full debugging level messages. This should be used only with Candle Customer Support involvement. The message volume can be extensive.

® PLEX COLLECT – specifies whether or not this address space may become the collector for this Sysplex. There are 2 values:

– YES indicates that this Candle Subsystem may become the Coupling Facility data collector for this Sysplex. Only one Candle Subsystem at a time is the collector. Candle Subsystems with this value may take over data collection should the current collector fail or be terminated. YES is the default.

– NO indicates that this Candle Subsystem may not become the collector for this Sysplex. This Candle Subsystem may initiate local collection if the Sysplex collector cannot be located.

® ADDRESS – Appended to each parameter, it is the storage location of this parameter within this address space. This value may be helpful for problem resolution efforts.

System Action: None.User Response: This information documents the settings in use. It may be helpful to compare these to the other Candle Subsystems expected to be in the same XCF group for consistency.

KCNPR001W COUPLING FACILITY PARMS MAY NOT BE HONORED. RKANPAR FILE BLOCKSIZE IS LESS THAN THE EXPECTED 8880SIZE. DEFAULTS MAY BE USED.Explanation: This message comes from initialization functions in the Candle Subsystem (KCNPRSR). parameters placed by CICAT in the &hilev.RKANPAR data set help control Coupling Facility collection in the Candle Subsystem. The parsing code that reads these parameters is expecting the file block size to be CICAT's default size of 8880 bytes. This message indicates that the actual file blocksize is smaller than expected and that control parameters may not be properly found as a result. Default values will be used for parameters that are not located.System Action: None.User Response: Default values for parameters should be reasonable for most users. If the default parameters do not suit local needs, call Candle Customer Support for further assistance. Resizing the RKANPAR file to its standard 8880 size should relieve this problem.


KCNPR002I PARMS NOT FOUND. DEFAULTS USED FOR:Explanation: This message comes from initialization functions in the Candle Subsystem (KCNPRSR). There are parameters placed by CICAT in the &hilev.RKANPAR data set to help control Coupling Facility collection in the Candle Subsystem. The parsing code that reads these parameters is expecting values for 4 keywords “XCF=”, “REFRESH=”, “PLEXCOLLECT=”, and “KCN_WTO=”. This message documents those values that are not found. Built in defaults will be used for their value.System Action: None.User Response: None required. If an overriding parameter was specified but not detected, verify that it was spelled correctly, that there are no blanks after the “=” sign, and that the entire KCNSTR00 member is less than 8880 bytes long.

KCP0001 DSI IS UNABLE TO REGISTER PHYSICAL NODE AT HUBExplanation: The physical node name used to distribute queries to remote data servers could not be registered at the hub CMS.System Action: The data server on which the error occurred will not participate in any CICS distributed queries.User Response: Check the TLVLOG for additional messages that may indicate the reason why node registration failed. If problems persist, contact Candle Customer Support.

KCP0002 function table PLN I/O ERROR ON PDS: TYPE=type, RC=rcExplanation: The function indicated by function was unable to 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.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0003 function table PDS AGENT DID NOT SUPPLY COLUMN: colExplanation: The function indicated by function was unable to locate the column identified by type in the CMS catalog.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0004 subtask CANNOT COMMUNICATE WITH XMIExplanation: The system was unable to locate the address of the XMI communication control block using CT/Engine services.System Action: The subtask identified by subtask terminates.User Response: Confirm that XMI successfully started as a subtask of the Candle Management Server address space. Ensure that there is a START command in the Candle Management Server CONFIG file that automatically starts XMI. If problems persist, contact Candle Customer Support.


KCP0005 subtask PROBE module PTF ptfno @ address ASSEMBLY time dateExplanation: This informational message is written to the TLVLOG when a probe is first invoked. It lists the probe name, most recently applied PTF, the load point and time and date of assembly.System Action: None.User Response: None, the message is informational.

KCP0006 probe MEMORY REQUEST FAILURE FOR ACCESS LISTExplanation: The specified probe was unable to allocate storage for the distribution list associated with a situation.System Action: Data will be collected for every CICS region.User Response: Consider increasing either the Candle Management Server region size or the GMMPERCENT value in the Candle Management Server startup configuration file.

KCP0007 XAM PROCESSING FOR THE SPECIFIED CONNECTIONS PARAMETER IS BYPASSED ID=tableExplanation: The connections parameter specified on the start command for the exception analysis manager (XAM) subtask is invalid.System Action: The exception analysis manager processes all connections in the monitored CICS regions.User Response: Specify a valid connections parameter. The valid format is CONNECTIONS=parameter where parameter is 1 to 4 characters, including an asterisk. Examples include:® CONNECTIONS=C*

® CONNECTIONS=C*6

KCP0008 probe ONDV REQUEST TIMED OUT FOR CICS regionExplanation: The probe did not receive a record buffer from the ONDV subtask of the Common Interface address space prior to the expiration of a one minute time interval for the named region.System Action: The probe bypasses ONDV processing for the named CICS region.User Response: Ensure that the ONDV subtask is active in the Common Interface used to monitor the identified CICS region. Also, check that the dispatching priority of the OCCI job is high enough to permit its responding to cross-memory requests in a timely fashion.

KCP0009 function CANNOT ACCESS OC CVTExplanation: The system was unable to locate the address of the CCC for CICS or OMEGAMON XE for CICSplex CVT control block in the CT/Engine GSA.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.


KCP0010 probe $ONDVREQ MACRO FAILURE FOR CICS region: RC=rcExplanation: The probe was unable to communicate with the ONDV subtask of the Common Interface. The return code denoted by rc indicates the cause of the error.System Action: The probe bypasses ONDV processing for the named CICS region.User Response: Ensure that the ONDV subtask is active in the Common Interface used to monitor the identified CICS region. If problems persist, contact Candle Customer Support.

KCP0011 probe UNABLE TO OBTAIN STORAGE IN OCCI LENGTH=lengthExplanation: The probe was unable to acquire storage in the Common Interface address space for ONDV record collection.System Action: The probe bypasses ONDV processing for the named CICS region.User Response: Consider increasing the OCCI region size. If problems persist, contact Candle Customer Support.

KCP0012 probe UNIT-OF-WORK DESCRIPTOR NOT SUPPLIED VIA PARMAExplanation: The probe was unable to locate the unit-of-work used to search for related transactions.System Action: The probe terminates.User Response: The SQL generated internally to drive the unit-of-work probe is in error. Contact Candle Customer Support.

KCP0014 probe ONDV NOT RUNNING FOR CICS region:Explanation: The probe was unable to locate the ONDV subtask in the Common Interface for the specified CICS region.System Action: The CICS region is ignored.User Response: Ensure that the ONDV subtask is active in the Common Interface used to monitor the CICS region.

KCP0016 CICS aaaaaaaa: bbbExplanation: The agent was unable to extract shared Temporary Storage queue information from the service task operating within the CICS address space denoted by aaaaaaaa.System Action: Temporary Storage queue data is not collected for the CICS region.User Response: Based on the text of the message denoted by bbb, attempt to correct the cause of the service task error. If problems persist, contact Candle Customer Support.

KCP0017 UNABLE TO ALLOCATE XCB CONTROL BLOCKExplanation: The cross-memory interface (XMI) subtask was unable to allocate one of its primary communications control blocks from subpool 251 storage.System Action: The cross-memory interface task terminates.User Response: Consider increasing the region size of the CT/Engine address space in which XMI is started.


KCP0018 ERROR WHILE COLLECTING RLS DATA: aaaExplanation: The agent was unable to extract Record Level Sharing (RLS) information due to the error denoted by aaa.System Action: RLS data is not collected for the MVS image.User Response: Based on the text of the message, attempt to correct the cause of the error. If problems persist, contact Candle Customer Support.

KCP0019 SYSTEM FAILURE DURING ATTACH OF subtask RC=rcExplanation: The ATTACH macro used to create the subtask identified by subtask failed. The return code denoted by rc represents the contents of register fifteen passed back by the ATTACH macro.System Action: The component being started terminates.User Response: Consult the IBM Macro Reference for a description of each return code generated by the ATTACH macro and take the necessary corrective action. If problems persist, contact Candle Customer Support.

KCP0020 probe PERSISTENT DATASTORE NOT INITIALIZEDExplanation: The function indicated by probe was unable to perform an I/O request to the Persistent Data Store (PDS).System Action: The function identified by probe terminates.User Response: Verify that the PDS has been properly configured. If historical records are not desired, consider stopping the automatic situations that attempt to write records to the PDS. If problems persist, contact Candle Customer Support.

KCP0021 XAM UNABLE TO ACQUIRE TABLE STORAGEExplanation: The VSAM=NO operand was included on the OC START, ID=XAM command.System Action: The Exception Analysis Manager (XAM) will not collect VSM file information used to compute split, extension, and RLS timeout rates. Therefore, colums that contain "Last Hour" data in the VSAM Analysis table will always be zero.User Response: None.

KCP0022 XAM EXCEPTION ANALYSIS MANAGER IS TERMINATINGExplanation: The Exception Analysis Manager (XAM) received a request to terminate.System Action: None.User Response: None.

KCP0023 XAM EXCEPTION ANALYSIS MANAGER IS ACTIVEExplanation: The Exception Analysis Manager (XAM) completed initialization.System Action: None.User Response: None.

KCP0024 XAM CONNECTIONS FILTER SETTING = aaaaExplanation: The generic connections filter used to limit the TCT scan has been accepted.System Action: None.User Response: None.


KCP0025 PROBE WHERE CLAUSE PREEMTS USE OF PARMA FOR CICS NAMESExplanation: The probe detected CICS names being passed using both PARMA (keyword CICSNAME) and WHERE clause filters.System Action: The PARMA values for CICS names are ignored.User Response: Remove the PARMA filter for CICS job names.

KCP0026 aaa PARAMETER LIST HAS AN INVALID FORMATExplanation: The agent denoted by aaa detected either a missing or incorrect set of parameters.System Action: The query is ignored.User Response: Contact Candle Customer Support.

KCP0027 XAM UNABLE TO ACQUIRE TABLE STORAGE: LENGTH=length, ID=tableExplanation: The exception analysis manager (XAM) subtask was unable to allocate length bytes of private storage for table identified by table.System Action: If the error occurs during initialization, the exception analysis subtask will terminate. Otherwise, XAM will continue processing with a decreased ability to compute rates per hour for the storage violation and VSAM control block exceptions.User Response: Consider increasing either the Candle Management Server region size or the GMMPERCENT value in the Candle Management Server startup configuration file.

KCP0028 XAM PROGRAM CHECK RECOVERY FOR CICS: regionExplanation: The exception analysis manager (XAM) subtask encountered a program check in one of its cross-memory mode collection routines while attempting to monitor the CICS denoted by region.System Action: XAM continues processing. No dump is produced.User Response: This may be the result of corrupted storage in the CICS address space. If problems persist, contact Candle Customer Support.

KCP0070 INVALID GROUP SPECIFICATION FOR CICS aaaaaaaaExplanation: The agent expects a group identifier for CICS aaaaaaaa, but found an invalid value. The value must be in the range 1-MAX_GROUPS (MAX_GROUPS is the value specified in the Global definition file of the OMEGAMON II for CICS product).System Action: The query is ignored.User Response: Specify a valid group number in the query predicate and retry the request.

KCP0100 probe GET PARM ERROR: PARMNAME=parmname, STATUS=statusExplanation: The probe was unable to obtain the address of the parameter identified by parmname. Status code status indicates the cause of the error.System Action: No data is collected.User Response: Contact Candle Customer Support.


KCP0101 probe GET VIEW STORAGE ERROR: LENGTH=length, STATUS=statusExplanation: The specified probe was unable to allocate the specified length of bytes of storage. Status code status indicates the cause of the error.System Action: No data is collected.User Response: Consider increasing either the Candle Management Server region size or the GMMPERCENT value in the Candle Management Server startup configuration file.

KCP0102 probe PUT PARM ERROR: PARMNAME=parmname, STATUS=statusExplanation: The specified probe was unable to identify the address of the parameter identified by parmname. Status code status indicates the cause of the error.System Action: No data is collected.User Response: Contact Candle Customer Support.

KCP0103 probe UNABLE TO MONITOR CICS region: RC=rcExplanation:CCC for CICS or OMEGAMON XE for CICSplex is unable to monitor CICS region. Return code rc indicates the type of error:

System Action: No data is collected.User Response: For return code x’04’, make sure that XMI (cross memory interface task) is an active subtask of the Candle Management Server address space. If problems persist, contact Candle Customer Support.

00 CICS region will be monitored by CCC for CICS or OMEGAMON XE for CICSplex.

04 XMI did not register the XCB address.

08 CICS region could not be found.

0C Specified region does not belong to CICS.

10 CICS release is not supported by CC for CICS or OMEGAMON XE for CICSplex.

14 CICS job is swapped out.

18 ESTAEX macro failed.

1C Cross memory error occurred during CICS validation.

20 CICS initialization is not complete.

24 XMIT DD card suffix used in CICS does not match that of Candle Management Server.

28 Unable to obtain storage required to build TDA.

2C Session Accounting Area build error occurred.

30 Module load error occurred (see console for message OC0760).

34 OCCI Session Accounting Area not found.


KCP0104 EXCEPTION ANALYSIS SUBTASK IS NOT ACTIVEExplanation: The CCC for CICS or OMEGAMON XE for CICSplex exception analysis subtask is not running in the Candle Management Server address space.System Action: No data is collected.User Response: Confirm that XMI successfully started as a subtask of the Candle Management Server address space. Ensure that there is a START command in the Candle Management Server CONFIG file that automatically starts XAM. If problems persist, contact Candle Customer Support.

KCP0105 probe CROSS MEMORY ERROR, CICS SWAPPED OUT: regionExplanation: The system attempted cross memory operations to a CICS region that was swapped out.System Action: No data is collected.User Response: None.

KCP0106 probe CROSS MEMORY ABEND COLLECTING column FOR CICS regionExplanation: The probe experienced an abend while attempting to collect data for a specific CICS region.System Action: The probe continues to attempt data collection for remaining columns.User Response: None.

KCP0107 probe CON GETMAIN FOR WORK AREA FAILED, RC=rcExplanation: The probe experienced an abend while attempting to GETMAIN storage for the work area used to build data about the CICS regions in this MVS image.System Action: The probe will not continue processing.User Response: Contact Candle Customer Support. Ensure that the TLVLOG is available and that you have the Reason Code issued in the message.

KCP0108 probe PRODUCE VALUE ERROR: STATUS=statusExplanation: The probe was unable to obtain extract column values. Status code status indicates the cause of the error.System Action: No data is collected.User Response: Contact Candle Customer Support.

KCP0109 COPY TMA/$OCMNTA ERROR; POSSIBLE DATA LOSSExplanation: The work area allocated by the agent that extracts transaction data is not large enough to accommodate the information gathered by the task cross-memory collector.System Action: Data in transaction reports may be incomplete.User Response: Contact Candle Customer Support.


KCP0111 WSR FLOATING POINT cccccccc, ERROR OCCURRED RESULT SET ZERO RA=xxxxxxxxExplanation: A floating point calculation generated a value too large to represent. cccccccc represents the calculation type (ADD|SUBTRACT|MULTIPLY|DIVIDE) and xxxxxxxx is a hexadecimal address.System Action: No data is collected.User Response: Contact Candle Customer Support.

KCP0112 WSR FP cccccccc, IN1=xxxxxxxxxxxxxxxx, IN2=xxxxxxxxxxxxxxxx, OUT=xxxxxxxxxxxxxxxx, RA=xxxxxxxxExplanation: A floating point calculation generated a value too large to represent. cccccccc represents the calculation type (ADD|SUBTRACT|MULTIPLY|DIVIDE) and xxxxxxxx is a hexadecimal value or address.System Action: No data is collected.User Response: Contact Candle Customer Support.

KCP0113 WSR FLOATING POINT cccccccccccccccc, DETECTED RA=xxxxxxxxExplanation: This is the diagnostic message previous to Abend U113, indicating the type of function that failed. cccccccccccccccc represents the error type and xxxxxxxx is a hexadecimal address.System Action: WSR collector will ABEND U113.User Response: Contact Candle Customer Support.

KCP0190 LU GROUP INVALID FOR THIS FUNCTION FOR CICS aaaaaaaaExplanation: The requested function does not support VTAM Logical Unit (LU) groups for CICS aaaaaaaa.System Action: The query is ignored.User Response: Specify one of the other group types and retry the request.

KCP0201 BOTTLENECK ANALYSIS COLLECTOR NOT ACTIVE FOR CICS aaaaaaaaExplanation: The Bottleneck Analysis collector is not active in the OMEGAMON for CICS Common Interface (OCCI) address space used to monitor CICS aaaaaaaa.System Action: The query is ignored.User Response: Start the collector and retry the request.

KCP0202 BOTTLENECK ANALYSIS COLLECTOR IS BUSY FOR CICS aaaaaaaaExplanation: The Bottleneck Analysis collector, running in the OMEGAMON for CICS Common Interface (OCCI) address space, is currently analyzing the environment of CICS aaaaaaaa. The agent cannot access the collection data until the collector finishes.System Action: The query is ignored.User Response: Retry the request.


KCP0203 COLLECTOR SUSPENDED, VALUES SHOWN NOT CURRENT FOR CICS aaaaaaaaExplanation: The Bottleneck Analysis collector, running in the OMEGAMON for CICS Common Interface (OCCI) address space, is suspended and is not sampling data for CICS aaaaaaaa. Only the values accumulated up to the time of suspend are returned by the query.System Action: The query continues execution.User Response: Resume the Bottleneck Analysis collector and retry the request.

KCP0207 COLLECTOR DETACHED DUE TO TOO MANY PROGRAM CHECKS FOR CICS aaaaaaaaExplanation: The Bottleneck Analysis collector, running in the OMEGAMON for CICS Common Interface (OCCI) address space, was detached for CICS aaaaaaaa due to an excessive number of program checks.System Action: The query is ignored.User Response: Contact Candle Customer Support.

KCP0210 DSPSERV MACRO FAILURE: CODE=error, REASON=reasonExplanation: The system was unable to create the data space used to hold CICS transaction data. The error code is represented by error, and reason denotes the reason code that is associated with the problem.System Action: The workload manager subtask terminates.User Response: Error and reason codes for the DSPSERV macro are described in the IBM System Programming Library: Application Development Macro Reference manual. Correct the cause of the problem and restart the subtask.

KCP0211 ALESERV MACRO FAILURE: CODE=rcExplanation: The system was unable to add an entry in the access list for the data space that harbors CICS transaction data. rc is the return code provided by the ALESERV macro.System Action: The workload manager subtask terminates.User Response: Return codes for the ALESERV ADD function are described in the IBM System Programming Library: Application Development Macro Reference manual. Correct the cause of the problem and restart the subtask.

KCP0212 WORKLOAD ANALYSIS TASK IS TERMINATINGExplanation: The workload subtask used to summarize CICS data by service class is stopping because of an operator request, or some kind of abnormal termination.System Action: None.User Response: If the shutdown is unexpected, check the console log for other messages that might indicate why the workload subtask is stopping. If problems persist, contact Candle Customer Support.


KCP0213 WCR PASSED INVALID LENGTH TO XMCOMExplanation: The workload subtask improperly formatted the parameter list it uses to extract CICS transaction data.System Action: The workload manager subtask abnormally terminates.User Response: Contact Candle Customer Support.

KCP0214 WORKLOAD ANALYSIS IS NOT RECEIVING DATA FROM regionExplanation: The CCC for CICS or OMEGAMON XE for CICSplex data collection exits are not running in the CICS region identified by region.System Action: Service level data for CICS region will not be gathered.User Response: Ensure that an ’OMEG INIT’ transaction has been run in CICS region. If problems persist, contact Candle Customer Support.

KCP0215 UNABLE TO OBTAIN RECORD CELL, DATA LOSTExplanation: The data space used to hold CICS transaction records is full.System Action: Until the workload summarization subtask processes the records in the data space, service level data for some transactions will be lost.User Response: Ensure that the Candle Management Server is getting sufficient cycles to process all of the CICS transaction data. Consider increasing the size of the data space by coding the BLOCKS= parameter on the WLM START command (OC START ID=WLM, BLOCKS=nnnnnn) found in RKANCMD(KDSSTART). If the BLOCKS keyword is not coded, the workload subtasks will use the installation default when creating the data space. Setting a higher value will give the WLM subtasks additional time to process transaction information. If problems persist, contact Candle Customer Support.

KCP0216 SUMMARY SUBTASK ABEND, CODE=ccExplanation: The workload summarization routine abnormally terminated with completion code cc.System Action: The workload analysis subtask terminates.User Response: Contact Candle Customer Support.

KCP0217 WCR BLOCKS VALUE EXCEEDS RANGE (10-524288)Explanation: The BLOCKS value coded on the OC START ID=WLM command is not within the permissible range for the DSPSERV macro.System Action: The workload analysis subtask terminates.User Response: Re-enter the command, specifying a valid value.

KCP0218 WCR UNABLE TO CREATE ADEQUATE DATA SPACE, BLOCKS=ccExplanation: A minimum of ten blocks must be available in the data space created by the WLM subtask. The actual number of blocks allocated by the DSPSERV macro is displayed as cc.System Action: The workload analysis subtask terminates.User Response: Modify the IEFUSI exit to permit a data space size of at least ten blocks.


KCP0220 SERVICE LEVEL ANALYSIS SUBTASK IS NOT ACTIVEExplanation: The service level analysis subtask is not running in the Candle Management Server.System Action: Service level data cannot be written to the persistent data store.User Response: Ensure that the WLM subtask was started under the Candle Management Server. If problems persist, contact Candle Customer Support.

KCP0221 function UNABLE TO LOCATE SQL FUNCTION PACKAGEExplanation: The system is unable to locate the C language function set used to issue SQL statements in the CT/Engine address space.System Action: The function terminates.User Response: Contact Candle Customer Support.

KCP0222 function table CREATE PATH FAILURE, RC=rcExplanation: The function indicated by function was unable to perform an SQL CreatePath for table table. rc is the return code generated by the SQL request.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0223 probe INPUT SQLDA ERROR, COLUMNS=columnsExplanation: The number of columns expected by probe probe does not match the column count returned in the SQLDA. columns shows the number of columns contained in the SQLDA input buffer.System Action: The probe identified by probe terminates.User Response: Contact Candle Customer Support.

KCP0224 function table OPEN REQUEST FAILURE, RC=rcExplanation: Function function was unable to perform an SQL OpenRequest for table table. rc is the return code generated by the SQL request.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0225 function table DROP PATH FAILURE, RC=rc Explanation: Function function was unable to perform an SQL DropPath for table table. rc is the return code generated by the SQL request.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0226 function table SERVICE LEVEL ANALYSIS SUBTASK HAS TERMINATEDExplanation: Function function encountered an error when attempting to retrieve data from the data space. The data space is no longer available because the service level analysis subtask has terminated.System Action: The function identified by function terminates.User Response: Identify the reason for the termination of the service level analysis subtask. If the termination was abnormal, collect the CMS message log and SYSUDUMP output and contact Candle Customer Support.


KCP0227 function table UPDATE FAILURE, RC=rcExplanation: Function function was unable to perform an SQL Update for table table. rc is the return code generated by the SQL request.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0228 function table INSERT FAILURE, RC=rcExplanation: Function function was unable to perform an SQL Insert for table table. rc is the return code generated by the SQL request.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0229 function table Unable to locate AR vector. Transaction ID translation disabledExplanation: Function function was unable to locate the AR vector where the transaction ID translation module pointer is. The AR vector is stored in the Target Descriptor Area for each monitored CICS region. Processing will continue without translating to the internal format the codes that represent PF, PA and special keys.System Action: Processing continues. Please note data that special transaction IDs (#F01 through #F36, #PA1 through #PA3, #LPA, #MAG, #OCD) will not be collected by the workload analysis tasks.User Response: Insure a CICS region is available when CMS starts up.

KCP0241 WSR - WLM COLLECTION WILL USE HH:MM: HRS. AS THE COLLECTION INTERVALExplanation: The workloads summarizer subtask (WSR) displays this message at initialization time, or when the workload analysis interval is changed at the workstation. It is an information message only.System Action: Processing continues.User Response: None.

KCP0242 IWMPQRY MACRO FAILURE, REASON CODE=reason.Explanation: The workload summarizer subtask (WSR) received reason code reason while attempting to obtain the current IBM service policy definition. This message applies to MVS release 5.1 and above.System Action: WSR terminates.User Response: Contact Candle Customer Support.

KCP0243 WSR WAITING FOR WORKLOAD DEFINITIONSExplanation: The system displays this message at 5 minute intervals until function WSP initializes the user defined interval, services classes and service policy, in storage. Function WSP is triggered by KCPDSI00, the Candle Management Server initialization function of CCC for CICS or OMEGAMON XE for CICSplex.System Action: Processing continues.


User Response: If the message is displayed repeatedly after Candle Management Server start up:1. Verify that member KDSCNFG in the TLVPARM dataset contains the start

command for KCPDSI00:START KCPDSI00

2. Verify that message CP0259 DSI $WLMSP INITIALIZATION COMPLETE was displayed on the TLVLOG.

3. If message KCP0259 is not found in TLVLOG, search TLVLOG for WSP error messages:KCP0221 KCP0222KCP0224 KCP0225KCP0251 KCP0252KCP0253 KCP0254KCP0255 KCP0256KCP0257 KCP0258

4. Perform the corrective action indicated for these messages.

KCP0244 WSR - UNABLE TO OBTAIN ACCUMULATION BUFFER, DATA LOSTExplanation: The workload summarizer subtask (WSR) is unable to obtain storage for an accumulation buffer. This condition may occur in busy systems with many CICS address spaces. The situation subsides when the subtask catches up with the transaction volume arriving from the CICS address spaces. The data for the transaction currently being processed does not accumulate.System Action: Processing continues.User Response: None.

KCP0245 WSR LSEXPAND MACRO FAILURE, RC=rcExplanation: The workload summarizer subtask (WSR) was not able to expand the linkage stack.System Action: WSR ends.User Response: Contact Candle Customer Support.

KCP0246 WSR REQUESTED TERMINATION IN PROGRESSExplanation: The workload summarizer subtask (WSR) has been posted to terminate.System Action: WSR ends.User Response: None.

KCP0247 WSR - WLM COLLECTION WILL USE cccccccc SERVICE POLICY service_policy, RULE: ruleExplanation: The workload summarizer subtask (WSR) issues this message at initialization, or when a new service policy becomes effective.

cccccccc represents one of the following service policies:®CANDLE’S when the service policy is activated at the workstation from the

CICS Workload Definitions icon under the Administration folder.

®IBM’S when the service policy was defined using the IBM WLM ISPF application.


service_policy is the service policy name.

rule shows one of the following values:®CANDLE Service policies, workloads and service classes defined using the

CICS Workload Definitions icon under the Administration folder of the workstation will be used exclusively by the workloads subtask under the Candle Management Server.

®IBM Service policies, workloads and service classes defined under the IBM WLM ISPF application will be used exclusively by the Candle Management Server.

® BOTH The workloads subtask will use

®IBM’s definitions for CICS 4.1 and above running MVS 5.1 and above

®Candle’s definitions for CICS releases below 4.1 running under any MVS release

®Candle’s definitions for CICS release 4.1 and above running under MVS releases below 5.1

System Action: Processing continues.User Response: None.

KCP0248 WSR ENFREQ ACTION=LISTEN MACRO FAILURE, RC=rcExplanation: Installation of the user exit that listens for changes in IBM’s service policy failed with return code rc.System Action: The summarizer subtask terminates if the choice of rules is IBM. If the choice of rules is BOTH or CANDLE, the summarizer subtask continues processing.User Response: Contact Candle Customer Support.

KCP0249 WSR ENFREQ ACTION=DELETE MACRO FAILURE, RC=rcExplanation: During termination processing, an attempt to delete the user exit that listens for IBM’s service policy changes failed with return code rc.System Action: Termination processing continues.User Response: Contact Candle Customer Support.

KCP0250 ENF SUCCESSFUL RECOVERY AFTER ABEND WAS DETECTED. ABEND CODE: abendExplanation: The ENF user exit recovered after an abend. This may be the result of the WLM subtask in the Candle Management Server not being active.System Action: The ENF user exit remains active.User Response: Contact Candle Customer Support.


KCP0251 WSP table FETCH REQUEST FAILURE, RC=rcExplanation: Function WSP was unable to perform an SQL Fetch for the table identified by table. rc is the return code generated by the SQL request. The table identified by table can be either the INTERVAL or SVPOL table. This problem can occur if there is no interval specified for the workload analysis collector, or if there is no service policy specified as active when the Candle workload definitions are being used.System Action: The function terminates.User Response: If the table is INTERVAL, use the workstation to verify that an interval is shown in the Interval and Rule Choice panel of the CICS Workload Definitions icon. If the table is SVPOL, select Service Policies in the Interval and Rule Choice panel of the CICS Workload Definitions icon, and activate a service policy. If the problem persists, contact Candle Customer Support.

KCP0252 function table FETCH RESULTED IN NULL DATAExplanation: An attempt by function function to perform an SQL Fetch for table table unexpectedly resulted in null data being returned.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0253 function table CLOSE FAILURE, RC=rcExplanation: The function identified by function was unable to perform an SQL CloseRequest for table table. rc is the return code generated by the SQL request.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0254 function UNABLE TO ACQUIRE STORAGE FOR storageExplanation: Function function was unable to acquire storage for the storage control block.System Action: The function identified by function terminates.User Response: Increase the size of the CCC for CICS or OMEGAMON XE for CICSplex region. If the problem persists, contact Candle Customer Support.

KCP0255 function UNABLE TO ACQUIRE SCLASS WORK STORAGE, RC=rcExplanation: Function function was unable to acquire work storage for the service class work area. rc is the return code generated by the storage request.System Action: The function identified by function terminates.User Response: Increase the size of the CCC for CICS or OMEGAMON XE for CICSplex region. If the problem persists, contact Candle Customer Support.

KCP0256 function UNABLE TO PROCESS TOKEN token FOR SERVICE CLASS sclassExplanation: The total length of the values specified to classify a service class exceeds allocated storage for the service class.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.


KCP0257 function UNABLE TO ALLOCATE STORAGE FOR SERVICE CLASS sclassExplanation: Function function was unable to acquire storage for an internal control block.System Action: The function identified by function terminates.User Response: Increase the size of the CCC for CICS or OMEGAMON XE for CICSplex region. If the problem persists, contact Candle Customer Support.

KCP0258 function FAILURE PROCESSING sclassExplanation: Function function encountered an error while processing the classification rules for sclass. A previous message described the error.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0259 function $WLMSP INITIALIZATION COMPLETEExplanation: The function completed initialization of the interval and service policy areas.System Action: Processing continues.User Response: None.

KCP0260 WSP MISSING GOAL ROW FOR SERVICE CLASS sclassExplanation: Function WSP did not find a GOAL table row for service class sclass.System Action: Processing continues. Note that data collected for service class sclass will not reflect the correct response time goal.User Response: Enter the goal for service class sclass.

KCP0261 WSP CRITICAL ERROR: TABLE SCLASS RETURNED NO ROWS, $WLMSP PROCESSING ABANDONEDExplanation: Function WSP found no rows in the SLCASS table, which should contain the classification rules for service classes. This message may appear:® at data server initialization time

® when a service policy is activated or reactivated at the workstation

® when the rules choice is changed at the workstation

System Action: WSP processing stops. If the message appears at initialization, workloads data collection will not start. If the message appears due to a service policy activation/reactivation, or a change in the choice of rules at the workstation, workloads data collection continues with the old definitions.User Response: If the message appears at initialization, issue the following commands at the MVS console:

F jobname,CTDS START KCPDSI00,STOPF jobname,CTDS RUN KCPDSI00

Monitor the TLVLOG for the following messages, which indicate normal completion of the initialization process:

KCP9002: DATA SERVER INTERFACE IS ACTIVEKCP0259: DSI $WLMSP INITIALIZATION COMPLETE

If the message appears because of a service policy activation/reactivation, or because of a change in the choice of rules, retry the action at the workstation.


KCP0262 MOSPR ZERO SERVICE POLICY ADDRESS DETECTEDExplanation: Function MOS found that the current service policy address was zero.System Action: The function terminates.User Response: Contact Candle Customer Support.

KCP0268 WSR - LOAD FOR MODULE module FAILED, rc=rcExplanation: The workloads summarizer subtask received return code rc when attempting to load module module.System Action: The summarizer subtask terminates if the choice of rules for workload analysis is IBM. It continues processing if the choice of rules is CANDLE. Ensure that module is in the STEPLIB for the Candle Management Server, correct the problem and retry the command

/F stask,OC START ID=WLM

where stask is the name of the started task for the Candle Management Server.

KCP0269 WSR - STORAGE OBTAIN FOR USER EXIT PARAMETER LIST FAILURE, RC=rcExplanation: The workloads summarizer subtask received return code rc when attempting to obtain common storage for the parameter list of the ENF listener user exit.System Action: The summarizer subtask terminates if the choice of rules for workload analysis is IBM. It continues processing if the choice of rules is CANDLE.User Response: Investigate the reason for common storage to be depleted, correct the problem and retry starting WLM.

KCP0270 TRT RETURN CODE rc FROM TARGET DESCRIPTOR AREA BUILDExplanation: The system received a non-zero return code during TDA build processing. The return code (rc) describes the reason:04 XMI did not register the XCB address.08 The system could not locate the specified CICS region.System Action:The system does not collect routing information.User Response: For return code x’04’, make sure that XMI (cross memory interface task) is an active subtask of the Candle Management Server address space. Ensure that there are active CICS regions on this system. If problems persist, contact Candle Customer Support.

KCP0271 probe HAS LOCATED MORE THAN nn CICS REGIONS IN THIS MVS IMAGEExplanation: Probe probe has located more than nn active CICS regions in this MVS image.System Action: The system only collects routing information for the first nn active CICS regions.User Response: If problems persist, contact Candle Customer Support.


KCP0280 IBM SERVICE CLASS COLLECTOR IS ACTIVEExplanation: The IBM service class collector has completed initialization.System Action: None.User Response: None.

KCP0281 IBM SERVICE CLASS COLLECTOR ALREADY ACTIVEExplanation: A second IBM service class collector task was started while one was already active.System Action: The task terminates.User Response: None.

KCP0282 IBM SERVICE CLASS COLLECTOR IS NOT ACTIVEExplanation: The IBM service class collector is not running.System Action: None.User Response: None.

KCP0283 IBM SERVICE CLASS COLLECTOR IS TERMINATINGExplanation: The IBM service class collector has received a request to terminate.System Action: None.User Response: None.

KCP0284 IBM SERVICE CLASS COLLECTOR IS NOT RESPONDINGExplanation: The IBM service class collector failed to terminate within thirty seconds after being notified to stop.System Action: Once the IBM service class collector detects the shutdown request, it will terminate.User Response: None.

KCP0285 function INVALID PARMA VALUE DETECTED valueExplanation: Function function retrieved an invalid parameter value.System Action: The function identified by function terminates.User Response: Contact Candle Customer Support.

KCP0286 function MOSTATUS NOTIFICATION COMPLETEExplanation: Function function has notified the service class processor function of a change in workload definitions.System Action: None.User Response: None.

KCP0287 function PROCESSING XXXXXX SERVICE CLASSESExplanation: Function function is building a list of Candle or IBM service classes; XXXXXX indicates which.System Action: None.User Response: None.


KCP0288 function MOSTATUS PROCESSING COMPLETEExplanation: Function function has successfully finished building a list of Candle’s or IBM’s service classes.System Action: None.User Response: None.

KCP0289 function SERVICE CLASSES EXCEED AVAILABLE STORAGEExplanation: Function function has encountered an internal error while attempting to build a list of IBM service classes.System Action: Function function terminates.User Response: Contact Candle Customer Support.

KCP0290 function UNABLE TO LOAD MODULE KCPISP0zExplanation: Function function attempted to load module KCPISP0z, where z. is the MVS release dependent suffix.System Action: Function function terminates.User Response: Verify that module KCPISP0z is in the TLVLOAD concatenation.

KCP0291 function ABEND RETRY IN PROGRESSExplanation: Function function has abended and is attempting recovery.System Action: Function function continues.User Response: None.

KCP0330 RESPONSE TIME ANALYSIS COLLECTOR NOT ACTIVE FOR CICS aaaaaaaaExplanation: The Response Time Analysis (RTA) collector is not active in the OMEGAMON for CICS Common Interface (OCCI) address space used to monitor CICS aaaaaaaa.System Action: The query is ignored.User Response: Start the collector and retry the request.

KCP0760 LOAD OF module FAILED: CODE=abend, REASON=reasonExplanation: Load module module could not be loaded. abend is the abend code, and reason is the reason code associated with the abend.System Action: The session does not initiate.User Response: Locate the abend code in the IBM System Codes manual, correct the cause of the load failure, and restart the session.

KCP0762 HOLD COUNT DISPLACEMENT VALIDATION FAILEDExplanation: OMEGAMON was unable to verify the location of the hold count field in the OUCB control block.System Action: The cross-memory interface (XMI) task terminates because OMEGAMON components cannot verify a target address space if it is swapped out.User Response: Contact Candle Customer Support.


KCP0764 TAI DETECTED AN INCORRECT WORK AREA LENGTHExplanation: The size of the ECSA work area allocated by TAM differs from that expected by module TAI.System Action: The cross memory interface task (XMI) abnormally terminates with a U0764 ABEND.User Response: Contact Candle Customer Support.

KCP0803 SSCVT CHAIN IS EMPTYExplanation: The SSCVT chain was scanned, and was found to be empty.System Action: The cross-memory interface (XMI) task abnormally terminates with a U0803 completion code.User Response: Contact Candle Customer Support.

KCP0804 INVALID SSCVT FOUND ON CHAINExplanation: While searching through the Subsystem Communication Vector Table chain for the element belonging to OMEGAMON XE, the cross-memory interface (XMI) task encountered an improperly formatted SSCVT.System Action: The cross-memory interface (XMI) task abnormally terminates with a U0804 completion code.User Response: Indicates that main storage was overlaid. If problems persist, contact Candle Customer Support.

KCP0808 XM INTERFACE TASK id ALREADY ACTIVE IN jobExplanation: A second cross-memory interface task was started while another one is still active. The CPXMIT number is identified by id and the job running the interface task is identified by job.System Action: The subtask terminates.User Response: Either use a CPXMITnn DD statement to start another cross-memory interface task, or stop the CMS in which the active task is running.

KCP0809 XM INTERFACE TASK IS ACTIVEExplanation: The cross-memory interface (XMI) task has completed initialization and is waiting for work.System Action: None.User Response: None.

KCP0810 XM INTERFACE TASK IS TERMINATINGExplanation: The cross-memory interface (XMI) task received a request to terminate.System Action: None.User Response: None.

KCP0811 XM INTERFACE TASK HAS ABENDEDExplanation: The cross-memory interface (XMI) task error exit intercepted an abnormal termination.System Action: The cross-memory interface (XMI) task attempts resource cleanup before continuing with termination.User Response: Restart XMI, and contact Candle Customer Support.


KCP0812 XM INTERFACE TASK RESOURCE CLEANUP IS COMPLETEExplanation: The cross-memory interface (XMI) task successfully completed resource cleanup.System Action: None.User Response: None.

KCP0813 subtask ESTAEX MACRO FAILURE. RC=rcExplanation: The subtask denoted by subtask received a non zero return code from the ESTAEX macro. This is usually caused by a lack of LSQA.System Action: The subtask terminates.User Response: The return code (rc) for the ESTAEX macro is described in the IBM Macro Reference manual. If the error was caused by a shortage of available storage, decrease the Candle Management Server region size and restart the subtask. If problems persist, contact Candle Customer Support.

KCP0815 SUBSYSTEM TABLE BUILD FUNCTION WAS UNABLE TO CREATE ITS TABLESExplanation: An internal error occurred during the attempt to create the OMEGAMON XE for CICS SSCVT and related control blocks.System Action: The cross-memory interface (XMI) task terminates.User Response: Ensure that no other attempt is being made to start the cross-memory interface task. Then attempt to start the cross-memory interface task again.

KCP0816 ENTRY TABLE CREATE FAILEDExplanation: An error occurred during the attempt to build a program call entry table.System Action: The cross-memory interface (XMI) task abnormally terminates with a U0816 completion code.User Response: Contact Candle Customer Support.

KCP0817 LINKAGE INDEX RESERVE FAILEDExplanation: An attempt to reserve a linkage index failed.System Action: The cross-memory interface (XMI) task abnormally terminates with a U0817 completion code.User Response: Contact Candle Customer Support.

KCP0818 program IS NOT A VALID PROGRAM NAMEExplanation: A START command requested an invalid program name (program).System Action: START processing ends.User Response: Correct and re-enter the START command.

KCP0819 UNABLE TO CONNECT ENTRY TABLEExplanation: An attempt to connect to the entry table created by the cross-memory interface (XMI) task has failed.System Action: The cross-memory interface (XMI) task abnormally terminates with a U0819 completion code.User Response: Contact Candle Customer Support.


KCP0920 probe LOOP DETECTED WHILE COLLECTING column FOR CICS regionExplanation: The probe intercepted a hard loop condition during data collection for a specific CICS region.System Action: Data for the CICS region is not provided by the probe.User Response: None.

KCP0946 module1 (Vnnn) AND module2 (Vnnn) INCOMPATIBLEExplanation: The versions of module module1 and the module it is attempting to load (module2) are incompatible.System Action: The load and its invoking facility fail.User Response: Verify that the CCC for CICS or OMEGAMON XE for CICSplex installation process completed successfully, and that module2 is in the Candle Management Server library.

KCP0999 XMI INTERNAL ERROR – CALL CANDLE TECHNICAL SUPPORTExplanation: The cross-memory interface (XMI) task encountered an event that should not occur.System Action: The cross-memory interface (XMI) task abnormally terminates.User Response: Contact Candle Customer Support.

KCP4151 GROUPNUM CANNOT BE USED MULTIPLE TIMESExplanation: Either multiple predicates in the same query include the GROUPNUM column, or an arithmetic operator other than EQ is used in the expression.System Action: The query is ignored.User Response: Limit the use of GROUPNUM to a single predicate and ensure that the predicate specifies equal (EQ), rather than some other operator.

KCP4153 GROUPNUM FILTER VALUE aa MUST BE BETWEEN 1 AND 30Explanation: A query requested a GROUPNUM of aa that is outside the range of permissible group numbers.System Action: The query is ignored.User Response: Change the group number to be in the range 1-30 and resubmit the request.

KCP9000 routine INITIALIZATION HAS STARTEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex initialization routine routine now has control.System Action: None.User Response: None.

KCP9001 STATISTICS COMMUNICATION AREA NOT AVAILABLEExplanation: The program used to provide performance statistics could not locate the communication area used to collect data.System Action: The MONITOR subtask terminates.User Response: None.


KCP9002 DATA SERVER INTERFACE IS ACTIVEExplanation: The Candle Management Server Interface has completed initialization.System Action: None.User Response: None.

KCP9003 DATA SERVER INTERFACE ALREADY ACTIVEExplanation: A second Candle Management Server Interface task was started while one was already active.System Action: The task terminates.User Response: None.

KCP9004 DATA SERVER INTERFACE IS NOT ACTIVEExplanation: The Candle Management Server Interface is not running.System Action: None.User Response: None.

KCP9005 DATA SERVER INTERFACE IS TERMINATINGExplanation: The Candle Management Server Interface has received a request to terminate.System Action: None.User Response: None.

KCP9006 DATA SERVER INTERFACE IS NOT RESPONDINGExplanation: The Candle Management Server Interface failed to terminate within thirty seconds after being notified to stop.System Action: Once the Candle Management Server Interface detects the shutdown request, it will terminate.User Response: None.

KCP9007 MODULE CSECT ADDRESS DATE TIME SYSMODExplanation: This message is the header line produced in response to an OC DISPLAY MODULES command.System Action: None.User Response: None.

KCP9008 module csect address date time sysmodExplanation: This message is generated for each CSECT on the MVS load list in response to an OC DISPLAY MODULES command. The six fields displayed in this message include the module, csect, address, date, time, and sysmod associated with each CICS module loaded from STEPLIB.System Action: None.User Response: None.

KCP9009 phase INITIALIZATION HAS ENDEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex initialization phase identified by phase has finished.System Action: None.User Response: None.


KCP9010 ATC NO CICS MODULES APPEAR ON LOAD LISTExplanation: The OC DISPLAY MODULES command found no programs on the MVS load list that contained a prefix of KCP.System Action: The command terminates.User Response: None.

KCP9011 ATC UNABLE TO OBTAIN COMMON WORK AREA STORAGEExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller could not acquire its work area.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex collection routines will function.User Response: Increase the amount of memory available to the Candle Management Server. If problems persist, contact Candle Customer Support.

KCP9012 PTHREAD_CREATE() ERRORExplanation: The thread used to monitor active CICS regions could not be started.System Action: None of the OMEGAMON XE for CICS queries will function.User Response: Inspect the logs for a message that might indicate why the thread failed to start. If problems persist, contact Candle Customer Support.

KCP9013 ATC UNABLE TO OBTAIN OCCVT STORAGEExplanation: The system was unable to allocate the OMEGAMON II for CICS communications vector table.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex collection routines will function.User Response: Increase the amount of memory available to the Candle Management Server. If problems persist, contact Candle Customer Support.

KCP9014 PTHREAD_DETACH() ERRORExplanation: Unused resources associated with the subnode monitoring thread cound not be freed.System Action: Resources remain allocated until CT/Engine region termination.User Response: None.

KCP9015 ATC entry_point ROUTINE ENTRY POINT NOT FOUNDExplanation: The program used by the attach controller to start subtasks contains an invalid entry point. entry_point denotes the entry point that could not be located.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex collection routines will function.User Response: Contact Candle Customer Support.


KCP9016 IRA MANAGER COMMAND UNKNOWN: aaaaaaaaExplanation: The IRAMAN KCPAGENT modify command specified an invalid argument, as denoted by aaaaaaaa.System Action: The command is ignored.User Response: Enter the correct IRAMAN KCPAGENT aaaaaaaa modify command.

KCP9017 IRA MANAGER COMMAND OPERAND MISSINGExplanation: The IRAMAN KCPAGENT modify command did not include an argument.System Action: The command is ignored.User Response: Enter the correct IRAMAN KCPAGENT aaaaaaaa modify command.

KCP9018 IRA_SUBNODE_REGISTER ERROR: RC=aa, NODE=bbbbbbbbExplanation: The function used to register CICS bbbbbbbb as on-line failed with a return code denoted by aa.System Action: The CICS subnode will not be available for situations and reports.User Response: Contact Candle Customer Support.

KCP9019 ATC INITIALIZATION RTN DIAGNOSTIC DUMPExplanation: This message provides a heading for work area displays shown in TLVLOG.System Action: None.User Response: None.

KCP9021 IRA_SUBNODE_DEREGISTER ERROR: RC=aa, NODE=bbbbbbbb Explanation: The function used to register CICS bbbbbbbb as off-line failed with a return code denoted by aa. System Action: The CICS subnode will continue to reflect an on-line status regardless of its actual state.User Response: Contact Candle Customer Support.

KCP9022 ATC START COMMAND FAILED. SEE PRIOR MESSAGESExplanation: The attach controller was unable to start an CCC for CICS or OMEGAMON XE for CICSplex function.System Action: The function does not initiate.User Response: Consult TLVLOG for additional messages.


KCP9023 ATC COMMAND FORMAT INVALID, SEE PRIOR MESSAGESExplanation: The attach controller detected a command with invalid syntax.System Action: The command is not processed.User Response: Consult TLVLOG for additional messages.

KCP9024 IRA_SUBNODE_SENDREQUEST CALL RETURNED WITH aaExplanation: The function used to submit CICS subnode status has failed with a return code denoted by aa.System Action: The CICS subnode will not reflect the true state of the region.User Response: Examine the RKLVLOG for messages that may indicate a problem withthe register/deregister functions. If problems persist, contact Candle Customer Support.

KCP9025 aaa UNABLE TO OBTAIN WORK AREA STORAGEExplanation: The agent identified by aaa was unable to allocate main memory.System Action: No data is collected.User Response: Consider increasing the CT/Engine region size.

KCP9030 ATC PROCESSING THE FOLLOWING COMMAND:Explanation: This message precedes any command received by the attach controller.System Action: None.User Response: None.

KCP9038 ATC STOP COMMAND FAILED RC=rcExplanation: An OC STOP command could not be processed.System Action: The task will not be stopped.User Response: Contact Candle Customer Support.

KCP9039 ATC STOP COMMAND FAILED. INTERNAL ERRORExplanation: An OC STOP command could not be processed.System Action: The task will not be stopped.User Response: Contact Candle Customer Support.

KCP9040 ATC STATUS COMMAND BEING PROCESSEDExplanation: A request for status has been received.System Action: None.User Response: None.

KCP9060 ATC THREAD START COMPLETED SUCCESSFULLYExplanation: A CT/Engine thread was initiated.System Action: None.User Response: None.


KCP9069 ATC TASK START FAILED ON $DISP ERRORExplanation: A program could not be initiated due to a dispatch queue problem.System Action: The task does not start.User Response: Contact Candle Customer Support.

KCP9070 CICS JOBNAME PARAMETER IS MISSING OR INVALIDExplanation: A START command for a program that requires a CICS jobname did not properly specify the CICS keyword.System Action: The task does not start.User Response: Ensure that a valid CICS name is passed on the START command.

KCP9198 ATC INITIALIZATION FAILED TO COMPLETE SUCCESSFULLYExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller failed to initialize.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex collection routines will function.User Response: Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact Candle Customer Support.

KCP9199 ATC OPERATOR INTERFACE DISABLED, RESTART REQUIREDExplanation: An error caused the attach controller to fail.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex operator commands will work under CT/Engine.User Response: Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact Candle Customer Support.

KCP9200 ATO OPERATOR INTERFACE NOT INSTALLEDExplanation: The operator interface was not initialized during CT/Engine initialization.System Action: The command is ignored.User Response: Contact Candle Customer Support.

KCP9201 ATO OPERATOR INTERFACE DISPATCH FAILUREExplanation: The system encountered an internal error when attempting to dispatch the work required to process an operator command.System Action: The command is ignored.User Response: Contact Candle Customer Support.

KCP9202 ATO UNABLE TO OBTAIN COMMAND PLIST STORAGEExplanation: Memory could not be acquired for the operator command parameter list.System Action: The command is ignored.User Response: Increase the amount of storage available to the Candle Management Server.


KCP9300 ATC STATUS -- module: entry_pointExplanation: This message displays the entry point of module module in response to a STATUS command with the DEBUG option.System Action: None.User Response: None.

KCP9311 ATC STATUS -- ATC OC$ATCWK: addressExplanation: This message displays the address of the attach parameter list used by the attach controller in response to a STATUS command.System Action: None.User Response: None.

KCP9312 ATC STATUS -- ATC OC$CVT: addressExplanation: This message shows the address of the OMEGAMON II for CICS CVT when a STATUS command is entered.System Action: None.User Response: None.

KCP9313 ATC STATUS -- ATC OC$APARM: addressExplanation: This message displays the attach controller anchor control block address.System Action: None.User Response: None.

KCP9314 ATC STATUS -- TASK ID: task_idExplanation: This message displays the task ID of the active task started by the attach controller.System Action: None.User Response: None.

KCP9315 ATC STATUS -- TASK ID: task_id CICS: regionExplanation: This message displays the task ID for the active task started by the attach controller that is monitoring a specific CICS region.System Action: None.User Response: None.

KCP9316 ATC STATUS -- APARM: address TYPE: typeExplanation: This message displays the address and type of attach parameter lists created by the attach controller.System Action: None.User Response: None.

KCP9317 ATC STATUS -- MODULE: module ENTRY PT: entry_pointExplanation: This message displays the name and entry point of each module loaded by the attach controller.System Action: None.User Response: None.


KCP9318 ATC STATUS -- TCB: address1 EOT ECB: address2Explanation: This message displays the address of each TCB (address1), and its corresponding end-of-task ECB (address2), created by the attach controller.System Action: None.User Response: None.

KCP9398 ATC STATUS -- NO TASKS CURRENTLY ACTIVEExplanation: The attach controller could not find any active tasks in response to a status request.System Action: None.User Response: None.

KCP9399 ATC STATUS -- NO TASKS STARTED YETExplanation: The attach controller has not processed a START command in response to a status request.System Action: None.User Response: None.

KCP9700 ATI SUBTASK INITIALIZATION TDA NOT FOUNDExplanation: The system was unable to locate the target descriptor area used to monitor a CICS region.System Action: The task does not start.User Response: Contact Candle Customer Support.

KCP9701 ATI SUBTASK MODULE E.P. MISSING OR INVALIDExplanation: The program entry point of a module to be started is zero.System Action: The task does not start.User Response: Contact Candle Customer Support.

KCP9889 ATC SOC4 MESSAGES ARE ALREADY SUPPRESSEDExplanation: The OMEGAMON XE for CICS attach controller has received a request to suppress SOC4 log messages, but message suppression is already enabled.System Action: The OC SUPRSOC4 command is ignored.User Response: None.

KCP9890 ATC SOC4 MESSAGE SUPPRESSION ACTIVATEDExplanation: The OMEGAMON XE for CICS attach controller has acknowledged a request to suppress SOC4 log messages.System Action: Messages will not be written to the RKLVLOG when a CICS agent abnormally terminates with a SOC4 abend code.User Response: None.

KCP9891 ATC S0C4 MESSAGE SUPPRESSION NOT ACTIVEExplanation: The OMEGAMON XE for CICS attach controller received a request to suppress S0C4 messages, but message suppression was never enabled.System Action: The OC SUPRS0C4 command is ignored.User Response: None.


KCP9892 ATC S0C4 MESSAGE SUPPRESSION DEACTIVATEDExplanation: Explanation: The OMEGAMON XE for CICS attach controller has acknowledged a request to stop suppressing S0C4 log messages.System Action: A message will be written to the RKLVLOG when CICS agents experience S0C4 ABENDs.User Response: None.

KCP9893 ATC INVALID S0C4 MESSAGE OPTION SPECIFIEDExplanation: The OMEGAMON XE for CICS attach controller did not recognize the S0C4 message suppression option specified in the OC SUPRS0C4 command.System Action: The OC SUPRS0C4 command is ignored.User Response: Reenter the command with an ON or OFF option.

KCP9894 ATC S0C4 MESSAGES ARE ALREADY SUPPRESSEDExplanation: The OMEGAMON XE for CICS attach controller has received a request to suppress S0C4 log messages, but message suppression is already enabled.System Action: The OC SUPRS0C4 command is ignored.User Response: None.

KCP9895 INCORRECT GROUP NAME IN RKCPIN = xxxxxxxx, PROCESSING STOPSExplanation: The CCC for CICS or OMEGAMON XE for CICSplex conversion routine detected the group name xxxxxxxx in the input file to the conversion. The group name should be WLMDEF.System Action: Processing stops.User Response: Ensure the file specified for RKCPIN is the WLMDEF archived file, and rerun this step.

KCP9896 TOO MANY TABLES IN RKCPIN, PROCESSING STOPSExplanation: The CCC for CICS or OMEGAMON XE for CICSplex conversion routine expects a maximum of 7 tables as input in the archive input file, DDname RKCPIN. The number of tables detected indicates the wrong file is being provided as input to KCPCNV00.System Action: Processing stops.User Response: Ensure the file specified for RKCPIN is the WLMDEF archived file, and rerun this step.

KCP9897 DICTIONARY WORK AREA GETMAIN UNSUCCESFUL, PROCESSING STOPSExplanation: The CCC for CICS or OMEGAMON XE for CICSplex conversion routine issued a GETMAIN unsuccessfully.System Action: Processing stops.User Response: Increase the REGION size parameter and rerun this step.


KCP9898 INVALID DICTIONARY POINTER, PROCESSING STOPSExplanation: The CCC for CICS or OMEGAMON XE for CICSplex conversion routine encountered an internal error.System Action: A dump is produced.User Response: Obtain the dump and a printout of the input file and contact Candle Customer Support.

KCP9899 KCPCNV00 PROCESSING COMPLETED WITHOUT ERRORSExplanation: The CCC for CICS or OMEGAMON XE for CICSplex conversion routine ended successfully.System Action: None.User Response: None.

KCP9900 ATC TERMINATION HAS STARTEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex termination routine now has control.System Action: None.User Response: None.

KCP9920 ATC START ATTACH ERROR RC=rcExplanation: The attach controller was unable to start an CCC for CICS or OMEGAMON XE for CICSplex function.System Action: The function does not initiate.User Response: Consult TLVLOG for additional messages.

KCP9921 ATC START REJECTED. TASK ID=task_id CURRENTLY RUNNING. ONLY ONE COPY PERMITTED AT A TIMEExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller found an active copy of task_id running in the Data Server address space.System Action: The START command is ignored.User Response: None.

KCP9922 ATC UNABLE TO OBTAIN ATTACH PARAMETER LIST STORAGEExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller could not acquire memory for the ATTACH macro.System Action: The task does not start.User Response: Increase the amount of memory available to the Candle Management Server. If problems persist, contact Candle Customer Support.

KCP9924 ATC FREEMAIN FAILURE FOR CT/Engine STORAGEExplanation: The system was unable to execute a $FMEM request to release CT/Engine managed storage.System Action: None.User Response: Contact Candle Customer Support.


KCP9925 ATC TASK-START RESOURCE ALREADY FREEDExplanation: The system has released resources associated with a task.System Action: None.User Response: None.

KCP9941 function MVS VERSION UNKNOWNExplanation: The subroutine used to determine the operating system release detected an unsupported release of MVS when called by function function.System Action: The function identified by function does not start.User Response: Contact Candle Customer Support.

KCP9942 function OCVRSN FAILURE, R1=r1, R15=r15Explanation: The subroutine used to determine the operating system release failed with return code r1 when called by function function.System Action: The task does not start.User Response: Contact Candle Customer Support.

KCP9943 ATC NO TABLE ENTRY FOR taskExplanation: The attach controller was unable to locate task task.System Action: The task does not start.User Response: Contact Candle Customer Support.

KCP9945 ATC $LOAD ERROR FOR MODULE: moduleExplanation: The CT/Engine service used to load a program has failed. module is the module that could be found.System Action: The task will not be started.User Response: Contact Candle Customer Support.

KCP9947 ATC ID= PARM NOT SPECIFIED OR INVALIDExplanation: The ID keyword on the OC command specifies an incorrect value.System Action: The task does not start.User Response: Correct the task name on the ID parameter and reenter the command.

KCP9948 ATC ID= PARM LENGTH ERRORExplanation: The ID keyword on the OC command specifies an incorrect value.System Action: The task does not start.User Response: Correct the task name on the ID parameter and reenter the command.

KCP9949 ATC INVALID HEADER FORMAT IN programExplanation: The internal module header in program program cannot be validated.System Action: The task does not start.User Response: Contact Candle Customer Support.

KCP9950 ATC HAS LOADED MODULE: programExplanation: The attach controller loaded program program.System Action: None.User Response: None.


KCP9989 ATC TRACING HAS BEEN ACTIVATEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller has acknowledged a request to turn on trace.System Action: Tracing of CCC for CICS or OMEGAMON XE for CICSplex will be initiated.User Response: None.

KCP9990 ATC INITIALIZATION HAS ISSUED ADDITIONAL ERROR MESSAGESExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller has failed to initialize.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex collection routines will function.User Response: Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact Candle Customer Support.

KCP9991 ATC TRACING IS NOT CURRENTLY ACTIVEExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller received a request to turn tracing off but tracing was never turned on originally.System Action: The OC TRACE command is ignored.User Response: None.

KCP9992 ATC TRACING HAS BEEN DEACTIVATEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller has acknowledged a request to turn off tracing.System Action: Tracing of CCC for CICS or OMEGAMON XE for CICSplex discontinues.User Response: None.

KCP9993 ATC INVALID TRACE OPTION SPECIFIEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller did not recognize the tracing option specified in the OC TRACE command.System Action: The OC TRACE command is ignored.User Response: Reenter the command with an ON or OFF option.

KCP9994 ATC TRACING IS ALREADY ACTIVEExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller has received a request to activate tracing, but tracing is already active.System Action: The OC TRACE command is ignored.User Response: None.


KCP9995 ATC TEST REJECTED, XDC(Y) NOT IN KDSSYSINExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller has received a TEST command but found that the XDC environment had not been established under the Engine.System Action: The OC TEST command is ignored.User Response: Place an XDC(Y) control card in the KDSSYSIN member of TLVPARM and restart the CMS address space.

KCP9996 ATC NOW INOPERATIVE. RESTART REQUIRED.Explanation: In order for CCC for CICS or OMEGAMON XE for CICSplex to collect data, the error that caused the attach controller to fail must be corrected and the Candle Management Server address space restarted.System Action: None. This message is for informational purposes only.User Response: Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact Candle Customer Support.

KCP9997 ATC INITIALIZATION CANNOT BE COMPLETEDExplanation: An error caused the attach controller to fail.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex collection routines will function.User Response: Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact Candle Customer Support.

KCP9998 ATC OPERATOR INTERFACE IS NOW DISABLEDExplanation: An error caused the attach controller to fail.System Action: None of the CCC for CICS or OMEGAMON XE for CICSplex operator commands will work under the Candle Management Server.User Response: Consult the console log for additional messages that would explain why the attach controller could not initialize. If problems persist, contact Candle Customer Support.

KCP9999 ATC TERMINATION HAS ENDEDExplanation: The CCC for CICS or OMEGAMON XE for CICSplex attach controller has terminated.System Action: None.User Response: None.

KD2C0010 INVALID SERVER PARAMETERSExplanation: The capture server component is unable to initialize a server component due to invalid linkage parameters.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.


KD2C0011 UNABLE TO SET RECOVERY ENVIRONMENTExplanation: The capture server component is unable to initialize a server component due to recovery environment errors.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.

KD2C0012 UNABLE TO SET UP ENVIRONMENTExplanation: The capture server component is unable to initialize a server component due to program environment errors.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.

KD2C0013 STORAGE UNAVAILABLE FOR STACKExplanation: The capture server component is unable to initialize a server component due to a shortage of virtual storage.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.

KD200015 DEFERRED ATF SESSION ATF009 COULD NOT OBTAIN THE LOCK, RC=20Explanation: An attempt to serialize access to the ATF VSAM dataset failed. The serialization is attempted 10 times and if, after the tenth time, the lock has not been obtained, then the KD200015 message is issued. The possible reasons are:1. Another user has the ATF dataset open for viewing, when the deferred ATF

trace starts.Ensure that each user has their own ATF dataset allocated for each trace.

2. Another user is executing an ATF report batch job with the ATF dataset being used for input

3. The ATF dataset has not been allocated correctly.Ensure that the dataset is allocated with the following attributes.DEFINE CLUSTER( - NAME(hilev.ATF)MB(050) SHR(2,3) LINEAR)

4. If the dataset is of a large size and has not previously been used, then ATF must initialize the VSAM file before use. The default time for this to occur is 60 seconds. In some installations, this is not sufficient and can lead to corrupted ATF datasets.

System Action: ATF is not started.User Response: Wait until the resource is available, then use a different dataset.

KD2C0021 ENVIRONMENT IS NOT SUPPORTED FOR MODULE mmmmmmmm ROUTINE rrrrrrrrExplanation: The capture server component is unable to load module mmmmmmmm when calling routine rrrrrrrr because the operating system environment is not supported.System Action: The capture server component terminates.


User Response: Contact Candle Customer Support.

KD2C0022 UNABLE TO LOAD MODULE mmmmmmmm FOR ROUTINE rrrrrrrrExplanation: The capture server component is unable to load module mmmmmmmm when calling routine rrrrrrrr because the load module was not found.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.

KD2C0023 UNABLE TO INITIALIZE LOAD MODULE mmmmmmmm FOR ROUTINE rrrrrrrrExplanation: The capture server component experienced an initialization error in module mmmmmmmm when calling routine rrrrrrrr during program initialization.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.

KD2C0024 VECTORS NOT SET BY INITIALIZATION PROGRAM mmmmmmmm FOR ROUTINE rrrrrrrrExplanation: The capture server component experienced an initialization error for module mmmmmmmm when calling routine rrrrrrrr because the program vectors were not correctly set by the initialization routine.System Action: The capture server component terminates.User Response: Contact Candle Customer Support.

KD2C0100 DRIVER INITIALIZEDExplanation: The capture server component is initialized.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0101 DRIVER INIT FAILED - RS ssssssss RI iiiiiiii LR rrrrrrrrExplanation: The capture server initialization request failed.

System Action: Processing terminates.User Response: Contact Candle Customer Support.

KD2C0102 DRIVER TERMINATEDExplanation: The capture server component has terminated.System Action: Processing terminates.User Response: None. This is an informational message only.

RS ssssssss Reason code.

RI iiiiiiii Additional reason information.

LR rrrrrrrr Lower routine return code.


KD2C0103 DRIVER TERM FAILED - RS ssssssss RI iiiiiiii LR rrrrrrrrExplanation: The capture server termination request failed to terminate normally.

System Action: Processing terminates.User Response: Call Candle Customer Support.

KD2C0104 SET NOT STARTED (ccccccccccccccccc) - ssssssssExplanation: The capture server start request failed for set name ssssssss for one of the following reasons (ccccccccccccccccc):

System Action: Processing continues.User Response: Contact Candle Customer Support.

KD2C0105 SET STARTED - ssssssss ccccccccExplanation: The capture server start request is completed for SET name ssssssss and connect ID cccccccc.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0107 SET STOPPED - ssssssss ccccccccExplanation: The capture server resources for SET name ssssssss and connect ID cccccccc have been released/stopped.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0108 SET NOT STARTED (NO CONTAINERS STARTED): ssssssss ccccccccExplanation: The capture server resources for SET name ssssssss and connect ID cccccccc were not allocated/started.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0111 SET NOT STARTED (NO DATA AVAILABLE): ssssssss ccccccccExplanation: The capture server resources for SET name ssssssss and connect ID cccccccc were started for read access, but there was no capture data available.System Action: Processing continues.User Response: None. This is an informational message only.

RS ssssssss Reason code.

RI iiiiiiii Additional reason information.

LR rrrrrrrr Lower routine return code.

SET NOT FOUND The capture container set name ssssssss was not found.

SET ALREADY STARTED The capture container set name ssssssss was already started.


KD2C0120 NO OUTPUT DATASETS AVAILABLE FOR CONTAINER ccccccccExplanation: The capture server has detected that no capture output datasets are available for the container name cccccccc.System Action: Processing continues.User Response: Verify that archival jobs have been completed for all full capture datasets.

KD2C0121 CONTAINER NOT STARTED FOR cccccccc - rrrrrrrrExplanation: The capture server was unable to start the container cccccccc for one of the following reasons (rrrrrrrr):

System Action: Processing continues.User Response: Perform the action that corresponds to the displayed reason.

KD2C0123 START FAILED FOR DATASET - dsname - rrrrrrrrExplanation: The capture server was unable to start the capture dataset dsname for one of the following reasons (rrrrrrrr):

System Action: The start request is terminated.

NO DATA AVAILABLE The container was started for read access, but no data was available.

NO DATASETS STARTED No datasets started due to errors encountered with capture datasets.

PWTR ATTACH FAILED Unable to attach the PWTR subtask.

UNABLE TO INIT OUTPUT Unable to initialize output.

ALLOCATION FAILED xxxxxxxx The dataset dsname was not allocated; the dynamic allocation return code xxxxxxxx.

NOT AUTHORIZED FOR UPDATE The user does not have update access to the dataset.

NOT AUTHORIZED FOR READ The user does not have read access to the dataset.

OPEN FAILED - CHECK DS TYPE The dataset may not be a linear dataset; check the dataset organization type.

DATASET IS NOT LINEAR The capture dataset is not a linear dataset.

DIV ERROR xxxxxxxx yyyyyyyy Data in virtual request failed. The DIV return code is xxxxxxxx and the DIV reason code is yyyyyyyy.

DATASET IS ALREADY IN USE An attempt to start the dataset for update access failed because the dataset is already being used for update access.


User Response: Perform the action that corresponds to the displayed reason.

KD2C0124 WARNING FOR DATASET dsname - 3390 TRK SIZE USED ddddExplanation: The capture server started the dataset, but the dataset is on unknown device type dddd. This may cause a performance degradation.System Action: Processing continues.User Response: Contact Candle Customer Support.

KD2C0125 STOP FAILED FOR DATASET dsname - rrrrrrrrExplanation: The capture server was unable to successfully stop the dataset dsname for one of the following reasons rrrrrrrr.

System Action: Processing continues, all resources for the dataset may not be released.User Response: Contact Candle Customer Support

KD2C0126 VALIDATE FAILED FOR DATASET dsname - rrrrrrrrExplanation: The capture server was unable to successfully validate the capture dataset dsname for one of the following reasons (rrrrrrrr):

ALLOCATION FAILED xxxxxxxx Correct the dataset name, and restart the capture server.

NOT AUTHORIZED FOR UPDATE Verify that the proper authority is given to the dataset.

NOT AUTHORIZED FOR READ Verify that the proper authority is given to the dataset.

OPEN FAILED - CHECK DS TYPE Check the dataset organization; the dataset must be defined as a linear VSAM dataset.

DATASET IS NOT LINEAR Specify a linear dataset name, and restart the capture server.

DIV ERROR xxxxxxxx yyyyyyyy Verify that the dataset is a linear VSAM dataset. If it is, contact Candle Customer Support; otherwise, redefine the dataset as a linear dataset.

DATASET IS ALREADY IN USE Verify that the dataset is correctly being used by the capture server.

DEALLOC FAILED The dynamic deallocation failed.

DIV ERROR xxxxxxxx yyyyyyyy Data in virtual request failed. The DIV return code is xxxxxxxx, and the DIV reason code is yyyyyyyy.


Note: Under some situations, the dataset can be archived.

System Action: Processing continues.User Response: Contact Candle Customer Support.

KD2C0127 FORMAT FAILED FOR DATASET - dsname - PRIMARY EXTENT IS TOO SMALLExplanation: The capture server was unable to format the capture dataset dsname because the primary extent is below the minimum size.System Action: Processing terminates; the dataset is not used.User Response: Redefine the capture dataset with a primary size of a least 3 cylinders, 45 tracks, or 370K, and restart the capture server.

DUPLICATE VALIDATION TIME A duplicate validation time exists. This may be the result of a duplicate dataset. The dataset can be archived; the dataset is not available for interactive retrieval.

XID# IS OUT OF SYNC The internal index directory XID# is not synchronized with the control block XCI#. This may be the result of a system outage. The dataset can be archived; the dataset is not available for interactive retrieval.

XIB# IS OUT OF SYNC The current index block XIB# is not synchronized with the control block XCI#. This may be the result of a system outage. The dataset can be archived; the dataset is not available for interactive retrieval.

XCI# IS CORRUPTED The control block XCI# is corrupted. The dataset is not usable.

XID# IS CORRUPTED The current index directory block XID# is corrupted. The dataset is not usable.

XIB# IS CORRUPTED The current index block XIB# is corrupted. The dataset is not usable.

DECOMPRESS IS UNAVAILABLE The dataset contains compressed data and the dataset is being accessed from an MVS/XA system. The IBM data expansion service load module CSRCEXA cannot be loaded. The procedure for making the load module available is documented in the MVS/ESA Application Development Guide. The dataset is not usable.

DATASET VERSION UNSUPPORTED The capture dataset is at an unsupported version. See message KD2C0131. Verify that the most recent maintenance is applied to all product components. The dataset is not usable.


KD2C0128 CAPTURING OUTPUT ON DATASET dsnameExplanation: The capture server has selected the current capture dataset dsname for output.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0129 CAPTURE DATASET HAS BEEN RESET FOR REUSE - dsnameExplanation: The capture server has reset the capture dataset dsname for reuse.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0130 DUPLICATE OBJECT ON DATASET dsname - object versionExplanation: The capture server has detected that the capture dataset has a duplicate object and version that exists in other datasets, but the data description does not match all other capture datasets.System Action: Processing terminates.User Response: Contact Candle Customer Support.

KD2C0131 VERSION OF CAPTURE DATASET IS UNSUPPORTED - DATASET xxxx CAPTURE yyyyExplanation: The capture server has detected that the capture dataset was created, but it is at an unsupported version. The dataset is at version xxxx while the highest supported version is yyyy.System Action: Processing terminates.User Response: Contact Candle Customer Support.

KD2C0132 CAPTURING OUTPUT ON LAST AVAILABLE DATASET FOR CONTAINER ccccccccExplanation: The capture server is capturing output on the last available dataset. System Action: Processing continues.User Response: Verify that all full capture datasets are archived.

KD2C0133 CAPTURE DATASET IS REUSABLE - dsnameExplanation: The capture server has detected that the capture dataset dsname is now reusable.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0140 SWITCHING FROM DATASET dsname - rrrrrr Explanation: The capture server is switching from the capture dataset dsname for one of the following reasons (rrrrrr):

DATASET IS FULL The capture dataset cannot be extended.

INDEX DIRECTORY IS FULL All usable space in the index directory blocks are used.


System Action: Processing continues.User Response: Perform the action that corresponds to the displayed reason.

KD2C0141 SWITCH IS REJECTED - CAPTURE SERVER IS TERMINATINGExplanation: The capture server switch request was rejected because the capture server is terminating.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0142 USER SWITCH REQUEST REJECTED - NOT CURRENTLY CAPTURING OUTPUT TO CONTAINER ccccccccExplanation: The capture server user switch request was rejected because the capture server is not currently capturing output for the container cccccccc.System Action: Processing continues.User Response: None. This is an informational message only.

KD2C0143 USER SWITCH REQUEST REJECTED - CURRENT OUTPUT DATASET IS EMPTY FOR CONTAINER ccccccccExplanation: The capture server user switch request was rejected because the current capture dataset is empty.System Action: Processing continues.User Response: Stop the capture server if the dataset must be deallocated.

KD2C0200 DIV I/O ERROR - DATASET dsname - DIV ERROR xxxxxxxx yyyyyyyyExplanation: A data in virtual request failed. The DIV return code is returned as xxxxxxxx and the DIV reason code is return as yyyyyyyy.System Action: Processing terminates.User Response: Contact Candle Customer Support.

USER REQUEST A dynamic request for switch has been requested.

OBJECT DIRECTORY IS FULL No more objects can be contained in the dataset.

DATASET IS FULL None. This is an informational message only.

INDEX DIRECTORY IS FULL None. This is an informational message only.

USER REQUEST None. This is an informational message only.

OBJECT DIRECTORY IS FULL Contact Candle Customer Support.


KD2C0900 ERROR DETECTED BY mmmmmmm Sxxxx Uuuuu RC=yyyyyyyy PSW=pppppppp pppppppp AT rrrrrrrr +offset levelExplanation: An abend has been detected by a capture server component.

System Action: Processing terminates.User Response: Contact Candle Customer Support.

KD2EXPFF PROFILE EXPORT FAILEDExplanation: The profile export was unable to complete properly due to an error.System Action: The profile is not exported to the requested dataset member.User Response: See the RKLVLOG for a more detailed message describing the error.

KD2EXP00 PROFILE EXPORT COMPLETED SUCCESSFULLYExplanation: The profile export was completed successfully.System Action: Profile is exported to the dataset specified in the command parameter list.User Response: None. This is an informational message only.

KD2IMPFF PROFILE IMPORT FAILEDExplanation: The profile import was unable to complete properly due to an error.System Action: The profile is not imported from the requested dataset member.User Response: See the RKLVLOG for a more detailed message describing the error.

KD2IMP00 PROFILE IMPORT COMPLETED SUCCESSFULLYExplanation: The profile import was completed successfully.System Action: Profile is imported from the dataset specified in the command parameter list.User Response: None. This is an informational message only.

KD2SSTR VSSENTRY: RC = nnExplanation: Dialog KD2SSTR received return code nn from VSSENTRY.System Action: Dialog KD2SSTR terminates.User Response: See the CL/SUPERSESSION Dialog Language Reference Manual for VSSENTRY information and an explanation of the specified return code.

mmmmmmm Module affected.

Sxxxx System abend code.

Uuuuu User abend code.

RC=yyyyyyy Reason code.

AT rrrrrrr+offset Module in error and its offset.

level Maintenance level of the module in error.


KDC00001 Bind complete: socket_addressExplanation: This is an informational message indicating that server initialization is complete. The server is listening for client requests on the socket_address specified.System Action: None.User Response: None.Message Type: INFO.

KDC00002 LLB service is active.Explanation: This is an information message indicating that the local location broker is active.System Action: None.User Response: None.Message Type: INFO.

KDC00003 GLB service is activeExplanation: This is an informational message indicating that the Global Location Broker is active.System Action: None.User Response: None.Message Type: INFO.

KDC00004 status codeExplanation: Status code status code was returned.System Action: None.User Response: None.Message Type: INFO.

KDC00005 Family unavailable: family_nameExplanation: Protocol (family) initialization for stack family_name has failed.System Action: The protocol (family) family_name is disabled and unavailable for use. Processing continues without family_name.User Response: This message does not necessarily indicate an error condition. DCS will attempt to initialize all protocol stacks (families) on a given platform. If a protocol is not explicitly disabled (see KDC_FAMILIES for more on disabling protocols) DCS will attempt to initialize that protocol for use. Family (protocol) initialization fails for these reasons:® Subsystem is not available. It is common to see SNA initialization fail in UNIX

environments because then basic subsystem services are not present.

® Protocol family is not properly configured. For MVS, the IP protocol family requires configuration of KLXINTCP for IBM’s IP stack, or KLXAINIT for Interlink’s IP stack.

® Run-time conflict or environment error. Run-time errors resulting in family (protocol) initialization failures are typically socket errors. See socket error messages for specific errors which are likely to result in protocol initialization failures.

Message Type: ERROR.


KDC00006 No families availableExplanation: DCS start-up has failed to initialize any protocol stack (family) for product use. No communication is possible.System Action: DCS terminates with errors.User Response: Family (protocol) initialization fails for these reasons:® Subsystem is not available. It is common to see SNA initialization fail in UNIX

environments because the basic subsystem services are not present.

® Protocol family is not properly configured. For MVS, the IP protocol family requires configuration of KLXINTCP for IBM’s IP stack, or KLXAINIT for Interlink’s IP stack.

® Run-time conflict or environment error. un-time errors resulting in family (protocol) initialization failures are typically socket errors. See socket error messages for specific errors which are likely to result in protocol initialization failures.

This is a terminal error. See DCS Configuration Reference for assistance on product configuration.Message Type: ABEND.

KDC00007 Family limit exceededExplanation: The number of available address families (protocols) exceeds the architectural limit of the product.System Action: The additional protocol stacks are ignored.User Response: This is a very unusual circumstance and one which should be reported to Candle Customer Support.Message Type: INFO.

KDCN0001 Component &1 started. Status: &2.Destination: OS/400=CNB3205Severity: 0System Programmer Response:No

KDCN0003 Component &1 (&2) status: &3.Explanation:

ComponentStatus Code Explanation

GLBD 20 Network transport is not available to establish communication.

LLBD 20 Cannot open the assigned known port.

LLBD 40 Network transport is not available.


User Response:

Destination: OS/400=CNB3206Severity: 0System Programmer Response:No

KDCN0004 Candle Management Server (CMS) &1 directory server did not start.Explanation: The directory server did not start.User Response: View errors entered in the CMS product log. Also, check the directory server joblog for additional messages. Correct error, end subsystem library, and start CMS again. Destination: OS/400=CNB0007Severity: 20System Programmer Response:Unattended

KDF0116E ERROR DURING KDFSHSML SDUMPX PROCESSING, RC= xxx, REASON= xxxExplanation: An SDUMPX macro, issued during abnormal termination of HSM log analysis, has failed.System Action: Abnormal termination will continue.User Response: This error should not occur. Contact Candle Customer Support.Destination: The MVS system console.

KDFAAE00 UNABLE TO OPEN FORM AUTHORIZATION TABLEExplanation: An update of the form authorization table failed.System Action: The form authorization record is not stored.User Response: Ensure that the CT/Engine table database cluster was defined according to product installation instructions. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAAE01 UNABLE TO OPEN FORM AUTHORIZATION TABLEExplanation: An update of the form authorization table failed.System Action: The form authorization record is not stored.

ComponentStatus Code User Response

GLBD 20 ® If SNA network transport is needed, check Candle Management Server (CMS) configuration. Make sure that SNA local LU name is specified as NONE.

® If TCP/IP network transport is required, check the CMS configuration. Specify the correct TCP/IP host address in TCP/IP address field.

LLBD 20 End the running LLBD and start CMS again.

LLBD 40 See status code 20 for GLBD.


User Response: Make sure that the CT/Engine table database cluster has enough space and extents. If the dataset has sufficient space, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAPP01 USER user_id HAS LOGGED ONExplanation: Logon processing for the specified user was completed.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFAPP02 USER user_id HAS LOGGED OFFExplanation: The specified user has logged off.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFAPP03 DEBUG MESSAGES ARE SUPPRESSEDExplanation: The generation of internal diagnostic messages was suppressed.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFAPP04 FORM LOADS WILL BE FORCEDExplanation: This message displays during a diagnostic routine.System Action: Product panels are reinitialized each time that they are executed by the product.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFAPP05 AUTHORIZATION FAILURE FOR PANEL panel_id, USER IS user_idExplanation: A user tried to access a panel or product function, but lacked authorization.System Action: The user is not granted access to the panel or function.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFAP0000I SERVICE PROBES INITIALIZATION HAS BEGUNExplanation: Initialization of the service probes has begun.System Action: The service probes continue initialization.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0001I SERVICE PROBES ANCHOR BLOCK HAS BEEN CREATEDExplanation: The service probes anchor block has been created.System Action: The service probes initialization continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.


KDFAP0019S SERVICE PROBES ANCHOR BLOCK CREATE ERROR STATUS CODE status_code REASON CODE reason_codeExplanation: The service probes anchor block could not be created.System Action: The service probes terminate.User Response: This is an internal error. Contact Candle Customer Support and provide the message contents.Destination: The CT/Engine log, RKLVLOG.

KDFAP0020S SERVICE PROBES NOT INITIALIZEDExplanation: An attempt was made to use the OMEGAMON II for SMS action services before they were made available.System Action: OMEGAMON II continues to run, however the action service probes cannot be executed.User Response: In order to run the action service probes, the CMS component must be fully initialized. If it is not, initialize CMS and retry the probes.If the CMS component was initialized and already issued the message KLVIN408 CANDLE ENGINE VERSION 170 READY, then check the CMS RKLVLOG for these informational messages:

KDFAP0000I SERVICE PROBES INITIALIZATION HAS COMMENCEDKDFAP0001I SERVICE PROBES ANCHOR BLOCK HAS BEEN CREATED

If these messages are found, the service probes should be initialized. Contact Candle Support Services for further information.If these messages are not found, then the action services probes have not been initialized. To investigate further:® Search the RKLVLOG of CMS for any related error messages.

® Insure that the RKANPAR datasets for CMS are correct.

® Insure that the RKANPAR dataset members have not been inadvertently modified.

Correct any errors and restart CMS. If further assistance is necessary, contact Candle Support Services.Destination: The RKLVLOG from the CMS address space.

KDFAP0021S SERVICE PROBES RUNTIME PARAMETER MEMBER KDFACTIN NOT FOUNDExplanation: An error occurred when an attempt was made to open the service probes runtime parameters member KDFACTIN. Member KDFACTIN could not be found in the RKANPARS dataset.System Action: Message KDFAP0029 is issued and the service probes terminate.User Response: Verify that member KDFACTIN exists in the RKANPARS dataset.Destination: The CT/Engine log, RKLVLOG.


KDFAP0022S SERVICE PROBES RUNTIME PARAMETER MEMBER KDFACTIN OPEN ERROR RETURN CODE return_codeExplanation: An error occurred when an attempt was made to open the service probes configuration parameter member KDFACTIN. Return codes are

System Action: Message KDFAP0029 is issued and the service probes terminate.User Response: If the problem persists, contact Candle Customer Support and provide the return code.Destination: The CT/Engine log, RKLVLOG.

KDFAP0023S SERVICE PROBES RUNTIME PARAMETER MEMBER KDFACTIN READ ERROR RETURN CODE return_codeExplanation: An error occurred when an attempt was made to read the service probes runtime parameters member KDFACTIN. Return codes are

System Action: Message KDFAP0029S is issued and the service probes terminate.User Response: If the problem persists, contact Candle Customer Support and provide the return code.Destination: The CT/Engine log, RKLVLOG.

KDFAP0024W KDFACTIN RUNTIME PARAMETER parameter_name NOT RECOGNIZEDExplanation: An unrecognized parameter was specified in the service probes runtime parameters member KDFACTIN.

0 Function completed successfully.

4 Invalid PDS handle.

5 Unsuccessful open.

6 Member not found.

8 Dynamic allocation failed.

9 DSNAME is greater than 44 characters.

10 DDNAME is greater than 8 characters.

0 Function completed successfully.

2 End of file.

4 Invalid PDS handle.

5 Get unsuccessful.

>256 An abend occurred. The value of the abend code is determined by dividing the return code value by 256. If the result is less than 4096, the abend code is issued as a result of a system abend. Otherwise the code is issued as a result of a user abend. The user abend code can be determined by subtracting 4096 from the result (after dividing by 256).


System Action: The parameter is ignored. The service probes continue to read the runtime parameters from the member KDFACTIN.User Response: Correct the runtime parameters member KDFACTIN.Destination: The CT/Engine log, RKLVLOG.

KDFAP0025E SERVICE PROBES RUNTIME PARAMETER MEMBER KDFACTIN CLOSE ERROR RETURN CODE return codeExplanation: A error occurred when closing the runtime parameters member KDFACTIN.System Action: The service probes terminate.User Response: This is an internal error. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP0028I SERVICE PROBES RUNTIME PARAMETER MEMBER KDFACTIN WAS READ SUCCESSFULLYExplanation: The runtime parameters for OMEGAMON II for SMS service requests were read successfully.System Action: The service probes initialization continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0029S SERVICE PROBES RUNTIME PARAMETER COULD NOT BE READExplanation: The runtime parameters for OMEGAMON II for SMS services requests could not be read.System Action: The service probes terminate.User Response: Review any error messages that precede this one. Contact Candle Customer Support if further assistance is required.Destination: The CT/Engine log, RKLVLOG.

KDFAP0030I PARAMETER parameter_name HAS BEEN ASSIGNED THE VALUE parameter_valueExplanation: This message confirms the value assigned to the specified parameter by the runtime parameters member KDFACTIN.System Action: The service probes continue to read the configuration parameters member KDFACTIN.User Response: If the value is unsatisfactory, change the appropriate line in the runtime parameters member KDFACTIN.Destination: The CT/Engine log, RKLVLOG.

KDFAP0031W PARAMETER parameter_name WAS SPECIFIED PREVIOUSLYExplanation: The value assigned to the specified parameter has already been assigned.System Action: The duplicate value is ignored and the service probes continue initializing.User Response: Check the runtime parameters member KDFACTIN and remove the duplicate specification of this parameter value.Destination: The CT/Engine log, RKLVLOG.


KDFAP0033W PARAMETER parameter_name VALUE parameter_value IS TOO LONG. MAXIMUM LENGTH IS maximum_length.Explanation: The value assigned to the specified parameter is too long.

System Action: The parameter assignment is ignored. The service probes continue initializing.User Response: Correct or remove the specified runtime parameter.Destination: The CT/Engine log, RKLVLOG.

KDFAP0034W PARAMETER parameter_name VALUE parameter_value IS TOO LARGE. MAXIMUM VALUE IS maximum_value.Explanation: The value assigned to the specified parameter is too large.

System Action: The parameter specification is ignored. The service probes continue initializing.User Response: Correct or remove the specified runtime parameter.Destination: The CT/Engine log, RKLVLOG.

KDFAP0035W PARAMETER parameter_name VALUE parameter_value IS TOO SMALL. MINIMUM VALUE IS minimum_valueExplanation: The value assigned to the specified parameter is too small.

System Action: The parameter specification is ignored. The service probes continue initializing.User Response: Correct or remove the specified runtime parameter.Destination: The CT/Engine log, RKLVLOG.

KDFAP0036W PARAMETER parmname VALUE parmvalue IS NOT NUMERICExplanation: A non-numeric value was specified for the numeric parameter.System Action: The incorrectly specified value is ignored. Service probes continue initializing.User Response: Correct or remove the specified runtime parameter.Destination: The CT/Engine log, RKLVLOG.

parameter_name The KDFACTIN keyword parameter name.

parameter_value The incorrectly specified value of the keyword parameter.

maximum_length The maximum acceptable length of the value.








KDFAP0039E RUNTIME PARAMETER parameter_name HAS NOT BEEN SPECIFIED AND WILL NOT BE DEFAULTEDExplanation: A valid assignment for the specified parameter could not be found in the runtime parameters member KDFACTIN. The parameter can not be defaulted.System Action: The service probes terminate.User Response: Add an assignment for the specified parameter to the runtime parameters member KDFACTIN and restart the service probes.Destination: The CT/Engine log, RKLVLOG.

KDFAP0040S SERVICE PROBES ADMINISTRATION RECORD READ ERRORExplanation: An attempt to read the administration record from the checkpoint dataset has failed. The administration record contains information associated with service requests issued during previous executions of the data collection (CMS) address space.System Action: The service probes initialization terminates and service requests will not be accepted for the remainder of the data collection (CMS) address space execution.User Response: Determine why the administration record cannot be read. If the service request checkpoint dataset has been corrupted, restore the dataset from a backup or delete and recreate the dataset. Warning: Previously issued service requests status and response information may

be lost by restoring or recreating the checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP0042W SERVICE PROBES CHECKPOINT DATASET OPEN FAILUREExplanation: An attempt to open the checkpoint dataset for service requests has failed. The service probes assume that this is the first time the checkpoint dataset has been utilized.System Action: The service probes will perform a cold start and write an administration record to the checkpoint dataset.User Response: None, unless the checkpoint dataset has been utilized by the service probes previously. If it has been utilized previously, attempt to determine why an administration record could not be found. If necessary, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP0043S SERVICE PROBES ADMINISTRATION RECORD NOT RECOGNIZEDExplanation: An invalid administration record was found in the service checkpoint dataset.System Action: The service probes terminate.User Response: Investigate why the administration record is invalid. If necessary, contact Candle Customer Support for assistance. To permit the service probes to initialize, restore the service checkpoint dataset (to restore any completed requests and responses), or redefine the service checkpoint dataset (to reinitialize the service probes).Destination: The CT/Engine log, RKLVLOG.


KDFAP0044I SERVICE PROBES ARE BEING COLD STARTEDExplanation: The service probes are being cold started.System Action: Service probes initialization continues. A new administration record is written to the service checkpoint dataset and the initialization continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0045I SERVICE PROBES ADMINISTRATION RECORD FOUNDExplanation: A valid administration record was found in the service checkpoint dataset.System Action: The service probes will be warm started.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0046I SERVICE PROBES ARE BEING WARM STARTEDExplanation: The checkpoint dataset for service requests have been successfully opened and checkpoint information will be used to restore service request information.System Action: Service probes initialization continues. Any completed requests and responses at the time of the previous termination are restored.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0047W SERVICE REQUEST RECORD FOR REQUEST nnn IS NOT RECOGNIZEDExplanation: An invalid service request record, request ID nnn, was found in the service checkpoint dataset when attempting to restore service requests from the checkpoint dataset.System Action: The invalid request record will be deleted. The request restoration processing continues.User Response: Investigate why the record was invalid. If the problem cannot be determined, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP0050I number_of_requests SERVICE REQUESTS HAVE BEEN RESTOREDExplanation: The specified number of service requests have been restored from the service checkpoint dataset.System Action: The service probes continue initialization.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0090I SERVICE PROBES INITIALIZATION HAS COMPLETEDExplanation: The initialization of the service probes has completed.System Action: The service probes will await service requests.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0091S SERVICE PROBES INITIALIZATION HAS FAILEDExplanation: The initialization of the service probes has failed.


System Action: The service probes indicate they are unable to process service requests.User Response: See the previous messages for the cause of the failure.Destination: The CT/Engine log, RKLVLOG.

KDFAP0100I SERVICE PROBES TERMINATION HAS BEGUNExplanation: The termination of the service probes has begun.System Action: The service probes termination continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0101I SERVICE PROBES TERMINATION HAS COMPLETEDExplanation: The termination of the service probes has completed.System Action: The service probes terminate.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0110A OMEGAMON II SMS SERVICES IN PROGRESS. DELAY SHUTDOWN(Y/N)?Explanation: Service requests on DASD volumes or datasets are currently in progress. The console operator must reply Y to delay the shutdown of the data collection (CMS) address space, or N to continue with immediate shutdown.System Action: The address space shutdown is suspended until the console operator replies to the message.User Response:1. Reply Y or YES to delay the shutdown of the data collection (CMS) address

space until active service requests are completed.2. Reply N or NO to proceed with an immediate shutdown of the data collection

(CMS) address space.3. Any other reply will cause the WTOR message to be reissued.

Note: Proceeding with the shutdown can cause damage to DASD volumes and datasets currently being processed by the address space. If a NO reply is issued, use the data logged in the MSG System Log and the RKLVLOG of the data collection (CMS) address space to review the service requests in progress at the time of shutdown. Refer to messages KDFAP120I and KDFAP130I.

Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

KDFAP0111I ADDRESS SPACE WILL BE SHUTDOWN IMMEDIATELYExplanation: This message is issued when the reply to message KDFAP0110A was N or NO.System Action: The data collection address space terminates immediately, abnormally terminating (ABEND SA03) the current services in progress.User Response: None.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.


KDFAP0112I SHUTDOWN IS DELAYED UNTIL SERVICES COMPLETEExplanation: This message is issued when user replies Y or YES to message KDFAP0110A.System Action: The data collection (CMS) address space shutdown is delayed until all services requests in execution are completed. Normal termination is resumed after service requests have completed.User Response: None.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

KDFAP0113I INVALID REPLY. Y=DELAY SHUTDOWN N=IMMEDIATE SHUTDOWNExplanation: This message is issued when an invalid reply is received for message KDFAP0110A.System Action: The console operator is reprompted for a decision to delay the data collection (CMS) address space shutdown by reissuing message KDFAP0110A.User Response: Reply Y or N to message KDFAP0110A.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

KDFAP0114W SERVICE REQUEST reqid COULD NOT BE CANCELEDExplanation: The service probes attempted to cancel an action request when preparing for termination; however, the attempt failed. This should not have any significant impact on the service probes.

System Action: The service probes continue to terminate.User Response: None.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

KDFAP0115I OMEGAMON II SMS SERVICES COMPLETEDExplanation: This message follows message KDFAP0112I and indicates that the outstanding service requests causing the data collection (CMS) address space shutdown delay have completed.System Action: The service probes termination completes and the data collection (CMS) address space continues with shutdown processing.User Response: None.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

KDFAP0120I SERVICE IN PROGRESS AT SHUTDOWNExplanation: This message precedes the list of active services requests at data collection (CMS) address space shutdown. Message KDFS0130S follows this message and lists the service requests in progress.System Action: See message KDFAP0130I.User Response: See message KDFAP0130I.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

reqid Identifies the ID number of the service request that could not be cancelled.


KDFAP0121W SERVICE PROBES ANCHOR BLOCK DESTROY ERROR STATUS CODE status_code REASON CODE reason_codeExplanation: The service probes anchor block could not be destroyed. This message should not have any significant impact on the service probes.System Action: Message KDFAP0100 will be issued and the service probes will terminate.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP0130I service_request ON volser_or_dataset name STARTED AT yy/mm/dd hh:mm:ssExplanation: This message follows message KDFAP0120I and is issued for each service request in progress at the time of data collection (CMS) address space shutdown.

System Action: Termination processing for the address space is suspended. WTOR message KDFS0110A is issued to prompt the console operator to delay the shutdown until service requests on DASD volumes and datasets complete.User Response: If an immediate shutdown is requested, or the address space is cancelled while the service requests were in progress, integrity of the DASD volume or datasets should be reviewed. If necessary, manual recovery processing should be taken to restore the DASD volume or datasets. Recovery processing depends on the service in progress:® Any HSM service requests—No recovery processing required.

® DFDSS Compress Dataset—If the dataset is damaged, recover the dataset from the HSM BACKDS taken immediately before compress processing was initiated.

® DFDSS Defragment Volume—DADSM message IEC602 will be issued if a dataset is accessed on a volume where DFDSS DEFRAG did not complete. Dataset SYS.DFDSS.DEFRAG.xxxxxx.volser.DUMMY is allocated on the volume by DFDSS and remains on the volume if the defragmentation was interrupted. Resubmit a DFDSS DEFRAG request on the volume to correct the problem.

service_request The description of the service request in progress.

volser_or_dataset name

The volume serial number of the DASD volume or name of the dataset being processed by the service request.

yy/mm/dd The date at which the service request started execution.

hh:mm:ss The time at which the service request started execution.


Note: OMEGAMON II also issues an HSM incremental backup before initiating defragment volume processing. If the IEC602 message is not corrected by resubmitting the defragmentation request, or if immediate access to datasets on the volume are required, an HSM recovery request can be used to restore individual datasets on the volume, or a HSM dump restore and incremental forward recovery can be used to restore the entire volume.

® All other DFDSS service requests—No recovery processing required.

Destination: The CT/Engine log, RKLVLOG.

KDFAP0900E DFDSS ACTION REQUEST ADDRESS SPACE HAS NOT BEEN CONFIGURED REFER TO CANDLE DOCUMENT DF99-4853, DSS VSCR, FOR CONFIGURATION INFORMATIONExplanation: The SLAVESTCNAME parameter was not found in the KDFACTIN member of dataset rhilev.RKANPAR. This parameter is required to execute DFDSS action requests.System Action: The service probe initialization fails. All dataset and volume action probes are suspended for further execution.User Response: Refer to Candle document DF99-4853, DSS VSCR, for information on how to configure the action request started task.Destination: The CT/Engine log, RKLVLOG.

KDFAP1010W FREE FAILED FOR DDNAME= ddname. RC=rc ERROR=error INFO=infoExplanation: A service response dataset containing response text could not be freed. The dataset is most likely open by another thread of execution and cannot be freed until the other thread of execution has closed the dataset.

System Action: This message is issued to the RKLVLOG. No further actions are taken to delete the dataset. If the error occurred in response to an SQL DELETE request to remove a completed service request, a return code of RCABVU (26) is returned to the application issuing the DELETE.User Response: None.Destination: The CT/Engine log, RKLVLOG.

ddname the DDNAME of the response dataset allocation

rc the SVC 99 return code for the deallocation request

error the SVC 99 error code for the deallocation request

info the SVC 99 information code for the deallocation request


KDFAP1020W DELETE FAILED FOR RESPONSE DATASET dsname Explanation: The service response dataset containing response text could not be freed and deleted in response to a SQL DELETE or while attempting to copy the contents of the dataset to the service checkpoint dataset. The dataset was most likely opened by another thread of execution and cannot be freed until that thread of execution has closed the dataset.

System Action: This message is issued to the RKLVLOG. No further actions are taken to delete the dataset. If the error occurred in response to an SQL DELETE request to remove a completed service request, a return code of RCABVU (26) is returned to the application issuing the DELETE.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFAP1110E UNABLE TO ALLOCATE SERVICE RESPONSE DATASET. RC= p0Explanation: The routine called to satisfy a service request could not allocate the service response dataset to save service response text. Dataset allocation could not be satisfied for the address space, or installation exits prevent the allocation of the dataset. p0 specifies the return code issued by the TSO/E ALLOCATE command. The most likely cause of the problem is that the response dataset was deleted or is currently allocated by another address space.System Action: The service request fails and a -3000 is set for the return code of the request.User Response: Determine why the dataset could not be allocated. If the problem cannot be determined, contact Candle Customer Support for assistance.Destination: Review the appropriate destination.

KDFAP1120E UNABLE TO WRITE TO SERVICE RESPONSE DATASET. RC= p0Explanation: An attempt to write response text to a service response dataset failed. p0 specifies the return code issued by the REXX EXECIO command. The most likely cause of this error is that the data collection (CMS) address space does not write security access to the response dataset, or an I/O error occurred on the volume on which the dataset resides.System Action: The current request for service fails and -4000 is set for the return code of the request.User Response: Determine why the write operation failed. If the problem cannot be determined, contact Candle Customer Support for assistance.

dsname The dataset name of the response dataset.

OMEGAMON II for SMS The CMS address space log, RKLVLOG.

All other products The data collection (CMS)address space SYSTSPRT output file.


Destination: Review the appropriate destination.

KDFAP1130E UNABLE TO ALLOCATE INPUT VIO DATASET. RC= p0.Explanation: The routine called to satisfy a service request could not allocate a temporary VIO dataset for control statements read by utility programs. VIO dataset allocation could not be satisfied for the address space, or installation exits prevent the allocation of the VIO dataset. p0 specifies the return code issued by the TSO/E ALLOCATE command.System Action: The service request fails and a -5000 is set for the return code of the request.User Response: Ensure that the data collection (CMS) address space is allowed to allocate temporary datasets to UNIT(VIO). Also ensure that VIO dataset allocation is configured properly for the system.Destination: Review the appropriate destination.

KDFAP1140I NO ADDITIONAL INFORMATION IS AVAILABLEExplanation: The routine called to satisfy a service request did not receive any response text for the request.System Action: The service request completes normally.User Response: None.Destination: Review the appropriate destination.


All other products The data collection (CMS) address space SYSTSPRT output file.






KDFAP1220E REXX ERROR EXECUTING EXEC ’ p0’. REXX RETURN CODE p1.Explanation: An error occurred when invoking the specified REXX exec. p1 specifies the REXX return code.System Action: The attempt to perform the associated service request is aborted. See TSO/E REXX Programming Services IRXEXEC return codes for a description of the actions taken by REXX.User Response: See the REXX messages issued prior to this message for more information regarding the error.Destination: Review the appropriate destination.

KDFAP1230E NULL RESULT FROM REXX EXEC ’ p0’.Explanation: A null result was returned by the specified REXX exec. The exec should provide a numeric result.System Action: None.User Response: This error may have been caused by an error in the stated REXX exec. Contact Candle Customer Support providing this message with the REXX exec name. If this problem has not been reported previously, you must determine why the REXX exec did not return a result. You might have to place additional problem determination aids in the REXX exec. Of course, the exec may have been changed by the customer.Destination: Review the appropriate destination.

KDFAP1231E NON-NUMERIC RESULT FROM REXX EXEC ’ p0’.Explanation: A non-numeric result was returned by the specified REXX exec. The exec should provide a numeric result.System Action: None.User Response: The routine calling REXX failed to indicate that a only a numeric result was valid. Contact Candle Customer Support providing this message with the REXX exec name. If this problem has not been reported previously, you must determine why the REXX did not return a numeric result. The routine calling REXX, KDFIRACT, may have failed to indicate the REXX exec was being invoked as a command, or a REXX error may have occurred. REXX

OMEGAMON II for SMS The CMS address space log, RKLVLOG, or the MVS system console.

All other products The data collection (CMS) address space SYSTSPRT output file, or to the MVS control console (WTO). or to the MVS system console (WTO).


All other products The data collection (CMS) address space SYSTSPRT output file, or to the MVS control console (WTO).


should detect an error (and issue message IRX0026) if a non-numeric result is being returned by an exec invoked as a command.Destination: Review the appropriate destination.

KDFAP1291E UNABLE TO ISSUE p0Explanation: An attempt to issue the specified message using the TSO/E PUTLINE service failed.System Action: An abend U0910 occurs after this message is issued and a dump is taken.User Response: See the description of the message that could not be issued. To determine why the TSO/E PUTLINE service failed, contact Candle Customer Support providing this message and the message that could not be issued. Also, have the abend U0910 dump available. This message should never be issued. It is issued only if the TSO/E PUTLINE service responds with a return code other than 0, 12, or 16. No other return codes should be applicable in the KDFIRACT environment.Destination: The MVS control console (WTO).

KDFAP1292E UNABLE TO ISSUE p0 - INVALID PARAMETERSExplanation: An attempt to issue the specified message using the TSO/E PUTLINE service failed. TSO/E indicated the associated parameters were invalid.System Action: An abend U0920 occurs after this message is issued and a dump is taken.User Response: See the description of the message that could not be issued. To determine why the TSO/E PUTLINE service failed, contact Candle Customer Support providing this message and the message that could not be issued. Also, have the abend U0920 dump available. This message is issued when the TSO/E PUTLINE service provides return code 12. The dump should be examined to determine why the parameter list was invalid.Destination: The MVS control console (WTO).

KDFAP1293E UNABLE TO ISSUE p0 - INSUFFICIENT STORAGEExplanation: An attempt to issue the specified message failed. TSO/E indicated that there was insufficient storage to issue the message.System Action: The system action depends on the text of the message that could not be issued. Refer to the system action of the message.User Response: See the description of the message that could not be issued. If this message is issued often, determine why storage was insufficient to issue the message.Destination: The MVS control console (WTO).


All other products The data collection (CMS) address space SYSTSPRT output file, or to the MVS control console (WTO).


KDFAP1310E INCOMPATIBLE LEVEL OF TSO/E. VERSION 2.3.0 OR ABOVE REQUIRED. VERSION=p0 RELEASE=p1.Explanation: The action services could not be initialized because an unsupported version of TSO/E was found. Action services requires TSO/E VERSION 2.3.0 or above to satisfy action requests. Variables p0 and p1 report the version and release of TSO/E found for the system.System Action: The action request processing is disabled for the remainder of the data collection (CMS) address space execution.User Response: Install the required version of TSO/E before attempting to issue any action requests.Destination: The CT/Engine log, RKLVLOG.

KDFAP1410E LOAD FAILED FOR MODULE= p0 ABEND=p1 REASON CODE=p2.Explanation: An attempt to load an executable load module p0 into virtual storage has failed with an MVS abend code of p1 and reason code of p2. Action load modules are dynamically loaded into virtual storage when the first action request is received. Subsequent action requests will reuse the dynamically loaded modules. If a load fails, the current action request fails as will subsequent action requests.System Action: The current request for action fails and a nonzero return code is returned to the application program.User Response: Refer to the MVS system codes documentation for further details on the load failure. Ensure that the complete set of load modules are referenced by the STEPLIB concatenation of the started task JCL. Also ensure that the entire list of load module libraries in the STEPLIB concatenation are APF-authorized.Destination: The CT/Engine log, RKLVLOG.

KDFAP1420E TSO/E ENVIRONMENT INITIALIZATION FAILED. RETURN CODE rc REASON CODE reason ABEND CODE abend.Explanation: An attempt to initialize the TSO/E environment for processing of OMEGAMON II for SMS service requests has failed.

System Action: Service request processing is disabled for the remainder of the CMS (data collection) address space execution, and OMEGAMON II for SMS service requests will not be accepted.

rc Specifies the return code from the TSO/E services environment initialization routine, IKJTSOEV.

reason Specifies the reason code from the TSO/E services environment initialization routine, IKJTSOEV.

abend Specifies the abend code from the TSO/E services environment initialization routine, IKJTSOEV.


User Response: Using the return code, reason code, and abend code displayed, determine why the TSO/E environment could not be initialized. Correct the error and restart the CMS address space to enable service request processing. If the cause of the initialization failure cannot be determined, contact Candle Customer Support for assistance.Destination: The CT/Engine log, RKLVLOG.

KDFAP1430E CONDITION VARIABLE INITIALIZATION FAILED. ERROR NUMBER nnn.Explanation: An attempt to initialize a POSIX condition variable used for service requests completion notification has failed.

System Action: Service request processing is disabled for the remainder of the CMS (data collection) address space execution, and OMEGAMON II for SMS service requests will not be accepted.User Response: Contact Candle Customer Support for assistance.Destination: The CT/Engine log, RKLVLOG.

KDFAP1440E MUTEX VARIABLE INITIALIZATION FAILED. ERROR NUMBER nnn.Explanation: An attempt to initialize a POSIX mutual exclusion variable used for service request serialization locks has failed.

System Action: Service request processing is disabled for the remainder of the CMS (data collection) address space execution, and OMEGAMON II for SMS service requests will not be accepted.User Response: Contact Candle Customer Support for assistance.Destination: The CT/Engine log, RKLVLOG.

KDFAP1450E UNABLE TO VERIFY PROPER FORMAT FOR MODULE KDFCRAETExplanation: Module KDFCRAET was loaded but the data found in the module was not in the format expected by the service probes.System Action: Service request initialization fails, and OMEGAMON II for SMS service requests will not be accepted for the remainder of the CMS (data collection) address space execution.User Response: This is an internal error. Verify that the KDFCRAET module was installed correctly and placed in an APF-authorized library. Contact Candle Customer Support for further assistance.Destination: The CT/Engine log, RKLVLOG.

nnn Specifies the error number set by the POSIX pthread_cond_init initialization routine.

nnn Specifies the error number set by the POSIX pthread_mutex_init initialization routine.


KDFAP1510E SERVICE PROBES COULD LOCATE ANCHOR BLOCK. STATUS=status REASON=reason.Explanation: This message indicates that the service probes attempt to locate the anchor block containing administrative control data has failed.

System Action: The service probes request will fail and return an error status to the application program making the request.User Response: This is an internal error. Contact Candle Customer Support and provide the message.Destination: The CT/Engine log, RKLVLOG.

KDFAP1520E UNABLE TO CREATE RESPONSE DATASET dsname FOR REQUEST reqidExplanation: The service probes could not create and catalog the specified service response dataset for service request reqid.System Action: The service probes request will fail and return an error status to the application program making the request.User Response: Ensure that the OMEGAMON II service request parameters specified in the KDFACTIN member of the runtime parameters dataset has been configured properly. Also verify that the security access rights have been granted to the data collection (CMS) address space to allow dataset create, delete, read, and write access to service response datasets.Destination: The CT/Engine log, RKLVLOG.

KDFAP1530E NEW REQUEST HAS DUPLICATE KEY OF reqidExplanation: The service probes could not accept a new a service request because a previously issued request uses the same internal request identifier. reqid identifies the ID number of the failed service request.System Action: The service probes request will fail and return an error status to the application program making the request.User Response: Ensure that the OMEGAMON II checkpoint dataset has not been overwritten. If the checkpoint dataset is damaged, the dataset can be restored to its original state from a dataset backup of the VSAM cluster, or it can be deleted and recreated. Restoration or recreation can cause the loss of service requests that have checkpointed. This problem may occur because a large number of service requests were issued and never deleted. If a large number of unwanted service requests are retained in the checkpoint dataset, issue delete requests to clear the unwanted requests and allow request identifiers to be reused.Destination: The CT/Engine log, RKLVLOG.

status Specifies the return code returned by the anchor locate service.

reason Specifies the reason code returned by the anchor locate service routine.


KDFAP1550S SERVICE REQUESTS DISABLED DUE TO CHECKPOINT FAILUREExplanation: This message is issued after a fatal checkpoint failure has been detected. Refer to messages issued prior to this message to determine the exact cause of the failure.System Action: The service request being processed fails and an error return code is set for the request. Additionally, service request processing will be disabled and no new service requests will be accepted.User Response: Ensure that the OMEGAMON II checkpoint dataset has not been overwritten and free space has not been exhausted. If the checkpoint dataset is damaged, the dataset can be restored to its original state from a dataset backup of the VSAM cluster, or it may be deleted and recreated. Restoration can cause the loss of service requests that were checkpointed after the backup was taken. This problem may occur because a large number of service requests were issued and never deleted. If a large number of unwanted service requests are retained in the checkpoint dataset, issue delete requests to allow storage in the checkpoint dataset to be reused.Destination: The CT/Engine log, RKLVLOG.

KDFAP1560E UNABLE TO CANCEL REQUEST reqid STATUS=statusExplanation: This message is issued when an attempt to cancel a service request that is awaiting execution or is currently executing, fails.

This message is normally issued during the shutdown of the data collection (CMS) address space when service requests are either awaiting execution or executing. Service requests awaiting execution will be restored upon restart of the data collection (CMS) address space, if possible. This message can also be issued in response to a delete operation on service requests that are awaiting execution.System Action: An error code is returned if the cancellation failure occurred as a result of a delete operation. Otherwise data collection (CMS) address space termination processing continues.User Response: If this message is issued in response to a delete action against a service request awaiting execution, contact Candle Customer Support for assistance.Destination: The CT/Engine log, RKLVLOG.

reqid Identifies the ID number of the service request that could not be cancelled.

status Identifies the error status code returned by thread cancellation service routine.


KDFAP1600I SERVICE REQUEST reqid STARTED. action ON objclass object.Explanation: This message indicates that a service request has begun execution.

System Action: The service request will complete normally but the cataloged dataset containing the response text will be kept until the text can be successfully copied to the checkpoint dataset. The service probes will attempt to copy the response text upon the next restart of the data collection (CMS) address space.User Response: If the checkpoint dataset is full, issue delete operations on unwanted service requests to allow storage in the checkpoint dataset to be reused.Destination: The CT/Engine log, RKLVLOG.

KDFAP1610E UNABLE TO READ CHECKPOINT DATASET FOR UPDATE FOR REQUEST reqidExplanation: This message indicates that the service probes could not recall the existing service request reqid from the checkpoint dataset.System Action: The service request will fail with a nonzero return code time of the failure will be noted, and a negative return code value for the request will be set.User Response: This is an internal error. If the cause of the error cannot be determined, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP1620E UNABLE TO UPDATE CHECKPOINT DATASET FOR REQUEST reqidExplanation: This message indicates that the service probes could not update the existing service request reqid in the checkpoint dataset. System Action: The service request will fail with a nonzero return code; time of the failure will be noted, and a negative return code value for the request will be set.User Response: This is an internal error. If the cause of the error cannot be determined, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

reqid Identifies the ID number of the service request.

action Describes the action request to be executed.

objclass Indicates the type of service to be executed. Possible values are DASD Volume or Dataset.

object Indicates the VOLSER of the DASD volume if the objclass value was DASD Volume, or the dataset name if the objclass value was Dataset.


KDFAP1630W UNABLE TO CONSOLIDATE RESPONSES FOR REQUEST reqidExplanation: This message indicates that the service probes could not copy text from a response dataset into the checkpoint dataset. Text temporarily stored in response datasets is copied to the checkpoint dataset following completion of each request. Response datasets are only deleted if the text is successfully copied to the checkpoint dataset. The most likely causes of the failure are:® Data collection address space shutdown was in progress during an attempt to

consolidate the response text.

® Lack of sufficient free storage in the checkpoint dataset to receive the response text.

System Action: The service request will complete normally but the cataloged dataset containing the response text will be kept until the text can be successfully copied to the checkpoint dataset. The service probes will attempt to copy the response text upon the next restart of the data collection (CMS) address space.User Response: If the checkpoint dataset is full, issue delete operations on unwanted service requests to allow storage in the checkpoint dataset to be reused.Destination: The CT/Engine log, RKLVLOG.

KDFAP1640E UNABLE TO DELETE CHECKPOINT RECORD FOR REQUEST reqidExplanation: The service probes could not delete the existing service request reqid in the checkpoint dataset.System Action: The deletion of the request will fail and a return code is issued indicating that the delete failure will be returned to the application program issuing the delete.User Response: This is an internal error. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP1645E TIMED-OUT WAITING FOR CHECKPOINT DATASET LOCK (KDFRRAQD)Explanation: The service probes could not obtain the checkpoint dataset lock. System Action: The request will fail. A return code will be issued to the application making the request.User Response: This is an internal error. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP1650E UNABLE TO READ ADMINISTRATION RECORD FROM CHECKPOINT DATASET.Explanation: This message indicates that the service probes could not recall the administration record from the checkpoint dataset.System Action: The service request will fail with a nonzero return code time of the failure will be noted, and a negative return code value for the request will be set.User Response: This is an internal error. If the cause of the error cannot be determined, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

reqid Identifies the ID number of the service request that could not be consolidated.


KDFAP1660E UNABLE TO UPDATE ADMINSTRATION RECORD IN CHECKPOINT DATASET.Explanation: The service probes could not update the administration record in the checkpoint dataset.System Action: The service request will fail with a nonzero return code time of the failure will be noted, and a negative return code value for the request will be set.User Response: This is an internal error. If the cause of the error cannot be determined, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP1670E UNABLE TO ADD NEW CHECKPOINT RECORD FOR REQUEST reqidExplanation: The service probes could not add a record to the checkpoint dataset for a new service request. The most likely cause of the failure is lack of sufficient free storage in the checkpoint dataset to receive the request record.System Action: The service request will fail with a nonzero return code time of the failure will be noted, and a negative return code value for the request will be set.User Response: Determine why the checkpoint dataset could not be updated. If the checkpoint dataset is full, issue delete operations on unwanted service requests to allow storage in the checkpoint dataset to be reused. If the cause of the error cannot be determined, contact Candle Customer Support for further assistance.Destination: The CT/Engine log, RKLVLOG.

KDFAP1690I SERVICE REQUEST reqid COMPLETED. RC=rcExplanation: This message indicates that service request reqid has completed execution.

System Action: The next service request in queue (if any) will be executed.User Response: The service request status and detail panels may be used to review the success or failure of the completed service request. If the record of the service request is no longer needed, a delete operation should be issued on the service request to allow storage in the checkpoint dataset to be reused.Destination: The CT/Engine log, RKLVLOG.

rc Identifies the return code value set by the service provider routine. This value is identical to the value displayed on service request details panels.


KDFAP1701E UNABLE TO ALLOCATE SERVICE RESPONSE DATASET dataset_name RETURN CODE return_code REASON CODE reason_code INFO CODE info_codeExplanation: An attempt to dynamically allocate the specified service response dataset failed. The service probes are unable to copy a service response from a service response dataset. The return code, reason code, info code, and message text provide detailed information regarding the error.

System Action: The service probes will not attempt to copy the service response again during this execution of the service probes.User Response: Determine why the dynamic allocation failed. The return code, reason code, and info code are documented in the MVS/ESA Authorized Assembler Programming Guide. If necessary, contact Candle Customer Support and provide the message contents.Destination: The CT/Engine log, RKLVLOG.

KDFAP1701I UNABLE TO ALLOCATE SERVICE RESPONSE DATASET dataset_name RETURN CODE return_code REASON CODE reason_code INFO CODE info_codeExplanation: An attempt to dynamically allocate the specified service response dataset failed. The service probes are unable to copy a service response from a service response dataset. The return code, reason code, info code, and message text provide detailed information regarding the error.

System Action: The service probes will not attempt to copy the service response again during this execution of the service probes.User Response: Determine why the dynamic allocation failed. The return code, reason code, and info code are documented in the MVS/ESA Authorized Assembler Programming Guide. If necessary, contact Candle Customer Support and provide the message contents.Destination: The CT/Engine log, RKLVLOG.

datatset_name The dataset name of the response dataset.

rc The SVC 99 return code for the allocation request.

error The SVC 99 error code for the allocation request.

info The SVC 99 information code for the allocation request.

dataset_name The dataset name of the response dataset.

rc The SVC 99 return code for the allocation request.

error The SVC 99 error code for the allocation request.

info The SVC 99 information code for the allocation request.


KDFAP1702E SERVICE RESPONSE DATASET OPEN ERROR dataset_name reasonExplanation: An attempt to open the specified service response dataset failed.

System Action: Unpredictable, as the system action is dependent upon the action that failed.User Response: Investigate the problem. See the following message. If appropriate, contact the Candle Customer Support and provide the message. Destination: The CT/Engine log, RKLVLOG.

KDFAP1703E SERVICE RESPONSE DATASET GET ERROR dataset_name reasonExplanation: An attempt to get a record from the specified service response dataset failed.

System Action: Unpredictable, as the system action is dependent upon the action that failed.User Response: Investigate the problem. See the following message. If appropriate, contact Candle Customer Support and provide the message.Destination: The CT/Engine log, RKLVLOG.

dataset_name The name of the dataset that failed to be opened.

reason Reason code describing the open failure:

4 Invalid DD name.8 Invalid record format.12 Invalid organization.16 RDJFCB macro call failed.20 Open process failed.24 Resource creation failed.52 OBTAIN macro call failed.256 System abend code abend_code.

dataset_name The name of the dataset that failed to be closed.

reason Close reason code describing the failure:

4 Invalid DD name.8 Invalid record format.12 Invalid organization.16 RDJFCB macro call failed.20 Open process failed.24 Resource creation failed.52 OBTAIN macro call failed.256 System abend code abend_code.


KDFAP1704E INVALID VALUES FOR SPACE space FOR ACTION actionExplanation: An invalid action effector table entry for the SPACEAE column was found.

System Action: The action request is not accepted and an INSERT return code is set for the request.User Response: This is an internal processing error. Contact Candle Customer Support and provide the message.Destination: The CT/Engine log, RKLVLOG.

KDFAP1801S SERVICE CHECKPOINT DATASET OWNERSHIP ACQUIRE FAILED. DSN=dsn.Explanation: The service probes claimed ownership of the service checkpoint dataset but the request failed. This message indicates another CMS address space, perhaps on another system in a shared DASD environment, owns the service checkpoint dataset, thus preventing this address space from having exclusive control.

System Action: The service probes terminate.User Response: Identify the other CMS address space that owns the checkpoint dataset specified in the KDFACTIN runtime parameter member. Ensure that no two CMS address spaces use the same checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP1802W SERVICE CHECKPOINT DATASET OWNERSHIP RELEASE ERROR.Explanation: A request to release the service checkpoint dataset ownership failed.System Action: The service probes continue execution. This error should not have any significant impact on the service probes.

User Response: None.Destination: The CT/Engine log, RKLVLOG.

space The invalid values specified in the SPACEAE column of the action effector table (OMSMS.ACTEFTRTAB).

action The value of the ACTNAMEAE column in the row of the action effector table (OMSMS.ACTEFTRTAB).

dsn Specifies the name of the checkpoint dataset.

dsn Specifies the name of the checkpoint dataset.


KDFAP1811S SERVICE CHECKPOINT DATASET OPEN ERROR RETURN CODE return_code REASON CODE reason_code.Explanation: The request to open the service checkpoint dataset failed.System Action: The service probes terminate.User Response: Determine why the open request failed. The return code and reason code are from a VSAM OPEN request and are documented in MVS/DFP Macro Instructions for Data Sets. If necessary, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFAP1812W SERVICE CHECKPOINT DATASET CLOSE ERROR INVALID HANDLEExplanation: The request to close the service checkpoint dataset failed.System Action: The service probes continue execution. The most likely cause of this error is a failure to open the checkpoint dataset. This error should not have any significant impact on the service probes.User Response: Refer to previously issued messages associated with possible open or dynamic dataset allocation errors.Destination: The CT/Engine log, RKLVLOG.

KDFAP1821E SERVICE CHECKPOINT DATASET reqtype REQUEST ERROR INVALID HANDLEExplanation: A service checkpoint dataset request failed because an invalid buffer was used. This is an internal error.

System Action: Unpredictable, as the system action is dependent upon the action that failed.User Response: This is an internal error. Contact Candle Customer Support and provide the message contents.Destination: The CT/Engine log, RKLVLOG.

KDFAP1822E SERVICE CHECKPOINT DATASET reqtype REQUEST ERROR VSAM RETURN CODE return code VSAM REASON CODE reason codeExplanation: A service checkpoint dataset request failed. VSAM provided a return code and a reason code.

System Action: Unpredictable, as the system action is dependent upon the action that failed.

reqtype Identifies the type of the I/O request. Values are: ACQUIRE BUFFER, BUFFER FLUSH, ERASE, GET, GET LOCK, POINT, PUT, START, and END.


return code Identifies the VSAM return code issued by the checkpoint dataset I/O routine.

reason code Identifies the VSAM reason code issued by the checkpoint dataset I/O routine.


User Response: Investigate the cause of the error. The return code and reason code are from the VSAM request and are documented in MVS/DFP Macro Instructions for Data Sets.Destination: The CT/Engine log, RKLVLOG.

KDFAP1823E SERVICE CHECKPOINT DATASET reqtype REQUEST ERROR BUFFER TOO SMALLExplanation: The request to get a service checkpoint dataset record failed because the buffer provided to receive the record was too small. This is an internal logic error.

System Action: Unpredictable, as the system action is dependent upon the type of record being read. The service probes will continue processing if possible. Other messages issued with this message may provide further details.User Response: This is an internal error. Contact Candle Customer Support and provide the message.Destination: The CT/Engine log, RKLVLOG.

KDFAP1824E SERVICE CHECKPOINT DATASET reqtype REQUEST ERROR RETURN CODE rc NOT RECOGNIZEDExplanation: An I/O request to the service checkpoint dataset failed. This is an internal logic error.

System Action: Unpredictable, as the system action is dependent upon the type of record being read. The service probes will continue processing if possible. Other messages issued with this message may provide further details.User Response: This is an internal error. Contact Candle Customer Support and provide the message.Destination: The CT/Engine log, RKLVLOG.



rc Identifies the return code issued by the VSAM I/O service.


KDFAP1830E SERVICE CHECKPOINT DATASET STORAGE EXHAUSTED. PUT REQUEST ERROR. VSAM RETURN CODE return code VSAM REASON CODE reason code.Explanation: A PUT I/O request to the service checkpoint dataset failed. A secondary allocation could not be acquired for the checkpoint dataset and no free storage could be found in the VSAM cluster.

System Action: The service probes will continue processing, if possible. Other messages issued with this message may provide further details.User Response: Ensure that the OMEGAMON II checkpoint dataset has not been overwritten and free space has not be exhausted. If the checkpoint dataset is damaged, the dataset can be restored to its original state from a dataset backup of the VSAM cluster, or it may be deleted and recreated. Restoration can cause the loss of service requests that were checkpointed after the backup was taken. This problem may also be caused by the unlikely event that a large number of service requests have been issued and never deleted. If a large number of unwanted service requests are retained in the checkpoint dataset, issue delete requests to allow storage in the checkpoint dataset to be reused. The TSO LISTC command, the IDCAMS LISTC command, or OMEGAMON II can be used to review the checkpoint dataset disk utilization. If more storage is required, the checkpoint dataset should be reallocated using larger primary and secondary allocation parameters. Contact Candle Customer Support for further assistance.Destination: The CT/Engine log, RKLVLOG.

KDFAP2010E SHOWCB FIELDS=(ACBLEN,RPLLEN), ERROR: R15(R15) R0(R0)Explanation: An attempt to determine the length of a VSAM access control block and a request parameter list failed. The SHOWCB is issued to recover from a previously detected VSAM OPEN failure.System Action: Open processing fails, and service probes initialization completes unsuccessfully.User Response: Ensure that the VSAM KSDS has been properly created for the OMEGAMON II for SMS services checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP2020E GENCB BLK=ACB ERROR: R15(R15) R0(R0)Explanation: An attempt to create and initialize a VSAM access control block has failed. The GENCB is issued to recover from a previously detected VSAM OPEN failure.System Action: Open processing fails, and service probes initialization completes unsuccessfully.User Response: Ensure that the VSAM KSDS has been properly created for the OMEGAMON II for SMS services checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

return code The VSAM return code issued by the checkpoint dataset I/O routine.

reason code The VSAM reason code issued by the checkpoint dataset I/O routine.


KDFAP2030E GENCB BLK=RPL ERROR: R15(R15) R0(R0)Explanation: An attempt to create and initialize a VSAM request parameter list has failed. The GENCB is issued to recover from a previously detected VSAM OPEN failure.System Action: Open processing fails, and service probes initialization completes unsuccessfully.User Response: Ensure that the VSAM KSDS has been properly created for the OMEGAMON II for SMS services checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP2040E UNABLE TO OPEN DDNAME(ddname) R15(R15) ACBERFLG(acberflg)Explanation: An attempt to reopen a VSAM dataset for load processing has failed. The OPEN is issued to recover from a previously detected VSAM OPEN failure.System Action: Open processing fails, and service probes initialization completes unsuccessfully.User Response: Ensure that the VSAM KSDS has been properly created for the OMEGAMON II for SMS Services Checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP2050E UNABLE TO INITIALIZE DDNAME(ddname) R15(R2) RPLERRCD(rplerrcd)Explanation: An attempt to load a new record into a VSAM dataset for load processing has failed. A PUT is issued to initialize the contents of a VSAM dataset that previously failed to OPEN.System Action: Open processing fails, and service probes initialization completes unsuccessfully.User Response: Ensure that the VSAM KSDS has been properly created for the OMEGAMON II for SMS services checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP2060E UNABLE TO CLOSE DDNAME(ddname) R15(R2) ACBERFLG(acberflg)Explanation: An attempt to close a VSAM dataset for load processing has failed. The CLOSE is issued to initialize the contents of a VSAM dataset that previously failed to OPEN.System Action: Open processing fails, and service probes initialization completes unsuccessfully.User Response: Ensure that the VSAM KSDS has been properly created for the OMEGAMON II for SMS services checkpoint dataset.Destination: The CT/Engine log, RKLVLOG.

KDFAP3004E DFDSS MASTER A.S. DETECTED ERROR DURING SLAVE A.S. EXECUTIONExplanation: The DFDSS slave address space returned a non-zero condition code to the master address space.System Action: The DFDSS master task terminates.User Response: Check the DFDSS slave address space for messages or a dump.Destination: The MVS system console.


KDFAP3006E SLAVE ADDRESS SPACE POSSIBLE JCL ERRORExplanation: The DFDSS slave address space ended without returning a condition code.System Action: The DFDSS master task terminates.User Response: A JCL error may have occurred. Check for any messages or for a dump in the DFDSS slave address space.Destination: The MVS system console.

KDFAP3007E TIMED OUT WAITING FOR SLAVE A.S. INITIALIZATIONExplanation: The SLAVESTCTIMEOUT value was exceeded before DFDSS slave address space initialization completed.System Action: The DFDSS master task terminates.User Response: Check the DFDSS slave address space for messages or a dump. You can also check the value of SLAVESTCTIMEOUT in member KDFACTIN in library rhilev.RKANPAR, and, if appropriate, change the time-out value (specified in seconds).Destination: The MVS system console.

KDFAP3008E ERROR OCCURRED IN SLAVE A.S., CHECK FOR POSSIBLE DUMPExplanation: The DFDSS slave address space returned a non-zero condition code to the master address space.System Action: The DFDSS master task terminates.User Response: Check the DFDSS slave address space for messages or a dump.Destination: The MVS system console.

KDFAP3009E ERROR DURING enqueue/dequeue, CODE= cccc, TERMINATINGExplanation: An error occurred during an enqueue or dequeue. The condition code from the error is included.System Action: The DFDSS master task terminates.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3012E ERROR INITIATING DFDSS STC, RC= rcrc, REASON= reasonExplanation: An error occurred starting the DFDSS slave address space. The ASCRE macro provides the rcrc and reason values.System Action: The DFDSS master task terminates.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3013E ERROR DURING SLAVE A.S. INITIALIZATION, RETURN CODE= rcrcExplanation: During initialization, the DFDSS slave address space returned a non-zero condition code to the master address space.System Action: The DFDSS master task terminates.User Response: Check the DFDSS slave address space for messages or a dump.Destination: The MVS system console.


KDFAP3014E ERROR ENCOUNTERED IN IKJTSOEV, RETURN CODE= rcrc, REASON CODE= reasonExplanation: A non-zero code was returned from the TSO/E environmental initialization.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3015E LOAD FAILED FOR MODULE IKJTSOEV, RETURN CODE= rcrc, REASON CODE= reasonExplanation: A non-zero code was returned from LOAD while attempting to load the module.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3016E ERROR DURING DYNAMIC ALLOCATION, ERROR= eeee, INFO= iiiiExplanation: A non-zero code was returned while attempting to dynamically allocate a resource.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3017E ERROR DURING VSAM OPERATION ON ACTION RESPONSE CHECKPOINT DATA, ERROR= eeeeExplanation: The DFDSS slave address space attempted to open, read, update, or close the Response Checkpoint Dataset. VSAM returned a non-zero condition code. Additional action messages will indicate the exact operation. One of the following messages will follow this message: KDFAP3035E, KDFAP3036E, KDFAP3037E, or KDFAP3038E.System Action: The DFDSS slave and master tasks terminate.User Response: Check the DFDSS slave address space for additional messages.Destination: The MVS system console.

KDFAP3030E ERROR OBTAINING SLAVE A.S. ENQ, RETURN CODE= rcrc, TERMINATINGExplanation: A non-zero code was returned while attempting to obtain an ENQUE.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.


KDFAP3031E ERROR ALLOCATING ACTION RESPONSE DATASET, TERMINATINGExplanation: An error was encountered dynamically allocating the action response dataset. Message KDFAP3016E should precede this message and provide the exact error and resolution.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3032E ERROR OBTAINING CMS ENQ, RETURN CODE= rcrc, TERMINATINGExplanation: A non-zero code was returned attempting to obtain an ENQUE.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3033E ERROR DURING ATTACH OF KDFIRACT, RETURN CODE= rcrc, TERMINATINGExplanation: A non-zero code was returned from ATTACH while attempting to execute the request REXX exec.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3034E ERROR ALLOCATING ACTION RESPONSE CHECKPOINT DATASET, TERMINATINGExplanation: An error was encountered dynamically allocating the action response checkpoint dataset. Message KDFAP3016E should precede this message and provide the exact error and information codes for resolution.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3035E ERROR OPENING ACTION RESPONSE CHECKPOINT DATASET, TERMINATINGSystem Action: An error was encountered opening the action response checkpoint dataset. Message KDFAP3017E should precede this message and provide the exact error and information codes for resolution.The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3036E ERROR READING ACTION RESPONSE CHECKPOINT DATASET, TERMINATINGExplanation: An error was encountered reading the action response checkpoint dataset. Message KDFAP3017E should precede this message and provide the exact error and information codes for resolution.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.


KDFAP3037E ERROR UPDATING ACTION RESPONSE CHECKPOINT DATASET, TERMINATINGExplanation: An error was encountered updating the action response checkpoint dataset. Message KDFAP3017E should precede this message and provide the exact error and information codes for resolution.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3038E ERROR CLOSING ACTION RESPONSE CHECKPOINT DATASET, TERMINATINGExplanation: An error was encountered closing the action response checkpoint dataset. Message KDFAP3017E should precede this message and provide the exact error and information codes for resolution.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3040E ERROR RETRIEVING PARMS, RC= rcrc, REASON= reasonExplanation: A non-zero return code was received from ASEXT while attempting to move from the DFDSS master address space to the slave address space.System Action: The DFDSS slave and master tasks terminate.User Response: Call Candle Customer Support.Destination: The MVS system console.

KDFAP3041E DFDSS SLAVE ADDRESS SPACE STARTED WITH INVALID JOB PARMS= (invalid_job_parms)Explanation: Invalid parameters were specified on the EXEC statement in the slave address started task JCL.System Action: The DFDSS slave and master tasks terminate.User Response: Correct the started task JCL and resubmit the request.Destination: The MVS system console.

KDFAPT33 OMEGAMON II FOR SMS IS UNABLE TO CONNECT TO CT/DSExplanation: The OMEGAMON II for SMS address space is unable to communicate with the CMS address space.System Action: None.User Response: Contact Candle Customer Support.

KDFAUT00 - SUPER USER HAS LOGGED ONExplanation: The special user ID CANSUPER was used to gain access to the product.System Action: The user logging on with the CANSUPER ID gains access to all product functions.User Response: None. This message is informational. See the OMEGAMON II for SMS User’s Guide for more information about CANSUPER.Destination: The CT/Engine log, RKLVLOG.


KDFAUT01 ATTEMPT TO LOGON AS SUPER USER FAILEDExplanation: An attempt was made to log onto the product using the special administrative logon ID CANSUPER. An incorrect password was specified.System Action: Access to the product is not granted.User Response: Repeat the logon procedure, specifying the correct password. If you do not have the correct password, contact your product administrator.Destination: The CT/Engine log, RKLVLOG.

KDFCH01I SQL LOAD COMPLETE, MEMBER= member.Explanation: This message is generated for each SQL source member that is loaded either during OMEGAMON II for SMS address space initialization or as a result of a a user navigating to a product panel.System Action: This message is issued to the RKLVLOG.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFCH02I PANEL LOAD COMPLETE, MEMBER= member.Explanation: This message is generated for each panel initialization source member that is loaded either during OMEGAMON II for SMS address space initialization or as a result of a user navigating to a product panel.System Action: This message is issued to the RKLVLOG.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFCH03E MEMORY ALLOCATION FAILURE, MEMBER= member.Explanation: This message is generated if storage is unable to be allocated during loading of SQL or panel initialization data.System Action: This message is issued to the RKLVLOG. The load request fails and returns a nonzero return code. The user session will continue, although blank or incorrect data may be shown.User Response: Increase virtual storage allocation for the address space and restart it.Destination: The CT/Engine log, RKLVLOG.

KDFCH04E I/O ERROR ON READ, MEMBER= member.Explanation: This message is generated if an I/O error occurs when trying to read data from either an SQL source dataset or from panel initialization data. member indicates the PDS member causing the error.System Action: This message is issued to the RKLVLOG. The load request fails and returns a nonzero return code. The user session will continue.User Response: Any panel showing results from this query will provide incorrect or blank output. Review product installation logs for errors, then contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.


KDFCT003 KDFS APPLICATION vtam-appl STARTEDExplanation: The OMEGAMON II for SMS application has been successfully started where vtam-appl is the OMEGAMON II for SMS APPLID.System Action: None.User Response: None. This is an informational message only.Destination: The CT/Engine log, RKLVLOG, and the MVS system console.

KDFD001I–KLGLM027 281

KDFD001I–KLGLM027

KDFD001I KDFDEVIN INPUT PARMS: parametersExplanation: This message displays the input parameters for data collection which are specified in the KDFDEVIN member of a dataset pointed to by the RKANPAR DD statement for the CMS address space.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFD002W KDFDEVIN: SMFDINTV VALUE=OFF; SMF DEVICE RECORDING DISABLEDExplanation: The KDFDEVIN member of a dataset pointed to by the RKANPAR DD statement for the CMS address space contains the parameter SMFDINTV(OFF).System Action: SMF recording is disabled within the CMS.User Response: None. This message is informational.To enable SMF recording within the CMS, specify a valid recording interval for the SMFDINTV parameter and a valid SMF user record number for the SMFRECN parameter. The SMFDINTV parameter accepts the following values:

Specify a user record number from 128–255 for the SMFRECN parameter. Restart the CMS address space.Destination: The CT/Engine log, RKLVLOG.

RMFSYNC Synchronizes with the RMF interval.

SMFSYNC Synchronizes with the SMF interval.

1-1439 Specifies the recording interval in minutes.

4


KDFD003W KDFDEVIN: INVALID SMFDINTV VALUE; SMF DEVICE RECORDING DISABLEDExplanation: The KDFDEVIN member of a dataset pointed to by the RKANPAR DD statement for the CMS address space contains an invalid value for the SMFDINTV parameter.System Action: SMF recording is disabled within the CMS.User Response: None. This message is informational.To enable SMF recording within the CMS, specify a valid recording interval for the SMFDINTV parameter and a valid SMF user record number for the SMFRECN parameter. The SMFDINTV parameter accepts the following values:

Specify a user record number from 128–255 for the SMFRECN parameter. Restart the CMS address space.Destination: The CT/Engine log, RKLVLOG.

KDFD004W KDFDEVIN: INVALID SMF RECORD ID SMF DEVICE RECORDING DISABLEDExplanation: The KDFDEVIN member of a dataset pointed to by the RKANPAR DD statement for the CMS address space contains an invalid SMF user record number on the SMFRECN parameter.System Action: SMF recording is disabled within the CMS.User Response: None. This message is informational. To enable SMF recording within the CMS, make sure that a valid SMF user record number (128–255) has been specified on the SMFRECN parameter. Then, restart the CMS address space.Destination: The CT/Engine log, RKLVLOG.

KDFD005E KDFDEVIN: APF AUTHORIZATION REQUIRED FOR DATA COLLECTExplanation: All load libraries specified in the STEPLIB DD statement of the CMS address space are not APF authorized.System Action: The initialization of the CMS terminates.User Response: Make sure that all the CMS load libraries are APF-authorized prior to restarting the CMS address space.Destination: The CT/Engine log, RKLVLOG.

KDFD006I KDFDRMFL RETURNING: rmf_levelExplanation: The internal representation (in hexadecimal characters) of the RMF level currently executing on the MVS system under which the CMS is running was displayed.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

RMFSYNC Synchronizes with the RMF interval.

SMFSYNC Synchronizes with the SMF interval.

1-1439 Specifies the recording interval in minutes.


KDFD007I KDFDSMF: SMF DEVICE RECORDING STARTEDExplanation: SMF DASD interval recording was started within the Candle Management Server address space.System Action: None.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.

KDFD008I KDFDSMF: SMF DEVICE RECORDING COMPLETEDExplanation: SMF DASD interval recording was completed in the Candle Management Server address space.System Action: None.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.

KDFD009I KDFDSMF: RMF INTERVAL= n HSECS ELAPSED= n HSECS REMAINING= n HSECSExplanation: SMF DASD interval recording is being synchronized with RMF interval recording within the Candle Management Server. The RMF interval length, elapsed time within the current RMF interval, and time remaining within the current interval are displayed in hundredths of a second (HSECS).System Action: None.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.

KDFD010I KDFDSMF: SMF RECORDING INTERVAL FOR STC SUB-SYSTEM= n HSECSExplanation: SMF DASD interval recording was being done at the same interval as the STC subsystem under SMF. The STC subsystem recording interval within SMF is displayed in hundredths of a second (HSECS).System Action: None.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.

KDFD011I KDFDSMF: RECORDING INTERVAL DEFAULTING TO 15 MINUTESExplanation: SMF DASD interval recording is being done every 15 minutes within the Candle Management Server address space.System Action: None.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.


KDFD012E KDFDEVIN: ALLOCATION FAILED FOR work_area SIZE=bytesExplanation: Data collection initialization failed during allocation of the required work area name indicated in the message. The size (in bytes) required for the work area is also displayed.System Action: The initialization of CMS terminates.User Response: Change the LIMIT parameter depending on the number of devices defined to your system. The LIMIT value is expressed as a power of 2, thus LIMIT (22,x) specifies 4 meg, LIMIT (23,x) specifies 8 meg, and so on. Each device table entry is 320 bytes, so LIMIT (23,x) allows allocation of a device table large enough to accommodate about 26,000 devices. LIMIT (24,x) will accommodate twice that many. If the error still occurs, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD013E KDFDEVIN: LOAD FAILED FOR KDFDccccExplanation: Data collection initialization failed while attempting to load the module indicated.System Action: The initialization of the CMS terminates.User Response: Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD014E KDFDEVIN: NODATA PARM - DATA COLLECTION BYPASSEDExplanation: Member KDFDEVIN of the dataset pointed to by the RKANPAR DD statement for the CMS address space was empty or not present.System Action: Data collection for OMEGAMON II is suppressed, but CMS initialization continues.User Response: Verify that the KDFDEVIN member exists or is not empty. See the OMEGAMON II for SMS Program Directory for information about creating a valid KDFDEVIN member. Then, restart the CMS address space with the corrected KDFDEVIN member of the dataset pointed to by the RKANPAR DD statement.Destination: The CT/Engine log, RKLVLOG.

KDFD015I KDFDSCIN INPUT PARMS: parametersExplanation: The input parameters for dataset collection specified in the KDFDSCIN member of the RKANPAR DD statement for the Candle Management Server address space are displayed.System Action: None.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.


KDFD016W KDFDSCIN: PARM ERRORS DETECTED; DEVICES WILL BE SKIPPEDExplanation: At least one hex device number is invalid in the input parameters for dataset collection specified in the KDFDSCIN member of the dataset pointed to by the RKANPAR DD statement for the Candle Management Server address space.System Action: The device or device range with the invalid number will be ignored and dataset collection will not occur for the devices.User Response: Correct the device (DEVICES) or device range (DEVRANGE) parameter(s) in the KDFDSCIN member, then restart the Candle Management Server address space.Destination: The CT/Engine log, RKLVLOG.

KDFD017I KDFDSCIN: DATASET COLLECTOR INITIALIZED; RC= return_codeExplanation: The dataset collector has been successfully initialized; the initialization return code is displayed. Valid return codes are zero (0) and 4.User Response: None.This is an informational message only.Destination: The CT/Engine log, RKLVLOG.

KDFD018I KDFDSCIN: DEVICES STARTED FOR COLLECTION; container SUCCESSFUL COUNT=nnn; FAILURE COUNT=nnnExplanation: The dataset collector has started collecting for devices as specified in the KDFDSCIN parameter member of the dataset pointed to by the RKANPAR DD statement. The number of devices for which collection was successfully started is given, as well as the number for which it failed.System Action: None.User Response: If the failure count is not zero (0), make sure that all devices specified on the VOLSERS, DEVICES, and DEVRANGE parameters in the KDFDSCIN member are valid devices for the system on which the CMS is active. If changes are made, restart the CMS address space.Destination: The CT/Engine log, RKLVLOG.

KDFD019W KDFDSCIN: NO DEVICES SPECIFIED FOR COLLECTIONExplanation: No devices were specified in the KDFDSCIN parameter member of the dataset pointed to by the RKANPAR DD statement for dataset collection.System Action: No devices are specified for dataset collection.User Response: If dataset collection is desired, specify devices via the VOLSERS, DEVICES, and DEVRANGE parameters in the KDFDSCIN member. Then restart the Candle Management Server address space.Destination: The CT/Engine log, RKLVLOG.


KDFD020E KDFDSCIN: CANDLE SUBSYSTEM INITIALIZATION FAILED; RC= return_codeExplanation: The Candle Management Server initialization call to the Candle Subsystem required for dataset collection failed with the return code displayed.System Action: Dataset collection does not occur.User Response: Make sure that the Candle Subsystem module KCNDLI is available to the Candle Management Server address space, then restart the Candle Management Server. Otherwise, record the return code and contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD021E KDFDSCIN: DATASET COLLECTOR INITIALIZATION FAILED; SSRQ RC= return_code INIT RC= return_codeExplanation: The Candle Management Server initialization call to the dataset collector failed with the given return codes.System Action: Dataset collection will not occur.User Response: Make sure that the Candle subsystem address space has been started. Since a retry to initialize will automatically be attempted when dataset collector data is requested, a restart of the Candle Management Server address space should not be necessary. Otherwise, record the two return codes and contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD022E KDFDSCIN: DATASET COLLECTOR DEVICE FAILED; SSRQ RC= return_code RC= return_codeExplanation: Dataset collection was not successfully started for any devices specified in the KDFDSCIN member of the dataset pointed to by the RKANPAR DD statement. The return codes are displayed.System Action: Dataset collection does not occur.User Response: Make sure that the devices specified on the VOLSERS, DEVICES, and DEVRANGE parameters in the KDFDSCIN member are valid devices for the system on which the Candle Management Server is active, then restart the Candle Management Server address space. Otherwise, record the two return codes and contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD023E KDFDSCIN: ALLOCATION FAILED FOR START LISTS; SIZE= bytesExplanation: Dataset collection initialization failed during allocation of the required area for device lists. The number of bytes required for the area is given in the message.System Action: Dataset collection does not occur.User Response: Attempt to restart the Candle Management Server address space with a larger region size. If the error still occurs, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.


KDFD024W KDFDSCIN: DATASET COLLECTION PREVIOUSLY DISABLED; RETRY NOT ATTEMPTEDExplanation: Due to an incoming request to the Candle Management Server for data, dataset collector initialization has been retried after an unsuccessful attempt during the Candle Management Server initialization. However, a prior attempt to initialize dataset collection encountered a problem which caused dataset collection to be completely disabled.System Action: Dataset collection does not occur.User Response: Find previous messages in the RKLVLOG from the KDFDSCIN module which will help identify the original reason for dataset collection being disabled and follow advice for the messages.Destination: The CT/Engine log, RKLVLOG.

KDFD025I KDFDSCIN: DATASET COLLECTION DISABLED; NO KDFDSCIN PARM MEMBERExplanation: Dataset collection has been disabled because the KDFDSCIN parameter member of the dataset pointed to by the RKANPAR DD statement was not found. The lack of the KDFDSCIN member is the normal way to disabling dataset collection.System Action: Dataset collection does not occur.User Response: This is an informational message only. If dataset collection is desired, specify devices via the VOLSERS, DEVICES, and DEVRANGE parameters in the KDFDSCIN member, then restart the Candle Management Server address space.Destination: The CT/Engine log, RKLVLOG.

KDFD026E KDFDSCIN: PARM MEMBER NOT FOUND IN PDS IN SECOND PASS; RC= return_codeExplanation: Dataset collection initialization failed during the second pass of parsing the KDFDSCIN member of the dataset pointed to by the RKANPAR DD statement. The member is no longer available, even though it was available during the first pass of parsing.System Action: Dataset collection does not occur.User Response: Correct the problem with the KDFDSCIN member, then restart the Candle Management Server address space. If the error still occurs, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD027I KDFDTERM: DATASET COLLECTION STOPPED; container SUCCESSFUL COUNT=nnn; FAILURE COUNT=nnnExplanation: During termination of the CMS address space, the dataset collector has stopped collecting for devices. The number of devices for which collection was successfully stopped is given, as well as the number for which it failed. A failure to stop collecting for some devices may be normal because they were not started during the CMS initialization.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.


KDFD028I KDFDTERM: DATASET COLLECTOR TERM NOT DONE; container reasonExplanation: During termination of the CMS address space, the dataset collector did not require termination for the reason specified.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFD029E KDFDTERM: DATASET COLLECTOR STOP DEVICE FAILED; container SSRQ RC=return_code STOP RC=return_codeExplanation: During termination of the CMS address space, the dataset collector failed to stop collecting for devices specified in the KDFDSCIN member of the dataset pointed to by the RKANPAR DD statement.System Action: Dataset collection may continue for devices even though the CMS address space is not active.User Response: If you no longer want dataset collection for devices, and previous messages issued during the CMS initialization indicate that it was successfully started, stop the Candle Subsystem address space, when convenient. If the dataset collector is left operating, you may experience some overhead degradation.Destination: The CT/Engine log, RKLVLOG.

KDFD030I KDFDCISS: $CACHENV INITIALIZED SUCCESSFULLYExplanation: The cache collection environment has been successfully initialized.System Action: None.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFD031E KDFDCISS: ERROR IN $CACHENV INITIALIZE; container RC=return_code REASON=reason_codeExplanation: The cache collection environment failed to initialize for the return and reason codes displayed.System Action: DASD and control unit cache data collection does not occur.User Response: Record the return code and reason code and contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD032E KDFDCISS: LOAD ERROR DURING $CACHENV INITIALIZEExplanation: The cache collection environment failed due to an error during an attempt to load the module KCCCOLL.System Action: DASD and control unit cache data collection does not occur.User Response: Make sure that the module KCCCOLL is available to the CMS address space, then restart the CMS. Otherwise, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.


KDFD033W KDFDCISS: ERROR IN $CACHRTR INITIAL CUSCAN; RC=return_code REASON=reason_codeExplanation: An error occurred in initializing cache control unit information; the return and reason codes are displayed.System Action: Control unit cache data collection does not occur.User Response: If no cache controllers are installed on the system, this message is normal and informational only. If cache controllers are installed, record the return code and reason code and contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD034W KDFDCISS: ALLOCATION FAILED FOR W#CCUWRK; SIZE=bytesExplanation: Cache control unit collection initialization failed during the allocation of a required work area. The size required for the area is displayed.System Action: Control unit cache data collection does not occur.User Response: Attempt to restart the CMS address space with a larger region size. If the error still occurs, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD035W KDFDCISS: EXTRA SPACE FOR CONTROL UNITS USED; DATA LOST FOR: cache_control_unitExplanation: An attempt was made to add the cache control unit specified to the control unit work area after initialization and all extra space allocated for such additions was used. The CMS was not be able to keep and report data about the specified control unit. The control unit is specified by the SSID (ssidFF00) or the SDID (FFFFcc00, where cc is the SDID).System Action: None.User Response: Although not immediately required, restart the CMS address space to remedy the situation.Destination: The CT/Engine log, RKLVLOG.

KDFD036W KDFDCISS: ERROR IN $CACHRTR UPDATE CUSCAN; RC=return_code REASON=reason_codeExplanation: An error occurred in retrieving cache control unit information for the return and reason codes displayed. All cache control unit status information may not be current.System Action: None.User Response: Record the return and reason codes and contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.


KDFD037W KDFDCISS: CU NOT FOUND IN W#CCUWRK DURING DEVICE ACCUMULATION PHASE: cache_control_unitExplanation: The specified cache control unit associated with a DASD device was not represented in the control unit work area. The control unit is specified by the SSID (ssidFF00) or the SDID (FFFFcc00, where cc is the SDID).System Action: Data pertaining to this DASD device is not included in cache control unit information.User Response: One occurrence of this message does not indicate a problem. If the message persists, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD038W KDFDCISS: CU UPDATED IN DEVICE ACCUM PHASE BUT NOT DURING CUSCAN PHASE: cache_contro_unitExplanation: The specified cache control unit associated with a DASD device has not had its data updated during the current collection interval. The control unit is specified by the SSID (ssidFF00) or the SDID (FFFFcc00, where cc is the SDID).System Action: All data will still be there; however, the control unit status information may not be current. None.User Response: One occurrence of this messages does not indicate a problem. If the message persists, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD039W KDFDCISS: ERROR IN $CACHRTR DEVICE ACCUM. SCAN; RC=return_code REASON=reason_codeExplanation: An error occurred in retrieving DASD cache information, which was to be accumulated at the cache control unit level. The return and reason codes are given in the message. All cache control unit statistics may not be current.System Action: None.User Response: One occurrence of this message does not indicate a problem. If the message persists, record the return and reason codes and contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD040W KDFDCISS: $CACHTAB FUNCTION=REFRESH (n) FAILED; RC=return_code REASON=reason_codeExplanation: An error occurred while refreshing current cache information; the return and reason codes are displayed. Cache information may not be as current as specified in the CACHINTV parameter in member KDFDEVIN.System Action: None.User Response: One occurrence of this message does not indicate a problem. If the message persists, record the return and reason codes and contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.


KDFD041W KDFDCISS: $CACHTAB FUNCTION=RESET FAILED; RC=return_code REASON=reason_codeExplanation: An error occurred while resetting cache base statistics; the return and reason codes are given in the message. Cache information will cover a longer period than specified in the CACHINTV parameter in the KDFDEVIN member.System Action: None.User Response: Record the return and reason codes and contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD042W COLLECTION INTERVAL TABLE INQUIRY FAILED - reasonExplanation: The probe that collects data collection interval information failed because of the reason appended to the end of the message.System Action: Processing continues. A default collection interval will be adopted.User Response: None.Destination: The CT/Engine log, RKLVLOG

KDFD043W COLLECTION INTERVAL TABLE UPDATE REJECTED - UPDATE IN PROGRESSExplanation: An attempt to update data collection interval information failed due to contention.System Action: The update is rejected.User Response: Retry the request. If the problem persists contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD044W COLLECTION INTERVAL TABLE UPDATE FAILED - $DEVWRK NOT FOUNDExplanation: An attempt to update data collection interval information failed because an internal control block could not be found.System Action: The update is rejected.User Response: Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD045I COLLECTION INTERVAL TABLE UPDATE SUCCESSFULExplanation: An update of the data collection interval information successfully completed.System Action: Normal processing continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.


KDFD047W DEVICE COLLECTION TABLE UPDATE FAILED - xxxxxxxxxxExplanation: An attempt to update the device collection table failed. The reason for the failure is stated in the message. Possible reasons are® KDFX REQUEST FAILED

® STORAGE UNAVAILABLE

® MONITOR RESET FAILED

This message may be preceded by an additional KDFD047W message containing diagnostic information in the format:

KDFXcccc REQUEST ERROR - CN RC=9999 KDFX RC=9999

System Action: OMEGAMON II continues monitoring using the existing device collection table.User Response: Try the update again. If the problem persists, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD048I DEVICE COLLECTION TABLE UPDATE SUCCESSFULExplanation: An attempt to update the device collection table completed successfully.System Action: OMEGAMON II continues monitoring using the updated device collection table.User Response: This is an informational message only.Destination: The CT/Engine log, RKLVLOG.

KDFD049W DEVICE COLLECTION TABLE ADD FAILED - xxxxxxxxxxExplanation: An attempt to add a device to the collection table failed. The reason for the failure is stated in the message. Possible reasons are® KDFX REQUEST FAILED

® MEMORY NOT AVAILABLE

® MONITOR RESET FAILED

® DUPLICATE ENTRY

This message may be preceded by an additional KDFD049W message containing diagnostic information in the format:

KDFXcccc REQUEST ERROR - CN RC=9999 KDFX RC=9999

System Action: OMEGAMON II continues monitoring using the existing device collection table.User Response: Try the update again. If the problem persists, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.


KDFD055W parameter KEYWORD SYNTAX INVALIDExplanation: An error was detected during the parsing of the KDFDEVSU member of the RKANPAR dataset.System Action: The DASD exclusion list will be incomplete.User Response: Correct the erroneous keyword syntax.Destination: The CT/Engine log, RKLVLOG.

KDFD056W STORAGE SHORTAGE PROCESSING parameter KEYWORDExplanation: A getmain failure occurred while processing the listed parameter of the KDFDEVSU member of the RKANPAR dataset.System Action: The DASD exclusion list will be incomplete.User Response: Review the region size of the CT/Engine address space.Destination: The CT/Engine log, RKLVLOG.

KDFD058W parameter KEYWORD INVALID DEVICE ADDRESS SPECIFIEDExplanation: A syntax error was discovered while processing the KDFDEVSU member of the RKANPAR dataset. The range of addresses in the listed parameter was invalid.System Action: The DASD exclusion list will be incomplete.User Response: Correct the erroneous syntax.Destination: The CT/Engine log, RKLVLOG.

KDFD060W parameter KEYWORD DUPLICATE ENTRY SPECIFIEDExplanation: A duplicate specification occurred while processing the KDFDEVSU member of the RKANPAR dataset.System Action: The DASD exclusion list will be incomplete.User Response: Correct the erroneous duplicate syntax.Destination: The CT/Engine log, RKLVLOG.

KDFD061W KDFDEVIN: RMF API INITIALIZATION FAILURE, RC=nnExplanation: An attempt to initialize the RMF API failed with a return code of nn.System Action: The RMF API will not be used to retrieve performance data.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFD063W parameter KEYWORD VALUE INVALIDExplanation: A syntax error was discovered while processing the KDFDEVSU member of the RKANPAR dataset.System Action: The DASD exclusion list will be incomplete.User Response: Correct the erroneous syntax.Destination: The CT/Engine log, RKLVLOG.


KDFD069E KDFD069E KDFDPDEV: SETUP FAILED FOR DASD TABLE INSERTS; RC=99Explanation: The setup request issued prior to inserting historical application information into the Persistent Data Store failed with return code ’99’.System Action: Historical information collection is bypassed for the current interval. Collection will be retried next interval.User Response: Verify the PDS was allocated and initialized without error. If the problem persists, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD070E KDFD070E KDFDPDEV: INSERT FAILED FOR DASD TABLE INSERT; RC=99 -- RECORDING TERMINATING FOR THIS INTERVALExplanation: A request to add historical DASD information to the Persistent Data Store failed with return code ’99’.System Action: Historical DASD information collection is terminated. Collection will be retried during the next collection interval.User Response: Verify the PDS was allocated and initialized without error. Check the CMS address space logs CTPDSOUT and CTPDSLOG for relevant messages. If the problem persists, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD071E KDFDPDEV: DASD PDS RECORDING DISABLED - $DEVWRK ADDRESS ZERO ON ENTRYExplanation: The recording of DASD information to the PDS will be disabled as an internal control block can not be found.System Action: Normal processing continues, but historical dasd information will be unavailable.User Response: Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD072W KDFDPDEV: DASD PDS RECORDING SKIPPED THIS INTERVAL - NO ENTRIES FOUND IN DEVICE TABLEExplanation: No DASD are currently being monitored and no historical information will be recorded for this interval.System Action: Normal processing continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFD073W KDFDPDEV: CACHE STATISTICS NOT RECORDED THIS INTERVAL - V#CISTOK IS ZEROExplanation: No cache statistics can be recorded.System Action: Normal processing continues, but no historical cache information will be available for this interval.User Response: None.Destination: The CT/Engine log, RKLVLOG.


KDFD074W KDFDPDEV: $CACHRTR ERROR; VOLSER=volser RC=nn REASON=xxExplanation: An error occurred attempting to retrieve cache statistics.System Action: Normal processing continues, but no historical cache information will be available for this interval.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFD075E KDFD075E KDFDTPIN: INPUT DATA NOT AVAILABLE - TAPE COLLECTION BYPASSEDExplanation: Module KDFDTPIN was unable to read member KDFDTPIN of the rhilev.TKDFPRMD dataset.System Action: Tape information will not be available. The collection of tape data will be disabled.User Response: If the KDFDTPIN member of the rhilev.TKDFPRMD dataset does not exist, define it using the CICAT™ configuration panels. If the member does exist, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD076I KDFD076I KDFDTPIN: INTERVAL OF OFF SPECIFIED - TAPE COLLECTION DISABLEDExplanation: The INTERVAL value in the KDFDTPIN member of the rhilev.TKDFPRMD dataset was specified as OFF.System Action: Tape information will not be available. The collection of tape data will be disabled.User Response: None, if no tape data is desired. If tape data is desired, define a collection interval using the CICAT configuration panels.Destination: The CT/Engine log, RKLVLOG.

KDFD077I KDFD076I KDFDTPIN: INTERVAL OF 0 SPECIFIED - TAPE COLLECTION DISABLEDExplanation: The INTERVAL value in the KDFDTPIN member of the rhilev.TKDFPRMD dataset was specified as 0.System Action: Tape information will not be available. The collection of tape data will be disabled.User Response: None, if no tape data is desired. If tape data is desired, define a nonzero collection interval using the CICAT configuration panels.Destination: The CT/Engine log, RKLVLOG.


KDFD080I KDFDPDSN reqid REQUEST ERROR RC= rcExplanation: DF request indicated by reqid could not be completed for KDFDPDSN. The error return code rc indicates the type of problem.System Action: A system request could not be completed.User Response: Most causes of this message are transient in nature, and do not indicate a problem. If the message persists, contact Candle Support Services. Possible return codes include:


KDFD081E KDFD081E KDFDTAPE: INVALID WORK AREAExplanation: The tape collection work area did not pass validation.System Action: The collection of tape data is disabled.User Response: Obtain a dump of the data collector address space and the RKLVLOG for the data collection address space. Then contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD082W KDFD082W KDFDTAPE: CATALOG READ ERROR, RC = xx - yySystem Action: An attempt to extract data from the tape catalog failed with return code xx and reason code yy. The collection of tape data continues. However, data for installed tape libraries will not be available.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD083E KDFD083E KDFDTAPE: CANDLE SUBSYSTEM FUNCTION DIOPUCBA: RC = xx - yyExplanation: An attempt to access the Candle Subsystem failed with return code xx and reason code yy.System Action: The collection of tape data is disabled. Tape data will not be available.User Response: Verify that the Candle Subsystem was installed with the proper level of maintenance, and has been started. Gather the RKLVLOG for the data collection address space, and contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

x’fe’ Indicates the PDS control blocks have not yet initialized. Retry, if the problem persists contact Candle Support Services.

x’ff’ Indicates that the PDS did not initialize successfully and the control blocks do not exist. Re-initialize the PDS datasets. The CTPDSOUT and CTPDSLOG JES datasets may have some information concerning the problem. If this fails, contact Candle Support Services.


KDFD084E KDFD084E KDFDTAPE: STORAGE UNAVAILABLE, LENGTH = xxxxxxxxExplanation: An attempt to obtain xxxxxxxx bytes of storage failed.System Action: The collection of tape data is disabled. Tape data will not be available.User Response: Keep the RKLVLOG for the data collection address space and contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD085E KDFD085E KDFDTAPE: LOAD FAILED FOR IEFEB4UVExplanation: IBM load module IEFEB4UV was not available to be loaded.System Action: The collection of tape data is disabled. Tape data will not be available.User Response: Load module IEFEB4UV should be in either SYS1.LINKLIB or SYS1.LPALIB. Contact your system programmer to determine the location of this IBM module. If it is located in either a linklisted dataset or a dataset in the LPALIB concatenation, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD086E KDFLDEV: REQUEST FOR HISTORICAL DATA FAILED - ERROR LOCATING DFPDSWKAExplanation: An attempt to retrieve historical device data failed because an internal control block could not be found.System Action: No data will be returned.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD089I KDFLDEV: HISTORICAL DATA FETCHED IS PAST RANGE; DATE REQUESTED = mm/dd/yy, TIME REQUESTED = hhmmss, DATE RETURNED = mm/dd/yy, TIME RETURNED = hhmmssExplanation: No qualifying data can be found for the historical request.System Action: Normal processing continues, but no data will be returned.User Response: None.Message Type: The CT/Engine log, RKLVLOG.

KDFD093W KDFDPAPL: RMF SYNCHRONIZATION FAILED - RECORDING INTERVAL DEFAULTING TO 15 MINUTESExplanation: Either RMF is inactive or its recording interval is less than one minute.System Action: Application statistics will be collected at 15 minute intervals.User Response: None.Destination: The CT/Engine log, RKLVLOG.


KDFD094E KDFD094E KDFDPAPL: SETUP FAILED FOR APPL TABLE INSERTS; RC=99Explanation: The setup request issued prior to inserting historical application information into the Persistent Data Store failed with return code ’99’.System Action: Historical information collection is bypassed for the current interval. Collection will be retried next interval.User Response: Verify the PDS was allocated and initialized without error. If the problem persists, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD095E KDFDPAPL: INSERT FAILED FOR APPL TABLE INSERT; RC=rc -- RECORDING TERMINATING FOR THIS INTERVAL, R5=r5Explanation: An attempt to insert historical application data into the Persistent Data Store (PDS) failed with return code specified as rc. r5 contains the length of the record being inserted.System Action: This historical record is bypassed and processing continues.User Response: Verify that the PDS is large enough, and that it was allocated and initialized without error. If the problem persists, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD096E KDFDPAPL: APPL PDS RECORDING DISABLED - reasonExplanation: An attempt to initialize historical application data recording in the Persistent Data Store failed because of reason.System Action: Historical collection for application data is bypassed for the life of this CMS address space.User Response: Contact Candle Customer Support.

Possible values for reason include:$DEVWRK ADDRESS ZERO ON ENTRY

OM2SM VECTOR TABLE NOT FOUND

$APPLWRK WORK AREA NOT FOUND

DFPDSWKA WORK AREA NOT FOUND

INVALID DFPDSWKA DETECTED

LOAD FAILED FOR KDFDRMFI


KDFD101I parm KEYWORD INVALID - SET TO DEFAULTExplanation: The value specified for keyword parm in member KDFDSCIN of the RKANPAR dataset is invalid.System Action: The default value is taken for the keyword parameter and processing continues.User Response: Correct the value for the keyword and issue the DFREF command to refresh the KDFDSCIN parameters.Destination: The CT/Engine log, RKLVLOG.


KDFD102W MSR AND SAMPCT KEYWORDS MUTUALLU EXCLUSIVEExplanation: Keywords MSR and SAMPCT were both specified for the same volume in member KDFDSCIN of the RKANPAR dataset. These keywords are mutually exclusive.System Action: The volume in error is bypassed for dataset level monitoring. Normal processing continues.User Response: Correct the error in KDFDSCIN and issue the DFREF command to refresh the KDFDSCIN parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD103W parm KEYWORD - MSR KEYWORD REQUIRES MONITOR STATUS ONExplanation: ’OFF" and ’MSR=’ were specified together on keyword parm in member KDFDSCIN of the RKANPAR dataset. The specification of an MSR value requires monitoring status to be specified as (or allowed to default to) ’ON’.System Action: The volume in error is bypassed for dataset level monitoring. Normal processing continues.User Response: Correct the error in KDFDSCIN and issue the DFREF command to refresh the KDFDSCIN parameters.

Possible values for parm include:DEVICES

DEVRANGE

VOLSERS


KDFD104W KDFDEVSU PARM KEYWORD parameter INVALIDExplanation: A syntax error was discovered while parsing the contents of the KDFDEVSU member of the RKANPAR dataset.System Action: The DASD exclusion list will be incomplete.User Response: Correct the erroneous syntax.Destination: The CT/Engine log, RKLVLOG.

KDFD105W KDFDEVSU PARM ERRORS DETECTED; EXCLUDE LIST INCOMPLETEExplanation: Errors have been detected while parsing the contents of the KDFDEVSU member of the RKANPAR dataset. A preceding error message will detail the exact cause of the error.System Action: The DASD exclusion list will only consist of those specifications successfully parsed prior to discovery of the error.User Response: Correct the erroneous syntax.Destination: The CT/Engine log, RKLVLOG.

KDFD106I KDFDEVSU PARM MEMBER NOT FOUND; EXCLUDE LIST WAS NOT BUILTExplanation: There is no KDFDEVSU member in the RKANPAR dataset.System Action: Normal processing continues, all devices will be monitored.User Response: None.Destination: The CT/Engine log, RKLVLOG.


KDFD109E KDFDCHPS - RMF API NOT AVAILABLEExplanation: IBM module ERBSMFI was not found in an available library.System Action: Processing continues, but all data which is normally obtained through the RMF API will appear as zeros or "n/a" on the screen.User Response: Find the library containing the RMF interface module ERBSMFI and make sure it is available to the CMS started task. This may involve concatenating it as a STEPLIB. Be aware that your shop may be running a third-party RMF substitute such as CMF. In that case, the CMF LOADLIB should be concatenated to the STEPLOIB in your CMS startup proc.Destination: The CT/Engine log, RKLVLOG.

KDFD110E KDFDCHPS: RMF API FAILURE, RC= xxxxxxxxExplanation: An error code (xxxxxxxx) was returned by the IBM RMF interface.System Action: The collector terminates using the RMF API for the duration of this collection interval. However, a new attempt to use the interface will be made during the next and subsequent collection intervals.User Response: Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD111E module: RMF SMF RECORD, INVALID DCSExplanation: An SMF record was encountered which should have contained a data control section, but did not.System Action: The collector stops using the RMF API for the duration of this collection interval. However, a new attempt to use the interface will be made during the next and subsequent collection intervals. User Response: Contact Candle Customer Support.

Possible values for module include:KDFDCHPS

KDFLCHP


KDFD112E KDFDCHPS: RMF API RETURN ERROR, RC=xxxxxxxxExplanation: Attempting to execute the RETURN function of the RMF interface, an error (xxxxxxxx) was returned.System Action: The collector stops using the RMF API for the duration of this collection interval. However, a new attempt to use the interface will be made during the next and subsequent collection intervals.User Response: Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFD113W CPMF UNAVAILABLE - NO CHPID DATAExplanation: The channel path measurement facility is unavailable.System Action: No further attempt is made to gather channel path data for this collection interval.User Response: Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.


KDFD114W CPMF INACTIVE - NO CHPID DATAExplanation: The channel path measurement facility is unavailable.System Action: No further attempt is made to gather channel path data for this collection interval.User Response: Ensure that CPMF is enabled on your system.Destination: The CT/Engine log, RKLVLOG.

KDFD115I CPMF MODE CHANGE - NO CHPID DATAExplanation: The channel path measurement facility mode has changed between inactive, compatibility or extended mode.System Action: No further attempt is made to gather channel path data for this collection interval.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFD116I KDFDEVIN DFSMSHSM NOT INSTALLEDExplanation: IBM’s Hierarchical Storage Management (HSM) system is not installed on the system.System Action: No further attempt is made to gather HSM related data.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFD1171 KDFDUDGI INPUT PARMS: xxxxxxxxExplanation: The input parameters from the KDFDUDGI member of the rhilev RKANPAR dataset were written as xxxxxxxx.System Action: None. Processing continues.User Response: This message is output as a result of an error. There should be an error message in the CMS SYSOUT log. Follow the instructions for the error.Destination: The CMS address space log, RKLVLOG.

KDFD118E KDFDUDGI MULTIPLE NAME PARAMETERS IN GROUP DEFINITION - GROUP IGNOREDExplanation: The NAME keyword was specified twice in the definition for a single user DASD group.System Action: The definition of the user DASD group is ignored.User Response: This message should be accompanied by message KDFD117I. Remove the multiple NAME keywords from the definition of the user DASD group in the KDFDUDGI member of the rhilev.RKANPAR dataset.Destination: The CMS address space log, RKLVLOG.

KDFD119E KDFDUDGI UNABLE TO ALLOCATE SUMMARY VECTORExplanation: The summary vector build failed.System Action: Processing continues; however, the product will be degraded. There will not be any user DASD groups available, and various components of the product will not function properly.User Response: Contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.


KDFD120E KDFDUDGI GROUP NAME PREVIOUSLY DEFINED - DUPLICATE IGNOREDExplanation: A user DASD group with this name was previously defined.System Action: This definition for the user DASD group is ignored. The previously defined user DASD group is not affected.User Response: All user DASD group definitions must have unique names. This message should be accompanied by message KDFD117I. Rename the user DASD group as defined in the KDFDUDGI member of the RKANPAR dataset.Destination: The CMS address space log, RKLVLOG.

KDFD121W KDFDUDGI INPUT DATA NOT AVAILABLE - NO USER GROUPS DEFINEDExplanation: Member KDFDUDGI of the rhilev.RKANPAR dataset was not found.System Action: No user DASD groups will be defined.User Response: This message may be ignored if there was no intention to define user DASD groups and the KDFDUDGI member of the rhilev.RKANPAR dataset does not exist. Otherwise, contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.

KDFD122E KDFDUDGI - xxxxx: yyyyyExplanation: A syntax error has occurred xxxx is the error; yyyyy. is the input data that caused the error.System Action: The user DASD group definition containing the error is ignored. Processing continues with the next user DASD group definition.User Response: Correct the error and restart the CMS address space. The error is in the KDFDUDGI member of the rhilev.RKANPAR dataset.Destination: The CMS address space log, RKLVLOG.

KDFD123E KDFD123E KDFDUDGI - STORAGE ALLOCATION FAILURE; SIZE= xxxxxExplanation: Allocation of xxxx bytes of virtual storage failed.System Action: The user DASD group definition containing the error is ignored. Processing of KDFDUDGI parameters is terminated.User Response: Contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.

KDFD124E KDFDUDGI - GROUP NAME MUST BE DEFINED PRIOR TO OTHER ELEMENTSExplanation: The first parameter of a user DASD group definition was not the NAME keyword.System Action: The user DASD group definition containing the error is ignored. Processing continues with the next user DASD group definition.User Response: A user DASD group definition must begin with the keyword NAME. This message is accompanied by message KDFD117I. Correct the error and restart the CMS address space. The error is in the KDFDUDGI member of the rhilev.RKANPAR dataset.Destination: The CMS address space log, RKLVLOG.


KDFD125I KDFDUDGI - EMPTY INPUT MEMBER PROCESSEDExplanation: The KDFDUDGI member of the rhilev.RKANPAR dataset was empty.System Action: No user DASD groups are defined. Processing continues.User Response: If the KDFDUDGI member of the rhilev.RKANPAR dataset was intentionally left empty, then no action is necessary. If the intention was to define user DASD groups, use CICAT to try again. If the problem persists, contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.

KDFD126E KDFDUDGI - INVALID INTERNAL CHAIN, RC = xxExplanation: An internal control block chain was invalid xx indicates the chain with the problem.System Action: The processing of user DASD group definitions halts.User Response: Generate a running dump of the CMS address space and contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.

KDFD127E KDFDUDGI - VOLSER INPUT INVALIDSystem Action: The input from the VOLSER keyword had invalid syntax.The processing of the user DASD group definition with the problem halts. Other processing continues normally.User Response: Review the rules for the VOLSER keyword and correct the mistake. Then restart CMS.Destination: The CMS address space log, RKLVLOG.

KDFD128E KDFDUDGI - INVALID DEVICE ADDRESSExplanation: The input from the DEVICE keyword had invalid syntax.System Action: The processing of the user DASD group definition with the problem halts. Other processing continues normally.User Response: Review the rules for the DEVICE keyword and correct the mistake. Then restart the CMS.Destination: The CMS address space log, RKLVLOG.

KDFD129E KDFDUDGI - INVALID INTERNAL INDEXExplanation: An internal control block had an invalid value.System Action: The processing of the user DASD group definition with the problem halts. Other processing continues normally.User Response: Review the definition for the user DASD group with the problem. If there are no syntax errors, contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.


KDFD130E KDFDUDGI - TOO MANY xxxxx ENTRIESExplanation: The allowable number of entries of type xxxxx was exceeded xxxxx is one of the keyword parameters.System Action: The processing of the user DASD group definition with the problem halts. Other processing continues normally.User Response: Review the definition for the user DASD group with the problem. Reduce the number of entries for which the limit is exceeded.Destination: The CMS address space log, RKLVLOG.

KDFD131E KDFDUDGI - INVALID DEVICE RANGEExplanation: A value in the DEVRANGE keyword was invalid.System Action: The processing of the user DASD group definition with the problem halts. Other processing continues normally.User Response: Review the definition for the user DASD group with the problem. Correct the DEVRANGE parameter with the problem.Destination: The CMS address space log, RKLVLOG.

KDFD132E KDFDSUMM - STORAGE ALLOCATION FAILURE; SIZE= xxxxxExplanation: An attempt to allocate xxxx bytes of virtual storage failed.System Action: The processing of performance and space data for SMS and user DASD groups terminates.User Response: Contact Candle Support Services.Destination: The CMS address space log, RKLVLOG.

KDFD140E KDFDUDSI ALLOCATION FAILURE FOR DATASET GROUPS HEADERSystem Action: A GETMAIN request failed. Candle Management Server start-up continues. Dataset groups will not be active.User Response: Restart the Candle Management Server with a larger region size. If the error persists, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD141E KDFDUDSI - input parameter valuesExplanation: An unrecognized keyword was encountered during the parsing of the KDFDUDSI member of the RKANPAR dataset.System Action: Normal operation continues. The specified parameter value is ignored.User Response: Correct the specified parameter. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD142E KDFDUDSI ALLOCATION FAILURE FOR DATASET GROUPExplanation: A GETMAIN request failed.System Action: Candle Management Server start-up continues. User dataset groups will not be available.User Response: Restart the Candle Management Server with a larger region size. If the error persists, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.


KDFD143E KDFDUDSI - GROUP NAME MAY ONLY BE SPECIFIED ONCEExplanation: The GRPNAME keyword was specified more than once in a single dataset group definition.System Action: Normal operation continues. The specified group is discarded.User Response: Correct the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD144E KDFDUDSI - GROUP NAME MUST BE UNIQUEExplanation: The same name was defined to two different dataset groups.System Action: Normal operation continues. The duplicate definition is discarded.User Response: Correct the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD145E KDFDUDSI - INVALID FEATURE NAME SPECIFIEDExplanation: An invalid feature name was specified.System Action: Normal operation continues. The invalid definition is discarded.User Response: Specify only valid feature names in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD146E KDFDUDSI - FEATURE STATUS NOT CORRECTLY SPECIFIEDExplanation: A valid feature status was not specified.System Action: Normal operation continues. The incorrect definition is discarded.User Response: Ensure that feature names have an accompanying valid feature status in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD147E KDFDUDSI - INVALID FEATURE STATUS SPECIFIEDExplanation: An invalid feature status was specified.System Action: Normal operation continues. The invalid definition is discarded.User Response: Specify a valid feature status in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.


KDFD147E KDFDUDSI - INVALID FEATURE STATUS SPECIFIEDExplanation: An invalid feature status was specified.System Action: Normal operation continues. The invalid definition is discarded.User Response: Specify a valid feature status in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD148 KDFDUDSI - FEATURE MAY ONLY BE SPECIFIED ONCEExplanation: The FEATURE keyword was specified more than once in a single dataset group definition.System Action: Normal operation continues. The incorrect group is discarded.User Response: Correct the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD149E KDFDUDSI - MAXIMUM NUMBER OF DSNAMES EXCEEDEDExplanation: The limit of 100 dataset names per dataset group was exceeded.System Action: Normal operation continues. The incorrect group is discarded.User Response: Reduce the number of dataset names in the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD150E KDFDUDSI - INVALID DATASET MASK SPECIFIEDExplanation: When specifying a dataset mask, the wildcard character must appear after (not within) the first-level qualifier. For example, ’SYS1?’ is invalid while ’SYS1.?’ is valid. When updating RKANPAR(KDFDUDSI) directly, the wildcard character is question mark (?). When using CICAT to specify dataset groups, the wildcard character is asterisk (*).System Action: Normal operation continues. The invalid group is discarded.User Response: Correct the dataset mask in the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD151E KDFDUDSI - DATASET NAME TOO LONGExplanation: A dataset name greater than 44 bytes was specified.System Action: Normal operation continues. The invalid group is discarded.User Response: Correct the dataset name in the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.


KDFD152E KDFDUDSI - NO DATASETS SPECIFIEDExplanation: A dataset group was specified without dataset entries.System Action: Normal operation continues. The invalid group is discarded.User Response: Correct the dataset name length in the dataset group definition in the KDFDUDSI member of the RKANPAR dataset. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.

KDFD153E KDFDUDSI - SAVEAREA STACK EXHAUSTEDExplanation: An internal error occurred.System Action: Dataset groups will not be available.User Response: Report this error to Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFD154I KDFDUDSI GROUPS READ= mmmm, GROUPS ACCEPTED= nnnnExplanation: As a result of parsing the KDFDUDSI member of the RKANPAR dataset, mmmm dataset groups were input of which nnnn were accepted.System Action: Dataset groups will be available.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFD155I KDFDUDSI USER DATASET GROUPS SUCCESSFULLY INITIALIZEDExplanation: Dataset groups initialization completed successfully.System Action: Dataset groups will be available.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFD156I KDFDUDSI USER DATASET GROUP WORKAREA LOCATED AT xxxxxxxxExplanation: This is the hexadecimal address of the workarea for dataset groups.System Action: Dataset groups will be available.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFD157E KDFDUDSI USER DATASET GROUPS NOT INITIALIZEDExplanation: Dataset group initialization failed for the reasons stated in previous messages.System Action: Dataset groups will not be available.User Response: Examine the error messages immediately preceding this message for the cause of the failure. To ensure correct input, use CICAT to respecify parameters.Destination: The CT/Engine log, RKLVLOG.


KDFDBG01 The contents of this message varies depending on debugging conditions in effectExplanation: This message is generated when the product is executed in debugging mode. It should appear only when diagnosing a problem with Candle Support Services.System Action: The message is written to the CT/Engine log dataset.User Response: Follow instructions from Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFDHSML INVALID REQUEST CODE - LOG ANALYSIS TERMINATEDExplanation: An invalid request was made of the HSM log analysis controller.System Action: HSM Log analysis will terminate.User Response: This error should not occur, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFDHSML LOGY ALLOCATION FAILED, DSN= dsname, RC= xxxExplanation: An attempt at allocating the HSM log dataset has failed with the specified return and reason code.System Action: The request will be attempted up to twice, as necessary. If the third attempt fails, HSM log analysis will terminate.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFDHSML LOGY CLOSE FAILED, DSN= dsname, RC= xxx REASON= yyyExplanation: An attempt at closing the HSM log dataset has failed with the specified return and reason code.System Action: Normal operation will continue.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFDHSML LOGY GET FAILED, DSN= dsname, RC= xxx REASON= yyyExplanation: An attempt at reading the HSM log dataset has failed with the specified return and reason code.System Action: The request will be attempted up to twice, as necessary. If the third attempt fails, HSM log analysis will terminate.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.


KDFDHSML LOGY OPEN FAILED, DSN= dsname, RC= xxx REASON= yyyExplanation: An attempt at opening the HSM log dataset has failed with the specified return and reason code.System Action: The request will be attempted up to twice, as necessary. If the third attempt fails, HSM log analysis will terminate.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFDHSML SERVICE TASK ATTACH FAILED nnn - LOG ANALYSIS TERMINATEDExplanation: An MVS ATTACH macro has failed with the specified return code.System Action: HSM Log analysis will terminate.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFDHSML STOP REQUEST nnn - LOG ANALYSIS TERMINATEDExplanation: Termination of HSM log analysis has completed with code ’nnn’.System Action: None.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFDSCTE DATASET COLLECTOR TERM NOT DONE, NOT PREVIOUSLY INITIALIZEDExplanation: An error occurred during the initialization of the dataset collector.System Action: None.User Response: Review the RKLVLOG log for previous error messages.Destination: The CT/Engine log, RKLVLOG.

KDFDSCTE DATASET COLLECTOR STOPPED. SUCCESSFUL COUNT= count FAILURE COUNT=failuresExplanation: The dataset collector ran successfully.System Action: None.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFHS017 KDFDHSIN LOGY INVALID MEMBER NAME/GDG VERSION LENGTHExplanation: An error was detected in the specification of the HSM LOGY dataset. The length of the PDS member name or GDG version is either zero bytes or greater than eight bytes.System Action: HSM log analysis does not initialize.User Response: Check the specification in member KDFDHSIN of the RKANPAR dataset.Destination: The CT/Engine log, RKLVLOG.


KDFL097E KDFLAPPL: REQUEST FOR HISTORICAL DATA FAILED - reasonExplanation: An attempt to retrieve historical application data from the Persistent Data Store failed due to reason.System Action: Volume and dataset information for this application will not be returned to the requesting panel.User Response: Contact Candle Customer Support.

Possible values for reason include:ERROR LOCATING DFPDSWKA

INVALID DFPDSWKA DETECTED

NO JOBNAME INDEX SPECIFIED

SETUP ERROR; RC=rc


KDFL098E KDFLAPPL: FETCH FAILED FOR APPL TABLE; TC=rc -- DATA RETRIEVAL FROM PDS TERMINATINGExplanation: In retrieving historical application data from the Persistent Data Store, the PDS fetch routine returned with a non-zero return code indicated in rc.System Action: Volume and dataset information for this application will not be returned to the requesting panel.User Response: Contact Candle Customer Support.

Possible values for reason include:


KDFL100I KDFLAPPL: HISTORICAL DATA FETCHED IS PAST RANGE;DATE REQUESTED = mm/dd/yy, TIME REQUESTED = hhmdd,DATE RETURNED = mm/dd/yy, TIME RETURNED = hhmmssExplanation: No qualifying data can be found for the historical request.System Action: Normal processing continues, but no data will be returned.User Response: None. Destination: The CT/Engine log, RKLVLOG.

KDFLAU01 INITIALIZATION OF FORM TABLE IN PROGRESSExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that initial loading of the form authorization table is in progress.System Action: Table initialization continues.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

x’ff’ Invalid DFPDSTBL address passed. Contact Candle Customer Support.

x’fe’ DFPDSWKA not found. Contact Candle Customer Support.

x’fd’ Error obtaining the PDS vector table. Contact Candle Customer Support.


KDFLAU02 INITIALIZATION OF FORM TABLE IS COMPLETEExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that initialization of the form authorization table has completed successfully.System Action: The table is initialized.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFLAU03 LOADING OF FORM TABLE IN PROGRESSExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that the form authorization table is being loaded into virtual storage.System Action: The table loads into virtual storage.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFLAU04 LOADING OF FORM TABLE IS COMPLETEExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that loading of the form authorization table has completed successfully.System Action: The table is loaded.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFLAU05 INITIALIZATION OF USER TABLE IN PROGRESSExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that the user authorization table is being initialized.System Action: Table initialization continues.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFLAU06 INITIALIZATION OF USER TABLE IS COMPLETEExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that initialization of the user authorization table has completed successfully.System Action: The user authorization table is initialized.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFLAU07 LOADING OF USER TABLE IN PROGRESSExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that loading of the user authorization table is in progress.System Action: The table loads into virtual storage.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.


KDFLAU08 LOADING OF USER TABLE IS COMPLETEExplanation: This message is written to the CT/Engine log dataset during product initialization, and indicates that loading of the user authorization table has completed successfully.System Action: The user authorization table is loaded.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFS000I REQUESTED MESSAGE messsage_id IS NOT DEFINEDExplanation: An attempt was made to issue the message number displayed; however, that message has not been defined to the message interface.System Action: Processing will continue as if the message had been issued.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFS001I DATASET I/O COLLECTION VERSION version_number INITIALIZATION COMPLETEExplanation: The dataset I/O collector version_number has successfully initialized and is ready to monitor devices.System Action: Processing will continue.User Response: None. This message is informational.Destination: The MVS system console.

KDFS002W DATASET I/O COLLECTION VERSION version_number INITIALIZATION UNSUCCESSFUL.Explanation: An attempt to initialize the dataset I/O collector version_number was not successful.System Action: The dataset I/O collector terminates. Dataset I/O data is not available.User Response: There should be a message issued prior to this. Follow the instructions for the previous message.Destination: The MVS system console.

KDFS0028I CANDLE DATASET I/O COLLECTOR RESOURCE MANAGER CLEANUP IN PROGRESSExplanation: The collector has terminated abnormally, and the resource manager routine has been invoked to clean up the environment.System Action: None.User Response: None. This message is informational. There should be other messages issued previously that require action. If there are no previous messages, contact Candle Customer Support.

KDFS003A SVC DUMP TAKEN FOR CANDLE DATASET I/O COLLECTIONExplanation: The dataset I/O collector has abended and an SVC dump has been taken.System Action: The dataset I/O collector will attempt an orderly termination upon completion of the dump.User Response: Contact Candle Customer Support. Do not delete the dump.Destination: The MVS system console.


KDFS004I CANDLE DATASET I/O SUBFUNCTION function_id RC = return_codeExplanation: An attempt to start the subfunction displayed was unsuccessful, and displayed the return code indicated in the message.System Action: Initialization continues; however, some functionality will be lost.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFS005W CANDLE DATASET I/O REQUIRES MVS SUPPORT FOR SCOPE=COMMON DATA SPACESExplanation: The dataset I/O collector must be run on a level of MVS/ESA that provides support for SCOPE=COMMON data spaces.System Action: Initialization is terminated.User Response: Do not attempt to run the dataset I/O collector on a level of MVS that does not meet the minimum requirement.Destination: The MVS system console.

KDFS006W ONLY ONE CANDLE DATASET I/O COLLECTOR MAY RUN ON THE SYSTEM AT A TIMEExplanation: The dataset I/O collector has detected another Candle dataset I/O collector to be active on the system.System Action: Initialization of this collector is terminated.User Response: Do not attempt to start a second collector. Make sure that only one dataset I/O collector (Candle Subsystem) is installed.

KDFS007W CANDLE DATASET I/O module UNABLE TO INSTALL I/O CONFIG EXIT, RC=return_codeExplanation: The dataset I/O collector module specified attempted to install an I/O configuration exit. The attempt failed with the return code displayed.System Action: Initialization of the collector terminates.User Response: See the IBM manual, MVS/ESA Planning: Dynamic I/O Configuration for an explanation of the displayed return code. If the return code as documented for the CONFCHG service indicates a product problem, contact Candle Customer Support. Otherwise, correct the problem with the system.

KDFS008A CANDLE DATASET I/O UNABLE TO OBTAIN PRIVATE STORAGEExplanation: An attempt to obtain private virtual storage failed.System Action: The collector terminates.User Response: Remove any constraints upon the region available. Since almost all storage usage is above the 16-megabyte line, this problem is likely the result of an artificial constraint on storage availability.Destination: The MVS system console.


KDFS009A CANDLE DATASET I/O module UNABLE TO VALIDATE CONTROL BLOCK control_blockExplanation: An attempt to validate the MVS control block specified from within the module failed.System Action: Depending upon the control block involved, either the collector will terminate or continue processing, bypassing the use of the control block specified in the message.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFS010A CANDLE DATASET I/O module OBTAIN FOR bytes OF storage_type RC=return_codeExplanation: An attempt by the module specified to obtain the indicated amount of storage_type virtual storage failed with the return code displayed.System Action: The collector terminates.User Response: Make sure that the installation has not artificially constrained the availability of the type of virtual storage in question, either private or common. If storage is not artificially constrained, contact Candle Customer Support.Destination: The MVS system console.

KDFS011A CANDLE DATASET I/O module UNABLE TO FIX number PAGES OF STORAGE, RC=return_codeExplanation: An attempt by the module specified to fix number of pages of virtual storage failed with a the return code displayed.System Action: The collector terminates.User Response: If this is not a result of an installation problem, contact Candle Customer Support.Destination: The MVS system console.

KDFS012A CANDLE DATASET I/O module INTERNAL VALIDATION ERROR numberExplanation: Routine module has determined that the product has not been installed correctly. The number indicates the source of the problem.System Action: The collector will not initialize.User Response: Check the linkage editor message for module from the APPLY of the product or maintenance for error messages. If the return code is zero (0), contact Candle Customer Support.Destination: The MVS system console.

KDFS013I CANDLE DATASET I/O VER version_number TERMINATINGExplanation: The collector is terminating.System Action: The collector terminates. I/O statistics will not be collected.User Response: If this is a result of a stop command, then no action is necessary. Otherwise, gather documentation, including any previous messages, and contact Candle Customer Support, if necessary.Destination: The MVS system console.


KDFS014A CANDLE DATASET I/O module SERVICE REQUEST request FAILURE, RC= return_codeExplanation: The module specified requested a service of either MVS or the Candle Subsystem, and the request failed with the return code displayed.System Action: The collector will terminate if the request is critical.User Response: If the failure was for an MVS service, ensure that it was not the result of an installation problem. If necessary, contact Candle Support Services.Destination: The MVS system console.

KDFS015A CANDLE DATASET I/O module DEVICE TABLE FULLExplanation: The module specified attempted to add a device type to an internal table, but the table had no free entries.System Action: The collector continues; however, data will not be collected for all devices.User Response: Contact Candle Support Services.Destination: The MVS system console.

KDFS016I CANDLE DATASET I/O - NO DEVICE TYPES TO MONITORExplanation: During initialization the collector found that there were no device types installed that it could monitor. It will monitor 3375, 3380, 3390, and future DASD devices.System Action: The collector terminates.User Response: If there are device types installed that the collector should monitor, contact Candle Customer Support. Otherwise, no action is required.

KDFS019A CANDLE DATASET I/O module ATTACH OF task_id FAILED, RC=return_codeExplanation: An attempt by module to attach the MVS subtask specified failed with the return code displayed.System Action: The collector terminates.User Response: Refer to IBM’s Application Development Reference: Services for Authorized Assembler Language Programs for an explanation of the return code. If the return code does not indicate an installation problem, contact Candle Customer Support.Destination: The MVS system console.

KDFS020I CANDLE DATASET I/O module SUBTASK task_id FAILEDExplanation: Routine module has determined that subtask task_id has terminated unexpectedly.System Action: The collector attempts to restart the subtask.User Response: Contact Candle Customer Support.Destination: The MVS system console.


KDFS021I CANDLE DATASET I/O module RESTARTING SUBTASK task_idExplanation: Routine module attempted to restart subtask task_id after it unexpectedly terminated.System Action: If the restart is successful, the collector continues; otherwise the collector terminates.User Response: None.Destination: The MVS system console.

KDFS022W CANDLE DATASET I/O module SUBTASK task_id FAILED - STOPPINGExplanation: A prior attempt to restart subtask task_id by routine module was unsuccessful.System Action: The collector terminates.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFS023A CANDLE DATASET I/O module ROUTINE routine FAILED return_code reason_codeExplanation: The module specified called routine, and the called routine returned with the return and reason codes displayed.System Action: The collector attempts to continue functioning. User Response: Review the appropriate user response.

Destination: The MVS system console.

KDFS024A CANDLE DATASET I/O module service INSTALLATION FAILEDExplanation: An attempt by routine module to install the service specified was not successful.System Action: The collector terminates.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFS025W CANDLE DATASET I/O module RELEASE OF bytes storage RC=return_ codeExplanation: An attempt by routine module to release the number of bytes of virtual storage specified failed with the return code displayed.System Action: The collector continues processing normally.User Response: Contact Candle Customer Support.Destination: The MVS system console.

OMEGAMON II for SMS This is an informational message only.

All other products Contact Candle Customer Support.


KDFS026W CANDLE DATASET I/O module UNABLE TO FREE number PAGES OF STORAGE, RC=return_codeExplanation: An attempt by routine module to free the specified number of pages of virtual storage was not successful. The return code from the PGSER service displayed.System Action: The collector continues processing normally.User Response: Refer to IBM’s Application Development Reference: Services for Authorized Assembler Language Programs for an explanation of the return code. Contact Candle Customer Support.Destination: The MVS system console.

KDFS027W CANDLE DATASET I/O module UCBLOOK RC = return_code, DEVICE NUMBER deviceExplanation: An invocation of the UCBLOOK service by routine module resulted in the return code displayed for device number device.System Action: The collector continues processing; however, there will be no data available for the specified device.User Response: See IBM’s MVS/ESA Planning: Dynamic I/O Configuration manual for an explanation of the return code. Contact Candle Customer Support.Destination: The MVS system console.

KDFS028 CANDLE DATASET I/O COLLECTOR RESOURCE MANAGER CLEANUP IN PROGRESSExplanation: The collector has terminated abnormally, and the resource manager routine has been invoked to clean up the environment.System Action: None.User Response: None. This is an informational message only. There should be other messages issued previously that require action. If there are no previous messages, contact Candle Support Services.Destination: The MVS system console.

KDFS029A UNABLE TO ATTACH MIGRATION SUBTASK, RC= return_codeExplanation: The ATTACH macro used to create the migration subtask failed. The return code displayed represents the contents of register 15 passed back by the ATTACH macro.System Action: The collector terminates.User Response: Refer to IBM’s Application Development Reference: Services for Authorized Assembler Language Programs for an explanation of the return code. If problems persist, contact Candle Customer Support.Destination: The MVS system console.


KDFS030A MIGRATION SUBTASK ABEND, CODE= abend_codeExplanation: The subtask used to arrange job and dataset information has abnormally terminated with the displayed completion code.System Action: The collector terminates.User Response: Inspect the console log for messages that may provide a clue as to why the ABEND occurred. If problems persist, contact Candle Customer Support.Destination: The MVS system console.

KDFS031A CVAFSEQ ERROR READING VTOC: RC= return_code, CVSTAT=xxExplanation: A volume table of contents could not be read using the CVAFSEQ macro. The volume for which the VTOC failure occurred is identified in a separate message displayed on the system console.System Action: Some dataset names may not be resolved for the volume’s I/O activity.User Response: Consult the IBM MVS/DFP System Programming Reference manual for an explanation of the return code and CVSTAT fields returned by CVAFSEQ. If problems persist, contact Candle Customer Support.Destination: The MVS system console.

KDFS032A UNABLE TO ACQUIRE VTOC STORAGE: LENGTH= bytes, RC=return_codeExplanation: The migration subtask was unable to allocate the specified number of bytes of private storage for its CVAF buffers. The return code displayed is provided by the STORAGE macro.System Action: The collector terminates.User Response: Increase the Candle Subsystem region size.Destination: The MVS system console.

KDFS033I UNABLE TO READ VOLUME TABLE OF CONTENTS FOR volserExplanation: The migration subtask was unable to read the VTOC of the displayed volser. An accompanying console message will be generated describing the precise cause of the error.System Action: Some dataset names may not be resolved for the volume’s I/O activity.User Response: Locate the diagnostic message that indicates the cause of the VTOC error and take any necessary corrective action. If problems persist, contact Candle Customer Support.Destination: The MVS system console.

KDFS034A CELL POOL FAILURE FOR SERVICE service, RC=return_codeExplanation: The cell pool service specified failed with the return code displayed. The migrator subtask uses callable cell pool services to create its internal table entries.System Action: The collector terminates.User Response: The IBM manual Reference: Services for Assembler Language Programs contains a description of the return codes associated with the failing service. Contact Candle Customer Support.


KDFS035I UNABLE TO READ FORMAT 4 DSCB WITH LSPACE, RC=return_codeExplanation: The LSPACE macro used by the migrator subtask has failed with the return code displayed. The volume for which the VTOC failure occurred is identified in a separate message displayed on the system console.System Action: Some dataset names may not be resolved for the volume’s I/O activity.User Response: Consult the IBM MVS/DFP System Programming Reference manual for an explanation of the return code and CVSTAT fields returned by CVAFSEQ. If problems persist, contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFS036I UNABLE TO OBTAIN DEVICE CELL, DATA LOSTExplanation: The migrator subtask has run out of cell pool storage to record dataset I/O information.System Action: Some information about dataset I/O activity is lost.User Response: Ensure that the archive subtask is running in the Candle Subsystem address space. If problems persist, contact Candle Customer Support.Destination: The MVS system console.

KDFS037A INSUFFICIENT STORAGE TO READ VTOC FOR VOLUME volserExplanation: The migrator subtask was unable to fit the VTOC for the volume specified in the space it had allocated.System Action: The collector terminates.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFS100E ATTACH FAILED FOR KDFSHSMM, RC= rcExplanation: An ATTACH macro failed with the indicated return code.System Action: HSM MCDS analysis will be unavailable.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS101I MCDS ANALYSIS HAS TERMINATEDExplanation: The HSM MCDS analysis feature terminated.System Action: None.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFS102E ACB ACQUISITION FAILED, COMPLETION CODE compl_codeExplanation: A request for an ACB failed with the indicated completion code.System Action: The HSM MCDS analysis feature will be unavailable.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.


KDFS103E UNABLE TO ALLOCATE MIGRATION CONTROL DATASET, RC= rcExplanation: A request to allocate the HSM MCDS failed with the indicated return code.System Action: The HSM MCDS analysis feature will be unavailable.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS104E OPEN FAILED FOR MIGRATION CONTROL DATASETExplanation: A request to open the HSM MCDS failed.System Action: The HSM MCDS analysis feature will be unavailable.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS105E ERROR IN VSAM START REQUESTExplanation: A request to browse the HSM MCDS failed.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS106E ERROR IN TERMINATION REQUESTExplanation: A request to close and deallocate the HSM MCDS failed.System Action: HSM MCDS processing continues.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS107E ERROR IN VSAM ccccc REQUEST, RC= return_code, REASON= reason_codeExplanation: A VSAM POINT or GET request failed with the indicated return and reason codes.System Action: HSM MCDS processing continues.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS108E SAVEAREA STACK EXHAUSTEDExplanation: An internal error occurred.System Action: The HSM MCDS analysis feature will be unavailable.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS109E MCDS SUBTASK ABEND, COMPLETION CODE compl_codeExplanation: The HSM MCDS analysis subtask abended with the indicated completion code.System Action: The HSM MCDS analysis feature will be unavailable.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.


KDFS110E INVALID POST CODE RECEIVED, CODE= post_codeExplanation: The indicated invalid post code was received from the HSM MCDS analysis subtask.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS111E BLDL for KDFSHSMM FAILED, RC= rcExplanation: Module KDFSHSMM is not available.System Action: The MCDS analysis feature will not be available.User Response: Verify the RKANMODL concatenation. If in doubt, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS14A CANDLE DATASET I/O module SERVICE REQUEST request FAILURE, RC=return_codeExplanation: The module specified requested a service of either MVS or the Candle Subsystem, and the request failed with the return code displayed.System Action: The collector will terminate if the request is critical.User Response: If the failure was for an MVS service, ensure that it was not the result of an installation problem. If necessary, contact Candle Customer Support.

KDFS15A CANDLE DATASET I/O module DEVICE TABLE FULLExplanation: The module specified attempted to add a device type to an internal table, but the table had no free entries.System Action: The collector continues; however, data will not be collected for all devices.User Response: Contact Candle Customer Support.

KDFS17A CANDLE DATASET I/O DSPSERV number FAILED, return_code-reason_codeExplanation: An attempt to create the dataspace number specified failed. The DSPSERV request returned the return_code and reason_code.System Action: The collector does not initialize.User Response: Refer to IBM’s Application Development Reference: Services for Authorized Assembler Language Programs for explanations of the return and reason codes. If the return and reason codes do not indicate a problem in your installation, contact Candle Customer Support.

KDFS18A CANDLE DATASET I/O ALESERV number FAILED, RC=return_codeExplanation: An attempt to add an entry to an access list for dataspace number failed. The return code from ALESERV was displayed.System Action: The collector does not initialize.User Response: Refer to IBM’s Application Development Reference: Services for Authorized Assembler Language Programs for an explanation of the return code. If the return code does not indicate a problem in your installation, contact Candle Customer Support.


KDFS201E STORAGE OBTAIN REQUEST FAILEDExplanation: An MVS STORAGE request failed.System Action: The HSM MCDS analysis feature will terminate.User Response: Restart the Candle Management Server with a larger region size. If the error persists, contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS202E DSPSERV CREATE FAILED, RC= rcExplanation: An MVS DSPSERV TYPE=CREATE request failed with the indicated return code.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS203E ALESERV REQUEST FAILED, RC= rcExplanation: An MVS ALESERV request failed with the indicated return code.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS204E STIMERM REQUEST FAILED, RC= rcExplanation: An MVS STIMERM request failed with the indicated return code.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS205I MCDS ANALYSIS SUBTASK STARTING QUIESCEExplanation: The HSM MCDS analysis feature is being shut down.System Action: HSM MCDS analysis will terminate.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFS206I MCDS ANALYSIS SUBTASK HAS TERMINATEDExplanation: The MCDS analysis feature has terminated.System Action: Normal operation continues.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFS207I MCDS DATASPACE LOCATED AT address, LENGTH lenExplanation: The HSM MCDS dataspace with the indicated length was created at the indicated address.System Action: The HSM MCDS analysis feature will proceed.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.


KDFS208I MCDS DATASPACE ID= id, STOKEN= tokenExplanation: These are the generated names of the HSM MCDS dataspace.System Action: The HSM MCDS analysis feature will proceed.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFS209E INTERNAL LOGIC ERRORExplanation: An internal error occurred.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS210E MCDS DATASPACE IS TOO SMALLExplanation: The HSM MCDS dataspace is too small for general use.System Action: The HSM MCDS analysis feature will terminate.User Response: Increase the MCDSDSPACESIZE parameter in the KDFDHSIN member of the RKANPAR dataset and recycle the Candle Management Server. Using CICAT to respecify, ensures correct parameter input.Destination: The CT/Engine log, RKLVLOG.

KDFS211E FAILURE IN ACQUISITION OF MCDS DSN, RC= rcExplanation: Locating the dataset name of the HSM MCDS failed with the indicated return code.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS212E INVALID DATA DETECTED FOR dsnameExplanation: An invalid HSM MCDS record was detected.System Action: The HSM MCDS analysis feature will continue.User Response: None. This message is informational.Destination: The CT/Engine log, RKLVLOG.

KDFS213E SVC DUMP WILL BE REQUESTEDExplanation: HSM MCDS analysis abended and requested a dump.System Action: The HSM MCDS analysis feature will terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.

KDFS214E SDUMPX REQUEST FAILED, RC= rcExplanation: An MVS SDUMPX request failed with the indicated return code.System Action: The HSM MCDS analysis feature will continue to terminate.User Response: Contact Candle Support Services.Destination: The CT/Engine log, RKLVLOG.


KDFSHL00 ABEND abend_code AVERTED IN RC++ PACKAGEExplanation: Error recovery processing detected that the specified abend occurred during processing.System Action: Error recovery is invoked.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFSHL01 ABEND abend_code AVERTED IN SESSION INITIALIZATIONExplanation: Error recovery processing detected that the specified abend occurred during processing.System Action: Error recovery is invoked.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFSHL02 ABEND abend_code AVERTED IN SESSION DISPATCHERExplanation: Error recovery processing detected that the specified abend occurred during processing.System Action: Error recovery is invoked.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFSHL03 ABEND abend_code AVERTED IN SESSION TERMINATIONExplanation: Error recovery processing detected that the specified abend occurred during processing.System Action: Error recovery is invoked.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFSHL04 ABEND abend_code AVERTED IN CREATING SESSION ENVIRONMENTExplanation: Error recovery processing detected that the specified abend occurred during processing.System Action: Error recovery is invoked.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFSHL05 ABEND abend_code AVERTED WHEN DESTROYING ENVIRONMENTExplanation: Error recovery processing detected that the specified abend occurred during processing.System Action: Error recovery is invoked.User Response: Contact Candle Customer Support.Destination: The MVS system console.

KDFSHSML HSMLOG DATASPACE AT CAPACITY - nnnnnnnn BLOCKSExplanation: The HSM log analysis dataspace is full.System Action: The dataspace will be rebuilt.User Response: Consider increasing the site default dataspace size.Destination: The CT/Engine log, RKLVLOG.


KDFSHSML HSMLOG DATASPACE XXXXXXXX CREATEDExplanation: The HSM log analysis dataspace has been successfully created.System Action: HSM log analysis initialization continues.User Response: None.Destination: The CT/Engine log, RKLVLOG.

KDFSHSML HSMLOG PROCESSING BYPASSED DUE TO ERRORExplanation: A GET request from the HSM log dataset has failed.System Action: The request will be attempted up to twice, as necessary. If the third attempt fails, HSM log analysis will terminate.User Response: This is an internal error. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFSHSML macro REQUEST - RC = 99999999 99999999Explanation: A DSPSERV or ALESERV request failed.System Action: HSM log analysis will terminate.User Response: This is an internal error. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFSHSML MESSAGE ARC nnnnn FORMAT ERROR DETECTED - TEXT:Explanation: An error occurred while parsing the specified HSM log message.System Action: The message is bypassed.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFSHSML MESSAGE CONTROL TABLE ERROR DETECTED - XXXXXXXXExplanation: This is an internal error which should not occur.System Action: The HSM log analysis dataspace will be rebuilt.User Response: This error should not occur. Contact Candle Customer Support.Destination: The CT/Engine log, RKLVLOG.

KDFSTR01 RC++ START - SESSION LIST AT addressExplanation: Informational message printed on the CT/Engine log dataset. This message lists the address of the product anchor control block.System Action: None.User Response: None. This message is informational.Destination: The MVS system console.

KDPAU00I DB2PLEX AUTODISCOVERY STARTEDExplanation: This is an informational message displayed during startup.System Action: None.User Response: None.


KDPAU01F AUTODISCOVERY INITIALIZATION FAILEDExplanation: An internal error is preventing OMEGAMON XE for DB2 from recognizing the DB2 subsystems that are currently online.System Action: None.User Response: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU02E MULTIPLE IPDC AUTODISCOVERY COMMANDS ISSUEDExplanation: The auto discovery command executed more than once.System Action: None.User Response: Check the RKANCMD file to make sure that only one AUTODISCOVER command is specified. If there is more than one command, remove the extra commands.

KDPAU03F UNABLE TO CREATE LOGICAL RESOURCEExplanation: An internal error is preventing OMEGAMON XE for DB2 from recognizing the DB2 subsystems that are currently online.User Response: None.System Action: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU04F UNABLE TO ACQUIRE LOGICAL RESOURCEExplanation: An internal error is preventing OMEGAMON XE for DB2 from recognizing the DB2 subsystems that are currently online.User Response: None.System Action: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU05F RESOURCE LOCK ERROR ERRNO=nnnnExplanation: A logic error preventing the acquisition of a lock.System Action:User Response: Contact Candle Customer Support and provide them with the error code displayed in the message. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU10F CONTROL BLOCK ALLOCATION FAILEDExplanation: Storage is not available for this function, indicating that either there is not enough storage available to the started task or some type of storage overlay is preventing the allocation.System Action: None.User Response: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.


KDPAU11F CONDITION INITIALIZATION FAILEDExplanation: This is an internal error.System Action: None.User Response: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU12F CONDITION MUTEX INITIALIZATION FAILEDExplanation: This is an internal error.System Action: None.User Response: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU13F MUTEX INITIALIZATION FAILEDExplanation: This is an internal error.System Action: None.User Response: Contact Candle Customer Support. Until a resolution is found, you can use CICAT to disable auto discovery and manually identify the DB2 systems.

KDPAU14E COMMAND="command" FAILED. STATUS=nnnnExplanation: The specified command did not complete properly. The command was issued to either start collecting data for a new DB2 subsystem or to stop collecting data for a DB2 system that is no longer active.System Action: None.User Response: Contact Candle Customer Support with the available information.

KDPAU99I DB2PLEX AUTODISCOVERY SHUTDOWNExplanation: This is an informational message indicating that auto discovery is no longer active.System Action: None.User Response: None.

KDPDC01E NO MATCHING KDPCNFG PARM FOR DB2ID (dbid)Explanation: There are no entries in the KDPCFNFG member of RKANPAR that have collection information for this DB2 subsystem.System Action: None.User Response: None.

KDPDC03F UNABLE TO ALLOCATE MEMORY FOR ANCHORExplanation: Storage is not available for this function, indicating that either there is not enough storage available to the started task or some type of storage overlay is preventing the allocation.System Action: None.User Response: Contact Candle Customer Support.


KDPDC04E NO DATA COLLECTORS SPECIFIED FOR DB2ID (dbid)Explanation: A DB2 system was identified to be monitored, but there are no collectors defined for that DB2 subsystem.System Action: None.User Response: Verify that the specifications used in CICAT for this DB2 system are correct.

KDPDC07E UNABLE TO ALLOCATE KDPDNFC PARM BLOCKExplanation: Storage is not available for this function, indicating that either there is not enough storage available to the started task or some type of storage overlay is preventing the allocation.System Action: None.User Response: Contact Candle Customer Support.

KDPDC08E INVALID SUBSYSTEM TYPE=’cccccccc’Explanation: The subsystem type is not DB2ID.System Action: None.User Response: Verify the statements in KDPCNFG to make sure the format of the commands is proper. The commands should all start with DB2ID(xxxx).

KDPDC09E INVALID SUBSYSTEM ID=’ccccccccccc’Explanation: The DB2 system name specified on the DB2ID statement is either missing or has more then 4 characters in the name.System Action: None.User Response: Correct this in the KDPCNFG member or rerun CICAT using the proper name of the DB2 subsystem.

KDPDC10E INVALID COLLECTOR=’cccccccc’ SPECIFIEDExplanation: The collector name is unknown. The valid collectors are COUPFAC(), THREAD(), OBJECTA(), OBJECTB(), OBJECTV, GBPSTAT(), CONFLICT() and SRM().System Action: None.User Response: None.

KDPDC11E ERROR OPENING RKANPAR(KDPCNFG)Explanation: The system was unable to open the KDPCNFG member of the RKANPAR library. CICAT creates this member when a LOAD operation is performed for this product.System Action: None.User Response: Verify that the member exists and can be accessed, and that the CICAT job succeeded.

KDPDC12E UNEXPECTED EOF IN RKANPAR(KDPCNFG)Explanation: An EOF condition was raised while processing a command with a continuation indicator.System Action: None.User Response: Check the KDPCNFG member to make sure there is no continuation character on the last line. The KDPCNFG member can be recreated using the CICAT job for loading the RTE.


KDPDC13E INVALID INTERVAL FOR DB2ID (dbid) cccccccc. IGNORED.Explanation: The interval value specified is not numeric and cannot be processed. The value specified has to represent the number of seconds between samples.System Action: None.User Response: Verify the value in the KDPCNFG member and set it to a number between 30 and 999.

KDPDC14F NO SUBSYSTEMS ENABLED IN RKANPAR(KDPCNFG)Explanation: No parameters controlling the DB2 systems have been specified in the KDPCNFG member.System Action: None.User Response: Verify that the CICAT job to load the libraries has been run.

KDPDS00I MONITORED SUBSYSTEMS:Explanation: This message will appear in the RKLVLOG as a result of issuing the DPDC DISPLAY command. This is the first line of output from the DPDC DISPLAY command. System Action: None.User Response: None.

KDPDS02I DB2(dbid) STATE=cccccccc COLLECTORS:Explanation: This message will appear in the RKLVLOG as a result of issuing the DPDC DISPLAY command. Each monitored DB2 system will display a line showing the identifier and its state. Valid states are STOPPING, STOPPED, STOPPED (NO AUTODISCOVERY), RESTARTING, RESTARTED, STARTING, STARTED, or UNKNOWN. The valid collectors are COUPFAC(), THREAD(), OBJECTA(), OBJECTB(), OBJECTV, GBPSTAT(), CONFLICT() and SRM().System Action: None.User Response: None.

KDPDS03I THREAD(nnn) OBJECTV(nnn) SRM(nnn)Explanation: This message will appear in the RKLVLOG as a result of issuing the DPDC DISPLAY command. Each monitored DB2 system will display a line showing which collectors are active and the sampling interval.System Action: None.User Response: None.

KDPDS99I nnn SUBSYSTEMS DISPLAYEDExplanation: This message will appear in the RKLVLOG as a result of issuing the DPDC DISPLAY command. This last line of the output contains the number of DB2 subsystems being monitored.System Action: None.User Response: None.


KDPGOVM1 OBJECT ANALYSIS state FOR DSGROUP group ON DB2 SUBSYSTEM dbidExplanation: This message will appear in the JESMSGL system output file and deals with group object analysis collection. Each DB2 system will display a line. The state value will be either ACTIVE or INACTIVE, the group will be the data sharing group name or the DB2 name (when data sharing is not in use), and the dbid will identify the DB2 system being monitored.System Action: None.User Response: None.

KDPGOVM2 OBJECT ANALYSIS ON MVSID smfid USING JOB ccccccccExplanation: This message will appear in the JESMSGL system output file and deals with group object analysis collection. The smfid identifies the MVS image where the DB2 is running and cccccccc is the name of the started task that collects data for the volume activity workspaces.System Action: None.User Response: None.

KDPGOVM3 OBJECT ANALYSIS ON MVSID smfid DISABLEDExplanation: This message will appear in the JESMSGL system output file and deals with group object analysis collection. The OBJECTV data collector for the system identified by smfid has been disabled, because it reached its limit of five exceptions (abends) when trying to gather data. This collector will remain disabled until the address space is recycled. System Action: None.User Response: None.

KDPAT001 DPDC GLOBAL VECTOR TABLE NOT FOUNDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment.System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support.

KDPAT007 DPDC COLLECTOR WAS NOT ATTACHED FOR DB2 dbid.R0(xxxxxxxx) R1(xxxxxxxx) R15(xxxxxxxx)Explanation: The attempt to attach a new TCB failed for the KDPCOL00 module. Register 15 will contain the error code from the attach request.System Action: None.User Response: Contact Candle Customer Support.

KDPBG001 DPDC GVT ALREADY INSTALLED AT ADDRESS xxxxxxxxExplanation: The KDPBGV00 routine has already run and allocated the Global Vector table.System Action: None.User Response: Contact Candle Customer Support.


KDPBG002 DPDC REQUIRES APF AUTHORIZATIONExplanation: The load library from where the program is loaded is not authorized.System Action: None.User Response: Add the library to the APF authorization list and restart the task.

KDPBG003 DPDC REQUIRES MVS/ESAExplanation: This product is not supported on the MVS operating system you are currently running.System Action: None. User Response: Contact Candle Customer Support.

KDPBG004 DPDC UNABLE TO ACQUIRE STORAGE FOR GVTExplanation: The storage request for the global vector table failed. This indicates that either there is not enough virtual memory available or that a storage corruption is preventing space allocation.System Action: None.User Response: Contact Candle Customer Support.

KDPCM001 DPDC IS NOT INITIALIZEDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment.System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support.

KDPCM003 DPDC AVT ALLOCATION FAILURE, SIZE=nnnnnnExplanation: The storage request for the application vector table failed. The size requested is shown as nnnnnn bytes. This indicates that either there is not enough virtual memory available or that a storage corruption is preventing space allocation.System Action: None.User Response: Contact Candle Customer Support.

KDPCM030 DPDC (dbid) MONITOR IS ALREADY STARTEDExplanation: The request to start the collection for the DB2 system is being ignored because the collector is already started.System Action: None.User Response: None.

KDPCM031 DPDC (dbid) MONITOR IS ALREADY STOPPEDExplanation: The request to stop the collection for the DB2 system is being ignored because the collector is already stopped.System Action: None.User Response: None.


KDPCM035 DPDC (dbid) MONITOR IS BEING TERMINATEDExplanation: The collector for the specified DB2 system is scheduled for termination.System Action: None.User Response: None.

KDPCM037 DPDC (dbid) MONITOR IS BEING RESTARTED. AVT ADDRESS=xxxxxxxxExplanation: The collector for the specified DB2 system is being restarted. The address of the application vector table is displayed.System Action: None.User Response: None.

KDPCM039 DPDC COMMAND FORMAT ERRORExplanation: An error was detected on the command displayed just before this message.System Action: None.User Response: Correct the syntax and reissue the command.

KDPCM042 IPDC ERROR LOADING MODULE modnameExplanation: The system was unable to load the auto discovery module or the display module from the load library.System Action: None.User Response: Verify that the module exists.

KDPCT001 DPDC IS NOT INITIALIZEDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment. System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support.

KDPCT002 DPDC GVT CREATED. ADDRESS=xxxxxxxxExplanation: This is an informational message. The initialization of the global vector table has completed and the address is displayed.System Action: None.User Response: None.

KDPCT007 DPDC description (modname) ROUTINE NOT FOUNDExplanation: The program identified by the description and module name was not able to be loaded from the load library.System Action: None.User Response: Verify that the proper load libraries are being used and that the specified member is present.


KDPDB001 DPDC GLOBAL VECTOR TABLE NOT FOUNDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment.System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support.

KDPDB007 DPDC SCOM SCAN (modname) ROUTINE NOT FOUNDExplanation: The program identified by the module name was not able to be loaded from the load library.System Action: None.User Response: Verify that the proper load libraries are being used and that the specified member is present.

KDPDB020 DB2 MASTER REGION FOR DB2ID dbid IS NOT FOUND OR DB2 ERLY NOT VALIDExplanation: The collector code was unable to locate the DB2 master started task for the specified DB2 system. This can be caused by the dbidMSTR started task not running or because the ERLY control block is invalid.System Action: None. User Response: If the master task is not running, restart the DB2 system. Otherwise, contact Candle Customer Support.

KDPDB025 JES CVT NOT FOUNDExplanation: This is an internal error.System Action: None.User Response: Contact Candle Customer Support.

KDPDB025 NO SUBSYSTEMS FOUNDExplanation: This is an internal error. System Action: None.User Response: Contact Candle Customer Support.

KDPDC005 DPDC UNABLE TO OPEN RKANPAR DATASET R0(xxxxxxxx) R1(xxxxxxxx) R15(xxxxxxxx)Explanation: An error occurred when trying to open the PDS RKANPAR. System Action: None.User Response: Verify that the dataset is available and not allocated to some other task in exclusive mode.

KDPDC006 DPDC UNABLE TO ENQUEUE RKANPAR DATASET R0(xxxxxxxx) R1(xxxxxxxx) R15(xxxxxxxx)Explanation: An attempt to obtain an ENQUEUE on the RKANPAR dataset has failed. The return code from the ENQUEUE request in R15.System Action: None.User Response: None.


KDPDC007 DPDC UNABLE TO FIND MEMBER member R0(xxxxxxxx) R1(xxxxxxxx) R15(xxxxxxxx)Explanation: The specified member is not located in the RKANPAR PDS. This indicates that the Load Runtime Members job may not have been run successfully from CICAT.System Action: None.User Response: None.

KDPDC009 DPDC COMMAND {ENTERED | PROCESSED}: ccccccccExplanation: The displayed command has been successfully executed if the PROCESSED string displays; it has failed if the ENTERED string displays. Message KDPDC039 follows this message when there is a failure.System Action: None. User Response: None.

KDPDC039 DPDC COMMAND FORMAT ERRORExplanation: The previous command has a format error.System Action: None.User Response: Correct the format and reissue the command.

KDPDE007 DPDC COLLECTOR SUCCESSFULLY DETACHED FOR DB2 dbid. TCB ADDRESS=xxxxxxxxExplanation: The collector has successfully stopped and the TCB used by it released.System Action: None.User Response: None.

KDPIN009 DPDC VECTOR TABLE NOT FOUND. DBDC NOT INITIALIZEDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment.System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support.

KDPSC001 DPDC GLOBAL VECTOR TABLE NOT FOUNDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment.System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support.

KDPSC007 DPDC description (modname) ROUTINE NOT FOUNDExplanation: The program identified by the description and the module name was not able to be loaded from the load library. System Action: None.User Response: Verify that the proper load libraries are being used and that the specified member is present.


KDPSC098 DB2 IRLM RELEASE LEVEL IS NOT RECOGNIZED. NO LOCK NOT COUPLING FACILITY DATA WILL BE COLLECTED.Explanation: The IRLM system being used is not supported by the product. System Action: None.User Response: Contact Candle Customer Support.

KDPTR001 DPDC TERMINATING. REASON Code(nnnn)Explanation: Data collection is being stopped. The reason code for the stop is displayed.System Action: None.User Response: None.

KDPTR003 DPDC PHASE n TERMINATION COMPLETEExplanation: This information message shows the completion of termination. The possible values for n are 1 and 2. On the completion of Phase 2, data collection is complete.System Action: None.User Response: None.

KDPWA001 DPDC GLOBAL VECTOR TABLE NOT FOUNDExplanation: The global vector table has not been allocated, indicating that the KDPBGV routine failed to properly initialize the environment.System Action: None.User Response: Look for error messages preceding this one for an indication as to what failed. Contact Candle Customer Support

KDSDC001 Initial load of CMS Catalog now in progressExplanation: CMS is loading its runtime Catalog dataset. No other activity takes place during this load. The loading process could take as long as 2 minutes, depending on the number of applications installed.User Response: This message is followed by another message when the loading is completed. Destination: OS/400=CNB0012Severity: 0System Programmer Response:Unattended

KDSDC002 Initial load of CMS catalog completeExplanation: The CMS has completed the loading of its runtime Catalog dataset. Destination: OS/400=CNB0021Severity: 0System Programmer Response:Unattended

KDSMA001 Startup of Candle Management Server (CMS) in progress.Explanation: CMS started successfully.System Action: None.User Response: None.Severity: 60


KDSMA002 Candle Management Server (CMS) did not start. Status: statusExplanation: CMS did not start. Operation operation was in progress and completed with status status.System Action: CMS stops.User Response: Verify your installation and configuration procedures to make sure you are properly installed and configured.Severity: 20

KDSMA003 Candle Management Server (CMS) ended successfully.Explanation: CMS stopped successfully.System Action: None.User Response: None.Severity: 60

KDSMA004 Internal services failed during operation while attempting to end.Explanation: Stop of CMS did not complete successfully. Operation operation was in progress and completed with status status and reason reason.System Action: CMS ends normal stop.Severity: 20

KDSMA005 Stop of internal services ended abnormally. Reason reason.Explanation: Abnormal condition abend caused CMS to stop running.Severity: 20

KDSMA006 Candle Management Server (CMS) data collection server did not start.Explanation: The data collection server did not start.User Response: View all error messages that were logged to the CMS product log. Also, check the joblog of the failed job for messages. Destination: OS/400=CNB0006Severity: 20System Programmer Response:Unattended

KDSMA007 Logon did not complete. Not enough memory. User &1.Explanation: You tried to log onto Candle Management Server (CMS) but not enough memory is currently available to process the request.User Response: See your CMS administrator to determine memory requirements. Destination: OS/400=CNB0008Severity: 0System Programmer Response:No

KDSMA008 Duplicate logon attempted. User &1.Explanation: You tried to log onto Candle Management Server (CMS) more than once. Destination: OS/400=CNB0009Severity: 0System Programmer Response:No


KDSMA009 User &1 logged off server &2.Destination: OS/400=CNB0010Severity: 0

KDSMA010 Communication did not succeed. User &1 &2 cancelled.Explanation: Candle Management Server (CMS) has detected a loss of communication to the user. Automatic cleanup processing is invoked. Destination: OS/400=CNB0011Severity: 0System Programmer Response:No

KDSMA011 Logon successful to server &1 user &2 &3.Destination: OS/400=CNB0019Severity: 0

KDSMA012 Logon did not complete. User &1.User Response: You tried to log onto the Candle Management Server (CMS) data collection server, but a possible logon string error has occurred. Verify installation and configuration procedures. Destination: OS/400=CNB0013Severity: 0System Programmer Response:No

KDSMA013 APPLID &1 is not valid or is unavailable.Explanation: An attempt to bind to APPLID &1 failed. This could be due to the APPLID being unavailable or because the APPLID is not correct.User Response: Verify installation and configuration procedures. Destination: OS/400=CNB0022Severity: 0System Programmer Response:No

KDSMA014 Node ID &1 length is too long.Explanation: The length of the node id must be less than 32 characters.User Response: Verify installation and configuration procedures. Destination: OS/400=CNB0023Severity: 0System Programmer Response:No

KDSNC001 Checking location broker statusExplanation: The location brokers are being checked to determine if they are already active. Severity: 0System Programmer Response:No

KDSNC002 Local location broker is not activeExplanation: The local location broker has not yet been started. CMS will start it. Severity: 0System Programmer Response:No


KDSNC003 Global location broker is not activeExplanation: The global location broker has not yet been started. CMS will start it. Severity: 0System Programmer Response:No

KDSNC004 Bind of local location broker complete: &1[&2]Explanation: The local location broker initialized successfully using address &1 and port &2. Severity: 0System Programmer Response:No

KDSNC005 Bind of global location broker complete: &1[&2]Explanation: The global location broker initialized successfully using address &1 and port %2. Severity: 0System Programmer Response:No

KDSNC006 Bind of local and global location broker complete: &1[&2]Explanation: The local and global location broker initialized successfully. Both are using address &1 and port &2. Severity: 0System Programmer Response:No

KDSNC007 Local Location Broker is activeExplanation: The local location broker initialized successfully. Severity: 0System Programmer Response:No

KDSNC008 Global Location Broker is activeExplanation: The global location broker initialized successfully. Severity: 0System Programmer Response:No

KDSNC009 Unable to create location brokers, status = &1Explanation: The local and/or global location broker failed to start. User Response: Verify installation and configuration procedures. Severity: 0System Programmer Response:No

KDSPA001 Logon validation did not complete. User ID not valid. User &1 &2.Explanation: You tried to log onto the CMS data collection server, but the user ID is not a valid user ID.User Response: Enter a valid user ID. Destination: OS/400=CNB0014Severity: 0System Programmer Response:No


KDSPA002 Logon validation did not complete. Password not valid. User &1 &2.Explanation: You tried to log onto the Candle Management Server (CMS) data collection server, but the password supplied for the user ID is not valid.User Response: Enter a valid password. Destination: OS/400=CNB0015Severity: 0System Programmer Response:No

KDSPA003 Logon validation did not complete - system error. User &1 &2.Explanation: You tried to log onto the Candle Management Server (CMS) data collection server, but a possible system error occurred.User Response: Refer to the appropriate Problem Determination Guide. Destination: OS/400=CNB0016Severity: 0System Programmer Response:No

KDSPA004 Logon validation failed. User &1 &2.Explanation: You tried to log onto the Candle Management Server (CMS) but the logon validation failed.User Response: Make sure the userid and password used is correct. Destination: OS/400=CNB0020Severity: 0System Programmer Response:No

KDSPM001 Remote request directory service lookup failed for node &1.Explanation: The location of the node specified in a remote request cannot be determined. Possible configuration error.User Response: Verify installation and configuration procedures. Destination: OS/400=CNB0017Severity: 0System Programmer Response:No

KDSRU001 Remote request communication failure to destination &1.Explanation: The Candle Management Server (CMS) data collection server has lost or could not communicate with a remote partner. Possible configuration error.User Response: Try again later. If still not successful, verify installation and configuration procedures. Destination: OS/400=CNB0018Severity: 0System Programmer Response:No


KFAAL00E INVALID SE LOCK STATE IN module COUNTER=lockcounterExplanation: An invalid state was detected in a shared or exclusive lock control block. An internal error has occurred that may cause integrity errors on shared resource access.The module value indicates the module where the problem was detected. The lockcounter value specifies the number of shared locks in progress. A lockcounter value of -1 means that a single user has an exclusive lock. A value of 0 means that no locks are in progress.System Action: Processing continues.User Response: Contact Candle Customer Support.

KFAA000E ALLOCATION ERROR FOR cbnameExplanation: An attempt to allocate memory for a control block has failed. The name of the control block is specified in cbname. This error can occur when virtual storage has been exhausted.System Action: Alert processing terminates abnormally, and no further attempt is made to distribute the alert to emitters.User Response: Examine the virtual storage limitations on the CMS and SITMON processes, and increase storage limits if possible.

KFAA001W KFAASITR LOOKUP TABLE NOT LOADEDExplanation: The alert automation environment could not be initialized, and the Situation Trap table could not be loaded into storage for alert processing.System Action: Alert automation is disabled. No alerts are issued when events are detected.User Response: Review the messages issued before this message, to determine the cause of environment initialization failure. This message is normal if no entries are specified in the KFAASITR runtime parameter file or if no KFAASITR parameter file is found.

KFAA002E THREAD CREATION ERROR ERROR= errnoExplanation: An attempt to start a thread of execution has failed. Threads are used to distribute action requests to alert emitters. The errno value indicates the status code issued by the POSIX pthread_create function.System Action: No further action is taken to transmit the action request to the alert emitter.User Response: Determine whether POSIX threading restrictions prevent the thread creation. If restrictions cannot be determined, contact Candle Customer Support.

KFAA003E GET LOCK ERROR=statusExplanation: An attempt to acquire a lock (pthread_mutex_lock) has failed. POSIX mutex locks are used to serialize access and update to internal control blocks shared by multiple threads of execution. The status value indicates the error code issued by the POSIX pthread_mutex_lock function.System Action: Alert processing is terminated. No further action requests are sent to the alert emitter.User Response: Contact Candle Customer Support.


KFAA004E COMMAND BUFFER OVERFLOW SITUATION=sitname DESTNODE=destnode ARG=argExplanation: An attempt to format the command string to be executed by an alert emitter has overflowed the internal buffer. The sitname and arg values indicate, respectively, the situation and argument being processed. The destnode value specifies the alert emitter.System Action: Alert processing for the event is terminated.User Response: Reduce the amount of data substituted into the command string by eliminating unnecessary attributes from the ARGn values specified for this event in the Situation Trap table (KFAASITR). If this error cannot be corrected, contact Candle Customer Support.

KFAA005S UNABLE TO ALLOCATE KFAASITR TABLEExplanation: An attempt to allocate a control block for the alert automation environment has failed. This error can occur when virtual storage is constrained.System Action: The automation environment cannot be initialized, and alert processing is disabled.User Response: Determine why the storage constraint occurred. If possible, increase storage limits for all the environments to be initialized, and then restart the CMS.

KFAA006S UNABLE TO INITIALIZE lockname ERRNO=statusExplanation: An attempt to initialize a lock (phtread_mutext_init) has failed. POSIX locks are used to serialize access and update to control blocks shared by multiple threads of execution. The lockname value specifies the lock whose initialization failed. The status value indicates the POSIX error code.System Action: No further attempt is made to initialize the lock, and alert automation initialization terminates. Alerts are not transmitted to alert emitters.User Response: Contact Candle Customer Support.

KFAA008W KFAASITR LOOKUP TABLE IS EMPTYExplanation: No destination node entries for alert emitters were specified in the Situation Trap table. This is a warning message.System Action: Alert automation is disabled until the table is refreshed.User Response: If alert automation is desired, review the contents of the Situation Trap table file, KFAASITR. Correct any syntax errors reported by messages issued previous to this message. After you correct the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.


KFAA009W KFAASITR COULD NOT BE OPENEDExplanation: The Situation Trap table (KFAASITR file) could not be found in the runtime parameter PDS (MVS CMS) or the /tables directory (UNIX CMS). This is a warning message.System Action: Alert automation is disabled until the table is refreshed.User Response: If alert automation is desired, ensure that the Situation Trap table file KFAASITR exists and contains at least one destination node entry. After the KFAASITR file has been created, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA010E DESTNODE NOT SPECIFIED IN LINE line NEAR tokenExplanation: The DESTNODE tag was not specified in an entry for the Situation Trap table (KFAASITR file). The DESTNODE tag must be specified for each entry in the table. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected. The token value indicates text near the entry where the destination node was not specified.System Action: The current entry is ignored, and processing continues with the next entry in the table.User Response: Correct the invalid Situation Trap table entry by ensuring that a DESTNODE tag is specified. Also ensure that each entry ends with a semicolon (;).

KFAA011E INVALID KFAASITR PARM=parmExplanation: An unexpected KFAASITR command parameter was specified. A MODIFY command issued to the MVS CMS address space has the following syntax:

MODIFY cmsjobname,CTDS KFAASITR parm

where cmsjobname is the jobname of the CMS address space and parm is one of the following:

System Action: The KFAASITR console command is ignored.User Response: Change the KFAASITR command parameter to one of those listed above.

REFRESH Reread the contents of the KFAASITR file to reinitialize the Situation Trap table.

DISPLAY Display the current contents of the Situation Trap table in memory.

TESTSIT Simulate the detection of a situation (named TestSituation) to verify proper operation of the alert automation environment and the alert emitters.


KFAA012W UNABLE TO ESTABLISH KFAASITR COMMAND STATUS=status REASON=reasonExplanation: An attempt to establish the KFAASITR console command in an MVS CMS environment has failed. The status and reason values indicate the status code and reason issued by the internal service function, OPER_DefineCommand.System Action: The KFAASITR command will not be accepted for the life of the MVS CMS address space.User Response: Contact Candle Customer Support.

KFAA013E MISSING SEMICOLON IN LINE line NEAR tokenExplanation: The end of the KFAASITR file containing Situation Trap table entries was found before the last entry in the table ended with a semicolon. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected. The token value indicates text near the entry where the destination node was not specified. This is a warning message.System Action: The last entry is processed and accepted if no syntax errors are detected.User Response: Review the KFAASITR file and ensure that all entries in the file end with a semicolon (;).

KFAA014W MULTIPLE VALUES DETECTED FOR tag IN LINE line NEW VALUE=new OLD=old CHECK SEMICOLONSExplanation: A duplicate tag was found for an entry in the Situation Trap table KFAASITR.The tag value specifies the tag duplicated for the current entry. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected. The new value is the last value specified. The old value is the previous value specified.System Action: The last value for the tag is accepted for the entry.User Response: Review the contents of the KFAASITR file and ensure that a single value is specified for each tag. Also check to ensure that all entries in the file end with a semicolon (;).

KFAA015E UNABLE TO LOAD mod entry STATUS=status REASON=reasonExplanation: An attempt to load a module into storage or to locate the address of a module in storage has failed. The mod value specifies the name of the module that could not be loaded. The status value is the STC1 status code associated with the error. The reason value is the RSN1 reason code associated with the error.System Action: The call to the module is aborted.User Response: Ensure that the libraries have been properly installed and configured. Contact Candle Customer Support.


KFAA020E INVALID LENGTH=length FOR tag="value" IN LINE lineExplanation: The value specified for a tag in the Situation Trap table KFAASITR has exceeded the maximum length for the tag. The maximum length varies for each tag. The length value specifies the maximum length acceptable for the tag. The tag and its value are specified in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.User Response: Correct the invalid length. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA021E INVALID VALUE FOR tag=value IN LINE lineExplanation: The value specified for a tag in the Situation Trap table KFAASITR is not acceptable. The tag and the value specified for it are shown in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.User Response: Correct the invalid value. After the KFAASITR file has been updated, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA022E INVALID SYNTAX: badtag IN LINE lineExplanation: A tag specified in the Situation Trap table KFAASITR is not acceptable. The badtag value specifies the unexpected entry. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.User Response: Correct the invalid tag. Ensure that the tag is spelled properly and specified in upper case. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA023E UNABLE TO ALLOCATE tag=valueExplanation: The storage required to store the value associated with a tag in the Situation Trap table KFAASITR could not be allocated. The tag and its value are specified in tag and value.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.User Response: Correct the invalid value. Ensure that the tag is spelled properly and specified in upper case. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.


KFAA024E ENDING QUOTE FOR TAG VALUE NOT FOUND IN LINE lineExplanation: The value specified for an entry in the Situation Trap table KFAASITR was not properly enclosed in quotes.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.User Response: Make sure that end quotes are specified in quoted values. Strings enclosed in quotes are processed as specified, and no attribute substitution is performed for these values (if tags are ARG1–ARG9). After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA025E WILDCARD NOT ALLOWED IN tag=value IN LINE lineExplanation: An asterisk was specified in the value associated with a tag in the Situation Trap table KFAASITR, but the value for this tag cannot be a wildcard. The tag and its specified value are shown in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.User Response: Correct the invalid value. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA026E TOO MANY WILDCARDS IN tag=value IN LINE lineExplanation: Two or more asterisks were specified in the value associated with a tag in the Situation Trap table KFAASITR, but only a single wildcard character is acceptable. The tag and its specified value are shown in tag and value. The line value specifies the line number in the KFAASITR runtime parameter file in which the error was detected.System Action: The tag is ignored, and syntax checking continues with the next tag for the current entry. The current entry is not accepted.User Response: Correct the invalid value. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.

KFAA030E oper SQL ERROR ON hdsee sql1api STATUS=statusExplanation: An attempt to transmit an action request to an alert emitter has failed during SQL processing. The oper value specifies the SQL operation which failed. The sql1api value specifies the SQL1 service function which failed. The status value specifies the SQL1 status code returned by the function.System Action: The alert automation action is terminated, and no further attempt is made to transmit the request to the alert emitter.User Response: Contact Candle Customer Support.


KFAA040I ACTION STARTED FOR SITNAME=sitname DESTNODE=destnode STATE=state REQUESTID=requestidExplanation: An alert automation action request has been successfully transmitted to an alert emitter. This is an informational message.The sitname value specifies the situation associated with the alert. The destnode value specifies the alert emitter. The state value specifies the current state of the associated event:

The requestid value is a unique integer assigned to the action request.System Action: The alert emitter proceeds to issue alerts or execute automation scripts for the alert.User Response: None.

KFAA041I CMD=commandstringExplanation: This informational message follows message KFAA040I. The commandstring value specifies the formatted command string transmitted to the alert emitter.System Action: The alert emitter proceeds to issue alerts or execute automation scripts for the alert.User Response: None.

KFAA042E NO RESPONSE FROM DESTNODE=destnode FOR SITNAME=sitname ORIGINNODE=originnode STATE=state ERRNO=status REQUESTID=reqidExplanation: This message follows messages KFAA040I and KFAA041I. No response was received within 60 seconds from the alert emitter responsible for alert automation requests.The destnode value specifies the alert emitter. The sitname value specifies the situation associated with the alert. The originnode value specifies the node from which the situation event was collected.The state value specifies the current state of the associated event:

The status value is the error number returned by the pthread_cond_timedwait service function. The reqid value is the unique integer request ID assigned to the action request.System Action: No further action is taken to determine the final disposition of the alert action request.User Response: End-user automation scripts must be written to complete execution as soon as possible. If automation scripts cannot complete within 60 seconds, a new thread of execution should be started by the automation script so that the successful response of automation can be recorded in the CMS message log. If this error persists, review the execution log provided by the alert emitter to determine whether automation failures have occurred.

1 The situation has become true.

2 The situation has become false.




KFAA050I ACTION COMPLETED FOR SITNAME=sitname DESTNODE=destnode STATE=state RC=rc REQUESTID=requestidExplanation: This informational message indicates the success or failure of an action request executed by an alert emitter, and marks the completion of the request.The sitname value specifies the situation associated with the alert. The destnode value specifies the alert emitter. The state value specifies the current state of the associated event:

The rc value specifies the return code issued by the automation script or by the alert sub-agent:

The requestid value is a unique integer assigned to the action request.System Action: No further processing is performed for the event.User Response: None.

KFAA051W DESTNODE=destnode OFFLINE FOR SITNAME=sitname ORIGINNODE=originnode STATE=state REQUESTID=requestidExplanation: An attempt to distribute an action request to an alert emitter has failed because the alert emitter is off-line and cannot be reached.The destnode value specifies the alert emitter. The sitname value specifies the situation associated with the alert. The originnode value specifies the node from which the situation event was collected. The state value specifies the current state of the associated event:

The requestid value is a unique integer assigned to the action request.System Action: No further action is taken to transmit the action request to the alert emitter.User Response: If this message persists, ensure that the alert emitter is started and registered with the CMS. If the alert emitter is properly started, an entry for the emitter will appear in the Nodes folder on the CMW desktop.If the emitter continues to remain off-line and alerts no longer need to be distributed to the emitter, update the Situation Trap table KFAASITR to remove the entry for the off-line alert emitter. After you update the KFAASITR file, issue a KFAASITR REFRESH console command (MVS CMS only) or restart the SMAF process to activate the new situation traps.



Zero Successful completion.

Other Automation or alert processing failure. You can find further information about the failure in the message log of the alert emitter.




KFAA060W UNABLE TO READ kdscnfg FILEExplanation: An attempt to read the kdscnfg file from the CMS configuration file directory (/tables directory) has failed.System Action: No connection to CMS can be established for alert automation processing. Alert processing is disabled.User Response: Ensure that the SMAF process is started from the proper directory and that the kdscnfg file is present. Restart CMS after corrections have been made.

KFAA070I USING CMS NODE=nodenameExplanation: The CMS node specified in the nodename value will be used to issue action requests to alert emitters. This is an informational message.System Action: Alert automation environment initialization continues.User Response: None.

KFAA090I KFAASITR REFRESHED. STATUS=statusExplanation: This message is issued to indicate the completion of a KFAASITR REFRESH command (MVS CMS only) to refresh the Situation Trap table. The status value indicates the status code issued by refresh processing:

System Action: If a zero value for the status is displayed, a new Situation Trap table is established, and subsequent events are processed from the updated entries in the table.User Response: If a non-zero value for the status is displayed, determine the cause of the failure by reviewing messages issued before this message.

KFAA091I TESTSIT INVOKED. STATUS=statusExplanation: This message is issued to indicate the completion of a KFAASITR TESTSIT command (MVS CMS only) to simulate the occurrence of a real event and to test the current Situation Trap table entries. The command triggers a dummy situation named "TestSituation". The status value indicates the status code issued by test processing:

System Action: If a zero value for the status is displayed, the Situation Trap table was searched and action requests were issued (if the simulated event matched any entries in the table).User Response: If a non-zero value for the status is displayed, determine the cause of the failure by reviewing messages issued before this message.

Zero Successful refresh processing.

Other Refresh processing failure.

0 Successful processing.

-1 Command string formatting error.

-2 Thread creation error.

-3 Alert automation environment disabled.


KFAA092I ACTIONS HAVE BEEN DISABLEDExplanation: An attempt to initialize the alert automation environment or to read the KFAASITR file to initialize the Situation Trap table has failed.System Action: Alert automation is disabled.User Response: Review messages issued before this message, and take appropriate action based on those messages.

KFAA093I ACTION ENVIRONMENT INITIALIZEExplanation: This informational message indicates that the alert automation environment has been successfully initialized.System Action: Situation events matching those defined in the Situation Trap table will cause action requests to be distributed to alert emitters.User Response: None.

KFAA094I KFAASITR LOOKUP TABLE:Explanation: This informational message is issued in response to a KFAASITR DISPLAY console command (MVS CMS only).System Action: The current contents of the Situation Trap table follow this message.User Response: None.

KFAA095I IF SITNAME=sitname AND ORIGINNODE=originnode AND STATE=state THENExplanation: This informational message displays the situation event data required to match the current entry in the Situation Trap table.The sitname value specifies the situation name or name pattern for the entry. An asterisk indicates a wildcard character.The originnode value specifies the source where the situation data was collected. An asterisk indicates a wildcard character.The state value specifies the current state of the situation required to match an event. Valid values are TRUE, FALSE, UNKNOWN, or ANY.System Action: Message KFAA096I follows this message to display the action and alert emitter assigned to situation events that match this entry.User Response: None.

KFAA096I DESTNODE=destnode CALLTYPE=calltype SCRIPT=scriptExplanation: This informational message, which follows message KFAA095I, displays the alert emitter destination node and the method to be used by the alert emitter to deliver the alert.The destnode value specifies the alert emitter name. The calltype value specifies the call method to be used to deliver action requests and alerts to the alert emitter:

The script value specifies the command to be executed (if CALLTYPE=0) or the name of the alert subagent to be notified (if CALLTYPE is non-zero).

Zero An automation script (REXX exec) is executed by the alert emitter.

Non-zero The alert is forward to an alert subagent by the alert emitter.


System Action: Message KFAA097I follows this message to display the action arguments to be passed to the alert emitter.User Response: None.

KFAA097I ARGn=valueExplanation: This informational message, which follows message KFAA096I, lists all arguments to be passed in the formatted command string transmitted to alert emitters.The n value specifies the position of the argument to be inserted into the command string. The value specifies the attribute name or quoted literal string to be inserted into the command string.System Action: The next Situation Trap table entry follows.User Response: None.

KFAA100I STACK SIZES: OG=curr/hih2o CT=curr/hih2o SNMP=curr/hih2oExplanation: This informational message is issued after all Situation Trap table entries are displayed in response to a KFAASITR REFRESH console command (MVS CMS only). The message displays the number of elements cached for OG/MVS, CT, and SNMP alert emitters.The curr value indicates the current number of cached SQL1 requests stored. The hih2o value indicates the highwater mark of cached SQL1 requests created since the start of the CMS.System Action: None.User Response: None.

KFAA193E ACTION ENVIRONMENT INITIALIZATION ERROR=errnoExplanation: The action environment could not be initialized because of a POSIX pthread_once service routine failure. The errno value shows the error number.System Action: No further action is taken to initialize the environment.User Response: Contact Candle Customer Support.

KFAA200E ACTION ENVIRONMENT NOT INITIALIZED DISPLAY COMMAND ENDEDExplanation: This message is issued when a console command to display the situation trap table (as defined by the KFAASITR runtime parameter file) could not be executed because the action environment failed to initialize.System Action: No further action is taken to display the situation trap table.User Response: Review the messages issued before this message, to determine the cause of environment initialization failure.

KIPA0502W UNABLE TO GET LOCK FOR REAL TIME DATA, USING INTERVAL DATAExplanation: The agent responsible for driving the data collection was unable to obtain a real time sample. In this case, the values returned will be for the previous sample taken. If this problem persists, it is an indication that another agent may be hung up waiting for the collector to complete. This is most likely an issue with the real time data collector not completing due to an internal error.System Action: The system will obtain and return the data collected during the previous request for data.


User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA0503E THE KIPSPB DATA COLLECTOR DID NOT FIND ANY POOL UTILIZATION DATAExplanation: A real time request was made for data but the KIPSPB collector responsible for gathering the data did not find any. This is an indication of an internal error.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA0514E ERROR nn GETTING GVT POINTERExplanation: The global vector table has not been allocated, indicating that the tasks initialization has not completed.System Action: The system will either continue to initialize or continue to terminate.User Response: Make a copy of the entire RKLVLOG and contact Candle Support Services.

KIPA0602W UNABLE TO GET LOCK FOR REAL TIME DATA, USING INTERVAL DATAExplanation: The agent responsible for driving the data collection was unable to obtain a real time sample. In this case, the values returned will be for the previous sample taken. If this problem persists, it is an indication that another agent may be hung up waiting for the collector to complete. This is most likely an issue with the real time data collector not completing due to an internal error.System Action: The system will obtain and return the data collected during the previous request for data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA0603E THE KIPWRK DATA COLLECTOR DID NOT FIND ANY VSAM/OSAM DATAExplanation: A real time request was made for data, but the KIPWRK collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: If you know that the IMS system being monitored has VSAM/OSAM activity and the problem persists, gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPA0614E ERROR nn GETTING GVT POINTERExplanation: The global vector table has not been allocated, indicating that the tasks initialization has not completed.System Action: The system will either continue to initialize or it will continue to terminate.User Response: Make a copy of the entire RKLVLOG and contact Candle Support Services.


KIPA0903E THE KIPCMP DATA COLLECTOR DID NOT FIND ANY DASD LOGGING INFORMATIONExplanation: A real time request was made for data, but the KIPCMP collector responsible for gathering the data did not find any.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: DASD logging information should always be available if the IMS system is running. Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA0914E ERROR nn GETTING GVT POINTERExplanation: The global vector table has not been allocated indicating that the tasks initialization has not completed.System Action: The system will either continue to initialize or continue to terminate.User Response: Make a copy of the entire RKLVLOG and contact Candle Support Services.


KIPA1002W UNABLE TO GET LOCK FOR REAL TIME DATA, USING INTERVAL DATAExplanation: The agent responsible for driving the data collection was unable to obtain a real time sample. In this case, the values returned will be for the previous sample taken. If this problem persists, it is an indication that another agent may be hung up waiting for the collector to complete. This is most likely an issue with the real time data collector not completing due to an internal error.System Action: The system will obtain and return the data collected during the previous request for data.User Response: If this problem persists, contact Candle Support Services.

KIPA1003E THE KIPCMP DATA COLLECTOR DID NOT FIND ANY ONLINE LOGGING DATASET INFORMATIONExplanation: A real time request was made for data, but the KIPCMP collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Online Logging Dataset information should always be available if the IMS system is running. Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPA1402W UNABLE TO GET LOCK FOR REAL TIME DATA, USING INTERVAL DATAExplanation: The agent responsible for driving the data collection was unable to obtain a real time sample. In this case, the values returned will be for the previous sample taken. If this problem persists, it is an indication that another agent may be hung up waiting for the collector to complete. This is most likely an issue with the real time data collector not completing due to an internal error.System Action: The system will obtain and return the data collected during the previous request for data.User Response: If this problem persists, contact Candle Support Services.


KIPA1403E THE KIPENV DATA COLLECTOR DID NOT FIND ANY ADDRESS SPACE DATAExplanation: A real time request was made for data, but the KIPENV collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Online Logging Dataset information should always be available if the IMS system is running. Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA1406E THE COLLECTOR DID NOT FIND A CONTROL REGION FOR THIS IMS SYSTEMExplanation: The ENV collector could not find the address space for the control region of the IMS system. This is either an internal error in the collector, or an issue where the IMS system terminated and the autodiscovery code has not recognized that it has gone away yet.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA1407I RSR NOT CONFIGURED FOR THIS IMS SYSTEMExplanation: Part of the information being reported through this agent contain information about RSR. This IMS system does not have RSR enabled.System Action: The remaining information about the IMS system is returned to be displayed by the CandleNet Portal.User Response: None.

KIPA1408I NO RSR VTAM CONNECTIONS DEFINEDExplanation: Part of the information being reported through this agent contain information about RSR VTAM connections. This IMS system does not have RSR VTAM connections enabled.System Action: The remaining information about the IMS system is returned to be displayed by the CandleNet Portal.User Response: None.




KIPA1703E THE KIPENV DATA COLLECTOR DID NOT FIND ANY ADDRESS SPACE TO MONITORExplanation: A real time request was made for data, but the KIPENV collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Online Logging Dataset information should always be available if the IMS system is running. If this problem persists, contact Candle Support Services.


KIPA1719E THE COLLECTOR DID NOT FIND AN IRLM REGION FOR THIS IMS SYSTEMExplanation: The IMS system being monitored does not make use of an IRLM system for data sharing. The address space for the IRLM is not being monitored with this IMS system. System Action: A record will be returned that contains a status indicator that the IRLM system is not defined for this IMS system.User Response: None.




KIPA2003E THE KIPWRK DATA COLLECTOR DID NOT FIND ANY TRANSACTION INFORMATIONExplanation: A real time request was made for data, but the KIPWRK collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.



KIPA2303E THE KIPWRK DATA COLLECTOR DID NOT FIND ANY RECOVERY CONTROL INFORMATIONExplanation: A real time request was made for data, but the KIPWRK collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.




KIPA2403E THE KIPENV DATA COLLECTOR DID NOT FIND ANY ADDRESS SPACE DATAExplanation: A real time request was made for data, but the KIPENV collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.








KIPA2703E THE KIPWRK DATA COLLECTOR DID NOT FIND ANY VSAM INFORMATIONExplanation: A real time request was made for data, but the KIPWRK collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Determine if the IMS system being monitored actually has VSAM information to display. Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.




KIPA2803E THE KIPCMP DATA COLLECTOR DID NOT FIND ANY ACTIVE DEVICE INFORMATIONExplanation: A real time request was made for data, but the KIPCMP collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA2814E ERROR nn GETTING GVT POINTERExplanation: The global vector table has not been allocated indicating that the tasks initialization has not completed.System Action: The system will either continue to initialize or it will continue to terminate.User Response: Make a copy of the entire RKLVLOG and contact Candle Support Services.

KIPA2821I THE COLLECTOR DID NOT FIND ANY ACTIVE DEVICES OR DEVICES IN AN ERROR STATEExplanation: A real time request was made for data, but the KIPCMP collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Only devices that are active at the time the sample was taken will be reported. This is a normal condition and does not require any user response.




KIPA2906E THE COLLECTOR DID NOT FIND A CONTROL REGION FOR THIS IMS SYSTEMExplanation: The ENV collector could not find the address space for the control region of the IMS system. This is either an internal error in the collector or an issue where the IMS system terminated and the autodiscovery code has not recognized that it has gone away yet.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.




KIPA3003E THE KIPWRK DATA COLLECTOR DID NOT FIND ANY TRANSACTION INFORMATIONExplanation: A real time request was made for data, but the KIPWRK collector responsible for gathering the data did not find any. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.




KIPA3122W THIS SYSTEM IS A DBCTL AND DOES NOT SUPPORT OTMAExplanation: This IMS system is a DBCTL type region and does not have any OTMA data to display. System Action: A row of data will be displayed indicating that OTMA is not available.User Response: None.


KIPA3106E THE COLLECTOR DID NOT FIND A CONTROL REGION FOR THIS IMS SYSTEMExplanation: The ENV collector could not find the address space for the control region of the IMS system. This is either an internal error in the collector or an issue where the IMS system terminated and the autodiscovery code has not recognized that it has gone away yet.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.



KIPA3203E THE KIPSPB DATA COLLECTOR DID NOT FIND ANY BUFFER POOL DATAExplanation: A real time request was made for data, but the KIPSPB collector responsible for gathering the data did not find any. This is an indication of an internal error.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.



KIPA3403E THE KIPSPB DATA COLLECTOR DID NOT FIND ANY SUBPOOL STATISTICS DATAExplanation: A real time request was made for data, but the KIPSPB collector responsible for gathering the data did not find any. This is an indication of an internal error.System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.



KIPA3429E UNABLE TO LOCATE PREVIOUS DATA FOR DELTA PROCESSINGExplanation: A request was made to return delta information based on the difference between counters at the last sample versus the current time. This message indicates that the previous sample could not be found. System Action: No data will be returned for this request and the CandleNet Portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPA3430E NO ELAPSED TIME BETWEEN CURRENT AND PREVIOUS SAMPLEExplanation: A request was made to return delta information based on the difference between counters at the last sample versus the current time. This message indicates that the time difference between them is zero.System Action: No data will be returned for this request and the CandleNet portal workspace will not display any data.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPAUT00I IMSPLEX AUTODISCOVERY STARTEDExplanation: The task to run autodiscovery has successfully started and is monitoring the system for IMS systems coming online or offline.System Action: Normal operation of autodiscovery logic continues.User Response: None.

KIPAUT01S IMSPLEX AUTODISCOVERY INITIALIZATION FAILEDExplanation: The task to run autodiscovery has not properly initialized. Other messages would have already displayed to indicate what type of errors were encountered during startup.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems. User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPAUT02E MULTIPLE IPDC AUTODISCOVERY COMMANDS ISSUEDExplanation: The IPDC AUTODISCOVERY command was executed more then one time. This command is used to start up the logic to monitor IMS systems. Once autodiscovery is started, there is no need to start it again.System Action: The request to start autodiscovery again is ignored.User Response: None.

KIPAUT03S UNABLE TO CREATE LOGICAL RESOURCEExplanation: The autodiscovery initialization code was attempting to create and reserve a resource in the Engine address space to prevent the shutdown of the address space until the autodiscovery code has had a chance to terminate. This error occurs when this resource could not be created.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPAUT04S UNABLE TO ACQUIRE LOGICAL RESOURCEExplanation: The autodiscovery initialization code was attempting to create and reserve a resource in the Engine address space to prevent the shutdown of the address space until the autodiscovery code has had a chance to terminate. This error occurs when this resource could not be reserved.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPAUT05S RESOURCE LOCK ERROR ERRNO=nnExplanation: A lock requested for the thread used to monitor the IMS systems failed. The error code returned by the Engine service is represented by the value of nn.System Action: Autodiscovery is terminated causing the product to be unable to detect or monitor any IMS systems.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPAUT10S CONTROL BLOCK ALLOCATION FAILED.Explanation: The allocation of storage for controlling autodiscovery has failed. This is fatal because the small amount of storage needed for controlling the autodiscovery logic is not available.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems.User Response: This is potentially an issue with MVS storage management. Contact your local systems.

KIPAUT11S CONDITION INITIALIZATION FAILED.Explanation: This is a fatal error for the autodiscovery initialization code. During start-up operations, the autodiscovery logic attempts to establish an independent thread to run in the Engine address space and fails to create the thread.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPAUT12S CONDITION MUTEX INITIALIZATION FAILED.Explanation: This is a fatal error for the autodiscovery initialization code. During start-up operations, the autodiscovery logic attempts to establish an independent thread to run in the Engine address space and fails to initialize the environment.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPAUT13S MUTEX INITIALIZATION FAILED.Explanation: This is a fatal error for the autodiscovery initialization code. During start-up operations, the autodiscovery logic attempts to establish an independent thread to run in the Engine address space and fails to initialize the independent thread.System Action: Autodiscovery is disabled causing the product to be unable to detect or monitor any IMS systems.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPAUT14E COMMAND=xxxxxx FAILED, STATUS=nnExplanation: The autodiscovery code was executing an IPDC command to either start or stop the monitoring of an IMS or IRLM system. The value of xxxxxx is the actual command string that was executed. The value of nn is the return code from the IPDC command that was attempted.System Action: The action intended by the command was not successful. The command was either set to start or stop the data collectors for the specified IMS or IRLM system. User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPAUT26I RESTART MONITORING FOR iMSIDExplanation: An IMS system that was marked as offline is being changed to online.System Action: Data collection will restart for the specified IMS system.User Response: None.

KIPAUT99I IMSPLEX AUTODISCOVERY SHUTDOWNExplanation: The address space which is running the autodiscovery logic is terminating. This message indicates that the tasks used for monitoring the IMS systems on this MVS LPAR have completed.System Action: Termination of the address space continues.User Response: None.

KIPBGV01I IP/I3 INITIALIZED, AUTODISCOVERY STARTEDExplanation: The startup routine has launched the autodiscovery initialization routine and has completed its work to get the collectors started.System Action: Collectors start functioning as IMS systems are detected.User Response: None.

KIPBGV02E IPDC REQUIRES APF AUTHORIZATION Explanation: The collectors and other modules required APF authorization to monitor the IMS systems. The initialization code has determined that this address space is not capable of running authorized programs.System Action: The product will not continue.User Response: Authorize the started task.

KIPBGV03E IPDC REQUIRES MVS/ESAExplanation: This product only runs in an MVS/ESA environment.System Action: The product will not run on this MVS system.User Response: Contact Candle Support Services.


KIPBGV04E IPDC UNABLE TO ACQUIRE STORAGE FOR GVTExplanation: The attempt to allocate storage for the product control block failed.System Action: The product will not run.User Response: This is potentially an issue with MVS storage management. Contact your local systems administrator.

KIPBGV07E IPDC description (xxxxxxxx) ROUTINE NOT FOUNDExplanation: The program identified by xxxxxxxx was not found in the module library. The description field indicates what the load module is used for. System Action: The system will attempt to continue, however the products ability to run will be based on which component is missing. User Response: Verify that the libraries pointed to for the started task are available and properly populated. Make a copy of the entire RKLVLOG and contact Candle Support Services.

KIPCOM00E Connect to KIP.IPFILTER for node failedExplanation: Unable to contact the HUB identified by node, in order to update Node Status and Node List tables. System Action: Attempt to update HUB tables is terminated.User Response: Contact Candle Support Services.

KIPCOM01E Failed inserting to KIP.IPFILTER for node, imsidExplanation: The update of the Node Status and Node List tables for HUB, identified by node of the IMS identified by imsid, failed. System Action: Attempt to update HUB tables is terminated.User Response: Contact Candle Support Services.

KIPCOM02E CreatePath error for IPFILTER, sqlStatus = statusExplanation: The path handle used to create request to the HUB could no be created. System Action: Attempt to update HUB tables is terminated.User Response: Contact Candle Support Services.

KIPCOM03E CreatePlan error for IPFILTER, sqlStatus = statusExplanation: Accessing the plan for the HUB failed. System Action: Attempt to update HUB tables is terminated.User Response: Contact Candle Support Services.

KIPCSQ01S CQSSSN subsys IMSID imsid INITIALIZATION FAILED – GETMAIN ERROR FOR C#CSQ CONTROL BLOCK. R15 = nnnnnnnnExplanation: The shared queues collector was unable to obtain storage for its internal C#CSQ control block. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the return code from the GETMAIN request (nnnnnnnn). System Action: The shared queues collector has failed to initialize and is unable to collect data from the shared queues.


User Response: The return code (R15) from the GETMAIN request is included in the message (nnnnnnnn). GETMAIN return codes are documented in the MVS Assembler Services Reference. This error is potentially an issue with MVS storage management. Contact your local systems administrator or Candle Support Services for assistance.

KIPCSQ02S CQSSSN subsys IMSID imsid INITIALIZATION FAILED - GETMAIN ERROR FOR QUEUE NAME BLOCKS. R15 = nnnnnnnnExplanation: The shared queues collector was unable to obtain storage for its queue name control blocks. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the return code from the GETMAIN request (nnnnnnnn).System Action: The shared queues collector has failed to initialize and is unable to collect data from the shared queues.User Response: The return code (R15) from the GETMAIN request is included in the message (nnnnnnnn). GETMAIN return codes are documented in the MVS Assembler Services Reference. This error is potentially an issue with MVS storage management. Contact your local systems administrator or Candle Support Services for assistance.

KIPCSQ03S CQSSSN subsys IMSID imsid CQS SUBSYSTEM NAME NOT PROVIDED FOR CQS VERSION 6Explanation: A CQS subsystem name was not provided in member KIPCQSID of the RKANPAR data set. A CQS subsystem name is required with CQS Version 6 for the indicated IMS system (imsid).System Action: The shared queues collector is unable to collect data from the shared queues.User Response: Verify that member KIPCSQID of the RKANPAR dataset specifies a valid CQS subsystem name for CQS Version 6.

KIPCSQ04E CQSSSN subsys IMSID imsid REGISTRATION BYPASSED - IMS NOT CONNECTED OR SHARED QUEUES NOT ACTIVEExplanation: The shared queues collector did not attempt to register to the indicated CQS subsystem (subsys) because either the CQS subsystem was not active or the indicated IMS system (imsid) was not connected to the CQS subsystem. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: Contact your IMS systems programmer for assistance to determine the status of the CQS and IMS address spaces.


KIPCSQ05E CQSSSN subsys IMSID imsid REGISTRATION FAILED - CQS ADDRESS SPACE IS NOT ACTIVEExplanation: The shared queues collector was unable to register to the CQS subsystem (subsys) for the indicated IMS system (imsid) because the CQS address space was not active. This error is output when the CQSREG request receives a return code of X’00000010’ and reason code of X’00000430’. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: The CQS address space must be started. Contact your IMS systems programmer for assistance.

KIPCSQ06E CQSSSN subsys IMSID imsid REGISTRATION FAILED. CQSREG RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to register to the CQS subsystem (subsys) for the indicated IMS system (imsid). The CQSREG request received the return code and reason code indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQSREG return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ07I CQSSSN subsys IMSID imsid REGISTRATION SUCCEEDED. CQSREG RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector has successfully been registered to the CQS subsystem (subsys) for the indicated IMS system (imsid).System Action: This is a normal initialization type operation for the shared queues collector.User Response: None.

KIPCSQ08E CQSSSN subsys IMSID imsid UNABLE TO CONNECT TO SHARED QUEUES - NO STRUCTURES TO CONNECT TOExplanation: The shared queues collector was unable to find any shared queues structures to connect to for the indicated CQS subsystem (subsys) and IMS system (imsid). This error is issued when field SQMSQSCT in the IMS Shared Queues Master Block (DFSSQM DSECT) is not greater than zero. Field SQMSQSCT contains a count of the structures. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: Contact your IMS systems programmer for assistance. If your IMS systems programmer indicates that there are structures and that this error is incorrect, please contact Candle Support Services who may request an SVC dump to be submitted.


KIPCSQ09E CQSSSN subsys IMSID imsid CQS INTERFACE ERROR ON CQSCONN REQUEST. R15/R0 = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to connect to the CQS subsystem (subsys) for the indicated IMS system (imsid). The CQS interface could not send the CQSCONN request to the CQS address space for the return code (R15) and reason code (R0) indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQS interface return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ10E CQSSSN subsys IMSID imsid CONNECT FAILED. CQSCONN RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to connect to the CQS subsystem (subsys) for the indicated IMS system (imsid). The CQSCONN request received the return code and reason code indicated in the message. If the return code is 8 and the reason code is in the range of X’00000300’ to X’00000400’, then the CQSCONN request failed for one or more structure list entries In this case, message KIPCSQ11E will be issued for each structure indicating the completion code received for the structure. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQSCONN return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ11E CQSSSN subsys IMSID imsid CONNECT COMPLETION CODE FOR STRUCTURE ssssssssssssssss IS nnnnnnnnExplanation: This message is output when message KIPCSQ10E is issued, indicating that the connect request received a return code of 8 and reason code in the range of X’00000300’ to X’00000400’. These reason codes indicate that the CQSCONN request failed for one or more structure list entries. In this case, message KIPCSQ11E is output for each structure to inform you of the CQSCONN completion code (nnnnnnnn) that the structure (ssssssssssssssss) received from the CQS subsystem (subsys) and indicated IMS system (imsid). System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQSCONN return and reason codes and structure completion codes (compcodes) can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.


KIPCSQ12I CQSSSN subsys IMSID imsid CONNECT SUCCEEDED. CQSCONN RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector has successfully connected to the CQS subsystem (subsys) for the indicated IMS system (imsid). System Action: This is a normal initialization type operation for the shared queues collector.User Response: None.

KIPCSQ13E CQSSSN subsys IMSID imsid CONNECT FAILED FOR STRUCTURE ssssssssssssssss WITH COMPLETION CODE nnnnnnnnExplanation: The shared queues collector was unable to connect to a structure. This message contains the CQSCONN completion code (nnnnnnnn) that the structure (ssssssssssssssss) received from the CQS subsystem (subsys) and indicated IMS system (imsid). System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQSCONN return and reason codes, and structure completion codes (compcodes) can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ14W CQSSSN subsys IMSID imsid CONNECT SUCCEEDED FOR UNKNOWN STRUCTURE ssssssssssssssss WHICH WILL BE IGNOREDExplanation: The shared queues collector connected to a structure that will not be processed since the structure is not a MSGQ (full function) structure or EMHQ (fast path) structure. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the name of the structure (ssssssssssssssss) that will be ignored. System Action: This is only a warning to inform you that data is not collected from the indicated structure.User Response: Determine the type of structure in question and contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ15E CQSSSN subsys IMSID imsid CQS INTERFACE ERROR ON CQSRSYNC FOR xxxx. R15/R0 = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to resync the MSGQ (full function) structure or EMHQ (fast path) structure for the CQS subsystem (subsys) and indicated IMS system (imsid). The CQS interface could not send the CQSRSYNC request to the CQS address space for the return code (R15) and reason code (R0) indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQS interface return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.


KIPCSQ16E CQSSSN subsys IMSID imsid RESYNC FAILED FOR xxxx. CQSRSYNC RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to resync the MSGQ (full function) structure or EMHQ (fast path) structure for the CQS subsystem (subsys) and indicated IMS system (imsid). The CQSRSYNC request received the return code and reason code indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQSRSYNC return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ17S CQSSSN subsys IMSID imsid DATASPACE ALLOCATION ERROR. DSPSERV RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to allocate the dataspace used to hold the shared queues data. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the return code and reason code from the DSPSERV request (nnnnnnnn/nnnnnnnn). System Action: The shared queues collector has failed to initialize and is unable to collect data from the shared queues. User Response: The return and reason codes from the DSPSERV request is included in the message. DSPSERV return and reason codes are documented in the MVS Assembler Services Reference. Contact your local systems administrator or Candle Support Services for assistance.

KIPCSQ18S CQSSSN subsys IMSID imsid ALET ERROR FOR DATASPACE. ALESERV RETURN CODE = nnnnnnnnExplanation: The shared queues collector was unable to acquire an ALET for the dataspace used to hold the shared queues data. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the return code from the ALESERV request (nnnnnnnn). System Action: The shared queues collector has failed to initialize and is unable to collect data from the shared queues. User Response: The return code from the ALESERV request is included in the message. ALESERV return codes are documented in the MVS Assembler Services Reference. Contact your local systems administrator or Candle Support Services for assistance.

KIPCSQ41S CQSSSN subsys IMSID imsid SHARED QUEUES C#CSQ CONTROL BLOCK IS INVALID. R9 = nnnnnnnnExplanation: The shared queues collector internal C#CSQ control block is invalid. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the address (R9 = nnnnnnnn) of the invalid C#CSQ control block. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: This is an internal product error. Contact Candle Support Services for assistance.


KIPCSQ51E CQSSSN subsys IMSID imsid CQS INTERFACE ERROR ON rrrrrrrr FOR qqqqqqqq. R15/R0 = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to issue a CQS request for the CQS subsystem (subsys) and indicated IMS system (imsid). The CQS interface could not send request rrrrrrrr for queue qqqqqqqq to the CQS address space for the return code (R15) and reason code (R0) indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQS interface return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ52W CQSSSN subsys IMSID imsid PARTIAL ddddddddddd DATA RETURNED FOR COLLECTION CYCLE AS qqqqqqqq IS BUSY – Explanation: Partial transaction or LTERM data was returned for this collection cycle as heavy activity is occurring on the indicated queue. Heavy activity means that the number of queues is growing very rapidly between CQSQUERY requests and as a result the buffer size required to hold the data returned by CQSQUERY keeps increasing on each request. This message identifies the CQS subsystem (subsys), IMS system (imsid), type of data (ddddddddddd), which is either transaction or LTERM queue and the queue type (qqqqqqqq). System Action: The shared queues collector continues processing, however, transaction or LTERM data may be missing from the shared queues reports. Complete data will be available in a subsequent collection cycle as indicated by the follow-on message, KIPCSQ53W.User Response: Contact your IMS systems programmer to determine why the indicated queue is growing at such a rapid pace. If this message is received frequently, please contact Candle Support Services for assistance.

KIPCSQ53W CQSSSN subsys IMSID imsid COMPLETE ddddddddddd DATA AVAILABLE IN SUBSEQUENT COLLECTION CYCLEExplanation: This is a follow-on message to KIPCSQ52W to inform you that complete transaction or LTERM data will be available in a subsequent cycle when the queue is not as busy. This message identifies the CQS subsystem (subsys), IMS system (imsid), and the type of data (ddddddddddd), which is either transaction or LTERM queue data.System Action: See message KIPCSQ52W.User Response: See message KIPCSQ52W.

KIPCSQ54S CQSSSN subsys IMSID imsid GETMAIN FAILED FOR qqqqqqqq NAME BLOCKS. R15 = nnnnnnnnExplanation: The shared queues collector was unable to obtain storage for the queue name control blocks. This message identifies the CQS subsystem (subsys), IMS system (imsid), queue name (qqqqqqqq), and the return code from the GETMAIN request (nnnnnnnn). System Action: The shared queues collector is unable to collect data from the shared queues data.


User Response: The return code in R15 from the GETMAIN request is included in the message (nnnnnnnn). GETMAIN return codes are documented in the MVS Assembler Services Reference. This error is potentially an issue with MVS storage management. Contact your local systems administrator or Candle Support Services for assistance.

KIPCSQ55E CQSSSN subsys IMSID imsid rrrrrrrr REQUEST FAILED FOR qqqqqqqq. RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to issue a CQS request for the CQS subsystem (subsys) and indicated IMS system (imsid). CQS request rrrrrrrr for queue qqqqqqqq received the return code and reason code indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: Return and reason codes for CQS requests can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ56E CQSSSN subsys IMSID imsid CQSBRWSE CONTINUE FAILED FOR qqqqqqqq. RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to issue a CQSBRWSE request for the CQS subsystem (subsys) and indicated IMS system (imsid). The CQSBROWSE FUNC=CONTINUE request received the return code and reason code indicated in the message. System Action: The shared queues collector is unable to collect data from the shared queues.User Response: CQSBRWSE return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ91E CQSSSN subsys IMSID imsid CQS INTERFACE ERROR ON CQSDISC REQUEST. R15/R0 = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector was unable to disconnect from the CQS subsystem (subsys) for the indicated IMS system (imsid). The CQS interface could not send the CQSDISC request to the CQS address space for the return code (R15) and reason code (R0) indicated in the message. System Action: The shared queues collector was unable to properly terminate. User Response: CQS interface return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance


KIPCSQ92E CQSSSN subsys IMSID imsid DISCONNECT FAILED. CQSDISC RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector is unable to disconnect from the CQS subsystem (subsys) for the indicated IMS system (imsid). The CQSDISC request received the return code and reason code indicated in the message. System Action: The shared queues collector was unable to properly terminate. User Response: CQSDISC return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ93I CQSSSN subsys IMSID imsid DISCONNECTED FROM SHARED QUEUES. RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector has successfully disconnected from the CQS subsystem (subsys) for the indicated IMS system (imsid). System Action: This is a normal operation that occurs when the shared queues collector is terminating.User Response: None.

KIPCSQ94E CQSSSN subsys IMSID imsid DEREGISTER FAILED. CQSDEREG RETURN/REASON CODES = nnnnnnnn/nnnnnnnnExplanation: The shared queues collector is unable to deregister from the CQS subsystem (subsys) for the indicated IMS system (imsid). The CQSDEREG request received the return code and reason code indicated in the message. System Action: The shared queues collector was unable to properly terminate.User Response: CQSDEREG return and reason codes can be found in the IBM Common Queue Server and Base Primitive Environment Guide and Reference. Contact your IMS systems programmer or Candle Support Services for assistance.

KIPCSQ95I CQSSSN subsys IMSID imsid DEREGISTERED FROM SHARED QUEUES. RETURN/REASON CODES = nnnnnnnn/nnnnnnnn Explanation: The shared queues collector has successfully deregistered from the CQS subsystem (subsys) for the indicated IMS system (imsid). System Action: This is a normal operation that occurs when the shared queues collector is terminating.User Response: None.

KIPDCI01E NO MATCHING KIPCNFG PARMS FOR tttt(iiii)Explanation: There were no matching parameters in the KIPCNFG member of the RKANPAR dataset for the IMS or IRLM system (tttt) and indicated system identifier (iiii).System Action: The indicated system will not be monitored; no data collectors will be started for the indicated system. User Response: If the indicated system is to be monitored, modify member KIPCNFG so that all collectors or selected collectors are specified for the system.


KIPDCI03S UNABLE TO ALLOCATE MEMORY FOR ANCHORExplanation: Unable to acquire storage for the internal anchor block. System Action:System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: This is potentially an issue with MVS storage management. Contact your local systems administration or Candle Support Services for assistance.

KIPDCI04E NO DATA COLLECTORS SPECIFIED FOR tttt(iiii)Explanation: Matching parameters were found for the IMS or IRLM system (tttt) in the KIPCNFG member of the RKANPAR dataset for the indicated system identifier (iiii), however, there were no collectors specified. System Action: The indicated system will not be monitored since no data collectors were specified. User Response: If the indicated system is to be monitored, at least one collector must be specified in member KIPCNFG of the RKANPAR dataset.

KIPDCI05I RKANPAR(KIPCQSID) MEMBER EMPTYExplanation: This message can be ignored if you are using CQS Version 7 or higher, as member KIPCQSID of the RKANPAR dataset is not used. Member KIPCQSID cannot be empty for CQS Version 6. For CQS Version 6, member KIPCQSID of the RKANPAR dataset must provide a CQS subsystem name in order to collect data from shared queues.System Action: For CQS Version 6, the shared queues collector will fail to initialize and no data will be collected from the shared queues. User Response: For CQS Version 6 only, provide a CQS subsystem name in member KIPCQSID of the RKANPAR dataset.

KIPDCI06I RKANPAR(KIPCQSID) NOT FOUNDExplanation: This message can be ignored if you are using CQS Version 7 or higher, as member KIPCQSID of the RKANPAR dataset is not used. Member KIPCQSID must be provided for CQS Version 6. For CQS Version 6, member KIPCQSID of the RKANPAR dataset must provide a CQS subsystem name in order to collect data from shared queues.System Action: For CQS Version 6, the shared queues collector will fail to initialize and no data will be collected from the shared queues. User Response: For CQS Version 6 only, provide a CQS subsystem name in member KIPCQSID of the RKANPAR dataset.

KIPDCI07E UNABLE TO ALLOCATE KIPCNFG PARM BLOCKExplanation: Unable to acquire storage for the internal KIPCNFG parameter block. System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: This is potentially an issue with MVS storage management. Contact your local systems administration or Candle Support Services for assistance.


KIPDCI08E INVALID SUBSYSTEM TYPE=’tttt…’Explanation: The subsystem type (tttt…) specified in the KIPCNFG member of the RKANPAR dataset is invalid. Valid subsystem types are IMS or IRLM. System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: Correct the subsystem type specified in the KIPCNFG member of the RKANPAR dataset. The only valid subsystem types are IMS or IRLM.

KIPDCI09E INVALID SUBSYSTEM ID=’iiii…’Explanation: The subsystem identifier (iiii…) specified in the KIPCNFG member of the RKANPAR dataset is invalid. The subsystem identifier must have a length of 1 to 4 characters. System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: Correct the subsystem identifier specified in the KIPCNFG member of the RKANPAR dataset to ensure that it has a proper length.

KIPDCI10E INVALID COLLECTOR=’cccccccc…’ SPECIFIEDExplanation: The collector name (cccccccc…) specified in the KIPCNFG member of the RKANPAR dataset is invalid. Valid IRLM collector names are CONFLICT and COUPFAC. Valid IMS collector names are DATASHAR, IMSENV, IMSPARMS, MQSTAT, MSC, OSAMSHAR, POOLS, RESOURCE, RTAGRP, RTAITEM, SHAREDQ, and WORKLOAD. System Action: The invalid collector name is not processed for the IMS or IRLM system. User Response: Correct the collector name specified in the KIPCNFG member of the RKANPAR dataset to ensure that it valid.

KIPDCI11E ERROR OPENING RKANPAR(KIPCNFG)Explanation: An attempt to open the RKANPAR dataset for member KIPCNFG failed. System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: Contact Candle Support Services for assistance

KIPDCI12E UNEXPECTED EOF IN RKANPAR(KIPCNFG)Explanation: While processing a continuation statement in member KIPCNFG of the RKANPAR dataset, end of file was unexpectedly reached. System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: Correct the statements in member KIPCNFG of the RKANPAR dataset to remove the continuation statement if in error or provide an additional statement continuing your parameters.


KIPDCI13W INVALID INTERVAL FOR tttt(iiii) cccccccc IGNOREDExplanation: An invalid interval value was specified in the KIPCNFG member of the RKANPAR dataset for the indicated collector (cccccccc), IMS or IRLM system (tttt), and system identifier (iiii).System Action: The interval value will be ignored for the collector and system indicated in the message, and a default interval value of 30 seconds will be used. User Response: If the default is not desired, correct the interval specification for the indicated collector and system in member KIPCNFG of the RKANPAR dataset.

KIPDCI14S NO SUBSYSTEMS ENABLED IN RKANPAR(KIPCNFG) Explanation: Member KIPCNFG of the RKANPAR dataset does not provide any subsystem identifiers to monitor.System Action: Processing is terminated and no IMS or IRLM systems can be monitored. User Response: Ensure that member KIPCNFG of the RKANPAR dataset specifies at least one subsystem to monitor.

KIPDSP00I MONITORED SUBSYSTEMS: Explanation: This is an informational message output from the IPDC DISPLAY command indicating that you have requested information about your monitored systems. Several informational messages will follow this message to provide information about the IMS and IRLM systems being monitored and their status. Explanation: None. System Action: None.

KIPDSP01I IRLM(iiii) STATE=ssssssssss COLLECTORS: Explanation: This is an informational message output from the IPDC DISPLAY command that provides information about the IRLM system (iiii) being monitored and its state or status (ssssssssss). System Action: None. User Response: Informational messages are useful in diagnosing the status of your monitored systems. Action may be required if the status of the system is not as you intended. Contact Candle Support Services for assistance.

KIPDSP02I IMS(iiii) STATE=ssssssssss COLLECTORS: Explanation: This is an informational message output from the IPDC DISPLAY command that provides information about the IMS system (iiii) being monitored and its state or status (ssssssssss). System Action: None. User Response: Informational messages are useful in diagnosing the status of your monitored systems. Action may be required if the status of the system is not as you intended. Contact Candle Support Services for assistance.


KIPDSP03I cccccccc(nnnn) cccccccc(nnnn) . . . Explanation: This is an informational message output from the IPDC DISPLAY command and follows message KIPDSP01I or KIPDSP02I. The text of the message lists the names of the collectors (cccccccc) and the interval being used (nnnn). System Action: None. User Response: Informational messages are useful in diagnosing the data collectors being used and the interval specified for the monitored system. Action may be required if the information is not as you intended. Contact Candle Support Services for assistance.

KIPDSP99I nn SUBSYSTEMS DISPLAYED Explanation: This is an informational message output from the IPDC DISPLAY command that indicates the number (nn) of subsystems that have been displayed. This is the last message output from the IPDC DISPLAY command.System Action: None. User Response: None.

KIPFIL00E InsertIPfilter call returned with statusExplanation: The attempt to insert IMS into the HUB filter table failed. System Action: Attempt to update HUB tables is terminated.User Response: Contact Candle Support Services.

KIPHUB00E GVT NOT FOUNDExplanation: The IPFILTER function failed to obtain a global vector table.System Action: Processing continues without the ability to perform node status.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPHUB01E REGISTRATION FAILEDExplanation: The IPFILTER function failed to obtain the application vector table.System Action: Processing continues without the ability to perform node registration. User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPHUB02S LOAD OF MMMMMMMM FAILEDExplanation: The IPFILTER function could not be loaded.System Action: Processing continues without the ability to perform node registration. The load module that failed to load is represented by the value of MMMMMMMM.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPHUB03I IPDC PHASE 1 TERMINATION COMPLETEExplanation: This indicates the first phase of termination processing has completed.System Action: Termination processing continues. User Response: None.

KIPINI01E IPDC VECTOR TABLE NOT FOUNDExplanation: The initialization startup routine failed to obtain a global vector table.System Action: Processing continues without the ability to perform node registration. User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPIRA01I SETTING SUB-NODE node TO ONLINEExplanation: The node value will be the origin node generated on behalf of a monitored IMS system. The format of the node is imsid:smfid:IMS. The ONLINE status indicates that autodiscovery code located an active IMS system and is making it available for monitoring by the CandleNet Portal.System Action: The IMS system identified by the node field is being enabled for monitoring.User Response: None.

KIPIRA02I SETTING SUB-NODE node TO OFFLINEExplanation: The node value will be the origin node generated on behalf of a monitored IMS system. The format of the node is imsid:smfid:IMS. The OFFLINE status indicates that autodiscovery code located an active IMS system that is not enabled for monitoring.System Action: The IMS system identified by the node field is being disabled for monitoring.User Response: None.


KIPIRA03I ADDING NEW ONLINE SUBNODE FOR ORIGIN NODE nodeExplanation: This message is generated when a new IMS system is detected after the monitoring agent has been started. It is functionally equivalent to message KIPIRA01I. The node value will be the origin node generated on behalf of a monitored IMS system. The format of the node is imsid:smfid:IMS.System Action: The IMS system identified by the node field is being enabled for monitoring.User Response: None.

KIPIRA04I ADDING NEW OFFLINE SUBNODE FOR ORIGIN NODE nodeExplanation: This message is generated when a new IMS system is detected after the monitoring agent has been started. It is functionally equivalent to message KIPIRA02I. The node value will be the origin node generated on behalf of a monitored IMS system. The format of the node is imsid:smfid:IMS.System Action: The IMS system identified by the node field is being disabled for monitoring.User Response: None.

KIPIRA05I CHANGING STATUS OF NODE node TO ONLINEExplanation: The IMS node identified by node is having its status changed to ONLINE. The message is generated when a node that was marked as offline is changed to online.System Action: The IMS system identified by the node field is being enabled for monitoring.User Response: None.

KIPIRA06I CHANGING STATUS OF NODE node TO OFFLINEExplanation: The IMS node identified by node is having its status changed to OFFLINE. The message is generated when a node that was marked as online is changed to offline.System Action: The IMS system identified by the node field is being disabled for monitoring.User Response: None

KIPKFA00E InsertNodeAtHub call returned with statusExplanation: The attempt to insert IMS status into the HUB Node Status table failed. System Action: Attempt to update HUB tables is terminated.User Response: Contact Candle Support Services.

KIPLOK50E Data server parameter list not foundExplanation: The attempt to retrieve the CT/DS parameter list failed. System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK51E Unable to locate pWorkA work areaExplanation: The view storage pointer could not be located. System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.


KIPLOK52E Unable to allocate Storage for LOKA resultExplanation: Unable to allocate storage for the output list for the lock data records.System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK53E Unable to allocate Storage for LIKE Node resultExplanation: The attempt to allocate storage for the output list of the origin node records failed.System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK54E Unable to allocate Storage for AtNode resultExplanation: The attempt to allocate storage for the output list of the real node records failed.System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK55E Unable to obtain lock result recordExplanation: An error occurred when retrieving a lock results record.System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK56E Unable to close request for inputExplanation: An attempt to do an SQL close failed. System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK57E Unable to open request for inputExplanation: An attempt to do an SQL open failed. System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK58E Unable to drop requestExplanation: An attempt to do an SQL drop failed. System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.

KIPLOK59E Unable to create select request pathExplanation: An attempt to create a SQL select path failed. System Action: The Global Locks Conflicts meta probe execution terminates.User Response: Contact Candle Support Services.


KIPMCB01E IPDC UNABLE TO START COLLECTOR FOR IRLM irlmnameExplanation: This message should not occur. An internal condition did not permit the IRLM data collector to begin processing.System Action: Processing will continue without the IRLM collector. User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPMCB02E IPDC GLOBAL VECTOR TABLE NOT FOUNDExplanation: This message should not occur. The IRLM collector was unable to locate it's Global Vector Table.System Action: Processing will continue without the IRLM collector. User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPMCB03W THE MONITORED IRLM IS AT AN UNSUPPORTED RELEASE LEVELExplanation: The IRLM data collector has located an IRLM, but it will not be monitored because it is not at a supported release level.System Action: Processing will continue without the IRLM collector for this IRLM. Processing is bypassed for the indicated IRLM. Otherwise processing will continue normally. User Response: Verify that the release level of the IRLM to be monitored is supported by the current release level of the XE IMSplex product.

KIPMCB04I IPDC LOCATED MCB, FOR IRLM irlmname AT ADDRESS addressExplanation: This informational message shows the virtual storage address of the MCB for given IRLM.System Action: Processing continues normally. User Response: Nothing required.

KIPMCB05W MCB FOR IRLM irlmname IS NOT FOUND OR MCB NOT VALIDExplanation: OMEGAMON XE could not locate or validate the MCB for the given IRLM. System Action: Processing is bypassed for the indicated IRLM. Otherwise processing will continue normally. User Response: Verify that the given IRLM has been started and fully initialized before contacting Candle Support Services.

KIPMCB06W JES CVT NOT FOUNDExplanation: This should not occur. System Action: Processing will continue without the IRLM collector. User Response: Rerun OMEGAMON XE later, after the JES CVT has been built by JES.


KIPMCB07W NO SUBSYSTEMS FOUNDExplanation: This should not occur. System Action: Processing will continue without the IRLM collector. User Response: Rerun OMEGAMON XE later, after the JES SSCT has been built by JES.

KIPOIC01E IPDC GLOBAL VECTOR TABLE NOT FOUNDExplanation: The primary control block used by the product was not found where it was suppose to be. System Action: The interface to the OMEGAMON classic product will not be initialized and monitoring of the IMS system will fail.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPOIC02E IPDC SCD SCAN (xxxxxxxx) ROUTINE NOT FOUNDExplanation: The program identified by xxxxxxxx was not found in the module library.System Action: The interface to the OMEGAMON classic product will not be initialized and monitoring of the IMS system will fail.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPOIC03W IPDC UNABLE TO LOCATE OI FOR IMS imsidExplanation: The IMS system identified in the message currently does not have an OI product running which monitors the IMS.System Action: Until the OI interface is started, the data collectors for the product will not start until the classic interface is enabled.User Response: Start up the OMEGAMON classic interface to start monitoring the IMS system.

KIPOIC04I IPDC WILL RETRY EVERY 10 SECONDSExplanation: This is an informational message to indicate that the OI interface will be tested every 10 seconds until the OI interface has started.System Action: The system waits for 10 seconds and once again checks for the OI interface being activated. The waiting and checking will continue until the OI interface is established. However, the message will only be generated once.User Response: Start up the OMEGAMON classic interface to start monitoring the IMS system.


KIPPRB00E xxxxxxxx CANNOT GET WORKA STORAGEExplanation: The program indicated by xxxxxxxx could not get the necessary work area storage during initialization processing.System Action: Termination of the program is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB01E xxxxxxxx PUT_PARM FAILURE FOR WORKAExplanation: The program indicated by xxxxxxxx could not register the work area with the data server during initialization processing.System Action: Termination of the program is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB03E xxxxxxxx GET_PARM FOR INDEX FAILEDExplanation: The program indicated by xxxxxxx was unable to acquire the index value used in the processing of row data.System Action: Termination of the program is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB05E xxxxxxxx PUT_PARM FOR ROW DATA FAILEDExplanation: The program indicated by xxxxxxx was unable to emit a row of data.System Action: Termination of the collection sample is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB07E xxxxxxxx UNKNOWN ROW DATA ERROR Explanation: The program indicated by xxxxxxx was unable to acquire the an expected row of data.System Action: Termination of the collection sample is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPPRB08E KIPILOKL SAMPLE_SETUP GET CCB ERRORExplanation: An attempt to acquire an address array for a control block was unsuccessful.System Action: Termination of the collection sample is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB09E KIPILOKL CANNOT GET RTR STORAGEExplanation: An attempt to acquire storage for RTR was unsuccessful.System Action: Termination of the collection sample for is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB10E KIPILOKL RTR REMCHAIN ENTRY NOT FOUNDExplanation: An attempt to remove an entry from the work request queue was not found.System Action: The program returns to the caller and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB11E KIPILOKL GET CTINDEX FAILEDExplanation: The program was unable to acquire the index value used in the processing of row data at sample setup time.System Action: Termination of the program is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.

KIPPRB12E KIPILOKL CCB ADDR NOT FOUNDExplanation: An attempt to acquire an address array for a control block was unsuccessful at sample setup time.System Action: Termination of the collection sample is scheduled and normal processing continues.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPPRB13I KIPILOKL SHUTDOWN DETECTEDExplanation: The program detected a shutdown during normal processing.System Action: Termination of the collection sample is scheduled and termination processing continues.User Response: None.

KIPSQL00E Create Path failed with statusExplanation: An attempt to create a path to CT/DS failed. System Action: Program terminates and returns caller with error status.User Response: Contact Candle Support Services.

KIPSQL01E Create Access Plan failed with statusExplanation: The access plan to the Data Server failed to be created. System Action: Program terminates and access to the data servers was not completed.User Response: Contact Candle Support Services.

KIPSQL02E GetInputSQLDA failed with statusExplanation: A lower level product component failed on a SQL request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL03E Create Request failed with status Explanation: A lower level product component failed on a SQL Create request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL04E OpenRequest failed with statusExplanation: A lower level product component failed on a SQL Open request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL05E Drop request incorrectly called with closed pathExplanation: A lower level product component failed on a SQL Drop request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.


KIPSQL06E Drop reqHdl failed with statusExplanation: A lower level product component failed on a SQL Drop request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL07E Drop planHdl failed with statusExplanation: A lower level product component failed on a SQL Drop request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL08E Drop pathHdl failed with statusExplanation: A lower level product component failed on a SQL Drop request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL09E OpenRequest returned with statusExplanation: A lower level product component failed on a SQL Open request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL10E GetOutputSQLDA request returned with statusExplanation: A lower level product component failed on a SQL request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQL11E CloseRequest returned with statusExplanation: A lower level product component failed on a SQL Close request with status. System Action: Control is returned to program requesting the SQL service with an indication an error has occurred. User Response: Contact Candle Support Services.

KIPSQS00E Unable to obtain group result record Explanation: An attempt to get a Shared Queue group record for summarization failed. System Action: The meta probe program is exited. User Response: Contact Candle Support Services.


KIPSQS01E Unable to obtain group result record *ALLExplanation: An attempt to get summarization group record for *ALL failed.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSQS02E Unable to close request for input statusExplanation: The SQL close request for a group did not successfully complete. The value status is the resulting SQL error status.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSQS03E Unable to open request for input statusExplanation: The SQL open request for a group did not successfully complete. The value status is the resulting SQL error status.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSQS04E Unable to drop request statusExplanation: The SQL Drop request for a group did not successfully complete. The value status is the resulting SQL error status.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSQS05E Unable to create select request path statusExplanation: The value status is the resulting SQL error status.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSQS06E Data server parameter list not foundExplanation: An attempt to get the PARMLIST from CT/DS failed.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSQQ07E Unable to locate pWorkA work areaExplanation: An attempt to get the pointer to the previous view storage failed.System Action: The meta probe program is exited. User Response: Contact Candle Support Services.

KIPSRV42E IRA REGISTRATION THREAD ALREADY ACTIVEExplanation: An attempt is being made to restart the registration process after it had already been started. The current attempt to start the registration thread will fail. The most likely cause of this error is an attempt to restart the monitoring agent without first terminating the active agent.System Action: The current thread will terminate, however the registration process will continue using the previously started thread.User Response: Gather diagnostic information and call Candle Support Services. See the “Problem Determination for OMEGAMON XE for IMS and IMSplex Products” appendix, located in Volume 5 of this manual, for the details on gathering the diagnostic information.


KIPSRV43E IRA REGISTRATION THREAD IS NOT ACTIVEExplanation: An attempt to stop the registration process failed to find the thread. This could happen if the agent was requested to terminate when it was not previously started.System Action: The request is terminated since there is nothing to do.User Response: None.

KIPSRV45E IRA REGISTRATION THREAD IS NOT RESPONDINGExplanation: An attempt to stop the registration process failed to obtain verification that the termination completed.System Action: The system continues its termination process.User Response: None.

KIPSRV46I IRA REGISTRATION THREAD IS ACTIVEExplanation: This is a notification that an independent thread has been activated to monitor node registration for the Intelligent Remote Agent.System Action: The agent package will periodically wake up and determine if autodiscovery has found any new systems to be monitored.User Response: None

KIPSRV47I IRA REGISTRATION THREAD IS TERMINATINGExplanation: This is a notification that an independent thread has been called for the purpose of terminating its activity. This call occurs when the agent is requested to stop or shutdown.System Action: The agent package will stop checking for changes detected by the autodiscovery code.User Response: None.

KIPSTA01I IMSPLEX GVT ADDRESS: addressExplanation: In response to an IPSTATUS command the IMSPLEX GVT control block virtual address is displayed.System Action: The GVT virtual address is written to RKVLOG. User Response: None.

KIPSTA02I IMSPLEX GVT NOT FOUNDExplanation: In response to an IPSTATUS command the IMSPLEX GVT control block could not be located.System Action: The IPSTATUS command terminates. User Response: None.

KIPSTA03E IPSTATUS COMMAND ERRORExplanation: One of the parameters to the IPSTATUS command was in error.System Action: The IPSTATUS command terminates. User Response: None.


KIPSTA04I IMSPLEX AVT ADDRESS FOR imsid : addressExplanation: In response to an IPSTATUS command the IMSPLEX AVT control block virtual address is displayed for imsid.System Action: The AVT virtual address is written to RKVLOG. User Response: None.

KIPSTA05I NO IMSPLEX MONITORS STARTED\Explanation: In response to an IPSTATUS command the IPSTATUS command processor could not find any IMSPLEX monitors. This message should not occur.System Action: The IPSTATUS command terminates. User Response: None.

KIPSTA06I IMSPLEX CCB ADDRESS FOR Explanation: In response to an IPSTATUS command the IMSPLEX CCB control block virtual address is displayed for imsid.System Action: The CCB virtual address is written to RKVLOG. User Response: None.

KIPSTA07I NO IMSPLEX COLLECTORS STARTEDExplanation: In response to an IPSTATUS command the IPSTATUS command processor could not find any IMSPLEX monitors. This message should not occur.System Action: The IPSTATUS command terminates. User Response: None.

KIPTRM01E IPDC TERMINATING. REASON CODE reason codeExplanation: IMSPLEX is terminating before start up is complete.System Action: Termination continues. User Response: None.

KIPTRM02E IPDC PHASE 1 TERMINATION COMPLETEExplanation: The GVT has been unchained from the SSCVT and the collectors have been posted to terminate.System Action: Termination continues. User Response: None.

KIPTRM03E IPDC PHASE 2 TERMINATION COMPLETEExplanation: The collectors have terminated and the GVT has been freed. System Action: Termination continues. User Response: None.

KLCCI001 CLUSTER INITIAL LOAD FAILED, SERVICE (service), RC (rc)Explanation: CL/CONFERENCE cannot complete the initialization process for the conference log dataset. service is the failing service name and rc is the return code from the failing service.System Action: CL/CONFERENCE initialization is terminated.User Response: Refer to the IBM VSAM Programmer’s Guide for the details of the failing service. Correct the problem and restart CL/CONFERENCE.Severity: WARNING.


KLCIN001 CL/CONFERENCE VERSION 141 INITIALIZATION COMPLETEExplanation: CL/CONFERENCE Version 141 has completed initialization.System Action: CL/CONFERENCE is ready for use once CL/ENGINE initialization is completed.User Response: None.Severity: INFO.

KLCIN002 UNABLE TO LOAD VIRTUAL CL/CONFERENCE COMPONENT: moduleExplanation: CL/CONFERENCE is unable to load the required component module. This error is usually caused by the absence of module from the CL/CONFERENCE load library.System Action: CL/CONFERENCE initialization is terminated.User Response: Look for additional information in messages displayed in the KLVCMnnn format. Correct the error and restart CL/CONFERENCE.Severity: ALERT.

KLCIN003 parametersExplanation: The message displays the parameters contained in the initialization member KLCINVCN.System Action: None.User Response: None.Severity: LOG.

KLCIN004 CONFERENCE LOG DATASET INACCESSIBLE, NO VSAM LSR RESOURCE: DSNAME (dsname)Explanation: CL/CONFERENCE is unable to process the conference log dataset because no VSAM LSR environment has been established.System Action: CL/CONFERENCE initialization is terminated.User Response: Examine the console log or the CL/ENGINE RKLVLOG for KLVVSnnn messages that explain the VSAM problem. Correct the error and then restart CL/CONFERENCE.Severity: WARNING.

KLCIN005 CONFERENCE LOG DATASET ALLOCATION FAILED: DSNAME (dsname)Explanation: CL/CONFERENCE is unable to allocate the dataset dsname.System Action: CL/CONFERENCE initialization is terminated.User Response: Examine the console log or the CL/ENGINE RKLVLOG for KLVDAnnn messages that explain the allocation problem. Correct the error and then restart CL/CONFERENCE.Severity: WARNING.

KLCIN006 CONFERENCE #FVT ADDR: xxxxxxxxExplanation: The CL/CONFERENCE vector table has been established at the hex address xxxxxxxx.System Action: None.User Response: None.Severity: INFO.


KLCIN007 CL/CONFERENCE VERSION 141 INITIALIZATION FAILEDExplanation: CL/CONFERENCE Version 141 is unable to complete the initialization process.System Action: CL/CONFERENCE initialization is terminated.User Response: Examine the console log or the CL/ENGINE RKLVLOG for error messages that explain the failure. Correct the error and then restart CL/CONFERENCE.Severity: ALERT.

KLCOP001 CSHOW ARGUMENT LIST: CNFID (conference) USER (userid)Explanation: This is a confirmation display of your input.System Action: The command is processed.User Response: None.Severity: REPLY.

KLCOP006 cnfuser OF cnftuser USER(S) SELECTEDExplanation: This information message lists the number of conference users being selected by the CSHOW command.System Action: None.User Response: None.Severity: REPLY.

KLCOP007 userid (termid, confrole)Explanation: This information message displays the conference user ID and the associated physical terminal ID and conference role (moderator, presenter, attendee, or participant).System Action: None.User Response: None.Severity: REPLY.

KLCOP008 confid (type, permission, join-notification, participant-status)Explanation: This information message displays the conference ID with the conference type (PRIVATE or PUBLIC), permission status (PERM or NOPERM), join-notification status (NOTEJN or NONOTEJN), and participant keyboard status (RESTRICT, OPEN, or SELECTIVE).System Action: None.User Response: None.Severity: REPLY.

KLCOP009 cnf OF tcnf CONFERENCE(S), cnfuser OF cnftuser USER(S) SELECTEDExplanation: This information message lists the number of conferences and the number of conference users being selected by the CSHOW command.System Action: None.User Response: None.Severity: REPLY.


KLCOP011 CANCEL ARGUMENT LIST: CNFID (conference) USER (userid)Explanation: This is a confirmation display of your CCANCEL command.System Action: The command is processed.User Response: None.Severity: REPLY.

KLCOP019 cancelled OF total CONFERENCE(S), cancelled OF total USER(S) CANCELLEDExplanation: This message lists the number of conferences and users cancelled by the CCANCEL command.System Action: None.User Response: None.Severity: REPLY.

KLECF001 LONGJMP ENCOUNTERED UNCROSSABLE BOUNDARYExplanation: During LONGJMP processing a condition forbidding the LONGJMP function was detected.System Action: The thread is abended.User Response: Contact Candle Customer Support with the dump associated with this message.Message Type: ABEND.

KLECF002 LONGJMP UNABLE TO LOCATE ENVIRONMENTExplanation: During LONGJMP processing it was determined that the LONGJMP environment was no longer intact.System Action: The thread is abended.User Response: Contact Candle Customer Support with the dump associated with this message.Message Type: ABEND.

KLECF003 JMPBDSA IS NULLExplanation: During LONGJMP processing it was determined that the LONGJMP buffer chain has been exhausted.System Action: The thread is abended.User Response: Contact Candle Customer Support with the dump associated with this message.Message Type: ABEND.

KLECF011 UNABLE TO ALLOCATE ACB: APPLID(applid)Explanation: An error occurred while attempting to allocate an ACB for applid.System Action: The ACB is not allocated.User Response: Contact Candle Customer Support.Message Type: ERROR.


KLECF012 UNABLE TO OPEN ACB: APPLID(applid) REASON(reason)Explanation: An error occurred while attempting to open an ACB for applid. reason is the reason code returned from open.System Action: The ACB is not opened.User Response: The REASON field contains the return code from the ACF/VTAM™ OPEN macro instruction. Refer to the IBM manual ACF/VTAM Programming to determine the cause of the error.Message Type: ERROR.

KLECF013 APPLICATION appl STARTEDExplanation: Application appl was successfully started.System Action: None.User Response: None.Message Type: REPLY, INFO.

KLECF014 APPLICATION appl STOPPEDExplanation: Application appl was successfully stopped.System Action: None.User Response: None.Message Type: REPLY, INFO.

KLECF015 DIALOG FUNCTION function HAS BEEN DYNAMICALLY REPLACEDExplanation: A dialog function module has been replaced by a new module.System Action: None.User Response: None.Message Type: INFO.

KLECF016 DIALOG FUNCTION function HAS BEEN DYNAMICALLY ADDEDExplanation: A new dialog function has been registered.System Action: None.User Response: None.Message Type: INFO.

KLECF996 ABORT REQUESTED FROM module+X’displacement’.Explanation: The abort function was issued by module at location displacement.System Action: The current thread is terminated.User Response: Contact Candle Customer Support with the contents of this message.Message Type: WARN.

KLECF997 ASSERTION FAILED: exprExplanation: The expression expr in an assert statement evaluated to zero. Message KLECF998 is also produced giving the location of the assert statement.System Action: The current thread is terminated.User Response: Contact Candle Customer Support.Message Type: WARN.


KLECF998 INTERRUPTED WHILE: EXECUTING LINE line OF source file (loc)Explanation: The expression in an assert statement at line line in source file source file evaluated to zero. loc is the module and displacement of the assert statement. Message KLECF997 is also produced listing the expression that evaluated to zero. System Action: The current thread is terminated.User Response: Contact Candle Customer Support.Message Type: WARN.

KLECF999 ABORT REQUESTEDExplanation: The abort function was requested by a program.System Action: The current thread is terminated.User Response: Contact Candle Customer Support.Message Type: ABEND.

KLEIN001 INVALID C LANGUAGE INTERFACE HEADER - moduleExplanation: During C language interface initialization processing, the specified module was inspected and found to have an invalid registration ID.System Action: The module is not made available to the C language environment.User Response: Contact Candle Customer Support with the module name shown in this message.Message Type: INFO.

KLEIN002 FUNCTION PACKAGE IS NON-REENTRANT: moduleExplanation: During C language interface initialization processing, the specified module was inspected and found to be non-reentrant.System Action: The module is not made available to the C language environment.User Response: Contact Candle Customer Support with the module name shown in this message.Message Type: INFO.

KLEIN003 C LANGUAGE INTERFACE STARTUP PROLOGUE COMPLETEExplanation: The C language interface initialization prologue processing has completed successfully.System Action: Processing continues.User Response: No action is required.Message Type: INFO.

KLEIN004 C LANGUAGE INTERFACE STARTUP EPILOGUE COMPLETEExplanation: The C language interface initialization epilogue processing has completed successfully.System Action: Processing continues.User Response: No action is required.Message Type: INFO.


KLEIN005 KLE_SVT VECTOR ALREADY IN USE AT OFFSET offset KLE_CVT OFFSET cvtoff EXISTING MODULE - emod, ATTEMPTING TO STORE - omodExplanation: The C language interface initialization process has determined that two C interface support modules are attempting to use the same program vector location. cvtoff is the vector table offset in the KLE_CVT. offset is offset of the module vector. emod is the name of the module whose entry address is currently stored in the vector. omod is the name of the module requesting the use of the vector.System Action: CT/Engine initialization is terminated.User Response: Save the RKLVLOG and contact Candle Customer Support with the contents of this message. Message Type: LOG, ERROR.

KLEIN006 KLE_CVT VECTOR ALREADY IN USE AT OFFSET cvtoff EXISTING MODULE - emod, ATTEMPTING TO STORE - omodExplanation: The C language interface initialization process has determined that two C interface support modules are attempting to use the same program vector location. cvtoff is the vector offset in the KLE_CVT. emod is the name of the module whose entry address is currently stored in the vector or SECONDARY VECTOR TABLE if a vector pointer in the KLE_CVT is non-zero. omod is the name of the module requesting the use of the vector.System Action: CT/Engine initialization is terminated.User Response: Save the RKLVLOG and contact Candle Customer Support with the contents of this message. Message Type: LOG, ERROR.

KLEIN007 iNVALID CFRAME VALUE - nnnnExplanation: During C language interface initialization processing, the CFRAME value, nnnn, was found to be in error.System Action: CT/Engine initialization is terminated.User Response: Correct the CFRAME value and restart the job. Message Type: LOG, ERROR.

KLEIN008 KLEINPRO RKANPAR PARAMETERS:Explanation: Module KLEINPRO logs its startup parameters as they are read from RKANPAR. This is the header message and will be followed by message KLEIN009.System Action: None.User Response: None.Message Type: LOG.

KLEIN009 parametersExplanation: As the parameters in module KLEINPRO are read, a log audit trail is created.System Action: None.User Response: None.Message Type: LOG.


KLEIN011 ACTION BAR C FUNCTIONS NOT INITIALIZEDExplanation: The C language action bar initialization routine determined that either the C interface CVT does not exist or the action bar function package could not be found.System Action: CT/Engine initialization is terminated.User Response: Save the RKLVLOG and contact Candle Customer Support with the contents of this message. Message Type: INFO.

KLELS001 UNSUPPORTED KLE LIBRARY CALLExplanation: A C language function program made a call to an unsupported module. Message KLELS002 is also issued.System Action: The thread is abended.User Response: Contact Candle Customer Support with the module names shown in message KLELS002.Message Type: ABEND.

KLELS002 caller MADE AN UNSUPPORTED LIBRARY CALL: moduleExplanation: A C language function program made a call to an unsupported module.System Action: The thread is abended.User Response: Contact Candle Customer Support with the module names shown in this message.Message Type: WARNING.

KLGAI001 APPLICATION STATUS: APPLID applid NOW (ACT | INACT | QSCE | STOP | UNAV) WAS (ACT | INACT | QSCE | STOP | UNAV)Explanation: The status of application applid has changed during this MONITOR interval. The WAS portion of the message is omitted on a first time check.System Action: None.User Response: If you want to change the MONITOR interval, modify KLGINGWY in your TLSPARM library according to instructions in the Customization Guide. For more information on VTAM status retrieval and monitoring, see function VIGSTAT in the Dialog Language Reference Manual.Severity: LOG, VIEW.


KLGAL002 APPLIST UNABLE TO ACCESS INIT LIBRARYExplanation: The initialization library (RKANPAR) could not be accessed by the APPLIST command because the library was not initialized properly at startup time. The most common cause of the error is an invalid RKANPAR DD statement.System Action: The APPLIST command is suppressed.User Response: Make sure the RKANPAR DD statement is correct. If it is not correct, there should be an error message indicating that the initialization library was unavailable at startup time (KLVIN409). Correct the DD statement in the startup procedure and restart CL/GATEWAY.Severity: ERROR.

KLGAL003 APPLIST MEMBER NOT FOUND: ID aid RKANPAR memnameExplanation: The member memname specified in the APPLIST command was not found in the initialization library (RKANPAR).System Action: The command is suppressed.User Response: Make sure that the correct member name is specified and that the member exists in your RKANPAR library. Reissue the command.Severity: ERROR.

KLGAL004 APPLIST DEFINED|DELETED|UPDATED: ID aid [SIZE applcnt]Explanation: The application list aid has been either defined, updated or deleted. If it was defined or updated, the size of the list is included.System Action: None.User Response: None.Severity: REPLY.

KLGAL005 APPLICATION DEFINITION FAILED: ID aidExplanation: A syntax error in applist memname caused the application list definition to fail. Check the previous message in the log for the specific error.System Action: The command fails.User Response: Refer to message KLGAL007 or the KLVSCnnn message that accompanies this message to determine the cause of the error. Correct the error and retry the APPLIST command.Severity: REPLY.

KLGAL006 EMPTY APPLIST NOT DEFINED: ID memnameExplanation: An application list member either did not contain any applications or the applications listed were not APPLDEFed.System Action: This application list will not be available for use.User Response: Make sure that there are applications in the APPLIST member and that they have all been APPLDEFed. Retry the command.Severity: ERROR.


KLGAL007 APPLDEF NOT FOUND, IGNORED: ID aid RKANPAR memname TOKEN token GROUP grpExplanation: A token and group specified in an APPLIST command did not match a token and group specified by the APPLDEF command.System Action: The token is not included in the list.User Response: Make sure that the token and group are correct and that the matching APPLDEF is executed before the APPLIST command. Reissue the command.Severity: WARNING.

KLGBG002 INVALID LINE NUMBER: BCGROUP name LINE nExplanation: The BCGROUP command contained an invalid line number as one of the operands.System Action: The command fails.User Response: Valid line numbers are 1–6. Correct the error and reissue the command.Severity: ERROR.

KLGBG003 BROADCAST GROUP: name (ADDED|UPDATED|DELETED) [LINE 1: ’text’] [LINE 2: ’text’] [LINE 3: ’text’] [LINE 4: ’text’] [LINE 5: ’text’] [LINE 6: ’text’]Explanation: The BCGROUP command was issued to display the current broadcast lines (text) and status for group name.System Action: None.User Response: None.Severity: REPLY.

KLGDF001 VIGAPPL ENVIRONMENT ERROR: FUNCTION(VIGAPPL)Explanation: A dialog that is not running in the CL/GATEWAY environment is using the VIGAPPL function.System Action: The current dialog fails.User Response: Make sure that you are logged onto either CL/GATEWAY for IMS or MVS before running this dialog.Severity: LOG, VIEW.

KLGDF002 INVALID REQUEST (service) FUNCTION VIGSTATExplanation: The service parameter was not entered. Valid services are GET, MONITOR, REMOVE, and SYNC.System Action: None.User Response: Re-enter the request using a valid service parameter. See function VIGSTAT in the Dialog Language Reference Manual for more information about this parameter.Severity: REPLY.


KLGDF031 OUTBOUND MESSAGE LIMIT EXCEEDED. VIRTUAL LU(luname). PHYSICAL LU(luname). SESSION CANCELLEDExplanation: CL/ENGINE has been notified that the pending outbound message limit is exceeded.System Action: The SINGLE session is terminated, and the user is returned to the CL/GATEWAY selection menu.User Response: None.Severity: LOG.

KLGDF032 OUTBOUND PENDING MESSAGE LIMIT EXCEEDED. PHYSICAL LU(luname). PASSTHRU SESSION CANCELLEDExplanation: CL/ENGINE has been notified that the pending outbound message limit is exceeded.System Action: The SINGLE session is terminated, and the user is returned to the CL/GATEWAY selection menu.User Response: None.Severity: LOG.

KLGDF041 UNABLE TO ACQUIRE PHYSICAL PRINTER: SENSE code Data Types LU lu VTLU terminal_virtual_lu VPLU printer_virtual_luExplanation: A printer (PRTNODE) was resolved during an application selection sequence, but the printer could not be acquired. This is the result of the VIGVSM function executing from a dialog.System Action: The action taken depends on the dialog in control when the error occurred.User Response: Determine the cause of the error, using the returned sense field described in help for sense data. Refer to the return codes documented in the Dialog Language Reference Manual.Severity: LOG, VIEW.

KLGDF042 UNABLE TO ALLOCATE VIRTUAL TERMINAL SESSION: SENSE code Data Types LU lu VTLU terminal_virtual_lu VPLU printer_virtual_luExplanation: The VIGVSM function failed. A frequent cause of this error is either an invalid pool name (POOL) or invalid virtual terminals within the pool.System Action: The action taken depends on the return code the dialog receives from this function.User Response: To determine the cause of the error, use the returned sense field described in help for sense data. For information on return codes, refer to the Dialog Language Reference Manual.Severity: LOG, VIEW.


KLGDF043 UNABLE TO ALLOCATE VIRTUAL PRINTER SESSION: SENSE code Data Types LU lu VTLU terminal_virtual_lu VPLU printer_virtual_luExplanation: The VIGVSM function failed. A frequent cause of this error is either an invalid pool name (PRTPOOL) or invalid virtual printers within the pool.System Action: The action taken depends on the return code the dialog received from this function.User Response: To determine the cause of the error, use the returned sense field described in help for sense data. For information on return codes, refer to the Dialog Language Reference Manual.Severity: LOG, VIEW.

KLGDF051 VIGMSG ENVIRONMENT ERRORExplanation: A dialog not running in the CL/GATEWAY environment is using the VIGMSG function.System Action: The current dialog fails.User Response: Log onto CL/GATEWAY before running this dialog.Severity: REPLY.

KLGDF052 n IS NOT SUPPORTED BY VIGMSGExplanation: The value n is not within the range of valid message numbers.System Action: The current dialog fails.User Response: Correct n and retry.Severity: REPLY.

KLGDF111 INVALID REQUEST(request) FUNCTION VIGBRCSTExplanation: The VIGBRCST function was invoked in a dialog, and the invalid request request was specified.System Action: The function is suppressed.User Response: Correct the request.Severity: REPLY.

KLGDF121 INVALID ELEMENT(element) FUNCTION VIGELEMExplanation: The VIGELEM function was invoked in a dialog, and the invalid element element was specified.System Action: The function is suppressed.User Response: Correct the element.Severity: REPLY.

KLGDF122 INVALID REQUEST(request) FUNCTION VIGELEMExplanation: The VIGELEM function was invoked in a dialog, and the invalid request request was specified.System Action: The function is suppressed.User Response: Correct the request.Severity: REPLY.


KLGDF141 INVALID ELEMENT(element) FUNCTION VIGEXITExplanation: The VIGEXIT function was invoked in a dialog, and the invalid element element was specified.System Action: The function is suppressed.User Response: Correct the element.Severity: REPLY.

KLGDF151 INVALID REQUEST(request) FUNCTION VIGGAPExplanation: The VIGGAP function was invoked in a dialog, and the invalid request request was specified.System Action: The function is suppressed.User Response: Correct the request.Severity: REPLY.

KLGDF161 INVALID ELEMENT(element) FUNCTION VIGGWExplanation: The VIGGW function was invoked in a dialog, and the invalid element element was specified.System Action: The function is suppressed.User Response: Correct the element.Severity: REPLY.

KLGDR001 VIGDR ENVIRONMENT ERRORExplanation: A dialog that is not running in the CL/GATEWAY environment is using the VIGDR function.System Action: The current dialog fails.User Response: Make sure that you are logged onto either CL/GATEWAY for IMS or CL/GATEWAY for MVS before running this dialog.Severity: REPLY.

KLGDR002 element name NOT SUPPORTED BY VIGDRExplanation: An invalid element was specified as the keyword of a VIGDR function.System Action: The current dialog fails.User Response: Correct the VIGDR function to specify a valid element name.Severity: REPLY.

KLGDY001 VIGDYN ENVIRONMENT ERRORExplanation: A dialog that is not running in the CL/GATEWAY environment is using the VIGDYN function.System Action: The current dialog fails.User Response: Make sure that you are logged onto either CL/GATEWAY for MVS or CL/GATEWAY for IMS before running this dialog.Severity: REPLY.


KLGIN002 UNABLE TO LOAD GATEWAY COMPONENT: moduleExplanation: The module specified could not be loaded during startup.System Action: Startup terminates.User Response: This message is accompanied by message KLVCM003, which gives a more specific reason why the module could not be loaded. Refer to help for sense data for more information on message KLVCM003.Severity: ALERT.

KLGIN101 GATEWAY INITIALIZATION COMPLETEExplanation: CL/GATEWAY initialization has completed successfully.System Action: None.User Response: None.Severity: INFO.

KLGLM001 NETWORK CONFIGURATION CHANGED, RESPECIFY REQUESTExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 0, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 0.Severity: REPLY.

KLGLM002 dest IS NOT A VALID SELECTIONExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 1, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 1.Severity: REPLY.

KLGLM003 HELP IS NOT AVAILABLEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 2, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 2.Severity: REPLY.

KLGLM004 dest IS NOT ACCEPTING SESSIONSExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 3, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 3.Severity: REPLY.


KLGLM005 logmode IS NOT A VALID LOGMODEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 4, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 4.Severity: REPLY.

KLGLM006 SESSION WAS REJECTED BY DESTINATION APPLICATIONExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 5, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 5.Severity: REPLY.

KLGLM007 SESSION WAS REJECTED BY LOGICAL UNITExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 6, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 6.Severity: REPLY.

KLGLM008 UNABLE TO START VIRTUAL SESSION WITH destExplanation: This error message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 7, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 7.Severity: REPLY.

KLGLM009 VIRTUAL TERMINAL POOL FOR dest IS EMPTYExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 8, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 8.Severity: REPLY.


KLGLM010 VIRTUAL PRINTER POOL FOR dest IS EMPTYExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 9, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 9.Severity: REPLY.

KLGLM011 APPLICATION LIST NOT FOUNDExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 10, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 10.Severity: REPLY.

KLGLM012 GATEWAY SETUP ERRORExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 11, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 11.Severity: REPLY.

KLGLM013 UNSUPPORTED COMMAND OR FUNCTION KEYExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 12, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 12.Severity: REPLY.

KLGLM014 UNABLE TO ESTABLISH PHYSICAL PRINTER SESSIONExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 13, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 13.Severity: REPLY.


KLGLM015 UNABLE TO ESTABLISH VIRTUAL PRINTER SESSIONExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 14, documented in the Customization Guide.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 14.Severity: REPLY.

KLGLM016 IMS SETUP: OPERATOR SESSION(S) UNAVAILABLEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 15, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005. Refer to these messages for more information.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 15.Severity: REPLY.

KLGLM017 IMS SETUP: INVALID LTERM NAMEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 16, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 16.Severity: REPLY.

KLGLM018 IMS SETUP: INVALID NODE NAMEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 17, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 17.Severity: REPLY.


KLGLM019 IMS SETUP: LTERM UNAVAILABLEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 18, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 18.Severity: REPLY.

KLGLM020 IMS SETUP: STOP NODE FAILEDExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 19, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 19.Severity: REPLY.

KLGLM021 IMS SETUP: DEQUEUE NODE FAILEDExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 20, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 20.Severity: REPLY.

KLGLM022 IMS SETUP: RESTART NODE FAILEDExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 21, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 21.Severity: REPLY.


KLGLM023 IMS SETUP: START NODE FAILEDExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 22, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 22.Severity: REPLY.

KLGLM024 IMS SETUP: LTERM IN USEExplanation: This exception message appears on a CL/GATEWAY for MVS or CL/GATEWAY for IMS application selection panel. It corresponds to configuration member MESSAGE 23, documented in the Customization Guide. This message is accompanied by messages KLIQM002, KLIQM004, or KLIQM005.System Action: The action taken depends on the reason for the error.User Response: Refer to the Customization Guide for more information on configuration member MESSAGE 23.Severity: REPLY.

KLGLM025 NO AUTHORIZED APPLICATIONSExplanation: External security system rejected all applications in the user’s applist.System Action: User cannot select an application.User Response: Get authorization for the applications from your security administrator.Severity: REPLY.

KLGLM026 RESOLUTION LIMIT EXCEEDEDExplanation: Data elements can be resolved by user entry through a panel. When the number of errors for a panel exceeds the limit, this message is displayed.System Action: None.User Response: None.Severity: REPLY.


KLGLM027 text GATEWAY(acbname) ID(termid) ELEMENT(elemname)Explanation: text is one of 26 message IDs found in the gateway configuration member. These IDs have the format:

$SMSGGWn

where n is 1–26. elemname can be one of the following:USERIDPASSWORDDEST GROUPACCT PROC

System Action: This message will not appear unless a site has modified the gateway configuration messages.User Response: The user response depends on the message.Severity: REPLY.


KLGOP011–KLVGM006 413

KLGOP011–KLVGM006

KLGOP011 NO IMS OPTION SELECTED, GATEWAY NOT ENABLED: TOKEN tokenidExplanation: The APPLDEF command must specify the IMS option unless GATEWAY is enabled.System Action: The command fails.User Response: Correct the error and reissue the command.Severity: ERROR.

KLGOP012 PRTPOOL OPTION REQUIRES POOL SPECIFICATIONExplanation: The APPLDEF command did not specify the POOL option but printer pooling requires the use of terminal pooling.System Action: The APPLDEF command terminates.User Response: Specify the POOL option if printer pooling is desired and reissue the command.Severity: ERROR.

KLGOP013 APPLICATION token ADDED|MODIFIED: [DEST name - text] [ALTDEST name - text] [GROUP group num] [ORDER order num] [HELP #aphelp] [IMS(ASSIGN)] [IMS(DEQUEUE)]Explanation: The parameters specified on the APPLDEF command are also displayed. For more information on each field, refer to the Customization Guide.System Action: None.User Response: None.Severity: REPLY.

KLGOP014 APPLICATION tokenid DELETEDExplanation: The APPLDEF command with the REMOVE option successfully removed the application tokenid.System Action: None.User Response: None.Severity: INFO.

5


KLGOP015 PRIMARY DESTINATION MISSING, REQUIREDExplanation: The APPLDEF command was not able to define a new application. Either the primary destination (DEST) parameter is missing or the group number is invalid.System Action: The APPLDEF command terminates.User Response: Correct the error and reissue the command.Severity: ERROR.

KLGOP016 APPLICATION tokenid NOT FOUNDExplanation: The APPLDEF command with the REMOVE option could not delete the application tokenid because it could not find it.System Action: The APPLDEF command terminates.User Response: Correct the error and reissue the command.Severity: ERROR.

KLGOP017 WARNING - TOKEN token ALREADY EXISTS IN GROUP, NEWGROUP IGNOREDExplanation: The APPLDEF command with the NEWGROUP operand attempted to modify a token that already exists in the NEWGROUP. The change is ignored. System Action: The current group number does not change.User Response: None.Severity: REPLY.

KLGOP018 EMPTY APPLIST DELETED: ID #applistExplanation: After the APPLDEF command with the REMOVE option successfully completed, the application was deleted from any APPLIST that refers to it. APPLIST contained only this application and is therefore deleted.System Action: None.User Response: None.Severity: INFO.

KLGOP019 IMS OPTION SELECTED BUT GATEWAY NOT INSTALLEDExplanation: The APPLDEF command with the IMS parameter cannot be issued unless CL/GATEWAY for IMS is installed.System Action: The command terminates.User Response: Correct the error and reissue the command.Severity: REPLY.

KLGOP020 VALUE SPECIFIED FOR xxxx PARAMETER EXCEEDS THE MAXIMUM (9999)Explanation: The specified value for this parameter exceeds the maximum allowed.System Action: The APPLDEF command terminates.User Response: Correct the error and reissue the command.Severity: ERROR.


KLGOP021 UNABLE TO ACCESS INITIALIZATION LIBRARY: APPLID applid DDNAME (RKANPAR)Explanation: The HOSTGATE command could not access the initialization library.System Action: The HOSTGATE command terminates.User Response: Ensure that the dataset name on ddname RKANPAR is correct. If you cannot attribute the cause of the error to an installation error, contact Candle Customer Support.Severity: ERROR.

KLGOP022 CONFIGURATION MEMBER NOT FOUND: APPLID applid MEMBER name DDNAME (RKANPAR)Explanation: The member name supplied on the CONFIG= parameter of the HOSTGATE command could not be found.System Action: If this message is caused by the absence of the CONFIG parameter, the member name defaults to the ACBNAME supplied on the command. The HOSTGATE command terminates.User Response: Correct the error and reissue the command.Severity: ERROR.

KLGOP023 UNSUPPORTED MESSAGE NUMBER: n APPLID applid MEMBER name LINE mExplanation: The configuration member name in the initialization library of the HOSTGATE command contained an unsupported message number n on line number m.System Action: The HOSTGATE command terminates.User Response: Refer to the Customization Guide for more information concerning message numbers.Severity: ERROR.

KLGOP024 DUPLICATE MESSAGE NUMBER: n APPLID applid MEMBER name LINE mExplanation: The configuration member name in the initialization library of the HOSTGATE command contained a duplicate message number n on line number m.System Action: The HOSTGATE command terminates.User Response: Correct the error and reissue the command. Refer to the Customization Guide for more information on message numbers.Severity: ERROR.


KLGOP025 UNSUPPORTED DATA TYPE: APPLID applid MEMBER config TYPE:invite LINE nExplanation: The HOSTGATE command was issued but data type invite in member config on line number n is not supported.System Action: The HOSTGATE command terminates.User Response: Correct the error and reissue the command. Refer to the Customization Guide for more information on data elements.Severity: ERROR.

KLGOP027 PANEL NOT AVAILABLE: APPLID applid MEMBER name TYPE datatype PANEL panid LINE nExplanation: The HOSTGATE command could not find panel panid in the panel library. PANEL= was specified as a data source of configuration member name on line number n in RKANPAR.System Action: The command terminates.User Response: Correct the error and reissue the command. This may require defining a panel in the panel library.Severity: ERROR.

KLGOP028 EXIT NOT AVAILABLE: APPLID applid MEMBER name TYPE datatype EXIT exitname LINE nExplanation: The HOSTGATE command could not load exit exitname from the load library. EXIT= was specified as a data source of configuration member name on line number n in RKANPAR.System Action: The command terminates.User Response: This message is accompanied by message KLVCM003. Correct the error and reissue the command.Severity: ERROR.

KLGOP029 NOP INSTRUCTION MISSING: APPLID applid MEMBER name TYPE datatype EXIT exitname LINE nExplanation: The HOSTGATE command loaded exit exitname successfully; however, the exit did not have a NOP instruction as the first instruction. EXIT= was specified as a data source of configuration member name on line number n in the initialization library.System Action: The command terminates.User Response: Refer to the Customization Guide for more information about the conventions that must be followed when writing an exit.Severity: ERROR.


KLGOP030 INVALID POSITIONAL USERDATA SYNTAX: APPLID applid MEMBER name TYPE datatype USERDATA syntaxExplanation: The HOSTGATE command found invalid USERDATA syntax syntax and USERDATA= was specified as a data source of configuration member name in the initialization library.System Action: The command terminates.User Response: Refer to the Customization Guide for more information about the USERDATA data source.Severity: ERROR.

KLGOP031 DUPLICATE USERDATA SPECIFICATION: APPLID applid MEMBER name TYPE datatype DUPTYPE dtype USERDATA syntaxExplanation: The HOSTGATE command was issued, but duplicate USERDATA syntax syntax was specified on more than one data type. USERDATA= was specified as a data source of configuration member name in the initialization library.System Action: The command terminates.User Response: Refer to the Customization Guide for more information on the USERDATA data source.Severity: ERROR.

KLGOP034 UNABLE TO OPEN VTAM ACB: APPLID applid REASON acberflgExplanation: The HOSTGATE command could not open ACB applid.System Action: The command terminates.User Response: Refer to IBM’s ACF/VTAM Programming manual to determine the cause of the error. This message is also accompanied by message KLVVT001. Correct the error and reissue the command.Severity: ERROR.

KLGOP035 GATEWAY STARTED: APPLID applid CONFIG config DIALOG dialogExplanation: The HOSTGATE command successfully started the GATEWAY applid.System Action: None.User Response: None.Severity: INFO.

KLGOP036 DUPLICATE DATA TYPE: APPLID applid MEMBER name TYPE datatype LINE nExplanation: The HOSTGATE command detected a duplicate data type datatype in configuration member name on line number n in the initialization library.System Action: The command terminates.User Response: Refer to the Customization Guide for more information on data types.Severity: ERROR.


KLGOP039 UNABLE TO ALLOCATE VTAM ACB: APPLID applidExplanation: When the HOSTGATE command was issued, CL/GATEWAY for MVS and CL/GATEWAY for IMS were unable to allocate a VTAM ACB.System Action: The command terminates.User Response: Refer to the Problem Determination Guide for help in resolving the error condition or in gathering the problem documentation that Candle requires to research the error condition.Severity: ERROR.

KLGOP040 GATEWAY STOPPED: APPLID applidExplanation: GATEWAY with applid applid terminated successfully.System Action: None.User Response: None.Severity: INFO.

KLGOP041 DEST OR USERDATA DATA ELEMENT MUST BE DEFINEDExplanation: The HOSTGATE command was issued. No DEST or USERDATA element was defined that CL/GATEWAY for MVS or CL/GATEWAY for IMS could resolve as a minimum configuration destination.System Action: The command terminates.User Response: Define the configuration correctly. Refer to the Customization Guide for more information on configuration members and data elements.Severity: ERROR.

KLGOP042 CONFIG mem LINE n APPLID appl ’text’Explanation: The HOSTGATE command was issued and each line in configuration member mem for APPLID appl is logged to create an audit trail.System Action: None.User Response: None.Severity: LOG.

KLGOP043 INVALID NAM SPECIFICATION: ELEMENT nameExplanation: The HOSTGATE command was issued and an invalid NAM specification for data element name was recognized. Either NAM was specified for the USERID data element or NAM was specified for a data element and no USERID data element was specified.System Action: The command terminates.User Response: Either remove the NAM specification on the data element specified or add the USERID data element to the configuration member and reissue the command. For more information on NAM and data elements, refer to the Customization Guide.Severity: ERROR.


KLGOP044 CONTROLLING DIALOG UNAVAILABLE: dialogExplanation: The HOSTGATE command was issued with the DIALOG parameter. The dialog specified was not available. The dialog was probably omitted from the CL/ENGINE panel library.System Action: The command terminates.User Response: Correct the error and reissue the command.Severity: ERROR.

KLGOP045 LIMIT OUT OF RANGE: ELEMENT elem LIMIT limExplanation: The resolution limit lim specified for the data element elem is too large.System Action: The command is suppressed.User Response: Make sure that the limit specified is correct.Severity: ERROR.

KLGOP051 SHOW: TYPE type ARGUMENT mask LU lu GATE applidExplanation: The results of the SHOW command appear.System Action: None.User Response: None. For more information on each field, refer to the Customization Guide.Severity: REPLY.

KLGOP052 NO SHOW INFORMATION FOUND: TYPE type ARGUMENT maskExplanation: The system could find no information on the option type and argument mask issued with the SHOW command.System Action: None.User Response: None.Severity: REPLY.

KLGOP500 message id message textExplanation: There is no text associated with this message ID. It always appears with another message, which explains the exact nature of the error.System Action: Depends on the nature of the error.User Response: Read the accompanying message and take appropriate action.Severity: REPLY.

KLGOP501 LIMIT nnn REACHED, SPECIFY NEW LIMIT OR END TO TERMINATE IMBRCSTExplanation: The current broadcast limit has been reached, and possible sessions remain to be processed.System Action: The system waits for a user response before taking a new action.User Response: Specify a new limit with the IMBRCST command, or END to terminate the IMBRCST command.Severity: REPLY.


KLGOP502 IMBRCST SCHEDULED TO nnn USER(S)Explanation: The IMBRCST command was issued and nnn users were scheduled to receive the broadcast.System Action: The broadcast is processed.User Response: None.Severity: REPLY.

KLGOP503 DIALOG dialog NOT FOUNDExplanation: The IMBRCST command was issued, but the dialog specified with the PANEL keyword (or the default) is unavailable.System Action: The command is ignored.User Response: Define the dialog in the panel library.Severity: REPLY.

KLGOP504 IMBRCST NOT ACTIVEExplanation: The IMBRCST command was issued, but this facility is inactive.System Action: The command is ignored.User Response: The IMBRCST command is not usable in the current environment.Severity: REPLY.

KLGOP505 IMBRCST TEXT LENGTH nnn EXCEEDED THE MAXIMUM ALLOWED AND HAS BEEN TRUNCATED TO 255Explanation: The IMBRCST was sent, but the text was truncated.System Action: IMBRCST text is truncated to 255 characters.User Response: None.Severity: INFO

KLGOP506 LIMIT INVALID, SPECIFY NEW LIMIT OR END TO TERMINATE IMBRCSTExplanation: Your response to message KLGOP501 was invalid.System Action: The system waits for a user response before taking a new action.User Response: Specify a valid limit (0–99999) with the IMBRCST command to continue, or END to terminate the IMBRCST command.Severity: REPLY.

KLGOP507 IMBRCST ENDED DUE TO LIMIT THRESHOLDExplanation: IMBRCST ended before scheduling all messages. The limit was reached, and either NOPROMPT was specified on the original IMBRCST command or END was entered in response to KLGOP501 or KLGOP506. This message is followed by KLGOP502.System Action: None.User Response: None.Severity: REPLY.


KLGOP997 LGMAINT INVALID COMMAND FORMATExplanation: The command LGMAINT was issued with operands.System Action: None.User Response: Reissue the command without operands.Severity: ERROR.

KLGOP998 CL MAINTENANCE LEVEL xxxxxxxx APPLIEDExplanation: The command KLGMAINT was issued successfully.System Action: None.User Response: None.Severity: INFO.

KLGOP999 CL MAINTENANCE LEVEL UNKNOWNExplanation: Maintenance was incorrectly applied, or KLSISNDX member in TLSPARM dataset was modified or deleted.System Action: None.User Response: Reapply sysmod Q147DOC.Severity: WARNING.

KLIDF011 UNSUPPORTED IMSGATE REQUESTExplanation: The CL/GATEWAY for IMS function was encountered in a dialog and completed unsuccessfully. The current environment portion of the message contains all the relevant information about the current user of the dialog (LTERM, DFS message, and so on).System Action: This depends on the dialog in use when the error occurred.User Response: For more information on dialogs and functions, refer to the Dialog Language Reference Manual. In particular, refer to the section on the CL/GATEWAY for IMS function return codes.Severity: LOG, VIEW.

KLIDF012 IMSGATE ENVIRONMENTAL ERROR argExplanation: The CL/GATEWAY for IMS function does not run unless CL/GATEWAY for IMS is installed.System Action: The function terminates.User Response: For more information on dialogs and functions, refer to the Dialog Language Reference Manual. In particular, refer to the section on the CL/GATEWAY for IMS function return codes.Severity: LOG, VIEW.


KLIOP102 IMS idname DEFIN|UPDAT:APPLID applid POOL pool[DUMMY nodename XLV|NOXLV][DISPSWD iddipwd][ASSPSWD idaspwd][STOPSWD idstpwd][RSTPSWD idrspwd][STAPSWD idtapwd][DEQPSWD iddqpwd]MIN n MAX n READY nACTIVE n PERM nExplanation: The reply to the IMS command is either DEFIN or UPDAT.System Action: None.User Response: None. For more information on each field, refer to the Customization Guide.Severity: REPLY.

KLIOP103 APPLID AND/OR POOL OPERAND(S) OMITTED, REQUIREDExplanation: The IMS command could not locate the APPLID or POOL (or both) operands.System Action: The IMS command terminates.User Response: Correct the error and reissue the command. For more information on the IMS command, refer to the Customization Guide.Severity: ERROR.

KLIOP202 UNABLE TO DETERMINE TARGET IMS: imsidExplanation: The MTO command could not locate the IMS system definition specified.System Action: The MTO command terminates.User Response: Determine if the IMS command that defines the IMS system imsid is valid. Correct any errors and reissue the command. For more information on the MTO and IMS commands, refer to the Customization Guide.Severity: ERROR.

KLIOP203 UNABLE TO PROCESS MTO REQUEST: imsidExplanation: The MTO command could not be processed, most probably because the IMS operator sessions for the IMS definition imsid are lacking.System Action: The MTO command terminates.User Response: Look for other error messages concerning this IMS definition. Correct any errors and reissue the command. For more information on the MTO and IMS commands, refer to the Customization Guide.Severity: ERROR.

KLIOP204 MTO RESPONSE FROM IMS imsid:Explanation: This message shows the response to the MTO command.System Action: None.User Response: None.Severity: REPLY.


KLIQM001 IMS OPERATOR LOGOFF: IMS imsname NODE nodenameExplanation: An operator logged off IMS from node nodename.System Action: None.User Response: None.Severity: INFO.

KLIQM002 UNABLE TO START IMS OPERATOR SESSION:SENSE sense IMS name APPLID applidPOOL poolExplanation: The user was unable to contact IMS with APPLID applid. Any attempt to use the dequeue or assign facilities for this IMS definition will fail.System Action: None.User Response: Determine the cause of the error using the sense field described in help for sense data.Severity: LOG, VIEW.

KLIQM003 IMS OPERATOR LOGON: IMS imsname NODE nodenameExplanation: A session has been established between the IMS definition imsname and the nodename specified. This message indicates that communications between IMS and CL/GATEWAY for IMS have been established correctly.System Action: None.User Response: None.Severity: INFO.

KLIQM004 INVALID LOGON RESPONSE FROM IMS:IMS imsname APPLID applidExplanation: CL/GATEWAY for IMS attempted to establish a session with IMS and received an invalid response. This message is accompanied by messages KLIQM001, KLIQM002, or both. The dequeue and assign facilities for the specified IMS definition are unavailable.System Action: None.User Response: Look for other messages concerning this IMS definition. If the cause of the problem cannot be determined, or if the problem persists, contact Candle Customer Support.Severity: WARNING.

KLIQM005 LTERM RECOVERY IN PROGRESS:REQLTERM lterm CURLTERM ltermREQNODE nodename CURNODE nodenameExplanation: This message can be the result of normal network activity (such as an IMS shutdown) and should not be cause for alarm.1. You have attempted to assign an LTERM to a node REQNODE nodename

that already has an assigned LTERM.2. The LTERM REQLTERM lterm was left in an abnormal state the last time it

was used. The LTERM on the requested node is CURLTERM lterm.


System Action:1. The current LTERM CURLTERM lterm on the requested node REQNODE

nodename is assigned to the dummy node. The requested LTERM REQLTERM lterm is assigned to the requested node.

2. The system attempts to recover any residual data in the requested LTERM REQLTERM lterm. The requested LTERM REQLTERM lterm is reassigned to the requested node REQNODE nodename. The dummy node is specified on the DUMMY parameter of the IMS command.

User Response: None, unless the LTERM recovery fails. If it does, there will be other messages indicating a specific reason why LTERM recovery failed.Severity: WARNING.

KLSIN011 MULTI-SESSION OPTION ENABLEDExplanation: The multi-session capability is enabled.System Action: None.User Response: None.Severity: INFO.

KLSMI000 NO PARAMETERS SPECIFIEDExplanation: No parameters were coded on the JCL EXEC PARM statement.System Action: A set of default values will be in effect. Message KLSMI004 follows this and shows these defaults.User Response: None.

KLSMI001 PARAMETERS: parmsExplanation: The parameters coded on the JCL EXEC PARM statement are displayed.System Action: None.User Response: None.

KLSMI002 INVALID KEYWORD: textExplanation: An invalid parameter was coded on the JCL EXEC PARM statement.System Action: The conversion run will be terminated after all of the EXEC PARM parameters have been validated.User Response: Correct the invalid keyword then resubmit the utility job.

KLSMI003 CONFLICTING KEYWORDSExplanation: Two conflicting parameters were coded on the JCL EXEC PARM statement.System Action: The utility run is terminated.User Response: Determine which options are desired, correct the PARM keyword on the EXEC statement, then resubmit the utility job.

KLSMI004 PROCESSING OPTIONS IN EFFECT: option, option,...Explanation: The utility parameters in effect are displayed.System Action: None.User Response: None.


KLSMI005 THE ddname DD IS REQUIREDExplanation: ddname is required.System Action: The utility run is terminated.User Response: Add the required DD statement to the utility job’s JCL and resubmit.

KLSMI006 THE KLSSYSIN DD IS REQUIRED FOR INCLUDE/EXCLUDE PROCESSINGExplanation: Either INCLUDE or EXCLUDE was coded on the JCL EXEC PARM statement but the SYSIN DD is not present.System Action: The utility run is terminated.User Response: Either remove the INCLUDE or EXCLUDE keyword from the EXEC PARM statement or add the SYSIN DD to the utility job’s JCL, then resubmit.

KLSMI007 DSNAME= dsname UNIQUE=nnnn PROCESSED=nnnn DUPLICATES=nnnnExplanation: The utility has finished its processing. This message displays a dataset name in the MIGRIN concatenation, the number of unique members in the library, the number of those members that were processed, and the number of members excluded from processing because they were found in a library that appeared earlier in the MIGRIN concatenation.System Action: None.User Response: None.

KLSMI008 TOTAL UNIQUE MEMBERS=nnnn PROCESSED=nnnnExplanation: The utility has finished its processing. This message displays the grand total number of unique members in all of the libraries in the MIGRIN concatenation, and the number of members that were actually processed.System Action: None.User Response: None.

KLSMI009 PROCESSING member IN dsnameExplanation: The utility has located member in the MIGRIN library dsname and will perform the required interrogation.System Action: None.User Response: None.

KLSMI010 INCLUDE/EXCLUDE MEMBER LIST:Explanation: Either INCLUDE or EXCLUDE was coded on the JCL EXEC PARM statement. The contents of the SYSIN file will be read and displayed following this message.System Action: None.User Response: None.


KLSMI011 PDS UPDATE FAILED FOR member - R15=rtncode R0=reasonExplanation: An attempt was made to update the MIGROUT file with an updated member, but the MVS STOW request failed with the indicated code. This is generally because there are no more directory entries left (rtncode will be 0C).System Action: The utility is terminated.User Response: For rtncode=0C, reallocate the MIGROUT file with a larger number of directory blocks, then resubmit the utility JCL. For other values of rtncode, refer to the IBM manual Data Administration: Macro Instruction Reference, under the STOW macro, for the explanation of the error, then perform the required correction and resubmit the utility JCL.

KLSMI012 PROCESSING COMPLETEDExplanation: All requested members have been interrogated.System Action: None.User Response: None.

KLSMI013 INVALID RECFM OR LRECL FOR ddnameExplanation: The MIGRININ or MIGROUT files do not have a record format (RECFM) of fixed (F), fixed blocked (FB), variable (V), or variable blocked (VB); or the KLSMI0OUT file does not have a logical record length (LRECL) at least as large as the KLSMI0IN LRECL.System Action: The utility is terminated.User Response: Correct the problem, then resubmit the utility JCL.

KLSMI014 MEMBER member IN dsnameExplanation: This message displays a title line written to SYSPRINT to identify which dialog’s text records follow.System Action: None.User Response: None.

KLSMI015 LINES MODIFIED=nnnn ADDED=nnnn FLAGGED=nnnnExplanation: This message displays a total line written to SYSPRINT to document what actions were performed against a member. If any lines were modified, added, or flagged, the message will also be written to the MESSAGE dataset. If no actions were performed, this message will not appear.System Action: None.User Response: None.

KLSMI100 MEMBER xxxxxxxx IS NOW OBSOLETEExplanation: The SSPL member xxxxxxxx is no longer used by this product.System Action: None.User Response: None.

KLSMI101 MEMBER xxxxxxxx SHOULD BE RENAMED AS yyyyyyyyExplanation: This product required the member to be renamed.System Action: None.User Response: Rename SSPL member xxxxxxxx as yyyyyyyy.


KLSRN001 NO PARAMETERS SPECIFIEDExplanation: No parameters were coded on the JCL EXEC PARM statement.System Action: Default values will be in effect. Message KLSRN004 shows the defaults.User Response: None.

KLSRN002 INVALID KEYWORD: textExplanation: An invalid parameter was coded on the JCL EXEC PARM statement. The valid keywords are

® EXCLUDE® INCLUDE® UDATA® ASISUDATA® SEPNLS® SHOWCHGSystem Action: The conversion terminates after all of the EXEC PARM parameters have been validated.User Response: Correct the invalid keyword, then resubmit the utility job.

KLSRN003 CONFLICTING KEYWORDSExplanation: Two conflicting parameters were coded on the JCL EXEC PARM statement. The following keywords are mutually exclusive and should not be specified in the same execution.® EXCLUDE and INCLUDE

® UDATA and NOUDATA and ASISUDATA

System Action: The utility run terminates.User Response: Determine which options you want, correct the PARM keyword on the EXEC statement, then resubmit the utility job.

KLSRN004 PROCESSING OPTIONS IN EFFECT: option, option,...Explanation: The utility parameters in effect display.System Action: None.User Response: None.

KLSRN005 OPEN FAILUREExplanation: This message is generated because of the following® DD statement missing for an input library

® Input library is not a PDS

® Input library is empty

System Action: The utility run terminates.


User Response: Add the required DD statement to the utility job’s JCL and resubmit. At least one of the following must be coded:

KLSRN006 THE SYSIN DD IS REQUIRED FOR INCLUDE/EXCLUDE PROCESSINGExplanation: The INCLUDE or EXCLUDE was coded on the JCL EXEC PARM statement, but no SYSIN DD exists.System Action: The utility run terminates.User Response: Either remove the INCLUDE or EXCLUDE keyword from the EXEC PARM statement or add the SYSIN DD to the utility job’s JCL. Resubmit the job.

KLSRN007 DSNAME= dsname UNIQUE=nnnn PROCESSED=nnnn DUPLICATES=nnnnExplanation: The utility has finished its processing. This message displays a dataset name in the input concatenation (DSNAME=), the number of members in the library (UNIQUE=), the number of those members that were processed (PROCESSED=), and the number of members excluded from processing (DUPLICATES=) because they were found in a library that appeared earlier in the input concatenation.System Action: None.User Response: None.

KLSRN008 TOTAL UNIQUE MEMBERS= nnnn in DDNAME=ddname PROCESSED=nnnnExplanation: The utility has finished its processing. This message displays the cumulative total number of unique members in all the libraries in the input concatenation, and the number of members that were actually processed.System Action: None.User Response: None.

KLSRN009 PROCESSING MEMBER member IN DSNAME dsnameExplanation: The utility is currently processing member in the input library dsname.System Action: None.User Response: None.

KLSRN010 include/exclude MEMBER LIST:Explanation: Either INCLUDE or EXCLUDE was coded on the JCL EXEC PARM statement. The contents of the SYSIN file are read and displayed.System Action: None.User Response: None.

VTPCLIB DDNAME for commands library

VTPILIB DDNAME for initialization library

VTPPLIB DDNAME for panels library


KLSRN011 PDS UPDATE FAILED FOR member in DDNAME=ddname Return Code=rtncode Reason Code=reasonExplanation: An attempt was made to update an output file with an updated member, but the MVS STOW request failed with the indicated code. This is generally because there are no more directory entries available (rtncode will be 0C).System Action: The utility is terminated.User Response: For rtncode=0C, reallocate the output file with a larger number of directory blocks, then resubmit the utility JCL. For other values of rtncode, refer to the IBM manual Data Administration: Macro Instruction Reference, under the STOW macro, for the explanation of the error, then perform the required correction and resubmit the utility JCL.

KLSRN012 PROCESSING COMPLETEDExplanation: All requested members have been processed.System Action: None.User Response: None.

KLSRN013 INVALID RECFM OR LRECL FOR ddnameExplanation: The DDNAME specified in ddname does not have a record format (RECFM) of fixed (F), fixed blocked (FB), variable (V), or variable blocked (VB); or the output file does not have a logical record length (LRECL) at least as large as the input LRECL.System Action: The utility is terminated.User Response: Reallocate the file appropriately, then resubmit KLSRNMJ job again.

KLSRN014 MEMBER member IN dsnameExplanation: This message displays a title line written to SYSPRINT to identify which member’s text records follow. The heading AMF is an acronym for

System Action: None.User Response: None.

KLSRN015 LINES MODIFIED= nnnn ADDED=nnnn FLAGGED=nnnnExplanation: This message displays a total line written to SYSPRINT to document what actions were performed against a member. If any lines were modified, added, or flagged, the message will also be written to the MESSAGE dataset.System Action: None.User Response: None.

A a line was added

M a line was modified

F a line was flagged due to errors


KLSRN101 MEMBER member LINE lineno UNEXPECTED CHARACTER FOUND ’characters’Explanation: The rename utility interprets the characters as a syntax error.System Action: Characters are written to output and processing continues.User Response: Correct the invalid syntax and run the utility again.

KLSRN102 MEMBER member LINE lineno CONTEXT SENSITIVE WORD ’token’ NOT CHANGEDExplanation: A token that is considered as context sensitive is not changed because the previous word is not one of the following:® ABCHOICE® CALL or CALLS or CALLED or CALLING® DIALOG or DIALOGS® I® INVOKE or INVOKES or INVOKING® ISDIALOG® MEMBER or MEMBERS® PSMSELCT® PSMSPLIT® REFRESH® SELECT® TIMEOUTSystem Action: Processing continues.User Response: Review output and verify if token should be changed.

KLSRN103 MEMBER member LINE lineno TOKEN NOT CHANGED AND MAY RESULT IN AN INVALID DIALOGExplanation: Token contains &VSPLANG and is not changed because token is not in KLSTBLS. Dialog name that contains imbedded &VSPLANG is usually resolved to a national language id of either 1, 2, 3, or 4. However, the dialog member name in a PDS is still named with a national language id of either EN, FR, GR, FC, or some characters other than 1, 2, 3, or 4.System Action: Processing continues.User Response: If dialog is user written, rename the object dialog so that the imbedded two character language id, (EN, FR, GR, or FC) becomes a one character language id, (1, 2, 3, or 4) respectively.

KLSRN104 MEMBER member IS ENCRYPTEDExplanation: Utility found an encrypted dialog.System Action: Encrypted dialog will be bypassed.User Response: None.

KLSRN105 MEMBER member LINE lineno EXPANDED BEYOND COLUMN 80 AND WAS SPLITExplanation: After rename, the line was expanded beyond 80 characters.System Action: Records are split.User Response: None required, although you may wish to reformat the lines affected for aesthetic or style reasons.


KLSRN106 MEMBER member LINE lineno EXPANDED BEYOND COLUMN 72Explanation: After rename, the line was expanded beyond 72 charactersSystem Action: None.User Response: None.

KLSRN107 MEMBER member LINE lineno EXPANDED BEYOND COLUMN 80 BUT COULD NOT BE SPLITExplanation: After rename, the line was expanded beyond 80 characters and the utility could not find a logical point at which to split the line.System Action: The complete expanded line is printed in the SYSPRINT dataset and the first 80 characters are written to the appropriate output PDS.User Response: Reformat the lines affected.

KLSRN201 FILE KLSTBLS CANNOT BE OPENED OR FILE IS EMPTYExplanation: This message is generated because of the following reasons:® file KLSTBLS is empty® DDNAME KLSTBLS is not specified in the JCL® invalid input was readAs supplied by the product, TLSSAMP(KLSTBLS) should contain the necessary input to run the rename utility.System Action: Job execution is terminated.User Response: Include DDNAME KLSTBLS.

KLUAP002 APDSM/ALLOCEAB $PSM-ALLOCX ERRORExplanation: An internal error was detected by CT/Engine.System Action: CT/Engine forces an abend with the completion code U0100. The abend is associated with a single CT/Engine user, whose terminal will hang. System operation for other users will continue normally. A VCANCEL command may be necessary to reinstate the hung user. CT/Engine automatically writes a formatted dump to the RKLVSNAP dataset.User Response: Contact Candle Customer Support.Message Type: ABEND.

KLUAP003 APDSM DATA STREAM REPROCESSED FOR session_id USERID=useridExplanation: This error occurred during processing of the application data stream for the specified session_id and userid.System Action: None.User Response: None.Message Type: INFO.

KLUDF011 INVALID TRIGGER DEFINITION BLOCKExplanation: The VSSTRIG function contained an invalid trigger definition block. This is a serious error.System Action: The address space terminates. User Response: Contact Candle Customer Support.Message Type: ABEND.


KLUDF021 option IS NOT A VSSINFO OPTIONExplanation: The specified option is not valid for the VSSINFO function. FOREGID is currently the only valid option.System Action: The current dialog fails.User Response: Specify a valid option and retry.Message Type: REPLY.

KLUDF022 VSSENTRY NOT ISSUED PRIOR TO VSSINFOExplanation: A dialog invoked the VSSINFO function before VSSENTRY. VSSENTRY must be invoked prior to any other VSS function.System Action: The current dialog fails.User Response: Correct the dialog and retry.Message Type: REPLY.

KLUDF023 FUNCTION VSSDEF INVOKED FROM DIALOG dialog IS NO LONGER SUPPORTEDExplanation: A dialog invoked the VSSDEF function, which is no longer supported.System Action: dialog completes with unpredictable results, generating RC=0.User Response: Use VSSALOC instead of VSSDEF and retry.Message Type: LOG.

KLUFG001 FOREGROUND SET FAILED FOR useridExplanation: Dialog command VSSFOREG failed.System Action: Return code 20 is set for the command.User Response: Retry the command.Message Type: REPLY.

KLUFT000 VSSFTMGR: DIALOG LOOP DETECTED FOR USER useridExplanation: An error in the controlling dialog causes the dialog to return immediately without moving a session to the foreground.System Action: The user window disappears.User Response: Review the message and correct the controlling dialog. If unable to locate the error, call Candle Customer Support.Message Type: LOG, VIEW.

KLUFT001 RESOURCE ERRORExplanation: An unexpected error has occurred in connection with processing a trigger dialog.System Action: The process is abnormally terminated.User Response: Contact Candle Customer Support.Message Type: ERROR.


KLUFT002 LOOP AVERTEDExplanation: An internal error was detected by CT/Engine. System Action: CT/Engine forces an abend with completion code U0100. The abend is associated with a single CT/Engine user, whose terminal will hang. System operation for other users will continue normally. CT/Engine will automatically create a dump.User Response: A VCANCEL command may be necessary to reinstate the hung user. Contact Candle Customer Support for help in resolving the error condition or in gathering the problem documentation that Candle requires to research the error condition.Message Type: ABEND.

KLUFU001 #VSSFUCB ERROR: SESSION STILL ACTIVEExplanation: An attempt was made to free a user control block while a session was still active.System Action: CT/Engine takes a diagnostic abend with completion code U0100. The abend is associated with a single CT/Engine user, whose terminal may hang. A VCANCEL command may be necessary to reinstate the hung user.User Response: Contact Candle Customer Support.Message Type: ABEND.

KLUFU101 WINDOW INTEGRITY ERRORExplanation: An internal error was detected.System Action: The user’s sessions are terminated.User Response: Contact Candle Customer Support.Message Type: ABEND.

KLUIB001 BUFFER SYNCHRONIZATION ERRORExplanation: While processing an inbound request, a synchronization error was detected for a virtual terminal buffer. This is a serious error.System Action: The address space terminates.User Response: Contact Candle Customer Support.Message Type: LOG.

KLUIN001 VIRTUAL SESSION SUPPORT INITIALIZATION COMPLETEExplanation: The successful initialization of virtual session support is logged to create an audit trail.System Action: None.User Response: None.Message Type: INFO.

KLUIN002 UNABLE TO LOAD VIRTUAL SESSION SUPPORT COMPONENT moduleExplanation: Virtual session support is unable to load the required component module. This error is usually caused by the absence of module from the CT/Engine load library.System Action: Initialization terminates.User Response: Look for additional information in messages in the KLVCMnnn format. Correct the error and restart virtual session support.Message Type: ALERT.


KLUIN003 KLUINVSS RKANPAR PARAMETERS:Explanation: Module KLUINVSS logs its startup parameters as they are read from RKANPAR. This is the header message and will be followed by message KLUIN004.System Action: None.User Response: None.Message Type: LOG.

KLUIN004 parametersExplanation: As the parameters in module KLUINVSS are read, a log audit trail is created.System Action: None.User Response: None.Message Type: LOG.

KLUOP001 VSHOW ARGUMENT LIST: argument listExplanation: Displays the arguments that were specified for this VSHOW command.System Action: None.User Response: None.Message Type: REPLY.

KLUOP002 session (appl,luname,cid,pool,logmode){TAKEDOWN | SETUP | ACTIVE[-F]}COMPRESSION {nnn% | OFF}Explanation: This reply from the VSHOW command appears if ACTIVE is specified. It follows KLUOP009 and displays information about a virtual session for the user. session is the virtual session ID; applid is the application name; luname is the logical unit name; cid is the VTAM network resource ID; pool is the virtual terminal pool name; and logmode is the VTAM logmode. TAKEDOWN means the session is currently being terminated; SETUP means the session is currently initializing; ACTIVE means the session is active. “-F” is displayed if the session is in the foreground at the user’s terminal.If compression is active, nnn displays the percentage of data stream compression; if not active, OFF is shown. The percentage is calculated by:

PLU-to-SLU-bytes - Term-Update-Bytes

Compression-Percent = --------------------------------------

PLU-to-SLU-bytes

System Action: None.User Response: None.Message Type: REPLY.


KLUOP003 PLU ---> SLU: MSGS(messages) BYTES(bytes)Explanation: This reply from the VSHOW command appears if STATS is specified. It lists the accumulated number of messages and bytes sent from the primary logical device to the secondary logical device.System Action: None.User Response: None.Message Type: REPLY.

KLUOP004 SLU ---> PLU: MSGS(messages) BYTES(bytes)Explanation: This reply from the VSHOW command follows KLUOP003 and lists the accumulated number of messages and bytes sent from the secondary logical unit to the primary logical unit.System Action: None.User Response: None.Message Type: REPLY.

KLUOP005 TERM REFRESH: MSGS(messages) BYTES(bytes)Explanation: This reply from the VSHOW command follows KLUOP004 and lists the accumulated number of messages and bytes sent to refresh the display on the terminal. A “refresh” occurs when the user switches between virtual sessions or an asynchronous pop-up is displayed.System Action: None.User Response: None.Message Type: REPLY.

KLUOP006 TERM UPDATE: MSGS(messages) BYTES(bytes)Explanation: This reply from the VSHOW command follows KLUOP005 and lists the accumulated amount of real traffic to the physical terminal in messages and bytes.System Action: None.User Response: None.Message Type: REPLY.

KLUOP007 SESSION session INACTIVEExplanation: This reply from the VSHOW command appears if INACTIVE is specified. The specified session is currently inactive.System Action: None.User Response: None.Message Type: REPLY.

KLUOP008 selected OF total USER(S), selected OF total SESSION(S) SELECTEDExplanation: This summary message lists the number of users and sessions selected by the VSHOW command options out of the total pool.System Action: None.User Response: None.Message Type: REPLY.


KLUOP009 userid {DISCONNECTED | userid (applid,luname,cid) ACTIVE [CONNECTED]}Explanation: This reply from the VSHOW command displays information about a single user. userid is the user’s ID. CONNECTED and DISCONNECTED indicate whether the user is attached to a terminal. ACTIVE means the user is currently active. applid is the application the user has logged onto; luname is the logical unit name; cid is the VTAM network resource id.System Action: None.User Response: None.Message Type: REPLY.

KLUOP010 TERM INPUT: MSGS(messages) BYTES(bytes)Explanation: This reply from the VSHOW command follows KLUOP006 and lists the accumulated number of input messages and bytes received from the physical terminal while it was logically connected to the virtual session.System Action: None.User Response: None.Message Type: REPLY.

KLUOP011 VCANCEL ARGUMENT LIST: argument listExplanation: Displays the arguments that were specified for this VCANCEL command. System Action: None.User Response: None.Message Type: REPLY.

KLUOP012 VCANCEL - EITHER USER OR ID REQUIREDExplanation: Either a user ID or a terminal ID must be entered with the VCANCEL command. System Action: The VCANCEL request is ignored.User Response: Reissue the command with a user ID or terminal ID.Message Type: REPLY, ERROR.

KLUOP013 VFORCE - REQUIRES USER=USERIDExplanation: You must specify a user ID to be forced.System Action: The VFORCE command is ignored.User Response: Reissue VFORCE with the USER= keyword.Message Type: REPLY, ERROR.

KLUOP014 VFORCE FOR USER userid INVALID. FOR CONFERENCE USE CCANCELExplanation: The user you were trying to force is using CL/CONFERENCE®. The VFORCE command will not work until you have used the CL/CONFERENCE command CCANCEL. System Action: The VFORCE command is ignored.User Response: Issue CCANCEL to cancel sessions for the CL/CONFERENCE user, then reissue VFORCE.Message Type: REPLY.


KLUOP015 USER userid FORCEDExplanation: The VFORCE command was successful.System Action: None.User Response: None.Message Type: REPLY.

KLUOP016 USER userid NOT FORCED: reasonExplanation: The VFORCE command failed for one of the following reasons (which is specified when the message appears):

System Action: As noted above.User Response: As noted above.Message Type: REPLY.

KLUOP017 VCANCEL FOR USER - userid MAY FAIL. VIRTUAL SESSIONS HUNG.Explanation: This user’s virtual sessions are hung.System Action: The system may not respond to the command.User Response: If the system does not respond, wait a few minutes then retry VCANCEL. If VCANCEL does not work, try VFORCE.Message Type: REPLY.

KLUOP018 cancelled OF total USER(S), cancelled OF total SESSION(S) CANCELLEDExplanation: This message lists the number of users and sessions cancelled by the VCANCEL command out of the total pool.System Action: None.User Response: None.Message Type: REPLY.

KLUOP019 VFORCE ARGUMENT LIST: argument listExplanation: Displays the arguments that were specified for this VFORCE command. System Action: None.User Response: None.Message Type: REPLY.

NOT FOUND The user ID was not found.

VCANCEL TERM NOT ISSUED

You must issue VCANCEL with the TERM operand before VFORCE.

VIRTUAL SESSION(S) FOUND

VFORCE found one or more virtual sessions and terminated them. Reissue VFORCE.


KLUOP020 VSSTRACE(ON | OFF) TRACING(NONE | [applid],luname)Explanation: This reply from the VSHOW command follows KLUOP009 and shows the trace status for the user. It is issued only when ACTIVE was specified. VSSTRACE shows the virtual session trace status, ON or OFF. TRACING shows the GTRACE options: NONE means GTRACE is not active for the user; applid is the application id, if ACB tracing is active, and luname is the logical unit name if terminal tracing is active.System Action: None.User Response: None.Message Type: REPLY.

KLUOP021 WINDOW(winid) TRACING(NONE | [applid],luname)Explanation: This reply from the VSHOW command follows KLUOP002. It shows the window ID winid for the virtual session or a minus sign (“-”) if the session is not in a window. TRACING shows the GTRACE options for this virtual session: NONE means GTRACE is not active; applid is the application ID, if ACB tracing is active, and luname is the logical unit name if terminal tracing is active.System Action: None.User Response: None.Message Type: REPLY.

KLUOP022 VIRTUAL SESSION SERVICES NOT INITIALIZED, VSHOW IGNOREDExplanation: The VSHOW command was issued before Virtual Session Services have fully initialized.System Action: The VSHOW request is ignored.User Response: Wait until message KLUIN001 is written to RKLVLOG, showing Virtual Session Services initialization is complete, then retry the command.Message Type: WARN.

KLUOP023 STATS INVALID WITH SUMMARY, STATS IGNORED.Explanation: The VSHOW command was entered with the SUMMARY and STATS keywords. These are mutually exclusive.System Action: The STATS keyword is ignored.User Response: If you wish statistics, reissue the VSHOW command without the SUMMARY keyword.Message Type: REPLY.

KLUOP030 VIRTUAL SESSION SERVICES NOT INITIALIZED, VCANCEL IGNORED.Explanation: The VCANCEL command was issued before Virtual Session Services have fully initialized.System Action: The VCANCEL request is ignored.User Response: Wait until message KLUIN001 is written to RKLVLOG, showing Virtual Session Services initialization is complete, then retry the command.Message Type: WARN.


KLUOP200 TRACE CLASS(USER) STATUS: USER(userid): {ENABLED | PENDING | DISABLED} *** END OF TRACE STATUS ***Explanation: These lines are the output for the VSSTRACE command when neither ON nor OFF was specified. They show the current status for each user for which tracing was requested. ENABLED means tracing is active; PENDING means the user is not logged on but a trace request will be issued when he does log on; DISABLED means tracing is currently inactive.System Action: None.User Response: None.Message Type: REPLY.

KLUOP201 TRACE REQUEST REJECTED. REQUIRED ARGUMENT NOT SPECIFIEDExplanation: A VSSTRACE command was specified without the required user ID.System Action: The VSSTRACE command is ignored.User Response: Reissue the VSSTRACE command with a user ID.Message Type: ERROR.

KLUOP202 TRACE USER (userid) {ENABLED | QUEUED | DISABLED}Explanation: The trace request for userid has been performed. ENABLED means tracing is active. QUEUED means tracing will start when userid logs on. DISABLED means tracing is not active.System Action: None.User Response: None.Message Type: REPLY.

KLUOP203 GTF INTERFACE HAS NOT BEEN ENABLEDExplanation: A VSSTRACE request has been issued for a resource but the GTF interface has not been enabled.System Action: The command continues, but GTF output will not be produced.User Response: Issue the GTF ON command to enable GTF tracing.Message Type: ALERT.

KLUPM001 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED LU luname USERID userid. ALL VIRTUAL SESSIONS CANCELLED.Explanation: A runaway application generated too many messages.System Action: Cancels sessions for this luname/user ID.User Response: None. This is an application problem.Message Type: ALERT.


KLUVT000 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED LU(luname) USERID:(userid). PHYSICAL SESSION CANCELLED.Explanation: An excessive number of outbound messages have been logged, causing the physical session to terminate.System Action: Physical session is cancelled.User Response: Make sure that there are no runaway applications. If there are no runaway applications, check the outbound message limit; it may be set too low.Message Type: LOG.

KLUVT001 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED LU(luname) USERID(userid). ALL VIRTUAL SESSIONS CANCELLED.Explanation: An excessive number of outbound messages have been logged. All virtual sessions are cancelled.System Action: None.User Response: Make sure that there are no runaway applications. If there are no runaway applications, check the outbound message limit; it may be set too low.

KLUXD001 QUERY REPLY DATA IS NOT VALID FOR USERID userExplanation: A 3270 datastream READ PARTITION QUERY command is sent to the user’s physical terminal device (if the logmode used by the physical terminal can be queried). When the device returns the requested replies, some basic validity checks are performed on the query reply data. This message is issued if any of these checks fail.System Action: Initialization is completed for the user, but the invalid query reply data is ignored. Any READ PARTITION QUERYs issued by applications on the virtual sessions are responded to with a single NULL query reply.User Response: At the time message KLUXD001 is sent to the RKLVLOG dataset, a snap of the query reply data that filed the validity checks is taken. The snap data is in the RKLVSNAP dataset and is identified as REQUESTED FROM KLUXQANA. Use timestamps in the RKLVLOG and RKLVSNAP data to correlate messages and snaps if multiple instances exist. Save these datasets and contact Candle Customer Support for further assistance.Message Type: LOG.

KLVAF001 NAF INITIALIZATION BYPASSEDExplanation: Either initialization library member KLVINNAF is empty or not defined. System Action: No accounting services are performed by CT/Engine. User Response: Contact Candle Customer Support.Message Type: INFO.


KLVAF002 SMF OPTION SELECTED, BUT JOBSTEP NOT APF AUTHORIZEDExplanation: The SMF option for the Network Accounting Facility (NAF) has been selected, but the CT/Engine job step is not authorized.System Action: The parameter is ignored.User Response: Either authorize the job step or remove the SMF option. Message Type: WARNING.

KLVAF003 RECORD TYPE n IS NOT COLLECTED BY SMF: SMFRTEST(r15)Explanation: The SMF record type specified in initialization library member KLVINNAF is not collected by SMF. 15 refers to the return code of the SMFRTEST macro instruction.System Action: The parameter is ignored.User Response: Refer to the IBM manual System Management Facilities for information on the SMFRTEST macro instruction.Message Type: WARNING.

KLVAF004 UNABLE TO ALLOCATE NAF DATASET: DSNAME(dsn)Explanation: The NAF dataset specified in initialization library member KLVINNAF cannot be allocated.System Action: CT/Engine terminates after any subsequent initialization routines are called.User Response: This message is accompanied by message KLVDA002, which gives a more specific reason why the dataset could not be allocated. Contact Candle Customer Support.Message Type: WARNING.

KLVAF005 NAF SMF RECORDING DISABLED, INVALID SMF RECORD NUMBER: smfrnoExplanation: During NAF initialization the SMF parameter in member KLVINNAF of RKANPAR was found to have a value that was less than 128 or greater than 255. smfrno is the invalid SMF record number that was specified.System Action: NAF SMF recording is disabled.User Response: Supply a valid SMF record number.Message Type: WARNING.

KLVAF006 NETWORK ACCOUNTING FACILITY INITIALIZED: DSNAME(dsn) SMF(arg) BLKSIZE(blksize)Explanation: The NAF facility is initialized with the attributes displayed.System Action: None.User Response: None.Message Type: INFO.


KLVAF007 NAF DATA SET RECORDING DISABLED, INVALID BLKSIZE SPECIFIED(badblk), MUST BE AT LEAST (blksize), MAXIMUM is 32767Explanation: During NAF initialization the BLKSIZE parameter in member KLVINNAF of RKANPAR was found to have a value that was not large enough to contain a NAF record. badblk is the invalid BLKSIZE that was specified. blksize is the minimum required BLKSIZE for the NAF dataset.System Action: NAF dataset recording is disabled.User Response: Supply a BLKSIZE that is at least blksize.Message Type: WARNING.

KLVAF008 NAF DATA SET RECORDING DISABLED, INVALID BUFNO SPECIFIED: bufnoExplanation: During NAF initialization the BUFNO parameter in member KLVINNAF of RKANPAR was found to have a value that was zero or greater than 99. bufno is the invalid BUFNO that was specified.System Action: NAF dataset recording is disabled.User Response: Supply a valid BUFNO.Message Type: WARNING.

KLVAF009 KLVINNAF RKANPAR PARAMETERS:Explanation: Module KLVINNAF logs its start-up parameters as they are read from RKANPAR. This is the header message and will be followed by message KLVAF010.System Action: None.User Response: None.Message Type: LOG.

KLVAF010 parametersExplanation: As the parameters in module KLVINNAF are read, a log audit trail is created.System Action: None.User Response: None.Message Type: LOG.

KLVAF013 UNABLE TO OPEN NAF DATASET: DSNAME(dsn) DCBDDNAM (ddname) R15(r15)Explanation: The NAF dataset specified in initialization library member KLVINNAF cannot be opened.System Action: CT/Engine terminates after any subsequent initialization routines are called.User Response: Examine the job log for other error messages concerning this dataset. The r15 field contains the return code from open. Message Type: WARNING.


KLVAF014 UNABLE TO LOAD KLVIONAFExplanation: One of the modules required for the NAF facility cannot be loaded.System Action: CT/Engine terminates after any subsequent initialization routines are called.User Response: If this message is preceded by message KLVCM003, then it will indicate why KLVIONAF could not be loaded. If message KLVCM003 is not found, then KLVIONAF is not in the RKANMODL library. Message Type: WARNING.

KLVAF101 SMFWTM SERVICE FAILED: R15(r15)Explanation: An attempt to use the SMFWTM service was unsuccessful; the return code is shown for reference.System Action: Any records contained in the block being written are lost.User Response: Refer to the IBM manual System Management Facilities for information on the SMFWTM macro instruction.Message Type: ALERT.

KLVAF102 NAF DATASET RECORDING DISABLED BY PERMANENT ERRORExplanation: NAF recording is disabled by an error. Possible errors are:® Dataset is full® Disk is full® I/O errorSystem Action: NAF recording terminates.User Response: Check to see if the dataset or disk is full. Either increase the size of the dataset or move it to another disk.Message Type: ALERT.

KLVAT001 "EVERY" REQUIRED WITH "REPEAT" KEYWORDExplanation: An AT command was entered with the REPEAT= keyword, which requires an EVERY= value.System Action: The command is ignored.User Response: Reissue the AT command with a non-zero EVERY= value.Message Type: ERROR.

KLVAT002 COULD NOT CREATE RESOURCE FOR AT COMMANDExplanation: An internal error has occurred while processing an AT ADD command. This is a ”should not occur” condition.System Action: The command is ignored.User Response: Contact Candle Customer Support.Message Type: ERROR.

KLVAT003 COULD NOT ESTABLISH EXITS FOR AT COMMANDExplanation: An internal error has occurred while processing an AT ADD command. This is a “should not occur” condition.System Action: The command is ignored.User Response: Contact Candle Customer Support.Message Type: ERROR.


KLVAT004 COMMAND TEXT TOO LONGExplanation: The CMD= keyword on an AT command was coded with a text string longer than 255 characters.System Action: The command is ignored.User Response: Reissue the AT command with a shorter CMD= value.Message Type: ERROR.

KLVAT005 CANCEL REQUIRES THE ID KEYWORDExplanation: An AT CANCEL command was issued without an ID= value.System Action: The command is ignored.User Response: Issue the AT LIST command with no operands to see all active AT commands, then reissue the original command with a valid ID= value.Message Type: ERROR.

KLVAT006 id ALREADY EXISTSExplanation: An AT ADD command was issued with an ID= value that is already active.System Action: The command is ignored.User Response: Issue the AT LIST command with no operands to see all active AT commands, then reissue the original command with a valid ID= value.Message Type: ERROR.

KLVAT007 id DOES NOT EXISTExplanation: An AT LIST or CANCEL command was issued with an ID= value that is not active.System Action: The command is ignored.User Response: Issue the AT LIST command with no operands to see all active AT commands, then reissue the original command with a valid ID= value.Message Type: ERROR.

KLVAT008 TIME MUST BE BETWEEN 00:00:00 and 23:59:59Explanation: An AT ADD command was issued with a TIME= value that is greater than 23:59:59 (11:59:59 PM).System Action: The command is ignored.User Response: Reissue the AT ADD command with a valid TIME= value.Message Type: ERROR.

KLVAT010 AT COMMAND ESTABLISHEDExplanation: This message confirms a successful AT ADD command.System Action: None.User Response: None.Message Type: REPLY.


KLVAT011 ID=id {DELAY=delay | TIME=time} EVERY=every REPEAT=repeatExplanation: This message is the first of three that report the values in effect for an AT command:


KLVAT012 OPERATOR=operid LAST=last DONE=done NEXT=nextExplanation: This message is the second of three that report the values in effect for an AT command:


KLVAT013 CMD=cmdExplanation: This message is the third of three that report the values in effect for an AT command. cmd is the command that will be executed.System Action: None.User Response: None.Message Type: REPLY.

KLVAT020 CURRENTLY ACTIVE AT COMMANDS:Explanation: This is the beginning of a list of active AT commands requested by an AT LIST command.System Action: None.User Response: None.Message Type: REPLY.

id The AT command’s identifier.

delay The time delay until the command was, or will be, first executed, if a delay was requested. Otherwise, time is the time the command was, or will be, first executed; NONE will be displayed if the command was first executed immediately.

every The time interval between command executions; it will be 00:00:00 if the command will be performed just once.

repeat The number of times the command will be performed.

operid The id of the CT/Engine operator who established the AT command.

last The time the command was last executed; NONE will be displayed if the command has not yet been executed.

done The number of times the command has been performed.

next The time the command will next be executed.


KLVAT021 NO AT COMMANDS ARE ACTIVEExplanation: An AT LIST command was issued but there are no AT commands in the system.System Action: None.User Response: None.Message Type: REPLY.

KLVAT030 id HAS BEEN CANCELLEDExplanation: An AT CANCEL command has been successfully completed for id.System Action: The AT command is removed from the system.User Response: None.Message Type: REPLY.

KLVBF001 INVALID BUFFER ANCHOR PASSED TO $FBUFExplanation: CT/Engine has detected a storage integrity error during buffer release processing.System Action: An abend U0200 is taken for the current task, which causes a dump of the current environment. Unaffected tasks in the address space continue normally. User Response: Contact Candle Customer Support.Message Type: REPLY.

KLVBU001 UNBIND-HOLD NOT EXPECTED: PLU($sclu) SLU($acid) CID($bwcid) POOL($vpname)Explanation: A CLSDST PASS was attempted by a virtual session application but the PASS operand was not specified on the VSM pool definition for this virtual terminal.System Action: The session start-up aborts.User Response: Change the VSM command to add the PASS operand for all applications that perform a CLSDST PASS.Note: TSO and NCCF are applications that always perform a CLSDST PASS. Applications that do not perform a CLSDST PASS cannot share a pool where the PASS operand is specified.Message Type: WARNING.

KLVBU002 MULTIPLE UNSOLICITED BINDS: PLU1($bwlu) CID1($bwcid) PLU2($bwlu) CID2($bwcid) SLU($acid) POOL($vpname)Explanation: An unsolicited BIND was received for SLU $acid before an expected UNBIND-HOLD was received for the current unsolicited BIND.System Action: CT/Engine terminates the session.


User Response: Note the error information below. Then, contact Candle Customer Support.

Message Type: WARNING.

KLVBU003 UNSOLICITED BIND NOT EXPECTED: PLU(plu) SLU(slu) CID(cid)Explanation: An unsolicited BIND was received by virtual terminal slu from application plu under the following conditions:® The UNSOLICITED BIND was received by a virtual terminal not defined in a

PASS or DEDICATE pool.

® The UNSOLICITED BIND was received by a virtual terminal defined in a PASS or DEDICATE pool after a previously established session is being terminated.

A previously established session can be terminated by:® User request

® Virtual terminal received an UNBIND HOLD from a CLSDST PASS issued by the application and the TIMEOUT interval specified in KLVINVSM expires.

® For a DEDICATE SESSLIM poll virtual terminal, VTAM fails to deliver the UNSOLICITED BIND in the time specified in KLVINVSM.

System Action: CT/Engine rejects the bind.User Response: If the application is issuing CLSDST PASS, it must be assigned a PASS or DEDICATE pool. If the virtual terminal slu belongs to a SESSLIM DEDICATE pool then adjust the timeout interval or ignore the message. See CT Engine: Customization Guide for details.Message Type: WARNING.

KLVBU004 VIRTUAL SESSION ESTABLISHMENT TIMEOUT FOR lunameExplanation: The CLSDST-PASS operation for luname did not complete in the time specified in KLVINVSM.System Action: The virtual session is terminated.User Response: None.Message Type: WARNING.

$bwlu Application that sent the first bind.

$bwcid CID of the session between p1 and $acid.

$bwlu Application that sent the second bind.

$bwcid CID of the session between p2 and $acid.

$acid Virtual terminal ID.

$vpname Pool that s was selected from.


KLVCM001 FORCED DELETION PENDING: MODULE(modname)Explanation: The module modname has been specified for deletion from the CT/Engine address space, but the module is still in use. When the module is no longer in use, an attempt is made to delete it. Currently the only external cause of this message is the REFRESH MODULE command. System Action: None.User Response: None.Message Type: REPLY, INFO.

KLVCM002 FORCED DELETION COMPLETE: MODULE(module)Explanation: The specified module was deleted from the CT/Engine address space.System Action: None.User Response: None.Message Type: INFO.

KLVCM003 LOAD FAILURE: MODULE(modname) CODE(r1) REASON(r15)Explanation: An attempt by CT/Engine to load the module modname into its address space failed. This error is most likely caused by the absence of the module in the CT/Engine load library.System Action: The module is not loaded and cannot be used.User Response: Refer to IBM’s Assembler Programming Reference to determine the reason the LOAD macro instruction failed. Use r1 and r15 to identify the cause.Message Type: ERROR, WARNING.

KLVDA001 IDCAMS VERIFY ERROR: R15(r15)Explanation: After dynamically allocating a VSAM cluster, CT/Engine has run an IDCAMS VERIFY against the data set. The VERIFY completed with a non-zero return code, r15.System Action: Depends on the reason for the error.User Response: Consult IBM’s Access Method Services to determine the cause of the error and take appropriate corrective action. Examine RKLVLOG for this information, which precedes KLVDA001:® Messages KLVDA003 and KLVDA007. These mark the beginning and end of

the IDCAMS VERIFY output messages, and include the DD name that was processed.

® IDCAMS messages. These will include return and reason codes for the error.

Note: The most frequent reason for a non-zero return code is when CT/Engine is restarted after an abnormal termination, or when the cluster is currently opened by another task. VERIFY will detect that the cluster’s structural information (end of file marker,and so on) does not match the catalog and will repair it. This is normal for VSAM processing, and is reported by the IDCAMS message VSAM OPEN RETURN CODE IS 168.

Message Type: ERROR.


KLVDA002 SVC 99 ERROR: R15(r15) ERROR(s99error) INFO(s99info)Explanation: An attempt by SVC99 to dynamically allocate or unallocate a file failed. This message may be immediately followed by one or two IBM messages that describe the error in more detail. r15 is the return code from SVC 99 and s99error and s99info are the error and info codes returned by SVC 99 in the dynamic allocation request block.System Action: The action depends on the reason for the error.User Response: Consult IBM’s Assembler Programming Reference for the meaning of the SVC 99 (DYNALLOC) return, reason, and info codes. Consult the appropriate IBM Messages manual for the meaning of any IBM messages that follow KLVDA002.Message Type: ERROR.

KLVDA003 PERFORMING VSAM FILE VERIFICATION: FILE(ddname)Explanation: After dynamically allocating a data set to the DD named ddname, CT/Engine has determined that it is a VSAM cluster. To ensure that the cluster structure is correct, CT/Engine will invoke the IBM IDCAMS utility to perform a VERIFY against the data set. Between the KLVDA003 and KLVDA007 messages are those issued by IDCAMS.System Action: None.User Response: None.Message Type: LOG.

KLVDA004 UNABLE TO ATTACH IDCAMS: R15(r15)Explanation: CT/Engine issued an ATTACH macro to invoke IDCAMS to perform a VSAM file verification. The ATTACH failed with the return code r15.System Action: The VSAM file verification is terminated. The data set remains allocated and is still available for use by the requester.User Response: Consult IBM’s Assembler Programming Reference to determine the reason the ATTACH macro failed and take appropriate corrective action.Message Type: ALERT.

KLVDA005 LOAD FAILED FOR IKJEFF18 (DAIRFAIL) R1(r1) R15(r15)Explanation: An attempt to load the IBM module IKJEFF18 failed. This module is used to extract descriptive messages after a dynamic allocation or unallocation failure. r1 is the abend code associated with this error and r15 is the reason code.System Action: Additional IBM error messages regarding the failed dynamic allocation or unallocation request will not be displayed.User Response: Contact your installation systems programmer with the abend and error codes in this message to determine the cause of the error.Message Type: ERROR.


KLVDA006 ERROR IN IKJEFF18 (DAIRFAIL) R15(r15)Explanation: An error occurred in the IBM module IKJEFF18 while attempting to extract descriptive error messages for a failed dynamic allocation or unallocation request. r15 is the return code from module IKJEFF18.System Action: Additional IBM error messages regarding the failed dynamic allocation or unallocation request will not be displayed.User Response: Contact your installation systems programmer with the R15 value in this message to determine the cause of the error.Message Type: ERROR.

KLVDA007 VSAM FILE VERIFICATION COMPLETE: R15(r15) FILE(ddname)Explanation: The IDCAMS VERIFY request for file ddname has completed with return code r15.System Action: None.User Response: If r15 is non-zero, message KLVDA001 will follow. Refer to the description of that message for possible actions.Message Type: LOG.

KLVDE001 error message COMMAND(DEDICATE) ‘text’Explanation: A DEDICATE command was issued with a syntax error.System Action: The dedicated session is not started.User Response: Examine error message to determine what the error was. text is the text at or near the location of the error. Correct the error and reissue the DEDICATE command.Message Type: ERROR.

KLVDE002 DEDICATE DIALOG UNAVAILABLE: DIALOG(dialog) LANGUAGE(language)Explanation: Dialog dialog, specified on a DEDICATE command, does not exist or cannot be refreshed from the DD indicated by the language code language.System Action: The dedicated session is not started.User Response: Issue the operator command, REFRESH D dialog LANG=language. If the response indicates the dialog does not exist, ensure that the name is correct and that the dialog is in the appropriate dialog library concatenation (RKANPlanguage). If the dialog cannot be refreshed because of errors, correct the errors. In either case, reissue the DEDICATE command after making the appropriate corrections.Message Type: ERROR.

KLVDE003 DEDICATED SESSION STARTED: DEVICE(name) POLLING INTERVAL IN SECONDS=(seconds)Explanation: A dedicated session has been started, as requested with the DEDICATE command.System Action: None.User Response: None.Message Type: REPLY.


KLVDE004 UNABLE TO ALLOCATE PSEUDO-ACB RESOURCE: DEVICE(name)Explanation: A temporary storage shortage caused a memory request to fail.System Action: The dedicated session is not started.User Response: Retry later, or increase the job region size in the JCL and retry.Message Type: ERROR.

KLVDE005 UNABLE TO LOAD KLVIODED: DEVICE(name)Explanation: An I/O support module for dedicated operation could not be loaded.System Action: The dedicated session is not started.User Response: Verify that KLVIODED is in the RKANMODL load library concatenation and is executable. If it is available and executable, contact Candle Customer Support.Message Type: ERROR.

KLVDE006 UNABLE TO ALLOCATE DEDICATED DEVICE: addressExplanation: The unit resource specified could not be allocated. RKLVLOG may contain other messages, such as KLVDAnnn, that describe the allocation failure.System Action: The dedicated session is not started.User Response: Specify a unit that exists, is online, and is not allocated to another job.Message Type: ERROR.

KLVDE007 UNABLE TO ALLOCATE PSEUDO-SCB RESOURCEExplanation: A temporary storage shortage caused a memory request to fail.System Action: The dedicated session is not started.User Response: Retry later, or increase the job region size and retry.Message Type: ERROR.

KLVDE008 UNABLE TO OPEN DEDICATED DCB: DDNAME(name) [unit-address]Explanation: The ddname specified in the DEDICATE command could not be opened, typically because the ddname was not in the JCL for the job.System Action: The dedicated session is not started.User Response: Review the JES SYSLOG for IBM data management messages (usually prefaced by IEC) to determine the reason the open failed. For a missing ddname, add the DD statement to the JCL, or use the alternate form of the DEDICATE command to have the unit dynamically allocated.Message Type: ERROR.

KLVDE009 UNABLE TO ACTIVATE DEDICATED SESSION: DEVICE(name)Explanation: An I/O error occurred while displaying the initial screen on a dedicated device.System Action: The dedicated session is not started.User Response: Correct the cause of the I/O error and reissue the command.Message Type: ERROR.


KLVDE010 DEDICATE I/O ERROR: WECBCC(code) SIOCC(code) STBYT(status) SENS0(sensbyte-0) SENS1(sensbyte-1) DEVICE(name)Explanation: An I/O error occurred on the identified device during a write operation. The ECB condition code and the SIO instruction return code are displayed, along with the status byte and sense bytes 0 and 1, to indicate the cause of the error.System Action: The I/O is retried every 2 seconds, up to 10 times. If the I/O does not succeed, the dedicated session is terminated.User Response: If this message occurs frequently, have the device diagnosed, then contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDE011 DEDICATE I/O ERROR: RECBCC(code) SIOCC(code) STBYT(status) SENS0(sensbyte-0) SENS1(sensbyte-1) DEVICE(name)Explanation: An I/O error occurred on the identified device during a read operation. The ECB condition code and the SIO instruction return code are displayed, along with the status byte and sense bytes 0 and 1, to indicate the cause of the error.System Action: The I/O is retried every 2 seconds, up to 10 times. If the I/O does not succeed, the dedicated session is terminated.User Response: If this message occurs frequently, have the device diagnosed, then contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDE012 DEVICE TYPE ucb-type NOT SUPPORTED BY DEDICATEExplanation: The unit type specified by the DEDICATE command or allocated to the ddname is not a 3270-type device. ucb-type is the UCBTYP field, in hexadecimal.System Action: The dedicated session is not started.User Response: Change the unit specification to a 3270-type device and retry the DEDICATE command.Message Type: ERROR.

KLVDE013 DEDICATED SESSION STOPPED: DEVICE(name)Explanation: The session is terminated for the identified device, as requested.System Action: None.User Response: None.Message Type: REPLY.

KLVDE014 UNABLE TO LOAD KLVEXDED: DEVICE(name)Explanation: An I/O support module for dedicated operation could not be loaded.System Action: The dedicated session is not started.User Response: Verify that KLVEXDED is in the RKANMODL load library concatenation and is executable. If it is available and executable, contact Candle Customer Support.Message Type: ERROR.


KLVDE015 SPLEVEL DOES NOT SUPPORT 4-DIGIT UNIT ADDRESSESExplanation: A DEDICATE DEV-XXXX command was issued to allocate a device with a 4-digit unit address. This level of MVS does not support 4-digit unit addresses.System Action: The dedicated session is not started.User Response: Reissue the DEDICATE command with UNIT-XXX to allocate a device with a 3-digit unit address.Message Type: ERROR.

KLVDE102 DEDICATED OPERATOR INITIALIZATION IN PROGRESSExplanation: A dedicated session has begun its initialization. This message is issued when the NODELAY keyword was specified on the DEDICATE command.System Action: None.User Response: None.Message Type: LOG, VIEW.

KLVDF000 SEARCH STRING > 256 BYTES NOT SUPPORTED BY INDEXExplanation: A search string longer than 256 characters was passed to the INDEX dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the INDEX function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it so that the search string is 256 characters or shorter. Refer to the Dialog Language Reference Manual for more information on INDEX. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF001 MESSAGE FROM DIALOG dialog [LU(unit) APPL(application)] ‘text’Explanation: A LOG dialog function was issued by dialog, requesting that text be written to the CT/Engine RKLVLOG and VIEWLOG files. If dialog is not a non-terminal dialog, the controlling application and logical unit name associated with it are also shown.

Note: The actual contents of text depend on what LOG options were requested, but always directly follow the KLVDF001 message.

System Action: None.User Response: None.Message Type: LOG, VIEW.

KLVDF002 NEGATIVE OFFSET NOT SUPPORTED BY nameExplanation: A negative string offset was passed to the name dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the name function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to specify a zero or positive offset into the source string. Refer to the Dialog Language Reference Manual for more information on name. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDF003 NEGATIVE LENGTH NOT SUPPORTED BY nameExplanation: A negative string length was passed to the name dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the name function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct the call to name to specify a zero or positive result length. Refer to the Dialog Lanuage Reference Manual for more information on name. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF004 X2D STRING LENGTH LIMIT EXCEEDEDExplanation: The SSPL dialog function X2D was invoked with a string that is longer than 8 characters. Message KLVDM015 follows this message and contains information about the dialog that contains the X2D function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it so that the string is 8 characters or shorter. Refer to the Dialog Lanuage Reference Manual for more information on X2D. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF005 X2D STRING CONTAINS NON-HEX CHARACTERSExplanation: The SSPL dialog function X2D was invoked with a string that contains characters other than the digits 0–9 and characters a–f and A–F. Message KLVDM015 follows this message and contains information about the dialog that contains the X2D function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it so that the string contains only 0–9, a–f, and A–F. Refer to the Dialog Lanuage Reference Manual for more information on X2D. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF006 TRIM TYPE type NOT SUPPORTED BY TRIM.Explanation: An invalid trim type specification was passed to the TRIM dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the TRIM function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to specify BOTH, LEADING or TRAILING as the trim type. Refer to the Dialog Lanuage Reference Manual for more information on TRIM. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDF007 INSUFFICIENT STORAGE FOR RESULT OF REPEAT FUNCTIONExplanation: The storage required to contain the result of a REPEAT dialog function was larger than the maximum allowed by CT/Engine. Message KLVDM015 follows this message and contains information about the dialog that contains the REPEAT function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, change it to request a smaller result string (typically no more than 32K characters). Refer to the Dialog Lanuage Reference Manual for more information on REPEAT. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF008 NEGATIVE COUNT NOT SUPPORTED BY REPEAT FUNCTIONExplanation: A negative repetition count was passed to the REPEAT dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the REPEAT function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to specify a positive repetition count. Refer to the Dialog Lanuage Reference Manual for more information on REPEAT. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF009 INVALID DBCS DATA DETECTED BY REPEAT FUNCTIONExplanation: Invalid data was detected by the REPEAT dialog function while processing Double Byte Character Set (DBCS) data. Message KLVDM015 follows this message and contains information about the dialog that contains the REPEAT function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to validate the DBCS data before invoking the REAPEAT dialog function. Refer to the Dialog Lanuage Reference Manual for more information on REPEAT. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF011 MESSAGE FROM DIALOG dialog [LU(unit) APPL(application)] ‘text’Explanation: A WTO dialog function was issued by dialog, requesting that text be written to the CT/Engine VIEWLOG file and MVS consoles. If dialog is not a non-terminal dialog, the controlling application and logical unit name associated with it are also shown.

Note: The actual contents of text depend on what WTO options were requested, but always directly follow the KLVDF011 message.

System Action: None.Message Type: INFO, VIEW.


KLVDF021 LOGOFF UNABLE TO FIND LOGICAL UNITExplanation: The LOGOFF dialog function was executed, but no logical unit was associated with the dialog. Either the dialog is not controlling any logical units, or the logical unit was already logged off. Message KLVDM015 follows this message and contains information about the dialog that contains the LOGOFF function.System Action: CT/Engine terminates the dialog.User Response: None.Message Type: LOG, VIEW.

KLVDF031 LINK ARGUMENT LIST INVALIDExplanation: The LINK dialog function failed because a null string was passed as the module name. Message KLVDM015 follows this message and contains information about the dialog that contains the LINK function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a module name to LINK. Refer to the Dialog Lanuage Reference Manual for more information on LINK. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF032 LINK FAILED FOR moduleExplanation: The LINK dialog function could not load the requested module, module. Either the module can not be found in the RKANMODL libraries or an error occurred during the load process. Message KLVDM015 follows this message and contains information about the dialog that contains the LINK function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: Ensure that module resides in a library concatenated to the RKANMODL DD statement. If the module is present examine RKLVLOG for a KLVCM003 message, which is issued when a load request fails.Message Type: LOG, VIEW.

KLVDF033 ABEND Ssss Uuuuu IN USER MODULE module AT DISPLACEMENT xxxxxxExplanation: A user program, module, invoked by the LINK dialog function, abended at offset xxxxx. The system completion code is sss and the user completion code is uuuu. The system code is displayed as three hexadecimal digits. The user code is translated to decimal and will be displayed in four positions. Message KLVDM015 follows this message and contains information about the dialog that contains the LINK function.System Action: A dump is produced for RKLVSNAP or the system dump data sets. CT/Engine then terminates the dialog and the user’s session.User Response: Examine the dump to determine the cause of the failure.Message Type: LOG, VIEW.


KLVDF034 USER MODULE module DOES NOT START WITH NOPExplanation: A user program, module, invoked by the LINK dialog function, does not have a proper NOP as the first instruction at the entry point. Message KLVDM015 follows this message and contains information about the dialog that contains the LINK function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: Correct the user program so that the first instruction at the entry point is a NOP of the form 4700xxxx, where xxxx is the desired size of the user work area passed in R2.Message Type: LOG, VIEW.

KLVDF041 TIMEOUT UNABLE TO FIND LOGICAL UNITExplanation: The logical unit associated with the TIMEOUT dialog is not found, probably because the logical unit has already been logged off.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, refer to the Dialog Lanuage Reference Manual for more information on TIMEOUT. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF061 PASS FAILED, R15(rtncd) REQSTAT(stat)Explanation: The PASS dialog function failed. The REQSTAT field contains the sense data returned by the request. Message KLVDM015 follows this message and contains information about the dialog that contains the PASS function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: Use the supplied sense information to determine the cause of the error. If the dialog is one that you have created or modified, refer to the Dialog Lanuage Reference Manual for more information on PASS.Message Type: LOG, VIEW.

KLVDF062 INVALID PASS ARGUMENT LISTExplanation: The PASS dialog function failed because the destination name was not supplied. Message KLVDM015 follows this message and contains information about the dialog that contains the PASS function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, refer to the Dialog Lanuage Reference Manual for more information on PASS. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDF063 PASS FUNCTION: INVALID QOPTION: qoptionExplanation: The PASS dialog function failed because the QOPTION specified for SIMLOGON is invalid. The only valid option is ‘QSESSLIM’. Message KLVDM015 follows this message and contains information about the dialog that contains the PASS function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a valid QOPTION. Refer to the Dialog Lanuage Reference Manual for more information on PASS. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF081 BEEP UNABLE TO FIND LOGICAL UNITExplanation: The BEEP dialog function is unable to find the logical unit of the current dialog. This error should occur only when the current session is terminated. Message KLVDM015 follows this message and contains information about the dialog that contains the BEEP function.System Action: CT/Engine terminates the dialog.User Response: None.Message Type: LOG, VIEW.

KLVDF091 resource UNABLE TO FIND LOGICAL UNITExplanation: In response to a dialog OPNDST request, the specified logical resource is not known to CT/Engine.System Action: The OPNDST request is ignored.User Response: If this error occurs while running CL/SUPERSESSION, specify a previously defined logical resource. Refer to the Dialog Lanuage Reference Manual for more information on OPNDST. Otherwise, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF101 UNKNOWN RETURN CODE RECEIVED FROM KLV$SAM. RC(rc).Explanation: During the execution of a SAM dialog function an unknown return code, rc, was received from a CT/Engine service routine.System Action: The SAM dialog function returns with the indicated condition code.User Response: Contact Candle Customer Support with the rc value.Message Type: LOG, VIEW.


KLVDF131 event IS AN INVALID EVENT CODEExplanation: An invalid event code, event, was passed to the ON dialog function. The only valid option is ‘TIMEOUT’. Message KLVDM015 follows this message and contains information about the dialog that contains the ON function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a valid event code. Refer to the Dialog Lanuage Reference Manual for more information on ON. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF132 ON TIMEOUT UNABLE TO FIND LOGICAL UNITExplanation: In response to a dialog ON function request, the logical resource specified is not known to CT/Engine. Message KLVDM015 follows this message and contains information about the dialog that contains the ON function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If this error occurs while running CL/SUPERSESSION®, specify a previously defined logical resource. Refer to the Dialog Lanuage Reference Manual for more information on ON. Otherwise, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF201 ABCHOICE: INVALID HANDLEExplanation: An invalid handle was passed to the ABCHOICE dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the ABCHOICE function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a valid handle (created by the ABCREATE dialog function). Ensure that the handle has not been freed by an ABFREE dialog function. Refer to the Dialog Lanuage Reference Manual for more information on ABCHOICE. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF211 ABFREE: INVALID HANDLEExplanation: An invalid handle was passed to the ABFREE dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the ABFREE function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a valid handle (created by the ABCREATE dialog function). Ensure that the handle has not been freed by a prior ABFREE. Refer to the Dialog Lanuage Reference Manual for more information on ABFREE. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDF221 ABSHOW: INVALID HANDLEExplanation: An invalid handle was passed to the ABSHOW dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the ABSHOW function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a valid handle (created by the ABCREATE dialog function). Ensure that the handle has not been freed by an ABFREE dialog function. Refer to the Dialog Lanuage Reference Manual for more information on ABSHOW. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDF231 ABSELECT: INVALID HANDLEExplanation: An invalid handle was passed to the ABSELECT dialog function. Message KLVDM015 follows this message and contains information about the dialog that contains the ABSELECT function.System Action: CT/Engine terminates the dialog and the user’s session.User Response: If the dialog is one that you have created or modified, correct it to pass a valid handle (created by the ABCREATE dialog function). Ensure that the handle has not been freed by an ABFREE dialog function. Refer to the Dialog Lanuage Reference Manual for more information on ABSELECT. If the error is in a Candle product dialog, contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDI001 KLVWAIT INVOKED FROM UNSUPPORTED ENVIRONMENTExplanation: CT/Engine dispatcher was invoked from SRB mode.System Action: CT/Engine abends U0200. User Response: Contact Candle Customer Support.Message Type: REPLY.

KLVDL001 INVALID LOGON STRING, EXCESS IGNOREDExplanation: The userdata passed to the KLVENTRY dialog contains more than five subfields.System Action: The excess fields are ignored.User Response: Correct the userdata definition to contain no more than five fields, separated by nulls. Valid fields are user ID, password, group, account, and procedure.Message Type: None.

KLVDL002 key IS NOT ACTIVEExplanation: A function key that is not assigned a function was pressed.System Action: The key is ignored.User Response: Refer to the bottom of the display panel for a list of active keys.Message Type: None.


KLVDL003 dlg: systerm Desc=descriptor, Charset=charset, CGCSGID=cgcsgid, APL support=supportExplanation: This message is generated when logging onto a CUA™ application. dlg is the dialog that determines whether the terminal will support APL characters when the screen is displayed. systerm is the terminal-id for the current session. The descriptor defines one terminal storage and symbol-set characteristics entry. The charset is the terminal storage identification: X’00’ to ‘07’. The cgcsgid is the coded graphic character set global identifier value. The support value of 0 indicates that APL is not supported, while a value of 1 indicates that APL is supported.System Action: None.User Response: Refer to the values in the message to resolve problems with APL support for a given terminal.Message Type: None.

KLVDL101 appl / lang / ddname: INVALID APPLIDExplanation: A CT/Engine-based application has invoked the help processor with an invalid parameter list. appl is the product code, which is incorrect. lang is the language code. ddname is the associated help file.System Action: The help processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL102 appl / lang / ddname: INVALID LANGUAGEExplanation: A CT/Engine-based application has invoked the help processor with an invalid parameter list. appl is the product code. lang is the language code, which is incorrect. ddname is the associated help file.System Action: The help processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL103 appl / lang / ddname: TBCREATE FAILED FOR table; RC=rcExplanation: The CT/Engine help processor cannot create the table table which will contain help information. rc is the return code from the TBCREATE SSPL dialog function. appl is the product code. lang is the language code. ddname is the associated help file.System Action: The help processor stops processing either the glossary or index.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDL104 appl / lang / ddname: IPC CREATE FAILED FOR qname; RC=rcExplanation: The CT/Engine help processor cannot create the communications queue qname for its internal processing. rc is the return code from the IPC CREATE SSPL dialog function. appl is the product code. lang is the language code. ddname is the associated help file.System Action: The help processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL105 dlg: DD(ddname) - KLVRDIR FAILED; RC=rcExplanation: The CT/Engine help processor cannot read the directory of the help library allocated to ddname. dlg is the dialog that has detected the error; rc is the return code from the utility program that was reading the directory.System Action: The help processor terminates.User Response: Ensure that the CT/Engine address space has the DD ddname allocated to it and that it points to a PDS containing help text. If a security package such as RACF™ is being used, the CT/Engine address space must have read access to the help libraries.Otherwise, save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: None.

KLVDL106 dlg: DD(ddname) - [INDEX | GLOSSARY] MEMBER(mem) PROCESSING FAILED; RC=rcExplanation: The CT/Engine help processor could not process the help member mem to extract the index or glossary information. dlg is the dialog that has detected the error, ddname is the DD name of the associated help library, and rc is the return code from the utility program that was processing mem.System Action: The help processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: None.

KLVDL107 appl / lang / ddname: IPC DEQUEUE INVALID HANDLEExplanation: During shutdown processing, the CT/Engine help processor could not release its communications queue. appl is the product code. lang is the language code. ddname is the associated help file.System Action: The help processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDL108 appl / lang / ddname: IPC DEQUEUE CONTENTIONExplanation: During shutdown processing, the CT/Engine help processor detected contention while accessing its communications queue. appl is the product code. lang is the language code. ddname is the associated help file.System Action: The help processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL109 appl / lang / ddname: NO [INDEX | GLOSSARY] ENTRIES GENERATEDExplanation: The CT/Engine help processor did not find any index or glossary entries during initialization of a CT/Engine-based application. appl is the product code. lang is the language code. ddname is the associated help file.System Action: The help index or glossary will not be available.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL110 dlg: [INDEX | GLOSSARY] TABLE(table) CANNOT BE OPENED; RC=rcExplanation: While attempting to respond to a help request, the CT/Engine help processor was unable to open the table table that contains help index or glossary information. dlg is the dialog that has detected the error; rc is the return code from the TBOPEN SSPL dialog function.System Action: The help processor terminates; help or the glossary is not available for the application.User Response: Review the CT/Engine RKLVLOG for other KLVDLnnn messages that may have been issued, and respond as directed.Otherwise, save the RKLVLOG and contact Candle Customer Support.Message Type: None.

KLVDL111 appl / lang / ddname / member: MEMBER NOT FOUNDExplanation: While attempting to update a help index or glossary table, the CT/Engine help processor was unable to locate the PDS member in the ddname file. appl is the product code. lang is the language code.System Action: No further processing is performed for member; the help processor continues with any other pending requests.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDL112 appl / lang / ddname / member: NO PRIMARY INDEX FOR termExplanation: While attempting to update a help index table, the CT/Engine help processor detected an error in PDS member, member, in the ddname file. term is the data associated with the error. appl is the product code. lang is the language code.System Action: term is ignored; the help processor continues with any other pending requests.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL113 dlg: TBCREATE FAILED FOR table; RC=rcExplanation: The CT/Engine date processor cannot create the table table which will contain date formatting information. dlg is the dialog that has detected the error; rc is the return code from the TBCREATE SSPL dialog function.System Action: The date processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: None.

KLVDL114 dlg: IPC CREATE FAILED FOR qname; RC=rcExplanation: The CT/Engine date processor cannot create the communications queue qname for its internal processing. dlg is the dialog that has detected the error; rc is the return code from the IPC CREATE SSPL dialog function.System Action: The date processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: None.

KLVDL115 dlg: IPC DEQUEUE INVALID HANDLE; RC=rcExplanation: During shutdown processing, the CT/Engine date processor could not release its communications queue. dlg is the dialog that has detected the error; rc is the return code from the IPC DEQUEUE SSPL dialog function.System Action: The date processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: None.

KLVDL116 dlg: IPC DEQUEUE CONTENTION; RC=rcExplanation: During shutdown processing, the CT/Engine date processor detected contention while accessing its communications queue. dlg is the dialog that has detected the error; rc is the return code from the IPC DEQUEUE SSPL dialog function.System Action: The date processor terminates.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: None.


KLVDL117 appl / lang / ddname: PDS SETWRT FAILED; RC=rcExplanation: While attempting to read a PDS directory, the CT/Engine help processor received return code rc from the PDS SSPL dialog function. appl is the product code. lang is the language code. ddname is the associated help file.System Action: No help or glossary information is available.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL118 appl / lang / ddname / member: MISSING INCLUDE NAMEExplanation: While attempting to update a help index table, the CT/Engine help processor detected an error in PDS member, member, in the ddname file. appl is the product code. lang is the language code.System Action: term is ignored; the help processor continues with any other pending requests.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL119 appl / lang / ddname / member: [INDEX | GLOSSARY] TBMOD FAILED RC=rcExplanation: While attempting to update a help index or glossary table, the CT/Engine help processor received an error (rc) on a TBMOD request. member is the PDS member being processed, which resides in the ddname file. appl is the product code. lang is the language code.System Action: Further processing for the help index or glossary is terminated.User Response: Save the CT/Engine RKLVLOG and contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDL120 appl / lang / ddname: GLOSSARY/INDEX SHUTDOWN COMPLETEExplanation: The CT/Engine help processor received a “quit” request and has terminated the help glossary and index tables normally. appl is the product code. lang is the language code. ddname is the associated help file.System Action: None.User Response: None.Message Type: LOG, VIEW.

KLVDL121 appl / lang / ddname: GLOSSARY/INDEX STARTUP COMPLETEExplanation: The CT/Engine help processor has completed initialization of the help glossary and index tables. appl is the product code. lang is the language code. ddname is the associated help file.System Action: None.User Response: None.Message Type: LOG, VIEW.


KLVDL201 TABLE action REQUEST FROM USER(userid) TERM(termid) FOR tableExplanation: The KLVTBULD SSPL dialog has been invoked to load or unload table. action is LOAD or UNLOAD, userid is the user, and termid is the terminal that invoked KLVTBULD.System Action: The load or unload request continues. Message KLVDL202 may follow this message if table is being loaded with a different name.User Response: None.Message Type: INFO.

KLVDL202 NEW TABLE NAME IS newnameExplanation: The KLVTBULD SSPL dialog has been invoked to load a table with a name (newname) different than the original name.System Action: The load or unload request continues.User Response: None.Message Type: INFO.

KLVDL300 appl USEREXIT(dlg) RETURNED INVALID RESULT(rc)Explanation: A programming error has been detected in dialog application appl.System Action: The dialog application is terminated.User Response: Save the contents of this message and contact Candle Customer Support.Message Type: LOG,VIEW.

KLVDL301 appl apdlg tkdlg textExplanation: Dialog application appl has requested that debugging information be written to RKLVLOG. Message KLVDL302 may follow this message.System Action: None.User Response: None.Message Type: LOG,VIEW.

KLVDL302 USEREXIT(dlg) KEY(key) TEXT(TEXT)Explanation: This message follows KLVDL301 and contains debugging information.System Action: None.User Response: None.Message Type: LOG,VIEW.

KLVDL303 appl USEREXIT(dlg) DID NOT RETURN A SYSKEY VALUEExplanation: A programming error has been detected in dialog application appl.System Action: The dialog application is terminated.User Response: Save the contents of this message and contact Candle Customer Support.Message Type: LOG,VIEW.


KLVDL400 TERMINAL OUTPUT WILL BE FORCED TO {UPPER CASE | MIXED CASE}Explanation: The KLVCASE dialog has been invoked to force subsequent logons to Candle SSPL-based products to be displayed in upper or mixed case.System Action: None.User Response: None.Message Type: LOG,VIEW. The message is also written to the MVS SYSLOG.

KLVDM001 MINIMUM/MAXIMUM OPTIONS MUTUALLY EXCLUSIVE: RKANPENU dialog LINE lineExplanation: The MINIMUM and MAXIMUM options specified on a )BODY dialog statement are mutually exclusive. The associated dialog and line number are shown for reference.System Action: Panel interpretation fails.User Response: Correct the error and try to refresh the panel.Message Type: WARNING.

KLVDM002 STRING VARIABLE TOO LONGExplanation: The CT/Engine variables manager detected an attempt to use a string longer than approximately 30,000 bytes.System Action: The thread is terminated with a U0100 abend, sending a dump to the RKLVSNAP file and/or the system’s dump datasets.User Response: Retain the CT/Engine run sheets, dump files, this message, and the MVS system log, then contact Candle Customer Support.Message Type: Abend.

KLVDM003 VARIABLE NAME EXPECTED: library(dialog) LINE(line)Explanation: The BODY section of dialog dialog contains an input field that does not contain a variable name, or a variable name prefix (typically an ampersand, &) that is not followed by a variable name. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, View.

KLVDM004 ATTRIBUTE CONFLICT FOR ATTR(attr) library(dialog) LINE(line)Explanation: The specified attribute, attr, in the BODY section of dialog dialog, conflicts with either an attribute that was previously defined or the variable name prefix (usually an ampersand, &). library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOV, VIEW.


KLVDM005 VARIABLE NAME TOO LONG ’varname’: library(dialog) LINE(line)Explanation: The BODY section of dialog dialog contains a variable name, varname, that is longer than 8 characters.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM005 ILLEGAL VARIABLE NAME: MEMBER ($ddmbr) LINE ($ddline)Explanation: An illegal variable name in line $ddline of member $ddmbr was encountered.System Action: The dialog is terminated. User Response: Contact Candle Customer Support.Message Type: ERROR.

KLVDM006 OPEN MIX STRING: library(dialog) LINE(line)Explanation: Line line of dialog dialog contains a DBCS shift-out character without a subsequent shift-in character. All DBCS mix strings must be complete on one line in the BODY section of a dialog. library is the DD name that contains the dialog.System Action: The panel compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM007 TABLE VARIABLE CONFLICT WITH VARIABLE ‘var’: library(dialog) LINE(line)Explanation: The variable var appears as both a table variable and a dialog variable in the BODY section of dialog dialog. Only one type of declaration is allowed. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The panel compilation fails.User Response: Correct the error and refresh the panel.Message Type: LOG, VIEW.

KLVDM008 NEGATIVE LENGTH STRING DETECTED BY KLVDMVTRExplanation: An internal error has been detected by the CT/Engine variables manager.System Action: The request is terminated with a U0100 abend, sending a dump to the RKLVSNAP file and/or the system’s dump datasets.User Response: Retain the CT/Engine run sheets, dump files, this message, and the MVS system log, then contact Candle Customer Support.Message Type: ABEND.


KLVDM009 DIALOG VARIABLE BUFFER INTEGRITY LOSTExplanation: The CT/Engine variables manager detected an error in its data structures.System Action: The request is terminated with a U0100 abend, sending a dump to the RKLVSNAP file and/or the system’s dump datasets.User Response: Retain the CT/Engine run sheets, dump files, this message, and the MVS system log, then contact Candle Customer Support.Message Type: ABEND.

KLVDM010 $DMFS FAIL CALLED BY dialog+X’offset’Explanation: This message is for internal use and appears only when DEBUG(Y) is coded in RKLVIN. It can be ignored unless requested by Candle Customer Support. Message KLVDM015 follows and contains additional information.System Action: None.User Response: None.Message Type: LOG, VIEW.

KLVDM011 DIALOG dialog FAILED; RC(rc) REASON(reason)Explanation: The specified dialog failed during execution.System Action: CT/Engine terminates the user’s session unless ONERROR was specified in the dialog invoking the failing dialog. KLVDM015 follows this message and displays information about the dialog, terminal, and application associated with the failure. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM012 LOOPCTR LIMIT EXCEEDEDExplanation: The LOOPCTR limit has been exceeded for a dialog. KLVDM015 follows this message and identifies the failing dialog.System Action: The dialog terminates.User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM013 INVALID NUMERIC ARGUMENTExplanation: A dialog has attempted a numeric operation on a value that was not numeric. KLVDM015 follows this message and identifies the failing dialog.System Action: The dialog terminates. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM014 MAIN STORAGE SHORTAGEExplanation: A dialog could not be executed because the Dialog Manager discovered a storage shortage. KLVDM015 follows this message and identifies the failing dialog.System Action: The dialog and the user’s session terminate.User Response: If the error persists, notify your System Administrator, who should review storage usage in CT/Engine, and increase the MINIMUM value in the RKLVIN file.Message Type: LOG, VIEW.

KLVDM015 DIALOG(dialog) [MEMBER(member) LINE(line)] Language(ccc) [LU(luname) APPL(applid)]Explanation: A warning or error has occurred while executing a dialog. This message follows the actual warning or error message and identifies the dialog, dialog, where the condition was detected.If the information can be determined, the location of the error is shown. member is either the dialog name or the name of a COPY member included in dialog. line is the line number in member where the error occurred.ccc is the language code currently in effect.If the executing dialog is associated with a physical terminal, luname is the logical unit name and applid is the VTAM application id.System Action: None.User Response: None.Message Type: LOG,VIEW.

KLVDM019 VARIABLE NAME TOO LONG: ‘name’Explanation: The CT/Engine dialog manager detected the use of a variable name (name) that is longer than 8 characters, and OPTIONS LONGVARNAME(IGNORE) was not coded in the KLVINDM member of RKANPAR. KLVDM015 follows this message and identifies the dialog associated with the error.System Action: If LONGVARNAME(FAIL) was specified, the dialog fails. Otherwise, the variable name is truncated at 8 characters and processing continues.User Response: Correct the variable name and refresh the dialog.Message Type: LOG, VIEW.

KLVDM020 UNSUPPORTED/INVALID $DMFS REQUEST RECEIVEDExplanation: The CT/Engine Dialog Manager was passed an invalid request.System Action: The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file and/or the system’s dump datasets.User Response: Retain the CT/Engine run sheets, dump files, this message, and the MVS system log, then contact Candle Customer Support.Message Type: ABEND.


KLVDM021 name IS ALREADY DEFINED: library(dialog) LINE(line)Explanation: The SSPL variable name is defined more than once in the DECLARE section of dialog, dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM022 STATIC VARIABLE “name” IS UNDECLARED; SCOPE(scope) ASSIGNEDExplanation: The Dialog Manager detected a reference to variable, name, which was not defined in the DECLARE section of the dialog. The NOTDECLARED(REPORT) option was requested, either in the KLVINDM member of RKANPAR or on the OPTION statement in the dialog. KLVDM015 follows this message and shows the dialog that contains the undeclared variable.

Note: It is acceptable for a dialog to have undeclared variables; this message is intended as a debugging tool.

System Action: name is treated as if it were declared as scope scope, and the dialog continues executing. The DEFAULTSCOPE keyword on the OPTION statement may be used to change the default scope. This message is issued only once for each individual reference to the variable.User Response: Review the dialog shown in message KLVDM015 to determine the proper variable scope, then add it to the DECLARE section.Message Type: LOG,VIEW.

KLVDM023 DYNAMIC VARIABLE “name” IS UNDECLARED; SCOPE(scope) ASSIGNEDExplanation: The Dialog Manager detected a reference to a dynamically constructed variable, name, which was not defined in the DECLARE section of the dialog. (Dynamically constructed variable names take the general form of &(&varname).) The NOTDECLARED(REPORT) option was requested, either in the KLVINDM member of RKANPAR or on the OPTION statement in the dialog. KLVDM015 follows this message and shows the dialog that contains the undeclared variable.

Note: It is acceptable for a dialog to have undeclared variables; this message is intended as a debugging tool.

System Action: name is treated as if it were declared as scope scope, and the dialog continues executing. The DEFAULTSCOPE keyword on the OPTION statement may be used to change the default scope. This message will be issued each time the dynamic variable is referenced.User Response: Review the dialog shown in message KLVDM015 to determine the proper variable scope, then add it to the DECLARE section.Message Type: LOG,VIEW.


KLVDM024 INVALID VARIABLE NAME X’hexstring’Explanation: The Dialog Manager detected an invalid dynamically constructed variable name, hexstring. (Dynamically constructed variable names take the general form of &(&varname).) KLVDM015 follows this message and shows the dialog associated with the error.System Action: A null is used for the variable’s value.User Response: Contact Candle Customer Support.Message Type: LOG, WIEW.

KLVDM030 KLVTBMGR LOGIC ERRORExplanation: The CT/Engine tables manager detected an invalid condition while performing a request.System Action: The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file and/or the system’s dump datasets.User Response: Retain the CT/Engine run sheets, dump files, this message, and the MVS system log, then contact Candle Customer Support.Message Type: REPLY.

KLVDM031 KLVTBMGR INVALID TABLE DELETE POINTERExplanation: The CT/Engine tables manager detected an invalid condition while performing a request.System Action: The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file and/or the system’s dump datasets.User Response: Retain the CT/Engine run sheets, dump files, this message, and the MVS system log, then contact Candle Customer Support.Message Type: REPLY.

KLVDM040 STATEMENT OUT OF PLACE: library(dialog) LINE(line)Explanation: The OPTION statement must appear as the first or top level of a dialog that includes other common members from the panel library. dialog is the dialog that was being refreshed; library is the name of the DD that contains the member; line is the line number in the member where the misplaced statement was found.System Action: The panel interpretation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM041 errmsg: ‘text’: library(dialog) LINE(line)Explanation: A statement in dialog dialog contains invalid syntax. library is the name of the DD that contains the member; line is the line number in the member where the error was detected. errmsg is an error message beginning with KLVSC; text is the text at or near the error.System Action: Compilation of the current source member is terminated. If dialog is a COPY member, processing of the previous source member will continue but the compilation will be failed when all processing is complete. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM042 RECURSIVE COPY DETECTED copymem): library(member) LINE(line)Explanation: A COPY statement for source member copymem was found in a dialog that is being processed as a result of a prior COPY for the same member. member is the source member that contains the second COPY; library is the name of the DD that contains the member; line is the line number in the member where the second COPY was found.System Action: Compilation of the current source member is terminated. If member is a COPY member, processing of the previous source member will continue but the compilation will be failed when all processing is complete. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM043 COPY MEMBER NOT FOUND: MEMBER(copymem): library(member) LINE(line)Explanation: The source member named on a COPY statement, copymem, could not be found. member is the source member that contains the COPY; library is the name of the DD that contains the member, and that does not contain the copy member; line is the line number in the member where COPY was found.System Action: Compilation of the current source member is terminated. If member is a COPY member, processing of the previous source member will continue but the compilation will be failed when all processing is complete. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM044 UNSUPPORTED LEVEL: ‘n’: library(dialog) LINE(line)Explanation: While compiling the SSPL dialog dialog, an OPTIONS statement was found at line line that specified an invalid LEVEL value, n. library is the name of the DD that contains the member.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: VIEW, ERROR.

KLVDM045 NOTDECLARED(text) IS INVALID: library(dialog) LINE(line)Explanation: While compiling the SSPL dialog member, an OPTIONS statement was found at line line that specified an invalid NOTDECLARED value, text. library is the name of the DD that contains the member.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM046 DEFAULTSCOPE(text) IS INVALID library(dialog) LINE(line)Explanation: While compiling the SSPL dialog member, an OPTIONS statement was found at line line that specified an invalid DEFAULTSCOPE value, text. library is the name of the DD that contains the member.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM048 INVALID PANEL CONTROL STATEMENT: text: library(dialog) LINE(line)Explanation: An invalid panel control statement, text, was encountered while compiling the dialog, dialog. library is the name of the DD that contains the member; line is the line number in the member where the invalid statement was found.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM049 INVALID DBCS DATA: XRC(xrc) MEMBER(panel) LINE(lineno)Explanation: An SSPL statement containing invalid DBCS data was encountered while interpreting a panel definition. The message provides the DBVALIDATE return code xrc, the panel name panel and line number lineno. The following are valid xrc values:

System Action: Panel interpretation terminates.User Response: Correct the SSPL statement and issue the REFRESH command to determine if the panel is ready for use.Message Type: WARNING.

KLVDM050 keyword(value) IS OUT OF RANGE (min-max); DEFAULTS TO defExplanation: keyword in the KLVINDM member of RKANPAR was specified with a value that is too small (min) or too large (max).System Action: The default value, def, will be used. CT/Engine initialization continues.User Response: Correct the keyword value. If the default value is unacceptable, recycle CT/Engine.Message Type: WARNING.

KLVDM051 DIALOG MANAGER INITIALIZED: LIMIT(limit)Explanation: A Dialog Manager initialization that completes successfully logs this message to create an audit trail.System Action: None.User Response: None.Message Type: INFO.

8 A DBCS subfield contains an odd number of bytes

12 A DBCS subfield contains an invalid codepoint

16 Missing SO. An SI character was detected before finding an SO.

20 Missing SI. An SO character was detected before finding an SI or end of string was detected.


KLVDM052 DIALOG LIBRARY UNAVAILABLEExplanation: The RKANPENU dialog library was not present or could not be opened during CT/Engine Dialog Manager initialization.System Action: Dialog Manager initialization fails and CT/Engine terminates.User Response: Ensure the RKANPENU DD is present and points to a dialog library, then restart the product.Message Type: ALERT.

KLVDM053 UNRECOGNIZED INITIALIZATION STATEMENT: stmttypeExplanation: The statement stmttype is not a valid initialization statement. The statement is in RKANPAR(KLVINDM).System Action: Initialization fails and CT/Engine terminates.User Response: Correct the statement and retry.Message Type: ALERT.

KLVDM054 keyword(value) IS INVALID; DEFAULTS TO defExplanation: keyword in the KLVINDM member of RKANPAR was specified with a value that is not a valid choice.System Action: The default value, def, will be used. CT/Engine initialization continues.User Response: Correct the keyword value. If the default value is unacceptable, recycle CT/Engine.Message Type: WARNING.

KLVDM056 KLVINDM RKANPAR PARAMETERS:Explanation: Module KLVINDM logs its start-up parameters as they are read from RKANPAR. This is the header message and will be followed by message KLVDM057.System Action: None.User Response: None.Message Type: LOG.

KLVDM057 parametersExplanation: As the parameters in module KLVINDM are read, a log audit trail is created.System Action: None.User Response: None.Message Type: LOG.

KLVDM058 SUPPORTED LANGUAGES: listExplanation: The Dialog Manager has finished searching for language-specific dialog library DD statements. list is the list of 3-character language codes that the Dialog Manager has found.System Action: None.User Response: None.Message Type: LOG.


KLVDM059 COULD NOT OPEN ddname PANEL LIBRARYExplanation: The Dialog Manager could not open the ddname DD, which is a dialog library.System Action: Dialog Manager initialization fails and CT/Engine terminates.User Response: Review the job and MVS logs for IBM data management messages (IEC) that identify the problem. Correct the error, then restart the product.Message Type: ALERT.

KLVDM070 COMPILED DIALOG EXCEEDS MAIN STORAGE LIMIT: library(dialog)Explanation: The compiled dialog, dialog, exceeds the maximum memory allocation permitted by CT/Engine. library is the DD name that contains the dialog.System Action: The panel compilation is terminated.User Response: Split dialog into smaller dialogs.Message Type: LOG, VIEW.

KLVDM071 DIALOG dialog NOT FOUND IN ddname LIBRARYExplanation: Dialog dialog was referenced on a select statement, dialog statement, COPY statement, or the REFRESH command, but it was not in the panel library, ddname.System Action: If the error occurs during an operator command, the command terminates. If it occurs during dialog execution, the dialog thread will generally be terminated. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM072 CRITICAL DIALOG MAY NOT HAVE PRESENTATION CAPABILITY library(dialog)Explanation: A critical dialog must have a presentation space. library is the DD name that contains the dialog.System Action: The dialog compilation fails.User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM073 DOWNLEVEL CONSTRUCTS CONVERTED; CHECK RKLVLOG FOR DETAILS: library(dialog)Explanation: While compiling the SSPL dialog dialog, one or more statements were found with downlevel syntax. library is the DD name that contains the dialog.System Action: None. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM074 TRACE REQUEST IGNORED FOR dialog - DIALOG TRACE IS OFFExplanation: A REFRESH operator command was issued for dialog with the TRACE keyword specified. However, Dialog Trace is not currently active.System Action: The dialog is compiled without trace information.User Response: If you wish dialog to be traceable, activate Dialog Trace with the DTRACE operator command, then reissue the REFRESH command. Otherwise, no action is needed.Message Type: LOG, VIEW.

KLVDM101 EXCESSIVE OPERANDS: statement PROVIDED (n) ALLOWS (m): library(dialog) LINE(line)Explanation: n operands are provided in the procedure or function statement statement, but only m operands are allowed. dialog is the dialog that contains the error. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM102 INSUFFICIENT OPERANDS: statement PROVIDED (n) REQUIRES (m) library(dialog) LINE(line)Explanation: n operands are provided in the procedure or function statement statement but only m operands are required. dialog is the dialog that contains the error. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM103 VOID EXPRESSION: library(dialog) LINE(line)Explanation: An expression was provided without operands, such as (()), in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM104 OPEN EXPRESSION: library(dialog) LINE(line)Explanation: An expression was provided with more opening than closing parentheses, such as ((expr), in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM105 UNBALANCED PARENTHESES: library(dialog) LINE(line)Explanation: An expression was provided with more closing than opening parentheses, such as (expr)), in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM106 label IS A DUPLICATE LABEL: library(dialog) LINE(line)Explanation: The label label is defined more than once within the dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM107 IMPROPER USE OF statement CONSTRUCT: library(dialog) LINE(line)Explanation: The dialog management statement statement was used improperly. This is usually an END or UNTIL statement without a DO, or an ELSE statement without an IF. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM109 IMPROPER TOKEN USAGE: library(dialog) LINE(line)Explanation: An invalid token was detected within dialog dialog. This is often a misspelled dialog function name. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM110 OPEN CONSTRUCT(S) IN PROCEDURE: library(dialog) LINE(line)Explanation: A DO statement without an END statement was found in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM111 LABEL label IS UNRESOLVED: library(dialog) LINE(line)Explanation: A GOTO or CALL statement referenced a label that was not found in the dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM112 PREMATURE END OF MEMBER: library(dialog) LINE(line)Explanation: The end of a dialog was reached before a statement was completed. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM113 OPEN ENVIRONMENT: ‘text’: library(dialog) LINE(line)Explanation: dialog contains an opening delimiter, text, without a closing delimiter. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM120 DOWNLEVEL FUNCTION SYNTAX: ‘name’ library(dialog) LINE(line)Explanation: Dialog dialog contains a dialog function call (name) that does not have parentheses around its argument list. This is known as ”level 0” syntax. library is the DD name that contains the dialog. line is the location where the condition was detected.System Action: This is an information message. The dialog continues compiling. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM121 UNBALANCED COMMENT DELIMITER(S): library(dialog) LINE(line)Explanation: A comment-end delimiter t(*/) was found in dialog dialog without a corresponding comment-start delimiter (/*). library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM122 INVALID HEX LITERAL: ‘\x’: library(dialog) LINE(line)Explanation: An invalid hexadecimal string, x was detected in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM123 INVALID STRING FUNCTION: ‘func’: library(dialog) LINE(line)Explanation: func was coded as a string function in dialog dialog, but it is either not a valid SSPL statement or dialog function name or is not allowed to be used as a string function. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails.User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM124 INVALID STRING FORMAT: ‘string’: library(dialog) LINE(line)Explanation: An invalid string, string, was detected in dialog dialog. It may be missing a closing quote, or may contain a missing or invalid variable name. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM125 DOWNLEVEL REFERENCE: ‘text’: library(dialog) LINE(line)Explanation: A statement in dialog dialog was coded using a syntax that is no longer supported. library is the DD name that contains the dialog. line is the location where the condition was detected.System Action: text is converted internally to the correct syntax and message KLVDM126 is issued to display it. The dialog continues compiling. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM126 CONVERTED REFERENCE: ‘text’: library(dialog) LINE(line)Explanation: This message follows KLVDM125 and displays how the unsupported syntax was converted. text is the converted text. dialog is the dialog that contains the statement. library is the DD name that contains the dialog. line is the location where the condition was detected.System Action: None.User Response: None.Message Type: LOG, VIEW.

KLVDM127 WARNING - OPEN COMMENT BLOCK: library(dialog) LINE(line)Explanation: During refresh processing for dialog dialog, the Dialog Manager detected an open comment block (more “/*” than “*/”). line is the line where the error was detected, and is typically an SSPL section marker ()PROLOG, )BODY, etc.). library is the DD name that contains the dialog.System Action: This is a warning message only. The dialog continues compiling, but portions of the dialog may be omitted or syntax errors may be reported.User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.


KLVDM128 MAXIMUM ATTRIBUTES EXCEEDED FOR ATTR(attr): library(dialog) LINE(line)Explanation: More than 252 panel attributes have been declared in dialog dialog. attr is the offending attribute. library is the DD name that contains the dialog. line is the location where the error was detected.System Action: The dialog compilation fails. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM130 diagnostic textExplanation: This message is for internal use. It can be ignored unless requested by Candle Customer Support.System Action: None.User Response: None.Message Type: LOG.

KLVDM131 TOKEN-TRACE, next, length, value, current, stack, frameExplanation: This message is for internal use. It can be ignored unless requested by Candle Customer Support.System Action: None.User Response: None.Message Type: LOG.

KLVDM132 LABEL-TRACE, next, length, value, current, stack, frameExplanation: This message is for internal use. It can be ignored unless requested by Candle Customer Support.System Action: None.User Response: None.Message Type: LOG.

KLVDM133 TRACE ENVIRONMENT READ FAILED, RC=rcExplanation: An internal processing error has occurred during Dialog Trace statement range processing.System Action: Any previous range remains active.User Response: Save the rc value and contact Candle Customer Support.Message Type: REPLY.

KLVDM134 STATEMENT RESOURCE INITIALIZATION FAILEDExplanation: An internal processing error has occurred during Dialog Trace statement range processing.System Action: Any previous range remains active.User Response: Contact Candle Customer Support.Message Type: REPLY.


KLVDM201 INSUFFICIENT STORAGE FOR RESULT OF ENCDEC FUNCTIONExplanation: The result of an encryption or decryption function was too large for the storage area to receive it. This is a “should not occur” condition.System Action: The dialog is terminated. KLVDM015 follows this message and displays information about the dialog, terminal, and application associated with the failure.User Response: Save a copy of the dialog, the contents of RKLVIN, and the CT/Engine run sheets, then contact Candle Customer Support.Message Type: LOG, VIEW.

KLVDM901 INVALID PARMS PASSED TO KLV$DMNLExplanation: An internal processing error has occurred.System Action: The current function is abended with code U0100 to force a diagnostic dump.User Response: Save the CT/Engine run sheets and RKLVLOG, JES SYSLOG, and SVC dump, then contact Candle Customer Support.Message Type: ABEND.

KLVDM902 LANGUAGE CODE MUST BE 3 CHARACTERSExplanation: A language code was entered that is too long or too short. Language codes must be 3 characters.System Action: The operator command is terminated.User Response: Reissue the command with a valid language code.Message Type: ERROR.

KLVDM903 LANGUAGE CODE ccc IS NOT VALIDExplanation: The language code, ccc, is not supported. Message KLVDM904 follows and lists the valid codes. The operator command is terminated.User Response: Reissue the command with a valid language code.Message Type: ERROR.

KLVDM904 VALID CODES ARE ccc ...Explanation: The language codes recognized by CT/Engine are displayed.System Action: None.User Response: None.Message Type: ERROR.

KLVER001 SNAP ID snid REQUESTED FROM module + X offsetExplanation: A $SNAP macro was coded to request a snap of the registers or the registers and a storage area. The snap was called in module at offset offset.System Action: CT/Engine takes the requested snap and continues.User Response: This is a debugging tool for Candle-developed CT/Engine applications, and is specific to a particular product.Message Type: INFO.


KLVER011 ABNORMAL TERMINATION AVERTED: ABEND EC MODE PSW psw REFERS TO abndmod + X abndoff ABEND: SYSTEM abend USER usrExplanation: An abend occurred in module abndmod at offset abndoff.System Action: CT/Engine issues snap dumps of the environment, and processing continues. User Response: Contact Candle Customer Support.Message Type: LOG, VIEW.

KLVER012 DUMPING TO SYSMDUMPExplanation: The system has been requested to capture a dump on the dataset specified by the SYSMDUMP DD statement.System Action: CT/Engine requested the system to take a dump of the environment. A summary dump is also taken on RKLVSNAP.User Response: Copy the dump to tape and contact Candle Customer Support.Refer to IBM’s Planning: Problem Determination and Recovery for information on defining and managing SYSMDUMP datasets.Message Type: LOG, VIEW.

KLVER013 ESTAE: estae AT address (module + offset) SNAPPING MAIN STORAGE SNAPPING TASK INFORMATION SNAPPING SYSTEM INFORMATION SNAP COMPLETEExplanation: An abend occurred at address in module.System Action: CT/Engine issues snap dumps of the environment, and processing continues. User Response: Contact Candle Customer Support.Message Type: ALERT.

KLVEV001 SYSECHO(text)Explanation: The dialog control verb &SYSECHO has been detected while evaluating an expression.System Action: The requested text is logged.User Response: None.Message Type: LOG, VIEW, REPLY.

KLVFL001 ALL PENDING VSAM CHANGES HAVE BEEN WRITTEN TO DASDExplanation: The CT/Engine operator command, FLUSH, was issued to request the IBM VSAM data management services to write all pending VSAM records to the appropriate cluster. The request has completed successfully.

Note: The KLVSTART member in RKANCMD, which contains commands that are performed during CT/Engine initialization, contains an EVERY 30:00 FLUSH command. This causes FLUSH to be issued every 30 minutes.

System Action: None.


User Response: None. To prevent accidental data loss, users are encouraged to leave the automatic FLUSH in RKANCMD(KLVSTART). To eliminate the automatic FLUSH, delete the statement from RKANCMD(KLVSTART).Message Type: REPLY.

KLVFL002 ALL PENDING RKLVLOG RECORDS HAVE BEEN WRITTENExplanation: The CT/Engine operator command, FLUSH, was issued to request the IBM data management services to write all pending RKLVLOG records to the currently active RKLVLOG data set. The request has completed successfully.System Action: None.User Response: None.Message Type: REPLY.

KLVFL003 ALL PENDING NAF RECORDS HAVE BEEN WRITTENExplanation: The CT/Engine operator command, FLUSH, was issued to request the IBM data management services to write all pending NAF records to the NAF data set and/or to SMF. The request has completed successfully.System Action: None.User Response: None.Message Type: REPLY.

KLVFM001 FREE STORAGE AREA INTEGRITY LOSTExplanation: The integrity of the free storage area has been lost. This is caused by a storage overlay.System Action: CT/Engine will abend U0200 to terminate the address space.User Response: Save the run sheets, dump files, and MVS system log, then contact Candle Customer Support.Message Type: ABEND.

KLVFM002 STORAGE RELEASE ERRORExplanation: An invalid storage release request has been detected. This is may be caused by a storage overlay or an invalid address.System Action: CT/Engine will abend U0100 to terminate the requesting thread.User Response: Save the run sheets, dump files, and MVS system log, then contact Candle Customer Support.Message Type: ABEND.

KLVGM001 STORAGE POOL LIMIT EXCEEDEDExplanation: A request for storage exceeded the LIMIT parameter that was specified or implied at start-up.System Action: For problem determination, a dump is generated with a user abend code.User Response: Increase the limit parameter value and restart the product. Message Type: REPLY.


KLVGM002 ZERO LENGTH STORAGE REQUESTExplanation: A zero length storage request was made toCT/Engine.System Action: For problem determination, a dump is generated with a user abend code. User Response: Contact Candle Customer Support.Message Type: REPLY.

KLVGM003 FREE STORAGE LIST INTEGRITY LOSTExplanation: The integrity of the free storage list has been corrupted.System Action: For problem determination, a dump is generated with a user abend code. User Response: Contact Candle Customer Support.Message Type: REPLY.

KLVGM004 FREE STORAGE AREA INTEGRITY LOSTExplanation: The integrity of the free storage area has been corrupted.System Action: For problem determination, a dump is generated with a user abend code.User Response: Contact Candle Customer Support.Message Type: REPLY.

KLVGM005 FREE STORAGE AREA EXHAUSTEDExplanation: CT/Engine has used all available free storage and was unable to satisfy a storage allocation request.System Action: For problem determination, a dump is generated with a user abend code.User Response: Adjust the CT/Engine MINIMUM and MAXIMUM parameters in the RKLVIN file and restart CT/Engine.Message Type: REPLY.

KLVGM006 FREE BLOCK INTEGRITY CHECK FAILEDExplanation: CT/Engine has detected an invalid storage release request.System Action: For problem determination, a dump is generated with a user abend code.User Response: Contact Candle Customer Support.Message Type: REPLY.


Candle Products Messages Manual, Vol 2 - IBMpublib.boulder.ibm.com/tividd/.../GC32-9171-00/en_US/PDF/GC32-9171-00.pdf · Candle Products Messages Manual Volume 2 (EU–KLVGM) GC32-9171-00

Documents