Rational Developer for System z, Version 7.6

Debug Tool messages

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:

I
An informational message calls attention to some aspect of a command response that might assist the programmer.
W
A warning message calls attention to a situation that might not be what is expected or to a situation that Debug Tool attempted to fix.
E
An error message describes an error that Debug Tool detected or cannot fix.
S
A severe error message describes an error that indicates a command referring to bad data, control blocks, program structure, or something similar.
U
An unrecoverable error message describes an error that prevents Debug Tool from continuing.

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.

EQA1000I
TEST (cu_name initialization):
Explanation:

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.

EQA1001I
The window configuration is configuration; the sequence of window is sequence
Explanation:

Used to display SCREEN as part of QUERY SCREEN.

EQA1002I
One window must be open at all times.
Explanation:

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.

EQA1003I
Target window is closed; FIND not performed.
Explanation:

The window specified in the FIND command is closed.

EQA1004I
Target window is closed; SIZE not performed.
Explanation:

The window specified in the SIZE command is closed.

EQA1005I
Target window is closed; SCROLL not performed.
Explanation:

The window specified in the SCROLL command is closed.

EQA1006I
Command
Explanation:

It is the character string 'Command' in the main panel command line.

EQA1007I
Step
Explanation:

It is the character string 'Step' in the main panel command line while stepping.

EQA1008I
Scroll
Explanation:

It is the character string 'Scroll' in the main panel command line.

EQA1009I
DBCS characters are not allowed.
Explanation:

The user entered DBCS characters in scroll, window object id, qualify, prefix, or panel input areas.

EQA1010I
More...
Explanation:

It is the character string 'More' in the main panel command line.

EQA1011I
Do you really want to terminate this session?
Explanation:

Asking for confirmation to terminate debug session. Enter Y for YES or N for NO.

EQA1012I
Enter Y for YES and N for NO
EQA1013I
Current command is incomplete, pending more input
Explanation:

This informational message is displayed while entering a block of commands, until the command block is closed by an END statement.

EQA1030I
PENDING:
Explanation:

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.

Programmer response:

Complete the command.

EQA1031I
The partially parsed command is:
Explanation:

The explanation of a command was requested or a command was determined to be in error.

Programmer response:

Determine the cause of the error and reenter the command.

EQA1032I
The next word can be one of:
Explanation:

This title line will be followed by message 1015.

EQA1033I
list items
Explanation:

This message is used to list all the items that can follow a partially parsed command.

Programmer response:

Reenter the acceptable part of the command and suffix it with one of the items in this list.

EQA1046I
The breakpoint-id breakpoint is replaced.
Explanation:

This alerts the user to the fact that a previous breakpoint action existed and was replaced.

Programmer response:

Verify that this was intended.

EQA1047I
The breakpoint-id breakpoint is replaced.
Explanation:

This alerts the user to the fact that a previous breakpoint action existed and was replaced.

Programmer response:

Verify that this was intended.

EQA1048I
Another generation of variable name is allocated.
Explanation:

An ALLOCATE occurred for a variable where an AT ALLOCATE breakpoint was established.

EQA1049I
The breakpoint-id breakpoint action is:
Explanation:

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.

EQA1050I
The breakpoint-id breakpoint has an EVERY value of number, a FROM value of number, and a TO value of number. The breakpoint action is:
Explanation:

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.

EQA1051I
The (deferred) breakpoint-id breakpoint action is:
Explanation:

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.

EQA1052I
The (deferred) breakpoint-id breakpoint has an EVERY value of number, a FROM value of number, and a TO value of number. The breakpoint action is:
Explanation:

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.

EQA1053I
The (disabled) breakpoint-id breakpoint action is:
Explanation:

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.

EQA1054I
The (disabled) breakpoint-id breakpoint has an EVERY value of number, a FROM value of number, and a TO value of number. The breakpoint action is:
Explanation:

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.

EQA1055I
The (disabled and deferred) breakpoint-id breakpoint action is:
Explanation:

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.

EQA1056I
The (disabled and deferred) breakpoint-id breakpoint has an EVERY value of number, a FROM value of number, and a TO value of number. The breakpoint action is:
Explanation:

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.

EQA1057I
AT stmt-number can be risky because the code for that statement might have been merged with that of another statement.
Explanation:

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.

EQA1058I
RUNTO is active at statement_id.
Explanation:

Display after LIST AT to reflect RUNTO position.

EQA1059I
The Entry breakpoint command for Load_Module_Name ::> CU Name has been deferred until the CU appears.
Explanation:

The compilation unit (program) that you specified could not be located by Debug Tool. The breakpoint is deferred until this CU is entered.

EQA1060I
The following suspended breakpoint exists: BP_name.
Explanation:

Used to display a command after LIST AT for suspended breakpoints only.

EQA1061I
The following suspended and disabled breakpoint exists: BP_name.
Explanation:

Used to display a command after LIST AT for suspended and disabled breakpoints only.

EQA1076I
Direction an unknown program.
Explanation:

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.

EQA1077I
Direction address Address in a PLANG NOTEST block.
Explanation:

The compile unit was compiled without the TEST option. The message is issued as a result of the LIST CALLS command.

EQA1078I
Direction Place in PLANG CU
Explanation:

CU name of the call chain. The message is issued as a result of the LIST CALLS command.

EQA1079I
Direction address Address in PLANG CU
Explanation:

The compile unit was compiled without the TEST option and is in the Debug Tool list of CUs.

EQA1086I
The previous declaration of variable name will be removed.
Explanation:

You declared a variable whose name is the same as a previously declared variable. This declaration overrides the previous one.

EQA1090I
The compiler data for program cu_name is
Explanation:

This is the title line for the DESCRIBE PROGRAM command.

EQA1091I
The program was compiled with the following options:
Explanation:

This is the first of a group of DESCRIBE PROGRAM messages.

EQA1092I
compile option
Explanation:

Used to display a compile option without parameters, for example, NOTEST.

EQA1093I
compile option (compile suboption)
Explanation:

Used to display a compile option with one parameter, for example, OPT.

EQA1094I
compile option (compile suboption, compile suboption)
Explanation:

Used to display a compile option with two parameters, for example, TEST.

EQA1095I
This program has no subblocks.
Explanation:

A DESCRIBE PROGRAM command refers to a program that is totally contained in one block.

EQA1096I
The subblocks in this program are nested as follows:
Explanation:

The names of the blocks contained by the program are displayed under this title line.

EQA1097I
space characters block name
Explanation:

The first insert controls the indentation while the second is the block name without qualification.

EQA1098I
The statement table has the short format.
Explanation:

The statement table is abbreviated such that no relationship between storage locations and statement identifications can be determined.

Programmer response:

If statement identifications are required, the program must be recompiled with different compiler parameters.

EQA1099I
The statement table has the NUMBER format.
Explanation:

The program named in the DESCRIBE PROGRAM command was compiled with GONUMBER assumed.

EQA1100I
The statement table has the STMT format.
Explanation:

The program named in the DESCRIBE PROGRAM command was compiled with GOSTMT assumed.

EQA1101I
file name
Explanation:

This message is used in listing items returned from the back end in response to the DESCRIBE ENVIRONMENT command.

EQA1102I
ATTRIBUTES for variable name
Explanation:

Text of a DESCRIBE ATTRIBUTES message.

EQA1103I
Its address is address
Explanation:

Text of a DESCRIBE ATTRIBUTES message.

EQA1104I
Compiler: Compiler version
Explanation:

Indicate compiler version for DESCRIBE CU.

EQA1105I
Its length is length
Explanation:

Text of a DESCRIBE ATTRIBUTES message.

EQA1106I
Programming language COBOL does not return information for DESCRIBE ENVIRONMENT
Explanation:

COBOL run-time library does not return information to support this command.

EQA1107I
There are no open files.
Explanation:

This is issued in response to DESCRIBE ENVIRONMENT if no open files are detected.

EQA1108I
The following conditions are enabled:
Explanation:

This is the header message issued in response to DESCRIBE ENVIRONMENT before issuing the list of enabled conditions.

EQA1109I
The following conditions are disabled:
Explanation:

This is the header message issued in response to DESCRIBE ENVIRONMENT before issuing the list of disabled conditions.

EQA1110I
This program has no Statement Table.
Explanation:

This message is used for the DESCRIBE CU command. If a CU was compiled with NOTEST, no statement table was generated.

EQA1111I
Attributes for names in block block name
Explanation:

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.

EQA1112I
variable name and/or attributes
Explanation:

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

EQA1114I
Currently open files are:
Explanation:

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.

EQA1115I
The program has insufficient compilation information for the DESCRIBE CU command.
Explanation:

This program has insufficient information. It might be compiled without the TEST option.

EQA1116I
Common Language Environment math library is being used
Explanation:

This is the response for the DESCRIBE ENVIRONMENT command when the Language Environment math library is being used.

EQA1117I
PL/I Math library is being used
Explanation:

This is the response for the DESCRIBE ENVIRONMENT command when the PL/I math library is being used.

EQA1118I
compile option (compile suboption, compile suboption, compile suboption)
Explanation:

Used to display a compile option with three parameters, for example TEST(ALL,SYM,SEPARATE)

EQA1119I
Current allocations:
Explanation:

Heading line for DESCRIBE ALLOCATIONS output.

EQA1120I
VOLUME CAT DISP OPEN DDNAME DSNAME
Explanation:

Header for DESCRIBE ALLOCATIONS output.

EQA1121I
------ --- ---------- ---- -------- ------------------------------ --------------
Explanation:

Header for DESCRIBE ALLOCATIONS output.

EQA1122I
allocation description
Explanation:

Description of the current allocation.

EQA1123I
Insufficient storage is available to process command.
Explanation:

There was not enough main memory available to process the command.

EQA1124I
Return code return code /reason code reason code from macro name macro invocation.
Explanation:

During the processing of the command, the indicated macro invocation failed with the indicated return and reason codes.

EQA1125I
ALLOCATE / FREE failed. Return code return code /reason code reason code from dynamic allocation.
Explanation:

The dynamic allocation failed with the indicated return and reason codes.

EQA1126I
ALLOCATE / FREE failed. Dataset dsname was not found.
Explanation:

The indicated data set was not cataloged or was not found on the volume on which it was cataloged.

EQA1127I
ALLOCATE / FREE failed. The FILE specified was already in use (ALLOCATE) or was not allocated (FREE).
Explanation:

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.

EQA1128I
ALLOCATE / FREE failed. Dataset dsame is already allocated to another JOB or USER.
Explanation:

The specified data set is already allocated in such a way that it cannot be allocated with the specified disposition.

EQA1129I
Command not supported on the current platform.
Explanation:

The command is not supported in the current environment (such as CICS®)

EQA1130I
The EQALANGX debug data also contains data for the following CUs:
Explanation:

This is the header used to display the additional CSECT's included in the EQALANGX data for the current CU.

EQA1131I
CU name CU language
Explanation:

Used to display CSECT's also included in the EQALANGX data for the current CU.

EQA1132I
EQALANGX version for this CU: EQALANGX_version
Explanation:

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.

EQA1133I
Current EQALANGX version: EQALANGX_version
Explanation:

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.

EQA1134I
The INCLUDE files in this program are indexed as follows: INCLUDE_file_names.
Explanation:

The names of the INCLUDE files contained by the program are displayed under this title line.

EQA1139I
***** PREVIOUS STATEMENT *****
Explanation:

Automonitor Previous Statement area in the Monitor window.

EQA1140I
character
Explanation:

This message is used to produce output for LIST ( ... ).

EQA1141I
expression name = expression value
Explanation:

This message is used to produce output for LIST TITLED ( ... ) when an expression is a scalar.

EQA1142I
expression element
Explanation:

This insert is used for naming the expression for expression element.

EQA1143I
>>> EXPRESSION ANALYSIS <<<
Explanation:

First line of output from the ANALYZE EXPRESSION command.

EQA1144I
alignment spaces. It is a bit field with offset bit offset.
Explanation:

Text of a DESCRIBE ATTRIBUTES message.

EQA1145I
Its Offset is offset.
Explanation:

Text of a DESCRIBE ATTRIBUTES message.

EQA1146I
column elements
Explanation:

This message is used to produce a columned list. For example, it is used to format the response to LIST STATEMENT NUMBERS.

EQA1147I
name
Explanation:

The name of a variable that satisfies a LIST NAMES request is displayed.

EQA1148I
name structure
Explanation:

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.

EQA1149I
name in parent name
Explanation:

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.

EQA1150I
name structure in parent name
Explanation:

The name of a variable that satisfies a LIST NAMES request is displayed. It is an aggregate contained within another aggregate.

EQA1151I
The following names are known in block block name
Explanation:

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.

EQA1152I
The following session names are known
Explanation:

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.

EQA1153I
The following names with pattern pattern are known in block name
Explanation:

This title line precedes the list of variable names that satisfy the pattern in a LIST NAMES command.

EQA1154I
The following session names with pattern pattern are known
Explanation:

This title line precedes the list of session names that satisfy the pattern in a LIST NAMES command.

EQA1155I
The following CUs are known in Load Module name:
Explanation:

This title line precedes a list of compile unit names for noninitial load modules in a LIST NAMES CUS command.

EQA1156I
The following CUs with pattern pattern are known in Load Module name
Explanation:

This title line precedes a list of compile unit names for noninitial load modules that satisfy the pattern in a LIST NAMES CUS command.

EQA1157I
There are no CUs with pattern pattern in Load Module name.
Explanation:

This line appears when no compile unit satisfied the pattern in a LIST NAMES CUS command for noninitial load modules.

EQA1158I
The following CUs have pattern pattern
Explanation:

This title line precedes a list of compile unit names for an initial load module in a LIST NAMES CUS command.

EQA1159I
There are no CUs with pattern pattern.
Explanation:

This line appears when no compile unit satisfied the pattern in a LIST NAMES CUS command for an initial load module.

EQA1160I
There are no Procedures with pattern pattern.
Explanation:

This line appears when no Procedures satisfied the pattern in a LIST NAMES PROCEDURES command.

EQA1161I
The following Procedures have pattern pattern:
Explanation:

This title line precedes a list of Procedure names for a LIST NAMES PROCEDURES command.

EQA1162I
There are no names in block block name
Explanation:

The LIST NAMES command found no variables in the specified block.

EQA1163I
There are no session names.
Explanation:

The LIST NAMES command found no variables that had been declared in the session for the current programming language.

EQA1164I
There are no names with pattern pattern in block name.
Explanation:

The LIST NAMES command found named variables in the named block but none of the names satisfied the pattern.

EQA1165I
There are no session names with pattern pattern.
Explanation:

The LIST NAMES command found named variables that had been declared in the session but none of the names satisfied the pattern.

EQA1166I
There are no known session procedures.
Explanation:

A LIST NAMES PROCEDURES was issued but no session procedures exist.

EQA1167I
register name = register value
Explanation:

Used when listing registers.

EQA1168I
No LIST STORAGE data is available for the requested reference or address.
Explanation:

The given reference or address is invalid.

EQA1169I
No frequency data is available
Explanation:

This message is issued upon failure to find frequency information.

EQA1170I
Frequency of verb executions in cu_name
Explanation:

This is the header produced by the LIST FREQUENCY command.

EQA1171I
character string = count
Explanation:

This is the frequency count produced by the LIST FREQUENCY command.

EQA1172I
TOTAL VERBS= total statements, TOTAL VERBS EXECUTED= total statements executed, PERCENT EXECUTED= percent executed
Explanation:

This is the trailer produced by the LIST FREQUENCY command.

EQA1173I
(history number) ENTRY hook for cu_name
Explanation:

This is a LIST HISTORY message.

EQA1174I
(history number) ENTRY hook for block block name in cu_name
Explanation:

This is a LIST HISTORY message.

EQA1175I
(history number) EXIT hook for cu_name
Explanation:

This is a LIST HISTORY message.

EQA1176I
(history number) EXIT hook for block block name in cu_name
Explanation:

This is a LIST HISTORY message.

EQA1177I
(history number) STATEMENT hook at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1178I
(history number) PATH hook at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1179I
(history number) Before CALL hook at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1180I
(history number) CALL CEETEST at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1181I
(history number) Waiting for program input from ddname
Explanation:

This is a LIST HISTORY message.

EQA1182I
(history number) LOAD occurred at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1183I
(history number) DELETE occurred at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1184I
(history number) condition name raised at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1185I
(history number) LABEL hook at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1186I
Unable to display value of variable name. Use LIST (variable name) for further details
Explanation:

This is used to inform the user that for some reason one of the variables cannot be displayed for LIST TITLED.

EQA1187I
There are no data members in the requested object.
Explanation:

The requested object does not contain any data members. It contains only methods.

EQA1188I
(history number) DATE hook at statement cu_name :> statement_id
Explanation:

This is a LIST HISTORY message.

EQA1189I
There are no CUs compiled with debug data. To see the CU names, issue SET DISASSEMBLY ON before LIST command.
Explanation:

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

EQA1190I
Unable to update the requested location.
Explanation:

The given reference or address is invalid.

EQA1191I
The length of target and source must be equal.
Explanation:

The number of bytes to be altered must be equal the length of source.

EQA1192I
The number of bytes to be altered is too large.
Explanation:

A maximum of 8 bytes of storage can be change when source is a hexadecimal number, and 4 bytes when source is integer number.

EQA1193I
There are no variables in section_name.
Explanation:

The LIST TITLED command found no variables that had been declared in the section.

EQA1194I
The following variables are known in section section_name
Explanation:

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.

EQA1226I
The EQUATE named EQUATE name is replaced.
Explanation:

This alerts the user to the fact that a previous EQUATE existed and was replaced.

Programmer response:

Verify that this was intended.

EQA1227I
The following EQUATE definitions are in effect:
Explanation:

This is the header for the QUERY EQUATES command.

EQA1228I
EQUATE identifier = "EQUATE string"
Explanation:

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.

EQA1229I
The program is currently exiting block block name.
Explanation:

Shows the bearings in an interrupted program.

EQA1230I
The program is currently executing prolog code for block name.
Explanation:

Shows the bearings in an interrupted program.

EQA1231I
You are executing commands within a __ctest function.
Explanation:

Shows the bearings in an interrupted program.

EQA1232I
You are executing commands within a CEETEST function.
Explanation:

Shows the bearings in an interrupted program.

EQA1233I
The established MONITOR commands are:
Explanation:

This is the header produced by LIST MONITOR.

EQA1234I
LanguageCode MONITOR monitor number monitor type
Explanation:

This is the line produced by LIST MONITOR before each command is displayed.

EQA1235I
The command for MONITOR monitor number monitor type is:
Explanation:

This is the header produced by LIST MONITOR monitor number.

EQA1236I
The MONITOR monitor number command is replaced.
Explanation:

This is a safety message: the user is reminded that a MONITOR command is replacing an old one.

EQA1237I
The current qualification is block name.
Explanation:

Shows the current point of view.

EQA1238I
The current location is cu_name :> statement id.
Explanation:

Shows the place where the program was interrupted.

EQA1239I
The program is currently entering block block name.
Explanation:

Shows the bearings in an interrupted program.

EQA1240I
You are executing commands within a CALL PLITEST statement.
Explanation:

Shows the bearings in an interrupted program.

EQA1241I
You are executing commands from the run-time command-list.
Explanation:

Shows the bearings in an interrupted program.

EQA1242I
You are executing commands in the breakpoint-id breakpoint.
Explanation:

Shows the bearings in an interrupted program.

EQA1243I
The setting of SET-command object is status
Explanation:

The status of the object of a SET command is displayed when QUERYed individually.

EQA1244I
SET-command object status
Explanation:

The status of the object of a SET command is displayed when issued as part of QUERY SET.

EQA1245I
The current settings are:
Explanation:

This is the header for QUERY SET.

EQA1246I
PFKEY string command
Explanation:

Used to display PFKEYS as part of QUERY PKFEYS.

EQA1247I
COLOR color hilight intensity colored area
Explanation:

Used to display SCREEN as part of QUERY SCREEN.

EQA1248I
You were prompted because STEP ended.
Explanation:

Shows the bearings in an interrupted program.

EQA1249I
character string - The QUERY source setting file name is not available.
Explanation:

The source listing name is not available. The source listing was not required or set before this command.

EQA1250I
SET INTERCEPT is already set on or off for FILE filename.
Explanation:

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.

EQA1251I
You were prompted because RUNTO ended.
Explanation:

The program has stopped because RUNTO cursor/statement command reached the cursor location or pointed statement number.

EQA1252I
********** AUTOMONITOR **********
Explanation:

Header for the automonitor area in the monitor window.

EQA1253I
You were prompted because Playback replay mode ended.
Explanation:

A PLAYBACK STOP command was processed, which terminated Playback replay mode.

EQA1254I
The LOADDEBUGDATA command was not processed.
Explanation:

An error occurred so the LLD command was not processed.

EQA1255E
The CU specified for the LOADDEBUGDATA command is not a disassembly CU.
Explanation:

Only a disassembly CU can be identified as assembler CU.

EQA1256E
An error occurred while attempting to load the debug (EQALANGX) file for a specified CU.
Explanation:

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.

EQA1257E
The MONITOR parameter HEX or DEFAULT is valid only for LIST reference command.
Explanation:

MONITOR n HEX or MONITOR n DEFAULT are valid only if n represents LIST reference command.

EQA1258E
There is no MONITOR LIST command with the referenced integer.
Explanation:

MONITOR n HEX or MONITOR n DEFAULT are valid only if n represents valid LIST command.

EQA1259I
The LOADDEBUGDATA command for CU_name has been deferred until the CU appears.
Explanation:

The indicated CU is not currently known to Debug Tool. The LOADDEBUGDATA will be executed when the CU appears in a loaded module.

EQA1260I
The CU specified for the LOADDEBUGDATA command is already an assembler or non-Language Environment COBOL CU.
Explanation:

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.

EQA1261I
The requested view is already active.
Explanation:

A CHANGEVIEW command requested a view that is already the active view for the currently qualified CU.

EQA1262I
The requested view is not supported by the currently qualified CU.
Explanation:

A CHANGEVIEW command requested a view that not supported by the programming language of the currently qualified CU.

