KLVDI001 KLVWAIT INVOKED FROM UNSUPPORTED ENVIRONMENT

Explanation

TMS:Engine dispatcher was invoked from SRB mode.

System action

TMS:Engine abends U0200.

User response

Contact IBM® Software Support.

Message Type

Reply

KLVDL001 INVALID LOGON STRING, EXCESS IGNORED

Explanation

The user data passed to the KLVENTRY dialog contains more than five subfields.

System action

The excess fields are ignored.

User response

Correct the user data definition to contain no more than five fields, separated by nulls. Valid fields are user ID, password, group, account, and procedure.

Message Type

None

KLVDL002 key IS NOT ACTIVE

Explanation

A function key that is not assigned a function was pressed.

System action

The key is ignored.

User response

Refer to the bottom of the display panel for a list of active keys.

Message Type

None

KLVDL003 dlg: systerm Desc=descriptor, Charset=charset, CGCSGID=cgcsgid, APL support=support

Explanation

This message is generated when logging onto a CUA application. dlg is the dialog that determines whether the terminal will support APL characters when the screen is displayed. systerm is the terminal-id for the current session. The descriptor defines one terminal storage and symbol-set characteristics entry. The charset is the terminal storage identification: X'00' to '07'. The cgcsgid is the coded graphic character set global identifier value. The support value of 0 indicates that APL is not supported, while a value of 1 indicates that APL is supported.

System action

None.

User response

Refer to the values in the message to resolve problems with APL support for a given terminal.

Message Type

None

KLVDL101 appl / lang / ddname: INVALID APPLID

Explanation

An TMS:Engine-based application has invoked the help processor with an invalid parameter list. appl is the product code, which is incorrect. lang is the language code. ddname is the associated help file.

System action

The help processor stops.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL102 appl / lang / ddname: INVALID LANGUAGE

Explanation

An TMS:Engine-based application has invoked the help processor with an invalid parameter list. appl is the product code. lang is the language code, which is incorrect. ddname is the associated help file.

System action

The help processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL103 appl / lang / ddname: TBCREATE FAILED FOR table; RC=rc

Explanation

The TMS:Engine help processor cannot create the table table which will contain help information. rc is the return code from the TBCREATE SSPL dialog function. appl is the product code. lang is the language code. ddname is the associated help file.

System action

The help processor stops processing either the glossary or index.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL104 appl / lang / ddname: IPC CREATE FAILED FOR qname; RC=rc

Explanation

The TMS:Engine help processor cannot create the communications queue qname for its internal processing. rc is the return code from the IPC CREATE SSPL dialog function. appl is the product code. lang is the language code. ddname is the associated help file.

System action

The help processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL105 dlg: DD(ddname) - KLVRDIR FAILED; RC=rc

Explanation

The TMS:Engine help processor cannot read the directory of the help library allocated to ddname. dkg is the dialog that has detected the error; rc is the return code from the utility program that was reading the directory.

System action

The help processor terminates.

User response

Ensure that the TMS:Engine address space has the DD ddname allocated to it and that it points to a partitioned data set containing help text. If a security package such as RACF® is being used, the TMS:Engine address space must have read access to the help libraries.

Message Type

None

KLVDL106 dlg: DD(ddname) - [INDEX | GLOSSARY] MEMBER(mem) PROCESSING FAILED; RC=rc

Explanation

The TMS:Engine help processor could not process the help member mem to extract the index or glossary information. dlg is the dialog that has detected the error, ddname is the DD name of the associated help library, and rc is the return code from the utility program that was processing mem.

System action

The help processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

None

KLVDL107 appl / lang / ddname: IPC DEQUEUE INVALID HANDLE

Explanation

During shutdown processing, the TMS:Engine help processor could not release its communications queue. appl is the product code. lang is the language code. ddname is the associated help file.

System action

The help processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL108 appl / lang / ddname: IPC DEQUEUE CONTENTION

Explanation

During shutdown processing, the TMS:Engine help processor detected contention while accessing its communications queue. appl is the product code. lang is the language code. ddname is the associated help file.

System action

The help processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL109 appl / lang / ddname: NO [INDEX | GLOSSARY] ENTRIES GENERATED

Explanation

The TMS:Engine help processor did not find any index or glossary entries during initialization of a TMS:Engine-based application. appl is the product code. lang is the language code. ddname is the associated help file.

System action

The help index or glossary will not be available.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL110 dlg: [INDEX | GLOSSARY] TABLE(table) CANNOT BE OPENED; RC=rc

Explanation

While attempting to respond to a help request, the TMS:Engine help processor was unable to open the table table that contains help index or glossary information. dlg is the dialog that has detected the error; rc is the return code from the TBOPEN SSPL dialog function.

System action

The help processor terminates; help or the glossary is not available for the application.

User response

Review the TMS:Engine RKLVLOG for other KLVDLnnn messages that may have been issued, and respond as directed. Otherwise, save the RKLVLOG and contact IBM Software Support.

