z/OS SMTP server

[Frank Swarbrick]

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.


I looked at the source code for the SMTPNOTE CLIST and see that even there the value is hardcoded. Do we just need to make this somehow configurable and make sure we configure it with the name of the LPAR the CICS is running in? Seems a bit of overkill.

Honestly, the whole requirement for a user application to actually specify SMTP commands seems to me to be more than a little crazy. 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:

220 ES05.firstbank.fb.ent2 Microsoft ESMTP MAIL Service ready at Tue, 2 Sep 2014 12:39:56 -0600
HELO
250 ES05.firstbank.fb.ent2 Hello [10.100.5.50]
whereas the z/OS SMTP server does require it. When not present the email is not sent and the SMTP log shows:
EZA5465E 09/02/14 12:48:53 Deleting Spool File from undetermined origin job number (JOB04887)


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).

Thanks,
Frank

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Skip Robinson]

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.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
***@sce.com



From: Frank Swarbrick <0000002782105f5c-dmarc-***@LISTSERV.UA.EDU>
To: IBM-***@LISTSERV.UA.EDU,
Date: 09/02/2014 12:15 PM
Subject: z/OS SMTP server
Sent by: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU>



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.


I looked at the source code for the SMTPNOTE CLIST and see that even there
the value is hardcoded. Do we just need to make this somehow configurable
and make sure we configure it with the name of the LPAR the CICS is
running in? Seems a bit of overkill.

Honestly, the whole requirement for a user application to actually specify
SMTP commands seems to me to be more than a little crazy. 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:

220 ES05.firstbank.fb.ent2 Microsoft ESMTP MAIL Service ready at Tue, 2
Sep 2014 12:39:56 -0600
HELO
250 ES05.firstbank.fb.ent2 Hello [10.100.5.50]
whereas the z/OS SMTP server does require it. When not present the email
is not sent and the SMTP log shows:
EZA5465E 09/02/14 12:48:53 Deleting Spool File from undetermined origin
job number (JOB04887)


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).

Thanks,
Frank


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Frank Swarbrick]

Can CICS query the &SYSNAME symbol? And is the "TCP Network Domain Name" always sourced from this symbol, or is it just "coincidental" that our LPAR name is the same (well, with the '.fb' suffixed) as the network domain name? According to the documentation of SMTPNOTE (found in TCP.SEZAINST) the "hostname" is "typically the NJE node name of this system."

Frank



________________________________
From: Skip Robinson <***@SCE.COM>
To: IBM-***@LISTSERV.UA.EDU
Sent: Tuesday, September 2, 2014 1:41 PM
Subject: Re: z/OS SMTP server


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.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
***@sce.com



From: Frank Swarbrick <0000002782105f5c-dmarc-***@LISTSERV.UA.EDU>
To: IBM-***@LISTSERV.UA.EDU,
Date: 09/02/2014 12:15 PM
Subject: z/OS SMTP server
Sent by: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU>




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.


I looked at the source code for the SMTPNOTE CLIST and see that even there
the value is hardcoded. Do we just need to make this somehow configurable
and make sure we configure it with the name of the LPAR the CICS is
running in? Seems a bit of overkill.

Honestly, the whole requirement for a user application to actually specify
SMTP commands seems to me to be more than a little crazy. 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:

220 ES05.firstbank.fb.ent2 Microsoft ESMTP MAIL Service ready at Tue, 2
Sep 2014 12:39:56 -0600
HELO
250 ES05.firstbank.fb.ent2 Hello [10.100.5.50]
whereas the z/OS SMTP server does require it. When not present the email
is not sent and the SMTP log shows:
EZA5465E 09/02/14 12:48:53 Deleting Spool File from undetermined origin
job number (JOB04887)


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).

Thanks,
Frank


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Frank Swarbrick]

Oh, and I guess SMTPNOTE is a REXX EXEC, not a CLIST. The docs call it a CLIST in several places (
Steps for customizing the SMTPNOTE CLIST (optional), etc.).



________________________________
From: Skip Robinson <***@SCE.COM>
To: IBM-***@LISTSERV.UA.EDU
Sent: Tuesday, September 2, 2014 1:41 PM
Subject: Re: z/OS SMTP server


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.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
***@sce.com



From: Frank Swarbrick <0000002782105f5c-dmarc-***@LISTSERV.UA.EDU>
To: IBM-***@LISTSERV.UA.EDU,
Date: 09/02/2014 12:15 PM
Subject: z/OS SMTP server
Sent by: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU>




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.


