Specifying dependency resolution criteria

To specify under which criteria the predecessor dependency is to be resolved, in the PREDECESSORS panel (see EQQAMPDL - Predecessors ) or APPLICATION PREDECESSORS panel (see EQQAMDPL - Application Predecessors ) enter the T command on the row of the selected external predecessor job (for example, PAYWEEK) as shown hereafter.
Figure 1. EQQAMPDL - Predecessors 
EQQAMPDL ----------------------- PREDECESSORS ---------------  ROW 1 TO 3 OF 3
Command ===>                                                  Scroll ===> PAGE

Enter the COND command to view the list of conditions, enter/change
data in the rows, and/or enter any of the following row commands:

I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete
S - Description of external dependency, T - Dependency resolution criteria 

Application      : PAYM2                        MONTHLY PAYROLL TRANSFER
Operation        : CPU1 040    PAYTRANS
No. of conditions: 0
Row  Pre Dependency   Oper         Transport time   Application id          Jobname
cmd  Typ Resl Mand    ws   no.       HH.MM          (for ext pred only)
''   O   _    _       SETP 010       _____          ________________        PAYTRANS
''   A   _    _       CPU1 040       _____          PAYM1___________        PAYMONTH
T    _   _    _       CPU1 020       _____          PAYW____________        PAYWEEK_
******************************* BOTTOM OF DATA **************************
The DEPENDENCY RESOLUTION CRITERIA panel (EQQAMMAT - DEPENDENCY RESOLUTION CRITERIA) is displayed:
Figure 2. EQQAMMAT - DEPENDENCY RESOLUTION CRITERIA
EQQAMMAT---------------- DEPENDENCY RESOLUTION CRITERIA ----------------
Command ===>                                                                  
Application :          PAYM2                   
Pred Application : PAYW                       Operation : CPU1  20     PAYWEEK
                                                                              
Resolution is mandatory:                  N  (P/C/N)                          
Resolution criteria chosen is:            C  (C/S/R/A)                        
                                                                              
 -(C) Closest preceding                                                       
                                                                              
 -(S) Same scheduled date                                                     
                                                                              
 -(R) Within a relative interval                                              
  FROM:                                                                       
  hours (HHH):   ___  minutes (MM):  __   when (B/A before/after IA): _       
  TO:                                                                         
  hours (HHH):   ___  minutes (MM):  __   when (B/A before/after IA): _       
                                                                              
 -(A) Within an absolute interval                                             
  FROM:                                                                       
  time (HH.MM):   _____  for days (D):  _   when (B/A before/after IA): _     
  TO:                                                                         
  time (HH.MM):   _____  for days (D):  _   when (B/A before/after IA): _

The panel displays the name of the predecessor and of the application to which it refers. The resolution criteria is based on the input arrival times. Proceed as follows:

  1. The Resolution is mandatory field applies only to dependencies between one operation and another operation. Specify if it is required that the dependency with the predecessor (the job named PAYWEEK in this example) be resolved according to the resolution criteria specified thereafter before the operation (the job named PAYTRANS in this example) can be started. Choose among the following values:
    P (plan)

    The dependency is mandatory at plan level. The predecessor is expected to exist at the time the occurrence that includes the successor is dynamically added into the current plan (via the MCP panel). If it does not, the addition of the occurrence fails. Also LTP and DP batch will fail if the predecessor is not found when they run.

    C (control)

    The dependency is mandatory at ad hoc add level. The predecessor is required, but may not be in the plan at the time the occurrence that includes the successor is added and may be made available later via ETT, PIF, or manual intervention. This means that if the predecessor is not found when an occurrence is added to the current plan, a pending mandatory predecessor entry is created and the occurrence is added in the waiting status. The pending mandatory predecessor entry is created also when LTP and DP batch start running and the predecessor is not found.

    N (no)

    The dependency is not mandatory. This means that, if the predecessor is not found, the dependency is considered resolved unless failure is required (within the dynamic addition of a dependency in the Modify Current Plan panel). This is the default value.

    Attention: If an operation that is used as a mandatory dependency is also suppress-if-late, it might be suppressed before the required mandatory action is taken and this could potentially cause a problem or unexpected results. There is nothing to prevent an operation from being suppress-if-late and a mandatory dependency although it might not make sense to define it in this manner.
  2. In the Resolution criteria chosen field specify the criteria that are to be followed to find a matching predecessor occurrence with which to resolve the dependency between PAYWEEK and PAYTRANS.

    The resolution criteria are based on the input arrival times of a predecessor and of the successor. For the predecessor, this time corresponds to the IA time defined at occurrence level. For the successor, this time corresponds to the operation IA time, if any, otherwise corresponds to the IA time of the occurrence. To search for a matching predecessor, the scheduler starts from the IA time of the successor, then moves backwards (for the nearest preceding), or forward (for the nearest following) until it finds the IA time of the closest predecessor.

    Choose one of the following values:
    C (Closest preceding)
    The matching predecessor is the one with the nearest preceding input arrival time. This is the default.
    S (Same scheduled date)
    The matching predecessor is the one with the nearest input arrival time within the same day of the operation (occurrence) under consideration. A matching predecessor is first searched before the IA time of the operation. Then, if not found, it is searched after the IA time of the operation.
    R (Within a relative interval)
    The matching predecessor is the one with the closest input arrival time in the interval specified below. The interval boundaries are calculated using an offset expressed in hours and minutes before or after the IA time of the successor operation - PAYTRANS in this example. The interval can be timed entirely before, entirely after, or across the IA time of PAYTRANS.
    Specify the start of the relative interval in the fields under the FROM label:
    1. Enter a number of hours from 0 to 167
    2. Enter a number of minutes from 0 to 59
    3. Enter B or A to specify that the interval starts before or after the IA time of the successor job (PAYTRANS)
    You can set the interval to start either:
    • At an indefinite time before the IA by leaving the hours, minutes, and when fields blank.
    • At the actual IA by leaving the hours and minutes fields blank and setting when to A or B.
    Specify the end of the relative interval in the fields under the TO label:
    1. Enter a number of hours from 0 to 167.
    2. Enter a number of minutes from 0 to 59.
    3. Enter B or A to specify that the interval ends before or after the IA time of the successor job (PAYTRANS).
    A (Within an absolute interval)
    The matching predecessor is the one with the closest input arrival time in the interval specified below. The interval boundaries are specified by a time and a number of days before or after the IA time of the successor operation - PAYTRANS in this example. The interval can be timed entirely before, entirely after, or across the IA time of PAYTRANS. For example, an interval can start at 12.30 of 3 days before the IA of PAYTRANS (or of the PAYM2 occurrence) and end 1 day after the IA at 14.30.
    Specify the start of the absolute interval in the fields under the FROM label:
    1. Enter a time value from 00.00 to 23.59
    2. Enter a number of days from 0 to 7
    3. Enter B or A to specify that the interval starts before or after the IA time of the successor job (PAYTRANS).
    Specify the end of the absolute interval in the fields under the TO label:
    1. Enter a time value from 00.00 to 23.59
    2. Enter a number of days from 0 to 7
    3. Enter B or A to specify that the interval ends before or after the IA time of the successor job (PAYTRANS)