Message Type

None

KLVDL111 appl / lang / ddname/ member: MEMBER NOT FOUND

Explanation

While attempting to update a help index or glossary table, the TMS:Engine help processor was unable to locate the partitioned data set member in the ddname file. appl is the product code. lang is the language code.

System action

No further processing is performed for member; the help processor continues with any other pending requests.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL112 appl / lang / ddname/ member: NO PRIMARY INDEX FOR term

Explanation

While attempting to update a help index table, the TMS:Engine help processor detected an error in partitioned data set member, member, in the ddname file. term is the data associated with the error. appl is the product code. lang is the language code.

System action

term is ignored; the help processor continues with any other pending requests.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL113 dlg: TBCREATE FAILED FOR table; RC=rc

Explanation

The TMS:Engine date processor cannot create the table table which will contain date formatting information. dlg is the dialog that has detected the error; rc is the return code from the TBCREATE SSPL dialog function.

System action

The date processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

None

KLVDL114 dlg: IPC CREATE FAILED FOR qname; RC=rc

Explanation

The TMS:Engine date processor cannot create the communications queue qname for its internal processing. dlg is the dialog that has detected the error; rc is the return code from the IPC CREATE SSPL dialog function.

System action

The date processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

None

KLVDL115 dlg: IPC DEQUEUE INVALID HANDLE; RC=rc

Explanation

During shutdown processing, the TMS:Engine date processor could not release its communications queue. dlg is the dialog that has detected the error; rc is the return code from the IPC DEQUEUE SSPL dialog function.

System action

The date processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

None

KLVDL116 dlg: IPC DEQUEUE CONTENTION; RC=rc

Explanation

During shutdown processing, the TMS:Engine date processor detected contention while accessing its communications queue. dlg is the dialog that has detected the error; rc is the return code from the IPC DEQUEUE SSPL dialog function.

System action

The date processor terminates.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

None

KLVDL117 appl / lang / ddname: PDS SETWRT FAILED; RC=rc

Explanation

While attempting to read a partitioned data set directory, the TMS:Engine help processor received return code rc from the PDS SSPL dialog function. appl is the product code. lang is the language code. ddname is the associated help file.

System action

No help or glossary information is available.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL118 appl / lang / ddname / member: MISSING INCLUDE NAME

Explanation

While attempting to update a help index table, the TMS:Engine help processor detected an error in partitioned data set member, member, in the ddname file. appl is the product code. lang is the language code.

System action

term is ignored; the help processor continues with any other pending requests.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL119 appl / lang / ddname/ member: [INDEX | GLOSSARY] TBMOD FAILED RC=rc

Explanation

While attempting to update a help index or glossary table, the TMS:Engine help processor received an error (rc) on a TBMOD request. member is the partitioned data set member being processed, which resides in the ddname file. appl is the product code. lang is the language code.

System action

Further processing for the help index or glossary is terminated.

User response

Save the TMS:Engine RKLVLOG and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL120 appl / lang / ddname: GLOSSARY/INDEX SHUTDOWN COMPLETE

Explanation

The TMS:Engine help processor received a quit request and has terminated the help glossary and index tables normally. appl is the product code. lang is the language code. ddname is the associated help file.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDL121 appl / lang / ddname: GLOSSARY/INDEX STARTUP COMPLETE

Explanation

The TMS:Engine help processor has completed initialization of the help glossary and index tables. appl is the product code. lang is the language code. ddname is the associated help file.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDL201 TABLE action REQUEST FROM USER(userid ) TERM(termid) FOR table

Explanation

The KLVTBULD SSPL dialog has been invoked to load or unload table. action is LOAD or UNLOAD, userid is the user, and termid is the terminal that invoked KLVTBULD.

System action

The load or unload request continues. Message KLVDL202 may follow this message if table is being loaded with a different name.

User response

None.

Message Type

INFO

KLVDL202 NEW TABLE NAME IS newname

Explanation

The KLVTBULD SSPL dialog has been invoked to load a table with a name (newname) different than the original name.

System action

The load or unload request continues.

User response

None.

Message Type

INFO

KLVDL300 appl USEREXIT(dlg) RETURNED INVALID RESULT(rc)

Explanation

A programming error has been detected in dialog application appl.

System action

The dialog application is terminated.

User response

Save the contents of this message and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL301 appl apdlg tkdlg text

Explanation

Dialog application appl has requested that debugging information be written to RKLVLOG. Message KLVDL302 may follow this message.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDL302 USEREXIT(dlg) KEY(key) TEXT(text)

Explanation

This message follows KLVDL301 and contains debugging information.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDL303 appl USEREXIT(dlg) DID NOT RETURN A SYSKEY VALUE

Explanation

A programming error has been detected in dialog application appl.

System action

The dialog application is terminated.

User response

Save the contents of this message and contact IBM Software Support.

Message Type

LOG, VIEW

