CA 7 R12.0 database is now managed by Ca Datacom/AD so the upgrade from CA7 11.3 to 12.0 includes some conversion steps in order to move from the 11.3 CA7 VSAM DB structure to the 12.0 CA7 Datacom DB structure. These steps are fully documented in CA7 12.0 Installation Guide topic ‘Database Conversion’.
In conversion Job AL2DCC50 it is executed the Database Export Import utility to import into Datacom/AD tables the export file created by conversion job AL2DCC20.
It will be necessary to specify the logical database name that should be assigned to this CA 7 instance using the ‘IMPORT=logicaldbname’ parameter.
If this job does not complete with return code 0, CA Support should be contacted before continuing to the next step.
Sometime, during conversion job AL2DCC50 execution, frequent CA Datacom DBUTLTY SPILLs are requested if there is a big file to import in Datacom/AD tables, so there is a lot of logging activity which can cause LXX file to fill quickly.
While running this CA Datacom DBUTLTY SPILL job, the error
DB13074E - ACTIVE JOB AL2DCC50 PREVENTING SPILL
can occur and the SPILL job fails, preventing the conversion job AL2DCC50 to complete successfully.
How to correct this problem?
CA 7 R12.0 - Datacom
This is the message text for the DB13074E message, as reported in the Datacom DB R14
Message Reference Guide:
ACTIVE JOB jjjjjjjj PREVENTING SPILL
The SPILL utility function was executed when the log had data, but none was spillable. The job name appears in the message text. This is an error situation and the utility abends.
Wait to attempt a spill until Multi-User indicates data is spillable.
Since the CA Datacom Log file keeps records based on time, when it is time to spill, the utility will start at the "oldest" block that has not already been spilled, and will spill the log - block by block. This message indicates that the oldest block (or "first" block) eligible to be spilled could not, because some job was still running that had active log records in that block, and the block was held in case the job failed and needed to back out.
The DB13074E error referred to job AL2DCC50 occurs because there is an unusual situation in which a single job (in this case AL2DCC50) fills the LXX file with its logging activity.
Anyway the SPILL can only occur after Datacom task has forced a checkpoint for the job which is runnig and it is currently active. Only after Ca Datacom has logged the following message after the last SPILL:
DB00104I - CHKPT JOB-AL2DCC50 NUMBER-61381 TSN-000…
it is possible to run a new SPILL successfully .
If the batch job AL2DCC50 requests a new SPILL too quickly (so before the above DB00104I message is got after the last SPILL) the error DB13074E occurs.
To bypass this inconvenience, which is not an error inside Datacom or CA7 but simply the effect of a very unusual temporary situation, there are some suggestions that can be applied:
1. Temporarily disable the automatic SPILL job submission in CA Datacom.
2. Temporarily lower the Log filling threshold value which engages an automatic Datacom checkpoint (this is the second value into the LOGSPILL parm specified to MUF task).
3. Temporarily increase the LOG file size to have less frequent SPILL requests or anyway the SPILL requests delayed against the DB Checkpoint message DB00104I. (This is usually the first option to try in this unusual situation).
For more information about the Logging process, please consult the CA Datacom/DB Database and System Administration Guide, in the section "Operating with Logging Active › Opening the Log Area (LXX)."
For more information about the DBUTLTY SPILL process, please consult the CA Datacom/DB DBUTLTY Reference Guide, in the section "SPILL (Transfer Data to RXX)," or the section "SPILLOPT (Transfer Data to RXX Using MAX/MIN)."
As always, please contact CA Technologies Support if you have further questions.