EQA1263W
Breakpoints have been set on statements that would be suppressed in the requested view. The view is not changed.
Explanation:

Debug Tool does not currently support changing to a view that would suppress statements that currently contain breakpoints.

EQA1264I
The current view is Current_View.
Explanation:

This message is displayed in response to the QUERY CURRENT VIEW command.

EQA1265E
Command failed due to an internal communications error.
Explanation:

The previous command could not be completed because of an internal communications error.

EQA1266I
You were prompted because JUMPTO ended.
Explanation:

The program has stopped because JUMPTO command reached the cursor location or pointed statement number.

EQA1267I
***** Previous Statement CU-name :> statement id *****
Explanation:

Automonitor Previous Statement area in the monitor window.

EQA1268I
The previous statement is out of scope. No variables can be displayed.
Explanation:

The data from the statement in which Debug Tool last had control cannot be resolved because the statement is no longer in scope.

EQA1269I
The previous location is CU-name :> statement id .
Explanation:

Shows the place in the program where the program was previously interrupted.

EQA1270I
***** AUTOMONITOR - PREVIOUS CU-name :> statement id *****
Explanation:

Header for the automonitor area in the Monitor window when PREVIOUS is specified.

EQA1271I
The program previously entered block block name.
Explanation:

Shows the location where Debug Tool previously had control.

EQA1272I
The program previously exited block block name.
Explanation:

Shows the bearings in an interrupted program.

EQA1273I
The program previously executed prolog code for block name.
Explanation:

Shows the bearings in an interrupted program.

EQA1274I
***** AUTOMONITOR CU-name :> statement id *****
Explanation:

Header with location for the automonitor area in the monitor window.

EQA1275I
********** AUTOMONITOR - PREVIOUS **********
Explanation:

Header without location information for the automonitor area in the monitor window when PREVIOUS is specified. Used when no location information is available.

EQA1276I
TEST:
Explanation:

Debug Tool is ready to accept a command from the terminal.

Programmer response:

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.

EQA1277I
The USE file is empty.
Explanation:

Debug Tool tried to read commands from an empty USE file. If unintentional, this could be because of an incorrect file specification.

Programmer response:

Correct the file specification and retry.

EQA1278I
alignment spaces command part
Explanation:

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.

EQA1279I
TEST (cu_name:> statement_id):
Explanation:

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.

Programmer response:

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.

EQA1280I
TEST (cu_name ENTRY):
Explanation:

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.

Programmer response:

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.

EQA1281I
TEST (cu_name:> block name ENTRY):
Explanation:

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.

Programmer response:

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.

EQA1282I
TEST (cu_name EXIT):
Explanation:

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.

Programmer response:

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.

EQA1283I
TEST (cu_name:> block name EXIT):
Explanation:

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.

Programmer response:

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.

EQA1284I
TEST (Application program has terminated):
Explanation:

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.

Programmer response:

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.

EQA1285I
TEST (label-name LABEL);
Explanation:

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.

Programmer response:

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.

EQA1286I
(Application program has terminated)
Explanation:

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.

EQA1287I
Unknown
Explanation:

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.

EQA1288I
initialization
Explanation:

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.

EQA1289I
ddname: program output
Explanation:

Displays program output with the ddname preceding the output.

EQA1290I
The program is waiting for input from ddname
Explanation:

Debug Tool has gained control because the program is waiting for input.

EQA1291I
Use the INPUT command to enter recsize characters for the intercepted fixed-format file.
Explanation:

Prompts you for intercepted input of fixed-format file.

EQA1292I
Use the INPUT command to enter up to a maximum of recsize characters for the intercepted variable-format file.
Explanation:

Prompt user for intercepted input of variable-formatted file.

EQA1293I
TEST (cu-name):
Explanation:

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.

Programmer response:

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.

EQA1294I
The suspended LOCAL MONITOR commands are:
Explanation:

This is the header produced by LIST MONITOR when suspended local monitors are present.

EQA1301I
A ABEND code ABEND occurred.
Explanation:

A system or user ABEND has been detected by Debug Tool.

EQA1306I
You were prompted because the CONDITION name condition was raised in your program.
Programmer response:

The program has stopped running due to the occurrence of the named condition.

EQA1307I
You were prompted because an ATTENTION interrupt occurred.
Explanation:

The attention request from the terminal was recognized and the Debug Tool was given control.

EQA1308I
You were prompted because a condition was raised in your program.
Explanation:

The program stopped running due to the occurrence of a condition whose name is unknown.

EQA1309I
CONDITION name is a severity or class SEVERITY code condition.
Explanation:

The condition named is described by its severity level or class code. See the z/OS Language Environment Programming Guide.

EQA1316I
Block block name contains the following statements:
Explanation:

This message precedes the message that identifies all statement numbers in the block.

EQA1317I
block level space characters block name
Explanation:

This message is used instead of EQA1097I when the number of block levels is greater than the indentation allowed.

EQA1318I
space_characters INCLUDE_file_name index_number
Explanation:

The first insert controls the indentation, the second is the INCLUDE file name, and the third insert is the source index block level.

EQA1320E
A trigraph was found when the FIND column specifications are not 1 to *.
Explanation:

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.

EQA1321E
The SET FIND BOUNDS column specifications are invalid.
Explanation:

The left column must be less than or equal to the right column.

EQA1322E
The FIND column specification(s) is invalid.
Explanation:

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.

EQA1323E
The FIND argument will not fit between the specific columns.
Explanation:

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.

EQA1324I
Bottom of data reached.
Explanation:

FIND has reached the bottom of the data without finding the string being searched for.

EQA1325I
Top of data reached.
Explanation:

FIND has reached the top of the data without finding the string being searched for.

EQA1326I
character string
Explanation:

This message is used to display the results of a command that the user has entered, such as LIST STORAGE.

EQA1327I
character string character string
Explanation:

This message is used to display the results of a command that the user has entered.

EQA1329I
The procedure named procedure name has the form:
Explanation:

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.

EQA1330I
You are not currently within a procedure.
Explanation:

The LIST PROCEDURE command was issued without naming a session procedure and the current command context is outside of a session procedure.

Programmer response:

Verify the request. Reenter the command and name a specific procedure if necessary.

EQA1331I
The RETRIEVE queue is empty.
Explanation:

There are no entries in the retrieve queue.

EQA1332I
FIND has continued from top of area.
Explanation:

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.

EQA1333I
The string was found.
Explanation:

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.

EQA1334I
The operating system has generated the following message:
Explanation:

The Operating System can issue its own messages. These are relayed to the user.

EQA1335I
OS message
Explanation:

The operating system can issue its own messages. These are relayed to the user.

EQA1336I
IBM Debug Tool Version 9 Release 1 Mod 0 time stamp 5655-U27: Copyright IBM Corp. 1992, 2008
Explanation:

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.

EQA1337I
Its address is address and its length is length
Explanation:

Text of a DESCRIBE ATTRIBUTES message for PL/I.

EQA1338I
Its offset is offset and its length is length
Explanation:

Text of a DESCRIBE ATTRIBUTES message for PL/I.

EQA1339I
Its length is length
Explanation:

Text of a DESCRIBE ATTRIBUTES message for PL/I.

EQA1340I
Its address is address
Explanation:

Text of a DESCRIBE ATTRIBUTES message for PL/I.

EQA1341I
Its Offset is offset
Explanation:

Text of a DESCRIBE ATTRIBUTES message for PL/I.

EQA1342I
ATTRIBUTES for variable name variable type
Explanation:

Text of a DESCRIBE ATTRIBUTES message for PL/I.

EQA1343I
Presently not in accessible storage
Explanation:

The requested variable cannot be accessed.

EQA1344I
The OTHERWISE statement would have been executed but was not present
Explanation:

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.

EQA1351I
PLAYBACK statement sequence error. PLAYBACK found stmt was found before PLAYBACK req stmt. Statement ignored.
Explanation:

Playback was not is the proper state to process the specified statement. The statement is ignored.

EQA1352I
PLAYBACK statement sequence error. PLAYBACK found stmt was found after PLAYBACK req stmt. Statement ignored.
Explanation:

Playback was not is the proper state to process the specified statement. The statement is ignored.

EQA1353I
Not enough memory available for PLAYBACK data collection. Increase memory specification on the PLAYBACK ENABLE command.
Explanation:

Not enough memory was available for Playback data collection. Increase the amount of memory available to Playback on the PLAYBACK ENABLE command.

EQA1354I
Return code RC from from PLAYBACK run-time API API name. PLAYBACK disabled.
Explanation:

The specified return code indicated an error condition detected by the Playback run-time API. Playback is disabled.

Programmer response:

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

EQA1355I
The current status of PLAYBACK is: PB insert1, PB insert2, PB insert3, PB insert4.
Explanation:

This message is issued in response to the QUERY PLAYBACK command.

EQA1356I
PLAYBACK START is not active. You are not in PLAYBACK replay mode.
Explanation:

This message is issued in response to the QUERY PLAYBACK LOCATION command when PLAYBACK replay is not active.

EQA1357I
PLAYBACK replay mode is active with PB Data. The direction is PB direction.
Explanation:

This message is issued in response to the QUERY PLAYBACK LOCATION command when PLAYBACK replay is active.

EQA1358I
The current location in the PLAYBACK buffer is PB location.
Explanation:

This message is issued in response to the QUERY PLAYBACK LOCATION command when PLAYBACK replay is active.

EQA1359I
Command is not allowed in PLAYBACK replay mode.
Explanation:

The previous command is not supported after PLAYBACK START.

EQA1360I
Command is not allowed in PLAYBACK NODATA replay mode.
Explanation:

The previous command is not supported after PLAYBACK START.

EQA1361I
PLAYBACK command not processed.
Explanation:

The previous command was ignored because of errors that were indicated by previous messages.

EQA1362I
There is no data in the PLAYBACK buffer. PLAYBACK START command rejected.
Explanation:

A PLAYBACK START command was entered but the PLAYBACK buffer is empty. The PLAYBACK START command is not processed.

EQA1363W
PLAYBACK replay has reached the first record in the PLAYBACK buffer. You must enter PLAYBACK FORWARD or PLAYBACK STOP.
Explanation:

Playback replay has reached the first record in the buffer. You cannot move farther backward.

EQA1364W
PLAYBACK replay has reached the last record in the PLAYBACK buffer. You must enter PLAYBACK BACKWARD or PLAYBACK STOP.
Explanation:

Playback replay has reached the last record in the buffer. You cannot move farther forward.

EQA1365I
PLAYBACK replay has stepped over one or more deleted compile units or compile units for which PLAYBACK has been disabled.
Explanation:

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.

EQA1366I
PLAYBACK START is not allowed when AUTOMONITOR options BOTH or PREVIOUS are in effect.
Explanation:

Playback cannot be started while AUTOMONITOR with option BOTH or AUTOMONITOR with option PREVIOUS are in effect.

EQA1367I
AUTOMONITOR options BOTH or PREVIOUS are not allowed while PLAYBACK is started.
Explanation:

AUTOMONITOR with option PREVIOUS or AUTOMONITOR with option BOTH is not allowed while PLAYBACK is started.

EQA1367I
Previous location is now out of scope. No variables can be displayed.
Explanation:

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.

EQA1370I
The following name_type names are currently exclude_or_included by user_or_debugtool.
Explanation:

This message precedes the output of the NAMES QUERY command and indicates the type of names that follow this message.

EQA1371I
name
Explanation:

This message lists the names output by the NAMES QUERY command.

EQA1372I
There are no name_type names currently exclude_or_included by user_or_debugtool.
Explanation:

This message is issued by the NAMES QUERY command when there is no data to be displayed.

EQA1373E
A pattern of "*" is invalid.
Explanation:

The NAMES EXCLUDE command does not allow a pattern of "*".

EQA1376I
Channel_Tag Channel_Name
Explanation:

This message contains the output from the DESCRIBE CHANNEL command.

EQA1377I
A CICS Storage Violation has not been detected.
Explanation:

Debug Tool did not detect any storage violation.

EQA1378W
A CICS Storage Violation has been detected. The leading/trailing check zone associated with the storage that starts at Hex_Str StgV_Address Quote_Str for a length of StgV_Length has been damaged.
Explanation:

Debug Tool detected a storage violation.

EQA1379I
No MEMORY data is available for the requested reference or address.
Explanation:

The given reference or address is invalid.

EQA1387I
DTCN Pattern-match breakpoint disabled for programs:
Explanation:

This is the title line for the LIST DTCN command.

EQA1388I
CADP Pattern-match breakpoint disabled for:
Explanation:

This is the title line for the LIST CADP command.

EQA1389I
program name
Explanation:

This message lists the program names output by the List DTCN command.

EQA1390I
Program = program name CU = compile_unit_name
Explanation:

This message lists the program and compile unit names output by the LIST CADP command.

EQA1391I
This program and/or compile unit is not in the pattern-match breakpoint list.
Explanation:

The Enable DTCN|CADP command is not allowed since this particular program and/or compile unit is not in the pattern-match breakpoint list.

EQA1392I
The pattern-match breakpoint list is empty.
Explanation:

There are no entries in the pattern-match breakpoint list.

EQA1393I
The program/pattern dtcn_pgm_name is not in the DTCN pattern-match breakpoint list.
Explanation:

The Enable DTCN command is not allowed for this particular program and/or compile unit.

EQA1400E
The value entered is invalid.
Explanation:

The user entered an invalid value.

EQA1401E
The command entered is not a valid panel sub-command.
Explanation:

The user entered a command not recognized by panel processor.

EQA1402E
Each window must have unique letters of L, M, S, and E.
Explanation:

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.

EQA1403E
Invalid prefix command was entered.
Explanation:

The user entered an invalid prefix command.

EQA1404E
Search target not found.
Explanation:

The target for the search command was not found.

EQA1405E
No previous search arguments exist; find not performed.
Explanation:

A FIND command was issued without an argument. Since the FIND command had not been issued previously, Debug Tool had nothing to search for.

EQA1406E
Invalid window ID.
Explanation:

The window header field contains an invalid window ID. Valid window IDs are SOURCE, MONITOR, and LOG.

EQA1407E
Invalid scroll amount entered.
Explanation:

Scroll field contains an invalid scroll amount.

EQA1408E
Duplicate window ID
Explanation:

More than one window header field contains the same window id.

EQA1410E
Variable_name is a LABEL on a modifiable instruction. No AT commands can be issued against it.
Explanation:

The specified label is on an instruction that is modified at some point in the program. Breakpoints cannot be set on such an instruction.

EQA1411E
Invalid variable number was entered.
Explanation:

The user entered an invalid variable.

EQA1412E
Prefix command not supported for current programming language.
Explanation:

Prefix command not supported for current programming language.

EQA1413E
There are no variables in the statement to display.
Explanation:

The specified prefix command is on the statement with no variables.

EQA1414E
Prefix command was entered on invalid statement.
Explanation:

The user entered prefix command on invalid line.

EQA1415E
Specified variable number is too big.
Explanation:

The user entered a variable number that exceeds the amount of variables in that statement.

EQA1416E
Multiple invalid prefix commands. For details, reenter commands individually.
Explanation:

More then one invalid prefix commands. To see details you must reenter the invalid command one at a time.

EQA1417E
Invalid line for prefix command. Line must be in the active block.
Explanation:

The user entered a prefix command on a line that is contained in a block that is not currently active.

EQA1430W
The EQUATE named EQUATE name was has not been established.
Explanation:

CLEAR EQUATE <name> was attempted for an EQUATE name that has not been established.

Programmer response:

For a list of the current EQUATES definitions, issue QUERY EQUATES.

EQA1431W
There are no EQUATE definitions in effect.
Explanation:

CLEAR EQUATE or QUERY EQUATES was issued but there are no EQUATE definitions.

EQA1432E
function is not supported.
Explanation:

Language/Country is not supported.

Programmer response:

Set National Language and Country.

EQA1433E
Switching to the programming language language-name is invalid because there are no language-name compilation units in the initial load module.
Explanation:

A SET PROGRAMMING LANGUAGE command was issued, but the initial load module contains no compilation units compiled in the language specified (or implied).

EQA1434E
Error in setting debug name to ?????????.
Explanation:

Refer to the maximum number of CUs allowed for debugging.

EQA1435E
Error in setting name.
Explanation:

This is a generic message for SET command errors.

EQA1436W
SET EXECUTE is OFF -- command will not be executed.
Explanation:

The command was parsed but not executed.

EQA1437W
SET DYNDEBUG can not be executed at this time. SET DYNDEBUG can only be executed at the beginning of a debugging session, before any STEP or GO commands. The DYNDEBUG status has not been changed.
Explanation:

The Dynamic Debug facility setting can not be changed to ON in the middle of a debugging session.

EQA1438W
SET DYNDEBUG can not be executed at this time. SET DYNDEBUG can only be executed at the beginning of a debugging session, before any STEP or GO commands. The DYNDEBUG status has not been changed.
Explanation:

The Dynamic Debug facility setting can not be changed to OFF in the middle of a debugging session.

EQA1439E
This CU is not AUTOMONITOR capable for expressions.
Explanation:

The CU is not AUTOMONITOR capable.

Programmer response:

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.

EQA1440E
SET AUTOMONITOR ON is not valid for this CU. Use the SET AUTOMONITOR ON LOG command to activate the statement trace function.
Explanation:

The current CU is not AUTOMONITOR capable. SET AUTOMONITOR ON LOG will activate the statement trace.

Programmer response:

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.

EQA1441I
The statement trace is now active. Use the SET AUTOMONITOR OFF command to deactivate the statement trace.
Explanation:

The statement trace is active for a CU that is not AUTOMONITOR capable.

EQA1442E
DYNDEBUG cannot be SET OFF when running without the Language Environment run-time.
Explanation:

The Dynamic Debug facility cannot be deactivated while running without the Language Environment® run-time.

EQA1443I
There are no INTERCEPT specifications in effect.
Explanation:

QUERY INTERCEPT was issued but there are no INTERCEPT specifications active.

EQA1444I
For this command to be effective, SETTINGS must be saved with SET RESTORE SETTINGS AUTO in effect.
Explanation:

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.

EQA1449E
The command is not supported with PL/I. Use PL/I built-in function HEX to obtain hexadecimal values.
Explanation:

%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).

EQA1450E
Unable to display the result from expression evaluation
Explanation:

The entire result from the expression evaluation cannot be displayed; for example, the array is too large.

EQA1451E
operand contains incompatible data type.
Explanation:

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.

EQA1452E
argument name is not a valid argument.
Explanation:

The specified argument is not valid.

EQA1453E
The number of arguments is not correct.
Explanation:

There are either too many or too few arguments specified.

EQA1454E
operand name is not a valid operand.
Explanation:

The specified operand is undefined or is an invalid literal.

EQA1455E
An unsupported operator/operand is specified.
Explanation:

An operator or an operand was not understood, and therefore was not processed. Examples of when this message is issued when using COBOL include:

EQA1456S
The variable variable name is undefined or is incorrectly qualified.
Explanation:

The named variable could not be located or undefined.

Programmer response:

You need to qualify to a different block in order to locate the variable.

EQA1457E
The exponent exponent contains a decimal point.
Explanation:

This feature is not supported. No decimal point is allowed in exponent specification.

EQA1458E
The address of data item has been determined to be invalid.
Explanation:

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.

EQA1459E
literal string is not a valid literal.
Explanation:

The combination of characters specified for the literal is not a valid literal.

EQA1460E
Operand operand name should be numeric.
Explanation:

A nonnumeric operand was found where a numeric operand was expected.

EQA1461E
Invalid data for data item is found.
Explanation:

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.

EQA1462E
Invalid sign for data item is found.
Explanation:

The sign position of a signed data item contains an invalid sign. The item might not have been initialized.

EQA1463E
A divisor of 0 is detected in a divide operation.
Explanation:

The expression contains a divide operation where the divisor was determined to be zero.

EQA1464E
data item is used as a receiver but it is not a data name.
Explanation:

The target of an assignment is not valid.

EQA1465E
The TGT for a program is not available.
Explanation:

The program might have been deleted or canceled.

EQA1466E
data item is not a valid subscript or index.
Explanation:

The subscript or index might be out of range or an ODO variable might not be initialized.

EQA1467E
No subscript or index is allowed for data item
Explanation:

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.

EQA1468E
Missing subscripts or indexes for data item
Explanation:

A data item defined as a table was referenced without specifying any subscripts or indexes. The reference is not allowed.

EQA1469E
Incorrect number of subscripts or indexes for data item
Explanation:

A data item defined as a table was referenced with incorrect number of subscripts or indexes. The reference is not allowed.

EQA1470E
Incorrect length specification for data item
Explanation:

The length of a data item is incorrect for the definition, usually due to a faulty ODO object.

EQA1471E
Incorrect value for ODO variable data item
Explanation:

The ODO variable might not have been initialized, or the current value is out of range.

EQA1472E
Invalid specification of reference modification.
Explanation:

The specification of the reference modification is not consonant with the length field.

EQA1473E
Invalid zero value for data item
Explanation:

The value of a data item is zero. A zero is invalid in the current context.

EQA1474E
procedure name was found where a data name was expected.
Explanation:

Invalid name is specified for a data item.

EQA1475E
data item is an invalid qualifier in a qualified reference.
Explanation:

A qualified reference is invalid. One or more qualifiers might be undefined or not in the same structure as the desired data item.

EQA1476E
Too many qualifiers in a qualified reference.
Explanation:

The qualified reference contains more than the legal number of qualifiers.

EQA1477E
DATA DIVISION does not contain any entries.
Explanation:

There is no data to display for a LIST * request because the DATA DIVISION does not contain any entries.

EQA1478E
No status available for sort file sort file
Explanation:

Status was requested for a sort file. There is never a status available for a sort file.

EQA1479E
Unable to locate any TGT. An attempt to locate any TGT failed.
Explanation:

No COBOL program exists in TEST mode.

EQA1480E
operand name is an invalid operand for SET command.
Explanation:

The operands for a SET command are incorrect. At least one of the operands must be index name.

EQA1481E
Too many digits for the exponent of floating point literal data item
Explanation:

The exponent specified for a floating-point literal contains too many digits.

