I am building a file for ETL.

I stuck a seq # key on the front of the record (with duplicates).

First, I populate the file with any customer record which was changed today - from the journal record - using a TAATOOL.

The seq # key is zero for all these new adds.

Next I come thru with a COBOL pgm and update the CUST records with current data.

When I try to rewrite record - after changing the seq#, I receive error 21 - OS is stating I cannot change key if dup keys are allowed.

I need to change the key from zero to a seq # for downstream processing - how can I get around this?

I don't want to add another file in between to accomplish.


This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.