Exceptions

An exception makes it possible to intercept a launch and to apply it a particular processing. The user can define exceptions on executions for a period, a processing date or a limited number in order to change future production once, without having to modify the schedule.

The exceptions in this list can be created from this document, from Job Runs and from Job Chains.

Several types of exceptions can be defined:

Hold

Suspend a launch in Launch Wait or Event Wait status. The launch can be manually released.
Jump

No condition check or Uproc execution. The Uproc won’t appear in the job runs. This exception cannot be applied to Session header Uproc.
Bypass condition check

Launch without: No condition check but there is Uproc execution.
Skip execution

Examine conditions but not Uproc execution. Job run proceeds into Completed status.

If several exceptions are applied to the same launch, the order of priority is as follows:

Exception	Application	New status	Priority
Hold	As soon as the launch appears	Deactivated	1
Jump	In a session, when the preceding Uproc is completed	None. The Uproc does not appear.	2
Bypass condition check	During condition checks	Pending	3
Skip execution	When the launch formula is validated	Completed	4

Actions:

New, Display, Update

Opens an exception declaration window. Refer to the section "Exception Details". In display mode, no modifications can be made. In update mode, only certain fields can be modified.
Send to

Deploys selected objects from a DUAS V6 node to a target: Package, node, Area or Management Unit. Refer to section "V6 Deployment Details".

Columns:

Type

This column displays the type of execution. It can have the following values:
- Bypass condition check: for a launch without condition checks; created from the Exceptions list only
- Force completion: for a "Force completion" action from the Job Runs or from the Job Chains Monitoring
- Jump: without conditions check and without execution; created from the Exceptions list only
- Skip execution: created from the Exceptions list or by a "Skip" action from the Job Runs or from the Job Chains Monitoring.
- Hold: for a suspended launch; created from the Exceptions list only
MU

Displays the exception’s Management Unit (execution MU of a Uproc).
Task

Task on which the exception is based.
Session, Session Version

Session on which the exception is based.
Uproc, Uproc Version

Uproc on which the exception is based.
Label: N/A.
Begin date

Start of the exception window.
End date

End of the exception window.
Launch N°

If the exception was created from the Execution job document, the launch number is displayed in this column.
Uproc N°

If the exception was created from the Execution job document, the Uproc number is displayed in this column.
Session N°

If the exception was created from the Execution job document, the Session number is displayed in this column.