Re: Identity Columns

GENERATED ALWAYS should ignore the what RPG passes in...

GENERATED BY DEFAULT would cause this problem...

Another possible source...do you have an SQL process that does an INSERT
with the "OVERRIDING SYSTEM VALUE" clause?

Charles


On Thu, Jun 14, 2018 at 6:41 AM Craig Richards <craig@xxxxxxxxxxxxxxxx>
wrote:

Hi All,

I have some files with Identity Columns typically defined something like:

MsgCnt_UniqueID for column UniqueID Integer
not Null
generated always as identity ( start with 1 increment by 1 cycle )
primary key

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.

There is a subfile program and maintenance screen which use the same
service program for DB access which all run in Activation Group QILE. But
these are called via a wrapper CL which does a RCLACTGRP between calls.

I'm a little stumped about what is causing this intermittent issue.
Is it dodgy to perform RLA with an identify column defined as above?
Or are there any special considerations I'm missing?

thanks kindly for any comments.

best regards,
Craig
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD