Just be sure your iSeries Netwok server jobs are running and that you have defined the proper IFS directories and files as SHARES on any attached and authorized PC with iSeries Access (Management Central) Then any of your networked PC's can access those shares and do whatever they are authorized to do at any time via BAT files or any other application. ======================================================== NetServer is the system facility that communicates out to the Windows network, so it does need to be running. Also, if a Windows process needs to access a directory in the /root file system of the IFS, a share does need to be defined. Management Central isn't involved. The Windows process can access shares either through an appropriate user ID or through NetServe GUEST profile access. If a user ID is used, it can be the user ID of the Windows process when there is a matching user profile with a matching password on the AS/400. If the user ID doesn't match, the Windows process can call the CWBLOGON System i Access program to create a connection under a chosen user/password combination. Note that the Windows process can also do its work in a normal Windows share on some Windows system on the network. The same share can be accessed by the AS/400. It can reach out through the /QNTC file system to external shares just like remote systems can reach in. Tom

Just be sure your iSeries Netwok server jobs are running and that you have defined the proper IFS directories and files as SHARES on any attached and authorized PC with iSeries Access (Management Central) Then any of your networked PC's can access those shares and do whatever they are authorized to do at any time via BAT files or any other application. ======================================================== NetServer is the system facility that communicates out to the Windows network, so it does need to be running. Also, if a Windows process needs to access a directory in the /root file system of the IFS, a share does need to be defined. Management Central isn't involved. The Windows process can access shares either through an appropriate user ID or through NetServe GUEST profile access. If a user ID is used, it can be the user ID of the Windows process when there is a matching user profile with a matching password on the AS/400. If the user ID doesn't match, the Windows process can call the CWBLOGON System i Access program to create a connection under a chosen user/password combination. Note that the Windows process can also do its work in a normal Windows share on some Windows system on the network. The same share can be accessed by the AS/400. It can reach out through the /QNTC file system to external shares just like remote systems can reach in. Tom