Candle Klvhskonct Gc32 9172 00 Users Manual Products Messages Manual, Vol 3

gc32917200 744d9db0-357b-4567-8988-501efc84eece Candle Indoor Furnishings GC32-9172-00 User Guide |

2015-02-05

: Candle Candle-Klvhskonct-Gc32-9172-00-Users-Manual-534001 candle-klvhskonct-gc32-9172-00-users-manual-534001 candle pdf

Open the PDF directly: View PDF .
Page Count: 522

Download
Open PDF In Browser	View PDF

Candle Products Messages Manual
Volume 3
(KLVHS–KONCT)

GC32-9172-00

February 2004

Candle Corporation
100 North Sepulveda Blvd.
El Segundo, California 90245-9796

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 © February 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.

Candle Products Messages Manual (KLVHS–KONCT)

Contents
Chapter 1.

KLVHS001–KLVSC009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2.

KLVSD001–KLXOP005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 3.

KM2EXPFF–KMCRCA002I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Chapter 4.

KMQxx001E–KOCJ0046 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Chapter 5.

KOGCM001–KONCT303. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Candle Products Messages Manual (KLVHS–KONCT)

KLVHS001–KLVSC009

KLVHS001

HANDLE SERVICES MANAGER INITIALIZATION COMPLETE
Explanation: The Handle Services initialization module has processed all input
parameters and initialized the Handle Services environment without error.
System Action: Processing continues.
User Response: None.
Message Type: INFO.

KLVHS002

keyword(value) OUT OF RANGE (min-max) USING DEFAULT VALUE
(default)
Explanation: The value specified in the keyword parameter was outside the
range (min-max) shown. The default value default has been substituted.
System Action: Processing continues.
User Response: If the default value is unacceptable, modify the keyword
parameter in your RKANPAR member KLVINHSM and restart CT/Engine.
Message Type: INFO.

KLVHS005

KLVINHSM RKANPAR PARAMETERS:
Explanation: Module KLVINHSM logs its start-up parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVHS006.
System Action: None.
User Response: None.
Message Type: LOG.

KLVHS006

parameters
Explanation: As the parameters in module KLVINHSM are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVHS001–KLVSC009

KLVHS011

MAXPOOLS(pools) USING(rpools), MAXHANDLES(handles)
USING(rhandles)
Explanation: The specified MAXPOOLS value pools was rounded to rpools.
The specified MAXHANDLES value handles was rounded to rhandles. The
rounded values will be used by the Handle Services Manager.
System Action: Processing continues.
User Response: None.
Message Type: INFO.

KLVHS201

HANDLE NOTIFY ROUTINE ABEND (tnnnn) - HANDLE(handle)
ADDR(addr) POOL(pool) EXIT(exit) PARM(parm) ASSOC(assoc)
Explanation: During handle name deregistration or handle pool purge
processing, a notify routine abended. t is the abend type (S)ystem or (U)ser and
nnnn is the abend code. The abend code is three hexadecimal digits for a system
abend and four decimal digits for a user abend. handle is the handle name. addr
is the address of the handle name block within the handle pool. pool is the handle
pool address. exit is the notify routine address. parm is the parameter passed to
the exit. assoc is the 32-bit associated value for this handle name.
System Action: A dump is produced and cleanup processing for the handle
name is terminated. Processing continues.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ERROR.

KLVHS202

NO HANDLE POOLS AVAILABLE
Explanation: A request to initialize a handle pool could not be serviced because
no empty table slot was available.
System Action: A dump is produced and the thread is terminated.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ERROR.

KLVHS203

HANDLE SERVICES MANAGER VECTOR TABLE IS INVALID
Explanation: The Handle Services Manager vector table was invalid during the
processing of a Handle Services request.
System Action: A dump is produced and the thread is terminated.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ERROR.

KLVHS204

HANDLE SERVICES MANAGER RETURN AREA NOT LARGE ENOUGH
Explanation: The Handle Services Manager return area ($HRA) was not large
enough to allow required information to be returned during the processing of a
Handle Services request.
System Action: A dump is produced and the thread is terminated.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVHS205

INVALID RELEASE HANDLE REQUEST
Explanation: The handle use count was already zero during the processing of a
Handle Services request to release a handle.
System Action: A dump is produced and the thread is terminated.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ERROR.

KLVHS811

HANDLE SERVICES MANAGER GLOBAL STATISTICS
Explanation: This is the title line for the HSM Global Statistics display.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS812

MAXIMUM POOLS = maxpools
Explanation: The maximum number of handle pools that can be allocated.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS813

MAXIMUM HANDLES PER POOL = maxhandles
Explanation: The maximum number of handles available in a single handle
pool.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS814

TOTAL POOLS IN USE = totalpools
Explanation: The total number of handle pools that are currently allocated and
in use.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS815

TOTAL HANDLES IN USE = totalhandles
Explanation: The total number of handles in use in all pools.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS816

TOTAL STORAGE IN USE = totalstorage
Explanation: The total amount of storage currently in use by Handle Services.
This storage is allocated above the 16 M line.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS001–KLVSC009

KLVHS817

TOTAL EXPANSIONS = totalexpansions
Explanation: The total number of times the Handle Services Manager
performed a handle pool expansion.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS818

AVERAGE HANDLES PER POOL = averagehandles
Explanation: The average number of handles in a handle pool.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS820

QUERYHSM - OWNERID= AND POOLID= KEYWORDS ARE MUTUALLY
EXCLUSIVE
Explanation: The QUERYHSM command was issued with both the
OWNERID= and POOLID= keywords specified.
System Action: Only GLOBAL statistics are displayed.
User Response: Re-enter the command with either POOLID= or OWNERID=
specified.
Message Type: INFO.

KLVHS821

HANDLE SERVICES MANAGER GLOBAL STATISTICS DETAIL
Explanation: This is the title line for the HSM Global Statistics Detail display.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS822

POOL ID = poolid, OWNERID = ownerid, SIZE = poolsize BYTES
Explanation: This message is printed when the QUERYHSM GLOBAL DETAIL
command is entered. It is printed once for each active handle pool. poolid is the
handle pool ID, ownerid is the owning logical resource name, and poolsize is the
handle pool size in bytes.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS829

END OF THE HSM STATISTICS DISPLAY
Explanation: This message indicates that all the requested Handle Services
Manager statistics have been displayed.
System Action: None.
User Response: None.
Message Type: INFO.

Candle Products Messages Manual (KLVHS–KONCT)

KLVHS830

INVALID OWNERID SPECIFIED ON QUERYHSM COMMAND - ownerid
Explanation: The specified ownerid is not a valid logical resource number or
was not 8 characters long. The owner ID must include all leading zeros.
System Action: Only GLOBAL statistics are displayed.
User Response: Issue QUERYHSM DETAIL command for a list of valid owner
IDs and then reissue the QUERYHSM OWNERID= command specifying all 8
characters of the owner ID.
Message Type: INFO.

KLVHS831

HANDLE SERVICES MANAGER LIST OWNERID STATISTICS
Explanation: This is the title line for the handle pool owner ID statistics display.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS832

OWNERID = cccccccc, NUMBER OF POOLS OWNED = nn
Explanation: This message is printed when the QUERYHSM OWNERID=
command is issued. cccccccc is the owner ID and nn is the number of pools
owned.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS833

POOLID = poolid, SIZE = nnnnnn BYTES, HANDLES IN POOL = hhhhhh
Explanation: In addition to message KLVHS832, this message is printed when
the QUERYHSM DETAIL OWNERID= command is issued. It is printed once,
immediately following message KLVHS832, for each owned handle pool. poolid
is the handle pool ID, nnnnnn is the size of the handle pool in bytes, and hhhhhh
is the number of handles in the pool.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS840

INVALID POOLID SPECIFIED ON QUERYHSM COMMAND - poolid
Explanation: The value poolid was specified on a QUERYHSM command, but
it is not a valid handle pool ID.
System Action: Only GLOBAL statistics are displayed.
User Response: Issue QUERYHSM DETAIL command to get a list of valid
pool IDs. Then reissue the QUERYHSM POOLID= command with the correct
pool ID.
Message Type: INFO.

KLVHS841

HANDLE SERVICES MANAGER LIST POOLID STATISTICS
Explanation: This is the title line for the handle pool statistics display.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS001–KLVSC009

KLVHS843

HANDLES IN POOL = handles, HANDLES IN USE = inuse
Explanation: In addition to message KLVHS822, this message is printed when
the QUERYHSM DETAIL POOLID= command is issued. It is printed
immediately following message KLVHS822. handles is the total number of
handles in the handle pool and inuse is the number of handles that are currently
in use.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS844

PRIMARY SIZE = prisize HANDLES, EXPANSION SIZE = expsize
HANDLES
Explanation: In addition to messages KLVHS822 and KLVHS843, this message
is printed when the QUERYHSM DETAIL POOLID= command is issued. It is
printed immediately following message KLVHS843. prisize is the initial number of
handles in the handle pool and expsize is the number of new handles added to
the pool each time it expands.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS845

NUMBER OF EXPANSIONS = nnn
Explanation: In addition to messages KLVHS822, KLVHS843, and KLVHS844,
this message is printed when the QUERYHSM DETAIL POOLID= command is
issued. It is printed immediately following message KLVHS844. nnn is the number
of times the handle pool has been expanded.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS851

HANDLE SERVICES MANAGER STORAGE ISOLATION STATISTICS
Explanation: This is the title line for the Handle Services Manager storage
isolation statistics display.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS852

PRIMARY SIZE = prisize, SECONDARY SIZE = secsize
Explanation: The values used to allocate the storage isolation pool used by
Handle Services. prisize is the initial storage amount allocated and secsize is the
additional amount of storage allocated each time the storage pool is expanded.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS853

CURRENT STORAGE IN USE = nnnnn
Explanation: The amount of storage in the storage pool that is currently in use.
System Action: None.
User Response: None.

Candle Products Messages Manual (KLVHS–KONCT)

Message Type:

INFO.

KLVHS854

MAXIMUM STORAGE EVER IN USE = nnnnn
Explanation: The maximum amount of storage in the storage pool that was
ever in use.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS855

CURRENT STORAGE ALLOCATED = nnnnn
Explanation: The total amount of CT/Engine storage currently allocated to the
storage pool.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIC001

CONTACT ESTABLISHED WITH node
Explanation: The intercommunications manager successfully established
communications with node, usually as a result of the NODE command being
issued.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIC002

CONTACT LOST WITH node
Explanation: The intercommunications manager has lost contact with node.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIC003

DEFINITION COMPLETE FOR node
Explanation: The intercommunications manager successfully completed
initialization for node, usually as a result of the NODE command being issued.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIC101

OPERATOR ACTIVE: ID(opid) LU(ocdev)
Explanation: Operator opid has logged on from device ocdev, causing this
message to be logged as an audit trail.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIC102

OPERATOR INACTIVE: ID(opid) LU(ocdev)
Explanation: Operator opid has logged off, creating this message to be logged
as an audit trail.
System Action: None.
User Response: None.

KLVHS001–KLVSC009

Message Type:

INFO.

KLVIN000

CT/IX INTERFACE INITIALIZED
Explanation: The CT Posix environment has been successfully established.
System Action: None.
User Response: This message is informational.

KLVIN000

UNABLE TO REGISTER CT/iX THREAD or PROCESS ANCHOR: RC(9999)
Explanation: A fatal an unexpected error has occurred.
System Action: The process terminated.
User Response: Gather relavent logs and report this problem to Candle
Customer Support.

KLVIN001

INVALID CT/IX INTERFACE HEADER -
Explanation: A fatal an unexpected error has occurred.
System Action: The process terminated.
User Response: Gather relavent logs and report this problem to Candle
Customer Support.

KLVIN400

TASK INITIALIZED: $DQA(dqa) TASK(task) $DSA(dsa) EVTBL(evtbl)
DPRTY(dprty)
Explanation: During CT/Engine start-up, the CT/Engine dispatcher started the
identified task to perform its work. The displayed fields contain information useful
for Candle diagnostic efforts.
System Action: None.
User Response: None.
Message Type: LOG.

KLVIN403

COMMAND LIBRARY UNAVAILABLE
Explanation: During CT/Engine start-up the command library, DD name
RKANCMD, could not be accessed. It is probably not present in the CT/Engine
JCL procedure.
System Action: Any data contained in the command library is unavailable.
User Response: Refer to the MVS system log for any IBM data management
messages (IEC). Determine the reason the command library could not be opened,
correct it, and restart CT/Engine.
Message Type: WARNING.

KLVIN405

STARTUP MODULE: modname [,@entry-point] SEQUENCE num [,USING
RKANPAR MEMBER member]
Explanation: During CT/Engine start-up, module modname with sequence
number num will be invoked. If an initialization parameter member of RKANPAR
is found for this module, it is identified as member in the message. The
entry-point address will only be included in the message if debug mode is in
effect.
System Action: None.
User Response: None.
Message Type: LOG.

Candle Products Messages Manual (KLVHS–KONCT)

KLVIN406

STARTUP ERROR: MODULE(modname) R15(r15)
Explanation: During CT/Engine start-up, module modname detected an error.
r15 should have a nonzero value.
System Action: CT/Engine is terminated after any subsequent start-up
modules are invoked.
User Response: Examine the CT/Engine log dataset for additional messages to
determine a more specific reason for the error. Correct it, and restart CT/Engine.
Message Type: ALERT.

KLVIN407

FLUSHING INITIAL MESSAGES
Explanation: After CT/Engine is successfully started, any pending messages are
written to the log so that start-up messages may be viewed by the site to
determine if the CT/Engine environment was correctly established.
System Action: None.
User Response: None.
Message Type: LOG.

KLVIN408

CANDLE ENGINE VERSION ver READY ON smfid SYS cpuid: GSA(nnnn)
Explanation: CT/Engine version ver is up and running on system smfid. The
variable nnnn refers to the address of the Global Storage Area, the CT/Engine
primary control block.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIN409

INITIALIZATION LIBRARY UNAVAILABLE
Explanation: During CT/Engine start-up the parameter library, DD name
RKANPAR, could not be accessed. It is probably not present in the CT/Engine
JCL procedure.
System Action: Any data contained in the parameter library is unavailable.
User Response: Refer to the MVS system log for any IBM data management
messages (IEC). Determine the reason the command library could not be opened,
correct it, and restart CT/Engine.
Message Type: WARNING.

KLVIN410

INITLIST MEMBER member BEING PROCESSED
Explanation: The INITLIST keyword was coded and member is being
processed for start-up member name overrides.
System Action: None.
User Response: None.
Message Type: INFO.

KLVIN411

override-statement
Explanation: The contents of the INITLIST member are echoed in
override-statement.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS001–KLVSC009

KLVIN412

STARTUP MODULE module NOT FOUND
Explanation: An override statement references a start-up module that is not
present in this CT/Engine address space.
System Action: The override is ignored and processing continues.
User Response: Correct the override statement and restart the CT/Engine
address space if necessary.
Message Type: WARNING.

KLVIN413

INITLIST MEMBER member NOT FOUND
Explanation: member could not be found in RKANPAR.
System Action: The start-up is terminated.
User Response: Correct the INITLIST keyword to specify a valid member
name and restart the CT/Engine address space.
Message Type: ERROR.

KLVIN414

OVERRIDE MEMBER member FOR STARTUP MODULE module NOT
FOUND
Explanation: member could not be found in RKANPAR for start-up module
module. This message will only be issued if the override member name differs
from the default.
System Action: The start-up is terminated.
User Response: Correct the INITLIST member to specify a valid override
member name and restart the CT/Engine address space.
Message Type: ERROR.

KLVIP003

UNSUPPORTED IPC SERVICE
Explanation: A service other than CREATE, DESTROY, DEQUEUE, PUSH,
ACCESS, ALARM, or QUEUE was requested from IPC.
System Action: The dialog is terminated.
User Response: If this error occurs while running CL/SUPERSESSION, correct
the error and restart the dialog process. If this error occurs while running any
other Candle product, contact Candle Customer Support.
Message Type: VIEW.

KLVLG001

CLUSTER INITIAL LOAD FAILED, SERVICE(service), RC(rc)
Explanation: During CT/Engine initialization, an error was encountered while
attempting to load the CL/CONFERENCE log cluster. service may be:
SHOWCB-1

A SHOWCB for a VSAM ACB failed.

SHOWCB-2

A SHOWCB for a VSAM RPL failed.

GENCBACB

A GENCB for a VSAM ACB failed.

GENCBRPL

A GENCB for a VSAM RPL failed.

OPEN

An OPEN failed for the VSAM cluster.

PUT

The initial load failed for the cluster.

System Action: The CL/CONFERENCE logging facility is unavailable.

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Using the RC and service name, determine the cause of the
error, correct it, and restart CT/Engine.
Message Type: ERROR.
KLVLI001

LOCK MANAGER INTEGRITY ERROR
Explanation: An internal error occurred while processing a lock.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVLR001

MAIN STORAGE SHORTAGE DETECTED, QUIESCE IN EFFECT
Explanation: CT/Engine detected a main storage shortage. To recover from the
shortage, CT/Engine will not accept any logons.
System Action: Users cannot logon or start a session.
User Response: None. However, if these messages occur frequently on your
system, you should examine the memory allocation parameters that are in effect.
These are the RKLVIN keywords MINIMUM, MAXIMUM, and RESERVE.
Message Type: ALERT.

KLVLR002

MAIN STORAGE SHORTAGE RELIEVED, QUIESCE RELEASED
Explanation: CT/Engine detected main storage availability and released the
quiesce caused by main storage shortage.
System Action: CT/Engine will now allow users to logon or start a session.
User Response: None.
Message Type: INFO.

KLVLR003

LOGICAL RESOURCE INTEGRITY ERROR
Explanation: While accessing the logical resource table, an integrity error was
detected.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: REPLY.

KLVLR004

PURGE/CLEANUP EXIT ERROR DETECTED, DUMP REQUESTED
Explanation: The CT/Engine logical resource manager detected an error during
resource purge or cleanup processing and has bypassed a purge/cleanup exit to
avoid further problems.
System Action: A dump is produced because DEBUG(Y) is in effect. Some
resources and storage may be hung.
User Response: Contact Candle Customer Support.

KLVHS001–KLVSC009

KLVLR005

PURGE/CLEANUP EXIT ERROR DETECTED resnum1 - resname - resnum2
Explanation: The CT/Engine logical resource manager detected an error during
resource purge or cleanup processing and has bypassed a purge/cleanup exit to
avoid further problems.
System Action: Some resources and storage may be hung.
User Response: Copy the exact contents of the message and contact Candle
Customer Support. Be sure to include the debugging data fields resnum1,
resname, and resnum2 contained in the message.

KLVLR006

LOGICAL RESOURCE CONTROL BLOCK ERROR
Explanation: An error was encountered while processing a resource manager
request.
System Action: The current request is ignored and a U0100 abend is
generated to supply information for the logic error.
User Response: Acquire the dump from the U0100 abend and contact Candle
Customer Support.
Message Type: REPLY.

KLVLR007

MAXIMUM LOGICAL RESOURCE TABLE SIZE EXCEEDED - RESOURCE
INITIALIZATION FAILED
Explanation: The maximum number of logical resources has been exceeded.
System Action: The current request is ignored. The system will continue
running. As resources are freed, new resources can be created, but the stability of
the system is unpredictable since it is not known what resources will be rejected.
User Response: Reduce activity on the system and contact Candle Customer
Support.
Message Type: ALERT.

KLVLW001

RKLVLOG IS CURRENTLY RECORDING ON ddname
Explanation: In response to the TLVLOG CT/Engine operator command, this
message shows where CT/Engine messages are currently being written to.
ddname is the ddname being used for RKLVLOG.
System Action: None.
User Response: None.
Severity: REPLY.

KLVLW002

MAXIMUM LINES: maxlines
Explanation: In response to the TLVLOG CT/Engine operator command, this
message shows the maximum number of lines that will be written to the currently
active RKLVLOG before an automatic TLVLOG SWITCH is performed.
Note: If the value is zero, there is no maximum.
System Action: None.
User Response: None.
Severity: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVLW003

LINES WRITTEN: lines
Explanation: In response to the TLVLOG CT/Engine operator command, this
message shows the number of lines that have been written to the currently active
RKLVLOG.
System Action: None.
User Response: None.
Severity: REPLY.

KLVLW004

RKLVLOG IS DISABLED BECAUSE OF AN I/O ERROR ON ddname
Explanation: In response to the TLVLOG CT/Engine operator command, this
message reports that an error has caused CT/Engine to stop writing messages to
the RKLVLOG file. ddname is the name of the DD to which CT/Engine had been
recording.
System Action: None.
User Response: Issue TLVLOG SWITCH to attempt to allocate a new
RKLVLOG dynamically.
Severity: REPLY.

KLVLW011

DYNAMIC ALLOCATION VALUES:
Explanation: In response to the TLVLOG CT/Engine operator command, this
message precedes a set of KLVLW012 messages that show the values that will be
used for the next RKLVLOG dynamic allocation.
System Action: None.
User Response: None.
Severity: REPLY.

KLVLW012

keyword - value
Explanation: Displays a RKLVLOG dynamic allocation parameter and its value.
Possible message text:
Keyword

Value

CLASS

The SYSOUT class.

COPIES

The number of copies.

DEST

The SYSOUT destination, if any.

FCB

The FCB name, if any.

FORM

The FORM name, if any.

HOLD

Whether the SYSOUT file will be placed in an operator hold
(YES) or not (NO).

UCS

The UCS name, if any.

USER

The user ID associated with the SYSOUT destination, if any.

WTRNAME

The external writer name, if any.

KLVHS001–KLVSC009

System Action: None.
User Response: None.
Severity: REPLY.
KLVLW022

RKLVLOG IS NOW RECORDING ON ddname
Explanation: In response to a TLVLOG SWITCH request, CT/Engine has
dynamically allocated a SYSOUT field and is now writing RKLVLOG messages to
it. ddname is the new ddname.
System Action: None.
User Response: None.
Severity: REPLY.

KLVLW023

ddname DD HAS BEEN CLOSED AND RELEASED
Explanation: In response to a TLVLOG SWITCH request, CT/Engine has
closed and dynamically deallocated the previous RKLVLOG file. ddname is the
ddname.
System Action: None.
User Response: None.
Severity: REPLY.

KLVLW027

COPIES MUST BE BETWEEN 1 AND 254
Explanation: An invalid COPIES value was entered on a TLVLOG command.
Only an integer between 1–254 is accepted.
System Action: The command terminates.
User Response: Reissue the command with a valid COPIES value.
Severity: ERROR.

KLVLW028

MAXLINES MUST BE BETWEEN 0 AND 16000
Explanation: An invalid MAXLINES value was entered on a TLVLOG
command. Only an integer between 0–16000 is accepted.
System Action: The command terminates.
User Response: Reissue the command with a valid MAXLINES value.
Severity: ERROR.

KLVLW029

HOLD VALUE MUST BE "YES" OR "NO"
Explanation: An invalid HOLD value was entered on a TLVLOG command.
Only YES or NO is accepted.
System Action: The command terminates.
User Response: Reissue the command with a valid HOLD value.
Severity: ERROR.

KLVLW031

RKLVLOG SWITCH REQUESTED
Explanation: A TLVLOG SWITCH request has been accepted. CT/Engine will
allocate a new RKLVLOG SYSOUT file and begin recording on it, then close and
release the old RKLVLOG file. This message is followed by KLVLW022 and
KLVLW023, which report successful processing.
System Action: None.
User Response: None.
Severity: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVLW041

RKLVLOG DATASET DISABLED BY PERMANENT ERROR
Explanation: A BSAM WRITE issued against the currently active RKLVLOG file
failed because of a permanent error.
System Action: RKLVLOG recording is suspended.
User Response: Refer to the MVS SYSLOG for any messages that may have
been issued by IBM’s data management routines. Issue TLVLOG SWITCH to
attempt to allocate a new RKLVLOG dynamically.
Severity: ALERT.

KLVLW081

DYNAMIC ALLOCATION FAILED FOR RKLVLOG: R15(rc) ERROR(error)
INFO(info)
Explanation: A TLVLOG SWITCH request was not successful because the
dynamic allocation for a new SYSOUT file failed. rc is the return code from the
DYNALLOC request; error and info are the error and information reason codes.
System Action: The command terminates. The previous RKLVLOG is still
active.
User Response: Refer to RKLVLOG or VIEWLOG for any KLVDAnnn
messages that may have been issued. Refer to IBM’s Authorized Assembler
Programming Reference for DYNALLOC return codes.
Severity: LOG, ERROR.

KLVLW082

COULD NOT OPEN ddname FOR RKLVLOG
Explanation: A TLVLOG SWITCHrequest could not open a dynamically
allocated SYSOUT file. ddname is the ddname that could not be opened.
System Action: The command terminates. The previous RKLVLOG is still
active; ddname remains allocated to the CT/Engine address space.
User Response: Refer to SYSLOG for any IEFxxxxx messages that may
describe the OPEN error.
Severity: LOG, ERROR.

KLVLW083

DYNAMIC DEALLOCATION FAILED FOR RKLVLOG: R15(rc)
ERROR(error) INFO(info)
Explanation: A TLVLOG SWITCH request could not dynamically deallocate
the RKLVLOG JCL DD statement. rc is the return code from the DYNALLOC
request; error and info are the error and information reason codes.
System Action: The RKLVLOG JCL DD statement remains allocated to the
CT/Engine address space. Refer to IBM’s Authorized Assembler Programming
Reference for DYNALLOC return codes.
Severity: LOG, ERROR.

KLVLW084

*SYSTLG* OPERATOR LOGON FAILED
Explanation: The pseudo-operator *SYSTLG* could not be initialized.
System Action: *SYSTLG* will not be recognized if specified with the AS
operator command. All other RKLVLOG processing continues normally.
User Response: If you are using operator validation in a NAM user exit (for
example, KLVA2NEV), ensure that the *SYSTLG* operator is authorized for
logon.
Severity: LOG, ERROR.

KLVHS001–KLVSC009

KLVNA001

SHOWCB FIELDS=(ACBLEN,RPLLEN) ERROR: R15(r15) R0(r0)
Explanation: A VSAM SHOWCB was issued to find the ACB and RPL lengths
and failed.
System Action: NAM initialization terminates without processing any other
control point specifications. Any NAM database is unavailable.
User Response: Consult the IBM manual Macro Instructions for Data Sets to
determine the reason the SHOWCB macro instruction failed. Return and reason
codes are indicated in the r15 and r0 fields.
Message Type: WARNING.

KLVNA002

parameters
Explanation: As the parameters in module KLVINNAM are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVNA003

DATABASE INACCESSIBLE, NO VSAM LSR RESOURCES:
DSNAME(dsname) CNTRLPT(cntrlpt)
Explanation: NAM database dsname on control point cntrlpt cannot be used
because no LSR resources were allocated during start-up. The parameters
required, as specified in the RKLVIN DD, are LSRKEYLN, LSRPOOL, and
LSRSTRNO.
System Action: CT/Engine start-up terminates.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

KLVNA004

DUPLICATE CONTROL POINT SPECIFICATION: CNTRLPT(cntrlpt)
Explanation: The control point name cntrlpt specified in the initialization library
member KLVINNAM is a duplicate.
System Action: CT/Engine initialization terminates.
User Response: Correct the error in KLVINNAM and restart CT/Engine.
Message Type: WARNING.

KLVNA005

DATABASE ALLOCATION FAILED: DSNAME(dsname) CNTRLPT(cntrlpt)
Explanation: CT/Engine was unable to allocate the dataset dsname. The control
point cntrlpt associated with the dataset is also displayed.
System Action: CT/Engine start-up terminates.
User Response: This message is accompanied by message KLVDA002, which
gives a more specific reason for the error. Use the information provided to
determine the cause of the error and restart CT/Engine.
Message Type: WARNING.

Candle Products Messages Manual (KLVHS–KONCT)

KLVNA006

DATABASE INITIAL LOAD COMPLETE: DSNAME(dsname)
CNTRLPT(cntrlpt)
Explanation: Initialization has completed successfully for the NAM database
dsname in control point cntrlpt.
System Action: None.
User Response: None.
Message Type: INFO.

KLVNA007

DATABASE dsname
INITIAL LOAD mm/dd/yy hh:mm:ss ON smfid
LAST ACCESSED mm/dd/yy hh:mm:ss ON smfid2
Explanation: This message is logged to create an audit trail for each NAM
database dsname specified in member KLVINNAM in the initialization library.
System Action: None.
User Response: None.
Message Type: LOG.

KLVNA008

KLVINNAM RKANPAR PARAMETERS:
Explanation: Module KLVINNAM logs its start-up parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVNA002.
System Action: None.
User Response: None.
Message Type: LOG.

KLVNA009

UNABLE TO LOAD USER SECURITY EXIT: EP(member)
Explanation: CT/Engine was unable to LOAD the security exit member chosen
as a security validation option. This message is accompanied by message
KLVCM003, which provides a more specific reason for the error.
System Action: CT/Engine start-up terminates.
User Response: If message KLVCM003 precedes this message, determine the
cause of the error, correct it, and restart CT/Engine. If KLVCM003 does not
precede this message, ensure that the load module exists in the RKANMODL
concatenation and restart CT/Engine.
Message Type: ERROR.

KLVNA010

CONTROLPOINT cntrlpt INITIALIZED
Explanation: NAM control point cntrlpt has been initialized.
System Action: None.
User Response: None.
Message Type: INFO.

KLVNA011

DATABASE INITIALIZATION FAILED: DSNAME(dsname)
CNTRLPT(cntrlpt)
Explanation: An error was encountered during NAM initialization of control
point cntrlpt.
System Action: CT/Engine initialization terminates.
User Response: Make sure that the NAM database is available and is not
allocated by another region.

KLVHS001–KLVSC009

Message Type:

WARNING.

KLVNA012

GENCB BLK=ACB ERROR: R15(r15) R0(r0)
Explanation: A VSAM GENCB that was issued to create an ACB failed.
System Action: CT/Engine initialization terminates.
User Response: Consult the IBM manual Macro Instructions for Data Sets to
determine the reason the GENCB macro instruction failed. Return and error
codes are indicated in the r15 and r0 fields.
Message Type: WARNING.

KLVNA013

GENCB BLK=RPL ERROR: R15(r15) R0(r0)
Explanation: A VSAM GENCB issued to create an RPL failed.
System Action: CT/Engine start-up terminates.
User Response: Consult the IBM manual Macro Instructions for Data Sets to
determine the reason the GENCB macro instruction failed. Return and reason
codes are indicated in the r15 and r0 fields.
Message Type: WARNING.

KLVNA014

UNABLE TO OPEN NAM DATABASE: DSNAME(dsname) DDNAME(ddn)
R15(r15) ACBERFLG(acberflg)
Explanation: An attempt by CT/Engine to OPEN the NAM database dsname
failed. More information is provided in the message for diagnostic purposes.
System Action: CT/Engine start-up terminates.
User Response: Consult the IBM manual Macro Instructions for Data Sets to
determine the reason the OPEN macro instruction failed. The return code is
indicated in the r15 field.
Message Type: WARNING.

KLVNA015

DATABASE INACCESSIBLE: DSNAME(dsname) CNTRLPT(cntrlpt)
Explanation: The NAM database dsname is not accessible.
System Action: CT/Engine start-up terminates.
User Response: Check the log for other messages concerning this dataset to
determine a more specific reason for the error. If none can be found, contact
Candle Customer Support.
Message Type: WARNING.

KLVNA016

DATABASE RELATIVE KEY POSITION NOT 0: DSNAME(dsname)
CNTRLPT(cntrlpt)
Explanation: The NAM database dsname relative key position is not 0. The
dataset was not defined properly.
System Action: CT/Engine start-up terminates.
User Response: Delete the NAM database in error, redefine it, and restart
CT/Engine. You may need to refer to the original installation procedures to
determine the correct parameters when defining the NAM database.
Message Type: WARNING.

Candle Products Messages Manual (KLVHS–KONCT)

KLVNA017

DATABASE KEY LENGTH NOT n: DSNAME(dsname) CNTRLPT(cntrlpt)
Explanation: While processing the NAM database dsname for control point
cntrlpt, an error was detected in the key length. The length must be equal to n.
Either an incorrect version of the NAM database is being used, or the database
was not defined properly.
System Action: CT/Engine start-up terminates.
User Response: Delete the NAM database in error, redefine it, and restart
CT/Engine. You may need to refer to the original installation procedures to
determine the correct parameters when defining the NAM database.
Message Type: WARNING.

KLVNA018

DATABASE CONTROL RECORD NOT FOUND: DSNAME(dsname)
CNTRLPT(cntrlpt)
Explanation: While attempting to initialize the NAM environment for control
point cntrlpt, an error was detected in the VSAM dataset dsname. The control
record for the database could not be located. This message is accompanied by
KLVVSnnn messages, that give a more specific reason for failure to locate the
record.
System Action: CT/Engine start-up terminates.
User Response: Look in the log for other messages concerning this dataset to
determine a more specific reason for the error. If none can be found, contact
Candle Customer Support.
Message Type: WARNING.

KLVNA019

DATABASE INITIAL LOAD FAILED: DSNAME(dsname) CNTRLPT(cntrlpt)
R15(r15) RPLERRCD(rplerrcd)
Explanation: An I/O error was detected while processing the NAM cluster.
System Action: CT/Engine start-up fails.
User Response: Consult the IBM manual Macro Instructions for Data Sets to
determine the reason the PUT macro instruction failed. Return and error codes
are indicated in the r15 and rplerrcd fields. If the error cannot be attributed to a
user error, contact Candle Customer Support.
Message Type: WARNING.

KLVNA020

keyword(value) IS INVALID FOR CNTRLPT(cntrlpt); DEFAULTS TO def
Explanation: keyword in the KLVINNAM 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.

KLVHS001–KLVSC009

KLVNA021

DATABASE CONTROL RECORD UPDATE FAILED: DSNAME(dsn)
CNTRLPT(cntrlpt)
Explanation: During NAM initialization, CT/Engine attempted to update the
database (dsn) associated with control point cntrlpt. The update failed.
System Action: NAM initialization continues, to identify any other errors.
CT/Engine will terminate after NAM initialization finishes.
User Response: Review RKLVLOG for KLVVS0nn messages that will identify
the error. Correct the error and restart CT/Engine.
Message Type: WARNING.

KLVNA022

MODCB BLK=ACB ERROR: R15(r15) R0(r0)
Explanation: During NAM initialization, CT/Engine attempted to update a
VSAM ACB. The update failed.
System Action: NAM initialization continues, to identify any other errors.
CT/Engine will terminate after NAM initialization finishes.
User Response: Consult the IBM manual Macro Instructions for Data Sets to
determine the reason the MODCB macro instruction failed. Return and reason
codes are indicated in the r15 and r0 fields.
Message Type: WARNING.

KLVNA023

DATABASE DSNAME RETRIEVAL FAILED, RC(rc) ERROR(error)
INFO(info) DDNAME(ddn) CNTRLPT(cntrlpt)
Explanation: During NAM initialization, an attempt to determine the dataset
name associated with DD ddn. The MVS DYNALLOC function failed with the
indicated return, error, and info codes.
System Action: NAM initialization continues, to identify any other errors.
CT/Engine will terminate after NAM initialization finishes.
User Response: Consult the IBM manual Authorized Assembler Programming
Reference to determine the reason DYNALLOC failed.
Message Type: WARNING.

KLVNA031

CLASSES DESCRIPTION NOT FOUND: CNTRLPT(cntrlpt)
RKANPAR(RKANPAR)
Explanation: The member specified on the CLASSES= parameter of control
point cntrlpt was not found in RKANPAR.
System Action: CT/Engine start-up fails.
User Response: Make sure that the correct member name of the protected
class list is specified, and try again.
Message Type: ALERT.

KLVNA032

DUPLICATE CLASS DEFINITION: CNTRLPT(cntrlpt)
RKANPAR(RKANPAR) LINE(line)
Explanation: The resource class name specified has already been defined.
System Action: CT/Engine start-up fails.
User Response: Make sure all resource class names are unique and try again.
Message Type: ALERT.

Candle Products Messages Manual (KLVHS–KONCT)

KLVNA034

DATABASE ALLOCATION FAILED - RESOURCE ERROR:
DSNAME(dsname) CNTRLPT(cntrlpt)
Explanation: CT/Engine was unable to allocate the data set dsname, because of
a logical resource manager error. The control point cntrlpt associated with the
dataset is also displayed.
System Action: CT/Engine start-up terminates.
User Response: This error is probably due to insufficient free storage. Make
sure storage pre-allocated by RKANPAR member KLVINSTG has not depleted all
storage specified by the MAXIMUM parameter in RKLVIN.
Message Type: WARNING.

KLVNA035

DATABASE ALLOCATION FAILED: DSNAME(dsname) CNTRLPT(cntrlpt)
Explanation: CT/Engine was unable to allocate the data set dsname. The
control point cntrlpt associated with the dataset is also displayed.
System Action: CT/Engine start-up terminates.
User Response: Review RKLVLOG for message KLVDA002 followed by IBM
IKJ message from SVC99. Correct the problem and retry.
Message Type: WARNING.

KLVNA036

CONTROL POINT OPTIONS NOT VALID WITH VALIDATE=
Explanation: The VALIDATE keyword was specified on the same logical
statement as the controlpoint definition in member KLVINNAM in the initialization
library.
System Action: CT/Engine start-up terminates.
User Response: Make sure the VALIDATE keyword has been specified as a
separate logical statement from the controlpoint definition and try again.
Message Type: WARNING.

KLVNA037

VALIDATE= validate IS INVALID
Explanation: An invalid value for the VALIDATE keyword was specified in
member KLVINNAM in the initialization library.
System Action: CT/Engine start-up terminates.
User Response: Make sure the VALIDATE keyword value is either SINGLE or
MULTIPLE and try again.
Message Type: WARNING.

KLVNA038

VALIDATE= ALREADY DEFINED; IGNORED
Explanation: The VALIDATE keyword was specified more than once in
member KLVINNAM in the initialization library.
System Action: CT/Engine start-up continues. The duplicate keyword is
ignored.
User Response: Remove the duplicate keyword.
Message Type: WARNING.

KLVHS001–KLVSC009

KLVNA101

UNABLE TO ACCESS NAM DATABASE: DSNAME(dsname)
CNTRLPT(cntrlpt)
Explanation: The network access manager (NAM) was called to validate
security for a user. DB was specified as an option for the control point cntrlpt, but
the database associated with the control point could not be accessed.
System Action: Security validation fails and the user is logged off.
User Response: Check initialization library member KLVINNAM to verify that
the control point and database have been defined correctly.
Message Type: ALERT.

KLVNA102

USER NOT DEFINED: CNTRLPT(cntrlpt) USERID(userid) [GROUP(group])
[TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The supplied user ID is invalid. This message
can be generated if the address space is not APF-authorized. Fields of interest are
the control point name cntrlpt, the userid userid, the group group, the terminal
name terminal, and the application name appl. The control point name cntrlpt
may be in the form cntrlpt1-cntrlpt2, where cntrlpt1 refers to the control point
used and cntrlpt2 to the control point requested. The message is logged to create
an audit trail, but this can be overridden at start-up time.
System Action: This message is installation specific. The system action
depends on the configuration of NAM. If using NAM to do the validation, the
userid was not defined in the NAM database. If using a NAM exit, the external
security package was unable to locate the userid. This message will appear in
RKLVLOG and may be seen at the terminal if the external security package has
not passed a message back to NAM. If a message was passed back by the external
security package, that message will be seen.
User Response: If you are a user viewing this message on your screen, re-enter
a valid user ID. Verify that the address space is APF-authorized.
Message Type: INFO.

KLVNA103

PASSWORD NOT AUTHORIZED: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The password supplied is invalid for the
userid. Fields of interest are the control point name cntrlpt, the userid userid, the
group group, the terminal name terminal, and the application name appl. The
control point name cntrlpt may be in the form cntrlpt1-cntrlpt2, where cntrlpt1
refers to the control point used and cntrlpt2 to the control point requested. The
message is logged to create an audit trail, but this can be overridden at start-up
time.

Candle Products Messages Manual (KLVHS–KONCT)

System Action: This message is installation specific. The system action
depends on the configuration of NAM. If using NAM to do the validation, the
password defined in the NAM database was different than the one entered at the
terminal. If using a NAM exit, the external security package detected a different
password than the one defined for the user. This message will appear in
RKLVLOG and may be seen at the terminal if the external security package has
not passed a message back to NAM. If a message was passed back by the external
security package, that message will be seen.
User Response: If you are a user viewing this message on your screen, supply
a correct password.
Message Type: INFO, VIEW.
KLVNA104

CURRENT PASSWORD EXPIRED: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The current password has expired. Fields of
interest are the control point name cntrlpt, the userid userid, the group group, the
terminal name terminal, and the application name appl. The control point name
cntrlpt may be in the form cntrlpt1-cntrlpt2, where cntrlpt1 refers to the control
point used and cntrlpt2 to the control point requested. The message is logged to
create an audit trail, but this can be overridden at start-up time.
System Action: This message is installation specific. The system action
depends on the configuration of NAM. If using NAM to do the validation, the
password defined in the NAM database has expired. If using a NAM exit, the
password defined to the external security package has expired. This message will
appear in RKLVLOG and may be seen at the terminal if the external security
package has not passed a message back to NAM. If a message was passed back
by the external security package, that message will be seen.
User Response: If you are a user viewing this message on your screen, supply
a new password.
Message Type: INFO, VIEW.

KLVNA105

NEW PASSWORD INVALID: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The new password was invalid. Fields of
interest are the control point name cntrlpt, the userid userid, the group group, the
terminal name terminal, and the application name appl. The control point name
cntrlpt may be in the form cntrlpt1-cntrlpt2, where cntrlpt1 refers to the control
point used and cntrlpt2 to the control point requested. The message is logged to
create an audit trail, but this can be overridden at start-up time.
System Action: This message is installation specific. The system action
depends on the configuration of NAM. If using NAM to do the validation, the new
password passed to NAM was invalid. If using a NAM exit, the new password
passed to the external security package was invalid. This message will appear in
RKLVLOG and may be seen at the terminal if the external security package has
not passed a message back to NAM. If a message was passed back by the external
security package, that message will be seen.

KLVHS001–KLVSC009

User Response: If you are a user viewing this message on your screen, supply
a valid new password.
Message Type: INFO, VIEW.
KLVNA106

USER NOT DEFINED TO GROUP: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The user userid is not defined to the group
specified. Fields of interest are the control point name cntrlpt, the userid userid,
the group group, the terminal name terminal, and the application name appl. The
control point name cntrlpt may be in the form cntrlpt1-cntrlpt2, where cntrlpt1
refers to the control point used and cntrlpt2 to the control point requested. The
message is logged to create an audit trail, but this can be overridden at start-up
time.
System Action: This message is installation specific. This message will appear
with the use of an external security package. The group supplied for the entered
userid was not valid. This message will appear in RKLVLOG and may be seen at
the terminal if the external security package has not passed a message back to
NAM. If a message was passed back by the external security package, that
message will be seen.
User Response: If you are a user viewing this message on your screen, specify
a valid group for the userid supplied.
Message Type: INFO, VIEW.

KLVNA107

USER ACCESS REVOKED: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The user (userid) access has been revoked.
Fields of interest are the control point name cntrlpt, the userid userid, the group
group, the terminal name terminal, and the application name appl. The control
point name cntrlpt may be in the form cntrlpt1-cntrlpt2, where cntrlpt1 refers to
the control point used and cntrlpt2 to the control point requested. The message is
logged to create an audit trail but this can be overridden at start-up time.
System Action: This message is installation specific. This message will appear
with the use of an external security package. Access will no longer be allowed for
this userid due to excessive invalid password attempts, userid expiration, or some
other internal processing by the external security package. This message will
appear in RKLVLOG and may be seen at the terminal if the external security
package has not passed a message back to NAM. If a message was passed back
by the external security package, that message will be seen.
User Response: Access has been revoked for this userid. Contact your security
administrator for the external security package and have the userid reset.
Message Type: INFO, VIEW.

Candle Products Messages Manual (KLVHS–KONCT)

KLVNA108

GROUP ACCESS REVOKED: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. Access to the group supplied has been
revoked for this userid. Fields of interest are the control point name cntrlpt, the
userid userid, the group group, the terminal name terminal, and the application
name appl. The control point name cntrlpt may be in the form cntrlpt1-cntrlpt2,
where cntrlpt1 refers to the control point used and cntrlpt2 to the control point
requested. The message is logged to create an audit trail, but this can be
overridden at start-up time.
System Action: This message is installation specific. This message will appear
with the use of an external security package. Access will no longer be allowed for
this userid/group due to excessive invalid password attempts, userid expiration, or
some other internal processing by the external security package. This message will
appear in RKLVLOG and may be seen at the terminal if the external security
package has not passed a message back to NAM. If a message was passed back
by the external security package, that message will be seen.
User Response: Access has been revoked for this userid/group combination.
Contact your security administrator for the external security package and have the
userid reset.
Message Type: INFO, VIEW.

KLVNA109

TERMINAL NOT AUTHORIZED: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The user userid is not authorized to use this
terminal. Fields of interest are the control point name cntrlpt, the userid userid, the
group group, the terminal name terminal, and the application name appl. The
control point name cntrlpt may be in the form cntrlpt1-cntrlpt2, where cntrlpt1
refers to the control point used and cntrlpt2 to the control point requested. The
message is logged to create an audit trail, but this can be overridden at start-up
time.
System Action: This message is installation specific. This message will appear
with the use of an external security package. Access is not allowed for the userid
from the terminal where signon was attempted. This message will appear in
RKLVLOG and may be seen at the terminal if the external security package has
not passed a message back to NAM. If a message was passed back by the external
security package, that message will be seen.
User Response: If you are a user viewing this message on your screen, correct
the userid or signon from a different terminal. If the problem persists, contact the
security administrator for the external security package.
Message Type: INFO, VIEW.

KLVHS001–KLVSC009

KLVNA110

APPLICATION NOT AUTHORIZED: CNTRLPT(cntrlpt) USERID(userid)
[GROUP(group]) [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called to validate security. The user userid is not
authorized to use the specified application. Fields of interest are the control point
name cntrlpt, the userid userid, the group group, the terminal name terminal, and
the application name appl. The control point name cntrlpt may be in the form
cntrlpt1-cntrlpt2, where cntrlpt1 refers to the control point used and cntrlpt2 to the
control point requested. The message is logged to create an audit trail, but this can
be overridden at start-up time.
System Action: This message is installation specific. This message will appear
with the use of an external security package. Access is not allowed for the userid
to the application where the signon was attempted. The userid is restricted to a set
of applications and the application where the signon was attempted was not one
of those. This message will appear in RKLVLOG and may be seen at the terminal
if the external security package has not passed a message back to NAM. If a
message was passed back by the external security package, that message will be
seen.
User Response: If you are a user viewing this message on your screen, correct
the userid or signon to a different application. If the problem persists, contact the
security administrator for the external security package.
Message Type: INFO, VIEW.

KLVNA111

OPERATOR NOT AUTHORIZED: CNTRLPT(cntrlpt)
[OPERATOR(operator)] [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the Network
Access Manager (NAM) was called. The operator operator is not authorized to use
the CT/Engine operator facility. Fields of interest are the control point name
cntrlpt, the operator id operator, the terminal name terminal, and the application
name appl. The control point name cntrlpt may be in the form cntrlpt1-cntrlpt2,
where cntrlpt1 refers to the control point used and cntrlpt2 to the control point
requested. The message is logged to create an audit trail, but this can be
overridden at start-up time.
System Action: This message is installation specific. This message will appear
with the use of an external security package. Access is not allowed for the userid
to the CT/Engine operator facility by the external security package. This message
will appear in RKLVLOG and may be seen at the terminal if the external security
package has not passed a message back to NAM. If a message was passed back
by the external security package, that message will be seen.
User Response: If you are a user viewing this message on your screen, correct
the operator ID. If the problem persists, contact your security administrator for the
security package.
Message Type: INFO, VIEW.

Candle Products Messages Manual (KLVHS–KONCT)

KLVNA112

COMMAND NOT AUTHORIZED: CNTRLPT(cntrlpt) [OPERATOR(operator)]
[COMMAND(command)] [TERM(terminal)] [APPL(appl)]
Explanation: Security validation for the specified user failed when the network
access manager (NAM) was called. The operator operator is not authorized to
issue the specified command. Fields of interest are the control point name name
cntrlpt, the operator ID operator, the command command, the terminal name
terminal, and the application name name appl. The control point name cntrlpt
may be in the form cntrlpt1-cntrlpt2, where cntrlpt1 refers to the control point
used and cntrlpt2 to the control point requested. The message is logged to create
an audit trail, but this can be overridden at start-up time.
System Action: The command terminates. This message is installation
specific. This message will appear with the use of an external security package.
The operator command entered was not allowed by the external security
package. This message will appear in RKLVLOG and may be seen at the terminal
if the external security package has not passed a message back to NAM. If a
message was passed back by the external security package, that message will be
seen.
User Response: If you are a user viewing this message on your screen, correct
the command or validate the command. If the problem persists, contact your
security administrator for the external security package.
Message Type: INFO, VIEW.

KLVNA113

PARAMETER REJECTED BY USER EXIT: CNTRLPT(cntrlpt)
[OPERATOR(operator)] [COMMAND(command)] [TERM(terminal)]
[APPL(appl)]
Explanation: A NAM FIELDEXIT has determined that a NAM request field is
not valid. The exit should have provided additional messages about the error.
Fields of interest are the control point name name cntrlpt, the operator ID
operator, the command command, the terminal name terminal, and the
application name name appl. The control point name cntrlpt may be in the form
cntrlpt1-cntrlpt2, where cntrlpt1 refers to the control point used and cntrlpt2 to the
control point requested. The message is logged to create an audit trail, but this can
be overridden at start-up time.
System Action: The function is not completed. This message is installation
specific, and may be generated for any NAM function. This message will appear
in RKLVLOG.
User Response: Contact your system programmer to determine why the
installation exit has rejected the value.
Message Type: INFO, VIEW.

KLVHS001–KLVSC009

KLVNA114

PASSTICKET REQUEST NOT AUTHORIZED: CNTRLPT(cntrlpt)
[OPERATOR(operator)] [COMMAND(command)] [TERM(terminal)]
[APPL(appl)]
Explanation: A NAM PASSTICKET request has been denied by the NAM user
exit and the exit has not supplied an override message.
System Action: No PassTicket is generated.
User Response: Contact your security administrator to ensure that you are
authorized to generate a PassTicket for the destination application and userid.
Message Type: INFO, VIEW.

KLVNA151

UNABLE TO ACCESS NAM DATABASE: DSNAME(dsname)
CNTRLPT(cntrlpt)
Explanation: Security validation for the specified user failed when NAM was
called. The database specified as an option for the control point cntrlpt could not
be accessed.
System Action: Security validation fails and the user is logged off.
User Response: Check the definitions of the control point and the database in
the initialization library member KLVINNAM.
Message Type: ALERT.

KLVNA251

UNABLE TO {DELETE | DEFINE} SAF RESOURCE LIST: CLASS(class)
R15(r15)
Explanation: The RACROUTE macro was issued to build or delete an
in-storage profile for class class and failed. r15 is the code returned by
RACROUTE.
System Action: For DELETE, the in-storage profile remains in virtual storage.
For DEFINE, the profile is unavailable.
User Response: Refer to IBM’s RACROUTE Macro Reference for the meaning
of r15.
Message Type: INFO.

KLVNA252

UNABLE TO {DELETE | DEFINE} RACF RESOURCE LIST: CLASS(class)
R15(r15)
Explanation: The RACLIST macro was issued to build or delete an in-storage
profile for class class and failed. r15 is the code returned by RACLIST.
System Action: For DELETE, the in-storage profile remains in virtual storage.
For DEFINE, the profile is unavailable.
User Response: Refer to IBM’s Authorized Assembler Programming Reference
for the meaning of r15.
Message Type: INFO.

Candle Products Messages Manual (KLVHS–KONCT)

KLVNA253

RESOURCE LIST BUILD DISABLED, NOT APF AUTHORIZED
Explanation: An attempt was made (either at initialization or through the NAM
RACLIST command) to build an in-storage profile (for use by your security
system). The attempt failed because the address space is not APF-authorized.
System Action: CT/Engine will use RACHECK macros instead of FRACHECK
to verify security access.
User Response: If you desire in-storage profiles, APF authorize the address
space. If your security system does not provide in-storage profiles, or you have
specified your own security exits in KLVINNAM, you may ignore this message.
Message Type: INFO.

KLVNA254

UNABLE TO CREATE DUMMY ACEE: RC(rc)
Explanation: The NAM RACLIST command was issued to refresh in-storage
profiles, but failed because a dummy ACEE could not be created.
System Action: The command is ignored.
User Response: Use the return code to determine the reason for the
RACROUTE (or possibly RACINIT failure). Refer to IBM’s RACROUTE Macro
Reference (RACROUTE) or Authorized Assembler Programming Reference
(RACINIT) for the meaning of rc.
Message Type: INFO.

KLVNA255

UNABLE TO DELETE DUMMY ACEE: RC(rc)
Explanation: The NAM RACLIST command was issued to refresh in-storage
profiles. The refresh was successful, but the dummy ACEE could not be deleted.
System Action: The ACEE remains active.
User Response: Use the return code to determine the reason for the
RACROUTE (or possibly RACINIT failure). Refer to IBM’s RACROUTE Macro
Reference (RACROUTE) or Authorized Assembler Programming Reference
(RACINIT) for the meaning of rc.
Message Type: INFO.

KLVNA256

REFRESH OF RESOURCE PROFILES COMPLETE
Explanation: The NAM RACLIST command was issued to refresh in-storage
profiles. The refresh was successful.
System Action: None.
User Response: None.
Message Type: INFO.

KLVNT001

"NTD dialog" DIALOG MANAGER INIT FAILED
Explanation: While performing an NTD operator command, CT/Engine could
not initialize the Dialog Manager for the dialog, dialog.
System Action: The NTD command terminates.
User Response: Save the MVS SYSLOG, and the CT/Engine RKLVLOG and
run sheets, then contact Candle Customer Support.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVNT002

"NTD dialog" DIALOG INVOCATION FAILED; DIALOG MANAGER RC(rc)
Explanation: The non-terminal dialog, dialog, failed with a return code of rc.
System Action: The NTD command terminates.
User Response: Refer to message KLVDM011 for a list of return codes, their
meanings, and responses.
Message Type: ERROR.

KLVOP001

OPERATOR(opid) RKANCMD(clist) LINE(lineno) command
Explanation: A command list clist was issued by operator opid. Each command
in the clist is logged to create an audit trail.
System Action: None.
User Response: None.
Message Type: LOG.

KLVOP002

INVALID COMMAND BUFFER [text]
Explanation: A zero or negative length was received by the CT/Engine
command processor. The optional text may be added by CT/Engine modules to
further describe the error.
System Action: The current operation terminates.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP003

INVALID OPERATOR ID [text]
Explanation: A command was issued specifying an inactive operator ID. This
typically occurs when the AS command is issued just as the operator the
command was directed to was logging off. The optional text may be added by
CT/Engine modules to further describe the error.
System Action: The command terminates.
User Response: If the command cannot be attributed to a user error, contact
Candle Customer Support.
Message Type: ERROR.

KLVOP004

APPLICATION NOT ACTIVE [text]
Explanation: A command was issued and directed to an inactive CT/Engine
application. The optional text may be added by CT/Engine modules to further
describe the error.
System Action: The command terminates.
User Response: Validate the application ID and reissue the command.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP005

APPLICATION NOT ACCEPTING COMMANDS [text]
Explanation: A command was issued and directed to a CT/Engine application
that does not have a common interface. The optional text may be added by
CT/Engine modules to further describe the error.
System Action: The command terminates.
User Response: Validate the application applid to determine if a command
interface is defined. Reissue the command specifying a valid application name.
Message Type: ERROR.

KLVOP006

COMMAND NOT FOUND [text]
Explanation: The command or CLIST issued could not be located. The optional
text may be added by CT/Engine modules to further describe the error.
System Action: The command fails.
User Response: Verify that:
1. The command issued is a valid CT/Engine command, or
2. The CLIST is located in the CT/Engine command library (RKANCMD).
Message Type: ERROR.

KLVOP007

COMMAND NOT AUTHORIZED [text]
Explanation: A CT/Engine command issued by an unauthorized operator. The
optional text may be added by CT/Engine modules to further describe the error.
System Action: The command fails.
User Response: None.
Message Type: ERROR.

KLVOP008

clist CLIST COMPLETED
Explanation: The RKANCMD clist member clist has completed execution.
System Action: None.
User Response: None.
Message Type: REPLY

KLVOP009

command COMMAND COMPLETED
Explanation: The command command has completed its output.
System Action: None.
User Response: None.
Message Type: REPLY

KLVOP011

INVALID CLASS NAME: class
Explanation: The DISPLAY command was issued with an invalid class class.
System Action: The command fails.
User Response: Re-enter the command with a valid class.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVOP012

*** ACTIVE RESOURCE LIST ***
class.arg: USE(user) TOKEN(rsid) OWNER(owner)
class.arg: USE(user) TOKEN(rsid)
n OF m RESOURCES DISPLAYED
Explanation: The DISPLAY command was issued and the resource list specified
is displayed. Fields of interest are the class name class, the resource number rsid
and the owner ID owner.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP021

SHUTDOWN COMMAND IGNORED, IMMEDIATE SHUTDOWN ALREADY
IN PROGRESS
Explanation: The user has entered a SHUTDOWN command while an
immediate shutdown was in progress.
System Action: The command is ignored.
User Response: None.
Message Type: INFO.

KLVOP022

SHUTDOWN MUST BE CONFIRMED WITHIN confirm SECONDS
Explanation: The SHUTDOWN command was issued requesting CT/Engine
termination. A confirming SHUTDOWN command must be issued within
confirm seconds, where confirm is the number of seconds that can occur between
initial and confirming shutdown requests. This is a CT/Engine initialization
parameter with a default value of 15 seconds.
System Action: CT/Engine shutdown proceeds if confirmed within confirm
seconds.
User Response: Issue another SHUTDOWN command so CT/Engine
termination can proceed.
Message Type: REPLY, INFO.

KLVOP023

SHUTDOWN STARTED BY operator AT device
Explanation: CT/Engine shutdown was requested and confirmed, and
shutdown is proceeding. The operator and device identify the origin of the
command.
System Action: None.
User Response: None.
Message Type: WARNING.

KLVOP024

SHUTDOWN PROCEEDING: rescnt RESOURCE(S) OUTSTANDING
Explanation: CT/Engine termination was requested and confirmed, and
termination is proceeding. The number rescnt refers to the number of resources
awaiting termination.
System Action: None.
User Response: Issue a second SHUTDOWN command to perform an
immediate shutdown and terminate all outstanding resources.
Message Type: INFO, VIEW.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP025

number SUBTASK(S) QUIESCED: DQA(addr)
Explanation: This message is logged to create an audit trail of each active
subtask quiesced during CT/Engine termination.
System Action: None.
User Response: None.
Message Type: LOG.

KLVOP026

SUBTASK subtask DETACHED
Explanation: This message is logged to create an audit trail of the detachment
of each subtask during CT/Engine termination.
System Action: None.
User Response: None.
Message Type: LOG.

KLVOP027

SHUTDOWN COMPLETE, nnnnK PRIMARY STORAGE UNUSED
Explanation: CT/Engine termination has completed. The unused storage
figure gives a rough guide to the remaining capacity in the current configuration.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP028

CONFIRMATION NOT RECEIVED, SHUTDOWN BYPASSED
Explanation: A confirming shutdown request was not issued in the allotted
confirm seconds, where confirm is the number of seconds that can occur between
initial and confirming shutdown requests. This is a CT/Engine initialization
parameter with a default value of 15 seconds.
System Action: The shutdown request fails.
User Response: Issue or confirm another initial shutdown request if CT/Engine
is to be terminated.
Message Type: ALERT.

KLVOP029

ABNORMAL TERMINATION REQUESTED BY SHUTDOWN
Explanation: The SHUTDOWN command with the abend option was
requested.
System Action: CT/Engine terminates with a dump.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVOP030

IMMEDIATE SHUTDOWN STARTED BY operator AT device
Explanation: The CONFIRM initialization parameter is zero for the
SHUTDOWN command issued by operator operator at device device.
System Action: CT/Engine terminates.
User Response: None.
Message Type: REPLY, WARNING.

KLVHS001–KLVSC009

KLVOP031

REPEATING COMMAND SCHEDULED EVERY n
Explanation: The CT/Engine EVERY command was issued.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP032

ZERO INTERVAL NOT ALLOWED ON "EVERY" COMMAND
Explanation: The CT/Engine EVERY command was issued with zero as time
interval operand.
System Action: The "EVERY" command is ignored.
User Response: Re-issue the command with a non-zero time interval operand.
Message Type: REPLY.

KLVOP033

TIME INTERVAL GREATER THAN 24:00:00 SPECIFIED
Explanation: The CL/ENGINE EVERY command was issued with a time
interval operand which evaluated to greater than 24 hours.
System Action: The "EVERY" command is ignored.
User Response: Re-issue the command with a time interval operand that
evaluates to less than 24 hours.
Message Type: REPLY.

KLVOP041

SESSION PASSED: LU(luname) DEST(applid)
Explanation: LU luname was successfully passed to destination applid by the
LOGOFF command.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP042

UNABLE TO PASS SESSION: LU(luname) R15 (r15) SENSE(sensors)
Explanation: An unsuccessful attempt was made to pass LU luname to another
application by the LOGOFF command.
System Action: None.
User Response: Use IBM’s ACF/VTAM Programming and the r15 and SENSE
sensors fields to determine the reason the CLSDST macro instruction failed and
take appropriate corrective action. The SENSE field format is explained in the
"CT/Engine Sense Data Format" appendix.
Message Type: ERROR.

KLVOP043

SESSION TERMINATION PENDING: LU(luname)
Explanation: The LOGOFF command was issued specifying termination of the
session between an active CT/Engine application and the logical unit luname.
System Action: The session between CT/Engine and luname is enabled for
termination. Termination is pending.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP044

SESSION luname NOT FOUND
Explanation: The CT/Engine LOGOFF command was issued, but the session
between an active CT/Engine application and the LU luname could not be found.
System Action: The command fails.
User Response: Validate the name of the logical unit in question and reissue
the command.
Message Type: ERROR.

KLVOP046

SESSION TERMINATED: LU(lu)
Explanation: The session between an active CT/Engine application and logical
unit lu has been terminated by the LOGOFF command.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP052

UNABLE TO LOAD APPLICATION EXIT: APPLID(applid) EXIT(exit)
Explanation: The OPEN command was issued, but CT/Engine could not load
the application module(s) associated with applid. This message is accompanied
by message KLVCM003, which gives a more specific reason why the module
could not be loaded.
System Action: The application is not opened.
User Response: Be sure that any module referenced on the open command is
located in the CT/Engine load library.
Message Type: ERROR.

KLVOP053

APPLICATION STARTED: APPLID(applid)
Explanation: The application applid was started successfully by the OPEN
command.
System Action: None.
User Response: None.
Message Type: INFO, REPLY.

KLVOP054

UNABLE TO INITIALIZE VTAM ACB: APPLID(applid)
Explanation: An attempt to allocate and initialize a VTAM ACB with the OPEN
command is unsuccessful.
System Action: The OPEN command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP055

APPLICATION STOPPED: APPLID(applid)
Explanation: CT/Engine application applid terminates successfully.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS001–KLVSC009

KLVOP061

SYSTEM OPERATORS:
ID(operator) DEV(dev) PEND(pendnum)
LIMIT(oplimit)

.
.
.
Explanation: The CT/Engine OPERS command was issued. Each active
operator operator at logical unit dev is displayed. Fields of interest are the number
of characters comprising the pending messages pendnum and the maximum
number of characters that may be pending oplimit.
System Action: None.
User Response: None.
Message Type: REPLY.
KLVOP071

PROFILE OPTIONS: [GLOBAL] [LOCAL] [FOLD arg] [SCP] [LIMIT=n]
Explanation: The PROFILE command was issued. The current operator
characteristics are displayed.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP081

MESSAGE FROM operator AT device message
Explanation: The SEND command was issued by operator operator at logical
unit device. Message message was sent to the current operator.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP082

OPERATOR operator NOT LOGGED ON
Explanation: The SEND command was issued specifying that a message be
routed to operator operator, but the operator was not logged on.
System Action: The command fails.
User Response: Validate the parameter operator using the OPERS command
and reissue the original command.
Message Type: ERROR.

KLVOP101

APPLID applid NOT ACTIVE
Explanation: The LOGON command attempted to initiate a session between an
LU and an CT/Engine application applid that is not active.
System Action: The command fails.
User Response: Validate the applid parameter and re-enter the command. If
you receive the same message, the application in question is not active. You can
activate it using the OPEN command.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP102

SESSION STARTED: LU(luname) APPL(appl)
Explanation: The LOGON command successfully started a session between
application appl and LU luname.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP103

UNABLE TO START SESSION: LU(luname) APPL (appl) SENSE(sense)
Explanation: The LOGON command to start a session between application
appl and LU luname failed.
System Action: The command fails.
User Response: Consult IBM’s ACF/VTAM Programming to determine the
cause for the error and take appropriate corrective action. The SENSE field
format is explained in the "CT/Engine Sense Data Format" appendix.
Message Type: ERROR.

KLVOP111

CANDLE ENGINE TIME: time
Explanation: The TIME command causes the CT/Engine time to be displayed.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP112

CANDLE ENGINE TIME RESET TO: time DATE: date
Explanation: The TIME RESET command has set the CT/Engine time and date
to the system local date and time.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP121

INTERNAL TRACE STATUS:
ERROR : arg
DISPATCH: arg
STORAGE : arg
VTAM : arg
LOGIRECS: arg
VSAM : arg
PSM: arg
Explanation: The TRACE command displays the current trace table eligibility
mask. arg is ENABLED OR DISABLED.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVHS001–KLVSC009

KLVOP122

INVALID TRACE ID: arg
Explanation: The TRACE command contains an invalid parameter arg.
System Action: The command fails.
User Response: Validate and correct the trace ID arg, and reissue the
command.
Message Type: ERROR.

KLVOP123

INVALID PREFIX CHARACTER: arg
Explanation: The TRACE command contains an invalid prefix character arg as
one of the parameters.
System Action: The command fails.
User Response: Correct the invalid prefix character (it must be (+) or (-)) and
reissue the command.
Message Type: ERROR.

KLVOP124

INTERNAL TRACE FACILITY DISABLED
Explanation: The TRACE command failed because the internal trace facility has
been disabled.
System Action: The command fails.
Message Type: ERROR.

KLVOP125

TRACE REQUEST REJECTED. REQUIRED ARGUMENT MISSING
Explanation: The GTRACE command was entered with the ON|OFF operand
without specifying a resource to be traced.
System Action: The trace request is rejected.
User Response: Specify the resource to be traced and reissue the command.
Message Type: ERROR.

KLVOP126

TRACE REQUEST REJECTED. INVALID CLASS(TERM|ACB) SPECIFIED
Explanation: An invalid CLASS was specifed.
System Action: The trace request is rejected.
User Response: Specify a correct CLASS and reissue the command.
Message Type: ERROR.

KLVOP127

TRACE REQUEST REJECTED. INTERNAL TRACE FACILITY DISABLED.
Explanation: A GTRACE CLASS(INT) ON command has been issued but no
internal trace table has been allocated at system startup.
System Action: The trace request is rejected.
User Response: If an internal trace is desired, specify DEBUG(Y) in the
KLVSYSIN member of RKANPAR and recycle the system.
Message Type: ERROR.

KLVOP128

TRACE TERM|ACB(resname) QUEUED|ENABLED|DISABLED
Explanation: The trace request for resname of TERM or ACB has been
performed.
System Action: None.
User Response: None.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP129

TRACE REQUEST REJECTED. TERM(resname) NOT A PHYSICAL
TERMINAL.
Explanation: The trace for resname of CLASS(TERM) has been requested, but
the resname is not a physical terminal.
System Action: The trace request is rejected.
User Response: Specify CLASS(ACB), or use the VSSTRACE command to
trace virtual sessions.
Message Type: ERROR.

KLVOP130

GTF INTERFACE HAS NOT BEEN ENABLED
Explanation: A trace request has been issued for a resource but the GTF
interface has not been enabled.
System Action: None.
User Response: Issue the GTF ON command to enable GTF tracing.
Message Type: WARNING.

KLVOP131

TRACE CLASS(INT|TERM|ACB|DLG) STATUS:
Explanation: This is the header message of the trace status display.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP132

TRACE REQUEST REJECTED. INVALID ARGUMENT SPECIFIED.
Explanation: A GTRACE command is specified with an invalid resname.
System Action: The trace request is rejected.
User Response: Correct and reissue the command.
Message Type: ERROR.

KLVOP141

MONITOR MASK FOR operator:
LOG : mask
REPLY: mask
ERROR: mask
INFO : mask
WARN : mask
ALERT: mask
VIEW: mask
USER: mask
Explanation: The MONITOR command displays the current monitor mask. The
mask parameter indicates if the message type is enabled (YES) or disabled (NO)
for this operator. Refer to the "CT/Engine Message Route Codes" appendix for
more information on message types.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVHS001–KLVSC009

KLVOP142

INVALID MESSAGE TYPE: type
Explanation: An invalid message type type was specified as one of the
parameters of the MONITOR command.
System Action: The command fails.
User Response: Refer to the "CT/Engine Message Route Codes" appendix for
more information on message types.
Message Type: ERROR.

KLVOP143

INVALID PREFIX CHARACTER: prefix
Explanation: An invalid message type prefix prefix was specified as one of the
parameters of the CT/Engine MONITOR command.
System Action: The command fails.
User Response: Correct the invalid message type prefix (it must be (+) or (-))
and reissue the command.
Message Type: ERROR.

KLVOP152

MODULE NOT FOUND: module
Explanation: The entry name module specified in the LINK command could
not be found in the CT/Engine load library. This message is accompanied by
message KLVCM003, which indicates a more specific reason why the module
could not be found.
System Action: The command fails.
User Response: Determine if the entry name module is a valid member name
or alias in the CT/Engine load library.
Message Type: ERROR.

KLVOP161

CLOSE IN PROGRESS: APPLID(applid)
Explanation: The CLOSE command terminates application applid.
System Action: Termination is proceeding for the application.
User Response: None.
Message Type: REPLY.

KLVOP162

APPLICATION NOT OPEN: APPLID(applid)
Explanation: Application applid specified in the CT/Engine CLOSE command is
not open.
System Action: The command fails.
User Response: Re-enter the command with the correct applid.
Message Type: ERROR.

KLVOP164

CRITICAL APPLICATION CANNOT BE CLOSED:
APPLID(applid)
Explanation: Application applid specified in the CLOSE command is not
eligible to be terminated because it was opened with the critical attribute.
System Action: The CLOSE command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP165

CLOSE COMPLETE: APPLID(applid)
Explanation: The CLOSE command was issued against applid and completed
successfully.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP182

EMULATION SESSION NOT AVAILABLE: STATUS(sense)
Explanation: A virtual session specified in the EMLU3767 command was not
available to service the request.
System Action: The command fails.
User Response: Refer to the "CT/Engine Message Route Codes" appendix for
the format of the STATUS (sense) field to determine the correct action to take.
Look for other error messages referring to the virtual pool associated with this
request.
Message Type: ERROR.

KLVOP183

EMULATION SESSION STARTED
Explanation: The emulation session specified in the EMLU3767 command was
started successfully.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP184

INVALID SEND STATUS: R1(hex)
Explanation: CT/Engine returned an invalid send status for the EMLU3767
command.
System Action: None.
User Response: Use IBM’s ACF/VTAM Programming and the R1 field to
determine the cause of the error and take appropriate corrective action. The
format of the R1 field is explained in the "CT/Engine Message Route Codes"
appendix.
Message Type: ERROR.

KLVOP185

EMULATION SESSION ENDED
Explanation: The emulation session started via the EMLU3767 command has
ended.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP186

UNABLE TO ACQUIRE VIRTUAL SESSION WITH applid SENSE(sense)
Explanation: The virtual session with applid specified by the EMLU3767
command could not be established.
System Action: None.
User Response: The format of the SENSE field is explained the "CT/Engine
Message Route Codes" appendix, which explains the cause of the error.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVOP191

REPLY FROM operator: COMMAND(command)
Explanation: Operator operator issued command command. This message is
issued to create an audit trail.
System Action: None.
User Response: None.
Message Type: LOG.

KLVOP191

INVALID CLASS NAME: class
Explanation: An AUTOPURG command has been issued from an operator
session that specifies an invalid CLASS= operand.
System Action: The AUTOPURG command is not executed.
User Response: Correct the CLASS=values specified on the AUTOPURG
command and attempt the command again.
Message Type: ERROR.

KLVOP192

*** AUTOPURGE CANDIDATE LIST *** restype.resname: USE(use),
RES(resaddr) OWNER(restype.resname) nnn RESOURCES SCHEDULED
FOR AUTOPURGE
Explanation: AUTOPURG has displayed the candidate list for resources to be
AUTOPURGed. The restype and resname fields show the class and name of the
resource to be AUTOPURGed and also of the OWNER of the resource, if one
exists. The use field shows the current use count for the resource. One line of
resource data will appear for each resource which matches the AUTOPURG
criteria. The nnn field of the last line of the message displays the total number of
resources that meet the AUTOPURG criteria.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP193

*** AUTOPURGED RESOURCES *** restype.resname: USE(use),
RES(resaddr) OWNER(restype.resname) xxx OF yyy RESOURCES
REQUIRED AUTOPURGE
Explanation: AUTOPURG has displayed the resources that actually were
AUTOPURGed. The restype and resname fields show the class and name of the
AUTOPURGed resource and also of the OWNER, if one exists. The use field
shows the current use count for the resource. Resources are not actually
terminated until the use count goes to zero. An AUTOPURG must be done for
each resource until the use count goes to zero to purge the resource. The last line
of the display shows the number of resources that were scheduled (xxx field) and
the number that actually had their use count decremented (yyy field).
System Action: None.
User Response: If the USE count is still positive, another AUTOPURG
command should be issued to purge the resource.
Message Type: ALERT.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP194

RESOURCE NAME IS REQUIRED
Explanation: The AUTOPURG command requires a resource name as part of
the AUTOPURGE criteria.
System Action: The AUTOPURG command is not executed.
User Response: To determine the resource name of the resource to
AUTOPURGE, the DISPLAY operator command can be used to show resources
that are currently in PURGE status and therefore available for AUTOPURGE.
Message Type: ERROR.

KLVOP195

restype.resname1 OWNS restype.resname2, NOT PURGEABLE
Explanation: The AUTOPURG command has detected that resource named by
resname1 owns the resource named by resname2. This resource will not be
AUTOPURGed until all resources owned by it have been terminated.
System Action: An AUTOPURG is not executed for that resource.
User Response: All resources owned by the resource named by resname1 must
be AUTOPURGed first.
Message Type: ERROR, ALERT.

KLVOP201

ANYAPPL SPECIFIED IN A NON DEDICATE POOL IGNORED
Explanation: The parameter ANYAPPL can be specified only on a DEDICATE
pool.
System Action: CT/Engine ignores the ANYAPPL parameter.
User Response: Correct VSM definitions. Refer to the Operator’s Guide, for
more information on issuing this parameter.
Message Type: REPLY.

KLVOP202

INVALID SUBCOMMAND: subcmd
Explanation: Subcommand subcmd specified in the VSM command is not
supported.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP203

UNABLE TO ALLOCATE VSM ACB: ACBNAME(applid) PSWD pswd
Explanation: An attempt to allocate and initialize a VTAM ACB failed.
System Action: Application applid is unavailable.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP204

APPLICATION acbname ALREADY DEFINED TO pool
Explanation: Application acbname specified in the VSM command has already
been defined to pool. Do not define an application more than once to the same
pool.
System Action: The command fails.
User Response: Reissue the command correctly.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVOP205

INCONSISTENT SPECIFICATION: NETNAME(netname)
ACBNAME(acbname) THROUGH(thru)
Explanation: An inconsistency was detected between the netname and thru, or
between the acbname and thru specified in the VSM command.
System Action: The command fails.
User Response: Correct the error and reissue the command.
Message Type: ERROR.

KLVOP207

UNABLE TO OPEN VSM ACB: ACBNAME(acbname) NETNAME (netname)
ARG(arg)
Explanation: The CT/Engine VSM command was issued but one of the
following occurred:
1. A VTAM (OPEN) failed and a KLVVT001 error message indicating the cause
of the error is written to RKLVLOG.
2. The resource could not be defined.
3. The pre-open exit routine specified when the application was opened did not
complete successfully.
System Action: If the THROUGH parameter was specified, an attempt is
made to start the other virtual applications. In any case, the virtual application
indicated is unavailable.
User Response: Depends on the reason for the error.
1. Use the CT/Engine log and IBM’s ACF/VTAM Programming to determine the
cause for the OPEN failure and take appropriate corrective action.
2. Contact Candle Customer Support for possible reasons why the resource
could not be defined.
3. Contact Candle Customer Support to determine why the pre-open routine
exit did not complete successfully.
Message Type: ERROR.

KLVOP208

DEDICATE ATTRIBUTE SPECIFIED, LIMIT=l IGNORED
Explanation: The parameter LIMIT=l is specified on a VSM pool which also
specified DEDICATE. DEDICATE implies a limit of l.
System Action: CT/Engine ignores the LIMIT=l parameter.
User Response: Remove either the LIMIT=l or the DEDICATE parameter to
suppress this message.
Message Type: REPLY.

KLVOP209

SESSLIM SPECIFIED IN A NON DEDICATE POOL IGNORED
Explanation: The parameter SESSLIM can be specified only on a DEDICATE
pool.
System Action: CT/Engine ignores the SESSLIM parameter.
User Response: Correct VSM definitions. See Customization and Operator’s
Guide.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP210

NOCAPPL SPECIFIED IN A NON DEDICATE POOL IGNORED
Explanation: The parameter NOCAPPL can be specified only on a DEDICATE
pool.
System Action: CT/Engine ignores the NOCAPPL parameter.
User Response: Correct VSM definitions. See Customization and Operator’s
Guide.
Message Type: REPLY.

KLVOP211

MODULE LIMIT: cmmax MODULE USAGE: cmcur
PANEL LIMIT: dmmax PANEL USAGE: dmcur
THREADS: stthr
Explanation: The STATUS command was issued. The following information is
displayed:
cmmax

The maximum number of bytes of storage CT/Engine will use
when loading modules. Zero means no limit.

cmcur

The current number of bytes of storage CT/Engine has used to
load modules.

dmmax

The maximum number of bytes of storage dialog management
may use to store panels. Zero means no limit.

dmcur

The current number of bytes the dialog manager is using to store
panels.

stthr

The current number of active threads.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVOP290

VIRTUAL SESSION POOL pool NOT DEFINED
Explanation: Pool pool specified in the VSM command could not be defined.
System Action: The pool specified is unavailable.
User Response: This message is accompanied by a more specific message
indicating why the pool could not be defined. Refer to that messages to determine
the cause of the error.
Message Type: ERROR.

KLVOP291

VIRTUAL SESSION POOL pool DELETED
Explanation: Termination of the virtual session POOL pool, previously created
via the VSM command, was requested and the virtual session POOL pool was
deleted.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS001–KLVSC009

KLVOP302

VIEWLOG CLUSTER NOT AVAILABLE
Explanation: The VIEWLOG cluster specified in the VIEWLOG command is not
available.
System Action: The command fails.
User Response: Look for other messages, KLVVL002 or KLVVL008, to
determine a more specific reason why the cluster is not available, and take
corrective action.
Message Type: ERROR.

KLVOP303

VIEWLOG CLUSTER NOT ACCESSIBLE
Explanation: The VIEWLOG cluster specified in the VIEWLOG command
could not be accessed.
System Action: The command fails.
User Response: Examine the log for other error messages concerning the
VIEWLOG cluster and take corrective action.
Message Type: ERROR.

KLVOP304

DATE FIELD INVALID: DATE(date)
Explanation: The date field date specified in the VIEWLOG FDATE command
is invalid.
System Action: The command fails.
User Response: Specify the date as mm/dd/yy.
Message Type: ERROR.

KLVOP312

AS COMMAND MAY NOT BE DIRECTED TO operator
Explanation: The AS command cannot be directed to operator operator.
System Action: The command fails.
User Response: Validate the operator parameter and reissue the command.
Message Type: ERROR.

KLVOP314

COMMAND ISSUED
Explanation: The AS command was issued.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP315

OPERATOR operator NOT LOGGED ON
Explanation: The AS command was issued but the operator operator was not
logged on.
System Action: The command fails.
User Response: If operator is *SYSVLG* check RKLVLOG for messages to
determine why *SYSVLG* was logged off. The VIEWLOG dataset may be full.
For all other operators, verify that you are using the correct ID and reissue the
command.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP402

UNABLE TO ALLOCATE JES SPOOL FILE: REASON(rsn)
Explanation: The BATCH command did not complete because CT/Engine was
unable to allocate the JES spool file required for the output of the command.
System Action: The command fails.
User Response: The reason field contains the return code from SVC 99
services. This message will be accompanied by message KLVDA002. Refer to that
message to determine the corrective action to be taken.
Message Type: ERROR.

KLVOP403

UNABLE TO OPEN JES SPOOL FILE
Explanation: The BATCH command did not complete because the JES spool
file could not be opened.
System Action: The command fails.
User Response: This message is accompanied by message KLVVS001, which
contains a more specific reason why the file could not be opened. Refer to that
message to determine the corrective action to be taken.
Message Type: ERROR.

KLVOP404

UNABLE TO ALLOCATE DATASET: DSNAME(dsname) REASON(rsn)
Explanation: The BATCH command did not complete because the dataset
containing the batch commands could not be allocated.
System Action: The command fails.
User Response: The reason field contains the return code from SVC 99
services. This message will be accompanied by message KLVDA002. Refer to that
message to determine the corrective action to be taken.
Message Type: ERROR.

KLVOP405

UNABLE TO OPEN DATASET: DSNAME(dsname)
Explanation: The BATCH command did not complete because the dataset
containing the batch commands could not be opened.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP406

UNABLE TO LOGON BATCH OPERATOR
Explanation: The BATCH command did not complete because the operator
(*SUBMIT*) could not be logged on.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP501

COMMAND ISSUED AS CN cnid:RC (rc)
Explanation: An MVS command was issued as console operator cnid. The SVC
34 used to submit the command to the operating system received the return
code rc.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVHS001–KLVSC009

KLVOP502

CT/Engine JOBSTEP NOT AUTHORIZED, COMMAND REJECTED
Explanation: CT/Engine is not running from an APF-authorized library and is
not able to issue the requested MVS command.
System Action: The command fails.
User Response: Run CT/Engine from an authorized library.
Message Type: ERROR.

KLVOP503

NO TEXT PASSED TO THE MVS COMMAND
Explanation: A CT/Engine MVS command was issued with no argument.
System Action: The MVS command is ignored.
User Response: Reissue the command with an argument.
Message Type: ERROR.

KLVOP504

TEXT PASSED TO THE MVS COMMAND GREATER THAN 126
CHARACTERS, COMMAND REJECTED
Explanation: The CT/Engine operator command MVS was issued with an
argument that was too long.
System Action: The MVS command is ignored.
User Response: Reissue the command with a shorter argument.
Message Type: ERROR.

KLVOP552

UNABLE TO ALLOCATE FORWARD ACB: APPLID(appl)
Explanation: CT/Engine was unable to allocate appl specified in the FORWARD
command.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP553

UNABLE TO OPEN FORWARD ACB: APPLID(appl) REASON(rc)
Explanation: CT/Engine was unable to OPEN the appl specified in the
FORWARD command.
System Action: The command fails.
User Response: The REASON field contains the return code from the
ACF/VTAM™ OPEN macro instruction. Refer to IBM’s ACF/VTAM Programming
to determine the cause of the error.
Message Type: ERROR.

KLVOP554

FORWARD TO appldest FROM appl1 STARTED
Explanation: Application appl1 will be FORWARDed to appldest as specified in
the FORWARD command.
System Action: None.
User Response: None.
Message Type: INFO.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP555

FORWARD TO appldest FROM appl1 STOPPED
Explanation: The forwarding of application appl1 was successfully stopped by
the FORWARD command.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP601

VPO FACILITY NOT AVAILABLE
Explanation: The VPO facility required for the VPO command is not active.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP651

UNABLE TO ALLOCATE DIALOG ACB: APPLID(appl)
Explanation: CT/Engine was unable to allocate the appl specified in the
DIALOG command.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP652

UNABLE TO OPEN DIALOG ACB: APPLID(appl) REASON(rc)
Explanation: CT/Engine was unable to OPEN the appl specified in the DIALOG
command.
System Action: The command fails.
User Response: The REASON field contains the return code from the
ACF/VTAM OPEN macro instruction. Refer to IBM’s ACF/VTAM Programming to
determine the cause of the error.
Message Type: ERROR.

KLVOP653

DIALOG APPLICATION appl STARTED: DIALOG(dialog)
LANGUAGE(language)
Explanation: Application appl with controlling dialog dialog was successfully
started by the DIALOG command. language is the language code used to locate
the dialog.
System Action: None.
User Response: None.
Message Type: REPLY, INFO.

KLVOP654

DIALOG APPLICATION appl STOPPED: DIALOG(dialog)
LANGUAGE(language)
Explanation: Application appl with controlling dialog dialog was successfully
stopped by the CLOSE command. language is the language code used to locate
the dialog.
System Action: None.
User Response: None.
Message Type: REPLY, INFO.

KLVHS001–KLVSC009

KLVOP655

LOGON DIALOG UNAVAILABLE: DIALOG(dialog) LANGUAGE(language)
Explanation: A DIALOG command was issued specifying dialog as the logon
dialog and a usable copy of the dialog could not be found in the DD pointed to by
the language code, language. This error may be caused by misspelling the dialog
name in the command or by syntax errors within the dialog itself. In the case of
syntax errors within the dialog, there will be additional messages describing the
errors that were detected.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP656

ATTENTION DIALOG UNAVAILABLE: DIALOG(dialog)
LANGUAGE(language)
Explanation: A DIALOG command was issued specifying dialog as the Window
Control dialog and a usable copy of the dialog could not be found in the DD
pointed to by the language code, language. This error may be caused by
misspelling the dialog name in the command or by syntax errors within the dialog
itself. In the case of syntax errors within the dialog, there will be additional
messages describing the errors that were detected.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP657

ATTENTION DIALOG AND NOPSM CONFLICT: DIALOG APPLICATION
appl
Explanation: A DIALOG command was issued specifying mutually exclusive
parameters.
System Action: The command fails.
User Response: Correct and reissue the command.
Message Type: ERROR.

KLVOP658

UNABLE TO INITIALIZE DIALOG MANAGER: LU(lu) APPLID(appl)
Explanation: The named lu was attempting to log onto the named DIALOG
application and an error was detected while starting execution of the logon dialog
associated with the application.
System Action: The named lu is disconnected from the application.
User Response: Check the CT/Engine log for associated error messages.
Message Type: VIEW.

KLVOP802

UNABLE TO ALLOCATE DATASET: DSNAME(dsname) REASON(rsn)
Explanation: The PRINT command completed unsuccessfully because dsname
could not be allocated.
System Action: The command fails.
User Response: The REASON field refers to the return code from SVC 99
services. This message is accompanied by message KLVDA002, which contains a
more detailed explanation why the dataset could not be allocated. Refer to that
message for more information.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP803

UNABLE TO OPEN DATASET: DSNAME(dsname)
Explanation: The PRINT command completed unsuccessfully because dsname
could not be opened.
System Action: The command fails.
User Response: None.
Message Type: ERROR.

KLVOP804

DATASET PRINT COMPLETE: DSNAME(dsname)
Explanation: The PRINT command was issued and completed successfully.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP805

PRINTER SESSION INACTIVE: PRINTER(printer)
Explanation: The PRINT command completed unsuccessfully because the
session associated with printer printer could not be found.
System Action: The command fails.
User Response: The session between the specified printer and CT/Engine must
be active when the command is issued. Currently a LOGON command must be
issued to log the printer onto the CT/Engine operator ACB.
Message Type: ERROR.

KLVOP809

PRINT REQUEST ACCEPTED
Explanation: The PRINT command completed successfully.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP851

UNABLE TO INITIALIZE ACB FOR NODE appl
Explanation: CT/Engine was unable to allocate the appl specified in the NODE
command.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP852

DUPLICATE NETWORK-ID: appl RKANPAR (config)
Explanation: A conflict was detected in configuration member config in
RKANPAR specified in the NODE command.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVOP853

UNABLE TO OPEN NODE ACB: APPLID(appl) REASON (rc)
Explanation: The NODE command failed because CT/Engine was unable to
open the appl specified.
System Action: The command fails.
User Response: The REASON field contains the return code from the
ACF/VTAM OPEN macro instruction. Refer to IBM’s ACF/VTAM Programming to
determine the cause of the error.
Message Type: ERROR.

KLVOP854

UNABLE TO LOAD NODE COMPONENT(S): APPLID(appl)
Explanation: CT/Engine was unable to load the node components specified in
the LOAD NODE command. Either KLVLUNDE, KLVEVNDE, or KLVICNDE
could not be loaded.
System Action: The command fails.
User Response: Look for other messages in the KLVCMnnn format to
determine which module could not be loaded and why.
Message Type: ERROR.

KLVOP855

NODE STARTED: APPLID(appl)
Explanation: Application appl was successfully started by the
Explanation: NODE command.
System Action: None.
User Response: None.
Message Type: REPLY, INFO.

KLVOP856

NODE STOPPED: APPLID(appl)
Explanation: NODE application appl was successfully stopped.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP857

VALIDATION DIALOG UNAVAILABLE: DIALOG(dialog)
LANGUAGE(language)
Explanation: A NOTE command was issued specifying dialog as the PANEL
(validation) dialog and a usable copy of the dialog could not be found in the DD
pointed to by the language code, language. This error may be caused by
misspelling the dialog name in the command or by syntax errors within the dialog
itself. In the case of syntax errors within the dialog, there will be additional
messages describing the errors that were detected.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP901

NAM INACTIVE
Explanation: The NAM command failed because the NAM facility is inactive.
Either no parameters were specified in the initialization library member
KLVINNAM, the member could not be found, or the NAM facility was never
correctly defined.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP902

NAM ? [CNTRLPT(cntrlpt)]
Explanation: The NAM command was issued and the NAM environment has
been entered. This is a prompting message. cntrlpt indicates the control point for
subsequent NAM commands.
System Action: None.
User Response: Enter NAM commands.
Message Type: REPLY.

KLVOP903

COMMAND: command
Explanation: The NAM command was issued and is returned to the operator.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP904

subcmd NOT RECOGNIZED
Explanation: A NAM subcmd command was issued, but the requested service
subcmd is not supported.
System Action: The command terminates.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP905

varname: text FOR USERID xxxxxxxx
Explanation: The NAM SET command was issued, and the variable varname
was successfully set to the value text for USERID xxxxxxxx.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP906

CNTRLPT cpname DATABASE IS dbname
Explanation: The NAM CNTRLPT cpname command was issued, and the
current control point database is dbname.
System Action: None.
User Response: Contact Candle Customer Support.
Message Type: REPLY.

KLVHS001–KLVSC009

KLVOP908

DUPLICATE DECLARATION: varname
Explanation: The NAM DECLARE command completed unsuccessfully
because the variable varname has already been declared.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: REPLY.

KLVOP909

varname DECLARED: LENGTH(n)
Explanation: The NAM DECLARE command successfully defined variable
varname with length n.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP910

ACCESS UPDATED|CREATED FOR USERID userid
Explanation: The NAM SET userid [PASSWORD=pswd, CHANGE=chg] was
issued to change or add a user control record for user userid.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP911

USER userid DELETED
Explanation: The NAM DELETE userid command was issued and all records
for the specified user have been deleted.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP912

USER userid NOT FOUND
Explanation: The NAM DELETE userid command was issued, but no records
could be found for the specified userid.
System Action: The command is ignored.
User Response: Contact Candle Customer Support.
Message Type: REPLY.

KLVOP914

varname ERASED FOR USERID userid
Explanation: A NAM SET command was issued for variable varname with no
value to set the variable to. The command action is to erase the variable for
USERID userid. The variable still exists on the NAM database but its value for the
specified user is zero or NULL.
System Action: The next variable is processed.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP915

VARIABLE name LENGTH len
Explanation: The NAM VLIST command was issued, and the declared variables
with the corresponding lengths are displayed.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP916

USER userid DEFINED date time
Explanation: The NAM DISPLAY command displays the current user statistics.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP917

LAST ACCESS date time
Explanation: The NAM DISPLAY command was issued. This message is only
issued if database entry validation is used for the current control point.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP918

varname: text
Explanation: The NAM DISPLAY command was issued and variables for the
requested user ID are displayed.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP919

NAM END
Explanation: The NAM END command was issued.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVOP920

VARIABLE varname IS UNDECLARED
Explanation: The NAM SET command was issued to set a variable varname for
a particular user ID, but the variable was never declared.
System Action: The command fails.
User Response: Before a NAM SET command can be issued to manipulate a
variable, the variable must be declared with the NAM DECLARE command.
Message Type: REPLY.

KLVOP921

INVALID VARIABLE REFERENCE: variable
Explanation: The NAM SET command was issued, but the command failed
because the variable variable is illegally referenced. Either the variable name was
too long, or there is no colon (:) separating the variable name and the text.
System Action: Any remaining variables are processed.
User Response: Correct the error and reissue the command.
Message Type: REPLY.

KLVHS001–KLVSC009

KLVOP922

VARIABLE EXPRESSION TOO LONG FOR varname: expr
Explanation: The NAM SET command was issued, but the command failed
because the length of varname, defined via the NAM DECLARE command, is not
long enough to hold the requested expression expr.
System Action: Any remaining variables are processed.
User Response: Correct the error and reissue the command. The NAM LIST
command can be used to list all the declared variables and their respective
lengths.
Message Type: REPLY.

KLVOP923

INVALID PASSWORD FOR USERID xxxxxxxx
Explanation: A NAM SET command was issued to change a password, and the
password was invalid.
System Action: The password is changed to an unknown value.
User Response: Issue the NAM SET command again with a valid password.
Message Type: REPLY.

KLVOP924

I/O ERROR: CNTRLPT(cntrlpt) DATABASE (dsname)
Explanation: An attempt to put a record to the database dsname by a NAM
command failed as a result of an I/O error.
System Action: The command fails.
User Response: Examine the CT/Engine log for error message KLVVS021 or
KLVVS031. These messages contain a more specific reason why the PUT
operation failed.
Message Type: ERROR.

KLVOP926

CNTRLPT cntrlpt DATABASE UNAVAILABLE
Explanation: A NAM command was issued but no control point database was
defined for this control point.
System Action: The command fails.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVOP927

USER cccccccc - PASSWORD NOT DEFINED
Explanation: A NAM DISPLAY cccccccc command was issued, but no
password has been set for this user ID.
System Action: None.
User Response: Contact your NAM database administrator to have a
password set for this user ID.
Message Type: REPLY.

KLVOP929

cpname[,cntrlpt[,...]]
Explanation: The NAM DBLIST command lists each control point, along with
its associated database.
System Action: None.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP930

cpname [,SAF(SUBSYS=sysid,REQUESTOR=rqid)] [,RACF] [,DB] [,EXIT]
[,NOTIFY] [,NONAF] [DATABASE=dsname]
Explanation: The NAM CPLIST command lists the current control points and
their attributes.
System Action: None.
User Response: Contact Candle Customer Support.
Message Type: REPLY.

KLVOP951

SCB DUMP
Explanation: The SNA command requested a dump of the session control block
and status of a certain session. This command is used as a debugging tool for
CT/Engine application programmers. Text is for Candle Customer Support use.
System Action: None.
User Response: None.
Message Type: ERROR.

KLVOP953

UNSUPPORTED SUBCOMMAND: subcmd
Explanation: The SNA command was issued with the specified subcommand,
but the subcommand is not supported.
System Action: The command is ignored.
User Response: Supply a valid subcommand name.
Message Type: ERROR.

KLVOP960

RTM rtm-name INTERFACE IS TERMINATING
Explanation: The specified RTM interface is being terminated in response to a
user request (RTM OFF).
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP961

RTM rtm-name INTERFACE ENABLED - EXTERNAL NAME: ext-name
USEREXIT: exit-name
Explanation: An RTM ON command for TYPE = ETE or NetSpy™ was
successfully processed. The interface to the indicated response time monitor is
now active.
Note: This is a USEREXIT change only if RTM is already ON.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP962

RTM rtm-name INTERFACE DISABLED
Explanation: An RTM OFF command processed successfully, or the interface
was active but was deactivated while processing an RTM ON command. The
interface to the indicated response time monitor is now inactive.
System Action: None.
User Response: None.
Message Type: INFO.

KLVHS001–KLVSC009

KLVOP963

COMMAND ERROR, RTM INTERFACE MAY BE SET “ON” OR “OFF”
Explanation: ON or OFF was not specified as the first positional parameter on
an RTM command.
System Action: The RTM command is not processed and the RTM interface
state is not changed.
User Response: Correct the command syntax and reissue the command.
Message Type: ERROR.

KLVOP964

RTM rtm-name INTERFACE IS NOT SUPPORTED FOR VTAM LEVEL
version-level
Explanation: An RTM command could not be processed because CT/Engine is
executing under a release of ACF/VTAM™ that does not support the ETE or
NetSpy RTM interface.
System Action: The RTM command is not processed and the RTM interface
state remains inactive.
User Response: Identify the release of ACF/VTAM that you are running.
ACF/VTAM release 3.1.0 and above support the ETE or NetSpy interface.
Message Type: ERROR.

KLVOP965

RTM rtm-name INTERFACE USEREXIT exit-name IS INVALID
Explanation: While processing an RTM ON command, the specified USEREXIT
could not be loaded into virtual storage, or the user exit module did not contain
an NOP instruction as the first word of the module.
System Action: The RTM command is not processed and the RTM interface
state remains inactive.
User Response: Verify that the user exit module was properly assembled and
link-edited into an accessible program library, and that the requirement for the
initial NOP instruction is met. Contact Candle Customer Support if you need
further assistance.
Message Type: ERROR.

KLVOP966

COMMAND ERROR, RTM rtm-name IS UNKNOWN
Explanation: An RTM command specified a response time monitor whose
name is not recognized. NPM, ETE, and NetSpy are currently supported.
System Action: The RTM command in error is not processed and the RTM
interface state is not changed.
User Response: Correct the name and issue the command again.
Message Type: ERROR.

KLVOP967

COMMAND ERROR, EXTERNAL NAME NOT VALID FOR RTM rtm-name
Explanation: An RTM ON command specified a parameter that is valid only for
the ETE or NetSpy interface.
System Action: The RTM command in error is not processed and the RTM
interface state is not changed.
User Response: Correct the name and issue the command again, or omit the
invalid parameter and issue the command again.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVOP968

RTM NPM INTERFACE ENABLED - USEREXIT: exit-name
Explanation: An RTM ON command for the NPM response time monitor was
successfully processed. The interface to NPM is now active.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP969

UNABLE TO CONNECT TO RTM rtm-name
Explanation: The RTM ON command failed.
System Action: The RTM interface state remains inactive.
User Response: Refer to message KLVRT021. Correct the problem if possible
and reissue the command.
Message Type: ALERT.

KLVOP970

RTM rtm-name NOT STARTED
Explanation: An RTM OFF command was issued for a response time monitor in
which the interface is not active.
System Action: Command is ignored.
User Response: None.
Message Type: INFO.

KLVOP971

GTF INTERFACE ENABLED, GTRACEID: id INTERNAL: status
Explanation: A GTF ON command has successfully been completed. id is the
ID written for all GTF records. status can be YES or NO. YES means that internal
trace records will also be written to GTF dataset.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP972

GTF INTERFACE DISABLED
Explanation: A GTF OFF command has successfully completed.
System Action: None.
User Response: None.
Message Type: INFO.

KLVOP973

COMMAND ERROR, GTF INTERFACE MAY BE SET "ON" OR "OFF"
Explanation: A GTF command with an invalid operand has been entered.
System Action: The command is rejected.
User Response: Correct the command and reissue it.
Message Type: ERROR.

KLVOP974

COMMAND ERROR, GTRACEID: id IS INVALID
Explanation: A GTF command with an invalid GTRACE ID has been entered.
System Action: The command is rejected.
User Response: Make sure that the GTRACE ID is within the range of 1–1023.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVOP975

COMMAND ERROR, INTERNAL: value IS INVALID
Explanation: A GTF command with an invalid value for the INTERNAL
operand has been entered.
System Action: The command is rejected.
User Response: Valid values for the INTERNAL operand are YES or NO.
Message Type: ERROR.

KLVPA001

SYNAD ERROR: synadmsg
Explanation: A physical error occurred while reading a partitioned dataset. The
operating system provides synadmsg, which is documented in IBM’s Macro
Instructions for Data Sets. The text of synadmsg includes the jobname, stepname,
unit address, device type, ddname, operation, error description, absolute track
address, and access method. Message KLVPA002 is issued to provide additional
diagnostic information. If the data set is a PDS/E, message KLVPA007 may follow
with additional operating system information.
System Action: The library is closed then reopened, and the operation is
retried.
User Response: Examine the text of synadmsg and KLVPA002 to determine
the reason for the error. If the error description in synadmsg is OUT OF
EXTENT, compress the library after the CT/Engine address space has been
terminated and is not running.
Message Type: INFO.

KLVPA002

SYNAD ERROR SENSE AND STATUS BYTES: xxxxyyyy
Explanation: A physical error has occurred while reading a partitioned dataset.
xxxx contains sense bytes 1 and 2, and yyyy contains status bytes 1 and 2 as
documented in IBM’s Using Data Sets. Message KLVPA001 was issued prior to
this to provide additional diagnostic information.
System Action: The library is closed, reopened, and the operation is retried.
User Response: Review message KLVPA001 and examine the sense and status
bytes to determine the cause of the error.
Message Type: INFO.

KLVPA003

LIBRARY ddname REFRESHED, SYNAD EXIT DRIVEN
Explanation: A physical error has occurred while reading the library referenced
by ddname. The library has been closed and reopened in an attempt to recover
from the failure. Messages KLVPA001 and KLVPA002 have been issued to
provide diagnostic information regarding the error.
System Action: None.
User Response: None.
Message Type: INFO.

Candle Products Messages Manual (KLVHS–KONCT)

KLVPA004

LIBRARY ddname UNUSABLE, REFRESH FAILED
Explanation: A physical error occurred while reading the library referenced by
ddname. The library was closed and reopened, and the error persisted when the
operation was retried.
System Action: The request is terminated.
User Response: Examine the accompanying KLVPA001 and KLVPA002
messages to determine the cause for the failure. If ddname is a critical library such
as RKANPENU, the CT/Engine address space should be stopped and restarted as
soon as possible.
Message Type: INFO.

KLVPA005

error, FUNCTION(PDS): ‘text’
Explanation: A syntax error, error, was found while processing the parameters
passed to the PDS SSPL dialog function. text is the text at or near the error.
Message KLVDM015 follows and identifies the associated dialog.
System Action: The dialog is terminated.
User Response: If this error occurs while running CL/SUPERSESSION, correct
the dialog and restart the dialog process. If this error occurs while running any
other Candle product, contact Candle Customer Support.
Message Type: VIEW.

KLVPA006

NO VALID REQUEST CODED FOR FUNCTION(PDS)
Explanation: A null string was passed as the request code to the PDS SSPL
dialog function. Message KLVDM015 follows and identifies the associated dialog.
System Action: The dialog is terminated.
User Response: If this error occurs while running CL/SUPERSESSION, correct
the dialog and restart the dialog process. If this error occurs while running any
other Candle product, contact Candle Customer Support.
Message Type: VIEW.

KLVPA007

synadmsg
Explanation: A physical error occurred while reading a PDS/E partitioned data
set. Message KLVPA007 follows KLVPA001 and displays additional information
provided by the operating system.
System Action: See KLVPA001.
User Response: See KLVPA001.
Message Type: INFO.

KLVPK001

INSUFFICIENT STORAGE FOR PACKED STRING
Explanation: During a PACK operation KLV$PACK determined that a piece of
storage large enough to hold a packed string could not be obtained.
System Action: The thread is abended.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVPM001

PSM NOT AVAILABLE: DIALOG(dlg) LU(lu) APPL(appl)
Explanation: A dialog attempted to execute a PSM dialog function that operates
on the presentation space screen-image buffer (for example, PSMATTR) and there
was no buffer. This may be caused, for example, by attempting to execute such a
function within a dialog that has no BODY. dlg is the name of the dialog in error
and it was executing on behalf of the terminal user at lu. appl is the controlling
application for lu.
System Action: The current dialog fails.
User Response: Contact Candle Customer Support.
Message Type: VIEW.

KLVPM003

UNSUPPORTED PSM SERVICE: DIALOG(dlg) LU(lu) APPL(appl)
Explanation: A dialog attempted to execute the PSM function and the service
name could not be recognized. This may be caused, for example, by misspelling
the service name or by a PSM function that is obsolete. All services of the PSM
function have been replaced by discrete functions. For example, PSM ATTR has
been replaced by the PSMATTR function. dlg is the name of the dialog in error
and it was executing on behalf of the terminal user at lu. appl is the controlling
application for lu.
System Action: The current dialog fails.
User Response: Replace the obsolete PSM function service in error with the
corresponding discrete function.
Message Type: VIEW.

KLVPM005

PSM BUFFER INTEGRITY ERROR
Explanation: 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.

KLVPM010

PSM MAXIMUM ERROR POPUP COUNT IS xx [, WAS yy]
Explanation: This message is displayed in response to the PSM command. With
no operands the current setting for the maximum popup count is displayed. In
response to the PSM ERPCOUNT=xx command both the original setting and the
new setting are displayed.
System Action: None.
User Response: None.
Message Type: INFO.

Candle Products Messages Manual (KLVHS–KONCT)

KLVPM011

TERMINAL luname LOGGED OFF - ERPCOUNT EXCEEDED
Explanation: A terminal, "luname", has caused more simultaneous error
recovery operations than the ERPCOUNT limit set by the PSM command.
"luname" is logged off.
System Action: None.
User Response: None.
Message Type: INFO.

KLVPM012

PSM PRIVATE EXTENSION NOT INITIALIZED
Explanation: The PSM command was issued and the PSM private extension
was not available.
System Action: The PSM command is not executed.
User Response: Wait until CT/Engine has completed initialization, then reissue
the command.
Message Type: INFO.

KLVPM013

PSM ERP INFO BLOCK POINTER IS ZERO
Explanation: The PSM command was issued and the PSM ERP block was not
available.
System Action: The PSM command is not executed.
User Response: Wait until CT/Engine has completed initialization, then reissue
the command.
Message Type: INFO.

KLVPM021

INPUT PROCESSING EXCEPTION: RC=rc,lu_name,
modname,attention_code,fdbk, error_data,datastream
Explanation: An input message from the physical terminal has caused an
exception condition in PSM where
rc

Identifies the reason for the error. See the reason code analysis
table below for more information.

lu_name

Physical terminal LU name.

modname

Module identifier.

attention_code

Pending AID.

fdbk

Feedback information internal to CT/Engine.

error_data

Two bytes of error data. See the reason code analysis table below
for a description of the valid data.

datastream

Up to first ten bytes of the input message causing the exception.

The following table lists possible reason codes for the input exception with
associated system action codes and user response codes. After locating the reason
code, refer to the appropriate system action and user response following this
table.

KLVHS001–KLVSC009

Table 1. Description of reason codes for KLVPM021
Reason
Code

Description

System
Action

User
Response

0601

Internal Exception Condition

0602

Internal Exception Condition

0603

Internal Exception Condition

0604

Internal Exception Condition

0605

Internal Exception Condition

0606

Internal Exception Condition

0607

Internal Exception Condition

0608

Internal Exception Condition

0609

Internal Exception Condition

060A

Internal Exception Condition

060B

Internal Exception Condition

060C

Internal Exception Condition

060D

Internal Exception Condition

060E

Internal Exception Condition

0901

Internal Exception Condition

0902

Internal Exception Condition

0903

Internal Exception Condition

0904

Internal Exception Condition

0905

Unsupported AID received
(error_data=unsupported aid)

0906

Invalid CLEAR/CLEAR partition

0907

Internal Exception Condition

0908

Internal Exception Condition

0909

Internal Exception Condition

090A

Invalid buffer address (error_data=buffer
address)

090B

Invalid codepoint detected
(error_data=codepoint)

090C

Invalid value in Set Attribute (error_data=Set
Attribute type/value pair)

090D

Unexpected end of output (error_data=last 1 or
2 bytes)

Candle Products Messages Manual (KLVHS–KONCT)

Table 1. Description of reason codes for KLVPM021
Reason
Code

System
Action

Description

User
Response

090E

Internal Exception Condition

090F

Internal Exception Condition

0910

Internal Exception Condition

0911

Internal Exception Condition

0912

Internal Exception Condition

0913

Unexpected formatted input (error_data=buffer
address)

0914

Input data from unknown field
(error_data=buffer address)

0915

Attention key received during pre-popup read.

0916

Read modified already satisfied.

System Action: One of the following:
® Action 1. Error recovery displays the TERMINAL INPUT ERROR message on
the terminal. The input message is rejected with an appropriate sense code
and normal processing resumes.
®

Action 2. Error recovery ignores the input message and normal processing
resumes.

User Response: One of the following:
® If the TERMINAL INPUT ERROR message displays, press ENTER to remove
the message and continue normal operation. If the problem persists, the
system administrator should obtain a VSSTRACE of the failure and a copy of
any related error messages and contact Candle Customer Support.
®

If the TERMINAL INPUT ERROR message displays, press ENTER to remove
the message and continue normal operation. If the problem persists, the
system administrator should analyze the failure and contact the appropriate
hardware or software vendor.

Message Type:
KLVPM051

INFO.

KLVINPSM RKANPAR PARAMETERS:
Explanation: Module KLVINPSM logs its start-up parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVPM052.
System Action: None.
User Response: None.
Message Type: LOG.

KLVHS001–KLVSC009

KLVPM052

parameters
Explanation: As the parameters in module KLVINPSM are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVPM101

QUERY REPLY DATA IS NOT VALID FOR LU(lu)
Explanation: Query reply data received from the named lu, in response to a
3270 Read Partition Query command, could not be correctly interpreted.
System Action: The session with the named lu continues normally. The
CT/Engine Presentation Space Manager will not allow certain 3270 extended
datastream orders (for example color, highlighting) to be used with the named lu.
User Response: Contact Candle Customer Support.
Message Type: LOG.

KLVPT001

PRINT FAILED FOR user TO printer, SENSE=xxxxxxxx
Explanation: A VSSPRINT or PSMPRINT request from user to printer printer
failed. For a VSSPRINT, user represents an actual userid ID. For a PSMPRINT,
user represents a physical terminal ID. The sense code from the failing send
request is xxxxxxxx.
System Action: The print request terminates.
User Response: Using the sense information, try to determine the problem
with the printer and retry.
Message Type: INFO.

KLVRE001

GCSDISKS REFRESHED
Explanation: The REFRESH GCSDISKS command was successful.
System Action: None.
User Response: None.
Message Type: REPLY

KLVRE002

INVALID REFRESH TYPE: type
Explanation: The type specified in the REFRESH command is invalid.
System Action: The command fails.
User Response: Correct the type parameter and reissue the command.
Message Type: ERROR.

KLVRE003

DIALOG dlgname REFRESHED (tracetype) LANGUAGE(language)
Explanation: The dialog dlgname, specified in the REFRESH command, was
successfully refreshed. tracetype indicates whether (TRACE) or not (NOTRACE)
the dialog is traceable. language is the language code.
System Action: None.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVRE004

UNABLE TO REFRESH DIALOG dlgname LANGUAGE(language)
Explanation: An error occurred while trying to refresh the DIALOG dlgname
specified in the REFRESH command. language is the language code used during
the refresh attempt.
System Action: The command fails. Any previously compiled copy of
dlgname remains available.
User Response: This message is accompanied by KLVDMnnn messages that
indicate why the panel could not be refreshed.
Message Type: ERROR.

KLVRE005

BLDL FAILED FOR modname
Explanation: A BLDL failed during a refresh operation for module modname
specified in the REFRESH MODULE command.
System Action: The command fails.
User Response: This message is accompanied by message KLVCM003, which
indicates why the BLDL failed.
Message Type: ERROR.

KLVRE006

BLDL COMPLETE: MODULE(modname)
SIZE: size
ENTRY: entry
Explanation: The REFRESH MODULE command completed successfully for
modname. size is the decimal size of the module in bytes. entry is the hexadecimal
entry point address.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVRE008

MISSING OR INVALID DSNAME(dsname)
Explanation: An invalid data set name, dsname, was coded on a REFRESH
SENSE command.
System Action: The sense code table is not refreshed. The previous global
sense table remains in effect.
User Response: Reissue the REFRESH SENSE command with a valid data set
name.
Message Type: ERROR.

KLVHS001–KLVSC009

KLVRE009

SENSE CODE TABLE REFRESH FROM "dsname(member)" resulttext
Explanation: A REFRESH SENSE command has completed. dsname is the
data set name and member is the member name that contain the table
definitions. resulttext displays the success or failure of the command:
COMPLETED
SUCCESSFULLY

The global sense table has been updated.

UNSUCCESSFUL, MEMBER
NOT FOUND

member is not in dsname.

UNSUCCESSFUL,
ALLOCATE FAILED FOR
DSN

dsname could not be allocated.

UNSUCCESSFUL, OPEN
ERROR

An MVS OPEN for dsname failed.

UNSUCCESSFUL, SYNTAX
ERROR ENCOUNTERED

member contains an invalid sense code definition.

System Action: If the command was successful, the global sense table has
been updated. Otherwise, the command terminates and the previous sense table
remains in effect.
User Response: Depends on resulttext.
COMPLETED
SUCCESSFULLY

None.

UNSUCCESSFUL, MEMBER
NOT FOUND

Reissue the command with the correct member and
data set names.

UNSUCCESSFUL,
ALLOCATE FAILED FOR
DSN

Review RKLVLOG for message KLVDA002 followed
by message IJK56228I from SVC99. Reissue the
command with a valid, cataloged data set name.

UNSUCCESSFUL, OPEN
ERROR

Review the JES log for IBM data management
messages (IEC). Ensure that dataset is a PDS.

UNSUCCESSFUL, SYNTAX
ERROR ENCOUNTERED

Review RKLVLOG for KLVSCnnn and KLVSEnnn
error messages. Correct the errors in member, then
reissue the command.

Message Type:

REPLY for success; ERROR otherwise.

Candle Products Messages Manual (KLVHS–KONCT)

KLVRM004

LOGICAL RESOURCE EXIT STACK INTEGRITY ERROR
Explanation: The CT/Engine Resource Manager detected inconsistent data
while processing a logical resource purge or cleanup request, usually because of a
storage overlay.
System Action: The request is terminated with a U0100 abend, sending a
dump to the RKLVSNAP file and/or the system’s dump data sets. The resource
involved is left in an indeterminate state.
User Response: Recycle the CT/Engine address space as soon as possible.
Retain the CT/Engine run sheets, dump files, this message, and the MVS system
log, then contact Candle Customer Support.
Message Type: ABEND.

KLVRS001

INVALID $RSS REQUEST
Explanation: KLV$RSS detected an invalid function code in its input parameter
list.
System Action: The thread is terminated.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ABEND.

KLVRS002

INVALID RSS RELEASE REQUEST
Explanation: An RSS release request was made for a lock that was not held.
System Action: The thread is terminated.
User Response: Contact Candle Customer Support. Keep dump, RKLVLOG,
SYSLOG, and runsheets.
Message Type: ABEND.

KLVRT001

PARAMETER ERROR
Explanation: CT/Engine detected an invalid RTM event code.
System Action: A call to RTM fails. CT/Engine creates a DUMP and continues
processing.
User Response: Contact Candle Customer Support with the contents of the
DUMP.
Message Type: ABEND.

KLVRT010

RTM NPM INTERFACE event IS UNRECOGNIZED
Explanation: The NPM interface module does not recognize the session
manager event code passed. Event code is a 2 hexadecimal digit field.
System Action: The NSI vector containing the session manager event is not
processed.
User Response: Contact Candle Customer Support.
Message Type: INFO.

KLVHS001–KLVSC009

KLVRT011

NPM MODULE FNMNSI REQUIRES APF AUTHORIZATION
Explanation: RTM support for NPM has been selected, but the CT/Engine job
step is not authorized.
System Action: The RTM command is not processed and the RTM interface
state remains inactive.
User Response: Authorize the job step. Make sure all libraries concatenated to
RKANMODL are APF authorized.
Message Type: ALERT.

KLVRT012

UNABLE TO LOAD NPM MODULE FNMNSI
Explanation: CT/Engine was unable to load the IBM-supplied module FNMNSI
because the NPM load library is not in the RKANMODL library concatenation or
in LINKLIST.
System Action: The RTM command is not processed and the RTM interface
state remains inactive.
User Response: Make FNMNSI accessible to CT/Engine by doing one of the
following:
® Copy module FNMNSI to one of the RKANMODL libraries and issue the RTM
ON command.
®

Concatenate the NPM load library to RKANMODL, restart CT/Engine, and
issue the RTM ON command.

Message Type:

ALERT.

KLVRT013

$STG ERROR
Explanation: CT/Engine was unable to allocate storage for the NPM/NSI NMVT
request units.
System Action: A call to NSI fails, CT/Engine creates a DUMP and continues
processing.
User Response: Contact Candle Customer Support with the contents of the
DUMP.
Message Type: ABEND.

KLVRT014

PARAMETER ERROR
Explanation: A call to NSI failed because of an invalid internal parameter.
System Action: A call to NSI fails, CT/Engine creates a DUMP and continues
processing.
User Response: Contact Candle Customer Support with the contents of the
DUMP.
Message Type: ABEND.

Candle Products Messages Manual (KLVHS–KONCT)

KLVRT020

RTM NPM SEND REQUEST FAILED: LU=lu-name APPL=applname
EVENT=X’xx’
Explanation: A non-zero return code was returned from the IBM-supplied
interface module FNMNSI because of a request error or an exceptional condition
where:
® lu-name is the physical terminal name.
®

applname is the application name if applicable.

System Action: Processing associated with the request is terminated.
User Response: A list of return codes and reason codes can be found in IBM’s
NPM Installation and Customization under the NetView® Synergy Interface
appendix. Contact Candle Customer Support if you need further assistance.
Message Type: INFO.
KLVRT021

RTM NPM request FAILED: RC=nn REASON=nnn
Explanation: A non-zero return code was returned from the IBM-supplied
interface module FNMNSI because of a request error or an exceptional condition.
This message is produced for CONNECT and DISCONNECT requests.
System Action: Processing associated with the request is terminated.
User Response: A list of return codes and reason codes can be found in the
IBM manual NPM Installation and Customization under the NetView Synergy
Interface appendix. Contact Candle Customer Support if you need further
assistance.
Message Type: ALERT.

KLVRT022

RTM NPM VECTOR ERROR
Explanation: CT/Engine detected an invalid internal NPM function call.
System Action: A call to NSI fails, CT/Engine creates a DUMP and continues
processing.
User Response: Contact Candle Customer Support with the contents of the
DUMP.
Message Type: ABEND.

KLVRT023

RTM NPM NSI ADDRESS SPACE NOT RUNNING
Explanation: The NPM NSI address space is not running. NPM has rejected a
SEND, CONNECT, or DISCONNECT request by CT/Engine with a return code of
20.
System Action: The RTM interface in CT/Engine is terminated if active. If the
rejected request is CONNECT, CT/Engine sets a timer and retries the request
every 60 seconds.
User Response: Start the NSI address space and reissue the RTM ON
command.
Message Type: ALERT.

KLVHS001–KLVSC009

KLVRT030

$STG ERROR
Explanation: CT/Engine was unable to allocate storage for the ETE or NetSpy
mapping message.
System Action: CT/Engine creates a DUMP and continues processing.
User Response: Contact Candle Customer Support with the contents of the
DUMP.
Message Type: ABEND.

KLVRT031

PARAMETER ERROR
Explanation: CT/Engine was unable to process the mapping message for ETE
or NetSpy interface because of an internal invalid parameter.
System Action: CT/Engine creates a DUMP and continues processing.
User Response: Contact Candle Customer Support with the contents of the
DUMP.
Message Type: ABEND.

KLVSC001

KEYWORD NOT FOUND: keyword environmental_information
Explanation: CT/Engine was parsing a line and encountered a keyword that
was not defined. This is one message in a class of syntax error messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

KLVSC002

REQUIRED OPERAND OMITTED: field environmental_information
Explanation: CT/Engine was parsing a line and encountered a required
operand that was omitted. This is one message in a class of syntax error
messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

KLVSC003

OPERAND TOO SHORT: operand environmental_information
Explanation: CT/Engine was parsing a line and encountered a keyword or
positional operand that was too short. This is one message in a class of syntax
error messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSC004

OPERAND TOO LONG: environmental_information operand
Explanation: CT/Engine was parsing a line and encountered a keyword or
positional operand that was too long. This is one message in a class of syntax
error messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

KLVSC005

INVALID NUMERIC OPERAND: operand environmental_information
Explanation: CT/Engine was parsing a line and encountered a keyword or
positional operand that must be numeric, but is not. This is one message in a class
of syntax error messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

KLVSC006

INVALID QUOTED STRING: string environmental_information
Explanation: CT/Engine was parsing a line and encountered a string that did
not adhere to quoting rules, probably due to a mismatch of quotes. This is one
message in a class of syntax error messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

KLVSC007

INVALID DELIMITER USAGE: string environmental_information
Explanation: CT/Engine was parsing a line and encountered an invalid use of
delimiters. This is caused by either a mismatch of delimiters or improper
delimiters. Valid delimiters are
Blank separates parameters.
,

Comma separates parameters.

Equal separates keyword from keyword value.

(

Open parens separates keyword from keyword value.

‘x’

Parameters within single quotes contain text with embedded delimiters.

Dash indicates continuation.

Plus continues as is.

)

Close parens delimits the end of a keyword value.

A common cause of this error is data added to a keyword that is defined as a
keyword without data. This is one message in a class of syntax error messages.

KLVHS001–KLVSC009

System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.
KLVSC008

AMBIGUOUS KEYWORD REFERENCE: keyword
environmental_information
Explanation: CT/Engine was parsing a line and encountered a keyword that
was ambiguous, probably because not enough characters were included to
uniquely define the keyword. This is one message in a class of syntax error
messages.
System Action: The action being performed terminates.
User Response: The environmental portion of the message indicates where the
syntax error was detected. Use this information to correct the error.
Message Type: ERROR, ALERT, WARNING.

KLVSC009

INVALID TIME SPECIFICATION
Explanation: A scan failed because time was specified incorrectly.
System Action: The command fails.
User Response: Correct the time parameter and try again.
Message Type: ERROR.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSD001–KLXOP005

2
KLVSD001

PRIMARY MAIN STORAGE INFORMATION:
Explanation: The STORAGE command was issued and this message identifies
the start of information about CT/Engine primary storage use. If DETAIL was
specified, message KLVSD003 follows this; otherwise KLVSD005 follows.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD002

EXTENDED MAIN STORAGE INFORMATION:
Explanation: The STORAGE command was issued and this message identifies
the start of information about CT/Engine extended storage use. If DETAIL was
specified, message KLVSD003 follows this; otherwise KLVSD005 follows. This
message follows KLVSD008.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD003

ALLOCATION DETAIL:
Explanation: This message is a header message and identifies the start of
detailed information about CT/Engine storage use. It is a conditional extension of
KLVSD001 and KLVSD002.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD004

SIZE(range) USE(usecnt) TOTAL(totcnt) ACCESSED(acccnt)
Explanation: This message displays information about a storage pool. It follows
KLVSD003.
range

Specifies a range (m–n, in bytes) of the sizes of data blocks in this
storage pool. For example, a range of 1–16 indicates that this pool
contains all blocks that are from 1–16 bytes long.

usecnt

Specifies the number of blocks in use in the pool.

totcnt

Specifies the total number of blocks in the pool.

acccnt

Specifies the number of times a request was made against the
pool.

KLVSD001–KLXOP005

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD005

LIMIT(stolim) SLOPE(sl) SIZES(range) TOTAL(tot)
Explanation: This message appears in response to the CT/Engine STORAGE
operator command and displays storage parameters about primary or extended.
It follows KLVSD001 and KLVSD002, or KLVSD004 if DETAIL was requested.
stolim

Specifies (in bytes) the size of the largest block that can be
allocated.

A Candle-internal parameter.

range

Specifies the number of storage areas.

tot

Specifies (in kilobytes) the total amount of storage available to
end-user applications and CT/Engine functions. Storage not
included in this total is storage obtained during CT/Engine
initialization for the following:
® resident load modules
® internal trace table
® Logical Resource Table
® log buffers
This storage is excluded from the tot field of the display because
once allocated it remains allocated for the life of the address space.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD006

FREE(free) CARVED(carved) OVERHEAD(ovhead)
Explanation: This message appears in response to the CT/Engine STORAGE
operator command and specifies additional information about primary and
extended storage. It follows KLVSD005.
free

Specifies (in kilobytes) the amount of storage available.

carved

Specifies (in kilobytes) the amount of storage allocated for use in
fulfilling storage requests.

ovhead

Specifies (in bytes) the amount of storage used for storage control.

System Action: None.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSD007

pp% IS IN USE; tt% ALLOWED [- THRESHOLD EXCEEDED]
Explanation: This message displays the amount of storage in use for primary or
extended storage. It follows KLVSD006.
pp

Indicates the amount of storage currently in use.

Indicates the defined quiesce threshold level for free storage. This
will not appear in the message if the threshold is defined as 0%.

THRESHOLD EXCEEDED will appear when the threshold value has been met
(for instance, in quiesce mode for free storage).
System Action: CT/Engine will inhibit the initiation of new work (sessions,
dialogs, and so on). Work that is already active will continue to run. When the
storage in use drops below the threshold, normal processing returns.
User Response: If THRESHOLD EXCEEDED persists, contact your systems
administrator who should review the CT/Engine storage use in order to determine
what actions should take place.
Message Type: REPLY.
KLVSD008

pp% HAS BEEN CARVED; tt% ALLOWED [- THRESHOLD EXCEEDED]
Explanation: This message displays the amount of storage carved in primary or
extended storage. It follows KLVSD007.
pp

Indicates the amount of storage currently carved.

Indicates the defined quiesce threshold level for carved storage. This
will not appear in the message if the threshold is defined as 0%.

THRESHOLD EXCEEDED will appear when the threshold value has been met
(for instance, in quiesce mode for carved storage).
System Action: CT/Engine will inhibit the initiation of new work (sessions,
dialogs, etc.). Once the threshold has been reached, this inhibition remains until
CT/Engine is restarted.
Users currently active on CT/Engine will continue to run, although they will not be
able to initiate new dialogs or sessions.
User Response: When THRESHOLD EXCEEDED is displayed, perform an
orderly shutdown of CT/Engine. Then contact your systems administrator, who
should review the CT/Engine storage use in order to determine what actions
should take place.
Message Type: REPLY.

KLVSD001–KLXOP005

KLVSD021

TMS(num) PREFIX(pfx) CUSHION(cshn)
Explanation: This message appears in response to the CT/Engine STORAGE
operator command and displays information about CT/Engine temporary storage
use.
num

Specifies (in bytes) the amount of temporary storage allocated.
CT/Engine uses this storage, for example, to resolve a string
expression. In general, this value should be zero.

pfx

Specifies (in bytes) the length of the storage block prefix.

cshn

Specifies (in bytes) the overhead for each storage block. This value
is equal to the value of pfx plus the debug overhead, if any.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD031

BUFFER POOL INFORMATION:
Explanation: This message marks the beginning of the buffer pool information.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD032

POOL BUFSIZE(bufsize) SEGSIZE(segsize) MASK(mask) SIDEQ(n)
Explanation: This message provides detailed information about a buffer pool.
Currently, there are four buffer pools, one for each of the standard 3270 model
sizes. The meaning of the individual fields are as follows:
bufsize

The size of the individual buffers that are allocated from within a
buffer segment. The standard sizes of the four buffer pools
correspond to the 3270 model types as follows:

1920
2560
3440
3564

Model2
Model3
Model4
Model5

segsize

The size of the buffer segments in the pool. The system
automatically determines the segment size, with 65536 (64K)
being the largest possible size and also the best size for buffer pool
performance.

mask

A bit mask that indicates the possible buffer allocations within the
buffer segment.

sideq

A list header to buffers that have been logically released but which
are not yet available for reallocation.

System Action: None.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSD033

BUFFERS INUSE(inuse) MAX(max) GETS(gets) FREES(frees)
Explanation: This message provides additional information about a buffer pool.
It follows KLVSD032.
inuse

The number of buffers that are currently in use. This number is
obtained from the simple calculation of gets minus frees at the time
the display is requested.

max

The maximum number of buffers from this pool that were ever
concurrently in use. This statistic is checked and updated, if
necessary, every time a buffer is obtained.

gets

The number of buffer allocation requests directed to this pool. This
number is a simple running total of get requests throughout the life
of the system.

frees

The number of buffer deallocation requests directed to this pool.
This number is a simple running total of free requests throughout
the life of the system.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD034

SEGMENTS INUSE(inuse) MAX(max) GETS(gets) FREES(frees) Q(q)
QMAX(qmax)
Explanation: This message provides additional information about a buffer pool.
It follows KLVSD033.
inuse

The number of segments that are currently in use. This number is
obtained from the simple calculation of gets minus frees at the time
the display is requested.

max

The maximum number of segments that were ever concurrently
allocated to this pool. This statistic is checked and updated, if
necessary, every time a segment is obtained.

gets

The number of segment allocations performed for this pool. This
number is a simple running total of get requests throughout the life
of the system.

frees

The number of segment deallocations performed for this pool.
This number is a simple running total of free requests throughout
the life of the system.

The number of segments currently on the free queue of segments
containing available buffers. This statistic is updated every time a
segment is added to or removed from the free queue.

qmax

The maximum number of segments that were ever concurrently on
the free queue of segments containing available buffers. This
statistic is checked and updated, if necessary, every time a
segment is added to the free queue.

KLVSD001–KLXOP005

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD039

END OF BUFFER POOL INFORMATION
Explanation: This message marks the end of the buffer pool information.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD101

MAIN STORAGE SCAN STARTED
Explanation: The storage MAP command was issued and this message
identifies the start of information about CT/Engine storage use. Messages
KLVSD102 thru KLVSD105, and KLVSD107 follow this.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD102

MAIN STORAGE SCAN ENDED
Explanation: This message marks the end of storage MAP information.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD103

NAME(blkid) SIZE(length) TOTAL(count)
Explanation: This message displays information about the content of carved,
allocated storage. Storage reported in this message is storage which has been
allocated with a specific, printable control block ID. It follows KLVSD107.
blkid

Specifies the control block ID for a data structure found in storage.
For example, a blkid of "$ACB" indicates that an Application
Control Block was located in storage.

length

Specifies the length in bytes of the blkid.

count

Specifies the total number of blkid of size length located in storage.

System Action: None.
User Response: None.
Message Type: REPLY.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSD104

NAME(....) SIZE(length) TOTAL(count)
Explanation: This message displays information about the content of carved,
allocated storage. Storage reported in this message is storage which has been
allocated as a "typed", "self-defining" data structure. These data structures do not
contain a printable control block ID. The "NAME" reported in this message is "....".
....

Specifies that the data structure located in storage does not have a
printable control block ID.

length

Specifies the length in bytes of the "self-defining" data structure.

count

Specifies the total number of "typed" structures of size length
located in storage.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD105

NAME(FREE) SIZE(length) TOTAL(count)
Explanation: This message displays information about the content of carved,
free storage. Storage reported in this message is storage which has been carved
and now resides on a free list. This storage is available for re-use.
FREE

Specifies that the data structure located in storage is on the free list.

length

Specifies the length in bytes of this free block.

count

Specifies the total number of "FREE" blocks of size length located
in storage.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD106

INSUFFICIENT STORAGE TO PROCESS COMMAND
Explanation: Processing of the storage MAP command has terminated because
there is insufficient storage in the extended private area.
System Action: The storage MAP command is terminated.
User Response: Reissue the command after ensuring that there is sufficient
storage. Refer to the Operator’s Guide for more information on the STORAGE
command.
Message Type: ERROR.

KLVSD001–KLXOP005

KLVSD107

STORAGE MAP FOR areadesc STORAGE
Explanation: This message displays the specific areas of storage to be mapped.
The mapped area is determined from the operands specified on the storage MAP
command.
areadesc

Specifies the area of storage to be mapped. PRIMARY indicates
only storage below the 16M line will be mapped. EXTENDED
indicates only storage above the 16M line will be mapped.
PRIMARY AND EXTENDED indicates all CT/Engine storage will
be mapped. PRIMARY AND EXTENDED is the default.

System Action: None.
User Response: None.
Message Type: REPLY.
KLVSD108

STORAGE INTEGRITY ERROR. SCAN TERMINATED
Explanation: Processing of the storage MAP command has terminated because
of errors encountered in the storage management data structures.
System Action: The command is terminated. CT/Engine issues snap dumps of
the environment for problem determination. CT/Engine processing continues.
User Response: Contact Candle Customer Support. Keep the dump and
RKLVLOG.
Message Type: ERROR.

KLVSE051

DEFAULT SENSE CODE TABLE DEFINED
Explanation: The global sense code table has been constructed from the
RKANPAR member KLVINSNS.
System Action: None.
User Response: None.
Message Type: INFO.

KLVSE052

INVALID TYPE SPECIFIED: type STATEMENT# nnn
Explanation: A sense code type other than LUSTAT or EXRESP was found in
statement nnn.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Correct the statement and reissue the REFRESH SENSE
command.
Message Type: ERROR.

KLVSE053

SENSE TABLE SIZE(nnnn)
Explanation: The sense code table has been built or refreshed and occupies
nnnn bytes of storage.
System Action: None.
User Response: None.
Message Type: LOG.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSE054

SYNTAX ERROR CONFLICTING PARAMETERS FOR SENSE ACTION
SETTING ‘statement’, STATEMENT# nnn
Explanation: The sense code statement contains an unknown keyword.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Correct the statement and reissue the REFRESH SENSE
command.
Message Type: ERROR.

KLVSE055

USER SENSE CODE TABLE DEFINED
Explanation: The REFRESH SENSE command has successfully completed and
the global sense table has been updated.
System Action: None.
User Response: None.
Message Type: INFO.

KLVSE056

TABLE CAPACITY OF 64K LU NAMES EXCEEDED FOR SENSE(xxxxxxxx)
Explanation: The sense code listed had more than 64K names listed for
FROMAPPL or FROMLU.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Reduce the number of LU names for the sense code and
reissue the REFRESH SENSE command.
Message Type: ERROR.

KLVSE057

INVALID HEX CHARACTERS IN SENSE CODE FIELDS, ‘statement’,
STATEMENT# nnn
Explanation: The sense code value in the statement indicated has characters
other than 0–9 or A–F.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Correct this sense code to contain valid hex characters and
reissue the REFRESH SENSE command.
Message Type: ERROR.

KLVSE058

SENSE TABLE SIZE (nnnnnn), EXCEEDS REQUEST LIMIT
Explanation: The sense code table size is larger than the current storage request
limit.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: If the table cannot be specified with wildcard names to
decrease the storage needed to hold it, the limit value for extended storage must
be increased.
Message Type: ERROR.

KLVSD001–KLXOP005

KLVSE059

SENSE TABLE TOO LARGE, IGNORED
Explanation: The sense code table exceeds 2G bytes and cannot be built.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVSE060

DUPLICATE LU ID FOR THIS SENSE CODE, THE FIRST IS RETAINED,
‘statement’, STATEMENT# nnn
Explanation: An LU ID was encountered that matches one already stored for
this sense code.
System Action: The processing actions specified on the first definition are
retained.
User Response: Remove the duplicate LU statement(s).
Message Type: WARN.

KLVSE061

EITHER FROMAPPL OR FROMLU IS REQUIRED, ‘statement’,
STATEMENT# nnn
Explanation: FROMAPPL or FROMLU must be coded.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Add the required keyword and reissue the REFRESH SENSE
command.
Message Type: ERROR.

KLVSE062

BOTH FROMAPPL AND FROMLU ARE NOT ALLOWED, ‘statement’,
STATEMENT# nnn
Explanation: FROMAPPL and FROMLU cannot be coded together.
System Action: If this error is encountered during CT/Engine initialization,
only the default sense rules will be loaded. If this response was from a REFRESH
SENSE command then the currently active global sense table is not refreshed.
User Response: Remove either FROMLU or FROMAPPL and reissue the
REFRESH SENSE command.
Message Type: ERROR.

KLVSE063

KLVINSNS RKANPAR PARAMETERS:
Explanation: Module KLVINSNS logs its start-up parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVSE064.
System Action: None.
User Response: None.
Message Type: LOG.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSE064

parameters
Explanation: As the parameters in module KLVINSNS are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSI001

INVALID STORAGE CLASS ccc ENCOUNTERED IN
RKANPAR(KLVINSTG)
Explanation: CT/Engine encountered an invalid storage class in the KLVINSTG
member. ccc is the invalid class found. Storage class must be P or X.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

KLVSI002

INVALID STORAGE SIZE sss ENCOUNTERED IN RKANPAR(KLVINSTG)
Explanation: CT/Engine encountered an invalid storage size in the KLVINSTG
member. sss is the invalid size found. Storage size must be a value from 1 to the
maximum defined in the LIMIT start-up parameter.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

KLVSI003

INVALID STORAGE COUNT nnn ENCOUNTERED IN
RKANPAR(KLVINSTG)
Explanation: CT/Engine encountered an invalid block count in the KLVINSTG
member. nnn is the invalid count found. Storage count must be a positive
number.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

KLVSI004

nnn BLOCKS OF LENGTH sss GENERATED IN ccc STORAGE
Explanation: nnn is the number of storage blocks generated, sss is the size of the
blocks generated, and ccc is the storage class for the blocks generated.
System Action: None.
User Response: None.
Message Type: INFO.

KLVSI005

STORAGE INITIALIZATION COMPLETE
Explanation: The storage initialization is complete.
System Action: None.
User Response: None.
Message Type: INFO.

KLVSD001–KLXOP005

KLVSI006

KLVINSTG RKANPAR PARAMETERS:
Explanation: Module KLVINSTG logs its start-up parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVSI007.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSI007

parameters
Explanation: As the parameters in module KLVINSTG are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSI010

CONTROL BLOCK ERROR DURING INITIALIZATION
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI011

INVALID STORAGE CLASS
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI020

CONTROL BLOCK ERROR DURING TERMINATION
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI021

LOGIC ERROR DURING TERMINATE REQUEST
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSI022

INVALID STORAGE CLASS ON TERMINATE REQUEST
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI030

CONTROL BLOCK ERROR DURING GET
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI031

INVALID STORAGE CLASS DURING GET
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI032

ZERO LENGTH STORAGE REQUEST
Explanation: A storage block with a length of zero was requested.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI033

STORAGE REQUEST LIMIT EXCEEDED
Explanation: A storage block with a length that exceeded the limit was
requested.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI040

CONTROL BLOCK ERROR DURING FREE
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSD001–KLXOP005

KLVSI041

ZERO ADDRESS ON FREE REQUEST
Explanation: A request to free a storage block at address zero was encountered.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI042

INVALID STORAGE AREA ON FREE REQUEST
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI043

STORAGE INTEGRITY ERROR
Explanation: An integrity error occurred during an attempt to free storage. A
probable storage overlay has occurred.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI044

STORAGE OVERLAP DETECTED
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI050

CONTROL BLOCK ERROR DURING USE/DROP
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVSI051

LOGIC ERROR DURING USE/DROP
Explanation: An internal processing error occurred during storage isolation
processing.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

Candle Products Messages Manual (KLVHS–KONCT)

KLVSP001

$SPS INVOCATION OR INTERNAL ERROR
Explanation: A CT/Engine processing routine detected an invalid request.
System Action: The request is terminated with a U0100 abend, sending a
dump to the RKLVSNAP file and/or the system’s dump data sets.
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.

KLVSP002

$SPS STRING LENGTH INVALID
Explanation: A CT/Engine processing routine detected an invalid parameter.
System Action: The request is terminated with a U0100 abend, sending a
dump to the RKLVSNAP file and/or the system’s dump data sets.
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.

KLVSQ000

QUIESCE MODE state FOR type
Explanation: This message indicates either a change in one of the possible
storage quiesce values or that a quiesce value is still active. This message will
appear when a quiesce mode changes or when the STGMON interval forces the
message to appear. Possible state values:
IS IN EFFECT
HAS BEEN ENTERED
HAS BEEN RELEASED
Possible type values:
FREE PRIMARY STORAGE
CARVED PRIMARY STORAGE
FREE EXTENDED STORAGE
CARVED EXTENDED STORAGE
System Action: None.
User Response: If a quiesce mode condition persists, contact your systems
administrator, who will contact your Candle product administrator. The systems
programmer should review the CT/Engine storage use in order to determine what
actions should take place.
Message Type: ALERT, WARNING.

KLVSS001

SUBSYSTEM name ALREADY ACTIVE
Explanation: A name name that was already active was used to initialize the
CT/Engine subsystem interface.
System Action: CT/Engine terminates.
User Response: Look in member KLVINSSI in RKANPAR and verify the
subsystem name.
Message Type: ALERT.

KLVSD001–KLXOP005

KLVSS002

SUBSYSTEM name INITIALIZED: SSCVT(addr)
Explanation: The CT/Engine subsystem interface name with SSCVT address
addr was successfully initialized.
System Action: None.
User Response: None.
Message Type: INFO.

KLVSS003

SUBSYSTEM name UNABLE TO LOAD KLVSSREQ
Explanation: CT/Engine was unable to initialize subsystem interface name.
Module KLVSSREQ could not be loaded.
System Action: CT/Engine terminates.
User Response: Look for messages in the KLVCMnnn format to determine a
more specific reason the module could not be loaded.
Message Type: ALERT.

KLVSS004

SUBSYSTEM name DUPLICATED
Explanation: CT/Engine found a duplicate subsystem name name.
System Action: CT/Engine terminates.
User Response: Look in member KLVINSSI in RKANPAR to locate the
duplicate subsystem name.
Message Type: ALERT.

KLVSS005

SUBSYSTEM name SUCCESSFULLY INSTALLED
Explanation: The CT/Engine subsystem interface name was successfully
installed.
System Action: None.
User Response: None.
Message Type: INFO.

KLVSS006

KLVINSSI RKANPAR PARAMETERS:
Explanation: Module KLVINSSI logs its start-up parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVSS006.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSS007

parameters
Explanation: As the parameters in module KLVINSSI are read, a log audit trail
is created.
System Action: None.
User Response: None.

Candle Products Messages Manual (KLVHS–KONCT)

KLVST001

CANDLE ENGINE INITIALIZATION ERROR(S), ABEND U0012
Explanation: One or more errors were detected during CT/Engine start-up.
System Action: CT/Engine terminates with a U0012 abend. Other KLVSTnnn
messages precede this one and identify the error(s).
User Response: Examine the CT/Engine and MVS logs to determine the
error(s) that were detected, take corrective action, and restart CT/Engine.
Message Type: ALERT.

KLVST002

TSO OPTION INVALID FOR NON-TSO ADDRESS SPACE
Explanation: The start-up parameter TSO was specified as Y (for yes), but
CT/Engine is not executing in a TSO address space.
System Action: CT/Engine terminates.
User Response: Correct the TSO parameter and retry.
Message Type: ALERT.

KLVST003

INVALID PARMLIST PARAMETER - text
Explanation: A syntax error was detected by CT/Engine in the parameter list
specified by the PARM= keyword on the MVS EXEC JCL statement. text is the
text at or near the point where the error was found.
System Action: CT/Engine terminates with a U0012 abend.
User Response: Correct the indicated area of text and restart CT/Engine.
Message Type: ALERT.

KLVST004

INVALID RKLVIN PARAMETER - text
Explanation: A syntax error was detected by CT/Engine in the RKLVIN start up
parameters. text is the text at or near the point where the error was found.
System Action: CT/Engine terminates with a U0012 abend.
User Response: Correct the indicated area of text and restart CT/Engine.
Message Type: ALERT.

KLVST005

MVS JOBSTEP AUTHORIZATION REQUIRED
Explanation: The initialization parameter SWAP=N was specified, but the job
step was not authorized.
System Action: CT/Engine terminates.
User Response: If the SWAP=N parameter is to be used, the job step must be
authorized.
Message Type: ALERT.

KLVST006

MVS/XA EXECUTION ENVIRONMENT REQUIRED
Explanation: AMODE31(YES) was specified as an initialization parameter but
CT/Engine is not running on an MVS/XA™ or MVS/ESA™ host.
System Action: CT/Engine terminates.
User Response: None.
Message Type: ALERT.

KLVSD001–KLXOP005

KLVST007

BLDVRP FAILED FOR VSAM LSR BUFFER POOL, RC=rc
Explanation: A BLDVRP macro was issued to allocate a VSAM local shared
resource buffer pool and ended with a non-zero return code, rc. The two most
likely causes are:
1. Insufficient main storage to satisfy the request.
2. A previously issued BLDVRP was issued without a corresponding DLVRP in
the CT/Engine address space. This typically occurs when CT/Engine is
running in a TSO address space and has previously abended in the current
TSO session.
System Action: CT/Engine terminates.
User Response: Refer to the IBM VSAM or DFP manual that describes the
BLDVRP macro for the meaning of rc. For the two most likely causes:
1. Adjust the main storage allocation parameters and/or LSRPOOL values and
restart the CT/Engine address space.
2. Start CT/Engine in a fresh address space.
Message Type: ALERT.

KLVST008

PRIMARY MAIN STORAGE UNAVAILABLE
Explanation: A variable length GETMAIN could not be satisfied. The
MINIMUM(nnn,P) start-up parameter regulates the minimum value that will
satisfy the GETMAIN request. This refers to below the line storage.
System Action: CT/Engine terminates.
User Response: Adjust the MINIMUM parameter and retry.
Message Type: ALERT.

KLVST009

FREEMAIN TYPE=VC FAILED
Explanation: A FREEMAIN that was issued for a previously allocated block of
main storage has failed.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVST010

PRIMARY RESERVED MAIN STORAGE UNAVAILABLE
Explanation: Insufficient main storage exists to satisfy the requirements for the
start-up parameter RESERVE(nnn,P). This message refers to below the line
storage.
System Action: CT/Engine terminates.
User Response: Adjust the storage allocation parameters, and retry.
Message Type: ALERT.

KLVST011

PRIMARY STORAGE NOT REALLOCATED
Explanation: A GETMAIN macro instruction failed.
System Action: CT/Engine terminates.
User Response: Retry the start-up procedure.
Message Type: ALERT.

Candle Products Messages Manual (KLVHS–KONCT)

KLVST012

EXTENDED MAIN STORAGE UNAVAILABLE
Explanation: A variable length GETMAIN could not be satisfied. The
MINIMUM(nnn,X) start-up parameter regulates the minimum value that will
satisfy the GETMAIN request. This message refers to above the line storage.
System Action: CT/Engine terminates.
User Response: Adjust the MINIMUM parameter, and retry.
Message Type: ALERT.

KLVST013

EXTENDED RESERVED MAIN STORAGE UNAVAILABLE
Explanation: Insufficient main storage exists to satisfy the requirements for the
start-up parameter RESERVE(nnn,X). This message refers to above the line
storage.
System Action: CT/Engine terminates.
User Response: Adjust the storage allocation parameters, and retry.
Message Type: ALERT.

KLVST014

INVALID TRACE SPECIFICATION
Explanation: The start-up parameter TRACE is invalid. Possible errors are:
1. The value was less than 2.
2. The value caused the trace table to use more than one half of the free storage
area.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVST015

TRACE TABLE STORAGE UNAVAILABLE
Explanation: Insufficient main storage exists for the allocation of the CT/Engine
internal trace table.
System Action: CT/Engine terminates.
User Response: Increase the MINIMUM parameter, and retry.
Message Type: ALERT.

KLVST016

INVALID EVENT SPECIFICATION
Explanation: The start-up parameter EVENT was invalid. Some possible causes
are:
1. The value was less than 2.
2. The value was greater than one fourth of the free storage area.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVST017

EVENT TABLE STORAGE UNAVAILABLE
Explanation: Insufficient main storage exists for the allocation of the CT/Engine
event hashing table.
System Action: CT/Engine terminates.
User Response: Increase the MINIMUM parameter and retry.
Message Type: ALERT.

KLVSD001–KLXOP005

KLVST018

UNABLE TO OPEN RKLVLOG DATASET
Explanation:
System Action: CT/Engine terminates.
User Response: This message will be accompanied by MVS messages
indicating the reason the dataset could not be opened.
Message Type: ALERT.

KLVST019

UNABLE TO OPEN RKLVSNAP DATASET
Explanation:
System Action: CT/Engine terminates.
User Response: This message will be accompanied by MVS messages
indicating the reason the dataset could not be opened.
Message Type: ALERT.

KLVST020

LIMIT/GRANULE OPTION SPECIFICATION ERROR
Explanation: The value specified for LIMIT was not greater than the value
specified for GRANULE.
System Action: CT/Engine terminates.
User Response: If this error occurs while running CL/SUPERSESSION, correct
LIMIT value and retry. If this error occurs while running any other Candle
product, contact Candle Customer Support.
Message Type: ALERT.

KLVST021

LOG BUFFER STORAGE UNAVAILABLE
Explanation: This error can be caused by either:
1. The start-up parameter MINIMUM is too small; or
2. The start-up parameters LOGBLOCK and LOGBUFS are too large.
System Action: CT/Engine terminates.
User Response: Adjust the appropriate start-up parameters and retry.
Message Type: ALERT.

KLVST022

RKLVLOG DCB STORAGE UNAVAILABLE
Explanation: Insufficient main storage exists for the allocation of the RKLVLOG.
System Action: CT/Engine terminates.
User Response: Adjust the storage allocation parameters and retry.
Message Type: ALERT.

KLVST023

RKLVSNAP DCB STORAGE UNAVAILABLE
Explanation: Insufficient main storage exists for the allocation of the
RKLVSNAP DCB.
System Action: CT/Engine terminates.
User Response: Adjust the storage allocation parameters and retry.
Message Type: ALERT.

Candle Products Messages Manual (KLVHS–KONCT)

KLVST024

FREE STORAGE LIST UNAVAILABLE
Explanation: CT/Engine was unable to allocate the free storage list because the
MINIMUM parameter is too small.
System Action: CT/Engine terminates.
User Response: Adjust the storage allocation parameters and retry.
Message Type: ALERT.

KLVST025

UNABLE TO IDENTIFY SUBTASK ENTRYPOINT
Explanation: The OS IDENTIFY macro issued to identify an entry point to
initialize the CT/Engine dispatcher did not complete successfully.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVST026

modname concat [address] module info
|TRANSIENT |ALREADY RESIDENT |RELOCATION ERROR |BLDL
ERROR [COMMAND=cmd |RESIDENT]| [CLASS=class[,DEFERRED]]
Explanation: During CT/Engine start-up, this message displays the attributes
and status of each module in the CT/Engine load library. Fields of interest are the
module name modname, the relative concatenation number concat, and the
module information field module info. TRANSIENT refers to modules that are not
loaded at this time. DEFERRED refers to modules that are not considered to be
transient but will be loaded at a later time. Any errors detected are also displayed
as ALREADY RESIDENT|RELOCATION ERROR|BLDL ERROR.
System Action: None.
User Response: None, unless error messages ALREADY
RESIDENT|RELOCATION ERROR|BLDL ERROR are displayed. If the cause of
the error cannot be attributed to a user modification, contact Candle Customer
Support.
Message Type: LOG.

KLVST027

REQUIRED POINTER(S) NOT RESOLVED, hex IS THE OFFSET
Explanation: One of the pointers required for CT/Engine execution could not be
resolved, probably due to a module that is missing from the CT/Engine load
library.
System Action: CT/Engine terminates.
User Response: Cross reference all the modules in the execution library with
the modules in the distribution library to determine if a module is missing. If the
error cannot be attributed to an installation error, contact Candle Customer
Support with the hex value.
Message Type: ALERT.

KLVSD001–KLXOP005

KLVST028

LOAD LIBRARY concat volser dsname
Explanation: These messages are logged at start-up time to display the dataset
names and related information associated with the RKANMODL DD statement.
Fields of interest are the concatenation number concat, the volser volser and the
dataset name dsname.
System Action: None.
User Response: None.
Message Type: LOG.

KLVST029

INVALID VALUE FOR SLOPE PARAMETER
Explanation: The SLOPE parameter specified on initialization parameter
SLOPE is invalid.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVST030

UNABLE TO DETERMINE CPU IDENTIFICATION
Explanation: CT/Engine was unable to determine the CPU ID of the machine it
is currently running on.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ALERT.

KLVST032

PERCENTAGE IS INVALID IN QUIESCE PARAMETER
Explanation: A QUIESCE parameter in the file contains an invalid percentage.
The percentage value must be in the range 0–100.
System Action: The message is displayed and initialization fails.
User Response: Correct the QUIESCE parameter in error and restart.
Message Type: ALERT.

KLVST033

STGMON INTERVAL IS INVALID IN STGMON PARAMETER
Explanation: The STGMON interval in the file contains an invalid time interval.
The value should be in the range 0–120.
System Action: The message is displayed and initialization fails.
User Response: Correct the STGMON interval and restart.
Message Type: ALERT.

KLVST034

FREE/CARVED INDICATOR IS INVALID IN QUIESCE PARAMETER
Explanation: A QUIESCE parameter in the KLVSYSIN file contains an invalid
storage type indicator. The value should be either C for carved storage or F for
free storage.
System Action: The message is displayed and initialization fails.
User Response: Correct the QUIESCE parameter in error and restart.
Message Type: ALERT.

100

Candle Products Messages Manual (KLVHS–KONCT)

KLVST035

INSTALLING ADDITIONAL ENTRYPOINT,
|TRANSIENT |ALREADY RESIDENT |RELOCATION ERROR |BLDL
ERROR [COMMAND=cmd |RESIDENT]
Explanation: An additional entry point for the module listed in message
KLVST026, preceding this message, has been processed.
System Action: None.
User Response: Refer to KLVST026.
Message Type: LOG.

KLVST036

AN ELEMENT OF COMPONENT CVT(name) IS module
Explanation: The module module, just processed and identified by the
preceding KLVST026 message, is part of a group of application modules.
System Action: None.
User Response: None.
Message Type: LOG.

KLVST037

COMPONENT
VECTOR TABLE INITIALIZED(name)
|BEGIN VECTORS DIFFER FROM PREVIOUS ELEMENTS
|GSA OFFSET DIFFERS FROM PREVIOUS ELEMENTS
|GSA VECTOR OFFSET USED -ERROR- MODULE ID(name)(module)
|VECTOR TABLE OFFSET ALREADY USED(module)(entry)
|REQUIRED POINTER MISSING FOR CVT(name), AT OFFSET=hex
Explanation: A group of application modules has been successfully initialized
(first message), or an error has been detected (remaining messages).
System Action: For the first message, none. For the remaining messages,
CT/Engine continues processing modules, but will terminate later.
User Response: For the first message, none. For the remaining messages,
contact Candle Customer Support.
Message Type: LOG.

KLVST038

STEPLIB AUTHORIZATION REQUIRED
Explanation: One or more products running in the CT/Engine address space
require the STEPLIB DD to be APF-authorized.
System Action: CT/Engine terminates with a U0012 abend.
User Response: APF-authorize the data sets in the STEPLIB concatenation
and restart CT/Engine.
Message Type: ALERT.

KLVST039

GCSDISKS STORAGE UNAVAILABLE
Explanation: CT/Engine initialization could not obtain storage for the
GCSDISKS keyword.
System Action: CT/Engine terminates with a U0012 abend.
User Response: Adjust the storage allocation parameters and restart
CT/Engine.
Message Type: ALERT.

KLVSD001–KLXOP005

101

KLVST040

WARNING: NO STORAGE FOR SOME LSR HIPERSPACE POOLS
Explanation: A BLDVRP macro was issued to allocate a VSAM local shared
resource buffer pool in Hiperspace, but there was not enough Hiperspace™
storage (BLDVRP returned X’2C’).
System Action: CT/Engine continues, using virtual storage for the buffer
pool(s) that could not be allocated in Hiperspace.
User Response: Refer to IBM’s Macro Instructions for Data Sets for the
BLDVRP return code X’2C’.
Message Type: LOG.

KLVST041

ERROR INITIALIZING SYSMDUMP DATASET
Explanation: An OPEN macro was issued to initialize the SYSMDUMP dataset,
which produced a non-zero return code. Refer to the accompanying IEC141I
message for details on the OPEN failure.
System Action: CT/Engine terminates with a U0012 abend.
User Response: Refer to IBM’s Planning: Problem Determination and
Recovery for details on pre-allocating SYSMDUMP datasets.
Message Type: ALERT.

KLVST042

SPLEVEL NOT MATCHED, ASSUMING assume. SYSTEM SPLEVEL
DETECTED=level
Explanation: CT/Engine was unable to match the SP level of the current
operating system (level) with an entry in its internal table of supported operating
systems.
System Action: CT/Engine assumes the SP level is assume. Execution
continues.
User Response: Contact Candle Customer Support with the contents of this
message.
Message Type: LOG.

KLVST043

UNABLE TO OPEN RKANPAR DATASET
Explanation: An OPEN macro was issued to initialize the RKANPAR dataset,
which produced a non-zero return code. Refer to the accompanying IEC141I
message for details on the OPEN failure.
System Action: CT/Engine terminates with a U0012 abend.
User Response: Correct the problem and restart CT/Engine.
Message Type: ALERT.

KLVST044

LOADLIST MEMBER NOT FOUND IN RKANPAR DATASET
(membername)
Explanation: A FIND macro issued to locate the named LOADLIST member in
the RKANPAR dataset produced a failing return code.
System Action: CT/Engine terminates with a U0012 abend.
User Response: Specify a valid member name and restart CT/Engine.
Message Type: ALERT.

102

Candle Products Messages Manual (KLVHS–KONCT)

KLVTB001

TABLE DATABASE INITIAL LOAD COMPLETE: DSNAME(dsname)
Explanation: During CT/Engine table initialization, the tables database
(dsname) was found to be unformatted.
System Action: The database is formatted for tables processing.
User Response: None.
Message Type: INFO.

KLVTB002

TABLE DATABASE dsname INITIAL LOAD date time ON sysid LAST
ACCESSED date time ON sysid
Explanation: CT/Engine table initialization has successfully opened the tables
database (dsname). The date, time, and SMF system ID when the database was
initially formatted by CT/Engine, and the last date, time and SMF system ID when
the database was last accessed by CT/Engine are also reported.
System Action: None.
User Response: None.
Message Type: INFO.

KLVTB003

UNABLE TO ALLOCATE TABLE CLUSTER: DSNAME(dsname)
Explanation: CT/Engine table initialization could not allocate the tables
database (dsname).
System Action: CT/Engine initialization is terminated.
User Response: Examine the MVS console log or the CT/Engine RKLVLOG
for KLVDAnnn messages, which will explain the allocation problem. Correct the
error, then restart CT/Engine.
Message Type: ERROR.

KLVTB004

keyword: ‘errormessage’ RKANPAR(KLVINTB)
Explanation: The table initialization member (KLVINTB in RKANPAR) has an
invalid keyword keyword in it.
System Action: CT/Engine initialization is terminated.
User Response: Examine errormessage and member KLVINTB in RKANPAR
for specific information about the error, and correct it.
Message Type: ERROR.

KLVTB005

UNABLE TO OPEN TABLE CLUSTER: DSNAME(dsname)
DDNAME(ddname) R15(r15) ACBERFLG(erflg)
Explanation: CT/Engine tables initialization was unable to open the tables
database (dsname) allocated to ddname.
System Action: CT/Engine initialization is terminated.
User Response: Refer to IBM’s Macro Instructions for Data Sets for the
meaning of r15 and erflg for OPEN errors. Correct the problem and restart
CT/Engine.
Message Type: ERROR.

KLVSD001–KLXOP005

103

KLVTB006

NO LSR POOL ALLOCATED
Explanation: CT/Engine tables initialization was unable to process the tables
database because no VSAM LSR environment was established.
System Action: CT/Engine initialization is terminated.
User Response: Examine the MVS console log or the CT/Engine RKLVLOG
for KLVVSnnn messages, which will explain the VSAM problem. Correct the error,
then restart CT/Engine.
Message Type: ERROR.

KLVTB007

UNABLE TO ACCESS TABLE CLUSTER
Explanation: CT/Engine tables initialization was unable to process the tables
database because it could not establish a VSAM request against the cluster.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, and the MVS
system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB008

UNABLE TO READ TABLE DATABASE CONTROL RECORD
Explanation: CT/Engine tables initialization could not read information it needs
to process the tables database.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, and the MVS
system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB009

UNABLE TO WRITE TABLE DATABASE CONTROL RECORD
Explanation: CT/Engine tables initialization could not update the tables
database.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, and the MVS
system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB010

SHOWCB FIELDS = (ACBLEN,RPLLEN) ERROR: R15(r15) R0(r0)
Explanation: CT/Engine tables initialization could not format the tables
database because the VSAM SHOWCB macro failed.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB011

UNABLE TO INITIALIZE TABLE CLUSTER DSNAME(dsname) R15(value)
DCR(hex)
Explanation: CT/Engine tables initialization could not format the tables
database because the VSAM OPEN macro failed.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log, then contact Candle Customer Support.
Message Type: ERROR.

104

Candle Products Messages Manual (KLVHS–KONCT)

KLVTB012

UNABLE TO LOAD TABLE CLUSTER: DSNAME(dsname) R15(value)
RPLERRCD(value) DCR(hex)
Explanation: CT/Engine tables initialization could not format the tables
database because the VSAM PUT macro failed.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB013

GENCB MACRO FAILURE R15(value) R0(value)
Explanation: CT/Engine tables initialization could not format the tables
database because the VSAM GENCB macro failed.
System Action: CT/Engine initialization is terminated.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB014

INVALID KEY LENGTH IN TABLE DATABASE: SUPPLIED(actual)
EXPECTED(valid)
Explanation: The CT/Engine tables database is incorrectly allocated. valid is the
required VSAM cluster key length; actual is the key length found on the actual
cluster.
System Action: CT/Engine initialization is terminated.
User Response: Reallocate the tables database cluster with the proper key and
control interval sizes, then restart CT/Engine.
Message Type: ERROR.

KLVTB015

INVALID RECORD LENGTH IN TABLE DATABASE: SUPPLIED(actual)
EXPECTED(valid)
Explanation: The CT/Engine tables database is incorrectly allocated. valid is the
minimum VSAM cluster record length; actual is the record length found on the
cluster.
System Action: CT/Engine initialization is terminated.
User Response: Reallocate the tables database cluster with the proper key and
control interval sizes, then restart CT/Engine.
Message Type: ERROR.

KLVTB016

NO TABLE DATABASE SPECIFIED - PERMANENT TABLES NOT
SUPPORTED
Explanation: The CT/Engine initialization member (KLVINTB in RKANPAR) is
either not present or is empty.
System Action: CT/Engine initialization continues, but no permanent table
services are available. These include TBOPEN, TBSAVE, and TBLIST. Attempts
to use these will result in return codes of 8, 12 and/or 20 from the associated
functions.

KLVSD001–KLXOP005

105

User Response: If permanent table services are desired, allocate a tables
database, create or update the KLVINTB member in RKANPAR, then restart
CT/Engine.
Message Type: WARNING.
KLVTB017

keyword(value) IS OUT OF RANGE (min-max); DEFAULTS TO def
Explanation: keyword in the KLVINTB 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.

KLVTB018

MINIMUM/MAXIMUM TUBPOOL CONFLICT; MAXIMUM SET TO val
Explanation: The MINIMUMTUBPOOL value in the KLVINTB member of
RKANPAR is not less than the MAXIMUMTUBPOOL value.
System Action: The MINIMUMTUBPOOL value, plus 8, will be used (val).
CT/Engine initialization continues.
User Response: Correct the MINIMUMTUBPOOL or MAXIMUMTUBPOOL
value. If the default value is unacceptable, recycle CT/Engine.
Message Type: WARNING.

KLVTB019

keyword(value) IS INVALID; DEFAULTS TO def
Explanation: keyword in the KLVINTB 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.

KLVTB020

TABLE ERASE FAILED, RC=rc
Explanation: An internal request to remove a permanent table from the tables
database was not successful.
System Action: The request terminates.
User Response: Contact Candle Customer Support.
Message Type: REPLY.

KLVTB020

TABLE ERASED
Explanation: An internal request to remove a permanent table from the tables
database was successful.
System Action: None.
User Response: None.
Message Type: REPLY.

106

Candle Products Messages Manual (KLVHS–KONCT)

KLVTB021

TABLE CONVERTED: table
Explanation: The TDB CONVERT command has successfully converted table
from Version 145 format to Version 146 format.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTB022

UNABLE TO ALLOCATE TABLE CLUSTER: DSNAME(dsname)
Explanation: The TDB CONVERT command could not allocate the Version
145 tables database.
System Action: The TDB CONVERT command ends.
User Response: Examine the MVS console log or the CT/Engine RKLVLOG
for KLVDAnnn messages, which will explain the allocation problem. Correct the
error, then reissue the TDB CONVERT command.
Message Type: WARNING.

KLVTB023

keyword: ‘errormessage’ COMMAND(TDB)
Explanation: The TDB command was issued with an invalid keyword keyword.
System Action: The TDB command ends.
User Response: Examine errormessage for specific information about the error
and correct it.
Message Type: ERROR.

KLVTB024

UNABLE TO OPEN TABLE CLUSTER: DSNAME(dsname)
DDNAME(ddname) R15(r15) ACBERFLG(erflg)
Explanation: The TDB CONVERT command could not open the Version 145
tables database (dsname) allocated to ddname.
System Action: The TDB CONVERT command ends.
User Response: Refer to IBM’s Macro Instructions for Data Sets for the
meaning of r15 and erflg for OPEN errors. Correct the problem and reissue the
TDB CONVERT command.
Message Type: ERROR.

KLVTB025

UNABLE TO INITIALIZE DIALOG MANAGER
Explanation: The TDB CONVERT command could not initialize the dialog
services function of CT/Engine for its processing.
System Action: The TDB CONVERT command ends.
User Response: Retain the CT/Engine run sheets and dump files, as well as the
MVS system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVTB026

UNABLE TO ACCESS TABLE CLUSTER
Explanation: The TDB CONVERT command could not OPEN the Version 145
tables database for processing.
System Action: The TDB CONVERT command ends.
User Response: Retain the CT/Engine run sheets and dump files, as well as the
MVS system log, then contact Candle Customer Support.
Message Type: ERROR.

KLVSD001–KLXOP005

107

KLVTB027

INVALID KEY LENGTH IN TABLE DATABASE: SUPPLIED(actual)
EXPECTED(valid)
Explanation: The Version 145 tables database specified on a TDB CONVERT
command does not have the correct key length (valid).
System Action: The TDB CONVERT command ends.
User Response: Reissue the TDB CONVERT command with the correct Basic
Table Services tables database VSAM cluster name.
Message Type: ERROR.

KLVTB028

INVALID SUBCOMMAND: keyword
Explanation: An invalid request (keyword) was made on the TDB command.
System Action: The TDB command ends.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVTB029

action TABLE REQUEST FAILED: RC(rc) TABLE(table)
Explanation: The tables service function action against table failed with the
indicated return code.
System Action: The TDB CONVERT command ends.
User Response: Some tables may have been successfully converted; refer to
CT/Engine RKLVLOG for KLVTB021 messages. Retain the CT/Engine run sheets
and dump files, this message, and the MVS system log, then contact Candle
Customer Support.
Message Type: ERROR.

KLVTB030

REQUEST FAILED - TABLE(table)
Explanation: An internal tables request failed.
System Action: The request terminates.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVTB031

BLOCK ERROR: TABLE(table) SEQUENCE(nnn) RECORD(hex)
Explanation: While processing a tables request, the CT/Engine tables manager
detected an invalid block in the tables database for table. nnn is the record
sequence number for the table that contains the block. hex is the block that was in
error, followed by the remainder of the VSAM record.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035), or will use the partially loaded table
(message KLVTB034).
User Response: None.
Message Type: LOG.

108

Candle Products Messages Manual (KLVHS–KONCT)

KLVTB032

SORT ERROR: TABLE(table)
Explanation: While processing a tables request, the CT/Engine tables manager
detected invalid sort information in the tables database for table.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035), or will use the partially loaded table
(message KLVTB034).
User Response: None.
Message Type: LOG.

KLVTB033

ROW ERROR: TABLE(table) READ(mmm) EXPECTED(nnn)
Explanation: While processing a tables request, the CT/Engine tables manager
detected a structural error in the tables database for table. mmm is the number of
rows successfully processed; nnn is the number of rows that were expected.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035), or will use the partially loaded table
(message KLVTB034).
User Response: None.
Message Type: LOG.

KLVTB034

RECOVERED [OLDER COPY] [WITH DATA ERRORS]: TABLE(table)
Explanation: While processing a tables request, the CT/Engine tables manager
detected an error in the tables database for table. If the recovery was performed
by loading an older copy of the table, the phrase OLDER COPY appears. If not
all of the data in the table could be recovered, the phrase WITH DATA
ERRORS appears. Previous KLVTB0nn message(s) should be present that
describe the original error.
Note: This error may occur when the table was not completely written to the
database at some earlier point, or when a VSAM I/O error occurs while
reading the table.
System Action: The request continues as if no error had occurred.
User Response: None.
Message Type: LOG.

KLVTB035

RECOVERING OLDER COPY: TABLE(table)
Explanation: While processing a tables request, the CT/Engine tables manager
detected an error in the tables database for table and will attempt to recover using
an earlier version of the table. Previous KLVTB0nn messages should be present
that describe the original error.
System Action: The invalid table is erased from the tables database to prevent
any future errors, and the request is retried with the earlier version of the table.
User Response: None.
Message Type: LOG.

KLVSD001–KLXOP005

109

KLVTB036

RECOVERY FAILED: TABLE(table)
Explanation: While processing a tables request, the CT/Engine tables manager
detected an error in the tables database for table. If there was an older copy of the
table on the database, the tables manager attempted to recover it, but that copy
also had errors. These errors were severe enough that no usable information
could be recovered. Previous KLVTB0nn messages should be present that
describe the original error.
System Action: The request is terminated with a nonzero return code. The
invalid table remains on the database.
User Response: Retain the CT/Engine run sheets, dump files, this message, the
MVS system log, and a copy of your tables database, then contact Candle
Customer Support. You must recreate the table and save it to the database after
the diagnostic information is obtained.
Message Type: LOG.

KLVTB037

WRITE ERROR: TABLE(table) RPLFDBWD(feedback) SEQUENCE(nnn)
RECORD(hex)
Explanation: The CT/Engine tables manager received a VSAM error while
updating the tables database for table. feedback is the RPL feedback word from
the failing request. nnn is the record sequence number for the table that was being
written. hex is the VSAM record contents.
System Action: The request is terminated with a nonzero return code. The
table remains open.
User Response: Refer to IBM’s Macro Instructions for Data Sets manual for the
meaning of the values in feedback. If the problem is not apparent, retain the
CT/Engine run sheets, dump files, this message, the MVS system log, and a copy
of your tables database, then contact Candle Customer Support.
Message Type: LOG.

KLVTB038

SYNC ERROR: TABLE(table) EXPECTED(edata) ACTUAL(adata)
SEQUENCE(nnn) RECORD(hex)
Explanation: While processing a tables request, the CT/Engine tables manager
detected invalid synchronization information in the tables database for table. A
VSAM record has been read that is not part of the table being loaded. edata is the
expected sync value; adata is the actual data read. nnn is the record sequence
number for the table that contains the block. hex is the block that was in error,
followed by the remainder of the VSAM record.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035), or will use the partially loaded table
(message KLVTB034).
User Response: None.
Message Type: LOG.

110

Candle Products Messages Manual (KLVHS–KONCT)

KLVTB039

ROW-END ERROR: TABLE(table) READ(mmm) EXPECTED(nnn)
Explanation: While processing a tables request, the CT/Engine tables manager
detected invalid synchronization information in the tables database for table. An
internal end-of-row marker is missing. mmm is the number of rows successfully
processed; nnn is the number of rows that were expected.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035), or will use the partially loaded table
(message KLVTB034).
User Response: None.
Message Type: LOG.

KLVTB040

KLVTBMGR LOGIC ERROR
Explanation: 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.

KLVTB041

KLVTBMGR INVALID TABLE DELETE POINTER
Explanation: 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.

KLVTB042

FREE $TUB INTEGRITY CHECK FAILED
Explanation: The CT/Engine tables manager detected a problem with an
internal control block 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.

KLVTB043

UNSUPPORTED/INVALID $DMTB REQUEST RECEIVED
Explanation: The CT/Engine tables 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: REPLY.

KLVSD001–KLXOP005

111

KLVTB045

RESIDUAL RECORD DELETED: TABLE(table) SEQUENCE(nnn)
Explanation: The CT/Engine tables manager detected an error while writing
table to the tables database. Data from an older copy of the table was not
completely removed during an earlier save request. nnn is the record sequence
number of the invalid data record for table.
System Action: The tables manager deletes the old, invalid records and
continues saving table. This message is issued for each record that is deleted.
User Response: None.
Message Type: LOG.

KLVTB046

CHAINING ERROR: TABLE(table) SEQUENCE(nnn) RECORD(hex)
Explanation: The CT/Engine tables manager detected an error while reading
the tables database for table. A block that spans multiple VSAM records is not
correct. nnn is the record sequence number for the table that contains the block.
hex is the block that was in error, followed by the remainder of the VSAM record.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035), or will use the partially loaded table
(message KLVTB034).
User Response: None.
Message Type: LOG.

KLVTB047

UNEXPECTED FIELD: TABLE(table) SEQUENCE(nnn) RECORD(hex)
Explanation: The CT/Engine tables manager detected an error while reading
the tables database for table. Too many variable names or sort fields have been
processed. nnn is the record sequence number for the table that contains the
block. hex is the block that was in error, followed by the remainder of the VSAM
record.
System Action: The tables manager will attempt to load a previous copy of the
table, if one exists (message KLVTB035). If there is no alternate table, message
KLVTB036 will be issued and the request terminated with a nonzero return code.
User Response: Refer to message KLVTB036.
Message Type: LOG.

KLVTB048

INVALID ERASE REQUEST DETECTED
Explanation: The CT/Engine tables manager detected an error before erasing a
record from the tables data base.
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: REPLY.

112

Candle Products Messages Manual (KLVHS–KONCT)

KLVTB049

INVALID RLB CHAIN DETECTED
Explanation: The CT/Engine tables manager detected an error while attempting
to lock a row from the tables data base.
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, and this
message, then contact Candle Customer Support.
Message Type: REPLY.

KLVTB051

UNSUPPORTED/INVALID $TBHLP REQUEST RECEIVED
Explanation: The CT/Engine tables 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: REPLY.

KLVTB052

KLVINTB RKANPAR PARAMETERS:
Explanation: Module KLVINTB logs its startup parameters as they are read from
RKANPAR. This is the header message and will be followed by message
KLVTB053.
System Action: None.
User Response: None.
Message Type: LOG.

KLVTB053

parameters
Explanation: As the parameters in module KLVINTB are read, a log audit trail is
created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVTI001

CANDLE ENGINE TIME: time
Explanation: The TIME command causes the CT/Engine time to be displayed.
Explanation: None.
User Response: None.
Message Type: REPLY.

KLVTI002

CANDLE ENGINE TIME RESET TO: time DATE: date
Explanation: The TIME RESET command has set the CT/Engine time and date
to the system local time and date shown.
System Action: None.
User Response: None.
Message Type: REPLY, VIEW

KLVSD001–KLXOP005

113

KLVTI201

INVALID $STMX REQUEST DETECTED
Explanation: A CT/Engine timing service has been passed invalid information.
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

KLVTQ101

CHANGE OF DAY PROCESSING COMPLETE: DATE date
Explanation: The CT/Engine timing services routine needed to adjust its queue
due to a day change.
System Action: None.
User Response: None.
Message Type: INFO.

KLVTQ102

INVALID $TRB DETECTED. $TRB ADDR(addr) $TRTIME(time)
$TRJDATE(jdate) $TRENTRY(entry) $TRPARM(parm) $TRASSOC(assoc)
$TRINTVL(intvl) ASSOCVAL(assocval)
Explanation: During the processing of an expired timer interval it was
determined that the $TRB had an invalid association vector. addr is the address of
the $TRB. time and jdate are the date and time that the timer request was
initiated. entry is the address of the exit routine. parm is the parameter to be
passed to the exit routine. assoc is the address of the association vector and intvl is
the length of the interval that this $TRB represents. assocval is the contents of the
association vector. assocval will be ******** if assoc is an invalid address.
System Action: The $TRB is freed, the $STMR exit routine is not run, and
processing continues.
User Response: Contact Candle Customer Support.
Message Type: LOG, VIEW.

KLVTR001

INTERNAL TRACE STATUS:
Explanation: The title for the INTERNAL TRACE STATUS display. The TRACE
command displays the current trace table eligibility mask.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR002

INVALID TRACE ID: ‘arg’
Explanation: The TRACE command contains an invalid parameter arg.
System Action: The command fails.
User Response: Validate and correct the trace id arg, and reissue the
command.
Message Type: ERROR.

114

Candle Products Messages Manual (KLVHS–KONCT)

KLVTR003

INVALID PREFIX CHARACTER: ‘arg’
Explanation: The TRACE command contains an invalid prefix character arg as
one of the parameters.
System Action: The command fails.
User Response: Correct the invalid prefix character (it must be (+) or (-)) and
reissue the command.
Message Type: ERROR.

KLVTR004

INTERNAL TRACE FACILITY DISABLED
Explanation: The TRACE command failed because the internal trace facility has
been disabled.
System Action: The command fails.
Message Type: ERROR.

KLVTR005

class arg
Explanation: class is the trace class being reported. arg is ENABLED OR
DISABLED.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR006

PRODUCT TRACE STATUS
Explanation: The title line for the PRODUCT TRACE STATUS displays.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR007

pr ENABLED
Explanation: pr
System Action:
User Response:
Message Type:

is a two character product id that is enabled for tracing.
None.
None.
REPLY.

KLVTR008

*** END OF DATA ***
Explanation: The end of the TRACE STATUS display.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR021

KLVSD001–KLXOP005

115

KLVTR022

TRACE REQUEST REJECTED. INVALID CLASS(class) SPECIFIED
Explanation: An invalid CLASS was specified. class is the class type specified.
System Action: The trace request is rejected.
User Response: Specify a correct CLASS and reissue the command.
Message Type: ERROR.

KLVTR023

KLVTR024

TRACE TERM|ACB(resname) QUEUED|ENABLED|DISABLED
Explanation: The trace request for resname of TERM or ACB has been
performed.
System Action: None.
User Response: None.
Message Type: ERROR.

KLVTR025

KLVTR026

KLVTR027

TRACE CLASS(INT|TERM|ACB) STATUS:
Explanation: This is the header message of the trace status display.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR028

116

Candle Products Messages Manual (KLVHS–KONCT)

KLVTR029

class: stat
Explanation: This message displays the status of internal trace class class. stat is
its status.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR031

type(res) : stat
Explanation: This message displays the status of resource res. type is the
resource type and stat is its status.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTR032

*** END OF TRACE STATUS ***
Explanation: This message marks the end of a section of trace status data.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVTS000

INVALID $CTMR REQUEST
Explanation: CT/Engine encountered a problem during timer services
processing.
System Action: CT/Engine terminates.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVTS001

TIMER ALREADY CANCELLED
Explanation: An attempt was made to cancel a timer request that had already
been cancelled.
System Action: The thread is terminated.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVTS011

TIMER ASSOCIATION VECTOR REUSE
Explanation: An attempt was made to create a timer request and the contents of
the supplied association vector referenced a currently active timer request.
System Action: The thread is terminated.
User Response: Contact Candle Customer Support.
Message Type: ABEND.

KLVUX000

INVALID USE OF KLV$$GBL BY A USEREXIT
Explanation: Proper linkage has not been established for the user exit.
System Action: For problem determination, a dump is generated with a user
abend code.
User Response: Review the user exit and make any necessary corrections.
Message Type: REPLY.

KLVSD001–KLXOP005

117

KLVVL001

VSAM SERVICES NOT AVAILABLE FOR VIEWLOG
Explanation: VIEWLOG requires VSAM support, but the CT/Engine VSAM
services routine did not initialize.
System Action: VIEWLOG initialization ends. VIEWLOG processing is not
available. CT/Engine initialization continues.
User Response: Review RKLVLOG for KLVVSnnn messages that will identify
the VSAM problem. Correct it and restart CT/Engine.
Message Type: WARNING.

KLVVL002

UNABLE TO ALLOCATE VIEWLOG CLUSTER: DSNAME(dsname)
Explanation: An unsuccessful attempt was made to dynamically allocate the
VIEWLOG cluster.
System Action: The VIEWLOG command is unavailable.
User Response: Look for dynamic allocation error messages (KLVDAnnn) to
determine a more specific reason the dataset could not be allocated, and take
appropriate corrective action.
Message Type: WARNING.

KLVVL003

VIEWLOG CLUSTER INITIALIZED: DSNAME dsn
Explanation: The VIEWLOG cluster dsn has been successfully initialized. This
message is logged to create an audit trail.
System Action: None.
User Response: None.
Message Type: INFO.

KLVVL004

UNABLE TO REOPEN VIEWLOG CLUSTER
Explanation: During CT/Engine startup, an unsuccessful attempt was made to
reopen the VIEWLOG cluster under LSR. This is done to get control interval
access to the cluster in order to initialize the VIEWLOG environment. An error
was made defining the VIEWLOG environment.
System Action: The VIEWLOG command is unavailable.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

KLVVL005

UNABLE TO LOGON *SYSVLG* FOR VIEWLOG
Explanation: The operator *SYSVLG* could not be defined.
System Action: The VIEWLOG command is unavailable.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

KLVVL006

SHOWCB FIELDS=(ACBLEN,RPLLEN) ERROR: R15(r15) R0(r0)
Explanation: A SHOWCB macro instruction issued to obtain the length of a
VSAM ACB completed unsuccessfully.
System Action: The VIEWLOG command is unavailable.
User Response: Use the appropriate VSAM programmer’s reference and the r0
and r15 fields to determine the cause of the error and take appropriate corrective
action.
Message Type: WARNING.

118

Candle Products Messages Manual (KLVHS–KONCT)

KLVVL007

SHOWCB FIELDS=RPLLEN ERROR: R15(r15) R0(r0)
Explanation: A SHOWCB macro instruction issued to obtain the length of a
VSAM RPL completed unsuccessfully.
System Action: The VIEWLOG command is unavailable.
User Response: Use the appropriate VSAM programmer’s reference and the r0
and r15 fields to determine the cause of the error and take appropriate corrective
action.
Message Type: WARNING.

KLVVL008

GENCB BLK=ACB ERROR: R15(r15) R0(r0)
Explanation: A GENCB macro instruction was issued to generate a VSAM ACB
and completed unsuccessfully.
System Action: The VIEWLOG command is unavailable.
User Response: Use the appropriate VSAM programmer’s reference and the r0
and r15 fields to determine the cause of the error and take appropriate corrective
action.
Message Type: WARNING.

KLVVL009

GENCB BLK=RPL ERROR: R15(r15) R0(r0)
Explanation: A GENCB macro instruction was issued to generate a VSAM RPL
and completed unsuccessfully.
System Action: The VIEWLOG command is unavailable.
User Response: Use the appropriate VSAM programmer’s reference and the r0
and r15 fields to determine the cause of the error and take appropriate corrective
action.
Message Type: WARNING.

KLVVL010

UNABLE TO OPEN VIEWLOG CLUSTER: DSNAME(dsn)
DDNAME(ddname) R15(r15) ACBERFLG(acberflg)
Explanation: During CT/Engine startup, an unsuccessful attempt was made to
open the VIEWLOG cluster dsn. The cluster was probably defined improperly.
System Action: The VIEWLOG command is unavailable.
User Response: Use the appropriate VSAM programmer’s reference and the
r15 and acberflg fields to determine the cause of the error and take appropriate
corrective action.
Message Type: WARNING.

KLVVL011

UNABLE TO LOAD VIEWLOG CLUSTER: R15(r15) R0(r0)
Explanation: An unsuccessful attempt was made to PUT an initial record to the
VIEWLOG cluster. The cluster was probably defined improperly.
System Action: The VIEWLOG command is unavailable.
User Response: Use the appropriate VSAM programmer’s reference and the r0
and r15 fields to determine the cause of the error and take appropriate corrective
action.
Message Type: WARNING.

KLVSD001–KLXOP005

119

KLVVL012

DISP(value) IS INVALID; DEFAULTS TO OLD
Explanation: An invalid value was coded on the DISP keyword in the
KLVINVLG member of RKANPAR.
System Action: DISP(OLD) will be used. VIEWLOG and CT/Engine
initialization continues.
User Response: Correct the keyword value. If the default value is
unacceptable, recycle CT/Engine.
Message Type: WARNING.

KLVVL013

RKANPAR(KLVINVLG) IS EMPTY
Explanation: The VIEWLOG initialization member, KLVINVLG, in RKANPAR is
either not present or contains no statements.
System Action: VIEWLOG initialization ends. VIEWLOG processing is not
available. CT/Engine initialization continues.
User Response: Create a valid KLVINVLG member and recycle CT/Engine.
Message Type: WARNING.

KLVVL014

DSNAME OR DDNAME IS REQUIRED FOR VIEWLOG
Explanation: The KLVINVLG member of RKANPAR does not have a data set
and/or DD name coded.
System Action: VIEWLOG initialization ends. VIEWLOG processing is not
available. CT/Engine initialization continues.
User Response: Modify the KLVINVLG member to specify a data set and/or
DD name, then recycle CT/Engine.
Message Type: WARNING.

KLVVL015

VIEWLOG DSNAME RETRIEVAL FAILED, RC(rc) ERROR(error) INFO(info)
DDNAME(ddn)
Explanation: During VIEWLOG initialization, an attempt to determine the data
set name associated with DD ddn failed. The MVS DYNALLOC function gave
with the indicated return, error, and info codes.
System Action: VIEWLOG initialization ends. VIEWLOG processing is not
available. CT/Engine initialization continues.
User Response: Consult the IBM manual Authorized Assembler Programming
Reference to determine the reason DYNALLOC failed.
Message Type: WARNING.

KLVVL016

KLVINVLG RKANPAR PARAMETERS:
Explanation: Module KLVINVLG logs its startup parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVVL017.
System Action: None.
User Response: None.
Message Type: LOG.

120

Candle Products Messages Manual (KLVHS–KONCT)

KLVVL017

parameters
Explanation: As the parameters in module KLVINVLG are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVM001

CT/Engine IS NOT ACTIVE
Explanation: This message is issued by the CT/Engine command interpreter
which is a VM extension. This indicates that the command interpreter has been
loaded but the CT/Engine has not initialized sufficiently for commands to be
forwarded to the CT/Engine.
System Action: The command issued is discarded.
User Response: Wait and retry the command.
Message Type: INFO.

KLVVM002

CT/Engine NOT COMPLETELY INITIALIZED YET
Explanation: This message is issued by the CT/Engine command interpreter
which is a VM extension. This indicates that CT/Engine is not yet, or no longer,
servicing requests.
System Action: The command issued is discarded.
User Response:
1. If this occurs during startup, wait and retry the command.
2. If this occurs after shutdown, the CT/Engine-based product must be restarted
before commands may be issued.
Message Type: INFO.

KLVVP000

VIRTUAL PRINTER MANAGER INITIALIZED, VPRINTER VECTOR: addr
Explanation: VPRINTER has been initialized. The vector address is addr.
System Action: None.
User Response: None.
Message Type: INFO.

KLVVP011

"FORM" MAY ONLY BE SPECIFIED IN THE MVS VERSION OF THE
PRODUCT
Explanation: "FORM" is not a valid VPRINTER parameter for the VM version of
the product.
System Action: The command is rejected and the VPRINTER is not started.
User Response: Review the command and reissue.
Message Type: ERROR.

KLVVP012

"USER" MAY ONLY BE SPECIFIED IN THE MVS VERSION OF THE
PRODUCT
Explanation: "USER" is not a valid VPRINTER parameter for the VM version of
the product.
System Action: The command is rejected and the VPRINTER is not started.
User Response: Review the command and reissue.
Message Type: ERROR.

KLVSD001–KLXOP005

121

KLVVP013

"TAG" MAY ONLY BE SPECIFIED IN THE VM VERSION OF THE
PRODUCT
Explanation: "TAG" is not a valid VPRINTER parameter for the MVS version of
the product.
System Action: The command is rejected and the VPRINTER is not started.
User Response: Review the command and reissue.
Message Type: ERROR.

KLVVP014

FFEED OPTION -xxxxxxxx- INVALID
Explanation: The specified formfeed option is invalid.
System Action: The command is rejected and the VPRINTER is not started.
User Response: Review the command and reissue.
Message Type: ERROR.

KLVVP015

MAXLINE PARAMETER NOT IN RANGE(1–255)
Explanation: The line length for SYSOUT data must be 1–255 characters.
System Action: The command is rejected and the VPRINTER is not started.
User Response: Specify a MAXLINE value between 1–255.
Message Type: ERROR.

KLVVP016

SYSOUT MUST BE SPECIFIED WITH THE FOLLOWING OPTIONS:
FFEED(IF)-, FFEED(FIRST)-, FFEED(NONE), IGNEOM-, XSEGLINE-,
NOTRUNC-.
Explanation: A VPRINTER option only valid for a SYSOUT VPRINTER was
specified for a VPRINTER that was not a SYSOUT VPRINTER.
System Action: The command is rejected and the VPRINTER is not started.
User Response: Review the command and reissue.
Message Type: ERROR.

KLVVP017

UNABLE TO ALLOCATE VPRINTER ACB: APPLID(appl)
Explanation: CT/Engine was unable to allocate the appl specified in the
VPRINTER command.
System Action: The command fails and the VPRINTER is not started.
User Response: Contact Candle Customer Support.
Message Type: ERROR.

KLVVP018

UNABLE TO OPEN VPRINTER ACB: APPLID(appl) REASON (rc)
Explanation: CT/Engine was unable to OPEN the appl specified in the
VPRINTER.
System Action: The command fails and the VPRINTER is not started.
User Response: The REASON field contains the return code rc 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.

122

Candle Products Messages Manual (KLVHS–KONCT)

KLVVP019

VPRINTER APPLICATION appl STARTED: PHYSPRT (printer)
Explanation: Application appl with physical printer printer was successfully
started by the VPRINTER command.
System Action: None.
User Response: None.
Message Type: INFO, REPLY.

KLVVP020

VPRINTER APPLICATION appl STOPPED: PHYSPRT (printer)
Explanation: Application appl with physical printer printer was successfully
stopped by the VPRINTER command.
System Action: None.
User Response: None.
Message Type: INFO, REPLY.

KLVVP021

ERROR RECONCILING CURRENT SESSION WITH VPRINTER REQUEST
CHAIN. REQUEST=request
Explanation: An error was encountered while processing the VPRINTER
request list.
System Action: This VPRINTER application continues normally.
User Response: Contact Candle Customer Support.
Message Type: INFO.

KLVVP022

COULD NOT ESTABLISH VPRINTER LOGON FOR session
Explanation: session could not establish a session with the VPRINTER because
the request could not be added to the VPRINTER request list.
System Action: The session is not added to the VPRINTER request list.
User Response: Contact Candle Customer Support.
Message Type: INFO.

KLVVP023

SYSOUT CLOSE FAILED FOR VPRINTER APPLICATION appl
Explanation: The MVS data management CLOSE operation used by the
VPRINTER application failed.
System Action: This VPRINTER application continues normally.
User Response: Perform the following steps:
1. Issue the CT/Engine CLOSE command for the VPRINTER ACB to stop the
application.
2. Examine the MVS SYSLOG for messages that indicate the reason for the
failure.
3. Correct the error and re-issue the CT/Engine VPRINTER command to restart
the application.
Message Type: INFO.

KLVSD001–KLXOP005

123

KLVVP031

ERROR RECONCILING CURRENT SESSION WITH VPRINTER REQUEST
CHAIN. REQUEST=request
Explanation: An error was encountered while processing the VPRINTER
request list.
System Action: The data sent from the application is rejected.
User Response: Contact Candle Customer Support.
Message Type: INFO.

KLVVP032

KLVVP033

KLVVP034

VPRINTER SEND TO PHYSICAL PRINTER aaaa/pppp FAILED,
SENSE(ssss)
Explanation: VPRINTER send to physical printer failed, where aaaa is the name
of the physical printer application, pppp is the name of the physical printer, and
ssss is the sense code data.
System Action: VPRINTER session aborted.
User Response: Retry request.
Message Type: INFO.

KLVVP035

RETRY LIMIT REACHED. VPRINTER APPLICATION applid
PHYSPRT(name) CLOSE IN PROGRESS
Explanation: The VPRINTER applid has reached its retry limit having failed to
acquire name within the specified number of attempts.
System Action: The VPRINTER is closed.
User Response: None.
Message Type: INFO, REPLY.

124

Candle Products Messages Manual (KLVHS–KONCT)

KLVVP036

SYSOUT OPEN FAILED FOR VPRINTER APPLICATION appl
Explanation: The VPRINTER application was unable to obtain a SYSOUT
dataset because of a dynamic allocation or OPEN failure.
System Action: This VPRINTER application hangs.
User Response: Perform the following steps:
1. Issue the CT/Engine CLOSE command for the VPRINTER ACB to stop the
application.
2. Examine the MVS SYSLOG for messages that indicate the reason for the
failure.
3. Correct the error and re-issue the CT/Engine VPRINTER command to restart
the application.
Message Type: ALERT.

KLVVP037

PENDING OUTBOUND MESSAGE LIMIT EXCEEDED. PRINTER(luname).
VIRTUAL SESSION LU(luname) CANCELLED.
Explanation: CT/Engine has been notified that the pending outbound message
limit is exceeded for a physical printer session.
System Action: The current VPRINTER session/user is cancelled. VPRINTER
will be unavailable until all pending messages on that physical printer are
processed or cleared.
User Response: Process or clear all pending messages for the physical printer.
Message Type: ALERT.

KLVVP038

PHYSICAL PRINT CONNECTION LOST, PRINT REQUEST request
INTERRUPTED
Explanation: Printing to the VPRINTER by request request has been
interrupted. The printer was likely allocated by another application via RELEASE
REQUEST.
System Action: The current request will attempt to re-allocate the printer.
Output from request will likely be interleaved with output from the other
application.
User Response: None.
Message Type: INFO.

KLVVP051

SYSOUT I/O FAILED FOR VPRINTER ECB=ecb appl
Explanation: The BSAM WRITE/CHECK operation to the SYSOUT dataset did
not complete successfully.
System Action: This VPRINTER application hangs.
User Response: Perform the following steps:
1. Issue the CT/Engine CLOSE command for the VPRINTER ACB to stop the
application.
2. Examine the MVS SYSLOG for messages that indicate the reason for the
failure.
3. Correct the error and re-issue the CT/Engine VPRINTER command to restart
the application.
Message Type: ALERT.

KLVSD001–KLXOP005

125

KLVVP201

VPO TERMINATED
Explanation: The VPO facility has terminated.
System Action: The facility is no longer available.
User Response: None.
Message Type: INFO.

KLVVP202

VPO TERMINATING
Explanation: The VPO facility is in the process of terminating.
System Action: The facility is no longer available.
User Response: None.
Message Type: INFO.

KLVVP300

VPRINTER: vprt -> PHYSICAL PRINTER: pprt
Explanation: A VPRINTQ command was issued. vprt is the VPRINTER name
and pprt is the associated physical printer.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP301

SESSION WITH ACB: session_partner QUEUED: mm/dd/yy hh:mm:ss
Explanation: A VPRINTQ command was issued. session_partner is the
application ACB with which this VPRINTER (described on the preceeding
KLVVP300 message) is in session. The date and time specify when the session
was initially established.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP302

NO VIRTUAL PRINTER REQUESTS ON CHAIN
Explanation: A VPRINTQ command was issued. The VPRINTER (described on
the preceeding KLVVP300 message) currently has no application sessions.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP303

SCREEN PRINT ON BEHALF OF: id
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message is a screen print on behalf of id.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP304

REQUEST TOKEN: token
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message has a request token of token.
System Action: None.
User Response: None.
Message Type: REPLY.

126

Candle Products Messages Manual (KLVHS–KONCT)

KLVVP305

PRINT REQUEST STATUS FLAGS:
Explanation: A VPRINTQ command was issued. Session status messages follow
this message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP306

SESS-VPRT_LOGGED-ON
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message is in session with the VPRINTER named in the
preceeding KLVVP300 message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP307

ACTIVELY PRINTING
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message is actively printing to the physical printer named
in the preceeding KLVVP300 message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP308

INTERVENTION REQUIRED SENT TO APPLICATION
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message attempted to send data to the VPRINTER named
in the preceeding KLVVP300 message. The VPRINTER was either busy or could
not acquire the physical printer.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP309

REQUEST READY FOR SERVICING
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message has attempted to send data to the VPRINTER but
the VPRINTER has not yet serviced that request.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP310

PRINT_REQ_PRINTED, LAST EB SENT, mm/dd/yy hh:mm:ss
Explanation: A VPRINTQ command was issued. The session named in the
preceeding KLVVP301 message has completed a send to the VPRINTER but still
remains in session with it. The time and date reflects the last complete
transmission.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD001–KLXOP005

127

KLVVP311

TERM REQUEST REQUIRES A SPECIFIED VPRINTER
Explanation: A VPRINTQ command was issued with the TERM= option but a
specific VPRINTER queue was not named.
System Action: The command is ignored.
User Response: Reissue the command specifying VPRT=vprinter_name.
Message Type: ERROR.

KLVVP312

SPECIFIED PRINTER NAME NOT FOUND: printer_name
Explanation: A VPRINTQ command was issued with the VPRT= option but the
specified VPRINTER was not found.
System Action: None.
User Response: Issue the VPRINTD command to review the defined
VPRINTERs and reissue the VPRINTQ command specifying a defined
VPRINTER.
Message Type: ERROR.

KLVVP313

SPECIFIED REQUEST TOKEN NOT FOUND: token
Explanation: A VPRINTQ command was issued with the TERM= option but
the specified request token was not found.
System Action: The command is ignored.
User Response: Issue a "VPRINTQ DETAIL" command for the desired
VPRINTER and specify a valid request token as displayed in message KLVVP304.
Message Type: ERROR.

KLVVP314

VRPINTER REQUEST TOKEN CONTAINS INVALID CHARACTERS
Explanation: A VPRINTQ command was issued with the TERM= option but
the specified request token contained invalid characters. Only alpha A–F and
numeric 0–9 are valid.
System Action: The command is ignored.
User Response: Reissue the command specifying a valid request token.
Message Type: ERROR.

KLVVP315

NO VPRINTERS DEFINED
Explanation: A VPRINTQ command was issued but there are no defined
VPRINTERs to report on.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP330

VPRINTER REQUEST (request) TERMINATED
Explanation: A VPRINTQ command was issued with the TERM= option and
the associated session was terminated.
System Action: None.
User Response: None.
Message Type: REPLY.

128

Candle Products Messages Manual (KLVHS–KONCT)

KLVVP400

VPRINTER: vprt -> CURRENT PHYSICAL PRINTER: phys_prt
Explanation: A VPRINTD command was issued. vprt is the VPRINTER name
and phys_prt is the currently associated physical printer.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP401

SPECIFIED PRIMARY PHYSICAL PRINTER: pri_phys_prt
Explanation: A VPRINTD command was issued. pri_phys_prt is the physical
printer specified on the original VPRINTER command named in the preceeding
KLVVP400 message. This message will only be displayed if ALTPU= was
specified when the VPRINTER was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP402

SPECIFIED ALTERNATE PHYSICAL PRINTER: alt_phys_prt
Explanation: A VPRINTD command was issued. alt_phys_prt is the alternate
printer specified on the original VPRINTER command named in the preceeding
KLVVP400 message. This message will only be displayed if ALTPU= was
specified when the VPRINTER was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP403

SESSION WITH: session_partner
Explanation: A VPRINTD command was issued. session_partner is the
application ACB the VPRINTER named in the preceeding KLVVP400 message is
currently in session with.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP404

SCREEN PRINT ON BEHALF OF: id
Explanation: A VPRINTD command was issued. The session named in the
preceeding KLVVP403 message is a screen print on behalf of id.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP405

## SESSION(S)
Explanation: A VPRINTD command was issued. This is total number of
sessions between applications and the VPRINTER named in the preceeding
KLVVP400 message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD001–KLXOP005

129

KLVVP406

RETRY IN PROGRESS: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message is currently
trying to reacquire the physical printer also named in the preceeding KLVVP400.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP407

NO RETRY LIMIT SPECIFIED
Explanation: A VPRINTD command was issued. This message reports that the
VPRINTER named in the preceeding KLVVP400 message had no RETRY count
specified when it was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP408

RETRIES LEFT: ##
Explanation: A VPRINTD command was issued. This message reports that the
VPRINTER named in the preceeding KLVVP400 message will CLOSE after ##
more unsuccessful retries.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP409

ALTERNATE PHYSICAL PRINTER ATTEMPTED: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message has
unsuccessfully attempted to acquire the physical printer named in the preceeding
KLVVP401 message and has subsequently directed all acquire attempts to the
alternate printer specified when the VPRINTER was defined which is named in
the preceeding KLVVP400 and KLVVP402 messages.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP410

CLEAR RU WILL UNBIND VIRTUAL SESSION: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message will treat a
CLEAR RU as a session unbind request.
System Action: None.
User Response: None.
Message Type: REPLY.

130

Candle Products Messages Manual (KLVHS–KONCT)

KLVVP411

SESSION HONORS RELREQ: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message will use the
RELREQ protocol when attempting to establish a session with the physical printer.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP412

WAIT FOR DR FROM PHYSICAL PRINTER: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message will wait for
definite response from the physical printer before passing back a response to the
application.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP413

OUTBOUND LIMIT REACHED: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message has reached
the limit specified or defaulted to in the OUTBDLIM startup parameter. Refer to
KLVVP037.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP414

IMMEDIATE PHYSICAL RELEASE SPECIFIED: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message will
immediately release the physical when no print requests remain.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP415

PHYSICAL SESSION HELD/IN USE: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message is currently in
session with the physical printer also named in the KLVVP400 message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD001–KLXOP005

131

KLVVP416

PHYSICAL SESSION TIMEOUT: mm:ss
Explanation: A VPRINTD command was issued. This message reports the idle
time allowed for the physical printer named in the KLVVP400 message before the
session between it and the VPRINTER also named in the KLVVP400 message is
terminated.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP417

PHYSICAL PRINTER OWNED:YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message currently
owns the physical printer also named in the KLVVP400 message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP418

MAXLINE: ###
Explanation: A VPRINTD command was issued. This message reports the
MAXLINE for the VPRINTER named in the KLVVP400 message.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP419

PHYSICAL SESSION ACTIVE: NO/YES, REQUEST(request)
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message is currently
servicing a request (request).
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP421

CHAINSIZE SPECIFIED: ###
Explanation: A VPRINTD command was issued. This message reports the
CHAINSIZ for the VPRINTER named in the KLVVP400 message. This message
will only be displayed if CHAINSIZ= was specified when the VPRINTER was
defined.
System Action: None.
User Response: None.
Message Type: REPLY.

132

Candle Products Messages Manual (KLVHS–KONCT)

KLVVP422

LOGMODE OVERRIDE SPECIFIED: xxxxxxxx
Explanation: A VPRINTD command was issued. This message reports the
LOGMODE for the VPRINTER named in the KLVVP400 message to use when
establishing a session with the physical printer also named in the KLVVP400
message. This message will only be displayed if LOGMODE= was specified when
the VPRINTER was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP423

PHYSICAL PRINTER IS SYSOUT: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message is a SYSOUT
VPRINTER.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP424

SYSOUT CLASS: class
Explanation: A VPRINTD command was issued. This message reports the
SYSOUT class of the VPRINTER named in the preceeding KLVVP400 message.
This message will only be displayed if the VPRINTER is a SYSOUT VPRINTER.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP425

SYSOUT DEST: dest
Explanation: A VPRINTD command was issued. This message reports the
DEST of the VPRINTER named in the preceeding KLVVP400 message. This
message will only be displayed if the VPRINTER is a SYSOUT VPRINTER and if
DEST= was specified when the VPRINTER was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP426

SYSOUT USER: user
Explanation: A VPRINTD command was issued. This message reports the
USER of the VPRINTER named in the preceeding KLVVP400 message. This
message will only be displayed if the VPRINTER is a SYSOUT VPRINTER and if
USER= was specified when the VPRINTER was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVSD001–KLXOP005

133

KLVVP427

SYSOUT FORM: form
Explanation: A VPRINTD command was issued. This message reports the
FORM of the VPRINTER named in the preceeding KLVVP400 message. This
message will only be displayed if the VPRINTER is a SYSOUT VPRINTER and if
FORM= was specified when the VPRINTER was defined.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP428

SYSOUT IGNORE EOM: YES/NO
Explanation: A VPRINTD command was issued. This message reports whether
or not the VPRINTER named in the preceeding KLVVP400 message will ignore
the EOM character. This message will only be displayed if the VPRINTER is a
SYSOUT VPRINTER.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP429

NO VPRINTERS DEFINED
Explanation: A VPRINTD command was issued but there are no defined
VPRINTERs to report on.
System Action: None.
User Response: None.
Message Type: REPLY.

KLVVP430

VPRT AND PPRT MAY NOT BE SPECIFIED TOGETHER
Explanation: A VPRINTD command was issued with both the PPRT= and
VPRT= options.
System Action: The command is ignored.
User Response: Respecify the command specifying either VPRT= or PPRT=.
Message Type: ERROR.

KLVVP431

SPECIFIED PRINTER NAME NOT FOUND: printer_name
Explanation: A VPRINTD command was issued with either the VPRT= or
PPRT= option but the specified VPRINTER or physical printer was not found.
System Action: None.
User Response: Issue the VPRINTD command to review the defined
VPRINTERs and reissue the VPRINTD command specifying a defined VPRINTER
or physical printer.
Message Type: ERROR.

KLVVS001

OPEN FAILED FOR VSAM ACB: R15(r15) ACBERFLG(acberflg)
Explanation: An unsuccessful attempt was made to open a VSAM ACB.
System Action: The dataset is unavailable.
User Response: Use the appropriate IBM DFP or VSAM programmer’s
reference (typically Macro Instructions for Data Sets) for the OPEN macro, and the
r15 and acberflg fields to determine the cause for the error. Then take appropriate
corrective action.
Message Type: ERROR.

134

Candle Products Messages Manual (KLVHS–KONCT)

KLVVS002

CLUSTER cid: BFRFND(bfrfnd) BUFRDS(bufrds) NUIW(nuiw)
STRMAX(strmax) UIW(uiw)
Explanation: This message is logged to create an audit trail before an attempt to
close a VSAM ACB.
bfrfnd

The number of times a read request was satisfied by a buffer already
in storage.

bufrds

The number of times a read request caused an I/O to be issued against
the VSAM cluster. Increasing the LSRPOOL value in RKLVIN for the
CI size associated with this cluster may reduce the number of reads.

nuiw

The number of nonuser-initiated writes. These are performed when all
buffers contain data and another buffer is required. VSAM causes the
pending buffers to be written.

strmax

The maximum number of concurrent VSAM requests against all
VSAM datasets during this CT/Engine run. If this value and the
LSRSTRNO value in the RKLVIN file are consistently equal, you may
want to increase LSRSTRNO, thus possibly reducing throughput delay
for CT/Engine VSAM requests.

uiw

The number of user-initiated writes. These are writes issued against
ACBs with the nondeferred write attribute and writes forced by
CT/Engine to release some VSAM buffers.

System Action: None.
User Response: None.
Message Type: LOG.
KLVVS003

VSAM ACB CLOSE FAILURE: R15(r15) ACBERFLG(acberflg)
Explanation: An unsuccessful attempt was made to close a VSAM ACB.
System Action: Any attempt to use the cluster in error may result in an error.
User Response: Use the appropriate IBM DFP or VSAM programmer’s
reference (typically Macro Instructions for Data Sets) for the CLOSE macro, and
the r15 and acberflg fields to determine the cause of the error. Then take
appropriate corrective action.
Message Type: ERROR.

KLVVS010

text
Explanation: A control statement in the KLVINVAM RKANPAR member has
been read and is being processed. text is the statement.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSD001–KLXOP005

135

KLVVS011

VSAM ACB GENERATION ERROR: R15(r15) R0(r0), TERMINATION
SCHEDULED
Explanation: During CT/Engine initialization, an error was detected when a
GENCB macro was issued to generate an ACB.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Use the appropriate IBM DFP or VSAM programmer’s
reference (typically Macro Instructions for Data Sets) for the GENCB macro, and
the r15 and r0 fields to determine the cause of the error. Then take appropriate
corrective action and restart CT/Engine.
Message Type: ALERT.

KLVVS012

EXCESS BYTES RESERVED IN $CCB FOR VSAM ACB: NEEDED(nbytes)
ALLOCATED(mbytes) EXCESS(mbytes-nbytes)
Explanation: The length of the VSAM ACB generated is less than the amount of
storage reserved for the ACB in the CT/Engine control block $CCB.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVS013

VSAM RPL GENERATION ERROR: R15(r15) R0(r0), TERMINATION
SCHEDULED
Explanation: During CT/Engine initialization, an error was detected when a
GENCB macro was issued to generate an RPL.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Use the appropriate IBM DFP or VSAM programmer’s
reference (typically Macro Instructions for Data Sets) for the GENCB macro, and
the r15 and r0 fields to determine the cause of the error. Then take appropriate
corrective action and restart CT/Engine.
Message Type: ALERT.

KLVVS014

EXCESS BYTES RESERVED IN $CRB FOR VSAM RPL: NEEDED(nbytes)
ALLOCATED(mbytes) EXCESS(mbytes-nbytes)
Explanation: The length of the VSAM RPL generated is less than the amount of
storage reserved for the RPL in the CT/Engine control block $CRB.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVS015

VSAM INITIALIZATION COMPLETE
Explanation: When the VSAM initialization startup module has successfully
completed, this message is logged to create an audit trail.
System Action: None.
User Response: None.
Message Type: INFO.

136

Candle Products Messages Manual (KLVHS–KONCT)

KLVVS016

VSAM ACB REQUIRES n BYTES, ONLY m BYTES WERE RESERVED,
INCREASE &$CCBSP$
Explanation: The amount of storage reserved in the CT/Engine $CCB control
block is not sufficient for the amount used by the VSAM ACB generated.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Retain the CT/Engine run sheets and dump files, this message,
the MVS system log, and determine your systems DFP release level, then contact
Candle Customer Support.
Message Type: WARNING.

KLVVS017

VSAM RPL REQUIRES n BYTES, ONLY m BYTES WERE RESERVED,
INCREASE &$CRBSP$
Explanation: The amount of storage reserved in the CT/Engine $CRB control
block is not sufficient for the amount used by the VSAM RPL generated.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Retain the CT/Engine run sheets and dump files, this message,
the MVS system log, and determine your systems DFP release level, then contact
Candle Customer Support.
Message Type: WARNING.

KLVVS018

VSAM INITIALIZATION BYPASSED, NO LSR POOL
Explanation: No LSR pool was allocated during CT/Engine startup.
System Action: The CT/Engine VSAM facility is unavailable.
User Response: Ensure that one or more LSRPOOL keywords are coded in
RKLVIN and restart CT/Engine.
Message Type: LOG.

KLVVS019

TOO MANY FREEPCTWARN VALUES
Explanation: More than 10 values were specified on the KLVINVAM RKANPAR
keyword, FREEPCTWARN.
System Action: The remainder of the KLVINVAM member will be processed,
then CT/Engine startup will be terminated.
User Response: Correct FREEPCTWARN to have 10 or fewer values.
Message Type: WARN, ERROR.

KLVVS020

KLVINVAM RKANPAR PARAMETERS:
Explanation: Module KLVINVAM logs its startup parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVVS010.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSD001–KLXOP005

137

KLVVS021

VSAM LOGIC ERROR: RPL(addr) CLUSTER(name) RPLFDBWD(rplfdbwd)
RPLIDWD(rplidwd) RPLOPTCD(rploptcd)
Explanation: A VSAM request issued by CT/Engine received RC=8, indicating
that a logical error occurred. For resource contention errors received for a given
request, this message is issued every 10 errors to reduce message traffic in
RKLVLOG.
System Action: If the error indicates VSAM resource contention, message
KLVVS026 will be issued and the request retried. Otherwise, the system action
depends on the reason for the error.
User Response: When this message is followed by KLVVS026, refer to that
message for appropriate actions. Otherwise, consult the appropriate IBM DFP or
VSAM reference manual (typically Macro Instructions for Data Sets) for the
meaning of RPLFDBWD (the feedback word) to determine the cause of the error,
then take the appropriate corrective action.
Message Type: LOG.

KLVVS026

VSAM type CONTENTION - REQUEST WILL BE RETRIED IN 0.50
SECONDS (nnn RETRIES)
Explanation: A VSAM request issued by CT/Engine was rejected because of
resource contention. type may be CI, BUFFER, or STRING. nnn is the number of
prior retries for this request. KLVVS021 precedes this message. For resource
contention errors received for a given request, this message is issued every 10
errors to reduce message traffic in RKLVLOG.
System Action: The CT/Engine requester is suspended for one-half second,
then the request is reissued.
User Response: If the condition occurs ofter, take the following actions:
STRING

Increase the LSRSTRNO value in RKLVIN to allow more
concurrent VSAM requests. If the value is at its maximum of 255,
no further action is available.

BUFFER

Increase the LSRPOOL value in RKLVIN for the CI size of the
cluster identified in the KLVVS021 message.

If the cluster identified in the KLVVS021 message has a CI size
greater than 4096, reallocate it with CISIZE(4096) and increase
the LSRPOOL value for buffer size 4096. If the CI size is 4096 or
smaller, no further action is available.

Message Type:
KLVVS031

138

LOG.

VSAM PHYSICAL ERROR: RPL(addr) CLUSTER(name)
RPLFDBWD(rplfdbwd) RPLIDWD(rplidwd) RPLOPTCD(rploptcd)
Explanation: A VSAM physical error was detected.
System Action: The system action depends on the reason for the error.
User Response: Consult the appropriate IBM DFP or VSAM reference manual
(typically Macro Instructions for Data Sets) for the meaning of RPLFDBWD (the
feedback word) to determine the cause of the error, then take the appropriate
corrective action.
Message Type: LOG.

Candle Products Messages Manual (KLVHS–KONCT)

KLVVS041

FREEPCTWARN VALUE INVALID: pct
Explanation: A FREEPCTWARN value is larger than 100 or less than 0.
System Action: The remainder of the KLVINVAM member will be processed,
then CT/Engine startup will be terminated.
User Response: Correct FREEPCTWARN so that all values are between 0–100
inclusive.
Message Type: WARN, ERROR.

KLVVS042

‘text’ IS NOT VALID FOR kwd RKANPAR(KLVINVAM)
Explanation: The KLVINVAM keyword, kwd, had a value, text, that is not YES
or NO.
System Action: The remainder of the KLVINVAM member will be processed,
then CT/Engine startup will be terminated.
User Response: Correct kwd to specify YES or NO.
Message Type: WARN, ERROR.

KLVVS043

SPACEINTERVAL VALUE INVALID: nnn
Explanation: The SPACEINTERVAL value is 0 or negative.
System Action: The remainder of the KLVINVAM member will be processed,
then CT/Engine startup will be terminated.
User Response: Correct SPACEINTERVAL so that the value is 1 or greater.
Message Type: WARN, ERROR.

KLVVS050

dd type EXTENTS=mmm FREE=nnn% DSNAME=dsn
Explanation: This message documents the current space usage for data set dsn,
allocated to DD dd. type is either DATA or INDEX. mmm is the current number of
extents occupied by the data or index. nnn is the current percentage of space free
within the cluster.
KLVVS050 is issued for any of these reasons:
® OPENMESSAGE=YES was specified and the cluster is being opened.
®

CLOSEMESSAGE=YES was specified and the cluster is being closed.

The number of data or index extents changed.

The free space percentage has reached or crossed one of the values specified
in the FREEPCTWARN keyword.

Note: OPENMESSAGE, CLOSEMESSAGE, and FREEPCTWARN are all
specified in the RKANPAR member, KLVINVAM.
System Action: None.
User Response: None.
Message Type: LOG, WARN.

KLVSD001–KLXOP005

139

KLVVS051

SHOWCB RC=rc REASON=rs dd dsn; SPACE MESSAGES DISABLED
Explanation: Space usage could not be determined for data set dsn, allocated
to dd, because a SHOWCB macro failed. rc is the return code (R15); rs is the
reason code (R0).
System Action: No further space usage monitoring will be done for the cluster.
All other VSAM operations are unaffected.
User Response: Contact Candle Customer Support with the contents of this
message and your MVS and DFP release and maintenance levels.
Message Type: LOG, WARN, ERROR.

KLVVS052

INVALID KLVVSSTM REQUEST
Explanation: An invalid parameter list was passed to a CT/Engine VSAM
service module.
System Action: The active thread is terminated. A diagnostic dump will be
taken to the system dump data sets or RKLVSNAP.
User Response: Retain the CT/Engine run sheets and the dump, and contact
Candle Customer Support.
Message Type: None.

KLVVT001

VTAM OPEN ERROR: APPLID(applid) R15(r15) ACBERFLG(acberflg)
Explanation: An unsuccessful attempt was made to open a VTAM ACB.
System Action: The application terminates.
User Response: Use the IBM manual ACF/VTAM Programming and the r15
and acberflg fields to determine the cause of the error and take appropriate
corrective action.
Message Type: LOG, VIEW.

KLVVT002

VTAM CLOSE ERROR: APPLID(applid) R15(r15) ACBERFLG(acberflg)
Explanation: An unsuccessful attempt was made to close a VTAM ACB.
System Action: None.
User Response: Use the IBM manual ACF/VTAM Programming and the r15
and acberflg fields to determine the cause of the error and take appropriate
corrective action.
Message Type: LOG, VIEW.

KLVVT003

CRITICAL APPLICATION TERMINATING: APPLID(applid)
Explanation: A critical application applid is in the process of terminating. An
application is defined as critical at open time.
System Action: None.
User Response: None.
Message Type: ALERT.

140

Candle Products Messages Manual (KLVHS–KONCT)

KLVVT004

VTAM ACCESS METHOD SUPPORT VECTOR LIST
RELEASE LEVEL level
COMPONENT ID id
FUNCTION LIST list
VECTOR vector
Explanation: The first VTAM ACB is successfully opened, causing information
about the current level of VTAM to be logged.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVT005

SETLOGON FAILURE: APPLID(applid), REQSTAT(reqstat)
Explanation: A SETON request for application ABCNAME failed. reqstat is the
return code and feedback information: the first byte of which is the return code,
the second byte is the feedback, and the third and fourth are the SNA sense code.
System Action: The application terminates.
User Response: Use the IBM manual ACF/VTAM Programming and the reqstat
field to determine the cause of the error and take appropriate corrective action.
Message Type: INFO.

KLVVT015

SESSION PROCEDURE TIMEOUT: LU(luname) SPT(timeout)
Explanation: A session initiation request has timed out. A REQSESS for
primary LU luname or SIMLOGON for secondary LU luname was issued and the
response to the request exceeded the timeout interval timeout.
System Action: The session initiation attempt fails.
User Response: Increase SPT value in member KLVINVTM in RKANPAR
library.
Message Type: INFO.

KLVVT021

text: appl, ,,, seqno,req, cntrl,
fdbk<,fdbk2><,osens>
Explanation: VTAM and CT/Engine information has been formatted because a
VTAM error has occurred or because CT/Engine has been directed to trace certain
VTAM actions. The data that may be shown follows (RPL field names are in
brackets):
text

Short description of the error.
API TRACE
CT/Engine has been directed to trace the flow of
control for this ACB.
EXIT TRACE
CT/Engine has been directed to trace the flow of
control for this ACB.
DFASY EXIT
CT/Engine has been directed to trace the flow of
control for this ACB.

KLVSD001–KLXOP005

141

REQUEST RETRY
The request was rejected because of a storage
shortage. CT/Engine will wait one second and then
retry the request.
INBOUND -RSPA negative response was received and DEBUG(Y)
has been requested.
INBOUND +RSP
A positive response was received and CT/Engine has
been directed to trace the flow of control for this ACB.
CHAIN RETRY
An exceptional condition was detected for this request
and is being retried.
CHAIN RETRY FAILED
An attempt to retry a request that failed for an
exceptional reason was not successful. The session is
terminated. Refer to the data fields in the message to
determine the problem.
OUTBOUND -RSPA negative response is being reflected to the requester.
Refer to the data fields in the message for more
information.
LOGICAL ERROR
A VTAM logical error was detected. Refer to the data
fields in the message for more information.
VTAM NSXIT, UNKNOWN RU
The CT/Engine Network Services Exit was scheduled,
but the request unit (RU) received was not a Cleanup,
Notify, or Network Services RU. Contact your site’s
VTAM systems programmer.
INVALID CORRELATOR
A solicited BIND has been received, but the
user-provided correlator returned by VTAM is not
valid. The BIND is rejected. Contact your VTAM
systems programmer.
PHYSICAL ERROR
A VTAM physical error was detected. If the error was
a VTAM storage shortage the request is retried until it
succeeds or fails for a different reason. Refer to the
data fields in the message to determine the problem.

142

appl

Application ID.

Logical unit name.

dest

Destination (for CLSDST PASS).

cid

Communication identifier.

Candle Products Messages Manual (KLVHS–KONCT)

logmode

Associated logmode.

seqno

RPL sequence number. [RPLSEQNO].

req

Request code. If it is one of a standard set, it is shown in English;
otherwise it is formatted in hexadecimal. [RPLREQ].

mod

Control modifier: [RPLSRTYP] and [RPLRH3].
R

Response

BB
EB
CEB
CD

Begin bracket
End bracket
Conditional end bracket
Change direction

cntrl

Control information. If it is one of a standard set, it is shown in
English; otherwise it is formatted in hex. [RPLCNTRL].

fdbk

Request feedback. If it is one of a standard set, it is shown in
English; otherwise it is formatted in hex. [RPLFDBK].

fdbk2

More feedback information, displayed in hex. [PRLFDBK2].

osens

Sense code information, displayed in hex. [RPLOSENS].

If a data item cannot be located, it is omitted from the message. If DEBUG(Y) was
specified in the CT/Engine KLVSYSIN file, the contents of any request units, the
RPL, and a CT/Engine control block will be displayed, if they are relevant.
System Action: The system action depends on the reason for the dump.
User Response: Refer to the IBM manual ACF/VTAM Programming to obtain
information about the FDBK, FDBK2, and OSENS fields. If the dump seems to be
associated with a persistent problem, contact Candle Customer Support.
Note: Many of these dumps are the result of normal conditions, such as
powering a terminal off.
Message Type:

LOG. If DEBUG(Y) is specified, LOG, VIEW.

KLVVT021

EXCEPTION RESPONSE
Explanation: An exception response was received by CT/Engine.
System Action: The system action depends on the reason for the exception
response.
User Response: If the exception response is not the result of normal network
activity, contact Candle Customer Support.
Message Type: LOG.

KLVVT021

DEFINITE RESPONSE
Explanation: The EXIT or API traces have been enabled. All responses received
by CT/Engine cause a VTAM request dump under these circumstances.
System Action: None.
User Response: None.
Message Type: LOG.

KLVSD001–KLXOP005

143

KLVVT021

VTAM LERAD EXIT
Explanation: A VTAM logic error was detected, causing the CT/Engine LERAD
exit to be scheduled.
System Action: None.
User Response: Consult your site’s VTAM systems programmer.
Message Type: LOG.

KLVVT021

VTAM NSEXIT, UNKNOWN RU
Explanation: The CT/Engine Network Services Exit was scheduled, but the RU
received was not a Cleanup RU or a Notify RU.
System Action: None.
User Response: Consult your site’s VTAM systems programmer.
Message Type: LOG.

KLVVT021

VTAM SYNAD EXIT
Explanation: A physical error or special condition was encountered by VTAM,
causing the CT/Engine SYNAD exit to be scheduled.
System Action: Unpredictable.
User Response: Consult your site’s VTAM systems programmer.
Message Type: LOG.

KLVVT021

PHYSICAL ERROR
Explanation: VTAM encountered a physical error, for example, a storage
shortage.
System Action: The operation is retried until successful. System action is
invisible to the user.
User Response: None. This message is logged for audit purposes only.
Message Type: LOG.

KLVVT021

API EXIT TRACE ENABLED
Explanation: The API exit trace has been enabled.
System Action: A VTAM request dump is taken.
User Response: None.
Message Type: LOG.

KLVVT021

RPL EXIT TRACE ENABLED
Explanation: The RPL exit trace has been enabled.
System Action: A VTAM request dump is taken.
User Response: None.
Message Type: LOG.

KLVVT021

INVALID CORRELATOR
Explanation: A solicited BIND has been received, and the user-provided
correlator returned by the access method is not valid.
System Action: The BIND is rejected.
User Response: Consult your site’s VTAM systems programmer.
Message Type: LOG.

144

Candle Products Messages Manual (KLVHS–KONCT)

KLVVT031

LOGON REJECTED: LU(luname) CID(cid)
Explanation: Either:
1. a resource ID could not be assigned, or
2. session initialization failed for the device luname and communication ID cid.
System Action: The session terminates.
User Response: Look for other error messages associated with this LU luname
to isolate the error.
Message Type: INFO.

KLVVT051

NETWORK SERVICES RU: APPLID(acb) LRN(lrn) RU(ru)
Explanation: The CT/Engine NSEXIT received a network services RU.
System Action: For cleanup requests, the session is terminated.
User Response: The RU field contains the network services RU type. Refer to
the IBM manual SNA Reference Summary to determine the NS RU type or
contact your site’s VTAM systems programmer.
Message Type: LOG.

KLVVT061

RELEASE REQUESTED: LU(luname) ACB(address)
Explanation: Another application program has requested a session with logical
unit luname. address is the address of the CT/Engine ACB for luname. VTAM
does not provide information about the application that requested the release.
System Action: A VTAM RELREQ command is issued against luname.
User Response: None.
Message Type: LOG, VIEW.

KLVVT062

RELEASE REQUESTED, SESSION NOT FOUND: LU(lu)
Explanation: Another application program has requested a session with logical
unit lu but the session between a CT/Engine application and LU lu could not be
found.
System Action: None.
User Response: None.
Message Type: LOG, VIEW.

KLVVT091

APPLICATION HAS BEEN HALTED: APPLID(applid)
Explanation: The VTAM operator is shutting down the network or this
application, or, an abend of VTAM has occurred.
System Action: Sessions between application applid and its associated logical
units terminate.
User Response: This message is normally the result of an orderly CT/Engine
shutdown. Each active application is closed by CT/Engine.
Message Type: WARNING.

KLVSD001–KLXOP005

145

KLVVT101

VTAM EXLST GENERATION ERROR: R15(r15) R0(r0) TERMINATION
SCHEDULED
Explanation: An error was detected during the generation of a VTAM EXLST.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error. Correct it, and restart CT/Engine. The return
code appears in the r15 field and the error return code appears in the r0 field.
Message Type: ALERT.

KLVVT102

VTAM ACB GENERATION ERROR: R15(r15) R0(r0) TERMINATION
SCHEDULED
Explanation: An error was detected during the generation of a VTAM ACB
GENCB macro.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error. Correct it, and restart CT/Engine. The return
code appears in the r15 field and the error return code appears in the r0 field.
Message Type: ALERT.

KLVVT103

EXCESS BYTES RESERVED IN $ACB FOR VTAM ACB: NEEDED(nbytes)
ALLOCATED(mbytes) EXCESS(mbytes-nbytes)
Explanation: The length of the VTAM ACB generated is less than the amount of
storage reserved for the ACB in the CT/Engine control block $ACB.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVT104

VTAM NIB GENERATION ERROR: R15(r15) R0(r0) TERMINATION
SCHEDULED
Explanation: An error was detected during the generation of a VTAM NIB
(GENCB macro).
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error. Correct it, and restart CT/Engine. The return
code appears in the r15 field and the error return code appears in the r0 field.
Message Type: ALERT.

KLVVT105

EXCESS BYTES RESERVED IN $NIB FOR VTAM NIB: NEEDED(nbytes)
ALLOCATED(mbytes) EXCESS(mbytes-nbytes)
Explanation: The length of the VTAM NIB generated is less than the amount of
storage reserved for the RPL in the CT/Engine control block $CRB.
System Action: None.
User Response: None.
Message Type: LOG.

146

Candle Products Messages Manual (KLVHS–KONCT)

KLVVT106

VTAM RPL GENERATION ERROR: R15(r15) R0(r0) TERMINATION
SCHEDULED
Explanation: An error was detected during the generation of a VTAM RPL
GENCB macro.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error. Correct it, and restart CT/Engine. The return
code appears in the r15 field and the error return code appears in the r0 field.
Message Type: ALERT.

KLVVT107

EXCESS BYTES RESERVED IN $ARB FOR VTAM RPL: NEEDED(nbytes)
ALLOCATED(mbytes) EXCESS(mbytes-nbytes)
Explanation: The length of the VTAM RPL generated is less than the amount of
storage reserved for the RPL in the CT/Engine control block $ARB.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVT108

NO EXTENDED SUPPORT FOR VTAM LEVEL: level
Explanation: Some extended functions such as RTM might not be able to
perform.
System Action: Processing continues.
User Response: If extended functions such as RTM are used contact Candle
Customer Support.
Message Type: LOG.

KLVVT109

VTAM ACB REQUIRES n BYTES, ONLY m BYTES WERE RESERVED,
INCREASE &$ACBSP$
Explanation: The amount of storage reserved in the CT/Engine control block
$ACB is not sufficient for the amount used by the VTAM ACB generated.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log. Determine your systems VTAM release level, then
contact Candle Customer Support.
Message Type: WARNING.

KLVVT110

VTAM NIB REQUIRES n BYTES, ONLY m BYTES WERE RESERVED,
INCREASE &$NIBSP$
Explanation: The amount of storage reserved in the CT/Engine control block
$SCB is not sufficient for the amount used by the VTAM NIB generated.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log. Determine your system’s VTAM release level, then
contact Candle Customer Support.

KLVSD001–KLXOP005

147

KLVVT111

VTAM RPL REQUIRES n BYTES, ONLY m BYTES WERE RESERVED,
INCREASE &$ARBSP$
Explanation: The amount of storage reserved in the CT/Engine control block
$ARB is not sufficient for the amount used by the VTAM RPL generated.
System Action: After any subsequent startup modules are invoked, CT/Engine
terminates.
User Response: Retain the CT/Engine run sheets and dump files, this message,
and the MVS system log. Determine your system’s VTAM release level, then
contact Candle Customer Support.
Message Type: WARNING.

KLVVT112

VTAM INTERFACE INITIALIZED [,XA] [,AUTHORIZED PATH]
[,SPT=VTSPT]
Explanation: The VTAM interface has been initialized and XA and
AUTHORIZED PATH are displayed if used. VTSPT specifies the VTAM session
procedure timeout.
System Action: None.
User Response: None.
Message Type: INFO.

KLVVT113

KLVINVTM RKANPAR PARAMETERS:
Explanation: Module KLVINVTM logs its startup parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVVT114.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVT114

parameters
Explanation: As the parameters in module KLVINVTM are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

148

Candle Products Messages Manual (KLVHS–KONCT)

KLVVT251

SESSION SETUP ERROR: POOL(pool) APPLID(applid) PLU(plu)
REQSTAT(rcfb)
Explanation: There has been a failure to establish a virtual session. pool and
applid identify the virtual terminal. plu is the requested application. rcfb is the
4-byte return code and feedback information:
1

Return code. The high bit (X’80’) will be turned on if this message is
being issued as a result of a VTAM NOTIFY request unit. The next bit
(X’40’) will be turned on if the data shown in bytes 3 and 4 is the user
sense code. The remaining bits are the notify reason from the NOTIFY
RU or the RPL return code (RPLRTNCD) from the VTAM acquire
request.

The reason code, from the NOTIFY RU (notify) or RPLFDB2
(acquire).

3,4

The sense code. This is from the NOTIFY RU for notify or from
RPLFDBK2/RPLUSNSI for acquire.

The NOTIFY request unit is described in the IBM manual ACF/VTAM
Programming, under ”NSEXIT Exit Routine”.
System Action: None.
User Response: Refer to the appropriate IBM VTAM manual for the meaning
of the sense code provided in bytes 3 and 4 of rcfb and correct the problem.
Message Type: INFO.
KLVVT501

INITIALIZATION MEMBER KLVINVPO NOT AVAILABLE
Explanation: Member KLVINVPO in the initialization library was not available
at startup time.
System Action: The VTAM programmed operator facility (VPO) is
unavailable.
User Response: If use of this facility is desired, define member KLVINVPO in
the initialization library and restart CT/Engine.
Message Type: LOG.

KLVVT503

INITIALIZATION MEMBER KLVINVPO IS EMPTY
Explanation: Member KLVINVPO in the initialization library is empty.
System Action: The VPO facility is unavailable.
User Response: If use of this facility is desired, update member KLVINVPO
and restart CT/Engine.
Message Type: WARNING.

KLVVT505

VPO SHOWCB ERROR: R15(r15) R0(r0)
Explanation: An error was detected upon execution of an MVS SHOWCB
macro instruction.
System Action: The CT/Engine programmed operator facility (VPO) is
unavailable.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error and take appropriate corrective action.
Message Type: WARNING.

KLVSD001–KLXOP005

149

KLVVT506

VPO ACB GENERATION ERROR: R15(r15) R0(r0)
Explanation: An error was detected upon execution of an MVS GENCB macro
instruction.
System Action: The CT/Engine programmed operator facility (VPO) is
unavailable.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error and take appropriate corrective action. The error
is in reference to the VPO ACB defined in initialization library member
KLVINVPO.
Message Type: WARNING.

KLVVT507

UNABLE TO OPEN VPO ACB: R15(r15) ACBERFLG(acberflg)
APPLID(applid)
Explanation: An error was detected upon execution of an MVS OPEN macro
instruction for the VPO ACB.
System Action: The CT/Engine programmed operator facility (VPO) is
unavailable.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error and take appropriate corrective action.
Message Type: WARNING.

KLVVT508

VPO RPL GENERATION ERROR: R15(r15) R0(r0)
Explanation: An error was detected upon execution of an MVS GENCB macro
instruction.
System Action: The CT/Engine programmed operator facility (VPO) is
unavailable.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error and take appropriate corrective action.
Message Type: WARNING.

KLVVT509

VPO APPLID IS NOT AUTHORIZED AS A PROGRAM OPERATOR:
APPLID(applid) RPLRTNCD(rplrtncd) RPLFDB2(rplfdb2)
Explanation: A DISPLAY NET,MAJNODES command was issued but the VPO
applid was not authorized to issue VTAM commands. The most probable cause is
the absence of the SPO parameter on the APPL definition.
System Action: The CT/Engine programmed operator facility (VPO) is
unavailable.
User Response: Consult the IBM manual ACF/VTAM Programming to
determine the cause of the error and take appropriate corrective action.
Message Type: WARNING.

KLVVT510

UNABLE TO INITIALIZE VPO RESOURCE ID: APPLID(applid)
Explanation: An unsuccessful attempt was made to identify the VTAM program
operator to the CT/Engine logical resource manager.
System Action: The VPO facility is unavailable.
User Response: Contact Candle Customer Support.
Message Type: WARNING.

150

Candle Products Messages Manual (KLVHS–KONCT)

KLVVT511

VPO INITIALIZATION COMPLETE: APPLID(applid)
Explanation: VPO initialization has completed successfully.
System Action: None.
User Response: None.
Message Type: INFO.

KLVVT512

KLVINVPO RKANPAR PARAMETERS:
Explanation: Module KLVINVPO logs its startup parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVVT513.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVT513

parameters
Explanation: As the parameters in module KLVINVPO are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLVVT851

UNSUPPORTED FUNCTION MANAGEMENT PROFILE: LU(luname)
FMPROF(prof)
Explanation: The function management profile prof is unsupported.
System Action: The session terminates.
User Response: Logical units with this FM profile cannot establish sessions
with CT/Engine. Consult the IBM manual SNA Reference Summary for more
information on FM profiles and bind parameters.
Message Type: LOG, WARNING, VIEW.

KLVVT852

UNSUPPORTED TRANSMISSION SERVICES PROFILE: LU(luname)
TSPROF(prof)
Explanation: The transmission services profile prof is unsupported.
System Action: The session terminates.
User Response: Logical units with this TS profile cannot establish sessions with
CT/Engine. Refer to the IBM manual SNA Reference Summary for more
information on TS profiles and bind parameters.
Message Type: LOG, WARNING, VIEW.

KLVVT901

ABNORMAL RECEIVE TERMINATION RTNCD(rplrtncd) FDB2(rplfdb2)
SSEI(rplssei) SSMI(rplssmi) USNSI(rplusnsi) ACB(acb) LU(lu)
Explanation: CT/Engine was unable to determine the correct action to take in
response to an exception request.
System Action: The session terminates.
User Response: If the reason for the error cannot be determined from the
information supplied and the error persists, contact Candle Customer Support.
Message Type: REPLY.

KLVSD001–KLXOP005

151

KLVVT902

INBOUND MESSAGE LIMIT EXCEEDED LU(luname) SESSION
CANCELLED
Explanation: The limit of inbound messages received either from application or
physical terminal luname is exceeded.
System Action: The session for the application/terminal is terminated.
User Response: Examine initialization parameter INBDLIM. Contact the
application or terminal vendor and increase the limit if appropriate.
Message Type: ALERT.

KLVVT903

INBOUND CHAIN ELEMENT LIMIT EXCEEDED LU(luname) SESSION
CANCELLED
Explanation: The limit of SNA chain elements per chain received either from
application or physical terminal luname is exceeded.
System Action: The session for the application/terminal is terminated.
User Response: Examine initialization parameter INBCHAINLIM. Contact the
application or terminal vendor and increase the limit if appropriate.
Message Type: ALERT.

KLVVT904

INBOUND MESSAGE SIZE LIMIT EXCEEDED LU(luname) SESSION
CANCELLED
Explanation: The inbound message size received from application or physical
terminal luname is greater than 524,288 bytes.
System Action: The session for the application/terminal is terminated.
User Response: Contact the application or terminal vendor.
Message Type: ALERT.

KLVVT951

VIRTUAL SESSION MANAGER INITIALIZED, TIMEOUT=tt, RETRY=rr
Explanation: This message is logged to create an audit trail when the virtual
session manager has been successfully initialized. TIMEOUT refers to the virtual
session establishment timeout specified in RKANPAR member KLVINVSM or the
default value. RETRY refers to the number of times CT/Engine will retry the
TIMEOUT interval.
System Action: None.
User Response: None.
Message Type: INFO.

KLVVT952

KLVINVSM RKANPAR PARAMETERS:
Explanation: Module KLVINVSM logs its startup parameters as they are read
from RKANPAR. This is the header message and will be followed by message
KLVVT953.
System Action: None.
User Response: None.
Message Type: LOG.

152

Candle Products Messages Manual (KLVHS–KONCT)

KLVVT953

parameters
Explanation: As the parameters in module KLVINVSM are read, a log audit trail
is created.
System Action: None.
User Response: None.
Message Type: LOG.

KLXCP001

IUCV CONNECT FAILED: PATH(path) REASON(reason)
Explanation: The IUCV CONNECT request for path path failed with reason
code reason.
System Action: None.
User Response: Correct the problem and retry the operation.
Message Type: WARN.

KLXCP001

IUCV CONNECT FAILED: PATH(9999) REASON(9999) IPRCODE(9999)
Explanation: The application connect to the Interlink IUVC (TCP/IP) protocol
stack failed.
System Action: The Interlink IUCV (TCP/IP) protocol is not available to the
application.
User Response: Examine IUCV IPR return codes for the cause of failure.

KLXCP002

IUCV INITIAL MESSAGE FAILED: PATH(path) REASON(reason)
Explanation: The IUCV initial SEND failed for path(path) with reason code
reason.
System Action: None.
User Response: Correct the problem and retry the operation.
Message Type: WARN.

KLXCP002

IUCV INITIAL MMSG FAILED: PATH(9999) REASON(9999)
Explanation: The application initial message to the Interlin 4.1 IUCV (TCP/IP)
protocol stack failed.
System Action: The Interlink IUCV (TCP/IP) protocol is not available to the
application.
User Response: This message is expected if the Interlink IUCV connect failed
(message KLXCP001 is also present in the log). If this message is not preceeded
by the KLXCP001 message, this is an error condition. In this instance, gather
relavent logs and submit them to Candle Customer Support.

KLXCT000

INELIGIBLE CT/IX PROCESS or
INELIGIBLE CT/IX THREAD
Explanation: This is an unexpected condition.
System Action: The process or thread is terminated.
User Response: Gather relavent logs and report this to Candle Customer
Support.

KLVSD001–KLXOP005

153

KLXIN001

subsys CONFIGURATION:
Explanation:
subsys

Subsystem this applied to.

TCP/IP

The HPNS interface is the High Performance, Native Socket
interface. Both IBM and Interlink support the HPNS interface
through the EZASMI macro.
The member KLXINTCP is the configuration member of
RKANPAR that is used to configure the IBM or Interlink 5.2 HPNS
interface. This message displays in the content of member
KLXINTCP.

TCP/ACCESS

This message displays the content of the KLXAINIT member of
RKANPAR.. The content is expected to be the Interlink Subsystem
name.

System Action: The process continues.
User Response: None. This message is informational.
Message Type: VIEW.
KLXIN002

SYNTAX ERROR - msg: text
Explanation:
For TCP/IP

The KLXINTCP configuration member of RKANPAR is invalid.
The syntax error is displayed in this message.

For Interlink TCP/ACCESS

CT/Engine initialization has detected a configuration error in the
KLXAINIT member of RKANPAR which names the TCPACCESS
subsystem. msg contains the card image of KLXAINIT member
found to be in error. text is not present.

System Action:
For TCP/IP

Initialization of the HPNS (TCP/IP) interface fails and the
application continues with no access to TCP/IP.

For Interlink TCP/ACCESS

CT/Engine initialization is terminated.

User Response:

154

For TCP/IP

Correct the KLXINTCP configuration member of RKANPAR and
restart the product.

For Interlink TCP/ACCESS

Correct the error, then restart the CT/Engine address space.

Message Type:

WARN.

Candle Products Messages Manual (KLVHS–KONCT)

KLXIN003

TCP/IP INTERFACE INITIALIZED
Explanation: Initialization of the HPNS (TCP/IP) protocol stack has completed
successfully.
System Action: The process continues.
User Response: This message is informational.
Message Type: LOG.

KLXIN003

TCP/ACCESS INTERFACE CONFIGURATION COMPLETE
Explanation: Initialization of the Interlink IUCV protocol stack has completed.
System Action: The process continues.
User Response: This message is informational.
Message Type: LOG.

KLXIN004

TCP/IP INTERFACE NOT OPENED: RC(9999)
Explanation: Allocation and initialization of the TCP/IP interface has failed.
System Action: TCP/IP access is not available to the application.
User Response: Gather relavent logs and submit them to Candle Customer
Support.
Message Type: WARN.

KLXIN004

TCP/ACCESS INTERFACE INITIALIZATION BYPASSED
Explanation: Initialization of the Interlink 4.1 IUCV protocol stack has been
bypassed. Member KLXAINIT was not found in the RKANPAR configuration
PDS.
System Action: The process continues.
User Response: This message is informational.
Message Type: WARN.

KLXIN005

subsys INTERFACE INITIALIZATION BYPASSED
Explanation:
subsys

Subsystem this applied to.

TCP/IP

Initialization of the HPNS (TCP/IP) protocol is bypassed:
configuration member KLXINTCP is not present in RKANPAR.

TCP/ACCESS

CT/Engine initialization of TCPACCESS Interlink support has been
bypassed.

Note that this is not necessarily an error.
System Action:
TCP/IP

The application continues without TCP/IP access.

For Interlink TCP/ACCESS

The TCP/ACCESS communication interface is not available. This
message indicates the KLXAINIT member of RKANPAR is missing.
If TCPACCESS/Interlink support is desired, add member
KLXAINIT containing the name of the Interlink subsystem to the
RKANPAR data set.

KLVSD001–KLXOP005

155

User Response:
TCP/IP

This message is informational.

For Interlink TCP/ACCESS

This message indicates the KLXAINIT member of RKANPAR is
missing. If TCPACCESS/Interlink support is desired, add member
KLXAINIT containing the name of the Interlink subsystem to the
RKANPAR data set.

Message Type:

INFO.

KLXIN006

TCP/IP INTERRUPT UNKNOWN: IPTYPE(iptype) IPPATHID(ippathid)
Explanation: None.
System Action: None.
User Response: None.
Message Type: WARN.

KLXIN007

TCP/IP PATH SEVERED: IPPATHID(ippathid)
Explanation: None.
System Action: None.
User Response: None.
Message Type: WARN.

KLXIN008

TCP/IP PATH NOT FOUND: IPTYPE(iptype) IPPATHID(ippathid)
Explanation: None.
System Action: None.
User Response: None.
Message Type: WARN.

KLXIN009

HPNS INITAPI FAILED: RC(FFFFFFFF) ERRNO(000003F3)
Explanation: A request to contact TCP/IP using the HPNS API has failed with
the noted IBM status information. This is most likely caused by a misconfigured
KLXINTCP member in RKANPAR.
System Action: None.
User Response: If no TCP/IP access is desired, delete KLXINTCP from
RKANPAR.

KLXIN009

HPNS INIAPI FAILED
Explanation: The HPNS interface is the High performance, Native Socket
interface. Both IBM and Interlink support the HPNS interface through the
EZASMI macro. This message indicates that the HPNS interface has failed (the
EZASMI TYPE=INITAPI has failed). The resulting errno should be examined for
the cause of failure.
System Action: The HPNS interface is no longer available. TCP/IP access is
not available to the application.
User Response: make sure the KLXINTCP member of RKANPAR contains the
correct TCP/IP stack identifier.

156

Candle Products Messages Manual (KLVHS–KONCT)

KLXOP000

Explanation: The IPMVS operator command is in error. The syntax error is
displayed in this message.
System Action: The IPMVS operator command is not executed.
User Response: Correct the command syntax and reissue the command.
Message Type: ERROR.

KLXOP001

TCP/IP NOT AVAILABLE
Explanation: The IPMVS operator command has failed becauseTCP/IP is not
available.
System Action: The operator command is not performed.
User Response: Make sure the product is configured for TCP/IP before using
IPMVS operator commands.
Message Type: ERROR.

KLXOP001

UNRECOGNIZED SUBCOMMAND:
Explanation: The LBDAEMON operator command failed. The subcommand is
not recognized.
System Action: The LBDAEMON operator command is ignored.
User Response: This message is informational.
Message Type: WARN.

KLXOP002

TCP/IP subcmd NOT RECOGNIZED
Explanation: The TCP/IP subcommand, subcmd was not recognized. It must be
START, STOP, PING, or CONNECT.
System Action: None.
User Response: Issue a valid TCP/IP subcommand.
Message Type: ERROR.

KLXOP002

TCP/IP’,SUBCMD,’ NOT RECOGNIZED:
Explanation: The IPMVS operator subcommand is not recognized.
System Action: The IPMVS operator command is ignored.
User Response: Reissue the IPMVS operator command with the proper
subcommand.

KLXOP002

UNRECOGNIZED DAEMON ID:
Explanation: The LBDAEMON START operator command failed because the
requested daemon is not valid.
System Action: The LBDAEMON START command is ignored.
User Response: Correct the daemon name/ID and retry the LBDAEMON
operator command.

KLXOP003

TCP/IP subcmd FAILED
Explanation: The TCP/IP subcommand, subcmd failed.
System Action: None.
User Response: Determine the reason for the failure and reissue the
command.
Message Type: ERROR.

KLVSD001–KLXOP005

157

KLXOP003

TCP/IP’,SUBCMD,’ FAILEDD:
Explanation: The IPMVS operator subcommand is valid, but failed in
execution.
System Action: None..
User Response: Gather relavent logs and submit them to Candle Customer
Support.

KLXOP003

DAEMON NOT AVAILABLE:
Explanation: The LBDAEMON command HAS failed because the requested
daemon is not available.
System Action: The LBDAEMON operator command is ignored.
User Response: This is an unusual condition. Gather relavent logs and report
the problem to Candle Customer Support.

KLXOP004

DAEMON STARTED:
Explanation: The LBDAEMON START command has completed successfully.
System Action: The requested DAEMON is started.
User Response: This message is informational.

KLXOP004

TCP/IP subcmd COMPLETED
Explanation: The TCP/IP subcommand, subcmd completed successfully.
System Action: None.
User Response: None.
Message Type: REPLY.

KLXOP004

TCP/IP’,SUBCMD,’ COMPLETED
Explanation: The IPMVS operator subcommand completed successfully.
System Action: The IPMVS operator command output is displayed.
User Response: This message is informational.

KLXOP005

rc HOSTNAME: hostname
Explanation: This is the hostname that was PING’ed or CONNECT’ed. rc is the
return code from the GETHOSTNAME function.
System Action: None.
User Response: None.
Message Type: REPLY.

KLXOP005

HOSTNAME:
Explanation: The IPMVS GETHOSTNAME command has returned this result.
System Action: The IPMVS operator command is executed.
User Response: The command was successful. This message is informational.

158

Candle Products Messages Manual (KLVHS–KONCT)

KM2EXPFF–KMCRCA002I

KM2EXPFF

PROFILE EXPORT FAILED
Explanation: The profile export was unable to complete properly due to an
error.
System Action: Profile is not exported to the requested dataset member.
User Response: See the CANSM2 RKLVLOG for a more detailed message
describing the error.

KM2EXP00

PROFILE EXPORT COMPLETED SUCCESSFULLY
Explanation: The profile export was completed successfully.
System Action: Profile is exported to the dataset specified in the command
parameter list.
User Response: None.

KM2HDI00

HISTORICAL DATA INTERFACE INITIALIZED
Explanation: The historical data interface task of OMEGAMON II for MVS has
become active and is ready to handle requests from the associated CANSM2
region.
System Action: None.
User Response: None.

KM2HDI80

CANSM2HD TERMINATED BY STOP COMMAND
Explanation: The historical data interface task of the CANSM2 region is shutting
down after receiving a STOP MVS command from the console.
System Action: None.
User Response: None.

KM2HDI90

HISTORICAL DATA INTERFACE CLOSED
Explanation: The historical data interface task is terminating because its
associated CANSM2 region has sent it a shutdown request.
System Action: None.
User Response: None.

KM2EXPFF–KMCRCA002I

159

KM2HDI99

160

CANSM2HD FAILED
KM2HDI99 REASON (xxxx) SESSION (xxxxxxxx) HANDLE (xxxxxxxx)
Explanation: The historical data interface is terminating after detecting a
non-recoverable condition. These two messages are produced together in the
order shown. The reason code defines the problem for the user. The SESSION and
HANDLE values are the CANSM2 session handle and cross memory handle,
respectively.
System Action: The task is shut down.
User Response: Remedy the error condition and restart the region. If the error
persists, call Candle Support. Please have the sysout from both this task and the
associated CANSM2 task available for reference.
Note that in the reason codes listed below, the first digit may or may not be an 8.
(An 8 at the beginning is a secondary indicator that helps Candle Customer
Support determine which routine issued the return code.)
REASON CODE

DESCRIPTION

0004

The CANSM2HD side has reset itself.

0008

CANSM2HD not ready to handle caller.

000C

Error state.

0010

Bad handle detected.

0014

Bad entry code.

0018

SSCVT value already in use.

001C

Unexpected return code from IEFSSREQ.

0020

SSCTSUSE contains zero.

0024

Invalid communication between CANSM2HD and CANSM2.

0028

GETMAIN failed.

002C

GETMAIN failed.

0030

FREEMAIN failed.

0034

Inquire failed.

0038

WAIT failed.

003C

POST failed due to zero ECB pointer.

0040

POST failed due to bad ASCB.

0044

POST failed due to missing ASCB.

0048

SUSE is too small to use.

004C

Not APF authorized.

0080

Invalid handle.

0084

Invalid function code.

0088

GETMAIN failed.

008C

Invalid service number to send.

Candle Products Messages Manual (KLVHS–KONCT)

REASON CODE

DESCRIPTION

0090

Invalid service number received.

0094

STOP command received by wait routine.

0098

Error when STOP command received.

KM2IMPFF

PROFILE IMPORT FAILED
Explanation: The profile import was unable to complete properly due to an
error.
System Action: Profile is not imported from the requested dataset member.
User Response: See the CANSM2 RKLVLOG for a more detailed message
describing the error.

KM2IMP00

PROFILE IMPORT COMPLETED SUCCESSFULLY
Explanation: The profile import was completed successfully.
System Action: Profile is imported from the dataset specified in the command
parameter list.
User Response: None.

KMC0001E

You may only link a single Queue Manager to another Queue Manager.
Explanation: You have attempted to drag multiple Queue Managers and
connect them to a single Queue Manager. This is not supported.
User Response: You must connect Queue Managers by individually dragging
and dropping.

KMC0002E

Your request failed. An unanticipated MQSeries error has occurred
RC=@1 Reason=@2.
Explanation: The MQSeries Queue Manager returned an unanticipated error to
a request from the Configuration Agent. The RC and Reason fields provide the
MQSeries return and reason codes, respectively.
User Response: Look up the return and reason codes in the IBM MQSeries
Application Programming Reference Manual. If necessary, contact Candle
Customer Support.

KMC0003E

Your request failed. Connection to Queue Manager lost.
Explanation: Connection to the Queue Manager from the Configuration Agent
has been lost. This can occur because the Queue Manager has ended.
User Response: Investigate why the Queue Manager connection was broken. If
necessary, restart the Queue Manager and the Configuration Agent.

KMC0004E

Your request failed. Not authorized for MQSeries connection.
Explanation: This reason code occurs only on MVS/ESA. It occurs because the
Configuration Agent is not authorized to connect to the Queue Manager.
User Response: Ensure that the Configuration Agent is authorized to connect
to the Queue Manager.

KM2EXPFF–KMCRCA002I

161

KMC0005E

Your request failed. MQSeries connection shutting down.
Explanation: This reason code occurs only on MVS/ESA. It indicates that the
connection between the Configuration Agent and the Queue Manager is shutting
down.
User Response: Investigate why the Queue Manager connection is shutting
down. If necessary, restart the Queue Manager and the Configuration Agent.

KMC0010E

Your request failed. Message format not valid.
Explanation: The Configuration Agent attempted to get a message with the
MQGMO_CONVERT option included in the GetMsgOpts parameter. One or both
of the CodedCharSetId and Encoding fields in the message differs from the
corresponding field in the MsgDesc parameter, but the message cannot be
converted successfully due to an error associated with the message format.
User Response: Check the format name that was specified when the message
was put. If this is not one of the built-in formats, check that a suitable exit with the
same name as the format is available for the Queue Manager to load. Verify that
the data in the message corresponds to the format expected by the exit.

KMC0011E

Your request failed. Gets inhibited for the queue.
Explanation: The Configuration Agent attempted to get a message from a
queue, but MQGET calls are currently inhibited for the queue. This can result
from the setting of SYSTEM.MQSC.REPLY.QUEUE (for distributed platforms) or
SYSTEM.COMMAND.REPLY.MODEL (on MVS).
User Response: You must manually reset the get inhibited property for the
queue.

KMC0012E

Your request failed. No more MQSeries handles available.
Explanation: The configuration issued an MQOPEN or MQPUT1 call, but the
maximum number of open handles allowed for the agent has already been
reached. Be aware that when a distribution list is specified on the MQOPEN or
MQPUT1 call, each queue in the distribution list uses one handle.
User Response: You must manually change the MAXHANDS property for the
Queue Manager. If the problem persists, contact Candle Customer Support.

KMC0013E

Your request failed. Maximum number of MQSeries connections
reached.
Explanation: The MQCONN call from the Configuration Agent was rejected
because the maximum number of concurrent connections has been exceeded.
User Response: Either increase the size of the appropriate install parameter
value, or reduce the number of concurrent connections.

KMC0015E

Your request failed. MQSeries message too big for channel.
Explanation: The Configuration Agent put a message to a remote queue, but
the message is larger than the maximum message length allowed by the channel.
This can occur for a Queue Manager which is being configured via an indirect
connection.
User Response: Increase the maximum message size of the channel to the
remote Queue Manager.

162

Candle Products Messages Manual (KLVHS–KONCT)

KMC0016E

Your request failed. MQSeries message too big for queue.
Explanation: The Configuration Agent attempted to put a message to a queue,
but the message is larger than the maximum message length allowed by the
queue. This can be caused by the definition for
SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or
SYSTEM.COM.
User Response: Increase the maximum message size of the queue.

KMC0017E

Your request failed. MQSeries message too big for Queue Manager.
Explanation: The Configuration Agent attempted to put a message to a queue,
but the message is larger than the maximum message length allowed by the
Queue Manager.
User Response: You must manually increase the MAXMSGL property for the
Queue Manager.

KMC0018E

Your request failed. An MQOPEN call was issued to create a dynamic
queue, but a queue with the same name as the dynamic queue already
exists.
Explanation: The configuration issued an MQOPEN call to create a dynamic
queue, but a queue with the same name as the dynamic queue already exists.
User Response: Restart the Configuration Agent. Collect the agent log files,
and call Candle Customer Support.

KMC0019E

Your request failed. The Configuration Agent is not authorized for
MQSeries access.
Explanation: The Configuration Agent is not authorized to perform the
operation attempted. If the ’Client userid is defined at Queue Manager’ property is
set for the Queue Manager, the problem could lie with the MQSeries authorities
associated with the user ID.
User Response: If the ’Client userid is defined at Queue Manager’ property is
set, ensure that the user ID has sufficient authority to perform the action. Also
ensure that the Configuration Agent has the required authority.

KMC0020E

Your request failed. MQSeries message data not converted.
Explanation: The configuration made an MQGET call with the
MQGMO_CONVERT option included in the GetMsgOpts parameter, and an error
occurred during conversion of the data in the message.
User Response: Collect the agent log files, and call Candle Customer Support.

KMC0021E

Your request failed. MQSeries object already exists.
Explanation: The Configuration Agent made an MQOPEN call create a
dynamic queue, but a queue with the same name as the dynamic queue already
exists.
User Response: Restart the Configuration Agent. Collect the agent log files,
and call Candle Customer Support.

KM2EXPFF–KMCRCA002I

163

KMC0022E

Your request failed. MQSeries object damaged.
Explanation: The object accessed by the Configuration Agent is damaged and
cannot be used. For example, this may be because the definition of the object in
main storage is not consistent, or because it differs from the definition of the
object on disk, or because the definition on disk cannot be read.
User Response: It may be necessary to stop and restart the Queue Manager, or
to restore the queue-manager data from back-up storage.
On OS/2, OS/400, Tandem NSK, and UNIX systems, consult the FFST record to
obtain more detail about the problem.

KMC0023E

Your request failed. MQSeries object in use.
Explanation: An MQOPEN call was issued by the Configuration Agent, but the
object in question has already been opened by this or another application with
options that conflict with those specified in the Options parameter. This arises if
the request is for shared input, but the object is already open for exclusive input; it
also arises if the request is for exclusive input, but the object is already open for
input (of any sort).
User Response: Restart the Configuration Agent. Collect the agent log files,
and call Candle Customer Support.

KMC0024E

Your request failed. MQSeries pageset error.
Explanation: The Configuration Agent encountered an error with the page set
while attempting to access it for a locally defined queue. This could be because
the queue is on a page set that does not exist. A console message is issued that
tells you the number of the page set in error.
User Response: Check that the storage class for the queue maps to a valid
page set using the DISPLAY Q(xx) STGCLASS, DISPLAY STGCLASS(xx), and
DISPLAY USAGE PSID commands. If you are unable to resolve the problem,
notify the system programmer who should:
1. Collect the following diagnostic information:
® A description of the actions that led to the error.
®

A listing of the application program being run at the time of the error.

Details of the page sets defined for use by MQSeries.

2. Attempt to re-create the problem, and take a system dump immediately after
the error occurs.
3. Contact your IBM Support Center.
KMC0025E

164

Your request failed. MQSeries pageset full.
Explanation: On an MQOPEN, MQPUT or MQPUT1 call from the
Configuration Agent, a page set data set was found to be full while attempting to
open or put a message on a locally defined queue.
This reason code occurs only on MVS/ESA.
User Response: Check which queues contain messages and look for any
looping programs that might be unnecessarily filling up queues. Otherwise,
request the system programmer to increase the size of the page set data sets.

Candle Products Messages Manual (KLVHS–KONCT)

KMC0026E

Your request failed. MQSeries queue is put inhibited.
Explanation: The Configuration Agent attempted to get a message from a
queue, but MQGET calls are currently inhibited for the queue. This can be caused
by the definition for SYSTEM.ADMIN.COMMAND.QUEUE (for distributed
platforms) or SYSTEM.COMMAND.INPUT (for MVS). This can also be caused by
the definition of SYSTEM.MQSC.REPLY.QUEUE (for distributed platforms), or
SYSTEM.COMMAND.REPLY.MODEL (for MVS).
User Response: You must manually reset the put inhibited property for the
queue.

KMC0028E

Your request failed. MQSeries queue deleted.
Explanation: The Configuration Agent attempted to refer to a dynamic queue
that has been deleted since the queue was opened.
User Response: Restart the Configuration Agent. Collect the agent log files,
and call Candle Customer Support.

KMC0029E

Your request failed. MQSeries queue is full.
Explanation: The Configuration Agent attempted to put a message into a
queue, but the maximum number of messages in the queue had already been
reached. This can be caused by the definition for
SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or
SYSTEM.COMMAND.INPUT (for MVS).
User Response: You must manually reset the MAXMSGS property for the
queue. This problem can also occur if the MQSeries Command Server or a
Sender or Server channel stops running.

KMC0031E

Your request failed. MQSeries Queue Manager not active.
Explanation: The Configuration Agent could not connect to the Queue
Manager because the Queue Manager is not active.
User Response: Start the Queue Manager.

KMC0032E

Your request failed. MQSeries Queue Manager not available.
Explanation: The Configuration Agent could not connect to the Queue
Manager because it is not available for connection at this time.
User Response: Ensure that the Queue Manager has been started.

KMC0033E

Your request failed. MQSeries Queue Manager quiescing.
Explanation: The Configuration Agent could not communicate with the Queue
Manager because the Queue Manager is in the quiescing state.
User Response: Wait until the Queue Manager has stopped, then restart the
Queue Manager and the Configuration Agent and restart the request.

KMC0034E

Your request failed. MQSeries Queue Manager stopping.
Explanation: The Configuration Agent could not communicate with the Queue
Manager because the Queue Manager is currently shutting down.
User Response: Wait until the Queue Manager has stopped, then restart the
Queue Manager and the Configuration Agent and restart the request.

KM2EXPFF–KMCRCA002I

165

KMC0035E

Your request failed. No space available for MQSeries queue.
Explanation: The Configuration Agent attempted to put a message to an
MQSeries queue, but there is no space available for the queue on disk or other
storage device.
User Response: Make more disk space available for the queue.

KMC0036E

Your request failed. Insufficient MQSeries system resource available.
Explanation: MQSeries has insufficient system resources to complete the
request successfully.
User Response: Run the application when the machine is less heavily loaded.
On OpenVMS, OS/2, OS/400, Tandem NSK, and UNIX systems, consult the
FFST record to obtain more detail about the problem.

KMC0037E

Your request failed. MQSeries security error.
Explanation: The Configuration Agent issued an MQCONN, MQOPEN,
MQPUT1, or MQCLOSE call, but it failed because a security error occurred. On
MVS/ESA, the security error was returned by the External Security Manager.
User Response: Note the error from the security manager, and contact your
system programmer or security administrator. On OS/400, the FFST log will
contain the error information.

KMC0038E

Your request failed. MQSeries coded character set id invalid.
Explanation: The configuration attempted to get a message from an MQSeries
queue, but the coded character-set identifier from which character data is to be
converted is not valid or not supported.
User Response: Check the character-set identifier that was specified when the
message was put, or that was specified for the SourceCCSID parameter on the
MQXCNVC call. If this is correct, check that it is one for which queue-manager
conversion is supported.

KMC0039E

Your request failed. Integer encoding in MQSeries message not
recognized.
Explanation: On an MQGET call issued by the Configuration Agent, with the
MQGMO_CONVERT option included in the GetMsgOpts parameter, the
Encoding value in the message being retrieved specifies an integer encoding that
is not recognized.
User Response: Check the integer encoding that was specified when the
message was put. If this is correct, check that it is one for which queue-manager
conversion is supported.

KMC0040E

Your request failed. Insufficient MQSeries storage available.
Explanation: A call from the Configuration Agent cannot complete because
sufficient storage is not available to the Queue Manager.
User Response: Make more storage available. On MVS/ESA, if no application
problems are found, ask your systems programmer to increase the size of the
region in which the Queue Manager runs.

166

Candle Products Messages Manual (KLVHS–KONCT)

KMC0041E

Your request failed. Unexpected MQSeries error. The call was rejected
because an unexpected error occurred.
Explanation: The request was rejected because an unexpected error occurred
with MQSeries.
User Response: On MVS/ESA, check whether any information has been
displayed on the console. If this error occurs on an MQCONN call, check that the
subsystem named is an active MQ subsystem. In particular, check that it is not a
DB2 subsystem. If the problem cannot be recreated, contact your system
programmer.

KMC0045E

Your request failed. Unknown MQSeries queue name.
Explanation: The queue name is unknown.
User Response: Specify a valid queue name.

KMC0047E

Your request failed. Unknown MQSeries transmission queue.
Explanation: On an MQOPEN or MQPUT1 call issued by the Configuration
Agent, a message is to be sent to a remote Queue Manager. The ObjectName or
the ObjectQMgrName in the object descriptor specifies the name of a local
definition of a remote queue (in the latter case).
User Response: Ensure that the definition of the remote queue is correct and
that the XMITQ specifies the name of a valid local transmit queue.

KMC0048E

Your request failed. MQSeries transmission queue not local.
Explanation: On an MQOPEN or MQPUT1 call issued by the Configuration
Agent, a message is to be sent to a remote Queue Manager. The ObjectName or
ObjectQMgrName field in the object descriptor specifies the name of a local
definition of a remote queue but one of the following applies to the XmitQName
attribute of the definition:
® XmitQName is not blank, but specifies a queue that is not a local queue.
®

XmitQName is blank, but RemoteQMgrName specifies a queue that is not a
local queue.

User Response: Ensure that the definition of the remote queue is correct and
that the XMITQ specifies the name of a valid local transmit queue.
KMC0049E

Your request failed. MQSeries transmission queue has incorrect usage.
Explanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a
remote Queue Manager, but one of the following occurred:
® ObjectQMgrName specifies the name of a local queue, but it does not have a
Usage attribute of MQUS_TRANSMISSION. The ObjectName or
ObjectQMgrName field in the object descriptor specifies the name of a local
definition of a remote queue but one of the following applies to the
XmitQName attribute of the definition:
®

XmitQName is not blank, but specifies a queue that does not have a Usage
attribute of MQUS_TRANSMISSION.

XmitQName is blank, but RemoteQMgrName specifies a queue that does not
have a Usage attribute of MQUS_TRANSMISSION.

KM2EXPFF–KMCRCA002I

167

The queue name is resolved through a cell directory, and the remote Queue
Manager name obtained from the cell directory is the name of a local queue,
but it does not have a Usage attribute of MQUS_TRANSMISSION.

User Response: Ensure that the definition of the remote queue is correct and
that the XMITQ specifies the name of a valid local transmit queue.
KMC0067E

Your request failed. MQSeries channel type invalid.
Explanation: The channel type associated with this channel is invalid.
User Response: Ensure that the channel type is valid for the target platform.

KMC0069E

Your request failed. MQSeries transmit protocol type invalid.
Explanation: The transmit protocol specified on the channel definition is
invalid.
User Response: Ensure that the transmit protocol type is valid for the target
platform.

KMC0070E

Your request failed. MQSeries batch size invalid.
Explanation: The batch size specified for the channel is not valid.
User Response: Correct the batch size. The value must be greater than zero,
and less than or equal to 9999.

KMC0071E

Your request failed. MQSeries disconnect interval invalid.
Explanation: The disconnect interval specified for the channel is not valid.
User Response: Correct the disconnect interval. The value must be greater
than or equal to zero, and less than or equal to 999,999.

KMC0072E

Your request failed. MQSeries short retry count invalid.
Explanation: The short retry count specified for the channel is not valid.
User Response: Correct the short retry count. The value must be greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0073E

Your request failed. MQSeries short timer value invalid.
Explanation: The short interval specified for the channel is not valid.
User Response: Correct the short interval. The value must be greater than or
equal to zero, and less than or equal to 999,999,999.

KMC0074E

Your request failed. MQSeries long retry count invalid.
Explanation: The long retry count specified for the channel is not valid.
User Response: Correct the long retry count. The value must be greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0075E

Your request failed. MQSeries long timer value invalid.
Explanation: The long interval specified for the channel is not valid.
User Response: Correct the long interval. The value must be greater than or
equal to zero, and less than or equal to 999,999,999.

KMC0076E

Your request failed. MQSeries sequence number wrap invalid.
Explanation: The sequence number wrap specified for the channel is not valid.
User Response: Correct the sequence number wrap. The value must be
greater than or equal to 100, and less than or equal to 999,999,999.

168

Candle Products Messages Manual (KLVHS–KONCT)

KMC0077E

Your request failed. MQSeries maximum message length invalid.
Explanation: The maximum message length specified for the queue or channel
is not valid.
User Response: Correct the maximum message length. On AIX, HP-UX, OS/2
Warp, Sun Solaris, and Windows NT, specify a value greater than or equal to zero,
and less than or equal to the maximum message length for the Queue Manager.
On other platforms, specify a value greater than 0, and less than or equal to
4,194,304.

KMC0078E

Your request failed. MQSeries put authority invalid.
Explanation: The put authority specified for the channel is not valid.
User Response: Correct the put authority.

KMC0081E

Your request failed. MSSeries message truncated.
Explanation: The command server received a message from the Configuration
Agent that is larger than its maximum valid message size.
User Response: Ensure that the MAXMSGL property of the
SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or
SYSTEM.COMMAND.INPUT (for MVS) is large enough.

KMC0084E

Your request failed. MQSeries data conversion value invalid.
Explanation: The convert property specified for the channel is not valid.
User Response: Correct the convert property.

KMC0088E

Your request failed. MQSeries MCA type invalid.
Explanation: The message channel agent type specified for the channel is
invalid.
User Response: Correct the message channel agent type.

KMC0092E

Your request failed. MQSeries like object has wrong type.
Explanation: An attempt was made to create an object based on the definition
of an existing object, but the new and existing objects had different types. This can
result from the incorrect definition of the IBM MQSeries default resources.
User Response: Ensure that the IBM-provided default resources for the actual
Queue Manager are valid.

KMC0093E

Your request failed. MQSeries object is open. An attempt was made to
delete or change an object that was in use.
Explanation: An attempt was made to delete or change an object that was in
use.
User Response: Wait until the object is no longer in use, then retry the
operation.

KM2EXPFF–KMCRCA002I

169

KMC0097E

Your request failed. MQSeries object name not valid.
Explanation: You attempted to create a new resource with an invalid name.
User Response: Ensure that the name is valid for the type of object. The
character set that can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Percent sign (%). The percent sign (%) is a special character to RACF®. If you
are using RACF as the external security manager for MQSeries for OS/390,
you should not use % in object names. If you do, these names are not
included in any security checks when RACF generic profiles are used.

KMC0098E

Your request failed. MQSeries allocation failed. An attempt to allocate a
conversation to a remote system failed.
Explanation: An attempt by MQSeries to allocate a conversation to a remote
system failed. The error may be due to an invalid entry in the channel definition,
or it may be that the listening program at the remote system is not running.
User Response: Ensure that the channel definition is correct, and start the
listening program if necessary. If the error persists, consult your MQSeries systems
administrator.

KMC0099E

Your request failed. MQSeries remote system not available.
Explanation: An attempt by MQSeries to allocate a conversation to a remote
system was unsuccessful. The error may be transitory, and the allocate may
succeed later. This reason can occur if the listening program at the remote system
is not running.
User Response: Ensure that the listening program is running, and retry the
operation.

170

Candle Products Messages Manual (KLVHS–KONCT)

KMC0100E

Your request failed. MQSeries channel configuration error.
Explanation: A configuration error was detected in the channel definition or
communication subsystem, and allocation of a conversation was not possible.
This may be caused by one of the following:
® For LU 6.2, either the ModeName or the TpName is incorrect. The
ModeName must match that on the remote system, and the TpName must be
specified. (On OS/400, these are held in the communications Side Object.)
®

For LU 6.2, the session may not be established.

For TCP, the ConnectionName in the channel definition cannot be resolved to
a network address. This may be because the name has not been correctly
specified, or because the name server is not available.

The requested communications protocol may not be supported on the platform.
User Response: Identify the error and take appropriate action.
KMC0101E

Your request failed. MQSeries connection refused.
Explanation: The attempt by MQSeries to establish a connection to a remote
system was rejected. The remote system might not be configured to allow a
connection from this system.
® For LU 6.2 either the user ID or the password supplied to the remote system is
incorrect.
®

For TCP the remote system may not recognize the local system as valid, or the
TCP listener program may not be started.

User Response: Correct the error or restart the listener program.
KMC0102E

Your request failed. MQSeries connection name invalid.
Explanation: The connection name in the channel definition could not be
resolved into a network address. Either the name server does not contain the
entry, or the name server was not available.
User Response: Ensure that the connection name is correctly specified and
that the name server is available.

KMC0103E

Your request failed. MQSeries send failed.
Explanation: An error occurred while MQSeries was sending data to a remote
system. This may be caused by a communications failure.
User Response: Consult your MQSeries systems administrator.

KMC0104E

Your request failed. MQSeries received data error.
Explanation: An error occurred while receiving data from a remote system. This
may be caused by a communications failure.
User Response: Consult your MQSeries systems administrator.

KMC0107E

Your request failed. Insufficient MQSeries storage available.
Explanation: Insufficient storage is available for MQSeries.
User Response: Consult your MQSeries systems administrator.

KM2EXPFF–KMCRCA002I

171

KMC0108E

Your request failed. Communication manager not available for
MQSeries.
Explanation: The MQSeries communications subsystem is not available.
User Response: Ensure that the MQSeries communications subsystem has
been started.

KMC0109E

Your request failed. MQSeries bind failed.
Explanation: The bind to a remote system by MQSeries during session
negotiation has failed.
User Response: Consult your MQSeries systems administrator.

KMC0110E

Your request failed. MQSeries channel in-doubt.
Explanation: The requested operation cannot complete because the MQSeries
channel is in doubt.
User Response: Examine the status of the channel, and either restart a channel
to resolve the in-doubt state, or resolve the channel.

KMC0111E

Your request failed. MQSeries channel in use.
Explanation: An attempt was made to perform an operation on an MQSeries
channel, but the channel is currently active.
User Response: Stop the channel or wait for it to terminate, then retry the
operation.

KMC0112E

Your request failed. MQSeries channel not found.
Explanation: You attempted an operation on an MQSeries channel, but the
channel doesn’t exist in the actual configuration.
User Response: Create the channel by performing an Update Actual from
Defined, then re-try the operation.

KMC0113E

Your request failed. Unknown remote MQSeries channel.
Explanation: There is no definition of the referenced channel at the remote
system.
User Response: Ensure that the local channel is correctly defined. If it is, add
an appropriate channel definition at the remote system.

KMC0114E

Your request failed. Remote MQSeries Queue Manager not available.
Explanation: The channel cannot be started because the remote Queue
Manager is not available.
User Response: Start the remote Queue Manager, then retry the operation.

KMC0115E

Your request failed. Remote MQSeries Queue Manager terminating.
Explanation: The channel is ending because the remote Queue Manager is
terminating.
User Response: Restart the remote Queue Manager, then retry the operation.

172

Candle Products Messages Manual (KLVHS–KONCT)

KMC0117E

Your request failed. MQSeries queue is not a transmission queue.
Explanation: The queue specified in the channel definition is not a transmission
queue.
User Response: Ensure that the queue is specified correctly in the channel
definition, and that it is correctly defined to the Queue Manager. Retry the
operation.

KMC0120E

Your request failed. MQSeries channel name invalid.
Explanation: You attempted to create a new channel with an invalid name.
User Response: Ensure that the channel name is valid for the type of object.
The character set that can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z

KMC0121E

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Your request failed. MQSeries transmission queue name invalid.
Explanation: You specified an invalid Transmit queue name for this channel.
User Response: Ensure that the queue name is valid for the type of object. The
character set that can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KM2EXPFF–KMCRCA002I

173

KMC0123E

KMC0124E

KMC0125E

174

Your request failed. MQSeries channel send exit name invalid.
Explanation: The Send exit name specified for the channel contained
characters that are not allowed for program names on the platform in question.
User Response: Specify a valid name for the send exit. The format and
maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.
®

On OS/400, it is of the form progname libname, where progname occupies
the first 10 characters, and libname the second 10 characters (both
blank-padded to the right if necessary). The maximum length of the string is
20 characters.

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

Your request failed. MQSeries channel security exit name invalid.
Explanation: The Security exit name specified for the channel contained
characters that are not allowed for program names on the platform in question.
User Response: Specify a valid name for the security exit. The format and
maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.
®

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

Your request failed. MQSeries channel message exit name invalid.
Explanation: The Message exit name specified for the channel contained
characters that are not allowed for program names on the platform in question.
User Response: Specify a valid name for the message exit.
The format and maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.
®

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

Candle Products Messages Manual (KLVHS–KONCT)

KMC0126E

Your request failed. MQSeries channel receive exit name invalid.
Explanation: The Receive exit name specified for the channel contained
characters that are not allowed for program names on the platform in question.
User Response: Specify a valid name for the receive exit. The format and
maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.
®

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

KMC0135E

Your request failed. Missing MQSeries connection name.
Explanation: The Connection Name property is required for sender or requester
channel types, but is not present.
User Response: Specify the Connection Name for the channel.

KMC0136E

Your request failed. MQSeries connection name invalid.
Explanation: The Connection Name property contains one or more blanks at
the start of the name.
User Response: Specify a valid connection name for the channel. The value
you specify depends on the transport type (TRPTYPE) to be used:

KM2EXPFF–KMCRCA002I

175

LU 6.2

On OS/390 there are two forms in which to specify the value:
® Logical unit name
The logical unit information for the Queue Manager, comprising the
logical unit name, TP name, and optional mode name. This can be
specified in one of 3 forms:
Form: Example
– luname: IGY12355
– luname/TPname: IGY12345/APING
– luname/TPname/modename: IGY12345/APINGD/#INTER
For the first form, the TP name and mode name must be specified for
the TPNAME and MODENAME attributes; otherwise these attributes
must be blank.
® Symbolic name
The symbolic destination name for the logical unit information for the
Queue Manager, as defined in the side information data set. The
TPNAME and MODENAME attributes must be blank.
Note: For cluster-receiver channels, the side information is on the
other Queue Managers in the cluster. Alternatively, in this case it can be
a name that a channel auto-definition exit can resolve into the
appropriate logical unit information for the local Queue Manager.
On OS/2 Warp it is the fully-qualified name of the partner LU, or an LU
alias. On OS/400, Windows NT, and UNIX systems, this is the name of
the CPI-C communications side object or, if the TPNAME is not blank,
this is the fully-qualified name of the partner logical unit.
See the information about configuration parameters for an LU 6.2
connection for your platform in the MQSeries Intercommunication
manual for more information.

NetBIOS

A unique NetBIOS name (limited to 16 characters).

SPX

The 4-byte network address, the 6-byte node address, and the 2-byte
socket number. These values must be entered in hexadecimal, with a
period separating the network and node addresses. The socket number
must be enclosed in brackets, for example:
CONNAME(’0a0b0c0d.804abcde23a1(5e86)’).
If the socket number is omitted, the MQSeries default value (X'5e86') is
assumed.

TCP

Either the host name, or the network address of the remote machine
(or the local machine for cluster-receiver channels). This can be
followed by an optional port number, enclosed in parentheses.
This parameter is required for channels with a channel type
(CHLTYPE) of SDR, RQSTR, CLNTCONN, CLUSSDR, and
CLUSRCVR. It is optional for SVR channels, and is not valid for RCVR
or SVRCONN channels.

Note: If you are using any of the special characters in your connection name (for
example, parentheses) you must enclose the string in single quotes.

176

Candle Products Messages Manual (KLVHS–KONCT)

KMC0137E

Your request failed. MQSeries MQSET failed.
Explanation: MQSeries MQSET call failed.
User Response: Check whether the Queue Manager is active.

KMC0138E

Your request failed. MQSeries channel not active.
Explanation: An attempt was made to stop an MQSeries channel, but the
channel was already stopped.
User Response: None.

KMC0139E

Your request failed. MQSeries channel terminated by security exit.
Explanation: A channel security exit terminated the MQSeries channel.
User Response: Check that the channel is attempting to connect to the correct
Queue Manager, and if so that the security exit is specified correctly, and is
working correctly, at both ends.

KMC0141E

Your request failed. MQSeries cell directory not available.
Explanation: The Scope property of the queue is to be CELL, but no name
service supporting a cell directory has been configured.
User Response: Configure the Queue Manager with a suitable name service.

KMC0142E

Your request failed. MQSeries message retry count not valid.
Explanation: The message retry count specified for the channel is not valid.
User Response: Correct the message retry count. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0144E

Your request failed. MQSeries message retry exit name invalid.
Explanation: The message retry exit name specified for the channel contained
characters that are not allowed for program names on the platform in question.
User Response: Specify a valid name for the receive exit. The format and
maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.

KMC0146E

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

Your request failed. MQSeries message retry interval invalid.
Explanation: The message retry interval specified for the channel is not valid.
User Response: Correct the message retry interval. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KM2EXPFF–KMCRCA002I

177

KMC0148E

Your request failed. MQSeries cluster queue cannot be a transmission
queue.
Explanation: The request was rejected by MQSeries because it would have
resulted in a cluster queue also being a transmission queue. This is not supported.
User Response: Ensure that the configuration specifies either:
® Usage Normal.
®

The Cluster Name and Cluster Namelist properties with values of blanks.

KMC0149E

Your request failed. MQSeries ClusterName and ClusterNamelist
attributes conflict.
Explanation: The request was rejected because it would have resulted in the
Cluster Name property and the Cluster Namelist property both being nonblank.
At least one of these properties must be blank.
User Response: Specify either a blank Cluster Name, or a blank Cluster
Namelist for the object.

KMC0150E

Your request failed. MQSeries Channel Status not found.
Explanation: You attempted to view the status of an MQSeries channel.
However, no channel status is available for the specified channel. This may
indicate that the channel has not been used.
User Response: None, unless this is unexpected, in which case consult your
MQSeries systems administrator.

KMC0151E

You cannot move cluster managed object @1 into a non-cluster
managed object @2.
Explanation: You are attempting to move cluster-generated object @1 into
non-cluster-generated object @2. This is not supported.
User Response: You can only move a cluster-generated object into another
cluster-generated object.

KMC0152E

Your request failed. MQSeries Queue contains one or more messages or
uncommitted put or get requests.
Explanation: You attempted to delete an MQSeries queue that is not empty.
User Response: Ensure that the queue you wish to delete does not contain any
messages. Retry the request.

KMC0153E

The Queue Manager is already a member of this cluster.
Explanation: You have attempted to make a Queue Manager participate in a
managed cluster by dragging and dropping the Queue Manager to the cluster.
However, the Queue Manager in question is already participating in the cluster.
User Response: None.

178

Candle Products Messages Manual (KLVHS–KONCT)

KMC0155E

This Queue Manager is not at the proper MQSeries version to support
cluster participation.
Explanation: You have attempted to make a Queue Manager participate in a
managed cluster by dragging and dropping the Queue Manager to the cluster.
However, the Queue Manager in question is not at the proper MQSeries version
to support clustering. For a Queue Manager to participate in a cluster, it must be
at least at version 5.1 (distributed platforms) or 2.1 (MVS).
User Response: Upgrade the MQSeries software to the proper version.

KMC0156E

You cannot delete Queue Manager @4 because is it still active.
Explanation: You are attempting to delete an actual Queue Manager. However,
the Queue Manager cannot be deleted because it is still active.
User Response: Select the Action option on the popup menu for the Queue
Manager, then select the Stop option, in order to stop the Queue Manager. Retry
the delete request once the Queue Manager has been successfully stopped.

KMC0157E

The Configuration Agent was unable to delete Queue Manager @4.
Explanation: You are attempting to delete an actual Queue Manager. However,
the Queue Manager cannot be deleted by the Configuration Agent.
User Response: Examine the agent and CMS log files to determine why the
Queue Manager could not be deleted.

KMC0158E

You cannot delete an actual Queue Manager on this platform.
Explanation: You are attempting to delete an actual Queue Manager on a
platform in which Queue Manager delete is not supported. Queue manager delete
is not supported for Queue Managers running on MVS.
User Response: None.

KMC0159E

The actual Queue Manager does not exist.
Explanation: You are attempting to delete an actual Queue Manager; however,
the actual Queue Manager does not exist.
User Response: None.

KMC0160E

You cannot stop the Queue Manager because there are pending
configuration requests.
Explanation: You are attempting to stop a Queue Manager; however, the agent
currently has pending configuration requests with the Queue Manager.
User Response: Wait until all pending configuration requests have completed
with this Queue Manager, then retry the request.

KMC0161E

You cannot stop an indirectly-connected Queue Manager.
Explanation: You are attempting to stop a Queue Manager which is defined as
an indirect connection; this is not supported.
User Response: You must manually stop an indirectly-connected Queue
Manager.

KMC0162E

The Queue Manager is not active.
Explanation: You are attempting to stop a Queue Manager; however, the
Queue Manager is not currently active.
User Response: None.

KM2EXPFF–KMCRCA002I

179

KMC0163E

Your request to stop the Queue Manager failed.
Explanation: You are attempting to stop a Queue Manager. However, the
Queue Manager cannot be stopped by the Configuration Agent.
User Response: Examine the agent and CMS log files to determine why the
Queue Manager could not be stopped.

KMC0164W

The MQSeries Queue Manager is already running.
Explanation: You are attempting to start a Queue Manager. However, the
Queue Manager is already active.
User Response: None.

KMC0165S

An invalid action code was detected by the Configuration Agent.
Explanation: An unsupported action request was sent to the Configuration
Agent by the Configuration Manager.
User Response: Collect the agent and CMS log files, and call Candle Customer
Support.

KMC0166S

A failure occurred in the MQSeries DSPMQFLS command.
Explanation: The Configuration Agent issued the MQSeries DSPMQFLS
command to obtain the name of the authorization file for the object; however, the
DSPMQFLS command failed.
User Response: Investigate why the DSPMQFLS command failed by
examining the agent and CMS log files. If the problem persists, call Candle
Customer Support.

KMC0167E

The Configuration Agent was unable to find the authorization file name
in the output from DSPMQFLS.
Explanation: The Configuration Agent issued the MQSeries DSPMQFLS
command to obtain the name of the authorization file for the object; however, the
agent was unable to determine the name of the authorization file from the output
from DSPMQFLS.
User Response: Investigate why the DSPMQFLS command failed by
examining the agent and CMS log files. It may be necessary to manually enter the
DSPMQFLS command and view the output. If the problem persists, call Candle
Customer Support.

KMC0168E

The MQSeries authorization filename as reported by DSPMQFLS is in an
incorrect format.
Explanation: The Configuration Agent issued the MQSeries DSPMQFLS
command to obtain the name of the authorization file for the object; however, the
file name as reported by DSPMQFLS is in an incorrect format, and cannot be
located.
User Response: Investigate why the DSPMQFLS command failed by
examining the agent and CMS log files. It may be necessary to manually enter the
DSPMQFLS command and view the output. If the problem persists, call Candle
Customer Support.

180

Candle Products Messages Manual (KLVHS–KONCT)

KMC0169E

The Configuration Agent was unable to open the MQSeries authorization
file.
Explanation: The Configuration Agent was unable to open the MQSeries
authorization file for the object in question.
User Response: Ensure that the authorization file for the MQSeries object
exists, and that the Configuration Agent has read access to this file. Review the
topic "Authorization Files" in the "Protecting MQSeries Objects" chapter of the
appropriate MQSeries System Administration Guide.

KMC0170E

The MQSeries authorization file is in an incorrect format.
Explanation: The Configuration Agent attempted to read the MQSeries
authorization file for the object in order to determine the object’s authorization
properties; however, the authorization file is in an incorrect format.
User Response: Ensure that the authorization file for the MQSeries object is in
the correct. Review the topic "Authorization Files" in the "Protecting MQSeries
Objects" chapter of the appropriate MQSeries System Administration manual for
more information. If the problem persists, contact Candle Customer Support.

KMC0171E

MQSeries authorization configuration is not supported on this platform.
Explanation: You attempted to configure authorization properties for a Queue
Manager that is running on a platform for which authorization properties are not
supported. Currently, authorization properties are only supported on Windows
NT and UNIX platforms.
User Response: Deselect the ’Configure MQSeries authorization’ option on the
Auto Start page of the Queue Manager settings.

KMC0172E

An error occurred processing the SETMQAUT command.
Explanation: The Configuration Agent issued the MQSeries SETMQAUT
command to modify the authorization properties of the object; however, the
SETMQAUT command failed.
User Response: Investigate why the SETMQAUT command failed by
examining the agent and CMS log files. If the problem persists, call Candle
Customer Support.

KMC0173E

An authorization principal or group name was invalid.
Explanation: The authorization page for the object specified the name of a
principal or group which does not exist.
User Response: Correct the authorization page for the object and retry the
request.

KMC0174E

An invalid MQSeries command argument was detected.
Explanation: The Configuration Agent passed a bad argument to the
SETMQAUT command.
User Response: Collect the agent and CMS log files, and call Candle Customer
Support.

KM2EXPFF–KMCRCA002I

181

KMC0175S

An unexpected error occurred on a SETMQAUT command.
Explanation: An internal MQSeries error occurred during the processing of the
SETMQAUT command.
User Response: Attempt to enter the SETMQAUT command manually for the
object. If the problem persists, contact IBM customer support.

KMC0176S

The Queue Manager has insufficient disk space to process MQSeries
command.
Explanation: The MQSeries SETMQAUT command cannot be completed due
to shortage of disk space.
User Response: Make more disk space available to MQSeries.

KMC0177S

The MQSeries authorization file has a bad stanza - SETMQAUT could not
be processed.
Explanation: The MQSeries SETMQAUT command failed because the
authority file contains an authority stanza that is not valid.
User Response: Correct the contents of the incorrect authorization file by
editing it. Review the topic "Authorization Files" in the "Protecting MQSeries
Objects" chapter of the appropriate MQSeries System Administration manual for
more information.

KMC0178S

The Configuration Agent has insufficient authority to process the
SETMQAUT command.
Explanation: The Configuration Agent does not have the proper authority to
issue the SETMQAUT command for the object.
User Response: Ensure that the Configuration Agent is running with sufficient
authority to issue the SETMQAUT command.

KMC0179E

Your request failed. The Configuration Agent has reached the maximum
number of Queue Manager connections on this platform type.
Explanation: You issued a request that would have caused the Configuration
Agent to connect with a Queue Manager; however, the agent is already connected
to the maximum number of Queue Managers allowed for the platform. On
Tandem NSK and AS/400, only one queue manager.
User Response: Restart the Configuration Agent and retry the request.

KMC0180E

MQSeries namelists are not supported on this platform.
Explanation: You attempted to create a new MQSeries namelist; however,
namelists are not supported on this platform and/or MQSeries version. Namelists
are supported on:
® Queue managers running on MVS
®

Queue managers running on distributed systems at version 5.1 of MQSeries

User Response: Delete the defined namelist objects, or upgrade to a version of
MQSeries which supports namelists.

182

Candle Products Messages Manual (KLVHS–KONCT)

KMC0181E

MQSeries storage classes are not supported on this platform.
Explanation: You attempted to create a new MQSeries storage class, however,
storage classes are not supported on this platform. Namelists are supported on
MVS only.
User Response: Delete the defined storage class objects.

KMC0182E

Your request failed. The Configuration Agent was unable to create the
Queue Manager.
Explanation: You attempted to create a new actual Queue Manager; however,
the CRTMQM command issued by the Configuration Agent failed.
User Response: Investigate why the CRTMQM command failed by examining
the agent and CMS log files. If necessary, issue the CRTMQM command
manually. If the problem persists, call Candle Customer Support.

KMC0183E

Your request failed. The Configuration Agent was unable to start the
Queue Manager.
Explanation: You attempted to start a Queue Manager; however, the STRMQM
command issued by the Configuration Agent failed.
User Response: Investigate why the STRMQM command failed by examining
the agent and CMS log files. If necessary, issue the STRMQM command manually.
If the problem persists, call Candle Customer Support.

KMC0184E

Your request failed. The Configuration Agent was unable to start the
MQSeries Command Server.
Explanation: You attempted to start a Queue Manager; however, the
STRMQCSV command issued by the Configuration Agent failed.
User Response: Investigate why the STRMQCSV command failed by
examining the agent and CMS log files. If necessary, issue the STRMQCSV
command manually. If the problem persists, call Candle Customer Support.

KMC0185E

Your request failed. The Configuration Agent was unable to connect with
the Queue Manager.
Explanation: The Configuration Agent attempted to connect with the Queue
Manager; however, the MQCONN request failed.
User Response: If you were attempting to create a new queue manager by
performing the actual Update from the defined operation, ensure that the Auto
create checkbox is selected (in the Auto Create section of the queue manager
settings). Otherwise, investigate why the MQCONN failed by examining the agent
and CMS log files. If the problem persists, call Candle Customer Support.

KMC0186E

Your request failed. The Configuration Agent was unable to create the
IBM default resources on the Queue Manager.
Explanation: You attempted to create a new actual Queue Manager; however,
the Configuration Agent was unable to create the IBM-provided default resources.
User Response: Investigate why the agent was unable to create the IBM default
resources by examining the agent and CMS log files. If necessary, create the
default resources manually. If the problem persists, call Candle Customer Support.

KM2EXPFF–KMCRCA002I

183

KMC0187E

Your request failed. The Configuration Agent was unable to open the
MQSeries reply-to queue.
Explanation: The Configuration Agent attempted to connect with the Queue
Manager; however, the agent was unable to open the Reply-to queue used to
communicate with the MQSeries command server.
User Response: Investigate why the agent was unable to open the queue by
examining the agent and CMS log files. If the problem persists, call Candle
Customer Support.

KMC0188E

Your request failed. The Configuration Agent was unable to open the
MQSeries command queue.
Explanation: The Configuration Agent attempted to connect with the Queue
Manager; however, the agent was unable to open the MQSeries command queue
used to communicate with the MQSeries command server. This can be caused by
the definition for SYSTEM.ADMIN.COMMAND.QUEUE.
User Response: Investigate why the agent was unable to open the queue by
examining the agent and CMS log files. Check the definition of
SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or
SYSTEM.COMMAND.INPUT (for MVS). If the problem persists, call Candle
Customer Support.

KMC0189E

Your request failed. The Configuration Agent was unable to perform an
MQINQ request for the MQSeries command queue.
Explanation: The Configuration Agent attempted to connect with the Queue
Manager; however, the agent was unable to perform an MQINQ request against
the MQSeries command queue used to communicate with the MQSeries
command server. This can be caused by the definition of the
SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or the
SYSTEM.COMMAND.INPUT queue (for MVS).
User Response: Investigate why the agent was unable to perform an MQINQ
against the queue by examining the agent and CMS log files. Check the definition
of SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or
SYSTEM.COMMAND.INPUT (for MVS). If the problem persists, contact Candle
Customer Support.

KMC0190E

Your request failed. The Configuration Agent cannot communicate with
the Queue Manager because the command server is not active.
Explanation: The Configuration Agent attempted to connect with the Queue
Manager; however, the agent determined that the MQSeries Command Server is
not currently active.
User Response: Manually start the MQSeries Command Server by issuing the
STRMQCSV command on the target system. Retry the request.

184

Candle Products Messages Manual (KLVHS–KONCT)

KMC0191E

Your request failed. The Configuration Agent could not establish
communication with the remote MQSeries Queue Manager.
Explanation: The Configuration Agent attempted to connect with an
indirectly-connected Queue Manager; however, the agent did not receive a
response from the Queue Manager.
User Response: Ensure that the indirectly-connected Queue Manager is active,
and that all channels used for bi-directional communication with the ’Through’
Queue Manager are running. Check the definitions of all channels, transmit
queues, and (if specified) remote queues.

KMC0192E

MQSeries processes are not supported on this platform.
Explanation: You attempted to create an actual MQSeries process; however,
processes are not supported on this platform and/or MQSeries version. Processes
are not supported on MQSeries Version 2.1 for Windows.
User Response: Delete the defined process objects.

KMC0193E

MQSeries server connection channels are not supported on this
platform.
Explanation: You attempted to create an actual MQSeries server connection
channel; however, server connection channels are not supported on this platform
and/or MQSeries version. Server connection channels are not supported on
MQSeries Version 2.1 for Windows.
User Response: Delete the defined server connection channel objects.

KMC0194E

Your request failed. The Configuration Agent is unable to create the
Queue Manager with this version of MQSeries.
Explanation: You attempted to create an actual Queue Manager; however,
Queue Manager create is not supported on this platform and/or MQSeries
version. The Configuration Agent cannot create Queue Managers on MVS or on
MQSeries Version 2.1 for Windows.
User Response: Create the Queue Manager manually.

KMC0195E

Your request failed. The Configuration Agent is unable to start the
Queue Manager with this version of MQSeries.
Explanation: You attempted to start a Queue Manager; however, Queue
Manager start is not supported on this platform and/or MQSeries version. The
Configuration Agent cannot start Queue Managers on MVS or on MQSeries
Version 2.1 for Windows.
User Response: Start the Queue Manager manually.

KMC0196E

Cluster sender channels are not supported on this version of MQSeries.
Explanation: You attempted to create an actual cluster sender channel.
However, the Queue Manager in question is not at the proper MQSeries version
to support clustering. For a Queue Manager to participate in a cluster, MQSeries
must be at least at the 5.1 version (for distributed platforms) or the 2.1 version (for
MVS).
User Response: Upgrade the MQSeries software to the proper version.

KM2EXPFF–KMCRCA002I

185

KMC0197E

Cluster receiver channels not supported on this version of MQSeries.
Explanation: You attempted to create an actual cluster receiver channel.
However, the Queue Manager in question is not at the proper MQSeries version
to support clustering. For a Queue Manager to participate in a cluster, MQSeries
must be at least at the 5.1 version (for distributed platforms) or the 2.1 version (for
MVS).
User Response: Upgrade the MQSeries software to the proper version.

KMC0198S

The configuration object contains an undefined attribute @1 = @2.
Explanation: The property indicated by @1 was found in the definition of this
configuration object. This property is unsupported.
User Response: Collect the CMS log files and call Candle Customer Support.

KMC0199E

The MQSeries object contains an invalid queue name @2.
Explanation: The queue name that you specified for this object is not a valid
MQSeries queue name.
User Response: Ensure that the queue name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
® Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).
®
®
®
®
®

KMC0200E

186

Numerics 0-9
Period (.)
Forward slash (/)
Underscore (_)
Percent sign (%). The percent sign (%) is a special character to RACF®. If you
are using RACF as the external security manager for MQSeries for OS/390,
you should not use % in object names. If you do, these names are not
included in any security checks when RACF generic profiles are used.

The MQSeries object contains an invalid Queue Manager name @2.
Explanation: The Queue Manager name that you specified for this object is not
a valid MQSeries Queue Manager name.
User Response: Ensure that the Queue Manager name is valid. The character
set that can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

®
®
®
®
®

Candle Products Messages Manual (KLVHS–KONCT)

KMC0201E

KMC0202E

The MQSeries object contains an invalid channel name @2.
Explanation: The channel name that you specified for this object is not a valid
MQSeries channel name.
User Response: Ensure that the channel name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

®
®
®
®
®

The MQSeries object contains an invalid process name @2.
Explanation: The process name that you specified for this object is not a valid
MQSeries process name.
User Response: Ensure that the process name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

®
®
®
®

KM2EXPFF–KMCRCA002I

187

KMC0203E

KMC0204E

188

The MQSeries object contains an invalid namelist name @2.
Explanation: The namelist name that you specified for this object is not a valid
MQSeries namelist name.
User Response: Ensure that the namelist name is valid. The character set that
can be used for naming MQSeries namelists is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

The contents of the namelist are invalid.
Explanation: The namelist contents contain one or more invalid entries.
User Response: Ensure that the namelist contents are valid. Each entry in the
contents must contain a valid MQSeries name. The character set that can be used
for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Candle Products Messages Manual (KLVHS–KONCT)

KMC0205E

The through Queue Manager field @1 is not defined in the configuration.
Explanation: You have selected the ’Indirect connection’ option for the Queue
Manager; however, the ’Through Queue Manager’ name is not defined anywhere
in the configuration.
User Response: Correct the ’Through Queue Manager’ field.

KMC0206E

The exit name @2 associated with this object is invalid.
Explanation: You have specified an invalid exit name for the object.
User Response: Specify a valid name for the exit.
The format and maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.

KMC0207E

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

The connection name @2 associated with this object is invalid.
Explanation: You specified an invalid connection name for the channel.
User Response: Specify a valid connection name for the channel. The value
you specify depends on the transport type (TRPTYPE) to be used:

KM2EXPFF–KMCRCA002I

189

LU 6.2

NetBIOS

A unique NetBIOS name (limited to 16 characters).

SPX

TCP

If you are using any of the special characters in your connection name (for
example, parentheses) you must enclose the string in single quotes.

190

Candle Products Messages Manual (KLVHS–KONCT)

KMC0208E

The modename @2 associated with this object has an invalid length.
Explanation: You specified an invalid modename for the channel.
User Response: Specify a valid mode name for the channel. On Tandem NSK,
this should be set to the SNA mode name. The name can also be nonblank for
client connection channels to be used with OS/2 Warp. On other platforms the
mode name can only be set to blanks; the actual name is then taken from the
CPI-C Communications Side Object, or APPC side information data set.

KMC0209E

The storage class name @2 associated with this object has an invalid
length.
Explanation: You specified an invalid storage class name for the queue.
User Response: Specify a valid storage class name for the queue. Storage class
names are restricted to a maximum of 8 characters in length.

KMC0210E

The MCA user id @2 associated with this object has an invalid length.
Explanation: You specified an invalid message channel agent userid for the
channel.
User Response: Specify a valid message channel agent user id. Message
channel agent user ids are restricted to a maximum of 12 characters in length.

KMC0211E

The user id @2 associated with this object has an invalid length.
Explanation: You specified an invalid LU6.2 task userid for the channel.
User Response: Specify a valid LU6.2 task user id. LU6.2 task userids are
restricted to a maximum of 12 characters in length.

KMC0212E

The password @2 associated with this object has an invalid length.
Explanation: You specified an invalid LU6.2 password for the channel.
User Response: Specify a valid LU6.2 password. Passwords are restricted to a
maximum of 12 characters in length.

KMC0213E

The MCA name @2 associated with this object has an invalid length.
Explanation: You specified an invalid MCANAME for the channel.
User Response: Specify a valid MCANAME. MCANAMEs are restricted to a
maximum of 20 characters in length.

KMC0214E

The ’Don’t check resources prefixed with’ @2 associated with this object
has an invalid length.
Explanation: You specified an invalid value for the 'Don’t check resources
prefixed with' property on the Validation page of the Queue Manager settings.
User Response: Specify a valid value for this field. The value specified is
limited to 255 characters in length.

KMC0215E

The Exit user data @2 associated with this object has an invalid length.
Explanation: You specified invalid exit data for the channel.
User Response: Specify valid exit data. Exit data is restricted to 32 characters
in length on this version of MQSeries.

KM2EXPFF–KMCRCA002I

191

KMC0216E

The Environmental data @2 associated with this object has an invalid
length.
Explanation: You specified invalid environment data for the process.
User Response: Specify a valid environment data. Environment data is
restricted to a maximum of 128 characters in length.

KMC0217E

The User data @2 associated with this object has an invalid length.
Explanation: You specified invalid user data for the process.
User Response: Specify valid user data. User data is restricted to a maximum
of 128 characters in length.

KMC0218E

The Trigger data @2 associated with this object has an invalid length.
Explanation: You specified invalid trigger data for the queue.
User Response: Specify valid trigger data. Trigger data is restricted to a
maximum of 64 characters in length.

KMC0219E

The TPNAME @2 associated with this object has an invalid length.
Explanation: You specified an invalid LU6.2 Transaction program name for the
channel.
User Response: Specify a valid LU6.2 Transaction program name. On Tandem
NSK, this should be set to the local TP name. This can be followed by the name of
the TP on the remote machine, for example: TPNAME(’localtp[.remotetp]’).
Both names can be up to 16 characters in length. The name can also be nonblank
for client connection channels to be used with OS/2 Warp.
On other platforms, this should be set to the SNA transaction program name,
unless the CONNAME contains a side-object name in which case it should be set
to blanks. The actual name is taken instead from the CPI-C Communications Side
Object, or the APPC side information data set.
See the information about configuration parameters for an LU 6.2 connection for
your platform in the MQSeries Intercommunication manual for more information.
On Windows NT SNA Server, and in the side object on OS/390, the TPNAME is
wrapped to upper case. This parameter is not valid for channels with a channel
type (CHLTYPE) of RCVR.

KMC0220E

The @1 event type is invalid.
Explanation: You specified an invalid Event control for the Queue Manager.
User Response: Specify a valid Event control.

KMC0221E

The @1 validation type is invalid.
Explanation: You specified an invalid Validation control for the object.
User Response: Specify a valid Validation control.

192

Candle Products Messages Manual (KLVHS–KONCT)

KMC0222E

The @1 application type is invalid.
Explanation: You specified an invalid application type for the process.
User Response: Specify a valid application type. Valid application types are:
® CICS: Represents a CICS transaction.
®

DOS: Represents a DOS application.

IMS: Represents an IMS transaction.

MVS: Represents an OS/390 application (batch or TSO).

NSK: Represents a Tandem NSK application.

OS2: Represents an OS/2 Warp application.

OS400: Represents an OS/400 application.

UNIX: Represents a UNIX application.

VMS: Represents a Digital OpenVMS application.

WINDOWS: Represents a Windows application.

WINDOWSNT: Represents a Windows NT application.

KMC0223E

The get inhibit type is invalid.
Explanation: You specified an invalid get inhibit property for the queue.
User Response: Specify a valid get inhibit property.

KMC0224E

The default open for input type is invalid.
Explanation: You specified an invalid default open property for the queue.
User Response: Specify a valid default open property.

KMC0226E

The put inhibit type is invalid.
Explanation: You specified an invalid put inhibit property for the queue.
User Response: Specify a valid put inhibit property.

KMC0227E

The queue definition type is invalid.
Explanation: You specified an invalid definition type property for the queue.
User Response: Specify a valid definition type property.

KMC0228E

The harden get backout type is invalid.
Explanation: You specified an invalid harden backout property for the queue.
User Response: Specify a valid harden backout property.

KMC0229E

The delivery sequence type is invalid.
Explanation: You specified an invalid message sequence property for the
queue.
User Response: Specify a valid message sequence property.

KMC0230E

The shareability type is invalid.
Explanation: You specified an invalid shareable property for the queue.
User Response: Specify a valid shareable property.

KM2EXPFF–KMCRCA002I

193

KMC0231E

The default persistence type is invalid.
Explanation: You specified an invalid default persistence property for the
queue.
User Response: Specify a valid default persistence property.

KMC0232E

The service interval event type is invalid.
Explanation: You specified an invalid service interval milliseconds property for
the queue.
User Response: Specify a valid service interval milliseconds property.

KMC0233E

The dead letter queue @1 associated with the Queue Manager is not
defined as a local queue.
Explanation: You defined a dead letter queue in the Queue Manager definition.
However, the DLQ name that you specified is not defined as a local queue within
the Queue Manager’s subordinate resources.
User Response: Ensure that the name you specify as a Dead Letter Queue for
the Queue Manager is defined as a local queue.

KMC0234E

The dead letter queue @1 associated with the Queue Manager is not
defined as USAGE(NORMAL).
Explanation: You defined a dead letter queue in the Queue Manager definition.
However, the DLQ name that you specified identifies a local queue that is defined
as a Transmit queue.
User Response: Change the Usage for the Dead Letter Queue to normal, or
identify a different Dead Letter Queue for the Queue Manager.

KMC0235W

One or more IBM standard MQSeries resources are not defined @1 @2
@3 @4.
Explanation: At least one of the default IBM-provided resources that should be
associated with the Queue Manager are not present in the defined configuration.
Up to three of the missing resource names are displayed.
User Response: This message is only a warning. If these resources are not
defined at the time of an Update Actual from Defined, or Update Defined from
Actual request against the Queue Manager, then they will be added dynamically
into the defined configuration by copying the definitions from the actual Queue
Manager.

KMC0236E

The default transmit queue @1 is not defined as a local queue within the
Queue Manager.
Explanation: You defined a default transmit queue in the Queue Manager
definition. However, the queue name that you specified is not defined as a local
queue within the Queue Manager’s subordinate resources.
User Response: Ensure that the name you specify as a default transmit queue
for the Queue Manager is defined as a local queue.

194

Candle Products Messages Manual (KLVHS–KONCT)

KMC0237E

The default transmit queue @1 is not defined as USAGE(XMITQ).
Explanation: You defined a default transmit queue in the Queue Manager
definition. However, the DLQ name that you specified identifies a local queue
that is defined with Usage Normal.
User Response: Change the Usage for the default transmit queue to Transmit
queue, or identify a different default transmit queue for the Queue Manager.

KMC0238E

The trigger process @1 associated with the queue is not defined within
Queue Manager.
Explanation: Triggering is enabled for the queue. However the defined trigger
process name associated with the queue is not defined within the Queue
Manager.
User Response: Either disable triggering for the queue, or ensure that the
Process name property identifies a process that is defined within the Queue
Manager.

KMC0239E

Triggering is enabled for the queue but the initiation queue is not
specified.
Explanation: Triggering is enabled for the queue. However, you did not specify
the name of an Initiation queue.
User Response: Either disable triggering for the queue, or identify the name of
a local queue defined on the Queue Manager which is to be used as the initiation
queue.

KMC0240E

The initiation queue @1 has the same name as the queue name.
Explanation: Triggering is enabled for the queue. However, you specified the
name of the queue as the initiation queue. This is not supported.
User Response: Either disable triggering for the queue, or identify the name of
another local queue defined on the Queue Manager which is to be used as the
initiation queue.

KMC0241W

The queue is defined as a transmit queue but it is not referenced by a
channel within the Queue Manager.
Explanation: The local transmit queue will not be used because there are no
sender or server channels defined in the Queue Manager which reference this
queue as a transmit queue.
User Response: This message is only a warning. You can stop the message
from appearing by either specifying Usage=Normal for the queue, or by
specifying the name of the queue as the Transmit queue name for a sender or
server channel within the Queue Manager.

KMC0242E

The transmit queue @1 associated with the channel is not defined as a
local queue within the Queue Manager.
Explanation: You defined a transmit queue in the remote queue definition.
However, the queue name that you specified is not defined as a local queue
within the Queue Manager’s subordinate resources.
User Response: Ensure that the name you specify as a transmit queue for the
remote queue is defined as a local queue within the Queue Manager.

KM2EXPFF–KMCRCA002I

195

KMC0243E

The transmit queue @1 associated with the channel is not defined as
USAGE(XMITQ).
Explanation: You defined a transmit queue in the remote queue definition.
However, the queue name that you specified identifies a local queue that is
defined with Usage Normal.
User Response: Change the Usage for the transmit queue to Transmit or
identify a different transmit queue for the remote queue.

KMC0244E

The maximum message length @1 associated with the queue is larger
than the maximum message length associated with the Queue Manager.
Explanation: The maximum message length associated with the queue is larger
than the maximum message length associated with the Queue Manager.
User Response: Correct the maximum message length. On AIX, HP-UX, OS/2
Warp, Sun Solaris, and Windows NT, specify a value greater than or equal to zero,
and less than or equal to the maximum message length for the Queue Manager.
On other platforms, specify a value greater than 0, and less than or equal to
4,194,304.

KMC0245E

The remote Queue Manager name not specified for the remote queue.
Explanation: You defined a remote queue, but the remote manager name is not
specified. This property is required.
User Response: Specify a valid MQSeries name for the remote manager name.
If an application opens the local definition of a remote queue, the remote Queue
Manager must not be blank or the name of the local Queue Manager. When the
open occurs, if the transmit queue is blank there must be a local queue of this
name, which is to be used as the transmission queue.
If this definition is used for a queue-manager alias, remote Queue Manager is the
name of the Queue Manager that is being aliased. It can be the name of the local
Queue Manager. Otherwise, then if XMITQ is blank, when the open occurs there
must be a local queue of this name, which is to be used as the transmission
queue.
If this definition is used for a reply-to alias, this name is the name of the Queue
Manager that is to be the reply-to Queue Manager.

KMC0246E

The remote queue @1 is not defined as a local queue within the Queue
Manager.
Explanation: You defined a remote queue, but the transmit queue is empty and
the remote manager name does not specify the name of a local queue defined on
the Queue Manager.
User Response: Specify the name of a local queue defined within this Queue
Manager which is defined with Usage=Transmit for the remote manager name. If
an application opens the local definition of a remote queue, the remote Queue
Manager must not be blank or the name of the local Queue Manager. When the
open occurs, if the transmit queue is blank there must be a local queue of this
name, which is to be used as the transmission queue.

196

Candle Products Messages Manual (KLVHS–KONCT)

KMC0247E

The remote queue @1 is not defined as USAGE(XMITQ) within the Queue
Manager.
Explanation: You defined a remote queue, but the transmit queue is empty and
the remote manager name identifies a local queue which is defined with
Usage=Normal.
User Response: Specify the name of a local queue defined within this Queue
Manager which is defined with Usage=Transmit for the remote manager name. If
an application opens the local definition of a remote queue, the remote Queue
Manager must not be blank or the name of the local Queue Manager. When the
open occurs, if the transmit queue is blank there must be a local queue of this
name, which is to be used as the transmission queue.

KMC0248W

The process is not referenced by a local or model queue within the
Queue Manager.
Explanation: The defined process will not be used because it is not referenced
as the process name by a local or model queue within the Queue Manager.
User Response: This message is only a warning. You can stop the message
from appearing by defining a local or model queue within the Queue Manager
that references the process on the Triggers settings page.

KMC0249E

The target queue not defined as local or remote queue within the Queue
Manager.
Explanation: The target queue name associated with this alias queue is not
defined as a local or remote queue within the Queue Manager.
User Response: Specify the name of a local or remote queue within the Queue
Manager as the alias queue’s target queue.

KMC0250W

The process is not referenced by a queue with triggering enabled within
the Queue Manager.
Explanation: The defined process will not be used because it is not referenced
as the process name by a local or model queue within the Queue Manager that
has triggering enabled.
User Response: This message is only a warning. You can stop the message
from appearing by defining a local or model queue within the Queue Manager
that references the process on the Triggers settings page and has triggering
enabled.

KMC0251E

The name list contains entry @1 which is not defined as a queue on the
Queue Manager.
Explanation: An entry on the contents of the namelist is not defined as a queue
within the Queue Manager.
User Response: Ensure that each entry in the namelist contents identifies the
name of a queue on the Queue Manager.

KM2EXPFF–KMCRCA002I

197

KMC0252E

The heartbeat interval @1 is larger than disconnect interval @2.
Explanation: You specified a heartbeat interval for the channel which is larger
than the channel’s disconnect interval.
User Response: Correct either the heartbeat interval, or the disconnect
interval. IBM recommends that you should set the heartbeat interval to be
significantly less than the disconnect interval.

KMC0253E

Sender/Server channel does not contain a reference to a transmit queue.
Explanation: You defined a sender or server channel, but the Transmit queue
name is not specified. This is required.
User Response: Specify the name of a local queue defined within this Queue
Manager which is defined with Usage=Transmit for the Transmit queue name.

KMC0254E

The channel references a transmit queue @1 which is not not defined as
a local queue within the Queue Manager.
Explanation: You defined a transmit queue in the channel definition. However,
the queue name that you specified is not defined as a local queue within the
Queue Manager’s subordinate resources.
User Response: Ensure that the name you specify as a transmit queue for the
channel is defined as a local queue within the Queue Manager.

KMC0255E

The channel references a transmit queue @1 which is not not defined as
USAGE(XMITQ).
Explanation: You defined a transmit queue in the channel definition. However,
the queue name that you specified identifies a local queue that is defined with
Usage Normal.
User Response: Change the Usage for the transmit queue to Transmit, or
identify a different transmit queue for the remote queue.

KMC0256E

The maximum message length of the transmit queue @1 exceeds the
maximum message length of the channel.
Explanation: You have defined a sender or server channel and its associated
transmit queue. However, the maximum message of the transmit queue is larger
than the maximum message length of the channel. This could result in problems if
messages are put to the transmission queue which are larger than the maximum
message length for the channel.
User Response: Specify a maximum message length for the channel which is
at least as large as the maximum message length for the transmit queue.

KMC0257W

The connected Queue Manager @1 does not exist.
Explanation: You defined a value for the Connected Queue Manager on the
Transmit page for this channel. However, the Connected Queue Manager does
not identify a defined Queue Manager within the configuration.
User Response: Either blank out the Connected Queue Manager field, or
specify the name of a Queue Manager which is currently defined.

198

Candle Products Messages Manual (KLVHS–KONCT)

KMC0258W

A Receiver/requester channel with the same name as this channel does
not exist on the receiving Queue Manager @1.
Explanation: You defined a value for the Connected Queue Manager on the
Transmit page for this channel. However, a receiver or requester channel with the
same name as this channel does not exist within the Queue Manager referenced
by the Connected Queue Manager. A sender or server channel must be able to
communicate with a receiver or requester channel of the same name.
User Response: Either blank out the Connected Queue Manager field, or
define a receiver or requester channel within the Connected Queue Manager that
has the same name as this channel.

KMC0259W

The receiver/requester channel on Queue Manager @1 is defined with an
inconsistent transport type to this channel.
Explanation: You defined a value for the Connected Queue Manager on the
Transmit page for this channel. However, the corresponding receiver or requester
channel defined within the Connected Queue Manager specifies a different
Transport type.
User Response: Correct the definition of either this channel, or of the
corresponding receiver or requester channel on the other Queue Manager, so that
the transport types are consistent.

KMC0260W

The maximum message length definition for this channel is inconsistent
with the receiver/requester channel on Queue Manager @1.
Explanation: You defined a value for the Connected Queue Manager on the
Transmit page for this channel. However, the corresponding receiver or requester
channel defined within the Connected Queue Manager specifies a different
maximum message length.
User Response: This message is only a warning. The maximum message
length is compared with the value for the partner and the actual maximum used is
the lower of the two values. To eliminate this warning message, correct the
definition of either this channel, or of the channel on the connected Queue
Manager.

KMC0261E

Triggering is enabled for the queue but initiation queue @1 is not found.
Explanation: Triggering is enabled for the queue. However, the value that you
specified as an initiation queue did not reference a local queue on this Queue
Manager.
User Response: Either disable triggering for the queue, or identify the name of
a local queue defined on the Queue Manager which is to be used as the initiation
queue.

KMC0262E

The initiation queue @1 associated with the queue is not
USAGE(NORMAL).
Explanation: Triggering is enabled for the queue. However, the value that you
specified as an initiation identified a local queue defined with Usage=Transmit.
User Response: Either disable triggering for the queue, or identify the name of
a local queue defined on the Queue Manager with Usage=Normal which is to be
used as the initiation queue.

KM2EXPFF–KMCRCA002I

199

KMC0263W

The batch size associated with the channel is inconsistent with the
receiver/requester channel on Queue Manager @1.
Explanation: You defined a value for the Connected Queue Manager on the
Transmit page for this channel. However, the corresponding receiver or requester
channel defined within the Connected Queue Manager specifies a different batch
size.
User Response: This message is only a warning. The maximum batch size
actually used is the lowest of the following:
® the batch size of the sending channel
®

the batch size of the receiving channel

the maximum number of uncommitted messages allowed at the sending
queue

KMC0264E

The queue depth high limit @1 for the queue is less than the queue
depth low limit.
Explanation: You defined a queue in which the upper queue depth threshold is
less than the lower queue depth threshold.
User Response: Correct the queue definition so that the upper queue depth
threshold is greater than the lower queue depth threshold.

KMC0265E

Namelists are not allowed on this platform.
Explanation: You defined a namelist object on a Queue Manager which does
not support namelists. Namelists are only supported on:
® MVS
®

Distributed systems running MQSeries 5.1 or greater

User Response: Delete the namelist definition, or upgrade MQSeries software
to a version which supports namelists.
KMC0266E

Storage classes are not allowed on this platform.
Explanation: You defined a storage class object on a Queue Manager which
does not support storage classes Storage classes are only supported on MVS.
User Response: Delete the storage class definition.

KMC0267E

Invalid scope type.
Explanation: You specified an invalid scope type property for the queue.
User Response: Specify a valid scope type property.

KMC0268E

Invalid trigger type.
Explanation: You specified an invalid trigger type property for the queue.
User Response: Specify a valid trigger type property.

KMC0269E

Invalid queue type.
Explanation: You specified an invalid queue type property for the queue.
User Response: Specify a valid queue type property.

KMC0270E

Invalid queue usage.
Explanation: You specified an invalid usage property for the queue.
User Response: Specify a valid usage property.

200

Candle Products Messages Manual (KLVHS–KONCT)

KMC0271E

Invalid data conversion.
Explanation: You specified an invalid convert property for the channel.
User Response: Specify a valid convert property.

KMC0272E

Invalid channel type.
Explanation: You specified an invalid channel type property for the channel.
User Response: Specify a valid channel type property.

KMC0273E

Invalid protocol type @2.
Explanation: You specified an invalid protocol type property for the channel.
User Response: Specify a valid protocol type property.
® LU62
®

SNA LU 6.2

NETBIOS: NetBIOS (supported only on OS/2 Warp, Windows, Windows NT,
and DOS; it also applies to OS/390 for defining client-connection channels
that will connect to servers on the platforms supporting NetBIOS).

SPX: Sequenced packet exchange (supported only on OS/2 Warp, Windows,
Windows NT, and DOS; it also applies to OS/390 for defining
client-connection channels that will connect to servers on the platforms
supporting SPX).

TCP: Transmission Control Protocol - part of the TCP/IP protocol suite.

UDP: User Datagram Protocol - part of the TCP/IP protocol suite (supported
only on AIX).

KMC0274E

Invalid put authority.
Explanation: You specified an invalid put authority property for the channel.
User Response: Specify a valid put authority property.

KMC0275E

Invalid autostart value.
Explanation: You specified an invalid auto start property for the Queue
Manager.
User Response: Specify a valid auto start property.

KMC0276E

Invalid indirect connection value.
Explanation: You specified an invalid indirect connection property for the
Queue Manager.
User Response: Specify a valid indirect connection property.

KMC0277E

Invalid default Queue Manager value.
Explanation: You specified an invalid default Queue Manager property for the
Queue Manager.
User Response: Specify a valid default Queue Manager property.

KMC0278E

Invalue autocreate value.
Explanation: You specified an invalid auto create property for the Queue
Manager.
User Response: Specify a valid auto create property.

KM2EXPFF–KMCRCA002I

201

KMC0279E

Invalid MVS value.
Explanation: You specified an invalid MVS property for the Queue Manager.
User Response: Specify a valid MVS property.

KMC0280E

Invalid channel autodefine value.
Explanation: You specified an invalid channel autodefine property for the
Queue Manager.
User Response: Specify a valid channel autodefine property.

KMC0281E

Invalid index type.
Explanation: You specified an invalid index type property for the queue.
User Response: Specify a valid index type property.
Note: The index type can only be specified for queues defined on Queue
Managers running on MVS.

KMC0282E

Invalid distribution list.
Explanation: You specified an invalid distribution list property for the queue.
User Response: Specify a valid distribution list property.

KMC0283E

Invalid NPM speed.
Explanation: You specified an invalid non-persistent delivery property for the
channel.
User Response: Specify a valid non-persistent delivery property.

KMC0284E

Invalid trigger control.
Explanation: You specified an invalid trigger control property for the queue.
User Response: Specify a valid trigger control property.

KMC0285E

Invalid queue depth high value @2.
Explanation: You specified an invalid upper queue depth threshold for the
queue.
User Response: Specify a valid upper queue depth threshold. The value is
expressed as a percentage of the maximum queue depth, and must be greater
than or equal to zero, and less than or equal to 100.

KMC0286E

Invalid queue depth low value @2.
Explanation: You specified an invalid lower queue depth threshold for the
queue.
User Response: Specify a valid lower queue depth threshold. The value is
expressed as a percentage of the maximum queue depth, and must be greater
than or equal to zero, and less than or equal to 100.

KMC0287E

Invalid maximum uncommitted messages value @2.
Explanation: You specified an invalid maximum uncommitted messages value
for the Queue Manager.
User Response: Specify a valid maximum uncommitted messages value.
Specify a value in the range 1 through 999,999,999.

202

Candle Products Messages Manual (KLVHS–KONCT)

KMC0288E

Invalid disconnect interval @2.
Explanation: You specified an invalid disconnect interval for the channel.
User Response: Specify a valid disconnect interval. The value must be greater
than or equal to zero, and less than or equal to 999,999.

KMC0289E

Invalid maximum priority @2.
Explanation: You specified an invalid maximum priority value for the Queue
Manager.
User Response: Specify a valid maximum priority value. Specify a value in the
range 0 through 9.

KMC0290E

Invalid heartbeat interval @2.
Explanation: You specified an invalid heartbeat interval for the channel.
User Response: Specify a valid heartbeat interval. The value must be greater
than or equal to zero, and less than or equal to 999,999.

KMC0291E

Invalid batch interval @2.
Explanation: You specified an invalid batch interval for the channel.
User Response: Specify a valid batch interval. The value must be greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0292E

Invalid max handles value @2.
Explanation: You specified an invalid maximum open handles value for the
Queue Manager.
User Response: Specify a valid maximum open handles value. Do not specify
a value less than zero or greater than 999,999,999.

KMC0293E

Invalid trigger interval @2.
Explanation: You specified an invalid trigger interval for the Queue Manager.
User Response: Specify a valid trigger interval. Do not specify a value less than
zero or greater than 999,999,999.

KMC0294E

Invalid service interval @2.
Explanation: You specified an invalid service interval for the queue.
User Response: Specify a valid service interval. The value is in units of
milliseconds, and must be greater than or equal to zero, and less than or equal to
999,999,999.

KMC0295E

Invalid retention interval @2.
Explanation: You specified an invalid retention interval for the queue.
User Response: Specify a valid retention interval. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0296E

Invalid trigger depth @2.
Explanation: You specified an invalid trigger depth for the queue.
User Response: Specify a valid trigger depth. The value must be greater than
zero, and less than or equal to 999,999,999.

KM2EXPFF–KMCRCA002I

203

KMC0297E

Invalid long retry value @2.
Explanation: You specified an invalid long retry count for the channel.
User Response: Specify a valid long retry count. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0298E

Invalid long timer value @2.
Explanation: You specified an invalid long retry interval for the channel.
User Response: Specify a valid long retry interval. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0299E

Invalid sequence number wrap value @2.
Explanation: You specified an invalid sequence number wrap value for the
channel.
User Response: Specify a valid sequence number wrap value. The value must
be greater than or equal to 100, and less than or equal to 999,999,999.

KMC0300E

Invalid short retry value @2.
Explanation: You specified an invalid short retry count for the channel.
User Response: Specify a valid short retry count. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0301E

Invalid short timer value @2.
Explanation: You specified an invalid short retry interval for the channel.
User Response: Specify a valid short retry interval. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0302E

Invalid message retry count @2.
Explanation: You specified an invalid message retry count for the channel.
User Response: Specify a valid message retry count. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0303E

Invalid message retry interval @2.
Explanation: You specified an invalid message retry interval for the channel.
User Response: Specify a valid message retry interval. The value must be
greater than or equal to zero, and less than or equal to 999,999,999.

KMC0304E

Invalid backout threshold @2.
Explanation: You specified an invalid backout threshold for the queue.
User Response: Specify a valid backout threshold. Specify a value greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0305E

Invalid default priority @2.
Explanation: You specified an invalid default message priority for the queue.
User Response: Specify a valid default message priority. The value must be
greater than or equal to zero, (the lowest priority) and less than or equal to the
maximum message priority specified for the Queue Manager.

204

Candle Products Messages Manual (KLVHS–KONCT)

KMC0306E

Invalid trigger message priority @2.
Explanation: You specified an invalid trigger message priority for the queue.
User Response: Specify a valid trigger message priority. The value must be
greater than or equal to zero, (the lowest priority) and less than or equal to the
maximum message priority specified for the Queue Manager.

KMC0307E

Invalid maximum queue depth @2.
Explanation: You specified an invalid maximum queue depth for the queue.
User Response: Specify a valid maximum queue depth. Specify a value
greater than or equal to zero, and less than or equal to:
® 999,999,999 if the queue is on MVS/ESA.
®

640,000 if the queue is on any other MQSeries platform.

KMC0308E

Invalid batch size @2.
Explanation: You specified an invalid batch size for the channel.
User Response: Specify a valid batch size. The value must be greater than
zero, and less than or equal to 9,999.

KMC0309E

Invalid MCA type.
Explanation: You specified an invalid message channel agent type for the
channel.
User Response: Specify a valid message channel agent type.

KMC0310E

Invalid maximum message length @2.
Explanation: You specified an invalid maximum message length for the queue
or channel.
User Response: Specify a valid maximum message length. On AIX, HP-UX,
OS/2 Warp, Sun Solaris, and Windows NT, specify a value greater than or equal
to zero, and less than or equal to the maximum message length for the Queue
Manager. See the MAXMSGL parameter of the ALTER Q.

KMC0312E

Invalid autostart listener value.
Explanation: You specified an invalid autostart listener property for the Queue
Manager.
User Response: Specify a valid autostart listener property.

KMC0313E

Invalid connection port @2.
Explanation: You specified an invalid port number for the Queue Manager.
User Response: Specify a valid port number. Specify a numeric IP port
number.

KM2EXPFF–KMCRCA002I

205

KMC0314E

Invalid Queue Manager autoconnect protocol @2.
Explanation: You specified an invalid autoconnect protocol for the Queue
Manager.
User Response: Specify a valid protocol type property:
® LU62.
®

SNA LU 6.2.

SPX : Sequenced packet exchange (supported only on OS/2 Warp, Windows,
Windows NT, and DOS; it also applies to OS/390 for defining
client-connection channels that will connect to servers on the platforms
supporting SPX).

TCP: Transmission Control Protocol - part of the TCP/IP protocol suite.

UDP: User Datagram Protocol - part of the TCP/IP protocol suite (supported
only on AIX).

KMC0315E

Invalid autostart channel initiator value.
Explanation: You specified an invalid start channel initiator property for the
Queue Manager.
User Response: Specify a valid start channel initiator property.

KMC0316E

Invalid autoconnect prototype resource group @2.
Explanation: You specified an invalid autoconnect prototype resource group for
the Queue Manager.
User Response: Specify a valid autoconnect prototype resource group. Specify
the name of a valid prototype resource group.

KMC0317E

Invalid storage class name @2.
Explanation: You specified an invalid name for the storage class.
User Response: Specify a valid name for the storage class. Storage class names
are restricted to a maximum of 8 characters in length.

KMC0318E

Invalid XCF group name @2.
Explanation: You specified an invalid IMS Bridge XCF Configuration Group
name for the storage class.
User Response: Specify a valid IMS Bridge XCF Configuration Group name
for the storage class. IMS Bridge XCF Configuration Group names are restricted to
a maximum of 8 characters in length.

KMC0319E

Invalid XCF member name @2.
Explanation: You specified an invalid IMS Bridge XCF Configuration Member
name for the storage class.
User Response: Specify a valid IMS Bridge XCF Configuration Member name
for the storage class. IMS Bridge XCF Configuration Member names are restricted
to a maximum of 8 characters in length.

206

Candle Products Messages Manual (KLVHS–KONCT)

KMC0320E

Invalid page set id @2.
Explanation: You specified an invalid page set id for the storage class.
User Response: Specify a valid page set id for the storage class. The string
consists of two numeric characters, in the range 00 through 99.

KMC0321E

Invalid authorization event.
Explanation: You specified an invalid authorization event property for the
Queue Manager.
User Response: Specify a valid authorization event property.

KMC0322E

Invalid Dead Letter Queue @2.
Explanation: You specified an invalid dead letter queue name for the Queue
Manager.
User Response: Specify a valid dead letter queue name. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0323E

Processes are not allowed on this version of MQSeries.
Explanation: You defined a process object on a Queue Manager which does not
support processes Processes cannot exist on a Queue Manager running MQSeries
2.1 for Windows.
User Response: Delete the definition of the process.

KMC0324E

Server connection channels are not allowed on this version of MQSeries.
Explanation: You defined a server connection channel on an unsupported
version of MQSeries. Server connection channels cannot exist on a Queue
Manager running MQSeries 2.1 for Windows.
User Response: Delete the definition of the server connection channel.

KMC0325E

The storage class @1 referenced by this queue is not defined.
Explanation: You defined a local or model queue containing a reference to a
storage class. This storage class is not defined within the Queue Manager.
User Response: Change the storage class definition to the name of a storage
class defined within the Queue Manager.

KM2EXPFF–KMCRCA002I

207

KMC0326E

Queue manager Log type invalid.
Explanation: You specified an invalid logging type property for the Queue
Manager.
User Response: Specify a valid logging type.

KMC0327E

Number of primary logs invalid @2 The value should be between 2 and
62.
Explanation: You specified an invalid number of primary logs for the Queue
Manager.
User Response: Specify a valid number of primary logs. The minimum is 2,
and the maximum is 62.

KMC0328E

Number of secondary logs invalid @2 The value should be between 1
and 61.
Explanation: You specified an invalid number of secondary logs for the Queue
Manager.
User Response: Specify a valid number of secondary logs. The minimum is 1,
and the maximum is 61.

KMC0329E

Invalid log file size @2.
Explanation: You specified an invalid log file size for the Queue Manager.
User Response: Specify a valid log file size.
In MQSeries for UNIX systems, the minimum value is 64, and the maximum is
16384.
In MQSeries for OS/2 Warp and Windows NT, the minimum value is 32, and the
maximum is 4095.

KMC0330E

Invalid log file path @2.
Explanation: You specified an invalid log file path for the Queue Manager.
User Response: Specify the name of a valid file path for the platform the
Queue Manager is to be created on.

KMC0331E

Invalid default .INI file @2 for Tandem NSK.
Explanation: You specified an invalid default ini file for the Queue Manager.
User Response: Specify a valid Tandem NSK file name.

KMC0332E

Invalid number of execution controllers @2 for Tandem NSK The value
should be between 1 and 256.
Explanation: You specified an invalid number of execution controllers for the
Queue Manager.
User Response: Specify a valid number of execution controllers. The minimum
is 1, and the maximum is 256.

KMC0333E

Invalid CCSID @2 for Tandem NSK The value should be between 1 and
999.
Explanation: You specified an invalid CCSID for the Queue Manager.
User Response: Specify a valid CCSID. Specify a number between 1 and the
maximum number as indicated in the message text.

208

Candle Products Messages Manual (KLVHS–KONCT)

KMC0334E

Invalid volume @2 for Tandem NSK.
Explanation: You specified an invalid volume for the Queue Manager.
User Response: Specify a valid volume. Specify a valid Tandem NSK volume.

KMC0335E

Invalid TS/MP PATHMON process name @2 for Tandem NSK.
Explanation: You specified an invalid process name for the Queue Manager.
User Response: Specify a valid Tandem NSK TS/MP PATHMON process
name.

KMC0336E

Invalid home terminal name @2 for Tandem NSK.
Explanation: You specified an invalid home terminal name for the Queue
Manager.
User Response: Specify a valid Tandem NSK home terminal name.

KMC0337E

Invalid MQSeries Status Server process name @2 for Tandem NSK.
Explanation: You specified an invalid MQSS server for the Queue Manager.
User Response: Specify a valid Tandem NSK MQSeries Status Server process
name.

KMC0338E

Invalid local queue definition - cluster queue cannot be a transmit queue.
Explanation: You defined a local or model queue containing a reference to a
cluster, but the queue is also defined with Usage=Transmit. This is not supported.
User Response: Either remove the cluster or cluster namelist reference from the
local queue definition, or change the Usage of the queue to Normal.

KMC0339W

The corresponding receiver channel is not associated with the sender
channel’s cluster set.
Explanation: You have defined a cluster sender channel and associated the
channel with one or more cluster names. However, at least one of the cluster
names is not associated with the corresponding cluster receiver channel.
User Response: Modify the definition of the cluster sender and cluster receiver
channels so that each cluster associated with sender channel is also associated
with the receiver channel.

KMC0340W

A cluster receiver channel corresponding to this cluster sender is not
defined on another Queue Manager.
Explanation: You have defined a cluster sender channel; however, there is no
corresponding cluster receiver channel on any other Queue Manager in the
configuration with a matching name.
User Response: You can either rename the cluster sender channel to have the
same name as the cluster receiver on the Queue Manager you wish the sender to
connect to; or you can define a cluster receiver channel with the same name on
the connected Queue Manager.

KM2EXPFF–KMCRCA002I

209

KMC0341W

The receiving Queue manager @1 is not a repository for the clusters
associated with the sender channel.
Explanation: You have defined a cluster sender channel; however, the Queue
Manager that the sender will connect to is not defined as a full repository for all
the clusters that the sender is associated with.
User Response: This message is a warning. Normally, predefined cluster
sender channels are only required to at least one Queue Manager which is acting
as a full repository for the cluster.

KMC0342W

Duplicate cluster receiver channels were detected in the configuration
which match this cluster sender.
Explanation: You have defined a cluster sender channel; however, the
Configuration Manager found more than one cluster receiver channel on other
Queue Managers in the configuration which could match up with this cluster
sender.
User Response: This message is a warning. Duplicate cluster receiver names
can create confusion, and can prevent the configuration product from performing
complete validation. You might consider adopting a naming standard for your
cluster receiver channels that prevents duplicate names.

KMC0343E

Cluster sender channels are not allowed on this version of MQSeries.
Explanation: You defined a cluster sender channel on a Queue Manager which
does not support them. Cluster sender channels are only supported on:
® MQSeries for MVS Version 2.1 and above.
®

MQSeries for distributed systems versions 5.1 and above.

User Response: Either delete the cluster sender, or upgrade MQSeries to a a
version that supports clustering.
KMC0344E

Cluster receiver channels are not allowed on this version of MQSeries.
Explanation: You defined a cluster receiver channel on a Queue Manager which
does not support them. Cluster receiver channels are only supported on:
® MQSeries for MVS Version 2.1 and above.
®

MQSeries for distributed systems versions 5.1 and above.

User Response: Either delete the cluster receiver or upgrade MQSeries to a a
version that supports clustering.
KMC0345E

210

Cluster and cluster namelist cannot both be specified.
Explanation: You defined a queue or channel which specifies both the Cluster
Name and Cluster Namelist properties. These properties are mutually exclusive.
User Response: Change the definition of the object so that either Cluster
Name or Cluster namelist is blank.

Candle Products Messages Manual (KLVHS–KONCT)

KMC0346E

The referenced cluster namelist @1 is not found within the Queue
Manager.
Explanation: You defined a value for the Cluster namelist for the queue or
channel. However, the name that you specified is not defined as a namelistwithin
the Queue Manager’s subordinate resources.
User Response: Ensure that the name you specify as a cluster namelist is
defined as a namelist within the Queue Manager.

KMC0347E

The repository cluster associated with the Queue Manager has no
cluster receiver channel defined in the Queue Manager.
Explanation: You defined a Queue Manager which is to act as full repository for
one or more clusters. However, at least one of these clusters does not have a
defined cluster receiver channel within this Queue Manager.
User Response: Ensure that there is a cluster receiver channel defined within
this Queue Manager associated with each cluster that the Queue Manager is to act
as a full repository for.

KMC0348E

Invalid cluster name @2.
Explanation: The cluster name associated with this object is not a valid
MQSeries cluster name.
User Response: Ensure that the cluster name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z

KMC0349E

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Invalid cluster workload exit data @2.
Explanation: You specified invalid cluster workload management exit data for
the Queue Manager.
User Response: Specify a valid cluster workload management exit data. The
maximum length is 32 characters.

KM2EXPFF–KMCRCA002I

211

KMC0350E

Invalid maximum cluster workload data length @2.
Explanation: You specified invalid cluster workload management maximum
message data for the Queue Manager.
User Response: Specify a valid cluster workload management maximum
message data. Specify a value between zero and 4 MB for OS/390, or between
zero and 999,999,999 on other platforms.

KMC0351E

Invalid cluster namelist @2.
Explanation: The cluster namelist associated with this object is not a valid
MQSeries namelist.
User Response: Ensure that the namelist name is valid.
® The character set that can be used for naming all MQSeries objects is as
follows:
®

Uppercase A-Z

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0352E

Invalid default bind.
Explanation: You specified an invalid default binding property for the queue.
User Response: Specify a valid default binding property.

KMC0353E

Invalid network priority @2.
Explanation: You specified an invalid network priority for the channel.
User Response: Specify a valid network priority. The value must be in the
range 0 through 9.

KMC0354W

MQSecure definintion is inconsistent with receiver/requester channel on
Queue Manager @1.
Explanation: There is a inconsistency between the definition of the MQSecure
properties on this channel, and the MQSecure properties for the corresponding
receiver or requester channel. The Message Encryption, Message Authentication,
and Connection Authentication property values must be identical for both
channels.
User Response: Ensure that the MQSecure options selected are identical for
both channels.

212

Candle Products Messages Manual (KLVHS–KONCT)

KMC0355E

Invalid pathname @2 for MQSecure exit.
Explanation: You specified an invalid MQSecure LIB path for the channel.
User Response: Specify a valid MQSecure LIB path. The value specified must
be a valid file path for the platform type that the Queue Manager is running on.

KMC0356W

MQSecure command queue @1 not found.
Explanation: MQSecure is enabled for the channel; however, the MQSecure
command queue is not defined within the Queue Manager.
User Response: Define the MQSecure resources by dragging and dropping the
appropriate MQSecure.Resources resource group prototype into the Queue
Manager.

KMC0357W

MQSecure problem queue @1 not found.
Explanation: MQSecure is enabled for the channel; however, the MQSecure
problem queue is not defined within the Queue Manager.
User Response: Define the MQSecure resources by dragging and dropping the
appropriate MQSecure.Resources resource group prototype into the Queue
Manager.

KMC0358W

MQSecure trigger process @1 not found.
Explanation: MQSecure is enabled for the channel; however, the MQSecure
trigger process is not defined within the Queue Manager.
User Response: Define the MQSecure resources by dragging and dropping the
appropriate MQSecure.Resources resource group prototype into the Queue
Manager.

KMC0359E

Invalid autostart inhibit type.
Explanation: You specified an invalid autostart property for the channel.
User Response: Specify a valid autostart property.

KMC0360E

Triggering is enabled for the transmit queue but the channel @1 is not
defined.
Explanation: You have enabled triggering for the transmit queue, but the
process name is blank, and the trigger data field does not contain the name of a
channel defined within the Queue Manager.
User Response: Correct the trigger data for queue. It should contain the name
of the channel to be started when the trigger occurs. Optionally, you can leave
both the process name and the trigger data blank for the queue, in which case the
channel initiator will search for a channel associated with the transmit queue.

KMC0361E

Invalid default protocol for managed cluster.
Explanation: You specified an invalid default network protocol for the managed
cluster.
User Response: Specify a valid default network protocol.

KMC0362E

Invalid full repository setting.
Explanation: You specified an invalid Acts as cluster repository property for the
cluster Queue Manager.
User Response: Specify a valid Acts as cluster repository property.

KM2EXPFF–KMCRCA002I

213

KMC0363E

The managed cluster does not have at least one full repository Queue
Manager.
Explanation: You defined a managed cluster, but none of the cluster Queue
Managers associated with the cluster are defined to act as a full repository.
User Response: Ensure that at least one of the cluster Queue Managers is
designated as a full repository for the cluster.

KMC0364E

Cluster Queue Manager should have at least one connection to a full
repository.
Explanation: This cluster Queue Manager is not a full repository, and it does not
have any defined connections to any full repositories.
User Response: Ensure that this cluster Queue Manager has a predefined
connection to at least one full repository Queue Manager by configuring the
Channels page in the cluster Queue Manager’s settings.

KMC0365W

The cluster queue must reside on at least one Queue Manager.
Explanation: You have defined a cluster queue, but you have not inidicated on
which cluster Queue Managers the queue is to reside.
User Response: Use the Cluster Queue Location page in the cluster queue’s
settings to indicate on which cluster Queue Manager the queue is to reside. At
least one cluster Queue Manager must be selected.

KMC0366E

The cluster queue definition conflicts with an identically name queue in
cluster @1.
Explanation: You have defined at least one other cluster queue in the
configuration that has the same name as this one, and is defined to reside on one
or more of the same Queue Managers. However, there is a conflict in the
definitions of these two cluster queues. For example, the maximum message
length of one cluster queue is 5000, while on the other cluster queue it is defined
as 9,999.
User Response: Examine the definitions of both cluster queues to resolve any
conflicts.

KMC0367E

Unable to locate the Queue Manager for this cluster Queue Manager.
Explanation: The Queue Manager that corresponds to this cluster Queue
Manager definition could not be found.
User Response: Collect the CMS log files, and call Candle Customer Support.

KMC0368E

The Queue Manager is not at the minimum MQSeries version to support
cluster participation.
Explanation: The Queue Manager that is participating in this managed cluster is
not at the proper MQSeries version to support clustering. For a Queue Manager to
participate in a cluster, MQSeries must be at least at the 5.1 version (for
distributed platforms) or the 2.1 version (for MVS).
User Response: Upgrade the MQSeries software to the proper version.

214

Candle Products Messages Manual (KLVHS–KONCT)

KMC0369E

Client connection channels are not allowed on this platform.
Explanation: You attempted to create an actual MQSeries client connection
channel; however, client connection channels are not supported on this platform
and/or MQSeries version. Client connection channels are not supported on
MQSeries Version 2.1 for Windows.
User Response: Delete the defined client connection channel objects.

KMC0370S

Missing or invalid application-specific function at CMS.
Explanation: The workstation made an undefined action request to the
Configuration Manager.
User Response: Collect the CMS and CMW log files, and call Candle
Customer Support.

KMC0371E

Invalid Queue Name: %s.
Explanation: The queue name that you specified for this object is not a valid
MQSeries queue name.
User Response: Ensure that the queue name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0372E

Invalid backout threshold: %s.
Explanation: You specified an invalid backout threshold for the queue.
User Response: Specify a valid backout threshold. Specify a value greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0373E

Invalid default priority: %s.
Explanation: You specified an invalid default message priority for the queue.
User Response: Specify a valid default message priority. The value must be
greater than or equal to zero, (the lowest priority) and less than or equal to the
maximum message priority specified for the Queue Manager.

KM2EXPFF–KMCRCA002I

215

KMC0374E

Invalid channel name: %s.
Explanation: The channel name @2 that you specified for this object is not a
valid MQSeries channel name.
User Response: Ensure that the channel name is valid. The character set that
can be used for naming MQSeries channels is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0375E

Invalid maximum message length: %s.
Explanation: The maximum message length specified is not valid.
User Response: Correct the maximum message length. On AIX, HP-UX, OS/2
Warp, Sun Solaris, and Windows NT, specify a value greater than or equal to zero,
and less than or equal to the maximum message length for the Queue Manager.
On other platforms, specify a value greater than or equal to zero, and less than or
equal to 4 MB, or 4,194,304 bytes.

KMC0376E

Invalid queue depth threshold: %s.
Explanation: You specified an invalid queue depth threshold for the queue.
User Response: Specify a valid queue depth threshold. The value is expressed
as a percentage of the maximum queue depth, and must be greater than or equal
to zero, and less than or equal to 100.

KMC0377E

Invalid service interval: %s.
Explanation: You specified an invalid service interval milliseconds property for
the queue.
User Response: Specify a valid service interval milliseconds property.

KMC0379E

Invalid maximum queue depth: %s.
Explanation: You specified an invalid maximum queue depth for the queue.
User Response: Specify a valid maximum queue depth. Specify a value
greater than or equal to zero, and less than or equal to:
® 999,999,999 if the queue is on MVS/ESA.
®

216

640 000 if the queue is on any other MQSeries platform.

Candle Products Messages Manual (KLVHS–KONCT)

KMC0380E

Invalid retention interval: %s.
Explanation: You specified an invalid retention interval for the queue.
User Response: Specify a valid retention interval. The value must be greater
than or equal to zero, and less than or equal to 999,999,999.

KMC0381E

Invalid storage class name: %s.
Explanation: You specified an invalid storage class name for the queue.
User Response: Specify a valid storage class name for the queue. Storage class
names are restricted to a maximum of 8 characters in length.

KMC0382E

Invalid configured system name: %s.
Explanation: You have selected the ’Indirect connection’ option for the Queue
Manager; however, the ’Through Queue Manager’ name is not a valid Queue
Manager name.
User Response: Correct the ’Through Queue Manager’ field. The character set
that can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KM2EXPFF–KMCRCA002I

217

KMC0383E

KMC0384E

KMC0385E

218

Invalid Queue Manager alias name: %s.
Explanation: You have selected the ’Indirect connection’ option for the Queue
Manager; however, the ’Queue manager alias’ name is not a valid queue name.
User Response: Correct the ’Queue manager alias’ field. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Invalid prototype name: %s.
Explanation: You specified an invalid based on prototype name for the object.
User Response: Specify a valid based on prototype name. The character set
that can be used for naming prototypes is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Invalid symbolic parameter list.
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 =, separated by commas. The
portion consists of 1 to 48 alphanumeric characters. The
portion contains 1 or more non-blank characters.

Candle Products Messages Manual (KLVHS–KONCT)

KMC0386E

Invalid Queue Manager name: %s.
Explanation: You specified an invalid Queue Manager name.
User Response: Correct the Queue Manager name. The character set that can
be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0387E

Invalid trigger interval: %s.
Explanation: You specified an invalid trigger interval for the Queue Manager.
User Response: Specify a valid trigger interval. Do not specify a value less than
zero or greater than 999,999,999.

KMC0388E

Invalid maximum open handles: %s.
Explanation: You specified an invalid maximum open handles value for the
Queue Manager.
User Response: Specify a valid maximum open handles value. Do not specify
a value less than zero or greater than 999,999,999.

KMC0389E

Invalid maximum uncommitted messages: %s.
Explanation: You specified an invalid maximum uncommitted messages value
for the Queue Manager.
User Response: Specify a valid maximum uncommitted messages value.
Specify a value in the range 1 through 999,999,999.

KM2EXPFF–KMCRCA002I

219

KMC0391E

KMC0392E

220

Invalid namelist name: %s.
Explanation: The namelist name that you specified for this object is not a valid
MQSeries namelist name.
User Response: Ensure that the namelist name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Invalid namelist.
Explanation: The namelist name that you specified for this object is not a valid
MQSeries namelist name.
User Response: Ensure that the namelist name is valid. The character set that
can be used for naming MQSeries namelists is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

Candle Products Messages Manual (KLVHS–KONCT)

KMC0393E

Invalid process name: %s.
Explanation: The process name that you specified for this object is not a valid
MQSeries process name.
User Response: Ensure that the process name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0394E

Invalid batch size: %s.
Explanation: The batch size specified for the channel is not valid.
User Response: Correct the batch size. The value must be greater than zero,
and less than or equal to 9999.

KMC0395E

Invalid sequence number wrap: %s.
Explanation: The sequence number wrap specified for the channel is not valid.
User Response: Correct the sequence number wrap. The value must be
greater than or equal to 100, and less than or equal to 999,999,999.

KMC0396E

Invalid trigger depth: %s.
Explanation: You specified an invalid trigger depth for the queue.
User Response: Specify a valid trigger depth. The value must be greater than
zero, and less than or equal to 999,999,999.

KMC0397E

Invalid disconnect interval: %s.
Explanation: The disconnect interval specified for the channel is not valid.
User Response: Correct the disconnect interval. The value must be greater
than or equal to zero, and less than or equal to 999,999.

KMC0398E

Invalid short retry count: %s.
Explanation: The short retry count specified for the channel is not valid.
User Response: Correct the short retry count. The value must be greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0399E

Invalid long retry count: %s.
Explanation: The long retry count specified for the channel is not valid.
User Response: Correct the long retry count. The value must be greater than
or equal to zero, and less than or equal to 999,999,999.

KM2EXPFF–KMCRCA002I

221

KMC0400E

Invalid short retry interval: %s.
Explanation: The short interval specified for the channel is not valid.
User Response: Correct the short interval. The value must be greater than or
equal to zero, and less than or equal to 999,999,999.

KMC0401E

Invalid long retry interval: %s.
Explanation: The long interval specified for the channel is not valid.
User Response: Correct the long interval. The value must be greater than or
equal to zero, and less than or equal to 999,999,999.

KMC0402E

Invalid exit name: %s.
Explanation: The exit name specified for the channel contained characters that
are not allowed for program names on the platform in question.
User Response: Specify a valid name for the send exit.
The format and maximum length of the name depends on the environment:
® On OS/2 Warp, Windows, and Windows NT, it is of the form
dllname(functionname), where dllname is specified without the suffix (".DLL).
The maximum length of the string is 128 characters.
®

On OS/390, it is a load module name, maximum length 8 characters (128
characters are allowed for exit names for client-connection channels).

KMC0403E

Invalid retry count: %s.
Explanation: The retry count specified for the channel is not valid.
User Response: Correct the retry count. The value must be greater than or
equal to zero, and less than or equal to 999,999,999.

KMC0404E

Invalid retry interval: %s.
Explanation: The retry interval specified for the channel is not valid.
User Response: Correct the retry interval. The value must be greater than or
equal to zero, and less than or equal to 999,999,999.

KMC0405E

Invalid Heartbeat Interval: %s.
Explanation: You specified an invalid heartbeat interval for the channel.
User Response: Specify a valid heartbeat interval. The value must be greater
than or equal to zero, and less than or equal to 999,999.

KMC0406E

Invalid Batch Interval: %s.
Explanation: You specified an invalid batch interval for the channel.
User Response: Specify a valid batch interval. The value must be greater than
or equal to zero, and less than or equal to 999,999,999.

KMC0407E

Invalid Port Number: %s.
Explanation: You specified an invalid port number for the Queue Manager.
User Response: Specify a valid port number. Specify a numeric IP port
number.

222

Candle Products Messages Manual (KLVHS–KONCT)

KMC0408E

Invalid Storage Class name %s.
Explanation: You specified an invalid name for the storage class.
User Response: Specify a valid storage class name. Storage class names are
restricted to a maximum of 8 characters in length.

KMC0409E

Invalid Page Set ID %s.
Explanation: You specified an invalid page set id for the storage class.
User Response: Specify a valid page set id for the storage class. The string
consists of two numeric characters, in the range 00 through 99.

KMC0410E

Invalid XCF group name %s.
Explanation: You specified an invalid IMS Bridge XCF Configuration Group
name for the storage class.
User Response: Specify a valid IMS Bridge XCF Configuration Group name
for the storage class. IMS Bridge XCF Configuration Group names are restricted to
a maximum of 8 characters in length.

KMC0411E

Invalid XCF member name %s.
Explanation: You specified an invalid IMS Bridge XCF Configuration Member
name for the storage class.
User Response: Specify a valid IMS Bridge XCF Configuration Member name
for the storage class. IMS Bridge XCF Configuration Member names are restricted
to a maximum of 8 characters in length.

KMC0412E

Authorization events not allowed on this platform.
Explanation: You have indicated that authorization events should be generated
for this Queue Manager. However, the Queue Manager is running on a platform
or version of MQSeries that does not support authorization events. Authorization
events cannot be enabled for Queue Managers running on MVS.
User Response: Disable the authorization events property for this Queue
Manager.

KMC0413E

Dead letter queue must not be specified on this platform.
Explanation: You have specified a dead letter queue name for this Queue
Manager. However, the Queue Manager is running on a platform or version of
MQSeries that does not support the dead letter queue. The dead letter queue is
not supported for MQSeries for Windows 2.1.
User Response: Blank out the dead letter queue name.

KMC0414E

SCOPE(CELL) not allowed on this platform.
Explanation: You have specified a Scope of Cell for this queue. However, the
Queue Manager is running on a platform or version of MQSeries that does not
support this. Cell scope is valid only on OS/2 Warp, UNIX systems, and Windows
NT.
User Response: Specify Scope=Queue Manager for this queue.

KM2EXPFF–KMCRCA002I

223

KMC0415E

MCATYPE(THREAD) not allowed on this platform.
Explanation: You have specified a Message Channel Agent Type of Thread for
this channel However, the Queue Manager is running on a platform or version of
MQSeries that does not support this. MCATYPE(THREAD) is supported only on
OS/2 Warp and Windows NT.
User Response: Specify Message Channel Agent Type = Process for this
channel.

KMC0416E

CONVERT(YES) not allowed on this platform.
Explanation: You have specified the convert option for this channel. However,
the Queue Manager is running on a platform or version of MQSeries that does not
support the convert option. The convert option is not supported for MQSeries for
Windows 2.1.
User Response: De-select the convert option for the channel.

KMC0417E

TCP/IP is the only valid protocol for this platform.
Explanation: You have selected a transport type other than TCP/IP for this
channel. However, the Queue Manager is running on a platform or version of
MQSeries that does not support this transport type. MQSeries for Windows 2.1
only supports TCP/IP protocol.
User Response: Specify a TCP/IP transport type for this channel.

KMC0418E

Triggers not allowed for this version of MQSeries.
Explanation: You have set the trigger option for this queue. However, the
Queue Manager is running on a platform or version of MQSeries that does not
support triggering. Triggering is not supported on MQSeries for Windows 2.1.
User Response: De-select the trigger option for the channel.

KMC0419E

Invalid primary log quantity %s.
Explanation: You specified an invalid number of primary logs for the Queue
Manager.
User Response: Specify a valid number of primary logs. The minimum is 2,
and the maximum is 62.

KMC0420E

Invalid secondary log quantity %s.
Explanation: You specified an invalid number of secondary logs for the Queue
Manager.
User Response: Specify a valid number of secondary logs. The minimum is 1,
and the maximum is 61.

KMC0421E

Invalid log file size %s.
Explanation: You specified an invalid log file size for the Queue Manager.
User Response: Specify a valid invalid log file size.
In MQSeries for UNIX systems, the minimum value is 64, and the maximum is
16384.
In MQSeries for OS/2 Warp and Windows NT, the minimum value is 32, and the
maximum is 4095.

224

Candle Products Messages Manual (KLVHS–KONCT)

KMC0422E

Invalid Default INI file %s.
Explanation: You specified an invalid default ini file for the Queue Manager.
User Response: Specify a valid Tandem NSK file name.

KMC0423E

Invalid number of execution controllers %s.
Explanation: You specified an invalid number of execution controllers for the
Queue Manager.
User Response: Specify a valid number of execution controllers. The minimum
is 1, and the maximum is 256.

KMC0424E

Invalid CCSID %s.
Explanation: You specified an invalid CCSID for the Queue Manager.
User Response: Specify a valid CCSID. Specify a number between 1 and 999.

KMC0425E

Invalid volume %s.
Explanation: You specified an invalid volume for the Queue Manager.
User Response: Specify a valid volume. Specify a valid Tandem NSK volume.

KMC0426E

Invalid TS/MP PATHMON process %s.
Explanation: You specified an invalid process name for the Queue Manager.
User Response: Specify a valid Tandem NSK TS/MP PATHMON process
name.

KMC0427E

Invalid home terminal %s.
Explanation: You specified an invalid home terminal name for the Queue
Manager.
User Response: Specify a valid Tandem NSK home terminal name.

KMC0428E

Invalid maximum message data %s.
Explanation: You specified invalid cluster workload management maximum
message data for the Queue Manager.
User Response: Specify a valid cluster workload management maximum
message data. Specify a value between zero and 4 MB for OS/390, or between
zero and 999,999,999 on other platforms.

KM2EXPFF–KMCRCA002I

225

KMC0429E

Invalid cluster name %s.
Explanation: The cluster name associated with this object is not a valid
MQSeries cluster name.
User Response: Ensure that the cluster name is valid. The character set that
can be used for naming all MQSeries objects is as follows:
® Uppercase A-Z
®

Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use
lowercase characters, and there are also restrictions on the use of lowercase
letters for OS/390 console support).

Numerics 0-9

Period (.)

Forward slash (/)

Underscore (_)

KMC0430E

Invalid network priority %s.
Explanation: You specified an invalid network priority for the channel.
User Response: Specify a valid network priority. The value must be in the
range 0 through 9.

KMC0431E

INDEXTYPE %s invalid for this version of MQSeries.
Explanation: You specified an invalid index type property for the queue.
User Response: Specify a valid index type property.
Note: The index type can only be specified for queues defined on Queue
Managers running on MVS.

KMC0432E

The selected object no longer exists in the configuration.
Explanation: The object that you selected from the topology display no longer
exists within the configuration. It may have been deleted by another user.
User Response: Close the topology window, select the View, Refresh now
option, and recreate the topology window. Retry the request.

KMC0433S

The version of the configuration framework currently installed is
incompatible with the MQSeries configuration application.
Explanation: The MQSeries Configuration workstation component is running
with an incompatible version of the configuration framework workstation
component.
User Response: Upgrade either the MQSeries configuration component or the
configuration framework workstation component to a level of full compatibility.

226

Candle Products Messages Manual (KLVHS–KONCT)

KMC0434I

Message Encryption requires Connection Authentication, however
Connection Authentication can be enabled independently of Message
Encryption. Do you wish to retain Connection Authentication?
Explanation: You have de-selected the message encryption option for the
channel. When encryption is selected, authentication is a mandatory option, so it
is marked selected and then disabled. However, authentication can be requested
by itself. This message indicates that encryption was disabled, and that you might
want to also disable connection authentication.
User Response: You should select No if connection authentication was only
selected because you wanted encryption; you should select Yes if authentication
should be retained if it is something that you still want to have.

KMC0435E

Invalid MQSS Server.
Explanation: You specified an invalid MQSS server for the Queue Manager.
User Response: Specify a valid Tandem NSK MQSeries Status Server process
name.

KMC0436E

This Configuration agent does not support the definition of client
connection channels.
Explanation: You have defined a client connection channel; however, the
Configuration Agent responsible for configuring the Queue Manager is backlevel
and does not support the definition of client connection channels.
User Response: Upgrade the Configuration Agent on the system running this
Queue Manager to at least the 3.5 level of CCC for MQSeries Configuration.

KMC0437E

A KEYPOSITION error was encountered attempting to read the Tandem
OAM Data Base.
Explanation: You have indicated that the configuration product should manage
MQSeries authorizations for this Queue Manager, running on the Tandem NSK
platform. However, the Configuration Agent encountered an error from the
KEYPOSITION service for the OAMDB file.
User Response: Examine the Configuration Agent log to determine the cause
of the failure. If the problem persists, contact Candle Customer Support.

KMC0438E

A READ error was encountered attempting to read the Tandem OAM
Data Base.
Explanation: You have indicated that the configuration product should manage
MQSeries authorizations for this Queue Manager, running on the Tandem NSK
platform. However, the Configuration Agent encountered an error from the READ
service for the OAMDB file.
User Response: Examine the Configuration Agent log to determine the cause
of the failure. If the problem persists, contact Candle Customer Support.

KMC0439E

Your request failed. The Configuration Manager was unable to locate the
MQSeries Monitoring agent.
Explanation: You entered an MQSeries command to be executed for the
resource; however, the request cannot be processed because the MQSeries
monitoring agent for the Queue Manager is not currently connected.
User Response: Start the MQSeries monitoring agent for the Queue Manager.

KM2EXPFF–KMCRCA002I

227

KMC0440E

Your request failed. The MQSeries Monitoring agent @1 returned an
unknown code @2.
Explanation: You entered an MQSeries command to be executed for the
resource; however, the request could not be processed by the MQSeries
monitoring agent, and an unanticipated return code was issued by MQSeries.
User Response: Look up the reason code in the IBM Manual MQSeries
Programmable System Management (SC33-1482), in Appendix A. Error Codes.
Take the action recommended. If the problem persists, contact Candle Customer
Support.

KMC0441E

The command text is too long for the MQSeries Monitoring agent to
handle.
Explanation: You entered an MQSeries command to be executed for the
resource; however, the request could not be processed because the text of the
command is too long.
User Response: Enter a shorter command.

KMC0442E

Your request failed. The Configuration Manager was unable to find the
command text.
Explanation: You selected the MQSeries command facility; however, the
request could not be processed because the command text is missing.
User Response: Enter a valid MQSeries command.

KMC0443I

Your MQSeries command was successfully submitted.
Explanation: Your MQSeries command was successfully processed.
User Response: None.

KMC0444E

Your request failed. The command was rejected by MQSeries.
Explanation: You entered an MQSeries command to be executed for the
resource; however, the request could not be processed by MQSeries, probably
because of invalid syntax.
User Response: Correct the syntax of the MQSeries command and re-submit.

KMC0445E

Your request to delete Queue Manager @1 failed. The Queue Manager is
a member of a managed cluster.
Explanation: You attempted to delete a Queue Manager; however, the Queue
Manager is currently part of a managed cluster, and cannot be deleted.
User Response: Delete all cluster Queue Manager objects referencing this
Queue Manager, then re-attempt the delete request.

KMC0446E

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 (%).

228

Candle Products Messages Manual (KLVHS–KONCT)

KMC0447E

Invalid application type: %s.
Explanation: You entered an invalid application type for the process.
User Response: Enter a valid application type. The application type should be
either one of the pre-defined keywords which appear in the drop-down list, or a
numeric value between 65,536 and 999,999,999 (indicating a user-defined
application type).

KMC0448E

Queue manager @1 could not be started. There was an error starting the
channel listener.
Explanation: The Configuration Manager attempted to start the Queue
Manager, and you had previously indicated in the Queue Manager settings that
the channel listener should be automatically started. However, an error was
encounted attempting to start the channel listener.
User Response: Examine the log for the Configuration Agent to determine
why the channel listener could not be started.

KMC0449E

Queue manager @1 could not be started. There was an error starting the
channel initiator.
Explanation: The Configuration Manager attempted to start the Queue
Manager, and you had previously indicated in the Queue Manager settings that
the channel initiator should be automatically started. However, an error was
encounted attempting to start the channel initiator.
User Response: Examine the log for the Configuration Agent to determine
why the channel initiator could not be started.

KMC0450E

Queue manager @1 could not be started. There was an error starting the
trigger monitor.
Explanation: The Configuration Manager attempted to start the Queue
Manager, and you had previously indicated in the Queue Manager settings that
the trigger monitor should be automatically started. However, an error was
encounted attempting to start the trigger monitor.
User Response: Examine the log for the Configuration Agent to determine
why the trigger monitor could not be started.

KMC0451E

Invalid autostart trigger monitor value.
Explanation: You specified an invalid start trigger monitor property for the
Queue Manager.
User Response: Specify a valid start trigger monitor property.

KMC0452E

Invalid QSGDISP value.
Explanation: You specified an invalid queue sharing group disposition property
for the Queue Manager.
User Response: Specify a valid queue sharing group disposition property.

KM2EXPFF–KMCRCA002I

229

KMC0453E

This QSGDISP value is not supported on this version of MQSeries.
Explanation: You specified a queue sharing group disposition other than
’Queue Manager’ on a unsupported version of MQSeries.
User Response: Specify a valid queue sharing group disposition property.
Note: The Queue Manager must be running on MQSeries 2.2 for OS/390 in
order for you to specify a value other than Queue Manager.

KMC0454E

Invalid CLUSDISP value.
Explanation: You specified an invalid queue sharing group cluster disposition
property.
User Response: Specify a valid queue sharing group cluster disposition
property.

KMC0455E

This CLUSDISP value is not supported on this version of MQSeries.
Explanation: You specified a queue sharing group cluster disposition other than
’Queue Manager’ on a unsupported version of MQSeries.
User Response: Specify a valid queue sharing group cluster disposition
property.
Note: The Queue Manager must be running on MQSeries 2.2 for OS/390 in
order for you to specify a value other than Queue Manager.

KMC0456E

Invalid CFSTRUCT value @2.
Explanation: You specified an invalid queue sharing group coupling facility
structure name.
User Response: Specify a valid name for the coupling facility structure.
Coupling facility structure names are restricted to a maximum of 12 characters in
length. The first character must be in the range A through Z, and the subsequent
characters must be in the range A-Z, 0-9.

KMC0457E

You cannot alter the QSGDISP value once the actual resource has been
created.
Explanation: You are attempting to alter the queue sharing group disposition
property. However, the property cannot be changed, either because this object is
based on a prototype, or because the actual object corresponding to this defined
object already exists. MQSeries does not permit the QSGDISP property of an
object to be modified once the actual object exists.
User Response: You must delete and redefine this object in order to change
the queue sharing group disposition property.

KMC0458E

You cannot alter the CLUSDISP value once the actual resource has been
created.
Explanation: You are attempting to alter the queue sharing group coupling
facility structure name; However, the name cannot be changed, either because
this object is based on a prototype, or because the actual object corresponding to
this defined object already exists. MQSeries does not permit the QSGDISP
property of an object to be modified once the actual object exists.
User Response: You must delete and redefine this object in order to change
the queue sharing group coupling facility structure name.

230

Candle Products Messages Manual (KLVHS–KONCT)

KMC0459E

Your request failed. Unknown MQSeries object name.
Explanation: The actual object does not exist.
User Response: Specify a valid object name.

KMC0461E

Invalid coupling facility structure @1.
Explanation: The coupling facility structure name you entered is invalid.
User Response: Specify a valid coupling structure name. It must begin with an
alphabetic character, followed by alphanumeric characters. The maximum length
is 12 characters.

KMC0462E

Principal or group @1 already exists in the authorization list.
Explanation: You attempted to add a user or group name to the authorization
list that already exists on the list.
User Response: Specify a user or group name that doesn’t already exist on the
list.

KMC0463E

You must identify the new entry as a principal or a group.
Explanation: You attempted to add a new entry to the authorization list, but you
didn’t indicate whether the new entry represents a principle or a group.
User Response: Select either ’Principle’ or ’Group’ as the Type for the new
entry.
Note: ’Principle’ is only valid if the Queue Manager is running on Windows NT.

KMC0464E

The channel is defined with QSGDISP(SHARED), but the transmit queue
@1 is not shared.
Explanation: You defined a sender or server channel with a Queue Sharing
Group Disposition of Shared; however, the transmit queue referenced by the
channel is not a shared queue.
User Response: Either change the definition of the QSGDISP property for the
channel to something other than Shared, or reference a shared transmit queue
within the channel definition.

KMC0465E

Index type of Message Token is not value for shared queues.
Explanation: You defined a local queue with an Index type of MSGTOKEN;
however, the Queue Sharing Group Disposition for the queue is Shared. These
properties are mutually exclusive.
User Response: Either specify a different value for the Index type, or change
the QSGDISP of the queue to something other than Shared.

KMC0466E

The maximum message length for a shared queue cannot exceed 64,512.
Explanation: You specified a maximum message length greater than 64,512 for
a shared queue.
User Response: Specify a smaller maximum message length.

KM2EXPFF–KMCRCA002I

231

KMC0467S

The authorization specification provided to the SETMQAUT command
contained one or more items that could not be interpreted.
Explanation: The authorization specification provided to the SETMQAUT
command by the Configuration Agent contained one or more items that could not
be interpreted.
User Response: Collect the agent and CMS log files, and call Candle Customer
Support.

KMCRCA002I

Candle WebSphere MQ Configuration Agent Starting Up.
Explanation: This message is produced on OS/390 only at agent startup, if the
CICAT value for "Enable startup console messages" was set to Y during
installation. It may be used by Automation software to detect that the agent has
started.
System Action: None.
User Response: None.

232

Candle Products Messages Manual (KLVHS–KONCT)

KMQxx001E–KOCJ0046

KMQxx001E

PARAMETER ERROR ON DOMAIN CALL. THE GATE BEING CALLED
WAS call. THE PARAMETER IN ERROR WAS xx.
Explanation: This is a generic message that can be issued from any CCC for
MQSeries component. It indicates that an internal error has occurred on a call to a
CCC for MQSeries GATE call. The message text xx is diagnostic information.
System Action: The error is propagated to the calling module.
User Response: Note the message text and contact Candle Customer Support.

KMQxx002E

ERROR INITIALIZING component DOMAIN.
Explanation: This is a generic message that can be issued from any CCC for
MQSeries component. It indicates that an internal error has occurred during
initialization of the specified component.
System Action: Initialization does not complete successfully.
User Response: Note the message text and contact Candle Customer Support.

KMQxx003E

IDERROR ON DOMAIN CALL. CALLING MODULE module - GATE
CALLED WAS call.
Explanation: This is a generic message that can be issued from any CCC for
MQSeries component. It indicates that an internal error has occurred on a call to a
CCC for MQSeries GATE call.
System Action: The error is propagated to the calling module.
User Response: Note the message text and contact Candle Customer Support.

KMQxx004E

LOGIC ERROR ON DOMAIN CALL CALLING MODULE module - GATE
CALLED call RESPONSE = rs - REASON = rc
Explanation: This is a generic message that can be issued from any CCC for
MQSeries component. It indicates that an internal error has occurred on a call to a
CCC for MQSeries GATE call.
System Action: The error is propagated to the calling module.
User Response: Note the message text and contact Candle Customer Support.

KMQxx001E–KOCJ0046

233

KMQxx005E

COMPONENT TRACE FAILED TO INITIALIZE FOR THE component
COMPONENT
Explanation: This is a generic message that can be issued from any CCC for
MQSeries component. It indicates that an internal error has occurred during trace
initialization for the specified component.
System Action: Tracing is not activated for the specified component.
User Response: None. If tracing is required and cannot be activated contact
Candle Customer Support.

KMQCI101E

BASE STARTUP ALREADY IN PROGRESS
Explanation: A KMQCMD to start CCC for MQSeries has been entered, but a
prior KMQCMD is still being processed.
System Action: The command is not executed.
User Response: Wait for the original KMQCMD to complete.

KMQCI102W

BASE STARTUP ALREADY COMPLETED
Explanation: Startup of CCC for MQSeries has already completed.
System Action: The current command is not executed.
User Response: None. This is information.

KMQCI103E

BASE STARTUP FAILURE - STORAGE ALLOCATION ERROR
Explanation: CCC for MQSeries initialization failed because of a virtual storage
shortage.
System Action: CCC for MQSeries initialization fails.
User Response: Increase the Candle Management Server (CMS) address space
memory allocation and restart it.

KMQCI104E

BASE STARTUP FAILURE - module ROUTINE FAILED
Explanation: CCC for MQSeries could not initialize because the named
initialization module failed.
System Action: CCC for MQSeries did not initialize.
User Response: Note the message text and contact Candle Customer Support.

KMQCI105I

OMEGAMON FOR WEBSPHERE MQ BASE INITIALIZATION COMPLETE
Explanation: Initialization of the OMEGAMON XE or DE for WebSphere MQ
base functions have completed successfully.
System Action: Processing continues.
User Response: None. This is a confirmation message.

KMQCI106E

INVALID MAJOR COMMAND
Explanation: The major verb on the KMQCMD command is invalid.
System Action: The command is not executed.
User Response: Correct the KMQCMD command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

234

Candle Products Messages Manual (KLVHS–KONCT)

KMQCI107E

INVALID MINOR COMMAND
Explanation: The minor verb on the KMQCMD command is invalid.
System Action: The command is not executed.
User Response: Correct the KMQCMD command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI108E

INVALID KEYWORD keyword
Explanation: The named keyword in the KMQCMD command is invalid.
System Action: The command is not executed.
User Response: Correct the KMQCMD command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI109E

INVALID VALUE value FOR KEYWORD keyword
Explanation: The indicated value associated with the named keyword on the
KMQCMD command is invalid.
System Action: The command is not executed.
User Response: Correct the KMQCMD command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI110E

COMMAND NOT SUPPORTED
Explanation: CCC for MQSeries does not support the KMQCMD command
entered.
System Action: The command is not executed.
User Response: Correct the KMQCMD command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI111E

COMMAND PROCESSING ERROR - FUNCTION func RESPONSE = rs
REASON = rc
Explanation: An error occurred in the processing of the KMQCMD operator
command.
System Action: The command is not executed.
User Response: Search the TLVLOG for prior errors indicating the nature of
the problem. If the problem persists, contact Candle Customer Support.

KMQCI112E

STARTUP ALREADY IN PROCESS
Explanation: A KMQCMD PERFORM STARTUP command was entered, but
CCC for MQSeries has already been started.
System Action: The command is not executed.
User Response: None. This is an informational message only.

KMQCI113W

STARTUP ALREADY COMPLETED
Explanation: A KMQCMD PERFORM STARTUP was entered, but CCC for
MQSeries startup has already completed.
System Action: The command is not executed.
User Response: None. This is an informational message only.

KMQxx001E–KOCJ0046

235

KMQCI114E

UNABLE TO LOAD DOMAIN INITIALIZATION MODULE
Explanation: CCC for MQSeries module KMQACIVC could not be loaded.
System Action: Processing of the KMQCMD PERFORM STARTUP command
terminates.
User Response: Contact Candle Customer Support.

KMQCI116I

VALIDATE COMMAND COMPLETED SUCCESSFULLY
Explanation: The set of commands contained within the member specified by
the LIST parameter on the KMQCMD PERFORM STARTUP command was
successfully checked and validated.
System Action: The commands within the LIST member will be executed
when CCC for MQSeries initialization completes.
User Response: None. This is a confirmation message.

KMQCI117E

$PAM request FAILED - RETURN CODE = rc
Explanation: While attempting to process the LIST member of the KMQCMQ
PERFORM STARTUP command, the named CT/ENGINE $PAM request failed
with return code rc from the service.
System Action: The KMQCMD PERFORM STARTUP command fails.
User Response: Validate the member name specified by the LIST parameter.
Ensure that the member exists in the RKANCMD dataset. If problems persist,
contact Candle Customer Support.

KMQCI118E

LIST OPERAND MISSING
Explanation: The LIST operand on a KMQCMD PERFORM STARTUP
command is missing.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI119E

OMEGAMON FOR WEBSPHERE MQ NOT ACTIVE - UNABLE TO
PROCESS
Explanation: A KMQCMD PERFORM SHUTDOWN command was entered,
but OMEGAMON XE or DE for WebSphere MQ is not active.
System Action: The command is not executed.
User Response: None. This is a confirmation message.

KMQCI120E

SHUTDOWN ALREADY IN PROGRESS
Explanation: A KMQCMD PERFORM SHUTDOWN command was entered,
but CCC for MQSeries is already in the process of a shutdown.
System Action: The command is not executed.
User Response: Wait for the original shutdown request to complete.

KMQCI121I

SHUTDOWN IS IN PROGRESS
Explanation: Shutdown of CCC for MQSeries has begun.
System Action: None.
User Response: None. This is a confirmation message.

236

Candle Products Messages Manual (KLVHS–KONCT)

KMQCI122E

SAMPLE INTERVAL TIME MISSING
Explanation: A KMQCMD PERFORM STARTMON command was entered, but
the sample interval time associated with the SAMPINT keyword is missing.
System Action: The command is not executed.
User Response: Correct the KMQCMD PERFORM STARTMON command
and resubmit it. For complete KMQCMD command descriptions, see the Candle
Command Center User’s Guide for MQSeries.

KMQCI123I

PERFORM STARTMON COMMAND PROCESSED SUCCESSFULLY
Explanation: The KMQCMD PERFORM STARTMON command was processed
successfully.
System Action: None.
User Response: None. This is a confirmation message.

KMQCI124W

MONITORING ALREADY ACTIVE
Explanation: A KMQCMD PERFORM STARTMON command was entered, but
monitoring is already active.
System Action: The command is not executed.
User Response: None. This is an informational message only.

KMQCI125E

NAME PARAMETER MISSING
Explanation: A SET GROUP, SET HISTORY, SET QUEUE, or SET CHANNEL
command was entered, but the NAME parameter was missing from the
command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI126I

SET GROUP COMMAND PROCESSED SUCCESSFULLY
Explanation: A SET GROUP command was processed successfully.
System Action: None.
User Response: None. This is a confirmation message.

KMQCI127E

LIKE NAME NOT FOUND
Explanation: A SET GROUP or SET MANAGER command was entered with
the LIKE parameter, but the group or manager specified by the LIKE parameter
was not previously defined.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQxx001E–KOCJ0046

237

KMQCI128E

NAME OR SUBSYS PARAMETER REQUIRED
Explanation: A SET MANAGER command was entered without the required
NAME or SUBSYS parameter.
System Action: The command is not executed.
User Response: Correct the SET MANAGER command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI129E

INCONSISTENT PARAMETERS SPECIFIED FOR STATUS
Explanation: A SET MANAGER command was entered with parameters that
conflict with the STATUS(DELETE) or STATUS(RESET) parameters.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI130I

SET MANAGER COMMAND PROCESSED SUCCESSFULLY
Explanation: The SET MANAGER command was processed successfully.
System Action: None.
User Response: None. This is a confirmation message.

KMQCI131E

NICKNAME DUPLICATES EXISTING MANAGER
Explanation: A SET MANAGER command was entered with a NICKNAME that
duplicates an existing MANAGER or NICKNAME.
System Action: The command is not executed.
User Response: Correct the SET MANAGER command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI132E

GROUP NAME NOT FOUND
Explanation: The SET MANAGER command was specified with a GROUP that
does not exist.
System Action: The command is not executed.
User Response: Correct the SET MANAGER command and resubmit it. For
complete KMQCMD command descriptions, see the Candle Command Center
User’s Guide for MQSeries.

KMQCI133E

INCONSISTENT NAME AND SUBSYS PARAMETERS
Explanation: A SET MANAGER command specifies a NAME and SUBSYS
parameter, but these names are inconsistent with a previous SET MANAGER
command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

238

Candle Products Messages Manual (KLVHS–KONCT)

KMQCI134E

DUPLICATE MANAGER FOR STATUS(ADD)
Explanation: A SET MANAGER command specifies the STATUS(ADD)
parameter, but a prior SET MANAGER command for this queue manager name
was entered.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI135E

MANAGER NOT FOUND
Explanation: The queue manager name specified on a SET QUEUE or SET
CHANNEL command was not defined by a prior SET MANAGER command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI136E

CHANNEL NOT FOUND
Explanation: A SET CHANNEL command with the STATUS(DELETE)
parameter was entered, but the NAME was not specified in a prior SET
CHANNEL command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI137E

DUPLICATE CHANNEL
Explanation: A SET CHANNEL command with the STATUS(ADD) parameter
was entered, but the NAME specified was defined by a prior SET CHANNEL
command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI138E

QUEUE NOT FOUND
Explanation: A SET QUEUE command with the STATUS(DELETE) parameter
was entered, but the NAME specified was not defined by a prior SET QUEUE
command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQxx001E–KOCJ0046

239

KMQCI139E

DUPLICATE QUEUE
Explanation: A SET QUEUE command with the STATUS(ADD) parameter was
entered, but the NAME specified was defined by a prior SET QUEUE command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI140E

MGRNAME PARAMETER MISSING
Explanation: The MGRNAME parameter was missing from the SET CHANNEL
or SET QUEUE command.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI141E

INVALID STATUS PARAMETER
Explanation: The STATUS parameter on the SET command is invalid.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI142I

SET CHANNEL COMMAND PROCESSED SUCCESSFULLY
Explanation: The SET CHANNEL command was processed successfully.
System Action: None.
User Response: None. This is a confirmation message.

KMQCI143I

SET QUEUE COMMAND PROCESSED SUCCESSFULLY
Explanation: The SET QUEUE command was processed successfully.
System Action: None.
User Response: None. This is a confirmation message.

KMQCI144E

NULL COMMAND IGNORED
Explanation: A KMQCMD command was entered with no operands.
System Action: The command is not executed.
User Response: Correct the command and resubmit it. For complete
KMQCMD command descriptions, see the Candle Command Center User’s
Guide for MQSeries.

KMQCI145I

COMMAND command ISSUED
Explanation: The named command was returned and processed.
System Action: The command is executed.
User Response: None. This is a confirmation.

240

Candle Products Messages Manual (KLVHS–KONCT)

KMQCI146E

TRACE HEAD NODE INITIALIZATION FAILED. RC=rc RSN=rs
Explanation: CCC for MQSeries failed to define a trace to MVS/ESA
component trace services. The return code rc and reason code rs are the hex
return codes from the CTRACE DEFINE macro call or an internal CCC for
MQSeries error.
System Action: Processing continues but component tracing may not be
available.
User Response: Determine why the CTRACE DEFINE failed by referring to
the MVS/ESA Authorized Assembler Reference ALE-DYN for the return and
reason codes for the CTRACE macro. If the return code is not described in this, an
internal CCC for MQSeries error has occurred. Note the message text and return
codes and contact Candle Customer Support.

KMQCI147E

module SUB-TRACE INITIALIZATION FAILED. RC=rc RSN=rs
Explanation: CCC for MQSeries failed to define a trace to MVS/ESA
component trace services for the named sub-trace component. The return code rc
and reason code rs are the hexadecimal return codes from the CTRACE DEFINE
macro call or an internal CCC for MQSeries error.
System Action: Processing continues but component tracing may not be
available.
User Response: Determine why the CTRACE DEFINE failed by referring to
the MVS/ESA Authorized Assembler Reference ALE-DYN for the return and
reason codes for the CTRACE macro. If the return code is not described in this, an
internal CCC for MQSeries error has occurred. Note the message text and return
codes and contact Candle Customer Support.

KMQCI148E

ONLY ONE OF MGRNAME, RMGRNAME OR GROUP MAY BE SPECIFIED
Explanation: The KMQCMD SET QUEUE or SET CHANNEL command has
been entered with incompatible operands.
System Action: Processing of the command is aborted.
User Response: Choose one of MGRNAME (manager name), RMGRNAME
(remote manager name) or GROUP (group name) operands to specify for the
given queue or channel mask being set and reenter the command.

KMQCI149W

MSGSECURITY IS OBSOLETE; USE MSGACCESS
Explanation: The MSGSECURITY keyword has been used on the SET
MANAGER command and it is no longer valid. It has been replaced by the
MSGACCESS keyword.
System Action: The keyword is ignored.
User Response: Use the MSGACCESS keyword on the SET MANAGER
COMMAND to specify one of the following message functions security levels for
the queue manager: NONE, DESC, RETRY, DATA, or DELETE. For more
information about these parameters, see the Customizing Monitoring Options
topic found in your version of the product documentation.

KMQxx001E–KOCJ0046

241

KMQCI150E

RMANAGER NAME CANNOT BE GENERIC
Explanation: A KMQCMD SET RMANAGER command has been entered with
the name operand specified as a mask.
System Action: Processing of the command is aborted.
User Response: Reenter the SET RMANAGER command with a specific name
of a remote MQ manager to be monitored.

KMQCI151I

SET RMANAGER COMMAND PROCESSED SUCCESSFULLY
Explanation: The KMQCMD SET RMANAGER command has been entered
and processed successfully.
System Action: None.
User Response: None. This is a confirmation message.

KMQCI152E

BOTH MGRNAME AND RMGRNAME CANNOT BE SPECIFIED
Explanation: The KMQCMD DISPLAY SETTINGS command has been entered
with incompatible operands.
System Action: Processing of the command is aborted.
User Response: Choose one of MGRNAME (manager name) or RMGRNAME
(remote manager name) operands to specify and reenter the command.

KMQCI153W

qopen or maxevent KEYWORD IS OBSOLETE
Explanation: The qopen or maxevent keyword is no longer used on the SET
MANAGER or SET GROUP commands.
System Action: The keyword is ignored.
User Response: Remove the keyword from SET MANAGER or SET GROUP
commands.

KMQCI154E

GROUP, MGRNAME OR RMGRNAME MUST BE SPECIFIED
Explanation: A monitoring option for the agent, for example a SET EVENTQIN
or SET EVENTQOUT or SET MQIMONITOR command, was entered without
one of the required parameter options: GROUP, MGRNAME, or (rarely)
RMGRNAME.
System Action: The command is ignored.
User Response: Correct and resubmit the command. Refer to the Customizing
Monitoring Options topic found in your version of the product documentation.

KMQCI155E

THE REMOTE MANAGER SPECIFIED IN THE EVENTQIN/OUT COMMAND
HAS NOT BEEN DEFINED. IT MUST BE DEFINED BEFORE THIS
COMMAND IS ISSUED
Explanation: The syntax for the SET EVENTQIN or SET EVENTQOUT
command was correct, but the queue manager specified in the RMANAGER
option has not been defined to CCC for MQSeries.
System Action: The command is ignored.
User Response: Use the SET RMANAGER command to define the remote
queue manager; then resubmit the command. For instructions on using SET
RMANAGER, see the Customizing Monitoring Options topic found in your
version of the product documentation.

242

Candle Products Messages Manual (KLVHS–KONCT)

KMQCI156E

THE GROUP SPECIFIED IN THE EVENTQIN/OUT COMMAND DOES NOT
EXIST. THE GROUP MUST BE DEFINED BEFORE THIS COMMAND IS
ISSUED
Explanation: The syntax for the SET EVENTQIN or SET EVENTQOUT
command was correct, but the group name specified in the GROUP option has
not been defined to CCC for MQSeries.
System Action: The command is ignored.
User Response: Use the SET GROUP command to define the remote queue
manager; then resubmit the command. For instructions on using SET GROUP,
refer to the Candle Command Center User’s Guide for MQSeries.

KMQCI157I

SET EVENTQIN/OUT COMMAND PROCESSED SUCCESSFULLY
Explanation: CCC for MQSeries accepted the SET EVENTQIN or SET
EVENTQOUT command.
System Action: The command is processed.
User Response: None. This is an informational message.

KMQCI158E

THE MANAGER NAME SPECIFIED IN THE EVENTQIN/OUT COMMAND
HAS NOT BEEN DEFINED. IT MUST BE DEFINED BEFORE THIS
COMMAND IS ISSUED
Explanation: The syntax for the SET EVENTQIN or SET EVENTQOUT
command was correct, but the manager name specified in the MGRNAME option
has not been defined to CCC for MQSeries.
System Action: The command is ignored.
User Response: Use the SET MANAGER command to define the remote
queue manager; then resubmit the command. For instructions on using SET
MANAGER, refer to the Candle Command Center User’s Guide for MQSeries.

KMQCI301I

GROUP(group_name) IS ESTABLISHED WITH FOLLOWING
SPECIFICATIONS: DEFAULT(YES|NO) EVENTS(REMOVE|BROWSE|NO)
REMOTEQ(remote_queue_name) AGGRHIST(aggregation_samples)
RETAINHIST(historical_aggregation_value)
Explanation: This message is issued in response to the DISPLAY SETTINGS
command and displays information from the previously issued SET GROUP
command(s).
System Action: None.
User Response: None. This is an informational message only.

KMQCI302I

MANAGER SET(manager_name_mask) IS ESTABLISHED WITH
FOLLOWING SPECIFICATIONS: GROUP(group_name)
SYSNAME(MVS_system_id) EVENTS(REMOVE|BROWSE|NO)
ACTIVE(YES|NO) AGGRHIST(aggregation_samples)
RETAINHIST(historical_aggregation_value)
Explanation: This message is issued in response to the DISPLAY SETTINGS
command and displays information from the previously issued SET MANAGER
command(s).
System Action: None.
User Response: None. This is an informational message only.

KMQxx001E–KOCJ0046

243

KMQCI303I

MQ MANAGER (manager_name) IN SET(manager_name_mask) IS
MONITORED
Explanation: This message is issued in response to the DISPLAY SETTINGS
command.
System Action: None.
User Response: None. This is an informational message only.

KMQCI304I

QUEUE SET(queue_name_mask) TYPES(queue_types) IS ESTABLISHED
Explanation: This message is issued in response to the DISPLAY SETTINGS
command and displays information from the previously issued SET QUEUE
command. Queue types can be any combination of the following: PREDEFINED,
PERMDYN, TEMPDYN or ALL.
System Action: None.
User Response: None. This is an informational message only.

KMQCI305I

QUEUE SET(queue_name_mask) TYPES(queue_types) IS SUPERSEDED
Explanation: This message is issued in response to the DISPLAY SETTINGS
command and displays information from the previously issued SET QUEUE
command. The specified queue_name_mask was superseded by another
queue_name_mask. Queue types can be any combination of the following:
PREDEFINED, PERMDYN, TEMPDYN or ALL.
System Action: This mask is not executed.
User Response: None. This is an informational message only.

KMQCI306I

CHANNEL SET(channel_name_mask) IS ESTABLISHED
Explanation: This message is issued in response to the DISPLAY SETTINGS
command and displays information from the previously issued SET CHANNEL
command.
System Action: None.
User Response: None. This is an informational message only.

KMQCI307I

MSGACCESS(parm) ICYCLE(interval_cycle) HLQ(high_level_qualifier)
Explanation: This message is issued in response to the DISPLAY SETTINGS
command and displays supplemental information from previously issued SET
commands such as SET GROUP, SET MANAGER, or SET RMANAGER.
System Action: None.
User Response: None. This is an informational message only.

KMQCI308I

RMANAGER SET(manager_name_mask) IS ESTABLISHED WITH
FOLLOWING SPECIFICATIONS: GROUP(group_name)
EVENTS(REMOVE|BROWSE|NO) ACTIVE(YES|NO)
REMOTEQ(remote_queue_name) AGGRHIST(aggregation_samples)
RETAINHIST(historical_aggregation_value)
Explanation: This message is issued in response to the DISPLAY SETTINGS
command, displays information from the previously issued SET RMANAGER
command, and displays information about remote manager settings.
System Action: None.
User Response: None. This is an informational message only.

244

Candle Products Messages Manual (KLVHS–KONCT)

KMQCI309I

REMOTE MQ MANAGER mgr IS MONITORED VIA ROUTE LOCAL
MANAGER mgr
Explanation: The KMQCMD DISPLAY SETTINGS command is showing that
the specified remote manager is monitored using a connection with the specified
local manager.
System Action: None.
User Response: None. This is an informational message only.

KMQCI310I

TOTAL NUMBER OF MONITORED QUEUES IS nnnnnnnn, TOTAL
NUMBER OF MONITORED CHANNELS IS nnnnnnnn
Explanation: This message is issued in response to the DISPLAY SETTINGS
command if the MGRNAME was specified. It displays the number of queues and
channels monitored for the specified queue manager.
System Action: None.
User Response: None. This is an informational message only.

KMQCI311I

ROUTE(route_list)
Explanation: The KMQCMD DISPLAY SETTINGS command is continuing to
display information about a GROUP or RMANAGER by showing the ROUTE list
which has been set.
System Action: None.
User Response: None. This is an informational message only.

KMQCI312I

RUSERID(remote_userID)
Explanation: The KMQCMD DISPLAY SETTINGS command is continuing to
display information about a GROUP or RMANAGER by showing the remote
userID that has been set.
System Action: None.
User Response: None. This is an informational message only.

KMQCI313I

REPLYTOQMGR(manager_name)
Explanation: This message is one of several possible messages given in
response to a KMQCMD DISPLAY SETTINGS command. It gives the
REPLYTOQMGR name specified for the group or remote queue manager being
addressed by the response.
System Action: None.
User Response: None.

KMQCI315W

MQ MANAGER (manager_name) IS ACTIVE BUT NOT MONITORED
BECAUSE reason_text
Explanation: This message is issued in response to the DISPLAY SETTINGS
command if the queue manager name is active but monitoring failed. The
reason_text can be one of the following:
1.NO SET MANAGER BLOCK WAS FOUND
2.MONITORING IS INITIALIZING
3.MONITORING IS BEING TERMINATED
4.INVALID SET MANAGER BLOCK WAS FOUND
5.SET MANAGER BLOCK WAS IN USE

KMQxx001E–KOCJ0046

245

6.SET MANAGER BLOCK IS NOT ACTIVE
7.SET MANAGER BLOCK HAS AFFINITY TO A DIFFERENT SYSTEM
8.MQSERIES VERSION IS NOT SUPPORTED
9.MONITORING FAILED
10.:OF UNDETERMINED REASON
System Action: None.
User Response: Depending on the reason, do one of the following:
® For reasons 1, 6, 7, issue the corrected SET MANAGER command.
®

For reasons 2 and 3, no response is necessary.

For reasons 4, 5, 8, and 9, contact Candle Customer Support.

For reason 10, reissue the DISPLAY SETTINGS command. This reason may
occur during the transition from one state to another.

KMQCI316I

MQ MANAGER (manager_name) IS NOT ACTIVE
Explanation: This message is issued in response to the DISPLAY SETTINGS
command if the manager_name for the specified queue manager is not active.
System Action: None.
User Response: None. This is an informational message only.

KMQCI317W

REMOTE MQ MANAGER manager_name SET NOT FOUND
Explanation: The KMQCMD DISPLAY SETTINGS could not find remote
manager manager_name given in the RMGRNAME parameter. A SET
RMANAGER command has not been issued for this remote manager.
System Action: None.
User Response: None.

KMQCI318W

REMOTE MQ MANAGER manager_name IS NOT MONITORED BECAUSE
reason_text
Explanation: This message is issued in response to the DISPLAY SETTINGS
command when a remote manager which has been specified for monitoring via a
SET RMANAGER command, is not being monitored because of the given reason.
The reason_text can be one of the following:
1.NO SET MANAGER BLOCK WAS FOUND
2.MONITORING IS INITIALIZING
3.MONITORING IS BEING TERMINATED
4.INVALID SET MANAGER BLOCK WAS FOUND
5.SET MANAGER BLOCK WAS IN USE
6.SET MANAGER BLOCK IS NOT ACTIVE
7.SET MANAGER BLOCK HAS AFFINITY TO A DIFFERENT SYSTEM
8.MQSERIES VERSION IS NOT SUPPORTED
9.MONITORING FAILED
10.OF UNDETERMINED REASON
System Action: None.

246

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Depending on the reason, do one of the following:
® For reasons 1, 6, 7, issue the corrected SET RMANAGER command.
®

For reasons 2 and 3, no response is necessary.

For reasons 4, 5, 8, and 9, contact Candle Customer Support.

For reason 10, reissue the DISPLAY SETTINGS command. This reason may
occur during the transition from one state to another.

KMQCI320I

DISPLAY COMPLETE
Explanation: The DISPLAY Settings command was processed successfully.
System Action: None.
User Response: None. This is a confirmation.

KMQCI321I

COMMAND NOT VALID BEFORE STARTUP HAS COMPLETED
Explanation: The specified KMQCMD command cannot be entered prior to
completion of initialization of CCC for MQSeries.
System Action: None.
User Response: None.

KMQCI322I

event_queuein or event_queueout: QMGRQ
(queue_manager_event_queue): PERFMQ (performance_event_queue):
CHANNELQ (channel_event_queue)
Explanation: This message is issued in response to a Display Settings
command. It provides information about the names defined using the SET
EVENTQIN and SET EVENTQOUT commands.
System Action: None. This message is informational.
User Response: None.

KMQCI323I

APPLICATION SET(applid_mask) IS ESTABLISHED WITH THE
FOLLOWING SPECIFICATIONS: TRANPGM(tranpgm_mask)
MGRNAME(queue_manager_name_mask) STATISTICS(level)
TRACE(level) TRACELIMIT(nnnnnnnn)
Explanation: This message is one of several possible messages given in
response to a KMQCMD DISPLAY SETTINGS command. It displays the
monitored CCC for MQSeries application sets.
System Action: None.
User Response: None.

KMQCI324I

TRACELIMIT REMAINDER IS nnnnnnnn; nnnnnnnn TRACE RECORDS
WRITTEN FOR THIS SET
Explanation: This message is displayed in response to a KMQCMD DISPLAY
SETTINGS command. It follows the message KMQCI323I and displays the
number of trace entries remained to be written and the number of trace records
written for the application set described in the previous KMQCI323I message.
System Action: None. This message is informational only.
User Response: None.

KMQCI330I

SET QSG COMMAND PROCESSED SUCCESSFULLY
Explanation: The control statement has been read and processed successfully.

KMQxx001E–KOCJ0046

247

System Action: Options specified on this command are now in effect.
User Response: None. This is an informational message.
KMQCI331E

SET QSG COMMAND FAILED RC(rc) REASON(reason)
Explanation: The processing of the SET QSG statement has unexpectedly
failed.
System Action: Processing continues.
User Response: Correct options specified on the command and reissue the
command.

KMQCI340I

QSG CHECKING INTERVAL IS interval SECONDS
QSG XCF GROUP NAME IS group
Explanation: QSG processing will proceed with the indicated options.
System Action: Processing continues.
User Response: None. This is an informational message.

KMQCI341I

QSG NAME(qsgname) MONITOR(monitorname) MGRNAME(mgrname)
Explanation: The indicated QSG options have been set.
System Action: Processing continues.
User Response: None. This is an informational message.

KMQCR002I

Candle WebSphere MQ agent starting up.
Explanation: This messsage is produced on OS/390 only at agent startup, if the
CICAT value for "Enable startup console messages" was set to Y during
installation. It may be used by Automation software to detect that the agent has
started.
System Action: None.
User Response: None.

KMQCT127I

MESSAGE WITH MSGID(msgid) AND CORRELID(correlid) IS DELETED
FROM QUEUE(qname) IN QMGR(mgrname)
Explanation: This message confirms that the delete action was successful.
System Action: The specified message is deleted from the queue.
User Response: None. This is a confirmation.

KMQCT128I

MESSAGE WITH MSGID(msgid) AND CORRELID(correlid) IS RETRIED
FROM QUEUE(dlqname) IN QMGR(mgrname) TO QUEUE(qname) IN
QMGR(mgrname2)
Explanation: This message confirms that the retry action was successful. The
message was moved from the dead-letter queue to the intended queue as
specified.
System Action: The specified message is successfully delivered to the intended
queue.
User Response: None. This is a confirmation.

248

Candle Products Messages Manual (KLVHS–KONCT)

KMQCT129I

ALL MESSAGES WITH GROUPID=groupID HAVE BEEN DELETED FROM
QUEUE=queue IN QUEUE MANAGER=qmgr
Explanation: All messages with the specified groupID have been deleted
successfully from the specified queue in queue manager qmgr.
System Action: None.
User Response: None.

KMQCT130I

ALL MESSAGES WITH GROUPID =groupID HAVE BEEN PUT TO
QUEUE=queue IN QUEUE MANAGER=qmgr
Explanation: All messages with the specified groupID have been successfully
retried and put to the specified queue in queue manager qmgr.
System Action: None.
User Response: None.

KMQDI101E

UNABLE TO {LOAD|UNLOAD} DATA DICTIONARY module
Explanation: CCC for MQSeries was unable to load or unload the named Data
Dictionary module.
System Action: Monitoring for the queue manager cannot be initialized.
User Response: Note the message text and contact Candle Customer Support.

KMQDU102I

THE SYSTEM DUMP FOR DUMPID dump_id IS NOW COMPLETE
Explanation: The system executes a dump of the Candle Management Server
(CMS) address space for diagnostic purposes.
System Action: The CMS address space dump is recorded into an available
SYS1.DUMP dataset and the processing continues.
User Response: Save the dump and contact Candle Customer Support.

KMQDU105I

A SYSTEM DUMP FOR DUMPID dump_id HAS FAILED WITH RETURN
CODE rc AND REASON CODE rs
Explanation: CCC for MQSeries attempted to dump the Candle Management
Server (CMS) address space and the SDUMP macro failed with the return code rc
and reason code rs.
System Action: Processing continues.
User Response: Contact Candle Customer Support.

KMQIT101E

ERROR IN FUNCTION function RESPONSE = rs REASON = rc
Explanation: A failure has occurred during the initialization of CCC for
MQSeries. The named function is the routine that encountered the error, rs is the
response code from this routine, and rc is the reason code.
System Action: Initialization of CCC for MQSeries cannot continue.
User Response: Note the message text and contact Candle Customer Support.

KMQIT102I

OMEGAMON FOR WEBSPHERE MQ INITIALIZATION COMPLETE
DMAN=xxxxxxxx
Explanation: Initialization of OMEGAMON XE or DE for WebSphere MQ has
completed successfully. The address xxxxxxxx indicates the location of the main
vector table and is intended for diagnostic purposes only.
System Action: Processing continues.
User Response: None. This is a confirmation message.

KMQxx001E–KOCJ0046

249

KMQIT103E

INITIALIZATION FUNCTION function FAILURE RESPONSE = rs
REASON = rc
Explanation: The named CCC for MQSeries initialization function encountered
an error, where rs is the response code and rc is the reason code.
System Action: Initialization of CCC for MQSeries cannot continue.
User Response: Note the message text and contact Candle Customer Support.

KMQIT104I

OMEGAMON FOR WEBSPHERE MQ TERMINATION STARTED
Explanation: Termination of OMEGAMON XE or DE for WebSphere MQ has
started.
System Action: Shutdown processing will be performed.
User Response: Wait for the KMQIT105I message which indicates that
termination has completed.

KMQIT105I

OMEGAMON FOR WEBSPHERE MQ TERMINATION COMPLETE
Explanation: Termination of OMEGAMON XE or DE for WebSphere MQ has
completed.
System Action: The agent has terminated.
User Response: None. This is a confirmation message.

KMQME102F

UNABLE TO LOAD MESSAGE TABLE KMQAMEMT
Explanation: CCC for MQSeries was unable to load message table
KMQAMEMT.
System Action: CCC for MQSeries terminates.
User Response: Contact Candle Customer Support.

KMQME103E

MESSAGE msg_id NOT FOUND
Explanation: CCC for MQSeries attempted to issue a message whose indicated
message ID was not found in the message table.
System Action: The processing continues.
User Response: Contact Candle Customer Support.

KMQME104I

ID=nnnnn ccc+ddd hex_string char_string
Explanation: This message is used to display the memory block in dump format
for diagnostic purposes. The ID nnnnn is a display ID which is used to associate
this generic display message with the preceeding message KMQMQ232W. The
ccc is the name of the memory block and ddd is the name of the offset into the
memory block. The hex_string and char_string are the hexidecimal and character
representations of the memory block.
System Action: None.
User Response: None.

KMQMH101E

INSUFFICIENT PRIVATE STORAGE
Explanation: MQI hook failed to obtain storage.
System Action: MQI hook disables itself.
User Response: Increase the region size of the MQ application where the error
occurred.

250

Candle Products Messages Manual (KLVHS–KONCT)

KMQMH102E

MQIMONITOR(cms_address_space) UNABLE TO ESTABLISH ESTAE,
RC=rc
Explanation: MQI hook failed to establish recovery environment in the specified
CMS address space which installed the MQI hook.
System Action: MQI hook disables itself.
User Response: Contact Candle Customer Support.

KMQMH103E

MQIMONITOR(cms_address_space) ALESERV FAILED, RC=rc
Explanation: MQI hook failed when establishing addressability to the specified
Candle Management Server address space. This message can be ignored since
control is returned back to the MQSeries address space.
System Action: MQI hook disables itself.
User Response: Check if the specified Candle Management Server address
space is still running. If it is not running, analyze why it stopped. If it is running,
contact Candle Customer Support.

KMQMH104E

MQIMONITOR(mq_monitoring_agent_address_space) INSUFFICIENT
DATA SPACE STORAGE
Explanation: MQI hook detected that there is insufficient data space to hold
MQI data.
System Action: MQI hook disables itself.
User Response: Check if the specified MQ Monitoring Agent address space is
running without problems. If the RKLVLOG indicates abends or other error
messages in the MQ Monitoring Agent address space, analyze these errors. Modify
the agents’s monitoring file so that the SET MQIMONITOR command specifies a
larger BUFFERSIZE. Restart the OMEGAMON Monitoring Agent for WebSphere
MQ.

KMQMH110E

MQIMONITOR(cms_address_space) SDUMPX FAILED, RC=rc
Explanation: MQI hook failed to produce diagnostic dump for the specified
CMS address space which installed the MQI hook.
System Action: Diagnostic dump is not produced, MQI hook disables itself.
User Response: Contact Candle Customer Support.

KMQMH112E

MQIMONITOR(cms_address_space) DATA SPACE UNECTEDLY
DELETED
Explanation: MQI hook abended and the recovery routine detected that the
data space for communicating with the Candle Management Server address
space was deleted.
System Action: Diagnostic dump is not produced, MQI hook disables itself.
User Response: Check if the specified Candle Management Server address
space is running without problems. If the RKLVLOG indicates abends or other
error messages in the Candle Management Server address space, analyze these
errors. If the problem persists, contact Candle Customer Support.

KMQxx001E–KOCJ0046

251

KMQMI101E

MQ API ERROR. OPERATION=op CC=cc RC=rc
Explanation: An error occurred on an MQSeries API request for the indicated
type of operation with the indicated completion and reason codes.
System Action: Processing terminates or continues, depending on the type of
operation.
User Response: Look up the completion and reason codes in the MQSeries
Application Programming Reference and report the problem to Candle Customer
Support.

KMQMI102E

ERROR ACCESSING QUEUE queue-name OPERATION=op CC=cc RC=rc
Explanation: An error occurred on an MQSeries API request, for the indicated
type of operation on the named queue, with the indicated completion and reason
codes.
System Action: Processing terminates or continues, depending on the type of
operation.
User Response: Look up the completion and reason codes in the MQSeries
Application Programming Reference and report the problem to Candle Customer
Support.

KMQMI103E

ERROR ALLOCATING NEW STORAGE FOR type
Explanation: A storage allocation error occurred for the indicated type of object.
System Action: Processing terminates.
User Response: Report the problem to Candle Customer Support.

KMQMI104I

MONITORING ENDED BECAUSE OF EVENT type
Explanation: The CCC for MQSeries Remote Monitoring Agent ended because
of an external event of the type indicated.
System Action: Processing terminates.
User Response: If a Ctrl-C was entered and event type is Ctrl-C Detected,
this is a successful termination. Report any other event type to Candle Customer
Support.

KMQMI105E

type EXCEPTION THROWN
Explanation: An unexpected exception of the indicated type occurred.
System Action: Processing terminates.
User Response: Report the problem to Candle Customer Support.

KMQMI106I

INITIALIZATION COMPLETED, SYSTEM sys MQMANAGER mgr WAITING
FOR SERVER INITIATION MESSAGE
Explanation: Initialization of the CCC for MQSeries Remote Monitoring Agent
has completed for the named queue manager on the named local system.
System Action: Waits for Candle Management Server initiation.
User Response: None. This is a confirmation message.

252

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI107I

MONITORING STARTED FOR qmgr, ReplyToQ IS reply
Explanation: The CCC for MQSeries Remote Monitoring Agent has been
contacted by the Candle Management Server and is now monitoring the named
local queue manager. The named queue, defined in the named local queue
manager, will be used to receive data collected by the agent.
System Action: Monitoring begins.
User Response: None. This is a confirmation message.

KMQMI108I

CHANNEL AND QUEUE MASKS RESET BY SERVER
Explanation: The agent has received and successfully processed a request from
the Candle Management Server to reset the channel and queue masks.
System Action: Processing resumes.
User Response: None. This is a confirmation message.

KMQMI109E

MQ INQUIRE COMMAND ERROR, CC=cc RC=rc
Explanation: An INQUIRE command sent to the MQSeries Command Server
has failed with the indicated completion and reason codes.
System Action: Processing continues but some data will be missing.
Look up the completion and reason codes in the MQSeries Programmable
System Management and report the problem to Candle Customer Support.

KMQMI110E

MQ VERSION NOT AVAILABLE BECAUSE reason, RC=rc
Explanation: The CCC for MQSeries Remote Monitoring Agent was unable to
determine the current version and release of MQSeries for one of the following
reasons:
® Unable to create temporary file name: A temporary file for receiving the
output from SYSLEVEL could not be allocated.
®

Unable to open file for output: The temporary file used to receive output from
SYSLEVEL could not be opened.

Unable to save STDOUT handle: The handle for the STDOUT file could not
be saved.

Unable to redirect STDOUT: Standard output could not be redirected to the
temporary file.

DosExecPgm failure: An error occurred attempting to invoke SYSLEVEL.

Unable to open file for input: The temporary file could not be opened for
input.

Unable to locate MQ Version information: The MQSeries version information
could not be located in the SYSLEVEL output file.

The reasons above may apply to some platforms and not to others. The indicated
return code is from the attempted operation.
System Action: Processing continues without MQSeries version information.
User Response: Report the problem to Candle Customer Support.

KMQxx001E–KOCJ0046

253

KMQMI111I

TERMINATE COMMAND PROCESSED. WAITING FOR SERVER
INITIATION MESSAGE.
Explanation: The CCC for MQSeries Remote Monitoring Agent has received an
indication from the Candle Management Server that monitoring of the remote
queue manager should be stopped.
System Action: Monitoring stops.
User Response: If you want to resume monitoring of the queue manager at a
later time, you must take the appropriate action at the Candle Management
Server.

KMQMI112E

UNABLE TO ALLOCATE REMOTE QUEUE
Explanation: An error occurred while allocating the remote queue named in the
preceding KMQMI002E message. This can occur when more than one Remote
Monitoring Agent is started.
System Action: Processing terminates.
User Response: Look up the completion and reason codes of the previous
KMQMI002E message in the MQSeries Application Programming Reference.

KMQMI113E

UNABLE TO CONNECT TO QUEUE MANAGER qmgr
Explanation: An error occurred while connecting to the named queue manager.
This can occur when there is an authorization problem or when the queue
manager is not started.
System Action: Processing terminates.
User Response: Look up the completion and reason codes of the previous
KMQMI001E message in the MQSeries Application Programming Reference.

KMQMI114I

event-type SIGNAL RECEIVED - IGNORED
Explanation: A signal event of type event-type has occurred.
System Action: None.
User Response: None. This is a confirmation.

KMQMI115E

START TIME FOR QMGR qmgr IS NOT AVAILABLE, BECAUSE REASON.
RC=rc
Explanation: The Remote Monitoring Agent could not determine the start date
and time of the named Queue Manager. This occurred for one of the following
reasons:
® Unable to create temporary file name: A temporary file for receiving the
output from the ps -ef command could not be allocated.
®

Unable to open file for output: The temporary file used to receive output from
ps -ef could not be opened.

The QMgr is not started: The MQ Manager has not been started.

System Action: Processing continues without Start date and time information.
User Response: Contact Candle Customer Support.

254

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI116E

MQ MANAGER COMMAND SERVER NOT RESPONDING.
Explanation: The CCC for MQSeries Remote Monitoring Agent attempted to
verify that the MQSeries command server is running, but the command server did
not respond.
System Action: Processing terminates.
User Response: Ensure that the MQSeries command server is running for the
queue manager being monitored. If necessary, start the command server by
entering the following command:, strmqcsv queue-manager-name

KMQMI117I

MQ MANAGER qmgr IS NOT DEFINED OR MONITORED
Explanation: The CCC for MQSeries Remote Monitoring Agent made contact
with the Candle Management Server, but the CMS queue manager is either not
defined to the local queue manager or it is not being monitored.
System Action: Processing continues.
User Response: Verify that the CMS queue manager is defined properly to the
local queue manager as either a transmit queue or a queue manager alias.

KMQMI118I

QUEUE qmgr IS NOT A TRANSMIT QUEUE
Explanation: The CCC for MQSeries Remote Monitoring Agent made contact
with the Candle Management Server, but qmgr is not defined as a transmit queue
or a queue manager alias.
System Action: Processing continues.
User Response: If you have problems with the Remote Monitoring Agent,
verify that the CMS queue manager is defined properly to the local queue
manager.

KMQMI119I

ERROR VALIDATING REPLY-TO QUEUE MANAGER
Explanation: The Remote MQSeries Agent made contact with Candle
Management Server, but could not confirm that the transmit queue and channel
are properly defined.
System Action: Processing continues.
User Response: If you encounter problems with the Remote Monitoring Agent,
verify that the CMS queue manager is defined properly to the local queue
manager, and that the sender/server channel is properly defined.

KMQMI120I

CHANNEL channel-name IS NOT RUNNING
Explanation: The Remote Monitoring Agent made contact with Candle
Management Server, but the sender/server channel, channel-name, is not in the
running state.
System Action: Processing continues.
User Response: If you encounter problems with the Remote Monitoring Agent,
verify that the sender/server channel is active.

KMQMI121I

UNABLE TO FIND SENDER/SERVER CHANNEL FOR qmgr
Explanation: The Remote Monitoring Agent made contact with the Candle
Management Server, but the CMS queue manager qmgr is not associated with
any monitored sender/server channels.
System Action: Processing continues.

KMQxx001E–KOCJ0046

255

User Response: If you encounter problems with the Remote Monitoring Agent,
verify that the CMS queue manager is defined properly to the local queue
manager.
KMQMI122I

MESSAGE RECEIVED WITH UNSUPPORTED CCSID=ccsid-IGNORED
Explanation: The Remote Monitoring Agent received a message from the
Candle Management Server with an unsupported Coded Character Set Id. ccsid is
the decimal value of the CCSID.
System Action: The message is ignored.
User Response: Determine why the CMS used the CCSID shown in the
message. If necessary, contact Candle Customer Support.

KMQMI123E

THE CORRECT PASSWORD HAS NOT BEEN PROVIDED
Explanation: The Remote Monitoring Agent received the reply "quit" when it
prompted for a password.
System Action: Processing terminates.
User Response: Rerun the program and supply the correct password.

KMQMI124E

ENVIRONMENT ERROR - UNABLE TO CREATE EVENT FOR %s, RC=rc
Explanation: This message is informational only.
System Action: None.
User Response: None.

KMQMI125I

SYSTEM name, MQMANAGER manager_name, INITIALIZATION
COMPLETED
Explanation: This message is informational only.
System Action: None.
User Response: None.

KMQMI126I

WILL RETRY IN ONE MINUTE
Explanation: This messages appears if the command server or queue manager
is not started. CCC for MQSeries will try to locate the server in one minute.
System Action: Processing continues.
User Response: Verify that the command server or queue manager is started.

KMQMI127I

DLQ NAME INQUIRE FAILED
Explanation: CCC for MQSeries could not locate the Dead Letter Queue.
System Action: Processing continues.
User Response: Verify that you have defined a Dead Letter Queue.

KMQMI128I

MQ MONITORING TERMINATED
Explanation: This message is informational only.
System Action: None.
User Response: None.

KMQMI129E

INVALID SET GROUP OPTION: option reason
Explanation: The specified SET GROUP option is either invalid or used
incorrectly. The reason indicates what is wrong.
System Action: Processing continues. The specified option is ignored.
User Response: Correct the option according to the reason and retry.

256

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI130E

SET GROUP SETTING option IS NOT SUPPORTED
Explanation: The specified SET GROUP option is not supported.
System Action: Processing continues. The option is ignored.
User Response: Enter a valid option and retry.

KMQMI131E

LIKE GROUP group WAS NOT DEFINED. LIKE COMMAND IGNORED
Explanation: The specified group in the LIKE GROUP command is not defined.
System Action: Processing continues. The LIKE GROUP command is ignored.
User Response: Either specify a group that exists or define a group using the
SET GROUP and resubmit the command.

KMQMI132E

INVALID SET MANAGER OPTION: option reason
Explanation: The specified SET MANAGER option is either invalid or used
incorrectly. The reason indicates what is wrong.
System Action: Processing continues. The option is ignored.
User Response: Correct the option according to the reason and retry.

KMQMI133E

SET MANAGER SETTING option IS NOT SUPPORTED
Explanation: The specified SET MANAGER option is not supported.
System Action: Processing continues. The option is ignored.
User Response: Enter a valid option and retry.

KMQMI134E

LIKE MANAGER manager WAS NOT DEFINED. LIKE COMMAND
IGNORED
Explanation: The specified manager in the LIKE MANAGER command is not
defined.
System Action: Processing continues. The LIKE MANAGER command is
ignored.
User Response: Either specify a manager that exists or define manager with
the SET MANAGER command and resubmit the command.

KMQMI135I

MULTIPLE MANAGER IS NOT SUPPORTED
Explanation: Multiple Manager is not supported on non-MVS platforms
System Action: Processing continues.
User Response: None.

KMQMI136E

MANAGER manager EXISTS, STATUS=ADD IS INVALID. SET MANAGER
IGNORED
Explanation: The specified manager already exists and cannot be added.
System Action: Processing continues. The SET MANAGER command is
ignored.
User Response: None.

KMQMI137E

INVALID PERFORM INCLUDE OPTION option reason
Explanation: The specified PERFORM INCLUDE option is either not supported
or unknown.
System Action: Processing continues.
User Response: None.

KMQxx001E–KOCJ0046

257

KMQMI138E

INVALID PERFORM STARTMON OPTION option reason
Explanation: The specified PERFORM STARTMON option is either not
supported or unknown.
System Action: Processing continues.
User Response: None.

KMQMI139I

PERFORM STARTUP IS NOT SUPPORTED
Explanation: The PERFORM STARTUP command is not supported on
non-MVS platforms.
System Action: Processing continues.
User Response: None.

KMQMI140I

PERFORM SHUTDOWN IS NOT SUPPORTED
Explanation: The PERFORM SHUTDOWN command is not supported on
non-MVS platforms.
System Action: Processing continues.
User Response: None.

KMQMI141E

INVALID COMMAND: command
Explanation: The specified COMMAND is not valid.
System Action: Processing continues.
User Response: None.

KMQMI142E

CANNOT OPEN COMMAND FILE command_file
Explanation: Cannot open the specified command_file you specified for CCC
for MQSeries.
System Action: Processing continues.
User Response: Create a command_file and restart CCC for MQSeries.

KMQMI143E

COMMAND FILE ENDED WITH A ’-’ CONTINUATION IS ECTED
Explanation: The command file has ’-’ as the last character of the last line. ’-’
indicates a continuation to the next line.
System Action: Processing continues.
User Response: Delete the very last ’-’ in the command file.

KMQMI144E

INVALID SET QUEUE OPTION option reason
Explanation: The specified SET QUEUE option is either invalid or used
incorrectly. reason indicates what is wrong.
System Action: Processing continues. This option is ignored.
User Response: Correct the option according to the reason and retry.

KMQMI145E

INVALID SET CHANNEL OPTION option reason
Explanation: The specified SET CHANNEL option is either invalid or used
incorrectly. reason indicates what is wrong.
System Action: Processing continues. The option is ignored.
User Response: Correct the option according to the reason and retry.

258

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI146E

QUEUE queue EXISTS, STATUS=ADD IS INVALID. SET QUEUE IGNORED
Explanation: SET QUEUE with STATUS(ADD) refers to a queue that already
exists.
System Action: Processing continues. The SET QUEUE command is ignored.
User Response: Reset the queue in the SET QUEUE command and restart
CCC for MQSeries.

KMQMI147E

CHANNEL channel EXISTS, STATUS=ADD IS INVALID. SET CHANNEL
IGNORED
Explanation: SET CHANNEL with STATUS(ADD) refers to a queue that
already exists.
System Action: Processing continues. The SET CHANNEL command is
ignored.
User Response: Reset the channel in the SET CHANNEL command and
restart CCC for MQSeries.

KMQMI148E

QUEUE queue DOES NOT EXIST, STATUS=DELETE IS INVALID. SET
QUEUE IGNORED
Explanation: SET QUEUE with STATUS(DELETE) refers to a queue that does
not exist.
System Action: Processing continues. The SET QUEUE command is ignored.
User Response: Reset queue in the SET QUEUE command and restart CCC
for MQSeries.

KMQMI149E

CHANNEL channel DOES NOT EXIST, STATUS=DELETE IS INVALID. SET
CHANNEL IGNORED
Explanation: SET CHANNEL with STATUS(DELETE) refers to a channel that
does not exist.
System Action: Processing continues. The SET CHANNEL command is
ignored.
User Response: Reset channel in the SET CHANNEL command and restart
CCC for MQSeries.

KMQMI150E

SET QUEUE SETTING option IS NOT SUPPORTED
Explanation: The specified option in the SET QUEUE command is not
supported.
System Action: Processing continues.
User Response: None.

KMQMI151E

SET CHANNEL SETTING option IS NOT SUPPORTED
Explanation: The specified option in the SET CHANNEL command is not
supported.
System Action: Processing continues.
User Response: None.

KMQMI152E

SET QUEUE REFERS TO A MGRNAME manager THAT DOES NOT EXIST.
SET QUEUE IGNORED
Explanation: SET QUEUE command refers to a manager that does not exist.
System Action: Processing continues. The SET QUEUE command is ignored.

KMQxx001E–KOCJ0046

259

User Response: Reset the manager in the SET QUEUE command and restart
CCC for MQSeries.
KMQMI153E

SET QUEUE REFERS TO A GROUP group THAT DOES NOT EXIST. SET
CHANNEL IGNORED
Explanation: SET QUEUE command refers to a group that does not exist.
System Action: Processing continues. The SET QUEUE command is ignored.
User Response: Reset the group in the SET QUEUE command and restart
CCC for MQSeries.

KMQMI154E

SET CHANNEL REFERS TO A MG1RNAME manager THAT DOES NOT
EXIST. SET CHANNEL IGNORED
Explanation: SET CHANNEL command refers to a manager that does not
exist.
System Action: Processing continues. The SET CHANNEL command is
ignored.
User Response: Reset the manager in the SET CHANNEL command and
restart CCC for MQSeries.

KMQMI155E

SET CHANNEL REFERS TO A GROUP group THAT DOES NOT EXIST.
SET CHANNEL IGNORED
Explanation: SET CHANNEL command refers to a group that does not exist.
System Action: Processing continues. The SET CHANNEL command is
ignored.
User Response: Reset the group in the SET CHANNEL command and restart
CCC for MQSeries.

KMQMI156E

SET QUEUE REFERS TO A QUEUE MASK queue_mask THAT DOES NOT
EXIST IN grp/mgr. SET QUEUE IGNORED
Explanation: SET QUEUE command cannot delete a queue_mask that does
not exist in the specified group or manager.
System Action: Processing continues. The SET QUEUE command is ignored.
User Response: Reset the queue_mask in the SET QUEUE command and
restart CCC for MQSeries.

KMQMI157E

SET CHANNEL REFERS TO A CHANNEL MASK channel_mask THAT
DOES NOT EXIST. SET CHANNEL IGNORED
Explanation: SET CHANNEL command cannot delete a channel_mask that
does not exist.
System Action: Processing continues. The SET CHANNEL command is
ignored.
User Response: Reset the channel_mask in the SET CHANNEL command
and restart CCC for MQSeries.

260

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI158E

NO MGRNAME OR GROUP DEFINED FOR resource. command IS
IGNORED
Explanation: There is no group or no manager associated with the Queue or
Channel resource.
System Action: Processing continues. The SET QUEUE or SET CHANNEL
command is ignored.
User Response: Add GROUP or MANAGER to the SET QUEUE or SET
CHANNEL command.

KMQMI159E

CHANNEL channel ALREADY EXISTS. SET CHANNEL COMMAND
IGNORED
Explanation: The specified channel already exists.
System Action: Processing continues. The SET CHANNEL command is
ignored.
User Response: None.

KMQMI160E

component INVALID TABLE INDEX VALUE=value
Explanation: The specified agent component has encountered an invalid index
parameter value.
System Action: The agent will not return data for the request.
User Response: Record information and contact Candle Customer Support.

KMQMI161E

component IS MISSING REQUIRED TABLE INDEX VALUE(S)
Explanation: The specified agent component cannot find the required index
parameter values. This message is typically associated with, and is merely a
symptom of, some other problem.
System Action: The agent will not return data for the request.
User Response: Carefully examine the messages in your log which precede
this message. Previous messages will give more detailed information about why
the agent is not functioning correctly. If the problem persists, contact Candle
Customer Support.

KMQMI162E

component ENCOUNTERED UNECTED VALUE=value
Explanation: The specified agent component encountered an unexpected
variable value.
System Action: Data returned for the request may be incomplete.
User Response: Record information and contact Candle Customer Support.

KMQMI165W

component INVOKED FOR UNSUPPORTED PLATFORM
Explanation: The specified agent component has been called on a platform for
which the function is not supported.
System Action: Applicable data cannot be returned for an unsupported
platform.
User Response: None.

KMQxx001E–KOCJ0046

261

KMQMI166I

NO SET MANAGER COMMAND IN THE COMMAND FILE. DEFAULT
MANAGER IS MONITORED
Explanation: CCC for MQSeries will monitor the default queue manager when
there is no SET MANAGER command in the command file.
System Action: Processing continues.
User Response: Add SET MANAGER command to the command file to
monitor a non-default queue manager.

KMQMI167I

NO PERFORM STARTMON COMMAND IN THE COMMAND FILE.
MONITORED MANAGER IS NOT INITIATED
Explanation: A PERFORM STARTMON command needs to exist in order for
CCC for MQSeries to start monitoring.
System Action: Processing continues but monitoring is not initiated.
User Response: Add a PERFORM STARTMON command to the command
file and restart CCC for MQSeries.

262

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI168W

NO QUEUE MANAGER WAS PROVIDED WITH -N COMMAND. DEFAULT
MANAGER IS MONITORED
Explanation: This message is informational.
System Action: Processing continues.
User Response: None.

KMQMI169E

ENVIRONMENT ERROR - UNABLE TO CREATE THREAD
Explanation: An attempt to start an independent path of execution within the
the monitoring agent that shares its address space code and global data failed.
System Action: The monitoring agent does not initialize successfully.
User Response: Terminate and restart the monitoring agent. If the problem
persists, note your system configuration and contact Candle Customer Support.

KMQMI170E

PERSISTENT DATA STORE module FAILURE, nn
Explanation: A failure has occurred in the specified Persistent Data Store
module. nn is diagnostic information only.
System Action: The requested data is unavailable.
User Response: Note the text of the message and contact Candle Customer
Support.

KMQMI171I

NODE node IS ON-LINE
Explanation: An MQSeries OMEGAMON Monitoring Agent has registered the
specified node as on-line. MQSeries OMEGAMON Monitoring Agents on MVS
can monitor multiple queue managers. This node corresponds to one of the
queue managers it is monitoring.
System Action: None.
User Response: None.

KMQMI172I

NODE node IS OFF-LINE
Explanation: An MQSeries OMEGAMON Monitoring Agent has registered the
specified node as off-line. MQSeries OMEGAMON Monitoring Agents on MVS
can monitor multiple queue managers. This node corresponds to one of the
queue managers it is no longer monitoring.
System Action: None.
User Response: None.

KMQMI173E

EVENTARRIVED FROM module FAILED WITH STATUS rc
Explanation: An MQSeries OMEGAMON Monitoring Agent attempted to signal
that an MQSeries event has occurred from module module, but received an error
with a status code of rc.
System Action: The Candle Management Workstation will not issue an alert if
the MQSeries event matched any situations being monitored for the
MQSeries_Events attribute group.
User Response: If this continues to occur, record the status and contact Candle
Customer Support.

KMQxx001E–KOCJ0046

263

KMQMI174I

EVENT COMMUNICATION QUEUE ENDED WITH RETURN CODE rc
Explanation: The return code rc was received while retrieving an MQSeries
event notification.
System Action: The MQSeries event notification process is terminated.
User Response: During normal address space shutdown, this message is
normal. If this message appears at any other time, note the text of the message
and contact Candle Customer Support.

KMQMI175E

ABEND IN PROCESSEVENT INTERCEPTED
Explanation: An abnormal termination was averted while attempting to process
an MQSeries event message.
System Action: The event message is ignored. Processing continues.
User Response: Examine RKLVLOG for other messages that might explain
this failure and contact Candle Customer Support.

KMQMI176E

INVALID MESSAGE RETRIEVED FROM EVENT COMMUNICATION
QUEUE - TYPE = tp
Explanation: An event communication message with invalid type tp was
received.
System Action: The event message is ignored and processing continues.
User Response: Note the text of the message and contact Candle Customer
Support.

KMQMI177E

INVALID MESSAGE FORMAT DETECTED IN EVENT NOTIFICATION
MESSAGE
Explanation: An event notification message was received with an invalid
format.
System Action: The message is ignored. Processing continues.
User Response: Note the text of the message and contact Candle Customer
Support.

KMQMI178E

INVALID SET AGENT COMMAND option reason
Explanation: The specified option entered in the SET AGENT command is
invalid for the reason given in the reason text.
System Action: The command is ignored.
User Response: Enter a valid option and resubmit the command.

KMQMI179I

MAXIMUM LENGTH FOR THE SET AGENT IS 8. SET AGENT IS
TRUNCATED TO 8 CHARACTERS
Explanation: The Name= parameter of the SET AGENT command is longer
than 8 characters; 8 characters is the maximum length for this parameter.
System Action: The name is truncated.
User Response: Specify a name parameter that is 8 characters or less and
resubmit the command.

264

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI180E

INVALID SET EVENTQIN/EVENTQOUT option reason
Explanation: The SET EVENTQIN or SET EVENTQOUT option is invalid for
the reason given in the reason text.
System Action: The command is ignored.
User Response: Specify a valid option and resubmit the command.

KMQMI181E

SET EVENTQIN/EVENTQOUT option IS NOT SUPPORTED
Explanation: The specified SET EVENTQIN or SET EVENTQOUT option is not
supported.
System Action: The command is ignored.
User Response: Specify a supported option and resubmit the command.

KMQMI182I

MAXIMUM DELAYED EVENTS QUEUED AWAITING ONLINE STATUS;
OLDER EVENTS WILL ROLL OFF
Explanation: MQSeries events notification for situations using the
MQSeries _Events attribute group has been delayed until the MQSeries
Monitoring Agent is fully on-line. Because the maximum number of events that
can be retained has been reached, the agent will no longer retain the oldest event
for each new event that is intercepted.
System Action: None.
User Response: This message can occur at startup when the monitored queue
managers’ event queues have many back-logged event messages. Determine the
reason for the MQSeries OMEGAMON Monitoring Agent’s inability to reach
on-line status or its loss of on-line status and correct the problem. This may occur
due to a communication failure with the Candle Management Server. If this is a
new monitoring environment, communication parameters such as
CTIRA_CELL_NAME may need adjustment. If the problem persists, contact
Candle Customer Support.

KMQMI183E

EXCESSIVE IPC DEQUEUE FAILURES. EVENT COMMUNICATION
TERMINATED
Explanation: More than 100 errors were encountered while attempting to
retrieve an event notification message.
System Action: The event notification process is terminated.
User Response: Note the presence of other error messages which may have
preceeded this message and contact Candle Customer Support.

KMQMI184E

ERROR IN OPENING filename
Explanation: The specified filename cannot be opened because it does not
exist.
System Action: None.
User Response: Check to make sure the specified filename exists. Enter a valid
filename and retry.

KMQxx001E–KOCJ0046

265

KMQMI185E

ERROR IN WRITING TO filename. WRITE IS NOT SUCCESSFUL OR DATA
LOST
Explanation: An error occurred when trying to write data to the specified
filename. The write is unsuccessful or the data written has been lost.
System Action: None.
User Response: Ensure that enough disk space is available for a write
operation and retry.

KMQMI186E

SET EVENTQIN/EVENTQOUT REFERS TO A GROUP OR MANAGER
name THAT DOES NOT EXIST. SET EVENTQIN/EVENTQOUT IGNORED
Explanation: The specified name in the SET EVENTQIN/EVENTQOUT
command does not exist.
System Action: The command is ignored.
User Response: Enter a valid name and resubmit the command.

KMQMI187I

AGENT SUCCESSFULLY
CONNECTED/RECONNECTED/DISCONNECTED TO/FROM THE SERVER
(server_name)
Explanation: The MQSeries Agent successfully established a
connection/reconnection to the Candle Management Server (CMS) or the
MQSeries Agent disconnected from the CMS.
System Action: None. This message is informational only.
User Response: None.

KMQMI193E

ERROR IN ESTABLISHING COMMITMENT CONTROL RC=rc
ERRNO=errno
Explanation: The command you submitted,
strcmtctl lcklvl(*cs) nfyobj(qsys/qsysopr *msgq) cmtscope(*job)

has failed with return code rc and error code errno.
System Action: The MQSeries Agent processing continues and the command
is ignored.
User Response: Correct the error in the command and restart the MQSeries
Agent.
KMQMI194E

ERROR IN ISSUING _RCOMMIT COMMAND RC=rc ERRNO=errno
Explanation: The command
Rcommit("KMQAGENT - KMQCMQMI commit")

266

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI195E

ERROR IN ISSUING _RROLLBCK COMMAND RC=rc ERRNO=errno
Explanation: The command
_Rrollbck()

QUEUE MANAGER manager IS INACTIVE. OPERATION operation CC=cc
RC=rc
Explanation: The MQSeries API call identified by operation failed with the
specified completion code and return code indicating that the queue manager
manager is inactive or in the process of terminating.
System Action: CCC for MQSeries will try to reestablish the connection to the
queue manager until it becomes active.
User Response: To monitor the queue manager, start the queue manager and
its associated command server.

KMQMI197I

MQSERIES MANAGER COMMAND SERVER IS AVAILABLE
Explanation: The monitoring agent has detected that the command server is
available for processing commands.
System Action: None. This message is informational only.
User Response: None.

KMQMI198I

MESSAGES DELETED. QMGR=queue_manager_name, Q=queue,
GROUPID=id
Explanation: As requested, the messages with the specified groupID have been
deleted from the specified queue in queue manager queue_manager_name.
System Action: None.
User Response: None.

KMQMI199I

MESSAGES RETRIED. QMGR=queue_manager_name, Q=queue,
DESTQMGR=queue_manager_destination, DESTQ=queue_destination,
GROUPID=id
Explanation: As requested, the dead letter queue messages with the specified
groupID have been retried from the specified queue in queue manager
queue_manager_name to queue queue in queue manager
queue_manager_name.
System Action: None.
User Response: None.

KMQxx001E–KOCJ0046

267

KMQMI201W

FAILED TO NOTIFY OFFLINE STATUS
Explanation: This message appears if you terminate the agent or an error
condition terminates the agent and the agent fails to send the offline status to the
Candle Management Server.
System Action: Agent terminates (goes offline).
User Response: The agent will notify the Candle Management Server in its
next cycle depending on the heartbeat interval you specified. This interval is set
using the CTIRA_HEARTBEAT variable set during installation. For more
information see the product installation documentation.

KMQMI202I

PDS INSERT FUNCTION IS REINITIALIZED FOR TABLE nnnnnnnn
Explanation: The PDS Insert Function for the specified table is available after it
was disabled. The time it was disabled is indicated by the preceeding message
KMQMI170E.
System Action: Historical data recording for the specified table resumes.
User Response: None.

KMQMI203W

nnn EVENTS LOST IN EVENT LOG FOR QUEUE MANAGER nnnn
Explanation: During the period of time that event logging was disabled, the
specified events from queue manager nnnn were not recorded into the persistent
datastore. The time that event logging was disabled is indicated by the preceeding
message KMQMI170E.
System Action: Event log recording resumes.
User Response: If event log integrity is critical, resolve the original problem
reported in message KMQMI170E.

KMQMI204W

directory name DIRECTORY NAME IS TOO LONG AND IGNORED. THE
MAXIMUM ALLOWED LENGTH IS n
Explanation: The directory name you specified using the SET EVENTLOG
command or the CTIRA_HIST_DIR environment variable is too long. The
maximum length of a directory name is specified as n.
System Action: The specified directory name is ignored.
User Response: Specify a valid directory name under the maximum allowable
length.

KMQMI205E

INVALID SET EVENTLOG option reason
Explanation: The SET EVENTLOG is either invalid or used inconsistently. The
specified reason indicates why the option is invalid.
System Action: None.
User Response: Correct the option according to the reason and retry the
command.

KMQMI206W

INVALID EVENT MESSAGE ENCOUNTERED and ignored.
Explanation: CCC for MQSeries tried to process an MQSeries event, but this
was not a valid MQSeries event.
System Action: The event is ignored.
User Response: Analyze the event information that is displayed following this
message to determine why it is invalid.

268

Candle Products Messages Manual (KLVHS–KONCT)

KMQMI207W

SAMPINT IS INCREASED TO seconds SECONDS BECAUSE VALUE
SPECIFIED IN CONFIGURATION FILE (seconds) IS TOO SMALL.
Explanation: The SAMPINT specified in the MQSeries Monitoring Agent
configuration file was not large enough to collect all MQSeries data samples.
System Action: SAMPINT is increased and processing continues normally.
User Response: Consider increasing the SAMPINT value in the MQSeries
Monitoring Agent configuration file.

KMQMI208I

ERROR LOG MONITORING FEATURE IS TURNED OFF
Explanation: The Error Log monitoring feature has been disabled by specifying
ERRLOGCYCLE(0) on either the SET MANAGER or SET GROUP monitoring
option. See the OMEGAMON XE for WebSphere MQ Monitoring User’s Guide
for descriptions of monitoring options.
System Action: Processing continues with Error Log monitoring disabled.
User Response: None.

KMQMI209E

SITUATION situationname FOR MESSAGE STATISTICS ATTRIBUTE
GROUP MUST SPECIFY SINGLE QUEUE NAME.
Explanation: The specified situation must specify the Queue_Name attribute
with an equal operator. A separate situation must be written for each individual
queue name. The reason for this requirement is because of the overhead of
collecting this data. This information should only be collected for specific queues
that need to be closely monitored.
System Action: No rows are returned for the requested situation.
User Response: Modify the situation to specify a specific queue name for the
Queue_Name attribute.

KMQMI210E

COLLECTION OF MESSAGE STATISTICS FAILED. QUEUE=queuename,
USERID=userid, RC=reasoncode
Explanation: Collection of message statistics for the specified queue was
requested by either a situation or an ad-hoc report request. The attempt to browse
messages on the queue failed with the specified return code. Return code values
below 9000 are values returned from WebSphere for MQSeries. Additional
information about these return codes may be obtained by referring to IBM
documentation. Some possible values are:
2001

Alias Base Q Type Error

2063

Security_Error

2004

Buffer Error

2069

Signal_Outstanding

2005

Buffer Length Error

2070

Signal_Request_Accepted

2009

Connection Broken

2071

Storage_Not_Available

2010

Data Length Error

2079

Truncated_Msg_Accepted

2011

Dynamic_Q_Name_Error

2080

Truncated_Msg_Failed

2016

Get_Inhibited

2082

Unknown_Alias_Base_Q

2017

Handle_Not_Available

2085

Unknown_Object_Name

2018

Hconn_Error

2086

Unknown_Object_Q_Mgr

KMQxx001E–KOCJ0046

269

270

2019

Hobj_Error

2087

Unknown_Remote_Q_Mgr

2024

Syncpoint_Limit_Reached

2091

Xmit_Q_Type_Error

2026

MD_Error

2092

Xmit_Q_Usage_Error

2033

No_Msg_Available

2099

Signal1_Error

2034

No_Msg_Under_Cursor

2100

Object_Already_Exists

2035

Not_Authorized

2101

Object_Damaged

2036

Not_Open_For_Browse

2102

Resource_Problem

2037

Not_Open_For_Input

2109

Suppressed_By_Exit

2041

Object_Changed

2110

Format_Error

2042

Object_In_Use

2111

Source_CCSID_Error

2043

Object_Type_Error

2112

Source_Integer_Enc_Error

2044

OD_Error

2113

Source_Decimal_Enc_Error

2045

Option_Not_Valid_For_Type

2114

Source_Float_Enc_Error

2046

Options_Error

2115

Target_CCSID_Error

2052

Q_Deleted

2116

Target_Integer_Enc_Error

2057

Q_Type_Error

2117

Target_Decimal_Enc_Error

2058

Q_Mgr_Name_Error

2118

Target_Float_Enc_Error

2059

Q_Mgr_Not_Available

2119

Not_Converted

2062

Second_Mark_Not_Allowed

2120

Converted_Msg_Too_Big

2130

Adapter_Serv_Load_Error

2199

Def_Xmit_Q_Usage_Error

2133

Adapter_Conv_Load_Error

2201

Name_In_Use

2136

Multiple_Reasons

2202

Connection_Quiescing

2140

CICS_Wait_Failed

2203

Connection_Stopping

2152

Object_Name_Error

2204

Adapter_Not_Available

2153

Object_Q_Mgr_Name_Error

2209

No_Msg_Locked

2154

Recs_Present_Error

2217

Connection_Not_Authorized

2155

Object_Records_Error

2219

Call_In_Progress

2156

Response_Records_Error

2241

Incomplete_Group

2157

ASID_Mismatch

2242

Incomplete_Msg

2161

Q_Mgr_Quiescing

2243

Inconsistent_CCSIDs

2162

Q_Mgr_Stopping

2244

Inconsistent_Encodings

2183

API_Exit_Load_Error

2245

Inconsistent_UOW

2184

Remote_Q_Name_Error

2246

Invalid_Msg_Under_Cursor

2186

GMO_Error

2247

Match_Options_Error

2192

Pageset_Full

2255

UOW_Not_Available

Candle Products Messages Manual (KLVHS–KONCT)

2193

Pageset_Error

2256

Wrong_GMO_Version

2194

Name_Not_Valid_For_Type

9002

Unsupported CCSID Found

2195

Unexpected_Error

9005

Insufficient Storage

2196

Unknown_Xmit_Q

9008

Not allowed by MSGACCESS
value

2197

Unknown_Def_Xmit_Q

9009

Agent timeout occurred

2198

Def_Xmit_Q_Type_Error

System Action: No rows are returned.
User Response: Resolve the reason for the problem.
KMQMQ101E

ALESERV FAILED. REQ=request RC=rc REASON=rs
Explanation: The named ALESERV request issued by CCC for MQSeries
failed.
System Action: Monitoring of the queue manager cannot continue.
User Response: Note the message text and contact Candle Customer Support.

KMQMQ102E

CROSS-MEMORY SERVER INITIALIZATION FAILED
Explanation: Initialization of the CCC for MQSeries cross-memory service task
has encountered a serious error.
System Action: CCC for MQSeries initialization fails.
User Response: Search for prior error messages in the TLVLOG. Note the
message text and contact Candle Customer Support.

KMQMQ103E

DUPLICATE SMF HOOK INSTALLED
Explanation: CCC for MQSeries was unable to install its SMF recording hook
because there are ten previously-installed copies of the hook already active.
System Action: CCC for MQSeries initialization fails.
User Response: Contact Candle Customer Support.

KMQMQ104E

ERROR INSTALLING SMF HOOK. RC=rc REASON=rs
Explanation: CCC for MQSeries was unable to install its SMF recording hook.
rc is the return code and rs is the reason code.
System Action: CCC for MQSeries initialization fails.
User Response: Note the message text and codes and contact Candle
Customer Support.

KMQMQ105E

BAD RETURN CODE FROM SERVER. RC=rc
Explanation: A data collection component of CCC for MQSeries received a bad
return code (rc) from either the cross-memory or MQSeries interface service task.
System Action: The data collection request fails.
User Response: Search for prior error messages in the TLVLOG. Note the
message text and contact Candle Customer Support.

KMQxx001E–KOCJ0046

271

KMQMQ106E

UNABLE TO WAIT FOR EVENT. RC=rc
Explanation: CCC for MQSeries was unable to get events from the queue
manager event queue because of bad SIGNAL code rc.
System Action: Monitoring of the event queue ends.
User Response: Note the message text and contact Candle Customer Support.

KMQMQ107E

ERROR FROM MQ API REQUEST request QMGR=manager CC=cc
REASON=rc
Explanation: CCC for MQSeries has received a bad completion code from the
named MQSeries API request, where manager is the queue manager name, cc is
the completion code, and rc is the reason code.
System Action: The function fails.
User Response: Note the message text and contact Candle Customer Support.

KMQMQ108E

ERROR RETURNED BY CROSS-MEMORY SERVER. CODE=rc
Explanation: A bad response code was received from the CCC for MQSeries
cross-memory server, where rc is the response code.
System Action: The function fails.
User Response: Note the message text and contact Candle Customer Support.

KMQMQ109I

NOW MONITORING MQ MANAGER mgr EVENT QUEUE queue
Explanation: CCC for MQSeries is now monitoring the named event queue
associated with the named queue manager.
System Action: None.
User Response: None. This is a confirmation.

KMQMQ110E

UNABLE TO MONITOR MQ MANAGER mgr EVENT QUEUE queue
Explanation: CCC for MQSeries is unable to monitor the named event queue
associated with the named queue manager.
System Action: Event monitoring for the named event queue is terminated.
User Response: Search for prior error messages in the TLVLOG. Note the
message text and contact Candle Customer Support.

KMQMQ111I

COLLECTION INITIALIZATION IN PROGRESS FOR QMGR=ssid
Explanation: Data collection initialization has begun for the MQSeries queue
manager identified by sub-system ID ssid.
System Action: None.
User Response: None. This is a confirmation.

KMQMQ112I

COLLECTION INITIALIZATION COMPLETE FOR QMGR=ssid
Explanation: Data collection initialization has completed successfully for the
MQSeries queue manager identified by subsystem ID ssid.
System Action: Data collection for this queue manager will be performed
during each sample by CCC for MQSeries until the queue manager terminates or
collection is stopped by a CCC for MQSeries operator command.
User Response: None. This is a confirmation.

272

Candle Products Messages Manual (KLVHS–KONCT)

KMQMQ113E

COLLECTION TERMINATED FOR QMGR=sbid, REASON=reason
Explanation: Data collection has been terminated for a queue manager with
subsystem ID sbid where reason is the textual reason causing termination.
System Action: Data collection for this queue manager is terminated.
Collection does not resume by CCC for MQSeries until the queue manager
restarts or collection is retarted via a CCC for MQSeries operator command.
User Response: Check the REASON value in the message. REASON values
indicate that the collection initialization has failed due to an internal condition.
Contact Candle Customer Support for more information about these REASON
values.

KMQMQ114I

MONITOR ENDED FOR MQ MANAGER mgr EVENT QUEUE queue
Explanation: CCC for MQSeries has stopped monitoring the named event
queue associated with the named queue manager.
System Action: None.
User Response: None. This is an informational message only.

KMQMQ115E

NO MORE HANDLES AVAILABLE FOR OPEN QUEUE FOR QMGR=sbid
Explanation: The MAXHANDLES value (maximum number of handles that
can be held by a single task) for the specified queue manager with subsystem ID
sbid has been exceeded by the CCC for MQSeries data collection component.
System Action: Data collection for queues in the indicated queue manager
cannot be completed by CCC for MQSeries. Data for some queues will not be
available for display. CCC for MQSeries requires that you monitor the
MAXHANDLES value for the number of queues you have defined to each queue
manager plus a fixed overhead of three queues.
User Response: Issue an ALTER QMGR MAXHANDS(nnnn) command to the
queue manager, where nnnn is greater than or equal to the number of queues
defined to that queue manager plus three. This enables CCC for MQSeries to
collect data for all queues defined to the queue manager.

KMQMQ116E

module TIMEOUT WAITING FOR RESPONSE FROM QMGR=mgr
Explanation: CCC for MQSeries issued a DISPLAY command to the specified
queue manager, but timed out before receiving a response.
System Action: Data collection for the resource cannot be performed. The
KMQMQ117E message, which contains the text of the DISPLAY command, is
written to TLVLOG.
User Response: Investigate the queue manager, and determine why it did not
respond to the operator command. If the problem persists, call Candle Customer
Support.

KMQMQ117E

COMMAND command ISSUED
Explanation: This message contains the text of the DISPLAY command that
timed out. The KMQMQ116E message precedes this message.
System Action: Data collection for the resource cannot be performed.
User Response: Investigate the queue manager, and determine why it did not
respond to the operator command. If the problem persists, call Candle Customer
Support.

KMQxx001E–KOCJ0046

273

KMQMQ118E

UNABLE TO OBTAIN COMMON STORAGE FOR SRB DRIVER
Explanation: The CCC for MQSeries cross-memory server task was unable to
allocate sufficient storage in the MVS extended common storage area (ECSA) for
the cross-memory SRB driver.
System Action: Initialization of CCC for MQSeries fails.
User Response: Determine whether there is sufficient ECSA in your MVS
system (currently, less than 400 bytes). If sufficient ECSA exists, contact Candle
Customer Support.

KMQMQ119I

COLLECTION TERMINATED FOR QMGR=sbid, REASON=NORMAL
TERMINATION
Explanation: Data collection has been terminated normally for the queue
manager indicated by subsystem ID sbid.
System Action: Data collection for this queue manager is terminated.
Collection does not resume by CCC for MQSeries until the queue manager
restarts or collection is restarted using a CCC for MQSeries operator command.
User Response: This is a normal condition. Termination was caused by a CCC
for MQSeries operator command, or the queue manager itself has stopped.

KMQMQ120E

AUTHORIZATION FAILED. QMGR=qmgr, QUEUE=queue
Explanation: The named queue in the named queue manager could not be
opened because the Candle Management Server is not authorized to open the
queue.
System Action: Data collection for the specified queue cannot be performed.
User Response: Grant the Candle Management Server started task READ
security access for the named queue.

KMQMQ121I

TIMEOUT WAITING FOR AGENT RESPONSE FOR REMOTE QMGR=qmgr
Explanation: A timeout occurred while polling a remote monitoring agent for
the specified remote queue manager.
System Action: The current sample of data cannot be collected, but
processing otherwise continues as normal.
User Response: None.

KMQMQ122I

NOW MONITORING CICS CHANNELS FOR APPLID appl ON qmgr
Explanation: CCC for MQSeries is now monitoring CICS channels on the
named applid with the named queue manager.
System Action: None.
User Response: None.

KMQMQ123E

UNABLE TO MONITOR CICS CHANNELS FOR APPLID appl ON qmgr
Explanation: CCC for MQSeries is unable to monitor CICS channels on the
named applid with the named queue manager.
System Action: CICS channel monitoring for the named applid is terminated.
User Response: Search for prior error messages in the TLVLOG. Note the
message text and contact Candle Customer Support.

274

Candle Products Messages Manual (KLVHS–KONCT)

KMQMQ124I

CICS CHANNEL MONITORING ENDED FOR APPLID appl ON qmgr
Explanation: CCC for MQSeries has stopped monitoring CICS channels on the
named applid for the named queue manager.
System Action: None.
User Response: None.

KMQMQ140W

REMOTE QMGR=qmgr IS NOT ACCESSIBLE VIA LOCAL QMGR=qmgr
RESPONSE = rc - REASON = rc
Explanation: Communication with the named remote queue manager using the
named local queue manager could not be established because the ROUTE
specification is incorrect. RESPONSE and REASON represent response and
reason codes from an MQOPEN for the remote queue.
System Action: The connection between the specified queue managers
cannot be established. If there are other local queue managers which satisfy the
ROUTE specification, CCC for MQSeries will attempt to use them. If no other
local queue manager is available, the monitoring will fail.
User Response: Correct the ROUTE specification for the local queue manager.

KMQMQ141E

CONNECTION TO LOCAL QMGR=qmgr FOR COMMUNICATION WITH
REMOTE QMGR=qmgr FAILED RESPONSE = rc - REASON = rc
Explanation: Communication with the named local queue manager using the
named remote queue manager could not be established because the ROUTE
specification is incorrect. RESPONSE and REASON represent internal response
and reason codes.
System Action: The connection between the specified queue managers
cannot be established. If there are other local queue managers which satisfy the
ROUTE specification, CCC for MQSeries will attempt to use them. If no other
local queue manager is available, initialization of monitoring will fail.
User Response: Check for security error messages in the Candle Management
Server JOBLOG, and resolve any that are found. Ensure that the ROUTE
specification for the local queue manager is correct. If the problem persists, note
the message text and contact Candle Customer Support.

KMQMQ142E

INQUIRE FOR REMOTE QUEUE queue ON QMGR= qmgr FAILED
RESPONSE = rc - REASON = rc
Explanation: The command server on the specified MQSeries queue manager
replied to an INQUIRE_Q command, but the reply indicated an unexpected error.
RESPONSE and REASON represent response and reason codes from an
INQUIRE_Q command for the specified remote queue.
System Action: CCC for MQSeries will fail monitoring for the specified remote
MQSeries queue manager.
User Response: Analyze response and reason codes and fix the underlying
problem, then restart monitoring for the specified remote MQSeries queue
manager.

KMQxx001E–KOCJ0046

275

KMQMQ143E

MESSAGE WITH UNSUPPORTED CCSID=coded_character_set_id IS
RECEIVED FROM QMGR=qmgr
Explanation: The message is received with a coded character set ID which is not
currently supported.
System Action: Monitoring for the specified MQSeries queue manager is
terminated.
User Response: Contact Candle Customer Support.

KMQMQ150W

EVENT QUEUE=Event_Queue_Name FOR QUEUE MANAGER QMgr IS
OPEN FOR INPUT BY ANOTHER APPLICATION OPEN_INPUT_COUNT=X
Explanation: CCC for MQSeries may not report on some or all of the events on
the monitored event queue because another application is performing destructive
reads on that queue. This is a warning message.
System Action: Processing continues.
User Response: Close the other applications that are using this queue.

KMQMQ151I

EVENT QUEUE=Event_Queue_Name FOR QUEUE MANAGER QMgr IS NO
LONGER OPEN FOR INPUT BY ANOTHER APPLICATION
Explanation: Another application no longer has the event queue open for the
specified queue manager.
System Action: Processing continues.
User Response: None. This is an informational message.

KMQMQ152I

EVENTS READ FROM QUEUE=Event_Queue_Name FOR QUEUE
MANAGER QMgr1 WILL BE WRITTEN TO Output_Queue_Name BY
ANOTHER APPLICATION
Explanation: CCC for MQSeries will copy event information to output queue,
Output_Queue_Name. This message is displayed after the user issues a SET
EVENTQOUT command.
System Action: Processing continues.
User Response: None. This is an informational message.

KMQMQ200E

MQI MONITORING FOR QMGR=queue_manager_name IS NOT STARTED,
INVALID ENVIRONMENT RC=rc, xx
Explanation: MQI monitoring could not be started because the specified queue
manager name is located in an invalid environment. xx is diagnostic information.
System Action: MQI monitoring is not started, but the rest of product
continues normally.
User Response: Verify that the specified queue manager operates without
problems, confirm that MQSeries version you are running is supported by CCC
for MQSeries. Otherwise, contact Candle Customer Support.

KMQMQ202I

NOW MONITORING MQI REQUESTS FOR QMGR=queue_manager_name
MQKA=xx
Explanation: MQI monitoring was successfully started for the specified queue
manager. xx is diagnostic information.
System Action: None.
User Response: None.

276

Candle Products Messages Manual (KLVHS–KONCT)

KMQMQ203E

MQI component PROCESSOR INITIALIZATION FAILED.
QMGR=queue_manager_name, RC=rc
Explanation: Initialization of one of the MQI monitoring components failed.
component is the name of failed component, queue_manager_name is the name
of queue manager where MQI monitoring failed, and rc is the reason code.
System Action: MQI monitoring is not started.
User Response: Contact Candle Customer Support.

KMQMQ204I

MONITORING OF MQI REQUESTS FOR QMGR=queue_manager_name
COMPLETED
Explanation: MQI monitoring for the specified queue manager terminated.
System Action: None.
User Response: None.

KMQMQ206E

MONITORING OF MQI REQUESTS FOR QMGR=queue_manager_name IS
DEACTIVATED, REASON CODE rc
Explanation: The MQI data processor detected that MQI monitoring is
deactivated. for the specified queue manager. rc is the internal reason code for
deactivation.
System Action: MQI monitoring terminates.
User Response: Check for more KMQMHxxx messages preceding this one in
the TLVLOG, which may contain more specific information. Check for SVC
dumps with the title CANDLE CCC FOR MQSERIES (MQI) PROBLEM
DETERMINATION DUMP. Contact Candle Customer Support.

KMQMQ207E

STORAGE ALLOCATION ERROR IN MQI DATA PROCESSOR FOR
QMGR=queue_manager_name
Explanation: MQI data processor detected a storage shortage. This message
indicates a performance problem in the Candle Management Server address
space. For example, this may indicate that the MQI data processor is not
processing data fast enough to accommodate incoming data.
System Action: MQI monitoring terminates.
User Response: Verify that Candle Management Server address space is
running without abends or loops. Increase dispatching priority of CMS address
space.

KMQMQ209E

MQI RECORD IS NOT COMPLETE. QMGR=queue_manager_name,
REASON CODE =rc, hex
Explanation: The MQI data processor detected that the incoming MQI record is
incomplete. queue_manager_name is the name of monitored queue manager, rc
is the reason code, hex is the hexadecimal display of the key portion of the MQI
record.
System Action: The MQI record is not processed.
User Response: Contact Candle Customer Support.

KMQxx001E–KOCJ0046

277

KMQMQ210E

MQI RECORD TYPE IS INVALID, QMGR=queue_manager_name, hex
Explanation: The MQI data processor detected that the incoming MQI record is
of an invalid type. queue_manager_name is the name of monitored queue
manager, hex is the hexadecimal display of the key portion of the MQI record.
System Action: The MQI record is not processed.
User Response: Contact Candle Customer Support.

KMQMQ211E

MQI TRACING IS DISABLED FOR QMGR=queue_manager_name, module
RC=rc, REASON=reason
Explanation: An error was detected for the specified queue manager during
MQI tracing initialization. module is the name of module which detected the error,
rc is the return code and reason is the reason code.
System Action: MQI tracing is disabled.
User Response: Check the RKPDLOG for Persistent Data Store error messages
and make sure that at least one of the datasets in the RKMQDSA group is
available for write access.

KMQMQ212W

MQI HANDLE TRANSLATION FAILED. QMGR=qmgr,
APPLICATION=application id, TRAN/PGM=tran/pgm name. THIS MAY
RESULT IN INCOMPLETE APPLICATION QUEUE STATISTICS.
Explanation: The identified application and transaction/program was in
progress at the time that OMEGAMON XE for WebSphere MQ Monitoring started
monitoring. An attempt to perform handle translation to determine the name of
the queue being accessed failed. This may occur if the identified application
thread terminates immediately after the MQI call.
System Action: Processing continues. Queue-related statistics are not
updated.
User Response: None.

KMQMQ213E

KMQAPI REQUESTED API module NOT SUPPORTED.
Explanation: The KMQAPI router module has encountered a request for an API
that is not supported.
System Action: The request fails.
User Response: Record information and contact Candle Customer Support.

KMQMQ214E

KMQAPI ERROR; API=module, RESPONSE=r1, REASON=r2
Explanation: The KMQAPI router module detected an error from the specified
API module.
System Action: The data requested is unavailable.
User Response: If the problem persists, contact Candle Customer Support
Note, it is possible for this message to occur at shutdown without causing serious
problems.

KMQMQ215E

APPLICATION DATA SAMPLE PROCESSOR TERMINATED.
QMGR=queue_manager_name, RC=rc
Explanation: The application data sample processor unexpectedly terminated.
queue_manager_name is the name of monitored queue manager, rc is the reason
code.
System Action: The application data sample processor terminates.

278

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Contact Candle Customer Support.
KMQMQ217E

ERROR RETURNED BY $IPC ACCESS. RETURN CODE=rc
Explanation: An unexpected return code occurred while attempting to access
the event communication queue.
System Action: The MQSeries event notification mechanism is disabled.
User Response: Note the text of the message and contact Candle Customer
Support.

KMQMQ218E

ERROR RETURNED BY $IPC QUEUE. RETURN CODE=rc
Explanation: An unexpected return code occurred while attempting to add a
message to the event communication queue.
System Action: The MQSeries event notification mechanism is disabled.
User Response: Note the text of the message and contact Candle Customer
Support.

KMQMQ219E

text
Explanation: When attempting to issue a command to MQSeries, the command
response contained a CSQN205I message with an unexpected return code value.
The text of this message consists of the command attempted and the responses to
it returned from the command server.
System Action: In general, the command has failed. Refer to CSQN205I
message and the return code contained within for further explanation. A
common cause of this message is that the Channel Initiator is not running, but
that is by no means the only possible cause.
User Response: If the command is failing because the Channel Initiator has
failed or has not yet been started, restart it. Correct any conditions associated
with the CSQN205I message. If the command appears to be syntactically or
semantically incorrect, or the problem cannot otherwise be resolved, note the text
of the KMQMQ219E messages and those immediately preceeding it and contact
Candle Customer Support.

KMQMQ220E

ERROR RETURNED BY $IPC QUERY. RETURN CODE=rc
Explanation: An unexpected return code occurred while attempting to obtain a
count of records on the IPF queue.
System Action: The MQSeries event notification mechanism is disabled.
User Response: Note the text of the message and contact Candle Customer
Support.

KMQMQ222W

MQI TRACING FOR APPLID(applid) TRANPGM(tranpgm)
QMGRNAME(qmgrname) IS TERMINATED DUE TO HIGH LOAD
Explanation: CCC for MQSeries detected a shortage of memory resources and
attempted to alleviate the problem by stopping MQI tracing for MQ applications
identified by applid, tranpgm, and qmgrname.
System Action: MQI tracing for the specified application(s) is suspended.
User Response: Narrow the scope of MQI tracing as much as possible and/or
specify a lower TRACELIMIT value. See the description of the SET
APPLICATION command for information about narrowing the scope of MQI
tracing.

KMQxx001E–KOCJ0046

279

KMQMQ223W

MQI MONITORING FOR MGRNAME=mgrname LEFT 5K OF ECSA
STORAGE IN ORDER TO MAINTAIN SYSTEM INTEGRITY
Explanation: During termination of MQI monitoring, CCC for MQSeries
detected that some of the storage could not be freemained because of a possibility
of violating system integrity.
System Action: None. This message is informational only.
User Response: None.

KMQMQ224E

MQ COMMANDS CANNOT BE EXECUTED FOR REMOTE QMGRS;
COMMAND NOT EXECUTED FOR QMGR=queue_manager_name
Explanation: You attempted to execute a CCC for MQSeries automation
command on the specified remote queue manager queue_manager_name. CCC
for MQSeries automation commands cannot be executed on remote queue
managers.
System Action: The command is ignored.
User Response: Execute the automation command on a local monitoring
agent node or execute it at the Candle Management Server.

KMQMQ225I

MQSERIES COMMAND INVOKED FOR QMGR=queue_manager_name
Explanation: The agent issuing the message has received a CCC for MQSeries
automation command to execute on the specified queue manager,
queue_manager_name.
System Action: A KMQMQ226I message will follow this message to display
the command text to execute on the target queue manager. The monitoring agent
will submit the command to the specified queue manager,
queue_manager_name.
User Response: None.

KMQMQ226I

COMMAND TEXT: command.text
Explanation: This message is issued to display the command text of a CCC for
MQSeries automation command before it is executed on the target queue
manager.
System Action: The monitoring agent will submit the command to the queue
manager and the queue manager will execute the command.
User Response: None.

KMQMQ227I

MQSERIES COMMAND COMPLETED FOR QMGR=queue_manager_name
Explanation: The agent issuing the message has received a response to a
previously submitted CCC for MQSeries automation command from the specified
queue manager, queue_manager_name.
System Action: A KMQMQ228I message will follow to display the response
text that was received from the queue manager.
User Response: None.

KMQMQ228I

RESPONSE TEXT: command.text
Explanation: This message is issued to display the response text of a CCC for
MQSeries automation command that was previously submitted to a queue
manager for execution.
System Action: None.

280

Candle Products Messages Manual (KLVHS–KONCT)

User Response: None.
KMQMQ229E

MQSERIES MESSAGE CORRUPTION FOR MESSAGE msgid. KEYWORD
PREFIXES=(msgkwpfx|prstblkwpfx), QMGR=qmgrname
Explanation: CCC for MQSeries detected the corruption of MQSeries messages
during data collection.
System Action: Monitored samples may be dropped for the specified queue
manager.
User Response: Contact Candle Customer Support and report any occurrence
of this message along with the values for the msgid, message keyword prefix
msgkwpfx, and parse table keyword prstblkwpfx.

KMQMQ230E

INVALID MQSERIES MESSAGE ORDER ENCOUNTERED FOR MESSAGE
msgid QMGR=qmgrname
Explanation: CCC for MQSeries did not receive MQSeries messages from
command execution in the expected order.
System Action: Monitored samples may be dropped for the specified queue
manager.
User Response: Contact Candle Customer Support and report any occurrence
of this message along with the values for the msgid and qmgrname.

KMQMQ232W

INVALID EVENT MESSAGE ENCOUNTERED, ID=nnnnn
Explanation: CCC for MQSeries tried to process an MQSeries event, but this
was not a valid MQSeries event.
System Action: The event is ignored.
User Response: Analyze the event that is displayed in message KMQME104I
to determine why it is invalid.

KMQMQ233W

CHANNEL INITIATOR FOR QMGR xxxx IS NOT ACTIVE. CLUSTER
INFORMATION CANNOT BE COLLECTED.
Explanation: The channel initiator address space for the specified queue
manager is not active. CCC for MQSeries is not able to collect some
cluster-related and cluster queue manager channnel information.
System Action: Processing continues.
User Response: Determine the reason for the channel initiator address space
not being active. In some cases this may be a normal situation. If needed, attempt
to start the channel initiator address space.

KMQMQ234W

CHANNEL INITIATOR FOR QMGR xxxx IS NOW ACTIVE. CLUSTER
INFORMATION IS NOW AVAILABLE.
Explanation: The channel initiator address space for the specified queue
manager is now active. CCC for MQSeries is now able to collect cluster-related
information, such as cluster queue and cluster queue manager channel
information.
System Action: Processing continues.
User Response: None.

KMQxx001E–KOCJ0046

281

KMQMQ235W

PERFORMANCE EVENTS DISABLED FOR QMGR xxxx. QUEUE
STATISTICS INFORMATION CANNOT BE COLLECTED.
Explanation: Queue statistics information was requested by specifying
STATISTICS(YES) on the SET QUEUE monitoring option. However, the
PERFMEV attribute of the queue manager being monitored is set to DISABLED.
This attribute must be set to ENABLED in order for the OMEGAMON Monitoring
Agent for WebSphere MQ to collect this information.
System Action: The OMEGAMON Monitoring Agent for WebSphere MQ
continues monitoring but some queue statistics data will be unavailable.
User Response: None.

KMQMQ236W

PERFORMANCE EVENTS FOR QMGR xxxx ARE NOW ENABLED.
QUEUE STATISTICS INFORMATION IS NOW AVAILABLE.
Explanation: The PERFMEV attribute of the queue manager being monitored
has been set to ENABLED. Queue statistics information can now be collected.
System Action: The OMEGAMON Monitoring Agent for WebSphere MQ
continues monitoring and all available queue statistics data will be collected.
User Response: None.

KMQMQ237W

QSG DATA EXTRACTION ERROR RC(rc) REASON(reason)
Explanation: An unexpected error has been detected while attempting to collect
QSG data.
System Action: Processing continues; some data for the current sample will be
lost.
User Response: Collect information for diagnosis.

KMQMQ238W

XCF macro FUNCTION function FAILED group.member RC(rc)
REASON(reason)
Explanation: The indicated XCF function has failed.
System Action: Processing continues; some data for the current sample will be
lost.
User Response: Collect information for diagnosis.

KMQMQ239E

XCF FUNCTION FAILED RC(rc) REASON(reason)
Explanation: An XCF function has unexpectedly failed.
System Action: Processing continues, but QSG data collection will probably
not be done.
User Response: Collect information for diagnosis.

KMQMQ240W

SRB(srbname) ABEND(abendcode) EPA(entrypoint) ADDR(address)
Explanation: An SRB scheduled by the MQSeries agent has unexpectedly
ABENDed
System Action: Channel status data for the current cycle will be lost.
Processing will continue.
User Response: Collect information for diagnosis.

KMQMQ241E

MQ COMMAND FAILED MSG(CSQN205I) RC(rc)
Explanation: An MQSeries command has failed with the indicated return code.

282

Candle Products Messages Manual (KLVHS–KONCT)

System Action: Processing continues, but no data will be collected for the
executing function.
User Response: Ensure that the command server is running on all queue
managers. Ensure that the channel initiator is running. Check queue manager
and channel initiator for error messages. Collect information for diagnosis.
KMQMQ242I

QSG MONITOR DISABLED DUE TO ZERO QSGCHKINTERVAL
Explanation: A value of zero seconds for the QSGCHKINTERVAL was
specified on the PERFORM STARTMON command.
System Action: Processing continues, but all QSG monitoring will be disabled.
User Response: If QSG monitoring is not desired on this agent, no action is
necessary. To activate monitoring, the QSGCHKINTERVAL value must be
non-zero and the agent restarted.

KMQMQ243I

QSG THREAD STARTED FOR XCF GROUP "groupname"
Explanation: The QSG monitoring thread has been started with the indicated
XCF group name.
System Action: This thread will watch for queue managers of interest that
could perform the QSG monitoring function. When one is found, the thread
determines whether to start monitoring by using the XCF serialization function.
User Response: None, this is an informational message. To completely disable
the thread, QSGCHKINTERVAL(0) may be specified on the PERFORM
STARTMON command.

KMQMQ244I

QSG MONITOR ACTIVE FOR QSG(qsgname) AT QMGR(qmgr)
Explanation: QSG monitoring for the indicated queue-sharing group using the
indicated queue manager has been initiated.
System Action: Processing continues with the monitoring function active.
User Response: None, this is an informational message.

KMQMQ245I

QSG MONITOR TAKEOVER FOR QSG(qsgname) AT QMGR(qmgr)
Explanation: QSG monitoring for the indicated queue-sharing group using the
indicated queue manager has been initiated in response to a takeover request.
System Action: Processing continues with the monitoring function active.
User Response: None, this is an informational message.

KMQMQ246I

QSG MONITOR INACTIVE FOR QSG(qsgname) AT QMGR(qmgr)
Explanation: QSG monitoring for the indicated queue-sharing group using the
indicated queue manager has been terminated, probably in response to a request
for takeover by another agent.
System Action: Processing continues, if takeover has been requested the other
agent should start QSG monitoring from another queue manager.
User Response: If produced in response to a takeover or shutdown request, no
action is necessary. Otherwise, collect information for diagnosis.

KMQMQ247I

QSG TAKEOVER INITIATED FOR QSG(qsgname) AT QMGR(qmgr)
Explanation: It was determined that QSG monitoring is already active from
another agent with MONITOR(YES) specified, but this agent has specified
MONITOR(TAKEOVER).

KMQxx001E–KOCJ0046

283

System Action: The other agent is requested to release the monitoring
function. When that is complete, this agent will take over the monitoring function
for the indicated queue-sharing group using the indicated queue manager.
User Response: Unless the message is seen repeatedly, no action is required.
Otherwise, collect information for diagnosis.
KMQMQ400E

aaaaaaaa EIBFN = nnnn EIBRESP = nnnnnnnn EIBRESP2 = nnnnnnnn
Explanation: An EXEC CICS command has returned an unexpected return
code. aaaaaaaa is the CICS applid.
System Action: Data collection for CICS channels is terminated.
User Response: Note the message text and contact Candle Customer Support.

KMQMQ401E

aaaaaaaa CICS release must be at least 3.3.0
Explanation: The CICS channel monitoring feature of CCC for MQSeries
requires at least version 3.3 for CICS. aaaaaaaa is the CICS applid.
System Action: Data collection for CICS channels is not initiated.
User Response: Ensure that CICS channel monitoring support is started in the
appropriate environments.

KMQMQ402E

aaaaaaaa Unknown input method
Explanation: An attempt at initiating CICS channel monitoring support has
been made by a method other than documented in the product installation
documentation. aaaaaaaa is the CICS applid.
System Action: Data collection for CICS channels is not initiated.
User Response: Use one of the methods given in the product installation
documentation to start data collection for CICS channels.

KMQMQ403E

aaaaaaaa No valid action specified
Explanation: The KMQC transaction was initiated without a valid action being
specified. aaaaaaaa is the CICS applid.
System Action: The request is ignored.
User Response: Re-enter the transaction with a valid action keyword.

KMQMQ404E

aaaaaaaa No transaction ID specified for KMQAMQCI
Explanation: Program KMQAMQCI must be associated with a valid transaction
identifier in order to run. None was found. aaaaaaaa is the CICS applid.
System Action: The program is terminated.
User Response: Specify, using CEDA, a transaction identifier (KMQC) for
program KMQAMQCI.

KMQMQ405E

aaaaaaaa Function keyword has not been implemented yet
Explanation: A keyword was specified for transaction KMQC that has not been
implemented at this time. aaaaaaaa is the CICS applid.
System Action: The request is ignored.
User Response: Re-enter the transaction using a valid action keyword.

KMQMQ406W

aaaaaaaa Extraneous parameter or HLQ invalid. Ignored
Explanation: Following a valid START keyword, either a parameter other than
HLQ was found or the format of the HLQ parameter was invalid. aaaaaaaa is the
CICS applid.

284

Candle Products Messages Manual (KLVHS–KONCT)

System Action: The parameter is ignored.
User Response: Ensure only valid, correctly formatted parameters are entered.
KMQMQ407E

aaaaaaaa KMQAMQCI specified with RELOAD=YES is not supported
Explanation: Program KMQAMQCI has been defined with the option
RELOAD=YES. This is not supported. aaaaaaaa is the CICS applid.
System Action: Data collection for CICS channels is not initiated.
User Response: Change the definition to RELOAD=NO.

KMQMQ408W

aaaaaaaa CCC for MQSeries already active in CICS
Explanation: An attempt was made to start CICS channel data collection in
CCC for MQSeries but collection is already active. aaaaaaaa is the CICS applid.
System Action: The request is ignored.
User Response: None.

KMQMQ409W

aaaaaaaa CCC for MQSeries not active in CICS. Request ignored
Explanation: An attempt was made to stop CICS channel data collection in
CCC for MQSeries but collection is not active. aaaaaaaa is the CICS applid.
System Action: The request is ignored.
User Response: None.

KMQMQ410E

aaaaaaaa Channel Definition File (CSQKCDF) is not available
Explanation: CICS channel data collection in CCC for MQSeries is unable to
read information from the MQ Channel Definition file. aaaaaaaa is the CICS
applid.
System Action: Data collection for CICS channels is not initiated.
User Response: Ensure that the MQ Channel Definition File (CSQKCDF) is
available for BROWSE and READ.

KMQMQ411I

aaaaaaaa CCC for MQSeries start accepted. HLQ=high_level_qualifier
Explanation: A successful request to start the data collection portion of the CICS
channel monitoring feature in CCC for MQSeries has been made using the
specified HLQ. aaaaaaaa is the CICS applid.
System Action: None.
User Response: None.

KMQMQ412E

aaaaaaaa MQ Verb = nnnnn CCode = nnnnnnnn Reason = nnnnnnnn
Explanation: An unexpected error occurred while processing an MQ API
request. aaaaaaaa is the CICS applid.
System Action: Data collection for CICS channels is terminated.
User Response: Note the message text and contact Candle Customer Support.

KMQxx001E–KOCJ0046

285

KMQMQ413I

aaaaaaaa CCC for MQSeries stop accepted
Explanation: A successful request to terminate data collection for CICS
channels was entered. aaaaaaaa is the CICS applid.
System Action: Data collection for CICS channels will stop.
User Response: None.

KMQMQ414W

aaaaaaaa MQSeries not active. Will retry connection
Explanation: An attempt was made to start data collection for CICS channel
monitoring support in CCC for MQSeries but the MQ manager for this CICS
region is not active. aaaaaaaa is the CICS applid.
System Action: The start request will be retried.
User Response: None.

KMQPD101E

module ROUTINE FOR PDS function FAILED. POST CODE code
Explanation: Persistent Data Store routine failed for the specified module and
function. code is the post code from PDS routine.
System Action: If this message occurs several times, MQI tracing is disabled.
User Response: Check the RKPDLOG for Persistent Data Store error messages
and make sure that at least one of the datasets in the RKMQDSA group is
available for write access.

KMQRM104E

ABEND RECOVERY ENTERED. CODE=ac FUNCTION=func
ADDRESS=Xaddress
Explanation: An abend has occurred within CCC for MQSeries where rc
indicates the abend code, func is the function that was in control, and Xaddress is
the address where the abend occurred.
System Action: Standard error recovery action is performed. A system dump
may be produced.
User Response: Note the message text and contact Candle Customer Support.

KMQTR101E

BUFFER SIZE REQUESTED IS TOO LARGE
Explanation: An attempt was made to set the component trace table size to a
value outside the valid range. The BUFSIZE parameter, specified in an operator
TRACE CT command or in SYS1.PARMLIB(CTKMQ00), cannot exceed 2
megabytes.
System Action: The size of the internal trace table remains unchanged.
User Response: Specify a smaller trace buffer size through the use of TRACE
CT or the CTKMQ00 parmlib member.

KMQTR102E

NO DEFINED TRACE COMPONENTS FOUND
Explanation: The component trace start/stop routine was invoked but no
component trace had been defined for the KMQ100 component.
System Action: None.
User Response: Contact Candle Customer Support for help in diagnosing the
problem.

286

Candle Products Messages Manual (KLVHS–KONCT)

KMQTR103E

BAD RETURN CODE FROM NAME/TOKEN SERVICES
Explanation: CCC for MQSeries received a bad return code while attempting to
use the MVS/ESA name or token services.
System Action: Processing continues but component tracing may not
function.
User Response: Investigate whether MVS/ESA modules IEANTRT, IEANTCR,
and IEANTDL are globally available to the MVS/ESA system. If the problem
persists after they have been made available as common service routines, contact
Candle Customer Support.

KMQTR104I

TRACE COMP=KMQ100 BUFFER SIZE SET TO nnnnnnnnK.
Explanation: The internal component trace table size was set to the value of
nnnnnnnn kilobytes.
System Action: nnnnnnnnK of virtual storage will be used for each internal
trace buffer. When tracing is active, there are at least 18 separate trace buffers in
each CCC for MQSeries address space.
User Response: None. This is an informational message only.

KMQTR105E

INVALID SUBNAME SPECIFIED. name
Explanation: A TRACE CT operator command was issued with the named
sub-trace. The named sub-trace was not initialized or the name is invalid.
System Action: None.
User Response: Specify another sub-trace name, or omit the sub-trace name
which sets tracing for all sub-traces.

KMQTR106E

INVALID ASID SPECIFIED. Xparameter
Explanation: A TRACE CT operator command was issued with the indicated
hex ASID parameter. The ASID is invalid or not available.
System Action: None.
User Response: Specify a valid hex ASID parameter on the TRACE CT
operator command.

KMQTR107E

INVALID JOBNAME SPECIFIED. parameter
Explanation: A TRACE CT operator command was issued with the indicated
JOBNAME parameter. The JOBNAME is invalid or not available.
System Action: None.
User Response: Specify a valid JOBNAME parameter on the TRACE CT
operator command.

KMQTR111I

TRACE STARTED FOR COMP=component SUB=sub
Explanation: Application component tracing has started in the system for the
named component and sub-trace component. Tracing can be stopped or
modified by operator commands. For more information about controlling
component traces, refer to the MVS/ESA SP System Commands.
System Action: The system trace continues until it is stopped by the TRACE
CT operator command.
User Response: None. This is an informational message only.

KMQxx001E–KOCJ0046

287

KMQTR112I

TRACE STOPPING FOR COMP=component SUB=sub
Explanation: Application component tracing is being terminated for the named
component and sub-trace component.
System Action: The system trace flushes any external write buffers and
terminates.
User Response: None. This is an informational message only.

KMQTR113I

TRACE EXTERNAL WRITER STOP FOR COMP=component
Explanation: Component tracing has stopped writing to an external trace writer.
System Action: The system flushes the remaining trace buffers. Internal tracing
continues as long as the trace remains active for this component.
User Response: None. This is an informational message only.

KMQTR114I

TRACE EXTERNAL WRITER START FOR COMP=component
Explanation: Component tracing has begun to write trace data to an external
writer.
System Action: Trace data is written to the external writer procedure until a
TRACE CT,WTRSTOP command is issued.
User Response: None. This is an informational message only.

KMQTR115E

TRACE BUFFER COULD NOT BE WRITTEN
Explanation: The component trace timed-out waiting for an external writer’s
trace buffer to become available.
System Action: The system continues but trace data may be lost.
User Response: Determine the reason why the trace external writer is not
responding. Check the status of the external writer procedure to which the
component trace is connected.

KMQTR116E

CTRACE WRITE ERROR RC=rc RSN=rs
Explanation: The component trace received an error condition while
attempting to issue an external trace writer request with the MVS/ESA
CTRACEWR macro.
System Action: Processing continues but trace data may be lost.
User Response: Check the return code rc and reason code rs from the
CTRACEWR macro in the MVS/ESA Authorized Assembler Reference ALE-DYN.

KMQTR117E

module LOAD FAILED
Explanation: The system attempted to use MVS/ESA name/token services but
the named module could not be found.
System Action: Processing continues but component tracing may not
function.
User Response: Investigate whether MVS/ESA modules IEANTRT, IEANTCR,
and IEANTDL are globally available to the MVS/ESA system. If the problem
persists after the modules have been made available as common service routines,
contact Candle Customer Support.

288

Candle Products Messages Manual (KLVHS–KONCT)

KMQVS101E

DATASPACE CREATION FAILED. RC=rc REASON=rs
Explanation: An error occurred while attempting to create the CCC for
MQSeries historical dataspace where rc is the return code from the DSPSERV
request and rs is the reason code.
System Action: Initialization of CCC for MQSeries fails.
User Response: Note the message text and contact Candle Customer Support.

KMQVS102E

ALESERV FAILED. RC=rc
Explanation: An ALESERV request issued by CCC for MQSeries failed, where
rc is the return code.
System Action: Initialization of CCC for MQSeries fails.
User Response: Note the message text and contact Candle Customer Support.

KMQVS103E

CELL POOL EXTEND FAILED. RC=rc
Explanation: CCC for MQSeries was unable to extend one of its dataspace cell
pools, where rc is the return code from the CSRP service.
System Action: The error is propagated back to the caller of the service.
User Response: Note the message text and contact Candle Customer Support.

KMQVS104E

CELL POOL CREATION FAILED. RC=rc
Explanation: CCC for MQSeries was unable to create a dataspace cell pool,
where rc is the return code from the CSRPBLD service.
System Action: The error is propagated back to the caller of the service.
User Response: Note the message text and contact Candle Customer Support.

KMQVS105E

FAILURE EXTENDING SIZE OF DATASPACE. RC=rc REASON=rs
Explanation: CCC for MQSeries was unable to expand the size of the historical
dataspace, where rc is the return code from the DSPSERV service and rs is the
reason code.
System Action: The error is propagated back to the caller of the service.
User Response: Note the message text and contact Candle Customer Support.

KMQVS106E

FAILURE GETTING CELL FROM POOL. RC=rc
Explanation: CCC for MQSeries was unable to allocate a cell from a dataspace
cell pool, where rc is the return code from the CSRPGET service.
System Action: The error is propagated back to the caller of the service.
User Response: Note the message text and contact Candle Customer Support.

KMQVS107E

FAILURE FREEING CELL TO POOL. RC=rc
Explanation: CCC for MQSeries was unable to free a cell back to a dataspace
cell pool, where rc is the return code from the CSRPFRE service.
System Action: The error is propagated back to the caller of the service.
User Response: Note the message text and contact Candle Customer Support.

KMQxx001E–KOCJ0046

289

KMQW000W

reason code-explanation text
Explanation: An MQSeries error has occurred when performing the requested
operation.
System Action: None.
User Response: Look up the reason code in the IBM MQSeries Application
Programming Reference for detailed information.

KMQW001I

MSG PUT ON XMIT Q SUCCESSFUL
Explanation: Requested message has been successfully put on the transmission
queue.
System Action: None.
User Response: None. This is a confirmation.

KMQW002E

UNSUPPORTED CCSID FOUND
Explanation: A message with an unsupported coded character set identifier
(CCSID) is received.
System Action: The message is ignored.
User Response: Verify that the message has a valid CCSID.

KMQW005E

INSUFFICIENT STORAGE
Explanation: Insufficient storage to perform the requested function.
System Action: The requested function is ignored.
User Response: Reissue the requested function after ensuring that there is
sufficient storage.

KMQW006E

MSG MISSING DLQ HEADER
Explanation: Agent has received a retry request for message with no dead-letter
header.
System Action: The retry request is ignored.
User Response: Ensure that the MQSeries Application, which put the message,
does not generate messages with no dead-letter header.

KMQW007E

TRUNCATED MSG NOT RETRIED
Explanation: Agent has received a retry request for truncated message.
System Action: The retry request is ignored.
User Response: Ensure that the MQSeries Application, which put the message,
does not generate truncated messages.

KMQW008E

NOT ALLOWED BY MSGACCESS
Explanation: Agent does not have the proper access level to the requested
message.
System Action: The message request is ignored.
User Response: Correct the MSGACCESS value in the agent configuration file
and restart the MQSeries Agent.

KMQW009E

AGENT TIMEOUT OCCURRED
Explanation: An agent timeout occurred during issuing the requested operation.
System Action: The operation is ignored.
User Response: Retry the operation.

290

Candle Products Messages Manual (KLVHS–KONCT)

KMQW010E

NOT ALLOWED BY COMMAND OPTION
Explanation: Agent does not allow executing the requested command.
System Action: The command is ignored.
User Response: Correct the COMMAND option in the agent configuration file
and restart the MQSeries Agent.

KMQW011E

FAILED DUE TO QMGR QUIESCING
Explanation: The command failed because queue manager is in a quiescing
state.
System Action: The command is ignored.
User Response: Ensure that queue manager is in the Running state and retry
the command.

KMQW012E

UNKNOWN REASON CODE
Explanation: An unknown reason code is return by MQSeries.
System Action: None.
User Response: Contact Candle Customer Support.

KMQW013I

COMMAND ACCEPTED BY MVS
Explanation: The queue manager on MVS has accepted the command.
System Action: None.
User Response: None.

KMQW014E

QMGR NOT ACTIVE
Explanation: Command cannot be processed because the queue manager is
inactive.
System Action: The command is ignored.
User Response: Start the queue manager and its associated command server,
then retry command.

KMQW015E

REMOTE QMGR NOT SUPPORTED
Explanation: Agent does not support to submit command for remote queue
manager.
System Action: The command is ignored.
User Response: Start a MQSeries OMEGAMON Monitoring Agent for the
remote queue manager.

KMQW016E

SYNTAX ERROR
Explanation: A syntax error was detected in the command.
System Action: The command is ignored.
User Response: Correct the syntax error and reissue the command.

KMQW017E

COMMAND FAILED
Explanation: The requested command is failed during execution.
System Action: The command is ignored.
User Response: Examine the agent log for response that returns from
MQSeries.

KMQxx001E–KOCJ0046

291

KMQW018E

NOT ALLOWED BY SECURITY
Explanation: The requested command is not allowed by the security system.
System Action: None.
User Response: Contact your security administrator.

KMQW019E

NOT SUPPORTED BY PLATFORM
Explanation: The command has been issued on a Windows platform on which
take action is not supported.
System Action: The command is ignored.
User Response: None.

KMS0101

Candle Management Server (CMS) shutdown requested.
Explanation: A request to shutdown the Candle Management Server (CMS) has
been received.
Severity: 0
System Programmer Response:No

KMS0150

Candle Management Server (CMS) shutdown deferred.
Explanation: A request to shutdown the Candle Management Server (CMS) has
been received but cannot be processed immediately. Shutdown will proceed as
soon as possible.
Severity: 0
System Programmer Response:No

KMVCCC001E

UNABLE TO LOCATE KMVCCC GLOBAL AREA
Explanation: The KMVCCC global structure was not located.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC002E

INVALID STATUS ITEM NAME IN GETATTRIBUTE REQUEST
Explanation: An invalid status item name was passed in a request to obtain
initial attributes.
System Action: The GetAttribute request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC003E

MANAGED OBJECT object NOT FOUND
Explanation: During a GetAttribute request, the specified object could not be
located.
System Action: The GetAttribute request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

292

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC004E

RULE FOR MANAGED OBJECT object IS TOO LONG
Explanation: While creating or updating the Status Data Manager (SDM)
resources for the specified managed object, the SDM rule string became too long.
This may be due to the number of children subordinate to the object.
System Action: The SDM rule is not updated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC005E

ENTERPRISE OBJECT NOT FOUND
Explanation: The KMVCCC Enterprise object was not located.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC006E

ENTERPRISE OBJECT IS NOT VALID
Explanation: The KMVCCC Enterprise object is not in a valid state.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC007I

ERROR return_code WHILE CONNECTING TO HUB -- RETRY IN 2
MINUTES
Explanation: Return_code was received while connecting to the Candle
Management Server hub.
System Action: The request will be retried in two minutes.
User Response: Make sure the KDCSHOST and KDSENV configuration
members are properly set up for locating the hub. If the problem persists, contact
Candle Support Services.
Message Type: Error.

KMVCCC008E

INTERNAL THREAD DISPATCH ERROR
Explanation: An error occurred while dispatching a thread.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC009E

UNRECOVERABLE ERROR return_code WHILE CONNECTING TO HUB
Explanation: Return_code was received while connecting to the Candle
Management Server hub.
System Action: No further attempts will be made.
User Response: Make sure the KDCSHOST and KDSENV configuration
members are properly set up for locating the hub. If the problem persists, contact
Candle Support Services.
Message Type: Error.

KMQxx001E–KOCJ0046

293

KMVCCC010E

UNABLE TO INITIALIZE KMVCCC SERVICE QUEUE
Explanation: An error occurred while setting up the KMVCCC service queue.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC011E

UNABLE TO INITIALIZE SDM INTERFACE
Explanation: An error occurred while setting up the interface to the Status Data
Manager (SDM).
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC012I

EIB CHANGE THREAD SHUTTING DOWN
Explanation: The thread that monitors the Candle Management Server hub for
changes to the enterprise, and the managed objects it contains, is shutting down.
System Action: Processing continues.
User Response: This message will most likely occur when the OMEGAVIEW
region is shutting down. If it occurs at other times, examine the log for other error
messages and contact Candle Support Services.
Message Type: Information.

KMVCCC013I

KMVCCC SERVICE THREAD SHUTTING DOWN
Explanation: The KMVCCC service thread is shutting down.
System Action: Processing continues.
User Response: This message will most likely occur when the OMEGAVIEW
region is shutting down. If it occurs at other times, examine the log for other error
messages and contact Candle Support Services.
Message Type: Information.

KMVCCC014E

UNABLE TO INITIALIZE NODE STATUS THREAD
Explanation: An error occurred while initializing the thread that monitors the
Candle Management Server hub for changes in node status.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC015E

UNABLE TO ATTACH NODE STATUS THREAD
Explanation: An error occurred while starting the thread that monitors the
Candle Management Server hub for changes in node status.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

294

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC016E

UNABLE TO INITIALIZE SITUATION STATUS THREAD
Explanation: An error occurred while initializing the thread that monitors the
hub for changes in node status.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC017E

UNABLE TO ATTACH SITUATION STATUS THREAD
Explanation: An error occurred while starting the thread that monitors the
Candle Management Server hub for changes in node status.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC018E

UNABLE TO INITIALIZE EIB CHANGE THREAD
Explanation: An error occurred while initializing the thread that monitors the
Candle Management Server hub for changes in node status.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC019E

UNABLE TO ATTACH EIB CHANGE THREAD
Explanation: An error occurred while starting the thread that monitors the
Candle Management Server hub for changes in node status.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC021E

ERROR return_code TRYING TO ADD SITUATION EVENT
Explanation: Return_code was received while processing a situation event.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC022E

INVALID MANAGED OBJECT DEFINITION, NO TEMPLATE
Explanation: A managed object definition without a template specification was
retrieved from the Candle Management Server hub.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Error.

KMVCCC023E

NO SDM INTERFACE AVAILABLE
Explanation: There is no interface to the Status Data Manager (SDM).
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Error.

KMQxx001E–KOCJ0046

295

KMVCCC024E

ERROR return_code TRYING TO CREATE MESSAGE QUEUE
Explanation: Return_code was received while creating a message queue for
internal communications.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC025E

ERROR return_code TRYING TO DESTROY MESSAGE QUEUE
Explanation: Return_code was received while deleting an internal
communications message queue.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC026E

ERROR return_code TRYING TO ADD MESSAGE TO QUEUE
Explanation: Return_code was received while adding a message to an internal
communications message queue.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC027E

ERROR return_code TRYING TO GET MESSAGE FROM QUEUE
Explanation: Return_code was received while getting a message from an
internal communications message queue.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC028I

SHUTDOWN DETECTED
Explanation: Shutdown of the OMEGAVIEW address space has been detected.
System Action: Shutdown continues and shutdown of the KMVCCC
component is initiated.
User Response: None.
Message Type: Information.

KMVCCC029

KMV_CCC ENVIRONMENT VARIABLE = value -- SUPPORT NOT
ENABLED
Explanation: The KMVCCC environment is not enabled. When specifying
OMEGAVIEW configuration values during CICAT configuration, the parameter
Display CCC Alerts? was not specified as Yes. The KMV_CCC environment
variable shows the value specified.
System Action: Processing continues, but the KMVCCC component will not
be activated.
User Response: None.
Message Type: Information.

296

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC030E

UNABLE TO CREATE DIALOG ENVIRONMENT FOR KMVCCC SERVICE
THREAD
Explanation: An internal error occurred that will prevent the creation of the
OMEGAVIEW panel to represent the enterprise.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC031I

KMVCCC SUPPORT INITIALIZATION IS COMPLETE
Explanation: The KMVCCC component is fully initialized.
System Action: Processing continues.
User Response: None.
Message Type: Confirmation.

KMVCCC032I

KMVCCC SHUTDOWN COMPLETE
Explanation: Shutdown of the KMVCCC component is complete.
System Action: None.
User Response: None.
Message Type: Confirmation.

KMVCCC033E

ERROR return_code WHILE FETCHING DATA FROM HUB
Explanation: Return_code was received while retrieving data from the Candle
Management Server hub.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC034E

ERROR return_code INITIALIZING THREAD ATTRIBUTE
Explanation: Return_code was received while initializing a thread attribute.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC035E

ERROR return_code TRYING TO CREATE NEW THREAD
Explanation: Return_code was received while creating a new thread.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC036E

UNABLE TO ATTACH SDM SERVICE THREAD
Explanation: An error occurred while starting the Status Data Manager (SDM)
service thread.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

297

KMVCCC037E

UNABLE TO CREATE DIALOG ENVIRONMENT FOR SDM SERVICE
THREAD
Explanation: An internal error occurred that prevents the creation of the Status
Data Manager (SDM) interface.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC038E

ERROR return_code CREATING NEW STATUS ITEM item
Explanation: Return_code was received while creating the specified status item.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC039E

ERROR return_code OPENING STATUS ITEM item
Explanation: Return_code was received while opening the specified status item.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC040E

ERROR return_code EMITTING VALUE TO ITEM item
Explanation: Return_code was received while emitting a value to the specified
status item.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC041E

ERROR return_code UPDATING RULE FOR ITEM item
Explanation: Return_code was received while updating the rule for the specified
status item.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC042E

ERROR return_code CLOSING STATUS ITEM item
Explanation: Return_code was received while closing the specified status item.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC043E

ERROR return_code DESTROYING STATUS ITEM item
Explanation: Return_code was received while deleting the specified status item.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

298

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC044E

INVALID REQUEST request_code RECEIVED BY SDM SERVICE
Explanation: The Status Data Manager (SDM) service received an invalid
request, request_code.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC045E

INVALID REQUEST request_code RECEIVED BY KMVCCC SERVICE
Explanation: The KMVCCC service received an invalid request, request_code.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC046E

ERROR return_code CREATING SDM SESSION
Explanation: Return_code was received while trying to create the Status Data
Manager (SDM) session.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC047E

UNABLE TO CREATE LOGICAL RESOURCE
Explanation: It was not possible to initialize a logical resource for use by the
KMVCCC support component.
System Action: The current request is terminated. Candle Command Center®
alerts will not be available.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC048E

UNABLE TO PROTECT LOGICAL RESOURCE
Explanation: It was not possible to protect the logical resource used by the
KMVCCC support component.
System Action: The current request is terminated. Candle Command Center
alerts will not be available.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC049E

CONSTRUCTION OF SQL REQUEST OBJECT FAILED
Explanation: An SQL request object failed to initialize properly.
System Action: The current request is terminated. Candle Command Center
alerts will not be available.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC050E

ERROR return_code FROM SQL OPEN REQUEST
Explanation: Return_code was received when opening an SQL request.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

299

KMVCCC051E

ERROR return_code FROM SQL FETCH REQUEST
Explanation: Return_code was received when fetching rows from an SQL
request.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC052E

UNABLE TO LOCATE object MANAGED OBJECT
Explanation: It was not possible to locate the specified managed object while
fetching initial attributes.
System Action: The current request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC053E

NO CHILDREN FOUND FOR THE ENTERPRISE
Explanation: While constructing the initial view of the Candle Command
Center® Enterprise, no subordinate managed objects were found.
System Action: The current request is terminated. Candle Command Center®
alerts will not be available.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC054E

ABEND DETECTED IN THREAD ROUTINE
Explanation: An abend was detected in a thread routine.
System Action: The thread is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC055E

ERROR return_code TRYING TO SUBMIT SDM SERVICE REQUEST
Explanation: An error was encountered while submitting a request to the Status
Data Manager (SDM) server.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC056E

ERROR return_code TRYING TO ADD ROW TO EVENTS TABLE
Explanation: An error was encountered while adding a row to the events table
for a managed object.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC057E

ERROR return_code TRYING TO OPEN THE EVENTS TABLE
Explanation: An error was encountered while opening the event table for a
managed object.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

300

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC058E

UNABLE TO LOCATE EVENT FOR SITUATION situation_name ON NODE
node_name
Explanation: No event entry could be found for the specified situation/node
combination while fetching initial attributes.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC059W

ATTRIBUTE NAME TRANSLATION CANNOT BE PERFORMED
Explanation: The attribute dictionary is unavailable to perform attribute name
translation while fetching initial attributes for a situation event.
System Action: The attribute display will show the untranslated column
names.
User Response: Examine TLVLOG for messages during start-up that might
explain why the attribute dictionary was not built.
Message Type: Internal error.

KMVCCC060E

ERROR return_code TRYING TO TRANSLATE ATTRIBUTE NAME attr
Explanation: An error occurred while translating the specified attribute.
System Action: The attribute display will show the untranslated column name.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC100E

UNABLE TO OPEN DDNAME RKANDATV OPENDIR
Explanation: An error occurred when opening the directory for the partitioned
dataset allocated to ddname RKANDATV.
System Action: Processing of ddname RKANDATV is terminated. Candle
Command Center®alerts will not be available.
User Response: Check the RKANDATV DD statement in the OMEGAVIEW
started task JCL. Verify that the proper runtime dataset is allocated and that
security authorization for read access is granted to the OMEGAVIEW started task.
Message Type: User error.

KMVCCC101I

READDIR ERROR RC=nnn
Explanation: An error or end of directory condition was detected when reading
the directory of the partitioned dataset allocated to ddname RKANDATV. Nnn is
the numeric return code issued by the internal I/O service routine.
System Action: Processing of ddname RKANDATV continues.
User Response: None.
Message Type: Information.

KMVCCC102E

OPENFILE ERROR ON RKANDATV(member) RC=rc
Explanation: An error occurred while opening the specified member of the
partitioned dataset allocated to ddname RKANDATV. Rc is the return code issued
by the internal I/O service routine.
System Action: Processing of ddname RKANDATV is terminated. Candle
Command Center® alerts will not be available.

KMQxx001E–KOCJ0046

301

User Response: Check the RKANDATV DD statement in the OMEGAVIEW
started task JCL. Verify that the proper runtime dataset is allocated and that
security authorization for read access is granted to the OMEGAVIEW started task.
Also ensure that the dataset directory is not corrupted and the dataset was not
being updated while OMEGAVIEW was reading it.
Message Type: User error.
KMVCCC103I

RKANDATV(member) RECORD=data
Explanation: An input record was successfully read from the specified member
of the RKANDATV dataset. Data shows the contents of the record fetched from
the RKANDATV member.
System Action: Processing of the RKANDATV DDNAME continues.
User Response: None.
Message Type: Information.

KMVCCC104I

RKANDATV(member) state
Explanation: A parser state changed after processing an input record read from
the RKANDATV dataset. Member is the member name from which the record
was read. State is the state entered after parsing the new input record.
System Action: Processing of ddname RKANDATV continues.
User Response: None.
Message Type: Information.

KMVCCC105W

DUPLICATE COLUMN=colname FOR ATTRIBUTE=attrnameIN
RKANDATV(member) LINE=nnn
Explanation: A duplicate entry for an existing attribute was found. Colname is
the column name. Attrname is the attribute name. Member is the member where
the duplicate entry was found. Nnn is the record number within the member.
System Action: The duplicate entry is ignored and processing continues.
User Response: None.
Message Type: Internal warning.

KMVCCC106I

ATTRIBUTE CREATED FOR COLUMN=colname
Explanation: A new attribute definition entry was successfully added to the
attribute dictionary. Colname is the column name associated with the new
dictionary entry.
System Action: Processing of the ddname RKANDATV continues.
User Response: None.
Message Type: Confirmation.

KMVCCC107I

RKANDATV(member) tag=value
Explanation: An attribute definition value was successfully parsed from the
current input record read from the RKANDATV dataset. Member is the member
name from which the value was parsed. Tag is the type of data found in the input
record. Value is the value of the data parsed from the input record.
System Action: Processing of ddname RKANDATV continues.
User Response: None.
Message Type: Confirmation.

302

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC108I

RKANDATV(member) tag=nnn
Explanation: An attribute definition value was successfully parsed from the
current input record read from the RKANDATV dataset. Member is the member
name from which the value was parsed. Tag is the type of data found in the input
record. Nnn is the numeric value parsed from the input record.
System Action: Processing of ddname RKANDATV continues.
User Response: None.
Message Type: Confirmation.

KMVCCC109W

DUPLICATE VALI=input FOR VALE=output IN RKANDATV(member)
LINE=nnn
Explanation: A duplicate entry for an attribute translation value was found.
Input and output are the input and output translation values. Member is where
the duplicate entry was found. The record number within the member is nnn.
System Action: The duplicate entry is ignored and processing continues.
User Response: None.
Message Type: Internal warning.

KMVCCC110I

ENUM ENTRY CREATED FOR VALI=input VALE=output
Explanation: A new attribute translation entry was successfully added to the
translation table for an attribute. Input and output are the input and output
translation values.
System Action: Processing of ddname RKANDATV continues.
User Response: None.
Message Type: Information.

KMVCCC111E

UNABLE TO ALLOCATE ATTRIBUTE ENTRY
Explanation: Storage allocation for a new attribute dictionary entry has failed.
System Action: Processing continues to the next attribute definition entry in
the current member of the RKANDATV dataset.
User Response: A low storage condition can be the cause of this error.
Increase the address space virtual storage region or other storage tuning limits for
the OMEGAVIEW address space. Contact Candle Support Services if storage
limits cannot be increased.
Message Type: Internal error.

KMVCCC112E

UNABLE TO CREATE COLUMN KEY=table.colname
Explanation: An error occurred while allocating storage for an attribute
dictionary key. Table is the name of the table and colname is the column name of
the attribute key.
System Action: Processing continues to the next attribute definition entry in
the current member of the RKANDATV dataset.
User Response: A low storage condition can be the cause of this error.
Increase the address space virtual storage region or other storage tuning limits for
the OMEGAVIEW address space. If storage limits cannot be increased, contact
Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

303

KMVCCC118E

ERROR return_code ADDING ROW TO TABLE table
Explanation: An error was encountered while adding a row to the table.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC119E

ERROR return_code OPENING TABLE table
Explanation: An error was encountered while opening the table.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC120W

DUPLICATE ATTRIBUTE=attrname FOR COLUMN=colname
Explanation: A duplicate entry for an existing attribute was found for the named
column and attribute.
System Action: The duplicate entry is ignored and processing continues.
User Response: None.
Message Type: Internal warning.

KMVCCC121E

UNABLE TO CREATE ATTRIBUTE=attrname
Explanation: An error occurred while allocating attribute dictionary entry
storage for the named attribute.
System Action: Processing continues to the next attribute definition entry in
the current member of the RKANDATV dataset.
User Response: A low storage condition can cause this error. Increase the
address space virtual storage region or other storage tuning limits for the
OMEGAVIEW address space. If storage limits cannot be increased, contact
Candle Support Services.
Message Type: Internal error.

KMVCCC122I

ENTRY CREATED FOR ATTRIBUTE=attrname
Explanation: A new attribute definition entry was successfully added to the
attribute dictionary. Attrname is the attribute name associated with the dictionary
entry.
System Action: Processing of the ddname RKANDATV continues.
User Response: None.
Message Type: Confirmation.

KMVCCC123E

UNABLE TO LOCATE SITUATION: sitname
Explanation: The named situation could not be found.
System Action: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMVCCC124E

ERROR return_code ADDING ROW TO NODE DISPLAY TABLE
Explanation: An error was encountered while adding a row to the table.
Message Type: The current request is ignored.
User Response: Contact Candle Support Services.
Message Type: Internal error.

304

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC125E

UNABLE TO ALLOCATE NODE STATUS
Explanation: An error occurred while allocating storage for a node status object.
System Action: Processing continues.
User Response: A low storage condition can cause this error. Increase the
address space virtual storage region or other storage tuning limits for the
OMEGAVIEW address space. If storage limits cannot be increased, contact
Candle Support Services.
Message Type: Internal error.

KMVCCC126E

UNABLE TO ALLOCATE ATTRIBUTE ENUMERATION
Explanation: An error occurred while allocating storage for an attribute
enumeration list.
System Action: Processing continues.
User Response: A low storage condition can cause this error. Increase the
address space virtual storage region or other storage tuning limits for the
OMEGAVIEW address space. If storage limits cannot be increased, contact
Candle Support Services.
Message Type: Internal error.

KMVCCC127E

UNABLE TO ALLOCATE COMMAND NODE ENTRY
Explanation: An error occurred while allocating storage for a command node
entry.
System Action: Processing continues.
Explanation: A low storage condition can cause this error. Increase the address
space virtual storage region or other storage tuning limits for the OMEGAVIEW
address space. If storage limits cannot be increased, contact Candle Support
Services.
Message Type: Internal error.

KMVCCC128E

UNABLE TO ALLOCATE NODE LIST
Explanation: An error occurred while allocating storage for a node list.
System Action: Processing continues.
User Response: A low storage condition can cause this error. Increase the
address space virtual storage region or other storage tuning limits for the
OMEGAVIEW address space. If storage limits cannot be increased, contact
Candle Support Services.
Message Type: Internal error.

KMVCCC130E

CONNECTION TO CMS UNAVAILABLE
Explanation: An attempt to access data from a Candle Management Server.
(CMS) has failed because the communication link between OMEGAVIEW and
the CMS address space has failed.
System Action: CCC/3270 operations indicate that no data was available for
the requested function and panels display no data.
User Response: Determine why the CMS connection has failed.
Message Type: Error.

KMQxx001E–KOCJ0046

305

KMVCCC131E

ALLTYPE type NOT SUPPORTED
Explanation: An attempt to access a console from CCC/3270 has failed because
the type of object used to determine the list of associated consoles could not be
determined or is not one of those supported. The invalid object type is indicated
by type.
System Action: The access console operation ends in error and no consoles
are displayed or selectable.
Explanation: Contact Candle Support Services.
Message Type: Internal Error.

KMVCCC132E

ERROR rc TRYING TO ADD ROW TO TEMP CONSOLE TABLE
Explanation: An attempt to add a new row to an internal console table has
failed, where rc is the error return code issued by table add services.
System Action: The access console operation ends in error and no consoles
are displayed or selectable.
User Response: Contact Candle Support Services.
Message Type: Internal Error.

KMVCCC133E

ERROR rc TRYING TO OPEN THE TEMP CONSOLE TABLE
Explanation: An attempt to create a temporary internal console table has failed,
where rc is the error return code issued by table creation services.
System Action: The access console operation ends in error and no consoles
are displayed or selectable.
Explanation: Contact Candle Support Services.
Message Type: Internal Error.

KMVCCC134E

UNABLE TO ALLOCATE MANAGED SYSTEM LIST FOR objname
Explanation: An attempt to allocate storage for the list of managed systems has
failed. The error can occur when storage shortages occur in the OMEGAVIEW
address space. Objname is the object associated with the managed system list.
System Action: The access console operation ends in error and no consoles
are displayed or selectable.
User Response: Contact Candle Support Services.
Message Type: Internal Error.

KMVCCC135W

NO MANAGED SYSTEMS FOUND FOR moname
Explanation: An attempt to determine the managed systems list for a selected
managed object has failed. A null list of managed systems was defined for the
managed object indicated by moname.
System Action: The access console operation ends in error and no consoles
are displayed or selectable.
User Response: Update the managed object by locating the managed object in
the Candle Management Workstation (CMW) Enterprise container and then
selecting Settings.
Message Type: Warning.

306

Candle Products Messages Manual (KLVHS–KONCT)

KMVCCC150E

Error processing predicate: pdt
Explanation: An error occurred processing the situation predicate.
System Action: The user is prevented from editing the situation.
User Response: Use the Candle Management Workstation editor to determine
the nature of the error.
Message Type: Error.

KN3000000E

ERROR RESOLVING NODENAME nnn
Explanation: None name nnn could not be resolved.
System Action: Processing continues.
User Response: If problem persists, contact Candle Support Services.

KN3AF001

OMEGAMON II for VTAM SHUTDOWN INITIATED –VTAM IS NOT ACTIVE
Explanation: OMEGAMON II for VTAM detected that VTAM was inactive and
initiated shutdown.
System Action: None.
User Response: Investigate the reason for the VTAM outage.
Message Type: Warning.

KN3AF002

COLLECTOR ERROR DURING SAMPLING OR RECORDING INTERVAL
PROCESSING — MODULE(error_module)
Explanation: A collector called during sample or recording interval processing
abended. Diagnostics data are written to the ONSNAP dump dataset and to the
program check or snap table in the product work area extension.
System Action: OMEGAMON II for VTAM continues to run if possible.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF003

BACKGROUND ETE COLLECTOR TERMINATED WITH ERROR —
MODULE(error_module) RC(return_code) SC(sense_code)
Explanation: The background ETE collector terminated due to an internal error.
System Action: OMEGAMON II for VTAM continues to run without the ETE
background collector.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF004

ACT TERMINATED ABNORMALLY
Explanation: The automatic collection task (ACT) terminated abnormally.
System Action: The automatic collection task is unavailable.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF005

NDM FUNCTIONS MODULE KN3AFNDM LOAD FAILED. NCP
STATISTICS DATA NOT AVAILABLE
Explanation: The automatic collection task (ACT) load of the NCP data
manager (NDM) functions module failed.

KMQxx001E–KOCJ0046

307

System Action: NCP statistics information is not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.
KN3AF006

MEMBER KN3CNMAP CONTAINS INVALID ACB NAME
Explanation: The ACB name found exceeds eight alphanumeric characters.
System Action: None.
User Response: Correct the ACB name and restart OMEGAMON II for VTAM.
Message Type: User error.

KN3AF007

MEMBER KN3CNMAP IS EMPTY OR NOT FOUND
Explanation: The member KN3CNMAP does not exist in dataset RKANPAR, or
this member does not contain the ACB name to be used for the communication
network management (CNM) interface.
System Action: None.
User Response: Check the OMEGAMON II for VTAM Configuration and
Customization Guide about member KN3CNMAP, which resides in dataset
RKANPAR.
Message Type: User error.

KN3AF010

CRB ALLOCATION FAILED DURING [TRACE CLEANUP] | [TRACE
DELETE] | [TRACE DISPLAY] | [TRACE INSTALL] | [TRACE REMOVAL] |
[TRACE START] | [TRACE STATUS] | [TRACE STOP] [VTAM TABLE
DISPLAY] — MODULE(error_module) RC(return_code)
Explanation: Collector Request Block (CRB) allocation failed while processing
the specified function.
System Action: The request was not processed.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF011

CRB FREE FAILED DURING [TRACE DELETE] | [TRACE DISPLAY] |
[TRACE INSTALL] | [TRACE REMOVAL] | [TRACE START] | [TRACE
STATUS] | [TRACE STOP] [VTAM TABLE DISPLAY] —
MODULE(error_module) RC(return_code)
Explanation: An attempt to free the Collector Request Block (CRB) failed upon
completion of the specified function.
System Action: The request was processed, but the Collector Request Block
was not freed.
User Response: While this problem does not immediately affect you, repeated
occurrences indicate an internal error. If problem persists, gather the preceding 30
minutes of the RKLVLOG and any dumps that were produced or taken, and
contact Candle Support Services.
Message Type: Internal error.

308

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF012

[TRACE DELETE] [TRACE DISPLAY] | [TRACE INSTALL] | [TRACE
REMOVAL] | [TRACE START] | [TRACE STATUS] | [TRACE STOP]
FAILED — MODULE(error_module) RC(return_code)
Explanation: The specified function failed.
System Action: The request was not processed.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF013

TABLE UPDATE FAILED DURING [TRACE DISPLAY] | [TRACE STATUS]
[VTAM TABLE DISPLAY] — MODULE(error_module) RC(return_code)
Explanation: A table update failed during the specified function.
System Action: The update was not processed.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF021

UNABLE TO OBTAIN LOCK — TYPE(lock_name) MODULE(error_module)
Explanation: While attempting to update monitor options for a user,
OMEGAMON II for VTAM determined that another user was also updating the
options.
System Action: OMEGAMON II for VTAM retries until successful or aborts the
request.
User Response: While this message sometimes occurs, persistent recurrence
warrants further investigation. If problem persists, gather the preceding 30
minutes of the RKLVLOG and any dumps that were produced or taken, and
contact Candle Support Services.
Message Type: Warning.

KN3AF031

VTAM TABLE DISPLAY COLLECTOR FAILED — MODULE(error_module)
RC(return_code) SC(sense_code)
Explanation: The VTAM table display collector failed.
System Action: Processing continues.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF032

VTAM TABLE DISPLAY COLLECTOR FAILED DURING TERMINATION
PROCESSING — MODULE(error_module) RC(return_code)
SC(sense_code)
Explanation: The VTAM table display collector failed during termination of the
VTAM tables display function.
System Action: Processing continues.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

309

KN3AF041

ETE CONNECTION FAILED — MODULE(error_module) RC(return_code)
SC(sense_code)
Explanation: During session establishment for a user, OMEGAMON II for
VTAM detected that the end-to-end response time environment was not
connected. OMEGAMON II for VTAM encountered an error while attempting to
connect the ETE environment.
System Action: Session establishment continues without the ETE feature.
User Response: Verify that the ETE started task is active and that you are
running the correct level of ETE. Also, review the information on enabling ETE in
the OMEGAMON II for VTAM Configuration and Customization Guide. Verify
that all steps completed are accurate. Then, retry logon. If problem persists, gather
the preceding 30 minutes of the RKLVLOG and any dumps that were produced
or taken, and contact Candle Support Services.
Message Type: Probable user error.

KN3AF042

UNABLE TO FREEMAIN USERWORK DURING SESSION TERMINATION
— MODULE(error_module) RC(return_code)
Explanation: FREEMAIN of a user work area failed during session termination.
(return_code is the FREEMAIN return code).
System Action: OMEGAMON II for VTAM continues operation.
User Response: Recurrence of this problem, while not detrimental to the
operation of OMEGAMON II for VTAM, indicates an internal error that needs to
be diagnosed by Candle Support Services. If problem persists, gather the
preceding 30 minutes of the RKLVLOG and any dumps that were produced or
taken, and contact Candle Support Services.
Message Type: Internal error.

KN3AF043

TRACE CLEANUP DETECTED AN ABEND CONDITION — ADDITIONAL
CLEANUP STARTED — MODULE(error_module)
Explanation: A trace facility abend condition was detected while in the process
of removing outstanding traces for a terminating user.
System Action: Trace cleanup attempts to continue.
User Response: If problem persists, gather the preceding 30 minutes of the
RKLVLOG and any dumps that were produced or taken, and contact Candle
Support Services.
Message Type: Internal error.

KN3AF044

ERROR ENCOUNTERED DURING TRACE CLEANUP —
MODULE(error_module) RC(return_code) SC(sense_code)
USERWORK(userwork_address) TRACE
HEADER(trace_header_block_address)
Explanation: OMEGAMON II for VTAM was unable to remove an outstanding
VTAM trace for a terminating user.
System Action: Trace cleanup continues to remove remaining outstanding
traces for the terminating user.
User Response: If problem persists, gather the preceding 30 minutes of the
RKLVLOG and any dumps that were produced or taken, and contact Candle
Support Services.

310

Candle Products Messages Manual (KLVHS–KONCT)

Message Type:

Internal error.

KN3AF045

CAPTURE READER CODES — MODULE(error_module) RC(return_code)
SC(sense_code)
Explanation: This message occurs in conjunction with a previous error message
and provides the internal error codes from the Capture Reader to facilitate
diagnosis by Candle Support Services.
System Action: None.
User Response: None.
Message Type: Internal error.

KN3AF046

ERROR ENCOUNTERED REMOVING TRACE FACILITY DURING
SESSION TERMINATION — MODULE(error_module) RC(return_code)
SC(sense_code) USERWORK(userwork_address)
Explanation: OMEGAMON II for VTAM encounterd an error while attempting
to remove the trace facility during user session termination.
System Action: Session termination continues.
User Response: If problem persists, gather the preceding 30 minutes of the
RKLVLOG and any dumps that were produced or taken, and contact Candle
Support Services.
Message Type: Internal error.

KN3AF047

USER SESSION TERMINATED — RC(return_code) SC(sense_code)
USERWORK(userwork_address)
Explanation: A user session has terminated. If the return/sense codes are
non-zero, OMEGAMON II for VTAM encountered an internal error while
terminating the session.
System Action: User session terminates.
User Response: While this problem has no visible affect on user sessions,
persistent recurrences of a non-zero return code indicate an internal error that
should be diagnosed by Candle Support Services. If problem persists, gather the
preceding 30 minutes of the RKLVLOG and any dumps that were produced or
taken, and contact Candle Support Services.
Message Type: Information/internal error.

KN3AF048

ETE DISCONNECT FAILED — MODULE(error_module) RC(return_code)
SC(sense_code)
Explanation: During session termination for an active user, OMEGAMON II for
VTAM determined that there were no active users of ETE and attempted to
disconnect ETE. An error was encountered.
System Action: Session termination continues.
User Response: If problem persists, gather the preceding 30 minutes of the
RKLVLOG and any dumps that were produced or taken, and contact Candle
Support Services.
Message Type: Internal error.

KN3AF050

CLUSTER INITIAL LOAD SUCCESSFUL FOR DDNAME(ddname)
Explanation: Cluster was successfully reopened and loaded with control record
for the specified ddname.

KMQxx001E–KOCJ0046

311

System Action: Cluster is loaded.
User Response: None.
Message Type: Information.
KN3AF051

CLUSTER INITIAL LOAD FAILED FOR DDNAME(ddname) —
MODULE(error_module) SERVICE(cccc) RC(nn)
Explanation: An error occurred during cluster initial load. Service with name
cccc for file ddname returned with RC=nn.
System Action: Retries several times, then disables VSAM logging if not
successful.
User Response: None.
Message Type: Information.

KN3AF052

UNABLE TO ACCESS RKANPAR — MODULE(error_module)
Explanation: This message is issued in conjunction with message KN3AF060.
During the initialization of VSAM logging, an error occurred requesting access to
the RKANPAR library. A member of this library contains the name of the VSAM
clusters.
System Action: VSAM logging is disabled.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Warning.

KN3AF053

member_name NOT FOUND IN RKANPAR — MODULE(error_module)
Explanation: This message is issued in conjunction with message KN3AF060.
During the initialization of VSAM logging, the member member_name was not
found in the RKANPAR library. This member should be present in RKANPAR and
contain the names of two predefined VSAM clusters.
System Action: VSAM logging is disabled.
User Response: Check that the RKANPAR library is not back-leveled.
Message Type: Installation error.

KN3AF054

ERROR WHEN READING member_name — MODULE(error_module)
Explanation: This message is issued in conjunction with message KN3AF060.
During the initialization of VSAM logging, an error occurred while reading
member member_name from the RKANPAR library. This member should contain
the names of two predefined VSAM clusters.
System Action: VSAM logging is disabled.
User Response: Check member member_name in the RKANPAR library.
Message Type: Warning.

KN3AF055

ERROR WHEN PARSING member_name — MODULE(error_module)
Explanation: This message is issued in conjunction with message KN3AF060.
During the initialization of VSAM logging, an error occurred while parsing
member member_name in the RKANPAR library. This member should contain
the names of two predefined VSAM clusters.
System Action: VSAM logging is disabled.
User Response: Check member member_name in the RKANPAR library.
Message Type: Installation error.

312

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF056

ALLOCATING DATASET dsname
Explanation: VSAM cluster dsname is being allocated for OMEGAMON II for
VTAM.
System Action: VSAM cluster dsname is allocated.
User Response: None.
Message Type: Information.

KN3AF057

CONTROL RECORD GET FAILED FOR DDNAME(ddname) —
MODULE(error_module)
Explanation: OMEGAMON II for VTAM was unable to retrieve control record
for update to file ddname.
System Action: None.
User Response: Check any accompanying messages. Resolve any DASD
problems. If no DASD problems are found, gather the preceding 30 minutes of
the RKLVLOG and any dumps that were produced or taken, and contact Candle
Support Services.
Message Type: Warning.

KN3AF058

CONTROL RECORD PUT FAILED FOR DDNAME(ddname) —
MODULE(error_module)
Explanation: OMEGAMON II for VTAM was unable to update control record
for file ddname.
System Action: None.
User Response: Check any accompanying messages. Resolve any DASD
problems. If no DASD problems are found, gather the preceding 30 minutes of
the RKLVLOG and any dumps that were produced or taken, and contact Candle
Support Services.
Message Type: Warning.

KN3AF059

UNABLE TO COMPLETE PUT TO VSAM DSN(dsname) —
MODULE(error_module)
Explanation: OMEGAMON II for VTAM was unable to complete PUT to
dsname before the next data sample became available. This can be the result of a
DASD problem or a performance problem.
System Action: OMEGAMON II for VTAM does not log current sample data to
a VSAM cluster.
User Response: In case of a contention or performance problem, try to
increase the dispatching priority of OMEGAMON II for VTAM.
Message Type: Warning

KMQxx001E–KOCJ0046

313

KN3AF060

VSAM LOGGING DISABLED — MODULE(error_module) REASON
(cccccccc)
Explanation: VSAM logging is disabled and the reason for it is cccccccc. This
message is usually accompanied by other messages in RKLVLOG. Following is
the list of possible reasons:.
LOAD

Some modules are missing.

ALLOC

Error during VSAM dataset allocation.

INIT

Error during initial load to VSAM cluster.

PUT

Error during VSAM PUT. Probable DASD problem.

INTERNAL

Internal error.

ABEND

Abend occurred during logging to VSAM cluster.

VSAMSERV

Internal VSAM services are unavailable.

System Action: VSAM logging is disabled.
User Response: Check for accompanying messages for any of the following
reasons:.
LOAD

Check installation.

ALLOC

Check installation.

PUT, INIT

Check for DASD problem.

INTERNAL,
ABEND

Contact Candle Support Services.

VSAMSERV

Check to make sure that termination was requested. If it was not,
gather the preceding 30 minutes of the RKLVLOG and any dumps
that were produced or taken, and contact Candle Support
Services.

Message Type:

Warning.

KN3AF061

ERROR WHEN READING FROM DSN(dsname) — MODULE(error_module)
Explanation: An error occurred when reading from a VSAM cluster named
dsname. This indicates a DASD problem.
System Action: None.
User Response: Check for any accompanying messages in RKLVLOG and
respond according to those messages.
Message Type: Warning.

KN3AF062

PUT FAILED FOR REASON OTHER THAN EOF FOR DSN(dsname) —
MODULE(error_module) FDBWD(fdbwd)
Explanation: OMEGAMON II for VTAM encountered an error while writing an
exception or interval record to the cluster dsname.
System Action: None.
User Response: Check for any accompanying messages in RKLVLOG and
respond according to those messages.
Message Type: Warning.

314

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF110

dialog_function - UNABLE TO OBTAIN PASSED
PARAMETER(parameter_name)
Explanation: The dialog function module (dialog_function), was not passed
parameter (parameter_name) from the dialog panel.
System Action: No data is displayed on the associated panel.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF111

dialog_function - NON-ZERO RETURN CODE FROM NDM CALL
FUNC=function_name, RETC=return code, REAS=reason_code.
Explanation: The call to the NCP data manager (NDM) from dialog function
(dialog_function) was unsuccessful. function_name is the function being
attempted, return_code is the NDM return code and reason_code is the NDM
reason code.
System Action: No data is displayed on the associated panel.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF112

dialog_function - NO control_block_name RETURNED FROM NDM CALL
Explanation: The call to the NCP data manager (NDM) from dialog function
(dialog_function) did not return control block (control_block_name).
System Action: No data is displayed on the associated panel.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF113

dialog_function - ERROR ADDING ROW TO TABLE FOR RESOURCE
(resource_name).
Explanation: The call from dialog function (dialog_function) to table services to
add a row to the display table for resource (resource_name) was unsuccessful.
System Action: No data is displayed on the associated panel.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF114

KN3AFNM0 - NO HASH TABLE ADDRESS FOUND IN NDA WORKAREA
Explanation: The address of the KN3AYNRE hash table was not found in the
NCP data manager task global anchor block, KN3AYNDA.
System Action: The NCP Performance light on the main status panel displays
IDLE.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

315

KN3AF115

KN3AFNM1 - UNABLE TO LOCATE SITE MONITOR TABLE: tablename.
Explanation: The dialog function was unable to obtain the handle of the NCP
site monitor table, tablename.
System Action: The threshold block, KN3AYNPB, is not updated with the
NCP site default monitor options.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF116

KN3AFNM1 UNABLE TO BUILD|LOCATE|MODIFY NPB|NSB FOR
resource_name TYPE=resource_type RC=return_code.
Explanation: An error occurred while processing an update request to the NCP
site monitor table options. The requested control block function has returned an
error. resource_name is the name of the resource, resource_type is the NRE
resource type and return_code is the return code from the control block function.
System Action: The NCP monitoring options are not updated.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF117

dialog_function NCP RESOURCE TYPE=resource_type NOT SUPPORTED
Explanation: A dialog passed an unknown resource type (resource_type) to
dialog function (dialog_function).
System Action: No data is displayed on the associated panel.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF118

function NPB|NSB FOR DELETE|START|STOP NOT LOCATED,
NAME=resource_name, TYPE=resource_type, RC=return_code.
Explanation: A request to delete, start or stop monitoring for a resource was
unable to locate the required control block. resource_name is the resource name,
resource_type is the NCP resource type and return_code is the return code from
the control block locate function.
System Action: The NCP resource remains in its currently monitored or
unmonitored state.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF119

NDM CONTROL MODULE KN3AFNSB LOAD FAILED. NCP STATISTICS
DATA NOT AVAILABLE.
Explanation: The automatic collection task (ACT) load of the NCP data
manager (NDM) control module failed.
System Action: NCP statistics information is not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

316

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF120

NDM FUNCTIONS INITIALIZATION FAILED REASON(reason_code)
Explanation: The automatic collection task (ACT) initialization of NCP data
manager (NDM) functions failed.
System Action: NCP statistics information is not available.
User Response: Verify the following reasons:
NDMINSTL

KN3FCCMD INSTALL NDMT was not performed at product
initialization. Install NDMT and restart the automatic collection task.

NDMDRLRN

Unable to acquire CT/Engine logical resource number. Log the
information displayed for problem diagnosis and contact Candle
Support Services.

ABEND

An abend occurred. Log the information displayed for problem
diagnosis and contact Candle Support Services.

Message Type:

User or internal error.

KN3AF121

NDM STARTUP FAILED RC(return_code) SC(sense_code) WILL RETRY
EACH ACT CYCLE INTERVAL
Explanation: The automatic collection task (ACT) could not start the NCP data
manager (NDM) task.
System Action: NCP statistics information is not available.
User Response: See the OMEGAMON II for VTAM NCP Data Manager Task
Return & Sense Codes appendix.
Message Type: Warning.

KN3AF122

NCP RESOURCE (resource_name) OWNED BY (npalu_name) DELETED
FROM RESOURCE TOPOLOGY
Explanation: An NCP resource has become unavailable to monitor.
System Action: NCP statistics information is not available for the resource.
User Response: Check the status of the NCP resource.
Message Type: Information.

KN3AF123

NCP TOPOLOGY UPDATE ERRORS DETECTED RC(return_code)
SC(sense code) WILL RETRY EACH ACT CYCLE INTERVAL
Explanation: NCP data manager (NDM) was unable to refresh the NCP
topology with data from the data server.
System Action: NCP statistics information is not available.
User Response: See OMEGAMON II for VTAM NCP Data Manager Task
Return & Sense Codes appendix.
Message Type: Warning.

KN3AF124

NCP RESOURCE(resource_name) OWNED BY npalu_name DELETED
FROM MONITORED TOPOLOGY
Explanation: An NCP resource has become unavailable to monitor.
System Action: NCP statistics information is not available for the resource.
User Response: Check the status of the NCP resource.
Message Type: Information.

KMQxx001E–KOCJ0046

317

KN3AF125

NCP DATA UPDATE ERRORS DETECTED RC(return_code) SC(sense
code)
Explanation: NCP data manager (NDM) was unable to refresh the NCP
topology with data from the data server.
System Action: NCP statistics information is not available for specific or all
resources.
User Response: See the OMEGAMON II for VTAM NCP Data Manager Task
Return & Sense Codes appendix.
Message Type: Warning.

KN3AF126

NCP DATA EXTRACT ERRORS DETECTED RC(return_code)
SC(sense_code)
Explanation: The automatic collection task (ACT) detected errors extracting
NCP statistics data from the NCP data manager (NDM).
System Action: NCP statistics information is not available for specific or all
resources.
User Response: See the OMEGAMON II for VTAM NCP Data Manager Task
Return & Sense Codes appendix.
Message Type: Warning.

KN3AF127

NCP STATISTICS DATA COLLECTION DISABLED
Explanation: The automatic collection task (ACT) determined that too many
errors associated with NCP statistics collection have occurred.
System Action: NCP statistics information is not available.
User Response: See previously issued messages.
Message Type: Warning.

KN3AF128

KN3AFNDM ABEND CODE(abend_code) ROUTINE(routine_name)
Explanation: An abend occurred in a KN3AFNDM process routine.
System Action: NCP statistics information is not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF129

NSB FUNCTIONS INITIALIZATION FAILED REASON(reason_code)
Explanation: The automatic collection task (ACT) initialization of the NCP start
block (NSB) functions failed.
System Action: NCP statistics information is not available.
User Response: Verify the following reasons:

318

NDMINSTL

KN3FCCMD INSTALL NDMT was not performed at product
initialization. Install NDMT and restart the automatic collection task.

ABEND

An abend occurred. Log the information displayed for problem
diagnosis and contact Candle Support Services.

Message Type:

Internal or user error.

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF130

START REQUEST RESOURCE(resource_name) NPALU(npalu_name)
GENDATE(generation_date) GENTIME(generation_time) FAILED
Explanation: The automatic collection task (ACT) was unable to start
monitoring an NCP resource. OMEGAMON II was unable to find resources that
match the generation date and generation time.
System Action: NCP statistics information is not available for the named
resource.
User Response: Ensure that the NCP generation date and generation time are
correct for the requested NCP to monitor.
Message Type: User error.

KN3AF131

request FAILED FOR RESOURCE(resource_name) NPALU(npalu_name)
GENDATE(generation_date) GENTIME(generation_time)
Explanation: The automatic collection task (ACT) was unable to start or stop
monitoring for a specific NCP resource.
System Action: NCP statistics information may be incomplete.
User Response: If the resource is valid for start or stop, log the information
displayed for problem diagnosis and contact Candle Support Services.
Message Type: User error.

KN3AF132

KN3AFNSB ABEND CODE(abend_code) ROUTINE(resource_name)
Explanation: An abend occurred in a KN3AFNSB process routine.
System Action: NCP statistics information may not be available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF133

NCP TOPOLOGY GENLEVEL MISMATCH FOR
RESOURCE(resource_name) NPALU(npalu_name)
GENDATE(generation_date) GENTIME(generation_time)
Explanation: The automatic collection task (ACT) detected a GENLEVEL
mismatch for a start or stop monitor request. OMEGAMON II was unable to find
resources that match the generation date and generation time.
System Action: NCP statistics information is not available for the named
resource.
User Response: Maintain the NCP site monitor options to ensure that the only
resources that have start or autostart options are those that match the current
NCP generation levels active in the network.
Message Type: User error.

KMQxx001E–KOCJ0046

319

KN3AF134

NCP TOPOLOGY NOT CREATED. WILL RETRY NEXT ACT CYCLE
INTERVAL
Explanation: The NCP resources have not been received from the NCP
collector task.
System Action: None
User Response: After a reasonable amount of time, if the NCP performance
status light continues to display N/A, check the NPALU connection to
OMEGAMON II for VTAM.
Message Type: Warning

KN3AF135

ACT LOCATE FAILED RC(return_code) SC(sense_code)
MODULE(module_name)
Explanation: An error was encountered in locating the automatic collection task
(ACT) work area. The ACT return code, sense code, and issuing module are
displayed in the message text.
System Action: OMEGAMON II for VTAM cannot successfully complete
initialization.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF136

KN3AXNPB ADD_NPB FUNCTION FAILED RC(return_code)
MODULE(module_name)
Explanation: An error occurred while adding an NCP parameter block (NPB) to
the NPB chain. Return code and issuing module are displayed in the message
text.
System Action: If the error occurred in module KN3AFNMI, the NCP
component cannot successfully complete initialization. However, if the error
occurred in a module other than KN3AFNMI, only the ADD for the selected
resource fails.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF137

KN3AXNSB ADD FUNCTION FAILED RC(return_code)
MODULE(module_name)
Explanation: An error occurred while adding an NCP parameter block (NPB) to
the NPB chain. Return code and issuing module are displayed in the message
text.
System Action: If the error occurred in module KN3AFNMI, the NCP
component cannot successfully complete initialization. However, if the error
occurred in a module other than KN3AFNMI, only the ADD for the selected
resource fails.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

320

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF138

KN3AXNPB GET_HASH FUNCTION FAILED RC(return_code)
MODULE(module_name)
Explanation: An error was encountered in creating the NCP parameter block
(NPB) hash table. Return code and issuing module are displayed in the message
text.
System Action: NCP component cannot successfully complete initialization.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF139

function_name GET STATUS RETURN CODE=return_code
HSHRC=Hash_Table_Services_return_code
Explanation: A request by function (function_name) to obtain the status lights
for a resource has failed. return_code is the function return code and
Hash_Table_Services_return_code is the Hash Table Services return code, if
applicable.
System Action: The status light for the resource displays Idle.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF140

NDM ACT RESOURCE CLEANUP IN PROGRESS
Explanation: The automatic collection task (ACT) has detected changes in the
NCP data manager (NDM) task and has requested a reset of current NDM
resources in use.
System Action: NCP statistics are incomplete for the current sample interval.
User Response: None.
Message Type: Warning.

KN3AF141

NDM ACT RESOURCE CLEANUP COMPLETE
Explanation: The automatic collection task (ACT) has reset all NCP data
manager (NDM) resources and will reinitialize NCP data collection at the next
sample interval.
System Action: Automatic collection task NCP statistics data is finalized for the
current sample interval.
User Response: None.
Message Type: Information.

KN3AF142

NDM TASK HAS RECYCLED SINCE LAST INTERVAL. RESOURCE
CLEANUP REQUESTED.
Explanation: The automatic collection task (ACT) detected that the NCP data
manager (NDM) task has been recycled during the current collection interval.
System Action: NCP statistics are incomplete for the current sample interval.
User Response: None.
Message Type: Warning.

KMQxx001E–KOCJ0046

321

KNOAF143

NCP VSAM LOGGING MODULE KN3AFNVW LOAD FAILED. NCP
STATISTICS DATA NOT AVAILABLE.
Explanation: The automatic collection task (ACT) was unable to load
KN3AFNVW.
System Action: NCP statistics are not available.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF144

KN3AFNDM SMFWTM FAILED TO LOG SMF RECORD RC (return_code)
Explanation: An error occurred while logging an SMF record table. Return code
is displayed in message text.
System Action: NCP statistics are not logged to SMF.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF145

KN3AFNDU UNABLE TO ALLOCATE KN3AYNRE (control_block_name)
SEGMENT FOR RESOURCE(resource_name) NPALU(npalu_name)
Explanation: The automatic collection task (ACT) was unable to allocate a
control block.
System Action: NCP statistics are not available for the NCP resource.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF146

KN3AFNMI - NCP DATA MANAGER TASK NOT INSTALLED
Explanation: The OMEGAMON II for VTAM initialization process detected that
the NCP data manager task was not installed.
System Action: NCP statistics are not available.
User Response: Ensure that a KN3FCCMD INSTALL NDMT is specified in
KN3STKN3. For more information, see the OMEGAMON II for VTAM
Configuration and Customization Guide.
Message Type: User error.

KN3AF147

module_name NPALU=npalu_name, OWNER=resource_name,
GENDATE/TIME=generation_date/generation_time
Explanation: This message follows message number KN3AF118 and gives
additional information about the failing resource. module_name is the name of
the module detecting the error, npalu_name is the name of the NPALU resource,
resource_name is the owning resource name, and
generation_date/generation_time is the generation date and time of the NCP
which contains the failing resource.
System Action: No data is displayed.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

322

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF148

module_name LOWER LEVEL MONITORED RESOURCES EXIST FOR
resource_name
Explanation: A request to stop monitoring an NCP resource has been entered,
but there are lower level resources which are still being monitored. These
resources must be manually stopped, before the requested resource can be
stopped module_name is the name of the module detecting the error, and
resource_name is the name of the resource that was to be stopped.
System Action: A pop-up appears explaining the available options.
User Response: None.
Message Type: Warning.

KN3AF149

module_name GET CRB FAILED, RC=return_code, SC=sense_code
Explanation: Module(module_name) was unable to obtain a Collector Request
Block (CRB). return_code is the return code and sense_code is the sense code
from the KN3AXCRB macro.
System Action: No data is displayed for some fields.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF150

module_name COLLECTOR(collector_module) ERROR, RC=return_code,
SC=sense_code
Explanation: Module(module_name) called collector module
(collector_module) to obtain data. The collector was unable to obtain the
requested data.return_code is the return code and sense_code is the sense code
from the collector.
System Action: No data is displayed for some fields.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF151

SMF RESPONSE TIME RECORDING FOR NCP RESOURCES IS INACTIVE
Explanation: The automatic collection task (ACT) cannot collect response time
data for NCP resources because of any of the following reasons:
® The NPALU is inactive.
® The NCP collector is down.
® The NCP collector is not connected to the NPALU.
System Action: SMF response time groups for NCP resources are marked
inactive in OMEGAMON II for VTAM and no SMF records are written for these
groups.
User Response: Investigate the status of the NPALU, NCP collector, and the
session between them. Refer to the OMEGAMON II for VTAM Configuration and
Customization Guide.
Message Type: Warning.

KMQxx001E–KOCJ0046

323

KN3AF153

ACT NPB CHECK FOR RESOURCE(ncp_resource_name)
NPALU(npalu_name) FAILED RC(return_code)
Explanation: The Automatic Collection Task (ACT) was unable to analyze the
named NCP resource for an exception condition. This can occur during ACT
cleanup processing because the session monitoring the named NPALU was lost.
System Action: No exception conditions can be reported for the named
resource.
User Response: If ACT cleanup has been requested (as expressed by message
KN3AF142), no response is required. Otherwise, contact Candle Support
Services.
Message Type: Warning.

KN3AF154

TOPOLOGY UPDATE FUNCTIONS INITIALIZATION FAILED
REASON(reason_code)
Explanation: The Automatic Collection Task (ACT) initialization of NCP
topology update functions failed.
System Action: NCP performance statistics are not available.
User Response: Depending on the reason given in the message, take one of
the following actions:.
NDMINSTL

KN3FCCMD INSTALL NDMT was not performed at OMEGAMON
II for VTAM initialization. Install NDMT and restart OMEGAMON II
for VTAM.

ABEND

An abend occurred. Log the information displayed for problem
diagnosis and contact Candle Support Services.

Message Type:

User or internal error.

KN3AF155

NCP TOPOLOGY UPDATE ERRORS DETECTED RC(return_code)
SENSE(sense_code). WILL RETRY EACH TOPOLOGY UPDATE
INTERVAL.
Explanation: The NCP Data Manager task (NDM) was unable to refresh the
NCP topology with data from the NCP collector.
System Action: The NCP topology is not updated.
User Response: See the OMEGAMON II for VTAM NCP Data Manager Task
Return & Sense Codes appendix.
Message Type: Warning.

KN3AF156

KN3AFNUT ABEND CODE(abend_code) ROUTINE(routine_name)
Explanation: An abend occurred in a KN3AFNUT process routine.
System Action: NCP performance statistics are not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

324

Candle Products Messages Manual (KLVHS–KONCT)

KN3AF157

TOPOLOGY UPATE FUNCTIONS MODULE KN3AFNUT LOAD FAILED.
NCP STATISTICS DATA NOT AVAILABLE.
Explanation: The Automatic Collector Task (ACT) load of the NCP topology
update functions module failed.
System Action: NCP performance statistics are not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3AF158

KN3AXNSB START FUNCTION FAILED FOR RESOURCE resource_name
RC(return_code) MODULE(module_name) EXECUTION CONTINUES
Explanation: An error occurred while processing a START function for a
defined NCP resource. The resource may not be correctly monitored. The
resource name, return code, and issuing module name are displayed in the
message.
System Action: Processing continues.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF159

KN3AXNSB STOP FUNCTION FAILED FOR RESOURCE resource_name
RC(return_code) MODULE(module_name) EXECUTION CONTINUES
Explanation: An error occurred while processing a STOP function for a defined
NCP resource. The resource may not be correctly monitored. The resource name,
return code, and issuing module name are displayed in the message.
System Action: Processing continues.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF160

module SUBORDINATE ROUTINE FAILED. FUNCTION TYPE: func_type
RETURN CODE: rc
Explanation: A call to the indicated module requested the indicated function to
be performed and the function failed.
System Action: Requested function is not performed and processing
continues.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3AF161

MODULE(module) NON-ZERO RETURN CODE FROM TCP/IP CALL,
MACRO(macro), RC(return_code)
Explanation: The specified module issued the specified TCP/IP API macro call
and received a non-zero return code.
System Action: The request is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

325

KN3CT000

TCP/IP STATISTICS COLLECTOR INITIALIZATION COMPLETE
Explanation: The TCP/IP collector successfully initialized.
System Action: None.
User Response: None
Message Type: Confirmation.

KN3CT001

$INIT FAILED FOR MAIN THREAD LRN
Explanation: A logical resource could not be acquired for the TCP/IP collector
task.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT002

TCP/IP STATISTICS COLLECTOR ABENDED, CODE=abend_code,
PSW=program_status_word, ROUTINE=program_name
Explanation: The TCP/IP collector task abended. The abend code, program
status word (PSW), and program name are displayed in the message.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services. See message KN3CT003 which follows.
Message Type: Internal error.

KN3CT003

Rregister_number - Rregister_number register_value
Explanation: This is diagnostic information following message KN3CT002.
System Action: None.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT004

TCP/IP STATISTICS COLLECTOR IS TERMINATING
Explanation: The TCP/IP collector is terminating.
System Action: None.
User Response: None
Message Type: Information.

KN3CT007

TCP/IP STATISTICS COLLECTOR COMPLETED TERMINATION
Explanation: The TCP/IP collector successfully completed termination.
System Action: None.
User Response: None
Message Type: Confirmation.

KN3CT008

ERROR PROCESSING NETSTAT command_name COMMAND
Explanation: An error occurred while processing the output of the named
NETSTAT command.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

326

Candle Products Messages Manual (KLVHS–KONCT)

KN3CT009

{TCP/IP COLLECTOR | MIB BROWSER} MEMORY ALLOCATION FAILED
Explanation: A memory allocation failed in the specified function.
System Action: The function terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT010

$ALOCQ FAILED: RC(return_code), ERROR(reason_code),
INFO(information_code)
Explanation: An SVC 99 query failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT011

$ALOC FAILED: RC(return_code), ERROR(reason_code),
INFO(information_code)
Explanation: An SVC 99 dynamic allocation failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT012

DSPSERV FAILED: RC(return_code)
Explanation: A dataspace create failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT013

ALESERV FAILED: RC(return_code)
Explanation: An ALET add failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT014

NAME/TOKEN CREATE FAILED: RC(return_code)
Explanation: The create of a name/token pair failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

327

KN3CT015

SNMP MANAGER ATTACH FAILED: RC(return_code)
Explanation: The attach of the SNMP manager task failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT050

SNMP MANAGER HAS TERMINATED
Explanation: The SNMP manager task terminated.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT051

RESMGR ADD FAILED: RC(return_code)
Explanation: The addition of a dynamic resource manager failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT052

SNMP MANAGER ERROR: RC(return_code)
Explanation: An SNMP manager request failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT053

SNMP MANAGER REQUEST TIMED OUT
Explanation: An SNMP manager request timed out before a response was
received.
System Action: The TCP/IP collector continues.
User Response: Ensure that the IBM-supplied TCP/IP SNMP agent address
space is running and is receiving adequate service from the operating system.
Message Type: Information.

KN3CT100

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS}
INITIALIZATION COMPLETE
Explanation: The specified function successfully initialized.
System Action: None.
User Response: None.
Message Type: Confirmation.

328

Candle Products Messages Manual (KLVHS–KONCT)

KN3CT102

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS} ABENDED,
CODE=abend_code, PSW=program_status_word,
ROUTINE=program_name
Explanation: The specified function abended. The abend code, Program Status
Word (PSW), and program name are displayed in the message.
System Action: The function terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services. See message KN3CT103 which follows.
Message Type: Internal error.

KN3CT103

Rregister_number - Rregister_number register_value
Explanation: This is diagnostic information following message KN3CT102.
System Action: None.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT104

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS} IS TERMINATING
Explanation: The function is terminating.
System Action: None.
User Response: None.
Message Type: Information.

KN3CT107

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS} COMPLETED
TERMINATION
Explanation: The function successfully completed termination.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3CT110

I/O FAILED FOR COMMAND OUTPUT DD. FUNCTION: function_name,
REASON reason_code
Explanation: An I/O request for the named function failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT111

COMMAND ATTACH FAILED: RC(return_code)
Explanation: The attach of a TCP/IP command processor failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

329

KN3CT112

$GMEM FAILED FOR COMMAND OUTPUT RECORD
Explanation: A memory allocation failed in the TCP/IP service task.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT113

$GMEM FAILED FOR COMMAND PARAM STRUCTURE
Explanation: A memory allocation failed in the TCP/IP service task.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT121

TCP/IP ADDRESS SPACE COLLECTOR FAILED.
ROUTINE=program_name, REASON=failure_reason, RETURN=return_code
Explanation: TCP/IP address space data collection failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT122

TCP/IP function_name FAILED. ERRNO=error_code
Explanation: The named TCP/IP function failed in the TCP/IP collector.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT123

TCP/IP API LOAD FAILED
Explanation: The load of the TCP/IP API support module failed.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3CT124

TCP/IP IMAGES
Explanation: This is a message header. It is the first message of a multiple
message group. Multiple KN3CT125 messages may follow KN3CT124.
System Action: None.
User Response: None
Message Type: Informational.

330

Candle Products Messages Manual (KLVHS–KONCT)

KN3CT125

NAME=name STATUS=status HOST=host IPADDR=xxx.xxx.xxx.xxx
Explanation: One KN3CT125 message per TCP/IP image follows message
KN3CT124, where:
NAME

TCP/IP procedure name.

STATUS

Active, Terminating, Down, Stopped, or Stopping.

HOST

TCP/IP host name.

IPADDR

Host primary IP address.

System Action: None.
User Response: None.
Message Type: Informational.
KN3CT131

MIB BROWSER INITIALIZATION FAILED: RC(retcode)
Explanation: Initialization of the MIB browser task failed with the return code
indicated.
System Action: The MIB browser terminates.
User Response: Log the information for problem diagnosis and contact Candle
Customer Support.
Message Type: Internal error.

KN3CT132

MIB BROWSER IS NOT ACTIVE RC=retcode MODULE(module)
Explanation: An attempt was made to use the MIB browser function of the
TCP/IP console, but the browser is not active.
System Action: The MIB browser function does not complete.
User Response: Examine the TLVLOG for messages KN3CT131, KN3CT050,
KN3CT051, KN3CT052, KN3CT053, or KN3CT009. If the messages indicate a
problem with SNMP, this may be a problem with the SNMP agent. Check the
status of the SNMP agent and examine the SNMP log for possible problems. A
restart of the SNMP agent and OMEGAMON may be necessary. If this fails to
resolve the problem, log the information for problem diagnosis and contact
Candle Customer Support.
Message Type: User or internal error.

KN3CT201

KN3CT201 module - UNABLE TO LOAD MODULE module
Explanation: TCP/IP component start-up was unable to load the specified
module.
System Action: The OMEGAMON II for VTAM TCP/IP component is
terminated.
User Response: Ensure that all installation and maintenance jobs ran correctly.
Then contact Candle Support Services.
Message Type: Probable installation error.

KMQxx001E–KOCJ0046

331

KN3CT202

KN3CT202 module - STORAGE ALLOCATION FAILURE SIZE = bytes
Explanation: The specified module was unable to allocate the specified number
of bytes of virtual storage.
System Action: The function requiring the process is not successful.
User Response: Ensure that the configuration values have not been modified.
Then contact Candle Support Services.
Message Type: User or internal error.

KN3CT203

KN3CT203 module - EXCEPTION GROUP group NOT DEFINED
Explanation: The specified module was unable to find a definition for the
specified exception group.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3CT204

KN3CT204 module - EXCEPTION excp NOT DEFINED
Explanation: The specified module was unable to find a definition for the
specified exception.
System Action: The request is terminated.
User Response: Contact Candle Support Services
Message Type: Internal error.

KN3CT205

KN3CT205 KN3AITXB - REQUIRED PARAMETER NOT SUPPLIED FOR
EXCEPTION: group excp
Explanation: Module KN3AITXB was passed an exception threshold for the
specified exception and group. The threshold was missing a required parameter.
Message Type: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3CT206

KN3CT206 KN3AITXB - INVALID HOST NAME dnsname
Explanation: Module KN3AITXB was passed the specified DNS name as part of
a high-priority connection definition. The name could not be resolved to an IP
address.
System Action: The request is terminated.
User Response: Ensure that the DNS name is valid. Then contact Candle
Support Services.
Message Type: User or internal error.

KN3CT207

KN3CT207 KN3AITXB - EZASMI INITIALIZATION FAILURE, RC = rc
Explanation: Module KN3AITXB was unable to initialize the EZASMI interface.
System Action: The process was terminated.
User Response: Check the return codes for the EZASMI INITAPI call and
contact Candle Support Services.
Message Type: Internal error.

332

Candle Products Messages Manual (KLVHS–KONCT)

KN3CT208

KN3CT208 KN3AITXB - EZASMI GETHOSTNAME FAILURE
Explanation: Module KN3AITXB could not perform a GETHOSTBYNAME
function via the EZASMI interface.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3CT209

KN3CT209 KN3AITXB - INVALID RETURN CODE FROM KN3APTXE
Explanation: Module KN3AITXB received an invalid return code from module
KN3APTXE.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3CT210

KN3CT210 KN3AITDE - INVALID ELEMENT INPUT: type
Explanation: Module KN3AITDE received a request for data with the specified
type which is invalid.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3CT211

KN3CT211 KN3AITXI -- UNABLE TO INITIALIZE EZASMI, RETURN CODE
= rc, REASON CODE = reason
Explanation: Module KN3AITXI was unable to initialize the EZASMI interface
The return code and reason code are displayed in the message.
System Action: The TCP/IP component is terminated.
User Response: Check for installation errors based on the return code. Then
contact Candle Support Services.
Message Type: User or internal error.

KN3CT301

KN3CT301 KN3AITDI - UNABLE TO LOAD MODULE module
Explanation: TCP/IP component start-up was unable to load the specified
module.
System Action: The OMEGAMON II for VTAM TCP/IP component is
terminated.
User Response: Ensure that all installation and maintenance jobs ran correctly.
Then contact Candle Support Services.
Message Type: Probable installation error.

KN3CT302

KN3CT302 KN3AITDE - REQUIRED SUB-ELEMENT PARAMETER
MISSING
Explanation: Module KN3AITDE received a request with a required
sub-element missing.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

333

KN3CT303

KN3CT303 KN3AITDD - INVALID ELEMENT PARAMETER parm
Explanation: Module KN3AITDD received a request with the specified element
parameter which is invalid.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3CV001

FIND REQUIRES STRING
Explanation: The FIND command was entered at the VTAM Console without a
character string.
System Action: None.
User Response: Enter the FIND command with a character string.
Message Type: User input error.

KN3CV002

CHARACTER STRING NOT FOUND
Explanation: A FIND command was entered at the VTAM Console. The
console log was searched, but no matching character string was found.
System Action: None.
User Response: Verify that the correct character string was specified.
Message Type: Information.

KN3CV003

LOCATE REQUIRES STRING
Explanation: A LOCATE command was issued at the VTAM Console. The
VTAM console log was searched, but no matching character string was located.
System Action: None.
User Response: Verify that the correct character string was specified.
Message Type: Information.

KN3CV004

VTAM COMMAND ERROR
Explanation: An internal error was detected while attempting to execute a
VTAM console command.
System Action: None.
User Response: Verify that the OMEGAMON II console APPLID prefix
specified on the Global Options panel contains the same first six characters of the
applids with auth=(pass,acq,spo) in the SYS1.VTAMLST member used to define
OMEGAMON II to VTAM.
Message Type: Installation error.

KN3CV005

VR IS NOT ACTIVE
Explanation: The VR that was selected is currently not active. Only active VRs
can be selected with a / or an action code.
System Action: None.
User Response: Select an active VR.
Message Type: User input error.

KN3CV006

FIELD IS NOT PROMPTABLE
Explanation: The prompt key (F4) was pressed when the cursor was not in a
promptable field. The prompt key can only be used in fields that are accompanied

334

Candle Products Messages Manual (KLVHS–KONCT)

by an adjacent plus (+) sign. When the input field is not promptable, you must
type the requested data.
System Action: None.
User Response: Enter the requested data.
Message Type: User input error.
KN3CV007

MUST BE EQ, NE, LT, LE, GT, or GE
Explanation: An invalid Operator was entered in response to a View Some
popup.
System Action: None.
User Response: Place the cursor in the operator field and press the prompt
(F4) key to obtain a list of valid operators. Tab to the desired operator and press
Enter.
Message Type: User input error.

KN3CV008

MUST BE NUMERIC
Explanation: A non-numeric value was entered in a field that requires a
numeric value.
System Action: None.
User Response: Enter a numeric value in the field.
Message Type: User input error.

KN3CV009

INVALID SELECTION
Explanation: An attempt to select an item from a menu was made; the number
or mnemonic that was entered is not on the menu, or the cursor is not positioned
to the left of a valid selection.
System Action: None.
User Response: Retype the selection character, or place the cursor to the left of
a valid selection and press Enter.
Message Type: User input error.

KN3CV010

SAMPLING INTERVAL WAS TOO LONG, TRY AGAIN
Explanation: The sampling interval used for calculating PIU rates is measured
from one panel refresh to the next panel refresh, with 30 seconds being the
maximum sample interval. The interval between presses of the Enter or F5 key
exceeded 30 seconds.
System Action: When the system detects that the maximum sample interval
has been exceeded, it issues this message and a new sampling interval is started.
Elapsed time in the interval is reset to zero.
User Response: Press the Enter key any time within the next 30 seconds to
display the current PIU rate.
Message Type: Information.

KMQxx001E–KOCJ0046

335

KN3CV011

USER COMMANDS UPDATED
Explanation: The user added, changed or deleted a user VTAM command.
System Action: The user commands update successfully.
User Response: None.
Message Type: Confirmation.

KN3CV012

TYPE A “/” NEXT TO THE DESIRED SELECTIONS
Explanation: The action bar Action pulldown panel allows the user to select one
or more selections by entering the / character.
System Action: None.
User Response: Type a / next to the desired selections and press Enter.
Message Type: User input error.

KN3CV013

SELECTION NOT AVAILABLE
Explanation: The menu selection is unavailable due to the current state of the
application.
System Action: None.
User Response: Make another selection.
Message Type: Warning.

KN3CV014

MUST BE Y OR N
Explanation: The input field accepts only Y or N (for Yes or No).
System Action: None.
User Response: Enter Y or N in the field.
Message Type: User input error.

KN3CV015

FIELD VALUE NOT VALID
Explanation: The data entered in this field is not valid.
System Action: None.
User Response: Press F1 for additional help on the field. Enter a valid value.
Message Type: User input error.

KN3CV016

COLLECTION INTERVAL TIMEOUT; DATA REINITIALIZED
Explanation: The interval between data requests cannot exceed 5 minutes.
System Action: A new collection interval is initiated, and all current values are
reset to zero.
User Response: None.
Message Type: Information.

KN3CV017

INTERNAL MVS COUNTER WRAPPED; DATA REINITIALIZED
Explanation: A reset condition has been detected for an MVS internal counter.
System Action: A new collection interval is initiated, and all current values are
reset to zero.
User Response: None.
Message Type: Information.

336

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV018

WRAP DETECTED IN SIO COUNTER; DATA REINITIALIZED
Explanation: A reset condition has been detected for a VTAM SIO counter.
System Action: A new collection interval is initiated, and all current values are
reset to zero.
User Response: None.
Message Type: Information.

KN3CV019

WRAP DETECTED IN SYSSIO COUNTER; DATA REINITIALIZED
Explanation: A reset condition has been detected for the MVS SIO counter.
System Action: A new collection interval is initiated, and all current values are
reset to zero.
User Response: None.
Message Type: Information.

KN3CV020

WRAP DETECTED IN PAGING COUNTER; DATA REINITIALIZED
Explanation: A reset condition has been detected for the MVS paging counter.
System Action: A new collection interval is initiated, and all current values are
reset to zero.
User Response: None.
Message Type: Information.

KN3CV021

AUTHORIZATION REQUIRED
Explanation: The user tried to perform a function that requires authority.
System Action: None.
User Response: Contact the system administrator to have your user authorities
updated. When your user authorities are updated by the administrator, log off
and logon, and retry the operation.
Message Type: Security.

KN3CV022

COMMAND REQUIRES ADDITIONAL OPERAND
Explanation: A command that requires one or more operands was entered on
the command line.
System Action: None.
User Response: Place the cursor on the command line and enter Help
followed by the command attempted. A help pop-up appears describing the
command. Re-enter the command with the appropriate operands.
Message Type: User input error.

KN3CV023

VARIABLE NAMED varname CONTAINS contents_of_varname
Explanation: A user with administrator authority issued the SHOW variable
command.
System Action: Displays the current contents of the variable.
User Response: None.
Severity: Information.

KMQxx001E–KOCJ0046

337

KN3CV024

DIALOG ERROR
Explanation: A user with administrator authority issued the DIALOG dlgname
command, but the dialog specified does not exist or contains errors and could not
be compiled and executed successfully.
System Action: None.
User Response: Edit and refresh the dialog, then retry the operation.
Message Type: Internal error.

KN3CV025

REQUEST SUCCESSFUL
Explanation: A user entered a command on the command line.
System Action: The command executes successfully.
User Response: None.
Message Type: Confirmation.

KN3CV026

INVALID COMMAND
Explanation: A user entered an invalid command on the command line.
System Action: None.
User Response: Place the cursor on the command line and press F1 to view
the help panel that lists valid commands.
Message Type: User input error.

KN3CV027

function_key KEY IS NOT ACTIVE
Explanation: A function key was pressed that is not supported on the current
panel. The available function keys are listed in the function key area at the bottom
of each panel.
System Action: None.
User Response: Use a valid function key.
Message Type: User input error.

KN3CV028

INVALID SELECTION
Explanation: A selection character, an action code, or a mnemonic was entered
which is not listed on the menu.
System Action: None.
User Response: Enter one of the listed choices.
Message Type: User input error.

KN3CV029

HELP PANEL help_dialog MISSING OR SYNTAX ERROR
Explanation: The user has requested a help panel that is either missing or
contains errors preventing it from displaying.
System Action: None.
User Response: Gather any logs or dumps produced and report the missing
panels to Candle Support Services.
Message Type: Information.

338

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV030

SELECT THE “ACTIONS” PULL-DOWN MENU
Explanation: One or more / selection characters have been entered, but no
actions have been selected from the Actions pulldown menu.
System Action: None.
User Response: Select the Actions pulldown from the action bar, then select
the desired actions from the pulldown.
Message Type: User input error.

KN3CV031

NOTEPAD UPDATED
Explanation: The user added, changed or deleted personal notes using the
command line NOTE command.
System Action: The user notepad updates successfully.
User Response: None.
Message Type: Confirmation.

KN3CV032

NOTEPAD CLEARED
Explanation: The user requested a notepad to be cleared while using the
command line NOTE command.
System Action: The user notepad clears successfully.
User Response: None.
Message Type: Confirmation.

KN3CV033

THRESHOLD CRITERIA UPDATED
Explanation: The user entered exception thresholds and pressed Enter.
System Action: Thresholds are successfully updated and become effective
within a few minutes.
User Response: None.
Message Type: Confirmation.

KN3CV034

RESOURCE(S) ADDED
Explanation: A response time, terminal, or group was added.
System Action: The response time, terminal, or group is added to ETE
response time monitoring.
User Response: None.
Message Type: Confirmation.

KN3CV035

FIELD IS REQUIRED
Explanation: The input field cannot contain blanks.
System Action: None.
User Response: Enter the appropriate data.
Message Type: User input error.

KN3CV036

FIRST CHARACTER MUST BE ALPHA
Explanation: The first character of the input field must begin with an alphabetic
character.
System Action: None.
User Response: Enter the appropriate data.
Message Type: User input error.

KMQxx001E–KOCJ0046

339

KN3CV037

GLOBAL OPTIONS UPDATED
Explanation: A user with administrator authority pressed Enter while viewing
the Global Options panel.
System Action: The Global options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV038

INVALID NUMERIC RANGE
Explanation: The input field requires a number within a specified range.
System Action: None.
User Response: Enter a number within the valid range.
Message Type: User input error.

KN3CV039

THRESHOLD UPDATE FAILED
Explanation: An internal error was detected while attempting to change
exception thresholds.
System Action: None.
User Response: Retry the operation. If the problem persists, gather any logs or
dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV040

GLOBAL OPTIONS UPDATE FAILED
Explanation: An internal error was detected while attempting to update the
Global Options.
System Action: None.
User Response: Retry the operation. If the problem persists, gather any logs or
dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV041

VR NUMBER INVALID
Explanation: An invalid virtual route number was specified.
System Action: None.
User Response: Specify a valid VR number.
Message Type: User input error.

KN3CV042

TP NUMBER INVALID
Explanation: An invalid TP number was specified.
System Action: None.
User Response: Specify a valid TP number.
Message Type: User input error.

340

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV043

ETE INTERFACE DISABLED
Explanation: The ETE response time monitor component is currently disabled.
This is the initial default when the product is installed. The ETE feature must be
specifically enabled after first verifying that system incompatibilities do not exist.
System Action: All ETE response time monitor functions are disabled.
User Response: Refer to the OMEGAMON II for VTAM instructions shipped
with the product, the OMEGAMON II for VTAM CCUST., and the End-to-End
Response Time Feature Reference Manual for information about installing and
activating the ETE response time component.
Message Type: Installation error.

KN3CV044

THE OPERAND FOR THE AUTOREFRESH COMMAND MUST BE “ON”,
“OFF”, OR A NUMERIC VALUE FROM 10-3600 SECONDS
Explanation: The AUTOREFRESH command was entered on the command
line without specifying a valid operand.
System Action: None.
User Response: Enter the AUTOREFRESH command in one of the following
formats:
AUTO ON
AUTO OFF
AUTO nnnn

where nnnn is 10 to 3600 seconds.
Message Type: User input error.
KN3CV045

MUST BE IN THE RANGE OF 15—360 MINUTES
Explanation: An invalid value was specified for the recording interval on the
Global Options panel.
System Action: None.
User Response: Specify a number within the valid range (15—360 minutes).
Message Type: User input error.

KN3CV046

THE SAS SOURCE LIBRARY SPECIFIED CANNOT BE LOCATED. THE
DATASET MAY HAVE BEEN DELETED, RENAMED OR UNCATALOGED.
Explanation: The SAS source library name specified on the historical graph
options panel cannot be located.
System Action: None.
User Response: Verify the SAS macro library name specified is valid.
Message Type: User input error.

KMQxx001E–KOCJ0046

341

KN3CV047

THE SAS CLIST WAS NOT ENTERED IN THE CORRECT FORMAT.
PLEASE USE THE FOLLOWING FORMAT:
CANDLE.ON.V500.SASCNTL(KN3CLST6)
Explanation: The SAS clist and member name specified on the historical graphs
options panel was entered in the wrong format.
System Action: None.
User Response: Enter the SAS clist name and member name in the following
format:
filename(membername)

Message Type:

User input error.

KN3CV048

THE SAS CLIST DATASET NAME SPECIFIED CANNOT BE LOCATED.
THE DATASET MAY HAVE BEEN DELETED, RENAMED OR
UNCATALOGED.
Explanation: The SAS CLIST dataset name specified on the historical graph
options panel cannot be located.
System Action: None.
User Response: Verify that the SAS CLIST library name specified is valid and
that the library name is cataloged.
Message Type: User input error.

KN3CV049

THE SAS CLIST MEMBER NAME SPECIFIED CANNOT BE LOCATED.
THE MEMBER MAY HAVE BEEN DELETED OR RENAMED.
Explanation: The SAS CLIST member name specified on the historical graphs
options panel cannot be located.
System Action: None.
User Response: Verify that the specified member exists.
Message Type: User input error.

KN3CV050

THE USAGE SELECTION IS ONLY VALID FOR THE IO00 AND CRPL
BUFFER POOLS
Explanation: The user requested the U (usage) action while accessing a buffer
pool panel. The U action is only valid for the IO00 and the CRPL buffer pools.
System Action: None.
User Response: Use the U action only for IO00 and CRPL buffer pools.
Message Type: User input error.

KN3CV051

ACTION IS ONLY VALID ON A SUBAREA
Explanation: The user entered an L (list) action code next to a virtual route
number while working with the Virtual Route Monitor List. The L action code is
only valid next to a subarea.
System Action: None.
User Response: Do not enter the L action code next to a VR.
Message Type: User input error.

342

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV052

MONITORING STARTED
Explanation: The user requested monitoring of a subarea and/or VRs while
working with the Virtual Route Monitor List.
System Action: The specified subarea/VRs are monitored.
User Response: None.
Message Type: Confirmation.

KN3CV053

MONITORING STOPPED
Explanation: The user requested to stop monitoring a subarea and/or VRs while
working with the Virtual Route Monitor List.
System Action: The specified subarea/VRs are not monitored.
User Response: None.
Message Type: Confirmation.

KN3CV054

MONITORING THRESHOLDS CHANGED
Explanation: The user requested monitoring of a subarea and/or VRs and
specified exception thresholds values while working with the Virtual Route
Monitor List.
System Action: The specified subarea/VR exception thresholds are changed.
User Response: None.
Message Type: Confirmation.

KN3CV055

MONITORING THRESHOLDS DELETED
Explanation: The user entered a D action code next to a subarea/VR that
appears undefined while working with the Virtual Route Monitor List.
System Action: The subarea/VR is removed from the list.
User Response: None.
Message Type: Confirmation.

KN3CV056

SUBAREA/VIRTUAL ROUTE UNDEFINED
Explanation: The user tried to start monitoring a subarea/VR that is no longer
defined to VTAM while using the Virtual Route Monitor List.
System Action: None.
User Response: Check with your system network configuration staff. It is likely
that VTAM tables were reconfigured, making certain subarea/VRs invalid. Use the
D action code to delete the definitions for undefined subareas/VRs.
Message Type: User input error.

KN3CV057

ONLY ALLOWED TO DELETE UNDEFINED ITEMS
Explanation: The user tried to enter the D action code next to a subarea/VR
while using the Virtual Route Monitor List.
System Action: None.
User Response: The D action code is only valid next to UNDEFINED
subarea/VRs.
Message Type: User input error.

KMQxx001E–KOCJ0046

343

KN3CV058

MONITOR OPTIONS UPDATE ERROR
Explanation: An internal error was detected while attempting to update the
Virtual Route Monitor List.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the error persists, gather any logs or
dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV059

MONITOR OPTIONS UPDATED
Explanation: The user pressed Enter while viewing Monitor Options for buffer
pools, CTC, LOCALS, NCP, response time or virtual routes.
System Action: The specified monitoring options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV060

TERMINAL OPTIONS UPDATED
Explanation: The user pressed Enter while viewing the Terminal Options panel.
System Action: The terminal options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV061

AUTOREFRESH OPTIONS UPDATED
Explanation: The user pressed Enter when viewing the Autorefresh Options
panel.
System Action: The autorefresh options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV062

STATUS BAR OPTIONS UPDATED
Explanation: The user pressed Enter when viewing the Status Bar Options
panel.
System Action: The status bar options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV063

NETWORK MANAGER OPTIONS UPDATED
Explanation: The user pressed Enter when viewing the Network Manager
Options panel.
System Action: The network manager options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV064

HISTORICAL GRAPH OPTIONS UPDATED
Explanation: The user pressed Enter when viewing the historical graph options
panel.
System Action: The historical graph options are updated.
User Response: None.
Message Type: Confirmation.

344

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV065

SMF DEFINITION ADDED
Explanation: The user added a response time SMF definition.
System Action: The SMF definition is added.
User Response: None.
Message Type: Confirmation.

KN3CV066

SMF DEFINITION CHANGED
Explanation: The user changed a response time SMF definition.
System Action: The SMF definition is changed.
User Response: None.
Message Type: Confirmation.

KN3CV067

SMF DEFINITION DELETED
Explanation: The user deleted a response time SMF definition.
System Action: The SMF definition is deleted.
User Response: None.
Message Type: Confirmation.

KN3CV068

RESPONSE TIME MUST BE GREATER THEN PREVIOUS RANGE
Explanation: When adding or changing a response time SMF definition, the
values specified in the upper bound range fields conflicted. The range 2 upper
bound must be greater then range 1. Range 3 must be greater then Range 2.
Range 4 must be greater then Range 3.
System Action: None.
User Response: Enter correct values for upper bounds in each range.
Message Type: User input error.

KN3CV069

THIS SMF DEFINITION ALREADY EXISTS
Explanation: When adding a response time SMF definition, the user specified a
terminal or group name that is already defined.
System Action: None.
User Response: The terminal or group name cannot conflict with any other
existing response time SMF definition.
Message Type: User input error.

KN3CV070

USERID ALREADY EXISTS
Explanation: The userid specified when adding a new user authority already
exists.
System Action: None.
User Response: Use the C (change) action or correct the userid and retry.
Message Type: User input error.

KN3CV071

USER AUTHORITY ADDED
Explanation: An administrator added a new user authority.
System Action: The user authorities are updated and take effect the next time
the user logs onto OMEGAMON II.
User Response: None.
Message Type: Confirmation.

KMQxx001E–KOCJ0046

345

KN3CV072

USER AUTHORITY CHANGED
Explanation: An administrator changed an existing user’s.s authorities.
System Action: The user’s authorities are updated and take effect the next
time the user logs onto OMEGAMON II.
User Response: None.
Message Type: Confirmation.

KN3CV073

USER AUTHORITY DELETED
Explanation: An administrator deleted an existing user’s authorities.
System Action: The authorities will be set to the $DEFAULT userid definitions
the next time the deleted user logs on.
User Response: None.
Message Type: Confirmation.

KN3CV074

AT LEAST 1 ADMINISTRATOR IS REQUIRED
Explanation: An administrator attempted to delete the only user with
administrator authority.
System Action: None.
User Response: Transfer administrator authority to another user before
deleting the desired user.
Message Type: Warning.

KN3CV075

NOT ALLOWED TO DELETE THE ONLY ADMINISTRATOR
Explanation: An administrator attempted to delete the only user with
administrator authority.
System Action: None.
User Response: Transfer administrator authority to another user before
deleting the desired user.
Message Type: Warning.

KN3CV078

SAS GRAPH PRINTED
Explanation: The user entered the P action code next to one of the SAS graphs
while using the historical graph component.
System Action: The SAS graph is routed for printing.
User Response: None.
Message Type: Confirmation.

KN3CV079

SAS GRAPHS PRINTED
Explanation: The user entered the P action code next to two or more SAS
graphs while using the historical graph component.
System Action: The SAS graphs are routed for printing.
User Response: None.
Message Type: Confirmation.

346

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV080

NAVIGATION NOT ALLOWED
Explanation: The user attempted to navigate to a panel that is already active in
the stack. As navigation takes place from the Status Display panel, the display
panels are stacked so that as you press F12, you can return up the stack.
System Action: None.
User Response: Choose another selection or press F12 until you return to the
panel you wish to view.
Message Type: Information.

KN3CV081

NEW RACHSRT PARAMETER IS NOT PRIME
Explanation: When using the SRT modeling, a number was entered that is not
prime.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV082

LIGHT PEN IS NOT SUPPORTED
Explanation: The user attempted to use a terminal light pen.
System Action: None.
User Response: Do not use a light pen with OMEGAMON II.
Message Type: User input error.

KN3CV083

TRACE ALREADY ACTIVE OR COMPLETED
Explanation: The user attempted to start a VTAM trace that is either already
started or has already completed.
System Action: None.
User Response: Add and start a new trace.
Message Type: User input error.

KN3CV084

TRACE IS STILL ACTIVE
Explanation: The user attempted to save a VTAM trace that is either active or
wrapping.
System Action: None.
User Response: Traces that are either ended or manually stopped can be
saved.
Message Type: User input error.

KN3CV085

TRACE IS ALREADY SAVED
Explanation: The user attempted to save a trace that has already been saved.
System Action: None.
User Response: None.
Message Type: User input error.

KN3CV086

TRACE WAS NEVER STARTED
Explanation: The user attempted to save a trace that was never started.
System Action: None.
User Response: Start the trace and let it complete before attempting to save it.
Message Type: User input error.

KMQxx001E–KOCJ0046

347

KN3CV087

TRACE IS NOT ACTIVE
Explanation: The user attempted to stop a trace that was never started.
System Action: None.
User Response: The stop action is only valid for active or wrapped traces.
Message Type: User input error.

KN3CV088

NUMBER EXCEEDS SYSTEM MAX OF nnnnnnn
Explanation: The number of PIUs requested exceeds the maximum allowed
which is set by the administrator on the Global Options panel.
System Action: None.
User Response: Specify a number less then or equal to the allowed maximum.
Message Type: User input error.

KN3CV089

CLOSE FAILED FOR SYSOUT DATASET
Explanation: An internal error was detected while attempting to close the screen
print log and route it for printing.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV090

nn SCREEN(S) ROUTED FOR PRINTING
Explanation: The user closed the screen print log.
System Action: The captured screen prints are routed for printing.
User Response: None.
Message Type: Confirmation.

KN3CV091

NO SCREEN PRINTS WERE REQUESTED
Explanation: The user closed the screen print log, but there were no screens
captured.
System Action: None.
User Response: Use the F11 key to capture screens before closing the screen
print log.
Message Type: Information.

KN3CV092

GET FAILED FOR DEFAULT PRINTER OPTIONS
Explanation: An internal error was detected while closing the screen print log.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV093

CREATE FAILED FOR SCREEN PRINT LOG
Explanation: An internal error was detected while closing the screen print log.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

348

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV094

ALLOCATE FAILED FOR SYSOUT DATASET
Explanation: An internal error was detected while closing the screen print log.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV095

ADD FAILED FOR SCREEN PRINT LOG
Explanation: An internal error was detected while closing the screen print log.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV096

OPEN FAILED FOR SYSOUT DATASET
Explanation: An internal error was detected while closing the screen print log.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV097

PUT FAILED FOR SYSOUT DATASET
Explanation: An internal error was detected while closing the screen print log.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem continues, gather any logs
or dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV098

VTAM TRACE ROUTED FOR PRINTING
Explanation: The user requested a VTAM trace report.
System Action: The VTAM trace is routed for printing.
User Response: None.
Message Type: Confirmation.

KN3CV099

YOU CAN ONLY PRINT ENDED, STOPPED, OR SAVED TRACES
Explanation: The user requested a VTAM trace report.
System Action: None.
User Response: Make sure the trace is ended, stopped, or saved before
attempting to print.
Message Type: User input error.

KN3CV100

THERE IS NO TRACE DATA TO PRINT
Explanation: The user requested a VTAM trace report on a trace that did not
capture any PIUs.
System Action: None.
User Response: Rerun the trace, then retry the print operation.
Message Type: User input error.

KMQxx001E–KOCJ0046

349

KN3CV101

PRINTER OPTIONS UPDATED
Explanation: The user pressed Enter while viewing the Printer \Options panel.
System Action: The printer options are updated.
User Response: None.
Message Type: Confirmation.

KN3CV102

ERROR, SEE VIEWLOG
Explanation: An internal error was detected while OMEGAMON II was
attempting to refresh the Status Display panel.
System Action: OMEGAMON II detected an unexpected error.
User Response: If the message persists, gather any logs or dumps produced
and contact Candle Support Services.
Message Type: Internal error.

KN3CV103

TRACE ABENDED, DATA STILL GOOD
Explanation: An internal error was detected while a VTAM trace was in
progress.
System Action: A dump is generated.
User Response: Gather any logs or dumps produced and contact Candle
Support Services.
Message Type: Internal error.

KN3CV104

LU NOT FOUND
Explanation: The LU specified was not found while attempting to start a VTAM
trace.
System Action: None.
User Response: Enter a valid LU name to trace.
Message Type: User input error.

KN3CV105

ENTER A NUMBER, THEN PRESS F2
Explanation: The user pressed the F2 key before entering a non-zero
RACHSRT parameter while using the SRT modeling feature.
System Action: None.
User Response: Specify a numeric RACHSRT parameter before pressing the
F2 key.
Message Type: User input error.

KN3CV106

THE EXCEPTIONS SELECTION IS NOT VALID FOR THIS COMPONENT
Explanation: Exceptions do not apply to the selected component. Only the
Show Details action applies.
System Action: None.
User Response: Enter the S action code to Show Details of this component.
Message Type: User input error.

350

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV107

ETE STARTED TASK IS NOT AVAILABLE
Explanation: OMEGAMON II has detected that the ETE Response Time feature
is currently not available to collect response time or VTAM trace data.
System Action: None.
User Response: Report the problem to your data center.
Message Type: Internal error.

KN3CV108

VTAM TRACE ERROR (SENSE CODE=sense_code)
Explanation: OMEGAMON II has detected that the ETE Response Time feature
is currently not available to collect response time or VTAM trace data.
System Action: Detailed message written to job log.
User Response: Retry the operation. If the problem persists, gather any logs or
dumps produced and contact Candle Support Services.
Message Type: Internal error.

KN3CV109

THE FOLLOWING ERROR OCCURRED WHEN OMEGAMON ATTEMPTED
TO ACCESS THE SPECIFIED SAS PRINT OPTIONS LIBRARY. [RETURN
CODE=return_code nn | SYSTEM CODE=X‘xxxx’ | USER
CODE=X‘xxxxxxxx’]
Explanation: When OMEGAMON II attempted to store the new historical graph
print options in the SAS Print Options Library partitioned dataset, an error was
detected.
System Action: None.
User Response: Research the Return Code, System Code, or User Code
displayed to determine the cause of the error. A possible cause is that
OMEGAMON II has not been given write access by the external security system
(such as CA-ACF2 or RACF).
Message Type: Internal error.

KN3CV110

USE THE R ACTION CODE TO START MONITORING
Explanation: The user attempted to change monitoring for a subarea or virtual
route that was not started.
System Action: None.
User Response: Use the R action code to start monitoring for a subarea or a
specific virtual route.
Message Type: User input error.

KN3CV111

TREND/EXCEPTION LOG FILE ACCESS ERROR
Explanation: OMEGAMON II was unable to access the Trend/Exception Log
VSAM file.
System Action: None.
User Response: Report the problem to your OMEGAMON II for VTAM
product administrator. The KN3INVSM member in the RKANPAR dataset must
contain the correct name of the Trend/Exception Log VSAM dataset. Browse the
sysout for OMEGAMON II for VTAM. A detailed explanation of the type of error
encountered is listed there.
Message Type: Installation error.

KMQxx001E–KOCJ0046

351

KN3CV112

REQUESTED PIU WAS NOT FOUND
Explanation: A VTAM Trace browse request was issued. The requested PIU was
not found.
System Action: None.
User Response: In most cases, there is nothing wrong. The message indicates
the browse request could not find the specified PIU.
You also receive this message if the browse request is not valid. For example: you
requested an invalid PIU number; you requested a find for a hexadecimal or
character string that does not exist; or you requested the search string PIU when a
search string was never specified in the trace definition.
Message Type: Warning.

KN3CV115

THE HISTORICAL GRAPH OPTIONS LOCATED ON THE ACTION BAR
OPTIONS PULLDOWN PANEL ARE NOT VALID. PLEASE UPDATE
HISTORICAL GRAPH OPTIONS BEFORE ATTEMPTING TO ACCESS
HISTORICAL GRAPHS.
Explanation: The user attempted to access historical graphs, but the historical
graphs options are not valid.
System Action: None.
User Response: Update the historical graph options from the action bar
options pulldown panel, then retry the operation.
Message Type: Information.

KN3CV116

AN UNEXPECTED ERROR OCCURRED
Explanation: When OMEGAMON II attempted to process a user request, an
unexpected error occurred.
System Action: None.
User Response: First check to see if the Tables Database ran out of space. If
that is not the problem, retry the operation. If the problem persists, look at
OMEGAMON II’s SYSOUT or message log, note the CT/Engine table services
return code, and report the problem to Candle Support Services.
Message Type: Internal error.

KN3CV117

VALID RANGE IS 20—300
Explanation: The sampling interval must be in the range of 20—300 seconds.
System Action: None.
User Response: Specify a value that is not less than 20 and not greater than
300.
Message Type: User input error.

KN3CV118

ENTER N, L, S, OR B
Explanation: The only acceptable characters to specify in this field are N
(None), L (Log), S (SMF), or B (Both).
System Action: None.
User Response: Specify an N for no recording, an L for Log File recording, an
S for SMF recording, or a B for both Log File and SMF recording.
Message Type: User input error.

352

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV119

ENTER YES OR NO
Explanation: This input field requires a value of Yes or No.
System Action: None.
User Response: Specify Yes to activate the option or No to deactivate the
option.
Message Type: User input error.

KN3CV120

ENTER C OR W
Explanation: The only acceptable characters in this field are W or C.
System Action: None.
User Response: Specify a W to indicate that the exception should have
warning (yellow) severity, or a C to indicate that the exception should have critical
(red) severity.
Message Type: User input error.

KN3CV121

ENTER A NUMERIC VALUE OR LEAVE BLANK
Explanation: This field requires a numeric value or no value.
System Action: None.
User Response: When you want OMEGAMON II to monitor for this exception,
specify the numeric threshold that must be reached for an exception condition to
be generated. Leave this field blank if you do not want OMEGAMON II to
monitor for this exception.
Message Type: User input error.

KN3CV122

CRITICAL MUST BE GREATER THAN WARNING
Explanation: The critical threshold specified must have a value that exceeds the
warning value specified.
System Action: None.
User Response: Raise the critical threshold and/or lower the warning
threshold.
Message Type: User input error.

KN3CV123

ENTER N, L, OR A
Explanation: The only acceptable characters in this field are N (None), L
(Monitor List), or A (All).
System Action: None.
User Response: Specify an N for no monitoring of virtual routes, an L to
monitor only the VRs in the monitor list, or an A to monitor all VRs.
Message Type: User input error.

KN3CV124

CRITICAL MUST BE LESS THAN WARNING
Explanation: The critical threshold specified must have a value that is less than
the warning value specified.
System Action: None.
User Response: Lower the critical threshold and/or raise the warning
threshold.
Message Type: User input error.

KMQxx001E–KOCJ0046

353

KN3CV125

THE CATEGORIES SELECTION IS ONLY VALID FOR THE IO00 BUFFER
POOL
Explanation: When accessing a buffer pool display, the G (Categories) action
was requested.
System Action: None.
User Response: The G action code is only valid for the IO00 buffer pool.
Choose one of the other action codes listed.
Message Type: User input error.

KN3CV126

THE DATA FOR THE table tablename IS NOT AVAILABLE IN THIS
DOMAIN.
Explanation: The PLU is a cross-domain resource (CDRSC) and the COSTAB
resides in the other domain, or the SLU is a CDRSC and the USSTAB resides in
the other domain. The name of the COSTAB displays, but the name of the
USSTAB is unavailable. The requested table is available in the other domain.
System Action: None.
User Response: Press Enter to continue. To view the table, log onto the
OMEGAMON II that monitors the other domain.
Message Type: Information.

KN3CV127

VALID RANGE IS 0–100
Explanation: The entry field requires a percentage and the value is out of range.
System Action: None.
User Response: Specify a number that is not less than zero and is not greater
than 100.
Message Type: User input error.

KN3CV128

VALID RANGE IS 15–360
Explanation: The trend recording interval must be in the range of 15–360
minutes.
System Action: None.
User Response: Specify a number that is not less than 15 and is not greater
than 360.
Message Type: User input error.

KN3CV129

VALID RANGE IS 1–120
Explanation: The number of hours of trend or exception records to display must
be 1–120.
System Action: None.
User Response: Specify a number that is not less than 1 and is not greater than
120.
Message Type: User input error.

354

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV130

VALID RANGE IS 128–255
Explanation: The SMF record number to be generated must be in the range
128–255.
System Action: None.
User Response: Specify a number that is not less than 128 and is not greater
than 255.
Message Type: User input error.

KN3CV131

VALID RANGE IS 1–500
Explanation: The maximum number of PIUs to be retained for one trace must
be in the range 1–500.
System Action: None.
User Response: Specify a number that is not less than 1 and is not greater than
500.
Message Type: User input error.

KN3CV132

ALPHANUMERIC FIELD REQUIRED
Explanation: The field must consist only of alphabetic and numeric characters,
and the first character must be alphabetic.
System Action: None.
User Response: Enter only alphabetic and numeric characters (A–Z, 0–9) and
start with an alphabetic character.
Message Type: User input error.

KN3CV133

VIEW COMMAND INVALID WHEN DISPLAYING DIRECTORY
Explanation: Since the VIEW command displays the Snapshot Directory, it is
invalid to enter the VIEW command while the Snapshot Directory is displayed.
System Action: None.
User Response: The Snapshot Directory displays all the snapshots you have
saved. Enter action code S (Show Snapshot) next to the snapshot you want to
view.
Message Type: User input error.

KN3CV134

ENTER N OR S
Explanation: The only acceptable characters to specify in this field are N or S.
System Action: None.
User Response: Specify an N for no response time trend recording or an S for
response time trend recording to SMF.
Message Type: User input error.

KN3CV135

VALID RANGE IS 1–99
Explanation: The response time definite response frequency must be in the
range 1–99.
System Action: None.
User Response: Specify a number that is not less than 1 and is not greater than
99.
Message Type: User input error.

KMQxx001E–KOCJ0046

355

KN3CV136

VALID RANGE IS 10–3600
Explanation: The automatic screen refresh interval must be in the range of 10–
3600 seconds.
System Action: None.
User Response: Specify a number that is not less than 10 and is not greater
than 3600.
Message Type: User input error.

KN3CV137

THE CONTROL BLOCK CANNOT BE ACCESSED FOR ONE OF THE
FOLLOWING REASONS:
1. THE CONTROL BLOCK IS NO LONGER VALID.
2. AN ATTEMPT TO ACCESS THE ADDRESS SPACE FAILED
Explanation: The control block is not available for display because the control
block address is no longer valid, or an attempt to swap in the address space failed.
System Action: None.
User Response: Press Enter to continue.
Message Type: Information.

KN3CV138

THE ADDRESS SPACE HAS TERMINATED
Explanation: The control block data is not available for display because the
address space is gone.
System Action: None.
User Response: Press Enter to continue.
Message Type: Information.

KN3CV139

THE ADDRESS SPACE IS BEING SWAPPED IN, TRY AGAIN LATER
Explanation: The control block data is not available for display because the
address space is being swapped in.
System Action: None.
User Response: Press Enter to continue. Try to access the data at a later time,
after the address space has been swapped in.
Message Type: Information.

KN3CV140

THERE WAS NO RPL CONTROL BLOCK FOUND FOR THIS SESSION
Explanation: Due to the transient nature of control blocks, an RPL with a CID
matching this session's CID could not be found. The data cannot be displayed.
System Action: None.
User Response: Press Enter to continue.
Message Type: Information.

KN3CV141

UNABLE TO DISPLAY THE CONTROL BLOCK DATA. CHECK THE
MESSAGE LOG FOR MORE INFORMATION
Explanation: An error occurred while trying to display the requested data
System Action: None.
User Response: Press Enter to continue. Note the OMEGAMON II collector's
return and sense codes, on the message log or OMEGAMON II's SYSOUT, and
report them to Candle Support Services.
Message Type: Internal error.

356

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV142

UNABLE TO FIND THE ACTUAL RPL. THE CRPL IS DISPLAYED
INSTEAD. MOST OF THE DATA FROM THE ORIGINAL RPL CAN BE
FOUND IN THE CRPL
Explanation: The actual RPL was not available. The CRPL is shown instead.
The CRPL contains most of the data from the original RPL.
System Action: None.
User Response: Press Enter to continue.
Message Type: Information.

KN3CV143

THE LOGMODE ENTRY FOR MODETAB tablename CANNOT BE
DETERMINED AT THIS TIME.
Explanation: The LOGMODE entry was not found in the MODETAB. The
LOGMODE entry was in an undetermined state at the time the request was made.
It is possible that the MODETAB was being dynamically refreshed or the session
was in a transitional state such as initiation or termination.
System Action: None.
User Response: Press Enter to continue. Try again later; a change in state may
synchronize the names.
Message Type: Information.

KN3CV144

THE DATA FOR THE LOGMODE ENTRY entryname IS NOT AVAILABLE
IN THIS DOMAIN.
Explanation: The PLU is a cross-domain resource (CDRSC) and the
LOGMODE entry resides in the other domain. The name of the LOGMODE entry
displays. The MODETAB is available in the domain in which the PLU resides.
System Action: None.
User Response: Press Enter to continue. To view the table, log onto the
OMEGAMON II that monitors the other domain where the PLU resides.
Message Type: Information.

KN3CV145

TUNING STATISTICS ARE NOT ACTIVE
Explanation: Tuning statistics are not currently active. If the VTAM command F
procname, NOTNSTAT was issued, VTAM stops recording tuning statistics,
OMEGAMON II for VTAM stops generating trend records for CTC, NCP, and
local devices and sets the three TNSTATS status lights on the Mains Status panel
to turquoise with text displaying NOTNSTAT.
System Action: None.
User Response: You can reactivate TNSTATS by entering the appropriate
VTAM command: F procname,TNSTATS
Message Type: Information.

KN3CV147

TRACE ALREADY EXISTS
Explanation: The trace ID requested is already in use.
System Action: None.
User Response: Specify a unique trace ID, or if you want to restart the existing
trace, use the R (Restart) action code.
Message Type: Information.

KMQxx001E–KOCJ0046

357

KN3CV148

TRACE NOT STARTED
Explanation: The selected trace was not started.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV149

NOT VALID FOR GROUPS. USE LIST (L) AND SELECT AN INDIVIDUAL
RESOURCE.
Explanation: User requested resource analysis for a group item in response time
analysis.
System Action: None.
User Response: Select only listed terminals or applids.
Message Type: User input error.

KN3CV150

RESOURCE NOT FOUND
Explanation: User requested resource analysis for a resource that could not be
found. When adding a response time definition for a line, user specified a
non-SDLC line. Only a SDLC line can be specified as a response time monitoring
line group.
System Action: None.
User Response: Verify resource name or network address through the VTAM
applications feature of OMEGAMON II for VTAM. When adding a response time
line group definition, specify an SDLC line in the Group Name field.
Message Type: User input error.

KN3CV151

RESOURCE NOT ACTIVE
Explanation: User requested resource analysis for a resource that was not
active.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV152

INVALID RESOURCE TYPE
Explanation: User requested resource analysis for an invalid resource type; not
an applid, terminal, or CDRSC.
System Action: None.
User Response: Enter a valid resource name.
Message Type: User input error.

KN3CV153

INVALID PARAMETER LENGTH
Explanation: The parameter input by the user was too long for the type of field
required.
System Action: None.
User Response: Reenter the parameter.
Message Type: User input error.

358

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV154

SPECIFY EITHER RESOURCE NAME OR NETWORK ADDRESS
Explanation: User entered both a resource name and a network address.
System Action: None.
User Response: Specify either a resource name or network address, not both.
Message Type: User input error.

KN3CV155

RPL DATA IS ONLY AVAILABLE FOR APPLID RESOURCES
Explanation: User requested a display of RPL data from terminal or CDRSC
type resources. RPL data is available only from applid type resources.
System Action: None.
User Response: None.
Message Type: User input error.

KN3CV156

RESOURCE HAS NO SESSIONS
Explanation: User has requested session information for a resource that
currently is not in session.
System Action: None.
Message Type: None.
Message Type: Information.

KN3CV157

THE VTAM REPLACEABLE CONSTANTS MODULE ISTRACON IS NOT
USED BY THIS RELEASE OF VTAM
Explanation: The VTAM constants function was selected, however the VTAM
replaceable constants module ISTRACON is not used by this release of VTAM.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV158

THE FOLLOWING ERROR OCCURRED WHEN OMEGAMON ATTEMPTED
TO VERIFY THE SPECIFIED SAS CLIST LIBRARY. RETURN
CODE=return_code | SYSTEM CODE=X‘xxxx’ | USER CODE=X‘xxxxxxxx’
Explanation: An unexpected error was encountered when OMEGAMON II for
VTAM was verifying the user-specified SAS CLIST library.
System Action: None.
User Response: Research the error return code displayed to determine the
cause of the problem. See the IBM TSO System Programming Command
Reference manual for more information.
Message Type: User error.

KN3CV159

VALUE MUST BE LESS THAN 2097148
Explanation: The data entered in this field exceeded 2097148.
System Action: None.
User Response: Press F1 for additional help on the field, and enter an
acceptable value.
Message Type: User input error.

KMQxx001E–KOCJ0046

359

KN3CV160

STORAGE REQUIRED FOR MODELLING NOT AVAILABLE. ENSURE
THAT LIMIT(23,X) IS CODED FOR THE STARTUP PARAMETER.
Explanation: Storage required for SRT modeling is not available from the
existing storage pool. This storage requirement is temporary and equals 4 times
the new RACHSRT parameter in panel KN3DENM, plus 8. Typically, this
problem is due to the storage request exceeding the largest storage block allowed
for this job.
System Action: None.
User Response: Ensure that LIMIT(23,X) is coded for the start-up parameter in
member KN3SYSIN of the RKANPAR dataset. If the problem persists, you may
need to increase your MAXIMUM(,X) definition. Use command STORAGE D to
display and analyze your storage allocations.
Message Type: Probable user error.

KN3CV161

ENTER N, L, P, OR U
Explanation: The only acceptable characters to specify in this field are N
(NCPs), L (lines), P (PUs), and U (LUs).
System Action: None.
User Response: Enter a valid selection.
Message Type: User input error.

KN3CV162

ENTER M OR C
Explanation: The only acceptable characters to specify in this field are M
(monitor) and C (collect).
System Action: None.
User Response: Enter M or C in the field.
Message Type: User input error.

KN3CV163

ENTER S, M, H
Explanation: The only acceptable characters to specify in this field are S
(seconds), M (minutes), and H (hours).
System Action: None.
User Response: Enter an S, M, or H in the field.
Message Type: User input error.

KN3CV164

INVALID LINE TYPE; PRESS F4 FOR PROMPT.
Explanation: The input field accepts only the following line type defaults SDLC,
TRPL, TRLL, and NONE.
System Action: None.
User Response: Enter a valid line type, or press F4 for a prompt list.
Message Type: User input error.

KN3CV165

ENTER L, P, OR U
Explanation: The only acceptable characters to specify in this field are L (lines),
P (PUs), and U (LUs).
System Action: None.
User Response: Enter L, P, or U in the field.
Message Type: User input error.

360

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV166

ENTER P OR U
Explanation: The only acceptable characters to specify in this field are P (PUs)
and U (LUs).
System Action: None.
User Response: Enter P or U in the field.
Message Type: User input error.

KN3CV167

RESOURCES MUST BE THE SAME TYPE
Explanation: Two different resource types were selected for a mark-and-copy
operation. Only matching resources can be copied.
System Action: None.
User Response: Select only matching resource types for Mark and Copy
actions.
Message Type: User input error.

KN3CV168

SELECT ONLY ONE RESOURCE WITH MARK
Explanation: More than one resource was selected with the Mark action code.
Only one Mark and one Copy action code are allowed per operation.
System Action: None.
User Response: Select one resource to be marked as the source and one
matching type resource as the copy target.
Message Type: User input error.

KN3CV169

SELECT ONLY ONE RESOURCE WITH COPY
Explanation: More than one resource was selected with the Copy action code.
Only one Mark and one Copy action code are allowed per operation.
System Action: None.
User Response: Select one resource to be marked as the source, and one
matching type resource as the copy target.
Message Type: User input error.

KN3CV170

SELECT A SOURCE RESOURCE WITH MARK
Explanation: A Copy action was selected without a corresponding Mark action
code.
System Action: None.
User Response: Use the Mark action code to select the source resource to be
copied.
Message Type: User input error.

KN3CV171

SELECT A TARGET RESOURCE WITH COPY
Explanation: A Mark action was selected without a corresponding Copy action
code.
System Action: None.
User Response: Use the Copy action code to select the target resource to be
copied to.
Message Type: User input error.

KMQxx001E–KOCJ0046

361

KN3CV172

RESOURCE HAS NO SUBORDINATE RESOURCES
Explanation: A List action was selected for a resource that has no subordinate
resources.
System Action: None.
User Response: Check to be sure the action was entered next to the correct
resource.
Message Type: Information.

KN3CV173

RESOURCE HAS ALREADY BEEN STARTED
Explanation: A Start action was requested for a resource that was already
started.
System Action: None.
User Response: Check to be sure the action was entered next to the correct
resource.
Message Type: Information.

KN3CV174

RESOURCE HAS NPACOLL=NO AND CANNOT BE MONITORED
Explanation: A Start action was requested for a resource that has the
NPACOLL parameter set to NO in the NCP generation source. Data cannot be
collected for this resource.
System Action: None.
User Response: Only resources with NPACOLL=YES can be monitored. If
you want to monitor this resource, reset the NPACOLL parameter.
Message Type: Information.

KN3CV175

RESOURCE IS NOT ACTIVE TO VTAM AND CANNOT BE MONITORED
Explanation: A Start action was requested for a resource that is not active in this
system’s VTAM. Inactive resources cannot be monitored.
System Action: None.
User Response: If you want to monitor this resource, activate the resource
under VTAM.
Message Type: Information.

KN3CV176

RESOURCE NOT STARTED OR WAS ALREADY STOPPED
Explanation: A Stop action was requested for a resource that is not active or
was already stopped.
System Action: None.
User Response: Check to be sure the action was entered next to the correct
resource.
Message Type: User input error.

KN3CV177

DELETE VALID ONLY FOR NCP TYPE RESOURCES
Explanation: A Delete action was requested on a resource other than an NCP.
Delete is valid only for NCPs.
System Action: None.
User Response: Check to be sure the action was entered next to the resource.
Message Type: User input error.

362

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV178

NO EXCEPTIONS ARE GENERATED FOR THIS FIELD
Explanation: Exceptions were requested for a data type that has no threshold
settings and cannot be monitored.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV179

MONITOR OPTIONS UPDATE ERROR
Explanation: While updating the NCP performance monitor options, an
internal error was detected.
System Action: None.
User Response: Retry the operation. If the error persists, contact Candle
Support Services.
Message Type: Internal error.

KN3CV180

MONITOR OPTIONS WILL BE UPDATED WITH THE CURRENT SITE
DEFAULTS
Explanation: User has requested a reset of the NCP monitor options settings
from a Change pop-up. Options are set to current site default settings when the
user exits with an update (with the Enter key).
System Action: None.
User Response: Use the Enter key to update the monitor options, or use F12
to cancel the update.
Message Type: Information.

KN3CV181

DELETE NOT ALLOWED FOR AN ACTIVE RESOURCE
Explanation: User has requested a delete from the Site Monitor List for an NCP
resource whose status is not ‘NA’. Available or active resources cannot be deleted.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV182

RESOURCE NOT FOUND
Explanation: User has requested a resource that is not valid or does not exist.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV183

RESOURCE ALREADY USING SITE DEFAULT OPTIONS
Explanation: User has requested a reset for a resource that is already using site
default monitoring options. Resources with monitor options of Site (displayed on
the NCP Site Monitor List) are using the site default monitor options.
System Action: None.
User Response: None.
Message Type: User input error.

KMQxx001E–KOCJ0046

363

KN3CV184

RESOURCE MUST BE AN LU OR TERMINAL
Explanation: User has requested resource analysis for a resource other than an
LU or terminal. Resource analysis returns session level data for partners in
session. SDLC and BSC lines or PUs and clusters are not valid selections for
resource analysis.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV185

NO SUBORDINATE RESOURCES ARE BEING MONITORED
Explanation: A List action was selected for a resource that has no subordinate
resources or whose subordinate resources are not being monitored.
System Action: None.
User Response: To start monitoring a resource, start the resource from the Site
Monitor List (under NCP performance monitor options) with the R action code
(Start). The Monitor or Collect option for the resource must be set to Monitor.
Administrator authority is required.
Message Type: Information.

KN3CV186

RESOURCE(S) ALREADY ADDED
Explanation: Response time terminal or group with the same name already
added.
System Action: None.
User Response: Use a unique name when adding a response time terminal or
group.
Message Type: Information.

KN3CV187

RESOURCE MUST BE STOPPED BEFORE MONITORING OPTIONS CAN
BE CHANGED
Explanation: A change action code has been entered for an NCP resource that
is currently being monitored. The resource is in a started, or a pending start,
mode. Monitoring options can be changed only when a resource is stopped.
System Action: None.
User Response: Enter a P action code (Stop) to stop monitoring the resource,
and a C action code (Change) to change monitoring options. Then enter an R
action code (Start) to resume monitoring.
Message Type: Information.

KN3CV188

NCP PERFORMANCE IS VALID ONLY FOR LU TYPES NCP, LINE, OR PU
Explanation: NCP Performance action cannot determine the type of LU when
collection is for APPLS or TERMINALs.
System Action: None.
User Response: Enter NCP Performance (N) action on a LU collected from an
NCP, Line, or PU.
Message Type: User input error.

364

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV189

GROUP DESCRIPTION ALREADY EXISTS
Explanation: Group description is already assigned to a group being monitored
by ETE.
System Action: None.
User Response: Choose a different group description.
Message Type: User input error.

KN3CV190

USER REQUESTED TO STOP MONITORING resource_name.
SUBORDINATE RESOURCES MUST BE STOPPED BEFORE THIS
RESOURCE CAN BE STOPPED.
Explanation: A Stop action was issued for a resource that had subordinates that
were being monitored. The high level resource cannot be stopped until the lower
level resources are stopped.
System Action: None.
User Response: List the lower level resources and issue Stop actions for each
one, beginning with the lowest level resource, LUs, and then PUs and lines.
Message Type: User input error.

KN3CV191

NCP RESOURCE IS NOT BEING MONITORED
Explanation: NCP resource has not been started in the NCP Site Monitor List.
System Action: None.
User Response: Under NCP performance monitor options, start the resource
from the Site Monitor List with the R action code (Start).
Message Type: User input error.

KN3CV192

NO UPDATE AUTHORIZATION, VIEW ONLY
Explanation: The user has no administrative authority to update the monitoring
options.
System Action: Monitoring options displays are view only.
User Response: If update authorization is required, have a product
administrator authorize the user ID.
Message Type: Information.

KN3CV193

RECORDING INTERVAL MUST BE GREATER THAN OR EQUAL TO THE
NCP COLLECTION INTERVAL OF nnnnnnnn SECONDS
Explanation: In the Global Monitoring Options panel, a value was specified for
the trend recording interval that was less than the current value of the NCP
collection interval. This is only acceptable if NCP trend recording is turned off.
System Action: None.
User Response: Set the trend recording interval greater than or equal to the
NCP collection interval, or use CICAT reconfiguration to set the NCP collection
interval to a value less than or equal to the trend recording interval, or turn NCP
trend recording off.
Message Type: User input error.

KMQxx001E–KOCJ0046

365

KN3CV198

THE TREND RECORDING INTERVAL (interval) IS LESS THAN THE NCP
COLLECTION INTERVAL (interval). TREND RECORDING FOR NCP
RESOURCES HAS BEEN DISABLED.
Explanation: NCP trend recording cannot occur if the global trend recording
interval is less than the NCP collection interval. At OMEGAMON II for VTAM
initialization, NCP trend recording is disabled if the NCP collection interval is
larger than the global trend recording interval
System Action: Trend recording is turned off for NCP resources.
User Response: Use the Global Monitoring Options panel to increase the trend
recording interval to a value greater than or equal to the NCP collection interval
and then re-enable the NCP trend recording option, or use CICAT
reconfiguration to decrease the NCP collection interval to a value less than or
equal to the trend recording interval. Decreasing the NCP collection interval
requires a restart of OMEGAMON II for VTAM.
Message Type: User specification error.

KN3CV199

NCP TREND RECORDING DISABLED AT STARTUP
Explanation: The trend recording interval must be greater than or equal to the
NCP collection interval. At initialization, if the collection interval exceeds the
global trend recording interval, NCP trend recording is turned off.
System Action: NCP trend recording is disabled.
User Response: If you want NCP trend recording, change the NCP trend
recording interval or the NCP collection interval so that the trend recording
interval is greater than or equal to the NCP collection interval. Then turn NCP
trend recording on.
Message Type: User specification error.

KN3CV205

ENTER M OR H
Explanation: The only acceptable characters to specify in this field are M
(minutes) and H (hours).
System Action: Field not updated.
User Response: Enter an M or H in the field.
Message Type: User input error.

KN3CV206

THE NCP TOPOLOGY UPDATE INTERVAL MUST BE GREATER THAN
OR EQUAL TO THE NCP COLLECTION INTERVAL OF nnn SECONDS
Explanation: While entering NCP default monitoring options, a value for NCP
topology update interval was specified that was less than the NCP collection
interval specified during CICAT customizaiton of OMEGAMON II for VTAM.
System Action: NCP default monitoring options are not updated.
User Response: Set the NCP topology update interval greater than or equal to
the NCP collection interval.
Message Type: User input error.

366

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV207

INVALID SCROLL AMOUNT
Explanation: While attempting to scroll forward, an invalid scroll amount was
entered in the line input field.
System Action: None.
User Response: Choose a number of lines to scroll that falls within the length
of the table displayed.
Message Type: User input error.

KN3CV208

Enter V or U
Explanation: The only acceptable character to specify in this field is V for virtual
circuits or U for logical units.
System Action: None.
User Response: Enter V or U in the field.
Message Type: User input error.

KN3CV210

NO LUS ASSOCIATED WITH RESOURCE
Explanation: The response time group for the specified resource did not locate
any LUs associated with the resource to be monitored.
System Action: The group does not appear in the response time display.
User Response: Check the resource name in the Site Monitor List or in the
NCP gen.
Message Type: Warning.

KN3CV211

ADDRESS SPACE NAME ALREADY EXISTS
Explanation: The TCP/IP address space could not be added to the list of
monitored TCP/IP address spaces because the address space name is already in
the list.
System Action: None.
User Response: Scroll through the list of TCP/IP address spaces on the TCP/IP
Status Summary panel to locate the address space.
Message Type: User error.

KN3CV212

CONNECTION ALREADY SPECIFIED
Explanation: The TCP/IP high priority connection could not be added to the
high priority connection list because the connection is already in the list.
System Action: None.
User Response: Scroll through the list of TCP/IP connections on the TCP/IP
Connections panel to locate the connection.
Message Type: User error.

KN3CV213

UPDATE SUCCESSFUL
Explanation: Indicates a successful update.
System Action: None.
User Response: None.
Message Type: Confirmation.

KMQxx001E–KOCJ0046

367

KN3CV214

UPDATE ERROR
Explanation: An error occurred during an update operation.
System Action: None.
User Response: The cursor is positioned at the field that was entered
incorrectly. Verify your input and reenter.
Message Type: User error.

KN3CV215

MUST BE ALPHABETIC
Explanation: An attempt was made to enter non-alphabetic characters into a
field that accepts only alphabetic characters.
System Action: None.
User Response: The cursor is positioned at the field that was entered
incorrectly. Verify your input and reenter.
Message Type: User error.

KN3CV216

BUFFER POOL DATA NOT AVAILABLE
Explanation: Buffer Pool data is available for TCP/IP versions 3.2 and below. A
TCP/IP release of greater than 3.2 was detected.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV217

CONNECTION NUMBER REQUIRED FOR DROP
Explanation: An attempt was made to drop a connection that had no
connection number.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV218

UDP CONNECTIONS CANNOT BE HIGH PRIORITY
Explanation: Addition of a UDP connection to the high-priority list of
monitored connections failed. UDP connections cannot be specified as
high-priority.
System Action: None.
User Response: None.
Message Type: Information.

KN3CV219

ADD OF TCP/IP ADDRESS SPACE FAILED
Explanation: Addition of a TCP/IP address space to the monitored list of
address spaces failed.
System Action: None.
User Response: The most likely cause of this error is an incorrect configuration
dataset name and member specification. Ensure the configuration dataset
information is correct and reenter.
Message Type: User input error.

368

Candle Products Messages Manual (KLVHS–KONCT)

KN3CV221

AT LEAST ONE ENTRY IS REQUIRED
Explanation: User pressed Enter is a data entry dialog that required an entry
and no entry was made.
System Action: None.
User Response: Enter a value in at least one of the data entry fields or press
F12 to cancel out of the dialog.
Message Type: User input error.

KN3CV222

CRITICAL MUST BE LESS THAN WARNING
Explanation: The critical threshold value must be less than the warning value,
when the less than or equal option is chosen.
System Action: None.
User Response: Raise the critical threshold and/or lower the warning
threshold.
Message Type: User input error.

KN3CV223

MUST BE >= OR <=.
Explanation: A logical operator is required for the threshold settings. Either >=
or <= must be specified.
System Action: None.
User Response: Use the F4=Prompt key to select a logical operator.
Message Type: User input error.

KN3CV224

OID NAME IS UNKNOWN
Explanation: The MIB object name specified on the TCP/IP console command
line with the BULKWALK command is not a recognized MIB object name.
System Action: None.
User Response: Names are case-sensitive. Check the spelling and case of the
object name, or use the Command pull-down to select an MIB object from the
MIB Browser menu.
Message Type: User input error.

KN3CV225

OID NUMBER IS UNKNOWN
Explanation: The MIB object ID number specified on the TCP/IP console
command line with the BULKWALK command is not a recognized MIB object
number.
System Action: None.
User Response: Check that the object ID number was specified correctly,
including the ending period, or use the Command pull-down to select an MIB
object from the MIB Browser menu.
Message Type: User input error.

KN3CV226

TCP/IP COMMAND ERROR
Explanation: When attempting to execute a TCP/IP console command, an error
was detected.
System Action: None.
User Response: Ensure that the command format and syntax are correct and
resubmit the command. Otherwise, the command is not supported.
Message Type: User input error.
KMQxx001E–KOCJ0046

369

KN3CV227

command COMMAND FAILED
Explanation: An attempt to execute the indicated command failed.
System Action: None.
User Response: Review all TCP/IP configuration steps relating to TCP/IP
command authorization and security. Ensure that the OMEGAMON address
space has the proper security authorization to perform the indicated command.
Review the RKLVLOG for additional messages relating to the error. If the problem
persists, gather the preceding 30 minutes of RKLVLOG and contact Candle
Customer Support.
Message Type: Possible configuration error.

KN3CV228

HI PRIORITY CONNECTION NOT DEFINED
Explanation: An attempt was made to delete an undefined TCP/IP high-priority
connection.
System Action: None.
User Response: Verify the connection definition in the CT/Engine operator
table manager. Log onto the CT/Engine operator and browse the
OMVTAM.TCPIP.EXCPSHUN.TABLE to determine how the connection was
originally defined. Once the error has been identified, retry the delete request.
Message Type: User input error.

KN3FC000

KN3FCCMD COMMAND PROCESSING COMPLETE
Explanation: The feature control command, KN3FCCMD, completed
processing.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC001

KN3FCCMD COMMAND REQUEST FAILED ROUTINE=routine_name
REASON=reason_code RETURN=return_code
Explanation: An error was detected during feature control command
(KN3FCCMD) processing.
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3FC002

KN3FCCMD COMMAND SYNTAX ERROR COMMAND(command_name)
Explanation: A syntax error was detected while processing feature control
command (KN3FCCMD) arguments.
System Action: The command request fails.
User Response: Enter KN3FCCMD HELP to list supported arguments.
Re-enter the command specifying valid KN3FCCMD arguments.
Message Type: User input error.

370

Candle Products Messages Manual (KLVHS–KONCT)

KN3FC003

KN3AYFCV NOT AVAILABLE. INSTALL OPTION REQUIRED.
Explanation: The KN3AYFCV resource was not found while processing one of
the following feature control command (KN3FCCMD) options:
START
STOP
STATUS

System Action: The command request fails. The feature was not installed.
User Response: Enter a KN3FCCMD INSTALL request specifying the features
requiring installation. Then you can use KN3FCCMD to start, stop, or obtain the
status of a feature. See the appendix in the OMEGAMON II for VTAM
Configuration and Customization Guide for more information about the
KN3FCCMD command.
Message Type: User input error.
KN3FC004

KN3FCCMD INVALID OPTION(option_name) FOR COMMAND
(command_name)
Explanation: An invalid command option was detected while processing feature
control command (KN3FCCMD) arguments.
System Action: The command request fails.
User Response: Enter KN3FCCMD HELP to list supported command options.
Reenter KN3FCCMD specifying valid command options. See the appendix in the
OMEGAMON II for VTAM Configuration and Customization Guide for more
information about the KN3FCCMD command.
Message Type: User input error.

KN3FC005

Explanation: This is a prefix for feature control command (KN3FCCMD) HELP
output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC010

FPON COMPONENT FUNCTIONS INSTALLATION COMPLETE
Explanation: The feature control command (KN3FCCMD) installed
OMEGAMON II for VTAM features (FPON) successfully.
System Action: None
User Response: None.
Message Type: Confirmation.

KN3FC011

FPON COMPONENT FUNCTIONS INSTALLATION FAILED
ROUTINE=KN3AHOF0 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing OMEGAMON II for VTAM features (FPON).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

371

KN3FC012

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS FPON output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC015

FPCT COMPONENT FUNCTIONS INSTALLATION COMPLETE
Explanation: The feature control command (KN3FCCMD) installed FPCT
features successfully.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC016

FPCT COMPONENT FUNCTIONS INSTALLATION FAILED
ROUTINE=KN3AHCF0 REASON=reason_code RETURN= return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing FPCT features.
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3FC017

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS FPCT output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC020

SEVT VTAM ENVIRONMENT INSTALLATION COMPLETE
Explanation: The feature control command (KN3FCCMD) installed VTAM
environment features (SEVT) successfully.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC021

SEVT VTAM ENVIRONMENT INSTALLATION FAILED
ROUTINE=KN3AHEV0 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing VTAM environment features (SEVT).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

372

Candle Products Messages Manual (KLVHS–KONCT)

KN3FC023

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS SEVT output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC024

SEVT VTAM ENVIRONMENT STATUS FAILED ROUTINE=KN3AHEV3
REASON=abend RETURN=abend_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was checking the status of VTAM environment features (SEVT).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3FC025

SEMV MVS ENVIRONMENT INSTALLATION COMPLETE
Explanation: The feature control command (KN3FCCMD) installed MVS
environment features (SEMV) successfully.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC026

SEMV MVS ENVIRONMENT INSTALLATION FAILED
ROUTINE=KN3AHMF0 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing MVS environment features (SEMV).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3FC027

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS SEMV output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC028

SEMV VTAM ENVIRONMENT STATUS FAILED ROUTINE=KN3AHEM3
REASON=abend RETURN=abend_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was checking the status of VTAM environment features (SEMV).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

373

KN3FC030

NCPC NPALU COLLECTOR INSTALLATION COMPLETE
Explanation: The feature control command (KN3FCCMD) installed the NCP
data collection feature (NCPC).
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC031

NCPC NPALU COLLECTOR INSTALLATION FAILED
ROUTINE=KN3AHNP0 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing the NCP collector environment features (NCPC).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3FC032

option_name OPTION REQUIRED FOR NCPC INSTALLATION
Explanation: A required component was not available to allow the feature
control command (KN3FCCMD) to install the NCP collector environment features
(NCPC).
System Action: The command request fails.
User Response: Check the following:
®
®
®
®
®

Was KN3FCCMD INSTALL FPCT successful?
Was KN3FCCMD INSTALL SEMV successful?
Was KN3FCCMD INSTALL SEVT successful?
Was NCPCACBN specified?
Was NCPCINTV specified?
If the problem persists, contact Candle Support Services.
Message Type: User error.
KN3FC035

NCPC NPALU COLLECTOR START FAILED ROUTINE=KN3AHNP1
REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was starting the NCP collector environment features (NCPC).
System Action: The command request fails.
User Response: Check if KN3FCCMD INSTALL NCPC was successful. If the
problem persists, contact Candle Support Services.
Message Type: User error.

KN3FC040

NCPC NPALU COLLECTOR STOP FAILED ROUTINE=KN3AHNP2
REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was stopping the NCP collector environment features (NCPC).
System Action: The command request fails.
User Response: Check if KN3FCCMD INSTALL NCPC was successful. If the
problem persists, contact Candle Support Services.
Message Type: User error.

374

Candle Products Messages Manual (KLVHS–KONCT)

KN3FC045

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS NCPC output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC050

NDMT NCP DATA MANAGER TASK INSTALLATION COMPLETE
Explanation: The feature control command (KN3FCCMD) installed the NCP
data manager feature (NDMT) successfully.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC051

NDMT NCP DATA MANAGER TASK INSTALLATION FAILED
ROUTINE=KN3AHNT0 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing the NCP data manager environment features
(NDMT).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3FC052

option_name OPTION REQUIRED FOR NDMT INSTALLATION
Explanation: Because a required component was unavailable, the feature
control command (KN3FCCMD) was unable to install the NCP data manager
environment features (NDMT).
System Action: The command request fails.
User Response: Check the following:
®
®
®
®

Was KN3FCCMD INSTALL FPON successful? See message KN3FC010.
Was NDMTPATH specification for the KN3FCCMD correct?
Was NDMTSRVR specification for the KN3FCCMD correct?
Was NDMTUSER specification for the KN3FCCMD correct?
If the problem persists, contact Candle Support Services.
Message Type: User error.
KN3FC055

NDMT NCP DATA MANAGER TASK START FAILED
ROUTINE=KN3AHNT1 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was starting the NCP data manager environment features
(NDMT).
System Action: The command request fails.
User Response: Check if KN3FCCMD INSTALL NDMT was successful. See
message KN3FC050. If the problem persists, log the information and contact
Candle Support Services.
Message Type: User error.

KMQxx001E–KOCJ0046

375

KN3FC060

NDMT NCP DATA MANAGER TASK STOP FAILED ROUTINE=KN3AHNT2
REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was stopping the NCP data manager environment features
(NCPC).
System Action: The command request fails.
User Response: Check if KN3FCCMD START NDMT was successful. See
message KN3FC050. If the problem persists, log the information and contact
Candle Support Services.
Message Type: User error.

KN3FC065

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS NDMT output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC070

DBUG EXTENDED DIAGNOSTICS MODE STARTED
Explanation: Extended diagnostics mode is active.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC071

DBUG EXTENDED DIAGNOSTICS MODE START FAILED
ROUTINE=KN3AHFD1 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was starting extended diagnostic mode (DBUG).
System Action: The command request fails.
User Response: Log the information and contact Candle Support Services.
Message Type: Internal error.

KN3FC072

DBUG EXTENDED DIAGNOSTICS MODE STOPPED
Explanation: Extended diagnostics mode is inactive.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3FC073

DBUG EXTENDED DIAGNOSTICS MODE STOP FAILED
ROUTINE=KN3AHFD2 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was stopping extended diagnostic mode (DBUG).
System Action: The command request fails.
User Response: Log the information and contact Candle Support Services.
Message Type: Internal error.

376

Candle Products Messages Manual (KLVHS–KONCT)

KN3FC074

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS DBUG output.
System Action: None.
User Response: None.
Message Type: Information.

KN3FC075

DBUG EXTENDED DIAGNOSTICS MODE STATUS FAILED
ROUTINE=KN3AHFD3 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was displaying extended diagnostic mode (DBUG).
System Action: The command request fails.
User Response: Log the information and contact Candle Support Services.
Message Type: Internal error.

KN3FC081

TCPC TCP/IP COLLECTOR INSTALLATION FAILED
ROUTINE=KN3ACTC0 REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was installing the TCP/IP collector feature (TCPC).
System Action: The command request fails.
User Response: Log the entire error message for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3FC082

option_name OPTION REQUIRED FOR TCPC INSTALLATION
Explanation: Because a required component was not available, the feature
control command (KN3FCCMD) could not install the TCP/IP collector feature
(TCPC).
System Action: The command request fails.
User Response: User Response: Check the following:
® Was KN3FCCMD INSTALL SEMV successful?
®

Was KN3FCCMD INSTALL FPON successful?

If the problem persists, contact Candle Support Services.
Message Type: User error.
KN3FC083

TCPC TCP/IP COLLECTOR LOAD FAILED FOR MODULE module_name
Explanation: The specified TCP/IP collector module could not be loaded into
storage during installation of the TCP/IP collector feature (TCPC).
System Action: TCP/IP collector installation fails.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

377

KN3FC084

TCP/IP PROFILE ALLOCATION FAILED. RC(return_code),
ERROR(reason_code), INFO(information_code)
Explanation: Dynamic allocation of a TCP/IP profile dataset failed during the
addition of a target TCP/IP to the address space list.
System Action: The target TCP/IP is not added to the address space list and
cannot be monitored.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3FC085

I/O FAILED FOR TCP/IP PROFILE DATASET. FUNCTION: function_name
REASON: reason_code
Explanation: An open or read I/O of a TCP/IP profile dataset failed during the
addition of a target TCP/IP to the address space list.
System Action: The target TCP/IP is not added to the address space list and
cannot be monitored.
User Response: Log the information for problem diagnosis and contact Candle
Support Services
Message Type: Internal error.

KN3FC089

TCPC TCP/IP COLLECTOR START FAILED ROUTINE=KN3ACTC1
REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was starting the TCP/IP collector feature (TCPC).
System Action: The command request fails.
User Response: Check if KN3FCCMD INSTALL TCPC was successful. If the
problem persists, contact Candle Support Services.
Message Type: User error.

KN3FC090

TCPC TCP/IP COLLECTOR STOP FAILED ROUTINE=KN3ACTC2
REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was stopping the TCP/IP collector feature (TCPC).
System Action: The command request fails.
User Response: Check if KN3FCCMD INSTALL TCPC was successful. If the
problem persists, contact Candle Support Services.
Message Type: User error.

KN3FC095

Explanation: This is a prefix for feature control command (KN3FCCMD)
STATUS TCPC output.
System Action: None.
User Response: None.
Message Type: Information.

378

Candle Products Messages Manual (KLVHS–KONCT)

KN3FC096

TCPC STATUS COMMAND FAILED ROUTINE=KN3ACTC3
REASON=reason_code RETURN=return_code
Explanation: An error was detected while the feature control command
(KN3FCCMD) was executing the status function for the TCP/IP collector feature
(TCPC).
System Action: The command request fails.
User Response: Check if KN3FCCMD INSTALL TCPC was successful. If the
problem persists, contact Candle Support Services.
Message Type: Internal error.

KN3FC100

OMEGAMON II for VTAM DIAGNOSTIC feature MODE ACTIVATED
Explanation: The internal diagnostic trace or trap facility was started in
response to a KN3FCCMD START feature command.
System Action: Processing continues.
User Response: None.
Message Type: Informational.

KN3FC101

OMEGAMON II for VTAM DIAGNOSTIC feature ACTIVATION FAILED
ROUTINE=KN3AHFT1 REASON=reason RETURN=return
Explanation: An error was detected during the processing of a KN3FCCMD
START TRACE or TRAP command.
System Action: Processing continues. The facility is not activated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3FC102

OMEGAMON II for VTAM DIAGNOSTIC feature MODE DEACTIVATED
Explanation: The internal diagnostic trace or trap facility was stopped in
response to a KN3FCCMD STOP feature command.
System Action: Processing continues.
User Response: None.
Message Type: Informational.

KN3FC103

OMEGAMON II for VTAM DIAGNOSTIC feature MODE DEACTIVATION
FAILED ROUTINE=KN3AHFT2 REASON=reason RETURN=return
Explanation: An error was detected during the processing of a KN3FCCMD
STOP TRACE or TRAP command.
System Action: Processing continues.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3FC104

OMEGAMON II for VTAM DIAGNOSTIC feature IS status DEACTIVATED
Explanation: This message reports the status of the diagnostic trace or trap
facility in response to a KN3FCCMD STATUS feature command.
System Action: Processing continues.
User Response: None.
Message Type: Informational.

KMQxx001E–KOCJ0046

379

KN3FC105

OMEGAMON II for VTAM DIAGNOSTIC feature STATUS FAILED
ROUTINE=KN3AHFT3 REASON=reason RETURN=return
Explanation: An error was detected during the processing of a KN3FCCMD
STATUS TRACE or TRAP command.
System Action: Processing continues.
User Response: Log the diagnostic information and contact Candle Support
Services.

KN3FT001

INITIALIZING FTP REPORTING THREAD
Explanation: The background FTP reporting thread is being started.
System Action: Processing continues.
User Response: None.

KN3FT002

FTP INITIALIZATION COMPLETE
Explanation: All initialization for the FTP agent is complete.
System Action: Processing continues.
User Response: None.

KN3FT003

FTP INITIALIZATION FAILED TO LOAD KN3INFT2
Explanation: Missing product module.
System Action: Processing terminates.
User Response: Check and correct installation.

KN3FT004

UNABLE TO OPEN ddname
Explanation: DD name ddname cannot be opened. Environment variables
cannot be read.
System Action: Processing continues.
User Response: Correct JCL if environment variables are to be used.

KN3FT005

UNABLE TO START REQUEST FOR ddname
Explanation: Unable to process ddname. No environment variables can be
read, no overrides will be in effect.
System Action: Processing continues.
User Response: Retry. If problem persists, contact Candle Support Services.

KN3FT006

UNABLE TO FIND KN3ENV IN ddname
Explanation: Member KN3ENV cannot be found in ddname. No environment
variables can be read, no overrides will be in effect.
System Action: Processing continues.
User Response: Add member if environment variables are to be used.

KN3FT007

ERROR xxxx READING KN3ENV IN ddname
Explanation: Unable to fully read ddname, internal error xxxx. Some or all
environment variables cannot be read, some overrides may not be in effect.
System Action: Processing continues.
User Response: Retry. If the problem persists, contact Candle Support
Services.

380

Candle Products Messages Manual (KLVHS–KONCT)

KN3FT008

CCCCCC OVERRIDE: nnn
Explanation: The CCCCCC environment variable with a value of nnn was
read.
System Action: Processing continues.
User Response: None.

KN3FT009

VALUE MORE LESS THAN nnn
Explanation: Follows message KN3FT008. The value of the environment
variable is out of normal range.
System Action: Processing continues.
User Response: Unless followed by message KN3FT010, correct the value.

KN3FT010

OVERRIDE VALUE ACCEPTED
Explanation: Follows message KN3FT008 or message KN3FT009. The value of
the environment variable has been used to override the default.
System Action: Processing continues.
User Response: None.

KN3FT011

CCCCCC iN USE... nnn
Explanation: Confirms value nnn of parameter cccccc that is in use.
System Action: Processing continues.
User Response: None.

KN3FT012

UNKNOWN VARIABLE: xxxx
Explanation: An unknown environment variable was found.
System Action: Processing continues.
User Response: Correct or remove the line in the KN3ENV member.

KN3FT102

TOTAL CSA USAGE nnn BYTES BEFORE & nnn AFTER TABLE UPDATE
Explanation: Reports CSA usage by the FTP agent before and after data is
copied from CSA to a local table. Note that the “after” number will never be zero.
System Action: Processing continues.
User Response: None.

KN3FT103

ERROR FREEING CSA
Explanation: An error occurred freeing CSA.
System Action: Processing continues.
User Response: Contact Candle Support Services.

KN3FT104

CSA MONITOR ENDED
Explanation: Background CSA monitor cycle ended.
System Action: Processing continues.
User Response: None.

KN3FT105

nnn SMF RECORDS DROPPED IN INTERVAL, NEEDED bbb MORE
BYTES CSA
Explanation: Insufficient CSA was available to record all FTP data. nnn records
were dropped, bbb more bytes of CSA would have been required to contain
them.
System Action: Processing continues.

KMQxx001E–KOCJ0046

381

User Response: See message KN3FT106.
KN3FT106

INCREASE BUFMAX AND/OR REDUCE COLLECT_INTERVAL
Explanation: Accompanies message KN3FT105.
System Action: Processing continues.
User Response: Decide whether to increase BUFMAX or to reduce
COLLECT_INTERVAL, or both.

KN3FT107

TABLE ERROR nnn RC: xxxx
Explanation: Internal error nnn with return code xxxx occurred..
System Action: Background processing terminates.
User Response: Stop and restart the agent. If the problem persists, contact
Candle Support Services.

KN3FT201

UNKNOWN TRAP EVENT nnn IGNORED
Explanation: An unknown (impossible) event occurred.
System Action: Processing continues.
User Response: Contact Candle Support Services.

KN3FT202

NO JOBNAME FOUND
Explanation: Logic error determining job/task name.
System Action: Processing terminates.
User Response: Retry. If problem persists, contact Candle Support Services.

KN3FT203

ERROR LOADING LLLLLL
Explanation: Unable to load or locate product module LLLLLL.
System Action: Processing terminates.
User Response: Check and correct installation.

KN3FT204

SMF EXIT ADDED: ssssss
Explanation: SMF exit ssssss was added.
System Action: Processing continues.
User Response: None.

KN3FT205

DELETING EXIT: ssssss
Explanation: Deleting SMF exit ssssss.
System Action: Processing continues.
User Response: None.

KN3FT206

FREEING CSA @xxxx LENGTH=nnn
Explanation: During agent shutdown, nnn bytes of CSA at location xxxx are
freed.
System Action: Processing continues.
User Response: None.

KN3FT207

CSA FREED
Explanation: CSA has been successfully freed.
System Action: Processing continues.
User Response: None.

382

Candle Products Messages Manual (KLVHS–KONCT)

KN3FT208

CSVDYNEX ADD FOR (ssssss)(jobname) (xxxx) FAILED RC=yyyy,
REASON=zzzz
Explanation: Error adding SMF exit ssssss.
® jobname is the name of the FTP agent address space
®

xxxx is address of exit in CSA

yyyy and zzzz are error codes from CSVDYNDEX

System Action: Processing terminates.
User Response: Contact Candle Support Services.
KN3FT209

NO CSA TO FREE
Explanation: During agent shutdown, no CSA needed to be freed.
System Action: Processing continues.
User Response: None.

KN3FT210

ERROR FREEING CSA
Explanation: During agent shutdown, an error occurred freeing CSA.
System Action: Processing terminates.
User Response: Contact Candle Support Services.

KN3FT211

ERROR RE-LOADING LLLLLL
Explanation: This should never occur. Message KN3FT203 should occur
instead.
System Action: Processing continues.
User Response: Contact Candle Support Services.

KN3FT212

OBTAINING nnn BYTES OF CSA
Explanation: nnn bytes of CSA are obtained during initialization.
System Action: Processing continues.
User Response: None.

KN3FT213

ERROR OBTAINING CSA
Explanation: Unable to obtain CSA.
System Action: Processing terminates.
User Response: Ensure enough CSA is available (see message KN3FT312).

KN3FT214

CSA @xxxx OBTAINED
Explanation: CSA described in message KN3FT212 was obtained at location
xxxx.
System Action: Processing continues.
User Response: None.

KN3FT215

RECOVERING FROM ALREADY ADDED EXIT
Explanation: An SMF exit for this job was found to be already added. The
existing exit is deleted and a new one is added. Note: this occurs on restart after
the FTP agent is cancelled instead of stopped.
System Action: Processing continues.
User Response: Always stop the FTP agent. Do not cancel it.

KMQxx001E–KOCJ0046

383

KN3FT216

ADDING SMF EXITS
Explanation: Starting to add SMF exits during initialization.
System Action: Processing continues.
User Response: None.

KN3FT217

ADDED SMF EXITS
Explanation: Finished adding SMF exits.
System Action: Processing continues.
User Response: None.

KN3FT218

DELETING SMF EXITS
Explanation: Starting to delete SMF exits at shutdown.
System Action: Processing continues.
User Response: None.

KN3FT219

DELETED SMF EXITS
Explanation: Finished deleting SMF exits.
System Action: Processing continues.
User Response: None.

KN3FT220

CSVDYNEX DELETE FOR (ssssss)(jobname) (xxxx) FAILED RC=xxxx,
REASON=xxxx
Explanation: Error deleting SMF exit ssssss.
® jobname is the name of the FTP agent address space
®

xxxx is the address of the exit in CSA

yyyy and zzzz are error codes from CSVDYNDEX

System Action: Processing continues.
User Response: None. If problem persists, contact Candle Support Services.
KN3FT221

ERROR FREEING CSA COPY OF RECORD
Explanation: Unable to free the CSA copy of the FTP data.
System Action: Processing continues.
User Response: Contact Candle Support Services.

KN3FT222

TOTAL CSA USAGE NOW nnn
Explanation: Total FTP agent CSA usage is nnn.
System Action: Processing continues.
User Response: None.

KN3FT223

TOTAL CSA USAGE NOW nnn
Explanation: Total FTP agent CSA usage is nnn.
System Action: Processing continues.
User Response: None.

KN3FT224

RESMGR ADD ERROR R15=xxxx
Explanation: Error xxxx adding resource manager. CSA will not be cleaned up
if the FTP agent is cancelled.
System Action: Processing continues.

384

Candle Products Messages Manual (KLVHS–KONCT)

User Response: None. If problem persists, contact Candle Support Services.
KN3FT225

RESMGR DELETE ERROR R15=xxxx
Explanation: Error xxxx deleting resource manager.
System Action: Processing continues.
User Response: None. If problem persists, contact Candle Support Services.

KN3FT226

NO UNPROCESSED SMF RECORDS
Explanation: No unprocessed SMF records remained at FTP agent shutdown.
System Action: Processing continues.
User Response: None.

KN3FT227

RESIDUAL CSA USAGE: nnn
Explanation: Final FTP agent CSA usage is nnn.
System Action: Processing continues.
User Response: If this value is not zero, contact Candle Support Services.

KN3FT228

DEQUEUE EXIT FOR EVENT xxxx
Explanation: Processing for event xxxx is complete.
System Action: Processing continues.
User Response: None.

KN3FT401

INITIALIZING CLEANUP THREAD
Explanation: Background history cleanup is starting.
System Action: Processing continues.
User Response: None.

KN3FT402

TABLE CLEANUP RUNNING
Explanation: Periodic table cleanup started.
System Action: Processing continues.
User Response: None.

KN3FT403

CLEANED UP nnn ROWS
Explanation: Periodic table cleanup ended. nnn rows were deleted.
System Action: Processing continues.
User Response: None.

KN3FT404

TABLE ERROR xxxx RC: yyyy
Explanation: Periodic table cleanup error xxxx occurred, return code is yyyy.
System Action: Cleanup thread terminates.
User Response: Restart the agent. If the problem persists, contact Candle
Support Services.

KN3FT501

OMEGAMON FTP AGENT RESOURCE MANAGER ENTERED
Explanation: The FTP agent was cancelled. The resource manager will attempt
cleanup.
System Action: Processing continues.
User Response: Always stop the FTP agent. Do not cancel it.

KMQxx001E–KOCJ0046

385

KN3FT502

ERROR: NO EYECATCHER IN CSA
Explanation: Resource manager was unable to locate the CSA fo the FTP
agent. The CSA may have already been freed.
System Action: The resource manager terminates.
User Response: None.

KN3FT503

RESOURCE MANAGER STARTED
Explanation: The resource manager has found a valid CSA and will now clean
it up.
System Action: Processing continues.
User Response: None.

KN3FT504

INVALID ROW POINTER
Explanation: The CSA is damaged.
System Action: The resource manager terminates.
User Response: None.

KN3FT505

ERROR FREEING CSA COPY OF RECORD
Explanation: Error freeing one CSA element.
System Action: The resource manager continues, but message KN3FT504 is
likely to display next.
User Response: None.

KN3FT506

Resource manager exiting
Explanation: The resource manager has freed all the CSA it can. Some CSA
cannot be freed as it contains the resource manager itself and associated data.
System Action: Termination continues.
User Response: To avoid loss of a small amount of CSA every time the
resource manager is used, always stop the FTP agent. Do not cancel it.

KN3IR001

IRA SUBNODE REGISTRATION THREAD IS ACTIVE
HOSTNAME=hostname SUBSYSTEMID=subsystemid
NODETYPE=nodetype PRODUCT=product VERSION=version
Explanation: OMEGAMON XE for Mainframe Networks IRA registration service
is available.
System Action: None.
User Response: None.

KN3IR002

TCP|NCP|VTAM MONITOR STARTING FOR ORIGINNODE originnode
Explanation: The IRA manager is starting to monitor the named originnode.
System Action: None.
User Response: Information only.

KN3IR003

TCP|NCP|VTAM MONITOR STARTED FOR ORIGINNODE originnode
Explanation: The IRA manager has started to monitor the named originnode.
System Action: None.
User Response: Information only.

386

Candle Products Messages Manual (KLVHS–KONCT)

KN3IR004

TCP|NCP|VTAM MONITOR SUBNODE REGISTERED FOR ORIGINNODE
originnode
Explanation: The IRA manager has registered to monitor the named
originnode.
System Action: None.
User Response: Information only.

KN3IR005

TCP|NCP|VTAM MONITOR SUBNODE DEREGISTERED FOR
ORIGINNODE originnode
Explanation: The IRA manager has deregistered monitoring the named
originnode.
System Action: None.
User Response: Information only.

KN3IR006

TCP|NCP|VTAM MONITOR STOPPED FOR ORIGINNODE originnode
Explanation: The IRA manager has stopped monitoring the named originnode.
System Action: None.
User Response: Information only.

KN3IR900

IRA type REGISTRATION TOKEN MISSING OR INVALID ROUTINE=routine
Explanation: The registration token to register the OMEGAMON XE for
Mainframe Networks product was not located.
System Action: The IRA on which the error occurred will not participate in any
distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why N3 product registration failed. If problems persist, contact Candle
Support Services.

KN3IR901

IRA type HAS ABENDED ROUTINE=routine
Explanation: An IRA Management function for the OMEGAMON XE for
Mainframe Networks product has abended.
System Action: The IRA on which the error occurred will not participate in any
distributed queries.
User Response: Gather RKLVLOG, JES messages and LOG for the IRA
address space and contact Candle Support Services.

KN3IR902

IRA type ENVIRONMENT ERROR ROUTINE=routine REASON=reason
Explanation: The product environment for the OMEGAMON XE for Mainframe
Networks product was not properly installed.
System Action: The IRA on which the error occurred will not participate in any
distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why N3 product environment was not properly installed. If problems
persist, contact Candle Support Services.

KN3IR903

pthread_create error
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread could not be started.

KMQxx001E–KOCJ0046

387

System Action: The IRA on which the error occurred will not participate in any
distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread could not be started. If problems persist,
contact Candle Support Services.
KN3IR904

pthread_detach error
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread could not be detached.
System Action: The IRA on which the error occurred will not participate in any
distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread could not be detached. If problems
persist, contact Candle Support Services.

KN3IR905

IRA Manager command unknown:
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread received an unsupported command.
System Action: The command is ignored.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread command was invalid. If problems
persist, contact Candle Support Services.

KN3IR906

IRA Manager command operand missing
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread received a command that did not have all required operands.
System Action: The command is ignored.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread command was invalid. If problems
persist, contact Candle Support Services.

KN3IR907

Unknown component for subnode registration cccc
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread received a request to register an unknown component.
System Action: The unknown component is not registered
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread component was invalid If problems
persist, contact Candle Support Services.

KN3IR908

IRA_Subnode_Register error: RC=xx Node=ccccccccccccc
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread received a non-zero return code from the CT IRA Registration functions.
System Action: The component subnode is not registered
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread component subnode failed. If problems
persist, contact Candle Support Services.

388

Candle Products Messages Manual (KLVHS–KONCT)

KN3IR909

IRA_Subnode_Deregister error: RC=xx Node=ccccccccccccc
Explanation: The OMEGAMON XE for Mainframe Networks IRA Registration
Thread received a non-zero return code from the CT IRA Registration functions.
System Action: The component subnode is not deregistered
User Response: Check the TLVLOG for additional messages that may indicate
the reason why IRA Registration Thread component subnode failed. If problems
persist, contact Candle Support Services.

KN3IR910

IRA SUBNODE REGISTRATION THREAD IS NOT ACTIVE
HOSTNAME=hostname SUBSYSTEMID=subsystemid
NODETYPE=nodetype PRODUCT=product VERSION=version
Explanation: An attempt was made to post a request to the N3 product
Subnode registration service and the thread was found to be not active.
System Action: The subnode registration request fails.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why N3 product Subnode registration service failed. If problems
persist, contact Candle Support Services.

KN3IR911

IRA SUBNODE REGISTRATION THREAD IS NOT RESPONDING
HOSTNAME=hostname SUBSYSTEMID=subsystemid
NODETYPE=nodetype PRODUCT=product VERSION=version
Explanation: An attempt was made to post a request to the N3 product
Subnode registration service and the thread was found responding to the request.
System Action: The subnode registration request fails.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why N3 product Subnode registration service failed. If problems
persist, contact Candle Support Services.

KN3IR912

IRA SUBNODE REGISTRATION THREAD CURRENTLY ACTIVE
HOSTNAME=hostname SUBSYSTEMID=subsystemid
NODETYPE=nodetype PRODUCT=product VERSION=version
Explanation: An attempt was made to start the N3 product Subnode
registration service and the thread was found currently active.
System Action: The subnode registration request fails.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why N3 product Subnode registration service failed. If problems
persist, contact Candle Support Services.

KN3IR913

IRA type REGISTRATION THREAD HAS ABENDED ROUTINE=cccccccc
Explanation: The IRA Management registration thread for the OMEGAMON
XE for Mainframe Networks Product has abended.
System Action: The IRA on which the error occurred will not participate in any
distributed queries.
User Response: Gather RKLVLOG, JES messages and LOG for the IRA
address space and contact Candle Support Services.

KN3IR914

INVALID REQUEST CODE (hhhhhhhh) ROUTINE=routine
Explanation: The IRA Management registration thread for the OMEGAMON
XE for Mainframe Networks Product incurred a catastrophic error.

KMQxx001E–KOCJ0046

389

System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Gather RKLVLOG, JES messages and LOG for the IRA
address space and contact Candle Support Services.
KN3IR915

STORAGE ALLOCATION FAILED FOR ELEMENT(element)
ROUTINE=routine
Explanation: The IRA Management registration function for the OMEGAMON
XE for Mainframe Networks Product could not allocate virtual Storage.
System Action: The current registration request will fail.
User Response: Determine insufficient storage problem.

KN3IR916

$SCAN ERROR PARSING cccccccc ROUTINE=cccccccc
Explanation: A error occurred parsing data from RKANPAR member
System Action: The current registration request will fail.
User Response: Determine $SCAN error.

KN3IR917

TCP MONITOR PROFILE INFORMATION NOT FOUND IN member FOR
ORIGINNODE originnode DEFAULTS WILL BE USED
Explanation: IRA registration detected that there is no profile information
defined in the RKANPAR member to monitor the originnode.
System Action: The IRA subnode manager will attempt to use the defaults
found in member and start the TCP Monitor for the originnode.
User Response: Update RKANPAR member KN3TCPMO with monitoring
information for the TCP/IP address space to monitor the originnode.

KN3IR918

$PAM ERROR REQUEST=request MEMBER=member R15=hhhhhhhh
R0=hhhhhhhh R1=hhhhhhhh ROUTINE=routine
Explanation: A error occurred reading the RKANPAR for the member.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Determine $PAM error.

KN3IR919

TCP MONITOR START FAILED FOR ORIGINNODE originnode
Explanation: An error occurred starting the TCP/IP collection monitor for the
originnode.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the start monitoring request failed. If problems persist, contact
Candle Support Services.

KN3IR920

TCP MONITOR REGISTRATION FAILED RC=xxxxxxxx FOR ORIGINNODE
originnode
Explanation: Subnode registration failed for the TCP/IP image for the
originnode.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.

390

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Check the TLVLOG for additional messages that may indicate
the reason why the registration request failed. If problems persist, contact Candle
Support Services.
KN3IR921

component SUBNODE REGISTRATION FAILED ROUTINE=routine
Explanation: Subnode registration failed.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the registration request failed. If problems persist, contact Candle
Support Services.

KN3IR922

TCP MONITOR STOP FAILED FOR ORIGINNODE originnode
Explanation: An error occurred starting the TCP/IP collection monitor for the
originnode.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the stop monitoring request failed. If problems persist, contact
Candle Support Services.

KN3IR923

TCP MONITOR DEREGISTRATION FAILED RC=xxxxxxxx FOR
ORIGINNODE originnode
Explanation: Subnode deregistration failed for the TCP/IP image for the
originnode.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the deregistration request failed. If problems persist, contact
Candle Support Services.

KN3IR924

IRA SUBNODE DEREGISTRATION FAILED ROUTINE=cccccccc
Explanation: Subnode registration failed.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the deregistration request failed. If problems persist, contact
Candle Support Services.

KN3IR925

UNABLE TO OBTAIN WORK AREA STORAGE ROUTINE=cccccccc
Explanation: Insufficient storage to satisfy request
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the storage request failed. If problems persist, contact Candle
Support Services.

KN3IR926

TCP MONITOR COLLECTION FAILED MACRO(cccccccc) macro
parameters RC=xxxxxxxx ROUTINE=cccccccc ORIGINNODE originnode
Explanation: IRA Collection failed.

KMQxx001E–KOCJ0046

391

System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the collection request failed. If problems persist, contact Candle
Support Services.
KN3IR927

TCP MONITOR COLLECTION FAILED ROUTINE=cccccccc UNABLE TO
LOCATE ORIGINNODE originnode
Explanation: IRA Collection failed.
System Action: The IRA subnode for which the error occurred will not
participate in any distributed queries.
User Response: Check the TLVLOG for additional messages that may indicate
the reason why the collection request failed. If problems persist, contact Candle
Support Services.

KN3LC100

LOCAL APPLID applid UNAVAILABLE, NDM TASK WILL TERMINATE.
Explanation: OMEGAMON II for VTAM was unable to open the VTAM ACB
applid.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Check that the APPL applid is defined to VTAM and active.
Message Type: Information.

KN3LC101

COLLECTOR APPLID applid UNAVAILABLE, NDM TASK WILL
TERMINATE.
Explanation: OMEGAMON II for VTAM was unable to connect to the VTAM
ACB applid.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Check that the APPL applid is defined to VTAM and active.
Check that the OMEGAMON II for VTAM which contains the NCP collection
component is active.
Message Type: Information.

KN3LC102

APPC REQUEST ERROR appc_request ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: An APPC service failed.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LC103

CLIENT MODULE module_name NOT FOUND ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: OMEGAMON II for VTAM was not able to locate a module
required for communication with the NCP collector component.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.

392

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.
KN3LC104

MISSING KN3AYLCA WORK AREA ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: OMEGAMON II for VTAM was not able to locate the
communications work area.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LC106

APPC VERSION MISMATCH. LOCAL VERSION local_version
COLLECTOR VERSION collector_version
Explanation: OMEGAMON II for VTAM detected that the NCP collector
component was at an incompatible service level.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Verify the service level of the OMEGAMON II for VTAM
containing the NCP collector component.
Message Type: User Error.

KN3LC107

SQL REQUEST ERROR, ROUTINE=routine-name
REQUEST=sql_request_codes
Explanation: An invalid SQL request was received.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LC108

FAILURE TO ACQUIRE STORAGE FOR storage_area
ROUTINE=routine_name RETURN=return_code REASON=reason_code
Explanation: OMEGAMON II for VTAM was not able to obtain the storage
required to process the current request.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LC109

KN3AYNCE SELECT COUNT ERROR ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: OMEGAMON II for VTAM detected an error with the data
returned from the NCP collection component.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.

KMQxx001E–KOCJ0046

393

User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.
KN3LC110

APPC CLIENT SERVICES ABEND CODE=abend_code PSW=psw
ROUTINE=routine_name
Explanation: An abend occurred in the module indicated.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LC111

Rnn - Rnn: registers
Explanation: Registers associated with abend message KN3LC110.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LC112

CONNECTION FAILURE ACBNAME localid
Explanation: The VTAM APPL localid has been terminated abnormally.
System Action: Collection of NCP data terminates. OMEGAMON II for VTAM
will attempt to restart collection at a regular interval.
User Response: Check that the APPL is active to VTAM. Candle Support
Services.
Message Type: Information.

KN3LS100

COLLECTOR APPLID applid IS UNAVAILABLE ROUTINE=routine_name
Explanation: APPC initialization failed during start-up.
System Action: APPC initialization will retry next collection interval.
User Response: None
Message Type: User error.

KN3LS101

APPC REQUEST ERROR appc_request DURING startup|shutdown
ROUTINE=routine_name RETURN=return_code REASON=reason_code
Explanation: APPC service failure occurred during initialization.
System Action: APPC request failed and the NCPC collector task is
terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS102

FAILURE TO ACQUIRE STORAGE FOR storage_area
ROUTINE=routine_name RETURN=return_code REASON=reason_code
Explanation: Storage could not be obtained for the specified area.
System Action: The APPC environment and NCPC collector are terminated.

394

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.
KN3LS103

INVALID COLLECTOR APPLID RECEIVED ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: Invalid acbname received from the collector keyword.
System Action: The APPC environment and NCPC collector are terminated.
User Response: Check the COLLECTOR acbname keyword on the
KN3FCCMD INSTALL NCPC command in the start-up member.
Message Type: User error.

KN3LS104

MODULE ENTRY POINT module_name NOT FOUND
ROUTINE=routine_name RETURN=return_code REASON=reason_code
Explanation: The entry point of the module name is not found.
System Action: The APPC environment and NCPC collector are terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS105

MISSING storage_area WORK AREA ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: The storage area is not available for normal APPC processing.
System Action: The APPC environment and NCPC collector are terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS106

APPC REQUEST ERROR appc_request ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: APPC service failure occurred during communication.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS107

INVALID TOKEN PASSED TOKEN=token ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: Incorrect data is representing the token.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS108

KN3AXNPA npa_request FAILED ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: The NPA service request did not complete.
System Action: The NDMT task is terminated.

KMQxx001E–KOCJ0046

395

User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.
KN3LS109

TABLE REQUEST ERROR ROUTINE=routine_name TABLE=table_name
Explanation: Invalid NCP resource table request.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS110

INVALID RESOURCE COUNT ERROR ROUTINE=routine_name
RETURN=return_code COUNT=count
Explanation: Invalid number received and cannot be processed.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS111

KN3AYWKG CHAIN ERROR ROUTINE=routine_name
RETURN=return_code REASON=reason_code
Explanation: The WORKG area does not exist when session terminating.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS112

LUCS SERVICES ABEND CODE=abend_code PSW=psw
ROUTINE=routine_name
Explanation: The referenced routine received a abend.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS113

R00 - R15: registers r0-r15
Explanation: Registers associated with abend in message KN3LS112.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3LS114

CONNECTION FAILURE USING ACBNAME applid
ROUTINE=routine_name
Explanation: The applid referenced received a communication failure.
System Action: The NDMT task is terminated.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

396

Candle Products Messages Manual (KLVHS–KONCT)

KN3ND000

NCP STATISTICS COLLECTOR AVAILABLE FOR REQUESTS
Explanation: The NCP NPALU collector task can receive requests.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3ND001

NCP STATISTICS COLLECTOR IS TERMINATING
Explanation: The NCP NPALU collector task is terminating.
System Action: None.
User Response: None.
Message Type: Information.

KN3ND002

NCP STATISTICS COLLECTOR ABENDED, CODE=abend_code
PSW=program_status_word
Explanation: The NCP NPALU collector task abended. The code and Program
Status Word (PSW) are displayed.
System Action: The NCP NPALU collector task attempts to recover and
continue executing.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services. Message KN3ND003 follows.
Message Type: Internal error.

KN3ND003

Rregister_number - Rregister_number register_value
Explanation: This is diagnostic information following message KN3ND002.
System Action: None.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND004

SESSION ESTABLISHED WITH NPALU=npalu_name
Explanation: The NCP NPALU collector task is in contact with
NPALU=npalu_name and is ready to monitor requests for the corresponding
NCP.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3ND005

SESSION REJECTED FOR NPALU=npalu_name reason_description
Explanation: The NCP NPALU collector task was unable to establish a session
with NPALU=npalu_name because of the specified reason.
System Action: NCP statistics data is not available from the NPALU.
User Response: Check the dataset names assigned to ddname KN3RRT
(Resource Resolution Table) and ddname KN3SRC (NCP-generated NDF source
library) in the started task JCL for the local NCP collector address space.
Message Type: User configuration or resource availability error.

KMQxx001E–KOCJ0046

397

KN3ND006

SESSION TERMINATED WITH NPALU=npalu_name
Explanation: The NCP NPALU collector task lost the session with NPALU=
npalu_name.
System Action: NCP statistics data is not available from the NPALU.
User Response: None.
Message Type: User configuration or resource availability error.

KN3ND007

NCP STATISTICS COLLECTOR COMPLETED TERMINATION
Explanation: The NCP NPALU collector task completed termination.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3ND008

FAILURE TO ACQUIRE STORAGE FOR MONITORING
ROUTINE=KN3AHN00 REASON=reason_code
Explanation: A storage failure prevented a resource from being monitored.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND009

FAILURE ADDING RESOURCE(resource_name) TO USER TOPOLOGY
ROUTINE=KN3AHN00 REASON=NETWORK TOPOLOGY SERVICES
FAILURE
Explanation: A resource could not be added to the user NCP topology due to a
failure in network topology services.
System Action: None.
User Response: See previously issued messages. Log the information for
problem diagnosis, and contact Candle Support Services.
Message Type: Internal error.

KN3ND010

STORAGE FAILURE IN NPALU COLLECTOR ROUTINE=routine_name
REASON=reason_code
Explanation: Storage could not be acquired in the specified routine.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND011

FAILURE TO OPEN VTAM ACB NAME(acb_name)
Explanation: The specified ACB name could not be opened to VTAM for the
NPALU collector task.
System Action: None.
User Response: Determine if the specified ACB name is in a connectable state.
Message Type: Warning.

398

Candle Products Messages Manual (KLVHS–KONCT)

KN3ND012

FAILED TO FIND OWNING RESOURCE owning_resource_name FOR
RESOURCE resource_name DURING DYNAMIC DELETE
Explanation: The owning resource named owning_resource_name was not
found in the topology as the owner of the resource named resource_name during
a dynamic resource delete.
System Action: The resource named resource_name is not deleted.
User Response: Log the message for problem diagnosis and call Candle
Support Services.
Message Type: Internal error.

KN3ND013

FORWARD REQUEST FOR NPALU(npalu_name) FAILED STORAGE
FAILURE MODULE=KN3AHN05 REASON=reason_code
Explanation: Collection data could not be forwarded from the specified NPALU
on the current collection interval. Collection will be attempted on the next interval.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND014

NCP DICTIONARY(module_name) FOR NCP RELEASE(NCP_release)
LOAD FAILED
Explanation: The data dictionary for the specified NCP release could not be
loaded. The NCP cannot be monitored.
System Action: None.
User Response: If the NCP is a supported release, contact Candle Support
Services.
Message Type: Internal error.

KN3ND015

$PAM($PAM_name) FAILED ROUTINE=KN3AHN04 DDNAME=KN3RRT
R15=return_code R0=return_code R1=return_code
Explanation: The specified CT/Engine function failed in accessing ddname
KN3RRT.
System Action: None.
User Response: Verify that the ddname KN3RRT is available to the NPALU
collector.
Message Type: User error.

KN3ND016

INPUT EXIT RECEIVE FAILED MODULE=KN3AHN06 R0=return_code
R1=return_code R15=return_code
Explanation: A VTAM receive function failed.
System Action: None.
User Response: See previously issued messages. Log the information for
problem diagnosis, and contact Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

399

KN3ND017

FAILURE ADDING DYNAMIC RESOURCE(resource_name) TO
TOPOLOGY ROUTINE=KN3AHN12 R0=register_value R1=register_value
R15=register_value
Explanation: Storage could not be acquired to add the specified resource to the
topology. NCP statistics are not available for that resource.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND018

MAXCOLL REACHED WHEN STARTING COLLECTION ON
resource_name NPALU=npalu_name
Explanation: The specified resource cannot start collection because the NCP is
already collecting data from the maximum number of resources allowed.
System Action: None.
User Response: Increase the MAXCOLL parameter in the NCP generation.
Message Type: User error.

KN3ND019

SEND OF START NETWORK DATA ACQUISITION RU FOR
resource_name FAILED ROUTINE=KN3AHN16 R0=return_code
R1=return_code
Explanation: The NCP sent a negative response to a start network data
acquisition RU for the specified resource.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND020

SEND OF STOP NETWORK DATA ACQUISITION RU FAILED
ROUTINE=KN3AHN16 R0=return_code R1=return_code
Explanation: The NCP sent a negative response to a stop network data
acquisition RU.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND021

SEND OF FORWARD NETWORK DATA RU FAILED
ROUTINE=KN3AHN16 R0=return_code R1=return_code
Explanation: The NCP sent a negative response to a forward network data RU.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND022

$PAM($PAM_name) FAILED ROUTINE=KN3AGSRC DDNAME=ddname
R15=return_code R0=return_code R1=return_code
Explanation: The specified CT/Engine $PAM (PDS services) function failed.
System Action: None.
User Response: Check the dataset names assigned to ddname KN3RRT
(Resource Resolution Table) and ddname KN3SRC (NCP-generated NDF source
library) in the started task JCL for the local NCP collector address space.
Message Type: Warning.

400

Candle Products Messages Manual (KLVHS–KONCT)

KN3ND023

$PAM($PAM_name) FAILED ROUTINE=KN3AGSRC DDNAME=ddname
MEMBER=member_name R15=register_value R0=register_value
R1=register_value
Explanation: The specified CT/Engine $PAM (PDS services) function failed
accessing the specified member.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND024

FAILURE OPENING DDNAME(ddname) FOR MVS LOAD
ROUTINE=KN3AGLOD
Explanation: The specified ddname could not be opened for an MVS load.
System Action: See previously issued messages.
User Response: None.
Message Type: User error.

KN3ND025

FAILURE DELETING MODULE(module_name)
Explanation: The specified module could not be deleted from MVS storage.
System Action: None.
User Response: None.
Message Type: Warning.

KN3ND026

FAILURE LOADING MODULE(module_name) ROUTINE=KN3AGLOD
SYSTEM CODE=system_code REASON CODE=reason_code
Explanation: The specified module could not be loaded into MVS storage. The
accompanying system and reason codes are provided.
System Action: See previously issued messages.
User Response: None.
Message Type: User error.

KN3ND027

NETWORK TOPOLOGY ERROR LOADING OR READING RRT
(RRT_name)
Explanation: The specified RRT could not be loaded or read. The
corresponding NCP topology could not be built.
System Action: None.
User Response: Verify that a valid RRT by the specified name is pointed to by
ddname KN3RRT.
Message Type: User error.

KN3ND028

NETWORK TOPOLOGY ERROR NPALU NAME MISMATCH IN RRT
(RRT_name) FOR NPALU(npalu_name)
Explanation: The specified RRT did not contain the correct NPALU name for
the indicated NPALU.
System Action: None.
User Response: Verify that the correct RRT is available to the NPALU
collector.
Message Type: User error.

KMQxx001E–KOCJ0046

401

KN3ND029

NETWORK TOPOLOGY DUPLICATE RESOURCE(resource_name) FOUND
IN RRT(RRT_name)
Explanation: The specified resource was found in the indicated RRT but
already exists in the current NCP topology.
System Action: None.
User Response: Verify your NCP generation.
Message Type: User error.

KN3ND030

NETWORK TOPOLOGY ERROR IN LOCATE FUNCTION DURING
ADDITION OF NCP(NCP_name) R15=register_value
Explanation: An unrecoverable error occurred locating resources in the current
topology while adding the indicated NCP. A check is being made in the current
topology for any duplicate resources.
System Action: None.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND031

NETWORK TOPOLOGY ERROR NCP(NCP_name) NOT FOUND IN
TOPOLOGY FOR DELETION
Explanation: You requested the deletion of a specified NCP, but it does not
exist.
System Action: None.
User Response: Check the status of the NCP.
Message Type: User or internal error.

KN3ND032

NCP SOURCE TO RRT MISMATCH FOR MEMBER NCP_source_member
DURING function_call. FOUND LABEL NCP_source_label
Explanation: The indicated NCP source member did not match the resources
found in its corresponding Resource Resolution Table (RRT).
System Action: None.
User Response: Verify that the NCP source member and its RRT match.
Message Type: User error.

KN3ND033

OPEN OF SOURCE MEMBER FOR NCP(NCP_source_member) FAILED
Explanation: The indicated NCP source member could not be opened.
System Action: None.
User Response: Verify the indicated NCP source member is available in
ddname KN3SRC, the NCP generated NDF source library.
Message Type: User error.

402

Candle Products Messages Manual (KLVHS–KONCT)

KN3ND034

KEYWORD(keyword) ON(macro_name) MACRO WITH LABEL(label_name)
IS NOT SPECIFIED
Explanation: This keyword is not explicitly specified on the macro with the
indicated label in the NCP source member. The keyword is used by the NCP
statistics component.
System Action: Some calculated statistics may not be available. See the
Planning chapter in the OMEGAMON II for VTAM Configuration and
Customization Guide.
User Response: Specify the keyword on the macro in the NCP source
member.
Message Type: Warning.

KN3ND035

DYNAMIC MOVE FAILED TO FIND (resource_name) RESOURCE IN
CURRENT TOPOLOGY
Explanation: A target or source resource, resource_name, was not found in the
current topology during a dynamic move. NCP topology information may be
incorrect.
System Action: None.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND036

RRT RELEASE LEVEL rrt_level UNKNOWN FOR NCP_name. USING
LEVEL rrt_level1 NCP RELEASE ncp-level.
Explanation: The NCP(NCP_name) is not generated at a supported release
level and cannot be monitored at that level.
System Action: The NCP will be monitored using rrt_level1 and ncp-level as
shown in the message.
User Response: If the NCP is a supported release, contact Candle Support
Services.
Message Type: Internal error.

KN3ND037

NCP WILL NOT BE MONITORED
Explanation: The NCP(NCP_name) specified in previous messages cannot be
monitored.
System Action: None.
User Response: See previous messages.
Message Type: Information.

KN3ND100

NCP DATA MANAGER TASK AVAILABLE FOR REQUESTS
Explanation: The NCP data manager task can receive requests.
System Action: None.
User Response: None.
Message Type: Confirmation.

KMQxx001E–KOCJ0046

403

KN3ND101

NCP DATA MANAGER TASK IS TERMINATING
Explanation: The NCP data manager task is terminating.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3ND102

NCP DATA MANAGER TASK ABENDED, CODE=abend_code
PSW=program_status_word ROUTINE=routine_name
Explanation: The NCP data manager task abended. The code, Program Status
Word (PSW), and routine are displayed.
System Action: The NCP data manager task attempts error recovery.
User Response: Log the information displayed for problem diagnosis, and
contact Candle Support Services. Message KN3ND103 follows.
Message Type: Internal error.

KN3ND103

Rregister_number - Rregister_number register_value
Explanation: This is diagnostic information following message KN3ND102.
System Action: None.
User Response: Log this information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND104

NCP DATA MANAGER TASK TERMINATION COMPLETE
Explanation: The NCP data manager task terminates.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3ND105

NCP DATA MANAGER TASK INITIALIZATION FAILED
REASON=reason_code RETURN=return_code
Explanation: An error occurred while initializing the NCP Data Manager task.
Return codes are dependent upon reason code and are used by Candle for
problem determination. Reason codes are
TASKLRN

Unable to establish CT/Engine logical resource number.

ALLOCTHT

Unable to allocate memory.

PATHCTDS

Unable to connect to NCP collector.

TOKNCTDS

Unable to acquire token for NCP collector.

CNCTCTDS

Unable to connect to NCP collector.

NCPCINTV

Unable to retrieve NCP collector interval value.

System Action: NCP Data Manager task does not initialize.

404

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Depending on the reason code, take recommended action or
contact Candle as follows:
TASKLRN

Log information and contact Candle Support Services.

ALLOCTHT

Change your memory allocations.

PATHCTDS

See previous message.

TOKNCTDS

See OMEGAMON II for VTAM RKLVLOG.

CNCTCTDS

Check if NCP collector is available.

NCPCINTV

See previous message.

Message Type:

Internal or user error.

KN3ND106

NRE ADD RESOURCE FAILED FOR NCP_name NPALU=npalu_name
RETURN=return_code
Explanation: An internal error has occurred within the NCP data manager task.
System Action: The NCP data manager task terminates.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND107

NRE DELETE RESOURCE FAILED FOR NCP_name NPALU=npalu_name
RETURN=return_code
Explanation: An internal error has occurred within the NCP data manager task.
System Action: The NCP data manager task terminates.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND108

SQL RESOURCE ALLOCATION FAILED RETURN=return_code
Explanation: An internal request for SQL resources by the NCP data manager
task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND109

API UPDATE TOPOLOGY REQUEST FAILED RETURN=return_code
SENSE=sense_code
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

405

KN3ND110

API UPDATE TOPOLOGY ERROR KN3AYNCE SNAP
Explanation: An internal request by the NCP data manager task has failed.
Message is diagnostic information.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND111

API UPDATE TOPOLOGY ERROR KN3AYNRE SNAP
Explanation: An internal request by the NCP data manager task has failed.
Message is diagnostic information.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND112

API UPDATE DATA REQUEST FAILED RETURN=return_code
SENSE=sense_code
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND113

API UPDATE DATA ERROR KN3AYNCE SNAP
Explanation: An internal request by the NCP data manager task has failed. The
message is diagnostic information.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND114

API UPDATE DATA ERROR KN3AYNRE SNAP
Explanation: An internal request by the NCP data manager task has failed. The
message is diagnostic information.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND115

KN3AYNRE RDI SEGMENT ALLOCATION FAILED
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

406

Candle Products Messages Manual (KLVHS–KONCT)

KN3ND116

KN3AYNRE RDS SEGMENT ALLOCATION FAILED
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND117

KN3AYNRE HEADER ALLOCATION FAILED
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND118

API ADD MONITOR REQUEST FAILED FOR resource_name
NPALU=npalu_name RETURN=return_code SENSE=sense_code
Explanation: A request to start monitoring resource (resource_name) failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND119

API DELETE MONITOR REQUEST FAILED FOR resource_name
NPALU=npalu_name RETURN=return_code SENSE=sense_code
Explanation: A request to stop monitoring resource cccccccc failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND120

KN3AYNCE ALLOCATION FAILED
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND121

API EXTRACT RESOURCE REQUEST FAILED FOR resource_name
NPALU=npalu_name RETURN=return_code SENSE=sense_code
Explanation: A request to extract resource data for resource_name failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

407

KN3ND122

API EXTRACT RESOURCE LIST REQUEST FAILED FOR resource_name
NPALU=npalu_name RETURN=return_code SENSE=sense_code
Explanation: A request to extract resource data owned by resource_name
failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND123

API ADD MONITOR LIST REQUEST FAILED FOR resource_name
NPALU=npalu_name RETURN=return_code SENSE=sense_code
Explanation: A request to add monitoring for a list of resources owned by
resource_name failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND124

API ADD MONITOR LIST KN3AXNTS ERROR RETURN=return_code
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND125

API DELETE MONITOR LIST REQUEST FAILED FOR resource_name
NPALU=npalu_name RETURN=return_code SENSE=sense_code
Explanation: A request to delete a list of monitored resources owned by
resource_name failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND126

API DELETE MONITOR LIST KN3AXNTS ERROR RETURN=return_code
Explanation: An internal request by the NCP data manager task has failed.
System Action: The NCP data manager task request fails.
User Response: Log the information for problem diagnosis, and contact
Candle Support Services.
Message Type: Internal error.

KN3ND130

KN3AGNPB SERVICE FUNCTION - ABENDED, CODE=abend_code
Explanation: A request being processed by the KN3AGNPB API module has
abended.
System Action: The site default or resource specific monitor options are not
modified.
User Response: Log the information displayed for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

408

Candle Products Messages Manual (KLVHS–KONCT)

KN3ND131

KN3AGNPB SERVICE FUNCTION - FAILED, FUNCTION=function_name,
RETURN=return_code
Explanation: A request being processed by the KN3AGNPB API module has
failed.
System Action: The site default or resource specific monitor options are not
modified.
User Response: Log the information displayed for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3ND132

KN3AGNPB ENTERED FOR AN INVALID FUNCTION
Explanation: An invalid or unsupported function code was passed to the
KN3AGNPB API.
System Action: The site default or resource specific monitor options are not
modified.
User Response: Log the information displayed for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3ND133

KN3AGNPB NO HASH TABLE ADDRESS FOUND IN THE ACT WORK
AREA
Explanation: The address of the hash table used to look up the KN3AGNPB
control block addresses could not be found in the KN3AYACT work area.
System Action: The site default or resource specific monitor options are not
modified.
User Response: Log the information displayed for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3ND134

KN3AGNPB GET NRE ERROR RETURN=return_code REASON=reason
Explanation: The NRE representing the CCU was not found.
System Action: The NPB task request fails.
User Response: Log the information displayed for problem diagnosis, and
contact Candle Support Services.
Message Type: Internal error.

KN3ND135

NDMT SERVICE REQUEST FAILED
Explanation: The NDM task detected a connection loss with the NCP collector.
System Action: The NDM task terminates.
User Response: Check the availability of the NCPC collector task. The NDM
task attempts to reconnect when available. For more details, see other messages
in the OMEGAMON II for VTAM RKLVLOG.
Message Type: Resource availability error.

KMQxx001E–KOCJ0046

409

KN3ND136

BIND FAILURE FOR NPALU=npalu_name SENSE=sense_code
Explanation: The NCP NPALU collector task was unable to establish a session
with the named NPALU because of the specified sense bytes.
System Action: The session between the NPALU and NCP collector is not
established.
User Response: Look up the sense bytes in the IBM VTAM Messages and
Codes manual.
Message Type: User configuration or resource availability error.

KN3ND137

SESSION LOGON FAILED FOR NPALU=npalu_name
REASON=reason_code
Explanation: The NCP NPALU collector task was unable to establish a session
with the named NPALU because of the specified reason.
System Action: The session between the NPALU and the NCP collector is not
established.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KN3ND138

KN3AGFPF FLOATING POINT FUNCTION FAILED REASON=ABEND
CODE=abend_code
Explanation: The floating point function (FPF) service module abended.
System Action: The FPF task request fails.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KN3ND139

SEVERE ERROR IN OWNER LOOKUP RES=resource_name,
OWNER=owner_name,RETURN=hex_return_code
Explanation: While attempting to insert resource_name into the monitored
topology, the NCP data manager was unable to locate the owning resource
(owner_name). Note the resource and owner names, and the hexadecimal return
code for problem diagnosis.
System Action: Monitoring of this resource fails.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3ND140

NMVRU REJECTED, REASON: reason_code ru_contents
Explanation: While processing TIC3 data, a Network Manager Vector (NMV)
RU was rejected. reason_code is

410

Invalid or unsupported NMVRU.

Associated resource not found.

Resource descriptor not found.

BER envelope not located in NMVRU

Invalid BER envelope

General error processing NMVRU counters.

Candle Products Messages Manual (KLVHS–KONCT)

The contents of the RU appears on the log in character and hexadecimal format
after the message text.
System Action: The TIC3 data is ignored, but processing continues.
User Response: Save the logged information and contact Candle Support
Services.
Message Type: Internal error.
KN3ND212

X.25 VC DEFINITIONS IN ERROR: SUFFIX=suffix, HEXNAME=hexname,
PRFPU=prfpu, PRFLU=prflu
Explanation: The specified names in the X.25 generation are not valid names.
System Action: None.
User Response: Verify that the names in your X.25 generation are valid.
Message Type: Warning.

KN3ND213

GENPUNAM ERRORS DETECTED
Explanation: The PU name generated in message KN3ND212 is not valid.
System Action: None.
User Response: Refer to message KN3ND212.
Message Type: Informational.

KN3ND214

GENLUNAM ERRORS DETECTED
Explanation: The LU name generated in message KN3ND212 is not valid.
System Action: None.
User Response: Refer to message KN3ND212.
Message Type: Informational.

KN3ND215

ERRORS DETECTED DURING X.25 RESOURCE SCANNING FOR
resource.NCP WILL NOT BE MONITORED
Explanation: The specified resource in the X.25 generation cannot be
processed.
System Action: The NCP controlling the resource is not monitored.
User Response: Refer to message KN3ND212, KN3ND213, or KN3ND214.
Verify that the names in your X.25 generation are valid.
Message Type: User configuration error.

KN3ND216

RRT TYPE FOR RESOURCE resource IS NOT IN TABLE - MODULE
(KN3AGNTS) LABEL(TYPETAB)
Explanation: The specified resource in the Resource Resolution Table (RRT)
has an unknown resource type.
System Action: The resource is not monitored, but processing of the RRT
continues.
User Response: Contact Candle Support Services. To resolve the problem,
Candle requires a copy of your RRT.
Message Type: Internal error.

KMQxx001E–KOCJ0046

411

KN3ND217

SCANNING OF NCP ncp_name STARTED
Explanation: The NCP topology build is being processed.
System Action: None.
User Response: None.
Message Type: Informational.

KN3ND218

APPC ENVIRONMENT NOT INITIALIZED.
Explanation: The APPC initialization failed during start-up.
System Action: APPC initialization will retry next interval.
User Response: Check the VTAM configuration definitions.
Message Type: User error.

KN3ND219

APPC ENVIRONMENT TERMINATION FAILED.
Explanation: The APPC termination failed during shutdown.
System Action: None.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KN3ND220

ADDITION OF NCP ncp_name IS COMPLETE.
Explanation: The NCP collector has successfully added the resources of the
named NCP to the topology.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3PN001

OMEGAMON II for VTAM (version_number) — INITIALIZATION
COMPLETED
Explanation: OMEGAMON II for VTAM initialization has completed for the
specified version.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3PN002

ACT STARTED SUCCESSFULLY
Explanation: ACT (Automatic Collector Task) has successfully started. ACT is
required for trending and exception analysis. It is started automatically during
start-up time of OMEGAMON II for VTAM.
System Action: None.
User Response: None.
Message Type: Confirmation.

412

Candle Products Messages Manual (KLVHS–KONCT)

KN3PN003

ACT TERMINATED WITH ERROR — RC(return_code) SC(sense_code)
Explanation: ACT (Automatic Collector Task) terminated with error.
OMEGAMON II for VTAM continues to run without providing trending and
exception analysis. All status lights on the main status panel display IDLE status.
System Action: OMEGAMON II for VTAM continues to run without the ACT.
User Response: Gather up to the preceding 30 minutes of the RKLVLOG and
any dumps that were produced, and contact Candle Support Services.
Message Type: Internal error.

KN3PN004

ETE CONNECTION FAILED — RC(return_code) SC(sense_code)
Explanation: During product initialization, OMEGAMON II for VTAM
encountered an error while attempting to connect the end-to-end response time
environment.
System Action: OMEGAMON II for VTAM continues to run without ETE.
User Response: Verify that the ETE started task is active and that you are
running the correct level of ETE. Also, review the information on enabling ETE in
the OMEGAMON II for VTAM Configuration and Customization Guide. Verify
that all steps were completed accurately. Then, restart OMEGAMON II for VTAM.
If problem persists, gather up to the preceding 30 minutes of the RKLVLOG and
any dumps that were produced, and contact Candle Support Services.
Message Type: Probable user error.

KN3PN005

ETE CONNECTED SUCCESSFULLY
Explanation: OMEGAMON II for VTAM successfully established the ETE
connection during product start-up.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3PN006

userid LOGGED ON — USERWORK(user_workarea_address)
RC(return_code)
Explanation: Specified user ID logged on.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3PN007

OMEGAMON II FOR VTAM (V500) - INITIALIZATION ERROR
Explanation: OMEGAMON II for VTAM encountered an error during start-up.
System Action: OMEGAMON II for VTAM fails to initialize and shuts down.
User Response: Search the RKLVLOG dataset for one of the following
messages: KN3PN020, KN3PN021, KN3PN022, or KN3PN024. These messages
provide more detailed information about the nature of the error.
Message Type: Probable user error.

KMQxx001E–KOCJ0046

413

KN3PN008

LOGON ERROR ENCOUNTERED FOR USER userid — FUNCTION
function_name) RC(return_code) SENSE(sense_code)
USERWORK(user_workarea_address) text_string
Explanation: This message is issued in conjunction with display panel
KN3DFATD when a user logon to OMEGAMON II for VTAM fails.
System Action: Logon fails.
User Response: Perform the action recommended on panel KN3DFATD.
Message Type: Probable user error.

KN3PN011

ERROR IN DIALOG calling_dialog — MODULE(dialog_function)
RC(return_code) SENSE(sense_code) LU(lu_name) APPL(applid)
USERID(userid) text string
Explanation: A generalized message providing diagnostics information when a
call from a dialog to a dialog function fails.
System Action: OMEGAMON II for VTAM will bypass the function and
continue if possible.
User Response: This message usually indicates a problem performing the
requested function. Gather up to the preceding 30 minutes of the RKLVLOG and
any dumps that were produced, and call Candle Support Services.
Message Type: Internal error.

KN3PN012

TABLE SERVICE ERROR IN DIALOG calling_dialog —
FUNCTION(table_services-function) TABLE(table_name) RC(return_code)
LU(lu_name) APPL(applid) USERID(userid) text_string
Explanation: A generalized message providing diagnostics information when a
table service function returns a non-zero return code.
System Action: OMEGAMON II for VTAM will bypasses the requested
function and continues operation.
User Response: This message usually indicates there is a problem performing
the requested table service function. Gather up to the preceding 30 minutes of the
RKLVLOG and any dumps that were produced, and call Candle Support
Services.
Message Type: Internal error.

KN3PN013

PDS ERROR IN DIALOG calling_dialog — FUNCTION(pds_function)
RC(return_code) LU(lu_name) APPL(applid) USERID(userid) text_string
Explanation: A generalized message providing diagnostics information when a
PDS function returns a non-zero return code.
System Action: None.
User Response: This message usually indicates a problem performing the
requested PDS function. The text string information usually explains the nature of
the error. Gather up to the preceding 30 minutes of the RKLVLOG and any
dumps that were produced, and contact Candle Support Services.
Message Type: Internal error.

414

Candle Products Messages Manual (KLVHS–KONCT)

KN3PN014

SAM ERROR IN DIALOG calling_dialog — FUNCTION(SAM_function)
RC(return_code) LU(lu_name) APPL(applid) USERID(userid) text string
Explanation: A generalized message providing diagnostics information when a
SAM (Sequential Access Manager/Dynamic Allocation) service function returns a
non-zero return code.
System Action: OMEGAMON II for VTAM bypasses the SAM function and
continues operation.
User Response: This message usually indicates a problem performing the
requested SAM function. The accompanying text string, if any, can be helpful in
identifying the cause of the problem. Gather up to the preceding 30 minutes of
the RKLVLOG and any dumps that were produced, and contact Candle Support
Services.
Message Type: Internal error.

KN3PN015

ENGINE SERVICES ERROR IN DIALOG calling_dialog —
FUNCTION(engine_services_function) RC(return_code) LU(lu_name)
APPL(applid) USERID(userid) text string
Explanation: A generalized message providing diagnostics information when a
call from a dialog to a dialog function fails.
System Action: OMEGAMON II for VTAM bypasses the function and
continues operation, if possible.
User Response: Gather up to the preceding 30 minutes of the RKLVLOG and
any dumps that were produced, and contact Candle Support Services.
Message Type: Internal error.

KN3PN016

ERROR IN DIALOG error_dialog — LU(lu_name) APPL(applid)
USERID(userid) text_string
Explanation: Error in specified dialog.
System Action: OMEGAMON II for VTAM continues operation.
User Response: Gather up to the preceding 30 minutes of the RKLVLOG and
any dumps that were produced, and contact Candle Support Services.
Message Type: Internal error.

KN3PN017

V500 PRODUCT CONVERSION COMPLETE
Explanation: During product initialization, OMEGAMON II for DB2 detected
the use of a previous version administrator’s monitoring options and converted
them.
System Action: Administrator’s monitoring options were converted.
User Response: None.
Message Type: Confirmation.

KN3PN018

V500 USER CONVERSION COMPLETE FOR user_id
Explanation: During user initialization, OMEGAMON II for VTAM detected the
use of a previous version user response time table and converted it.
System Action: User response time table was converted.
User Response: None.
Message Type: Confirmation.

KMQxx001E–KOCJ0046

415

KN3PN020

OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - APF
AUTHORIZATION FAILED
Explanation: OMEGAMON II for VTAM is not running with APF-authorization.
System Action: OMEGAMON II for VTAM fails to initialize and shuts down.
User Response: Verify that each library in the STEPLIB concatenation for
OMEGAMON II for VTAM is APF-authorized.
Message Type: Probable user error.

KN3PN021

OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - INVALID
VTAM LEVEL DETECTED
Explanation: OMEGAMON II for VTAM was started under an unsupported
release of VTAM.
System Action: OMEGAMON II for VTAM fails to initialize and shuts down.
User Response: Contact Candle Support Services to order the proper
maintenance for your VTAM release.
Message Type: Probable user error.

KN3PN022

OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - UNABLE
TO OPEN CNM ACB. ACBERFLG(acberr_name)
Explanation: OMEGAMON II for VTAM was unable to open the ACB used for
communication network management (CNM) communication with VTAM.
acberr_name contains the contents of the ACBERFLG field of the ACB, in
hexadecimal.
System Action: OMEGAMON II for VTAM fails to initialize and shuts down.
User Response: Look up the meaning of acberr_name in the IBM publication
VTAM Programming. The following are some common values for acberr_name:
58

APPLID is already opened by another ACB.

APPLID is not defined to VTAM. Verify that the major node
containing the APPL statement referenced in
RKANPAR(KN3CNMAP) has been varied active to VTAM.

Correct the problem as indicated, and contact Candle Support Services.
Message Type: Probable user error.
KN3PN023

OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE - UNABLE
TO ACTIVATE PMI EXIT. ERROR(pmi_error)
Explanation: OMEGAMON II for VTAM was unable to activate the
Performance Monitor Interface exit in a VTAM 4.3 environment. pmi_error
contains the error code as indicated by VTAM in the IST985I message.
System Action: OMEGAMON II for VTAM fails to initialize and shuts down.
User Response: Look up the meaning of pmi_error in the IBM publication
VTAM Message and Codes. A common value for pmi_error is
20

Unable to load the exit module. Verify that the OMEGAMON II for
VTAM load library is part of the VTAMLIB concatenation within the
VTAM start-up JCL.

For other values of pmi_error, contact Candle Support Services.
Message Type: Probable user error.

416

Candle Products Messages Manual (KLVHS–KONCT)

KN3PN024

OMEGAMON II FOR VTAM (V500) INITIALIZATION FAILURE RC(return_code) SC(sense_code)
Explanation: OMEGAMON II for VTAM initialization failed. return_code is the
return code from the initialization process; sense_code is the sense code.
System Action: OMEGAMON II for VTAM fails to initialize and shuts down.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KN3PN025

NCP GLOBAL OPTIONS TABLE CONVERSION COMPLETE
Explanation: During initialization, OMEGAMON II for VTAM converted the
NCP global options table for use with the user-specified NCP topology update
interval feature. This message is issued one time to confirm the conversion.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3PN026

THE TREND RECORDING INTERVAL (interval) IS LESS THAN THE NCP
COLLECTION INTERVAL (interval). TREND RECORDING FOR NCP
RESOURCES HAS BEEN DISABLED.
Explanation: The NCP trend recording interval must be greater than or equal to
the NCP collection interval. At OMEGAMON II for VTAM initialization, NCP trend
recording is disabled if the NCP collection interval is greater than the global trend
recording interval.
System Action: NCP trend recording is disabled.
User Response: Use the Global Monitoring Options panel to increase the trend
recording interval to a value greater than or equal to the NCP collection interval
and then re-enable the NCP trend recording option, or use CICAT
reconfiguration to decrease the NCP collection interval to a value less than or
equal to the trend recording interval. Decreasing the NCP collection interval
requires a restart of OMEGAMON II for VTAM.
Message Type: User specification error.

KN3PN027

OMEGAMON II for VTAM STACK ERROR DETECTED
Explanation: An error was detected either releasing or obtaining stack storage.
System Action: The task abends with a system dump.
User Response: Log the diagnostic information and contact Candle Support
Services
Message Type: Internal error.

KN3PN028

OMEGAMON II for DB2 FOR VTAM EXTERNAL FUNCTION LEVEL
SECURITY ENABLED
Explanation: OMEGAMON II for VTAM is configured to use an external
security package to control access to certain product functions.
System Action: None.
User Response: None.
Message Type: Confirmation.

KMQxx001E–KOCJ0046

417

KN3PN029

OMEGAMON II for DB2 FOR VTAM INTERNAL FUNCTION LEVEL
SECURITY ENABLED
Explanation: OMEGAMON II for VTAM is configured to use an internal facility
to control access to certain product functions.
System Action: None.
User Response: None.
Message Type: Confirmation.

KN3PN030

MEMBER mbr_name NOT FOUND IN RKANPAR
Explanation: An error occurred during the configuration of external function
level security.
System Action: Initialization continues using internal facilities to control access
to product functions.
User Response: Review configuration steps for function level security. If the
problem cannot be resolved, contact Candle Support Services.
Message Type: Error.

KN3SD001

SDM LOGON INITIATED FOR PRODUCT(SDM_product) —
SESSION(SDM_session_name) SDMAPPL(SDM_applid)
SYSTERM(SDM_luname) REFRESH(SDM_refresh_interval)
TRIGGER(SDM_hot_key)
Explanation: A message indicating an SDM (Status Data Manager) session has
been established between an SDM product (OMEGAVIEW or Status Monitor)
and OMEGAMON II for VTAM.
The parameters have the following meaning:
SDM_product

Product that establishes the SDM session: OMEGAVIEW or
Status Monitor.

SDM_session_name

Name assigned to this session by the SDM product.

SDM_applid

Applid defined in the SDM product with which
OMEGAMON II for VTAM can establish a session to emit
SDM status to the SDM product.

SDM_luname

Name of LU that has established the session with
OMEGAMON II for VTAM.

SDM_refresh_interval

Auto-update interval requested by the SDM product.

SDM_hot_key

Key used to return to the SDM.

System Action: None.
User Response: None.
Message Type: Information.

418

Candle Products Messages Manual (KLVHS–KONCT)

KN3SD002

ERROR PROCESSING AN SDM FUNCTION IN DIALOG calling_dialog —
APPL(SDM_application) SESSION(SDM_session_name)
FUNCTION(SDM_function_name) STATUS_ITEM(SDM_status_item)
RC(return_code)
Explanation: A generalized message generated only when there is a non-zero
return code from an SDM function call. The parameters have the following
meaning:
calling_dialog

OMEGAMON II for VTAM dialog that calls this SDM function.

SDM_application

Applid defined in the SDM product with which OMEGAMON II
for VTAM established the session to emit SDM status to the
SDM product.

SDM_session_name

Name assigned to this session by the SDM product.

SDM_function_name SDM function requested.
SDM_status_item

One of the status light items to be emitted to the SDM product,
such as the CTC TNSTATS light or the NCP TNSTATS light.

return_code

Return code from the SDM function.

System Action: The SDM session was not established, but OMEGAMON II for
VTAM continues to operate.
User Response: Make sure that the SDM definitions are correct according to
the OMEGAMON II for VTAM Configuration and Customization Guide and the
customization guide for OMEGAVIEW or Status Monitor (depending on the
product installed).
Message Type: Probable user error.
KN3SD003

[ENHANCED] | [ORIGINAL] ZOOM ACTIVATED
Explanation: The OMEGAVIEW enhanced or original zoom function has been
activated.
System Action: None.
User Response: None.
Message Type: Information.

KO41031

Situation &1 is true.
Explanation: Situation &1 is occurring. This situation continues to be true until
message KO41032 is written to the Candle Management Server (CMS) product
log.
User Response: If you have AUTOMATED FACILITIES, you may want to
define or start a policy.
Severity: 0
System Programmer Response:No

KO41032

Situation &1 is no longer true.
Explanation: Situation &1 is no longer occurring.
User Response: View all error messages that were logged to the CMS product.
Message KO41031 shows you when situation &1 became true.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

419

KO41034

Monitoring for situation &1 ended.
Explanation: A user or program ended a running situation. You can also end all
running situations with the END CMS command. AUTOMATED FACILITIES
policies may also end situations.
Severity: 0
System Programmer Response:No

KO41035

Object &1 changed by &2.
Explanation: Object &1 was changed by object &2.
Severity: 10
System Programmer Response:No

KO41036

Monitoring for situation &1 started.
Explanation: You may start a situation using a start situation command. All
situations defined to autostart do so during the start of Candle Management
Server (CMS) processing. AUTOMATED FACILITIES policies may also start
situations.
Severity: 0
System Programmer Response:No

KO41037

Situation &1 is no longer true.
Explanation: Situation &1 is no longer occurring.
User Response: View all error messages that were logged to the Candle
Management Server product log. Message KO41031 shows you when situation
&1 became true.
Severity: 80
System Programmer Response:Immediate

KO41038

Situation &1 is true.
Explanation: A situation, such as CPU greater than 90%, is occurring at the
time and date indicated. The situation continues to be true until message
KO41032 is written to the log.
User Response: Try to find out why the situation is occurring and take
appropriate action to correct the situation. If you have AUTOMATED
FACILITIES, for example, you could define or start a policy.
Severity: 80
System Programmer Response:Immediate

KO41039

Error in request &1. Status: &2. Reason: &3.
Explanation: The Candle Management Server program encountered an error.

420

Candle Products Messages Manual (KLVHS–KONCT)

User Response: The following lists possible error codes. If a reason code
appears that is not on this list, note it and contact your service representative.
Error
Code

Description

User Response

1131

Embedded situation not found.

Check to make sure that all embedded
situations exist. If they do, call your
service representative.

1133

Invalid attribute name.

Ensure that the attribute name is valid
and try again. If problem occurs again,
contact your service representative.

1134

Configuration file in library not
found or damaged.

Install the product again.

1136

Object not found.

Delete and create the object again. If
problem occurs again, contact your
service representative.

1145

Invalid situation name supplied.

Contact your service representative.

1168

More than 10 levels of embedded
situations found.

Simplify your situation.

1174

Cannot retrieve current attributes for
event type situation.

Simplify your situation.

1178

Situation definition is too complex
and exceeds system capacity.

Simplify your situation.

2013

String scan with space inside the
string.

Situation Editor accepts a string
without quotes. However, single
quotes are required around
multiple-word text values.

Severity: 20
System Programmer Response:Unattended
KO41041

Enterprise situation &1 is true.
Explanation: A situation, such as CPU greater than 90%, is occurring at the
time and date indicated. The situation continues to be true until message
KO41042 is written to the log.
Severity: 0
System Programmer Response:No

KO41042

Enterprise situation &1 is no longer true.
Explanation: The status is no longer true for this situation.
User Response: View all error messages that were logged to the Candle
Management Server (CMS) product log. Message KO41041 shows you when
situation &1 became true.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

421

KO41044

Monitoring for enterprise situation &1 ended.
Explanation: A user or program ended a running situation. All running
situations end when a user issues an END CMS command. AUTOMATED
FACILITIES policies may also end situations.
Severity: 0
System Programmer Response:No

KO41046

Monitoring for enterprise situation &1 started.
Explanation: A user or program started a previously inactive situation. All
situations defined to autostart do so during a START CMS command.
AUTOMATED FACILITIES policies may also start situations.
Severity: 0
System Programmer Response:No

KO42076

Operator reply required for Policy &1.
Severity: 0
System Programmer Response:No

KO46254

Situation &1 reset.
Severity: 0
System Programmer Response:No

KO46255

Situation definition &1 updated by &2.
Explanation: The situation definition was updated by the user.
Severity: 0
System Programmer Response:No

KO46256

Situation definition &1 created by &2.
Explanation: The situation definition was created by the user.
Severity: 0
System Programmer Response:No

KO46257

Situation definition &1 deleted by &2.
Explanation: The situation definition was deleted by the user.
Severity: 0
System Programmer Response:No

KO46258

Predicate compare value &2 for predicate &3 not valid.
Explanation: Predicate compare value &2 for predicate &3 is not valid. It must
be numeric.
User Response: Change the compare value & 2 to a numeric.
Severity: 0
System Programmer Response:No

KO46259

Name not allowed for message queue library name.
Explanation: Select a message queue in another library.
Severity: 0
System Programmer Response:No

422

Candle Products Messages Manual (KLVHS–KONCT)

KO46260

Predicate data cannot contain blank field.
Explanation: The first parameter for the PDT field cannot contain a blank.
User Response: Remove the blank in the parameter in the PDT field.
Severity: 0
System Programmer Response:No

KO46261

Only one selection allowed.
Explanation: More than one option was selected. Only one option can be
selected at a time.
User Response: Blank out the additional selections and try again.
Severity: 0
System Programmer Response:No

KO46262

Situation definition &1 printed.
Explanation: You printed situation &1.
User Response: View the printed situation definition.
Severity: 0
System Programmer Response:No

KO46263

Candle Management Server (CMS) data queue error was detected.
Explanation: The error message received was &1.
Severity: 0
System Programmer Response:No

KO46264

Time portion of monitor interval not valid.
Explanation: For the TIMEFRQ parameter, the time portion of the monitor
interval cannot be less than 000030 if the day portion contains zero.
User Response: Increase the monitor interval to at least 000030.
Severity: 0
System Programmer Response:No

KO46265

Attribute &2 not allowed.
Explanation: Attribute &2 is not allowed in conjunction with attribute &3 in a
predicate. Some attributes cannot be combined in a predicate to form a situation.
User Response: Refer to the appropriate Candle Management Server (CMS)
Reference Manual to determine if a particular attribute can be combined with
another.
Severity: 0
System Programmer Response:No

KO46266

Date and time portions of monitor interval must both be zero.
Explanation: For the TIMEFRQ parameter, the day and time portions of the
monitor interval must both be zero if all attributes in the situation definition are
notification attributes with the same prefix. Attributes can be of two types:
® Sampled
®

Notification

KMQxx001E–KOCJ0046

423

User Response: Refer to the appropriate Candle Management Server (CMS)
Reference Manual to determine the type of a particular attribute.
Severity: 0
System Programmer Response:No
KO46267

Situation definition validation did not occur.
Explanation: You attempted to use *AVG with a non-integer attribute.
Severity: 40
System Programmer Response:Immediate

KO46268

Situation definition &1 displayed.
Severity: 0
System Programmer Response:No

KO46269

Name &1 cannot contain blanks.
Explanation: The name &1 contains imbedded blanks. Remove imbedded
blanks from the name.
Severity: 0
System Programmer Response:No

KO48001

AUTOMATED FACILITIES started.
Severity: 0
System Programmer Response:No

KO48008

AUTOMATED FACILITIES received request to stop.
Severity: 0
System Programmer Response:No

KO48009

Policy &1 ended.
Explanation: The policy has completed a pass through its activity graph. No
activities are running. Depending on its completion option, the policy then either
deactivates or starts another pass through the activity graph.
Severity: 0
System Programmer Response:No

KO48010

Policy &1 started.
Explanation: The policy is starting a pass through its activity graph. All activities
having no predecessors are in the running state; all other activities are in the
pre-run state. The pass completes when no activities remain in the running state.
At that time, message KO48009 is issued. The policy may also be deactivated
before it finishes running.
Severity: 0
System Programmer Response:No

KO48071

Policy &1 activated.
Explanation: The policy has been activated. This may occur for three reasons:

424

The policy is marked to autostart and STRAF is being processed.

A user issues a start policy command or the equivalent menu option against
this policy.

Candle Products Messages Manual (KLVHS–KONCT)

Another policy contains a CHANGE_POLICY or embedded policy activity
that activates this policy.

The policy now starts, runs, ends, and then either restarts or deactivates based on
its completion option.
Severity: 0
System Programmer Response:No
KO48073

Policy &2, activity &1 has started.
Explanation: Activity started in the policy.
Severity: 0
System Programmer Response:No

KO48074

Policy &2, activity &1 ended with end code &3 reason &4.
Explanation: Activity &1 in policy &2 has finished.
User Response: See the appropriate AUTOMATED FACILITIES Reference
Manual for explanations of end codes.
Severity: 0
System Programmer Response:No

KO48076

Policy &1 has deactivated itself.
Explanation: The policy ended and its “restart upon completion” option was set
to No. The policy ceases all operations.
User Response: Activate the policy again. To make the policy restart upon
completion, change the policy definition so that the restart option is *YES and
then activate it.
Severity: 0
System Programmer Response:No

KO48077

Policy &1 deactivated by external request.
Explanation: An external agent (user or other policy) requested the policy to
deactivate. The policy immediately ceases all operations, canceling activities in
progress.
Severity: 0
System Programmer Response:No

KO48078

Policy &1 updated by &2.
Explanation: Policy &1 has been updated by policy &2.
Severity: 0
System Programmer Response:No

KO48079

Activity &1 in policy &2 updated by &3.
Explanation: The policy has been updated by the user.
Severity: 0
System Programmer Response:No

KO48080

Ranking group &1 updated by &2.
Explanation: The ranking group has been updated by the user.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

425

KO48081

Ranking group entry &1 in ranking group &2 updated by &3.
Explanation: The tanking group entry in ranking group has been updated by
the user.
Severity: 0
System Programmer Response:No

KO48082

Policy &1 created by &2.
Explanation: The policy has been created by the user.
Severity: 0
System Programmer Response:No

KO48083

Activity &1 in policy &2 created by &3.
Explanation: Activity in the policy has been created by a user.
Severity: 0
System Programmer Response:No

KO48084

Ranking group &1 created by &2.
Explanation: The ranking group has been created by the user.
Severity: 0
System Programmer Response:No

KO48085

Ranking group entry &1 in ranking group &2 created by &3.
Explanation: The ranking group entry in the ranking group has been created by
the user.
Severity: 0
System Programmer Response:No

KO48086

Policy &1 deleted by &2.
Explanation: The policy has been deleted by the user.
Severity: 0
System Programmer Response:No

KO48087

Activity &1 in policy &2 deleted by &3.
Explanation: Activity in the policy has been deleted by the user.
Severity: 0
System Programmer Response:No

KO48088

Ranking group &1 deleted by &2.
Explanation: The ranking group has been deleted by the user.
Severity: 0
System Programmer Response:No

KO48089

Ranking group entry &1 in ranking group &2 deleted by &3.
Explanation: The ranking group entry in the ranking group has been deleted by
the user.
Severity: 0
System Programmer Response:No

426

Candle Products Messages Manual (KLVHS–KONCT)

KO48090

Policy &1 has deactivated. Restart limit exceeded.
Explanation: The policy was defined to restart upon completion and did so
more than 5 times in a 10-minute interval. Since the policy was defined with the
“limit restarts” option set to *YES, the policy deactivates instead of restarting. The
policy immediately ceases all operations.
User Response: View the error messages that were logged to the product log to
determine what the policy was doing. If a logic error was causing the policy to fire
too frequently, correct the involved definitions and reactivate the policy.
Severity: 0
System Programmer Response:No

KO48091

Changing priority for job &1 (job number &2) to &3.
Explanation: Policy &4, activity &5 is changing the priority for job &1 to &3.
Severity: 0
System Programmer Response:No

KO48092

Changing job queue for job &1 (job number &2) to &3.
Explanation: Policy &4, activity &5 is changing the job queue for job &1 to &3.
Severity: 0
System Programmer Response:No

KO48093

Changing time slice for job &1 (job number &2) to &3.
Explanation: Policy &4, activity &5 is changing the time slice for job &1 to &3.
Severity: 0
System Programmer Response:No

KO48095

Changing output queue for job &1 (job number &2) to &3.
Explanation: Policy &4, activity &5 is changing the output queue for job &1
to &3.
Severity: 0
System Programmer Response:No

KO48096

Policy &3, activity &4 - Changing policy &1 to status &2.
Explanation: Policy &3, activity &4 is changing policy &1 to status &2.
Severity: 0
System Programmer Response:No

KO48097

Changing activity level for pool &1 to &2.
Explanation: Policy &3, activity &4 is changing the activity level for pool &1 to
&2.
Severity: 0
System Programmer Response:No

KO48098

Changing size for pool &1 to &2.
Explanation: Policy &3, activity &4 is changing the size for pool &1 to &2.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

427

KO48099

Policy &3, activity &4 - Changing situation &1 to status &2.
Explanation: Policy &3, activity &4 is changing situation &1 to status &2.
Severity: 0
System Programmer Response:No

KO48106

Ending job &1 (job number &2).
Explanation: Policy &3, activity &4 is ending job &1.
Severity: 0
System Programmer Response:No

KO48110

Policy &2, activity &3 - Evaluating situation &1.
Explanation: Policy &2, activity &3 is evaluating situation &1.
Severity: 0
System Programmer Response:No

KO48112

Holding job &1 (job number &2).
Explanation: Policy &3, activity &4 is holding job &1.
Severity: 0
System Programmer Response:No

KO48119

Releasing job &1 (job number &2).
Explanation: Policy &3, activity &4 is releasing job &1.
Severity: 0
System Programmer Response:No

KO48139

Policy &1, activity &2 - Writing data to user automation data queue.
Explanation: Policy &1, activity &2 is writing data to a user automation data
queue.
Severity: 0
System Programmer Response:No

KO48140

Policy &2, activity &3 - Proceeding to user choice activity: &1
Explanation: Policy &2, activity &3 is proceeding to user choice activity &1.
Severity: 0
System Programmer Response:No

KO48141

Policy &2, activity &3 - Presenting user choice to &1.
Explanation: Policy &2, activity &3 is presenting user choice to &1.
Severity: 0
System Programmer Response:No

KO48142

Policy &4, activity &5 - Transferring user choice from &1 to &2 at request
of &3.
Explanation: Policy &4, activity &5 is transferring user choice from &1 to &2 at
request of &3.
Severity: 0
System Programmer Response:No

428

Candle Products Messages Manual (KLVHS–KONCT)

KO48143

Policy &3, activity &4 - Escalating user choice from &1 to &2 due to
timeout.
Explanation: Policy &3, activity &4 is escalating user choice from &1 to &2 due
to timeout.
Severity: 0
System Programmer Response:No

KO48144

Policy &4, activity &5 - Escalating user choice from &1 to &2 at request of
&3.
Explanation: Policy &4, activity &5 is escalating user choice from &1 to &2 at
request of &3.
Severity: 0
System Programmer Response:No

KO48145

Policy &1, activity &2 - Canceling user choice action due to timeout.
Explanation: Policy &1, activity &2 is canceling user choice action due to
timeout.
User Response: Change the timeout parameters.
Severity: 0
System Programmer Response:No

KO48148

Policy &2, activity &3 - Waiting for &1 seconds.
Explanation: Policy &2, activity &3 is waiting for &1 seconds.
Severity: 0
System Programmer Response:No

KO48150

Policy &2, activity &3 - Running policy &1.
Explanation: Policy &2, activity &3 is running policy &1.
Severity: 0
System Programmer Response:No

KO48151

Policy &2, activity &3 - Waiting for event from situation &1.
Explanation: Policy &2, activity &3 is waiting for event from situation &1.
Severity: 0
System Programmer Response:No

KO48152

Situation &1 could not find message queue &2.
Explanation: The message queue specified to receive reports of situations firing
could not be found.
User Response: Create the queue or add the library where the queue exists.
Severity: 20
System Programmer Response:No

KO48153

Policy &3, activity &4 - Executing command at &2: &1
Severity: 0
System Programmer Response:No

KO48154

Execute command: &1
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

429

KO48155

Execute command: &1 and &2 additional commands of the same form.
Severity: 0
System Programmer Response:No

KO48156

Not able to start monitoring for situation &1.
Severity: 0
System Programmer Response:No

KO48686

&1
Severity: 0

KO49014

Situation list printed.
Severity: 0
System Programmer Response:No

KO49015

Situation &1 imbedded in situation &2. Not deleted.
Explanation: The situation you have requested to delete is imbedded in another
situation.
User Response: Either delete situation &2 or change it so that it does not
reference situation &1.
Severity: 0
System Programmer Response:No

KO49016

Situation &1 imbedded in policy &2. Not deleted.
Explanation: The situation you requested to delete is imbedded in a policy.
User Response: Either delete policy &2 or change it so that it does not
reference situation &1.
Severity: 20
System Programmer Response:No

KO49017

Policy &1 imbedded in policy &2. Not deleted.
Explanation: The policy you requested to delete is imbedded in another policy.
User Response: Either delete policy &2 or change it so that it does not
reference policy &1.
Severity: 20
System Programmer Response:No

KO49019

Candle Management Server (CMS) log not displayed
Explanation: Not able to display the message queue for CMS.
User Response: View the joblog for specific reasons.
Severity: 0
System Programmer Response:No

KO49020

Situation validation failed. *MAX cannot be used with this attribute.
Explanation: Attempt to use *MAX with a non-integer attribute.
Severity: 40
System Programmer Response:No

430

Candle Products Messages Manual (KLVHS–KONCT)

KO49021

Situation validation failed. *MIN cannot be used with this attribute
Explanation: Attempt to use *MIN with a non-integer attribute.
Severity: 40
System Programmer Response:No

KO49022

Situation validation failed. This operator cannot be used with this
attribute.
Severity: 40
System Programmer Response:No

KO49023

Situation validation failed. *COUNT not valid for this attribute.
Explanation: Attempt to use *COUNT with a non-integer attribute.
Severity: 40
System Programmer Response:No

KO49024

Situation validation failed. *STR cannot be used with this attribute.
Explanation: Attempt to use *STR with a non-string attribute.
Severity: 40
System Programmer Response:No

KO49025

Situation validation failed. Invalid compare value for *STR.
Severity: 40
System Programmer Response:No

KO49026

Situation validation failed. *TIME cannot be used with this attribute.
Explanation: Attempt to use *TIME with a non-time attribute
Severity: 40
System Programmer Response:No

KO49027

Situation validation failed. Compare value not valid for *TIME.
Explanation: Format of *TIME compare value was not entered correctly.
User Response: Enter the correct format for the *TIME compare value. Refer
to the appropriate Candle Management Server (CMS) Reference Manual for
details.
Severity: 40
System Programmer Response:No

KO49028

Candle Management Server (CMS) did not complete startup.
Explanation: Security level validation did not complete.
User Response: View the joblog for additional messages.
Severity: 0
System Programmer Response:No

KO49029

Situation &1 not a candidate for get current attribute.
Explanation: Situation &1 contains event-driven attribute.
User Response: Do not attempt to add a "get current attribute" for this
situation.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

431

KO49030

Situation validation did not complete. *SUM cannot be used with this
attribute.
Explanation: Attempted to use *SUM with a non-integer attribute.
Severity: 0
System Programmer Response:No

KO49031

Status list printed.
Explanation: View the status list.
Severity: 0

KO49032

Situation status printed.
Explanation: View the printed situation status.
Severity: 0

KO49033

Nothing printed; list is empty.
Severity: 0

KO49034

Situation &1 is an enterprise situation. Not deleted.
Explanation: Situation &1 is an enterprise situation that can be deleted only
from OMEGAVIEW
User Response: Delete situation &1 from OMEGAVIEW.
Severity: 0
System Programmer Response:No

KO49035

Object &1 in library &2 type &3 not found or not usable.
Explanation: The startup process cannot continue because object &1 could not
be used.
User Response: Check library &2 for &3 and fix problem. If not found, install
the Candle Management Server (CMS) again.
Severity: 0
System Programmer Response:No

KO49036

Situation &1 is an enterprise situation. Not changed.
Explanation: Situation &1 is an enterprise situation that can be changed only
from OMEGAVIEW.
User Response: Change situation &1 from OMEGAVIEW.
Severity: 0
System Programmer Response:No

KO49037

Candle Management Server (CMS) or AUTOMATED FACILITIES
command failure occurred.
Explanation: An error occurred in an Candle Management Server (CMS) or an
AUTOMATED FACILITIES command.
User Response: To determine the cause, view the CMS job log, restart CMS,m
and fix the problem accordingly.
Severity: 0
System Programmer Response:No

432

Candle Products Messages Manual (KLVHS–KONCT)

KO49038

Situation validation failed; cannot use *SNGPDT predicate with *SIT
predicate.
Explanation: Attempted to create a situation with a single situation predicate. A
*SIT predicate must have a minimum of two predicates.
User Response: Add more predicates using *AND or *OR in the predicate
relation.
Severity: 0
System Programmer Response:No

KO49040

Situation &1 is not a candidate for the Reset option.
Explanation: Situation &1 is a sample-driven situation and thus cannot be reset.
Severity: 0

KO49041

Situation &1 ended abnormally.
Explanation: An error was encountered on this situation or possibly on another
situation for which a similar message is being issued. The error required this
situation and the situation in error (if different) to be shut down. Some examples
of the types of errors that can cause this condition follow:
®

The situation predicate may not have sufficiently narrowed the scope of things
to be examined. This may have resulted in overloading the Candle
Management Server (CMS) with too much data.

The situation may have used *ACGJB or *SEC attributes without having the
necessary SYSVALs set, or without having set up the necessary journals and
journal receivers.

A job or subsystem required to evaluate the situation may have been ended
by an operator.

The above is not an exhaustive list of possible errors.
System Action: If the situation was started explicitly by an operator, then the
situation is shut down. If the situation was running in an AUTOMATED
FACILITIES policy, as a *SIT activity type or an *EVALUATE_SITUATION
activity program, then the activity containing the situation ends with a
*PROBLEM endcode.
User Response: Look for a KO49044 log entry issued at about the same time
as this message. That log entry indicates which CMS job encountered the error.
The job may still be active. Examine the joblog for clues about the ultimate cause
of the error. Correct the situation in error before attempting to restart it.
Severity: 40
System Programmer Response:No
KO49042

Situation &1 is occurring; &2 events available for status.
Explanation: The event is occurring; the data of 10 events is kept and the
previous events are deleted.
Severity: 0
System Programmer Response:Immediate

KMQxx001E–KOCJ0046

433

KO49043

Situation &1 is occurring; &2 events available for status; oldest events
discarded.
Explanation: The event is occurring; the data of 10 events is kept and the
previous events are deleted.
Severity: 0
System Programmer Response:Immediate

KO49044

Job &1 encountered an error.
Explanation: An error was encountered by this Candle Management Server
(CMS) job. Some examples of the types of errors that may have been
encountered follow:
®

A situation predicate may not have sufficiently narrowed the scope of things
to be examined. This may have resulted in overloading CMS with too much
data.

A situation may have used *ACGJB or *SEC attributes without having the
necessary SYSVALs set, or without having set up the necessary journals and
journal receivers.

A job or subsystem required to evaluate a situation may have been ended by
an operator.

The above is not an exhaustive list of possible errors.
User Response: Examine the joblog for &1 to find the error or errors. Correct
the errors before attempting the same functions again.
Severity: 40
System Programmer Response:No
KO4SRV001

Candle Management Server (CMS) startup in progress.
Severity: 0
System Programmer Response:No

KO4SRV002

Candle Management Server (CMS) startup job already running.
Explanation: You tried to start CMS but it is already in the process of starting.
Another user has already issued the start command.
User Response: Wait until the earlier startup process is complete and then try
again.
Severity: 0
System Programmer Response:No

KO4SRV003

Starting Candle Management Server (CMS) network server.
Severity: 0
System Programmer Response:No

KO4SRV004

Network server active.
Severity: 0
System Programmer Response:No

434

Candle Products Messages Manual (KLVHS–KONCT)

KO4SRV005

Starting Candle Management Server (CMS) network requesters.
Severity: 0
System Programmer Response:No

KO4SRV006

Network requesters active.
Severity: 0
System Programmer Response:No

KO4SRV007

Starting Candle Management Server (CMS) local directory server.
Severity: 0
System Programmer Response:No

KO4SRV008

Local directory server active.
Severity: 0
System Programmer Response:No

KO4SRV009

Starting Candle Management Server (CMS) global directory server.
Severity: 0
System Programmer Response:No

KO4SRV010

Global directory server active.
Severity: 0
System Programmer Response:No

KO4SRV011

Starting Candle Management Server (CMS) data collection server.
Severity: 0
System Programmer Response:No

KO4SRV012

Data collection server active.
Severity: 0
System Programmer Response:No

KO4SRV013

Starting Candle Management Server (CMS) network data collection
server.
Severity: 0
System Programmer Response:No

KO4SRV014

Network data collection server active.
Severity: 0
System Programmer Response:No

KO4SRV015

Starting Candle Management Server (CMS) situation monitor.
Severity: 0
System Programmer Response:No

KO4SRV016

Situation monitor active.
Severity: 0
System Programmer Response:No

KO4SRV017

Candle Management Server (CMS) shutdown in progress.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

435

KO4SRV018

Stopping Candle Management Server (CMS) situation monitor.
Severity: 0
System Programmer Response:No

KO4SRV019

Situation monitor stopped.
Severity: 0
System Programmer Response:No

KO4SRV020

Stopping Candle Management Server (CMS) data collection server.
Severity: 0
System Programmer Response:No

KO4SRV021

Data collection server stopped.
Severity: 0
System Programmer Response:No

KO4SRV022

Stopping Candle Management Server (CMS) network data collection
server.
Severity: 0
System Programmer Response:No

KO4SRV023

Network data collection server stopped.
Severity: 0
System Programmer Response:No

KO4SRV024

Stopping Candle Management Server (CMS) network services.
Severity: 0
System Programmer Response:No

KO4SRV025

Network services stopped.
Severity: 0
System Programmer Response:No

KO4SRV026

Stopping Candle Management Server (CMS) global directory server.
Severity: 0
System Programmer Response:No

KO4SRV027

Global directory server stopped.
Severity: 0
System Programmer Response:No

KO4SRV028

Stopping Candle Management Server (CMS) local directory server.
Severity: 0
System Programmer Response:No

KO4SRV029

Local directory server stopped.
Severity: 0
System Programmer Response:No

436

Candle Products Messages Manual (KLVHS–KONCT)

KO4SRV030

Candle Management Server (CMS) shutdown completed.
Explanation: CMS was requested to shut down by the END CMS command.
Severity: 0
System Programmer Response:No

KO4SRV031

Candle Management Server (CMS) startup job already on job queue.
Explanation: The job queue already contains an CMS startup job.
User Response: Make sure the library subsystem is active and the job queue is
not held.
Severity: 0
System Programmer Response:No

KO4SRV032

Candle Management Server (CMS) startup complete.
Explanation: All required components of CMS are active in the library
subsystem.
Severity: 60
System Programmer Response:No

KO4SRV033

Candle Management Server (CMS) no longer active.
Explanation: CMS has ended since this command was last used.
User Response: View all error messages that were logged to the CMS product
log and then restart CMS.
Severity: 60
System Programmer Response:No

KO4SRV034

Candle Management Server (CMS) requested to end during startup.
Explanation: Before CMS startup processing completed, an end CMS
command was issued.
User Response: Restart CMS.
Severity: 0
System Programmer Response:No

KO4SRV035

Starting Candle Management Server (CMS) worklist manager.
Severity: 0
System Programmer Response:No

KO4SRV036

Worklist manager active.
Severity: 0
System Programmer Response:No

KO4SRV037

Stopping Candle Management Server (CMS) worklist manager.
Severity: 0
System Programmer Response:No

KO4SRV038

Worklist manager ended.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

437

KO4SRV039

Starting Candle Management Server (CMS) data collection event
notification.
Severity: 0
System Programmer Response:No

KO4SRV040

Data collection event notification active.
Severity: 0
System Programmer Response:No

KO4SRV041

Starting Candle Management Server (CMS) situation monitor status
queuing.
Severity: 0
System Programmer Response:No

KO4SRV042

Situation monitor status queuing active.
Severity: 0
System Programmer Response:No

KO4SRV043

Ending Candle Management Server (CMS) data collection event
notification.
Severity: 0
System Programmer Response:No

KO4SRV044

Data collection event notification ended.
Severity: 0
System Programmer Response:No

KO4SRV045

Stopping Candle Management Server (CMS) situation monitor status
queuing.
Severity: 0
System Programmer Response:No

KO4SRV046

Situation monitor status queuing ended.
Severity: 0
System Programmer Response:No

KO4SRV047

Validation could not be performed.
Explanation: Candle Management Server (CMS) is not active. Validation
requires CMS to be active.
User Response: Activate CMS.
Severity: 0
System Programmer Response:No

KO4SRV048

Candle Management Server (CMS) did not start. Status codes: &1/&2.
Explanation: CMS did not start successfully.
User Response: View all error messages that were logged to the CMS product
log. Restart the CMS.
Severity: 40
System Programmer Response:Unattended

438

Candle Products Messages Manual (KLVHS–KONCT)

KO4SRV049

Candle Management Server (CMS) started.
Severity: 0
System Programmer Response:No

KO4SRV050

Startup failed due to errors in environment definitions.
Explanation: Startup parameter file &1 in library &2 does not contain all
required parameter fields, and startup is ended. The startup parameter file &1 in
library &2 contains fewer parameter fields than the startup program expects.
User Response: Verify installation procedures. You can also install and then try
to start Candle Management Server (CMS) again.
Severity: 50
System Programmer Response:Unattended

KO4SRV051

Candle Management Server (CMS) cannot process this command.
Explanation: This command returned completion code &1. Completion codes
and their meanings are:
Completion
Code

Meaning

The CMS program is not active.

This command is not at the correct release level.

The services that this command requests are busy.

User Response: If the CMS is not active, start it. If the command is not at the
correct release level, make sure all required maintenance is installed and try
again. If the requested services are busy, try the command again.
Severity: 30
System Programmer Response:No
KO4SRV052

Candle Management Server (CMS) not active.
Explanation: The system received a CMS command, but CMS has not been
started.
User Response: Check the message log to identify which command was sent.
Start CMS and then try the command again.
Severity: 30
System Programmer Response:No

KO4SRV053

Candle Management Server (CMS) already active.
Explanation: The START CMS command has already been issued and the
CMS is already active.
Severity: 20
System Programmer Response:No

KMQxx001E–KOCJ0046

439

KO4SRV054

Job &2/&3 submitted.
Explanation: Job &2/&3 submitted to job queue &4 in &5. The job that starts
the Candle Management Server (CMS) program has submitted the CMS program
batch job. The CMS is now active.
Severity: 0
System Programmer Response:No

KO4SRV055

Job &1 submitted to batch job queue.
Explanation: The START CMS command submitted job &1.
User Response: Determine which job queue contains the batch job and review
other details about the job.
Severity: 0
System Programmer Response:No

KO4SRV056

Unable to start Candle Management Server (CMS) task &1.
Explanation: The CMS command could not start task &1, which is missing or
invalid.
User Response: Check the log for messages. Also, make sure that the library
subsystem, job queue, user profile, path, and/or library path exist and are correct.
If these are missing, install the CMS again.
Severity: 30
System Programmer Response:Unattended

KO4SRV057

Candle Management Server (CMS) not ended.
Explanation: The value for the "Confirm request to end" prompt was No. The
END CMS command was not run. and the CMS is still active.
User Response: To end the CMS, reply *YES to "Confirm request to end".
Severity: 0
System Programmer Response:No

KO4SRV058

Candle Management Server (CMS) had ended.
Explanation: The CMS stopped because an END CMS command was issued.
Severity: 0
System Programmer Response:No

KO4SRV059

Candle Management Server (CMS) stopped unexpectedly.
Explanation: The CMS program cannot continue because of an unexpected
processing failure.
User Response: Check the job log for messages and the CMS job status.
Severity: 40
System Programmer Response:Unattended

KO4SRV060

Candle Management Server (CMS) ended Situation &1
Explanation: The CMS received and acknowledged a request to end the
situation, and has ended the situation.
Severity: 0

440

Candle Products Messages Manual (KLVHS–KONCT)

KO4SRV061

Candle Management Server (CMS) starting Situation &1.
Explanation: The CMS received and acknowledged a request to start the
situation and is now doing so.
Severity: 0

KO4SRV062

Command &1 did not complete.
Explanation: &1 is pending, but the Candle Management Server (CMS)
subsystem is busy. A timeout error occurred between issuing the command and
running of the CMS jobs. The CMS program did not acknowledge the request.
User Response: Check the status of the job and view the previously listed
messages. If no errors occur, try the command again.
Severity: 0

KO4SRV063

Candle Management Server (CMS) request &1 did not complete.
Explanation: Command &1 was not able to complete the request due to
program error. An incorrect response was received from the situation monitor
component.
User Response: View all error messages that were logged to the CMS product
log. Check all CMS joblogs for messages.
Severity: 0
System Programmer Response:Unattended

KO4SRV064

Situation definition &1 deleted.
Explanation: The definition is deleted. If the situation is active, it remains so
until you stop it.
User Response: Verify that situation &1 is active.
Severity: 0
System Programmer Response:No

KO4SRV065

Situation definition &1 created.
Explanation: The Candle Management Server (CMS) CREATE SITUATION
command created situation &1.
Severity: 0
System Programmer Response:No

KO4SRV066

Situation list printed.
Explanation: Pressing the appropriate function key caused the entire situation
list to be printed.
User Response: View the situation list.
Severity: 0
System Programmer Response:No

KO4SRV067

Situation definition &1 changed.
Explanation: The Candle Management Server (CMS) CHANGE SITUATION
command changed the situation definition.
User Response: If situation is active, changes do not take place until the
situation is ended and then restarted.
Severity: 0
System Programmer Response:No

KMQxx001E–KOCJ0046

441

KO4SRV068

Input not supplied for required fields.
Explanation: A required parameter was not specified.
User Response: Enter the correct value for highlighted fields.
Severity: 30
System Programmer Response:No

KO4SRV069

Situation definition &1 not found.
Explanation: The Candle Management Server (CMS) could not locate situation
definition &1.
User Response: If the definition contains mixed case characters, enclose the
definition in single quotes. Check that situation &1 is spelled correctly.
Severity: 10
System Programmer Response:No

KO4SRV070

Configuration information changed.
Explanation: The CONFIGURE CMS command was used to change
configuration options.
User Response: View current configuration options. End the Candle
Management Server (CMS) and then start it again to run with new options.
Severity: 0
System Programmer Response:No

KO4SRV071

Data not valid for this field.
Explanation: The Candle Management Server (CMS) detected incorrect data
for a specific field. For example, a field that requires numeric data contains
character data.
User Response: Verify that you are using the kind of data required for this
field.
Severity: 30
System Programmer Response:No

KO4SRV072

Not able to read record in configuration file.
Explanation: The Candle Management Server (CMS) encountered error
condition &1, message ID &2 while reading keyed record &3 in file &4. Either the
key length is incorrect or an I/O error occurred. The configuration file is not read.
User Response: Check the file for errors and try the configuration command
again.
Severity: 30
System Programmer Response:Unattended

KO4SRV073

Not able to locate record in configuration file.
Explanation: The Candle Management Server (CMS) encountered error
condition &1, error ID &2 while locating keyed record &3 in file &4. Either the file
was not opened for read operations or an I/O error occurred. The configuration
file was not read.
User Response: Check the configuration file for errors and try the command
again.
Severity: 30
System Programmer Response:Unattended

442

Candle Products Messages Manual (KLVHS–KONCT)

KO4SRV074

Not able to update record in configuration file.
Explanation: The Candle Management Server (CMS) encountered error
condition &1, error ID &2, while updating keyed record &3 in file &4. Either the
file was not opened for update operations, or an I/O error occurred. The
configuration file is not updated.
User Response: Check the configuration file for errors and try the command
again.
Severity: 30
System Programmer Response:Unattended

KO4SRV075

Situation definition &1 already exists.
Explanation: The Candle Management Server (CMS) detected that situation
definition &1 was already defined.
User Response: Before creating or renaming this situation definition, change
the situation definition name, delete the existing situation definition, or omit the
command.
Severity: 0
System Programmer Response:No

KO4SRV076

Situation monitoring for &1 already active.
Explanation: The Candle Management Server (CMS) start command was
issued for situation definition &1. The CMS DISPLAY SITUATION command
shows all active situations.
User Response: If situation &1 contains mixed case, put quotes around
definition and try the command again.
Severity: 0
System Programmer Response:No

KO4SRV077

Situation monitoring for &1 not active.
Explanation: The Candle Management Server (CMS) detected situation &1 was
not active. The CMS DISPLAY SITUATION command shows all active situations.
User Response: If situation &1 contains mixed case, put quotes around the
definition and try command again.
Severity: 0
System Programmer Response:No

KO4SRV078

National Language Support conversion failed.
Explanation: The Candle Management Server (CMS) program was not able to
translate the contents of a text description field.
User Response: View specific messages in the product and job logs.
Severity: 0
System Programmer Response:No

KO4SRV079

Value &3 not valid for parameter &2.
Explanation: A required value was not entered for this parameter.
User Response: Enter the correct value for this parameter.
Severity: 20
System Programmer Response:No

KMQxx001E–KOCJ0046

443

KO4SRV080

Value &3 not valid for parameter &2.
Explanation: A required value was not entered for the parameter.
User Response: Enter the correct value for the required field.
Severity: 20
System Programmer Response:No

KO4SRV081

Value &3 not valid for parameter &2.
Explanation: The first character must be alphabetic.
Severity: 20
System Programmer Response:No

KO4SRV082

*PROMPT not allowed for parameter &2.
Explanation: Candle Management Server (CMS) allows only *PROMPT for
specific fields. This field is not allowed.
User Response: Enter a specific name in the field for parameter &2.
Severity: 20
System Programmer Response:No

KO4SRV083

Value &3 not valid for parameter &2.
Explanation: No imbedded blanks allowed.
User Response: Refer to the appropriate Candle Management Server (CMS)
Reference Manual for correct values.
Severity: 20
System Programmer Response:No

KO4SRV084

Irrecoverable errors while updating configuration file.
Explanation: Not authorized to access this file.
User Response: Contact a user with access privileges. Check the work object
authority to see what kind of access you need.
Severity: 99
System Programmer Response:Unattended

KO4SRV085

Local directory server Luname must match Candle Management Server
(CMS) Luname.
Explanation: The network directory server Luname must match the one that
you specified earlier.
User Response: Enter the correct network directory server Luname.
Severity: 99

KO4SRV086

Local directory server network name must match Candle Management
Server (CMS) network name.
Severity: 99

KO4SRV087

Candle Management Server (CMS) server Luname not valid.
Severity: 99

KO4SRV088

Directory server Luname not valid.
Severity: 99

444

Candle Products Messages Manual (KLVHS–KONCT)

KO4SRV089

Specify *SNA Directory Server.
Explanation: An *SNA directory server must be specified when no Candle
Management Server (CMS) TCP/IP address is present. Message CPF0002 follows.
Severity: 99

KO4SRV090

Value &3 not valid for parameter &2.
Explanation: Contains variant characters. Invariant characters are:
®

uppercase A-Z

lowercase a-z

<+> % & * / () “ &4 , _ - . : ; ?

User Response: Enter invariant characters.
Severity: 20
System Programmer Response:No
KO4SRV091

Predicate attribute &2 not known or not valid.
Explanation: You entered an attribute that is not valid.
User Response: Enter a valid attribute or use *PROMPT to choose an
attribute.
Severity: 0
System Programmer Response:No

KO4SRV092

Get Attributes request was not successful.
Severity: 0
System Programmer Response:No

KO4SRV093

Value &3 not valid for parameter &2.
Explanation: A required value was not specified.
User Response: The first character must be alphabetic or value must be *ALL.
Severity: 20
System Programmer Response:No

KO4SRV094

Value &3 not valid for parameter &2.
Explanation: The first character must be alphabetic or value must be
*PROMPT.
User Response: Change the first character in the parameter &2 to alphabetic,
or change parameter &2 to *PROMPT.
Severity: 20
System Programmer Response:No

KO4SRV095

Multiple predicates not allowed with PDTREL value *SNGPDT.
Explanation: You entered *SNGPDT in the PDTREL field with more than one
predicate.
User Response: Enter *AND or *OR in the PDTREL field ,or delete all but one
predicate in the situation.
Severity: 20
System Programmer Response:No

KMQxx001E–KOCJ0046

445

KO4SRV096

Multiple predicates required with PDTREL value *AND or *OR.
Explanation: You entered *AND or *OR in the PDTREL field, but did not enter
more than one predicate.
User Response: Enter more predicates or enter *SNGPDT in the PDTREL
field.
Severity: 20
System Programmer Response:No

KO4SRV097

Predicate relational operator must be *EQ when function is *SIT.
Explanation: You entered something other than *EQ in the relational field
when the predicate is another situation.
User Response: Enter *EQ in the relational operator field or change the PDT
field to something other than *SIT.
Severity: 20
System Programmer Response:No

KO4SRV098

Predicate compare value must be *TRUE when function is *SIT.
Explanation: You entered something other than *TRUE in the compare value
field when the predicate is another situation.
User Response: Enter *TRUE in the compare value field or change the
predicate function to something other than *SIT.
Severity: 20
System Programmer Response:No

KO4SRV099

Predicate compare value not valid.
Explanation: Predicate compare value &2 for attribute &3 is not valid. Allowed
values range from &4 to &5.
User Response: Refer to the appropriate Candle Management Server (CMS)
Reference Manual for compare values.
Severity: 20
System Programmer Response:No

KO4SRV100

Predicate compare value for attribute &3 not valid.
Explanation: Predicate compare value &2 for attribute &3 is not valid; allowed
values are &4 &5 &6 &7 &8 &9 &10 &11 &12 &13.
User Response: Change the predicate compare value to one of the following:
&4 &5 &6 &7 &8 &9 &10 &11 &12 &13.
Severity: 20
System Programmer Response:No

KO4SRV101

Predicate compare value not known or not valid.
Explanation: Compare value &2 for attribute &3 not known or not valid.
User Response: Enter a correct value. Refer to the appropriate Candle
Management Server (CMS) Reference Manual for compare values.
Severity: 20
System Programmer Response:No

KO4SRV102

Predicate attribute &2 not valid.
Explanation: A situation cannot reference itself.

446

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Enter a correct value for this attribute. Refer to the appropriate
Candle Management Server (CMS) Reference Manual for attribute values.
Severity: 20
System Programmer Response:No
KO4SRV103

Unable to create CMS Message Queue.
Explanation: The CMS tried to create a Message Queue to communicate with
its companion processes and the create failed.
Severity: 20
System Programmer Response:No

KO4SRV104

CMS message receipt failed.
Explanation: The CMS tried to receive a message from its message queue and
the receive failed.
Severity: 20
System Programmer Response:No

KO4SRV105

Send to &1 failed.
Explanation: The CMS Manager tried to send a message to &1, but the send
failed.
Severity: 20
System Programmer Response:No

KO4SRV106

Unsupported CMS option specified.
Explanation: The parameter passed to the CMS is not recognized as a valid
operand.
User Response: Enter a correct value for the CMS operand. Refer to the
appropriate Candle Management Server (CMS) Reference Manual for valid
values.
Severity: 20
System Programmer Response:No

KO4SRV107

Detecting Candle Management Server (CMS) local directory server.
Severity: 0
System Programmer Response:No

KO4SRV108

Detecting Candle Management Server (CMS) global directory server.
Severity: 0
System Programmer Response:No

KO4SRV109

CMS &1 on &2 is starting
Severity: 0
System Programmer Response:No

KO4SRV110

CMS &1 on &2 is running
Severity: 0
System Programmer Response:No

KO4SRV111

CMS &1 on &2 is stopping
Severity: 0

KMQxx001E–KOCJ0046

447

System Programmer Response:No
KOCJO001

INITIALIZE COMPLETED NORMALLY.
Explanation: This facility has initialized successfully.
System Action: Processing continues normally.
User Response: None.
Message Type: Confirmation.

KOCJO002

INTERFACE SHUTDOWN REQUESTED.
Explanation: A request to shut down is being processed.
System Action: The facility terminates all processing.
User Response: None.
Message Type: Confirmation.

KOCJO003

INTERFACE SHUTDOWN COMPLETED.
Explanation: This facility was in a suspended state when a shutdown was
requested. The shutdown request has completed termination of this facility.
System Action: All processing is terminated.
User Response: None.
Message Type: Confirmation.

KOCJO004

INTERFACE SUSPEND REQUESTED.
Explanation: A request to suspend the facility is being processed.
System Action: The facility disables operations and returns to a suspended
state.
User Response: None.
Message Type: Confirmation.

KOCJO005

INTERFACE INITIALIZED STATUS: SUSPENDED.
Explanation: This facility has partially initialized to a suspended state.
System Action: The facility remains in a suspended state until a resume
request is processed.
User Response: None.
Message Type: Confirmation.

KOCJO006

INTERFACE RESUMED SUCCESSFULLY.
Explanation: A request to resume operations has been processed.
System Action: The facility is now fully initialized and continues processing
normally.
User Response: None.
Message Type: Confirmation.

KOCJO007

ASSEMBLED AGAINST DIFFERENT CICS RELEASE.
Explanation: Initialization failed because the facility determined that it was not
assembled using the correct CICS macro libraries.
System Action: Processing terminates.
User Response: Assemble the facility using the correct CICS macro libraries.
Message Type: User error.

448

Candle Products Messages Manual (KLVHS–KONCT)

KOCJO008

UNABLE TO DETERMINE START TYPE.
Explanation: The facility was unable to determine how it was invoked. This can
occur if the facility was invoked using a mechanism other than those documented.
System Action: The program terminates without taking any action.
User Response: Determine how the program was invoked. If this seems to be
an error in the facility, contact Candle Support Services.
Message Type: User or internal error.

KOCJO009

KOCPLT00 NOT LOCATED. CHECK LINKEDIT.
Explanation: The facility could not locate entry point KOCPLT00 during
execution.
System Action: The program terminates without taking any action.
User Response: Check that module KOCFI200 was available during linkedit of
the module. Relink the module using the supplied JCL.
Message Type: User error.

KOCJO010

FAILURE IN CICS INQUIRE.
Explanation: An unexpected response code was received from an EXEC CICS
INQUIRE.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: Internal error.

KOCJO011

KEYWORD UNSUPPORTED, PLEASE REENTER.
Explanation: A keyword was entered which is not supported.
System Action: The program terminates without taking any action.
User Response: Refer to the documentation for a list of supported keywords.
Message Type: User error.

KOCJO012

JOURNAL NUMBER ERROR.
Explanation: The journal specified in the JOURNUM parameter could not be
located in the CICS region.
System Action: The program terminates without taking any action.
User Response: Correct the JOURNUM parameter or the Journal Control
Table.
Message Type: User error.

KOCJO013

OMEGAMON IS ALREADY ACTIVE.
Explanation: This facility detected that OMEGAMON II for CICS was already
initialized in this CICS region.
System Action: The program terminates without taking any action.
User Response: Code the facility program before KOCOME00 in the PLT or
start this facility before an OMEG INIT is issued.
Message Type: User error.

KMQxx001E–KOCJ0046

449

KOCJO014

SUSPEND TRANSACTION INACTIVE.
Explanation: An attempt to suspend the facility was made and the background
transaction was not active.
System Action: The program terminates without taking any action.
User Response: Determine why the background transaction is not active. If
you determine the error is in this facility, contact Candle Support Services.
Message Type: User or internal error.

KOCJO015

INTERFACE ALREADY SUSPENDED.
Explanation: An attempt was made to suspend this facility when it was already
in a suspended state.
System Action: The program terminates without taking any action.
User Response: None.
Message Type: Information.

KOCJO016

JOURNAL OPEN ERROR.
Explanation: An error was detected when attempting to open the CICS journal.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

KOCJO017

INTERFACE ALREADY ACTIVE.
Explanation: An attempt to initialize or resume this facility was made when it
was already active.
System Action: The program terminates without taking any action.
User Response: None.
Message Type: Information.

KOCJO018

EXIT ENABLE ERROR.
Explanation: An error was detected when attempting to enable the CICS global
user exit.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

KOCJO019

EXIT EXTRACT ERROR.
Explanation: An error was detected when attempting to extract information
relating to the CICS global user exit.
Explanation: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

450

Candle Products Messages Manual (KLVHS–KONCT)

KOCJO020

GETMAIN FAILURE.
Explanation: An error was detected when attempting to obtain storage for use
as a buffer.
System Action: The program terminates without taking any action.
User Response: Check the size of the ECDSA or EDSALIM to ensure there is
enough space for the buffers specified.
Message Type: User or internal error.

KOCJO021

EXIT START FAILURE.
Explanation: An error was detected when attempting to start the CICS global
user exit.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

KOCJO022

EXIT STOP FAILURE.
Explanation: An error was detected when attempting to stop the CICS global
user exit.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

KOCJO023

FREEMAIN FAILURE.
Explanation: An error was detected when attempting to release buffer storage.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: Internal error.

KOCJO024

EXIT DISABLE FAILURE.
Explanation: An error was detected when attempting to disable the CICS global
user exit.
System Action: The program terminates without taking any action.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

KOCJO025

FAILURE IN CICS ASSIGN.
Explanation: An error was detected during the processing of an EXEC CICS
ASSIGN command.
System Action: The program terminates without taking any action.

KMQxx001E–KOCJ0046

451

User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: Internal error.
KOCJO026

TRANSACTION START FAILURE.
Explanation: An error was detected when attempting to start the background
transaction.
System Action: The program terminates without taking any action.
User Response: Ensure that the transaction named in the TRANSID keyword
is defined to CICS. Use AUXTRACE or CEDF to determine the cause of the
unexpected return code. If you determine the error is in this facility, contact
Candle Support Services.
Message Type: User or internal error.

KOCJO027

INTERFACE INACTIVE.
Explanation: An attempt was made to suspend or shut down this feature when
it was not active in the system.
System Action: The program terminates without taking any action.
User Response: None.
Message Type: Information.

KOCJO028

INITIALIZE IS ALREADY IN PROCESS.
Explanation: A request has been issued and an initialization request is currently
in process.
System Action: The program terminates without taking any action.
User Response: Retry the request at a later time.
Message Type: Information.

KOCJO029

RESUME IS ALREADY IN PROCESS.
Explanation: A request has been issued while a resume request is currently in
process.
System Action: The program terminates without taking any action.
User Response: Retry the request at a later time.
Message Type: Information.

KOCJO030

SUSPEND IS ALREADY IN PROCESS.
Explanation: A request has been issued while a suspend request is currently in
progress.
System Action: The program terminates without taking any action.
User Response: Retry the request at a later time.
Message Type: Information.

KOCJO031

SHUTDOWN IS ALREADY IN PROCESS.
Explanation: A request has been issued while a shutdown request is currently in
process.
System Action: The program terminates without taking any action.
User Response: Retry the request at a later time.
Message Type: Information.

452

Candle Products Messages Manual (KLVHS–KONCT)

KOCJO032

UNKNOWN FUNCTION IN PROCESS.
Explanation: A request was issued and an unknown function was in progress.
System Action: The program terminates without taking any action.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KOCJO033

ERROR OCCURRED DURING CLEANUP DISABLE.
Explanation: An error occurred while attempting to disable the CICS global user
exit after a previous error had occurred.
System Action: The program terminates without taking any action.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KOCJO034

ERROR OCCURRED DURING CLEANUP FREEMAIN.
Explanation: An error occurred while attempting to release buffer storage after a
previous error had occurred.
System Action: The program terminates without taking any action.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KOCJO035

HANDLE ABEND FAILURE.
Explanation: An error was detected when processing an EXEC CICS HANDLE
ABEND command.
System Action: The background task terminates.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected error. If you determine the error is in this facility, contact Candle
Support Services.
Message Type: Internal error.

KOCJO036

EXIT WORK AREA NOT LOCATED.
Explanation: The background transaction was unable to locate the global user
exit work area for this facility.
System Action: The background task terminates.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected error. If you determine the error is in this facility, contact Candle
Support Services.
Message Type: Internal error.

KOCJO037

ERROR RECEIVED DURING WAIT PROCESSING.
Explanation: An error was detected when processing an EXEC CICS WAIT
command.
System Action: The background task terminates.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected error. If you determine the error is in this facility, contact Candle
Support Services.
Message Type: Internal error.

KMQxx001E–KOCJ0046

453

KOCJO038

ERROR RECEIVED DURING FREEMAIN PROCESSING.
Explanation: An error was detected when attempting to release buffer storage.
System Action: The background task terminates.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected error. If you determine the error is in this facility, contact Candle
Support Services.
Message Type: Internal error.

KOCJO039

JOURNAL WRITE FAILURE.
Explanation: An error was detected while attempting to write a completed
buffer to the CICS journal.
System Action: The background task terminates.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected error. If you determine the error is in this facility, contact Candle
Support Services.
Message Type: User or internal error.

KOCJO040

INTERFACE TRANSACTION HAS ABENDED.
Explanation: The background task has abended.
System Action: The background task terminates.
User Response: Use AUXTRACE or CEDF to determine the cause of the
unexpected error. If you determine the error is in this facility, contact Candle
Support Services.
Message Type: Internal error.

KOCJO041

RTYPE NOT PRESENT IN DICTIONARY.
Explanation: The global user exit has determined that the RTYPE field is not
present in the dictionary.
System Action: The exit ceases processing.
User Response: Ensure that MCT field 112, RTYPE, is not excluded from
performance records.
Message Type: User error.

KOCJO042

TRANSID NOT PRESENT IN DICTIONARY.
Explanation: The global user exit has determined that the transaction ID field is
not present in the dictionary.
System Action: The exit ceases processing.
User Response: Ensure that MCT field 001, TRAN, is not excluded from
performance records.
Message Type: User error.

KOCJO043

TASK NUMBER NOT PRESENT IN DICTIONARY.
Explanation: The global user exit has determined that the task number field is
not present in the dictionary.
System Action: The exit ceases processing.
User Response: Ensure that MCT field 031, TRANNUM, is not excluded from
performance records.
Message Type: User error.

454

Candle Products Messages Manual (KLVHS–KONCT)

KOCJO044

NETNAME NOT PRESENT IN DICTIONARY.
Explanation: The global user exit has determined that the network name field is
not present in the dictionary.
System Action: The exit ceases processing.
User Response: Ensure that MCT field 097, NETNAME, is not excluded from
performance records.
Message Type: User error.

KOCJO045

UOWID NOT PRESENT IN DICTIONARY.
Explanation: The global user exit has determined that the unit-of-work ID field
is not present in the dictionary.
System Action: The exit ceases processing.
User Response: Ensure that MCT field 098, UOWID, is not excluded from
performance records.
Message Type: User error.

KOCJO046

OMEGBSC NOT PRESENT IN DICTIONARY.
Explanation: The global user exit has determined that the OMEGBSC field is
not present in the dictionary.
System Action: The exit ceases processing.
User Response: Ensure that the OMEGBSC EMP is defined in the MCT as
described in the CCUST.. You cannot change the name of this field when using
this facility.
Message Type: User error.

KMQxx001E–KOCJ0046

455

456

Candle Products Messages Manual (KLVHS–KONCT)

KOGCM001–KONCT303

KOGCM001

FUNCTION=PSMREAD, RC=rc {LU(luname) SESSID(sessid)}
Explanation: A problem occurred while reading a command from the product.
System Action: The command is ignored.
User Response: If RC=8 a timeout occurred. Investigate the cause of slow
response by the product. Examine the POVI log for accompanying messages.
Message Type: LOG.

KOGCM002

ZERO LENGTH COMMAND {LU(luname) SESSID(sessid)}
Explanation: A null command was received from the product.
System Action: The command is ignored.
User Response: Investigate the command procedure to understand why a null
command was sent.
Message Type: LOG.

KOGCM003

UNKNOWN COMMAND, command {LU(luname) SESSID(sessid)}
Explanation: An unrecognized command was received from the product.
System Action: The command is ignored.
User Response: Investigate the command procedure to understand why an
invalid command was sent.
Message Type: LOG.

KOGCM004

SESSION CANNOT BE STARTED. FUNCTION=TBGET, RC=rc
{LU(luname) SESSID(sessid)}
Explanation: A session could not be started because stored session information
could not be retrieved.
System Action: The session is not started.
User Response: Examine the CL/Engine log for more detailed messages
describing the error.
Message Type: LOG.

KOGCM006

DIALOG NOT FOUND.
Explanation: The attempt to invoke a dialog failed because the dialog did not
exist in any TLVPNLS library.
System Action: None.
User Response: Reissue the command using the correct dialog name.
Message Type: LOG.

KOGCM001–KONCT303

457

KOGCM005

LU(luname) OG/MVS Command input: command
Explanation: The specified command input was received from the product.
System Action: An attempt will be made to execute the command.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGDF005

UNKNOWN APPSTAT FUNCTION subfunction
Explanation: The APPSTAT function was passed an invalid subfunction.
System Action: The storing or retrieval of application status being attempted
will not occur. Main menu application status may be incorrect.
User Response: Determine whether the problem persists. Contact Candle
Customer Support.
Message Type: LOG.

KOGDF006

APPSTAT CALLED BEFORE INITIALIZATION FOR subfunction
Explanation: The APPSTAT dialog function was called for the specified
subfunction, i.e. INQUIRE or GET, before all control blocks were initialized for the
POVI environment. This message may also appear during storage shortage
situations and will be preceded by CT/Engine Messages in that case.
System Action: The APPSTAT dialog function returns a status of UNKW
(unknown).
User Response: Examine the log for messages describing a storage shortage.
Consider the effect of recent changes, particularly to TLVCMDS
RKOGPARM(KOGPSTRT). Contact Candle Customer Support if this message
occurs more than once per application in one execution of the POVI address
space.
Message Type: LOG.

KOGDF007

APPLICATION STATUS: APPLID(xxxxxxxx) NOW(yyyy) RPL(zzzz)
Explanation: The APPSTAT function returned a new status for the requested
application. In the text above, xxxxxxxx will be replaced by the 8-byte application
ID, yyyy by the 4-byte mnemonic for STATUS, and zzzz by the 6-byte
hexadecimal values for RPLRTNCD, RPLFDBK2, and RPLFDBK3.
The status mnemonics are:

458

ACT

The application is active.

INAC

The application is not active.

UNAV

The application is not available, possibly due to problems with an
intermediate node.

STOP

The application is not accepting logons.

QSCE

The application is quiescing.

UNDF

The application is undefined.

UNKW

Unknown status.

Candle Products Messages Manual (KLVHS–KONCT)

This appears while waiting for VTAM to initially update the status, if errors are
found in the APPSTAT request, or if the status returned by VTAM cannot be
otherwise classified.
System Action: None. This is an informational message only
User Response: No action is required. If you wish to investigate the status of
individual applications, the following are suggested actions:
INAC

Verify that the VTAM application is started and is accepting logon
requests.

UNAV

Verify that no intermediate node has failed.

STOP

See INAC above.

QSCE

See INAC above.

UNDF

This may be due to a misspelled application name or to a syntax
error in the name. It may also arise if the VTAM application major
node is not active. In the latter case, issue a
V NET,ACT,ID= command to enable the
application name.

UNKW

Unknown status can occur as a result of the situations shown
under Explanation above. Further investigation should include
attempting to manually log on to the application in question from
a physical 3270 terminal. In addition, the IBM VTAM
Programming manual documents the zzzz field in detail, which
should identify the specific problem.

Message Type:

LOG.

KOGEC001

NO SESSION SPECIFIED
Explanation: A S sessid command was received from the product with the
sessid omitted
System Action: The session is not started.
User Response: Investigate the command procedure to understand why the
sessid was omitted.
Message Type: LOG.

KOGEC002

SPECIFIED SESSION NOT DEFINED TO POVI
Explanation: A S sessid command was received from the product specifying a
sessid which had not been defined to POVI during initialization in TLVCMDS
RKOGPARM(KOGVTERM) using the APPLDEF command.
System Action: The session is not started.
User Response: Either correct the cfile or REXX to start with a valid defined
session, add the APPLDEF command to define the session during POVI
initialization, or enter the APPLDEF command on the command line of either the
Operator or CUA/Operator CT/Engine facilities.
Message Type: LOG.

KOGCM001–KONCT303

459

KOGEC003

LU(luname) \K keyname
Explanation: A \K command to transmit an aid key to a started application was
received from the specified product LU. "\" is the default POVI environment
command prefix character, which may be different, depending on customization.
System Action: The specified aid key is transmitted to the application.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC004

\#TYPE (nnn)variablename contents|*CONFIDENTIAL*
Explanation: A \#TYPE command was received from the product to type the
contents of a variable at the specified relative unprotective field number. If the
variable name is "PASSWORD", then the contents are replaced with
*CONFIDENTIAL*". The "\" is the default POVI environment command prefix
character; it may be different, depending on customization.
System Action: The command is executed.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC005

\@TYPE PARAMETER, parameter, INVALID
Explanation: A \@TYPE command was received to simulate the typing of the
specified variables contents at the specified row and column, and the specified
row/column is invalid. The "\" is the default POVI environment command prefix
character; it may be different, depending on customization.
System Action: The command completes unsuccessfully.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC006

\TYPE row col variablename contents|*CONFIDENTIAL*
Explanation: A \TYPE command was received from the product to simulate the
keying of the specified variables contents at the specified screen location. If the
variable’s name is password then the contents are replaced with
*CONFIDENTIAL*". The "\" is the default POVI environment command prefix
character; it may be different, depending on customization.
System Action: The command is executed.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC007

\CUR row,col {LU(luname) SESSID(sessid)}
Explanation: The \CUR command has been received from the product to
display the current cursor coordinates indicated in the message. The "\" is the
default POVI environment command prefix character; it may be different,
depending on customization.
System Action: The command is executed.
User Response: None. This is an informational message only.
Message Type: LOG.

460

Candle Products Messages Manual (KLVHS–KONCT)

KOGEC008

KABSEVAL INVOKED NAME=name VALUE=value
Explanation: The dialog KABSEVAL has been called to evaluate a named
variable.
System Action: The named variable’s contents are returned.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC009

EVALUATED RESULT=value
Explanation: Dialog KABSEVAL has been called to evaluate a named variable.
System Action: The named variable’s contents are returned.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC010

\LOC PARAMETER position, INVALID
Explanation: A \LOC command was received from the product to simulate
cursor positioning for a started application, but the specified position was invalid.
The "\" is the default POVI environment command prefix character; it may be
different, depending on customization.
System Action: The application cursor is not repositioned.
User Response: Determine why the CFILE or REXX program transmits an
invalid cursor position.
Message Type: LOG.

KOGEC011

LU(luname) \TYPE VARIABLE=variablename VALUE=value
Explanation: A \TYPE command was received from the specified product LU to
simulate the keying of the specified variable’s value at the current cursor position.
The "\" is the default POVI environment command prefix character; it may be
different, depending on customization.
System Action: The command is executed.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC012

\SEE ENTERED BY userid|luname SYSPARM= variablename
Explanation: A \SEE command was received from the specified product virtual
terminal LU or the specified user at a physical terminal. The "\" is the default POVI
environment command prefix character; it may be different, depending on
customization.
System Action: The command is executed.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGCM001–KONCT303

461

KOGEC013

\SET ABORT PSMREAD RC=rc
Explanation: The PSMREAD function used to read parameters passed for the
\SET command failed. The "\" is the default POVI environment command prefix
character; it may be different, depending on customization.
System Action: The command completes unsuccessfully.
User Response: If RC=8 there was a timeout, and the cause of slow product
response should be investigated. Otherwise examine the log for messages
detailing the cause of the error.
Message Type: LOG.

KOGEC014

LU(luname) \SET EXITED, VARIABLE variablename, VALUE= LEN=0
Explanation: The \SET command executed successfully for the specified
product LU. The "\" is the default POVI environment command prefix character; it
may be different, depending on customization.
System Action: The variable is set to null.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC015

LU(luname) SET EXITED VARIABLE=variablename
VALUE=value|*CONFIDENTIAL* LENGTH=length
Explanation: The \SET command has completed for the specified product LU
and the specified variable is set to the specified value, having the specified length.
If the variable has the name "password" then "*CONFIDENTIAL*" is substituted
for the value. The "\" is the default POVI environment command prefix character;
it may be different, depending on customization.
System Action: The command executed successfully.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC016

\WAIT seconds
Explanation: A \WAIT command has been received from the product. The "\" is
the default POVI environment command prefix character; it may be different,
depending on customization.
System Action: No data will be transmitted to the application for the specified
number of seconds.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEC017

LU(luname) SESSID(sessid) STATUS=status
Explanation: The specified LU has issued the \STATUS command to obtain an
application’s status. The \ is the default POVI environment command prefix
character; it may be different, depending on customization.
System Action: The specified status is returned to the requestor.
User Response: None. This is an informational message only.
Message Type: LOG.

462

Candle Products Messages Manual (KLVHS–KONCT)

KOGEC018

Expected Environment Command prefix character is prefixchar
Explanation: The character given by prefixchar has been established as the
POVI environment command prefix character.
System Action: Only data beginning with the specified character will be
recognized as a command.
User Response: If commands are not being recognized and executed, ensure
that the same character has been specified for the POVITRGC startup parameter.
Message Type: LOG.

KOGER001

INVALID SELECTION CODE
Explanation: A selection code other than "/", or "S" was used to select a session
from the main menu.
System Action: The session will not be started.
User Response: Reselect the session using "/" or "S", or use the options
pulldown to turn on the implicit selection option and select using only the cursor
key.
Message Type: LOG.

KOGER002

key KEY IS NOT ACTIVE
Explanation: The specified key is not active for the main menu.
System Action: The specified key is ignored.
User Response: Examine the function key line at the bottom of the display to
determine what the valid keys are.
Message Type: LOG.

KOGEV001

LU(luname) PLAYBACK MANAGER ACCESS DENIED
Explanation: Access to the Playback Manager was denied because POVI was
customized to grant access only to specific LUs.
System Action: The specified LU is logged off.
User Response: If the LU should be granted access then recustomize POVI to
grant access to this LU.
Message Type: LOG.

KOGEV002

LU luname LOGGED ON TO PLAYBACK MANAGER
Explanation: The specified product LU has logged on to the Playback Manager.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEV003

RECORDING GATEWAY ACCESS DENIED FOR USER uuuuuuuu
Explanation: Access to the Recording Manager was denied because the userid
and password were not valid for the customized security method.
System Action: The specified user will be logged off.
User Response: Re-enter a valid userid and password, or define the specified
user and password using the selected security method.
Message Type: LOG.

KOGCM001–KONCT303

463

KOGEV004

VSSENTRY FAILED WITH RC=nn
Explanation: Initialization of POVI’s virtual session services failed.
System Action: The user is logged off.
User Response: If the KABNLOG NAM variable was >400, examine the POVI
log for detailed messages. Otherwise, set KABNLOG >400, recycle POVI,
recreate the failure, and examine the POVI log.
Message Type: LOG.

KOGEV005

luname ACCESSED THE RECORDING MANAGER
Explanation: The specified LU successfully logged on to the Recording
Manager.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGEX001

luname EXITED PROGRAMMERLESS OVI
Explanation: The specified LU successfully logged off the Playback Manager.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGIN001

POVI GLOBAL SESSION TABLE CREATION ERROR, RC=nn
Explanation: During user initialization, the POVI global session table could not
be created.
System Action: POVI will be unusable since the user’s main menus will not
contain any sessions.
User Response: Examine the POVI log for more detailed messages describing
the error.
Message Type: LOG.

KOGIN002

POVI INITIALIZATION COMPLETE
Explanation: POVI has initialized successfully.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGLM001

LU(luname) HAS ROWS=rows, COLS=cols
Explanation: The named LU has the specified screen size.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGLM002

LU(luname) USES LOGMODE=logmodename
Explanation: The physical session for the specified LU was started using the
specified logmode name.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

464

Candle Products Messages Manual (KLVHS–KONCT)

KOGLM003

LU(luname) WILL USE LOGMODE=logmode FOR ITS VIRTUAL SESSIONS
Explanation: The specified LU will use the specified logmode name for any
virtual sessions that it starts.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGLM004

LU(luname), SYSPRSVC=sysprsvc
Explanation: The Presentation Services field from the bind image is displayed.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGLM005

LU(luname) USES AN INVALID LOGMODE
Explanation: The product virtual terminal LUs have been configured with an
invalid logmode, a possible installation error.
System Action: The LU is logged off.
User Response: Re-examine installation and customization procedures. Set the
message diagnostics level so that logmode messages are output. Recreate the
problem, and examine the messages in the log.
Message Type: LOG.

KOGMM001

UNABLE TO OPEN POVI.SESSION.TABLE, RC=rc
Explanation: POVI’s global session table cannot be opened. POVI will be
unusable since no sessions will appear on the main menu.
System Action: The main menu will contain no sessions.
User Response: Examine the log for more detailed messages describing the
problem.
Message Type: LOG.

KOGMM002

UNABLE TO CREATE POVI.LUNAME.TABLE, RC=rc
Explanation: The user’s session table cannot be created.
System Action: The user’s main menu will not be displayed.
User Response: Examine the log for more detailed messages describing the
problem.
Message Type: LOG.

KOGMM003

TBSORT FAILURE FOR luname, RC=rc
Explanation: The user’s session table will not be sorted.
System Action: The user’s session table will be displayed on their main menu,
possibly in unsorted order.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGMM005

LOCAL SESSION TABLE ADD ERROR FOR luname, RC=nn
Explanation: All sessions could not be added to the user’s session table which
will be displayed on the main menu.
System Action: The main menu selections will be incomplete.

KOGCM001–KONCT303

465

User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.
KOGOP000

APPLDEF SUCCESSFULLY ADDED sessid, DEST(dest)
Explanation: An APPLDEF command has successfully completed after being
issued from either TLVCMDS RKOGPARM(KOGAPPLS) or from an Operator
facility.
System Action: The added session ID will be eligible for display on the main
menu.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGOP001

TABLE ADD ERROR FOR SESSID sessid, RC=nn
Explanation: The session ID, sessid, specified in an APPLDEF command, could
not be added.
System Action: The session ID will not be added nor will it be eligible for
display on the user’s main menu.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGOP002

TABLE OPEN ERROR FOR SESSID sessid, RC=nn
Explanation: The global session table could not be opened.
System Action: The main menu will not be displayed.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGOP003

POVI AS$B CHAIN CORRUPTION DETECTED, RECOVERY
SUCCESSFUL
Explanation: An internal logic error occurred.
System Action: Selections will be missing from the main menu.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGOP004

APPLDEF FAILED FOR DUPLICATE SESSID, sessid
Explanation: Multiple APPLDEF commands have been issued for the same
session ID.
System Action: The second instance of the session ID will not be selectable
from main menus.
User Response: Either refrain from issuing the APPLDEF command for a
duplicate session ID, or reissue the APPLDEF command for the correct session ID.
Message Type: LOG.

466

Candle Products Messages Manual (KLVHS–KONCT)

KOGOP005

VDEFINE ERROR FOR SESSID sessid, RC=nn
Explanation: An internal logic error caused the current APPLDEF command to
fail.
System Action: The specified session ID will be omitted from main menus.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGOP006

keyword=, A REQUIRED PARAMETER, WAS OMITTED
Explanation: The specified keyword was omitted from the APPLDEF
command.
System Action: None, the command was not successful.
User Response: Consult the command documentation, correct the command,
and reissue it.
Message Type: LOG.

KOGRT006

KOGRT009

LU(luname)*screen data
Explanation: A row of screen data received from an application started by the
specified product LU is displayed.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGRT010

LU(luname) SESSID(sessid) VIRTUAL TERMINAL CURSOR AT rr, cc
Explanation: The cursor position from the simulated application screen is
displayed.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGRT011

STATUS INQUIRY ACTIVE FOR sessid
Explanation: A status inquiry has been initiated for the specified application.
System Action: Upon completion of the inquiry the application status will be
updated for the main menu and subsequent \STATUS command. The "\" is the
default POVI environment command prefix character; it may be different,
depending on customization.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGRU001

KABS$RUN, INITIAL PSMEXP RC=rc
Explanation: A communications error occurred.

KOGCM001–KONCT303

467

System Action: Further communication with the product may not be possible.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.
KOGRU002

SCREEN SIZE PROBLEM WITH ROWS=xx, COLS=yy
Explanation: An internal logic error occurred.
System Action: Further communication with the product will not be reliable.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGRU003

WAITING FOR sessid ACTIVATION nn SECONDS AT luname
Explanation: The session for sessid has been started but is not yet active.
System Action: POVI continues waiting for the session to become active.
User Response: Investigate the cause of the slow response or the inability to
use the associated application.
Message Type: LOG.

KOGRU004

VIRTUAL SESSION ACTIVATION TIMEOUT {LU(luname) SESSID(sessid)}
Explanation: POVI timed out waiting for the specified session to become active.
System Action: The session will not be started with the application.
User Response: Investigate the cause of slow response or the inability to start
sessions with the associated application. If the cause is slow response, which might
be expected, consider adjusting POVI Virtual Session timeout parameters.
Message Type: LOG.

KOGRU005

MONITORING HAS BEGUN FOR SESSION sessid FOR luname
Explanation: A started session has become active and is ready for use by the
product.
System Action: None.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGRU007

luname WAITING FOR nn SECONDS FOR sessid, LAST RC=rc
Explanation: The application associated with sessid is not responding.
System Action: POVI continues to wait for a response from the associated
application.
User Response: Investigate the cause of slow response or the lack of any
response from the application.
Message Type: LOG.

KOGRU011

COMMUNICATIONS ERROR. FUNCTION=PSMIMP RC=rc {LU(luname)
SESSID(sessid)}
Explanation: A communications error occurred so that application data could
not be forwarded to the product.

468

Candle Products Messages Manual (KLVHS–KONCT)

System Action: By default, both physical and virtual sessions are terminated.
If POVI has been configured using the "return to main menu" option (by setting
the KABNRMNU NAM variable), then a return is made to the main menu, and
this message is displayed on the main menu message line.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.
KOGRU012

VIRTUAL SESSION TERMINATED {FOR SLU(luname)}
{FUNCTION=VSSEXP RC=8} {LU(luname) SESSID(sessid)}
Explanation: The specified session given by sessid has terminated
unexpectedly.
System Action: By default, both physical and virtual sessions are terminated.
If POVI has been configured using the "return to main menu" option (by setting
the KABNRMNU NAM variable), then a return is made to the main menu, and
this message is displayed on the main menu message line.
User Response: Consult the POVI and system logs for more details on why the
session terminated.
Message Type: LOG.

KOGRU013

COMMUNICATIONS ERROR. FUNCTION=PSMREAD RC=rc {LU(luname)
SESSID(sessid)}
Explanation: A communications error occurred while waiting for data.
System Action: By default, both physical and virtual sessions are terminated.
If POVI has been configured using the "return to main menu" option (by setting
the KABNRMNU NAM variable), then a return is made to the main menu, and
this message is displayed on the main menu message line.
User Response: Examine the POVI log for more detailed messages describing
the error.
Message Type: LOG.

KOGRU014

TIMEOUT. FUNCTION=PSMREAD {LU(luname) SESSID(sessid)}
Explanation: POVI has timed out while waiting for data.
System Action: By default, both physical and virtual sessions are terminated.
If POVI has been configured using the "return to main menu" option (by setting
the KABNRMNU NAM variable), then a return is made to the main menu, and
this message is displayed on the main menu message line.
User Response: Investigate the cause of the slow response or hang. If that level
of response might be expected from time to time, then the timeout value can be
reconfigured using the "NAM SET" command to increase the value of the
KABNTMOT variable.
Message Type: LOG.

KOGRU017

TESTING PATH, PF12 PRESSED
Explanation: Someone has logged onto the Playback Manager from a physical
terminal.
System Action: Only PF2 and PF12 will be accepted.
User Response: Do not sign onto the Playback Manager since it abides by a
strict protocol which is unsuitable for use at a physical terminal.

KOGCM001–KONCT303

469

Message Type:

LOG.

KOGRU018

ILLOGICAL KEY:xxxx FROM LU "luname"
Explanation: Someone has logged onto the Playback Manager from a physical
terminal.
System Action: Only PF2 and PF12 will be accepted.
User Response: Do not sign onto the Playback Manager since it abides by a
strict protocol which is unsuitable for use at a physical terminal.
Message Type: LOG.

KOGRU019

TERMINATION PROCEEDING FOR LU luname, SESSION sessid
Explanation: An unrecoverable error occurred for the session given by sessid,
which was started by luname.
System Action: By default, both physical and virtual sessions are terminated.
If POVI has been configured using the "return to main menu" option (by setting
the KABNRMNU NAM variable), then a return is made to the main menu, and a
message is displayed on the main menu message line.
User Response: Examine the log or the main menu message line for more
detailed messages describing the problem.
Message Type: LOG.

KOGRU020

LU(luname) VIRTUAL SESSION STARTED for SESSID(sessid) SLU(slu)
Explanation: A virtual session with the application associated with sessid has
been started, using slu for the Virtual Terminal LU.
System Action: Product communication with the started application will now
be possible.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGST001

POVI GLOBAL SESSION TABLE OPEN FAILED, RC=nn
Explanation: While determining the status of a VTAM application, an error
occurred.
System Action: Main menu application status will not be current.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGST002

APPSTAT INQUIRE FAILURE FOR APPLNM, RC=rc
Explanation: The status of the specified VTAM application could not be
determined.
System Action: Main menu application status will not be current.
User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.

KOGST003

APPLICATION STATUS NOT OBTAINED. TBSKIP RC=rc
Explanation: The status of an application could not be determined.
System Action: Main menu application status will not be current.

470

Candle Products Messages Manual (KLVHS–KONCT)

User Response: Examine the POVI log for more detailed messages describing
the problem.
Message Type: LOG.
KOGTB001

FUNCTION=TBCREATE RC=rc {description}
Explanation: A TBCREATE operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGTB002

FUNCTION=TBADD RC=rc {description}
Explanation: A TBADD operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGTB003

FUNCTION=TBGET RC=rc {description}
Explanation: A TBGET operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGTB004

{description} FUNCTION=TBDISPL RC=rc
Explanation: A TBDISPL operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGTB005

{description} FUNCTION=TBOPEN RC=rc
Explanation: A TBOPEN operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGTB006

FUNCTION=TBSKIP RC=rc {description}
Explanation: A TBSKIP operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.

KOGCM001–KONCT303

471

User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.
KOGTB007

FUNCTION=TBTOP RC=rc {description}
Explanation: A TBTOP operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGTB009

FUNCTION=TBPUT RC=rc {description}
Explanation: A TBPUT operation failed on an internal table.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGUT001

FUNCTION=PDS SETWRT RC=rc {description}
Explanation: A PDS I/O operation failed.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGUT002

FUNCTION=UNLOAD RC=rc REASON=(code,data) {description}
Explanation: An UNLOAD operation failed.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGUT003

The PDS Name is missing or invalid.
Explanation: PDS Name, a required field was not entered, or was entered
incorrectly.
System Action: None. A valid PDS Name must be entered first.
User Response: Correct the PDS Name and retry the function.
Message Type: LOG.

KOGUT004

At least one script must be selected.
Explanation: Enter was pressed to process selections, but no selections were
made.
System Action: None. A selection must first be made.
User Response: Make a selection and retry the function.
Message Type: LOG.

472

Candle Products Messages Manual (KLVHS–KONCT)

KOGUT005

Importing|Exporting scriptname from|to pdsname.
Explanation: The attempted import or export is being processed.
System Action: None. The message is informational.
User Response: None.
Message Type: LOG.

KOGUT006

Script successfully exported|imported.
Explanation: Selected scripts (except for those not confirmed) were successfully
exported or imported.
System Action: None. The message is informational.
User Response: None.
Message Type: LOG.

KOGUT007

FUNCTION=PDS FIND RC=rc {description}
Explanation: A PDS I/O operation failed.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGUT009

FUNCTION=LOAD RC=rc REASON=(code,data) {description}
Explanation: A LOAD operation failed.
System Action: The description describes the disposition of the function being
attempted.
User Response: Report the error message along with a problem description to
Candle Customer Support.
Message Type: LOG.

KOGUT010

No script export|import confirmed.
Explanation: Scripts were selected for import or export but none were
confirmed.
System Action: No scripts are imported or exported.
User Response: Reselect scripts for which import or export can be confirmed.
Message Type: LOG.

KOGUT011

scriptname exported|imported.
Explanation: The specified script was successfully imported or exported.
System Action: The import or export operation was successful.
User Response: None.
Message Type: LOG.

KOGCM001–KONCT303

473

KOGUT012

Records truncated. RECFM not V|VB or LRECL<512.
Explanation: A write of records having a length longer than LRECL was
attempted.
System Action: Some truncated data may have been written. The member
could have been corrupted.
User Response: Ensure that the member’s former contents are restored if this is
the wrong dataset. If this was the intended dataset, then reallocate it using the
correct RECFM and LRECL.
Message Type: LOG.

KOGVL00I

LU0 SESSION ESTABLISHED FROM SLU APPLID=applid
Explanation: A logon has been initiated by a VU Client to the VU Server task.
The applid identifies the remote VU Client APPLID which initiated the logon.
System Action: VU Server logon continues.
User Response: None. This is an informational message.

KOGVL02I

USERID=userid TRACE=trace RUSIZE=rusize
Explanation: A logon has been initiated by a VU Client to the VU Server task.
The userid identifies the USERID specified during the logon. The trace indicates
the level of trace message requested by the VU Client during logon. The rusize
indicates the maximum number of bytes that may be contained in the VTAM
request units transmitted to the VU Client.
System Action: VU Server logon continues.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL03S

UNABLE TO LOCATE VU SERVER ANCHOR BLOCK=address
Explanation: An attempt to locate the VU Server Anchor Block has failed. The
address specifies the location returned by anchor block look-up routines to find
the common block of storage used to store global execution flags and parameters.
This message normally occurs if a logon is attempted while the VU Server is
terminating or while the CT/DS address space is terminated.
System Action: VU Server logon fails and the LU0 session with the VU Client
is terminated.
User Response: Call Candle Customer Support if this message occurs during
normal operation of the CT/DS address space.

KOGVL04S

INVALID USERDATA OPTION=options
Explanation: Invalid USERDATA parameter was specified in the logon request.
The options value specifies the invalid values found in the USERDATA string
passed by a VU Client during the logon.
System Action: VU Server logon fails and the LU0 session with the VU Client
is terminated.
User Response: Verify that valid values are specified in the USERDATA field of
the product LOGON command.

474

Candle Products Messages Manual (KLVHS–KONCT)

KOGVL05S

UNABLE TO DETERMINE SLU APPLID
Explanation: An attempt to determine the SLU APPLID of the VU Client failed.
System Action: VU Server logon fails and the LU0 session with the VU Client
is terminated.
User Response: Call Candle Customer Support if this message occurs during
normal operation of the CT/DS address space.

KOGVL06S

UNABLE TO LOCATE VU SERVER IPC QUEUE
Explanation: An attempt to locate the VU Server Inter-process communication
queue has failed. This message normally occurs if a logon is attempted while the
VU Server is terminating or while the CT/DS address space is terminated.
System Action: VU Server logon fails and the LU0 session with the VU Client
is terminated.
User Response: Call Candle Customer Support if this message occurs during
normal operation of the CT/DS address space.

KOGVL07S

IPC QUEUE ERROR=rc
Explanation: An attempt to transmit data to the VU Server Inter-process
communication queue has failed. The rc value is the return code issued by the
IPC service routine and can be used to determine the cause of the IPC error.
This message normally occurs if a logon is attempted while the VU Server is
terminating or while the CT/DS address space is terminated.
System Action: VU Server logon fails, and the LU0 session with the VU Client
is terminated.
User Response: Call Candle Customer Support if this message occurs during
normal operation of the CT/DS address space.

KOGVL08E

UNABLE TO INITIALIZE rname
Explanation: An attempt to initialize a logical resource has failed. The rname
value indicates the name of the resource that could not be initialized.
This message normally occurs if a VU API service request is attempted while the
VU Server is terminating or while the CT/DS address space is terminated.
System Action: VU API service request fails, and an error code is returned to
the VU Client.
User Response: Call Candle Customer Support if this message occurs during
normal operation of the CT/DS address space.

KOGVL09E

UNABLE TO ALLOCATE MEMORY FOR rname
Explanation: An attempt to allocate memory for a logical resource has failed.
The rname value indicates the name of the resource that could not be allocated.
This message can occur if a VU API service request is attempted when the CT/DS
address space is experiencing a virtual storage shortage.
System Action: VU API service request fails and an error code is returned to
the VU Client.
User Response: Review CT/DS startup parameters controlling the allocation of
primary and extended virtual storage and verify that sufficient storage is available.
Call Candle Customer Support if this message occurs during normal operation of
the CT/DS address space.

KOGCM001–KONCT303

475

KOGVL10I

INBOUND LU0 PACKET (STATUS=status):
Explanation: This message precedes message KOGVL15I and is used to
diagnose VTAM session problems. The status value indicates the return code
issued by the VTAM RECEIVE service routine.
System Action: VU Server proceeds to service the requested VU API request
received in the LU0 packet.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL11S

INVALID FORMAT LU PACKET LENGTH=length
Explanation: An attempt to service a VU API request has failed because the
LU0 packet containing the service request was not within the expected size. The
length value indicates the size of the packet received. This message can occur if a
VTAM (ex: from a physical terminal) logs on to the VU Server session and
transmits improperly formatted data to the VU Server.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

KOGVL12S

INVALID LU0 PACKET HEADER LENGTH=length
Explanation: An attempt to service a VU API request has failed because the
LU0 packet containing the service request header was not within the expected
size. The length value indicates the size of the packet header received. This
message can occur if a VTAM (ex: from a physical terminal) logs on to the VU
Server session and transmits improperly formatted data to the VU Server.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

KOGVL13E

INVALID LU0 PACKET SEQUENCE NUMBER=inseq EXPECT=exseq
Explanation: An attempt to service a VU API request has failed because the
LU0 packet containing the service request did not specify the expected sequence
number. The inseq value indicates the value of the sequence number in the
packet received. The exseq value indicates the value of the sequence number that
was expected. This error message indicates that one or more packets may have
been lost due to VTAM transmission errors.
System Action: VU Server rejects the request and transmits an error response
to the client. The next expected sequence number for the VU Server is reset to
inseq+1
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

476

Candle Products Messages Manual (KLVHS–KONCT)

KOGVL14I

OUTBOUND LU0 PACKET:
Explanation: This message precedes message KOGVL15I and is used to
diagnose VTAM session problems.
System Action: VU Server proceeds to transmit the response packet to the VU
Client in response to a service request.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL15I

aaaaaaaaaa:xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx *cccccccccccccccc*
Explanation: This message follows messages KOGVL11I, KOGVL15I, and
KOGVL16E and is used to diagnose VTAM session problems. The message is
repeated one or more times to dump the contents of all or a portion of inbound
and outbound LU0 packets.
aaaaaaaaaa

specifies the address at which the LU0 buffer is located.

xxxxxxxx

the hexadecimal representation of the buffer contents.

cccccccccccccccc

the display character representation of the buffer contents.

System Action: VU Server proceeds to process or transmit the packet.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.
KOGVL16E

INVALID pdutype REQUEST PDU:
Explanation: An attempt to service a VU API request has failed because the
Protocol Data Unit which contains the request parameters did not contain the
expected number of parameters or was not formatted properly. The pdutype
value indicates the type of the VU API request issued. Message KOGVL15I follows
this message to dump the contents of the PDU for diagnosis.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure that unauthorized applications do not issue logon
requests to the VU Server session. If this error message reoccurs contact Candle
Customer Support for further diagnosis.

KOGVL20I

CLEANUP FOR SERVICE CALL VUPL=address TYPE=typeno
Explanation: Cleanup and termination of a VU API service parameter list
resource has been initiated. The address identifies the address of the control block
associated with the logical resource. The typeno indicates numeric type of the VU
API service request.
System Action: VU Server processes cleanup of the service request
parameters and frees memory associated with the parameters.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGCM001–KONCT303

477

KOGVL21I

CLEANUP FOR SESSION/PATH VUSPLR=address
Explanation: Cleanup and termination of a session/path resource has been
initiated. The address identifies the address of the control block associated with
the logical resource.
System Action: VU Server processes cleanup of the session/path resource,
frees memory associated with the resource, and terminates the VTAM session.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL22I

CLEANUP FOR REQUEST VURQLR=address
Explanation: Cleanup and termination of a VU request resource has been
initiated. The address identifies the address of the control block associated with
the logical resource.
System Action: VU Server processes cleanup of the request resource, frees
memory associated with the resource, and drops the VU API request.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL23I

AUTOMATIC DROPREQUEST ISSUED FOR REQUEST=lrn
Explanation: A DROP for a VU API request is automatically issued when the
VTAM session between a VU Client and the VU Server is terminated. The lrn
identifies the logical resource number of the VU API request. All VU request
handles created by service requests carried by the VTAM session to be terminated
are dropped automatically to ensure that resources associated with the requests
are terminated and released before the session is terminated.
System Action: VU Server initiates a DROP for the request and proceeds with
VTAM session termination.
User Response: None. This is an informational message.

KOGVL24I

lrtype CREATED. LRN=lrn @address
Explanation: A logical resource was successfully allocated and initialized by the
VU Server. The lrtype identifies the logical resource type that was created and
initialized. The lrn identifies the logical resource number assigned to the resource.
The address identifies the address of the control associated with the logical
resource.
System Action: VU Server proceeds with normal execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

478

Candle Products Messages Manual (KLVHS–KONCT)

KOGVL25E

INVALID REQUEST=reqtype FROM SLU APPLID=applid
MATCHNO=prcno
Explanation: An invalid request type for a VU request was specified by the VU
Client. The reqtype identifies the invalid request type specified by the VU Client.
The applid identifies the SLU APPLID of the VU Client. The prcno identifies the
process ID of the VU Client. This message is issued when an improperly formatted
VU API service request is received by the VU Server.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

KOGVL26E

UNABLE TO SEND RESPONSE PACKET STATUS=status
Explanation: An attempt to send a response to a VU Client by a VTAM session
has failed. The status value specifies the return code issued by the VTAM LU0
SEND service routine. This message is issued when an abnormal termination of a
VTAM LU0 session occurs.
System Action: VU Server makes no further attempts to notify the VU Client
of the disposition of the service call.
User Response: Verify that normal LOGOFF processing is used to terminate
VTAM sessions between VU Clients and Server address spaces. If this error
message reoccurs contact Candle Customer Support for further diagnosis.

KOGVL27E

UNABLE LOCATE SESSION FOR LRN=lrn
Explanation: An attempt to locate a session logical resource required to send a
response to a VU Client using a VTAM session has failed. The lrn value specifies
the logical resource number associated with the VU session/path logical resource
that could not be found. This message is issued when a VTAM session is
terminated while active service requests are in progress.
System Action: VU Server makes no further attempts to notify the VU Client
of the disposition of the service call.
User Response: Verify that session LOGOFF is not issued until all service
requests issued by VU Client processes have been completed.

KOGVL29E

VTAM LU0 SEND ERROR STATUS=status SENSE=sense
Explanation: An attempt to send a response to a VU Client using a VTAM
session has failed. The status value specifies the return code issued by the VTAM
LU0 send service routine. The sense value specifies the sense code issued by the
VTAM LU0 send service routine. This message is issued when an abnormal
termination of a VTAM LU0 session occurs.
System Action: VU Server makes no further attempts to notify the VU Client
of the disposition of a service call.
User Response: Verify that normal LOGOFF processing is used to terminate
VTAM sessions between VU Clients and Server address spaces. If this error
message reoccurs contact Candle Customer Support for further diagnosis.

KOGCM001–KONCT303

479

KOGVL30E

UNABLE TO TERMINATE lrtype STATUS=status
Explanation: An attempt to terminate and cleanup a logical resource has failed.
The lrtype is the value type of the logical resource which could not be terminated.
The status value specifies the return code issued by the logical resource manager.
This message is issued when an invalid resource number is specified by a VU
Client or the resource number of a previously terminated resource was specified.
System Action: VU Server makes no further attempts to terminate the
resource and an error status is returned to the VU Client initiating the service
request.
User Response: Verify that the acceptable sequence of VU API service calls is
issued. For example, an attempt to DROP a VU request handle more than once
from 2 or more matches can cause this error. If this error message reoccurs contact
Candle Customer Support for further diagnosis.

KOGVL31E

BAD pdutype CONTINUATION. SEQNO=seqno EXPECTED=eseqno
Explanation: A continutation of a multi-packet Protocol Data Unit was
improperly formatted. The pdutype value indicates the type service request that
could not be continued. The seqno value specifies the PDU sequence number
found in the continuation packet. The eseqno value specifies the PDU sequence
number that was expected. This message is caused when normal packet
transmission is interrupted and restarted, resulting in the loss of packets, or when
PDUs in packets are incorrectly formatted by the VU Client.
System Action: VU Server rejects the continuation request and transmits an
error response to the client. Any further attempts to continue the service request
will be rejected.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

KOGVL31E

UNEXPECTED pdutype PDU SEQNO=seqno
Explanation: A multi-packet Protocol Data Unit was improperly formatted. The
pdutype value indicates the type service request. The seqno value specifies the
PDU sequence number found in the continuation packet. This message is issued
when normal packet transmission is interrupted and restarted, resulting in the loss
of packets, or when PDUs in packets are incorrectly formatted by the VU Client.
System Action: VU Server rejects the request and transmits an error response
to the client. Any further attempts to continue the service request will be rejected.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

480

Candle Products Messages Manual (KLVHS–KONCT)

KOGVL33I

pdutype REQUEST CONTINUED. LRN=lrn @address SEQNO=seqno
Explanation: An multi-packet Protocol Data Unit was successfully continued.
The pdutype value indicates the type of service request. The lrn indicates the
logical resource number of the VU parameter list. The address indicates the
address of the VU parameter list being continued. The seqno value specifies the
PDU sequence number found in the continuation packet.
System Action: VU Server proceeds with normal execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL34I

pdutype PDU BEING PARSED BY routine
Explanation: A Protocol Data Unit containing VU API service parameters is
being processed by a VU Server routine. The pdutype value indicates the type
service request. The routine indicates the name of the VU Server routine handling
the service request.
System Action: VU Server proceeds with normal execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL35I

PREVIOUS pdutype PARMS LOCATED LRN=lrn @address
Explanation: A previously started set of service call parameters have been
located for continuation. The pdutype value indicates the type of service request.
The lrn indicates the logical resource number of the VU parameter list. The
address indicates the address of the VU parameter list.
System Action: VU Server proceeds with normal execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL36I

CONTINUATION OF pdutype SUCCESSFUL
Explanation: A multi-packet Protocol Data Unit has been reassembled
successfully and will now be dispatched for service execution. The pdutype value
indicates the type of service request.
System Action: VU Server proceeds with dispatch of the service request.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVL37E

INVALID REQUEST LRN=lrn SPECIFIED IN pdutype PDU
Explanation: An invalid logical resource number for a VU request was specified
by the VU Client. The lrn identifies the invalid logical resource number. The
applid identifies the SLU APPLID of the VU Client. The prcno identifies the
process ID of the VU Client.
This message is issued when a VU request handle is used after a DROP has been
successfully completed on the request or when an invalid request handle has been
specified in the VU API service call.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure that the proper sequence of VU API service calls and
that VU API request handles are reused properly.

KOGCM001–KONCT303

481

KOGVL38E

INVALID NO. SUBSTITUTE VALUES=novals EXPECTED=enovals
Explanation: The number of values received in a substitution specified by the
VU Client. The lrn identifies the invalid logical resource number specified by the
VU Client. The applid identifies the SLU APPLID of the VU Client. The prcno
identifies the process ID of the VU Client.
This message is issued when a VU request handle is used after a DROP has been
successfully completed on the request or when an invalid request handle has been
specified in the VU API service call.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

KOGVL40E

UNEXPECTED pduprocess ERROR. STATUS=status FETCH ABORTED
Explanation: The processing of a Protocol Data Unit containing a VU API
service request caused an internal processing error to occur. The pduprocess
identifies the specific point in processing at which the error occurred. The status
identifies status code returned by the internal service routines called to process the
PDU. This message is issued when an improperly formatted VU API service
request is received by the VU Server.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

KOGVL41E

COLUMN(colno) TOO BIG FOR LU0 PACKET(rusize)
Explanation: The queried value of a column of data to be fetched exceeds the
maximum request unit size that may be transmitted in a response packet to the
VU Client. The colno identifies the relative column number within the row to be
fetched that exceeds the size of the response packet. The rusize specifies the
maximum number of bytes that can be transmitted to the VU Client.
System Action: VU Server rejects the fetch request and transmits an error
response to the client.
User Response: Ensure that the matching version of the VU API is used to
communicate to the VU Server. Also ensure that unauthorized applications do not
issue logon requests to the VU Server session. If this error message reoccurs
contact Candle Customer Support for further diagnosis.

KOGVL99I

TERMINATING SESSION WITH SLU APPLID=applid
Explanation: A session with a VU Client is termininating. The applid value
indicates the SLU APPLID that identifies the VU Client.
System Action: VU Server proceeds with termination and shutdown of the
LU0 session.
User Response: None. This is an informational message only.

482

Candle Products Messages Manual (KLVHS–KONCT)

KOGVS001

LU(luname) STARTING VIRTUAL SESSION FOR sessid, APPL=appl,
POOL=pool, LOGMODE=logmode
Explanation: The session given by sessid will be started using the specified
parameters.
System Action: An attempt will be made to start the session.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGVS002

description FUNCTION=VSSFOREG RC=nnn
Explanation: An attempt to start a session failed with the specified return code.
A brief description of the failure is also given.
System Action: The session is not started, and a return is made to the main
menu, displaying this message on the message line.
User Response: Ensure that TLVPARM RKOGPARM(KOGSYSIN) contains
DEBUG(Y), recreate the problem, and locate messages KLVVT021 and/or
KLVVT251 in the POVI log. These messages, output when the DEBUG option is
set, identify the specific cause of the error.
Message Type: LOG.

KOGVS003

FIELD IS PROTECTED {LU(luname) SESSID(sessid)}
Explanation: POVI 3270 automation attempted to type data into a protected
field.
System Action: The data is not typed and this message is returned to the POVI
main menu message line and is output to the POVI log. When the message is
output to the POVI log the controlling product luname and POVI sessid are given
so that the offending automation program can be identified.
User Response: Correct the automation program.
Message Type: LOG.

KOGVS004

LU(luname1) VIRTUAL LU luname2 ACTIVE
Explanation: The product LU given by luname1 has logged onto the POVI
playback manager and started a session with an application using the virtual LU
given by luname1.
System Action: Commands from the product to control the application will
now be accepted.
User Response: None. This is an informational message only.
Message Type: LOG.

KOGVS00I

VU SERVER STARTED
Explanation: This message is issued during the initialization of the CT/DS
address space to indicate that VU Server processing has begun execution.
System Action: VU Server startup continues.
User Response: None. This is an informational message.

KOGCM001–KONCT303

483

KOGVS01E

INVALID VALUE FOR PLU APPLID=applid
Explanation: The VTAM Primary Logical Unit Application ID specified in the
KDSCNFG member of the TLVPARM ddname dataset is invalid. The applid value
indicates the value specified on the START KOGVUSRV control statement. This
value is required and must specify an active VTAM APPLID defined for the VU
Server process.
System Action: VU Server is aborted.
User Response: Correct the START KOGVUSRV startup control statement to
refer to the valid PLU APPLID as described in the installation documentation.
Verify that the PLU APPLID is properly configured and varied active.

KOGVS02E

INVALID VALUE FOR TIMEOUT=seconds
Explanation: The inactivity time limit specified in the KDSCNFG member of the
TLVPARM ddname dataset is invalid. The seconds value indicates the value
specified on the START KOGVUSRV control statement. This value is optional but,
if specified, must be numeric in format.
System Action: VU Server startup is aborted.
User Response: Correct the START KOGVUSRV startup control statement to
specify a valid time limit as described in the installation documentation.
Note: The CT/DS (Data Collection) address space must be restarted to restart
the VU Server.

KOGVS03E

INVALID VALUE FOR TRACE=level
Explanation: The trace level specified in the KDSCNFG member of the
TLVPARM ddname dataset is invalid. The level value indicates the value specified
on the START KOGVUSRV control statement. This value is optional but, if
specified, must be one of the following values: ALL, FLOW, PACKETS, SQL1,
SERVER, THREAD, or LU0.
System Action: VU Server startup is aborted.
User Response: Correct the START KOGVUSRV startup control statement to
specify a valid trace level, as described in the installation documentation.

KOGVS04I

ANCHOR=addr PLU APPLID=applid TIMEOUT=seconds TRACE=level
Explanation: This message reports the startup values used by the VU Server for
execution. The addr value indicates the VU Server anchor control block address
where global system options are stored during the life of the VU Server process.
The applid value indicates that Primary Logical Unit Application ID used by the
VU Server process to receive logon requests from VU Clients. The seconds value
indicates the inactivity time limit in seconds at which the VU Server process will
terminate VTAM sessions. A value of zero indicates that no inactivity limit is set.
The level value indicates the level of trace messages to be displayed in the
TLVLOG output.
System Action: VU Server startup continues.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

484

Candle Products Messages Manual (KLVHS–KONCT)

KOGVS05E

VU SERVER IPC QUEUE CREATE ERROR=status
Explanation: An attempt to create the interprocess communication queue for
the VU Server process has failed. The status value indicates the return code
received from the IPC service routine called to create the message queue. This
message is issued when the CT/DS address space is not properly configured or
installed.
System Action: VU Server startup is aborted.
User Response: Review installation and configuration of the CT/DS software. If
the problem source cannot be determined, call Candle Customer Support.

KOGVS06E

UNABLE TO START PLU APPLID=applid STATUS=status
Explanation: The VTAM Primary Logical Unit Application ID specified in the
KDSCNFG member of the TLVPARM ddname dataset cannot be opened by the
VU Server. The applid value indicates the value specified on the START
KOGVUSRV control statement. This value is required and must specify an active
VTAM APPLID defined for the VU Server process.
System Action: VU Server is aborted.
User Response: Correct the START KOGVUSRV startup control statement to
refer to a valid PLU APPLID as described in the installation documentation. Verify
that the PLU APPLID is properly configured and varied active.

KOGVS10E

IPC DEQUEUE ERROR=status
Explanation: An attempt to read data from the interprocess communication
queue for the VU Server process has failed. The status value indicates the return
code received from the IPC service routine called to read the message queue. This
message is issued when the CT/DS address space is not properly configured or
installed.
System Action: VU Server execution is terminated.
User Response: Review installation and configuration of the CT/DS software. If
the problem source cannot be determined, call Candle Customer Support.

KOGVS11I

VU SERVER SHUTDOWN IN PROGRESS
Explanation: This message is issued during the shutdown of the CT/DS address
space to indicate that VU Server shutdown has begun.
System Action: VU Server continues cleanup and termination processing.
User Response: None. This is an informational message.

KOGVS12E

INVALID IPC MESSAGE RECEIVED. LENGTH=length
Explanation: An incorrectly formatted message was received from the VU
Server interprocess communication message queue. The length value indicates
the length of the improperly formatted message. This message is issued when the
VU Server software is not properly configured or installed.
System Action: VU Server execution is terminated.
User Response: Review installation and configuration of the VU Server
software. If the problem source cannot be determined, call Candle Customer
Support.

KOGCM001–KONCT303

485

KOGVS13I

VUPL=address DISPATCHED TO THREAD=threadID
Explanation: A VU service request has been successfully dispatched to a thread
process for execution. The address is the address of the VU service parameter list.
The threadId is internal thread number of the task created to execute the service
request.
System Action: VU Server proceeds to execute the requested service.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVS20E

VU THREAD CREATE ERROR=status
Explanation: An attempt to dispatch a VU service request to a thread has failed.
The status value indicates the return code received from the process creation
service routine. This message is issued when the CT/DS address space is not
properly configured or installed.
System Action: VU Server continues to service other requests.
User Response: Review installation and configuration of the CT/DS software. If
the problem source cannot be determined, call Candle Customer Support.

KOGVS90S

VU SERVER INITIALIZATION FAILED
Explanation: A severe error has occurred to prevent the successful initialization
of the VU Server process. Error messages describing the cause of the startup
failure precede this message.
System Action: VU Server startup is aborted.
User Response: Refer to the user responses of error messages issued by the VU
Server before this message was issued. Correct the cause of the error and restart
the CT/DS (Data Collection) address space to restart the VU Server.

KOGVS99I

VU SERVER IS TERMINATING
Explanation: This message is issued during the shutdown of the CT/DS address
space to indicate that VU Server shutdown has completed.
System Action: VU Server terminates.
User Response: None. This is an informational message.

KOGVT00I

VU THREAD STARTED
Explanation: This message is issued whenever a VU API service request has
been dispatched for execution. It can be used to mark the date and time at which
the service request begins execution.
System Action: The VU API service request begins execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

486

Candle Products Messages Manual (KLVHS–KONCT)

KOGVT10E

UNABLE TO LOCATE PARAMETERS LRN=lrn
Explanation: An attempt to locate a VU service parameter list resource required
to execute a service request has failed. The lrn value specifies the logical resource
number associated with the VU parameter list logical resource that could not be
found.
This message indicates an internal error has occurred.
System Action: VU Server makes no further attempts to notify the VU Client
of the disposition of a service call.
User Response: Call Candle Customer Support for further diagnosis.

KOGVT14I

VUPL TYPE=vupltype CONTENTS:
Explanation: A VU API service request has been dispatched for execution. It
precedes message KOGVT15I that dumps the contents of the VU parameter list,
which describes the requested service to be executed.
System Action: VU API service request begins execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT15I

aaaaaaaaa:xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx *cccccccccccccccc*
Explanation: This message follows messages KOGVT14I and KOGVT16E to
dump the contents of the VU parameter list for a service request.
aaaaaaaaaa

specifies the address of the parameter list.

xxxxxxxx

the hexadecimal representation of the parameter list contents.

cccccccccccccccc

the display character representation of the parameter list contents.

System Action: VU API service request begins execution.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.
KOGVT16E

PROCESS FUNCTION NOT SPECIFIED:
Explanation: A VU parameter list did not specify the address of the function to
be called to service the request. This message precedes message KOGVT15I. This
message indicates that an internal error has occurred.
System Action: VU Server makes no further attempts to execute the service
request.
User Response: Call Candle Customer Support for further diagnosis.

KOGCM001–KONCT303

487

KOGVT17W

LOCATE SERVER FAILED STATUS=status REASON=reason
Explanation: The CT Data Server name cannot be located during logon
processing. The status value is the status returned by the CT/DS name lookup
routine. The reason value is the reason code returned by the CT/DS server name
lookup routine.
This message indicates an internal error has occurred. The server name is
required for the create path service call which is issued during VU Server session
logon to verify access to CT/DS.
System Action: The VU Server uses the default name "SRVR01" as the CT/DS
server name and proceeds with SQL1 create path processing.
User Response: Call Candle Customer Support for further diagnosis.

KOGVT18I

CT/DS SERVER NAME=name FOUND
Explanation: The CT Data Server name lookup routine has successfully located
the name of the data server. The server name is required for the create path
service call which is issued during VU Server session logon to verify access to
CT/DS. The name value displays the data server name.
System Action: VU API create path processing continues.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT19I

CT/DS SERVER NAME NOT FOUND USING default
Explanation: The CT Data Server name lookup routine could not locate the
name of the data server. The server name is required for the create path service
call which is issued during VU Server session logon to verify access to CT/DS. The
default value displays the default data server name that will be used in create path
processing.
System Action: VU API create path processing continues.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT20I

sqlroutine CALLED STATUS=status
Explanation: This message indicates that an internal service routine (SQL1 API
function) was called and displays the integer status code returned by the routine.
The sqlroutine value indicates the name of the internal service routine called. The
status value is the integer return code issued by the service routine.
System Action: VU API service request execution continues.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT21E

LOGON FAILED FOR USERID=userID STATUS=status
Explanation: An attempt to logon to the CT Data Server has failed. The userID
value indicates the user ID specified in the VU Client LOGON command. The
status value is the integer return code issued by the create path service routine.
System Action: The VTAM session between the VU Client and the VU Server
is terminated.
User Response: Ensure that security options have been set to allow the user ID
to access the VU Server.

488

Candle Products Messages Manual (KLVHS–KONCT)

KOGVT22E

sqlroutine FAILED. STATUS=status
Explanation: An internal service routine (SQL1 API function) was called and
returned a non-zero integer status code indicating an error. The sqlroutine value
indicates the name of the internal service routine called. The status value is the
integer return code issued by the service routine.
This error message is normally issued when invalid service parameter values are
passed in service requests. For example, a syntax error in the search criteria
specified in a VUQUERY API function call will result in an
SQL1_CreateAccessPlan failure.
System Action: VU API service request completes and an error status is
returned to the VU Client.
User Response: Correct the VU API function parameter that causes the service
routine to reject the service request.

KOGVT23W

CT/DS LOGOFF FAILED STATUS=status
Explanation: CT/DS service routines indicate an unsuccessful drop path
operation. The status value is the integer return code issued by the internal service
routine. A drop path service call is issued during termination of the VTAM session
between a VU Client and the VU Server. The drop path call ensures that active
requests and resources are terminated and released before logoff.
This error message normally occurs when sessions are terminated during CT/DS
(Data Collection) address space shutdown.
System Action: VTAM logoff processing proceeds.
User Response: If this message is issued during normal CT/DS operation call
Candle Customer Support for further diagnosis.

KOGVT24E

REQUEST NOT FOUND FOR LRN=lrn
Explanation: A VU request handle cannot be located for requested processing.
The lrn value is an integer identifier for the request handle.
This message is issued when a VU request handle is used after a DROP has been
successfully completed on the request or when an invalid request handle has been
specified in the VU API service call.
System Action: VU Server rejects the request and transmits an error response
to the client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

KOGVT25I

NUMBER OF SUBSTITUTION SYMBOLS FOUND=noparms
Explanation: This message displays the number of substitution symbols found
after successfully compiling a query, insert, or delete request. The noparms value
indicates the number of substitution symbols found in the compiled request.
System Action: VU Server completes the request and transmits a successful
response to the client.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGCM001–KONCT303

489

KOGVT26I

COMPILING SQL=sql
Explanation: This message is issued prior to compilation of a query, insert, or
delete request. The sql value displays the SQL statement to be compiled.
System Action: VU Server proceeds to call internal service routines to compile
the SQL statement.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT27I

AUTOMATIC CLOSE ISSUED FOR REQUEST LRN=lrn
Explanation: This message is issued when an open VU request handle is found
prior to a drop of the request handle. The close is done automatically to ensure
that resources associated with the request handle are terminated and released
before the request handle drop processing is initiated. The lrn value is the logical
resource number associated with the VU request handle.
System Action: VU Server proceeds to call internal service routines to close
and drop the request.
User Response: None. This is an informational message.

KOGVT28E

OPEN ATTEMPTED ON REQUEST LRN=lrn ALREADY OPEN
Explanation: An attempt to open a VU request handle was made but the
request has already been opened. The lrn value is the logical resource number
associated with the VU request handle.
System Action: VU Server completes the requested VUOPEN service call and
returns an error status to the VU Client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

KOGVT29E

REQUEST LRN=lrn INVALID ALREADY DROPPED
Explanation: An attempt to drop a VU request handle was made but the handle
could not be found. The lrn value is the logical resource number associated with
the VU request handle.
System Action: VU Server completes the requested VUDROP service call and
returns an error status to the VU Client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

KOGVT30E

CLOSE ATTEMPTED ON REQUEST LRN=lrn ALREADY CLOSED
Explanation: An attempt to close a VU request handle was made but the
request has already been closed. The lrn value is the logical resource number
associated with the VU request handle.
System Action: VU Server completes the requested VUCLOSE service call
and returns an error status to the VU Client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

490

Candle Products Messages Manual (KLVHS–KONCT)

KOGVT31I

SUBSTITUTING novals VALUES INTO REQUEST LRN=lrn
Explanation: This message is issued prior to executing a substitute request. The
novals value is the number of values to be inserted into substitution symbols. The
lrn value is the logical resource number associated with the VU request handle.
System Action: VU Server proceeds to execute the requested VUSUBST
service call.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT32E

SUBSTITUTE FAILED FOR REQUEST LRN=lrn ALREADY OPEN
Explanation: An attempt to substitute values into a VU request handle cannot
be executed because the request has already been opened. The lrn value is the
logical resource number associated with the VU request handle.
System Action: VU Server completes the requested VUSUBST service call
and returns an error status to the VU Client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

KOGVT33E

INVALID NO.SUBSTITUTE VALUES=novals EXPECTED=expected
Explanation: An attempt to substitute an improper number of values into a
query, insert, or delete request handle has been detected. The novals value
indicates the number of values to be substituted. The expected value indicates the
number of substitution symbols found in the VU request handle.
System Action: VU Server completes the requested VUSUBST service call
and returns an error status to the VU Client.
User Response: Ensure the number of substitution values specified in the
VUSUBST service call matches the substitution symbols generated by the VU
Template plus the number specified in the optional search criteria, if any.

KOGVT34E

KOGCM001–KONCT303

491

KOGVT34I

SUBSTITUTING parmname=value TYPE=type LENGTH=length
Explanation: This message is issued prior to substituting a value into a
substitution symbol found in a compiled VU request. The parmname value
indicates the column or relative position of the substitution symbol that will be
assigned a value. The value displays the value to be assigned to the symbol. The
type value indicates the format expected for the substitution value (INTEGER,
CHAR, BITSTRING, and so forth). The length value indicates the maximum
length of the value to be substituted.
System Action: The VU Server proceeds to substitute all values.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT35E

SUBSTITUTION VALUE FOR parnname INVALID "value" (type,length)
Explanation: An incorrectly formatted value was specified for a substitution
symbol in a VUSUBST service call. The parmname value indicates the column or
relative position of the symbol. The value displays the value to be assigned to the
symbol. The type value indicates the expected format of the substitution value
(INTEGER, CHAR, BITSTRING, and so forth). The length value indicates the
maximum length of the value to be substituted.
System Action: The VU Server completes the requested VUSUBST service
call and returns an error status to the VU Client.
User Response: Correct the incorrectly formatted substitution value and
ensure that the proper values are matched to the substitution symbols specified by
the VU Template and by the optional search criteria in query requests.

KOGVT36E

SUBSTITUTION VALUE FOR parmname TRUNCATED FROM len TO newlen
Explanation: A value specified for a substitution symbol in a VUSUBST service
call exceeds the maximum length acceptable. The parmname value indicates the
column or relative position of the symbol. The len displays the length of the value
to be substituted. The newlen value indicates the truncated length of the value.
System Action: Character values are right truncated to the maximum number
of characters accepted by the substitution symbol. Integer values will have high
order bits truncated to fit within the maximum length. Decimal and Floating point
values will have least significant digits truncated to fit the maximum length.
Bitstrings will be right truncated to the maximum number of characters accepted.
The VU Server completes the requested VUSUBST service call and returns a
warning status to the VU Client.
User Response: Correct the substitution value to ensure the values are the
proper lengths.

KOGVT37E

FETCH ATTEMPTED ON CLOSED REQUEST LRN=lrn
Explanation: An attempt to fetch rows from a closed VU request handle has
occurred. The lrn value is the logical resource number associated with the VU
request handle.
System Action: VU Server completes the requested VUFETCH service call
and returns an error status to the VU Client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API requesthandles are reused properly.

492

Candle Products Messages Manual (KLVHS–KONCT)

KOGVT38E

FETCH ATTEMPTED BEYOND END OF DATA REQUEST LRN=lrn
Explanation: An attempt to fetch rows beyond the last row of a query was
made. Normally, an end-of-table status value is returned when the last row of a
result table is fetched. This error message is issued when the VU Client issues a
VUFETCH service call after the end-of-table indication in a previous VUFETCH
call. The lrn value is the logical resource number associated with the VU request
handle.
System Action: VU Server completes the requested VUFETCH service call
and returns an error status to the VU Client.
User Response: Ensure the proper sequence of VU API service calls and that
VU API request handles are reused properly.

KOGVT40I

colname(type,length)=value
Explanation: This message logs the retrieval of a column value in a row fetched
by a VUFETCH service call. The colname value indicates the column or relative
position of the column in the row to be fetched. The type value indicates the
format of the column (INTEGER, CHAR, BITSTRING, and so forth). The length
value indicates the length of the column value. The value displays the column
value retrieved.
System Action: VU Server proceeds to the next column in the row(s) to be
fetched.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KOGVT99I

VU THREAD IS TERMINATING
Explanation: This message is issued whenever a VU API service request has
completed execution. It can be used to mark the date and time at which the
service request completes execution.
System Action: VU API service request completes.
User Response: None. This is a diagnostic message issued when TRACE
options have been enabled.

KONAF001

KONAF002

KOGCM001–KONCT303

493

KONAF003

KONAF004

KONAF005

NDM FUNCTIONS MODULE KONAFNDM LOAD FAILED. NCP
STATISTICS DATA NOT AVAILABLE
Explanation: The automatic collection task (ACT) load of the NCP data
manager (NDM) functions module failed.
System Action: NCP statistics information is not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF006

MEMBER KONCNMAP CONTAINS INVALID ACB NAME
Explanation: The ACB name found exceeds eight alphanumeric characters.
System Action: None.
User Response: Correct the ACB name and restart OMEGAMON II for VTAM.
Message Type: User error.

KONAF007

MEMBER KONCNMAP IS EMPTY OR NOT FOUND
Explanation: The member KONCNMAP does not exist in dataset RKANPAR, or
this member does not contain the ACB name to be used for the communication
network management (CNM) interface.
System Action: None.
User Response: Check the OMEGAMON II for VTAM Configuration and
Customization Guide about member KONCNMAP, which resides in dataset
RKANPAR.
Message Type: User error.

494

Candle Products Messages Manual (KLVHS–KONCT)

KONAF010

KONAF011

KONAF012

KONAF013

KOGCM001–KONCT303

495

KONAF021

KONAF031

KONAF032

KONAF041

ETE CONNECTION FAILED — MODULE(error_module) RC(return_code)
SC(sense_code)
Explanation: During session establishment for a user, OMEGAMON II for VTAM
detected that the end-to-end response time environment was not connected.
OMEGAMON II for VTAM encountered an error while attempting to connect the
ETE environment.
System Action: Session establishment continues without the ETE feature.
User Response: Verify that the ETE started task is active and that you are
running the correct level of ETE. Also, review the information on enabling ETE in
the OMEGAMON II for VTAM Configuration and Customization Guide. Verify
that all steps completed are accurate. Then, retry logon. If problem persists, gather
the preceding 30 minutes of the RKLVLOG and any dumps that were produced or
taken, and contact Candle Support Services.
Message Type: Probable user error.

496

Candle Products Messages Manual (KLVHS–KONCT)

KONAF042

KONAF043

KONAF044

KONAF045

KOGCM001–KONCT303

497

KONAF046

KONAF047

KONAF048

KONAF050

CLUSTER INITIAL LOAD SUCCESSFUL FOR DDNAME(ddname)
Explanation: Cluster was successfully reopened and loaded with control record
for the specified ddname.
System Action: Cluster is loaded.
User Response: None.
Message Type: Information.

498

Candle Products Messages Manual (KLVHS–KONCT)

KONAF051

KONAF052

UNABLE TO ACCESS RKANPAR — MODULE(error_module)
Explanation: This message is issued in conjunction with message KONAF060.
During the initialization of VSAM logging, an error occurred requesting access to
the RKANPAR library. A member of this library contains the name of the VSAM
clusters.
System Action: VSAM logging is disabled.
User Response: Gather the preceding 30 minutes of the RKLVLOG and any
dumps that were produced or taken, and contact Candle Support Services.
Message Type: Warning.

KONAF053

member_name NOT FOUND IN RKANPAR — MODULE(error_module)
Explanation: This message is issued in conjunction with message KONAF060.
During the initialization of VSAM logging, the member member_name was not
found in the RKANPAR library. This member should be present in RKANPAR and
contain the names of two predefined VSAM clusters.
System Action: VSAM logging is disabled.
User Response: Check that the RKANPAR library is not back-leveled.
Message Type: Installation error.

KONAF054

ERROR WHEN READING member_name — MODULE(error_module)
Explanation: This message is issued in conjunction with message KONAF060.
During the initialization of VSAM logging, an error occurred while reading
member member_name from the RKANPAR library. This member should contain
the names of two predefined VSAM clusters.
System Action: VSAM logging is disabled.
User Response: Check member member_name in the RKANPAR library.
Message Type: Warning.

KONAF055

ERROR WHEN PARSING member_name — MODULE(error_module)
Explanation: This message is issued in conjunction with message KONAF060.
During the initialization of VSAM logging, an error occurred while parsing
member member_name in the RKANPAR library. This member should contain
the names of two predefined VSAM clusters.
System Action: VSAM logging is disabled.
User Response: Check member member_name in the RKANPAR library.
Message Type: Installation error.

KOGCM001–KONCT303

499

KONAF056

KONAF057

KONAF058

KONAF059

500

Candle Products Messages Manual (KLVHS–KONCT)

KONAF060

Some modules are missing.

ALLOC

Error during VSAM dataset allocation.

INIT

Error during initial load to VSAM cluster.

PUT

Error during VSAM PUT. Probable DASD problem.

INTERNAL

Internal error.

ABEND

Abend occurred during logging to VSAM cluster.

VSAMSERV

Internal VSAM services are unavailable.

System Action: VSAM logging is disabled.
User Response: Check for accompanying messages for any of the following
reasons:.
LOAD

Check installation.

ALLOC

Check installation.

PUT, INIT

Check for DASD problem.

INTERNAL,
ABEND

Contact Candle Support Services.

VSAMSERV

Check to make sure that termination was requested. If it was not,
gather the preceding 30 minutes of the RKLVLOG and any dumps
that were produced or taken, and contact Candle Support
Services.

Message Type:

Warning.

KONAF061

KONAF062

KOGCM001–KONCT303

501

KONAF110

KONAF111

KONAF112

KONAF113

KONAF114

KONAFNM0 - NO HASH TABLE ADDRESS FOUND IN NDA WORKAREA
Explanation: The address of the KONAYNRE hash table was not found in the
NCP data manager task global anchor block, KONAYNDA.
System Action: The NCP Performance light on the main status panel displays
IDLE.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

502

Candle Products Messages Manual (KLVHS–KONCT)

KONAF115

KONAFNM1 - UNABLE TO LOCATE SITE MONITOR TABLE: tablename.
Explanation: The dialog function was unable to obtain the handle of the NCP
site monitor table, tablename.
System Action: The threshold block, KONAYNPB, is not updated with the
NCP site default monitor options.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF116

KONAFNM1 UNABLE TO BUILD|LOCATE|MODIFY NPB|NSB FOR
resource_name TYPE=resource_type RC=return_code.
Explanation: An error occurred while processing an update request to the NCP
site monitor table options. The requested control block function has returned an
error. resource_name is the name of the resource, resource_type is the NRE
resource type and return_code is the return code from the control block function.
System Action: The NCP monitoring options are not updated.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF117

KONAF118

KONAF119

NDM CONTROL MODULE KONAFNSB LOAD FAILED. NCP STATISTICS
DATA NOT AVAILABLE.
Explanation: The automatic collection task (ACT) load of the NCP data
manager (NDM) control module failed.
System Action: NCP statistics information is not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KOGCM001–KONCT303

503

KONAF120

KONFCCMD INSTALL NDMT was not performed at product
initialization. Install NDMT and restart the automatic collection task.

NDMDRLRN

Unable to acquire CT/Engine logical resource number. Log the
information displayed for problem diagnosis and contact Candle
Support Services.

ABEND

An abend occurred. Log the information displayed for problem
diagnosis and contact Candle Support Services.

Message Type:

User or internal error.

KONAF121

KONAF122

KONAF123

KONAF124

504

Candle Products Messages Manual (KLVHS–KONCT)

KONAF125

KONAF126

KONAF127

KONAF128

KONAFNDM ABEND CODE(abend_code) ROUTINE(routine_name)
Explanation: An abend occurred in a KONAFNDM process routine.
System Action: NCP statistics information is not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF129

KONFCCMD INSTALL NDMT was not performed at product
initialization. Install NDMT and restart the automatic collection task.

ABEND

An abend occurred. Log the information displayed for problem
diagnosis and contact Candle Support Services.

Message Type:

Internal or user error.

KOGCM001–KONCT303

505

KONAF130

KONAF131

KONAF132

KONAFNSB ABEND CODE(abend_code) ROUTINE(resource_name)
Explanation: An abend occurred in a KONAFNSB process routine.
System Action: NCP statistics information may not be available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF133

506

Candle Products Messages Manual (KLVHS–KONCT)

KONAF134

KONAF135

KONAF136

KONAXNPB ADD_NPB FUNCTION FAILED RC(return_code)
MODULE(module_name)
Explanation: An error occurred while adding an NCP parameter block (NPB) to
the NPB chain. Return code and issuing module are displayed in the message
text.
System Action: If the error occurred in module KONAFNMI, the NCP
component cannot successfully complete initialization. However, if the error
occurred in a module other than KONAFNMI, only the ADD for the selected
resource fails.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF137

KONAXNSB ADD FUNCTION FAILED RC(return_code)
MODULE(module_name)
Explanation: An error occurred while adding an NCP parameter block (NPB) to
the NPB chain. Return code and issuing module are displayed in the message
text.
System Action: If the error occurred in module KONAFNMI, the NCP
component cannot successfully complete initialization. However, if the error
occurred in a module other than KONAFNMI, only the ADD for the selected
resource fails.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KOGCM001–KONCT303

507

KONAF138

KONAXNPB GET_HASH FUNCTION FAILED RC(return_code)
MODULE(module_name)
Explanation: An error was encountered in creating the NCP parameter block
(NPB) hash table. Return code and issuing module are displayed in the message
text.
System Action: NCP component cannot successfully complete initialization.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF139

KONAF140

KONAF141

KONAF142

508

Candle Products Messages Manual (KLVHS–KONCT)

KNOAF143

NCP VSAM LOGGING MODULE KONAFNVW LOAD FAILED. NCP
STATISTICS DATA NOT AVAILABLE.
Explanation: The automatic collection task (ACT) was unable to load
KONAFNVW.
System Action: NCP statistics are not available.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF144

KONAFNDM SMFWTM FAILED TO LOG SMF RECORD RC (return_code)
Explanation: An error occurred while logging an SMF record table. Return code
is displayed in message text.
System Action: NCP statistics are not logged to SMF.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF145

KONAFNDU UNABLE TO ALLOCATE KONAYNRE (control_block_name)
SEGMENT FOR RESOURCE(resource_name) NPALU(npalu_name)
Explanation: The automatic collection task (ACT) was unable to allocate a
control block.
System Action: NCP statistics are not available for the NCP resource.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF146

KONAFNMI - NCP DATA MANAGER TASK NOT INSTALLED
Explanation: The OMEGAMON II for VTAM initialization process detected that
the NCP data manager task was not installed.
System Action: NCP statistics are not available.
User Response: Ensure that a KONFCCMD INSTALL NDMT is specified in
KONSTKON. For more information, see the OMEGAMON II for VTAM
Configuration and Customization Guide.
Message Type: User error.

KONAF147

module_name NPALU=npalu_name, OWNER=resource_name,
GENDATE/TIME=generation_date/generation_time
Explanation: This message follows message number KONAF118 and gives
additional information about the failing resource. module_name is the name of
the module detecting the error, npalu_name is the name of the NPALU resource,
resource_name is the owning resource name, and
generation_date/generation_time is the generation date and time of the NCP
which contains the failing resource.
System Action: No data is displayed.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KOGCM001–KONCT303

509

KONAF148

KONAF149

module_name GET CRB FAILED, RC=return_code, SC=sense_code
Explanation: Module(module_name) was unable to obtain a Collector Request
Block (CRB). return_code is the return code and sense_code is the sense code
from the KONAXCRB macro.
System Action: No data is displayed for some fields.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF150

KONAF151

510

Candle Products Messages Manual (KLVHS–KONCT)

KONAF153

ACT NPB CHECK FOR RESOURCE(ncp_resource_name)
NPALU(npalu_name) FAILED RC(return_code)
Explanation: The Automatic Collection Task (ACT) was unable to analyze the
named NCP resource for an exception condition. This can occur during ACT
cleanup processing because the session monitoring the named NPALU was lost.
System Action: No exception conditions can be reported for the named
resource.
User Response: If ACT cleanup has been requested (as expressed by message
KONAF142), no response is required. Otherwise, contact Candle Support
Services.
Message Type: Warning.

KONAF154

KONFCCMD INSTALL NDMT was not performed at OMEGAMON
II for VTAM initialization. Install NDMT and restart OMEGAMON II
for VTAM.

ABEND

An abend occurred. Log the information displayed for problem
diagnosis and contact Candle Support Services.

Message Type:

User or internal error.

KONAF155

KONAF156

KONAFNUT ABEND CODE(abend_code) ROUTINE(routine_name)
Explanation: An abend occurred in a KONAFNUT process routine.
System Action: NCP performance statistics are not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KOGCM001–KONCT303

511

KONAF157

TOPOLOGY UPATE FUNCTIONS MODULE KONAFNUT LOAD FAILED.
NCP STATISTICS DATA NOT AVAILABLE.
Explanation: The Automatic Collector Task (ACT) load of the NCP topology
update functions module failed.
System Action: NCP performance statistics are not available.
User Response: Log the information displayed for problem diagnosis and
contact Candle Support Services.
Message Type: Internal error.

KONAF158

KONAXNSB START FUNCTION FAILED FOR RESOURCE resource_name
RC(return_code) MODULE(module_name) EXECUTION CONTINUES
Explanation: An error occurred while processing a START function for a
defined NCP resource. The resource may not be correctly monitored. The
resource name, return code, and issuing module name are displayed in the
message.
System Action: Processing continues.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF159

KONAXNSB STOP FUNCTION FAILED FOR RESOURCE resource_name
RC(return_code) MODULE(module_name) EXECUTION CONTINUES
Explanation: An error occurred while processing a STOP function for a defined
NCP resource. The resource may not be correctly monitored. The resource name,
return code, and issuing module name are displayed in the message.
System Action: Processing continues.
User Response: Log the diagnostic information and contact Candle Support
Services.
Message Type: Internal error.

KONAF160

KONAF161

512

Candle Products Messages Manual (KLVHS–KONCT)

KONCT000

TCP/IP STATISTICS COLLECTOR INITIALIZATION COMPLETE
Explanation: The TCP/IP collector successfully initialized.
System Action: None.
User Response: None
Message Type: Confirmation.

KONCT001

KONCT002

TCP/IP STATISTICS COLLECTOR ABENDED, CODE=abend_code,
PSW=program_status_word, ROUTINE=program_name
Explanation: The TCP/IP collector task abended. The abend code, program
status word (PSW), and program name are displayed in the message.
System Action: The TCP/IP collector task terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services. See message KONCT003 which follows.
Message Type: Internal error.

KONCT003

Rregister_number - Rregister_number register_value
Explanation: This is diagnostic information following message KONCT002.
System Action: None.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KONCT004

TCP/IP STATISTICS COLLECTOR IS TERMINATING
Explanation: The TCP/IP collector is terminating.
System Action: None.
User Response: None
Message Type: Information.

KONCT007

TCP/IP STATISTICS COLLECTOR COMPLETED TERMINATION
Explanation: The TCP/IP collector successfully completed termination.
System Action: None.
User Response: None
Message Type: Confirmation.

KONCT008

KOGCM001–KONCT303

513

KONCT009

KONCT010

KONCT011

KONCT012

KONCT013

KONCT014

514

Candle Products Messages Manual (KLVHS–KONCT)

KONCT015

KONCT050

KONCT051

KONCT052

KONCT053

KONCT100

KOGCM001–KONCT303

515

KONCT102

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS} ABENDED,
CODE=abend_code, PSW=program_status_word,
ROUTINE=program_name
Explanation: The specified function abended. The abend code, Program Status
Word (PSW), and program name are displayed in the message.
System Action: The function terminates.
User Response: Log the information for problem diagnosis and contact Candle
Support Services. See message KONCT103 which follows.
Message Type: Internal error.

KONCT103

Rregister_number - Rregister_number register_value
Explanation: This is diagnostic information following message KONCT102.
System Action: None.
User Response: Log the information for problem diagnosis and contact Candle
Support Services.
Message Type: Internal error.

KONCT104

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS} IS TERMINATING
Explanation: The function is terminating.
System Action: None.
User Response: None.
Message Type: Information.

KONCT107

{TCP/IP SERVICE THREAD | MIB BROWSER | XMCS} COMPLETED
TERMINATION
Explanation: The function successfully completed termination.
System Action: None.
User Response: None.
Message Type: Confirmation.

KONCT110

KONCT111

516

Candle Products Messages Manual (KLVHS–KONCT)

KONCT112

KONCT113

KONCT121

KONCT122

KONCT123

KONCT124

TCP/IP IMAGES
Explanation: This is a message header. It is the first message of a multiple
message group. Multiple KONCT125 messages may follow KONCT124.
System Action: None.
User Response: None
Message Type: Informational.

KOGCM001–KONCT303

517

KONCT125

NAME=name STATUS=status HOST=host IPADDR=xxx.xxx.xxx.xxx
Explanation: One KONCT125 message per TCP/IP image follows message
KONCT124, where:
NAME

TCP/IP procedure name.

STATUS

Active, Terminating, Down, Stopped, or Stopping.

HOST

TCP/IP host name.

IPADDR

Host primary IP address.

System Action: None.
User Response: None.
Message Type: Informational.
KONCT131

KONCT132

MIB BROWSER IS NOT ACTIVE RC=retcode MODULE(module)
Explanation: An attempt was made to use the MIB browser function of the
TCP/IP console, but the browser is not active.
System Action: The MIB browser function does not complete.
User Response: Examine the TLVLOG for messages KONCT131, KONCT050,
KONCT051, KONCT052, KONCT053, or KONCT009. If the messages indicate a
problem with SNMP, this may be a problem with the SNMP agent. Check the
status of the SNMP agent and examine the SNMP log for possible problems. A
restart of the SNMP agent and OMEGAMON may be necessary. If this fails to
resolve the problem, log the information for problem diagnosis and contact
Candle Customer Support.
Message Type: User or internal error.

KONCT201

KONCT201 module - UNABLE TO LOAD MODULE module
Explanation: TCP/IP component start-up was unable to load the specified
module.
System Action: The OMEGAMON II for VTAM TCP/IP component is
terminated.
User Response: Ensure that all installation and maintenance jobs ran correctly.
Then contact Candle Support Services.
Message Type: Probable installation error.

518

Candle Products Messages Manual (KLVHS–KONCT)

KONCT202

KONCT202 module - STORAGE ALLOCATION FAILURE SIZE = bytes
Explanation: The specified module was unable to allocate the specified number
of bytes of virtual storage.
System Action: The function requiring the process is not successful.
User Response: Ensure that the configuration values have not been modified.
Then contact Candle Support Services.
Message Type: User or internal error.

KONCT203

KONCT203 module - EXCEPTION GROUP group NOT DEFINED
Explanation: The specified module was unable to find a definition for the
specified exception group.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KONCT204

KONCT204 module - EXCEPTION excp NOT DEFINED
Explanation: The specified module was unable to find a definition for the
specified exception.
System Action: The request is terminated.
User Response: Contact Candle Support Services
Message Type: Internal error.

KONCT205

KONCT205 KONAITXB - REQUIRED PARAMETER NOT SUPPLIED FOR
EXCEPTION: group excp
Explanation: Module KONAITXB was passed an exception threshold for the
specified exception and group. The threshold was missing a required parameter.
Message Type: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KONCT206

KONCT206 KONAITXB - INVALID HOST NAME dnsname
Explanation: Module KONAITXB was passed the specified DNS name as part
of a high-priority connection definition. The name could not be resolved to an IP
address.
System Action: The request is terminated.
User Response: Ensure that the DNS name is valid. Then contact Candle
Support Services.
Message Type: User or internal error.

KONCT207

KONCT207 KONAITXB - EZASMI INITIALIZATION FAILURE, RC = rc
Explanation: Module KONAITXB was unable to initialize the EZASMI interface.
System Action: The process was terminated.
User Response: Check the return codes for the EZASMI INITAPI call and
contact Candle Support Services.
Message Type: Internal error.

KOGCM001–KONCT303

519

KONCT208

KONCT208 kONAITXB - EZASMI GETHOSTNAME FAILURE
Explanation: Module KONAITXB could not perform a GETHOSTBYNAME
function via the EZASMI interface.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KONCT209

KONCT209 KONAITXB - INVALID RETURN CODE FROM KONAPTXE
Explanation: Module KONAITXB received an invalid return code from module
KONAPTXE.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KONCT210

KONCT210 KONAITDE - INVALID ELEMENT INPUT: type
Explanation: Module KONAITDE received a request for data with the specified
type which is invalid.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KONCT211

KONCT211 KONAITXI -- UNABLE TO INITIALIZE EZASMI, RETURN CODE
= rc, REASON CODE = reason
Explanation: Module KONAITXI was unable to initialize the EZASMI interface
The return code and reason code are displayed in the message.
System Action: The TCP/IP component is terminated.
User Response: Check for installation errors based on the return code. Then
contact Candle Support Services.
Message Type: User or internal error.

KONCT301

KONCT301 KONAITDI - UNABLE TO LOAD MODULE module
Explanation: TCP/IP component start-up was unable to load the specified
module.
System Action: The OMEGAMON II for VTAM TCP/IP component is
terminated.
User Response: Ensure that all installation and maintenance jobs ran correctly.
Then contact Candle Support Services.
Message Type: Probable installation error.

KONCT302

KONCT302 KONAITDE - REQUIRED SUB-ELEMENT PARAMETER
MISSING
Explanation: Module KONAITDE received a request with a required
sub-element missing.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

520

Candle Products Messages Manual (KLVHS–KONCT)

KONCT303

KONCT303 KONAITDD - INVALID ELEMENT PARAMETER parm
Explanation: Module KONAITDD received a request with the specified element
parameter which is invalid.
System Action: The request is terminated.
User Response: Contact Candle Support Services.
Message Type: Internal error.

KOGCM001–KONCT303

521

522

Candle Products Messages Manual (KLVHS–KONCT)

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : Yes
Producer                        : Acrobat Distiller 4.05 for Windows
Create Date                     : 2004:02:02 10:03:59
Creator                         : FrameMaker 6.0
Keywords                        : February, 2004
Subject                         : GC32-9172-00
Author                          : IBM
Title                           : Candle Products Messages Manual, Vol 3
Modify Date                     : 2004:08:10 18:37:43-05:00
Page Count                      : 522
Page Mode                       : UseOutlines

EXIF Metadata provided by EXIF.tools

Candle Klvhskonct Gc32 9172 00 Users Manual Products Messages Manual, Vol 3

gc32917200 744d9db0-357b-4567-8988-501efc84eece Candle Indoor Furnishings GC32-9172-00 User Guide |

Navigation menu

Versions of this User Manual:

Views

Navigation