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



Hi Aaron

The only attribute I can think of that will help is a file attribute
(FILETYPE = *DATA or *SRC) I'm not sure how consistent that is never having
had to rely on it.

It's available in the QDBRTVFD API in format FILD0100 if I'm reading the
documentation correctly.

I used that API once; have fun.... :)


Regards
Evan Harris

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Aaron Bartell
Sent: Monday, 29 September 2008 2:51 p.m.
To: RPG programming on the AS400 / iSeries
Subject: QUSLOBJ - how to differentiate source PF's from data PF's

I am writing a program to call QUSLOBJ and am wondering if there is a way to
tell source physical files from data physical files (i.e. QRPGLESRC vs.
CUSTMSTPF). When I call the API there is both the object type and
attribute, but these end up being the same for both types of objects. I
have looked through the variety of result formats and am not seeing anything
that would be a differentiator. Note that checking for "Q*" isn't an option
because there will be source physical files with names that start with
letters other than "Q".

QUSLOBJ API docs:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/
quslobj.htm

Any ideas?
Aaron Bartell
http://mowyourlawn.com


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.