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 10, 2012

DFHWS2LS: Variable names in the generated PL/I / COBOL code

DFHWS2LS: Variable names in the generated PL/I / COBOL code is unnecessary added a number where it is not necessary for unique identification of the fields.

The customer is not quite happy with the way DFHWS2LS builds               
declarations especially with the result if WS2LS is re-run after any    
changes(adds) to the WSDL were made.                                    
-                                                                       
When there are new fields added with a 'Type' which was                 
already used for other elements, WS2LS builds for each element          
a subfield according the type definitions. WS2LS makes these subfields  
unique by adding a number.                                              
After a re-run it may happen that most of fields  were changed          
which means that there is huge amount of rework required. 


ISSUE 1
The following example shows that the numbering mechanism used for the generated data structures has some very serious consequences.

PROBLEM:
Variable names in the generated PL/I / COBOL code is unnecessary added a number where it is not necessary for unique identification of the fields.

CONSEQUENCES:

It is not possible to reuse the program code that is written to map from the generated PL/I or Cobol code to a corresponding PL/I or Cobol Com Area.
When  small changes in the XML Schema are introduced (like inserting an element) then
Need for refactoring/rewriting greater parts of the mapping code can occur
Great risk of introducing errors in the mapping code can occur. Furthermore these errors are very hard to find.

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
    |
    Apr 1, 2015

    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 twelve months time if you wish it to be considered then.