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
TMS:Engine dispatcher was invoked from SRB mode.
TMS:Engine abends U0200.
Contact IBM® Software Support.
Reply
The user data passed to the KLVENTRY dialog contains more than five subfields.
The excess fields are ignored.
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.
None
A function key that is not assigned a function was pressed.
The key is ignored.
Refer to the bottom of the display panel for a list of active keys.
None
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.
None.
Refer to the values in the message to resolve problems with APL support for a given terminal.
None
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.
The help processor stops.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help processor stops processing either the glossary or index.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help processor terminates.
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.
None
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.
The help processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
None
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.
The help processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help index or glossary will not be available.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The help processor terminates; help or the glossary is not available for the application.
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.
None
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.
No further processing is performed for member; the help processor continues with any other pending requests.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
term is ignored; the help processor continues with any other pending requests.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
The date processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
None
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.
The date processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
None
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.
The date processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
None
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.
The date processor terminates.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
None
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.
No help or glossary information is available.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
term is ignored; the help processor continues with any other pending requests.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
Further processing for the help index or glossary is terminated.
Save the TMS:Engine RKLVLOG and contact IBM Software Support.
LOG, VIEW
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.
None.
None.
LOG, VIEW
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.
None.
None.
LOG, VIEW
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.
The load or unload request continues. Message KLVDL202 may follow this message if table is being loaded with a different name.
None.
INFO
The KLVTBULD SSPL dialog has been invoked to load a table with a name (newname) different than the original name.
The load or unload request continues.
None.
INFO
A programming error has been detected in dialog application appl.
The dialog application is terminated.
Save the contents of this message and contact IBM Software Support.
LOG, VIEW
Dialog application appl has requested that debugging information be written to RKLVLOG. Message KLVDL302 may follow this message.
None.
None.
LOG, VIEW
This message follows KLVDL301 and contains debugging information.
None.
None.
LOG, VIEW
A programming error has been detected in dialog application appl.
The dialog application is terminated.
Save the contents of this message and contact IBM Software Support.
LOG, VIEW
The KLVCASE dialog has been invoked to force subsequent logons to SSPL-based products to be displayed in upper or mixed case.
None.
None.
LOG, VIEW. This message is also written to the z/OS® SYSLOG.
The MINIMUM and MAXIMUM options specified
on a )BODY
dialog
statement are mutually exclusive. The associated dialog and
line number are shown for reference.
Panel interpretation fails.
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.
WARNING
The TMS:Engine variables manager detected an attempt to use a string longer than approximately 30,000 bytes.
The thread is terminated with a U0100 abend, sending a dump to the RKLVSNAP file or the system's dump data sets or both.
Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.
Abend
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.
The dialog compilation fails.
Contact IBM Software Support.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
The BODY section of dialog dialog contains a variable name, varname, that is longer than 8 characters.
The dialog compilation fails.
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.
LOG, VIEW
An illegal variable name in line $ddline of member $ddmbr was encountered.
The dialog is terminated.
Contact IBM Software Support.
ERROR
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.
The panel compilation fails.
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.
LOG, VIEW
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.
The panel compilation fails.
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.
LOG, VIEW
An internal error has been detected by the TMS:Engine variables manager.
The request is terminated with a U0100 abend, sending a dump to the RKLVSNAP file or the system's dump data sets.
Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.
ABEND
The TMS:Engine variables manager detected an error in its data structures.
The request is terminated with a U0100 abend, sending a dump to the RKLVSNAP file and the system's dump data sets or both.
Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.
ABEND
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.
None.
None.
LOG, VIEW
The specified dialog failed during execution.
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.
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. |
LOG, VIEW, INFO
The LOOPCTR limit has been exceeded for a dialog. KLVDM015 follows this message and identifies the failing dialog.
The dialog terminates.
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.
LOG, VIEW
A dialog has attempted a numeric operation on a value that was not numeric. KLVDM015 follows this message and identifies the failing dialog.
The dialog terminates.
Contact IBM Software Support.
LOG, VIEW
A dialog could not be executed because the dialog manager discovered a storage shortage. KLVDM015 follows this message and identifies the failing dialog.
The dialog and the user's session terminate.
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.
LOG, VIEW
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.
None.
None.
LOG, VIEW
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.
If LONGVARNAME(FAIL)
was specified,
the dialog fails. Otherwise, the variable name is truncated at 8 characters
and processing continues.
Correct the variable name and refresh the dialog.
LOG, VIEW
The TMS:Engine dialog manager was passed an invalid request.
The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file or the system's dump data sets or both.
Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log. Then contact IBM Software Support.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
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.
Review the dialog shown in message KLVDM015 to determine the proper variable scope. Then add it to the DECLARE section.
LOG, VIEW
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.
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.
Review the dialog shown in message KLVDM015 to determine the proper variable scope. Then add it to the DECLARE section.
LOG, VIEW
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.
A null is used for the variable's value.
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.
LOG, VIEW
The TMS:Engine tables manager detected an invalid condition while performing a request.
The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file of the system's dump data sets or both.
Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log, and then contact IBM Software Support.
REPLY
The TMS:Engine tables manager detected an invalid condition while performing a request.
The request is terminated with a U0200 abend, sending a dump to the RKLVSNAP file or the system's dump data sets or both
Keep the TMS:Engine run sheets, dump files, this message, and the z/OS system log, and then contact IBM Software Support.
REPLY
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.
The panel interpretation fails.
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.
LOG, VIEW
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.
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.
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.
LOG, VIEW
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.
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.
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.
LOG, VIEW
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.
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.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
VIEW, ERROR
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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. |
Panel interpretation terminates.
Correct the SSPL statement and issue the REFRESH command to determine if the panel is ready for use.
WARNING
keyword in the KLVINDM member of RKANPAR was specified with a value that is too small (min) or too large (max).
The default value, def, will be used. TMS:Engine initialization continues.
Correct the keyword value. If the default value is unacceptable, recycle TMS:Engine.
WARNING
A dialog manager initialization that completes successfully logs this message to create an audit trail.
None.
None.
INFO
The RKANPENU dialog library was not present or could not be opened during TMS:Engine dialog manager initialization.
Dialog manager initialization fails and TMS:Engine terminates.
Ensure the RKANPENU DD is present and points to a dialog library. Then restart the product.
ALERT
The statement stmttype is not a valid initialization statement. The statement is in RKANPAR(KLVINDM).
Initialization fails and TMS:Engine terminates.
Correct the statement and retry.
ALERT
keyword in the KLVINDM member of RKANPAR was specified with a value that is not a valid choice.
The default value, def, will be used. TMS:Engine initialization continues.
Correct the keyword value. If the default value is unacceptable, recycle TMS:Engine.
WARNING
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.
None.
None.
LOG
As the parameters in module KLVINDM are read, a log audit trail is created.
None.
None.
LOG
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.
None.
None.
LOG
The dialog manager could not open the ddname DD, which is a dialog library.
Dialog manager initialization fails and TMS:Engine terminates.
Review the job and z/OS logs for IBM data management messages (IEC) that identify the problem. Correct the error and restart the product.
ALERT
The dialog dialogname contains a Double-Byte Character Set (DBCS) string which is not properly terminated by a Shift-Out (SO) character.
The system assumes a SO character at the indicated row and column number.
Add the proper SO character.
INFO
The compiled dialog, dialog, exceeds the maximum memory allocation permitted by TMS:Engine. library is the DD name that contains the dialog.
The panel compilation is terminated.
Split dialog into smaller dialogs.
LOG, VIEW
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.
If the error occurs during an operator command, the command terminates. If it occurs during dialog execution, the dialog thread will generally be terminated.
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.
LOG, VIEW
A critical dialog must have a presentation space. library is the DD name that contains the dialog.
The dialog compilation fails.
Contact IBM Software Support.
LOG, VIEW
While compiling the SSPL dialog dialog, one or more statements were found with downlevel syntax. library is the DD name that contains the dialog.
None.
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.
LOG, VIEW
A REFRESH operator command was issued for dialog with the TRACE keyword specified. However, dialog trace is not currently active.
The dialog is compiled without trace information.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
If this is a user-supplied dialog, enter the closing delimiter and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.
LOG, VIEW
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.
This is an information message. The dialog continues compiling.
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.
LOG, VIEW
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.
The dialog compilation fails.
If this is a user-supplied dialog, correct the error. If this is an IBM-supplied dialog, contact IBM Software Support.
LOG, VIEW
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.
The dialog compilation fails.
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.
LOG, VIEW
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.
The dialog compilation fails.
If this is a user-supplied dialog, correct the syntax and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.
LOG, VIEW
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.
The dialog compilation fails.
If this is a user-supplied dialog, correct the string and recompile. If this is an IBM-supplied dialog, contact IBM Software Support.
LOG, VIEW
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.
text is converted internally to the correct syntax and message KLVDM126 is issued to display it. The dialog continues compiling.
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.
LOG, VIEW
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.
None.
None.
LOG, VIEW
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.
This is a warning message only. The dialog continues compiling, but portions of the dialog may be omitted or syntax errors may be reported.
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.
LOG, VIEW
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.
The dialog compilation fails.
Contact IBM Software Support.
LOG, VIEW
This message is for internal use. It can be ignored unless requested by IBM Software Support.
None.
None.
LOG
This message is for internal use. It can be ignored unless requested by IBM Software Support.
None.
None.
LOG
This message is for internal use. It can be ignored unless requested by IBM Software Support.
None.
None.
LOG
An internal processing error has occurred during dialog grace statement range processing.
Any previous range remains active.
Save the rc value and contact IBM Software Support.
REPLY
An internal processing error has occurred during dialog trace statement range processing.
Any previous range remains active.
Contact IBM Software Support.
REPLY
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.
The dialog is terminated. KLVDM015 follows this message and displays information about the dialog, terminal, and application associated with the failure.
Save a copy of the dialog, the contents of RKLVIN, and the TMS:Engine run sheets. Then contact IBM Software Support.
LOG, VIEW
An internal processing error has occurred.
The current function is abended with code U0100 to force a diagnostic dump.
Save the TMS:Engine run sheets and RKLVLOG, JES SYSLOG, and SVC dump. Then contact IBM Software Support.
ABEND
A language code was entered that is too long or too short. Language codes must be 3 characters.
The operator command is terminated.
Reissue the command with a valid language code.
ERROR
The language code, ccc, is not supported. Message KLVDM904 follows and lists the valid codes. The operator command is terminated.
Reissue the command with a valid language code.
ERROR
The language codes recognized by TMS:Engine are displayed.
None.
None.
ERROR