Re: Writing to a Windows server instead of to the IFS -- MIDRANGE-L

Man, I can be dense. None of these answers look easy & straight forward.

I am using Scott Klement's examples to write a PC file to the IFS of the System i. It uses a path & file name, which of course I expect. It occurs to me that one can type in any path name and there is no real reason that it won't write directly to what ever is at that path?

But like so many things, it just isn't so. My first question is: Am I dreaming? Is it really simple, or is it a lot of hoop-jumping and therefore of limited value??

vhamberg@xxxxxxxxxxx wrote:

Although we do sometimes have customers use QNTC to put documents on a Windows, be strongly urge the use of NFS - network file system - every Unix/Linux box already probably has this, and there is a free install from MS for Windows. It is usually set up for anonymous access from a limited list of hosts (IP addresses) but can be secured using the UID/GID functionality - we have those in our user profiles now - just a glorified Unix box we is!!

You could go to our site - www.rjssoftware.com - go to the support link there and then to our wiki - do a search for NFS - we have a couple articles on setting things up, including the MS install.

Once set up, it works basically the same as QNTC - a mount of the remote share - but it works so much faster.

HTH
Vern

-------------- Original message -------------- From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>

QNTC....
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 Release NewProfHdl Release OldProfHdl
Now, ensure that each of the network shares that you need to access will allows access to the NETUSER profile.
Easy, right?
Let me know if you need more... Eric
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [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?

--
--------------------------------- Booth Martin http://www.Martinvt.com ---------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.