Error Codes › WD Messages

WD Messages

This section lists the reasons and actions for WD messages.

WD00

Reason:

CAIRIM was not active when the #RIMSTAT macro was invoked.

Action:

Ensure that CAIRIM is installed and active before starting CA InterTest for CICS.

WD01

Reason:

Reserved

Action:

None, this is an informational message.

WD02

Reason:

The TWA size for the transaction ICDB is less than 1536.

Action:

Increase the TWA size for the ICDB transaction to 1536 or more.

WD03

Reason:

Reserved

Action:

None, this is an informational message.

WD09

Reason:

CA InterTest for CICS communication failure.

Action:

Ensure that the workstation GUI interface was not disconnected from the CICS region. If the GUI was not disconnected then activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON command and the ICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD12

Reason:

An internal error; TCP/IP send failure.

Action:

Ensure that the workstation GUI interface was not disconnected from the CICS region. If the GUI was not disconnected then activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL =ITTRACE,ON command and the ICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD13

Reason:

An internal TCP/IP receive failure occurred.

Action:

Ensure that the workstation GUI interface was not disconnected from the CICS region. If the GUI was not disconnected then activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON command and the ICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD14

Reason:

Could not load the CA InterTest for CICS IN25CUI9 message block module.

Action:

Ensure that the CA InterTest for CICS load module library in the CICS DFHRPL contains IN25CUI9. If the load module library contains IN25CUI9, activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD15

Reason:

Could not load the CA InterTest for CICS IN25PGM2 module.

Action:

Ensure that CA InterTest for CICS has been successfully started. If CA InterTest for CICS was successfully started, then activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD16

Reason:

Could not locate the CA InterTest for CICS PROM table.

Action:

Ensure that CA InterTest for CICS has been successfully started. If CA InterTest for CICS were successfully started, then activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD17

Reason:

Could not locate the CA InterTest for CICS PROM table appendix.

Action:

Ensure that CA InterTest for CICS has been successfully started. If CA InterTest for CICS was successfully started, then activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD18

Reason:

CA InterTest for CICS debugger internal logic error; unknown TWA function request.

Action:

Ensure that CA InterTest for CICS has been successfully started. If CA InterTest for CICS was successfully started, then activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD22

Reason:

The ICDB transaction was not initiated by the graphical user interface PC user.

Action:

Ensure that ICDB transaction was started by the CA InterTest for CICS PC user. Otherwise, activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD34

Reason:

CA InterTest for CICS internal logic error; no message block.

Action:

Issue the CA InterTest for CICS CNTL=ITTRACE_ON command and the ICDB TRACE_ON command. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD45

Reason:

CA InterTest for CICS internal logic error; invalid TWA user function request.

Action:

Ensure that CA InterTest for CICS has been successfully started. If CA InterTest for CICS were successfully started, then activate the CICS auxiliary trace. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal. For assistance, contact CA technical support.

WD46

Reason:

CA InterTest for CICS internal logic error; unknown error condition.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD47

Reason:

CA InterTest for CICS internal logic error; product version error.

Action:

For assistance, contact CA technical support.

WD48

Reason:

An internal TCP/IP macro failure; SEND failure.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and the ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD49

Reason:

An internal TCP/IP macro failure; RECEIVE failure.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD50

Reason:

CA InterTest for CICS internal logic error; unknown error encountered.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD51

Reason:

CA InterTest for CICS internal logic error; corrupt program save area.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD56

Reason:

CA InterTest for CICS internal logic error; PC-to-Mainframe session link error.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD57

Reason:

CA InterTest for CICS internal logic error; EXEC CICS LOAD command error.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD62

Reason:

CA InterTest for CICS internal logic error; security authorization failure on an execution of an EXEC CICS command.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD63

Reason:

CA InterTest for CICS internal logic error; EXEC CICS command error.

Action:

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.

WD66

Reason:

CA InterTest for CICS internal error; invalid TWA length.

Action:

The TWA size for the transaction must be equal to or greater than 1536 bytes. If it is equal to or greater than 1536 then activate the CICS auxiliary trace.

Activate the CICS auxiliary trace. Then issue the CA InterTest for CICS CNTL=ITTRACE_ON and ICDB TRACE_ON commands. Retry the sequence of events that caused the error. Then collect the auxiliary trace, the transaction dump, and any relevant messages sent to the terminal or the systems console. For assistance, contact CA technical support.