Create JOB Statement page

On the Create JOB Statement page in the Step Perform wizard, you can accept the default JOB statement, modify the default JOB statement, or create a new JOB statement. The JOB statement can be applied to the job in the current step, or to all steps in the current workflow for which you are the step owner.

On the first access of this page, the JOB statement is initialized with IBM-supplied values. Thereafter, the JOB statement is populated with the values you used previously in the Workflows task.

Edit the JOB statement as needed. For example, you can modify the account number and job class. When you finish, select whether the JOB statement is to be applied to the job in the current step, or to all steps in the current workflow for which you are the step owner.

z/OSMF performs only limited validation of the JOB statement. Therefore, you must ensure that the JOB statement contains valid values for your installation.

For more information about specifying values for a JCL JOB statement, see z/OS MVS JCL Reference.

Variables in the JOB statement

The JOB statement might include variables for installation-specific values on your system. If so, the variables are enclosed in braces ('{ }'). To view the actual values for the variables, click View Substitutions. You can modify instance variables, but not global variables.

For example, in the following JOB statement, the user ID for receiving job notifications is represented by the instance variable named st_user.
//IZUWFJB  JOB  (ACCTINFO),CLASS=STEP,MSGCLASS=STEP,
//               MSGLEVEL=(1,1),REGION=0M,NOTIFY=${st_user}
On clicking View Substitutions, the variable is resolved to the user ID IBMUSER.
//IZUWFJB  JOB  (ACCTINFO),CLASS=STEP,MSGCLASS=STEP,
//               MSGLEVEL=(1,1),REGION=0M,NOTIFY=IBMUSER
You can overwrite this value to specify another user ID for receiving job notifications.