Re: Soft Close/Pseudo-Close

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Soft close / Pseudo close is for the table itself, not any individual records...

Thus, it's not possible for it to interfere with an RPG CHAIN...

It sounds as if the Hibernate commit isn't occurring and the records
hibernate changed are still locked...as it appears that rows locks
should be released even if COMMIT HOLD is used...

I'd suggest digging into the commitment control status via WRKJOB  for
the job servicing the hibernate requests...

HTH,
Charles

On Mon, May 21, 2012 at 12:22 PM, Lewis, Doug <Doug.Lewis@xxxxxxxxxx> wrote:
> Hi All,
>
> We have a Java app that performs a Hibernate commit and then calls a RPGLE stored procedure. The stored procedure is returning an error code due to a lock on a file it is chaining to. This file is being locked within the same job and appears to be a Pseudo-Close issue.
>
> Threads from the archive allude to using ALCOBJ/DLCOBJ or changing the QAQQINI. It seems to me that both of these options would destroy the ODP. I would prefer to keep the performance from the reusable data path do to the fact that changes are being made to speed up the app.
>
> We are at V6r1.
>
> Is this a bug? Shouldn't native I/O recognize this and proceed?
>
> Any thoughts or ideas on how to resolve this would be appreciated.
>
> Thanks,
>
>
> Doug Lewis
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.