Conventions used for the end-to-end scheduling plan

The Symphony file used for end-to-end scheduling is created during the IBM Z Workload Scheduler current plan creation process. It contains all the jobs on distributed systems and all the z/OS® jobs that are predecessors of at least one job on the distributed system. It also contains topology information on the distributed network with all the workstation and domain definitions, including the master domain manager of the distributed network, that is, the IBM Z Workload Scheduler host.

The following list describes the conventions set for the Symphony file used for end-to-end scheduling:

  • Workstations:
    • The name used for the master of the distributed network is OPCMASTER.
    • The name of the other workstations is the same name used for the distributed agents.
  • Schedules (job streams) and jobs:
    • All the schedules are defined on OPCMASTER.
    • The jobs are defined on the workstation where they have to run.
    • Symphony also contains a dummy schedule named GLOBAL that holds a job named SPECIAL_RESOURCES. This job is used to represent dependencies on special resources.
    • The name of a schedule is a hexadecimal number reporting the occurrence token. This is a unique identifier for an occurrence in the current plan. Use the occurrence token value to find an occurrence in the current plan from the ISPF dialogs or from the Dynamic Workload Console.
    • The name of a job is made up according to the specifications described in Defining standards for generating job names in the Symphony file.
The following information applies to job names related to TWSJOBNAME:
  • The new rules for the job name in the Symphony file depend on the setting of the TWSJOBNAME parameter
  • All the characters that are not allowed in the Symphony file are changed to dashes (‒)
  • The resulting string is converted to uppercase.