Defining standards for generating job names in the Symphony file

Add the statement: 
JTOPTS TWSJOBNAME(EXTNAME|EXTNOCC|JOBNAME|OCCNAME)
to define the rules the scheduler is to follow for generating the job name in the Symphony file in USS. The default parameter is OCCNAME.
If you specify EXTNAME, EXTNOCC, or JOBNAME, the job name in the Symphony file is made up according to one of the following formats:
  • X_Num_JobInfo, when the job is created.
  • X_Num_Ext_JobInfo, when the job is first deleted and then re-created in the current plan.
where:
X
Is J for normal operations, P for jobs representing pending predecessors, or R for recovery jobs. For jobs representing pending predecessors, the job name is in all cases generated by using the OCCNAME criterion. This is because, in the case of pending predecessors, the current plan does not contain the required information (except the name of the occurrence) to build the Symphony name according to the other criteria.
Num
The operation number.
Ext
The hexadecimal value of a sequential number that is increased every time an operation is deleted and then re-created.
JobInfo
Depends on the chosen criterion:
For EXTNAME
JobInfo is filled with the first 32 characters of the extended job name associated to that job (if it exists) or with the 8-character job name (if the extended name does not exist). Note that the extended job name, in addition to being defined in the database, must also exist in the current plan.
For EXTNOCC
JobInfo is filled with the first 32 characters of the extended job name associated to that job (if it exists) or with the application name (if the extended name does not exist). Note that the extended job name, in addition to being defined in the database, must also exist in the current plan.
For JOBNAME
JobInfo is filled with the 8-character job name.
If you specify OCCNAME, the job name in the Symphony file is made up according to one of the following formats:
  • X_Num_Application Name, when the job is created.
  • X_Num_Ext_Application Name, when the job is first deleted and then re-created in the current plan.
where:
X
Can be J for normal operations, P for jobs representing pending predecessors, and R for recovery jobs.
Num
The operation number.
Ext
A sequential decimal number that is increased every time an operation is deleted and then re-created.
Application Name
The name of the occurrence to which the operation belongs.

The criterion used to generate a job name will be maintained throughout the entire life of the job.

To choose the EXTNAME, EXTNOCC, or JOBNAME criterion, the EQQTWSOU data set must have a record length of 160 bytes. Before using any of the above keywords, you must migrate the EQQTWSOU data set. Sample EQQMTWSO is available to migrate this data set from 120 to 160 bytes.

The following limitations apply when using the EXTNAME and EXTNOCC criteria:
  • The job name in the Symphony file can contain only alphanumeric characters, dashes, and underscores. All the other characters accepted for the extended job name are changed to dashes. Note that a similar limitation applies also for JOBNAME: when defining members of partitioned data sets (such as the script or the job libraries), national characters can be used, but they are changed to dashes in the Symphony file.
  • The job name in the Symphony file must be in uppercase. All lowercase characters in the extended name are automatically changed to uppercase by IBM Z Workload Scheduler.
Note: Using the job name (or the extended name as part of the job name) in the Symphony file implies that it becomes a key for identifying the job. This also means that the extended name or jobname is used as a key for addressing all the events directed to the agents. For this reason, be aware of the following for operations included in the Symphony file:
  • Editing the Extended Name is inhibited for operations created when TWSJOBNAME was set to EXTNAME or EXTNOCC.
  • Editing the Jobname is inhibited for operations created when the TWSJOBNAME keyword was set to EXTNAME or JOBNAME.