IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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.

Add a new idea Subscribe
Status Delivered
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Jul 18, 2012

RELATED IDEAS

Tolerate spaces in SSL certificate name

When using SSL security in CICS, unless you have a default certificate on the KEYRING a certificate must be specified. There is no error at define time if the certificate name contains spaces, but when attempting to install the TCPIP Service CICS issues an error stating "Install of TCPIPSERVICE [name] failed because CERTIFICATE [cert name] is invalid."


CICS is one of the few applications our company has come across that does not support the use of spaces in the certificate name. When creating a certificate in CICS currently the name would have to be something like, "CICS-SSL-Certificate-Example". It would be better, so we can standardize naming across all platforms and applications, to be able to use an SSL certificate name of something like, "CICS SSL Certificate Example".

This limitation is also true and applicable for the TCPIPSSLCERT parameter used for the CICS web user interface allowing for secure connections from the web user interface and the CICS Explorer.

Idea priority Low
  • Guest
    Reply
    |     Jun 16, 2017

    This RFE is satisfied by CICS TS 5.4 which is generally available from today June 16th 2017.
    For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113

  • Guest
    Reply
    |     May 16, 2017

    This RFE is satisfied by CICS TS 5.4 which was announced on May 16th 2017 with a planned general availability date of June 16th 2017.
    For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113

  • Guest
    Reply
    |     Jan 8, 2016

    This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

  • Guest
    Reply
    |     Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |     Jul 25, 2014

    We are currently running CICS v5.1. This issue happens when there is a keyring with no default certificate and the certificate name must be specified in the WUIPARM member in the SEYUPARM dataset. For the TCPIPSSLCERT parameter we are able to use a certificate with a name such as TCPIPSSLCERT(CPSM-BETA-CERT-2016) but are not able to use a certificate name such as TCPIPSSLCERT(CPSM BETA CERT 2016). When attempting to use a certificate name containing spaces we get the following error message in the EYULOG and the region shuts down.

    07/25/2014 09:08:59 EYUVS0109I CICSBWIA TCPIPSSLCERT(CPSM BETA CERT G2 2016)
    07/25/2014 09:08:59 EYUVS0108I CICSBWIA STARTUP PARAMETERS READ.
    07/25/2014 09:08:59 EYUVS0104E CICSBWIA Parameter (TCPIPSSLCERT) invalid.
    07/25/2014 09:08:59 EYUVS0103E CICSBWIA Parameter service failed.
    07/25/2014 09:08:59 EYUVS0005S CICSBWIA CICSPlex SM Web User Interface initialization failed. (Parameter service.)
    07/25/2014 09:08:59 EYUVS0004I CICSBWIA CICSPLEX SM WEB USER INTERFACE TERMINATION COMPLETE.

    The keyring we are using is called CPSMRING and I have checked that both certificates are in that keyring.

  • Guest
    Reply
    |     Jul 10, 2014

    I have been investigating this RFE and have a query. I cannot actually reproduce the problem. I generated certificate names containing one or two blanks as part of the name eg. 'Beard 2048-Certificate' and 'Beard 2048 Certificate'. I then defined TCPIPSERVICE resources to use these certificates. They installed with no problem and the TCPIPSERVICEs were usable. I also generated TCPIPSERVICE resources using these certificate names using DFHCSDUP, and these also worked.

    The only way I can reproduce the problem is to configure CICS to use the wrong keyring. If the KEYRING system initialisation parameter does not match keyring name generated by DFH$RING, then the TCIPISERVICE will not install and I see the error stating "Install of TCPIPSERVICE [name] failed because CERTIFICATE [cert name] is invalid."

    I did my tests on the latest version of CICS, that is CICS TS 5.2. On what version of CICS are you seeing this problem? Are you absolutely sure that the certificates are in the correct keyrings?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.