writing to keyed AS400 targets with 6.2.2

[blom0344]

We have upgraded the client access V5R2 to PTF level SI16136 (nov. 2004)which should be the latest one for V5R2.
As long as we run inserts into AS400 file without having keys/constraints on the target everything runs smoothly (but only with isolation level COMMIT IMMEDIATE (*NONE) )

Inserting data into a file with primary key defined causes rejected rows , even if we are dead certain that no duplicate keys are going to be inserted.

Running an update/insert strategy does not cause any rows to be rejected, but then the logging shows that even with an empty table about 15% are treated as an update and 85% as an insert. Of course this will never work with building sales-history etc.

We see similar behavior with running against a V5R3 machine, so we are wondering if Client Access is the right medium anyway.

Anybody experience with the combination V6.2.2 / AS400 / Client Access?

Ties Blom
Information analyst

 

[blom0344]

Well, didn't expect much of a reaction anyway, but here is the verdict anyway:

INFA support came up with the suggestion to change a registry setting to change the default array inserts to single row inserts. This means that insert performance is about 3 times slower, but it means that only duplicates are rejected (and no t the rest of the array) We haven't dug into it to check the AS400 part of the issue, but for now it works ( albeit quite slowly)

Cheers!

Ties Blom
Information analyst