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.
Whilst this requirement is valid, based on our current plans and priorities for IBM z/OS Connect Enterprise Edition, it is not likely that this could be implemented in the next 12 months. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
Hello,
Thank you for your feedback.
As mentioned in the Business Justification, we are using a middle are from TIBCO Software that we are planning to replace with z/OS Connect.
TIBCO made a modification to allow data to immediately follow the IMS transaction name without a blank.
Here is an excerpt from an IMS trace :
+0388 QLOGMSGD... Message Text
+0388 MSGXDLEN... 004D MSGXFLG1... 03 MSGXFLG2... 00
+038C MSGXSTXT... Message Text
+0000 D5E3E2C5 C3F1C4C4 C4D9D3D6 C3F7F2F5 *NTSEC1DDDRLOC725*
+0010 5C404040 40404040 40404040 40404040 ** *
+0020 40404040 40404040 40404040 40404040 * *
+0030 40404040 40404040 40404040 40000000 * ...*
+0040 00000000 00000000 00 *......... *
The transaction name is NTSEC1.
This IMS is using NOBLANK in the OPTIONS of the COMM macro stage 1.
In this case the message is received by TIBCO Substation that acts as an OTMA Client. IMS Connect is not involved.
We would like to reproduce the same behaviour using z/OS Connect and IMS Connect.
Thanks and Regards,
René
When configuring IMS general communications, the COMM macro allows you to specify either BLKREQD or NOBLANK for transaction codes in IMS messages. See topic https://www.ibm.com/docs/en/ims/15.2.0?topic=environments-comm-macro:
BLKREQD | NOBLANK
Specifies whether the 1 to 8 byte transaction code requires a trailing blank. NOBLANK lets you enter a 1 to 8 byte transaction code without having to specify a trailing blank. The selection of NOBLANK indicates that a blank does not have to be specifically entered after a 1 to 8 byte transaction code, but if data is being included after the transaction code, then a blank must be inserted between the code and the data.
With either BLKREQD or NOBLANK, a blank must exist between the transaction code and the data if the transaction code is less than 8 bytes and is followed by data.
Considering NOBLANK, it is necessary to use a copybook where the trancode field is always 1 byte longer than the trancode if data follows.
For example, transaction 'NTSEC' would require the first segment to reserve 6 bytes total for the transaction code and trailing blank...
01 INPUT-MSG.
02 IN-LL PIC S9(4) COMP-5.
02 IN-ZZ PIC S9(4) COMP-5.
02 IN-TRCD PIC X(6).
02 IN-DATA PIC X(...).
while transaction 'NTSEC1' would require the first segment to reserve 7 bytes total for the transaction code and the trailing blank:
01 INPUT-MSG.
02 IN-LL PIC S9(4) COMP-5.
02 IN-ZZ PIC S9(4) COMP-5.
02 IN-TRCD PIC X(7).
02 IN-DATA PIC X(...).
If there is a means by which the behaviors of BLKREQD and NOBLANK do not apply (e.g., custom middleware), we'd appreciate any details or traces of such messages and how they are processed by IMS.