RE: Record lock, no retry?

Sorry, the OPM remark added nothing to the discussion.

From what I've observed OPM or all main-line ILE would both operate as desired. We get the undesirable outcome when the record lock occurs within a procedure. I think Kevin's on the right track about that.

My copy of the ILE Concepts book was from v5r4, so I downloaded the 7.3 version.

Default Actions for Unhandled Exceptions
If an exception message is percolated to the control boundary, the system takes a
default action. If the exception is a notify message, the system sends the default
reply, handles the exception, and allows the sender of the notify message to
continue processing. If the exception is a status message, the system handles the
exception and allows the sender of the status message to continue processing. If
the exception is an escape message, the system handles the escape message and
sends a function check message back to where the resume cursor is currently
positioned. If the unhandled exception is a function check, all entries on the stack
up to the control boundary are cancelled and the CEE9901 escape message is sent
to the next prior stack entry.


Thanks




-----Original Message-----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Wednesday, September 05, 2018 1:02 PM
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
Subject: Re: Record lock, no retry?

I don't see how this would help Justin. Somehow you need to track down why an error is not being signalled directly on the I/O operation. ILE or OPM shouldn't;t matter there surely.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 5, 2018, at 1:56 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

You may be on to what's going on. "We" may just have to change our expectations, or go back to monolithic OPM code.

Thanks



-----Original Message-----
From: Kevin Bucknum [mailto:Kevin@xxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 05, 2018 12:35 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxx>
Subject: RE: Record lock, no retry?

Since the location of the error doesn't appear to be in a control boundary, I think your only options are going to the monitor/error extender, or reconfigure your call stack so that the error occurs in a control boundary.

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

--
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