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


  • Subject: Re: Where is the PF-SRC attribute?
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Mon, 08 Feb 1999 08:37:42 -0700

Loyd,

I have used the QDBRTVFD API to retrieve this attribute.  If you look at the 
copy 
source member in QSYSINC, the value you are looking for is bit 4 (the 5th bit) 
of 
the field QDBBITS.  A '1' indicates a *SRC file.  The PF/LF attribute is bit 2 
for of 
this field.  If this is the only reason you have to support this API, I would 
look into 
using RTVFD.

David Morris

>>> lg - Loyd Goodbar <lgoodbar@watervalley.net> 02/05 4:52 PM >>>
I'm starting to write a program to process source physical files, but I can't
seem to find the attribute that tells me a file is source versus data. I was
using the QUSLOBJ API to get a list of files in a library, then possibly
QUSOBJD (? I'm not at the AS/400 now) API to retrieve the file desciption. I
can see *FILE as the type and PF as the (extended?) attribute, but not source
versus data. Where can I find this?

Thanks,
Loyd

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.