KLVDL400 TERMINAL OUTPUT WILL BE FORCED TO {UPPER CASE | MIXED CASE}

Explanation

The KLVCASE dialog has been invoked to force subsequent logons to SSPL-based products to be displayed in upper or mixed case.

System action

None.

User response

None.

Message Type

LOG, VIEW. This message is also written to the z/OS® SYSLOG.

KLVDM001 MINIMUM/MAXIMUM OPTIONS MUTUALLY EXCLUSIVE: RKANPENU dialog LINE line

Explanation

The MINIMUM and MAXIMUM options specified on a )BODY dialog statement are mutually exclusive. The associated dialog and line number are shown for reference.

System action

Panel interpretation fails.

User response

If the problem is with a user-defined dialog, correct the error and try to refresh the panel. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

WARNING

KLVDM002 STRING VARIABLE TOO LONG

Explanation

The TMS:Engine variables manager detected an attempt to use a string longer than approximately 30,000 bytes.

System action

The thread is terminated with a U0100 abend, sending a dump to the RKLVSNAP file or the system's dump data sets or both.

User response

Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.

Message Type

Abend

KLVDM003 VARIABLE NAME EXPECTED: library(dialog) LINE(line)

Explanation

The BODY section of dialog dialog contains an input field that does not contain a variable name, or a variable name prefix (typically an ampersand, &) that is not followed by a variable name. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

Contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM004 ATTRIBUTE CONFLICT FOR ATTR(attr) library(dialog) LINE(line)

Explanation

The specified attribute, attr, in the BODY section of dialog dialog, conflicts with either an attribute that was previously defined or the variable name prefix (usually an ampersand, &). library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If the problem is with a user-defined dialog, check your panel definition and correct the error. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM005 VARIABLE NAME TOO LONG 'varname': library(dialog) LINE(line)

Explanation

The BODY section of dialog dialog contains a variable name, varname, that is longer than 8 characters.

System action

The dialog compilation fails.

User response

If the problem is with a user-created dialog, shorten the variable name to 8 characters or less and issue the REFRESH command to determine if the panel definition is correct. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM005_d ILLEGAL VARIABLE NAME: MEMBER ($ddmbr) LINE ($ddline)

Explanation

An illegal variable name in line $ddline of member $ddmbr was encountered.

System action

The dialog is terminated.

User response

Contact IBM Software Support.

Message Type

ERROR

KLVDM006 OPEN MIX STRING: library(dialog) LINE(line)

Explanation

Line line of dialog dialog contains a DBCS shift-out character without a subsequent shift-in character. All DBCS mix strings must be complete on one line in the BODY section of a dialog. library is the DD name that contains the dialog.

System action

The panel compilation fails.

User response

If the problem is with a user-defined dialog, check your panel definition and correct the error. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM007 TABLE VARIABLE CONFLICT WITH VARIABLE 'var': library(dialog) LINE(line)

Explanation

The variable var appears as both a table variable and a dialog variable in the BODY section of dialog dialog. Only one type of declaration is allowed. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The panel compilation fails.

User response

If the problem is with a user-defined panel, check your panel definition and correct the error. If the problem is with an IBM-supplied panel, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM008 NEGATIVE LENGTH STRING DETECTED BY KLVDMVTR

Explanation

An internal error has been detected by the TMS:Engine variables manager.

System action

The request is terminated with a U0100 abend, sending a dump to the RKLVSNAP file or the system's dump data sets.

User response

Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.

Message Type

ABEND

KLVDM009 DIALOG VARIABLE BUFFER INTEGRITY LOST

Explanation

The TMS:Engine variables manager detected an error in its data structures.

System action

The request is terminated with a U0100 abend, sending a dump to the RKLVSNAP file and the system's dump data sets or both.

User response

Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.

Message Type

ABEND

KLVDM010 $DMFS FAIL CALLED BY dialog+X'offset'

Explanation

This message is for internal use and appears only when DEBUG(Y) is coded in RKLVIN. It can be ignored unless requested by IBM Software Support. Message KLVDM015 follows and contains additional information.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDM011 DIALOG dialog FAILED; RC(rc) REASON(reason)

Explanation

The specified dialog failed during execution.

System action

TMS:Engine ends the user's session unless ONERROR was specified in the dialog invoking the failing dialog. KLVDM015 follows this message and displays information about the dialog, terminal, and application associated with the failure.

User response

