× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. March 2011

Re: Retrieving exception info in procedure

Paul

Are you saying you specified the PSDS in a subprocedure? And it let you? This statement from the RPG Reference say -

"The PSDS must be defined in the main source section; therefore, there is only one PSDS per module."

If you WERE able to put one in a subprocedure, its subfields would not be available outside that subprocedure.

I think!
Vern

On 3/11/2011 12:25 PM, Paul Nicolay wrote:
Scott,

I tried defining the PSDS globally in the procedure... but the exception fields are blank :-(

Thanks,
Paul

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: vrijdag 11 maart 2011 18:42
To: RPG programming on the IBM i / System i
Subject: Re: Retrieving exception info in procedure

Depending on the amount of detail you need... the %STATUS() BIF might help. If you need more detail, you could use the QMHRCVPM() API...
PSDS should also be available (as global variables) to your subprocedures.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.