|
Client Access File Transfer must be initiated from the client. You should be able to set up a remote command in Client Access as well. The remote command could initiate your CPYSPLF. You could batch this on the PC with the file transfer command using WinBatch or something like it. You could set up the batch on the Windows scheduler if you have it running. Maintaining a Client Access overnight can be problematic, but it's all do-able. If you configure a shared IFS directory in Netserver you can: CPYSPLF to a data file. CPYTOSTMF or CPYTOIMPF from the data file to a text file in the IFS directory, specifying *PCASCII for the code page. The people on the PC side can access the IFS directory directly from their PC's on the network. The two AS/400 CPY statements can be put in a CL and scheduled. The users may access the text file from the share about as easily as if it were on their C: drives. -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@xxxxxxxxxxxxxxxxx> -----Original Message----- From: Bob Kohlndorfer [mailto:kohlnbob@xxxxxxxxxx] Sent: Friday, October 24, 2003 4:56 AM To: Midrange Systems Technical Discussion Subject: Getting Data from iSeries to PC Hello, I have been given the task of getting the data from spool files on the iSeries to PC's. I have used CPYSPLF to turn the spool file into a data file. Then I have been able to use Client Access File Transfer utility to bring it down to a PC. I have saved the .TTO file of the file transfer and can run that to download the file. I would like to automate the process so that it could run either when the people on the PC side want to run it or when the someone on the iSeries side decides it is time to download. That is I am not sure which side will initiate the download of the file to the PC. Any ideas on how I can accomplish these tasks? Thanks in advance, Bob
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.