EQA1482E
command name command is terminated due to an error in processing.
Explanation:

The command is terminated unsuccessfully because an error occurred during processing.

EQA1483E
reference could not be formatted for display.
Explanation:

The requested data item could not be displayed due to an error in locating or formatting the data item.

EQA1484E
Resources (for example, heap storage) are not available for processing and the command is terminated unsuccessfully.
Explanation:

The command could not be completed due to inadequate resources.

Programmer response:

Increase the region size and restart Debug Tool.

EQA1485E
The command is not supported because the CU is compiled with incorrect compiler options.
Explanation:

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.

EQA1486E
variable name is presently not in accessible storage.
Explanation:

The variable might be CONTROLLED or AUTOMATIC and does not yet exist.

EQA1487S
The number of dimensions for variable name is number -- but number have been specified.
Explanation:

The wrong number of subscripts were specified with the variable reference.

EQA1488E
The indices in variable name are invalid. Use the DESCRIBE ATTRIBUTES command (without any indices specified) to see the valid indices.
Explanation:

The subscripts with the variable reference do not properly relate to the variable’s characteristics.

EQA1489S
variable name is not a based variable but a locator has been supplied for it.
Explanation:

A pointer cannot be used unless the variable is BASED.

Programmer response:

Use additional qualification to get to the desired variable.

EQA1490S
variable name cannot be used as a locator variable.
Explanation:

Only variables whose data type is POINTER or OFFSET can be used to locator with other variables.

EQA1491S
There is no variable named character string, and if it is meant to be a built-in function, the maximum number of arguments to the character string built-in function is number, but number were specified. If it is meant to be a STORAGE alteration command, the syntax is not valid.
Explanation:

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.

EQA1492S
There is no variable named character string, and if it is meant to be a built-in function, the minimum number of arguments to the character string built-in function is number, but number were specified.
Explanation:

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.

EQA1493E
There is no variable named character string, and if it is meant to be a built-in function, remember built-in functions are allowed only in expressions.
Explanation:

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.

EQA1494S
variable name is an aggregate. It cannot be used as a locator reference.
Explanation:

The variable that is being as a locator is not the correct data type.

EQA1495S
The name variable name is ambiguous and cannot be resolved.
Explanation:

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.

Programmer response:

Retry the command with enough qualification so that the name is unambiguous.

EQA1496S
The name variable name refers to a structure, but structures are not supported within this context.
Explanation:

Given DCL 1 A, 2 B FIXED, 2 C FLOAT, the name A refers to a structure.

Programmer response:

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.

EQA1497S
An aggregate cannot be used as an index into an array.
Explanation:

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.

Programmer response:

Use a scalar as the index.

EQA1498S
Generation and recursion numbers must be positive.
Explanation:

In %GENERATION(x,y) and %RECURSION(x,y), y must be positive.

EQA1499S
Generation and recursion expressions cannot be aggregate expressions.
Explanation:

In %GENERATION(x,y) and %RECURSION(x,y), y must be a scalar.

EQA1500S
%RECURSION can be applied only to parameters and automatic variables.
Explanation:

In %RECURSION(x,y), x must be a parameter or an automatic variable.

EQA1501S
%RECURSION number of procedure name does not exist. The present number of recursions of the block block name is number.
Explanation:

In %RECURSION(x,y), y must be no greater than the number of recursions of the block where x is declared.

EQA1502S
%Generation can be applied only to controlled variables.
Explanation:

In %GENERATION(x,y), x must be controlled.

EQA1503S
%Generation number of variable name does not exist. The present number of allocations of variable name is number.
Explanation:

In %GENERATION(x,y), y must be no greater than the number of allocations of the variable x.

EQA1504S
%Generation number of %RECURSION (procedure name, number) does not exist. The present number of allocations of %RECURSION (procedure name, number) is number.
Explanation:

In %GENERATION(x,y), y must be no greater than the number of allocations of the variable x.

EQA1505S
The variable variable name belongs to a FETCHed procedure and is a CONTROLLED variable that is not a parameter. This violates the rules of PL/I.
Explanation:

PL/I does not allow FETCHed procedures to contain CONTROLLED variable types.

Programmer response:

Correct the program.

EQA1506S
The variable character string cannot be used.
Explanation:

The variable belongs to the class of variables, such as members of structures with REFER statements, which Debug Tool does not support.

EQA1507E
The expression in the QUIT command must be a scalar that can be converted to an integer value.
Explanation:

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.

EQA1508E
An internal error occurred in C run time during expression processing.
Explanation:

This message applies to C. An internal error occurred in the C run time and the command is terminated.

EQA1509E
The unary operator operator name requires a scalar operand.
Explanation:

This message applies to the C unary operator ! (logical negation).

EQA1510E
The unary operator operator name requires a modifiable lvalue for its operand.
Explanation:

This message applies to the C unary operators ++ and --.

EQA1511E
The unary operator operator name requires an integer operand.
Explanation:

This message applies to the C unary operator ~ (bitwise complement).

EQA1512E
The unary operator operator requires an operand that is either arithmetic or a pointer to a type with defined size.
Explanation:

This message applies to the C unary operators + and -. These operators cannot be applied to pointers to void-function designators, or pointers to functions.

EQA1513E
The unary operator operator requires an arithmetic operand.
Explanation:

This message applies to the C unary operator + and -.

EQA1514E
Too many arguments specified in function call.
Explanation:

This message applies to C function calls.

EQA1515E
Too few arguments specified in function call.
Explanation:

This message applies to C function calls.

EQA1516E
The logical operator operator requires a scalar operand.
Explanation:

This message applies to the C binary operators && (logical and) and || (logical or).

EQA1517E
The operand of the type cast operator must be scalar.
Explanation:

This message applies to the C type casts.

EQA1518E
The named type of the type cast operator must not be an expression.
Explanation:

This message applies to the C type casts.

EQA1519E
A real type cannot be cast to a pointer type.
Explanation:

This message applies to C type casts. In the example 'float f;', the type cast '(float *) f' is invalid.

EQA1520E
A pointer type cannot be cast to a real type.
Explanation:

Invalid operand for the type cast operator.

EQA1521E
The operand in a typecast must be scalar.
Explanation:

This message applies to C type casts.

EQA1522E
Argument argument in function call function has an invalid type.
Explanation:

This message applies to C function calls.

EQA1523E
Invalid type for function call.
Explanation:

This message applies to C function calls.

EQA1524E
The first operand of the subscript operator must be a pointer to a type with defined size.
Explanation:

This message applies to the C subscript operator. The subscript operator cannot be applied to pointers to void, function designators or pointers to functions.

EQA1525E
Subscripts must have integer type.
Explanation:

This message applies to the C subscript operator.

EQA1526E
The first operand of the sizeof operator must not be a function designator, a typedef, a bitfield or a void type.
Explanation:

This message applies to the C unary operator sizeof.

EQA1527E
The second operand of the operator operator must be a member of the structure or union specified by the first operand.
Explanation:

This message applies to the C operators (select member) and -> (point at member).

EQA1528E
The first operand of the operator operator must have type pointer to struct or pointer to union.
Explanation:

This message applies to the C operator -> (point at member).

EQA1529E
The operand of the operator operator must be an array, a function designator, or a pointer to a type other than void.
Explanation:

This message applies to the C indirection operator.

EQA1530E
The first operand of the operator operator must have type struct or union.
Explanation:

This message applies to the C subscript operator (select member).

EQA1531E
The relational operator operator requires comparable data types.
Explanation:

This message applies to the C relational operators. For example, <, >, <=, >=, and ==.

EQA1532E
The subtraction operator requires that both operands have arithmetic type or that the left operand is a pointer to a type with defined size and the right operand has the same pointer type or an integral type.
Explanation:

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.

EQA1533E
Assignment contains incompatible types.
Explanation:

This message applies to C assignments, for example, +=, -=, and *=.

EQA1534E
The TEST expression in the switch operator must have integer type.
Explanation:

This applies to the test expression in a C switch command.

EQA1535E
The addition operator requires that both operands have arithmetic or that one operand has integer type and the other operand is a pointer to a type with defined size.
Explanation:

This message applies to the C binary operator +.

EQA1536E
The operand of the address operator must be a function designator or an lvalue that is not a bitfield.
Explanation:

This message applies to the C unary operator & (address).

EQA1537E
Invalid constant for the C language.
Explanation:

This message applies to C constants.

EQA1538E
Argument argument in function call function is incompatible with the function definition. Since Warning is on, the function call is not made.
Explanation:

This message applies to C function calls. The argument must have a type that would be valid in an assignment to the parameter.

EQA1539E
The binary operator operator requires integer operands.
Explanation:

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 <<=).

EQA1540E
The binary operator operator requires a modifiable lvalue for its first operand.
Explanation:

This message applies to the C binary assignment operators.

EQA1541E
The binary operator operator requires arithmetic operands.
Explanation:

This message applies to the C binary operators * and /.

EQA1542E
Source in assignment to an enum is not a member of the enum. Since Warning is on, the operation is not performed.
Explanation:

This message applies to C. You attempted to assign a value to enum, but the value is not legitimate for that enum.

EQA1543E
Invalid value for the shift operator operator. Since Warning is on, the operation will not be performed.
Explanation:

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.

EQA1544E
Array subscript is negative. Since Warning is on, the operation is not performed.
Explanation:

This message applies to the C subscripts.

EQA1545E
Array subscript exceeds maximum declared value. Since Warning is on, the operation is not performed.
Explanation:

This message applies to the C subscripts.

EQA1546E
ZeroDivide would have occurred in performing a division operator. Since Warning is on, the operation is not performed.
Explanation:

Divide by zero is detected by C run time.

EQA1547E
variable is presently not in accessible storage.
Explanation:

This message applies to C. Use the LIST NAMES command to list all known variables.

EQA1548E
There is no variable named variable
Explanation:

This message applies to C. Use the LIST NAMES command to list all known variables.

EQA1549E
The function call function is not performed because the function linkages do not match.
Explanation:

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.

EQA1550E
There is no typedef identifier named name
Explanation:

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.

EQA1551E
name is the name of a member of an enum type.
Explanation:

This message applies to C.

EQA1552E
The name name is invalid.
Explanation:

This message applies to C declarations.

EQA1553E
Linkage type for function call function is unknown.
Explanation:

This message applies to C function calls.

EQA1554E
Function call function has linkage type PL/I, which is not supported.
Explanation:

This message applies to C function calls.

EQA1555E
Function call function has linkage type FORTRAN which is not supported.
Explanation:

This message applies to C function calls.

EQA1556E
name is a tag name. This cannot be listed since it has no storage associated with it.
Explanation:

This message applies to C tag names.

EQA1557E
name is not an lvalue. This cannot be listed since it has no storage associated with it.
Explanation:

This message applies to C names.

EQA1558E
name has storage class void, not permitted on the LIST command.
Explanation:

This message applies to C. In the example 'void' funcname (...), the command LIST TITLED (funcname()) is invalid.

EQA1559E
The second operand of the %RECURSION operator must be arithmetic.
Explanation:

This message applies to C. In %RECURSION(x,y), the second expression, y, must have arithmetic type.

EQA1560E
The second operand of the %RECURSION operator must be positive.
Explanation:

This message applies to C. In %RECURSION(x,y), the second expression, y, must be positive.

EQA1561E
The first operand of the %RECURSION operator must be a parameter or an automatic variable.
Explanation:

This message applies to C. In %RECURSION(x,y), the first expression, x, must be a parameter or an automatic variable.

EQA1562E
The first operand of the %INSTANCE operator must be a parameter or an automatic variable.
Explanation:

This message applies to C. In %INSTANCE(x,y), the first expression, x, must be a parameter or an automatic variable.

EQA1563E
Generation specified for %RECURSION is too large.
Explanation:

This message applies to C. In %RECURSION(x,y), the recursion number, y, exceeds the number of generations of x that are currently active.

EQA1564E
The identifier identifier has been replaced.
Explanation:

This message applies to C declarations.

EQA1565E
The declaration is too large
Explanation:

This message applies to C declarations.

EQA1566E
An attempt to modify a constant was made. Since Warning is on, the operation is not performed.
Explanation:

This message applies to C.

EQA1567E
An attempt to take the address of a variable with register storage was made. Since Warning is on, the operation is not performed.
Explanation:

This message applies to C.

EQA1568E
Type of expression to %DUMP must be a literal string.
Explanation:

This message applies to CALL %DUMP for C.

EQA1569E
Octal constant is too long.
Explanation:

This message applies to C constants.

EQA1570E
Octal constant is too big.
Explanation:

This message applies to C constants.

EQA1571E
Hex constant is too long.
Explanation:

This message applies to C constants.

EQA1572E
Decimal constant is too long.
Explanation:

This message applies to C constants.

EQA1573E
Decimal constant is too big.
Explanation:

This message applies to C constants.

EQA1574E
Float constant is too long.
Explanation:

This message applies to C constants.

EQA1575E
Float constant is too big.
Explanation:

This message applies to C constants.

EQA1576E
The environment is not yet fully initialized.
Explanation:

You can STEP and try the command again.

EQA1577E
Size of the aggregate is too large
Explanation:

This message applies to PL/I constants.

EQA1578E
Only "=" and "¬=" are allowed as operators in comparisons involving program control data.
Explanation:

Other relationships between program control data are not defined.

Programmer response:

Check to see if a variable was misspelled.

EQA1579E
Program control data may be compared only with program control data of the same type.
Explanation:

ENTRY vs ENTRY, LABEL vs LABEL, etc. are okay. LABEL vs ENTRY is not.

EQA1580E
Area variables cannot be compared.
Explanation:

Equivalency between AREA variables is not defined.

EQA1581E
Aggregates are not allowed in conditional expressions such as the expressions in IF ... THEN, WHILE ( ... ), UNTIL ( ... ), and WHEN ( ... ) clauses.
Explanation:

This is not supported.

Programmer response:

Check to see if the variable name was misspelled. If this was not the problem, you must find other logic to perform the task.

EQA1582E
Only "=" and "¬=" are allowed as operators in comparisons involving complex numbers.
Explanation:

Equal and not equal are defined for complex variables, but you have attempted to relate them in some other way.

EQA1583E
Strings with the GRAPHIC attribute may be concatenated only with other strings with the GRAPHIC attribute.
Explanation:

You are not allowed to concatenate GRAPHIC (DBCS) strings to anything other than other GRAPHIC (DBCS) strings.

EQA1584E
Strings with the GRAPHIC attribute may be compared only with other strings with the GRAPHIC attribute.
Explanation:

Equivalency between the GRAPHIC data type and other data types has not been defined.

EQA1585E
Only numeric data, character strings, and bit strings may be the source for conversion to character data.
Explanation:

You are trying to convert something to a character format when such a relationship has not been defined.

EQA1586E
Only numeric data, character strings, and bit strings may be the source for conversion to bit data.
Explanation:

You are trying to convert something to a bit format when such a relationship has not been defined.

EQA1587E
Only numeric data, character strings, bit strings, and pointers may be the source for conversion to numeric data.
Explanation:

You are trying to convert something to a numeric format when such a relationship has not been defined.

EQA1588E
Aggregates are not allowed in control expressions.
Explanation:

This message applies to PL/I constants.

EQA1589W
CONVERSION would have occurred in performing a CHARACTER to BIT conversion, but since WARNING is on, the conversion will not be performed.
Explanation:

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.

EQA1590W
Varying string variable name has a length that is greater than its declared maximum. It will not be used in expressions until it is fixed.
Explanation:

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.

EQA1591W
Varying string variable name has a negative string length. It will not be used in expressions until it is fixed.
Explanation:

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.

EQA1592W
Fixed decimal variable variable name contains bad data. Since WARNING is on, the operation will not be performed.
Explanation:

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.

EQA1593W
The size of AREA variable variable name is less than zero. Since WARNING is on, the operation will not be performed.
Explanation:

Negative sizes are not understood and, therefore, are not processed.

EQA1594W
The size of AREA variable variable name exceeds its declared maximum size. Since WARNING is on, the operation will not be performed.
Explanation:

Performing the operation would alter storage that is outside of the AREA. Such an operation is not within PL/I, so will be avoided.

EQA1595W
Fixed binary variable variable name contains more significant digits than its precision allows. Since WARNING is on, the operation will not be performed.
Explanation:

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.

EQA1596E
The subscripted variable variable name was not found. The name matches a built-in function, but the parameters are wrong.
Explanation:

This message applies to PL/I constants.

EQA1597E
AREA condition would have been raised
Explanation:

This message applies to PL/I constants.

EQA1598E
The bounds and dimensions of all arrays in an expression must be identical.
Explanation:

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.

EQA1599E
You cannot assign an array to a scalar.
Explanation:

The PL/I language does not define how a scalar would represent an array; the assignment is rejected as an error.

EQA1600E
Aggregate used in wrong context.
Explanation:

This message applies to PLI constants.

EQA1601E
The second expression in the built-in function name built-in function must be greater than or equal to 1 and less than or equal to the number of dimensions of the first expression.
Explanation:

The second expression of the named built-in function is dependent upon the dimensions of the array (the first built-in function argument).

Programmer response:

Correct the relationship between the first and second arguments.

EQA1602E
The second expression in the built-in function name built-in function must not be an aggregate.
Explanation:

Debug Tool does not support aggregates in this context.

EQA1603E
The first argument in the built-in function name built-in function must be an array expression.
Explanation:

The named built-in function expects an array to be the first argument.

EQA1604E
Argument number number in the built-in function name built-in function must be a variable.
Explanation:

You used something other than a variable name (for example, a constant) in your invocation of the named built-in function.

EQA1605E
STRING( variable name ) is invalid because the STRING built-in function can be used only with bit, character and picture variables.
Explanation:

You must use a variable of the correct data type with the STRING built-in function.

EQA1606E
POINTER( variable name ,...) is invalid because the first argument to the POINTER built-in function must be an offset variable.
Explanation:

The first argument to POINTER was determined to be something other than an OFFSET data type.

EQA1607E
POINTER(..., variable name ) is invalid because the second argument to the POINTER built-in function must be an area variable.
Explanation:

The second argument to POINTER was determined to be something other than an AREA data type.

EQA1608E
OFFSET( variable name ,...) is invalid because the first argument to the OFFSET built-in function must be a pointer variable.
Explanation:

The first argument to OFFSET was determined to be something other than a POINTER data type.

EQA1609E
OFFSET(..., variable name ) is invalid because the second argument to the OFFSET built-in function must be an area variable.
Explanation:

The second argument to OFFSET was determined to be something other than an AREA data type.

EQA1610E
built-in function name ( variable name ) is invalid because the argument to the built-in function name built-in function must be a file reference.
Explanation:

The name built-in function requires the name of a FILE to operate. Some other data type was used as the argument.

EQA1611E
COUNT( variable name ) must refer to an open STREAM file.
Explanation:

You must name an open STREAM file in the COUNT built-in function.

EQA1612E
LINENO( variable name ) must refer to an open PRINT file.
Explanation:

You must name an open PRINT file in the LINENO built-in function.

EQA1613E
SAMEKEY( variable name ) must refer to a RECORD file.
Explanation:

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.

EQA1614E
The argument in the built-in function name built-in function must be a variable.
Explanation:

The built-in function is expecting a variable but a constant or some other invalid item appeared as one of the arguments.

EQA1615E
Argument to POINTER is an aggregate when pointer is being used as a locator.
Explanation:

This message applies to PL/I constants.

EQA1616E
The result of invoking the GRAPHIC built-in function must not require more than 16383 DBCS characters.
Explanation:

GRAPHIC(x,y) is illegal if y > 16383, and GRAPHIC(x) is illegal if length(CHAR(X)) > 16383.

EQA1617W
The first argument to the built-in function name built-in function is negative, but since WARNING is on, the evaluation will not be performed.
Explanation:

The specified built-in function would fail if a negative argument was passed. Use of the built-in function will be avoided.

EQA1618W
The second argument to the built-in function name built-in function is negative, but since WARNING is on, the evaluation will not be performed.
Explanation:

The specified built-in function would fail if a negative argument was passed. Use of the built-in function will be avoided.

EQA1619W
The third argument to the built-in function name built-in function is negative, but since WARNING is on, the evaluation will not be performed.
Explanation:

The specified built-in function would fail if a negative argument was passed. Use of the built-in function will be avoided.

EQA1620E
If the CHAR built-in function is invoked with only one argument, that argument must not have the GRAPHIC attribute with length 16383.
Explanation:

CHAR(x) is illegal if x is GRAPHIC with length 16383 since the resultant string would require 32768 characters.

EQA1621E
built-in function ( variable name ) is not defined since variable name is not connected.
Explanation:

This applies to the PL/I CURRENTSTORAGE and STORAGE built-in functions.

EQA1622E
built-in function ( variable name ) is not defined since variable name is an unaligned fixed-length bit string.
Explanation:

This applies to the PL/I CURRENTSTORAGE and STORAGE built-in functions.

EQA1623E
built-in function (x) is undefined if ABS(x) > 1.
Explanation:

This applies to the PL/I ASIN and ACOS built-in functions.

EQA1624E
ATANH(z) is undefined if z is COMPLEX and z = +1 or z = -1.
Explanation:

This applies to the PL/I ATANH built-in function.

EQA1625E
ATAN(z) is undefined if z is COMPLEX and z = +1i or z = -1i.
Explanation:

This applies to the PL/I ATAN built-in function.

EQA1626E
Built-in function not defined since the argument is real and less than or equal to zero
Explanation:

This message applies to PL/I constants.

EQA1627E
SQRT(x) is undefined if x is REAL and x < 0.
Explanation:

This applies to the PL/I SQRT built-in function.

EQA1628E
built-in function (x,y) is undefined if x or y is COMPLEX.
Explanation:

This applies to the PL/I ATAN and ATAND built-in functions.

EQA1629E
Built-in function(X,Y) is undefined if X=0 and Y=0
Explanation:

This applies to PL/I constants.

EQA1630E
The argument in built-in function is too large.
Explanation:

This applies to the PL/I trigonometric built-in functions. For short floating-point arguments, the limits are:

