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



Paul,
Juat a WAG (so if it not valid, please do not byte :) by head off), but have you
tried to specify the Export keyword on the PSDS in your service pgm and then
defining another DS in you main pgm specifying the Import keyword?
This might allow you to make the PSDS visible in the main pgm.
 
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical
Solutions Implementer V5R3

  
 






________________________________
From: Paul Nicolay <Paul.Nicolay@xxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Sat, March 12, 2011 12:45:47 PM
Subject: RE: Retrieving exception info in procedure

Vern,

Yes, LogError() will even be in a different service program.

That's why I hoped to find an API to access this kind of information... don't
know if receive message will be an option.

If not I guess we need to pass it as a parameter, but I was trying to avoid
that.

Kind regards,
Paul

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Vern Hamberg
Sent: zaterdag 12 maart 2011 14:35
To: RPG programming on the IBM i / System i
Subject: Re: Retrieving exception info in procedure

Paul

OK, then I'm lost. Oh wait - are you hoping to see the exception fields from the
caller in the LogError procedure? Is the LogError in a different code unit
(source member)? Then you won't see it. The PSDS is a module-based item, and
bound units don't transfer it between themselves.

That's all I can think of.

Vern

On 3/12/2011 3:44 AM, Paul Nicolay wrote:
Vern,

No, maybe I worded it confusing... I defined it in the main source (of the
source member that contains my LogError procedure).

But anyway, the exception fields are blank (while in the calling program
they're still fine).

Kind regards,
Paul

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: vrijdag 11 maart 2011 22:27
To: RPG programming on the IBM i / System i
Subject: 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
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To
post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.



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.