To establish SSL/TLS communication between two systems the systems
negotiate to determine the most secure cipher and protocol that is
supported and allowed on both systems. If that negotiation fails, it is
usually because the SSL/TLS support on one of the systems is seriously
down level from
https://www.ibm.com/docs/en/zos/2.4.0?topic=messages-ezd1285i
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Crusty Old Guy
Sent: Friday, December 9, 2022 8:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Interpreting SEND/RECV
Right, definitely bad practice. How do they fall back? New name is
the only way to go.
On 12/9/2022 9:16 AM, Mark Jacobs wrote:
At $currentjob whenever an XCF policy is changed and stored in the couple
dataset their standard practice is to replace the current active policy using
the same
Can you tell us a bit more about the environment? So far you're mostly
saying "Something didn't work."
Is there any AT-TLS involved?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Not 100% sure, but I believe that is the data being sent to the remote side
encrypted. If I'm right then depending when it is being sent, could be a
userid, password, command, or if on the data connection data from the file
being transferred.
