Al -- 

There may be an easier solution . . . 

1. Restore the ITH file from tape to ANOTHER LIBRARY.

2. Write a Query to find put the records in the restored version of
ITH and NOT in the production versionto an output file.
-- RESTORE/ITH as the first file, BPCSF/ITH as the secondary file
-- join type 3 (unmatched records)
-- join criteria - be sure of uniqueness - (see note below)
-- select ALL fields from the restored file
-- put the records into an OUTFILE, how about RESTORE/ITHX

3. Query ITHX and confirm to your satisfaction that it has the records
you need and only the records you need.  Repeat #1 & #2 adjusting the
query if necessary.
--> Do not cut corners here - run lots of tests, comparing quantities
and record counts across time periods, etc, until you are 100% sure
the output file is correct.

4. Save a copy of the production ITH file

5. CPYF *ADD from the output file to the production ITH file.
--> CPYF MBROPT(*ADD) -- no *MAP, *DROP, etc.
--> Test again - look for duplicate records

6. Run a reset, and query balances against the saved ITH from step 4.

Note:  I am not sure how the transaction sequence number works on your
system.  We have had issues with it, and have a (very simple) program
to reset it based on date and time.  I would NOT use the sequence
number to test for uniqueness.

Have fun.




-- 
Tom Jedrzejewicz
tomjedrz@xxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.