CA-7.200 - BOTH LOG FILES ARE FULL

Products

• CA 7 Workload Automation

Issue/Introduction

Why does CA 7 issue the following WTOR?

CA-7.200 - BOTH LOGS FILES ARE FULL

CA-7.200 - AWAITING REPLY: LOGP, LOGS, OR CANCEL

Cause

 

 

Resolution

CA 7 is unable to write to neither LOGP or LOGS because the LOG dump jobs have not run. This will cause CA 7 to hang until the WTOR is replied to.

 

PERFORM THE FOLLOWING TO ADDRESS THE ERROR to allow CA 7 to resume processing:

 

1.  Run both LOGP and LOGS dump jobs outside of CA 7.

2.  Reply to the WTOR message CA-7.200 (LOGP or LOGS) CA 7 will resume processing.

 

Now you need to determine why the job(s) didn't run and take corrective action to prevent the WTOR from being issued again.

 

Things to check:

 

-  Check to see if the log dump jobs are currently in the active workload queue by issuing command:  LQ,JOB=xxxxxxxx  (where xxxxxxx is the log dump jobs)

   If the job is found in the REQ queue, address the outstanding requirement.      

   If the job is found in the RDY queue, determine if the job was submitted and what happened to the job.

   The job will need to be cancelled from the queue.  

-  Check the run log to see when the jobs last ran: LRLOG,JOB=xxxxxxxx  (where xxxxxxx is the log dump jobs)

-  If the job never entered the queue you need to run the SASSHIS8 Report-08 for the timeframe the WTOR was issued.  

   Do a find on the log dump jobs and check messages for any problem.

-  After correcting the problem, demand the log dump job that was not active (either LOGP or LOGS) and make sure it completes.

   

If unable to determine, please open a support case.