New opportunities for modifying job definitions already in the plan or in the database

Modify a job instance in the plan before it runs, modify an instance of a job in the plan that has already run and rerun the modified job or modify the job definition explicitly in the production plan getting the JCL directly from a remote data set.

You can now edit the JCL on zAgent if a job is in error and modify the job definition explicitly in the database getting the JCL directly from a remote data set.

With the extra opportunities for modifying job definitions you can now modify a job instance in the plan or in the database before it runs or modify an instance of a job in the plan that has already run and rerun it.

This feature adds the flexibility you need so that you can now make changes to the definition even after it has already been submitted into the plan, maintaining the original definition in the database. With this additional flexibility you can go and get the JCL and run it again changing the data set name containing the JCL, change the JCL defined explicitly in the production plan file and you can also change the job definition explicitly in the production plan file getting the JCL from the remote data set. This can be done from either the Job Stream Graphical View, the job monitoring view, or from the conman command line.

For details about how to modify the job definition in the plan see the section Editing the JCL by definition, retrieving from a remote data set here: Defining and editing jobs in the Dynamic Workload Console