CLRPFM and DDL record identity column

We are gradually modernizing our accounts payable system and have defined the files with DDL.

The basic method is data is added to an entry file (by a PHP program) that has an identity column. The entry file is processed and the identity column is moved to a similarly defined field in the master file that is NOT defined as an identity column but will be used as if it were an identity column. It is defined as an integer, same as the record id in the entry file.

The reasoning for this method was SQL is not being used in the RPG programs, so the identity column in the master file may not get incremented correctly. The entry file is fed by PHP/SQL so the DDL should do its thing there and we would have nice unique identities that could be added to the master files.

After each batch is updated, we run CLRPFM on the entry file. I was assuming this would not reset the record id number, but we have been getting some duplicate ids in the master file. As we are preparing this system, we are slinging data around like there's no tomorrow, so it's possible that we did something ourselves that caused the duplicates. But I'd like to make sure my method for coming up with unique numbers from the entry file are valid.


So can anyone confirm that CLRPFM will not reset the identity column in a DDL defined file?


---Dale