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

RE: PSDS source informations availability

Do you ever use SQLRPG? I don't know if this will make a difference, but in this case the actual object is created from a temporary interim source member but I don't know whether or not this will be reflected in the PSDS information.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Marco Benetti
Sent: Friday, January 17, 2014 9:50 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: PSDS source informations availability

Hi.

In a RPGLE program I need information about the source from which I compiled. I need to know library, file source and member.
I always compile with CRTBNDRPG command. So I have an object *PGM for each source member.

I found the needed information in the PSDS (Program Status Data Structure):

D SRC_FILE 304 313 Source file D SRC_LIB 314 323 Source file lib D SRC_MBR 324 333 Source file mbr


My doubt is..
Are these three information ALWAYS available?
Even, for instance, in case of not observable program?

I made some test with CHGPGM RMVOBS(*ALL) and everything seems working properly: those three fields are correctly valued. 
There are cases in which these informations are not available?

Thanks in advance

Marco

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.