ADAPD

Purpose

Use the ADAPD control statement to specify an application or an operation as the predecessor for the application that is being built by the ADSTART statement.

You should remember that there can be up to four versions of an AD with different validity dates. If there is more than one version, the batch loader searches the ADs defined by your APDADID keyword to find an AD with a current validity date. ADs with active status are searched first, followed by those with pending status.

You identify a predecessor operation by one or more of the following values:
  • Operation number (APDOPNO)
  • Workstation name (APDWSID)

You must specify enough of these keywords to uniquely identify a predecessor operation. If no operation is specified it is assumed that the predecessor is an application, therefore an application dependency is created.

If the output is directed to a VSAM data set, a predecessor operation can be defined by an ADOP statement occurring later in the input data set. This is because most validity checking occurs after all statements in the input data set are read.

If the output is directed to an active IBM Z Workload Scheduler subsystem and the predecessor operation does not already exist in the AD database, specify both the operation number and the workstation name in the ADAPD statement.

Format


1  ADAPD
1  ACTION (
2.1! ADD
2.1 SETDEFAULT
1 )
2?  DESCR ('
3.1 predecessor description
2 ')
2?  APDADID (
3.1 predecessor application ID
2 )
2?  APDCSEL (
3.1! C
3.1 S
3.1 A
3.1 R
2 )
2?  APDIVFD (
3.1 days
2 )
2?  APDIVFHH (
3.1 hh
2 )
2?  APDIVFHHH (
3.1 hhh
2 )
2?  APDIVFMM (
3.1 mm
2 )
2?  APDIVFWHE (
3.1 A
3.1 B
2 )
2?  APDIVTD (
3.1 days
2 )
2?  APDIVTHH (
3.1 hh
2 )
2?  APDIVTHHH (
3.1 hhh
2 )
2?  APDIVTMM (
3.1 mm
2 )
2?  APDIVTWHE (
3.1 A
3.1 B
2 )
2?  APDIVTYPE (
3.1 A
3.1 R
2 )
1+ .
1  APDWSID (
2.1 predecessor workstation
1 )
1  APDOPNO (
2.1 predecessor operation number
1 )

Restrictions

You cannot use ACTION(SETDEFAULT) to set default values for the following keywords:
  • APDADID
  • APDWSID

Parameters

ACTION (SETDEFAULT | ADD)
If you specify SETDEFAULT, the remaining keyword values that you specify on the ADAPD statement become default values for all ADAPD statements that follow. No application description is updated. Keywords that you do not specify are assigned their standard defaults.

If you specify ADD or use it by default, the statement can result in an update of the database.

DESCR ('predecessor description')
A free-format description of the dependency. It can be up to 50 characters and must be contained within single quotation marks. Do not include delimiters, such as parentheses and single quotation marks, in the description.

IBM Z Workload Scheduler holds descriptions only for external dependencies. This field cannot be used to hold a description for an internal dependency.

APDADID (predecessor application ID)
Specifies the application ID. If you use DBCS characters, you must enter them as a quoted string started by a shift-out and ended by a shift-in.
APDCSEL (C | S | A | R)
Specifies on which basis a matching predecessor is selected. Can be 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.
A
Within an absolute interval. The matching predecessor is the one with the closest input arrival time in the specified interval. The interval boundaries are specified by a time and a number of days before or after the IA time of the operation (occurrence). The interval can be timed entirely before, entirely after, or across the IA time of the operation (occurrence).
R
Within a relative interval. The matching predecessor is the one with the closest input arrival time in the specified interval. The interval boundaries are calculated using an offset expressed in hours and minutes before or after the IA time of the operation (occurrence). The interval can be timed entirely before, entirely after, or across the IA time of the operation (occurrence).
APDIVFD (days)
The start of the absolute interval, in days. The allowed range is 0-7.
APDIVFHH (hh)
The start of the absolute interval, in the HH format. The allowed range is 00-24. Goes together with APDIVFMM. For example, if the absolute interval starts at 10:30 of the day before the input arrival time of the successor, it is defined by: 
APDIVFHH(10) APDIVFMM(30) APDIVFD(1) APDIVFWHE(B)
APDIVFHHH (hhh)
The start of the relative interval, in hours. The format is HHH and the allowed range is 0-167. Goes together with APDIVFMM.
APDIVFMM (mm)
The minutes fraction of the start of the relative or absolute interval.
APDIVFWHE (A | B)
Specifies if the start of the relative or absolute interval is before (B) or after (A) the input arrival time of the successor.

For relative intervals only, you can choose to make the interval start at an indefinite time in the plan (in this case the mechanism used is similar to that of the closest preceding predecessor). To do this, do not specify this parameter, nor any of the APDIVF... ones.

APDIVTD (days)
The end of the absolute interval, in days. The allowed range is 0-7.
APDIVTHH (hh)
The end of the absolute interval, in the HH format. The allowed range is 00-24. Goes together with APDIVFMM. For example, if the absolute interval ends at 12:30 two days after the input arrival time of the successor, it is defined by: 
APDIVTHH(12) APDIVTMM(30) APDIVTD(2) APDIVTWHE(A)
APDIVTHHH (hhh)
The end of the relative interval, in hours. The format is HHH and the allowed range is 0-167. Goes together with APDIVTMM.
APDIVTMM (mm)
The minutes fraction of the end of the relative or absolute interval.
APDIVTWHE (A | B)
Specifies if the end of the relative or absolute interval is before (B) or after (A) the input arrival time of the successor.

For relative intervals only, you can choose to make the interval start at an indefinite time in the plan (in this case the mechanism used is similar to that of the closest preceding predecessor). To do this, do not specify this parameter, nor any of the APDIVF* ones.

APDIVTYPE (A | R)
The interval type. Can be one of the following:
A
Absolute interval. Must be defined by the following parameters: APDIVFWHE, APDIVFHH, APDIVFMM, APDIVFD, APDIVTWHE, ADPDIVTHH, ADPDIVTMM, ADPDIVTD.
R
Relative interval. Must be defined by the following parameters: APDIVFWHE, APDIVFHHH, APDIVFMM, APDIVTWHE, APDIVTHHH, APDIVTMM.
APDWSID (predecessor workstation)
The four-character workstation name of a predecessor operation to this operation.
APDOPNO (predecessor operation number)
The operation number of a predecessor operation to this operation.

Examples

In this example, an application predecessor named PAYDAILYPRED is defined for the application PAYDAILY:
ADSTART ADID(PAYDAILY)...
ADAPD APDADID(PAYDAILYPRED) APDCSEL(R) 
APDIVTYPE(R) APDIVFHHH(012) APDIVFMM(30) APDIVFWHE(B) 
APDIVTHHH(018) APDIVTMM(15) APDIVTWHE(A)

The application dependency is to be resolved by finding the matching predecessor within a relative interval, as defined by the value of APDCSEL. The details of the interval are defined by the APDIV* statements.