I looked at the source code for the SMTPNOTE CLIST and see that even there
the value is hardcoded. Do we just need to make this somehow configurable
and make sure we configure it with the name of the LPAR the CICS is
running in? Seems a bit of overkill.

Honestly, the whole requirement for a user application to actually specify
SMTP commands seems to me to be more than a little crazy. 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:

220 ES05.firstbank.fb.ent2 Microsoft ESMTP MAIL Service ready at Tue, 2
Sep 2014 12:39:56 -0600
HELO
250 ES05.firstbank.fb.ent2 Hello [10.100.5.50]
whereas the z/OS SMTP server does require it. When not present the email
is not sent and the SMTP log shows:
EZA5465E 09/02/14 12:48:53 Deleting Spool File from undetermined origin
job number (JOB04887)


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).

Thanks,
Frank


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Michael Klaeschen]

In our shop we have a started task called SMTP which is associated to a
JES output class. That started task's cataloged procedure calls
PGM=MVPMAIN with a CONFIG DD reading a certain statement for NJEDOMAIN. I
think this is the SMTP setup "not CSSMTP". You might check this in your
environment. I am pretty sure, your NJEDOMAIN reads ZOS. The interesting
point is *not* to set up an NJE node or even network (I think you can do
but that's another story). Here, the NJE domain name is used in the
default set of rewrite rules for the RFC822 header fields. For us this is
a good (or "correct") setup when for example we IEBGENER our memos to the
JES output class associated with SMTP. We just write "HELO ZOS" and our
SMTP started task will forward the correct way to our Lotus Domino service
including query of MX records and all that stuff.

Cheers
Michael






Von: Frank Swarbrick <0000002782105f5c-dmarc-***@LISTSERV.UA.EDU>
An: IBM-***@LISTSERV.UA.EDU
Datum: 2014-09-02 20:56
Betreff: z/OS SMTP server
Gesendet von: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU>



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.


I looked at the source code for the SMTPNOTE CLIST and see that even there
the value is hardcoded. Do we just need to make this somehow configurable
and make sure we configure it with the name of the LPAR the CICS is
running in? Seems a bit of overkill.

Honestly, the whole requirement for a user application to actually specify
SMTP commands seems to me to be more than a little crazy. 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:

220 ES05.firstbank.fb.ent2 Microsoft ESMTP MAIL Service ready at Tue, 2
Sep 2014 12:39:56 -0600
HELO
250 ES05.firstbank.fb.ent2 Hello [10.100.5.50]
whereas the z/OS SMTP server does require it. When not present the email
is not sent and the SMTP log shows:
EZA5465E 09/02/14 12:48:53 Deleting Spool File from undetermined origin
job number (JOB04887)


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).

Thanks,
Frank

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


Basler Sachversicherungs-AG
Amtsgericht Bad Homburg v.d.H., HRB 9357 | USt-ID-Nr. DE 276021973
Basler Straße 4, 61345 Bad Homburg v.d.H.
Vorstand: Jan De Meulder - Vorsitzender, Markus Jost, Dr. Jürg
Schiltknecht, Dr. Alexander Tourneau, Dr. Christoph Wetzel
Aufsichtsratsvorsitzender: Dr. Martin Strobel

Basler Lebensversicherungs-AG |
Amtsgericht Hamburg, HRB 4659 | Ust-ID-Nr. DE 276021973
Ludwig-Erhard-Straße 22, 20459 Hamburg
Vorstand: Jan De Meulder - Vorsitzender, Markus Jost, Dr. Jürg
Schiltknecht, Dr. Alexander Tourneau, Dr. Christoph Wetzel
Aufsichtsratsvorsitzender: Dr. Martin Strobel

Basler Versicherung AG Direktion für Deutschland |
Amtsgericht Bad Homburg v.d.H., HRB 1228 | USt-ID-Nr. DE 281452875
Basler Straße 4, 61345 Bad Homburg v.d.H.
Hauptbevollmächtigter für Deutschland: Jan De Meulder

Basler Leben AG Direktion für Deutschland |
Amtsgericht Bad Homburg v.d.H., HRB 1229 | Ust-ID-Nr. DE 281452875
Basler Straße 4, 61345 Bad Homburg v.d.H.
Hauptbevollmächtigter für Deutschland: Jan De Meulder

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Frank Swarbrick]

Actually our NJEDOMAIN reads "BITNET", which I assume is either the z/OS delivered default or was put there because that is the example given in the documentation. Doesn't like we even use NJE here, so I think the value of that particular parm is n/a.

