MQ transaction in CICS TS 5.4 is using a different ACF2 logonid

Document ID : KB000111902
Last Modified Date : 22/08/2018
Show Technical Document Details
After upgrading to CICS TS 5.4, the MQ transaction that ran as a non terminal transaction using the CICS region logonid is now using the default non terminal logonid.  How do this be fixed?
IBM has enhanced CICS TS 5.4 with many new features.  They include a change for MQ Series transactions.

New resource, MQMONITOR, provides a better mechanism for controlling MQ trigger and bridge monitors

A new RDO-defined resource, MQMONITOR, is provided to complement the existing MQCONN resource. You can use this new resource to configure an MQMONITOR, which can be a trigger monitor, an MQ bridge monitor, or a user-written monitor.

Configuration options include the ability to specify a transaction ID to be used by the monitor, the user ID under which a monitor task runs, and the user ID to be used by the monitor to start the application tasks if an alternative user ID is not provided by the application. The AUTOSTART option automatically starts monitors when the CICS-MQ connection is started. Monitors are automatically stopped when the CICS-MQ connection is stopped. Any number of MQMONITOR resources can be defined and installed. Using the MQMONITOR resource removes the need to use the CKQC transaction to start and stop monitors manually.

With the introduction of the MQMONITOR resource, CICS now differentiates between the userID under which the transaction that is monitoring the MQ queue runs (the MONUSERID) and the userID under which the initiated transactions run. This userID (the USERID) is used by default, unless it is otherwise provided. This has implications for any MQMONITOR resources that are dynamically created when an MQCONN is installed. See Review the use of MQCONN in Upgrading CICS regions for details.

Additional Information:
For more information, go to this IBM website: What's new in CICS Transaction Server for z/OS 5.4