Re: Identity Columns

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 06/14/2018 08:41:03
AM:

When performing writes to a table with one of these fields using RGPLE

RLA

I thought that the UniqueID column in the RPG program was just ignored

and

a new unique ID assigned.

However I find I'm sometimes getting some duplicate key errors which are
definitely with the Table ( not other indices ) and the primary key on

the

table is just the identity column.

Obviously with an SQL Write, I can specify a list of fields, excluding

the

identity column.

In RPG is it necessary to use Data Structures on the DB operations to

also

specify a list of fields which excludes the ID column?

I haven't convinced myself 100 percent, but this issue only seemed to
appear when I was calling the program and then switching library lists

and

calling the program again.

You mentioned other indexes. Does that mean you confirmed that
the duplicate key wasn't occurring with a secondary unique key rather than
the primary?

Otherwise... I haven't used RLA to write to a table with an
identity column. However, comparing to using SQL, you cannot include the
identity column in your RLA WRITE. SQL has the advantage of extended
indicators so that you can include, but ignore, the identity column. You
don't have that luxury in RPG RLA. So, you must omit the identity column
for your RPG RLA access.

That said... There can definitely be an issue with switching
library lists if the file/table in question is a different file/table in
another library. In this case, the file should be user-controlled and an
explicit CLOSE issued -- unless you're using the cycle and setting the
*INLR indicator before switching library lists. In other words, you must
make sure the file is hard-closed before switching library lists.


Sincerely,

Dave Clark