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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
This RFE is satisfied by CICS Transaction Server for z/OS V5.5 which is GA today 14th December 2018.
This RFE is satisfied by CICS Transaction Server for z/OS V5.5 which is announced today 2nd October 2018 and which has a planned availability date of 14th December 2018.
For more information see the CICS TS V5.5 announcement letter https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS218-352/index.html&request_locale=en
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.
Hi Radhik, Thanks for the comment. After the application got invalid certificate error during SSL handshaking and DFHSO0123 is issued, DFHPI0404 message should output the name of webservice and pipeline. There should also be a DFHPI0400 message issued. With these information, one should be able to tie the error messages to the application. Wonder if you have looked into these messages?
Thanks, Jenny
We like to see if the webservice name can be included with the error message so that we can identify the consumer/requester.
This would help us to save time identifying which application is passing
1) an incorrect/invalid cert during a DFHSO0123 with RC=414
2) an invalid cipher/protocol negotiation issues resulting in DFHPI0404
3) no common cipher negotiated> DFHSO0123 with RC=402
Most of the services are hosted on server's that host more than 6-8 applications and its difficult to identify the app which is causing the error. By knowing the webservice name would help identify the requestor.
We run TS5.2 on z/OS 2.2
thanks
Radhik
We are looking for performance metrics for CICS WEB API requests that use URIMAPs with usage client. The statistics show socket wait time but there is no indication of the URIMAP that is associated to the socket wait time. Without knowing the URIMAP we cannot determine the destination for the requests. Also, some transactions issue CICS WEB API requests to multiple URIMAP's and we cannot identify the socket wait time associated to each request (for example, which one might be the elongated one). In addition, is there any way to tell what transactions are using particular URImaps?
This is a candidate for a future release