COS and SIN
ABS(X) <= (2**18)*pi
TAN
ABS(X) <= (2**18)*pi if x is real and ABS(REAL(X)) <= (2**17)*pi if x is complex
TANH
ABS(IMAG(X)) <= (2**17)*pi if x is complex
COSH, EXP and SINH
ABS(IMAG(X)) <= (2**18)*pi if x is complex
COSD, SIND and TAND
ABS(X) <= (2**18)*180

For long floating-point arguments, the limits are:

COS and SIN
ABS(X) <= (2**50)*pi
TAN
ABS(X) <= (2**50)*pi if x is real and ABS(REAL(X)) <= (2**49)*pi if x is complex
TANH
ABS(IMAG(X)) <= (2**49)*pi if x is complex
COSH, EXP and SINH
ABS(IMAG(X)) <= (2**50)*pi if x is complex
COSD, SIND and TAND
ABS(X) <= (2**50)*180

For extended floating-point arguments, the limits are:

COS and SIN
ABS(X) <= (2**106)*pi
TAN
ABS(X) <= (2**106)*pi if x is real and ABS(REAL(X)) <= (2**105)*pi if x is complex
TANH
ABS(IMAG(X)) <= (2**105)*pi if x is complex
COSH, EXP and SINH
ABS(IMAG(X)) <= (2**106)*pi if x is complex
COSD, SIND and TAND
ABS(X) <= (2**106)*180
EQA1631E
The subject of the SUBSTR pseudovariable ( character string ) is not a string.
Explanation:

You are trying to get a substring from something other than a string.

EQA1632E
Argument to pseudovariable must be complex numeric
Explanation:

This message applies to PL/I constants.

EQA1633E
The first argument to a pseudovariable must refer to a variable, not an expression or a pseudovariable.
Explanation:

The arguments that accompany a pseudovariable are incorrect.

EQA1634E
The length of the bit string that would be returned by UNSPEC is greater than the maximum for a bit variable. Processing of the expression will stop.
Explanation:

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.

EQA1635E
Maximum number of arguments to PLIDUMP subroutine is two
Explanation:

This message applies to PL/I constants.

EQA1636E
Invalid argument in CALL %DUMP
Explanation:

This message applies to PL/I constants.

EQA1637E
PL/I cannot process the expression expression name.
Explanation:

This applies to PL/I constants.

EQA1638E
Argument argument number to the MPSTR built-in function must not have the GRAPHIC attribute.
Explanation:

GRAPHIC (DBCS) strings are prohibited as arguments to the MPSTR built-in function.

EQA1639E
ALLOCATION( variable name ) is invalid because the ALLOCATION built-in function can be used only with controlled variables.
Explanation:

You must name a variable that is ALLOCATEable.

Programmer response:

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.

EQA1640E
variable name is an aggregate and hence is invalid as an argument to the POINTER built-in function when that built-in function is used as a locator.
Explanation:

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.

EQA1641E
Structures are not supported within this context.
Explanation:

Given dDCL 1 A, 2 B FIXED, 2 C FLOAT, the name A refers to a structure.

Programmer response:

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.

EQA1642E
The first argument to the built-in function name built-in function must have POINTER type.
Explanation:

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

EQA1643E
The argument in the built-in function name built-in function must have data type: data type.
Explanation:

This message applies to various built-in functions. By built-in function, the datatypes required are:

ENTRYADDR
ENTRY
BINARYVALUE
POINTER
BINVALUE
POINTER
EQA1644W
STRINGRANGE is disabled and the SUBSTR arguments are such that STRINGRANGE ought to be raised. Debug Tool will revise the SUBSTR reference as if STRINGRANGE were enabled.
Explanation:

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.

EQA1645E
The subject of the pseudovariable name pseudovariable must have data type: data type.
Explanation:

This message applies to various pseudovariables. By pseudovariable, the datatypes required are:

ENTRYADDR
ENTRY VARIABLE
EQA1646E
built-in function (z) is undefined if z is COMPLEX.
Explanation:

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.

EQA1647I
Value is unprintable. Use LIST %HEX ( variable name to display the value.
EQA1648S
Only session variables may be modified in PLAYBACK replay mode.
Explanation:

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.

EQA1649E
Error: see Command Log.
Explanation:

An error has occurred during expression evaluation. See the Debug Tool Command Log for more detailed information.

EQA1650E
The range of statements statement_id - statement_id is invalid because the two statements belong to different blocks.
Explanation:

AT stmt1-stmt2 is valid only if stmt1 and stmt2 are in the same block.

EQA1651W
The breakpoint-id breakpoint has not been established.
Explanation:

You just issued a CLEAR/LIST command against a breakpoint that does not exist.

Programmer response:

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.

EQA1652E
Since the program for the statement statement-number does not have hooks at statements, AT commands are rejected for all statements in the program.
Explanation:

The program has not been prepared properly so AT commands are rejected for all statements in the program.

Programmer response:

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.

EQA1653E
A file name is invalid in this context.
Explanation:

A command (for example, AT ENTRY) specified a C file name where a function or compound statement was expected.

EQA1654E
Since the cu cu_name does not have hooks at block entries and exits, all AT ENTRY and AT EXIT commands will be rejected for the cu.
Explanation:

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.

EQA1655E
Since the program for the label label-name does not have hooks at labels, AT commands are rejected for all labels in the program.
Explanation:

A compilation unit must have been compiled with TEST(PATH) or TEST(ALL) for hooks to be present at labels.

EQA1656E
statement_id contains a value that is invalid in this context.
Explanation:

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

EQA1657W
There are no breakpoint-class breakpoints set.
Explanation:

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.

EQA1658W
There are no enabled breakpoint-class breakpoints set.
Explanation:

The command CLEAR/LIST AT was entered but there are no enabled AT breakpoints presently set in the requested class of breakpoints.

EQA1659W
There are no disabled breakpoint-class breakpoints set.
Explanation:

The command CLEAR/LIST AT was entered but there are no disabled AT breakpoints presently set in the requested class of breakpoints.

EQA1660W
The breakpoint-id breakpoint is not enabled.
Explanation:

You issued a specific LIST AT ENABLED command against a breakpoint that is not enabled.

EQA1661W
The breakpoint-id breakpoint is not disabled.
Explanation:

You issued a specific LIST AT DISABLED command against a breakpoint that is not disabled.

EQA1662W
The breakpoint-id breakpoint cannot be triggered because it is disabled.
Explanation:

You cannot TRIGGER a disabled breakpoint.

EQA1663W
There are no breakpoints set. No breakpoints are currently set.
EQA1664W
There are no disabled breakpoints set.
Explanation:

No disabled breakpoints are currently set.

EQA1665W
There are no enabled breakpoints set.
Explanation:

No enabled breakpoints are currently set.

EQA1666W
1The breakpoint-id breakpoint is already enabled.
Explanation:

You cannot ENABLE an enabled breakpoint.

EQA1667W
The breakpoint-id breakpoint is already disabled.
Explanation:

You cannot DISABLE a disabled breakpoint.

EQA1668W
The attempt to set this breakpoint has failed.
Explanation:

For some reason, when Debug Tool tried to set this breakpoint, an error occurred. This breakpoint cannot be set.

EQA1669W
The FROM or EVERY value in a breakpoint command must not be greater than the specified TO value.
Explanation:

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.

EQA1670W
GO/RUN BYPASS is ignored. It is valid only when entered for an AT CALL, AT GLOBAL CALL, or AT OCCURRENCE.
Explanation:

GO/RUN BYPASS is valid only when Debug Tool is entered for an AT CALL, AT GLOBAL CALL, or AT OCCURRENCE breakpoint.

EQA1671W
AT OCCURRENCE breakpoint or TRIGGER of condition condition-name cannot have a reference specified. This command not processed.
Explanation:

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.

EQA1672W
AT OCCURRENCE breakpoint or TRIGGER of condition condition-name must have a valid reference specified. This command not processed.
Explanation:

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.

EQA1673W
An attempt to automatically restore an AT breakpoint type breakpoint failed.
Explanation:

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.

EQA1674W
An attempt to automatically disable an AT breakpoint type breakpoint failed.
Explanation:

Debug Tool was attempting to disable a breakpoint for a CU that has been deleted from storage (or deactivated), and failed in that attempt.

EQA1675E
variable name is not a LABEL variable or constant. No GOTO or JUMPTO commands can be issued against it.
Explanation:

You are trying to use a GOTO or JUMPTO command with a variable name that cannot be associated with a label in the program.

EQA1676S
label name is a label variable that is uninitialized or that has been zeroed out. It cannot be displayed and should not be used except as the target of an assignment.
Explanation:

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

EQA1677S
file name is a file variable that is uninitialized or that has been zeroed out. It cannot be displayed and should not be used except as the target of an assignment.
Explanation:

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

EQA1678E
The program CU-name has a short statement number table, and therefore no statement numbers in the program can be located.
Explanation:

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.

Programmer response:

Check to see if the program had been compiled using release name. If so, was the statement table suppressed?

EQA1679E
variable name is not a controlled variable. An ALLOCATE breakpoint cannot be established for it.
Explanation:

You cannot establish an AT ALLOCATE breakpoint for a variable that cannot be allocated.

EQA1680E
variable name is a controlled parameter. An ALLOCATE breakpoint can be established for it only when the block in which it is declared is active.
Explanation:

Debug Tool cannot, at this time, correlate a block to the named variable. As a result, a breakpoint cannot be established.

Programmer response:

Establish the breakpoint via an AT ENTRY ... AT ALLOCATE ....

EQA1681E
variable name is not a FILE variable or constant.
Explanation:

ON/SIGNAL file-condition (variable) is invalid because the variable is not a PL/I FILE variable.

EQA1682E
variable name is not a CONDITION variable.
Explanation:

ON/SIGNAL CONDITION (variable) is invalid because the variable is not a PL/I CONDITION variable.

EQA1683E
Since the cu cu_name does not have hooks at statements with modified behavior due to the Millennium Language Extensions, all AT DATE commands will be rejected for the cu.
Explanation:

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.

EQA1684E
Since the program for the statement statement-number has DYNAMIC DEBUG turned off, AT commands are rejected for all statements in the program.
Explanation:

A compile unit must have been compiled with TEST(STMT) or TEST(ALL) or set DYNDEBUG ON for at statements.

EQA1685E
The command AT Keyword is not supported in the Compile Unit Cu_name.
Explanation:

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.

EQA1686E
The command/option Keyword is not supported for Disassembly View.
Explanation:

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.

EQA1687E
The command LIST Keyword is not supported in the Compile Unit Cu_name.
Explanation:

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.

EQA1688E
Variable Variable is not available during Playback replay.
Explanation:

The expression cannot be evaluated during Playback replay, because the indicated variable is not available during replay.

EQA1689E
A breakpoint cannot be set on this statement when the STORAGE runtime option is in effect. Remove STORAGE or set the breakpoint after the next LR R13,Rx instruction.
Explanation:

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.

EQA1690I
The current programming language does not return information for DESCRIBE ENVIRONMENT.
Explanation:

The current programming language does not support the DESCRIBE ENVIRONMENT command.

EQA1691I
AT OCCURRENCE breakpoint or trigger of condition string_ptr is not supported with the current language. This command is not processed.
Explanation:

The command is not supported for a ENTERPRISE PLI.

EQA1692W
Restoring of assembler breakpoints is not currently supported.
Explanation:

Breakpoints in assembler compile units are not restored.

EQA1693E
The command AT Keyword is not supported in the Compile Unit Cu_name because it is PLI compiled with the NOTEST option and does not have the hook necessary to set the breakpoint.
Explanation:

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.

EQA1694I
The command_name command is not supported in the current program.
Explanation:

The command, command_name, is not supported in programs that are compiled with Enterprise PL/I.

EQA1695E
Variable Variable has a hex value that is too long to display.
Explanation:

The expression has a hex value that exceeds the maximum length limit required to be displayable.

EQA1696E
Conditional Expression Conditional_Logic_Expression in WHEN clause can not be evaluated.
Explanation:

The conditional expression is not valid. Make sure the variable is known in current compile unit or that the attributes are compatible.

EQA1697E
Conditional Expression Conditional_Logic_Expression in WHEN clause can not be evaluated at current location.
Explanation:

The conditional expression is not valid. Make sure the variable is known in current compile unit or that the attributes are compatible.

EQA1698E
The CU containing a referenced variable has not yet been entered. Storage does not exist for the referenced variable.
Explanation:

You have attempted to evaluate a variable in an implicitly created CU. Storage has not yet been allocated for this variable.

EQA1699E
Address_Length_Info Flags Name
Explanation:

This message contains the output from the DESCRIBE LOADMODS command.

EQA1700E
The session procedure, procedure name, is either undefined or is hidden within a larger, containing procedure.
Explanation:

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.

EQA1701E
The maximum number of arguments to the %DUMP built-in subroutine is 2, but number were specified.
Explanation:

%DUMP does not accept more than two parameters.

EQA1702E
Invalid argument in CALL %DUMP.
Explanation:

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.

EQA1703E
No arguments can be passed to a session procedure.
Explanation:

Parameters are not supported with the CALL procedure command.

EQA1704E
Invalid or incompatible dump options or suboptions
Explanation:

This message is from the feedback code of Language Environment CEE3DMP call.

EQA1705E
Dump argument exceeds the maximum length allowed.
Explanation:

The dump option allows a maximum of 255 characters. The dump title allows a maximum of 80 characters.

EQA1706E
pgmname must be loaded before calling the program.
Explanation:

The CALL command was terminated unsuccessfully.

EQA1707E
The following data was produced by Fault Analyzer.
Explanation:

This message is used as a header for the call %FA.

EQA1708I
The HOGAN environment is not available.
Explanation:

The Computer Sciences Corporation's KORE-HOGAN product is not installed.

EQA1709E
Command CALL %HOGAN is only available in a CICS environment.
Explanation:

The CALL %HOGAN command is only valid in a CICS environment with Computer Sciences Corporation's KORE-HOGAN installed.

EQA1710E
You are not authorized to execute that function.
Explanation:

The function that you requested has been rejected by a security manager.

EQA1711E
Program can not be found.
Explanation:

An error occurred in locating the program needed to perform the function you requested.

EQA1712E
Function not available in Dual Terminal Mode.
Explanation:

The function that you requested is not supported when Debug Tool is running in Dual Terminal mode.

EQA1713E
Load module load_module could not be found.
Explanation:

The indicated load module was specified as an operand of the DESCRIBE LOADMODS command but is not an active load module.

EQA1714I
BP_Operation successful for suspended breakpoint.
Explanation:

The requested breakpoint was successfully performed on a suspended breakpoint.

EQA1720E
There is no declaration for variable name.
Explanation:

A command (for example, CLEAR VARIABLES) requires the use of a variable, but the specified variable was not declared (or was previously cleared).

Programmer response:

For a list of session variables that can be referenced in the current programming language, use the LIST NAMES TEST command.

EQA1721E
The size of the variable is too large.
Explanation:

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.

EQA1722E
Error in declaration; invalid attribute variable name.
Explanation:

A session variable is declared with invalid or unsupported attribute.

EQA1723E
There is no session variables defined.
Explanation:

The CLEAR VARIABLES command is entered but there is no declaration for session variables.

EQA1724E
There is no tag type tag named tag name.
Explanation:

This message applies to C. It is issued, for example, after DESCRIBE ATTRIBUTES enum x if x is not an enum tag.

EQA1725E
tag type tag name is already defined.
Explanation:

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.

EQA1726E
tag type tag name cannot be cleared while one or more declarations refer to that type.
Explanation:

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.

EQA1727E
enum member name is the name of a declared variable. It cannot be used as the name of a member of an enum type.
Explanation:

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};
EQA1728E
The tag type tag name is recursive: it contains itself as a member.
Explanation:

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;
}
EQA1729E
An error occurred during declaration processing.
Explanation:

Unable to process the declaration. The command is terminated unsuccessfully.

EQA1739I
Some or all of the save_restore_cmd could not be restored from dsname
Explanation:

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.

EQA1740E
EQALANGX debug file cannot be found for Compile_Unit_name. Use the SET SOURCE command to indicate the new location of the EQALANGX file.
Explanation:

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.

EQA1741E
Error in setting DBCS ON when the terminal is not DBCS capable.
Explanation:

Error in setting DBCS ON when the debug session terminal is not DBCS capable.

EQA1742I
Debug Trace: Trace Data
Explanation:

This is output generated by internal Debug Tool trace for problem determination purposes only.

EQA1743I
save_restore_cmd not restored from dsname
Explanation:

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.

EQA1744I
save_restore_cmd is in effect for dsname
Explanation:

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.

EQA1745I
save_restore_cmd restored from dsname
Explanation:

The specified data was successfully restored from the specified data set.

EQA1746E
save_restore_cmd were not saved. Data set does not exist: dsname
Explanation:

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.

EQA1747I
save_restore_cmd saved to dsname with restore_cmd
Explanation:

The indicated data was successfully saved to the specified data set with the indicated restore options.

EQA1748E
save_restore_cmd unable to open dsname. Possible RACF error, invalid member name, etc.
Explanation:

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.

EQA1749E
save_restore_cmd data set dsname is allocated to another user or job.
Explanation:

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.

EQA1750E
An error occurred during expression evaluation.
Explanation:

Unable to evaluate the expression. The command is terminated unsuccessfully.

EQA1751E
Program pgmname not found.
Explanation:

A bad program name is specified in a CALL command and processing is terminated unsuccessfully.

EQA1752S
Comparison in command-name command was invalid. The command was ignored.
Explanation:

This message applies to COBOL. The operands to be compared are of incompatible types.

EQA1753S
The nesting of "switch" command exceeded the maximum.
Explanation:

This message applies to C. There are too many nested levels of switch commands.

EQA1754S
An error occurred in "switch" command processing. The command is terminated.
Explanation:

This message applies to C. The switch command is terminated because an error occurred during processing.

EQA1755S
Comparison with the keyword-name keyword in command-name command was invalid. The command was ignored.
Explanation:

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-EVALUATE
EQA1756W
EQALANGX file not available for CSECT CMD_NAME.
Explanation:

A debug data file is not found for the supplied CSECT name.

EQA1757W
Cannot save_restore breakpoints and/or monitors because an OPEN exit is active.
Explanation:

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.

EQA1763E
save_restore_cmd failed because dsname is not a partitioned data set.
Explanation:

The specified data set must be a partitioned data set.

EQA1764E
save_restore_cmd could not locate data set dsname.
Explanation:

The specified data set could not be located.

EQA1765E
save_restore_cmd error rc-reason allocating dsname.
Explanation:

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.

EQA1766E
The target of the GOTO command is in an inactive block.
Explanation:

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

EQA1767S
No offset was found for label "label".
Explanation:

No offset associated with the label was found; the code associated with the label might have been removed by optimization.

EQA1768S
The label "label" is not known.
Explanation:

The label is not known.

EQA1769S
The label "label" is ambiguous - multiple labels of this name exist.
Explanation:

The label is ambiguous; multiple labels of this name exist.

EQA1770S
The GOTO is not permitted, perhaps because of optimization.
Explanation:

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.

EQA1771S
The GOTO is not permitted due to language rules.
Explanation:

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.

EQA1772S
The GOTO was not successful.
Explanation:

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.

EQA1773E
GOTO is invalid when the target statement number is in a C function.
Explanation:

The target statement number in a GOTO command must belong to an active procedure.

EQA1776E
The target of the JUMPTO command is in an inactive block.
Explanation:

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.

EQA1777E
variable_name is not a LABEL variable or constant. No JUMPTO commands can be issued against it.
Explanation:

You are trying to JUMPTO a variable name that can not be associated with a label in the program.

EQA1778S
The JUMPTO is not allowed, perhaps because of optimization.
Explanation:

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.

EQA1779S
The JUMPTO is not permitted due to language rules.
Explanation:

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.

EQA1780S
The JUMPTO was not successful.
Explanation:

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.

EQA1781E
JUMPTO is invalid when the target statement number is in a C function.
Explanation:

The target statement number in a JUMPTO command must belong to an active procedure.

EQA1782I
EQALANGX data from LANGX_File_ID will be used for deferred LDD cu_spec.
Explanation:

When the deferred LDD for the specified CU is executed, the EQALANGX data will be loaded from the specified data set.

EQA1786W
There are no entries in the HISTORY table.
Explanation:

Debug Tool has not yet encountered any of the situations that cause entries to be put into the HISTORY table; so it is empty.

EQA1787W
There are no STATEMENT entries in the HISTORY table.
Explanation:

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.

EQA1788W
There are no PATH entries in the HISTORY table.
Explanation:

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.

EQA1789W
Requested register(s) not available.
Explanation:

You are trying to work with a register but none exist in this context (for example, during environment initialization).

EQA1790W
There are no active blocks.
Explanation:

The LIST CALLS command was issued before any STEP or GO.

EQA1791E
The pattern pattern is invalid.
Explanation:

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

EQA1792S
Only the ADDR and POINTER built-in functions may be used to specify an address in the LIST STORAGE command.
Explanation:

LIST STORAGE(built-in function(...)) is invalid if the built-in function is not the ADDR or POINTER built-in function.

EQA1793S
ENTRY, FILE, LABEL, AREA, EVENT or TASK variables are not valid in a LIST command.
Explanation:

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.

EQA1794S
Block Block_name is not currently active.
Explanation:

The block is not currently active for LIST TITLED

Programmer response:

Issue LIST TITLED or LIST TITLED * from within the block.

EQA1795W
Symbol information at current location is not accessible.
Explanation:

The symbols including variables or other data may not have been allocated at this location, you may STEP and issue the command again.

EQA1806E
The command element character is invalid.
Explanation:

The command entered could not be parsed because the specified element is invalid.

EQA1807E
The command element character is ambiguous.
Explanation:

The command entered could not be parsed because the specified element is ambiguous.

EQA1808E
The hyphen cannot appear as the last character in an identifier.
Explanation:

COBOL identifiers cannot end in a hyphen.

EQA1809E
Incomplete command specified.
Explanation:

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.

EQA1810E
End-of-source has been encountered after an unmatched comment marker.
Explanation:

A /* ... was entered but an */ was not present to close the comment. The command is discarded.

Programmer response:

You must either add an */ to the end of the comment or explicitly indicate continuation with an SBCS hyphen.

