Looking for relevant Networking Whitepapers? Visit the SearchNetworking.com Research Library.
Gilly400 | Jun 11 2008 2:23PM GMT
Hi,
I would suggest using a sort of “trigger file” to indicate that there is a file to be processed. You FTP your file to your non-secured folder, then FTP the trigger file to indicate that there’s a file to be processed. On a machine which has access to both the secured and non-secured folders you have a job running which waits for the trigger file to appear and once the trigger file is there, moves your file from the non-secured folder to the secured folder and removes the trigger file.
The use of the trigger file ensures that your job to move the file doesn’t try to move the file while it’s still being written to the folder.
Regards,
Martin Gilbert.
Looks like you have two things going on here..
1. FTP the file to an FTP server..
2. Copy the file from the FTP server to something no so FTP friendly..
Martin’s suggestions for setting up the script is fine, and the trigger file idea is OK, but you can also try running a “remote command” in the FTP script.
Try it manually first - from an iSeries command line type FTP [servername] and then log in with the proper ID and password. Then type HELP QUOTE and see what it tells you. The FTP “QUOTE” command should allow you to run a system command on a remote system - assuming the remote system supports it. You can also type HELP SERVER and get a list of commands the server supports.
I believe you should be able use the QUOTE command to include a line in your script after the PUT to run a batch file to handle the copy to the “secured” directory..
Another alternative is forget the FTP altogether. Use CPYTOSTMF to drop the file onto an IFS directory and then have your “secure” system pull the file from there..
Regards
Mike