Better than the stack, invoke FTP using the VMFTP package. The VMFTP
package can be obtained from:
Fran Hensler's excellent Slippery Rock University FTP site with
the most recent updates as of 2009-03-13 at:
http://zvm.sru.edu/~DOWNLOAD/
VMFTP macros are(written in rexx code with filetype "VMFTP", permitting
you to fully automate pretty much anything and everything in FTP. You get
to examine the full message and return code from every returned line.
Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's.
"Paul Gilmartin" <[email protected]>
Sent by: "CMSTSO Pipelines Discussion List" <[email protected]>
12/01/2010 12:09 PM
Please respond to
"CMSTSO Pipelines Discussion List" <[email protected]>
To
[email protected]
cc
Subject
FTP and the dreaded console stack
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
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal policies
and to protect our business. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
