Skip to Main Content
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.

Status Not under consideration
Categories Runtime
Created by Guest
Created on Aug 7, 2012

Provide an option in CICS TS (as a WEBSERVICE requester) to use a JMS message type of jms_text instead of existing jms_bytes

Currently CICS TS 4.1 when acting a webservice requester ( EXEC CICS INVOKE WEBSERVICE) and using MQ transport, CICS specifies a JMS message type of jms_bytes.
"We are testing a CICS outbound web service (implemented on a Unix platform).
For this specific service we must use MQ.
The URI in the INVOKE WEBSERVICE looks like this
"jms:/queue?destination=A.CV00.AO.WEBSERVICES_REQUEST@SQ1T&targetService=/ACV/SendHoldStatus/1"
The message arrives but the receiver cann't handle the message.
Part of the RFH-header contains:
<mcd>
<Msd>jms_bytes</Msd>
</mcd>
<jms>
<Dst>queue://SQ1T/A.CV00.AO.WEBSERVICES_REQUEST</Dst>
</jms>
And that is were is goes wrong, because the receiver expects a jms_text
message. "
Background:
CICS apar PK20393 from 2006 which is incorporated into base CICS TS 4.1.
PROBLEM CONCLUSION:
DFHPITQ has been changed to set a JMS message type of jms_bytes from jms_text.
.
From the email exchanges it was revealed that CICS changed to using
jms_bytes for interoperability with other IBM products and based on recommendations from the the W3C SOAP/JMS spec that highlights concerns with using TextMessage -
see http://www.w3.org/TR/soapjms/#textmessage-considerations.

Customer is asking for an option to allow them to specify jms_text or jms_bytes in CICS.

Idea priority Medium
  • 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
    |
    Jan 20, 2014

    This requirement has been re-evaluated. Looking at current plans, it is not likely that this would be implemented in the next two CICS TS releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in eighteen months time if you wish it to be considered then.