KLU messages
The messages that begin with the KLU prefix are associated with the Tivoli Enterprise Monitoring Server on z/OS® or Tivoli® Management Services:Engine (TMS:Engine).
KLUAP002 APDSM/ALLOCEAB $PSM-ALLOCX ERROR
Explanation
An internal error was detected by TMS:Engine.
System action
TMS:Engine forces an abend with the completion code U0100. The abend is associated with a single TMS:Engine user, whose terminal will hang. System operation for other users will continue normally. A VCANCEL command may be necessary to reinstate the hung user. TMS:Engine automatically writes a formatted dump to the RKLVSNAP data set.
User response
Contact IBM® Software Support.
Severity
ABEND
KLUAP003 APDSM DATA STREAM REPROCESSED FOR session_id USERID=userid
Explanation
This error occurred during processing of the application data stream for the specified session_id and userid.
System action
None.
User response
None.
Severity
INFO
KLUDF001 FIELD DATA: ddddddddddddddddddd
Explanation
A VSSDEBUG statement was encountered in a dialog. This message displays the data from a 3270 field.
System action
Processing continues.
User response
None
Severity
INFO
KLUDF002 FIELD ATTRIBUTE: xx
Explanation
A VSSDEBUG statement was encountered in a dialog. This message displays the attribute byte from a 3270 field.
System action
Processing continues.
User response
None
Severity
INFO
KLUDF011 INVALID TRIGGER DEFINITION BLOCK
Explanation
The VSSTRIG function contained an invalid trigger definition block. This is a serious error.
System action
The address space terminates.
User response
Contact IBM Software Support.
Severity
ABEND
KLUDF020 rrrrrrrr, VSSINFO 'xxxxxxxxxxxxxxxxx’
Explanation
A VSSINFO statement was encountered in a dialog but it contains a syntax error indicated by rrrrrrrr. The operands on the VSSINFO statement are xxxxxxxxxxxxxxxxx.
System action
The current dialog is terminated.
User response
Edit the dialog and correct the VSSINFO statement.
Severity
ABEND
KLUDF021 option IS NOT A VSSINFO OPTION
Explanation
The specified option is not valid for the VSSINFO function. FOREGID is currently the only valid option.
System action
The current dialog fails.
User response
Specify a valid option and retry.
Severity
REPLY
KLUDF022 VSSENTRY NOT ISSUED PRIOR TO VSSINFO
Explanation
A dialog invoked the VSSINFO function before VSSENTRY. VSSENTRY must be invoked prior to any other VSS function.
System action
The current dialog fails.
User response
Correct the dialog and retry.
Severity
REPLY
KLUDF023 FUNCTION VSSDEF INVOKED FROM DIALOG dialog IS NO LONGER SUPPORTED
Explanation
A dialog invoked the VSSDEF function, which is no longer supported.
System action
dialog completes with unpredictable results, generating RC=0.
User response
Use VSSALOC instead of VSSDEF and retry.
Severity
LOG
KLUFG001 FOREGROUND SET FAILED FOR userid
Explanation
Dialog command VSSFOREG failed.
System action
Return code 20 is set for the command.
User response
Retry the command.
Severity
REPLY
KLUFT000 VSSFTMGR: DIALOG LOOP DETECTED FOR USER userid
Explanation
An error in the controlling dialog causes the dialog to return immediately without moving a session to the foreground.
System action
The user window disappears.
User response
Review the message and correct the controlling dialog. If unable to locate the error, call IBM Software Support.
Severity
LOG, VIEW
KLUFT001 RESOURCE ERROR
Explanation
An unexpected error has occurred in connection with processing a trigger dialog.
System action
The process is abnormally terminated.
User response
Contact IBM Software Support.
Severity
ERROR
KLUFT002 LOOP AVERTED
Explanation
An internal error was detected by TMS:Engine.
System action
TMS:Engine forces an abend with completion code U0100. The abend is associated with a single TMS:Engine user, whose terminal will hang. System operation for other users will continue normally. TMS:Engine will automatically create a dump.
User response
A VCANCEL command may be necessary to reinstate the hung user. Contact IBM Software Support for help in resolving the error condition or in gathering the problem documentation that IBM Software Support requires to research the error condition.
Severity
ABEND
KLUFU001 #VSSFUCB ERROR: SESSION STILL ACTIVE
Explanation
An attempt was made to free a user control block while a session was still active.
System action
TMS:Engine takes a diagnostic abend with completion code U0100. The abend is associated with a single TMS:Engine user, whose terminal may hang. A VCANCEL command may be necessary to reinstate the hung user.
User response
Contact IBM Software Support.
Severity
ABEND
KLUFU101 WINDOW INTEGRITY ERROR
Explanation
An internal error was detected.
System action
The user's sessions are terminated.
User response
Contact IBM Software Support.
Severity
ABEND
KLUIB001 BUFFER SYNCHRONIZATION ERROR
Explanation
While processing an inbound request, a synchronization error was detected for a virtual terminal buffer. This is a serious error.
System action
The address space terminates.
User response
Contact IBM Software Support.
Severity
LOG
KLUIN001 VIRTUAL SESSION SUPPORT INITIALIZATION COMPLETE
Explanation
The successful initialization of virtual session support is logged to create an audit trail.
System action
None.
User response
None.
Severity
INFO
KLUIN002 UNABLE TO LOAD VIRTUAL SESSION SUPPORT COMPONENT module
Explanation
Virtual session support is unable to load the required component module. This error is usually caused by the absence of module from the TMS:Engine load library.
System action
Initialization terminates.
User response
Look for additional information in messages in the KLVCMnnn format. Correct the error and restart virtual session support.
Severity
ALERT
KLUIN003 KLUINVSS RKANPAR PARAMETERS:
Explanation
Module KLUINVSS logs its startup parameters as they are read from RKANPAR. This is the header message and will be followed by message KLUIN004.
System action
None.
User response
None.
Severity
LOG
KLUIN004 parameters
Explanation
As the parameters in module KLUINVSS are read, a log audit trail is created.
System action
None.
User response
None.
Severity
LOG
KLUOP001 VSHOW ARGUMENT LIST: argument list
Explanation
Displays the arguments that were specified for this VSHOW command.
System action
None.
User response
None.
Severity
REPLY
KLUOP002 session (appl,luname,cid,pool,logmode) {TAKEDOWN | SETUP | ACTIVE[-F]} COMPRESSION {nnn% | OFF}
Explanation
This reply from the VSHOW command appears if ACTIVE is specified. It follows KLUOP009 and displays information about a virtual session for the user. session is the virtual session ID; applid is the application name; luname is the logical unit name; cid is the VTAM® network resource ID; pool is the virtual terminal pool name; and logmode is the VTAM logmode.
TAKEDOWN means the session is currently being terminated; SETUP means the session is currently initializing; ACTIVE means the session is active. (-F) is displayed if the session is in the foreground at the user's terminal.
If compression is active, nnn displays the percentage of data stream compression; if not active, OFF is shown. The percentage is calculated by:
Compression-Percent =
PLU-to-SLU-bytes - Term-Update-Bytes
--------------------------------------
PLU-to-SLU-bytes
System action
None.
User response
None.
Severity
REPLY
KLUOP003 PLU ---> SLU: MSGS(messages) BYTES(bytes)
Explanation
This reply from the VSHOW command appears if STATS is specified. It lists the accumulated number of messages and bytes sent from the primary logical device to the secondary logical device.
System action
None.
User response
None.
Severity
REPLY
KLUOP004 SLU ---> PLU: MSGS(messages) BYTES(bytes)
Explanation
This reply from the VSHOW command follows KLUOP003 and lists the accumulated number of messages and bytes sent from the secondary logical unit to the primary logical unit.
System action
None.
User response
None.
Severity
REPLY
KLUOP005 TERM REFRESH: MSGS(messages) BYTES(bytes)
Explanation
This reply from the VSHOW command follows KLUOP004 and lists the accumulated number of messages and bytes sent to refresh the display on the terminal. A refresh occurs when the user switches between virtual sessions or an asynchronous pop-up is displayed.
System action
None.
User response
None.
Severity
REPLY
KLUOP006 TERM UPDATE: MSGS(messages) BYTES(bytes)
Explanation
This reply from the VSHOW command follows KLUOP005 and lists the accumulated amount of real traffic to the physical terminal in messages and bytes.
System action
None.
User response
None.
Severity
REPLY
KLUOP007 SESSION session INACTIVE
Explanation
This reply from the VSHOW command appears if INACTIVE is specified. The specified session is currently inactive.
System action
None.
User response
None.
Severity
REPLY
KLUOP008 selected OF total USER(S), selected OF total SESSION(S) SELECTED
Explanation
This summary message lists the number of users and sessions selected by the VSHOW command options out of the total pool.
System action
None.
User response
None.
Severity
REPLY
KLUOP009 userid {DISCONNECTED | userid (applid,luname,cid) ACTIVE [CONNECTED]}
Explanation
This reply from the VSHOW command displays information about a single user. userid is the user's ID. CONNECTED and DISCONNECTED indicate whether the user is attached to a terminal. ACTIVE means the user is currently active. applid is the application the user has logged onto; luname is the logical unit name; cid is the VTAM network resource ID.
System action
None.
User response
None.
Severity
REPLY
KLUOP010 TERM INPUT: MSGS(messages) BYTES(bytes)
Explanation
This reply from the VSHOW command follows KLUOP006 and lists the accumulated number of input messages and bytes received from the physical terminal while it was logically connected to the virtual session.
System action
None.
User response
None.
Severity
REPLY
KLUOP011 VCANCEL ARGUMENT LIST: argument list
Explanation
Displays the arguments that were specified for this VCANCEL command.
System action
None.
User response
None.
Severity
REPLY
KLUOP012 VCANCEL - EITHER USER OR ID REQUIRED
Explanation
Either a user ID or a terminal ID must be entered with the VCANCEL command.
System action
The VCANCEL request is ignored.
User response
Reissue the command with a user ID or terminal ID.
Severity
REPLY, ERROR
KLUOP013 VFORCE - REQUIRES USER=USERID
Explanation
You must specify a user ID to be forced.
System action
The VFORCE command is ignored.
User response
Reissue VFORCE with the USER= keyword.
Severity
REPLY
KLUOP014 VFORCE FOR USER userid INVALID. FOR CONFERENCE USE CCANCEL
Explanation
The user you were trying to force is using CL/CONFERENCE. The VFORCE command will not work until you have used the CL/CONFERENCE command CCANCEL.
System action
The VFORCE command is ignored.
User response
Issue CCANCEL to cancel sessions for the CL/CONFERENCE user, then reissue VFORCE.
Severity
REPLY
KLUOP015 USER userid FORCED
Explanation
The VFORCE command was successful.
System action
None.
User response
None.
Severity
REPLY
KLUOP016 USER userid NOT FORCED: reason
Explanation
The VFORCE command failed for one of
the following
reasons (which is specified when the message appears):
- NOT FOUND: The user ID was not found.
- VCANCEL TERM NOT ISSUED: You must issue VCANCEL with the TERM operand before VFORCE.
- VIRTUAL SESSION(S) FOUND : VFORCE found one or more virtual sessions and terminated them. Reissue VFORCE.
System action
As noted above.
User response
As noted above.
Severity
REPLY
KLUOP017 VCANCEL FOR USER - userid MAY FAIL. VIRTUAL SESSIONS HUNG.
Explanation
This user's virtual sessions are hung.
System action
The system may not respond to the command.
User response
If the system does not respond, wait a few minutes then retry VCANCEL. If VCANCEL does not work, try VFORCE.
Severity
REPLY
KLUOP018 cancelled OF total USER(S), cancelled OF total SESSION(S) CANCELLED
Explanation
This message lists the number of users and sessions cancelled by the VCANCEL command out of the total pool.
System action
None.
User response
None.
Severity
REPLY
KLUOP019 VFORCE ARGUMENT LIST: argument list
Explanation
Displays the arguments that were specified for this VFORCE command.
System action
None.
User response
None.
Severity
REPLY
KLUOP020 VSSTRACE(ON | OFF) TRACING(NONE | [applid],luname)
Explanation
This reply from the VSHOW command follows KLUOP009 and shows the trace status for the user. It is issued only when ACTIVE was specified. VSSTRACE shows the virtual session trace status, ON or OFF. TRACING shows the GTRACE options: NONE means GTRACE is not active for the user; applid is the application id, if ACB tracing is active, and luname is the logical unit name if terminal tracing is active.
System action
None.
User response
None.
Severity
REPLY
KLUOP021 WINDOW(winid) TRACING(NONE | (applid],luname)
Explanation
This reply from the VSHOW command follows KLUOP002. It shows the window ID winid for the virtual session or a minus sign (-) if the session is not in a window. TRACING shows the GTRACE options for this virtual session: NONE means GTRACE is not active; applid is the application ID, if ACB tracing is active, and luname is the logical unit name if terminal tracing is active.
System action
None.
User response
None.
Severity
REPLY
KLUOP022 VIRTUAL SESSION SERVICES NOT INITIALIZED, VSHOW IGNORED
Explanation
The VSHOW command was issued before Virtual Session Services have fully initialized.
System action
The VSHOW request is ignored.
User response
Wait until message KLUIN001 is written to RKLVLOG, showing Virtual Session Services initialization is complete, then retry the command.
Severity
WARN
KLUOP023 STATS INVALID WITH SUMMARY, STATS IGNORED.
Explanation
The VSHOW command was entered with the SUMMARY and STATS keywords. These are mutually exclusive.
System action
The STATS keyword is ignored.
User response
If you wish statistics, reissue the VSHOW command without the SUMMARY keyword.
Severity
REPLY
KLUOP030 VIRTUAL SESSION SERVICES NOT INITIALIZED, VCANCEL IGNORED.
Explanation
The VCANCEL command was issued before Virtual Session Services have fully initialized.
System action
The VCANCEL request is ignored.
User response
Wait until message KLUIN001 is written to RKLVLOG, showing Virtual Session Services initialization is complete, then retry the command.
Severity
WARN
KLUOP200 TRACE CLASS(USER) STATUS: USER(userid): {ENABLED | PENDING | DISABLED} *** END OF TRACE STATUS ***
Explanation
These lines are the output for the VSSTRACE command when neither ON nor OFF was specified. They show the current status for each user for which tracing was requested. ENABLED means tracing is active; PENDING means the user is not logged on but a trace request will be issued when he does log on; DISABLED means tracing is currently inactive.
System action
None.
User response
None.
Severity
REPLY
KLUOP201 TRACE REQUEST REJECTED. REQUIRED ARGUMENT NOT SPECIFIED
Explanation
A VSSTRACE command was specified without the required user ID.
System action
The VSSTRACE command is ignored.
User response
Reissue the VSSTRACE command with a user ID.
Severity
ERROR
KLUOP202 TRACE USER (userid) {ENABLED | QUEUED | DISABLED}
Explanation
The trace request for userid has been performed. ENABLED means tracing is active. QUEUED means tracing will start when userid logs on. DISABLED means tracing is not active.
System action
None.
User response
None.
Severity
REPLY
KLUOP203 GTF INTERFACE HAS NOT BEEN ENABLED
Explanation
A VSSTRACE request has been issued for a resource but the GTF interface has not been enabled.
System action
The command continues, but GTF output will not be produced.
User response
Issue the GTF ON command to enable GTF tracing.
Severity
ALERT
KLUPM001 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED LU luname USERID userid. ALL VIRTUAL SESSIONS CANCELLED.
Explanation
A runaway application generated too many messages.
System action
Cancels sessions for this luname/user ID.
User response
None. This is an application problem.
Severity
ALERT
KLUVT000 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED LU(luname) USERID:(userid). PHYSICAL SESSION CANCELLED.
Explanation
An excessive number of outbound messages have been logged, causing the physical session to terminate.
System action
Physical session is cancelled.
User response
Make sure that there are no runaway applications. If there are no runaway applications, check the outbound message limit; it may be set too low.
Severity
LOG
KLUVT001 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED LU(luname) USERID(userid). ALL VIRTUAL SESSIONS CANCELLED.
Explanation
An excessive number of outbound messages have been logged. All virtual sessions are cancelled.
System action
None.
User response
Make sure that there are no runaway applications. If there are no runaway applications, check the outbound message limit; it may be set too low.
KLUVT002 PENDING OUTBOUND MESSAGE LIMIT EXCEEDED. LU(luname) USERID(uuuuuuuu) PHYSICAL SESSION CANCELLED
Explanation
The outbound physical message limit has been exceeded on the virtual session.
System action
The session is terminated.
User response
This message may indicate that a dialog contains an error that causes large volumes of data to be produced.
KLUXD001 QUERY REPLY DATA IS NOT VALID FOR USERID user
Explanation
A 3270 datastream READ PARTITION QUERY command is sent to the user's physical terminal device (if the logmode used by the physical terminal can be queried). When the device returns the requested replies, some basic validity checks are performed on the query reply data. This message is issued if any of these checks fail.
System action
Initialization is completed for the user, but the invalid query reply data is ignored. Any READ PARTITION QUERYs issued by applications on the virtual sessions are responded to with a single NULL query reply.
User response
At the time message KLUXD001 is sent to the RKLVLOG data set, a snap of the query reply data that filed the validity checks is taken. The snap data is in the RKLVSNAP data set and is identified as REQUESTED FROM KLUXQANA. Use timestamps in the RKLVLOG and RKLVSNAP data to correlate messages and snaps if multiple instances exist. Save these data sets and contact IBM Software Support for further assistance.
Severity
LOG