Naming a started task (source JCL is a job)

If you plan to run the started task more than once on the same system or on different systems within a sysplex, consider using unique job names for each instance of the started task. For example, you may want to name started tasks according to the system tasks they support; you can name one set of jobs for CICS® terminal-owning regions (CICSTOR1, CICSTOR2) and another set for CICS application-owning regions (CICSAOR1, CICSAOR2).

Note: You are not required to change the name of your started task; you probably will not want to change the name of a started task that typically has only one instance (OAM or LLA, for example).

There are four ways that you can name or identify a started task:

JOBNAME parameter
Use the JOBNAME parameter on the START command to rename the started task dynamically (see the description of START in z/OS MVS System Commands for details).
Membername
If you do not use the JOBNAME parameter on the START command and the source JCL is a procedure, the system automatically assigns the membername as the jobname.
Source JCL
If you do not use the JOBNAME parameter on the START command and the source JCL for the started task is a job, the jobname provided on the JOB statement is assigned as the jobname.
Identifier
If specified on the START command, and the started task runs in a system address space that is created using common system address space procedure IEESYSAS, the identifier is assigned to the started task.

Note: Given the capability to assign the jobname dynamically, it is recommended that you use the JOBNAME parameter instead of the identifier. Only operators can view the identifier for a started task, limiting automation and identification by other users.

If you decide to change the names of started tasks, be sure to update other applications to recognize the new names.