Creating cross dependencies

About this task

To add a cross dependency to a local job on a job that is defined on a remote engine, you must define a normal dependency for your local job on a shadow job that:
  • Points to the remote job on which you want to create the cross dependency
  • Is defined on a local workstation of remote engine type, that points to the engine where the remote job is defined.

To define the cross dependency, perform the following steps:

Procedure

  1. Define a remote engine workstation

    On a remote engine workstation you can run only shadow jobs. As a prerequisite for creating a remote engine workstation, you must ensure that an HTTP or HTTPS destination to communicate with the remote engine exists. The name of this destination must be specified in the remote engine workstation definition.

    1. From the navigation toolbar, click Administration > Workload Environment Design > Create Workstations.
    2. Select an engine from the list and click Create Workstations.
    3. Specify the workstation attributes, selecting Remote engine as Workstation Type. For more details about the options to select, see the online help by clicking the question mark located at the top right corner of the panel.
  2. Define a shadow job

    It runs on the remote engine workstation and must contain the key values to identify the remote job.

    1. Click Administration >Workload Design>Manage Workload Definitions to define a job of type Shadow Job.
    2. Select an engine from the list and click Go. You can select either a distributed engine (to create a shadow job as an independent object) or on a z/OS engine (to create a shadow job within an existing job stream.)
    3. The Workload Designer opens. In the Working List panel, create the new job.
      New > File Transfer and Coordination
      New > Job Definition > File Transfer and Coordination
    4. Select either Shadow Distributed or Shadow z/OS, depending on the type of remote engine on which the remote job is scheduled to run. For more details about the attributes to select, see the online help by clicking the question mark located at the top right corner of the panel.

    Shadow jobs can be added to the plan by the plan creation process or dynamically at run time. The shadow job scheduled time is used to identify the job instance in the remote engine plan.

  3. Add the shadow job as a dependency of the local job

    The dependency can be internal (distributed only) or external. In the Details view, right-click the local job and use the pop-up menu to add the shadow job as a dependency.

Results

As soon as the shadow job status satisfies the dependency rule, the dependency of the local job on the shadow job is resolved, and the cross dependency for the local job on the remote job is also resolved.

For more information about cross dependencies, see Cross dependencies

Parent topic: Designing your Workload
Related concepts:
Cross dependencies