.
Thanks again,
Jerry
-Original Message-
From: Edgington, Jerry
Sent: Monday, November 16, 2020 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: RE: Need some help with SSL error
We have tracing in AT/TLS turned on, but nothing in the trace for these
connections. So, I don't belie
56968 EZBTTRCV
I am looking to trace to TCPIP for that specific IP address.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Edgington, Jerry
Sent: Monday, November 16, 2020 9:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Need some help with SSL
UA.EDU
Subject: Re: Need some help with SSL error
This message was sent from an external source outside of Western & Southern's
network. Do not click links or open attachments unless you recognize the sende
Did you get any messages from AT-TLS (prefix EZY) ?. Trace level 7 should
cause error messages to appear on the job log in addition to the unix syslog.
Maybe the rule is not being triggered. If you are able to increase the trace
level to 31 you should be able to see what System SSL options were
AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Need some help with SSL error
AT/TLS config:
TcpImage TCPIP /etc/pagent.conf FLUSH PURGE
##LogLevel 31 ## Default logging level.
##LogLeve
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Joe
Monk
Sent: Monday, November 16, 2020 8:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Need some help with SSL error
This
Sorry ... my email client cut off the ATTLS parms and I didnt see them.
Joe
On Mon, Nov 16, 2020 at 7:06 AM Joe Monk wrote:
> Error 100B:
>
> 100B Unexpected SSL handshake encountered.An SSL handshake header was
> encountered on a basic port or the client immediately entered an SSL
> handshake
Error 100B:
100B Unexpected SSL handshake encountered.An SSL handshake header was
encountered on a basic port or the client immediately entered an SSL
handshake for a CONNTYPE option value other than SECURE or ANY. Verify that
the client and port settings are compatible.
A quick google found this:
I need some help, please. We have an automated system, using TN3270 screen
scraping. Over the weekend, we IPL'ed, first time in April, 2020 and now, when
this "automated" system/client tries to connect over TN3270, we are getting
this error message:
M 410 20320 14:22:03.02 STC096
