Re: Record lock, no retry?

Nah - not a gamer. Just a late flight - didn't land until 20 after midnight.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 5, 2018, at 5:15 PM, Krill, Coy <CKrill@xxxxxxxxxxx> wrote:

I'm old, didn't get to bed until 2am either because I was playing Destiny 2: Forsaken. Any chance you were doing the same :-)

Coy Krill
Core Processing Team Lead
Washington Trust Bank


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> On Behalf Of Jon Paris
Sent: 2018 September 05 14:13
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
Subject: Re: Record lock, no retry?
Importance: Low

Yes - you are correct. My excuse is that I'm old and didn't get to bed until 2am this morning <grin>


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 5, 2018, at 2:20 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Jon,

Justin said the failing code was in a *MODULE, so I'm assuming this is
a sub-procedure in a *SRVPGM...

Without error handling in the procedure or it's calling *PGM, wouldn't
the error get percolated up as a "The call to &1 ended in error."
rather than the original "record lock".

From your own RPG Exception handling Redpaper...
- All exception/error handling has been removed and the processing
logic has been placed in two subprocedures, ProgramProc and FileProc.
- The divide by zero error has been reintroduced.

When you run this program you might expect it to fail with the RNQ0102
Attempt to divide by zero message at (3) above, but it doesn’t!
Instead, the program fails with a RNQ0202 The call to PROGRAMPRO ended
in error (C G D F) message at (2) above. You see the following
information in the joblog:

Attempt made to divide by zero for fixed point operation.
Function check. MCH1211 unmonitored by ERROR10 at statement
0000002100, instruction X'0000'.
The call to PROGRAMPRO ended in error (C G D F).

Charles

On Wed, Sep 5, 2018 at 12:02 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

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

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

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

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


---------------------------------------------------------------------
This electronic mail message and any attachments may contain confidential or privileged information and is intended for use solely by the above-referenced recipient. Any review, copying, printing, disclosure, distribution, or other use by any other person or entity is strictly prohibited under applicable law. If you are not the named recipient, or believe you have received this message in error, please immediately notify the sender by replying to this message and delete the copy you received

---------------------------------------------------------------------

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