Data base extract - JCL specification

The Data Base Extract - JCL Specification screen, is used to specify the extract TO file dataset name, its attributes, and the extract job JCL information. This screen is displayed after the Data Base Dataset Specification screen for DLI extract job types and after the Data Base Extract Option Specification screen for BMP extract job types.

Data Base Extract - JCL Specification Screen

TO dataset

Enter the TO file dataset name. If you are extracting to an existing data set, the name must conform to the characteristics for a valid extract TO file as described in Extract TO/Load FROM File Data set.

Member

Enter the member name if the file is a partitioned dataset. If you leave this field blank, a member list is displayed. You can create new members by entering the name of the new member in the Member field or by selecting the new member on the Member List screen.

Volser

Displays the volume serial number of the disk or tape that contains the data set.

Dataset Disposition

Enter SHR or OLD to allocate to existing data sets. Enter NEW to allocate new data sets. New data sets are created as sequential, variable length record, blocked files.

Generic Unit

Enter the device type where the new data set is to reside. The names of these devices are somewhat installation dependent. Some common examples are DISK, TAPE, and 3380 devices.

Block Size

Enter the block size for the new data set. Because the new data set has variable length records and is blocked, the block size must be at least four bytes greater than the logical record length (the logical record length, LRECL, is shown to the right of the Block Size field).

The LRECL to be used is the sum of the following:

• 
  
  • The maximum segment length being unloaded
  • The maximum concatenated key for the segments being unloaded
  • A fixed size prefix of 28 bytes

The block size is taken from the screen. If the field is blank or the value is less than the LRECL + 4, the block size is set to LRECL + 4. These values are used for a new data set. For an existing data set, the LRECL and block size must be equal to or greater than the calculated values.

If you want to make the LRECL larger so that the data set is usable for extracts of other databases, enter JCL on the command line and modify the LRECL, BLKSIZE, or both of the IXPTO data set prior to submitting the job.

Space Units

Indicate whether the space for the new data set is to be allocated in blocks (BLK), tracks (TRK), or cylinders (CYL). This field does not apply to extract data sets written to tape.

Primary Quantity

Enter the number of space units to be reserved for the new data set. This field does not apply to extract data sets written to tape.

Secondary Quantity

Enter the number of space units to be allocated if the new data set uses secondary extents. This field does not apply to extract data sets written to tape.

Job Statement Information

Enter the sysout class for the extract reports, the JOB statement, and other related JCL statements (for example, /*JOBPARM and /*ROUTE statements).

Terminating the Screen

Do the following to terminate the Data Base Extract - JCL Specification screen:

• Press Enter to generate the JCL, submit the extract job for execution, and return to the Data Base Extract - Data Base Specification screen.
• Enter the JCL command to advance to an ISPF/PDF Edit screen, where you can edit the generated JCL before submitting it. See to Editing the Generated JCL.
• Enter the END command to return to the Data Base Extract - Data Base Specification screen without submitting the extract job.
• Enter the RETURN command to return to the Primary Option Menu without submitting the extract job.

Data privacy dataset allocation

When disguising an extract and you specified a data set on tape or an existing PDS on DASD, (TO Dataset), the Data Privacy Dataset Allocation window displays when you press Enter on the Data Base Extract - JCL Specification Screen.

Data Privacy Dataset Allocation window

Two Data Privacy work data sets must be allocated on DASD. Each must be large enough to contain a copy of the extract data set. Please provide the allocation parameters that will be used to create these data sets:

Generic Unit

Enter the device type for the Data Privacy work data sets.

Block Size

Enter the block size for the Data Privacy work data sets.

Space Units

Indicate whether the space for the Data Privacy work data sets is to be allocated in blocks (BLK), tracks (TRK), or cylinders (CYL).

Primary Quantity

Enter the number of space units to be reserved for the Data Privacy work data sets.

Secondary Quantity

Enter the number of space units to be allocated if the Data Privacy work data sets use secondary extents.

Press Enter to continue with the JCL generation.

Editing the Generated JCL

If you entered the JCL command on the Data Base Extract - JCL Specification screen, an ISPF/PDF Edit screen similar to the one shown in the following figure is displayed.

ISPF/PDF Edit Screen

At this point in the conversation, the ISPF/PDF editor has been invoked on the temporary data set that contains the JCL generated to do the extract. All ISPF edit commands are available for use. For example, to insert additional JCL statements, use the I (Insert) line command. To change the JCL, type over the data. To delete a line, use the D (Delete) line command. You can use the CREATE and REPLACE primary commands to save the generated JCL into a partitioned (PDS) or sequential dataset, which enables you to submit the JCL in the future without using the online conversation screens.

Do the following after you view or edit the JCL:

• Enter the SUBMIT command to submit the extract job for execution. The Data Base Extract Report described on here is generated.
• Enter the END or CANCEL command to return to the Data Base Extract - Data Base Specification screen.