Contact IBM Software Support or check the return code (rc), correct the error in the failing dialog, refresh the dialog, and retry. Possible rc values, their meanings, and responses:
Return code Meaning
4 Dialog not available; either the dialog is not in TLVPNLS or it could not be compiled. Look for other KLVDMxxx messages to identify the problem and correct it.
8 Device dependent routine start-up failed. Save the MVS SYSLOG and TMS:Engine TLVLOG and job log. Then contact IBM Software Support.
12 SSPL function failed during )INIT processing. Look for other KLVDMxxx messages to identify the problem and correct it. Possibilities include using non-numerics in a numeric calculation and passing an invalid parameter to a dialog function.
16 SSPL function failed during )PROLOG processing. Same as RC(12).
20 Device not supported. This is typically caused by a non-terminal dialog attempting to use )BODY, which is not allowed. If this is the case, either do not run the dialog as a non-terminal or correct the dialog design. Otherwise, save the z/OS SYSLOG and TMS:Engine RKLVLOG and job log. Then contact IBM Software Support.
24 An I/O error occurred while trying to write the )BODY data to the terminal. Refer to the TMS:Engine TLVLOG file for additional messages which should identify the problem.
28 SPL function failed during )EPILOG processing. Same as RC(12).
32 SSPL function failed during )TERM processing. Same as RC(12).
36 A RESHOW command was issued in the )TERM section, which is not allowed. Correct the dialog and retry.
40 A SELECT command was issued in the )TERM section, which is not allowed. Correct the dialog and retry.
44 A TBDISPL failed, either because the dialog does not have a )BODY TABLE section, or because the physical terminal was not large enough to display at least one table row. Do not issue TBDISPL against this dialog, add a )BODY TABLE section, or ensure that the )BODY TOP and )BODY BOTTOM sections are not too large. Retry the dialog.

Message Type

LOG, VIEW, INFO

KLVDM012 LOOPCTR LIMIT EXCEEDED

Explanation

The LOOPCTR limit has been exceeded for a dialog. KLVDM015 follows this message and identifies the failing dialog.

System action

The dialog terminates.

User response

If the problem is with a user-defined dialog, correct the error, refresh the dialog, and test it. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM013 INVALID NUMERIC ARGUMENT

Explanation

A dialog has attempted a numeric operation on a value that was not numeric. KLVDM015 follows this message and identifies the failing dialog.

System action

The dialog terminates.

User response

Contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM014 MAIN STORAGE SHORTAGE

Explanation

A dialog could not be executed because the dialog manager discovered a storage shortage. KLVDM015 follows this message and identifies the failing dialog.

System action

The dialog and the user's session terminate.

User response

If the error persists, notify your system administrator, who should review storage usage in TMS:Engine, and increase the MINIMUM value in the RKLVIN file.

Message Type

LOG, VIEW

KLVDM015 DIALOG(dialog) [MEMBER(member) LINE(line)] Language(ccc) [LU(luname) APPL(applid)]

Explanation

A warning or error has occurred while executing a dialog. This message follows the actual warning or error message and identifies the dialog, dialog, where the condition was detected.

If the information can be determined, the location of the error is shown. member is either the dialog name or the name of a COPY member included in dialog. line is the line number in member where the error occurred. ccc is the language code currently in effect.

If the executing dialog is associated with a physical terminal, luname is the logical unit name and applid is the VTAM® application OD.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDM019 VARIABLE NAME TOO LONG: 'name'

Explanation

The TMS:Engine dialog manager detected the use of a variable name (name) that is longer than 8 characters, and OPTIONS LONGVARNAME(IGNORE) was not coded in the KLVINDM member of RKANPAR. KLVDM015 follows this message and identifies the dialog associated with the error.

System action

If LONGVARNAME(FAIL) was specified, the dialog fails. Otherwise, the variable name is truncated at 8 characters and processing continues.

User response

Correct the variable name and refresh the dialog.

Message Type

LOG, VIEW

KLVDM020 UNSUPPORTED/INVALID $DMFS REQUEST RECEIVED

Explanation

The TMS:Engine dialog manager was passed an invalid request.

System action

The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file or the system's dump data sets or both.

User response

Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM021 name IS ALREADY DEFINED: library(dialog) LINE(line)

Explanation

The SSPL variable name is defined more than once in the DECLARE section of dialog, dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If the problem is with a user-defined dialog, correct the error, refresh the dialog, and test it. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM022 STATIC VARIABLE "name" IS UNDECLARED; SCOPE(scope) ASSIGNED

Explanation

The dialog manager detected a reference to variable, name, which was not defined in the DECLARE section of the dialog. The NOTDECLARED(REPORT) option was requested, either in the KLVINDM member of RKANPAR or on the OPTION statement in the dialog. KLVDM015 follows this message and shows the dialog that contains the undeclared variable.

Note: It is acceptable for a dialog to have undeclared variables; this message is intended as a debugging tool.

System action

name is treated as if it were declared as scope scope, and the dialog continues executing. The DEFAULTSCOPE keyword on the OPTION statement may be used to change the default scope. This message is issued only once for each individual reference to the variable.

User response

Review the dialog shown in message KLVDM015 to determine the proper variable scope. Then add it to the DECLARE section.

Message Type

LOG, VIEW

KLVDM023 DYNAMIC VARIABLE "name" IS UNDECLARED; SCOPE(scope) ASSIGNED

Explanation

