KLVPA001 SYNAD ERROR: synadmsg

Explanation

A physical error occurred while reading a partitioned data set. The operating system provides synadmsg, which is documented in IBM z/OS DFSMS 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 (extended partitioned data set), 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 TMS: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 data set. xxxx contains sense bytes 1 and 2, and yyyy contains status bytes 1 and 2 as documented in DFSMS/MVS Using Datasets (SC26-4922) . 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

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 TMS: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 partitioned data set 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 IBM® Tivoli® product, contact IBM Software Support.

Message Type

VIEW

KLVPA006 NO VALID REQUEST CODED FOR FUNCTION(PDS)

Explanation

A null string was passed as the request code to the partitioned data set 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 IBM Tivoli product, contact IBM Software Support.

Message Type

VIEW

KLVPA007 synadmsg

Explanation

A physical error occurred while reading a PDS/E (extended 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 IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.

Message Type

ERROR

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 IBM Software Support.

Message Type

VIEW

KLVPM002 eeeeeeeeeeeeee FUNCTION(PSMATTR): ccccccccccccccc

Explanation

The syntax error eeeeeeeeeeeeee has been encountered while parsing the PSM ATTR command ccccccccccccccc.

System action

The command is ignored and processing continues.

User response

Correct the problem and re-enter the command.

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 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 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

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 TMS: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 TMS: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 following reason code analysis table for more information.
  • lu_name: Physical terminal LU name.
  • modname: Module identifier.
  • attention_code: Pending AID.
  • fdbk: Feedback information internal to TMS:Engine.
  • error_data: Two bytes of error data. See the following reason code analysis table 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:
Table 1. Description of reason codes for KLVPM021
Reason Code Description System Action User Response
0601 Internal Exception Condition 1 1
0602 Internal Exception Condition 1 1
0603 Internal Exception Condition 1 1
0604 Internal Exception Condition 1 1
0605 Internal Exception Condition 1 1
0606 Internal Exception Condition 2 1
0607 Internal Exception Condition 2 1
0608 Internal Exception Condition 2 1
0609 Internal Exception Condition 1 1
060A Internal Exception Condition 1 1
060B Internal Exception Condition 1 1
060C Internal Exception Condition 1 1
060D Internal Exception Condition 1 1
060E Internal Exception Condition 1 1
0901 Internal Exception Condition 1 1
0902 Internal Exception Condition 1 1
0903 Internal Exception Condition 1 1
0904 Internal Exception Condition 1 1
0905 Unsupported AID received (error_data = unsupported aid) 1 2
0906 Invalid CLEAR/CLEAR partition 1 2
0907 Internal Exception Condition 1 1
0908 Internal Exception Condition 1 1
0909 Internal Exception Condition 1 1
090A Invalid buffer address (error_data = buffer address) 1 2
090B Invalid codepoint detected (error_data = codepoint) 1 2
090C Invalid value in Set Attribute (error_data = Set Attribute type/value pair) 1 2
090D Unexpected end of output (error_data = last 1 or 2 bytes) 1 2
090E Internal Exception Condition 2 1
090F Internal Exception Condition 2 1
0910 Internal Exception Condition 2 1
0911 Internal Exception Condition 2 1
0912 Internal Exception Condition 2 1
0913 Unexpected formatted input (error_data = buffer address) 2 2
0914 Input data from unknown field (error_data = buffer address) 2 2
0915 Attention key received during pre-popup read. 2 2
0916 Read modified already satisfied. 2 2

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 IBM Software 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

INFO

KLVPM051 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

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 TMS:Engine Presentation Space Manager will not allow certain 3270 extended data stream orders (for example color, highlighting) to be used with the named lu.

User response

Contact IBM Software Support.

Message Type

LOG

KLVPR000 eeeeeeeeeeeeee, FUNCTION(PRODUCT): ccccccccccccccc

Explanation

The syntax error eeeeeeeeeeeeee has been encountered while parsing the PSM command ccccccccccccccc.

System action

The current dialog fails.

User response

Correct the dialog.

Message Type

VIEW

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

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

KLVRE007 PARAMETER pppppppp INVALID

Explanation

The trace status specified on a REFRESH command is not TRACE or NOTRACE.

System action

The command is ignored and processing continues.

User response

Re-enter the command and specify either TRACE or NOTRACE.

Message Type

ERROR

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

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: A z/OS® 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 data set is a partitioned data set.
  • 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

KLVRM004 LOGICAL RESOURCE EXIT STACK INTEGRITY ERROR

Explanation

The TMS: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 or the system dump data sets or both. The resource involved is left in an indeterminate state.

User response

Recycle the TMS:Engine address space as soon as possible. Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software 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 IBM Software 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 IBM Software Support. Keep dump, RKLVLOG, SYSLOG, and runsheets.

Message Type

ABEND

KLVRT001 PARAMETER ERROR

Explanation

TMS:Engine detected an invalid RTM event code.

System action

A call to RTM fails. TMS:Engine creates a DUMP and continues processing.

User response

Contact IBM Software 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 IBM Software Support.

Message Type

INFO

KLVRT011 NPM MODULE FNMNSI REQUIRES APF AUTHORIZATION

Explanation

RTM support for NPM has been selected, but the TMS: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

TMS: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 TMS: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 TMS:Engine, and issue the RTM ON command.

Message Type

ALERT

KLVRT013 $STG ERROR

Explanation

TMS:Engine was unable to allocate storage for the NPM/NSI NMVT request units.

System action

A call to NSI fails, TMS:Engine creates a DUMP and continues processing.

User response

Contact IBM Software 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, TMS:Engine creates a DUMP and continues processing.

User response

Contact IBM Software Support with the contents of the DUMP.

Message Type

ABEND

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 Z NetView Messages and Codes, which you can find at IBM Z® NetView. Contact IBM Software 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 IBM Z NetView Messages and Codes, which you can find at IBM Z NetView. Contact IBM Software Support if you need further assistance.

Message Type

ALERT

KLVRT022 RTM NPM VECTOR ERROR

Explanation

TMS:Engine detected an invalid internal NPM function call.

System action

A call to NSI fails, TMS:Engine creates a DUMP and continues processing.

User response

Contact IBM Software 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 TMS:Engine with a return code of 20.

System action

The RTM interface in TMS:Engine is terminated if active. If the rejected request is CONNECT, TMS: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

KLVRT030 $STG ERROR

Explanation

TMS:Engine was unable to allocate storage for the ETE or NetSpy mapping message.

System action

TMS:Engine creates a DUMP and continues processing.

User response

Contact IBM Software Support with the contents of the DUMP.

Message Type

ABEND

KLVRT031 PARAMETER ERROR

Explanation

TMS:Engine was unable to process the mapping message for ETE or NetSpy interface because of an internal invalid parameter.

System action

TMS:Engine creates a DUMP and continues processing.

User response

Contact IBM Software Support with the contents of the DUMP.

Message Type

ABEND

KLVSC001 KEYWORD NOT FOUND: keyword environmental_information

Explanation

TMS: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

TMS: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

TMS: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

KLVSC004 OPERAND TOO LONG: environmental_information operand

Explanation

TMS: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

TMS: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

TMS: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

TMS: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>: 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.

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

TMS: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

KLVSC010 $GSA TABLE ID IS INVALID

Explanation

While processing a STORCHK command, the $GSA table failed a validity check.

System action

The command is ignored and processing continues.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVSC011 STORAGE OVERLAY - BAD SRT PTR. R9=BLK

Explanation

During STORCHK command processing, a bad SRT pointer was discovered.

System action

The system is abnormally terminated.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVSC012 STORAGE OVERLAY - BAD BLOCK ID. R9=BLK

Explanation

During STORCHK command processing, a bad storage block ID was discovered.

System action

The system is abnormally terminated.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVSC013 STORAGE OVERLAY - BAD FREE CHAIN PTR. R9=BLK

Explanation

During STORCHK command processing, a bad pointer was discovered in the free chain.

System action

The system is abnormally terminated.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVSC015 STORAGE OVERLAY - BAD TRAILER. R9=BLK

Explanation

During STORCHK processing, a storage block was discovered which did not have a correct trailing string.

System action

The system is abnormally terminated.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVSC017 STORAGE OVERLAY - FREE STORAGE NOT FF. R9=BLK

Explanation

During STORCHK command processing, a block of free storage was found to contain something other than X’FF’.

System action

The system is abnormally terminated.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVSC021 GMEM STORAGE CHECK CANNOT RUN WITH OVERLAY TOOL

Explanation

An attempt was made to run STORCHK concurrently with the overlay detection tool. The tools may not run concurrently.

System action

The STORCHK command is ignored.

User response

If you want to run STORCHK, stop the overlay detection tool.

Message Type

ERROR

KLVSC022 GMEM STORAGE CHECK IS STARTING...

Explanation

Processing of a STORCHK command is starting.

System action

Processing continues.

User response

None.

Message Type

INFO

KLVSC023 GMEM STORAGE CHECK IS COMPLETE. NO ERRORS WERE FOUND.

Explanation

Processing of a STORCHK command has completed.

System action

Processing continues.

User response

None.

Message Type

INFO

KLVSD001 PRIMARY MAIN STORAGE INFORMATION:

Explanation

The STORAGE command was issued and this message identifies the start of information about TMS: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 TMS: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 TMS: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 116 indicates that this pool contains all blocks that are from 116 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.

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 TMS: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.
  • sl: An internal parameter.
  • range: Specifies the number of storage areas.
  • tot: Specifies (in kilobytes) the total amount of storage available to end-user applications and TMS:Engine functions. Storage not included in this total is storage obtained during TMS: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 TMS: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

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.
  • tt: 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

TMS: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 TMS: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.
  • tt: 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

TMS:Engine will inhibit the initiation of new work (sessions, dialogs, etc.). Once the threshold has been reached, this inhibition remains until TMS:Engine is restarted.

User response

When THRESHOLD EXCEEDED is displayed, perform an orderly shutdown of TMS:Engine. Then contact your systems administrator, who should review the TMS:Engine storage use in order to determine what actions should take place.

Message Type

REPLY

KLVSD021 TMS(num) PREFIX(pfx) CUSHION(cshn)

Explanation

This message appears in response to the TMS:Engine STORAGE operator command and displays information about TMS:Engine temporary storage use.
  • num: Specifies (in bytes) the amount of temporary storage allocated. TMS: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 for Model2
    • 2560 for Model3
    • 3440 for Model4
    • 3564 for 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

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.
  • q: 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.

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 TMS: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

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. If the problem persists, contact IBM Software Support.

Message Type

ERROR

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 TMS: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. TMS:Engine issues snap dumps of the environment for problem determination. TMS:Engine processing continues.

User response

Contact IBM Software Support. Keep the dump and RKLVLOG.

Message Type

ERROR