|
View previous topic :: View next topic
|
| Author |
Message |
Kaliragavendran
New User
Joined: 04 Sep 2019
Posts: 3
Location: India
|
|
|
|
Hi
Can someone help me on how to send email without smtp...
I have using smtp for all our projects..but i have client and they dont have smtp or SAS to send email from mainframe to external ..
Thanks |
|
| Back to top |
|
 |
hankoerlemans
New User
Joined: 25 Jan 2018
Posts: 55
Location: Australia
|
|
|
|
Do you have connectivity from your z-system to an internal mail relay ?
If so you have basic SMTP using the JES2 spool to route to a relay.
Look at the z/OS Communications Server manuals |
|
| Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| I think you also need z/OS 2.4 (which most shops do not have running in production yet) for this and you also need to setup JES2 to talk to TCPIP, which is non trivial. |
|
| Back to top |
|
|
hankoerlemans
New User
Joined: 25 Jan 2018
Posts: 55
Location: Australia
|
|
|
|
RTFM buddy. There isn't a TCPIP connection from JES at all.
I have been using the clunky SMTP relay to send email via JES2 for years.
Ever since it was made available back whenever.... |
|
| Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| I'll be the first to admit I'm not real current on JES2. However, note that Kaliragavendran does not want even the basic rather clunky SMTP, which means the JES2 hack to ship something to SMTP (about which I know nothing) will not work, which brings us back to z/OS 2.4 and configuring JES2 to talk to TCPIP. |
|
| Back to top |
|
|
hankoerlemans
New User
Joined: 25 Jan 2018
Posts: 55
Location: Australia
|
|
|
|
Are you referring to the discussion elsewhere about sockets ?
At great expense to the management ....... 
My system is z/OS 2.3 . I did this on 2.1 as well although some of the specifics have changed over time. Moved the code into USS for one thing.
See SEZAINST(CSSMTP) for the STC JCL.
Some bits from the cssmtp.conf file
| Code: |
# ------------------------------------------------------
# The ExtWrtName statement specifies the external writer name used by
# the CSSMTP application for selection criteria when interfacing with
# the JES2 or JES3 subsystems.
ExtWrtName SMTP # the external writer name
TargetServer
{
TargetIp my.site.smtp.relay # target ip address
}
|
my.site.smtp.relay needs to be pingable from the z-box.
And of course there can't be other mysterious blockers on your relays which I know nothing about.
then
| Code: |
/*REXX*/
trace r
domfr = 'hcl.com'
domto = 'gmail.com'
noden = 'nodename' /* See your jes config deck for the value */
mailfr = 'mywork.email' || '@' || domfr
mailto = 'myprivate.email' || '@' || domto
/* Issue SMTP message via SMTP batch interface */
queue "helo "domfrm
queue "mail from:<"mailfr">"
queue "rcpt to:<"mailto">"
queue "data"
queue "Date: " || date('N') || " " || time('C')
queue "From:<"mailfr">"
queue "To:<"mailto">"
queue "Subject: Batch job has abended"
queue " "
queue "If you set up the text properly for this message"
queue "then you can use this code as a FA notify exit"
queue " "
queue "Regards Hank Oerlemans, FA Support"
queue "."
queue ""
"ALLOC DD(DD1) SYSOUT(B) DEST("noden".SMTP)" /* SMTP needs to match the wtr name in the .conf file */
address mvs "EXECIO * DISKW DD1 (FINIS"
"FREE DD(DD1)"
exit
|
No socket programming at all.
You can just write boring report files in the language of your choice. |
|
| Back to top |
|
|
|
|
