All messages are shown in this section are in mixed case English. The uppercase English message text is the same, but is in uppercase letters.
Each message has a number of the form EQAnnnnx, where EQA indicates that the message is an Debug Tool message, nnnn is the number of the message, and x indicates the severity level of each message. The value of x is I, W, E, S, or U, as described below:
Symbols in messages
Many of the Debug Tool messages contain information that is inserted by the system when the message is issued. In this publication, such inserted information is indicated by italicized symbols, as in the following:
EQA1046I The breakpoint-id breakpoint is replaced.
The portion of Debug Tool located on the host notifies you of errors associated with debugging functions carried out by the host.
Refer to the following topics for more information related to the material discussed in this topic.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs after Debug Tool initialization and before any program hooks are reached. Enter a command. If you are not sure what you can enter, enter HELP or ?. Information is displayed identifying the commands you are allowed to enter.
Used to display SCREEN as part of QUERY SCREEN.
Only one window was open when a CLOSE command was issued. At least one window must be open at all times, so the CLOSE command is ignored.
The window specified in the FIND command is closed.
The window specified in the SIZE command is closed.
The window specified in the SCROLL command is closed.
It is the character string 'Command' in the main panel command line.
It is the character string 'Step' in the main panel command line while stepping.
It is the character string 'Scroll' in the main panel command line.
The user entered DBCS characters in scroll, window object id, qualify, prefix, or panel input areas.
It is the character string 'More' in the main panel command line.
Asking for confirmation to terminate debug session. Enter Y for YES or N for NO.
This informational message is displayed while entering a block of commands, until the command block is closed by an END statement.
Debug Tool needs more input in order to completely parse a command. This can occur in COBOL, for example, because PERFORM; was entered on the last line.
Complete the command.
The explanation of a command was requested or a command was determined to be in error.
Determine the cause of the error and reenter the command.
This title line will be followed by message 1015.
This message is used to list all the items that can follow a partially parsed command.
Reenter the acceptable part of the command and suffix it with one of the items in this list.
This alerts the user to the fact that a previous breakpoint action existed and was replaced.
Verify that this was intended.
This alerts the user to the fact that a previous breakpoint action existed and was replaced.
Verify that this was intended.
An ALLOCATE occurred for a variable where an AT ALLOCATE breakpoint was established.
Used to display a command after LIST AT when there is no every_clause. Enabled breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is an every_clause. Enabled breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is no every_clause. Deferred and enabled breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is an every_clause. Deferred and enabled breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is not an every_clause. For disabled breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is an every_clause. For disabled breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is not an every_clause. For disabled and deferred breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
Used to display a command after LIST AT when there is an every_clause. For disabled and deferred breakpoints only. This message is followed by a message of one or more lines showing the commands performed each time the breakpoint is hit.
You are trying to issue an AT STATEMENT command against a statement but the code for that statement was either optimized away or combined with other statements.
Display after LIST AT to reflect RUNTO position.
The compilation unit (program) that you specified could not be located by Debug Tool. The breakpoint is deferred until this CU is entered.
Used to display a command after LIST AT for suspended breakpoints only.
Used to display a command after LIST AT for suspended and disabled breakpoints only.
The program might be written in an unsupported language or may be a disassembled program. The message is issued as a result of the LIST CALLS command.
The compile unit was compiled without the TEST option. The message is issued as a result of the LIST CALLS command.
CU name of the call chain. The message is issued as a result of the LIST CALLS command.
The compile unit was compiled without the TEST option and is in the Debug Tool list of CUs.
You declared a variable whose name is the same as a previously declared variable. This declaration overrides the previous one.
This is the title line for the DESCRIBE PROGRAM command.
This is the first of a group of DESCRIBE PROGRAM messages.
Used to display a compile option without parameters, for example, NOTEST.
Used to display a compile option with one parameter, for example, OPT.
Used to display a compile option with two parameters, for example, TEST.
A DESCRIBE PROGRAM command refers to a program that is totally contained in one block.
The names of the blocks contained by the program are displayed under this title line.
The first insert controls the indentation while the second is the block name without qualification.
The statement table is abbreviated such that no relationship between storage locations and statement identifications can be determined.
If statement identifications are required, the program must be recompiled with different compiler parameters.
The program named in the DESCRIBE PROGRAM command was compiled with GONUMBER assumed.
The program named in the DESCRIBE PROGRAM command was compiled with GOSTMT assumed.
This message is used in listing items returned from the back end in response to the DESCRIBE ENVIRONMENT command.
Text of a DESCRIBE ATTRIBUTES message.
Text of a DESCRIBE ATTRIBUTES message.
Indicate compiler version for DESCRIBE CU.
Text of a DESCRIBE ATTRIBUTES message.
COBOL run-time library does not return information to support this command.
This is issued in response to DESCRIBE ENVIRONMENT if no open files are detected.
This is the header message issued in response to DESCRIBE ENVIRONMENT before issuing the list of enabled conditions.
This is the header message issued in response to DESCRIBE ENVIRONMENT before issuing the list of disabled conditions.
This message is used for the DESCRIBE CU command. If a CU was compiled with NOTEST, no statement table was generated.
This is a title line that is the result of a DESCRIBE ATTRIBUTES *;. It precedes the names of all variables contained within a single block.
The first insert controls the indentation while the second is the qualified variable name followed by attribute string. (for C, only the attributes are given.)
This is the title line for the list of files that are known to be open. This is in response to the DESCRIBE ENVIRONMENT command.
This program has insufficient information. It might be compiled without the TEST option.
This is the response for the DESCRIBE ENVIRONMENT command when the Language Environment math library is being used.
This is the response for the DESCRIBE ENVIRONMENT command when the PL/I math library is being used.
Used to display a compile option with three parameters, for example TEST(ALL,SYM,SEPARATE)
Heading line for DESCRIBE ALLOCATIONS output.
Header for DESCRIBE ALLOCATIONS output.
Header for DESCRIBE ALLOCATIONS output.
Description of the current allocation.
There was not enough main memory available to process the command.
During the processing of the command, the indicated macro invocation failed with the indicated return and reason codes.
The dynamic allocation failed with the indicated return and reason codes.
The indicated data set was not cataloged or was not found on the volume on which it was cataloged.
If the command was ALLOCATE, the specified file was already allocated. FREE the file and retry the ALLOCATE. If the command was FREE, the specified file was not allocated.
The specified data set is already allocated in such a way that it cannot be allocated with the specified disposition.
The command is not supported in the current environment (such as CICS®)
This is the header used to display the additional CSECT's included in the EQALANGX data for the current CU.
Used to display CSECT's also included in the EQALANGX data for the current CU.
This message is issued as part of the output of DESCRIBE CUS. It indicates the version of the EQALANGX program used to generate the debug data for the specified CU. If this version is earlier than the current version of the EQALANGX program, unexpected results may occur in some situations.
This message is issued as part of the output of DESCRIBE CUS. It indicates the version of the EQALANGX program that is current for this version of Debug Tool.
The names of the INCLUDE files contained by the program are displayed under this title line.
Automonitor Previous Statement area in the Monitor window.
This message is used to produce output for LIST ( ... ).
This message is used to produce output for LIST TITLED ( ... ) when an expression is a scalar.
This insert is used for naming the expression for expression element.
First line of output from the ANALYZE EXPRESSION command.
Text of a DESCRIBE ATTRIBUTES message.
Text of a DESCRIBE ATTRIBUTES message.
This message is used to produce a columned list. For example, it is used to format the response to LIST STATEMENT NUMBERS.
The name of a variable that satisfies a LIST NAMES request is displayed.
The name of a variable that satisfies a LIST NAMES request is displayed. It is contained within an aggregate but is a parent name and not an elemental data item.
The name of a variable that satisfies a LIST NAMES request is displayed. It is contained within an aggregate and is an elemental data item.
The name of a variable that satisfies a LIST NAMES request is displayed. It is an aggregate contained within another aggregate.
This is a title line that is the result of a LIST NAMES command. It precedes the names of all variables contained within a single block.
This is a title line that is the result of a LIST NAMES command. It precedes the names of all session variables contained within a single block.
This title line precedes the list of variable names that satisfy the pattern in a LIST NAMES command.
This title line precedes the list of session names that satisfy the pattern in a LIST NAMES command.
This title line precedes a list of compile unit names for noninitial load modules in a LIST NAMES CUS command.
This title line precedes a list of compile unit names for noninitial load modules that satisfy the pattern in a LIST NAMES CUS command.
This line appears when no compile unit satisfied the pattern in a LIST NAMES CUS command for noninitial load modules.
This title line precedes a list of compile unit names for an initial load module in a LIST NAMES CUS command.
This line appears when no compile unit satisfied the pattern in a LIST NAMES CUS command for an initial load module.
This line appears when no Procedures satisfied the pattern in a LIST NAMES PROCEDURES command.
This title line precedes a list of Procedure names for a LIST NAMES PROCEDURES command.
The LIST NAMES command found no variables in the specified block.
The LIST NAMES command found no variables that had been declared in the session for the current programming language.
The LIST NAMES command found named variables in the named block but none of the names satisfied the pattern.
The LIST NAMES command found named variables that had been declared in the session but none of the names satisfied the pattern.
A LIST NAMES PROCEDURES was issued but no session procedures exist.
Used when listing registers.
The given reference or address is invalid.
This message is issued upon failure to find frequency information.
This is the header produced by the LIST FREQUENCY command.
This is the frequency count produced by the LIST FREQUENCY command.
This is the trailer produced by the LIST FREQUENCY command.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is a LIST HISTORY message.
This is used to inform the user that for some reason one of the variables cannot be displayed for LIST TITLED.
The requested object does not contain any data members. It contains only methods.
This is a LIST HISTORY message.
This line appears when the setting of Disassembly is OFF and none of the compile units has a debug data. To see all names of these CUS issue SET DISASSEMBLY ON, and then repeat LIST NAMES CUS
The given reference or address is invalid.
The number of bytes to be altered must be equal the length of source.
A maximum of 8 bytes of storage can be change when source is a hexadecimal number, and 4 bytes when source is integer number.
The LIST TITLED command found no variables that had been declared in the section.
This is a title line that is the result of a LIST TITLED command. It precedes the list of all variables contained within a section.
This alerts the user to the fact that a previous EQUATE existed and was replaced.
Verify that this was intended.
This is the header for the QUERY EQUATES command.
Used to display EQUATE identifiers and their associated strings. The string is enclosed in quotation marks so that any leading or trailing blanks are noticeable.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
This is the header produced by LIST MONITOR.
This is the line produced by LIST MONITOR before each command is displayed.
This is the header produced by LIST MONITOR monitor number.
This is a safety message: the user is reminded that a MONITOR command is replacing an old one.
Shows the current point of view.
Shows the place where the program was interrupted.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
The status of the object of a SET command is displayed when QUERYed individually.
The status of the object of a SET command is displayed when issued as part of QUERY SET.
This is the header for QUERY SET.
Used to display PFKEYS as part of QUERY PKFEYS.
Used to display SCREEN as part of QUERY SCREEN.
Shows the bearings in an interrupted program.
The source listing name is not available. The source listing was not required or set before this command.
You tried to issue the SET INTERCEPT ON/OFF for a file that is already set to ON/OFF. This is just an informational message to notify you that you are trying to duplicate the current setting. The command is ignored.
The program has stopped because RUNTO cursor/statement command reached the cursor location or pointed statement number.
Header for the automonitor area in the monitor window.
A PLAYBACK STOP command was processed, which terminated Playback replay mode.
An error occurred so the LLD command was not processed.
Only a disassembly CU can be identified as assembler CU.
Either the file containing the EQALANGX debug data could not be found or there was an undetermined error loading the EQALANGX file for a specified CU.
MONITOR n HEX or MONITOR n DEFAULT are valid only if n represents LIST reference command.
MONITOR n HEX or MONITOR n DEFAULT are valid only if n represents valid LIST command.
The indicated CU is not currently known to Debug Tool. The LOADDEBUGDATA will be executed when the CU appears in a loaded module.
An LDD has already been done for the CU specified in the LDD command. This LDD may have been done previously by the user or an implicit LDD may have been done for the CU. This happens when a user-entered LDD is successful and, subsequently, the CU goes away and later reappears.
A CHANGEVIEW command requested a view that is already the active view for the currently qualified CU.
A CHANGEVIEW command requested a view that not supported by the programming language of the currently qualified CU.
Debug Tool does not currently support changing to a view that would suppress statements that currently contain breakpoints.
This message is displayed in response to the QUERY CURRENT VIEW command.
The previous command could not be completed because of an internal communications error.
The program has stopped because JUMPTO command reached the cursor location or pointed statement number.
Automonitor Previous Statement area in the monitor window.
The data from the statement in which Debug Tool last had control cannot be resolved because the statement is no longer in scope.
Shows the place in the program where the program was previously interrupted.
Header for the automonitor area in the Monitor window when PREVIOUS is specified.
Shows the location where Debug Tool previously had control.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Header with location for the automonitor area in the monitor window.
Header without location information for the automonitor area in the monitor window when PREVIOUS is specified. Used when no location information is available.
Debug Tool is ready to accept a command from the terminal.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information is displayed identifying the commands you are allowed to enter.
Debug Tool tried to read commands from an empty USE file. If unintentional, this could be because of an incorrect file specification.
Correct the file specification and retry.
This is part of a command that is being displayed in the log or in response to a LIST AT. Since a group of commands can be involved, their appearance is improved by indenting the subgroups. Therefore, the first insert is used for indentation, and the second to contain the command. This is the command as it is understood by Debug Tool.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at a statement and a statement table is available.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information is displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at a compile unit entry.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information will be displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at a block entry.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information will be displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at a compile unit exit.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information will be displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at a block exit.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information will be displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at the termination of the application program.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information will be displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in line mode when an initial prompt occurs at a label.
Enter a command. If you are not sure what you can enter, enter HELP or ?. Information is displayed identifying the commands you are allowed to enter.
Debug Tool is ready to accept a command from the terminal. This message is used in full-screen mode when an initial prompt occurs at the termination of the application program.
Debug Tool is ready to accept a command from the terminal. This message is used in full-screen mode when an initial prompt occurs and the location is unknown.
Debug Tool is ready to accept a command from the terminal. This message is used in full-screen mode when an initial prompt occurs after Debug Tool initialization and before any program hooks are reached.
Displays program output with the ddname preceding the output.
Debug Tool has gained control because the program is waiting for input.
Prompts you for intercepted input of fixed-format file.
Prompt user for intercepted input of variable-formatted file.
Debug Tool is ready to accept a command from the terminal. This message is used in linemode when an initial prompt occurs at a statement and a statement table is not available.
Enter a command. If you are not sure of what you can enter, enter HELP or ?. Information is displayed identifying the available commands you are allowed to enter.
This is the header produced by LIST MONITOR when suspended local monitors are present.
A system or user ABEND has been detected by Debug Tool.
The program has stopped running due to the occurrence of the named condition.
The attention request from the terminal was recognized and the Debug Tool was given control.
The program stopped running due to the occurrence of a condition whose name is unknown.
The condition named is described by its severity level or class code. See the z/OS Language Environment Programming Guide.
This message precedes the message that identifies all statement numbers in the block.
This message is used instead of EQA1097I when the number of block levels is greater than the indentation allowed.
The first insert controls the indentation, the second is the INCLUDE file name, and the third insert is the source index block level.
When searching through C or C++ source code, you can only specify FIND columns (explicitly or through SET FIND BOUNDS) other than 1 to * if no trigraphs exist in the source code.
The left column must be less than or equal to the right column.
The left column must be less than or equal to the right source margin. If left and right columns are specified, the left column must be less than or equal to the right column.
If left and right columns are specified or defaulted for FIND, the argument must fit within the specified columns. If only a left column is specified, the argument must fit within the left column and the right source margin.
FIND has reached the bottom of the data without finding the string being searched for.
FIND has reached the top of the data without finding the string being searched for.
This message is used to display the results of a command that the user has entered, such as LIST STORAGE.
This message is used to display the results of a command that the user has entered.
This is the information that is produced when a LIST PROCEDURE command is processed. This message is followed by a message of one or more lines showing the commands that form the procedure.
The LIST PROCEDURE command was issued without naming a session procedure and the current command context is outside of a session procedure.
Verify the request. Reenter the command and name a specific procedure if necessary.
There are no entries in the retrieve queue.
FIND searched the file to the end of the string without finding it and continues the search from the top, back to the starting point of the search.
FIND was successful in locating the target string. The line on which the string was found is displayed just above this message when operating in line mode.
The Operating System can issue its own messages. These are relayed to the user.
The operating system can issue its own messages. These are relayed to the user.
This message is used to place the Debug Tool logo, a timestamp, and copyright at the beginning of the log.
This message is also issued in response to the CALL %VER command. See CALL %VER command for further details on additional information about the time stamp when CALL %VER is used.
Text of a DESCRIBE ATTRIBUTES message for PL/I.
Text of a DESCRIBE ATTRIBUTES message for PL/I.
Text of a DESCRIBE ATTRIBUTES message for PL/I.
Text of a DESCRIBE ATTRIBUTES message for PL/I.
Text of a DESCRIBE ATTRIBUTES message for PL/I.
Text of a DESCRIBE ATTRIBUTES message for PL/I.
The requested variable cannot be accessed.
The was no OTHERWISE clause present in the SELECT statement and none of the WHEN clauses were selected. This message is simply indicating that the OTHERWISE clause would have been executed if it had been present.
Playback was not is the proper state to process the specified statement. The statement is ignored.
Playback was not is the proper state to process the specified statement. The statement is ignored.
Not enough memory was available for Playback data collection. Increase the amount of memory available to Playback on the PLAYBACK ENABLE command.
The specified return code indicated an error condition detected by the Playback run-time API. Playback is disabled.
Return code 63 indicates not enough memory was available for Playback. Restart your Debug Tool session and enter the PLAYBACK ENABLE command using the integer option. For example: PLAYBACK ENABLE * 10000
This message is issued in response to the QUERY PLAYBACK command.
This message is issued in response to the QUERY PLAYBACK LOCATION command when PLAYBACK replay is not active.
This message is issued in response to the QUERY PLAYBACK LOCATION command when PLAYBACK replay is active.
This message is issued in response to the QUERY PLAYBACK LOCATION command when PLAYBACK replay is active.
The previous command is not supported after PLAYBACK START.
The previous command is not supported after PLAYBACK START.
The previous command was ignored because of errors that were indicated by previous messages.
A PLAYBACK START command was entered but the PLAYBACK buffer is empty. The PLAYBACK START command is not processed.
Playback replay has reached the first record in the buffer. You cannot move farther backward.
Playback replay has reached the last record in the buffer. You cannot move farther forward.
Playback replay has encountered data for a compile unit that is no longer active because the load module containing it was canceled or deleted, because the enclave containing it terminated, etc. Playback cannot replay this data because the necessary control blocks are no longer present.
Playback cannot be started while AUTOMONITOR with option BOTH or AUTOMONITOR with option PREVIOUS are in effect.
AUTOMONITOR with option PREVIOUS or AUTOMONITOR with option BOTH is not allowed while PLAYBACK is started.
The variables from the previous statement cannot be resolved because the data is no longer available from the runtime at the time of the request.
This message precedes the output of the NAMES QUERY command and indicates the type of names that follow this message.
This message lists the names output by the NAMES QUERY command.
This message is issued by the NAMES QUERY command when there is no data to be displayed.
The NAMES EXCLUDE command does not allow a pattern of "*".
This message contains the output from the DESCRIBE CHANNEL command.
Debug Tool did not detect any storage violation.
Debug Tool detected a storage violation.
The given reference or address is invalid.
This is the title line for the LIST DTCN command.
This is the title line for the LIST CADP command.
This message lists the program names output by the List DTCN command.
This message lists the program and compile unit names output by the LIST CADP command.
The Enable DTCN|CADP command is not allowed since this particular program and/or compile unit is not in the pattern-match breakpoint list.
There are no entries in the pattern-match breakpoint list.
The Enable DTCN command is not allowed for this particular program and/or compile unit.
The user entered an invalid value.
The user entered a command not recognized by panel processor.
Look at the Window Layout Select Panel, verify that each window has an L, M, S, or E and that each letter is used only once. For example, you cannot have two windows with the letter L.
The user entered an invalid prefix command.
The target for the search command was not found.
A FIND command was issued without an argument. Since the FIND command had not been issued previously, Debug Tool had nothing to search for.
The window header field contains an invalid window ID. Valid window IDs are SOURCE, MONITOR, and LOG.
Scroll field contains an invalid scroll amount.
More than one window header field contains the same window id.
The specified label is on an instruction that is modified at some point in the program. Breakpoints cannot be set on such an instruction.
The user entered an invalid variable.
Prefix command not supported for current programming language.
The specified prefix command is on the statement with no variables.
The user entered prefix command on invalid line.
The user entered a variable number that exceeds the amount of variables in that statement.
More then one invalid prefix commands. To see details you must reenter the invalid command one at a time.
The user entered a prefix command on a line that is contained in a block that is not currently active.
CLEAR EQUATE <name> was attempted for an EQUATE name that has not been established.
For a list of the current EQUATES definitions, issue QUERY EQUATES.
CLEAR EQUATE or QUERY EQUATES was issued but there are no EQUATE definitions.
Language/Country is not supported.
Set National Language and Country.
A SET PROGRAMMING LANGUAGE command was issued, but the initial load module contains no compilation units compiled in the language specified (or implied).
Refer to the maximum number of CUs allowed for debugging.
This is a generic message for SET command errors.
The command was parsed but not executed.
The Dynamic Debug facility setting can not be changed to ON in the middle of a debugging session.
The Dynamic Debug facility setting can not be changed to OFF in the middle of a debugging session.
The CU is not AUTOMONITOR capable.
Refer to the description of the SET AUTOMONITOR command in the Debug Tool Reference and Messages document to determine the requirements this CU must fulfill in order to use the SET AUTOMONITOR command.
The current CU is not AUTOMONITOR capable. SET AUTOMONITOR ON LOG will activate the statement trace.
Refer to the description of the SET AUTOMONITOR command in the Debug Tool Reference and Messages document to determine the requirements this CU must fulfill in order to use the SET AUTOMONITOR command.
The statement trace is active for a CU that is not AUTOMONITOR capable.
The Dynamic Debug facility cannot be deactivated while running without the Language Environment® run-time.
QUERY INTERCEPT was issued but there are no INTERCEPT specifications active.
In order for SET RESTORE BPS AUTO or SET RESTORE MONITORS AUTO to be effective, the settings must be automatically restored when Debug Tool is started. You entered one of these commands but the current setting is SET RESTORE SETTINGS NOAUTO.
%HEX and MONITOR LIST %HEX are not valid for PL/I. It is recommended that the PL/I built-in function HEX be used instead. For example: LIST HEX(expr) or MONITOR LIST HEX(expr).
The entire result from the expression evaluation cannot be displayed; for example, the array is too large.
Comparison or assignment involves incompatible data types, or incompatible or unsupported date fields. If you are using COBOL, see Allowable comparisons for the IF command (COBOL) for allowable comparisons for the Debug Tool IF command, and Allowable moves for the MOVE command (COBOL) for allowable moves for the Debug Tool MOVE command.
The specified argument is not valid.
There are either too many or too few arguments specified.
The specified operand is undefined or is an invalid literal.
An operator or an operand was not understood, and therefore was not processed. Examples of when this message is issued when using COBOL include:
The named variable could not be located or undefined.
You need to qualify to a different block in order to locate the variable.
This feature is not supported. No decimal point is allowed in exponent specification.
This can happen for items within a data record where the file is not active or the record area is not available; for items in a structure following Occurs, depending on the item where the ODO variable was not initialized; or for items in the LINKAGE SECTION that are not based on a valid address.
The combination of characters specified for the literal is not a valid literal.
A nonnumeric operand was found where a numeric operand was expected.
The memory location for a data item contains data that is inconsistent with the data type of the item. The item might not have been initialized.
The sign position of a signed data item contains an invalid sign. The item might not have been initialized.
The expression contains a divide operation where the divisor was determined to be zero.
The target of an assignment is not valid.
The program might have been deleted or canceled.
The subscript or index might be out of range or an ODO variable might not be initialized.
One or more subscripts or indexes were specified for a data item that was not defined as a table. The reference to the data item is not allowed.
A data item defined as a table was referenced without specifying any subscripts or indexes. The reference is not allowed.
A data item defined as a table was referenced with incorrect number of subscripts or indexes. The reference is not allowed.
The length of a data item is incorrect for the definition, usually due to a faulty ODO object.
The ODO variable might not have been initialized, or the current value is out of range.
The specification of the reference modification is not consonant with the length field.
The value of a data item is zero. A zero is invalid in the current context.
Invalid name is specified for a data item.
A qualified reference is invalid. One or more qualifiers might be undefined or not in the same structure as the desired data item.
The qualified reference contains more than the legal number of qualifiers.
There is no data to display for a LIST * request because the DATA DIVISION does not contain any entries.
Status was requested for a sort file. There is never a status available for a sort file.
No COBOL program exists in TEST mode.
The operands for a SET command are incorrect. At least one of the operands must be index name.
The exponent specified for a floating-point literal contains too many digits.
The command is terminated unsuccessfully because an error occurred during processing.
The requested data item could not be displayed due to an error in locating or formatting the data item.
The command could not be completed due to inadequate resources.
Increase the region size and restart Debug Tool.
For COBOL, the CUs must be compiled with VS COBOL II Version 1 Release 3 and the TEST compiler or FDUMP option, or AD/Cycle® COBOL and the compile-time TEST option.
The variable might be CONTROLLED or AUTOMATIC and does not yet exist.
The wrong number of subscripts were specified with the variable reference.
The subscripts with the variable reference do not properly relate to the variable’s characteristics.
A pointer cannot be used unless the variable is BASED.
Use additional qualification to get to the desired variable.
Only variables whose data type is POINTER or OFFSET can be used to locator with other variables.
A subscripted variable could not be found. Its name, however, is also that of a PL/I built-in function. If the built-in function was intended, the wrong number of arguments were present. It can be also STORAGE alteration function. If that command was intended, then invalid syntax was present.
A subscripted variable could not be found. Its name, however, is also that of a PL/I built-in function. If the built-in function was intended, more arguments must be present.
A variable could not be found. Its name, however, is also that of a PL/I built-in function. If the built-in function was intended, it is not in the correct context. Note that in Debug Tool, pseudo-variables cannot be the target of assignments.
The variable that is being as a locator is not the correct data type.
Names of structure elements can be ambiguous if not fully qualified. For example, in DCL 1 A, 2 B, 3 Z POINTER, 2 C, 3 Z POINTER, the names Z and A.Z are ambiguous.
Retry the command with enough qualification so that the name is unambiguous.
Given DCL 1 A, 2 B FIXED, 2 C FLOAT, the name A refers to a structure.
Break the command into commands for each of the basic elements of the structure, or use the DECLARE command with a BASED variable to define a variable overlaying the structure.
Given DCL A(2) FIXED BIN(15) and DCL B(2) FIXED BIN(15), references to A(B), A(B+2), and so on are invalid.
Use a scalar as the index.
In %GENERATION(x,y) and %RECURSION(x,y), y must be positive.
In %GENERATION(x,y) and %RECURSION(x,y), y must be a scalar.
In %RECURSION(x,y), x must be a parameter or an automatic variable.
In %RECURSION(x,y), y must be no greater than the number of recursions of the block where x is declared.
In %GENERATION(x,y), x must be controlled.
In %GENERATION(x,y), y must be no greater than the number of allocations of the variable x.
In %GENERATION(x,y), y must be no greater than the number of allocations of the variable x.
PL/I does not allow FETCHed procedures to contain CONTROLLED variable types.
Correct the program.
The variable belongs to the class of variables, such as members of structures with REFER statements, which Debug Tool does not support.
The expression in the QUIT command cannot be an array, a structure or other data aggregate, and if it is a scalar, it must have a type that can be converted to integer.
This message applies to C. An internal error occurred in the C run time and the command is terminated.
This message applies to the C unary operator ! (logical negation).
This message applies to the C unary operators ++ and --.
This message applies to the C unary operator ~ (bitwise complement).
This message applies to the C unary operators + and -. These operators cannot be applied to pointers to void-function designators, or pointers to functions.
This message applies to the C unary operator + and -.
This message applies to C function calls.
This message applies to C function calls.
This message applies to the C binary operators && (logical and) and || (logical or).
This message applies to the C type casts.
This message applies to the C type casts.
This message applies to C type casts. In the example 'float f;', the type cast '(float *) f' is invalid.
Invalid operand for the type cast operator.
This message applies to C type casts.
This message applies to C function calls.
This message applies to C function calls.
This message applies to the C subscript operator. The subscript operator cannot be applied to pointers to void, function designators or pointers to functions.
This message applies to the C subscript operator.
This message applies to the C unary operator sizeof.
This message applies to the C operators (select member) and -> (point at member).
This message applies to the C operator -> (point at member).
This message applies to the C indirection operator.
This message applies to the C subscript operator (select member).
This message applies to the C relational operators. For example, <, >, <=, >=, and ==.
This message applies to the C binary operator -. The difference between two pointers to void or two pointers to functions is undefined because sizeof is not defined for void types and function designators.
This message applies to C assignments, for example, +=, -=, and *=.
This applies to the test expression in a C switch command.
This message applies to the C binary operator +.
This message applies to the C unary operator & (address).
This message applies to C constants.
This message applies to C function calls. The argument must have a type that would be valid in an assignment to the parameter.
This message applies to the C binary operator % (remainder), << (bitwise left shift), >> (bitwise right shift), & (bitwise and), ??¬' (bitwise exclusive or), |(bitwise inclusive or), and the corresponding assignment operators (for example, %=, and <<=).
This message applies to the C binary assignment operators.
This message applies to the C binary operators * and /.
This message applies to C. You attempted to assign a value to enum, but the value is not legitimate for that enum.
This message applies to the C binary operators << (bitwise left shift) and >> (bitwise right shift). Shift values must be nonnegative and less than 33. These tests are made only when WARNING is on.
This message applies to the C subscripts.
This message applies to the C subscripts.
Divide by zero is detected by C run time.
This message applies to C. Use the LIST NAMES command to list all known variables.
This message applies to C. Use the LIST NAMES command to list all known variables.
This message applies to C function calls and can occur,for example, when a function’s linkage is specified as CEE, but the function was compiled with linkage OS.
This message applies to C. The message is issued, for example, in response to the command DESCRIBE ATTRIBUTE typedef x, if x is not a typedef identifier.
This message applies to C.
This message applies to C declarations.
This message applies to C function calls.
This message applies to C function calls.
This message applies to C function calls.
This message applies to C tag names.
This message applies to C names.
This message applies to C. In the example 'void' funcname (...), the command LIST TITLED (funcname()) is invalid.
This message applies to C. In %RECURSION(x,y), the second expression, y, must have arithmetic type.
This message applies to C. In %RECURSION(x,y), the second expression, y, must be positive.
This message applies to C. In %RECURSION(x,y), the first expression, x, must be a parameter or an automatic variable.
This message applies to C. In %INSTANCE(x,y), the first expression, x, must be a parameter or an automatic variable.
This message applies to C. In %RECURSION(x,y), the recursion number, y, exceeds the number of generations of x that are currently active.
This message applies to C declarations.
This message applies to C declarations.
This message applies to C.
This message applies to C.
This message applies to CALL %DUMP for C.
This message applies to C constants.
This message applies to C constants.
This message applies to C constants.
This message applies to C constants.
This message applies to C constants.
This message applies to C constants.
This message applies to C constants.
You can STEP and try the command again.
This message applies to PL/I constants.
Other relationships between program control data are not defined.
Check to see if a variable was misspelled.
ENTRY vs ENTRY, LABEL vs LABEL, etc. are okay. LABEL vs ENTRY is not.
Equivalency between AREA variables is not defined.
This is not supported.
Check to see if the variable name was misspelled. If this was not the problem, you must find other logic to perform the task.
Equal and not equal are defined for complex variables, but you have attempted to relate them in some other way.
You are not allowed to concatenate GRAPHIC (DBCS) strings to anything other than other GRAPHIC (DBCS) strings.
Equivalency between the GRAPHIC data type and other data types has not been defined.
You are trying to convert something to a character format when such a relationship has not been defined.
You are trying to convert something to a bit format when such a relationship has not been defined.
You are trying to convert something to a numeric format when such a relationship has not been defined.
This message applies to PL/I constants.
The specified conversion probably contained characters that were something other than '0' or '1'. Since the conversion to BIT could therefore not be done, this message is displayed rather than raising the CONVERSION condition.
The variable named has been declared as VARYING with length n, but its current length is greater than n. The variable might be uninitialized or might have been written over.
The variable named has been declared as VARYING with length n, but its current length is less than 0. The variable might be uninitialized or it might have been written over.
A variable contains bad decimal data if its usage would cause a data exception to occur (that is, its numeric digits are not 0-9 or its sign indicator is invalid), or it has even precision but its leftmost digit is nonzero. LIST STORAGE can be used to find the contents of the variable, and an assignment statement can be used to correct them.
Negative sizes are not understood and, therefore, are not processed.
Performing the operation would alter storage that is outside of the AREA. Such an operation is not within PL/I, so will be avoided.
For example, a FIXED BIN(5,0) variable can have only 5 significant digits thus limiting its valid range of values to -32 through 31 inclusive.
This message applies to PL/I constants.
This message applies to PL/I constants.
Array elements of an expression ( such as A + B or A = B ) must all have the same number of dimensions and the same lower and upper bounds for each dimension.
The PL/I language does not define how a scalar would represent an array; the assignment is rejected as an error.
This message applies to PLI constants.
The second expression of the named built-in function is dependent upon the dimensions of the array (the first built-in function argument).
Correct the relationship between the first and second arguments.
Debug Tool does not support aggregates in this context.
The named built-in function expects an array to be the first argument.
You used something other than a variable name (for example, a constant) in your invocation of the named built-in function.
You must use a variable of the correct data type with the STRING built-in function.
The first argument to POINTER was determined to be something other than an OFFSET data type.
The second argument to POINTER was determined to be something other than an AREA data type.
The first argument to OFFSET was determined to be something other than a POINTER data type.
The second argument to OFFSET was determined to be something other than an AREA data type.
The name built-in function requires the name of a FILE to operate. Some other data type was used as the argument.
You must name an open STREAM file in the COUNT built-in function.
You must name an open PRINT file in the LINENO built-in function.
You must name a RECORD file in the SAMEKEY built-in function. This requirement is tested for all file constants, but is tested for file variables only if the file variable is associated with an open file.
The built-in function is expecting a variable but a constant or some other invalid item appeared as one of the arguments.
This message applies to PL/I constants.
GRAPHIC(x,y) is illegal if y > 16383, and GRAPHIC(x) is illegal if length(CHAR(X)) > 16383.
The specified built-in function would fail if a negative argument was passed. Use of the built-in function will be avoided.
The specified built-in function would fail if a negative argument was passed. Use of the built-in function will be avoided.
The specified built-in function would fail if a negative argument was passed. Use of the built-in function will be avoided.
CHAR(x) is illegal if x is GRAPHIC with length 16383 since the resultant string would require 32768 characters.
This applies to the PL/I CURRENTSTORAGE and STORAGE built-in functions.
This applies to the PL/I CURRENTSTORAGE and STORAGE built-in functions.
This applies to the PL/I ASIN and ACOS built-in functions.
This applies to the PL/I ATANH built-in function.
This applies to the PL/I ATAN built-in function.
This message applies to PL/I constants.
This applies to the PL/I SQRT built-in function.
This applies to the PL/I ATAN and ATAND built-in functions.
This applies to PL/I constants.
This applies to the PL/I trigonometric built-in functions. For short floating-point arguments, the limits are:
For long floating-point arguments, the limits are:
For extended floating-point arguments, the limits are:
You are trying to get a substring from something other than a string.
This message applies to PL/I constants.
The arguments that accompany a pseudovariable are incorrect.
This will occur in UNSPEC(A) where A is CHARACTER(n) and n > 4095, where A is CHARACTER(n) VARYING and n > 4093, where A is AREA(n) and n > 4080, etc.
This message applies to PL/I constants.
This message applies to PL/I constants.
This applies to PL/I constants.
GRAPHIC (DBCS) strings are prohibited as arguments to the MPSTR built-in function.
You must name a variable that is ALLOCATEable.
The variable by that name cannot be a controlled variable within the current context. If the variable exists somewhere else (and is a controlled variable), you should use qualification with the variable name.
The argument to the POINTER built-in function is invalid. The argument to the POINTER built-in function should be an OFFSET data type for the first argument, or an AREA data type for the second argument.
Given dDCL 1 A, 2 B FIXED, 2 C FLOAT, the name A refers to a structure.
Break the command into commands for each of the basic elements of the structure, or use the DECLARE command with a BASED variable to define a variable overlaying the structure.
This applies to the POINTERADD built-in function. The first argument must have pointer type, and it must be possible to convert the other to FIXED BIN(31,0).
This message applies to various built-in functions. By built-in function, the datatypes required are:
See the Language Reference built-in function chapter for the description of when STRINGRANGE is raised. See the Language Reference condition chapter for the values of the revised SUBSTR reference.
This message applies to various pseudovariables. By pseudovariable, the datatypes required are:
This applies to the PL/I ACOS, ASIN, ATAND, COSD, ERF, ERFC, LOG2, LOG10, SIND and TAND built-in functions. This applies to PL/I constants.
An attempt was made to modify storage during PLAYBACK replay mode when DATA was in effect. Only session variables can be modified in this situation.
An error has occurred during expression evaluation. See the Debug Tool Command Log for more detailed information.
AT stmt1-stmt2 is valid only if stmt1 and stmt2 are in the same block.
You just issued a CLEAR/LIST command against a breakpoint that does not exist.
Verify that you referred to the breakpoint using the same syntax that was used to establish it. Perhaps a CLEAR command occurred since the command that established the breakpoint.
The program has not been prepared properly so AT commands are rejected for all statements in the program.
Make sure the program has been prepared properly by checking Part 2. Preparing your program for debugging and Appendix F. Syntax of the TEST Compiler option in the Debug Tool User’s Guide. Also, the LIST LINE NUMBERS command can be used to list all statement or line numbers that are valid locations for an AT LINE or AT STATEMENT breakpoint.
A command (for example, AT ENTRY) specified a C file name where a function or compound statement was expected.
A compile unit must have been compiled with TEST(BLOCK), TEST(PATH) or TEST(ALL) for hooks to be present at block exits and block entries.
A compilation unit must have been compiled with TEST(PATH) or TEST(ALL) for hooks to be present at labels.
%STATEMENT and %LINE are invalid in AT commands at block entry and block exit, and in AT and LIST STATEMENT commands at locations that are outside of the program.
The command CLEAR/LIST AT was entered but there are no AT breakpoints presently set, or the command CLEAR/LIST AT class was entered but there are no AT breakpoints presently set in that class.
The command CLEAR/LIST AT was entered but there are no enabled AT breakpoints presently set in the requested class of breakpoints.
The command CLEAR/LIST AT was entered but there are no disabled AT breakpoints presently set in the requested class of breakpoints.
You issued a specific LIST AT ENABLED command against a breakpoint that is not enabled.
You issued a specific LIST AT DISABLED command against a breakpoint that is not disabled.
You cannot TRIGGER a disabled breakpoint.
No disabled breakpoints are currently set.
No enabled breakpoints are currently set.
You cannot ENABLE an enabled breakpoint.
You cannot DISABLE a disabled breakpoint.
For some reason, when Debug Tool tried to set this breakpoint, an error occurred. This breakpoint cannot be set.
In an every_clause specified with a breakpoint command, if the TO value was specified, the FROM or EVERY value must be less than or equal to the TO value.
GO/RUN BYPASS is valid only when Debug Tool is entered for an AT CALL, AT GLOBAL CALL, or AT OCCURRENCE breakpoint.
The following AT OCCURRENCE conditions must have a qualifying reference: CONDITION, ENDFILE, KEY, NAME, PENDING, RECORD, TRANSMIT and UNDEFINEDFILE. This would also apply to the corresponding TRIGGER commands.
The following AT OCCURRENCE conditions must have a valid qualifying reference: CONDITION, ENDFILE, KEY, NAME, PENDING, RECORD, TRANSMIT and UNDEFINEDFILE. This would also apply to the corresponding TRIGGER commands.
Debug Tool was attempting to restore a breakpoint that had been set in the previous process and has failed in that attempt. There are two reasons this could have happened. If the Compile Unit (CU) has been changed (that is, modified and recompiled/linked) between one process and the next or a breakpoint had been established for a statement or variable that no longer exists due to the change, when Debug Tool attempts to reestablish that breakpoint, it will fail with this message.
Debug Tool was attempting to disable a breakpoint for a CU that has been deleted from storage (or deactivated), and failed in that attempt.
You are trying to use a GOTO or JUMPTO command with a variable name that cannot be associated with a label in the program.
You are trying to make use of a LABEL variable, but the control block representing that variable contains improper information (for example, an address that is zero).
You are trying to make use of a FILE variable, but the control block representing that variable contains improper information (for example, an address that is zero).
A command requires determining which statement was associated with a particular storage address. A statement table could not be located to relate storage to statement identifications.
Check to see if the program had been compiled using release name. If so, was the statement table suppressed?
You cannot establish an AT ALLOCATE breakpoint for a variable that cannot be allocated.
Debug Tool cannot, at this time, correlate a block to the named variable. As a result, a breakpoint cannot be established.
Establish the breakpoint via an AT ENTRY ... AT ALLOCATE ....
ON/SIGNAL file-condition (variable) is invalid because the variable is not a PL/I FILE variable.
ON/SIGNAL CONDITION (variable) is invalid because the variable is not a PL/I CONDITION variable.
A compile unit must have been compiled with the DATEPROC option and either TEST(STMT) or TEST(ALL) for hooks to be present at statements affected by the Millennium Language Extensions.
A compile unit must have been compiled with TEST(STMT) or TEST(ALL) or set DYNDEBUG ON for at statements.
The command is not supported for a DISASSEMBLY compile unit. Only the AT OFFSET form of the AT command is supported for a DISASSEMBLY compile unit.
The command or option is not supported for a DISASSEMBLY compile unit. See the Debug Tool Reference and Messages document for information about the restrictions on the use of this command.
The command is not supported for a DISASSEMBLY compile unit. See the Debug Tool Reference and Messages document for information about the restrictions on the use of this command.
The expression cannot be evaluated during Playback replay, because the indicated variable is not available during replay.
When the STORAGE runtime option is in effect, breakpoints are not allowed on the prologue instructions between the first BALR R14,R15 and the next LR R13,Rx. You may set a breakpoint on an instruction following the next LR R13,Rx or you may rerun your program without the STORAGE runtime option and set a breakpoint on the specified statement.
The current programming language does not support the DESCRIBE ENVIRONMENT command.
The command is not supported for a ENTERPRISE PLI.
Breakpoints in assembler compile units are not restored.
The command is not supported for a Compile Unit compiled with a High Level Language compiler with the NOTEST option since the compile unit does not have the hook necessary to set the breakpoint.
The command, command_name, is not supported in programs that are compiled with Enterprise PL/I.
The expression has a hex value that exceeds the maximum length limit required to be displayable.
The conditional expression is not valid. Make sure the variable is known in current compile unit or that the attributes are compatible.
The conditional expression is not valid. Make sure the variable is known in current compile unit or that the attributes are compatible.
You have attempted to evaluate a variable in an implicitly created CU. Storage has not yet been allocated for this variable.
This message contains the output from the DESCRIBE LOADMODS command.
This is issued in response to a CALL, CLEAR or QUERY command when the target session procedure cannot be located. It cannot be located for one of two reasons: it was not defined or it was imbedded with another session procedure.
%DUMP does not accept more than two parameters.
In PL/I, the %DUMP arguments must be scalar data that can be converted to character. In C, the %DUMP arguments must be pointers to character or arrays of character.
Parameters are not supported with the CALL procedure command.
This message is from the feedback code of Language Environment CEE3DMP call.
The dump option allows a maximum of 255 characters. The dump title allows a maximum of 80 characters.
The CALL command was terminated unsuccessfully.
This message is used as a header for the call %FA.
The Computer Sciences Corporation's KORE-HOGAN product is not installed.
The CALL %HOGAN command is only valid in a CICS environment with Computer Sciences Corporation's KORE-HOGAN installed.
The function that you requested has been rejected by a security manager.
An error occurred in locating the program needed to perform the function you requested.
The function that you requested is not supported when Debug Tool is running in Dual Terminal mode.
The indicated load module was specified as an operand of the DESCRIBE LOADMODS command but is not an active load module.
The requested breakpoint was successfully performed on a suspended breakpoint.
A command (for example, CLEAR VARIABLES) requires the use of a variable, but the specified variable was not declared (or was previously cleared).
For a list of session variables that can be referenced in the current programming language, use the LIST NAMES TEST command.
A variable can require no more than 2**24 - 1 bytes in a non-XA machine and no more than 2**31 - 1 bytes in an XA machine.
A session variable is declared with invalid or unsupported attribute.
The CLEAR VARIABLES command is entered but there is no declaration for session variables.
This message applies to C. It is issued, for example, after DESCRIBE ATTRIBUTES enum x if x is not an enum tag.
This message applies to C. A tagged enum, struct, or union type cannot be redefined, unless all variables and type definitions referring to that type and then the type itself are first cleared. For example, given
enum colors {red,yellow,blue} primary, * ptrPrimary;enum colors cannot be redefined unless primary, ptrPrimary, and then enum colors are first cleared.
This message applies to C. A CLEAR DECLARE of a tagged enum, struct, or union type is invalid while one or more declarations refer to that type. For example, given
enum colors {red,yellow,blue} primary, * ptrPrimary;CLEAR DECLARE enum colors is invalid until CLEAR DECLARE (primary, ptrPrimary) is issued.
This message applies to C. For example, given
int blue;
The use of the name blue in the following declaration is invalid:
enum teamColors {blue,gold};This message applies to C. A struct or union type must not contain itself as a member. For example, the following declaration is invalid:
struct record {
int member;
struct record next;
}Unable to process the declaration. The command is terminated unsuccessfully.
An attempt was made to restore breakpoints and/or monitor settings from the specified data set. However, the specified data set contained invalid data so some or all of the breakpoints and/or monitor settings could not be restored from the specified data set.
The EQALANGX file containing the listing and the debugging tables cannot be found. Some of the possible conditions that could cause this are: The debug file does not exist under the default DSName, or the user does not have authorization to access the debug file.
Error in setting DBCS ON when the debug session terminal is not DBCS capable.
This is output generated by internal Debug Tool trace for problem determination purposes only.
An attempt was made to read the specified data set in order to determine if settings should be automatically restored or to restore the breakpoints and/or monitor settings. However, the member did not exist, the data set could not be read, or the data set contained invalid data. This might result from data having never been saved in this data set.
An attempt was made to automatically restore settings from the specified data set. However, the SETTINGS NOAUTO option was in effect when the set data was saved and, therefore, the set data will not be restored.
The specified data was successfully restored from the specified data set.
An attempt was made to save the indicated data in the specified data set. However, the data set does not exist. Allocate and catalog the data set and retry the operation.
The indicated data was successfully saved to the specified data set with the indicated restore options.
An attempt was made to open the specified data set in order to determine if settings should be automatically restored or to save the current settings. However, the data set could be allocated but could not be opened. This may be the result of not having RACF® access to the data set, of having a member name specified that did not exist, or any other problem that could cause a System 013 Abend.
An attempt was made to allocate the specified data set in order to determine if settings should be automatically restored or to save the current settings. However, the data set could not be allocated because it was already allocated to another user.
Unable to evaluate the expression. The command is terminated unsuccessfully.
A bad program name is specified in a CALL command and processing is terminated unsuccessfully.
This message applies to COBOL. The operands to be compared are of incompatible types.
This message applies to C. There are too many nested levels of switch commands.
This message applies to C. The switch command is terminated because an error occurred during processing.
This message applies to COBOL. The operands to be compared are incompatible. For example, the following comparison is invalid:
EVALUATE TRUE
When 6 List ('invalid');
when other List ('other');
END-EVALUATEA debug data file is not found for the supplied CSECT name.
Breakpoints and monitors cannot be saved or restored when an OPEN exit is active because MVS does not support using dynamic allocation in this situation.
The specified data set must be a partitioned data set.
The specified data set could not be located.
The specified data set could not be allocated. The return code and reason code are shown as ddd-xxxxyyyy. In most cases, xxxx is the S99Error code from dynamic allocation. You can use this code to determine more information about the source of the error. For more information about the S99Error codes, see z/OS MVS Programming: Authorized Assembler Services Guide. You should also inspect the MVS console log for other messages associated with this error.
You are trying to GOTO a block that is not active. If it is inactive it doesn't have a register save area, base registers, and so on (all of the mechanics established that would allow the procedure to run).
No offset associated with the label was found; the code associated with the label might have been removed by optimization.
The label is not known.
The label is ambiguous; multiple labels of this name exist.
The GOTO command is not recommended. For COBOL, this might be due to optimization, or because register contents other than the code base cannot be guaranteed for the target.
The GOTO command is not recommended. For COBOL, this might be due to optimization, or because register contents other than the code base cannot be guaranteed for the target.
There are various reasons why a GOTO command can be unsuccessful; this message covers all the other situations not covered by the other message in the GOTO LABEL messages group.
The target statement number in a GOTO command must belong to an active procedure.
You are trying to JUMPTO a block that is not active. If it is inactive it doesn't have a register save area, base registers, and so on -- all of the mechanics established that would permit the procedure to execute.
You are trying to JUMPTO a variable name that can not be associated with a label in the program.
The JUMPTO command is not recommended. For COBOL, this may be due to optimization, or because register contents other than the code base cannot be guaranteed for the target.
The JUMPTO command is not recommended. For COBOL, this may be due to optimization, or because register contents other than the code base cannot be guaranteed for the target.
There are various reasons why a JUMPTO command may not be successful; this message covers all the other situations not covered by the other message in the JUMPTO LABEL messages group.
The target statement number in a JUMPTO command must belong to an active procedure.
When the deferred LDD for the specified CU is executed, the EQALANGX data will be loaded from the specified data set.
Debug Tool has not yet encountered any of the situations that cause entries to be put into the HISTORY table; so it is empty.
LIST STATEMENTS or LIST LAST n STATEMENTS was entered, but there are no STATEMENT entries in the HISTORY table. Debug Tool was not invoked for any STATEMENT hooks.
LIST PATH or LIST LAST n PATH was entered, but there are no PATH entries in the HISTORY table. Debug Tool was not invoked for any PATH hooks.
You are trying to work with a register but none exist in this context (for example, during environment initialization).
The LIST CALLS command was issued before any STEP or GO.
A pattern is invalid if it is longer than 128 bytes or has more than 16 parts. (Each asterisk and each name fragment forms a part.)
LIST STORAGE(built-in function(...)) is invalid if the built-in function is not the ADDR or POINTER built-in function.
The contents of these program control variables can be displayed by using the HEX or UNSPEC built-in functions or by using the LIST STORAGE command.
The block is not currently active for LIST TITLED
Issue LIST TITLED or LIST TITLED * from within the block.
The symbols including variables or other data may not have been allocated at this location, you may STEP and issue the command again.
The command entered could not be parsed because the specified element is invalid.
The command entered could not be parsed because the specified element is ambiguous.
COBOL identifiers cannot end in a hyphen.
The command, as it was entered, requires additional command elements (for example, keywords, variable names). Refer to the definition of the command and verify that all required elements of the command are present.
A /* ... was entered but an */ was not present to close the comment. The command is discarded.
You must either add an */ to the end of the comment or explicitly indicate continuation with an SBCS hyphen.
The start of a constant was entered (a quotation mark started the constant) but another quotation mark was not found to terminate the constant before the end of the command was reached.
There could be several solutions for this, among them:
In COBOL, an E in a float constant must be followed by at least one decimal digit (optionally preceded by a sign). In C, if a + or - sign is specified after an E in a float constant, it must followed by at least one decimal digit.
An unmatched or nested shift code was found.
All identifiers must be contained in 255 bytes or less. COBOL identifiers must be contained in 30 bytes or less and C identifiers in 255 bytes or less.
A character code point was encountered that was not within the defined code values for the first or second byte of a DBCS character.
An error was detected while parsing a command within a USE file, or within a file specified on the run-time TEST option. It occurred at the record number that was displayed.
A hexadecimal digit must follow 0x.
Only an octal digit can follow a digit-0.
All COBOL DBCS names must have at least one double byte character not defined as double byte alphanumeric. For EBCDIC, these are characters with X'42' in the leading byte, with the trailing byte in the range X'41' to X'FE'. For ASCII, the leading byte is X'82' and the trailing byte is in the range X'40' to X'7E'.
Alphanumeric double-byte characters have a leading byte of X'42' in EBCDIC and X'82' in ASCII. The trailing byte is an alphanumeric character. The valid COBOL subset of these is A-Z, a-z, 0-9.
COBOL DBCS names cannot have a leading or trailing DBCS hyphen.
Continuation rules do not apply to DBCS names, DBCS literals or mixed SBCS/DBCS literals. These items must appear on a single line.
An end of line was encountered before finding a closing shift-in control code. This message is for the System/370 environment.
A shift-out shift-in pair of control characters were found with no intervening DBCS characters. This message is for the System/370 environment.
No closing Shift-In control code was found before end of file. This message is for the System/370 environment.
No closing quotation mark
A fixed binary constant must be between -2**31 and 2**31 exclusive.
A fixed decimal constant must be between -10**20 and 10**20 exclusive.
This limit applies to all PL/I FLOAT BINARY constants.
This limit applies to all PL/I FLOAT DECIMAL constants.
This limit applies to all C float constants and to all PL/I FLOAT BINARY constants.
This limit applies to all PL/I FLOAT DECIMAL constants.
This limit applies to all PL/I FLOAT BINARY constants.
This limit applies to all PL/I FLOAT DECIMAL constants.
This limit applies to all C float constants.
This is the range of values allowed by C.
The LOAD MODULE request failed, the module was not found.
The LOAD MODULE request failed, there is not enough storage.
The LOAD MODULE request was unsuccessful.
The DELETE MODULE request was unsuccessful.
Only modules loaded by the Debug Tool may be deleted.
The LOAD MODULE request was unsuccessful.
IDISNAP is a part of the product Fault Analyzer. Verify Fault Analyzer is installed properly.
Verify IDISNAP routine is available in the enviroment.
%FA was complete.
%FA was complete. See your Fault Analyzer history file.
You cannot issue a LOAD request until Debug Tool initialization is complete.
An implicit LOAD command was issued for the specified load module as the result of a QUALIFY LOAD or QUALIFY CU command for a load module that was not currently loaded. A corresponding CLEAR LOAD will be issued when execution is resumed.
An implicit CLEAR LOAD command was issued for the specified load module. This module was previously loaded as the result of a QUALIFY LOAD or QUALIFY CU command for a load module that was not currently loaded.
A LOAD command was used in a non-Language Environment environment to load a load module that contained one or more Language Environment compile units or an attempt was made to QUALIFY to an Language Environment compile unit in a previously loaded load module. These compile units cannot be created until Language Environment is active. Compile units will be created only for non-Language Environment compile units.
An implicit CU was created for the specified CU in the specified load module as the result of a QUALIFY CU command for a load module that was already loaded and a COBOL CU that had not yet been executed. The CU will be destroyed when execution is resumed.
The specified implicitly created CU is being destroyed. This module was previously created as the result of a QUALIFY CU command for a CU that had not already been created.
The attempt to destroy the specified CU was unsuccessful.
An error during the initial processing (OPEN) of the file occurred.
An error occurred performing an input or output operation.
This command is one of a collection that is allowed only when your terminal is operating in full-screen mode. The function is not supported in line mode or in a batch mode.
This message is issued when not enough storage is available to process the last command issued or to handle the last invocation.
Increase size of virtual storage.
This could be caused by a bad file name specified with the call dump FNAME option.
A command, such as LIST, LIST TITLED, LIST STORAGE, or DESCRIBE ATTRIBUTES, which takes input from the source window was entered with the cursor in the source window, but the cursor was not positioned at a variable name.
Reposition the cursor and reenter.
Under MVS, data definition names are limited to 8 characters and data set names are limited to 44 characters. If a partitioned data set is named, the member name must be specified (with up to 8 characters, enclosed in parentheses).
The user attempted to issue a GOS/RUN or STEP request when the program was waiting for input. The input must be entered to resume execution.
The user attempted to enter the INPUT command when the program was not waiting for any input.
The logical record length is less than 32 bytes or greater than 256 bytes.
The user attempted to open a new log file and the old one could not be closed; the new log file is used, however.
An error occurred during processing of the list lines command. Possible return codes:
If the Preferences File TEST option is not specified, the default is INSPPREF. The user did not specify the Preferences File TEST option, so Debug Tool assumes INSPPREF and tries to open it. If INSPPREF is not allocated, this open fails.
Start of commands in the global preferences file.
Start of commands in the user preferences file.
Start of commands in the commands file.
End of commands in the global preferences file.
End of commands in the user preferences file.
End of commands in the commands file.
The global preferences file is opened successfully.
The previously-executing command was terminated because of an attention request. Normal debugging can continue.
The attention key was pressed three times because the application was looping either in system code or application code without debugging hooks. Only the GO/RUN and QUIT commands are valid at this point.
The STEP and GO/RUN commands are not allowed after the application program ends.
The environment is in a position that it would not be meaningful to trigger a condition. For example, you have control during environment initialization.
A condition name was expected, but the name entered is not the name of a known condition.
For some reason, when Debug Tool tried to trigger the specified condition, it failed and the condition was not signaled.
There is another block that has the same name as this block.
Provide further block name qualification: by load module name, by compile unit name, or by additional block names if a nested block.
While you can QUALIFY to any block, you cannot QUALIFY UP (for example, change the qualification to the block’s parent) unless there really is a parent of that block. In this case, there is no parent of the currently-qualified block.
You have either misinterpreted your current execution environment or you have to qualify to some block explicitly.
While you can QUALIFY to any block you cannot QUALIFY RETURN (for example, change the qualification to the block’s invoker) unless there really is an invoker of that block. In this case, there is no invoker of the currently-qualified block.
You have either misinterpreted your current run-time environment or you have to qualify to some block explicitly.
The block that you named could not be located by Debug Tool.
Provide further block name qualification: by load module name, by compile unit name, or by additional block name(s) if a nested block.
The qualification you are using (or the spelling of the block names) prevented Debug Tool from locating the target block.
Verify that the named block should be within the current qualification.
The compilation unit (program) that you named could not be located by Debug Tool.
The statement number does not exist or cannot be used. Note that the statement number could exist but is unknown.
Load module qualification is referring to a load module that cannot be located.
The load module might be missing or it might have been loaded before Debug Tool was first used. On the System/370, Debug Tool is aware of additional load modules only if they were FETCHed after Debug Tool got control for the first time.
The compilation unit might be misspelled or missing.
The compilation unit you named is not unique.
Add further qualification so that the correct load module will be known.
There is another block that has the same name as this block.
Provide further block name qualification: by load module name, by compile unit name, or by additional block names if a nested block.
The current location is unknown; as such, the reference or statement must be explicitly qualified.
Either explicitly set the qualification using the SET QUALIFY command or supply the desired qualification to the command in question.
The compilation unit (program) that you named could not be located in the current enclave by Debug Tool.
The compilation unit might be misspelled or missing, or it might be outside of the current enclave.
The block or CU that you named could not be located by Debug Tool.
Provide further block name qualification--by load module name, by compile unit name, or by additional block names(s) if a nested block.
Debug Tool does not have accurate information about the program, and thus cannot provide reliable results.
Recompile the program with one of the following or later versions of the COBOL compiler:
Results are unreliable, because the program might use the previous value that was saved in temporary storage or a register.
You can SET WARNING OFF to allow the update to take place or recompile the program without optimization.
The program was compiled with the OPTIMIZE(FULL) option, and the compiler discarded the data item because it was not referenced in the program.
Results might be unreliable because the program might use the previous value that was saved in temporary storage or a register.
Recompile the program without the Optimize option.
The compilation unit (program) that you specified could not be located by the Debug Tool. The breakpoint is deferred until this CU is entered.
The CU name (Program) must be added to the block name to allow Debug Tool to locate the block named.
Assembler CU names longer than 8 characters are not currently supported.
You are trying to clear an element of a structure. You must clear the entire structure by naming its level-one identifier.
This applies to the PL/I ATANH built-in function.
This applies to the PL/I LOG built-in function.
This applies to the PL/I LOG, LOG2 and LOG10 built-in functions.
This applies to the PL/I ATAN and ATAND built-in functions.
The current statement has no variables.
The command could not be completed due to inadequate resources. The variable is too big.
The file created by the FORMAT(DWARF) suboption of the DEBUG compiler option that contains the debugging tables cannot be found. Some of the possible conditions that could cause this are:
An EQALANGX file containing the assembler debugging information does not match the object. Either the CSECT length is different, selected object code is different, or the EQALANGX file is not for the correct language.
A MONITOR n command was issued when the MONITOR table is empty, but n is greater than 1.
A MONITOR n command was issued but n is greater than 1 plus the highest numbered MONITOR command.
A MONITOR command was issued but the MONITOR table is full.
A LIST MONITOR n or CLEAR MONITOR n command was issued, but n is greater than the highest numbered MONITOR command.
A CLEAR MONITOR n command was issued, but MONITOR has already been cleared.
A LIST MONITOR or CLEAR MONITOR command was issued, but there are no MONITOR commands established.
A FIND command must include a string to find when no previous FIND command has been issued.
A FIND attempt failed to find the requested string.
A SYSTEM command was issued. The underlying operating system received it but did not process it successfully.
The underlying operating system was passed a command that was not recognized. The system could not process the command.
The specified variable has an error in its definition or length and address information is not currently available in the execution of the program.
The Automonitor can only be set off with the SET AUTOMONITOR OFF command.
The Automonitor function is already off.
The given command is not supported on the current platform.
The source or listing information is not available. Some of the possible conditions that could cause this are: The listing file could not be found, the CU was not compiled with the correct compile options, inadequate resources were available.
When using CICS this condition could occur because one of more of the following TDQueues are not defined:
The assignment contains incompatible data types; the assignment cannot be made.
The operation, if performed, would result in the AREA condition. The condition is being avoided by rejecting the operation.
You are trying to get apply the PL/I IMAG or REAL pseudovariable to a variable that is not complex numeric.
The program environment is such that a GOTO cannot be performed correctly. For example, you could be in control during environment initialization and base registers (supporting the GOTO logic) have not been established yet.
There are several statement types that are not allowable as the target of a GOTO or JUMPTO command. FORMAT statements are one of them.
The national-language-specified conflicts with the supported national languages for this installation of Debug Tool. Verify that the Language Environment run-time NATLANG option is correct.
For PL/I, the value of the return code must be nonnegative and less than 1000.
LABEL variables cannot be the object of the AT command.
Shorten the search argument to a string length 64 or less.
Supply a search argument inside the quotation marks.
The Debug File containing the listing and the debugging tables can not be found. Some of the possible conditions that could cause this are: The Debug File was deleted from the system, or the user does not have authorization to access the debug file.
A Debug File containing the listing and the debugging tables has already being validated.
A Debug File containing the listing and the debugging tables does not match the creation date of the object.
A Debug File containing the listing and the debugging tables does not match the creation date of the object, and the data it contains is not valid.
The Debug File was nowhere to be found.
I/O errors when trying to open/read Debug File.
A conversation allocation request failed due to invalid conversation characteristics obtained from the APPC/MVS side information file. There could be several reasons for this:
Contact your APPC/MVS system administrator to modify the characteristics associated with the given symbolic_destination_name in the side information file. For information about the recommended values for mode_name and TP_name, see the CODE/370 Installation manual. The OS/2 system error log can contain valuable diagnostic information. To access the system error log, select System Error Log from the FFST/2™ folder or type SYSLOG at the OS/2 command line.
The conversation cannot be allocated because of a condition that is not temporary. There could be several reasons for this:
Ensure that you specified the correct symbolic_destination_name or contact your APPC/MVS system administrator to correct the condition. The OS/2 system error log can contain valuable diagnostic information. To access the system error log, select System Error Log from the FFST/2 folder or type SYSLOG at the OS/2 command line.
The conversation cannot be allocated because of a condition that might be temporary. There could be several reasons for this:
Verify that mode_name is defined on the target workstation using the CM/2 Communication Manager Setup panels. If mode_name is defined on the workstation, contact your MVS/ESA system programmer to ensure that mode_name is also defined on the MVS system. The OS/2 system error log can contain valuable diagnostic information. To access the system error log, select System Error Log from the FFST/2 folder or type SYSLOG at the OS/2 command line.
Partner_LU_name rejected the allocation request because the host program specified a workstation program that partner_LU_name recognizes but it cannot start. There could be several reasons for this:
Define the transaction program on the workstation or ensure that the transaction program definition is correct. The symbolic_destination_name can be used to obtain the workstation transaction program name from the APPC/MVS side information table. For information about the recommended values for TP_name, see the CODE/370 Installation manual. The OS/2 system error log can contain valuable diagnostic information. To access the system error log, select System Error Log from the FFST/2 folder or type SYSLOG at the OS/2 command line.
Partner_LU_name rejected the allocation request because the host program specified a workstation TP_name that partner_LU_name does not recognize. The transaction program definition is missing on the workstation.
Define the transaction program on the workstation. The symbolic_destination_name can be used to obtain the workstation transaction program name from the APPC/MVS side information table. For information about the recommended values for TP_name, see the CODE/370 Installation manual. The OS/2 system error log can contain valuable diagnostic information. To access the system error log, select System Error Log from the FFST/2 folder or type SYSLOG at the OS/2 command line.
The host communications code received an unexpected return code from a TCP/IP call. The information displayed is for diagnostic purposes.
For remote debug mode, you need to provide the correct TCP/IP address and/or port number of the workstation.
The initialization of the LU 6.2 conversation between the host and the workstation (in a batch process) has failed. The debugger is terminated and the execution of the batch application continues. Note the accompanying messages as to possible causes.
For Q++ programs, Debug Tool requires that you specify the path where the list files are stored in the environment variable QPPLISTFILES.
You can use the Language Environment runtime option ENVAR to specify the path where the list files are stored. For example, the following runtime option specifies that the list files are stored in the path /u/USER1/SAMPLE/list_files: ENVAR("QPPLISTFILES=/u/USER1/SAMPLE/list_files/") To learn more about specifying environment variables using Language Environment runtime options, see Language Environment Customization.
Conversation initialization failed due to an invalid session ID in the Session Parameter. There could be several reasons for this,
Diagnostic information is recorded in either the EVFERROR.LOG or the EQALU62.LOG. The path where these logs are stored is in the CODETMPDIR environment variable in CONFIG.SYS. If there is already an existing PWS Debug Tool session with the given session ID then a different session ID must be provided for concurrent debug sessions on the same workstation. If a session ID is not specified, it defaults to CODEDT. For a description of the Session Parameter and its contents, see the Debug Tool manual.
Conversation initialization failed. A batch program, attempting to start an LU 6.2 debug session, has passed an invalid Session Parameter. For example, LU2 or MFI has been specified for session type or a session ID longer than eight characters has been specified. For a description of the Session Parameter and its contents, see the Debug Tool manual.
Correct the Session Parameter and invoke the batch application again.
The terminal id specified to receive Debug Tool screen was detected but not acquired.
Correct the Debug Tool Term Id using DTCN Replace function or logon to already defined one.
Keywords APPC&, TCPIP&, VADAPPC&, and VADTCPIP& require a workstation ID to be entered.
Correct or enter the workstation destination name.
Keywords VADTCPIP& or TCPIP& require a port ID to be entered. The value of this port id ranges from 1 to 65535 ('FFFF'x). If not entered or in error, a default value of 8001 is used.
Correct or enter the TCP/IP port ID.
Load module qualification is referring to a load module that cannot be located.
The load module might be missing or it might have been loaded before Debug Tool was first used. Debug Tool is aware of additional load modules only if they were FETCHed after Debug Tool got control for the first time.
The compilation unit may be misspelled or missing.
The current location is unknown; as such, the reference or statement must be explicitly qualified.
Either explicitly set the qualification using the SET QUALIFY command or supply the desired qualification to the command in question.
This message is issued if the specified VTAM terminal is currently in use.
End the session that is currently using the LU.
An unrecoverable error occurred acquiring or communicating with a VTAM® terminal. error_type is one of the following:
This message is issued whenever a permanent error is detected communicating with the VTAM terminal. A terminal condition is then signaled to LE causing program termination.
| error_type | insert1 | insert2 | insert3 |
|---|---|---|---|
| RPL or INQUIRE RPL or No default LOGMODE | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | rcrnoooo where: rc-R15,rn-R0, or rcrn-RPLSense if RtnCodeFdBk2 = 0404 or 0403, and oooo-Error Offset in EQAYVTAM | ppddkkkk where: pp-RPLCode, dd-RtnCode, and kkkk-FdBk2 |
| ACB | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | ACBERR |
| MODCB | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | xxxxyyzz where: xxxx-0000, yy-MODCB R0, and zz-MODCB R15 |
| Logic | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | 0 |
| Function | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | EQAYVTAM function code |
| Storage | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | 0 |
| Undefined LU | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | 0 |
| Unknown | ggnnoomm where: gg - CsFlag, nn - CsFunc, oo - CSFlagOf, and mm - CSReqMod | Error Offset in EQAYVTAM | 0 |
If an ACB error is reported, check with your installer to ensure that the VTAM modifications required by Debug Tool have been made. If Undefined LU error is reported, check the MFI% operand of the TEST parameter to ensure that the correct VTAM terminal Logical Unit identifer was specified and that the terminal in known to VTAM.
Otherwise, contact IBM® support.
This message is issued when the LU is acquired after EQA1997I is issued.
None.
A referenced symbol cannot be evaluated because the required hardware is not present. Binary Floating Point requires 64-bit hardware. Decimal Floating Point requires 64-bit and decimal floating point hardware.
Correctly qualify the referenced variable and retry the command.
The command is not supported in the current environment (e.g., non-CICS)
This is the title line for the LIST DTCN command.
This is the title line for the LIST CADP command.
This message lists the program names output by the List DTCN command.
This message lists the program and compile unit names output by the LIST CADP command.
The Enable CADP command is not allowed since this particular program and/or compile unit is not in the pattern-match breakpoint list.
The Enable DTCN command is not allowed since this particular program is not in the pattern-match breakpoint list.
There are no entries in the pattern-match breakpoint list.
There is no channel named DFHNODE known to the current program.
There was an error evaluating the expression entered for the WHEN condition for the break point. LIST AT can be used to view the expression. Debug Tool continues processing.
Please check the TCPIP address and port specified and verify that the remote debugger daemon is listening.
An error during the initial processing (OPEN) of the file occurred.
Modify the command providing an ending location that is higher than starting location.
Reduce size being requested. Use DESCRIBE CHANNEL to verify the size of the container.
Start of commands in the global preferences file.
Start of commands in the user preferences file.
Start of commands in the commands file.
End of commands in the global preferences file.
End of commands in the user preferences file.
End of commands in the commands file.
The global preferences file is opened successfully.
This message header is for QUERY DEFAULT LISTINGS.
Debug Tool detected a storage violation.
This message contains the output from the DESCRIBE CHANNEL command.
Debug Tool did not detect any storage violation
There was not enough main memory available to process the command.
Under MVS data definition names are limited to 8 characters and dataset names are limited to 44 characters.
Display results of a command.
The command is not supported on Non-CICS Environments.
Debug Tool currently supports AMode(64) only for assembler and disassembly.
The command is not supported on Non-CICS Environments.
The command is not supported on Non-CICS Environments.
You must use CICS TS 3.1 or later to be able to use this feature.
The container name provided does not belong to the channel specified or does not exist.
There are no containers known to the current program.
There are no channels known to the current program.
A channel with that name was not found. Verify the name of.
Read CICS Documentation on Channels and Containers.
The LOAD MODULE request failed, the module was not found.
The LOAD MODULE request failed, there is not enough storage.
The LOAD MODULE request was unsuccessful.
The DELETE MODULE request was unsuccessful.
Only modules loaded by Debug Tool may be deleted.
The LOAD MODULE request was unsuccessful.
The indicated CU is not currently known to Debug Tool. The LOADDEBUGDATA will be run when the CU appears in a loaded module.
An LDD has already been done for the CU specified in the LDD command. This LDD may have been done previously by the user or an implicit LDD may have been done for the CU. This happens when a user-entered LDD is successful and, subsequently, the CU goes away and later reappears.
Only a disassembly CU can be identified as assembler CU.
Either the file containing the EQALANGX debug data could not be found or there was an undetermined error loading the EQALANGX file for a specified CU.
The compilation unit (program) that you named could not be located by Debug Tool.
An EQALANGX file containing the assembler debugging information does not match the object. Either the CSECT length is different, selected object code is different, or the EQALANGX file is not for the correct language.
The NAMES EXCLUDE command does not allow a pattern of "*".
The value specified before the colon in the fourth operand of the TEST runtime parameter is not in the correct format.
Correct the specification of the fourth TEST operand.
The debug file name cannot be found. The following list describes some of the possible conditions that could cause this:
The current compile unit was compiled without symbolic information. Variable information is not accessible to Debug Tool. The CU must be recompiled with TEST to provide this information.
The application has issued an EXEC CICS SEND command with the LAST Option while being debugged in single terminal mode. This would end the terminal session being used by Debug Tool, so Debug Tool has suppressed the LAST option.
If the LAST option needs to be exercised, consider debugging the application in dual terminal mode.
The search string was not found.
A qualified reference is invalid. One or more qualifiers may be undefined or not in the same structure as the desired data item.
While stepping through a program in the disassembly view, you are about to execute an instruction that will cause a transfer (branch) out of the current Compile Unit. A breakpoint is required where you would like to obtain control.
Set a breakpoint and/or enter STEP or GO to continue.
While stepping through a program in the disassembly view, you are about to execute an instruction that must run from the original location and therefore the breakpoint must be temporarily removed. A breakpoint is required where you would like to obtain control.
Set a breakpoint and/or enter STEP or GO to continue.
While stepping through a program in the disassembly view, an instruction was encountered in an unsupported location or an instruction that is not allowed to have a breakpoint was found to have a breakpoint. A breakpoint is required where you would like to obtain control. The breakpoint is automatically removed.
Set a breakpoint and/or enter STEP or GO to continue.
While debugging a program, Debug Tool could not stop the application because a valid save area back chain did not exist. The back chain pointer is located at +4 in the save area pointed to by register 13. This will most likely occur when stepping through the prolog code of a Compile Unit.
During initialization Debug Tool did not find a usable Dynamic Debug facility SVC. Either the SVC was not found or a downlevel version was detected. The Dynamic Debug facility is disabled.
Have your installer install the correct Dynamic Debug facility SVC.
The run-time API did not have enough memory to save application DATA during Playback data collection.
Use the PLAYBACK DISABLE command to disable Playback. You can then re-start Playback and specify more memory for use by Playback on the PLAYBACK ENABLE command.
The run-time API is no longer able to collect application DATA. The return code indicates a terminal error in the run-time.
Use the PLAYBACK DISABLE command to disable Playback. Return code 63 indicates not enough memory was available for Playback. Restart your Debug Tool session and enter the PLAYBACK ENABLE command using the integer option. For example: PLAYBACK ENABLE * 10000.
Playback data collection has used all available memory. The earliest collected data will be overlayed with newer data.
If it is necessary to retain more Playback data, specify a larger memory size on the PLAYBACK ENABLE command.
Results might be unreliable because the program might use the previous value that was saved in temporary storage or a register.
Recompile the program without the Optimize option.
Results would be unreliable because the program might use the previous value that was saved in temporary storage or a register.
You can SET WARNING OFF to allow the update to take place or recompile the program without optimization.
When the STORAGE runtime option is in effect, breakpoints are not allowed on the prologue instructions between the first BALR R14,R15 and the next LR R13,Rx. You may set a breakpoint on an instruction following the next LR R13,Rx or you may rerun your program without the STORAGE runtime option and set a breakpoint on the specified statement.
The indicated System or User ABEND was detected.
Investigate the cause of the ABEND.
During initialization Debug Tool did not find a usable Dynamic Debug facility SVCs EQA00SVC(IGC0014E) and EQA01SVC(IGX00051). Either the SVC was not found or a downlevel version was detected. The Dynamic Debug facility is disabled for read only programs. Other Dynamic Debug facilities may not operate correctly.
Have your installer install the correct Dynamic Debug facility SVC.
During initialization Debug Tool detected a downlevel Dynamic Debug facility SVC version. The Dynamic Debug facility is disabled for read only programs.
Have your installer install the correct Dynamic Debug facility SVC.
During initialization Debug Tool detected a downlevel Dynamic Debug facility SVC version.
Have your installer install the correct Dynamic Debug facility SVC.
During initialization Debug Tool detected a downlevel Dynamic Debug facility SVC version.
Have your installer install the correct Dynamic Debug facility SVC.
This message is used to place the Debug Tool logo, a time stamp, and copyright at the beginning of the line.
This message is used to place the Debug Tool logo, a time stamp, and copyright at the beginning of the line.
Refer to the description of the SET AUTOMONITOR command in the Debug Tool Reference and Messages document to determine the requirements this CU must fulfill in order to use the SET AUTOMONITOR command.
Debug Tool has stopped in a program and the value in GPR 13 is not a valid address.
Debug Tool will attempt to continue. However, some information may be missing or incorrect.
The Language Environment was invoked with TEST/NOPROMPT or NOTEST causing Debug Tool to be initialized during an enclave that was not the top enclave. The enclave in which Debug Tool was initialize is now terminating. Debug Tool will no longer intercept non-Language Environment events and, therefore, you can no longer debug non-Language Environment programs.
If you do not need to debug higher-level, non-Language Environment programs or to intercept non-Language Environment events, no action is required. Otherwise, re-run the job without NOPROMPT or with the CALL to CEETEST, PLITEST or ctest() in a higher-level enclave.
The Debug Tool was invoked with an EQAOPTS options module that specified SVCSCREEN OFF. Debug Tool will not intercept non-Language Environment events and, therefore, debugging of non-Language Environment programs will be limited.
If you do not need to debug non-Language Environment programs or to intercept non-Language Environment events, no action is required. Otherwise, you must have your installer provide an EQAOPTS that specifies SVCSCREEN ON.
The Debug Tool was invoked with an EQAOPTS options module that specified CONFLICT=NOOVERRIDE. Debug Tool will not intercept non-Language Environment events and, therefore, debugging of non-Language Environment program will be limited.
If you do not need to debug non-Language Environment programs or to intercept non-Language Environment events, no action is required. Otherwise, you must terminate the prior use of SVC SCREENING (TCBSVCS, TCBSVCSP, TCBSVCA2) before starting Debug Tool or have your installer provide an EQAOPTS that specifies CONFLICT=OVERRIDE. CONFLICT=OVERRIDE allows Debug Tool to save and restore the previous use of SVC SCREENING (TCBSVCS, TCBSVCSP, TCBSVCA2).
The Debug Tool was invoked with an EQAOPTS options module that specified CONFLICT=OVERRIDE. Debug Tool will save and restore the SVC Screening values.
SVC SCREENING is indicated by TCBSVCS, TCBSVCSP, and TCBSVCA2. These values are saved during Debug Tool startup and restored at Debug Tool termination.
Debug Tool was invoked with an invalid VADSCP suboption in the TEST runtime option string. Internal conversion tables for the default code page 00037 are used for translation between Debug Tool and the distributed debugger.
Correct the VADSCP suboption and restart the debug session.
Problem encountered in a code page conversion using z/OS Unicode conversion services. Internal conversion tables for the default code page 00037 are used.
See z/OS Support for Unicode: Using Conversion Services book for explanation of return code, reason code, and appropriate action.
z/OS Unicode conversion services failed. Internal conversion tables for the default code page 00037 are used in the debug session.
See z/OS Support for Unicode: Using Conversion Services book for explanation of return code, reason code, and appropriate action in the accompanied EQA2462W message. A typical problem is that the conversion images are not available. Consult with your system programmer to see what is available on the system.
This message is issued by the NAMES command when there is no data to be displayed.
This message precedes the output of the NAMES command and indicates the type of names that follow this message.
This message lists the names output of the NAMES command.
This is the header used to display the additional CSECTs included in the EQALANGX data for the current CU.
Used to display CSECTs also included in the EQALANGX data for the current CU.
COPE's usage of SVC Screening will be restored at the end of this Debug Tool session. Debug Tool was invoked with an EQAOPTS options module that specified MERGE. Debug Tool will save the COPE screening values on entry, merge them with Debug Tool's during the execution of the program, and then restores the original COPE SVC Screening values when Debug Tool terminates. SVC Screening is indicated by TCBSVCS, TCBSVCSP, and TCBSVCA2.
If you did not intend to MERGE the Debug Tool SVC Screening tables with another program, modify your EQAOPTS to specify what you require.
In order to be Language Environment compliant your application needs to follow the Language Environment rules.
Follow the Language Environment rules.
The savearea has become Language Environment compliant and all commands will work properly.
None.
In a non-CICS environment, an EQAOPTS with a SUBSYS specification of ssss was found. If Debug Tool needs to allocate a C, C++ or Enterprise PL/I source data set from a library system that stores the source in a data set that has a DSORG of DA or VSAM, then the SUBSYS=ssss allocation parameter will be used when Debug Tool allocates the data set.
If you need this support, ensure that the ssss subsystem is running on the system that you are running Debug Tool on.
During execution of the program Debug Tool encountered a hook or other event when the PSW specified AMODE64. Debug Tool will ignore all events that occur in this state and the program will continue to execute.
None.
An implicit CU was created for the specified CU in the specified load module as the result of a QUALIFY CU command for a load module that was already loaded and a COBOL CU that had not yet been executed. The CU will be destroyed when execution is resumed.
None.
An implicit LOAD command was issued for the specified load module as the result of a QUALIFY LOAD or QUALIFY CU command for a load module that was not currently loaded. A corresponding CLEAR LOAD will be issued when execution is resumed.
None.
An implicit CLEAR LOAD command was issued for the specified load module. This module was previously LOADed as the result of a QUALIFY LOAD or QUALIFY CU command for a load module that was not currently loaded.
None.
The specified implicitly created CU is being destroyed. This module was previously created as the result of a QUALIFY CU command for a CU that had not already been created.
None.
The attempt to destroy the specified CU was unsuccessful.
None.
The specified symbol was used in an assembler expression. However, it is not a valid symbol in the current compile unit.
Correct the assembler expression and retry the command.
Invalid syntax was discovered at or near the part of the expression shown in the error message.
Correct the assembler expression and retry the command.
The specified expression is invalid in the current context.
Correct the assembler expression and retry the command.
The specified operator is not valid in an assembler expression.
Correct the assembler expression and retry the command.
A relational expression (an expression that contains a conditional operator such as =, ^= or <=) was found in an unexpected context or was not found where one was expected.
Correct the assembler expression and retry the command.
An internal Debug Tool error has occurred processing an assembler expression.
Report this error to your IBM representative.
An assembler assignment contain a source and receiver that are not compatible for assignment. For example, a string longer than four bytes cannot be assigned to an arithmetic receiver.
Correct the assignment operands and retry the command.
An error such as an addressing error occurred while Debug Tool was attempting to execute an assignment. Either the source or receiver may be incorrectly specified.
Report this error to your IBM representative.
The Disassembler breakpoints no longer apply to an assembler program. The user should reapply any required breakpoints.
Set appropriate breakpoints.
The specified symbol was used in a non-Language Environment COBOL expression. However, either there are more than one variable by this name and the reference was not sufficiently qualified to disambiguate the reference or the qualification specified was invalid.
Correctly qualify the referenced variable and retry the command.
This message is issued by the remote interface in response to the SET LDD command.
None.
This message is issued by the remote interface in response to the QUERY LDD command.
None.
A LOAD request cannot be issued until Debug Tool initialization is complete.
A LOAD command was used in a non-Language Environment environment to load a load module that contained one or more Language Environment CUs. These CUs cannot be created until Language Environment is active. CUs will be created only for non-Language Environment CUs in this load module.
The data at the cursor location is either incorrect or some data is missing. There could be several reasons for this:
Correct the entry where the cursor is positioned and invoke the function again. You can use Help (PF1) to find the context sensitive help for that field.
DTCN discovered an internal error.
Contact IBM service.
During processing, DTCN discovered an internal CICS error
Correct the error and issue the command again. If the error persists, contact your CICS system programmer and/or IBM service.
There is no action defined with the PF key used by the user.
Use the keys displayed in the bottom line. For more information about the actions defined for this panel, use PF2 key for general help.
The add command failed because a profile for that terminal is already stored in the Debug Tool Profile Repository.
You can use Show(PF7) command to display the profile or modify the TermId+TranId and Add a new profile.
The profile for that terminal does not exist in the Debug Tool Profile Repository and cannot be updated. Specify different terminal to update.
You can use Next(PF8) command to browse the Profile Repository starting from any point.
The profile for the terminal does not exist in the Debug Tool Profile Repository and cannot be updated.
Specify different Terminal+Transaction Id to delete. You can use Next(PF8) command to browse the Profile Repository starting from any point.
The profile for the Terminal does not exist in the Debug Tool Profile Repository.
Specify different Terminal to display. You can use Next(PF8) command to browse the Profile Repository from any point.
There are no more profiles in the Debug Tool Profile Repository.
DTCN deleted all profiles stored in the Debug Tool Profiles Repository. This action affects all users working with that CICS region.
DTCN needs at least one identifier to identify the resource you want to debug.
Provide one or more resources to be debugged. DTCN uses a combination of resource IDs to uniquely identify a resource. You should specify adequate resource qualification to ensure that you debug only the tasks you wish to debug.
You have tried to set up a debug session using TCP/IP, but TCP/IP SOCKETS for CICS is not active in the CICS region.
Either set up a non-TCP/IP session, or refer to the TCP/IP SOCKETS for CICS publications for guidance on activating it.
A profile was saved in the Debug Tool Profile Repository.
Existing profile was updated in the Debug Tool Profile Repository.
Existing profile was deleted from the Debug Tool Profile Repository
PF3 has been pressed, but the new profile has not been saved in the repository.
Press PF4 to save the profile in the repository, or press PF3 again to exit from DTCN without saving the new profile.
An attempt has been made to save a profile in the DTCN repository, but its debug resources match an existing profile.
Provide additional resource IDs to qualify your debugging needs better.
Your site has specified in its EQAOPTS member that this field must be filled in. For more information, refer to DTCNFORCExxxxxx options in macro EQAXOPT.
Enter a resource name in the field.
The terminal ID at the highlighted cursor location does not match the current terminal.
Press PF10 to set the value to the current terminal identifier.
The field at the current cursor location is invalid for the PF10 action. This key may only be pressed when the current cursor location is in the terminal or display ID fields.
If you wish to update the terminal ID or display ID fields, move the cursor to one of those fields and press PF10 again. Otherwise, no further action is required.
SET MONITOR COLUMN OFF was issued while SET MONITOR WRAP is OFF. The command is rejected, because the Monitor window already shows the values in one, scrollable line. The Monitor window must stay in columnar format.
Change the setting of MONITOR WRAP to ON, and then issue SET MONITOR COLUMN OFF.
SET MONITOR WRAP OFF was issued while SET MONITOR COLUMN is OFF. The command is rejected, because the Monitor window can show values in one scrollable line only when the setting of MONITOR COLUMN is ON.
Change the setting of MONITOR COLUMN to ON, and then issue SET MONITOR WRAP OFF.
Because SET MONITOR COLUMN is ON, the monitor window width must be at least 36 characters. The window size is not changed.
To change the Monitor window size, you need to first SET MONITOR COLUMN OFF.
Columnar format in the Monitor window can be displayed only if the width of Monitor window is bigger than 36 characters.
To SET MONITOR COLUMN ON, you need first change the width of the Monitor window.
Debug Tool did not find a current channel in the program. This could be because the program has not been invoked with a channel.
Go to the CICS Transaction Server V3.1 (or later) information center and look for the topic "The current channel", which describes a current channel and gives examples of how to invoke a channel.
Debug Tool could not find the channel for the program. The name might be misspelled.
Verify that you have spelled the channel name correctly. If you aren't sure about the channel name, use DESCRIBE CHANNEL * command for a list of channels known.
There are no channels known to the current program.
Go to the CICS Transaction Server V3.1 (or later) information center and look for the topics "Creating a channel" or "The scope of a channel" for instructions and explanations.
Debug Tool could not find any channels known to the program. This could be because no channels have been created or assigned.
Go to the CICS Transaction Server V8.1 (or later) information center and look for the topics "Discovering which containers were passed to a program" or "Discovering which containers were returned from a link" to learn more about finding or identifying containers.
Debug Tool could not find the container in the channel. The names might be misspelled.
Verify that you have spelled the container name and channel name correctly. After you make any corrections, retry the command. If you aren't sure about the channel name or container name, use DESCRIBE CHANNEL * command.
You must use CICS Transaction Server V3.1 or later to be able to use this feature.
You cannot use the DESCRIBE CHANNEL command in a non-CICS environment.
You cannot use the LIST CONTAINER command in a non-CICS environment.
There is no channel named DFHNODE known to the current program.
Follow CICS directions on creating channels and containers.
You cannot use the CHKSTGV command in a non-CICS environment.
Reduce size being requested. Use DESCRIBE CHANNEL to verify the size of the container.
Modify the command providing an ending location that is higher than starting location.
You cannot use the SET IGNORELINK command in a non-CICS environment.
This command requires CICS.
The CALL %FM command requires that IBM File Manager be installed and customized for CICS.
Verify that IBM File Manager is installed and customized for CICS as described in the topic "Updating the CICS start up procedures" in the Customization Guide for IBM File Manager.
This command requires that IBM File Manager be installed.
Verify that IBM File Manager is installed and customized for CICS as described in the topic "Updating the CICS start up procedures" in the Customization Guide for IBM File Manager.
Debug Tool found an invalid character in the base address field or in the address column of the Memory window. You can put only hexadecimal characters or the G or R commands in those areas.
Type in hexadecimal characters, the G or R commands, or clear any characters you might have accidentally entered. Then press Enter.
Debug Tool found an invalid character in the data column of the Memory window. You can put only hexadecimal characters or the G or R commands in those areas.
Type in hexadecimal characters, the G or R commands, or clear any characters you might have accidentally entered. Then press Enter.
Debug Tool found an invalid command in the history entry field of the Memory window. You can put only the G or R commands in the history entry field.
Type in hexadecimal characters, the G or R commands, or clear any characters you might have accidentally entered. Then press Enter.
Debug Tool found multiple changes in a history entry field of the Memory window. You can only enter one command at a time.
Clear the extra characters, then press Enter.
You cannot use the FIND command in the Memory window.
Do not use the FIND command in the Memory window.
You cannot use any one of the following scroll amounts for the Memory window: TOP, BOTTOM, MAX, and TO.
You cannot use this command on a logical window that has not been assigned to a physical window.
Use one of the following methods to assign the logical window to a physical window:
The width of the physical window assigned to the Memory window is less than the full screen width.
Do one of the following:
The valid Amode values are 24 and 31.
Enter a valid Amode value.
You cannot enter the SCROLL LEFT command in the Memory window. The Memory window displays memory content in the entire width of the window.
You cannot enter the SCROLL RIGHT command in the Memory window. The Memory window displays memory content in the entire width of the window.
You have reached the top of memory space that the Memory window can display.
Do not enter SCROLL UP command.
You have reached the bottom of memory space that the Memory window can display.
Do not enter SCROLL DOWN command.
Look at the Window Layout Select Panel. Verify that L and E are not used in the panel layout.
You cannot enter the SCROLL TO command in the Memory window.
The variable named has been declared as VARYING with length n, but its current length is greater than n. The variable may be unuseable.
Check the length of the variable.
The specified identifier is used but has not been defined.
Define the identifier before using it. Check its spelling. If the identifier has been defined in a header file, check that any required macros have been defined.
The result from the expression evaluation cannot be displayed. For example, the basing pointer has a zero or uninitialized value.
The EQALANGX data does not correspond to the CSECT in the loaded load module because the CSECT length does not match.
Regenerate the EQALANGX data or ensure that the matching object has been link-edited into the current load module.
The EQALANGX data does not correspond to the CSECT in the loaded load module because the object code at the specified offset does not match.
Regenerate the EQALANGX data or ensure that the matching object has been link-edited into the current load module.
The EQALANGX data does not correspond to the CSECT in the loaded load module because CSECT was coded in the specified programming language but the EQALANGX data is for a different programming language.
Regenerate the EQALANGX data or ensure that the matching object has been link-edited into the current load module.
A Debug File containing the listing and the debugging tables does not match the creation date of the object.
The status of the object of a SET command is displayed when QUERYed individually.
Use the Modules view to look at the load modules and programs.
Shows the place where the program was interrupted.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
Shows the bearings in an interrupted program.
This message is issued when there is not enough storage available to satisfy the request.
Increase the storage limit (for example, the region size).
Debug Tool uses Binder APIs to retrieve necessary information for the debugging of a load module. When the load module is loaded from a system managed library, the Binder APIs cannot retrieve this necessary information. Hence, Debug Tool cannot debug the module.
Contact your System Programmer and have them place the module in a non-system managed library.
Debug Tool uses binder APIs to retrieve necessary information for the debugging of a load module. When the load module is loaded from a system managed library the binder APIs cannot retrieve this necessary information. In this case, a module by the same name and with the same length was found in the data set(s) allocated to the specified DDName. That module was used by the binder APIs.
None.
Debug Tool uses binder APIs to retrieve necessary information for the debugging of a load module. When the load module is loaded from a system managed library the binder APIs cannot retrieve this necessary information. In this case, a module by the same name and but with a different length was found in the data set(s) allocated to the specified DDName. Because the lengths do not match, that module cannot be used by the binder APIs and, therefore, the load module cannot be debugged.
None.
Debug Tool uses binder APIs to retrieve necessary information for the debugging of a load module. The load module length returned by the binder APIs does not match the length of the load module in memory.
None.
Debug Tool uses binder APIs to retrieve necessary information for the debugging of a load module. When the load module is loaded from LLA, the binder APIs cannot retrieve this necessary information. Debug Tool then looks in file EQALOAD or STEPLIB to attempt to find a load module with the same name and length in order to obtain this information. No such copy was found. Hence, Debug Tool cannot debug the module.
Allocate either EQALOAD or STEPLIB to a data set containing a copy of the specified program that matches the copy in LLA or do an LLA refresh to ensure that the system is using the latest copy.
This message is issued by the remote interface in response to the SET ASSEMBLER STEPOVER command.
None.
This message is issued by the remote interface in response to SET INTERCEPT being turned on and for COBOL DISPLAY UPON CONSOLE output.
None.
This message is issued by the remote interface in response to SET INTERCEPT being turned on and for COBOL DISPLAY UPON CONSOLE output.
None.
This message is issued by the remote interface in response to SET INTERCEPT being turned on and for COBOL DISPLAY UPON CONSOLE output.
None.
This message contains the output from the DESCRIBE LOADMODS command.
The indicated load module was specified as an operand of the DESCRIBE LOADMODS command but is not an active load module.
A Debug File containing the listing and the debugging tables does not match the creation date of the object, and the data it contains is not valid.
The "Stop When Date Fields are Accessed" breakpoints are also known as DATE breakpoints, which are supported only in COBOL compile units compiled with the DATEPROC compiler option. The application will not stop if a date field in any of the following types of compile units is accessed:
If the application being debugged does not contain a COBOL compile unit compiled with the DATEPROC compiler option, remove this breakpoint.
Debug Tool could not obtain an address for this expression or variable. The expression or variable might be out of scope or the syntax might not be valid.
Check that the expression or variable is typed in correctly. Check that the variable or variables used are within scope of the current compile unit. Check that the expression or variables are supported in the current programming language.
The command is only valid in a CICS Environment.
None.
The z/OS XML System Services parser returned the indicate return code and reason code. See the z/OS XML System Services documentation for a complete description of the associated error. This message may be accompanied by message EQA4701I and/or EQA4702I and EQA4703I.
This message may be issued following message EQA4700E. It contains a short description of the error associated with the Return Code and Reason Code included in that message.
This message may be issued following message EQA4700E and will be followed by message EQA4703I. It contains a few characters of the XML source surrounding the point at which the error was detected by the XML parser.
This message follows message EQA4702I and uses an asterisk to indicate the column in that message at which the error was detected by the XML parser.
The XML keyword was specified without the EBCDIC or ASCII suboperand. In this case, all characters with a value less than X'80', except for X'40', are assumed to be ASCII characters. All characters with a value greater than or equal to X'80' are assumed to be EBCDIC characters. If the specified area contains more ASCII characters than EBCDIC characters, ASCII is defaulted. Otherwise, EBCDIC is defaulted.
If the correct encoding was not defaulted, specify the EBCDIC or ASCII keyword suboperand of the XML keyword.
Debug Tool XML processing requires the z/OS XML System Services that are only available when running z/OS V1R8 or later or on z/OS V1R7 with the proper APAR installed. The command cannot be processed.
Debug Tool attempted to allocate a file while the user program was processing in a OPEN exit. MVS does not allow this. This message should be followed by another message explaining the action taken by Debug Tool.
Refer to the following message and take the appropriate action.
This message is an internal diagnostic message and should not be seen unless you are using special processes as instructed by Debug Tool support.
Report this message to Debug Tool support.
Debug Tool was entered for an SVC or overlay hook after Language Environment routines had set the CeeCAAXHCL flag but Debug Tool was not able to establish and ESPIE.
If this message is followed by unexpected Debug Tool behavior, report the message to Debug Tool support.
Debug Tool called IFAEDREG to check for an enabled product registration for Debug Tool. IFAEDREG indicated that the check did not succeed.
If Debug Tool is licensed to run on this machine, the system programmer should register and enable the product registration per the appropriate Program Directory.
Debug Tool found a DBCS shift-out control character in the screen buffer, but was unable to find a corresponding shift-in control character. A shift-in control character has been inserted. Debugging results may be unpredictable now.
Make sure there is a matching shift-in control character for each shift-out control character.
The requested user interface is not available so Debug Tool will quit processing events and the application will continue to run. (Note that any calls to restart Debug Tool are ignored.) This behavior was specified in the EQAOPTS customization module via the EQAXOPT macro invocation option NODISPLAY,QUITDEBUG.
Make sure the user interface specified as a suboption in the TEST runtime option is correct and available. However, if you do not want the processing of a QUIT DEBUG command when this situation is detected then change the EQAXOPT macro invocation option to NODISPLAY,DEFAULT in your EQAOPTS customization module.
The user name specified on the VTAM% option has not been associated to a terminal using the Debug Tool Terminal Interface Manager.
Use the Debug Tool Terminal Interface Manager to associate the user name with a terminal and rerun the application.
The Language Environment routine CEE3MBR failed and returned the indicated feedback code.
Determine the cause of the error using the indicated feedback code.
Debug Tool Program EQA00CIC in load module EQA00OSX was unable to load the specified program.
Ensure that the group (EQA) that contains the Debug Tool run time routines is in the group list used during CICS start-up. If required, rerun the EQACCSD job and restart the CICS region. Check the Debug Tool website for any applicable updates your system might require. If the problem persists, contact Debug Tool support.
Debug Tool has experienced a problem, and is reporting diagnostic information (usually return codes given to Debug Tool by a subsystem.)
Check the log for further diagnostic messages. If there is no obvious cause for the problem, contact IBM Support.
Debug Tool has issued an EXEC CICS command and has received an unexpected response.
Check the log for further diagnostic messages. If there is no obvious cause for the problem, contact IBM Support.
Debug Tool is reporting that another CICS XPCFTCH global user exit has set a modified entry address (MEA) and prevented Debug Tool from any possible debugging of a specific non-Language Environment program. XXXXXXXXX can be either : 'Prior MEA' or 'Program' or 'Transid' and YYYYYYYYY is the data associated with each. Note this message is only issued once when this occurs the first time after the Debug Tool CICS exits are activated. Subsequent conflicts are not written to the CICS JES log.
Multiple XPCFTCH exits running in the same CICS region which can each set the MEA and return to CICS is usually not recommended. For Debug Tool, you will be unable to debug any non-Language Environment programs when the MEA was changed by another XPCFTCH exit. The behavior of Debug Tool in this kind of scenario will likely be unpredictable.
Debug Tool detected an error in attempting to deactivate the NewProg supporting exits.
An error has likely occurred during Debug Tool CICS region initialization. Ensure that Debug Tool is properly installed in the CICS region. Also verify that the Debug Tool hlq.SEQAMOD data set is in the region DFHRPL DD and the CICS resource definitions from hlq.SEQASAMP(EQACCSD) have been added.
Debug Tool is reporting that NewProg support is now disabled in the current CICS region after a DTCP transaction was issued with the 'F' parameter. This support is to allow multi-region CICS configurations (for example, TOR/AOR), where DTCN is used, to work properly when DTCN is executed in one region (TOR) and tasks to be debugged are routed to an alternate region (AOR). This is only required in the regions where DTCN does not run.
Debug Tool is reporting that the non-Language Environment-supporting CICS exits are now enabled in the current CICS region. This was accomplished by using PLTPI program EQA0CPLT and starting with INITPARM=(EQA0CPLT='NLE').
Debug Tool is reporting that NewProg support is now enabled in the current CICS region. This support is to allow multi-region CICS configurations (for example, TOR/AOR), where DTCN is used, to work properly when DTCN is executed in one region (TOR) and tasks to be debugged might be routed to an alternate region (AOR). This is only required in the regions where DTCN does not execute.
Debug Tool is reporting that its single-terminal mode screen stacking exits are now enabled. This is to support installations where starting CICS exits is restricted by an external security manager (for example, RACF) and prevents Debug Tool from starting the exits when it starts a debug session for a user. This was accomplished using PLTPI program EQA0CPLT and starting with INITPARM=(EQA0CPLT='STK').
Debug Tool detected an error while attempting to activate the non-Language Environment supporting exits.
The error most likely occurred during Debug Tool CICS region initialization. Verify that the Debug Tool hlq.SEQAMOD data set is the in the region DFHRPL and the CICS resource definitions from hlq.SEQASAMP(EQACCSD) have been added.
Debug Tool detected an error in attempting to activate the NewProg supporting exits.
An error has likely occurred during Debug Tool CICS region initialization. Ensure that Language Environment is properly installed in the CICS region. Also verify that the Debug Tool hlq.SEQAMOD data set is in the region DFHRPL DD and the CICS resource definitions from hlq.SEQASAMP(EQACCSD) have been added.
The Debug Tool non-Language Environment CICS global user exits were made active in a CICS region where Debug Tool did not successfully initialize during CICS region startup.
Ensure that Language Environment is installed in the CICS region and verify that the Debug Tool installation steps were executed properly. For example, the Debug Tool hlq.SEQAMOD data set is in the DFHRPL DD and that the hlq.SEQASAMP(EQACCSD) job was run to add Debug Tool resource definitions to the CICS region.
Internal Debug Tool SVC Screening error or Debug Tool SVC (109 extended code 51) issued outside Debug Tool. The SVC will abend.
If using Debug Tool contact your IBM representative.
Internal Debug Tool SVC Screening error or Debug Tool SVC (109 extended code 51) issued outside Debug Tool. The SVC will abend.
If using Debug Tool contact your IBM representative.
Internal Debug Tool SVC Screening error or Debug Tool SVC (109 extended code 51) issued outside Debug Tool. The SVC will abend.
If using Debug Tool contact your IBM representative.
SVC Screening is in use by another product and SVC Screening CONFLICT=NOOVERRIDE is specified by EQAOPTS. Handling of non-Language Environment events is not available. Debugging of non-Language Environment programs will be restricted in this Debug Tool session.
The Debug Tool was invoked with an EQAOPTS options module that specified CONFLICT=NOOVERRIDE. Debug Tool will not intercept non-Language Environment events and, therefore debugging of no-Language Environment programs will be limited.
If you do not need to debug non-Language Environment programs or to intercept non-Language Environment events, no action is required. Otherwise, you must terminate the prior use of SVC SCREENING (TCBSVCS, TCBSVCSP, TCBSVCA2) before starting Debug Tool or have your installer provide an EQAOPTS that specified CONFLICT=OVERRIDE. CONFLICT=OVERRIDE allow Debug Tool to save and restore the previous use of SVC SCREENING (TCBSVCS, TCBSVCSP, TCBSVCA2).
Debug Tool detected an error during the ENABLE of a required CICS exit program.
Determine if the Debug Tool hlq.SEQAMOD library is available in the DFHRPL concatenation of the CICS region and the resource definitions provided in hlq.SEQASAMP(EQACCSD) have been added to the CICS region that is initializing.
Debug Tool detected an error during the ENABLE of a required CICS exit program.
Determine if the Debug Tool hlq.SEQAMOD library is available in the DFHRPL concatenation of the CICS region and the resource definitions provided in hlq.SEQASAMP(EQACCSD) have been added to the CICS region that is initializing.
Debug Tool CICS PLT program EQA0CPLT detected an error during the search for Debug Tool region-level resources.
An error has likely occurred during Debug Tool CICS region initialization. Ensure that Language Environment is properly installed in the CICS region. Also, verify that the Debug Tool hlq.SEQAMOD data set is in the region DFHRPL DD and the CICS resource definitions from hlq.SEQASAMP(EQACCSD) have been added.
Debug Tool detected a NOTAUTH condition during an EXTRACT EXIT call to CICS.
Determine if the current Debug Tool user has external security-manager (RACF) access to the EXITPROGRAM CICS CLASS. This includes the ability to issue the EXEC CICS EXTRACT/ENABLE/DISABLE EXIT commands. If this is not permitted, then use of Debug Tool PLT initialization routine, EQA0CPLT, is recommended. Refer to the Debug Tool Customization Guidefor information on EQA0CPLT.
Debug Tool CICS PLT program EQA0CPLT detected an error during the ENABLE of a required CICS exit program.
An INVREQ response was received during a call to CICS to ENABLE the Debug Tool screen-stack exits. Contact IBM Support Center and report the error.
Debug Tool CICS PLT program EQA0CPLT detected an error during the ENABLE of a required CICS exit program.
Determine if the CICS region user id has external security-manager (RACF) access to the EXITPROGRAM CICS CLASS. This includes the ability to issue the EXEC CICS EXTRACT/ENABLE/DISABLE EXIT commands.
Debug Tool CICS PLT program EQA0CPLT detected an error during the ENABLE of a required CICS exit program.
Determine if the Debug Tool hlq.SEQAMOD library is available in the DFHRPL concatenation of the CICS region and the resource definitions provided in hlq.SEQASAMP(EQACCSD) have been added to the CICS region that is initializing.
Debug Tool detected an unsupported release of CICS and defaults to the latest release of CICS that this version of Debug Tool supports.
Determine if Debug Tool is starting on a supported release of CICS. See the Debug Tool Program Directory for the list of CICS releases that are supported.
Debug Tool program EQA0CPLT is starting. This program activates various Debug Tool resources during CICS region startup. This includes starting up Debug Tool support for running in CICS multi-region configurations (INITPARM=(EQA0CPLT='NWP')) and starting Debug Tool screen stack exits once at region initialization (INITPARM=(EQA0CPLT='STK')) and starting Debug Tool non-Language Environment-supporting exits (INITPARM=(EQA0CPLT='NLE')). Combinations of these selections are also supported. For example:
INITPARM=(EQA0CPLT='NWP,STK,NLE')
Debug Tool program EQA0CPLT is ending. This program activates various Debug Tool resources during CICS region startup. This includes starting up Debug Tool support for running in CICS multi-region configurations (INITPARM=(EQA0CPLT='NWP')) and starting Debug Tool screen stack exits once at region initialization (INITPARM=(EQA0CPLT='STK')) and starting Debug Tool non-Language Environment-supporting exits (INITPARM=(EQA0CPLT='NLE')).
Debug Tool has detected abend Abcode while processing program Abprogram under CICS. Ret@ is the address of the location where the abend was issued.
This message occurs when the non-Language Environment Debug Tool CICS exits are active and an abend has occurred in the application currently being debugged. It is trapped as a result of the TRAP(ON) runtime option. The default behavior for the STEP or GO command at this time is for Debug Tool to display the abend and allow the task to terminate or allow any active CICS HANDLE abend routines to run or, if applicable, allow any Language Environment user handlers or signal catchers to run. Use the TRAP(OFF) runtime option if you do not want Debug Tool to capture abends. This message is written to the CICS region's JES message log.
Debug Tool has detected program check interrupt code Intcd while processing program Abprogram under CICS. Int@ is the address of the location where the program check occurred.
This message occurs when the non-Language Environment Debug Tool CICS exits are active and a program check has occurred in the application currently being debugged. It is trapped as a result of the TRAP(ON) runtime option. The default behavior for the STEP or GO command at this time is for Debug Tool to display the abend and allow the task to terminate or allow any active CICS HANDLE abend routines to run or, if applicable, allow any Language Environment user handlers or signal catchers to run. Use the TRAP(OFF) runtime option if you do not want Debug Tool to capture program checks. This message is written to the CICS region's JES message log.
Debug Tool program EQANCPLT is starting. This program activates the Debug Tool non-Language Environment CICS global exits which must be executed as either a stage 2 or 3 PLT post initialization program.
Debug Tool program EQANCPLT is ending. This program activates the Debug Tool non-Language Environment CICS global exits which must be executed as either a stage 2 or 3 PLT post initialization program..
Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS.
Contact IBM support center and report the error. If this message occurs repeatedly, disable the non-Language Environment CICS exits using transaction DTCX (DTCXXF) or by removing the EQANCPLT from the CICS PLT.
Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS.
Contact IBM support center and report the error. If this message occurs repeatedly, disable the non-Language Environment CICS exits using transaction DTCX (DTCXXF) or by removing the EQANCPLT from the CICS PLT.
Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS due to back-level Dynamic Debug facility SVCs.
Verify that the latest version of the Debug Tool Dynamic Debug facility SVCs are installed. The level of the SVCs can be checked by running the exec in dthlq.SEQAEXEC(EQADTSVC).
Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS due to back-level Dynamic Debug facility SVCs. This message occurs with message EQA9966E and indicates the detected levels of the two Debug Tool Dynamic Debug facility SVCs.
Verify that the latest version of the Debug Tool Dynamic Debug facility SVCs are installed. The level of the SVCs can be checked by running the exec in dthlq.SEQAEXEC(EQADTSVC). For non-Language Environment support, EQA00SVC must be at least 04 and EQA01SVC at least 05.
Debug Tool CICS exit activation transaction DTCX is unable to determine a valid exit type to start or stop.
Verify that DTCX is issued with an exit type of X=all exits or F=XPCFTCH exit or E=E=XEIIN or A=XPCTA or H=XPCHAIR. Note there is no blank space between DTCX and this parameter (for example: DTCXXO = turn all exits ON and DTCXXF = turn all exits OFF).
Debug Tool CICS exit activation transaction DTCX or Newprog activation transaction DTCP is unable to determine a valid action to take, O=ON or F=OFF.
Re-enter the transaction with an O or F parameter where O=On and F=Off.
Debug Tool CICS global user exits activated successfully.
Debug Tool CICS global user exits deactivated successfully.
Debug Tool CICS exit activation transaction DTCX successfully started the glueexitname exit where glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR.
Debug Tool CICS exit activation transaction DTCX successfully stopped the glueexitname exit where glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR.
Debug Tool CICS exit activation transaction DTCX was unable to activate glueexitname - dtexitname where glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR and dtexitname is either EQANCFTC, EQANCXEI, EQANCXAB, or EQANCXHA.
Verify that the latest dthlq.SEQASAMP(EQACCSD) CICS resource definitions are installed and the Debug Tool dthlq.SEQAMOD library is in the CICS DFHRPL DD concatenation. If this has already been done, contact IBM support center and report the error.
Debug Tool CICS exit activation transaction DTCX was unable to deactivate glueexitname - dtexitname where glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR and dtexitname is either EQANCFTC, EQANCXEI, EQANCXAB, or EQANCXHA.
Verify that the latest dthlq.SEQASAMP(EQACCSD) CICS resource definitions are installed and the Debug Tool V5.1 dthlq.SEQAMOD library is in the CICS DFHRPL DD concatenation. If this has already been done, contact IBM support center and report the error.
The requested CICS global user exit for non-Language Environment assembler support was already active. glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR.
Debug Tool is unable to activate the non-Language Environment CICS global exits due to back-level Dynamic Debug facility SVCs. dtsvcname is either EQA00SVC or EQA01SVC.
Verify that the latest version of the Debug Tool Dynamic Debug facility SVCs are installed. The level of the SVCs can be checked by running the exec in dthlq.SEQAEXEC(EQADTSVC). For non-Language Environment support, EQA00SVC must be at least 04 and EQA01SVC at least 05.
Debug Tool is unable to set a hook and stop in this program because the separate debug file cannot be located. This program was specified using a DTCN or CADP profile.
Verify that the debug data file exists and make its location known to Debug Tool by using the SET DEFAULT LISTINGS or SET SOURCE command, the EQAUEDAT user exit or the EQADEBUG DD name.
EQANMDBG was unable to load the user program specified as the first positional parameter.
Ensure that the specified program name is spelled correctly and that the program is available in the standard search path for load modules.
error_description is replaced with the following text:
(where aaaa is the CICS abend code.)
Look up the CICS abend code in the CICS Messages and Codes manual and take the appropriate action to resolve the CICS abend
The internal Debug Tool storage allocation chains have been corrupted. Other forms of this message might also appear with additional information about the error.
Ensure that your program is not overwriting Debug Tool storage. Check the Debug Tool web site for any applicable service updates your system might require. If the problem persists, contact Debug Tool support.
Debug Tool has issued an EXEC CICS command, and has received an unexpected response.
Review the command and response to determine if CICS configuration needs to be changed. If there is no obvious cause for the error condition, contact IBM Support.
An invalid value was specified for the indicated runtime parameter.
Correct the specified value.
EQANMDBG was invoked without a positional parameter specifying the name of the program to be debugged.
Specify an initial positional parameter indicating the name of the program to be debugged.
The non-Language Environment version of Debug Tool (EQANMDBG) was invoked but the Debug Tool Dynamic Debug facility SVCs required for dynamic debug support have not been installed.
Have your system programmer complete the installation of the required Debug Tool Dynamic Debug facility SVCs.
One of the required Debug Tool load modules is missing.
Contact your system programmer to verify the proper installation of Debug Tool.
A non-Language Environment program issued a LINK SVC for the specified load module. However, an invalid address was specified for the first positional parameter that is used to specify Language Environment runtime parameters and user parameters. This parameter must be valid, so that Debug Tool can add the TEST parameter.
Correct the parameter address passed to the LINK SVC.
A Debug Tool QUIT command was issued in a multi-enclave environment.
No action is necessary.
The Debug Tool V5R1 (or later) non-Language Environment program was invoked but the installed version of the Debug Tool Dynamic Debug facility SVCs were from a earlier version of Debug Tool.
Have your system programmer install the current V5R1 or later Debug Tool Dynamic Debug facility SVCs.
This is an internal Debug Tool message. No user response is required.
An error was encountered loading the specified load module.
Retry the Debug Tool session. Check the Debug Tool website for any applicable service updates your system might require. If the problem persists, contact Debug Tool support.
An internal Debug Tool error has occurred.
Check the Debug Tool web site for any applicable service updates your system might require. If the problem persists, contact Debug Tool support.
The Dynamic Debug facility was unable to successfully use the Authorized Debug facility to place a hook into an application that has been loaded into protected (read only) storage.
If the application has been compiled with hooks (eg TEST(ALL,...) then you will be able to debug this application. If the application has been compiled with TEST(NONE,..) then you will not be able to STEP or set breakpoints.
Ensure that both the Dynamic Debug facility and Authorized Debug facility have been activated. Ensure that you have the access through your security system to resource EQADTOOL.AUTHDEBUG in CLASS(FACILITY).
There is insufficient storage for Debug Tool to initialize.
Increase the region size availalable to the program and rerun.
All EQA9995E messages signify a severe error has occurred in the Dynamic Debug facility SVC routine while processing an 0A91 instruction.
A severe error has occurred in the Debug Tool Authorized Debug Facility SVC routine EQA01SVC. EQA01SVC is SVC 109 with extended function code 51.
Check the Debug Tool web site for any applicable service updates your system might require. If the problem persists, report the error message text, return code, and reason code to your IBM representative.
The ASMADOP module could not be loaded. Debugging via a Disassembly View cannot be supported.
The Debug Tool profile has been skipped because a more qualified profile has been found or an older, equally qualified, profile has been found.
Additional EQA9998I messages will follow. See the details of these additional messages for the appropriate response.
See details of message issued for appropriate response or indication of potential problem. Check the Debug Tool web site for any applicable service updates your system might require. If the problem persists, contact Debug Tool support.
Warning Message issued by Debug Tool Module
See details of message issued for appropriate response or indication of potential problem. Check the Debug Tool web site for any applicable service updates your system might require.