JCL/overrides utility

The Execute Saved Request (ESR) Options  screen shown in the following figure is displayed when you select Option 2, JCL/Overrides, from the Utilities Menu.

Use this screen to initiate a process that generates the JCL and optional override files to execute previously saved requests. Eligible saved requests can either be extract, load, extract and load, and delete requests.

The creation of the File-AID/RDX Execute Saved Request JCL will typically be done by the Application Programmer as part of preparing or staging for turnover to Production Control.

Important

Execute Saved Request is supported for requests created by File-AID/RDX Release 4.5 and above. Extract and load requests which were created prior to File-AID/RDX Release 4.5 will execute, but they are not supported for this functionality.

Execute Saved Request (ESR) Options

 File-AID/RDX --------------  Execute Saved Request (ESR) Options  -------------
 COMMAND ===>                                                                   
                                                                               
 Primary Commands: ENTER to select Requests, GEN to generate                   
                                                                               
 Specify Requests to be Processed:                 Members selected.  . . .: 1
   Request File             ===> FRSAMP.EXTCRIT                                 
   Member name              ===> ORDER        (* or pattern for selection list)
                                                                               
 Specify Execute Saved Request Files:                                           
   ESR JCL File             ===> FRSAMP.ESRJCL                                  
   Object Override File     ===> FRSAMP.OBJOVERR                                
   SC Override File         ===> FRSAMP.SCOVERR                                
   JCLOUT for extract JCL   ===>
   JCLOUT for load JCL      ===>
                                                                              
 Select files and DD statements to generate for each request:
   N Gen ESR JCL               N Include JCLOUT   DD for Job scheduler input
   N Gen Object override file  N Include OVERRIDE DD for Object override
   N Gen SC override file      N Include SCOVERRD DD for SC override
 Object Override File Options:
   Override DB2 table names       ===> N    (Y = Yes; N = No)                 
   Override File Usage            ===> 2    (1 = Global; 2 = Per Request) 

On this screen you specify the input saved request and output ESR (Execute Saved Request) JCL files as well as any override information.

Enter GEN to process the selected options.

When the message “Generate process complete” displays, verify that the desired JCL and/or override files have been generated.

Specify Requests to be Processed

This section provides information about the following fields:

Request file

Specify the name of a previously saved request file for which you want to generate the JCL for execution at a later time. Eligible saved requests include load, extract and load, and delete requests.

Member name

Specify the member name of the saved request(s). Leave blank or use a pattern to select from the Request File Member List. You can select multiple or all members from the list for processing.

Important

  1. If you specify a sequential request file as input, File-AID/RDX fills the Member name field with TEMPNAME and uses TEMPNAME as the member name in the output PDS(s). After processing is completed, rename the fixed TEMPNAME member name in the output PDS(s) and the PARM entry in the ESR JCL to avoid overwriting when processing another sequential request file.
  2. For cloned or modeled requests object override files will not be generated and when executing ESR JCL for cloned or modeled requests, any included object override files will be ignored.

Members selected

Identifies how many saved request members have been selected from the request file.

Specify Execute Saved Request Files

This section provides information about the following fields:

ESR JCL File

Specify the name of the output file to store the generated JCL for execution at a later time. The ESR JCL file must be PDS - member names will be the same names as the request file member names. When the input request file is sequential, File-AID/RDX defaults to TEMPNAME as the member name.

Object Override File

Specify the name of the Object Override file that stores the original and new object and environment names for execution of saved requests at a later time. The Object Override file must be sequential for Override File Usage 1=GLOBAL and PDS for Override File Usage 2=Per Request.

SC Override File

Specify the name of the SC (Selection Criteria) Override file that stores the original and new selection criteria of the driving object for execution of saved requests at a later time. The SC Override file can be sequential or PDS.

JCLOUT for extract JCL

Specify the name of the JCLOUT file for the extract JCL. The JCL generated when the ESR job is run will be generated to the file named on the JCLOUT DD statement. If the data set is a PDS, the member name of the generated JCL will be the same as the request name. The JCLOUT file can be sequential or PDS.

JCLOUT for load JCL

Specify the name of the JCLOUT file for the load JCL. The JCL generated when the ESR job is run will be generated to the file named on the JCLOUT DD statement. If the data set is a PDS, the member name of the generated JCL will be the same as the request name. The JCLOUT file can be sequential or PDS.

The JCLOUT files can specify any MVS output file that is capable of accepting JCL. Specifically, the data set characteristics should include RECFM=FB, LRECL=80.

It is your responsibility to manage the assignment of data set names such that there will not be conflict and that there will be proper control and flow of the JCL into and through any scheduling systems.

If any of the ESR JCL or override files don’t exist, you must specify the allocation parameters in the Create New File screen.

Select files and DD statements to generate for each request

This section provides information about the following fields:

Gen ESR JCL

Select with Y to create JCL members for execution at a later time. Specify N (default) and JCL members will not be created.

Gen Object Override File

Select with Y to include the object override file in the ESR JCL. Specify N (default) and the Object override file will not be generated.

Gen SC Override File

Select with Y to include the SC (Selection Criteria) override file in the ESR JCL. Specify N (default) and the SC (Selection Criteria) override file will not be generated.

Include JCLOUT DD for Job scheduler input

Select with Y to generate DD for Job scheduler input in the ESR JCL. Specify N (default) and the DD for Job scheduler input will not be included.

Include OVERRIDE DD for Object override

Select with Y to generate DD for use of Object Override in the ESR JCL. Specify N (default) and the DD for use of Object Override will not be included.

Include SCOVERRD DD for SC override

Select with Y to generate DD for use of Selection Criteria Override in the ESR JCL. Specify N (default) and the DD for use of Selection Criteria Override will not be included.

Important

If you only want to generate or update the SC override file, you must also specify Y for Gen Object Overrides File.

Object Override File Options

This section provides information about the following fields:

Override DB2 Table Names

Specify Y to update the object override file to include Db2 Table names. Specify N and File-AID/RDX will not include Db2 table names in the object override file update.

Override File Usage

Specify 1 for a global override file. The global override file contains all override entries from all selected requests. Remember that the Object Override File must be sequential for global.

Specify 2 (default) for an override file per request. Remember that the Object Override File must be a PDS for this option.

Primary Commands

The following File-AID/RDX-specific primary commands are valid on this screen:

GEN

Processes the selected ESR options without displaying any JCL. Before issuing the GEN command, make sure you have specified the desired request members from the request file, the ESR JCL file, any override files, and the desired processing options. File-AID/RDX will issue the message “Generate process complete” upon completion of the process.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*