Re: Possible Automated Troubleshooting on RECORD LOCK -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: Re: Possible Automated Troubleshooting on RECORD LOCK
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Fri, 1 Apr 2016 14:27:44 -0400
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 4/1/2016 12:32 PM, Hoteltravelfundotcom wrote:

Record 5858274 in use by job 427038/NINAM/XT09DD0B10.

This would help alot. So my question is, can the RPG be able to discern the
above message?

No joke; my favourite part of the RPG Reference is error handling. On
the 7.2 Knowledge Center, that's right near the top; in the 'Basics of
RPG IV' section.

One place that this particular message is exposed is in the Program
Status Data Structure.

There are relationships between the File Information Status Data
Structure (INFDS), Program Status Data Structure (PSDS), %error or the
(e) extender and %status, but generally speaking, it is good to
understand these relationships.

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.