Yes - write your FTP commands in a file. 'FILEDEF INPUT DISK CP3K FTPINPUT A'
'PIPE (name CP3K.EXEC:10)', '|command FTP 10.6.0.10 (EXIT', /* go get a directory listing */ '| inside /150/ /226/ ', '| stem ftpfile.' On Wed, Dec 1, 2010 at 1:09 PM, Paul Gilmartin <[email protected]> wrote: > Well, I converted my 1000+ line exec to a stage. Mostly changing > its filetype and saving the initial subcommand environment name > to use later. ("STAGE = address()" works; "PARSE SOURCE" doesn't.) > Some "PIPE" commands become "CALLPIPE", but it remains mostly > procedural. It will evolve. > > One early change I made was from a technique of logging to a file > and doing a SENDFILE NOTE SMTP at the end. That's now a stage > invoked by ADDPIPE, lines added by OUTPUT, so if the main stage > crashes I still get a report. > > But I also invoke an old FTP stage, now with CALLPIPE. But is there > any way to pass commands to FTP other than queueing them on the > console stack? I'd love to do "callpipe stem COMMANDS. | COMMAND FTP", > but, alas, that's not how COMMAND works. I'm afraid of the stack. > too many programmers don't match their pushes and their pops, and other > programmers adopt DESBUF as an aggressive defense. > > If each Rexx stage has a private stack, I'm home free, but I fear > that isn't so, is it? If two concurrent stages attempt to use the > same stack asynchronously disaster is guaranteed. > > Any suggestions? I don't know of a builtin FTP stage. > > Thanks, > gil > -- Mark D Pace Senior Systems Engineer Mainline Information Systems
