Update saved extract requests

The following panel is displayed when you select Option 1, Update, from the Utilities Menu.

Use this screen to initiate a batch job that updates your saved extract requests with the current information from the specified Relationship file.

This utility function operates against a library of saved requests. Any changes made to a saved request will be made to a copy of the saved request; the original saved request will not be changed.

Update Saved Extract Requests

On this screen you specify the Extract Request library to be updated and whether to copy only the changed requests or all requests into the new Extract Request library. You also identify the Db2 subsystem from which to gather catalog information and the Relationship file from which to update the relationship information in the extract requests. Only the requests that were created using the specified Relationship File will be updated, all others will be bypassed.

Enter GO to submit the job or enter JCL to review the JCL before submitting.

After you enter GO, File-AID/RDX displays the message: JOB SUBMITTED and returns to the Utilities Menu.

Specify Request Information

This section provides information about the following fields:

Validate Action

Specify whether to generate a report only (R) or update the requests (U) as well.

Request to Copy

Specify whether to copy only the updated requests (U) or all requests (A) into the new request library, if the request file is a PDS.

Request File

Specify the name of the existing extract request to be updated. If you don’t use quotes around the name, File-AID/RDX will add your TSO ID as the prefix. The existing request file will not be updated. Changed request data will be copied into the new request file.

Member

Specify the member name of the existing extract request to be updated, if the request file is a PDS. Specifying a pattern selects all matching member names for processing at execution time.

New Request File

Specify the name of the new extract request file into which the updated request data is to be copied. If you don’t use quotes around the name, File-AID/RDX will add your TSO ID as the prefix. Leaving this field blank will use the original file as the output file.

If the new file does not exist, File-AID/RDX displays the Create New File panel where you specify the file allocation values for the new request file.

Update requests that use the following SSID and relationship file

This section provides information about the following fields:

SSID

Specify the subsystem ID of the Db2 subsystem from where you want to gather catalog information to update the request. Specify ALL if catalog information is to be gathered from all Db2 subsystems listed in the request.

Relationship File

Specify the name of the Relationship file from which to update the relationship information in the extract requests.

Primary Commands

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

JCL

View the JCL for the Update Saved Extract Requests utility (see Update Saved Extract Requests JCL). File-AID/RDX shows the Generated JCL panel where you review and modify the JCL. Enter the SUBMIT command to submit the job.

GO (G)

Submits this Update Saved Extract Requests job request without displaying the JCL. Before issuing the GO command, make sure you have specified the existing and new request files, the relationship file and Db2 subsystem. File-AID/RDX will also issue a message upon completion of the job.

Update process

In effect, a new extract request will be created using the Driving Object specified in the original request. Any user modifications made in the original request will be applied to the new request; this will include the following:

• Extract Options
• Extract Scope - object view line commands
• (Exclude, All, Passthru)
• Extract Scope object sampling criteria
• Extract Scope - relationship view line commands
• (Exclude)
• Extract Scope relationship sampling criteria
• Extract Scope relationship navigation criteria
• Selection Criteria

The updated request is identical to the old request except for the changes made to the set of related objects; the following will not change:

• Unrelated objects
• Input (External) Key File
• IMS and Output Key File
• Extract File

Errors

There may be situations in which the updated saved request is no longer valid, for example, if the driving object no longer exists. Whenever error checking can detect that the new request is invalid, it is marked “not executable” and cannot be executed. An example for marking a request “not executable” can occur when a relationship has been added to an IMS object or Output Key, which requires defining the IMS key file in order for the request to actually be executable.

Any request marked “not executable” can be corrected with the online interface (Option 2 Extract); correcting the request removes the not executable indicator.

File-AID/RDX currently does integrity checking whenever changes are made to the navigation settings. The integrity checking is done to verify that the extract will be loadable. In the online interface, the user has the option to accept or reject the objects identified in the integrity warning. Since this update will be done in batch, this option will not be available; accept any changes identified by the integrity warning.

“Modeled” Relationships

File-AID/RDX allows extract requests to be created for Db2 objects that are not in the Relationship file by choosing to model the relationships defined for a different set of Db2 objects (see Using Relationship Definitions Across Db2 Subsystems). Any request that was created prior to File-AID/RDX Release 4.5 using modeling will be converted into a single table extract, unless relationships have been added to the relationship file for the driving object.

Modeled requests created with File-AID/RDX Release 4.5 and higher include the record type 57 Model: (see record type 57). When a request with record type 57 is encountered File-AID/RDX:

• First checks if relationships have been added to the driving object to make it directly related to other objects.
  If this is the case, these relationships are now the controlling factor and used to update the request.
• If no direct relationship exists to the driving object then File-AID/RDX retrieves relationship information in the same way that it was originally done using the type 57 Model object and then compares it with the contents of the request. If this relationship information has changed then the changes are reflected in the saved request. If there are no relationship changes, the request remains unchanged.

Batch Job

The following figure shows a sample job. The JCL parameters are based on the values in the Prepare, Product Option, and Subsystem tables as specified during the execution of Install Manager.

Update Saved Extract Requests JCL

The parameter information in the PARM field in the EXEC statement must have the following format:

The following DD statements are required:

Return Codes

An execution return code (RC) appears in the output listing. For return codes 4, 8, and 16, an error code and message indicating the specific problem also appear in the listing. In general, the return codes can be summarized as follows:

Report

A report (see the following figure ) will be produced during the Update Saved Request processing which will include a line for each member processed and details of the actions taken for each request. Members which are not processed because they did not meet the specified criteria or were not extract requests are identified with a message stating the reason.

Sample Update Saved Extract Requests Report