Anyways, as I said, the emails are being forwarded with no problem to our (MS Exchange) email server. It's just vexing me that we get the warning messages.


For what its worth, here is the OUTPUT DD for this started task:


EZA5562I Resolver Usage YES Specified
EZA5355E GATEWAY specified but SMTPNJE DD card not found. NJE gateway
EZA5356E facility will not be enabled.
EZA5126I ====================================================================
EZA5125I IBM MVS SMTP CS V1R13 on Tue, 19 Aug 14 21:25:06 -0600
EZA5127I Jobname of SMTP Server : SMTP
EZA5128I TCP Network Domain Name : ZOSD.fb
EZA5129I Gateway TCP Network to NJE : Yes
EZA5130I NJE Network Node Name : ZOSD
EZA5131I NJE Domain Name : BITNET
EZA5133I Local Delivery Format : Netdata
EZA5189I Local Output Class : B
EZA5134I NJE Delivery Format : Punch
EZA5190I NJE Output Class : B
EZA5136I PostMaster Address : <***@ZOSD.fb>
EZA5137I Userid for Bad Spool Files : SPRCC
EZA5317I Listen on Address : Unspecified
EZA5139I Port for Server SMTP : 25
EZA5191I REMOTEPORT for SMTP client : 25
EZA5140I Inactivity Timeout : 180 seconds
EZA5141I Finish Open Timeout : 120 seconds
EZA5142I Retry down sites every : 20 minutes
EZA5143I Return mail older than : 3 days
EZA5265I Warn about mail older than : 1 days
EZA5144I Max Length of Accepted Mail : 524288 bytes
EZA5648I MaxMsgSent : 0
EZA5236I Max Temporary Error Retries : Disabled
EZA5225I Resolver Tracing : Disabled
EZA5228I Name Resolution Method : Nameserver, Port 53
EZA5231I Nameserver Address(.1.) : 10.1.104.11
EZA5231I Nameserver Address(.2.) : 10.1.104.18
EZA5232I Nameserver Response Timeout : 1 seconds
EZA5233I Resolver Retry Interval : 20 minutes
EZA5234I UDP Retries/Nameserver/Interval: 4
EZA5235I RCPT TO: response delay : 60 seconds
EZA5145I Translate Table : TCPIP.STANDARD.TCPXLBIN
EZA5263I DBCS Conversion : Disabled
EZA5175I Mail Logging : Yes
EZA5179I Debugging Enabled : No
EZA5319I Outbound Open Session Limit : None
EZA5388I InboundOpenLimit : 0
EZA5322I SMSG Authorization List : Processed
EZA5272I Deliver via Mailer : None
EZA5645I IP Mailer Name : MAIL.FB ALL
EZA5186I Mail File Dataset Prefix : SYS5.ZOSD.
EZA5187I Mail File Unit Name : SYSDA
EZA5183I Spool Poll Interval : 30 Seconds
EZA5569I No Source Routing : Disabled
EZA5573I RcptReply452 Active : No
EZA5574I SMTP ExitDirection : Inbound
EZA5471I DeleteBadSpoolFile : No
EZA5209I Local Time Zone : SYSTZ
EZA5390I STOPONRENF : Inactive
EZA5260I Rewrite 822 Mail Headers : Enabled. Using default rules

I'm curious what you see in your SMTP.OUTPUT and your SMTP.LOGFILE (assuming you have LOG set).

Frank




________________________________
From: Michael Klaeschen <***@BASLER.DE>
To: IBM-***@LISTSERV.UA.EDU
Sent: Tuesday, September 2, 2014 1:49 PM
Subject: Re: z/OS SMTP server


In our shop we have a started task called SMTP which is associated to a
JES output class. That started task's cataloged procedure calls
PGM=MVPMAIN with a CONFIG DD reading a certain statement for NJEDOMAIN. I
think this is the SMTP setup "not CSSMTP". You might check this in your
environment. I am pretty sure, your NJEDOMAIN reads ZOS. The interesting
point is *not* to set up an NJE node or even network (I think you can do
but that's another story). Here, the NJE domain name is used in the
default set of rewrite rules for the RFC822 header fields. For us this is
a good (or "correct") setup when for example we IEBGENER our memos to the
JES output class associated with SMTP. We just write "HELO ZOS" and our
SMTP started task will forward the correct way to our Lotus Domino service
including query of MX records and all that stuff.

Cheers
Michael






Von: Frank Swarbrick <0000002782105f5c-dmarc-***@LISTSERV.UA.EDU>
An: IBM-***@LISTSERV.UA.EDU
Datum: 2014-09-02 20:56
Betreff: z/OS SMTP server
Gesendet von: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU>




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.


I looked at the source code for the SMTPNOTE CLIST and see that even there
the value is hardcoded. Do we just need to make this somehow configurable
and make sure we configure it with the name of the LPAR the CICS is
running in? Seems a bit of overkill.

Honestly, the whole requirement for a user application to actually specify
SMTP commands seems to me to be more than a little crazy. 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:

220 ES05.firstbank.fb.ent2 Microsoft ESMTP MAIL Service ready at Tue, 2
Sep 2014 12:39:56 -0600
HELO
250 ES05.firstbank.fb.ent2 Hello [10.100.5.50]
whereas the z/OS SMTP server does require it. When not present the email
is not sent and the SMTP log shows:
EZA5465E 09/02/14 12:48:53 Deleting Spool File from undetermined origin
job number (JOB04887)


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).