The dialog manager detected a reference to a dynamically constructed variable, name, which was not defined in the DECLARE section of the dialog. (Dynamically constructed variable names take the general form of &(&varname).) The NOTDECLARED(REPORT) option was requested, either in the KLVINDM member of RKANPAR or on the OPTION statement in the dialog. KLVDM015 follows this message and shows the dialog that contains the undeclared variable.

Note: It is acceptable for a dialog to have undeclared variables; this message is intended as a debugging tool.

System action

name is treated as if it were declared as scope scope, and the dialog continues executing. The DEFAULTSCOPE keyword on the OPTION statement may be used to change the default scope. This message will be issued each time the dynamic variable is referenced.

User response

Review the dialog shown in message KLVDM015 to determine the proper variable scope. Then add it to the DECLARE section.

Message Type

LOG, VIEW

KLVDM024 INVALID VARIABLE NAME X'hexstring'

Explanation

The dialog manager detected an invalid dynamically constructed variable name, hexstring. (Dynamically constructed variable names take the general form of &(&varname).) KLVDM015 follows this message and shows the dialog associated with the error.

System action

A null is used for the variable's value.

User response

If the problem is with a user-defined dialog, review the dialog shown in KLVDM015 and correct the SSPL code that constructs the invalid variable name. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM030 KLVTBMGR LOGIC ERROR

Explanation

The TMS: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 of the system's dump data sets or both.

User response

Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log, and then contact IBM Software Support.

Message Type

REPLY

KLVDM031 KLVTBMGR INVALID TABLE DELETE POINTER

Explanation

The TMS: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 or the system's dump data sets or both

User response

Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log, and then contact IBM Software Support.

Message Type

REPLY

KLVDM040 STATEMENT OUT OF PLACE: library(dialog) LINE(line)

Explanation

The OPTION statement must appear as the first or top level of a dialog that includes other common members from the panel library. dialog is the dialog that was being refreshed; library is the name of the DD that contains the member; line is the line number in the member where the misplaced statement was found.

System action

The panel interpretation fails.

User response

If the problem is with a user-defined dialog, move the )OPTION statement in member to beginning of the dialog, and refresh it. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM041 errmsg: 'text': library(dialog) LINE(line)

Explanation

A statement in dialog dialog contains invalid syntax. library is the name of the DD that contains the member; line is the line number in the member where the error was detected. errmsg is an error message beginning with KLVSC; text is the text at or near the error.

System action

Compilation of the current source member is terminated. If dialog is a COPY member, processing of the previous source member will continue but the compilation will be failed when all processing is complete.

User response

If the problem is with a user-defined dialog, correct the statement shown, and refresh the dialog. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM042 RECURSIVE COPY DETECTED copymem): library(member) LINE(line)

Explanation

A COPY statement for source member copymem was found in a dialog that is being processed as a result of a prior COPY for the same member. member is the source member that contains the second COPY; library is the name of the DD that contains the member; line is the line number in the member where the second COPY was found.

System action

Compilation of the current source member is terminated. If member is a COPY member, processing of the previous source member will continue but the compilation will be failed when all processing is complete.

User response

If the problem is with a user-defined dialog, remove or correct the invalid control statement and attempt to refresh the panel. If the command completes successfully, the panel is ready for use. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM043 COPY MEMBER NOT FOUND: MEMBER(copymem): library(member) LINE(line)

Explanation

The source member named on a COPY statement, copymem, could not be found. member is the source member that contains the COPY; library is the name of the DD that contains the member, and that does not contain the copy member; line is the line number in the member where COPY was found.

System action

Compilation of the current source member is terminated. If member is a COPY member, processing of the previous source member will continue but the compilation will be failed when all processing is complete.

User response

If the problem is with a user-defined dialog, check your panel definition and correct the panel's )COPY control statement, or add the member into the panel library. Then refresh the dialog. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM044 UNSUPPORTED LEVEL: 'n': library(dialog) LINE(line)

Explanation

While compiling the SSPL dialog dialog, an OPTIONS statement was found at line line that specified an invalid LEVEL value, n. library is the name of the DD that contains the member.

System action

The dialog compilation fails.

User response

If the problem is with a user-defined dialog, correct or remove the LEVEL keyword. Recompile the dialog. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

VIEW, ERROR

KLVDM045 NOTDECLARED(text) IS INVALID: library(dialog) LINE(line)

Explanation

While compiling the SSPL dialog member, an OPTIONS statement was found at line line that specified an invalid NOTDECLARED value, text. library is the name of the DD that contains the member.

System action

The dialog compilation fails.

User response

If the problem is with a user-defined dialog, correct or remove the NOTDECLARED keyword. Recompile the dialog. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM046 DEFAULTSCOPE(text) IS INVALID library(dialog) LINE(line)

Explanation

While compiling the SSPL dialog member, an OPTIONS statement was found at line line that specified an invalid DEFAULTSCOPE value, text. library is the name of the DD that contains the member.

