Step 3. Define a shadow job on the remote engine workstation

Create a shadow job pointing to a specific job instance defined on a remote engine when you want to track in your local environment the status of that remote job and define cross dependencies on that remote job.

A shadow job is bound to a remote engine job according to the IA time specified in the shadow job, which in turn is calculated according to the time zone of the remote job.

You can choose among the following matching criteria:
If the remote engine is distributed
Closest preceding
The matching predecessor is the one with the nearest preceding input arrival time.
If the remote engine is z/OS
Any of the following:
Closest preceding
The matching predecessor is the one with the nearest preceding input arrival time. This is the default.
Same scheduled date
The matching predecessor is the one with the nearest input arrival time within the same day (starting at 00.00 and ending at 23.59) 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.

Within a relative interval
The matching predecessor is the one with the closest input arrival time within the interval specified. The interval boundaries are calculated using an offset expressed in hours and minutes before or after the IA time of the successor operation. The interval can be timed entirely before, entirely after, or across the IA time of the successor operation.

When the interval is across the IA time, a matching predecessor is first searched before the IA time of the successor operation. Then, if not found, it is searched after the IA time of the successor operation.

Within an absolute interval
The matching predecessor is the one with the closest input arrival time within the specified interval. The interval boundaries are specified by a time and a number of days before or after the IA time of the successor operation. The interval can be timed entirely before, entirely after, or across the IA time of the successor operation.

When the interval is across the IA time, a matching predecessor is first searched before the IA time. Then, if not found, it is searched after the IA time of the operation.

The shadow job status transition is derived from the remote job instance status transition.

You can create a shadow job from the OPERATIONS panel, as shown in EQQAMOPL - Operations . Choose a remote engine workstation as the workstation for the operation, and select option 13 (REMOTE JOB INFO) in the OPERATION DETAILS panel to specify the information to identify the job instance in the remote engine plan.

On HCL Workload Automation distributed environments, you can use alias for job stream names and job names. If you are defining in your HCL Workload Automation for Z environment a distributed shadow job, make sure that:
  • The remote job stream name specified, contains the job stream name as it is defined in the database.
  • The remote job name specified, contains the alias, if defined, of the remote job to bind.
If you do not follow these guidelines, the bind fails and the status of the shadow job becomes ERROR.

For more details about the settings that define a shadow job, see Specifying remote job information in shadow jobs.