Previous Topic: Messages

Next Topic: Server Component (SCM) Messages


Main Task (MTK) Messages

The following descriptions list the reasons and actions for main task messages:

CAHFMTK001E

Failed to setup CCI communication, please check server ID

Reason:

Error Message—During initialization, the server task was unable to establish connection to CAICCI (Common Communication Interface).

Action:

The server task will end due to this error. Verify that CAICCI and CCITCP tasks are active. If not, start CAICCI and CCITCP and then start CA DRAS. If the problem persists, contact CA Support for assistance.

CAHFMTK002E

Failed to terminate CCI communication

Reason:

Error Message—the CAICCI communication link could not be properly closed when the CA DRAS task was shut down.

Action:

If the CAICCI and CCITCP tasks are active, check to see if any error messages or abends have occurred.

CAHFMTK003I

CCI communication terminated

Reason:

Informational Message—the server task has successfully terminated communication with CAICCI. This occurs once during CA DRAS shut-down.

Action:

None.

CAHFMTK004I

CCI communication started

Reason:

Informational Message—the server task has successfully established communication with CAICCI. This occurs once during CA DRAS startup.

Action:

None.

CAHFMTK005I

Request processing threads created

Reason:

Informational Message—the server task has successfully created its processing threads. This occurs once during startup.

Action:

None.

CAHFMTK007E

Erroneous status (<status>) from CCI receive

Reason:

Error Message—an error occurred during data transmission. An asynchronous request has completed with a non-zero status. The server task will terminate (RC=16).

Action:

Check the CAICCI and CCITCP tasks for problems. Restart the CA DRAS task. If the problem persists, contact CA Support for assistance.

CAHFMTK008E

Cannot get CCI conversation ID

Reason:

Error Message—an error occurred during data transmission. The incoming data (from an asynchronous CCI request) was not part of a CCI conversation established by/for the CA DRAS task. The server task will terminate (RC=16).

Action:

Check the CAICCI and CCITCP tasks for problems. Restart the CA DRAS task. If the problem persists, contact CA Support for assistance.

CAHFMTK009E

No conversation ID for incoming data

Reason:

Error Message—CA DRAS was unable to obtain the CAICCI conversation ID from the incoming data (an asynchronous CCI request). The input data is ignored.

Action:

If there are a large number of these errors, contact CA Support for assistance.

CAHFMTK010E

Cannot get CCI sender's ID

Reason:

Error Message—CA DRAS was unable to obtain the CAICCI sender ID from the incoming data (from an asynchronous CCI request). The server task will terminate (RC=16).

Action:

Check the CAICCI and CCITCP tasks for problems. Restart the CA DRAS task. If the problem persists, contact CA Support for assistance.

CAHFMTK011E

Cannot get CCI incoming data length

Reason:

Error Message—CA DRAS was unable to obtain the data length from the incoming data (from an asynchronous CCI request). The server task will terminate (RC=16).

Action:

Check the CAICCI and CCITCP tasks for problems. Restart the CA DRAS task. If the problem persists, contact CA Support for assistance.

CAHFMTK012E

Cannot create a PQE for the incoming request

Reason:

Error Message—CA DRAS was unable to create a process queue element (PQE) for the incoming data (from an asynchronous CCI request).

Action:

Restart CA DRAS and monitor the task's storage usage. Verify that the task has adequate region for processing. Also check the CAICCI and CCITCP tasks for errors. If the problem persists, contact CA Support for assistance.

CAHFMTK013E

CCI send for conid(<conversation id>) failed, status = <status code>, reason = reason code>

Reason:

Error Message—CA DRAS unsuccessfully replied to a client application that had made a CCI request. This is most likely to occur if the client application that initiated the CCI request was no longer active/receiving when the request was completed by the server. This message is always followed by CAHFMTK020I.

Action:

Check the status of your CA OM Web Viewer to determine if there are any problems with the client application. Monitor the task for additional problems. If the problem persists, contact CA Support for assistance.

CAHFMTK014I

Output message(<address>) messageLength(<size>) sent to client(<cci name>) conid(<conversation id>)

Reason:

Informational Message—CA DRAS has successfully replied to a client application that had made a CCI request.

Action:

None.

CAHFMTK015E

conid(<conversation id>) has invalid output data dataBuffer(<address>) dataLength(<size>)

Reason:

Error Message—an error occurred when CA DRAS attempted to reply to an asynchronous CCI request. This is most likely to occur if the client application that initiated the CCI request was no longer active/receiving when the request was completed by the server.

Action:

Check the status of your CA OM Web Viewer to determine if there are any problems with the client application. Monitor the task for additional problems. If the problem persists, contact CA Support for assistance.

CAHFMTK016I

DRAS is terminating

Reason:

Informational Message—the CA DRAS task has begun shutdown processing as a result of a STOP command. This occurs once during CA DRAS shutdown.

Action:

None.

CAHFMTK018E

Failed to initialize server(<server name>)

Reason:

Error Message—problems occurred during initialization preventing the server task from starting.

Action:

None—this message follows other, more descriptive error messages.

CAHFMTK019E

Failed to process configuration file, status = <status code>

Reason:

Error Message—problems occurred during initialization.

Action:

Check the configuration file (referenced by the DRASCFG DD statement) for errors. Correct any errors and then restart the task. If the problem persists, contact CA Support for assistance.

CAHFMTK020I

Cancel connection for client(<cci name>) conid(<conversation id>)

Reason:

Informational Message—the CA DRAS task is canceling the CCI connection for a client. The message always follows error message CAHFMTK013E.

Action:

None.

CAHFMTK021I

CA DRAS server (<server genlevel>) started

Reason:

Informational Message—the server task has been started. This message also lists the CA DRAS version and maintenance level.

Action:

None.

CAHFMTK022I

Client(<cci name>) not found, connection for this client has been canceled

Reason:

Informational Message—the CA DRAS task is canceling the CCI connection for a client. The message generally follows error message CAHFMTK013E.

Action:

None.

CAHFMTK023S

Log task ABEND. CA-DRAS is terminating.

Reason:

The CA DRAS logging subtask has abended and CA DRAS has terminated with a U0100 abend.

Action:

Try to restart CA DRAS. Report the problem to CA Support.

CAHFMTK025S

Critical task ABEND. CA-DRAS is terminating.

Reason:

A critical subtask has abended and CA DRAS has terminated with a U0300 abend.

Action:

Try to restart CA DRAS. Report the problem to CA Support.

CAHFMTK026S

Processing thread ABEND. n of t threads still running.

Reason:

A processing subtask has abended. There are still n of the original t threads running. (t is the number you specified in the SET THREADS command.)

Action:

Continue to monitor CA DRAS. If the number of remaining threads falls too low to support your workload, shut down and restart CA DRAS. Report the error to CA Support.

CAHFMTK027S

All processing threads have ABENDED. CA-DRAS is terminating.

Reason:

All processing threads have abended and CA DRAS has terminated with a U0400 abend.

Action:

Try to restart CA DRAS. Report the problem to CA Support.

CAHFMTK028E

Command is only allowed in the configuration file

Reason:

You have entered a command from the console that is only allowed in the configuration file (referenced by the DRASCFG DD statement).

Action:

To complete the action you requested, put it in the configuration file and recycle CA DRAS.

CAHFMTK029I

Message echoing turned x

Reason:

Informational Message—displays the ECHO condition for message echoing, where x can be ON or OFF.

Action:

None.

CAHFMTK030I

Message suppression turned x

Reason:

Informational Message—displays the condition for message suppression, where x can be ON or OFF.

Action:

None.

CAHFMTK031I

message-id added to echoed messages list

Reason:

Informational Message—indicates the specified message ID, routing, and descriptor code will be added to a linked list of echoed messages.

Action:

None.

CAHFMTK032I

Longwait timeout set to mins minutes

Reason:

Informational Message—indicates session time-out time in the LONGWAIT command, where mins equals the minutes specified before idle users' sessions will be terminated.

Action:

None.

CAHFMTK033I

Longwait timeout has been turned off

Reason:

Informational Message—indicates that the LONGWAIT command has been disabled and CA DRAS is not checking for idle users.

Action:

None.

CAHFMTK034W

Language language not found

Reason:

Warning Message—CA DRAS cannot find the language specified in the configuration file.

Action:

Verify the language in the configuration file. Otherwise, the default translation tables will be used.

CAHFMTK035W

Load module CAHFDCPG not found

Reason:

Warning Message—CA DRAS cannot find the codepage load module.

Action:

None. The default translation tables will be used.

CAHFMTK036W

Default translation tables will be used

Reason:

Warning Message—This message follows either CAHF034W or CAHF035W.

Action:

None.

CAHFMTK038S

Unable to find CAHARLSE module

Reason:

Severe error. CA DRAS cannot find CA View CAHARLSE module. CA DRAS terminates with return code 8.

Action:

Determine why there is no CAHARLSE module in the CA View CAILIB. This could also be because there is no CA View CAILIB available to CA DRAS. Correct and restart CA DRAS.

CAHFMTK039S

Unable to find CADSRLSE module

Reason:

Severe error. CA DRAS cannot find CA Dispatch CADSRLSE module. CA DRAS terminates with return code 8.

Action:

Determine why there is no CADSRLSE module in the CA Dispatch CAILIB. This could also be because there is no CA Dispatch CAILIB available to CA DRAS. Correct and restart CA DRAS.

CAHFMTK040S

Invalid product code pppppppp

Reason:

Severe error. pppppppp is a product code specified in the PROD parameter of the ACCESS configuration statement and it is invalid. CA DRAS terminates with return code 8.

Action:

Correct the product code. Restart CA DRAS.

CAHFMTK041S

Release mismatch. Product: pppppppp

Reason:

Severe error. pppppppp is a product code specified in the PROD parameter of the ACCESS configuration statement. It does not match the release number in the product's CAILIB. For example, DISPAT11 (meaning CA Dispatch r11.n) has been entered on an ACCESS statement, but the CAILIB is for a non-supported CA Dispatch. CA DRAS terminates with return code 8.

Action:

Either correct the ACCESS statement or make available a CAILIB for the release of the product you want to use. Restart CA DRAS.