System action

The dialog compilation fails.

User response

If the problem is with a user-defined dialog, correct or remove the DEFAULTSCOPE keyword. Recompile the dialog. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM048 INVALID PANEL CONTROL STATEMENT: text: library(dialog) LINE(line)

Explanation

An invalid panel control statement, text, was encountered while compiling the dialog, dialog. library is the name of the DD that contains the member; line is the line number in the member where the invalid statement was found.

System action

The dialog compilation fails.

User response

If the problem is with a user-defined dialog, currently supported control statements are )BODY, )EPILOGUE, )PROLOGUE, )COMMENT, and )COPY. Correct the control statement and issue the REFRESH command to determine if the panel is ready for use. If the problem is with an IBM-supplied dialog, contact IBM Software Support.

Contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM049 INVALID DBCS DATA: XRC(xrc) MEMBER(panel) LINE(lineno)

Explanation

An SSPL statement containing invalid DBCS data was encountered while interpreting a panel definition. The message provides the DBVALIDATE return code xrc, the panel name panel and line number lineno. The following are valid xrc values:

Return code Meaning
8 A DBCS subfield contains an odd number of bytes
12 A DBCS subfield contains an invalid codepoint
16 Missing SO. An SI character was detected before finding an SO.
20 Missing SI. An SO character was detected before finding an SI or end of string was detected.

System action

Panel interpretation terminates.

User response

Correct the SSPL statement and issue the REFRESH command to determine if the panel is ready for use.

Message Type

WARNING

KLVDM050 keyword(value) IS OUT OF RANGE (min-max); DEFAULTS TO def

Explanation

keyword in the KLVINDM member of RKANPAR was specified with a value that is too small (min) or too large (max).

System action

The default value, def, will be used. TMS:Engine initialization continues.

User response

Correct the keyword value. If the default value is unacceptable, recycle TMS:Engine.

Message Type

WARNING

KLVDM051 DIALOG MANAGER INITIALIZED: LIMIT(limit)

Explanation

A dialog manager initialization that completes successfully logs this message to create an audit trail.

System action

None.

User response

None.

Message Type

INFO

KLVDM052 DIALOG LIBRARY UNAVAILABLE

Explanation

The RKANPENU dialog library was not present or could not be opened during TMS:Engine dialog manager initialization.

System action

Dialog manager initialization fails and TMS:Engine terminates.

User response

Ensure the RKANPENU DD is present and points to a dialog library. Then restart the product.

Message Type

ALERT

KLVDM053 UNRECOGNIZED INITIALIZATION STATEMENT: stmttype

Explanation

The statement stmttype is not a valid initialization statement. The statement is in RKANPAR(KLVINDM).

System action

Initialization fails and TMS:Engine terminates.

User response

Correct the statement and retry.

Message Type

ALERT

KLVDM054 keyword(value) IS INVALID; DEFAULTS TO def

Explanation

keyword in the KLVINDM member of RKANPAR was specified with a value that is not a valid choice.

System action

The default value, def, will be used. TMS:Engine initialization continues.

User response

Correct the keyword value. If the default value is unacceptable, recycle TMS:Engine.

Message Type

WARNING

KLVDM056 KLVINDM RKANPAR PARAMETERS:

Explanation

Module KLVINDM logs its start-up parameters as they are read from RKANPAR. This is the header message and will be followed by message KLVDM057.

System action

None.

User response

None.

Message Type

LOG

KLVDM057 parameters

Explanation

As the parameters in module KLVINDM are read, a log audit trail is created.

System action

None.

User response

None.

Message Type

LOG

KLVDM058 SUPPORTED LANGUAGES: list

Explanation

The dialog manager has finished searching for language-specific dialog library DD statements. list is the list of 3-character language codes that the dialog manager has found.

System action

None.

User response

None.

Message Type

LOG

KLVDM059 COULD NOT OPEN ddname PANEL LIBRARY

Explanation

The dialog manager could not open the ddname DD, which is a dialog library.

System action

Dialog manager initialization fails and TMS:Engine terminates.

User response

Review the job and z/OS logs for IBM data management messages (IEC) that identify the problem. Correct the error and restart the product.

Message Type

ALERT

KLVDM061 DBCS STRING TRUNCATED IN DIALOG(dialogname) BODY AT ROW(rownum) COL(columm)

Explanation

The dialog dialogname contains a Double-Byte Character Set (DBCS) string which is not properly terminated by a Shift-Out (SO) character.

System action

The system assumes a SO character at the indicated row and column number.

User response

Add the proper SO character.

Message Type

INFO

KLVDM070 COMPILED DIALOG EXCEEDS MAIN STORAGE LIMIT: library(dialog)

Explanation

The compiled dialog, dialog, exceeds the maximum memory allocation permitted by TMS:Engine. library is the DD name that contains the dialog.

System action

The panel compilation is terminated.

User response

Split dialog into smaller dialogs.

