Rational Developer for System z, Version 7.6

Non-Language Environment IMS messages

Each message has a number of the form EQAInnnnx, where EQAI indicates that the message is non-Language Environment IMS™ message, nnnn is the number of the message, and x indicates the severity level of each message. The variable x can be any of the following values:

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.

EQAI1002S
CSVQUERY failure
Explanation:

Query application MPP failed.

User response:

Consult your system programmer.

EQAI1003S
Environment AIB call failed
Explanation:

Query environment AIB call failed.

User response:

Consult your system programmer.

EQAI1004S
Environment IOPCB call failed
Explanation:

Query environment IOPCB call failed.

User response:

Consult your system programmer.

EQAI1008S
Error loading EQANIDBG
Explanation:

Load Debug Tool non-Language Environment front end failed.

User response:

Consult your system programmer.

EQAI1009S
Invalid EQASET specification
Explanation:

Load Debug Tool non-Language Environment front end failed.

User response:

Consult your system programmer.

EQAI1013S
Retrieve of token failed with rc returncode
Explanation:

Fail to retrieve token (EQAuser_ID). The return code is returncode.

User response:

Run the EQASET transaction from the terminal where the application transaction is invoked.

EQAI1020S
Retrieve token failed
Explanation:

Fail to retrieve token.

User response:

Start EQASET transaction with a valid keyword (MFI, TCP, VTCP, VTAM®).

EQAI2005I
DEBUG SET ON FOR MFI SETTING
Explanation:

Debugging is turned on and setting is MFI.

User response:

None.

EQAI2006I
DEBUG SET ON FOR TCP SETTING
Explanation:

Debugging is turned on and setting is TCP.

User response:

None.

EQAI2007I
DEBUG SET ON FOR VTCP SETTING
Explanation:

Debugging is turned on and setting is VTCP.

User response:

None.

EQAI2008I
DEBUG SET OFF
Explanation:

Debugging is turned off.

User response:

None.

EQAI2009I
DEBUG SET ON FOR SPECIFIED MFI LU
Explanation:

Debugging is turned on and setting is the specified MFI LU name.

User response:

None.

EQAI2010I
DEBUG SET ON FOR SPECIFIED TCP IP
Explanation:

Debugging is turned on and setting is the specified MFI LU name.

User response:

None.

EQAI2011I
DEBUG SET ON FOR SPECIFIED VTCP IP
Explanation:

Debugging is turned on and setting is the specified VTCP IP address.

User response:

None.

EQAI2012I
VALID KEYWORDS: ON, OFF, MFI=, TCP=, VTCP, VTAM=, STATUS
Explanation:

Valid keywords for EQASET transaction.

User response:

None.

EQAI2013E
USERID FROM IMS ENVIRONMENT IS BLANK
Explanation:

User ID is blank or cannot be found.

User response:

Contact your system programmer.

EQAI2014E
NO DATA RECEIVED
Explanation:

EQASET transaction is entered without keyword.

User response:

Reference documentation for EQASET definition and usage.

EQAI2015E
NAME/TOKEN SAVE FAILED RC= returnCode
Explanation:

Fail to save setting value.

User response:

Contact your system programmer.

EQAI2016E
MFI/TCP/VTCP VALUE MUST BE SET TO USE KEYWORD ON
Explanation:

No setting exists when debugging is turned on with EQASET ON.

User response:

Set value of one of the settings (MFI, TCP, VTCP) with EQASET transaction.

EQAI2017I
NO STATUS
Explanation:

No on/off switch exists.

User response:

Set value of one of the settings (MFI, TCP, VTCP) with EQASET transaction.

EQAI2018I
DEBUG SET ON FOR SPECIFIED VTAM LU
Explanation:

Debugging is turned on and setting is the specified VTAM LU associated with user id.

User response:

None.

EQAI2019I
DEBUG SET ON FOR VTAM SETTING
Explanation:

Debugging is turned on and setting is VTAM.

User response:

None.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)