Re: Using QNTC -- MIDRANGE-L

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

I am in the same boat here. the Windows people say that it "is too much work" to get NFS going over our "robust Windows Active Directory structure". "we have leveraged object permissions to a high degree of
customization". and we also are using DFS (Distributed File System) which is like DNS for file servers...

We do map QNTC servers here, and since it takes time for the mapping to occur, we submit a separate job in the STARTUP program to perform the mapping.

-gerald

sjl wrote:

All -

After reading through the archives about issues and concerns with using the QNTC file system to copy files to/from a Windows server, I fully understand that NFS is better and more stable.

However, given that:

1) There is an incredible bureaucracy within our multinational company to get the necessary approvals that must be done to install NFS on the Windows Server (if not already installed)

and

2) Other production applications on our systems are already using QNTC to copy files to/from Windows servers

I need to know about any potential gotcha's beyond the necessity of putting a MKDIR '/QNTC/Servername' in the system startup program to ensure that the server name remains mapped after an IPL.

Regards,
sjl

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.