The QNTC file system is intended to provide access to Windows Networking Shares, aka Network Neighborhood from a few years back.
The trick with QNTC is that you cannot directly control the user credentials used to open the connection. The system uses whatever profile/password is in effect for the job that is accessing the network share.
What I did, when I needed to have standardized read/write access across network shares, was to create a profile in the iSeries AND in Windows domain, that have EXACTLY the same login credentials on both sides. For illustration, we'll call it NETUSER....
Now, before you try to read or write through the QNTC filesystem, you need to use the QSYGETPH, QWTSETP, and QSYRLSPH api's to do the following:
Get the CURRENT profile handle (OldProfHdl)....
Get the NETUSER profile handle (NewProfHdl)
Swap the job to NewProfHdl
Do your read/write via IFS /QNTC/......
Swap the job to OldProfHdl
Now, ensure that each of the network shares that you need to access will allows access to the NETUSER profile.
Easy, right? <g>
Let me know if you need more...
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Booth Martin
Sent: Wednesday, October 17, 2007 5:04 PM
To: Midrange Systems Technical Discussion
Subject: Writing to a Windows server instead of to the IFS
Writing to a Windows server instead of to the IFS
Scott Klement's programs for writing CSV files to the IFS is pretty
spiffy and an emotional lift! Man, its a nice feeling to map the IFS to
my PC and open a csv file with Open Office with no file transfers, etc.
It raises the obvious question however. Can we also write directly to a
Windows server? And, if so, how do we submit the User/password?
This mailing list archive is Copyright 1997-2019 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