From a Windows desktop, map a drive letter to the IFS folder, then use drag and drop.
Or use FTP.
Both of these solutions require a specific TCP service be running on your i. FTP requires (of course) the FTP service, while mapping a drive letter requires the "iSeries NetServer" service (support for Windows network Neighborhood).
Last Wiki Answer Submitted: March 3, 2010 4:28 pm by Littlepd1,130 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
In short, you do it the same way for a .CSV file in your AS400 as for one anywhere else. You double-click it or drag/drop it or pass its name in as a parm when you run a program or whatever.
The “trick” is simply that the fully-qualified path to the .CSV file must be known to your desktop.
And you make the path known the same way you do for any path anywhere else in your network. You create a share that announces itself to the network. You can then either have a mapped drive to that share or you can use the standard Windows format for qualifying to a remote resource, just like a resource on any Windows or Linux server.
Note that FTP only needs to be running on the i if you use it as the server. If you use it as the client, then FTP has to be running as a server on the PC.
Technically, a similar kind of situation is true for mapped drives. One side will act as a client for each connection; the other as a server. On the i, NetServer is either the client or the server as needed for Windows networking. (And the File host server is accessed by NetServer.) And on the PC for Windows, the Server service and possibly others need to be running — I’m not at all clear on all the possibilities there.
Use one of the free email programs and email it to your self. You could also use SNDDST.
In short, you do it the same way for a .CSV file in your AS400 as for one anywhere else. You double-click it or drag/drop it or pass its name in as a parm when you run a program or whatever.
The “trick” is simply that the fully-qualified path to the .CSV file must be known to your desktop.
And you make the path known the same way you do for any path anywhere else in your network. You create a share that announces itself to the network. You can then either have a mapped drive to that share or you can use the standard Windows format for qualifying to a remote resource, just like a resource on any Windows or Linux server.
Tom
Note that FTP only needs to be running on the i if you use it as the server. If you use it as the client, then FTP has to be running as a server on the PC.
Technically, a similar kind of situation is true for mapped drives. One side will act as a client for each connection; the other as a server. On the i, NetServer is either the client or the server as needed for Windows networking. (And the File host server is accessed by NetServer.) And on the PC for Windows, the Server service and possibly others need to be running — I’m not at all clear on all the possibilities there.
Tom