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



OK - I see your point.  I never qualify library in LF source, just depend
on *LIBL.

...Neil





"Dan Bale" <dbale@samsa.com>


        To:     <midrange-l@midrange.com>
        cc:
        Subject:        RE: File attributes PF38, LF38, PF38-DTA, PF38-SRC


Would an native LF source member know what to do with:
     A                                 PFILE(FILEOBJ.LIBRARY)

Isn't that the correct syntax for s/38 qualified objects?

Might be the same type of issue for REF and REFFLD specs that qualify the
object.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )

Neil Palmer wrote:

That would only affect you if you had something like a CLP program with
type CLP38 instead of CLP.
The attribute on the files would make no difference for PF, LF etc.  There
are some differences between PRTF38 and PRTF though.

...Neil






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.