Reason:
CA Workload Automation SE is unable to read a message from the scratch queue. The message may have been written to the scratch queue incorrectly. Issued by SASSCHDO.
Action:
The WTO is informational and no action is required unless terminal xxxxxxx hangs. In that case, we recommend the following steps:
If the previous steps do not work, try starting CA Workload Automation SE with a TYPE=ERST. It may be necessary to relink CA Workload Automation SE (N520 of install jobs) to execute a DMPQ/MOVQ start up, or both.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|