On Tue, 2 Sep 2014 12:41:40 -0700, Skip Robinson wrote:
>Is this guy really a 'CLIST'? I haven't used CLIST for so long that I
>don't know all the modern capabilities. LPAR name is set in standard
>system symbol &SYSNAME. Rexx can certainly obtain the symbol. If the
>symbol is available, the code needs to be modified once to work in all
>environments.
>
And, of course, they may differ:
user@HOST: ping $(rexx "say mvsvar(sysname)")
EZZ3111I Unknown host 'MVS3'
Sysadmin territorial dispute: LPAR name is 4 characters (is this a SMF
restriction?)
and our nework administrators enforce their own incompatible conventions.
>
>From: Frank Swarbrick
>Date: 09/02/2014 12:15 PM
>
>I am writing a simple CICS application to use the EXEC CICS SPOOLxxxx
>commands to write data to JES to be used by z/OS SMTP (not CSSMTP which we
>do not have running). My question is simple, but perhaps the answer is
>not. The question is, what is the best way to get the correct "domain
>name" to be used in the SMTP HELO command?
>
>We have quite a few batch processes that use the z/OS SMTP server to send
>email. All of them appear to just have coded "HELO ZOS". While this
>works, it also is not technically "correct" because "ZOS" is not in fact
>the "domain name". Rather, in our DEV LPAR it should be "zosd.fb" and in
>production "prd1.fb". So we have a lot of the following the the SMTP
>LOGFILE DD:
>EZA5460I 09/02/14 09:01:24 BSMTP Helo Domain: ZOS I've never heard of you!
>rather than the more desirable:
>EZA5460I 09/02/14 12:23:11 BSMTP Helo Domain: zosd.fb Yours too, I see!
>
>SMTP doesn't seem to really care. Other than the message above it still
>works no matter if you supply the "correct" domain or not.
>
There may be a security motive to validate it. It might be fussier if
you make a socket connection to port 25, especially from a different
system. What happens if you route your SYSOUT to an SMTP server
on a different system?
>Honestly, the whole requirement for a user application to actually specify
>SMTP commands seems to me to be more than a little crazy.
>
You can write a macro for that. In fact, they have, haven' t they?
XMITIP, FSVO "they".
>... And in any
>case, the requirement for specifying "who I am" on the HELO is even odder.
> Especially since (for example) the Microsoft Exchange SMTP server doesn't
>even require it: ...
>
>Perhaps in the end I'll just use "HELO ZOS" just like every other email
>job we have. But I like to have things as "correct" as possible (when
>possible and not a huge amount of extra work).
>
SMTP servers are apt to kindly fill in a lot of blanks. I routinely omit
"Date:", perhaps even "From:", and let the server supply them.
(Mostly from z/VM or Solaris.)
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
