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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Nov 16, 2016

PL/I PICUTRE Data Type Support Required in z/OS Connect EE

We are generating SAR files for PL/I Copybooks using BAQLS2JS provided by z/OS Connect EE v2.0. The Copybook contains PIC data types. We were told by IBM that the tool does not support the PIC data type. Therefore we would require the PIC data type support in the product.

Below is the list of data types and samples we are trying out in a Proof Of Concept. Since we were not able to progress after the PIC failure we could not verify that the product supports all the data types that we are using. Therefore we have provided a complete list of data types with examples that we would require support for. We would appreciate it if there are any data types that are not currently supported to be included in the product.


List of Data Type : Example(s) that require product support

PICTURE Type:
==============
PIC'999'
PIC '(13)9V9999'
PIC'(10)9'
PIC'99' INIT(99)
Pic'ZZZZ,ZZZ,ZZZ,ZZ9V.99-'

FIXED DEC Type:
==============
FIXED DEC(2)
FIXED DEC(19,4)
FIXED(30,16) INIT(0)
PRODUCT_ID(W_ARR_SIZE) FIXED DEC(13,0)

FIXED BIN Type:
==============
FIXED BINARY(31)

FLOAT Type:
==============
Float Dec(17,2)

BIT Type:
==============
BIT(1)
BIT(1) INIT('1'B)

CHAR Type:
==============
CHAR(8)
CHAR(10) INIT(' ')

Fixed length array Type:
==============
PRODUCT_ID(W_ARR_SIZE) FIXED DEC(13,0)

like Type:
==============
like MQMD

POINTER Type:
==============
BASED (ABCD1234_COM_PTR)

Thank you.

Idea priority High
  • Guest
    Reply
    |
    Jul 24, 2019

    Since this requirement was originally raised, there have been extensive enhancements to the mapping capabilities of z/OS Connect Enterprise Edition V3.

    As such a significant proportion of the requirements listed here have now been delivered.
    See the "COBOL to JSON schema mapping" and "PL/I to JSON schema mapping" topics in the knowledge center here:
    https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/designing/service_cobol2json.html
    https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/designing/service_pli2json.html

    To acknowledge this and to help us get a better picture of the next most urgent requirements in this space this RFE is being closed as delivered.

    If you have any further requirements for service mapping please raise them separately as additional RFEs

  • Guest
    Reply
    |
    Mar 9, 2018

    A Part of our scenario has the fact, that we want to replace SOAP webservices 1:1 (without change) to REST/SOAP. No matter, if this is clever or not, but we have a lot of them and to quickly be able to integrate them in a REST environment with OAUTH2 this would be our decision.

    We made a POC the last days for this and saw, that there are 2 PL/1 variable types missing:

    -> BIT(n) [with n not a multiple of 8]
    -> CHAR(n) VARYING

    As our Soap services are generated with RDZ EST Tooling we are sure, that there are other customers with the same problem.

    We would need a support in API Toolkit V3 upwards for this.