On Mon, 22 Dec 2008 15:22:51 -0600, Bob Bates <[email protected] m> wrote:
>I've come across something that has me a bit baffled. Using SENDFILE fn ft [email protected] ought to route the file to SMTP because of the . In the node, right? > >I believe it worked that way but can't seem to prove it. I know DEFAULTS SET SENDFILE SMTP fixes that. And it also knows to send it via RSCS is there isn't a dot. S o, shouldn't it work the other way? > >To be clear: > >SENDFILE MY FILE A [email protected] fails: Node ID not valid for RSC S >SENDFILE MY FILE A [email protected] (SMTP works >SENDFILE MY FILE A m...@rscsnode works > >DEFAULTS SET SENDFILE SMTP > >SENDFILE MY FILE A [email protected] works >SENDFILE MY FILE A m...@rscsnode works. > >You'd think I would need (RSCS on that last one since the default is SMT P. Can someone confirm this? This system is z/VM 5.4. I have a user that says all was good prior to the rollout a couple weeks ago. > >I also know there is a TCPEXIT that can be used if you want to change th e rules. We weren't using it that I can find. > >Bob Bates > >Enterprise Hosting Services > >w. (469)892-6660 >c. (214) 907-5071 I ran into this. I rather agree with you. IBM's answer was "that's the wa y it works". I think the reason given was backwards compatibility. I suppose if you had code depending in getting an error return from SENDF ILE before sending the file by some other path, then you wold not like it if the file starting b eing sent (and perhaps, subsequently rejected) when you installed a new release of CMS. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
