Authorities
and privilegesUse the Submit MVS JCL jobstream (VWPMVS) Warehouse Center program to submit a JCL jobstream that resides on MVS to an MVS system for execution.
Before you use this program, test your JCL file by running it from TSO under the same user ID that you plan to use with this program.
When you define a step that uses this program, do not specify a source or target table for the step.
To submit a JCL jobstream on MVS:
Specify information for your step:
In the Name field, you can type a new name for the step. Otherwise, you can keep the name that the Data Warehouse Center automatically supplied for the step. This field is required.
In the Administrator field, type the name of the person who is responsible for the maintenance of this step. This field is optional.
In the Description field, type a business description for your step. This description can be a maximum of 255 characters. This field is optional.
In the Notes field, type detailed information that might be helpful to users who can access this step. This field is optional.
On the Parameters page, in the MVS system name field, type the name of the MVS host on which to run the job.
In the MVS User ID field, type the user ID to use to connect to the MVS host.
In the MVS password field, type the password for the user ID.
In the Verify MVS password field, type the password again for the user ID .
In the MVS JCL File field, type the name of the JCL file to submit.
In the Local spool file full path name field, type the path and file name of the file on the agent site that is to receive the JES log file.
On the Processing Options page, in the Agent Site list, select an agent site where you want your step to run. The selections in this list are agent sites that are common to the source tables, the target table, and the transformer or program that you are defining.
If you want to have the option to to run your step at any time, select the Run on demand checkbox. Your step must be in test or production mode before you can run it.
Optional: Select the Populate externally check box if the step is populated externally, meaning that it is invoked in some way other than by the Data Warehouse Center. The step does not have to have any other means of running in the Data Warehouse Center in order to change the mode to production.
If Populate externally is not selected, then the step must either have a schedule, be linked to a transient table that is input to another step, or be started by another program in order to change the mode to production.
In the Retry area, specify how many times you want the step to run again if it needs to be retried and the amount of time that you want to pass before the next run of the step.
Click OK. to save your changes and close the step notebook.
Related information