IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.

  • Guest
  • Jun 24 2019
  • Future consideration
What is your industry? Retail
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.   

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.