EQA1811E
End-of-source has been encountered after an unmatched quotation mark.
Explanation:

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.

Programmer response:

There could be several solutions for this, among them:

  1. You must either add a quotation mark to the end of the constant or explicitly indicate continuation (with an SBCS hyphen).
  2. If DBCS is ON you should also verify that you didn't try to start a constant with an SBCS quotation mark and terminate it with a DBCS quotation mark (or vice versa).
  3. You might have entered a character constant that contained a quotation mark -- and you didn't double it.
EQA1812E
A decimal exponent is required.
Explanation:

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.

EQA1813E
Error reading DBCS character codes.
Explanation:

An unmatched or nested shift code was found.

EQA1814E
Identifier is too long.
Explanation:

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.

EQA1815E
Invalid character code within DBCS name, literal or DBCS portion of mixed literal.
Explanation:

A character code point was encountered that was not within the defined code values for the first or second byte of a DBCS character.

EQA1816E
An error was found at line line-number in the current input file.
Explanation:

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.

EQA1817E
Invalid hexadecimal integer constant specified.
Explanation:

A hexadecimal digit must follow 0x.

EQA1818E
Invalid octal integer constant specified.
Explanation:

Only an octal digit can follow a digit-0.

EQA1819E
A COBOL DBCS name must contain at least one nonalphanumeric double byte character.
Explanation:

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

EQA1820E
Invalid double byte alphanumeric character found in a COBOL DBCS name. Valid COBOL double byte alphanumeric characters are: A-Z, a-z, 0-9.
Explanation:

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.

EQA1821E
The DBCS representation of the hyphen was the first or last character in a DBCS name.
Explanation:

COBOL DBCS names cannot have a leading or trailing DBCS hyphen.

EQA1822E
A DBCS Name, DBCS literal or mixed SBCS/DBCS literal may not be continued.
Explanation:

Continuation rules do not apply to DBCS names, DBCS literals or mixed SBCS/DBCS literals. These items must appear on a single line.

EQA1823E
An end of line was encountered before the end of a DBCS name or DBCS literal.
Explanation:

An end of line was encountered before finding a closing shift-in control code. This message is for the System/370 environment.

EQA1824E
A DBCS literal or DBCS name contains no DBCS characters.
Explanation:

A shift-out shift-in pair of control characters were found with no intervening DBCS characters. This message is for the System/370 environment.

EQA1825E
End-of-source was encountered while processing a DBCS name or DBCS literal.
Explanation:

No closing Shift-In control code was found before end of file. This message is for the System/370 environment.

EQA1826E
A DBCS literal was not delimited by a trailing quote or apostrophe.
Explanation:

No closing quotation mark

EQA1827E
Invalid separator character found following a DBCS name.
EQA1828E
Fixed binary constants are limited to 31 digits.
Explanation:

A fixed binary constant must be between -2**31 and 2**31 exclusive.

EQA1829E
Fixed decimal constants are limited to 20 digits.
Explanation:

A fixed decimal constant must be between -10**20 and 10**20 exclusive.

EQA1830E
Float binary constants are limited to 109 digits.
Explanation:

This limit applies to all PL/I FLOAT BINARY constants.

EQA1831E
Float decimal constants are limited to 33 digits.
Explanation:

This limit applies to all PL/I FLOAT DECIMAL constants.

EQA1832E
Floating-point exponents are limited to 3 digits.
Explanation:

This limit applies to all C float constants and to all PL/I FLOAT BINARY constants.

EQA1833E
Float decimal exponents are limited to 2 digits.
Explanation:

This limit applies to all PL/I FLOAT DECIMAL constants.

EQA1834E
Float binary constants must be less than 1E+252B.
Explanation:

This limit applies to all PL/I FLOAT BINARY constants.

EQA1835E
Float decimal constants must be less than 7.23700557733226221397318656304298E+75.
Explanation:

This limit applies to all PL/I FLOAT DECIMAL constants.

EQA1836E
Float constants are limited to 35 digits.
Explanation:

This limit applies to all C float constants.

EQA1837E
Float constants must be bigger than 5.3976053469340278908664699142502496E-79 and less than 7.2370055773322622139731865630429929E+75.
Explanation:

This is the range of values allowed by C.

EQA1856S
The module "module" cannot be loaded - it was NOT found.
Explanation:

The LOAD MODULE request failed, the module was not found.

EQA1857S
The module "module" cannot be loaded - there is NOT enough storage to do the load.
Explanation:

The LOAD MODULE request failed, there is not enough storage.

EQA1858S
The module "module" cannot be loaded.
Explanation:

The LOAD MODULE request was unsuccessful.

EQA1859S
The module "module" cannot be deleted.
Explanation:

The DELETE MODULE request was unsuccessful.

EQA1860S
The module "module" was NOT loaded by the Debug Tool and therefore CANNOT be deleted.
Explanation:

Only modules loaded by the Debug Tool may be deleted.

EQA1861S
The module "module" cannot be loaded because it was already loaded by Debug Tool.
Explanation:

The LOAD MODULE request was unsuccessful.

EQA1862E
IDISNAP could not be loaded. Verify Fault Analyzer is available or loaded.
Explanation:

IDISNAP is a part of the product Fault Analyzer. Verify Fault Analyzer is installed properly.

Programmer response:

Verify IDISNAP routine is available in the enviroment.

EQA1863I
%FA complete. See your Fault Analyzer history file.
Explanation:

%FA was complete.

Programmer response:

%FA was complete. See your Fault Analyzer history file.

EQA1864S
LOAD is not supported during initialization. STEP or GO, then retry the LOAD command.
Explanation:

You cannot issue a LOAD request until Debug Tool initialization is complete.

EQA1865I
An implicit LOAD was issued for module "loadmod".
Explanation:

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.

EQA1866I
An implicit CLEAR LOAD was issued for module "loadmod".
Explanation:

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.

EQA1867W
A load module contains LE CUs but LE is not active. The LE CUs will not be created.
Explanation:

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.

EQA1868I
An implicit CU was created for "CU_name" in "loadmod".
Explanation:

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.

EQA1869I
Implicit CU "CU_name" in "loadmod" is being destroyed.
Explanation:

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.

EQA1870S
The CU CU_name cannot be destroyed.
Explanation:

The attempt to destroy the specified CU was unsuccessful.

EQA1872E
An error occurred while opening file: file name. The file may not exist, or is not accessible.
Explanation:

An error during the initial processing (OPEN) of the file occurred.

EQA1873E
An error occurred during an input or output operation.
Explanation:

An error occurred performing an input or output operation.

EQA1874I
The command command name can be used only in full screen mode.
Explanation:

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.

EQA1875I
Insufficient storage available.
Explanation:

This message is issued when not enough storage is available to process the last command issued or to handle the last invocation.

EQA1876E
Not enough storage to display results.
Explanation:

Increase size of virtual storage.

EQA1877E
An error occurred in writing messages to the dump file.
Explanation:

This could be caused by a bad file name specified with the call dump FNAME option.

EQA1878E
The cursor is not positioned at a variable name.
Explanation:

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.

Programmer response:

Reposition the cursor and reenter.

EQA1879E
The listing file name given is too long.
Explanation:

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

EQA1880E
You may not resume execution when the program is waiting for input.
Explanation:

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.

EQA1881E
The INPUT command is only valid when the program is waiting for input.
Explanation:

The user attempted to enter the INPUT command when the program was not waiting for any input.

EQA1882E
The logical record length for filename is out of bounds. It will be set to the default.
Explanation:

The logical record length is less than 32 bytes or greater than 256 bytes.

EQA1883E
Error closing previous log file; Return code = rc
Explanation:

The user attempted to open a new log file and the old one could not be closed; the new log file is used, however.

EQA1884E
An error occurred when processing the source listing. Check return code return code in the Using the Debug Tool manual for more detail.
Explanation:

An error occurred during processing of the list lines command. Possible return codes:

EQA1885I
Attempt to open INSPPREF failed. User did not specify the Preferences File TEST option and/or did not allocate INSPPREF.
Explanation:

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.

EQA1886I
*** Global preferences file commands follow ***
Explanation:

Start of commands in the global preferences file.

EQA1887I
*** User preferences file commands follow ***
Explanation:

Start of commands in the user preferences file.

EQA1888I
*** Commands file commands follow ***
Explanation:

Start of commands in the commands file.

EQA1889I
*** Global preferences file commands end ***
Explanation:

End of commands in the global preferences file.

EQA1890I
*** User preferences file commands end ***
Explanation:

End of commands in the user preferences file.

EQA1891I
*** Commands file commands end ***
Explanation:

End of commands in the commands file.

EQA1892I
Global Preferences file exists: file name
Explanation:

The global preferences file is opened successfully.

EQA1902W
The command has been terminated because of the attention request.
Explanation:

The previously-executing command was terminated because of an attention request. Normal debugging can continue.

EQA1903E
An attention request has been issued. Enter QUIT to terminate Debug Tool or GO or RUN to resume execution.
Explanation:

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.

EQA1904E
The STEP and GO/RUN commands are not allowed at termination.
Explanation:

The STEP and GO/RUN commands are not allowed after the application program ends.

EQA1905W
You cannot trigger a condition in your program at this time.
Explanation:

The environment is in a position that it would not be meaningful to trigger a condition. For example, you have control during environment initialization.

EQA1906S
The condition named CONDITION name is unknown.
Explanation:

A condition name was expected, but the name entered is not the name of a known condition.

EQA1907W
The attempt to trigger this condition has failed.
Explanation:

For some reason, when Debug Tool tried to trigger the specified condition, it failed and the condition was not signaled.

EQA1918S
The block name block-qualification :> block_name is ambiguous.
Explanation:

There is another block that has the same name as this block.

Programmer response:

Provide further block name qualification: by load module name, by compile unit name, or by additional block names if a nested block.

EQA1919E
The present block is not nested. You cannot QUALIFY UP.
Explanation:

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.

Programmer response:

You have either misinterpreted your current execution environment or you have to qualify to some block explicitly.

EQA1920E
The present block has no dynamic parent. You cannot QUALIFY RETURN.
Explanation:

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.

Programmer response:

You have either misinterpreted your current run-time environment or you have to qualify to some block explicitly.

EQA1921S
There is no block named block_name.
Explanation:

The block that you named could not be located by Debug Tool.

Programmer response:

Provide further block name qualification: by load module name, by compile unit name, or by additional block name(s) if a nested block.

EQA1922S
There is no block named block_name within block block-qualification.
Explanation:

The qualification you are using (or the spelling of the block names) prevented Debug Tool from locating the target block.

Programmer response:

Verify that the named block should be within the current qualification.

EQA1923S
There is no compilation unit named cu_name.
Explanation:

The compilation unit (program) that you named could not be located by Debug Tool.

EQA1924S
Statement statement_id is not valid.
Explanation:

The statement number does not exist or cannot be used. Note that the statement number could exist but is unknown.

EQA1925S
There is no load module named load module name.
Explanation:

Load module qualification is referring to a load module that cannot be located.

Programmer response:

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.

EQA1926S
There is no cu named cu_name within load module load module name.
Explanation:

The compilation unit might be misspelled or missing.

EQA1927S
There are number CUs named cu_name, but neither belongs to the current load module.
Explanation:

The compilation unit you named is not unique.

Programmer response:

Add further qualification so that the correct load module will be known.

EQA1928S
The block name block_name is ambiguous.
Explanation:

There is another block that has the same name as this block.

Programmer response:

Provide further block name qualification: by load module name, by compile unit name, or by additional block names if a nested block.

EQA1929S
Explicit qualification is required because the location is unknown.
Explanation:

The current location is unknown; as such, the reference or statement must be explicitly qualified.

Programmer response:

Either explicitly set the qualification using the SET QUALIFY command or supply the desired qualification to the command in question.

EQA1930S
There is no compilation unit named CU-name in the current enclave.
Explanation:

The compilation unit (program) that you named could not be located in the current enclave by Debug Tool.

EQA1931S
There is no cu named CU-name within load module load module name in the current enclave.
Explanation:

The compilation unit might be misspelled or missing, or it might be outside of the current enclave.

EQA1932S
Block or CU block_name is not currently available
Explanation:

The block or CU that you named could not be located by Debug Tool.

Programmer response:

Provide further block name qualification--by load module name, by compile unit name, or by additional block names(s) if a nested block.

EQA1933W
The program was compiled with the OPTIMIZE compiler option either by a release of the COBOL compiler that does not support debugging of optimized code, or by a release of the compiler that is missing the required service for debugging of optimized code. Until it is recompiled with the proper release and service level of the COBOL compiler, results of Debug Tool commands are unpredictable.
Explanation:

Debug Tool does not have accurate information about the program, and thus cannot provide reliable results.

Programmer response:

Recompile the program with one of the following or later versions of the COBOL compiler:

EQA1934E
The assignment was not performed because the assigned value might not be used by the program, due to optimization.
Explanation:

Results are unreliable, because the program might use the previous value that was saved in temporary storage or a register.

Programmer response:

You can SET WARNING OFF to allow the update to take place or recompile the program without optimization.

EQA1935E
Data Item variable name was discarded due to optimization.
Explanation:

The program was compiled with the OPTIMIZE(FULL) option, and the compiler discarded the data item because it was not referenced in the program.

EQA1936W
The assignment was performed but the assigned value might not be used by the program, due to optimization.
Explanation:

Results might be unreliable because the program might use the previous value that was saved in temporary storage or a register.

Programmer response:

Recompile the program without the Optimize option.

EQA1937W
This breakpoint is deferred.
Explanation:

The compilation unit (program) that you specified could not be located by the Debug Tool. The breakpoint is deferred until this CU is entered.

EQA1938W
Provide a CU (Program) Name to qualify the block name.
Explanation:

The CU name (Program) must be added to the block name to allow Debug Tool to locate the block named.

EQA1939W
CU-name is an assembler CU name that is longer than 8 characters.
Explanation:

Assembler CU names longer than 8 characters are not currently supported.

EQA1940E
variable name is a not a level-one identifier.
Explanation:

You are trying to clear an element of a structure. You must clear the entire structure by naming its level-one identifier.

EQA1941E
ATANH(x) is undefined if x is REAL and ABS(x) >= 1.
Explanation:

This applies to the PL/I ATANH built-in function.

EQA1942E
LOG(z) is undefined if z is COMPLEX and z = 0.
Explanation:

This applies to the PL/I LOG built-in function.

EQA1943E
built-in function (x) is undefined if x is REAL and x <= 0.
Explanation:

This applies to the PL/I LOG, LOG2 and LOG10 built-in functions.

EQA1944E
built-in function (x,y) is undefined if x=0 and y=0.
Explanation:

This applies to the PL/I ATAN and ATAND built-in functions.

EQA1945I
There are no variables in the statement to display.
Explanation:

The current statement has no variables.

EQA1946I
The variable is too big to be displayed. Resources (for example, heap storage) are not available.
Explanation:

The command could not be completed due to inadequate resources. The variable is too big.

EQA1948E
The FILE CompileUnitName created by the FORMAT(DWARF) suboption of the DEBUG compiler option cannot be found. Make sure the file is in the location specified during compile time or use the EQADEBUG DD statement or EQAUEDAT user exit before starting the debug session to indicate the alternate location of the file.
Explanation:

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:

EQA1949E
The EQALANGX file does not match the object for Compile Unit name. The EQALANGX file cannot be used.
Explanation:

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.

EQA1950E
The MONITOR table is empty. If the first MONITOR command entered is numbered, it must have number 1.
Explanation:

A MONITOR n command was issued when the MONITOR table is empty, but n is greater than 1.

EQA1951E
The number of entries in the MONITOR table is monitor-number. New MONITOR commands must be unnumbered or have a number less than or equal to monitor-number.
Explanation:

A MONITOR n command was issued but n is greater than 1 plus the highest numbered MONITOR command.

EQA1952E
The MONITOR command table is full. No unnumbered MONITOR commands will be accepted.
Explanation:

A MONITOR command was issued but the MONITOR table is full.

EQA1953E
No command has been set for MONITOR monitor-number.
Explanation:

A LIST MONITOR n or CLEAR MONITOR n command was issued, but n is greater than the highest numbered MONITOR command.

EQA1954E
The command for MONITOR monitor-number has already been cleared.
Explanation:

A CLEAR MONITOR n command was issued, but MONITOR has already been cleared.

EQA1955E
There are no MONITOR commands established.
Explanation:

A LIST MONITOR or CLEAR MONITOR command was issued, but there are no MONITOR commands established.

EQA1956E
No previous FIND argument exists. FIND operation not performed.
Explanation:

A FIND command must include a string to find when no previous FIND command has been issued.

EQA1957E
String could not be found.
Explanation:

A FIND attempt failed to find the requested string.

EQA1958E
The requested SYSTEM command could not be run.
Explanation:

A SYSTEM command was issued. The underlying operating system received it but did not process it successfully.

EQA1959E
The requested SYSTEM command was not recognized.
Explanation:

The underlying operating system was passed a command that was not recognized. The system could not process the command.

EQA1960S
There is an error in the definition of variable variable name. Attribute information cannot be displayed.
Explanation:

The specified variable has an error in its definition or length and address information is not currently available in the execution of the program.

EQA1961E
Automonitor cannot be removed or replaced. Use SET AUTOMONITOR OFF command.
Explanation:

The Automonitor can only be set off with the SET AUTOMONITOR OFF command.

EQA1962E
Automonitor is already set off.
Explanation:

The Automonitor function is already off.

EQA1963S
The command command is not supported on this platform.
Explanation:

The given command is not supported on the current platform.

EQA1964E
Source or Listing data is not available, or the CU was not compiled with the correct compile options.
Explanation:

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:

EQA1965E
Attributes of source of assignment statement conflict with target variable name. The assignment cannot be performed.
Explanation:

The assignment contains incompatible data types; the assignment cannot be made.

EQA1966E
The AREA condition would have been raised during an AREA assignment, but since WARNING is on, the assignment will not be performed.
Explanation:

The operation, if performed, would result in the AREA condition. The condition is being avoided by rejecting the operation.

EQA1967E
The subject of the built-in function name pseudovariable (character string) must be complex numeric.
Explanation:

You are trying to get apply the PL/I IMAG or REAL pseudovariable to a variable that is not complex numeric.

EQA1968W
You cannot use the GOTO command at this time.
Explanation:

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.

EQA1969E
GOTO label-constant or JUMPTO label-constant will not be permitted because that constant is the label for a FORMAT statement.
Explanation:

There are several statement types that are not allowable as the target of a GOTO or JUMPTO command. FORMAT statements are one of them.

EQA1970E
The 3-letter national language code national language is not supported for this installation of Debug Tool. Uppercase United States English (UEN) will be used instead.
Explanation:

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.

EQA1971E
The return code in the QUIT command must be nonnegative and less than 1000.
Explanation:

For PL/I, the value of the return code must be nonnegative and less than 1000.

EQA1972E
variable name is not a LABEL constant No AT commands can be issued against it
Explanation:

LABEL variables cannot be the object of the AT command.

EQA1973E
The FIND argument cannot exceed a string length of 64
Explanation:

Shorten the search argument to a string length 64 or less.

EQA1974E
The FIND argument is invalid, the string length is zero
Explanation:

Supply a search argument inside the quotation marks.

EQA1975E
SYSDEBUG/SEPARATE file can not be found for Compile_Unit_name which was compiled with SEPARATE compile option but the debug file containing the debugging tables and the listing created by the compiler can not be found. Use the Set Source command to indicate the new location of the SYSDEBUG/SEPARATE file.
Explanation:

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.

EQA1976E
The debug information for Compile Unit name has already been validated, changing the debug file is not allowed. The command will not be performed.
Explanation:

A Debug File containing the listing and the debugging tables has already being validated.

EQA1977E
The Debug File creation date does not match the object for Compile Unit name, but further validation showed that debug data in the file can still be used.
Explanation:

A Debug File containing the listing and the debugging tables does not match the creation date of the object.

EQA1978E
The Debug File creation date does not match the object for Compile Unit name. The Debug file can not be used.
Explanation:

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.

EQA1979E
The Debug File for Compile Unit name is not available or was not found.
Explanation:

The Debug File was nowhere to be found.

EQA1980E
The Debug File for Compile Unit name could not be opened or read.
Explanation:

I/O errors when trying to open/read Debug File.

EQA1981E
Invalid mode name, transaction program name, or partner LU name associated with symbolic_destination_name. Mode_name= mode_name and partner_LU_name= partner_LU_name
Explanation:

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:

  1. The mode_name characteristic specifies a mode name that is either not recognized by the LU as valid or is reserved for SNA service transaction programs.
  2. The TP_name characteristic specifies an SNA service transaction program name.
  3. The partner_LU_name characteristic specifies a partner LU name that is not recognized by the LU as being valid.
Programmer response:

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.

EQA1982E
Permanent conversation allocation failure for symbolic_destination_name. Partner_LU_name= partner_LU_name and mode_name= mode_name
Explanation:

The conversation cannot be allocated because of a condition that is not temporary. There could be several reasons for this:

  1. The workstation where the partner_LU_name is defined is turned off or Communications Manager/2 is not started.
  2. The partner_LU_name has not been defined.
  3. The current session limit for the specified partner_LU_name and mode_name pair is zero.
  4. A system definition error or a session-activation protocol error has occurred.
Programmer response:

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.

EQA1983E
Temporary conversation allocation failure for symbolic_destination_name. Partner_LU_name= partner_LU_name and mode_name= mode_name.
Explanation:

The conversation cannot be allocated because of a condition that might be temporary. There could be several reasons for this:

  1. Undefined mode_name (not temporary)
  2. Temporary lack of resources at the host LU or workstation LU

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.

EQA1984E
The workstation transaction program is permanently unavailable at symbolic_destination_name. Partner_LU_name= partner_LU_name.
Explanation:

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:

  1. Missing transaction program definition on the workstation.
  2. Invalid OS/2 program path and file name specified in the transaction program definition.
Programmer response:

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.

EQA1985E
Unrecognized transaction program name at symbolic_destination_name. Partner_LU_name= partner_LU_name.
Explanation:

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.

Programmer response:

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.

