13

001

Reason:

During the execution of the caller's database command, the client interface requested a data translation descriptor from the server. The request failed.

Action:

Run a PXX report to obtain detailed information about the failure.

37

001

Reason:

A connection to the server has not been properly established for the caller. (An unknown attachment handle was passed to Wdbntry( ).)

Action:

Before issuing any database commands, make sure that an ODBC session has been properly established and that the correct handle was obtained from ODBC.

002

Reason:

The Work Area where the results of the database command were supposed to be stored is not large enough to hold the result.

Action:

Increase the size of the Work Area.

68

002

Reason:

An attempt to establish a connection to the server failed.

Action:

Calling WGetErrInfo( ) will provide a detailed error message.

194

(BAD_TRANS_ACTION)

Reason:

An error occurred in data translation.

Action:

Examine the data being sent to or received from the server and correct it.

196

(CCI_CONV_PROBLEM)

Reason:

An error occurred in conversing with the server.

Action:

Calling WGetErrInfo( ) will obtain a detailed error message.

68

202

(MSG_PART_OVERFLOW)

Reason:

When receiving a reply from the server, the client interface received a message that contained a component longer than expected.

Action:

For assistance, contact CA Support at http://support.ca.com.

207

(BAD_LENGTH)

Reason:

The total length of the message to be sent to the server exceeded 32767 bytes.

Action:

Modify the request to reduce the number of bytes transmitted from the client to the server.

209

(FLOAT_ERROR)

Reason:

An error occurred during the translation of floating-point data.

Action:

Examine the data being sent to or received from the server and correct it.

222

Reason:

The server was unable to obtain memory to fulfill the request.

Action:

Increase the size of the partition/address space used by the server.

223

Reason:

The request type received by the server was invalid. This could be caused by attempting to use navigational commands with an r2 server.

Action:

For assistance, contact CA Support at http://support.ca.com.

224

Reason:

The attachment handle received by the server was unknown.

Action:

For assistance, contact CA Support at http://support.ca.com.

226

Reason:

The server encountered a communications (CAICCI) error.

Action:

Contact your server administrator.

233

Reason:

The server could not load the RAAT/CBS command processor (SVNATPR).

Action:

Contact your server administrator.

234

Reason:

The server could not load the Metadata command processor (SVMDTPR).

Action:

Contact your server administrator.

235

Reason:

The server could not load the URT processor (SVURTPR).

Action:

Contact your server administrator.

89

002

Reason:

During the execution of a database command, the client interface software attempted to allocate memory. The request failed.

Action:

Increase the amount of memory available to the client interface software by closing unused applications (Windows). If the problem persists, contact CA Support at http://support.ca.com.