Previous Topic: DBH6001ENext Topic: CA Datacom/DB Return Codes


DBH6003E

#HCHECK FUNCTION=CHK=MSG FAILED RC=nn with R0=nn

Reason:

A CA Datacom health check attempted to write health checker message text using the CHK-MSG function provided by CA Common Services for z/OS. This attempt received a non-zero return code.

Action:

Check for other error messages. If there are none, contact CA Support.

DBH6004E

Risk of MUFPLEX failure because Coupling Facility structure $STRNAME is too small.

Reason:

The DTCM_DB_CF_LIST-STR health check of CA Datacom found an exception condition. This is because the Coupling Facility structure currently is not large enough to handle a MUFPLEX mode 'A' or 'B' configuration.

Action:

Detail user response information is contained in the actual DTCM_DB_CF_LIST-STR health check text.

DBH6005E

Risk of MUFPLEX failure because Coupling Facility structure &STRNAME is too small

Reason:

The DTCM_DB_CF_LIST-STR health check of CA Datacom found an exception condition. This is because the Coupling Facility structure currently is not large enough to handle a MUFPLEX mode 'S' configuration.

Action:

Detail user response information is contained in the actual DTCM_DB_CF_LIST-STR health check text.

DBH6006E

List structure &STRNAME not defined to the coupling facility

Reason:

The DTCM_DB_CF_LIST-STR health check of CA Datacom found an exception condition. This is because the Coupling Facility structure currently was not present during the initialization in a MUFPLEX mode 'A' or 'B' configuration.

Action:

Detail user response information is contained in the actual DTCM_DB_CF_LIST-STR health check text.

DBH6007E

One or more CA Datacom/DB transactions have been force check pointed.

Reason:

The DTCM_DB_FORCE_CHKPT health check of CA Datacom found an exception condition due to a log file force checkpoint occurring.

Action:

Detail user response information is contained in the actual DTCM_DB_CF_LIST-STR health check text.