BATCH JOB READIED

CA VM:Schedule signaled CA VM:Batch to run a CA VM:Batch request.

BATCH RUN PENDING

CA VM:Schedule signaled CA VM:Batch to start a request but a run of that request is currently in progress. The next run of the request is pending the current run’s completion.

CANCELED- AUTOLOG ERROR

Canceled due to an XAUTOLOG command error.

CANCELED- ON HOLD

Canceled and request is on hold.

DATE ADJUSTED

CA VM:Schedule changed the original run date to meet your other specifications, like MONTHEND.

EXECUTION COMPLETE

Ran as scheduled.

EXECUTION ERROR

Could not run. For example, if your request were to send a message to someone who was not logged on.

INITIATION DELAYED

Run time changed with DELAY FOR or DELAY UNTIL.

INITIATION FAILED

Could not start, probably because the user ID it was to run on was disconnected or logged on.

INITIATION SKIPPED

Not run because you used the SKIP command or the system was down at the time, or because the request did not run before the WITHIN time was exceeded.

JOB NOT FOUND

Could not run because the CA VM:Batch job associated with this schedule request no longer exists.

JOB NOT RUN

Could not run because the CA VM:Batch job was not associated with a CA VM:Schedule request; the CA VM:Batch job has no scheduling options.

NORMAL INITIATION

Started without error.

NOT PREVIOUSLY RUN

Not executed yet.

NOT RESCHEDULED

Not scheduled to run again.

PURGE SCHEDULED

Canceled or finished running for its last scheduled time, so all information about it will be erased from the CA VM:Schedule database.

READY CMD ERROR

Could not run the scheduled CA VM:Batch job because of an error in the CA VM:Batch READY command.

REQUEST CANCELED

Canceled and will not run again.

SKIPPED TO COMPLETION

Kept from running with SKIP so many times or for so long a period that there are no runs left.

UNKNOWN TERMINATION

Started normally, but CA VM:Schedule does not know how it completed. The user ID may have gone into a VM or CP READ, or been forced off by the system. This status can also occur when a request is to be monitored using the job execution monitor, but the autologged user ID does not have access to the CA VM:Schedule communications modules (VMDCOM and VMSCHED).

USER HOLD REMOVED

Was kept from running indefinitely. HOLD has since been removed, but request has not run yet.

USER REQUEST ABENDED

Started but could not complete because of a serious error.

USER REQUEST ON HOLD

Kept from running indefinitely, either by HOLD ON or because CA VM:Schedule encountered an error.

USER WAS LOGGED ON

Could not run because the user ID on which it was to run was logged on.

CA VM:Batch NOT AVAIL

Could not run a CA VM:Batch request because CA VM:Batch was not running.

WITHIN TIME EXPIRED

Could not run because the time specified with WITHIN has passed.