Thanks for the suggestions, I'll give OCOPY or IEBGENER a try. I originally chose cp for convenience of the developers. They are replacing ftp steps with sftp steps in their batch jobs. I wanted to keep it at 'replace STEP A' with STEP B. So with the constraints of BPXBATCH being able to only execute one command, I created small scripts with a cp command to copy the file then sftp or scp to send the file to the remote system. I'll need to be able to call OCOPY or IEBGENER from such a script.
On Tue, 7 Apr 2015 20:21:33 +0000, Barkow, Eileen <[email protected]> wrote: Why can't you use OCOPY to copy the file instead of cp? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
