This problem happens when a backup program has a lock on the XCOM log at the same time as CA XCOM is trying to use the log. CA XCOM is programmed to wait for the log to become available. Unfortunately, when the log that is being backed up is very large, the time that CA XCOM waits expires before the log becomes available.
In this case, there are two options to resolve the problem:
- Reduce the size of the log.
- Increase the amount of time that CA XCOM will wait for the log to become available.
The parameter that controls the amount of time a process will wait for the resource it needs is ' Default Wait Time in Seconds '. This parameter is associated with the CLASS that the process - Subsystem runs.
To determine the class:
-> Routing Entries
-> Details (pick one)
CLASS = QBATCH
Enter the CLASS - QBATCH, and the LIBRARY - *LIBL
Select 5 Details - next to the associated entry
Raise the Default Wait Time In Seconds - 120 is the default
Note: This problem can still occur if the XCOMLOG grows too large or the wait time is not sufficient.