Thanks,
Frank

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


Basler Sachversicherungs-AG
Amtsgericht Bad Homburg v.d.H., HRB 9357 | USt-ID-Nr. DE 276021973
Basler Straße 4, 61345 Bad Homburg v.d.H.
Vorstand: Jan De Meulder - Vorsitzender, Markus Jost, Dr. Jürg
Schiltknecht, Dr. Alexander Tourneau, Dr. Christoph Wetzel
Aufsichtsratsvorsitzender: Dr. Martin Strobel

Basler Lebensversicherungs-AG |
Amtsgericht Hamburg, HRB 4659 | Ust-ID-Nr. DE 276021973
Ludwig-Erhard-Straße 22, 20459 Hamburg
Vorstand: Jan De Meulder - Vorsitzender, Markus Jost, Dr. Jürg
Schiltknecht, Dr. Alexander Tourneau, Dr. Christoph Wetzel
Aufsichtsratsvorsitzender: Dr. Martin Strobel

Basler Versicherung AG Direktion für Deutschland |
Amtsgericht Bad Homburg v.d.H., HRB 1228 | USt-ID-Nr. DE 281452875
Basler Straße 4, 61345 Bad Homburg v.d.H.
Hauptbevollmächtigter für Deutschland: Jan De Meulder

Basler Leben AG Direktion für Deutschland |
Amtsgericht Bad Homburg v.d.H., HRB 1229 | Ust-ID-Nr. DE 281452875
Basler Straße 4, 61345 Bad Homburg v.d.H.
Hauptbevollmächtigter für Deutschland: Jan De Meulder

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Paul Gilmartin]

Post by Skip Robinson
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:

***@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.

Post by Skip Robinson
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
EZA5460I 09/02/14 09:01:24 BSMTP Helo Domain: ZOS I've never heard of you!
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?

Post by Skip Robinson
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".

Post by Skip Robinson
... 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ed Gould]

Post by Paul Gilmartin
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.

Gil:

SMFID has a 4 character name restriction, AFAIK its been there since
MVT.

Ed

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Skip Robinson]

SMFID is <= 4 characters and is independent of SYSNAME, which is <= 8
characters. They may be set the same by the installation. MVSVAR(SYSNAME)
returns the LPAR name.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
***@sce.com



From: Ed Gould <***@COMCAST.NET>
To: IBM-***@LISTSERV.UA.EDU,
Date: 09/02/2014 02:04 PM
Subject: Re: z/OS SMTP server

Post by Paul Gilmartin
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.

Gil:

SMFID has a 4 character name restriction, AFAIK its been there since
MVT.

Ed

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[John McKown]

Post by Skip Robinson
SMFID is <= 4 characters and is independent of SYSNAME, which is <= 8
characters. They may be set the same by the installation. MVSVAR(SYSNAME)
returns the LPAR name.

Not really the LPAR name. That name is defined in the IOCDS at the
hardware level. The MVSVAR can return: (1) the SYSSMFID which is <= 4
characters in length and defined in the SMFPRMxx member of PARMLIB;
(2) the SYSNAME which is defined in the IEASYSnn member of PARMLIB and
is normally used to specify the system name in a sysplex and in DFP
SMS constructs. The LPAR name does not appear to be available using
TSO REXX. You can see it in the output of the z/OS operator command: D
M=CPU . It is >=1 & <= 8 just like the SYSNAME, but need not have the
same value. This value can be gotten via the CSRSI macro in HLASM or
the CSRSI callable service in an HLL. At my shop, we set all 3 to the
same value.

Post by Skip Robinson
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile

--
There is nothing more pleasant than traveling and meeting new people!
Genghis Khan

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Skip Robinson]

