When you have completed the Specify EXTRACT Parameters and Execute panel, press ENTER. Move evaluates the Access Definition to be used and entries on the Specify EXTRACT Parameters and Execute panel. The Extract Process proceeds as follows.
If the Extract File does not exist, you are prompted for allocation information and Move allocates the file. (See the Common Elements Manual for a description of the allocation prompts.)
If you have entered Save at the If Batch, Review or Save JCL prompt, you are prompted for the name of the file in which to save the JCL and control statements and to indicate whether the job should be submitted after saving. (Details are discussed later in this section.)
Certain error conditions in the Access Definition prevent the Extract Process from proceeding. Other conditions trigger warning messages.
Database changes can be detected only when the Access Definition is edited or used. Thus, error conditions are most common when an Access Definition is used without prior review. The following error conditions also prevent you from saving an Access Definition after editing it. The error conditions include:
A warning indicates a condition that may require your attention, but does not prevent the Extract Process from proceeding. A warning gives you the option of proceeding or aborting the Extract Process. Warnings are issued for the following conditions:
If one or more error or warning conditions are encountered, the EXTRACT Errors & Warnings panel is displayed. Any error prevents the Extract Process from proceeding. The Extract Process can continue despite warnings.
You may use the SHOW STEPS command to display additional information about how the Extract Process will proceed.
In the following figure, the EXTRACT Errors & Warnings panel is displayed. Three warnings are documented.
+------------------- EXTRACT Errors & Warnings ------------------+
| |
| EXTRACT Process Can Proceed Despite the Following Warnings: |
| 1 Table(s) in UNKNOWN Status |
| 2 Table(s) will not be Traversed (See SHOW STEPS) |
| 1 Relationship(s) will not be Traversed (See SHOW STEPS) |
| |
| Press ENTER Key to Proceed Despite Warnings |
| Enter END Command to Return to EXTRACT Menu to Correct Problem |
| |
+----------------------------------------------------------------+If specified, the data set containing the primary key values for selected rows using Point-and-Shoot is checked as part of the validation of the Access Definition.
A problem is encountered when:
If a problem is encountered, you are prompted to specify how to proceed. You can continue processing without using the Point-and-Shoot values or respecify the Point-and-Shoot file name.
For batch execution, Move builds the necessary JCL and Batch Utility control statements. The JOB card information is taken from the JCL specified on the Job Card and Print Options panel.
If you entered YES at the prompt, Prompt for Changes Before Job Submission on the Job Card and Print Options panel, the default job card as indicated on that panel is displayed prior to job submission. You may edit the job card and specify whether changes are to apply to the current job only or are to be applied permanently. (See the Common Elements Manual for details.)
The information on the Job Card and Print Options panel is used, along with the extract parameters, to build the JCL and control statements required to perform the Extract Process. If you enter Review at the prompt If Batch, Review or Save JCL on the Specify EXTRACT Parameters and Execute panel, the complete JCL and control statements are displayed in the ISPF editor. You can edit and save the JCL and control statements. (See the Batch Utilities Guide for the EXTRACT statement keywords and values.)
When you have completed reviewing the JCL and control statements, you can submit the job. If you have set the option so that jobs are automatically submitted when END is used, the job is submitted. Otherwise, you will have to explicitly SUBMIT the job from the ISPF editor. (See the Common Elements Manual for information on establishing whether jobs are automatically submitted when END is used.)
If you do not want to submit the job, use CANCEL to return to the Specify EXTRACT Parameters and Execute panel. You can modify the specifications or cancel the Extract Process from this panel.
If an error in the job card is encountered, a message is displayed. You can review the job card and correct the error or terminate the Extract Process.
If you save the generated batch job to a data set, you can submit the job directly from the ISPF editor instead of from within an online session. When you do so, you can override the default Creator ID, selection criteria, and SQL WHERE clause defined in the Access Definition used for the Extract Process. This is especially useful when several extracts are to be performed for a set of tables that vary only by Creator ID or by some set of selection criteria.
You can override these values for batch execution by using the PSDFOVRD DD statement to point to the desired overrides. (Examples follow the discussion of the overrides.)
To override the Image Copy DSN parameter for an unload program, specify:
UNL_IMAGECOPY_DSN image.file.dsnTo override the Image Copy Date parameter for an unload program, specify:
UNL_IMAGECOPY_DATE yyyy-mm-ddTo override the Image Copy Time parameter for an unload program, specify:
UNL_IMAGECOPY_TIME hh.mm.ssTo override the Image Copy Date Criteria parameter for an unload program, specify:
UNL_IMAGECOPY_SELECT { A | B | L | S }To process an Image Copy data set created on a different subsystem, specify:
UNL_OBID [cid.]tblname obidTo override the commit count that was specified when the job was created, specify:
COMMIT_COUNT valueThe value can range from zero to the site limit.
To change commit processing from number of updates to elapsed time, specify:
COMMIT_MINUTES valueThe value is specified in minutes and will override the commit count. The value can range from 1 to 1440. The process report will be changed to reflect the change from the number of updates to elapsed time.
To override the default Creator ID in the Access Definition, specify:
DEFCID cid Only one DEFCID parameter may be specified for an Extract Process. This override also affects the names of the tables in the relationships on the Relationship Usage list. If a relationship is not found for the updated table name, an error occurs when the extract is performed.
To override the selection criteria in the Access Definition for a table or to specify selection criteria for a table that does not have selection criteria in the Access Definition, specify:
SEL [cid.]table column [ selcriteria ] Selection criteria can be specified for one or more columns in the table, but each criteria must apply to a different column.
You can specify only one SEL parameter for each column in a table. You can specify selection criteria overrides for as many columns in as many tables as you want as long as a separate SEL parameter is provided for each column.
To override the SQL WHERE Clause in the Access Definition for a table or to specify an SQL WHERE Clause for a table that does not have one in the Access Definition, specify:
SQL [cid.]table [ /correlation/ ] [ where ]If you do not specify an SQL WHERE Clause, any SQL WHERE Clause specified in the Access Definition is ignored for the current Extract Process.
You can specify the WHERE Clause override for more than one table as long as a separate SQL parameter is provided for each. You can specify only one SQL parameter for a table.
To override the numeric value in the Access Definition used as a factor for selecting rows from a table, specify:
EVERY_NTH_ROW [cid.]tblname value To override the numeric value in the Access Definition used to limit the number of rows selected from a table, specify:
ROW_LIMIT [cid.]tblname value To override the default value of a substitution variable assigned in the Access Definition, specify:
VAR varname value To override the Group Selection Processing in the Access Definition for the Start Table or to specify Group Selection Processing when it has not been defined, specify:
GROUP [column VALUES=values ROWS=rows] The value must be in the range 1 and 4,294,967,295. Specify an asterisk to obtain a specific number of rows from all distinct values of the column. (For additional information on Group Selection Processing, see the Common Elements Manual.)
The value must be in the range 1 and 4,294,967,295. Specify an asterisk to obtain all rows for each distinct value of the selected column.
Only one asterisk may be specified, therefore an asterisk cannot be specified for both values and rows.
This specification can be used with most selection criteria. However, the Every Nth specification is ignored.
Specify GROUP with no operands to ignore the Group Selection specifications in the Access Definition for the current Extract Process.
To override the default treatment for objects referred to in the Access Definition that no longer exist, specify:
UNKNOWN { FAIL | ALLOW }Since the Extract Process uses existing tables and the existing relationships between those tables to traverse the database, be aware that if an unknown table or relationship is bypassed, “related” tables in the Access Definition may not be included even when these tables exist.
UNKNOWN ALLOW is typically used when you override the default Creator ID with DEFCID. Changing the default Creator ID may result in naming tables that do not exist. The UNKNOWN ALLOW parameter lets you direct the Extract Process to skip these “unknown” tables.
To override the extracting of uncommitted data from the database during the Extract Process, specify:
WITH_UR { Y | N }Use the Y operand to extract uncommitted data from the database. Use N to only archive committed data.
The following rules apply when specifying these parameters:
The parameters should conform to the same syntax required when specified directly in the jobstream.
To override the default Creator ID and specify selection criteria for two of the tables in the extract, insert in the JCL:
//PSDFOVRD DD *
DEFCID PSTDEMO2
* LIMIT SELECTION TO CUSTOMERS IN NEW JERSEY
* WHO HAVE ORDERS FOR WHICH THE
* FREIGHT CHARGES EXCEEDED $50.00
SEL CUSTOMERS STATE ='NJ'
SEL ORDERS FREIGHT_CHARGES >50.00SEL requires at least one space between the column name and the selection criteria.
//PSDFOVRD DD *
* LIMIT SELECTION TO CUSTOMERS IN PRINCETON,
* NEW JERSEY
SQL PSTDEMO2.CUSTOMERS WHERE CITY=
'PRINCETON' AND STATE='NJ'//PSDFOVRD DD DSN=PST.SAMPLE.PARMS,DISP=SHR//PSDFOVRD DD *
* CHANGE IMAGE COPY SPECIFICATION TO
* A PARTICULAR DATASET
UNL_IMAGECOPY_SELECT S
UNL_IMAGECOPY_DSN PST.IMAGE.COPYYou can save the JCL and Batch Utility control statements, modify them, and execute the process without re-invoking Move. Specify S to the prompt, If Batch, Review or Save JCL. The following prompts for the information to save the JCL and control statements.
+---------------------------- Save JCL Parameters --------------------------+
| |
| DSN to Save JCL to ===> |
| Member (if PDS) ===> |
| Replace Existing Data ===> Y-Yes, N-NO |
| |
| DSN to Hold SYSIN Data ===> |
| Member (if PDS) ===> |
| Replace Existing Data ===> Y-Yes, N-NO |
| |
| Submit JCL, or Review ===> S-Submit, R-Review, N-Neither |
+---------------------------------------------------------------------------+This panel includes:
If you specify a partitioned data set, specify the member name in Member.
If you specify a partitioned data set, specify the member name in Member.
If you select Submit, the JCL and control statements are saved and the job is submitted. If you select Review, use ISPF facilities to save or submit the JCL and control statements. If you select Neither, the JCL and control statements are saved, but not submitted or displayed for review.
If an unload program is used, the job can only be executed in batch. However, disregard the error messages and return codes in the report for the unload program. You should review the Move Extract Process Report to determine whether the job executed successfully.
For example, the Extract Process uses the unload program only to read the data; the data is not written to DDNAME SYSREC. (The Extract Process uses its own facilities to write the data to the Extract File.) For example, UNLOAD PLUS sets a return code of 4 to indicate no records were written to SYSREC although the Extract Process has performed successfully. As another example, UNLOAD PLUS sets a return code of 12 when the Extract Process was successful but terminated prematurely, because of a user limit for the number of rows from an individual table or for the number of rows extracted for the entire process.
The Extract Process Report always contains appropriate messages. Usually these messages are sufficient. However, the following message may be generated when termination is due to processing of the unload program.
Error detected
during execution of the Unload Program.
See z/OS® Job Log for the error message.
Before invoking an unload program, Move checks for errors to ensure that the selection criteria adhere to restrictions of the unload program. If an error is encountered, Move displays a message. These restrictions are:
When an Extract Process is performed online, Move provides a status notification pop-up window. The content of the window varies depending on whether data and/or object definitions are being extracted. In the following figure, data is being extracted.
+-------------- EXTRACT Process Status -------------+
| |
| EXTRACT Process in Progress |
| |
| Total Number of Extracted Rows: 2053 |
| |
| Processing Table: FOPDEMO.ORDERS |
| Total Rows: 523 |
| |
+---------------------------------------------------+The total number of rows that have been extracted is displayed. Also, the name of the currently processing table and total rows that have been extracted from that table are displayed. This is revised:
When object definitions are extracted, the status panel includes a list of the object definitions (primary keys and relationships, indexes, etc.), and the status of each as one of the following: