Checkpoint/Resumption

The Checkpoint/Resumption screen shown in the following figure is displayed when you select Option 10- Checkpoint/Resumption from the Extract Menu.

Important

  1. The Checkpoint/Resumption option is not available for:
  2. When specifying both Checkpoint/Resumption and Data Privacy Specification, you must save the Extract Request (see Save Extract Request) before submitting it. You must use the same Extract Request file for the Extract Checkpoint and Extract Resumption jobs (see Checkpoint/Resumption Confirmation Windows). The pre-disguise extract file generated during the extract with Data Privacy process ('hlq.EXTRACT.Dyymmdd.Thhmmss’) must also be retained when Checkpoint/Resumption is specified; it will only be deleted after the resumption completed the whole extract process and retention is not specified (see also Retain Pre-Disguise File).

Checkpoint/Resumption

 File-AID/RDX ----------------  Checkpoint/Resumption ----------------
 COMMAND ===>                                              
                                                                               
 Enable Checkpoint/Resumption ===> N   (Y = Yes, N = No)

 Specify Checkpoint Data File (Required):     
   File name   ===>                             
   Member      ===>           (Blank or pattern for member list)
   Disposition ===> NEW       (NEW, OLD)                      

 Specify Checkpoint Control Options:     
   After Elapsed Time In Minutes ===>                                          
   After Extract Step Number     ===>                                          

 Specify Checkpoint Control File:     
   File name   ===>                             
   Member      ===>           (Blank or pattern for member list)
   Disposition ===> NEW       (NEW, OLD)                      

   To use the Operator Modify command during extract execution for a    
   controlled shutdown with resumption, enable Checkpoint/Resumption and
   specify the Checkpoint Data File. 

Enabling checkpoint processing and specifying a checkpoint in your extract request will stop the extract execution in a controlled manner when the checkpoint (a specified extract step number or a specified time interval) is reached or when the z/OS Operator Modify command is issued (see also Stop Extract Execution with z/OS Operator MODIFY Command). In all cases, processing on the object currently being extracted will complete before the checkpoint is taken and a controlled stop occurs. You will then be able to resume and complete the extract from the checkpoint.

The TPT Trace (DD Name TPTPRINT) includes the following statement when the extract execution was stopped at a specified checkpoint:

Checkpoint taken. Terminate=Y, Write trailers=N, Write reports=N

Enable Checkpoint/Resumption

Specify Y (Yes) when you want to turn on checkpoint processing for this extract request. N (No) is the default and will not enable checkpoint processing.

Specify Checkpoint Data File

The Checkpoint Data file (see also Checkpoint Data File) stores the File-AID/RDX internal control blocks, chase keys, key trees, etc., that are required for resumption of the extract at a later point.

Important

The Extract file and the Checkpoint Data file are logically related to each other and must be unique. Compuware recommends to define a separate Checkpoint Data file or member for each extract that has Checkpoint/Resumption Enabled.

File Name

Specify the name of the Checkpoint Data file. This file can be a PDS, PDSE, or sequential file.

Member

If the file you specified in File Name is a PDS or PDSE, you can enter a member name. If you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window containing a list of members that match the specified pattern. The only valid pattern character is an asterisk (*). You can create new members by entering the name of the new member in the Member field.

Disposition

Specify the disposition of the Checkpoint Data file. You can save to an existing file with a disposition of OLD, replacing any content with the new content. Specify a disposition of NEW to create a new PDS/PDSE or sequential file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the Create New File screen. The file will not be created until extract execution time.

Specify When to Checkpoint

There are two ways to specify a checkpoint. If you specify both, the first encountered will initiate the controlled execution stop. If neither checkpoint is reached during execution, the extract completes normally.

After Elapsed Time In Minutes

Specify the minutes of elapsed execution time (clock time) after which File-AID/RDX will initiate the controlled execution stop.

After Extract Step Number

Specify the extract step number (based on the TPT Trace steps) after which File-AID/RDX will initiate the controlled execution stop. The Extract step number field can store up to 5 digits.

Specify Checkpoint Control File

The Checkpoint Control file (see also Checkpoint Control File) stores the 'When to Checkpoint' information as specified on this panel and is required when specifying a value in either of the After Elapsed Time In Minutes or After Extract Step Number fields.

File Name

Specify the name of the Checkpoint Control file. This file can be a PDS, PDSE, or sequential file.

Member

If the file you specified in File Name is a PDS or PDSE, you can enter a member name. If you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window containing a list of members that match the specified pattern. The only valid pattern character is an asterisk (*). You can create new members by entering the name of the new member in the Member field.

Disposition

Specify the disposition of the Checkpoint Control file. You can save to an existing file with a disposition of OLD, replacing any content with the new content. Specify a disposition of NEW to create a new PDS/PDSE or sequential file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the Create New File screen.

Important

The extract request must be saved in order to use Checkpoint/Resumption. If you make changes, you must re-save the request.

Primary Command

The following File-AID/RDX-specific primary command is valid on this screen:

END

Saves your input, returns to the Extract Menu and sets the current value for Checkpoint/Resumption accordingly (see 10- Checkpoint/Resumption).

Checkpoint/Resumption Confirmation Windows

When Checkpoint/Resumption is enabled for an extract request, File-AID/RDX displays confirmation windows when submitting the request with Option 13 - View JCL, 14 - Submit JCL, or the G (Go), C (Change selection criteria & Go), or V (View JCL) line command.

When submitting the request for the first time, or the Checkpoint Data file for the request is empty, File-AID/RDX displays the Checkpoint Processing - Confirmation Window where you confirm checkpoint processing or cancel this extract execution request.


Yes

Continue the extract execution with Checkpoint Processing enabled.

No

Cancel the extract execution.


Checkpoint Processing - Confirmation Window

image2021-10-25_10-16-21.png

When submitting the request after the extract had been stopped at a checkpoint or with the z/OS Operator Modify command and the Checkpoint Data file for the request contains resumption data, File-AID/RDX displays the Checkpoint Processing - Resumption Confirmation Window where you confirm to resume the stopped extract or cancel the resumption. If you cancel the resumption through this window, the contents of Checkpoint Data file will be cleared and the extract starts from the beginning.

Yes

Resume the extract execution from the Resumption Checkpoint.

No

Clears the contents of the Checkpoint Data file and starts the extract from the beginning. If Checkpoint Processing is still enabled, execution will stop when the checkpoint is reached.

Checkpoint Processing - Resumption Confirmation Window

image2021-10-25_10-16-57.png

 

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