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



You might try using stat() to determine the existence of a file in the
IFS - that works for me.

WRKLNK works with all the IFS file systems; WRKFLR only works with the
QDLS file system. Don't use QDLS - it's slower and more limiting than
the other file systems.

> -------- Original Message --------
> Subject: Question about access()
> From: "Marvin Radding" <marvin.radding@xxxxxxxxxxxxxxxxxxxxx>
> Date: Mon, January 09, 2006 10:44 am
> To: <rpg400-l@xxxxxxxxxxxx>
> 
> I am trying to create a program to write directly to the IFS.  I am using 
> access() to determine the existence of a file in the IFS.  But all I get are 
> 'No such path or directory.' and when I try to use pathconf() I get the same. 
>  In order to access the directory and the file I have to use WRKLNK rather 
> than WRKFLR.  What is the difference between the two?  And what routines do I 
> use other than access() and pathconf()?
> 
> Thanks for the help.
> 
> Marvin
> 
> -- 
> This is the RPG programming on the AS400 / iSeries (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 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.