EQA1986E
Unexpected TCP/IP error. Module= module_name, Location= location_id, TCP/IP call= call_type, return_code= rc.
Explanation:

The host communications code received an unexpected return code from a TCP/IP call. The information displayed is for diagnostic purposes.

Programmer response:

For remote debug mode, you need to provide the correct TCP/IP address and/or port number of the workstation.

EQA1987E
Debugger terminated, execution continues.
Explanation:

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.

EQA1988I
The environment variable QPPLISTFILES is not defined.
Explanation:

For Q++ programs, Debug Tool requires that you specify the path where the list files are stored in the environment variable QPPLISTFILES.

Programmer response:

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.

EQA1989E
Invalid session ID - session_ID
Explanation:

Conversation initialization failed due to an invalid session ID in the Session Parameter. There could be several reasons for this,

  1. The session ID is longer than 8 characters or contains invalid characters. Valid session IDs consist of 1-8 alphanumeric characters.
  2. There is already another PWS Debug Tool session with the given session ID.
Programmer response:

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.

EQA1990E
Invalid session parameter - session_parameter
Explanation:

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.

Programmer response:

Correct the Session Parameter and invoke the batch application again.

EQA1991E
CICS terminal TERM is not accessible
Explanation:

The terminal id specified to receive Debug Tool screen was detected but not acquired.

Programmer response:

Correct the Debug Tool Term Id using DTCN Replace function or logon to already defined one.

EQA1992E
Missing workstation parameter
Explanation:

Keywords APPC&, TCPIP&, VADAPPC&, and VADTCPIP& require a workstation ID to be entered.

Programmer response:

Correct or enter the workstation destination name.

EQA1993E
Invalid TCP/IP portid parameter
Explanation:

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.

Programmer response:

Correct or enter the TCP/IP port ID.

EQA1994E
There is no load module named loadmod_name.
Explanation:

Load module qualification is referring to a load module that cannot be located.

Programmer response:

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.

EQA1995S
There is no CU named &&&& within load module &&&&.
Explanation:

The compilation unit may be misspelled or missing.

EQA1996S
Explicit qualification is required because the location is unknown.
Explanation:

The current location is unknown; as such, the reference or statement must be explicitly qualified.

Programmer response:

Either explicitly set the qualification using the SET QUALIFY command or supply the desired qualification to the command in question.

EQA1997I
VTAM 3270 waiting for LU lu_name
Explanation:

This message is issued if the specified VTAM terminal is currently in use.

Programmer response:

End the session that is currently using the LU.

EQA1998S
VTAM 3270 error_type error, RC=rc insert1 insert2 insert3
Explanation:

An unrecoverable error occurred acquiring or communicating with a VTAM® terminal. error_type is one of the following:

RPL or INQUIRE RPL
A nonzero return code was received from a VTAM RPL operation.
ACB
A nonzero return code was received from a VTAM ACB operation. This may result from improper installation of Debug Tool.
MODCB
A nonzero return code was received from a VTAM MODCB operation.
Logic
An internal logic error was detected.
Function
An internal logic error was detected.
Storage
Sufficient memory could not be obtained by the VTAM interface program.
Undefined LU
The VTAM Logical Unit specified in the MFI%xxxxxxxx: parameter was not known to VTAM.
Unknown
An internal logic error was detected.

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.

Table 8. Definitions for error_type, insert1, insert2, and insert3
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
Programmer response:

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.

EQA1999I
VTAM3270 acquired LU lu_name
Explanation:

This message is issued when the LU is acquired after EQA1997I is issued.

Programmer response:

None.

EQA2000E
The hardware required to support a referenced symbol is not present.
Explanation:

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.

Programmer response:

Correctly qualify the referenced variable and retry the command.

EQA2001E
Syntax error at '%1'.
EQA2002E
Syntax error: The expression is incomplete.
EQA2003E
Cannot find the symbol '%1'.
EQA2004E
Cannot find a type for symbol '%1'.
EQA2005E
Syntax error: The expression is not a pointer.
EQA2006E
Syntax error: The expression is not a class.
EQA2007E
Syntax error: Invalid literal starting at %1
EQA2008E
Invalid operand
EQA2009E
Invalid type
EQA2010E
Invalid operator
EQA2011E
Invalid operation
EQA2012E
Unsupported operator
EQA2013E
Unknown expression type
EQA2014E
An expression may not return a value of type %1.
EQA2015E
An expression may not return %1 because it has no data members.
EQA2016E
The expression cannot be parsed.
EQA2017E
Functions with C++ linkage may not be used in expressions. Only functions with C linkage are permitted.
EQA2018E
Invalid reference
EQA2019E
Subscript out of bounds
EQA2020E
Failed to evaluate
EQA2021E
Call show_self()
EQA2022E
Evaluate now
EQA2023E
Not within current scope
EQA2250I
Command not supported on the current platform.
Explanation:

The command is not supported in the current environment (e.g., non-CICS)

EQA2251I
DTCN Pattern-match breakpoint disabled for programs:
Explanation:

This is the title line for the LIST DTCN command.

EQA2252I
CADP Pattern-match breakpoint disabled for:
Explanation:

This is the title line for the LIST CADP command.

EQA2253I
&&&&
Explanation:

This message lists the program names output by the List DTCN command.

EQA2254I
Program = &&&& CU = &&&&
Explanation:

This message lists the program and compile unit names output by the LIST CADP command.

EQA2255I
This program and/or compile unit is not in the pattern-match breakpoint list.
Explanation:

The Enable CADP command is not allowed since this particular program and/or compile unit is not in the pattern-match breakpoint list.

EQA2256I
The program/pattern &&&& is not in the DTCN pattern-match breakpoint list.
Explanation:

The Enable DTCN command is not allowed since this particular program is not in the pattern-match breakpoint list.

EQA2257I
The pattern-match breakpoint list is empty.
Explanation:

There are no entries in the pattern-match breakpoint list.

EQA2258R
There is no SOAP (DFHNODE) channel in the current program.
Explanation:

There is no channel named DFHNODE known to the current program.

EQA2259E
Debug Tool encountered an error evaluating the condition expression following WHEN for the break point. Use LIST AT to view the break point and the expression.
Explanation:

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.

EQA2260E
Failure to connect to the remote debugger. Address: address_name. Port: port_number. IP sockets returned: rc. Possible cause: invalid IP address.
Explanation:

Please check the TCPIP address and port specified and verify that the remote debugger daemon is listening.

EQA2261E
An error occurred while opening file: &&&&. The file may not exist, or is not accessible.
Explanation:

An error during the initial processing (OPEN) of the file occurred.

EQA2262E
Ending location should be higher than starting location.
Explanation:

Modify the command providing an ending location that is higher than starting location.

EQA2263E
Total requested amount exceed size of the container.
Explanation:

Reduce size being requested. Use DESCRIBE CHANNEL to verify the size of the container.

EQA2264I
*** Global preferences file commands follow ***
Explanation:

Start of commands in the global preferences file.

EQA2265I
*** User preferences file commands follow ***
Explanation:

Start of commands in the user preferences file.

EQA2266I
*** Commands file commands follow ***
Explanation:

Start of commands in the commands file.

EQA2267I
*** Global preferences file commands end ***
Explanation:

End of commands in the global preferences file.

EQA2268I
*** User preferences file commands end ***
Explanation:

End of commands in the user preferences file.

EQA2269I
*** Commands file commands end ***
Explanation:

End of commands in the commands file.

EQA2270I
Global Preferences file exists: &&&&
Explanation:

The global preferences file is opened successfully.

EQA2271I
The setting of DEFAULT LISTINGS is:
Explanation:

This message header is for QUERY DEFAULT LISTINGS.

EQA2272W
A CICS Storage Violation has been detected. The leading/trailing check zone associated with the storage that starts at '&&&&'X for a length of &&&& has been damaged.
Explanation:

Debug Tool detected a storage violation.

EQA2273I
&&&& &&&&
Explanation:

This message contains the output from the DESCRIBE CHANNEL command.

EQA2274I
A CICS Storage Violation has not been detected.
Explanation:

Debug Tool did not detect any storage violation

EQA2275E
Insufficient storage is available to process command.
Explanation:

There was not enough main memory available to process the command.

EQA2276E
The listing file name given is too long.
Explanation:

Under MVS data definition names are limited to 8 characters and dataset names are limited to 44 characters.

EQA2277I
&&&&
Explanation:

Display results of a command.

EQA2278E
CHKSTGV command is only available in a CICS Environment.
Explanation:

The command is not supported on Non-CICS Environments.

EQA2279E
The Language Environment attempted to present a Language Environment event to Debug Tool when the user program was executing in AMode(64). Debug Tool does not currently support Language Environment events in Amode(64). The event is ignored.
Explanation:

Debug Tool currently supports AMode(64) only for assembler and disassembly.

EQA2280E
LIST CONTAINER command is only available in a CICS Environment.
Explanation:

The command is not supported on Non-CICS Environments.

EQA2281E
DESCRIBE CHANNEL command is only available in a CICS Environment.
Explanation:

The command is not supported on Non-CICS Environments.

EQA2282E
This command is not supported in this CICS Version/Release.
Explanation:

You must use CICS TS 3.1 or later to be able to use this feature.

EQA2283E
There is no container with that name in the specified channel.
Explanation:

The container name provided does not belong to the channel specified or does not exist.

EQA2284E
There are no containers to display.
Explanation:

There are no containers known to the current program.

EQA2285E
There are no channels to display.
Explanation:

There are no channels known to the current program.

EQA2286E
There is no channel with that name in this program.
Explanation:

A channel with that name was not found. Verify the name of.

EQA2287E
There is no current channel in this program
Explanation:

Read CICS Documentation on Channels and Containers.

EQA2288S
The module "module_name" cannot be loaded - it was NOT found.
Explanation:

The LOAD MODULE request failed, the module was not found.

EQA2289S
The module "module_name" cannot be loaded - there is NOT enough storage to do the load.
Explanation:

The LOAD MODULE request failed, there is not enough storage.

EQA2290S
The module "module_name" cannot be loaded.
Explanation:

The LOAD MODULE request was unsuccessful.

EQA2291S
The module "module_name" cannot be deleted.
Explanation:

The DELETE MODULE request was unsuccessful.

EQA2292S
The module "module_name" was NOT loaded by the Debug Tool and therefore CANNOT be deleted.
Explanation:

Only modules loaded by Debug Tool may be deleted.

EQA2293S
The module "module_name" cannot be loaded because it was already loaded by Debug Tool.
Explanation:

The LOAD MODULE request was unsuccessful.

EQA2294I
The LOADDEBUGDATA command for CU_name has been deferred until the CU appears.
Explanation:

The indicated CU is not currently known to Debug Tool. The LOADDEBUGDATA will be run when the CU appears in a loaded module.

EQA2295I
The CU specified for the LOADDEBUGDATA command is already an assembler or non-Language Environment COBOL CU.
Explanation:

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.

EQA2296E
The CU specified for the LOADDEBUGDATA command is not a disassembly CU.
Explanation:

Only a disassembly CU can be identified as assembler CU.

EQA2297E
An error occurred while attempting to load the debug (EQALANGX) file for a specified CU.
Explanation:

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.

EQA2298S
There is no compilation unit named compile_unit_name.
Explanation:

The compilation unit (program) that you named could not be located by Debug Tool.

EQA2299E
The EQALANGX file does not match the object for object_name. The EQALANGX file cannot be used.
Explanation:

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.

EQA2300E
A pattern of "*" is invalid.
Explanation:

The NAMES EXCLUDE command does not allow a pattern of "*".

EQA2301E
Value too long to display.
EQA2302E
Not allocated
EQA2303E
The value specified in the fourth operand of the TEST runtime parameter is not valid.
Explanation:

The value specified before the colon in the fourth operand of the TEST runtime parameter is not in the correct format.

Programmer response:

Correct the specification of the fourth TEST operand.

EQA2304E
Format of value failed
EQA2305E
NULL
EQA2306E
Register not used
EQA2307E
Invalid string
EQA2308E
Divide by zero
EQA2309E
Invalid expression
EQA2310E
Expression not supported
EQA2311E
Incompatible types
EQA2312E
Expression validation failed
EQA2313E
Expression evaluation failed
EQA2314E
Evaluation not supported
EQA2315E
Expression not evaluated
EQA2316E
Variable not found
EQA2317E
Invalid value for update
EQA2318E
Update of value not allowed at this time
EQA2319E
Update of value not supported
EQA2320E
Operation not supported
EQA2321I
Please see log window for messages
EQA2322E
Invalid address
EQA2323E
Storage unit style is not supported
EQA2324E
Storage address style is not supported
EQA2325E
Register variable(s) out of range
EQA2326E
Invalid program name
EQA2327E
Failure loading view information
EQA2328E
Failure evaluating expression context. Contact IBM support.
EQA2329E
Frequency data is not allowed with this breakpoint type.
EQA2330E
Invalid line to set a line breakpoint
EQA2331E
Initialization failure - Debug Tool and front-end levels are incompatible
EQA2332E
Invalid storage data
EQA2333E
Incomplete update - a portion of storage is not updateable
EQA2334E
Storage is not updateable
EQA2335E
Failure updating storage contents
EQA2336E
Procedure name is an internal procedure, not an entry point
EQA2337E
Breakpoint type not supported
EQA2338I
Program at end of job
EQA2339E
A DLL load occurred. Current program location cannot be determined
EQA2340I
Target program(s) loaded - START/CALL required
EQA2341E
Insufficient storage to load view
EQA2342E
Program exception has occurred
EQA2343I
Debug session initialization complete
EQA2344E
Debug file name could not be found
Explanation:

The debug file name cannot be found. The following list describes some of the possible conditions that could cause this:

EQA2345E
Debug file version not supported
EQA2346I
Maximum number of debug files (256) reached
EQA2347E
Invalid debug file name
EQA2348E
Debug file format is invalid
EQA2349E
Debug file not supported - contains multiple "@PROCESS" statements
EQA2350E
Insufficient storage to read debug file
EQA2351E
I/O error reading debug file
EQA2352E
I/O error opening debug file
EQA2353E
Debug file CSECT name does not match compile unit CSECT name
EQA2354I
USE file processing has paused - USE file is still active
EQA2355E
Altering the PSW is not supported
EQA2356E
Program not auto-started - debug file name could not be found
EQA2357E
Program not auto-started - debug file version not supported
EQA2358E
Program not auto-started - max number of debug files (256) reached
EQA2359E
Program not auto-started - invalid debug file name
EQA2360E
Program not auto-started - debug file format is invalid
EQA2361E
Program not auto-started - insufficient storage
EQA2362E
Program not auto-started - I/O error reading debug file
EQA2363E
Program not auto-started - I/O error opening debug file
EQA2364E
Program not auto-started - failure processing debug information
EQA2365E
Exit point name must be a primary entry
EQA2366E
Exit breakpoints not allowed on internal procedures
EQA2367E
Failure processing debug information. Program compiled with NOTEST
EQA2368I
Search has wrapped
EQA2369E
Invalid link pointer
EQA2370I
End of link chain reached
EQA2371E
Invalid breakpoint label name
EQA2372E
Jump to location must be within currently active program
EQA2373E
Initialization failure - extended qualification is not supported
EQA2374E
SOM object not instantiated
EQA2375E
Field is not updatable
EQA2376E
Update of field failed
EQA2377E
Invalid data
EQA2378I
Application has terminated
EQA2379E
Internal error. Please, contact IBM support
EQA2380E
Jump to Location while at initialization is not allowed
EQA2381E
The target of the Jump to Location is invalid
EQA2382E
The target of the Run to Location is invalid
EQA2383I
The environment is not yet fully initialized. Use Step or Run.
EQA2384E
The Defer option is not permitted for Line Breakpoints.
EQA2385E
The entry point is not active or debug data is not available.
EQA2386E
You are monitoring an inaccessible or uninitialized variable.
EQA2387E
Cannot modify BreakPoints. Delete existing BreakPoint then add new.
EQA2388E
Cannot monitor this type of expression or variable
EQA2389E
The C component of the LE runtime has not been initialized.
EQA2390E
Exec Imminent. Click any button to continue.
EQA2391E
Time stamp on listing does not match time stamp on object.
EQA2392E
Unable to find requested executable module.
EQA2393E
Debug Tool has frozen this thread. Registers are not available.
EQA2394E
Stop at date field references.
EQA2395E
The entered expression is invalid, please check the expression.
EQA2396E
Expression breakpoints are not supported for this language.
EQA2397E
The expression has inaccessable or uninitialized data.
EQA2398E
No hooks present at statements, breakpoint not set.
EQA2399E
Debug Tool has frozen this thread. Call stack is not available.
EQA2400E
Operations involving engine settings are currently not supported.
EQA2401E
This register cannot be edited. Changes have been ignored.
EQA2402I
Program was stopped due to load occurence breakpoint.
EQA2403I
Program was stopped due to storage change breakpoint.
EQA2404E
The debug information is not accessible for the requested thread.
EQA2405E
The PL/I component of the LE runtime has not been initialized.
EQA2406E
The Cobol component of the LE runtime has not been initialized.
EQA2407E
Too many local variables for local monitor. Use program monitor instead.
EQA2408E
Variable cannot be displayed because this compile unit was compiled without symbolic information.
Explanation:

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.

EQA2409E
The LAST option on an EXEC CICS SEND command has been suppressed.
Explanation:

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.

Programmer response:

If the LAST option needs to be exercised, consider debugging the application in dual terminal mode.

EQA2410E
Search target not found.
Explanation:

The search string was not found.

EQA2411E
Variable needs further qualification or qualification is invalid.
Explanation:

A qualified reference is invalid. One or more qualifiers may be undefined or not in the same structure as the desired data item.

EQA2412I
You are currently on an instruction that will leave the current Compile Unit and may cause Debug Tool to lose control. You must ensure that a breakpoint is set on a subsequent instruction or statement. At location LOCN.
Explanation:

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.

Programmer response:

Set a breakpoint and/or enter STEP or GO to continue.

EQA2413I
You are currently on an instruction that must run without a breakpoint. Debug Tool may lose control. You must ensure that a breakpoint is set on a subsequent instruction or statement. At location LOCN.
Explanation:

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.

Programmer response:

Set a breakpoint and/or enter STEP or GO to continue.

EQA2414I
You are currently on an instruction that is the target of an EX instruction or one that is not allowed to have a breakpoint. A breakpoint should be set on the EX or a subsequent instruction or statement. This breakpoint is removed at location LOCN.
Explanation:

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.

Programmer response:

Set a breakpoint and/or enter STEP or GO to continue.

EQA2415I
Debug Tool could not stop at one or more instructions because a valid save area backchain was not found. At location LOCN.
Explanation:

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.

EQA2416I
Debug Tool detected a missing or invalid Debug Tool SVC EQA00SVC(IGC0014E). The installed version is vers. DYNDEBUG is disabled.
Explanation:

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.

Programmer response:

Have your installer install the correct Dynamic Debug facility SVC.

EQA2417I
Not enough memory available for PLAYBACK data collection. You must DISABLE PLAYBACK.
Explanation:

The run-time API did not have enough memory to save application DATA during Playback data collection.

Programmer response:

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.

EQA2418I
Return code RC from PLAYBACK run-time API API name . You must DISABLE PLAYBACK.
Explanation:

The run-time API is no longer able to collect application DATA. The return code indicates a terminal error in the run-time.

Programmer response:

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.

EQA2419W
Playback data collection has wrapped. Earlier data has been overlayed.
Explanation:

Playback data collection has used all available memory. The earliest collected data will be overlayed with newer data.

Programmer response:

If it is necessary to retain more Playback data, specify a larger memory size on the PLAYBACK ENABLE command.

EQA2420W
The assignment was performed but the assigned value might not be used by the program, due to optimization.
Explanation:

Results might be unreliable because the program might use the previous value that was saved in temporary storage or a register.

Programmer response:

Recompile the program without the Optimize option.

EQA2421E
The assignment was not performed because the assigned value might not be used by the program, due to optimization.
Explanation:

Results would be unreliable because the program might use the previous value that was saved in temporary storage or a register.

Programmer response:

You can SET WARNING OFF to allow the update to take place or recompile the program without optimization.

EQA2422E
A breakpoint cannot be set on this statement when the STORAGE runtime option is in effect. Remove STORAGE or set the breakpoint after the next LR R13,Rx instruction.
Explanation:

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.

EQA2423S
A AbendCode ABEND occurred.
Explanation:

The indicated System or User ABEND was detected.

Programmer response:

Investigate the cause of the ABEND.

EQA2424I
Debug Tool detected a missing or invalid Debug Tool SVC EQA01SVC(IGX00051). The installed version is vers. DYNDEBUG is disabled for read only programs.
Explanation:

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.

Programmer response:

Have your installer install the correct Dynamic Debug facility SVC.

EQA2425I
Debug Tool detected a down level Debug Tool SVC EQA01SVC(IGX00051). The installed version is vers. Version 2 is required when using CICS with TRANISO=YES. DYNDEBUG is disabled.
Explanation:

During initialization Debug Tool detected a downlevel Dynamic Debug facility SVC version. The Dynamic Debug facility is disabled for read only programs.

Programmer response:

Have your installer install the correct Dynamic Debug facility SVC.

EQA2426I
Debug Tool detected a down level Debug Tool SVC EQA01SVC(IGX00051). The installed version is vers. Version 8 is required for this version of Debug Tool.
Explanation:

During initialization Debug Tool detected a downlevel Dynamic Debug facility SVC version.

Programmer response:

Have your installer install the correct Dynamic Debug facility SVC.

EQA2427I
Debug Tool detected a down level Debug Tool SVC EQA01SVC(IGX00051) or EQA00SVC(IGC0014E). EQA01SVC is version VERS. EQA00SVC is version VERS. EQA01SVC version 6 and EQA00SVC version 5 are required.
Explanation:

During initialization Debug Tool detected a downlevel Dynamic Debug facility SVC version.

Programmer response:

Have your installer install the correct Dynamic Debug facility SVC.

