Reason
The CA ACF2 for DB2 synchronization utility was unable to verify the existence and attributes of the DB2 subsystem ssss. The named DB2 subsystem must not only be defined to the system but must also be active at the time that the synchronization job is run.
The xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx provides additional information relating to the DB2 validation failure. Reasons include the following:
DB2 SUBSYSTEM NOT FOUND
The named subsystem ID was not found. Check your input control statements and cross‑check these against your system definitions.
DB2 SUBSYSTEM NOT ACTIVE
An entry for the named DB2 subsystem was found in the subsystem name table, but the CA ACF2 for DB2 synchronization utility determined that the subsystem was inactive. The named DB2 subsystem must be active to run the synchronization utility.
DB2 SUBSYSTEM VALIDATION ERROR
An internal error occurred while validating the named DB2 subsystem ID. This might be due to an internal or an environmental error. Gather job log information, job output, and any dumps and contact CA Technologies Technical Support for assistance. Be prepared to provide a system dump if requested.
APF AUTHORIZATION REQUIRED
The CA ACF2 for DB2 synchronization utility must run from an APF‑authorized library. An authorization check failed. Ensure that the synchronization utility is run from an APF‑authorized library.
UNKNOWN ERROR
An internal error occurred while validating the DB2 subsystem name. This might be due to an internal or an environmental error. Gather job log information, job output, and any dumps, and contact CA Technical Support for assistance. Be prepared to provide a system dump if requested.
Action
See the reason code description above.
|
Copyright © 2006 CA Technologies.
All rights reserved.
|
|