End of support

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Saving tailored skeleton JCL

Skeleton JCL can be saved to a data set rather than having MainView SRM Automation submit the job.

This process enables you to review JCL before running the job. The data set is created with a prefix that is specified in the SMMSYS AUTOJ_OINDX parameter. The remainder of the data set name is created as described in Data set naming conventions for tailored skeleton JCL.

Note

After the tailored JCL is saved to a data set, you must manage and submit these data sets manually. The Automation component never deletes these files. You should assign migration and other data-set-management attributes to these data sets as needed.

The data sets that are created can be viewed in the WBSL view and submitted manually. After submission, you can use line commands to delete the data set. For identification purposes, the data set name contains the following information:

  • Name of the function and solution that created the data set

  • Date and time that the data set was created

To accumulate and save skeleton JCL to a data set over a time interval, you can use the ACT_ACCUM parameter in the rule list definition of the solution. This can be used to limit the number of data sets that are created by a solution.

Was this page helpful? Yes No Submitting... Thank you

Comments