Generating Service Actions
To generate a Service Action, you specify data sets for the job and set various processing options.
DASD MANAGER PLUS
places the worklist in its own data set and generates the JCL into a separate data set for the JCL to run the worklist. You can assign values to the job generation options or accept the defaults.
To generate a Service Action
- From the Action Menu panel, select Generate Job for an Action.The Action List panel is displayed.
In the Act field, type G next to a Service Action and press Enter.The first Action Job Generation panel is displayed.
ASUIAG0 ----------------------- Action Job Generation -------------------------
Command ===>
Action: RDAPKM.DEMO
Status: GENERATED NOT EXECUTED
Select JCL Type and Build Options, then press Enter.
JCL Type . . . 1 1. Build Initial JCL
2. Build Restart JCL
3. Build Startover JCL
JCL Build Options
Record Events 1 1. Yes
2. No
Restart ParmThe Action field displays the Service Action that you are generating. The Status field shows the current status of the action. The DO_WORKIDS table provides the status. The field can contain one of the following values:
- Not Generated—the action has not been generated
- Generated Not Executed—the action has been generated but not submitted
- Executed Successfully—the action has been generated, submitted, and ran successfully
- Executed with Errors—the action has been generated, submitted, and completed unsuccessfully
- The JCL Type field indicates what type of JCL to generate, depending on the Service Action status. Specify the JCL Type as follows:
- Type 1 to initially start the job.
Type 2 to restart the job.
Use this option if the execution job failed previously. (You can select this option if the Action Status is Executed with Errors.) DASD MANAGER PLUS creates JCL from the old job. If you select this JCL type, you can use RESTART PARM to insert parameters into job stream.
To regenerate the JCL, on the next panel you must select Build JCL.
- Type 3 to restart the execution job from the beginning. DASD MANAGER PLUS creates JCL from existing JCL.
In the JCL Build Options fields, perform the following steps:
In the Record Events field, type 1 to log events in the DASD MANAGER PLUS database.DASD MANAGER PLUS inserts commands into the job stream that cause the execution program to insert entries into the EVENTS table.
This option is not valid if the JCL Type is Build Restart JCL.
- In the Restart Parm field, specify information to pass to a restart job. The Restart Parm field is available only if the JCL Type is Build Restart JCL.
- Press Enter.
The second Action Job Generation panel is displayed.
ASUIAG1 ----------------------- Action Job Generation -------------------------
Command ===>
Action : RDAPKM.DEMO
Status : GENERATED NOT EXECUTED
JCL POF: AUS.DOPSEC.CNTL(AJXvrPOF)
Specify Dataset Names
JCL . . . . . . . . 'ASU.DEMO.JCLLIB(&WKID)'
Worklist . . . . . 'ASU.DEMO.WORKLIST(&WKID)'
Diagnostics . . . . SYSOUT
Select Processing Options, then press Enter to Continue.
_ Override POF Values
S Build Worklist
S Edit Worklist
S Build JCL
S Edit JCL
S Submit JCLThe Action field displays the Service Action that you are generating. The Status field shows the current status of the action. The DO_WORKIDS table provides the status. The field can contain one of the following:
- Not Generated—the action has not been generated
- Generated Not Executed— the action has been generated but not submitted
- Executed Successfully— the action has been generated, submitted, and ran successfully
- Executed with Errors—the action has been generated, submitted, and completed unsuccessfully
The JCL POF field displays the name of the Service Action POF, if one exists. If this field is blank, the product use the POF specified in the user options.
Set the options as follows:
Field
What to enter
JCL
The name of the data set in which to build the JCL file, or accept the default
The data set must be sequential or a member of an existing PDS. This field defaults to the data set that you specified in the user options
Worklist
The name of the data set in which to build the worklist file, or accept the default
The data set must be sequential or a member of an existing PDS. This field defaults to the data set that you specified in the user options
Diagnostics
The name of the data set in which to place the diagnostic messages that result from generating the JCL and worklist files
This file must be sequential. The default is SYSOUT
Override POF Values
Type S to set the JCL Options overrides to use for this generation only.
The product resets the variables to the user options immediately after generation
Build Worklist
Type S to generate (or regenerate) the worklist.
Edit Worklist
Type S to display the worklist for viewing or editing after it is generated.
Build JCL
Type S to generate (or regenerate) the JCL.
Edit JCL
Type S to display the JCL for editing after it is generated.
Submit JCL
Type S to submit the JCL to execute the commands in the worklist.
You can submit the job now or later.
- Review your entries, and press Enter to process the job.
- Depending on the processing options that you specified, perform one of the following steps:
- If you chose to edit the worklist, the worklist is displayed. Press END to continue.
If you chose to edit the JCL, the JCL is displayed. Press END to continue.
Alternatively, you can submit the job from the edit panel by typing SUB on the COMMAND line.
- If you chose to submit the job by using the Submit JCL option, the product generates the worklist and JCL, and displays the Action Job Generation panel. The message <ENTER> TO SUBMIT appears at the top-right portion of the panel.
- Press Enter to submit the job for processing, or press END to exit the Action Job Generation panel without submitting the job.