All I can think of is to add the new record and delete the old record. That's what we did back in my mainframe days when changing the key was not allowed.
Scott Lindstrom
Reynolds Leveraged Services | HP-UX, Linux, and AS/400 Administrator
-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Thursday, July 05, 2012 4:28 PM
To: 'COBOL Programming on the iSeries/AS400'
Subject: [COBOL400-L] file update - change key value
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.
Thanks!
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit
http://www.symanteccloud.com
______________________________________________________________________
midrange.com
