We use other JES2 batch to EMAIL products, JES2MAIL IIRC, J2JOE, but if
you want to use the;
//NFT NOTIFY EMAIL='[email protected]'
JES2 statement I think you need JES2EDS ?
correct me if I am mistaken
Carmen
On 1/18/2022 10:40 AM, Mark Regan wrote:
You should look at using Lionel Dyck's XMITIP REXX program. You can get it
directly from his site, athttps://www.lbdsoftware.com, or at CBT Tape, at
https://www.cbttape.org, file 314.
Regards,
Mark Regan, K8MTR General, EN80tg
CTO1 USNR-Retired (1969-1991)
Nationwide Insurance, Retired, 1986-2017
z/OS Network Software Consultant (z NetView, z/OS Communications Server)
Contractor, Checks & Balances, Inc.
Email:[email protected]
LinkedIn:https://www.linkedin.com/in/mark-t-regan
On Sun, Jan 16, 2022 at 8:18 AM Mike Shorkend<[email protected]>
wrote:
Hi,
I am trying to set up email notification for job termination but have run
into a problem that the JES2EDS started task can't connect to z/OSMF. This
is the joblog(I have had to obfuscate the URI and NODE)
J E S 2 J O B L O G -- S Y S T E M S Y S D -- N O
D E N O D E 1
1.25.31 S0452379 ---- SUNDAY, 16 JAN 2022 ----
1.25.31 S0452379 IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00001
1.25.31 S0452379 IEF196I IGD104I SYS3.TCPIP.TCPPARMS
RETAINED,
1.25.31 S0452379 IEF196I DDNAME=SYS00001
1.25.31 S0452379 IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00005
1.25.31 S0452379 IEF196I IGD104I SYS3.TCPIP.TCPPARMS
RETAINED,
1.25.31 S0452379 IEF196I DDNAME=SYS00005
1.25.31 S0452379 IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00007
1.25.31 S0452379 IEF196I IGD104I SYS3.PLX2.TCPIP.STANDARD.TCPXLBIN
RETAINED,
1.25.31 S0452379 IEF196I DDNAME=SYS00007
1.25.31 S0452379 IEF196I IGD103I SMS UNIX FILE ALLOCATED TO DDNAME
SYS00011
1.25.31 S0452379 IEF196I IGD104I UNIX FILE WAS RETAINED, DDNAME IS
(SYS00011)
1.25.31 S0452379 IEF196I FILENAME IS (/etc/hosts)
1.25.32 S0452379 $HASP1529 106 0420 Socket closed by remote partner
1.25.32 S0452379 $HASP1534 z/OSMF server URI
https://host.domain.co.il:1443/zosmf
1.25.32 S0452379 $HASP1535 Current message is in email queue $EDSQ004 at
offset 0000
918 in EMQT 02000088FF01
1.25.32 S0452379 *$HASP1523 Unable to connect to z/OSMF server.
If I plugin the URI to a browser, I connect to z/OMSF without a problem.
$HASP1529 sends you to the HTTP toolkit where a 106 return code is:
Meaning: A communication error has been detected. One or
more of the following problems has occurred:
• A failure in the communication with the web server
• An error in an underlying sockets or SSL/TLS service call
• An error in obtaining the necessary system resources to
process the connect.
Action: Check the diagArea for further diagnostic information.
The toolkit uses many internal services, including sockets, SSL,
and other calls when processing an HTTP API service call. If one
of these internal services fails because of an error in
communications with the targeted server or because of an
internal environmental condition, the error is reported in the
diagnostic area. This information can be useful to the
application programmer but, in many cases, it is for the use of
IBM Support. If one of these errors occurs, clean up the
environment, check for possible communication configuration
problems, and reissue the request
Before opening a case with IBM, has anyone else run into this (and
hopefully solved it)?
z/OS 2.4 and I think that I have followed all the prereq tasks.
Thanks
Mike
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email [email protected] with the message: INFO IBM-MAIN
--
/I am not bound to win, but I am bound to be true. I am not bound to
succeed, but I am bound to live by the light that I have. I must stand
with anybody that stands right, and stand with him while he is right,
and part with him when he goes wrong. *Abraham Lincoln*/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
