3.1 Understanding the Different States of a Job

When a job runs, it generates intermediate results and a final result. The possible results are Success, Warning, Error, and Aborted. The intermediate results have an impact on the final result. The final result is generated when the job is finished.

For each result, you can specify the action you want performed when it occurs. You can instruct the job to generate an event for Novell Audit or Novell Sentinel and also generate an e-mail notification. Alternatively, you might want no action to occur for an intermediate success result and an e-mail notification to be sent for an intermediate error result.

Success

Returned when a job has successfully executed without any errors or warnings.

Warning

Returned when a job cannot complete its execution because of unfulfilled prerequisites required for a successful run of the job. For example, a driver is not configured with health check before a health check job is run on the driver. The job returns a warning as a final result.

A warning is also displayed when a job partly succeeds in executing its defined task. For example, when a Password Expiration Notification job does not find an object’s passwordExpirationTime attribute value, the job generates a warning message for that object as an intermediate result. If you instructed the job to send an e-mail to the address contained in the object’s mail LDAP attribute, the job does not send the specified e-mail. When the job finishes its scheduled run, Identity Manager displays a warning with an appropriate message.

A Password Generator job generates an intermediate success message when it successfully generates a password for a user. If the job fails to generate a password for a user object for some reason, Identity Manager displays a warning as a final result.

Error

Returned when a job has insufficient rights on the object on which it is scheduled to run. An error is also reported when a job is executing and an exception occurs. For example, running a Schedule Driver job to run an already running driver or schedule the job to stop an already stopped driver.

Abort

Stops a job before the job completes its scheduled run. For example, terminating a job using dxcmd. Or, when Identity Manager engine is stopped, all running jobs are automatically aborted.