Is there a cert you need to add to jes2 userid keychain?
Dave Jousma Vice President | Director, Technology Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429<tel:+16166538429> ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Mike Shorkend <[email protected]> Sent: Sunday, January 16, 2022 8:17:40 AM To: [email protected] <[email protected]> Subject: JES2 mail notification **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
