Extract Tool

Update Destination File Option (6 of 9)

Once you have used the Update Destination File option, the extracted data from the source file is moved to the destination file. After you enter the name of the EXTRACT template that you wish to use, VA FileMan makes sure the template's mapping information is correct and acceptable and then populates the destination file, adding entries as new records. VA FileMan will not, however, check to see if any of those records to be moved already exist in the destination file. Since this two-step process can be quite time-consuming, it can be queued at the "DEVICE:" prompt.

Here is a sample of the dialogue:

Select EXTRACT OPTION: UPDATE DESTINATION FILE
Select EXTRACT ACTIVITY: 3   CHANGE  08-31-92     EDITED    
SELECTOR:SMITH,J   EXTRACT

You MUST enter an EXTRACT template name.  This EXTRACT template 
will be used to populate your destination file.
PRINT TEMPLATE: CHANGE EXTRACT       **EXTRACT**    (AUG 
30,1992)       USER #2  FILE #16000 

Excuse me, this will take a few moments...
Checking the destination file...

If entries cannot be moved to the destination file, an exception 
report will be printed.

Select a device where to print the exception report.

QUEUEING to this device will queue the Update process.
EXCEPTION REPORT DEVICE: QUEUE TO PRINT ON
DEVICE: PRINTER

After the destination file has been updated, VA FileMan changes the extract activity status from SELECTED or EDITED to UPDATED DESTINATION FILE. At this point, the entries from the source file are no longer available on lookups. This protective measure prevents you from attempting to edit the selected source file entries so that they contain the same data as the corresponding destination file entries.

The following Exception Report is printed when the Extract Tool fails to move all of the data in a source entry into the destination file. A failed INPUT transform is one possible cause of such a failure. In this case, the incomplete entry in the destination file is deleted. The source entry is not locked and its internal entry number is deleted from the extract list. The total number of entries extracted is reduced by the total numbers of entries appearing on the exception report.

EXTRACT  ACTIVITY EXCEPTION REPORT            JUN 27,1996   PAGE: 1
-------------------------------------------------------------------

EXTRACT ACTIVITY: 9          ARCHIVER: SMITH, J

THE FOLLOWING ENTRIES IN THE 'TEST' FILE WERE NOT MOVED BY THE 
EXTRACT TOOL

Entry # 9 was NOT processed because:
  The value 'NEW' for field FTEXT MULT LABEL in FTEXT MULT SUB-FIELD in file TEST is not
valid.

Enter # 30 was NOT processed because:
  The value 'NEW' for field FTEXT MULT LABEL in FTEXT MULT SUB-FIELD in file TEST is not 
valid.

*** PLEASE KEEP THIS FOR FUTURE REFERENCE ***

The following is a list of recommended steps to take when an exception report is printed:

1. Finish the active extract activity by purging or canceling.
   
   
2. Determine the problem with the source entry and fix it.
   
   
3. If there are several entries on the exception report, start another extract activity. Your SEARCH/SORT template can be reused to use the same search specifications.
   
   
4. Adjust the extract list to match the list of entries on the exception report by using the Add/Delete Selected Entries option.
   
   
5. Proceed as before.

For exceptions caused by INPUT transforms, keep in mind that the value of each field in an extracted record is tested against the INPUT transform of its destination field. If any value fails its destination field's INPUT transform, the extract for the entire record will fail. Make sure the INPUT transforms on the destination fields are appropriate for the data you will be extracting.

NOTE: If you are extracting a Subrecord using the EXTRACT^DIAXU entry point and its FILING_LEVEL parameter, and a value fails the INPUT transform, only the extract of the Subrecord will fail.

Reviewed/Updated: March 4, 2007