Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace z/OS
Created by Guest
Created on Mar 8, 2017

TLS Failure Message Enhancements :: System SSL error code added to all TLS handsahke/authentication failure messages

Currently when an FTP fails we get a cryptic message such as the following in the FTP server
ID=FTPSEC100168 SECURE fails Reason=4 Text=The TLS handshake failed

or in a client connection

EZY2640I Using dd:SYSFTPD=SYS5.TCPIP.PUBLIC(CFTPSEC) for local site configuration parameters.
EZA1450I IBM FTP CS V2R1
EZA1456I Connect to ?
EZA1736I AMVS.MF.JPMCHASE.NET 921
EZA1554I Connecting to: AMVS.mf.jpmchase.net 169.116.55.11 port: 921.
220-FTPSEC1 IBM FTP CS V2R1 at AMVS.mf.jpmchase.net, 15:57:14 on 2017-03-07.
220 Connection will close if idle for more than 30 minutes.
EZA2897I Authentication negotiation failed
EZA2898I Unable to successfully negotiate required authentication
EZA1701I >>> QUIT
221 Quit command received. Goodbye.


Now these messages lack the SYSTEM SSL code that you only see if you have debug turned on. So I'm proposing that the SYSTEM SSL error code be added to all TLS authentication fail type messages that are posted to speed up debugging issues

Idea priority High
  • Guest
    Reply
    |
    Apr 8, 2022
    We are no longer enhancing FTP's native usage of System SSL. Based on our discussion on 4/6/2022, we learned that the customer has already converted over from native use of System SSL to AT-TLS, which is the recommended direction.
  • Guest
    Reply
    |
    Oct 30, 2020

    This item is not in our plans but is being kept in our backlog.