Setting the JCL options for job cards
To set the JCL options for job cards
Use the following menu selections to display the JCL Generation Jobcard Options Update panel:
From this panel
Select this item and press Enter
DASD MANAGER PLUS Main Menu
User Options
User Options
JCL generation options
JCL Generation Update - Main Menu
Jobcard Options
JCL Generation Jobcard Options Update panel
------------------- JCL GENERATION JOBCARD OPTIONS UPDATE ----------------
COMMAND ===>
Type data and press Enter.
Is a TSO submit exit used to generate jobcards?. . N (Y/N)
Enter Jobcards below:
//MVSCAL2I JOB (&ZACCTNUM),'&PGMR',
// CLASS=A,MSGLEVEL=(1,1),NOTIFY=&SYSUID
//*
//*
//*
Jcllib . . . . . .
Sysexec. . . . . . BMC.DB2.Vvvrr.BMCREXX
Region size . . . 0M (See JCL Reference for valid options)
Memlimit. . . . . NOLIMIT (See JCL Reference for valid options)
Time parameter . . (See JCL Reference for valid options)
System MLIB. . . . SYS1.OOOO.ISPMENU
Runtime HLQ. . . . BMC.DB2.Vvrr
User HLQ . . . . .
LLQ. . . . . . . .
ULLQ . . . . . . . (Leave blank if using runtime enablement)- In the Is a TSO submit exit used to generate jobcards? field, type Y or N.
- In the Enter Jobcards below: field, type the job statement information that you want to add to the JCL.
- In the Jcllib field, enter the name of one of the following types of partitioned data sets (PDSs):
- A PDS that contains customized JCL to be included in the job
- A PDS that specifies the cataloged procedures (PROCs) that are used for non-worklist JCL
In the Sysexec field, type the name of the PDS in which a REXX EXEC is a member.
- In the Region size field, type the amount of memory to allocate for each step so that your job can run.
- In the Memlimit field, type the limit on the above-the-bar memory for an address space.
- In the Time parameter field, type the value for the TIME limit for each step in a batch job stream.
- In the System MLIB field, type the name of the system ISPF message library.
In the Runtime HLQ field, type the high-level qualifier (HLQ) for ISPF data sets for the installation environment.During installation, if you chose to use the runtime enablement (RTE) feature, the Installation System set this value to an HLQ for user runtime libraries. If you chose not to use RTE, the Installation System set the value to an HLQ for Execution.
This value supports the following symbolic variables:
- &DB2V2 and &DB2V3, which resolve to the version of Db2
&SSID, which resolves to the DB2 subsystem ID
When you include the &SSID symbolic variable, the product can use a single POF with multiple subsystems.
In the User HLQ field, type the high-level qualifier used for the user-defined data sets for the installation environment.
- In the LLQ field, type the low-level qualifier for ISPF data sets for the installation environment.During installation, if you chose to use the runtime enablement feature, the Installation System set this value to BMC. If you chose not to use the feature, the Installation System set the value to DB.
In the ULLQ field, type the low-level qualifier for user-defined data sets for the installation environment.
- Press END to save your changes and return to the DASD MANAGER PLUS Main Menu.