CHGPF - Gotcha

[BG0794 <BG0794@xxxxxxx>]

The other day, I used the CHGPF command to re-map the files data elements
(utilizing the source file/library parms.).  The new DDS in addition to having
added fields, also specified that one of the new fields is to be part of the
key.  The original file was keyed by a single 6 digit numeric field and the
key was not Unique.  The new additional key was a 3 digit numeric field (just
a sequence number to force uniqueness).  The DDS was also changed to make the
file uniquely keyed.  After the CHGPF was executed, a newly compiled RPG
program attempted to write records in to the new definition of the file.  The
file was defined as output only.  The write op-code had the error indicator
specified to catch duplicate key problems.  I placed the write in a do loop
checking for the I/O error indicator to ensure a unique key.  Well...  it
never sensed the dup key (and therefore not incrementing the second key
value).   Proof that the file was uniquely keyed was done by trying a CPYF
statement and UPDDTA against the file.  Each running of the command indicated
that there were duplicate keys in the file.  
    Anyway, I fixed the problem by recreating the file by using CRTPF
(actually I duped the file via crtduobj from a library where the file had been
previously created by the CRTPF).  Is this a bug?  Maybe, I have not contacted
IBM with the problem yet. 

Bill Greenfield
CAS
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---