Message Type

LOG, VIEW

KLVDM071 DIALOG dialog NOT FOUND IN ddname LIBRARY

Explanation

Dialog dialog was referenced on a select statement, dialog statement, COPY statement, or the REFRESH command, but it was not in the panel library, ddname.

System action

If the error occurs during an operator command, the command terminates. If it occurs during dialog execution, the dialog thread will generally be terminated.

User response

If this is a user-supplied dialog, determine the location of the invalid reference, correct it, and retry the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM072 CRITICAL DIALOG MAY NOT HAVE PRESENTATION CAPABILITY library(dialog)

Explanation

A critical dialog must have a presentation space. library is the DD name that contains the dialog.

System action

The dialog compilation fails.

User response

Contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM073 DOWNLEVEL CONSTRUCTS CONVERTED; CHECK RKLVLOG FOR DETAILS: library(dialog)

Explanation

While compiling the SSPL dialog dialog, one or more statements were found with downlevel syntax. library is the DD name that contains the dialog.

System action

None.

User response

If this is a user-supplied dialog, refer to the TMS:Engine RKLVLOG file for KLVDM120, KLVDM125, or KLVDM126 messages associated with member. These will identify the downlevel syntax. Modify the dialog as appropriate.

If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM074 TRACE REQUEST IGNORED FOR dialog - DIALOG TRACE IS OFF

Explanation

A REFRESH operator command was issued for dialog with the TRACE keyword specified. However, dialog trace is not currently active.

System action

The dialog is compiled without trace information.

User response

If you want dialog to be traceable, activate dialog trace with the DTRACE operator command. Then reissue the REFRESH command. Otherwise, no action is needed.

Message Type

LOG, VIEW

KLVDM101 EXCESSIVE OPERANDS: statement PROVIDED (n) ALLOWS (m): library(dialog) LINE(line)

Explanation

n operands are provided in the procedure or function statement statement, but only m operands are allowed. dialog is the dialog that contains the error. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM102 INSUFFICIENT OPERANDS: statement PROVIDED (n) REQUIRES (m) library(dialog) LINE(line)

Explanation

n operands are provided in the procedure or function statement statement but only m operands are required. dialog is the dialog that contains the error. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM103 VOID EXPRESSION: library(dialog) LINE(line)

Explanation

An expression was provided without operands, such as (()), in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM104 OPEN EXPRESSION: library(dialog) LINE(line)

Explanation

An expression was provided with more opening than closing parentheses, such as ((expr), in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM105 UNBALANCED PARENTHESES: library(dialog) LINE(line)

Explanation

An expression was provided with more closing than opening parentheses, such as (expr)), in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM106 label IS A DUPLICATE LABEL: library(dialog) LINE(line)

Explanation

The label label is defined more than once within the dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM107 IMPROPER USE OF statement CONSTRUCT: library(dialog) LINE(line)

Explanation

The dialog management statement statement was used improperly. This is usually an END or UNTIL statement without a DO, or an ELSE statement without an IF. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM109 IMPROPER TOKEN USAGE: library(dialog) LINE(line)

Explanation

An invalid token was detected within dialog dialog. This is often a misspelled dialog function name. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM110 OPEN CONSTRUCT(S) IN PROCEDURE: library(dialog) LINE(line)

Explanation

A DO statement without an END statement was found in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM111 LABEL label IS UNRESOLVED: library(dialog) LINE(line)

Explanation

A GOTO or CALL statement referenced a label that was not found in the dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM112 PREMATURE END OF MEMBER: library(dialog) LINE(line)

Explanation

The end of a dialog was reached before a statement was completed. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error and test the dialog. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM113 OPEN ENVIRONMENT: 'text': library(dialog) LINE(line)

Explanation

dialog contains an opening delimiter, text, without a closing delimiter. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, enter the closing delimiter and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM120 DOWNLEVEL FUNCTION SYNTAX: 'name' library(dialog) LINE(line)

Explanation

Dialog dialog contains a dialog function call (name) that does not have parentheses around its argument list. This is known as level 0 syntax. library is the DD name that contains the dialog. line is the location where the condition was detected.

System action

This is an information message. The dialog continues compiling.

User response

If this is a user-supplied dialog, modify the dialog so that the function arguments are enclosed in parentheses immediately following the function. If the function has no arguments, parentheses are still required, for example, VSSREFR(). After making the changes, add )OPTION LEVEL(1) at the beginning of the dialog to indicate that functions are identified by parenthetical parameter lists.

If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM121 UNBALANCED COMMENT DELIMITER(S): library(dialog) LINE(line)

Explanation