Right, LPAR name is not automatically set in a static symbol. I guess in
nearly 20 years of sysplex we've never needed Rexx access to that name.
However, it would be a simple matter to set an installation symbol like
this in IEASYMxx:

SYSDEF LPARNAME(lpar-name) /* For this LPAR */

SYMDEF(pppLPAR=lpar-name) /* Set installation symbol */

where 'lpar-name' is the name of an LPAR

and 'ppp' (optional) is an installation-specific prefix used in all
locally defined symbols. I recommend using the SHARE installation code
here.

There would be one pair of such statements for each LPAR that shares
IEASYMxx. In a Rexx, MVSVAR(pppLPAR) would return the name of the current
LPAR.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
***@sce.com



From: John McKown <***@GMAIL.COM>
To: IBM-***@LISTSERV.UA.EDU,
Date: 09/02/2014 03:27 PM
Subject: Re: z/OS SMTP server

Post by Skip Robinson
SMFID is <= 4 characters and is independent of SYSNAME, which is <= 8
characters. They may be set the same by the installation.

MVSVAR(SYSNAME)

Post by Skip Robinson
returns the LPAR name.

Not really the LPAR name. That name is defined in the IOCDS at the
hardware level. The MVSVAR can return: (1) the SYSSMFID which is <= 4
characters in length and defined in the SMFPRMxx member of PARMLIB;
(2) the SYSNAME which is defined in the IEASYSnn member of PARMLIB and
is normally used to specify the system name in a sysplex and in DFP
SMS constructs. The LPAR name does not appear to be available using
TSO REXX. You can see it in the output of the z/OS operator command: D
M=CPU . It is >=1 & <= 8 just like the SYSNAME, but need not have the
same value. This value can be gotten via the CSRSI macro in HLASM or
the CSRSI callable service in an HLL. At my shop, we set all 3 to the
same value.

Post by Skip Robinson
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile

--
There is nothing more pleasant than traveling and meeting new people!
Genghis Khan

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Jon Perryman]

HELO is used to reduce spam. It wants to validate the domain name. In this case, zos is not defined in your DNS or it does not match the IP address of the SMTP client. If you on the same system, then 127.0.0.1 may be sufficient. If however you connect from different systems, then you may need DNS names unique for each client system. It could be any name that you desire as long as your exec can obtain it (e.g. sysname, lpar name, a system variable or ???). As you see, your SMTP ignores this error so anyone could potentially send spam thru this SMTP.

Jon Perryman.

Post by Frank Swarbrick
EZA5460I 09/02/14 09:01:24 BSMTP Helo Domain: ZOS I've never heard of you!
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.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Mike Stayton]

The HELO SMTP command is following the syntax as described in RFC 821.
HELO <SP> <domain> <CRLF>

domain is a required parameter. For the z/OS SMTP server it can be any string. The string itself is ignored by the server. A possible use is to identify the z/OS LPAR that created the mail message.

Since this is a CICS task creating the mail message, the CICS SOCKET API could be used to obtain the host name. Use the gethostname() function. Use the socket() function to obtain a socket, call the gethostname() function and call the close() function to close the socket.

Or use the SMFID, the system name from the CVTSNAME field, or the CICS system name.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Frank Swarbrick]

Where do you find the quote that is your second paragraph? Because it does seem to, at least slightly, care what the value of the string is and that it matches the domain as known my the SMTP server.


Where does SMTP retrieve its domain from? Does it also use gethostname()?



________________________________
From: Mike Stayton <***@POBOX.COM>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, September 3, 2014 5:42 AM
Subject: Re: z/OS SMTP server


The HELO SMTP command is following the syntax as described in RFC 821.
HELO <SP> <domain> <CRLF>

domain is a required parameter. For the z/OS SMTP server it can be any string. The string itself is ignored by the server. A possible use is to identify the z/OS LPAR that created the mail message.

Since this is a CICS task creating the mail message, the CICS SOCKET API could be used to obtain the host name. Use the gethostname() function. Use the socket() function to obtain a socket, call the gethostname() function and call the close() function to close the socket.

Or use the SMFID, the system name from the CVTSNAME field, or the CICS system name.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Paul Gilmartin]

... As you see, your SMTP ignores this error so anyone could potentially send spam thru this SMTP.

"[A]nyone" who can CONNECT via TCP/IP to port 25 of your system. In most
cases a firewall will prevent this.

Note that this applies to a TCP/IP connection to SMTP. Most z/OS users are
more familiar with the BSMTP protocol using the spool, which is less likely to
be widely exposed.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN