RE: Record lock, no retry? -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Record lock, no retry?
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Wed, 5 Sep 2018 17:56:16 +0000
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Record lock, no retry? , Jon Paris

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.