how to write to a windows folder from an AS400

i am doing some research for a vendor.
he has an AS400 and we need to have him put some transfer files into a folder on the windows server.
the network admin of his comp has said no FTP....

is there a way to "map" a drive on the AS400 TO a shared windows folder that would allow direct writing to that folder?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

There are several ways to do that.  One way would be to create a "share" on the 400.  Then map the windows box to it.  There are a few CPY commands to get your 400 data in that share. CPYTOIMPF and CPYTOSTMF are two of the commands.

You will use the iSeries Navigator to create the share.  Navigator is part of iSeries Access.  You may have to install additional features of Navigator.

You could also install the Windows Unix utilities and then you can "mount" a drive.  Your Windows admin may shoot that one down also.

The last one that comes to mind is the 400s QNTC file system.  I know it will do this kind of thing.  I have never done it.

Steve Bowdoin
CASorterAuthor Commented:
i can do a share TO the AS400 FROM the windows box...   but there are permission issues when trying to access files through the SQL scheduler that is trying to process the files.  we are trying to work through those, but the network dudes are pretty tight.

what i need is TO the windows box FROM the AS400

what do you get when you do a  WRKLNK '/QNTC/*' ?

there are many things that can get in the way but if you see your windows server that would be great.

make sure your AS/400 user id and Windows user id and passwords are the same.

See what the net dudes think of "windows services for Unix".

HTML5 and CSS3 Fundamentals

Build a website from the ground up by first learning the fundamentals of HTML5 and CSS3, the two popular programming languages used to present content online. HTML deals with fonts, colors, graphics, and hyperlinks, while CSS describes how HTML elements are to be displayed.

Gary PattersonVP Technology / Senior Consultant Commented:
There are two AS/400 utilities that are designed to help with AS/400-Windows file sharing.  which one you use depends on which is the server and which is the client.

NetServer (AS/400 as server, Windows as client) is a tool that allows you to share AS/400 Integrated File System Folders in a Windows environment.  It lets Windows clients access the AS/400 using the SMB/CIFS protocol, and allows Windows clients to use Windows explorer or DOS commands to manipulate stream files in the AS/400 IFS.

NetClient / QNTC (AS/400 as client, Windows as server) does the opposite job.  It allows AS/400 clients to access Windows shares using the SMB/CIFS protocol.

Steve's definitely on the right track suggesting QNTC.  

"Windows Services for Unix" is not required with QNTC.

The AS/400 QNTC (NetClient) file system is designed exactly for this need.  There is a bit of configuration and planning required, so please save yourself a lot of trouble, and read the documentation carefully before you start setting it up.  In particular, you'll need to set up a Windows user ID for QNTC to use to access the Windows share.  That user ID will need to have the proper share rights and NTFS permissions to perform the desired operations (or the share and NTFS folder will need to be authorized for Everyone, and that is usually not a good idea.)

QNTC is part of the base AS/400 operating system, so no special installation steps are required.

QNTC allows Windows shares to be accessed using the SMB protocol from the AS/400 Integrated File System.  Once properly configured, AS/400 applications can read, write, delete, and update stream files in the QNTC file system just like any other IFS files:

For example, lets say we have the following servers:

MYWIN2003 (A Windows 2003 server)
MYAS400 (An AS/400)

And MYWIN2003 has a share called "Shared":


Once configured, on the AS/400, I can move a stream file called "myfile.txt" from my home IFS folder to the Windows share with the following AS/400 command.

MOV OBJ('/home/gary/myfile.txt') TODIR('/QNTC/MYWIN2003/Shared/')

The MOV command can also optionally perform code page or CCSID conversion:

Once QNTC is configured, the AS/400 automatically detects shares on the local subnet (same IP subnet as the AS/400).  Shares that reside on Windows servers on different subnets have to be manually added to the QNTC file system using the AS/400 CRTDIR command or the mkdir() API.  These links have to be re-created after every IPL, so it is a good idea to put them inthe system startup program (just like mapping drives in Windows).

Joe Hertvik wrote a nice, short article on QNTC that explains the basics:

Full configuration details the IBM Information Center for your release:


- Gary Patterson


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CASorterAuthor Commented:
this is not for me... it is for a vendor,   i will pass the info on to him.


will keep you posted
It seems a little strange that a "vendor" has a system in the AS/400 line but can't set up a connection to their own network. However...

One part that might make it easier is for the fact that there must be both authentication and authorization for the current user in the AS/400 process to the shared Windows resources. To ease that process, there is often a local user created on the Windows machine. This local user will have a user ID and password that matches a user profile on the AS/400. Matching user name and password makes the connection easier.

The AS/400 process that copies the data doesn't have to be started by that user; but, if it's not, it does need to be able to switch its "current user" to be that user during the operations that actually interact with the Windows share.

The vendor's 'network guys' might balk at creating a local user on a Windows box, but it doesn't have to be a Windows Server box. Mostly it just needs to be Win2K or later and be part of the same domain that the AS/400 NetServer configuration sets up to join.

There is much more that can be done, but a matching user/password combination on both systems can sure make things easier. This might be done only during beginning tests. More sophistication can be introduced as the whole process becomes more familiar.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IBM System i

From novice to tech pro — start learning today.