|
Shouldn't the C-style IFS API also work in/on /QNTC? Has someone tried it with access()?
Wasn't "transparency" the root-idea behind QNTC?
I don't have a QNTC counterpart here, so I can't test it myself.
Regards,
Daniel
Am 08.05.2026 um 14:47 schriebstefan@xxxxxxxxxx:
You can use the stat64 ( for larger files ) or stat ( for files up to around 2Gb) in the following file systems:
* "Root" (/)
* QOpenSys
* User-defined
* QNTC
* QSYS.LIB
* Independent ASP QSYS.LIB
* QOPT
* Network File System
* QFileSvr.400
Best regards
Stefan
--
No trees were killed in the sending of this message, but a large number of electrons were terribly upset.
Stefan Tageson
+46 732 369934
stefan@xxxxxxxxxx<mailto:stefan@xxxxxxxxxx>
________________________________
From: MIDRANGE-L<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Rob Berendt<robertowenberendt@xxxxxxxxx>
Sent: Friday, May 8, 2026 14:20
To: Midrange Systems Technical Discussion<midrange-l@lists.midrangecom>
Subject: Re: How to check if exist in IFS (QTNC) a file
Too bad:
IFS_OBJECT_STATISTICS table function
No rows are returned for remote file system objects. This means that for
the QNTC file system, only a row for /QNTC is returned. For the Network
File System (NFS) and QFileSvr.400 file systems, no rows are returned.
On Fri, May 8, 2026 at 6:31 AM gio.cot via MIDRANGE-L <--
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Hi all
I would need to check in a windows server (mapped via QTNC), if exist a
file
with partial name;
example: if i run "DSPLNK
OBJ('/qntc/zz-yy-appxx/XT/DOCS/TX/ORDERS/HIST/myfile_26_90501*') , i can
see that in the folder exist a file named "myfile_26_90501_11052026.txt"
can i do with clp or rpg run a command to check existance passing the file
partial name ?
usually i use extproc('access') File_Exists = access(pathptr:F_OK)
Thanks in advance
Gio
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.