This portal is to open public enhancement requests for IBM Sterling products and services. 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 updateson 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
Alternative to +SETALL permissions requirement on IBM MQ Adapter connections using -EQN
IBM MQ Adapter connections often use the -EQN facility to designate an alternate queue from the input -QN so that error messages do not get stuck in the input queue and interfere with message processing over time.
The use of -EQN requires the +SETALL permission on the IBM MQ server for the given itxuser. Presumably this is because the -EQN function is using the full -HDR syntax on PUT to preserve all current MQMD settings. E.g., the message is being copied as is instead of being re-created.
Unfortunately, our organization has identified +SETALL as a security risk because the so granted itxuser has the same effective authority level as the MQ administrators. This elevated access needs to be removed, but in doing so, the -EQN setting no longer works.
In discussions with IBM Support the implication was that the current usage of -EQN cannot be altered due to impacts to other clients.
Therefore, I propose a new optional command be added to the IBM MQ Adapter to be used in conjunction with the -EQN command. Essentially, the new command tells -EQN to either continue using the default behavior of -HDR (preserving current MQMD settings), or to allow -DH on -EQN (effectively putting a new message).
This means that users that do not want to use the flag will continue to have the default behavior and require no code changes as long as they accept the usage of +SETALL permissions. For those that cannot allow the +SETALL permissions, the new command would allow -EQN to continue to work with a minor update to the IBM MQ Adapter connection settings. While this does create a new message and deletes the current MQMD, our organization has decided this is an acceptable loss. In general, we are not exploiting those header settings for reprocessing anyway, but rather using message content.
What is your industry?
How will this idea be used?
To alleviate an enterprise security concern and still utilize the -EQN function. Without this enhancement we will have to discontinue usage of the -EQN command and instead use BackUp OnError on the input card to save the message as a file. This will require the additional rework of the error processing for these processes. As we have hundreds of queues, or primary adapter, the potential re-work to accommodate the security concern will be large.
Option to create persistence IBM MQ message without message descriptor
Objective - Create IBM MQ message with persistence flag = 1 to a queue where 'Default Persistence' attribute set to 'Not Persistence' The only option available is to use MessageDescriptor which is complex. Requesting enhancement in the order of pr...
Do not place IBM confidential, company confidential, or personal information into any field.