× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks for the reply Bradley
I agree - the RC of zero made me furrow my forehead as well

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
‘If you're going through hell, keep going.’
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of B Stone
Sent: Wednesday, October 16, 2019 9:10 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: How can I tell if our transmissins are using TLS 1.2

RC shouldn't be zero if there was an error. It should be -10 I bet. The errno (3426) usually with an -10 RC indicates that you are correct in thinking TLS 1.2 isn't set up properly.

This may help to check:
https://developer.ibm.com/articles/i-system-ssl-ibmi/

That may be out of date but if you google set up tls 1.2 ibm I you should find more info.

I would look at that and do some testing. I would also contact your software vendor and ask them if there is a bug in their error reporting.



Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #15 <https://www.bvstools.com/mailtool.html>: The ability to add a Footer to each email sent using an IFS stream file.

On Wed, Oct 16, 2019 at 7:54 AM Alan Shore via MIDRANGE-L < midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi everyone
Are you sitting comfortably
Then I will begin
We "moved" to TLS 1.2 quite a few months ago Last June, ups required
us to send our manifest transmissions to a new end point One that
would ONLY accept transmissions using TLS 1.2 This past weekend we
performed an ipl No updates Just an ipl, followed by a number of file
RGZPFM's Since Monday, we are unable to successfully transmit to the
new end point The job log shows the message
3426 SSL_Handshake failed█ with RC code 0

I tried googling
3426 SSL_Handshake failed
But didn't find anything
I am waiting to hear from someone at ups, but it occurred to me Are we
no longer transmitting using TLS 1.2?
We are on V7r3
Does anyone know how I can tell if we are transmitting using TLS 1.2?


Alan Shore
E-mail : ASHORE@xxxxxxxx<mailto:ASHORE@xxxxxxxx>
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.