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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 requirement has been evaluated and on the basis of current plans and market interest, it is not likely that this would be implemented in future zOS Connect EE 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.
While z/OS Connect does support alignment of data structure fields on half, full, and double-word boundaries, it does not support PL/I techniques that save space within an ALIGNED structure by omitting padding (e.g., last record is shorter than first).
To expose PL/I programs with ALIGNED structures as services, a wrapper program with UNALIGNED versions of the structures could be exposed instead. For the request, the wrapper program would assign an UNALIGNED version of the request structure to an ALIGNED version and link to the original program. For the response, the wrapper program would assign the ALIGNED version of the response structure to the UNALIGNED version. The following example shows how a wrapper program can efficiently map between ALIGNED and UNALIGNED versions of structures:
PGM1WRAP: PROC;
DCL 01 PGM1_REQUEST ALIGNED,
02 ...;
DCL 01 PGM1_RESPONSE ALIGNED,
02 ...;
DCL 1 ZCEE_REQUEST LIKE PGM1_REQUEST UNALIGNED;
DCL 1 ZCEE_RESPONSE LIKE PGM1_RESPONSE UNALIGNED;
/* Get ZCEE_REQUEST from IMS message queue or CICS container */
PGM1_REQUEST = ZCEE_REQUEST; /* unaligned to aligned */
CALL PGM1(PGM1_REQUEST, PGM1_RESPONSE); /* pass aligned */
ZCEE_RESPONSE = PGM1_RESPONSE; /* aligned to unaligned */
/* Put ZCEE_RESPONSE to IMS message queue or CICS container */
RETURN;
END PGM1WRAP;