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.
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
This requirement is satisfied by CICS TS 5.2 which is generally available from June 13th 2014.
This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Transaction Server for z/OS, V5.2 announcement letter
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107
This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Tools for z/OS, V5.2 announcement letter
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107
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.
This is a candidate for a future release.
It's totally true I'm starting with an existing application. I confirm you that we are changing the WSDL manually to circumvent the lack of support for OCCURS DEPENDING ON, not to make fields optional.
But the PERL Script developped by us allows also to hide the program name everywhere where it's used to generate tag names (Cf. RFE 15821)
We need some more information here. The fact you are using DFHLS2WS implies you are starting with an existing application. You describe that you generate WSDL for that application, and are changing the WSDL manually in order to circumvent one or more of the limitations of DFHLS2WS. The most obvious such limitation is the lack of support for OCCURS DEPENDING ON, or is there another reason to mark fields in the WSDL as minOccurs="0" ? For example, to make fields optional ?
Is the requirement asking for OCCURS DEPENDING ON on support ? This is a well known requirement.
Or is the requirement asking to suppress certain fields from the XML interface? If so , there's a wizard in RDz that allows that to be done today. If RDz is used to generate the WSBind file, you can select which individual fields you want to include in the WSDL, either for input or for output, and it will build a suitable WSBind file for you.