A comment-end delimiter (*/) was found in dialog dialog without a corresponding comment-start delimiter (/*). library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the error. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM122 INVALID HEX LITERAL: '\x': library(dialog) LINE(line)

Explanation

An invalid hexadecimal string, x was detected in dialog dialog. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, enter the correct value (\xx, where either x = 0 - 9 or A - F) and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM123 INVALID STRING FUNCTION: 'func': library(dialog) LINE(line)

Explanation

func was coded as a string function in dialog dialog, but it is either not a valid SSPL statement or dialog function name or is not allowed to be used as a string function. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the syntax and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM124 INVALID STRING FORMAT: 'string': library(dialog) LINE(line)

Explanation

An invalid string, string, was detected in dialog dialog. It may be missing a closing quote, or may contain a missing or invalid variable name. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

If this is a user-supplied dialog, correct the string and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM125 DOWNLEVEL REFERENCE: 'text': library(dialog) LINE(line)

Explanation

A statement in dialog dialog was coded using a syntax that is no longer supported. library is the DD name that contains the dialog. line is the location where the condition was detected.

System action

text is converted internally to the correct syntax and message KLVDM126 is issued to display it. The dialog continues compiling.

User response

If this is a user-supplied dialog, refer to KLVDM126 for the correct syntax and modify the dialog accordingly. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM126 CONVERTED REFERENCE: 'text': library(dialog) LINE(line)

Explanation

This message follows KLVDM125 and displays how the unsupported syntax was converted. text is the converted text. dialog is the dialog that contains the statement. library is the DD name that contains the dialog. line is the location where the condition was detected.

System action

None.

User response

None.

Message Type

LOG, VIEW

KLVDM127 WARNING - OPEN COMMENT BLOCK: library(dialog) LINE(line)

Explanation

During refresh processing for dialog dialog, the dialog manager detected an open comment block (more /* than */). line is the line where the error was detected, and is typically an SSPL section marker ()PROLOG, )BODY, etc.). library is the DD name that contains the dialog.

System action

This is a warning message only. The dialog continues compiling, but portions of the dialog may be omitted or syntax errors may be reported.

User response

If this is a user-supplied dialog, review dialog member and correct the open comment block. If this is an IBM-supplied dialog, contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM128 MAXIMUM ATTRIBUTES EXCEEDED FOR ATTR(attr): library(dialog) LINE(line)

Explanation

More than 252 panel attributes have been declared in dialog dialog. attr is the offending attribute. library is the DD name that contains the dialog. line is the location where the error was detected.

System action

The dialog compilation fails.

User response

Contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM130 diagnostic text

Explanation

This message is for internal use. It can be ignored unless requested by IBM Software Support.

System action

None.

User response

None.

Message Type

LOG

KLVDM131 TOKEN-TRACE, next, length, value, current, stack, frame

Explanation

This message is for internal use. It can be ignored unless requested by IBM Software Support.

System action

None.

User response

None.

Message Type

LOG

KLVDM132 LABEL-TRACE, next, length, value, current, stack, frame

Explanation

This message is for internal use. It can be ignored unless requested by IBM Software Support.

System action

None.

User response

None.

Message Type

LOG

KLVDM133 TRACE ENVIRONMENT READ FAILED, RC=rc

Explanation

An internal processing error has occurred during dialog grace statement range processing.

System action

Any previous range remains active.

User response

Save the rc value and contact IBM Software Support.

Message Type

REPLY

KLVDM134 STATEMENT RESOURCE INITIALIZATION FAILED

Explanation

An internal processing error has occurred during dialog trace statement range processing.

System action

Any previous range remains active.

User response

Contact IBM Software Support.

Message Type

REPLY

KLVDM201 INSUFFICIENT STORAGE FOR RESULT OF ENCDEC FUNCTION

Explanation

The result of an encryption or decryption function was too large for the storage area to receive it. This is a should not occur condition.

System action

The dialog is terminated. KLVDM015 follows this message and displays information about the dialog, terminal, and application associated with the failure.

User response

Save a copy of the dialog, the contents of RKLVIN, and the TMS:Engine run sheets. Then contact IBM Software Support.

Message Type

LOG, VIEW

KLVDM901 INVALID PARMS PASSED TO KLV$DMNL

Explanation

An internal processing error has occurred.

System action

The current function is abended with code U0100 to force a diagnostic dump.

User response

Save the TMS:Engine run sheets and RKLVLOG, JES SYSLOG, and SVC dump. Then contact IBM Software Support.

Message Type

ABEND

KLVDM902 LANGUAGE CODE MUST BE 3 CHARACTERS

Explanation

A language code was entered that is too long or too short. Language codes must be 3 characters.

System action

The operator command is terminated.

User response

Reissue the command with a valid language code.

Message Type

ERROR

KLVDM903 LANGUAGE CODE ccc IS NOT VALID

Explanation

The language code, ccc, is not supported. Message KLVDM904 follows and lists the valid codes. The operator command is terminated.

User response

Reissue the command with a valid language code.

Message Type

ERROR

KLVDM904 VALID CODES ARE ccc ...

Explanation

The language codes recognized by TMS:Engine are displayed.

System action

None.

User response

None.

Message Type

ERROR