RE: Best practice for establishing a QNTC path

We have a file share that is secured to a single service account.
Then a program is used to Connect to the file share from the iSeries.
If verifies the QNTC folder and also establishes a Kerberos ticket for the service account.
So both are done in the same place and the processes that use the share's files just need to run the "Connect" program.
Those processes are restricted to the user profile we allow to access the remote share.


I liked having the creation of the QNTC folder and the authentication in the same process. That way I knew that I could set up the folder when I needed to establish a connection.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Jason Aleksi
Sent: Thursday, June 3, 2021 10:24 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Best practice for establishing a QNTC path

*Possible Solutions*

1) Create a CL script that runs MKDIR DIR(‘/QNTC/server’) for each
remote file server as part of the startup IPL sequence.



2) Modify each CL/RPG program to check/create the link each time:
MKDIR DIR(‘/QNTC/server’)
MONMSG CPFA0A0 /* Ignore if object already exists */



Are there any other methods or preferred best practices?



-JA-