EQA2428E
This command is either invalid or unsupported.
EQA2429E
This command is not supported.
EQA2430E
This command is not supported with this UI.
EQA2431I
Automonitor is on for this debug session.
EQA2432I
Automonitor is off.
EQA2433E
Load Debug Data failed for :
EQA2434E
Unknown CU :
EQA2435I
This program has no statement table.
EQA2436I
The statement table has the STMT format.
EQA2437I
The statement table has the NUMBER format.
EQA2438I
The statement table has the SHORT format.
EQA2439I
The program was compiled with the following options:
EQA2440I
Program Information for this compile unit is:
EQA2441I
IBM Debug Tool Version 9 Release 1 Mod 0
Explanation:

This message is used to place the Debug Tool logo, a time stamp, and copyright at the beginning of the line.

EQA2442I
5655-U27: Copyright IBM Corp. 1992, 2008
Explanation:

This message is used to place the Debug Tool logo, a time stamp, and copyright at the beginning of the line.

EQA2443I
Assembler debug mode is active.
EQA2444I
Assembler debug mode is no longer active.
EQA2445I
Disassembly debug mode is now active.
EQA2446I
Disassembly debug mode is no longer active.
EQA2447I
The setting of LOG is on.
EQA2448I
The setting of LOG is off.
EQA2449I
Dynamic debug mode is on.
EQA2450I
Dynamic debug mode is off.
EQA2451I
The setting of WARNING is on.
EQA2452I
The setting of WARNING is off.
EQA2453E
SET DYNDEBUG can not be executed at this time. SET DYNDEBUG can only be executed at the beginning of a debugging session, before any STEP or GO commands. The DYNDEBUG status has not been changed.
EQA2454I
This CU is not AUTOMONITOR capable for expressions.
Programmer response:

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.

EQA2455E
Program uses non-standard linkage. R13 contains an invalid address.
Explanation:

Debug Tool has stopped in a program and the value in GPR 13 is not a valid address.

Programmer response:

Debug Tool will attempt to continue. However, some information may be missing or incorrect.

EQA2456I
Returning from enclave where Debug Tool was initialized. Handling of non-LE events has been suspended. Debugging of non-LE programs is suspended in this Debug Tool session.
Explanation:

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.

Programmer response:

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.

EQA2458I
SVC Screening is disabled by EQAOPTS. Handling of non-LE events is not available. Debugging of non-LE programs will be restricted in this Debug Tool session.
Explanation:

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.

Programmer response:

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.

EQA2459I
SVC Screening is in use by another product and SVC Screening CONFLICT=NOOVERRIDE is specified by EQAOPTS. Handling of non-LE events is not available. Debugging of non-LE programs will be restricted in this Debug Tool session.
Explanation:

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.

Programmer response:

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

EQA2460I
SVC Screening is in use by another product and SVC Screening CONFLICT=OVERRIDE is specified by EQAOPTS. Previous use of SVC Screening will be restored at the end of this Debug Tool session.
Explanation:

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.

EQA2461W
Code page in the VADSCP suboption is not between 00001 and 99999. Default code page 00037 is assumed.
Explanation:

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.

Programmer response:

Correct the VADSCP suboption and restart the debug session.

EQA2462W
Code page conversion of string failed. z/OS Unicode conversion services return code is VERSand reason code is VERS.
Explanation:

Problem encountered in a code page conversion using z/OS Unicode conversion services. Internal conversion tables for the default code page 00037 are used.

Programmer response:

See z/OS Support for Unicode: Using Conversion Services book for explanation of return code, reason code, and appropriate action.

EQA2463W
z/OS Unicode conversion services encountered a serious problem. Default code page 00037 is used in the debug session.
Explanation:

z/OS Unicode conversion services failed. Internal conversion tables for the default code page 00037 are used in the debug session.

Programmer response:

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.

EQA2464I
There are no &&&& names currently &&&& by &&&&.
Explanation:

This message is issued by the NAMES command when there is no data to be displayed.

EQA2465I
The following &&&& names are currently &&&& by &&&&.
Explanation:

This message precedes the output of the NAMES command and indicates the type of names that follow this message.

EQA2466I
&&&&
Explanation:

This message lists the names output of the NAMES command.

EQA2467I
The EQALANGX debug data also contains data for the following CUs:
Explanation:

This is the header used to display the additional CSECTs included in the EQALANGX data for the current CU.

EQA2468I
&&&& &&&&
Explanation:

Used to display CSECTs also included in the EQALANGX data for the current CU.

EQA2469I
The SVC Screening required for Debug Tool will be merged with the SVC Screening already active for COPE.
Explanation:

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.

Programmer response:

If you did not intend to MERGE the Debug Tool SVC Screening tables with another program, modify your EQAOPTS to specify what you require.

EQA2471I
Your Language Environment enabled application has stopped at a location where a non Language Environment compliant R13 savearea backchain exists. At location LOCN. Commands such as LIST CALLS will not operate properly.
Explanation:

In order to be Language Environment compliant your application needs to follow the Language Environment rules.

Programmer response:

Follow the Language Environment rules.

EQA2472I
Your Language Environment enabled application has stopped at a location where the non Language Environment compliant R13 savearea backchain no longer exists. At location LOCN.
Explanation:

The savearea has become Language Environment compliant and all commands will work properly.

Programmer response:

None.

EQA2473I
EQAOPTS setting SUBSYS=ssss is in effect for use when reading source code from a library system.
Explanation:

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.

Programmer response:

If you need this support, ensure that the ssss subsystem is running on the system that you are running Debug Tool on.

EQA2474I
Debug Tool could not stop at one or more instructions because the program is executing with a PSW that specifies AMODE 64. At location LOCN.
Explanation:

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.

Programmer response:

None.

EQA2475I
An implicit CU was created for "&&&&" in "&&&&".
Explanation:

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.

Programmer response:

None.

EQA2476I
An implicit LOAD was issued for module "&&&&".
Explanation:

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.

Programmer response:

None.

EQA2477I
An implicit CLEAR LOAD was issued for module "&&&&".
Explanation:

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.

Programmer response:

None.

EQA2478I
Implicit CU "&&&&" in "&&&&" is being destroyed.
Explanation:

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.

Programmer response:

None.

EQA2479S
CU "&&&&" cannot be destroyed.
Explanation:

The attempt to destroy the specified CU was unsuccessful.

Programmer response:

None.

EQA2480E
'symbol' is an undefined symbol.
Explanation:

The specified symbol was used in an assembler expression. However, it is not a valid symbol in the current compile unit.

Programmer response:

Correct the assembler expression and retry the command.

EQA2481E
Invalid syntax in expression at or near 'expression_fragment'.
Explanation:

Invalid syntax was discovered at or near the part of the expression shown in the error message.

Programmer response:

Correct the assembler expression and retry the command.

EQA2482E
Invalid expression at or near 'expression_fragment'.
Explanation:

The specified expression is invalid in the current context.

Programmer response:

Correct the assembler expression and retry the command.

EQA2483E
'operator' is an invalid operator.
Explanation:

The specified operator is not valid in an assembler expression.

Programmer response:

Correct the assembler expression and retry the command.

EQA2484E
A relational expression is not allowed in the current context or a relational expression was not found where one was expected.
Explanation:

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.

Programmer response:

Correct the assembler expression and retry the command.

EQA2485S
An internal error has occured processing an assembler expression.
Explanation:

An internal Debug Tool error has occurred processing an assembler expression.

Programmer response:

Report this error to your IBM representative.

EQA2486S
The source and receiver are not compatible for assignment.
Explanation:

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.

Programmer response:

Correct the assignment operands and retry the command.

EQA2487S
A runtime error occured processing an assignment statement. The source or receiver may not be addressable.
Explanation:

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.

Programmer response:

Report this error to your IBM representative.

EQA2488W
An LDD command was executed for a Disassembler CU that contained user breakpoints. These breakpoints have been removed.
Explanation:

The Disassembler breakpoints no longer apply to an assembler program. The user should reapply any required breakpoints.

Programmer response:

Set appropriate breakpoints.

EQA2489E
Symbol is an ambiguous or incorrectly qualified reference.
Explanation:

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.

Programmer response:

Correctly qualify the referenced variable and retry the command.

EQA2490I
The DEFAULT VIEW is now &&&&.
EQA2491I
The setting of DEFAULT VIEW is &&&&.
EQA2492I
The setting of current view is &&&&.
EQA2493I
Program was stopped due to watch breakpoint on COBOL Level-88 condition-name &&&&.
EQA2494I
Program was stopped due to watch breakpoint on COBOL Level-88 condition-name &&&& and the condition &&&& evaluated to be true.
EQA2495I
Evaluation of the conditional expression &&&& failed.
EQA2496I
The setting of LDD is now &&&&.
Explanation:

This message is issued by the remote interface in response to the SET LDD command.

Programmer response:

None.

EQA2497I
The setting of LDD is &&&&.
Explanation:

This message is issued by the remote interface in response to the QUERY LDD command.

Programmer response:

None.

EQA2498I
LOAD is not supported during initialization. STEP or GO and retry LOAD command.
Explanation:

A LOAD request cannot be issued until Debug Tool initialization is complete.

EQA2499I
A load module that was loaded as the result of a LOAD command contains LE CUs but LE is not active. The LE CUs will not be created.
Explanation:

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.

EQA2500E
Incorrect or missing data
Explanation:

The data at the cursor location is either incorrect or some data is missing. There could be several reasons for this:

  1. Invalid combination of options specified.
  2. Invalid data for field.
  3. Data not entered, when required by options given.
  4. Quotes specified when not allowed.
Programmer response:

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.

EQA2501E
DTCN internal error
Explanation:

DTCN discovered an internal error.

Programmer response:

Contact IBM service.

EQA2502E
Internal CICS error
Explanation:

During processing, DTCN discovered an internal CICS error

Programmer response:

Correct the error and issue the command again. If the error persists, contact your CICS system programmer and/or IBM service.

EQA2503E
Key Not Defined.
Explanation:

There is no action defined with the PF key used by the user.

Programmer response:

Use the keys displayed in the bottom line. For more information about the actions defined for this panel, use PF2 key for general help.

EQA2504E
Add failed - profile exists
Explanation:

The add command failed because a profile for that terminal is already stored in the Debug Tool Profile Repository.

Programmer response:

You can use Show(PF7) command to display the profile or modify the TermId+TranId and Add a new profile.

EQA2505E
Replace failed - profile does not exist
Explanation:

The profile for that terminal does not exist in the Debug Tool Profile Repository and cannot be updated. Specify different terminal to update.

Programmer response:

You can use Next(PF8) command to browse the Profile Repository starting from any point.

EQA2506E
Delete failed - profile does not exist
Explanation:

The profile for the terminal does not exist in the Debug Tool Profile Repository and cannot be updated.

Programmer response:

Specify different Terminal+Transaction Id to delete. You can use Next(PF8) command to browse the Profile Repository starting from any point.

EQA2507E
Show failed - profile does not exist
Explanation:

The profile for the Terminal does not exist in the Debug Tool Profile Repository.

Programmer response:

Specify different Terminal to display. You can use Next(PF8) command to browse the Profile Repository from any point.

EQA2508E
Next failed - profile does not exist
Explanation:

There are no more profiles in the Debug Tool Profile Repository.

EQA2510I
DTCN closed
Explanation:

DTCN deleted all profiles stored in the Debug Tool Profiles Repository. This action affects all users working with that CICS region.

EQA2511E
Specify at least one resource to debug
Explanation:

DTCN needs at least one identifier to identify the resource you want to debug.

Programmer response:

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.

EQA2512E
TCP/IP SOCKETS for CICS is not active
Explanation:

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.

Programmer response:

Either set up a non-TCP/IP session, or refer to the TCP/IP SOCKETS for CICS publications for guidance on activating it.

EQA2514I
Debug Tool profile saved
Explanation:

A profile was saved in the Debug Tool Profile Repository.

EQA2515I
Debug Tool profile replaced
Explanation:

Existing profile was updated in the Debug Tool Profile Repository.

EQA2516I
Debug Tool profile deleted
Explanation:

Existing profile was deleted from the Debug Tool Profile Repository

EQA2517I
Profile not saved. Press PF4, or PF3 again to exit without saving.
Explanation:

PF3 has been pressed, but the new profile has not been saved in the repository.

Programmer response:

Press PF4 to save the profile in the repository, or press PF3 again to exit from DTCN without saving the new profile.

EQA2518I
Duplicate profile exists. Specify additional debug resources.
Explanation:

An attempt has been made to save a profile in the DTCN repository, but its debug resources match an existing profile.

Programmer response:

Provide additional resource IDs to qualify your debugging needs better.

EQA2519E
Site rules require that this field be filled in.
Explanation:

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.

Programmer response:

Enter a resource name in the field.

EQA2520W
Terminal mismatch. Press PF10 to set the value to the current terminal identifier.
Explanation:

The terminal ID at the highlighted cursor location does not match the current terminal.

Programmer response:

Press PF10 to set the value to the current terminal identifier.

EQA2521E
Invalid field. PF10 may only be used to reset terminal or display ID.
Explanation:

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.

Programmer response:

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.

EQA2600E
In order to SET MONITOR COLUMN OFF, you need to first SET MONITOR WRAP ON.
Explanation:

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.

Programmer response:

Change the setting of MONITOR WRAP to ON, and then issue SET MONITOR COLUMN OFF.

EQA2601E
In order to SET MONITOR WRAP OFF, you need to first SET MONITOR COLUMN ON.
Explanation:

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.

Programmer response:

Change the setting of MONITOR COLUMN to ON, and then issue SET MONITOR WRAP OFF.

EQA2602E
Because SET MONITOR COLUMN is ON, the monitor window width must be at least 36 characters. The window size is not changed.
Explanation:

Because SET MONITOR COLUMN is ON, the monitor window width must be at least 36 characters. The window size is not changed.

Programmer response:

To change the Monitor window size, you need to first SET MONITOR COLUMN OFF.

EQA2603E
The width of the Monitor window is less than 36 characters. SET MONITOR COLUMN ON is not allowed.
Explanation:

Columnar format in the Monitor window can be displayed only if the width of Monitor window is bigger than 36 characters.

Programmer response:

To SET MONITOR COLUMN ON, you need first change the width of the Monitor window.

EQA2610E
There is no current channel in program.
Explanation:

Debug Tool did not find a current channel in the program. This could be because the program has not been invoked with a channel.

Programmer response:

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.

EQA2611E
The channel channel_name was not found.
Explanation:

Debug Tool could not find the channel for the program. The name might be misspelled.

Programmer response:

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.

EQA2612E
There are no channels to display.
Explanation:

There are no channels known to the current program.

Programmer response:

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.

EQA2613E
There are no containers to display.
Explanation:

Debug Tool could not find any channels known to the program. This could be because no channels have been created or assigned.

Programmer response:

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.

EQA2614E
There is no container with that name in the specified channel.
Explanation:

Debug Tool could not find the container in the channel. The names might be misspelled.

Programmer response:

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.

EQA2615E
This command is not supported in this CICS Version/Release.
Explanation:

You must use CICS Transaction Server V3.1 or later to be able to use this feature.

EQA2616E
The DESCRIBE CHANNEL command is available only in a CICS environment.
Explanation:

You cannot use the DESCRIBE CHANNEL command in a non-CICS environment.

EQA2617E
The LIST CONTAINER command is available only in a CICS environment.
Explanation:

You cannot use the LIST CONTAINER command in a non-CICS environment.

EQA2618E
There is no SOAP (DFHNODE) channel in the current program.
Explanation:

There is no channel named DFHNODE known to the current program.

Programmer response:

Follow CICS directions on creating channels and containers.

EQA2619E
The CHKSTGV command is available only in a CICS environment.
Explanation:

You cannot use the CHKSTGV command in a non-CICS environment.

EQA2620E
The requested bytes exceed the end of the container.
Explanation:

Reduce size being requested. Use DESCRIBE CHANNEL to verify the size of the container.

EQA2621E
Ending location should be higher than starting location.
Explanation:

Modify the command providing an ending location that is higher than starting location.

EQA2622E
The SET IGNORELINK command is available only in a CICS environment
Explanation:

You cannot use the SET IGNORELINK command in a non-CICS environment.

EQA2627E
The command CALL %FM is available only in a CICS environment.
Explanation:

This command requires CICS.

EQA2628E
IBM File Manager for z/OS is not installed in this CICS region.
Explanation:

The CALL %FM command requires that IBM File Manager be installed and customized for CICS.

Programmer response:

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.

EQA2629E
IBM File Manager for z/OS could not be started.
Explanation:

This command requires that IBM File Manager be installed.

Programmer response:

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.

EQA2631E
Invalid character found in an address field.
Explanation:

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.

Programmer response:

Type in hexadecimal characters, the G or R commands, or clear any characters you might have accidentally entered. Then press Enter.

EQA2632E
Invalid character found in a data field.
Explanation:

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.

Programmer response:

Type in hexadecimal characters, the G or R commands, or clear any characters you might have accidentally entered. Then press Enter.

EQA2633E
Invalid command found in a history entry field.
Explanation:

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.

Programmer response:

Type in hexadecimal characters, the G or R commands, or clear any characters you might have accidentally entered. Then press Enter.

EQA2634E
Multiple changes found in a history entry field.
Explanation:

Debug Tool found multiple changes in a history entry field of the Memory window. You can only enter one command at a time.

Programmer response:

Clear the extra characters, then press Enter.

EQA2635E
The FIND command is not valid in the Memory window.
Explanation:

You cannot use the FIND command in the Memory window.

Programmer response:

Do not use the FIND command in the Memory window.

EQA2636E
Invalid scroll amount is specified for the Memory window.
Explanation:

You cannot use any one of the following scroll amounts for the Memory window: TOP, BOTTOM, MAX, and TO.

EQA2637E
Invalid window operation. The logical window not assigned to a physical window.
Explanation:

You cannot use this command on a logical window that has not been assigned to a physical window.

Programmer response:

Use one of the following methods to assign the logical window to a physical window:

EQA2638E
Invalid Memory window width.
Explanation:

The width of the physical window assigned to the Memory window is less than the full screen width.

Programmer response:

Do one of the following:

EQA2639E
Invalid Amode value is specified.
Explanation:

The valid Amode values are 24 and 31.

Programmer response:

Enter a valid Amode value.

EQA2640E
SCROLL LEFT is not valid in the Memory window.
Explanation:

You cannot enter the SCROLL LEFT command in the Memory window. The Memory window displays memory content in the entire width of the window.

EQA2641E
SCROLL RIGHT is not valid in the Memory window.
Explanation:

You cannot enter the SCROLL RIGHT command in the Memory window. The Memory window displays memory content in the entire width of the window.

EQA2642E
Top of the memory area is reached.
Explanation:

You have reached the top of memory space that the Memory window can display.

Programmer response:

Do not enter SCROLL UP command.

EQA2643E
Bottom of the memory area is reached.
Explanation:

You have reached the bottom of memory space that the Memory window can display.

Programmer response:

Do not enter SCROLL DOWN command.

EQA2644E
L and E letters cannot be both used.
Explanation:

Look at the Window Layout Select Panel. Verify that L and E are not used in the panel layout.

EQA2645E
SCROLL TO is not valid in the Memory window.
Explanation:

You cannot enter the SCROLL TO command in the Memory window.

EQA2661W
variable_name has a length that is greater than its declared maximum. Breakpoint cannot be set until expression is fixed.
Explanation:

The variable named has been declared as VARYING with length n, but its current length is greater than n. The variable may be unuseable.

Programmer response:

Check the length of the variable.

EQA2662E
identifier is undefined.
Explanation:

The specified identifier is used but has not been defined.

Programmer response:

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.

EQA2663E
Unable to display the variable based on an invalid pointer.
Explanation:

The result from the expression evaluation cannot be displayed. For example, the basing pointer has a zero or uninitialized value.

EQA3001I
.
EQA3002I
( | )
EQA3003I
Licensed Materials - Property of IBM
EQA3004I
Copyright IBM Corp.|
EQA3005I
US Government Users Restricted Rights - Use, duplication
EQA3006I
or disclosure restricted by GSA ADP Schedule Contract
EQA3007I
with IBM Corporation.
EQA3009I
** Opened File List
EQA3010I
|
EQA3011I
** End Opened File List
EQA3012I
** Job Search List
EQA3013I
** End Job Search List
EQA3014I
** Default Search List
EQA3015I
** End Default Search List
EQA3016I
** Referenced List
EQA3017I
| | |
EQA3018I
** End Referenced List
EQA3019E
Container name exceeds maximum
EQA3020E
File name exceeds maximum
EQA3021E
Open failure on DD:JCLLIB, specifies default concatenation list
EQA3022E
Number of containers exceeds default concatenation limit
EQA3023E
Container name read from file too long
EQA3024E
Number of containers on JCLLIB exceeds limit
EQA3025E
Attempt to nest source too deeply
EQA3026E
Number of source files used exceeds limit
EQA3027E
File name for INCLUDE or external PROC name is too long
EQA3028E
INCLUDE file or cataloged PROC not found: name
EQA3030E
Container Name parameter is not valid
EQA3031E
File Name parameter is not valid
EQA3032E
Open failure on DD:INFILE, specifies JCL file
EQA3033E
Comment continuation flag was not followed by valid card
EQA3034E
End of file after comment continuation flag
EQA3038E
DLM= delimiter not two characters
EQA3039E
DLM= parameter on DD statement < 2 chars.
EQA3040W
DLM= contains & not followed by &
EQA3043E
Illegal statement found in PROC definition
EQA3046E
Illegal statement within include group
EQA3048E
PEND without matching procedure invocation
EQA3050E
Memory allocation failure
EQA3054E
Includes nested too deeply
EQA3058E
Symbolic name too long
EQA3059E
Multiple JOB cards
EQA3062E
Too many parms
EQA3063E
Parenthesis and apostrophe nesting exceeded
EQA3065E
If nesting exceeds limit
EQA3066E
ENDIF without IF
EQA3067E
Keyword parameter or SET statement missing =
EQA3068E
JCLLIB missing ORDER=
EQA3070E
EXEC card has null first parameter
EQA3071E
EXEC card PGM= has null value
EQA3072E
DD concatenation without DD statement
EQA3073E
Missing JOB card
EQA3074E
DD after JOB not JOBLIB or JOBCAT or PROCLIB
EQA3075E
Multiple JOBCAT statements
EQA3076E
Multiple JOBLIB statements
EQA3078E
Illegal statement in procedure
EQA3079E
PROC nesting exceeded limit
EQA3080E
Query empty context stack
EQA3081E
PROC stack underflow
EQA3082I
Statement: | | | |
EQA3083I
Substitution: | | | |
EQA3084E
Too many steps in job
EQA3086E
StepName.DDName too long
EQA3087E
Could not find step named on override DD
EQA3088E
Could not add DD; no PGM= steps found
EQA3089I
Added to Proc:| | | |
EQA3090I
Override Proc:| | | |
EQA3091E
Fatal Error: | | | |
EQA3092E
Statement label is too long
EQA3093E
Statement parameter text is too long
EQA3095E
Instream PROC has no name
EQA3096E
Instream PROC PEND not found before end of file
EQA3097I
Input parameters:
EQA3098E
Internal error
EQA3100W
Could not substitute DB2 run unit for SYSTSIN *
EQA3101W
Could not open|
EQA3102W
Could not find OUTPUT spec named|
EQA3103W
Could not open DD DDITV02 for DB2/IMS
EQA3104W
Could not read DD DDITV02
EQA3105W
Could not substitute DB2 run unit for DSNMVT01
EQA3108W
Could not find IMS program name
EQA3109W
Could not find IMS PSB name|
EQA3110E
Internal error
EQA3111E
Override not proceeded by named DD stmt
EQA3119E
Data set name is too long
EQA3120I
5655-U27: Debug Tool for z/OS
EQA3130I
Warning found in | | at line|
EQA3131I
Warning found in | | at line|
EQA4000E
The length of CSECT CSectName in memory is X'LMLength' which does not match the length of X'LangXLength' found in the EQALANGX data
Explanation:

The EQALANGX data does not correspond to the CSECT in the loaded load module because the CSECT length does not match.

Programmer response:

Regenerate the EQALANGX data or ensure that the matching object has been link-edited into the current load module.

EQA4001E
The object code at offset X'offset' in CSECT CSectName in memory is X'LMObject' which does not match the instructions X'LangXObject' found at that offset in the EQALANGX data.
Explanation:

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.

Programmer response:

Regenerate the EQALANGX data or ensure that the matching object has been link-edited into the current load module.

EQA4002E
The EQALANGX data for language CSECT CSectName is for a different programming language.
Explanation:

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.

Programmer response:

Regenerate the EQALANGX data or ensure that the matching object has been link-edited into the current load module.

EQA4003W
The Debug File creation date does not match the object for CompileUnit, but further validation showed that debug data in the file can still be used.
Explanation:

A Debug File containing the listing and the debugging tables does not match the creation date of the object.

EQA4004I
The setting of SET-command keyword is query-status.
Explanation:

The status of the object of a SET command is displayed when QUERYed individually.

EQA4005I
You cannot use the QUERY QUALIFY command in remote debug mode. However, the Modules view displays a list of currently loaded modules. You can expand each node on the list to view the compile unites in each module.
Explanation:

Use the Modules view to look at the load modules and programs.

EQA4006I
The current location is CU-name:>Statement-id.
Explanation:

Shows the place where the program was interrupted.

EQA4007I
You are executing commands in the Bkp-Id breakpoint.
Explanation:

Shows the bearings in an interrupted program.

EQA4008I
You are executing commands from the run-time command-list.
Explanation:

Shows the bearings in an interrupted program.

EQA4009I
You were prompted because promptCode ended.
Explanation:

Shows the bearings in an interrupted program.

EQA4010I
The program is currently entering block Block-name.
Explanation:

Shows the bearings in an interrupted program.

EQA4011I
The program is currently exiting block Block-name.
Explanation:

Shows the bearings in an interrupted program.

EQA4012I
The program is currently executing prolog code for Block-name.
Explanation:

Shows the bearings in an interrupted program.

EQA4013I
You are executing commands within a CeeCPliTest-name or equivalent function.
Explanation:

Shows the bearings in an interrupted program.

EQA4014E
There was insufficient storage to satisfy the request from ModuleName for X'Length' bytes of storage. Debug Tool might abend or your results might be unpredictable. Try increasing your region size.
Explanation:

This message is issued when there is not enough storage available to satisfy the request.

Programmer response:

Increase the storage limit (for example, the region size).

EQA4015E
Load module information could not be retrieved for module ModuleName because the loading service (provider) that loaded the module loaded it from a system managed library (e.g. LPA). The load module cannot be debugged.
Explanation:

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.

Programmer response:

Contact your System Programmer and have them place the module in a non-system managed library.

EQA4017I
Load module ModuleName was loaded from LLA. The load module information was processed from a data set found in file DDName.
Explanation:

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.

Programmer response:

None.

EQA4018E
Load module ModuleName was loaded from LLA. A load module by the same name was found in a data set found in file DDName. However, the lengths of the load modules did not match.
Explanation:

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.

Programmer response:

None.

EQA4019E
When the binder APIs extracted the debug information for load module ModuleName the length of the load module in memory did not match the length extracted by the binder APIs.
Explanation:

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.

Programmer response:

None.

EQA4020E
Load module information could not be retrieved for module ModuleName because the loading service (provider) that loaded the module loaded it from LLA and no matching copy was found in either EQALOAD or STEPLIB. The load module cannot be debugged.
Explanation:

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.

Programmer response:

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.

EQA4021I
The setting of ASSEMBLER STEPOVER is now &&&&.
Explanation:

This message is issued by the remote interface in response to the SET ASSEMBLER STEPOVER command.

Programmer response:

None.

EQA4022I
Console: File not suitable for I/O interception.
Explanation:

This message is issued by the remote interface in response to SET INTERCEPT being turned on and for COBOL DISPLAY UPON CONSOLE output.

Programmer response:

None.

EQA4023I
Console: I/O interception not supported.
Explanation:

This message is issued by the remote interface in response to SET INTERCEPT being turned on and for COBOL DISPLAY UPON CONSOLE output.

Programmer response:

None.

EQA4024I
Console: UponConsoleOP
Explanation:

This message is issued by the remote interface in response to SET INTERCEPT being turned on and for COBOL DISPLAY UPON CONSOLE output.

Programmer response:

None.

EQA4025I
&&&& &&&& &&&& &&&&.
Explanation:

This message contains the output from the DESCRIBE LOADMODS command.

EQA4026E
Load module loadmod_name could not be found.
Explanation:

The indicated load module was specified as an operand of the DESCRIBE LOADMODS command but is not an active load module.

EQA4027E
The Debug File creation date does not match the object for &&&&. The Debug File can not be used.
Explanation:

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.

EQA4040W
The "Stop When Date Fields are Accessed" breakpoint is set, but only COBOL compile units support these types of breakpoints.
Explanation:

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:

Programmer response:

If the application being debugged does not contain a COBOL compile unit compiled with the DATEPROC compiler option, remove this breakpoint.

EQA4050E
The expression or variable &&&& is not valid, undefined, or not correctly qualified.
Explanation:

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.

Programmer response:

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.

EQA4051E
This command is only valid in a CICS Environment
Explanation:

The command is only valid in a CICS Environment.

Programmer response:

None.

EQA4052I
IGNORELINK mode is now active.
EQA4053I
IGNORELINK mode is no longer active.
EQA4700E
A parse error was detected by the z/OS XML System Services parser: Return Code=rc, Reason Code=X'reason', Offset=X'buffoffset'. See the XML System Services User's Guide and Reference for a description of this error.
Explanation:

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.

EQA4701I
error_description
Explanation:

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.

EQA4702I
Context=|context|
Explanation:

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.

EQA4703I
|cursor|
Explanation:

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.

EQA4704I
XML(EBCDICorASCII) assumed.
Explanation:

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.

Programmer response:

If the correct encoding was not defaulted, specify the EBCDIC or ASCII keyword suboperand of the XML keyword.

EQA4705E
z/OS XML System Services are not installed. The command cannot be processed.
Explanation:

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.

EQA9926I
*** Allocate attempted from OPEN exit.
Explanation:

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.

Programmer response:

Refer to the following message and take the appropriate action.

EQA9927I
***Did ESPIE with CeeCaaXHCL on
Explanation:

This message is an internal diagnostic message and should not be seen unless you are using special processes as instructed by Debug Tool support.

Programmer response:

Report this message to Debug Tool support.

EQA9928W
***No ESPIE with CeeCaaXHCL on
Explanation:

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.

Programmer response:

If this message is followed by unexpected Debug Tool behavior, report the message to Debug Tool support.

EQA9929E
Debug Tool failed Product Registration. IFAEDREG RC = 00000004. The enclave will be terminated.
Explanation:

Debug Tool called IFAEDREG to check for an enabled product registration for Debug Tool. IFAEDREG indicated that the check did not succeed.

Programmer response:

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.

EQA9930W
EQA50DSP did not find a matching shift-in character so one was inserted.
Explanation:

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.

Programmer response:

Make sure there is a matching shift-in control character for each shift-out control character.

EQA9931W
Requested user interface not available. Processing will continue as if a QUIT DEBUG command had been entered.
Explanation:

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.

Programmer response:

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.

EQA9932S
Association does not exist for VTAM% specification
Explanation:

The user name specified on the VTAM% option has not been associated to a terminal using the Debug Tool Terminal Interface Manager.

Programmer response:

Use the Debug Tool Terminal Interface Manager to associate the user name with a terminal and rerun the application.

EQA9933W
CEE3MBR failed for load-module. FC=xxxxxxxx
Explanation:

The Language Environment routine CEE3MBR failed and returned the indicated feedback code.

Programmer response:

Determine the cause of the error using the indicated feedback code.

EQA9934W
Debug Tool EQA00CIC: Error loading Program. See **.SEQASAMP(EQACCDS)
Explanation:

Debug Tool Program EQA00CIC in load module EQA00OSX was unable to load the specified program.

Programmer response:

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.

EQA9935E
XXXXXXXX
Explanation:

Debug Tool has experienced a problem, and is reporting diagnostic information (usually return codes given to Debug Tool by a subsystem.)

Programmer response:

Check the log for further diagnostic messages. If there is no obvious cause for the problem, contact IBM Support.

EQA9936I
EQA00CIC Bad response from EXEC CICS cmd.
Explanation:

Debug Tool has issued an EXEC CICS command and has received an unexpected response.

Programmer response:

Check the log for further diagnostic messages. If there is no obvious cause for the problem, contact IBM Support.

EQA9937W
XPCFTCH MEA conflict- XXXXXXXX: YYYYYYYYY
Explanation:

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.

Programmer response:

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.

EQA9938E
Error in deactivate of NewProg exits.
Explanation:

Debug Tool detected an error in attempting to deactivate the NewProg supporting exits.

Programmer response:

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.

EQA9939I
IBM Debug Tool NewProg support deactivated.
Explanation:

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.

EQA9940I
IBM Debug Tool NonLE exits enabled.
Explanation:

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').

EQA9941I
IBM Debug Tool NewProg support activated.
Explanation:

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.

EQA9942I
IBM Debug Tool Screen stack exits enabled.
Explanation:

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').

EQA9943E
Error in activate of NonLE exits.
Explanation:

Debug Tool detected an error while attempting to activate the non-Language Environment supporting exits.

Programmer response:

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.

EQA9944E
Error in activate of NewProg exits.
Explanation:

Debug Tool detected an error in attempting to activate the NewProg supporting exits.

Programmer response:

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.

EQA9945S
Debug Tool DTRCB Unavailable.
Explanation:

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.

Programmer response:

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.

EQA9946S
EQA01SVC TCBSVCA2 invalid - xxx where xxx=start, stop, term, strtX, stopX
Explanation:

Internal Debug Tool SVC Screening error or Debug Tool SVC (109 extended code 51) issued outside Debug Tool. The SVC will abend.

Programmer response:

If using Debug Tool contact your IBM representative.

EQA9947S
EQA01SVC EQASVCSCREEN N/T create
Explanation:

Internal Debug Tool SVC Screening error or Debug Tool SVC (109 extended code 51) issued outside Debug Tool. The SVC will abend.

Programmer response:

If using Debug Tool contact your IBM representative.

EQA9948S
EQA01SVC No DTRCB at InitScreen
Explanation:

Internal Debug Tool SVC Screening error or Debug Tool SVC (109 extended code 51) issued outside Debug Tool. The SVC will abend.

Programmer response:

If using Debug Tool contact your IBM representative.

EQA9949S or EQA9949I
TCB SVC Screening already active and NOOVERRIDE is specified by EQAOPTS.
Explanation for Severe error:

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.

Explanation for Informational message:

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.

Programmer response:

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

EQA9950E
Error enabling XEIIN screen exit.
Explanation:

Debug Tool detected an error during the ENABLE of a required CICS exit program.

Programmer response:

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.

EQA9951E
Error enabling XEIOUT screen exit.
Explanation:

Debug Tool detected an error during the ENABLE of a required CICS exit program.

Programmer response:

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.

EQA9952E
Error in locate of Debug Tool RCB.
Explanation:

Debug Tool CICS PLT program EQA0CPLT detected an error during the search for Debug Tool region-level resources.

Programmer response:

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.

EQA9953E
NOTAUTH Error issuing CICS EXTRACT EXIT.
Explanation:

Debug Tool detected a NOTAUTH condition during an EXTRACT EXIT call to CICS.

Programmer response:

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.

EQA9954E
Invalid EXIT ENABLE request.
Explanation:

Debug Tool CICS PLT program EQA0CPLT detected an error during the ENABLE of a required CICS exit program.

Programmer response:

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.

EQA9955E
User not authorized for EXIT ENABLE.
Explanation:

Debug Tool CICS PLT program EQA0CPLT detected an error during the ENABLE of a required CICS exit program.

Programmer response:

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.

EQA9956E
Invalid program name on EXIT ENABLE.
Explanation:

Debug Tool CICS PLT program EQA0CPLT detected an error during the ENABLE of a required CICS exit program.

Programmer response:

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.

EQA9957E
Invalid CICS release. Latest CICS used.
Explanation:

Debug Tool detected an unsupported release of CICS and defaults to the latest release of CICS that this version of Debug Tool supports.

Programmer response:

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.

EQA9958I
IBM Debug Tool CICS PLT init start.
Explanation:

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')
EQA9959I
IBM Debug Tool CICS PLT init end.
Explanation:

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')).

EQA9960I
Program abend: Abcode Prog: Abprogram Ret@: XXXXXXXX
Explanation:

Debug Tool has detected abend Abcode while processing program Abprogram under CICS. Ret@ is the address of the location where the abend was issued.

Programmer response:

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.

EQA9961I
Program interrupt: Intcd Prog: Abprogram Int@: XXXXXXXX
Explanation:

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.

Programmer response:

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.

EQA9962I
IBM Debug Tool Exit Activation PLT start.
Explanation:

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.

EQA9963I
IBM Debug Tool Exit Activation PLT end.
Explanation:

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

EQA9964E
Create EQADTA name/token error. RC: RC
Explanation:

Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS.

Programmer response:

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.

EQA9965E
CEEDBGEVNTEXT Error. RC: RC
Explanation:

Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS.

Programmer response:

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.

EQA9966E
Back-level Debug Tool SVC detected. V5R1 or later SVCs required for Non-LE support.
Explanation:

Debug Tool is unable to initialize for a non-Language Environment assembler program under CICS due to back-level Dynamic Debug facility SVCs.

Programmer response:

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

EQA9967I
EQA00SVC Level:Eqa00svcVersion EQA01SVC Level:Eqa01svcVersion
Explanation:

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.

Programmer response:

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.

EQA9968E
Invalid Exit Type ...
Explanation:

Debug Tool CICS exit activation transaction DTCX is unable to determine a valid exit type to start or stop.

Programmer response:

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

EQA9969E
Select O=On or F=Off
Explanation:

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.

Programmer response:

Re-enter the transaction with an O or F parameter where O=On and F=Off.

EQA9970I
CICS exit activation successful.
Explanation:

Debug Tool CICS global user exits activated successfully.

EQA9971I
CICS exit deactivation successful.
Explanation:

Debug Tool CICS global user exits deactivated successfully.

EQA9972I
DT glueexitname CICS exit now ON.
Explanation:

Debug Tool CICS exit activation transaction DTCX successfully started the glueexitname exit where glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR.

EQA9973I
DT glueexitname CICS exit now OFF.
Explanation:

Debug Tool CICS exit activation transaction DTCX successfully stopped the glueexitname exit where glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR.

EQA9974E
Error enabling glueexitname - dtexitname.
Explanation:

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.

Programmer response:

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.

EQA9975E
Error disabling glueexitname - dtexitname.
Explanation:

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.

Programmer response:

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.

EQA9976I
DT glueexitname exit already active.
Explanation:

The requested CICS global user exit for non-Language Environment assembler support was already active. glueexitname is either XPCFTCH, XEIIN, XEIOUT, XPCTA, or XPCHAIR.

EQA9977E
dtsvcname is backlevel. Exits not enabled.
Explanation:

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.

Programmer response:

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.

EQA9978I
Unable to set hook because debug data cannot be located for program_name
Explanation:

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.

Programmer response:

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.

EQA9979I
Unable to load user program UserProgram
Explanation:

EQANMDBG was unable to load the user program specified as the first positional parameter.

Programmer response:

Ensure that the specified program name is spelled correctly and that the program is available in the standard search path for load modules.

EQA9980E
error_description
Explanation:

error_description is replaced with the following text:

(where aaaa is the CICS abend code.)

Programmer response:

Look up the CICS abend code in the CICS Messages and Codes manual and take the appropriate action to resolve the CICS abend

EQA9981I
EQAx0STO Internal Error WTO_Num
Explanation:

The internal Debug Tool storage allocation chains have been corrupted. Other forms of this message might also appear with additional information about the error.

Programmer response:

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.

EQA9982E
A non-zero response code was returned from EXEC CICS "command". Resp value = EIBRESP
Explanation:

Debug Tool has issued an EXEC CICS command, and has received an unexpected response.

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

EQA9983I
Invalid keyword value: value
Explanation:

An invalid value was specified for the indicated runtime parameter.

Programmer response:

Correct the specified value.

EQA9984I
No user program name was specified.
Explanation:

EQANMDBG was invoked without a positional parameter specifying the name of the program to be debugged.

Programmer response:

Specify an initial positional parameter indicating the name of the program to be debugged.

EQA9985I
Dynamic Debug is required for non-LE Debug Tool.
Explanation:

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.

Programmer response:

Have your system programmer complete the installation of the required Debug Tool Dynamic Debug facility SVCs.

EQA9986E
Error in CEEEV006 loading OSI
Explanation:

One of the required Debug Tool load modules is missing.

Programmer response:

Contact your system programmer to verify the proper installation of Debug Tool.

EQA9987I
First parameter to load_module is not addressable. Cannot debug this module.
Explanation:

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.

Programmer response:

Correct the parameter address passed to the LINK SVC.

EQA9988S
Debug Tool has terminated the enclave.
Explanation:

A Debug Tool QUIT command was issued in a multi-enclave environment.

Programmer response:

No action is necessary.

EQA9989I
EQANMDBG requires Debug Tool V5R1 or later SVC.
Explanation:

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.

Programmer response:

Have your system programmer install the current V5R1 or later Debug Tool Dynamic Debug facility SVCs.

EQA9990I
LOAD detect.
Programmer response:

This is an internal Debug Tool message. No user response is required.

EQA9991E
Error loading load_module
Explanation:

An error was encountered loading the specified load module.

Programmer response:

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.

EQA9992E
Internal error processing Language Environment service FunctionCode
Explanation:

An internal Debug Tool error has occurred.

Programmer response:

Check the Debug Tool web site for any applicable service updates your system might require. If the problem persists, contact Debug Tool support.

EQA9993I
EQA00OHT: Failed to set hook in R/O storage
Explanation:

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.

Debug Tool Action:

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.

Programmer response:

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

EQA9994E
No storage for DT RCB
Explanation:

There is insufficient storage for Debug Tool to initialize.

Programmer response:

Increase the region size availalable to the program and rerun.

EQA9995E
REQUIRED TEXT
Explanation:

All EQA9995E messages signify a severe error has occurred in the Dynamic Debug facility SVC routine while processing an 0A91 instruction.

Programmer response:
  1. Make sure none of the applications you are debugging issue the reserved 0A91 (SVC 145) instruction.
  2. If you have non-IBM products installed on your system, make sure none of them issue the reserved 0A91 (SVC 145) instruction.
  3. Try running the Dynamic Debug facility IVP (Installation Verification Program). This program can be found in member EQAWIVPS of data set EQAW.SEQASAMP.
  4. Have your system support person re-install the Dynamic Debug facility SVC using member EQAWISVC of data set EQAW.SEQASAMP and then run the IVP (see step 3).
  5. Check the Debug Tool web site for any applicable service updates your system might require.
  6. If the problem persists, report the error message text, return code, and reason code to your IBM representative.
EQA9996E
ERROR DESCRIPTION
Explanation:

A severe error has occurred in the Debug Tool Authorized Debug Facility SVC routine EQA01SVC. EQA01SVC is SVC 109 with extended function code 51.

Programmer response:

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.

EQA9997E
ERROR DESCRIPTION
Explanation:

The ASMADOP module could not be loaded. Debugging via a Disassembly View cannot be supported.

Programmer response:
  1. Have your system support person verify that the ASMADOP module is available (in the search path).
  2. Check the Debug Tool web site for any applicable service updates your system might require.
  3. If the problem persists, report the error message text to your IBM representative.
EQA9998I
Debug Tool DTCN profile skipped.
Explanation:

The Debug Tool profile has been skipped because a more qualified profile has been found or an older, equally qualified, profile has been found.

Programmer response:

Additional EQA9998I messages will follow. See the details of these additional messages for the appropriate response.

EQA9999E
ERROR DESCRIPTION
Explanation:

Severe Internal Error in Debug Tool Module
Please contact your IBM Representative
Failure address - xxxxxxxx
Program Check at module+offset
Programmer 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.

EQA9999W
ERROR DESCRIPTION
Explanation:

Warning Message issued by Debug Tool Module

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


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)