JOBNAME as keyword on command QUEUE

What is IBM’s opinion on making it possible to include jobname as a keyword in the execution of the command QUEUE TRAN (just as jobname is a keyword on the command PSTOP)?

For example, currently the possible keywords for the command are
QUEUE TRAN NAME(tranname) OPTION(optionname) DATA(messagedata)

Adding jobname as a keyword
QUEUE TRAN NAME(tranname) JOBNAME(jobname) OPTION(optionname) DATA(messagedata)

Why is this functionality needed?
Answer: When simultaneously running several transaction-oriented BMPs each using the same input transaction code, it is not possible to use QUEUE to send a message directed to one of the transaction-oriented BMPs in particular. An example where this is needed is during the automated process of restarting transaction-oriented BMPs where the BMPs sharing the same input transaction code need to be restarted sequentially. Sending a message to each BMP using QUEUE is a more simple, maintainable and intuitive solution than creating a type-2 AO exit routine, using the /LOG command to send the AOI token and message to be fetched by the exit routine, and finally reading the message directed by the exit routine to the AOI token using the DL/I call GMSG from the application program.
If able to instead use QUEUE, then the message will be fetched by the existing GU in the application program’s main loop, like the other messages, and there will be no need for a customized exit routine nor the GMSG call.