× 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 don’t really need ACS to access the root file system.

Seems kind of klunky to me to use the ACS IFS access for downloading plus you may be giving out undesired access accidentally. I use the IFS access but not often. Usually only when I don’t have another way to access the IFS.

One option I’ve used successfully recently is to use the SAMBA (Windows file transfer client) client on IBMi to copy files to a network location. (Assuming you have more than the 1 system). The SAMBA SMBCLIENT app runs from PASE and doesn’t need NetServer running.

Either that or using a UNC path instead of drive letter allows you to NOT map a drive. Just share the UNC path with users and teach them about UNC instead of drive letter.

Email of course where you don’t need an archive copy.

Just a couple of thoughts.

Regards
Richard Schoen

----------------------------------------------------------------------

message: 1
date: Mon, 10 Aug 2020 20:57:07 +0000
from: "Howie, Bill" <BHowie@xxxxxxxxxxxxxxxx>
subject: Using ACS to access the IFS

Hello all,

I'm attempting to try some options that will steer us away from using the QDLS file system. I'm looking at creating directories in the root file system and was playing around with how ACS accesses the IFS. It seems to be REALLY slow. These directories I'm looking at creating will be ones that we will want the users to have access to, so of course we will have to lock them down authority-wise, but if I can't get around the slowness of the IFS access in ACS I'm not sure it's an option. I can of course, map a drive through Windows. I wondered what everyone's thoughts were on the best method of access. Right now we have a lot of programs that will run reports that email a CSV file to a user. But we will run into issues where they don't email for whatever reason. So the thought was that an alternative is to just park the file in a directory on the IFS where the email communication isn't necessary. But we also want to have something where speed isn't an issue. And I'd rather try
to get away from having to map drives on everyone's machines if I can help it. What's everyone out there doing for this kind of functionality? All responses are, as always, greatly appreciated.

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.