Reason:
The indicated user ID was forced off the system while executing a request. This happens when a user ID goes into a CP READ or VM READ and is forced off by the system after the user ID has been idle for a specified amount of time. This can also happen if a request is to be monitored by the Request Execution Monitor, but the autologged user ID does not have access to the VM:Schedule communications module (VMSCHED MODULE).
Action:
Determine why the request failed and resubmit it when the problem has been corrected.
|
Copyright © 2013 CA.
All rights reserved.
|
|