Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Future consideration
Created by Guest
Created on Jun 10, 2022

Multiple MQ monitoring subsystems in an lpar

Currently if any maintenance hits the 3 lmods concerned with the subsystem interface AGMQSTBC/AGMQSTBX/AGMQSSIN we have to either stop all ZAPM activity across that entire image, AGMQ TERM for any MQ regions where monitoring is active, stop CICS regions where we have APM running, perform SETSSI DELETE/ADD actions (locally preferred over a new SSN name for procedural reasons) or IPL.

This means that we are forced into having a single release level of zAPM across the lpar and any maint which hits the 3 lmods, or even any maint that has in its pre-req chain those 3 lmods, requires us to roll it out across the lpar big bang. This is disruptive and not very DevOps/Agile.

We would like the ability to release to a subset of an lpars zAPM active CICS/MQ regions with the use a user defined SUBNAME/INITRTN pairing. This would allow us to do:-

  1. Update linklist with 3 x new ssn lmods

  2. SETSSI ADD,SYSNAME=NEW1,INITRTN=AGMSSINx (where x is determined by IBM, alphanumeric, increasing with any new AGMQSTBx/AGMQSTBx/AGMQSSIx lmods.

  3. Update a subset of SAGMMODy libs with new code level.

  4. Point CICS/zCEE at new SAGMMODx libs (aliasing and symlinks potentially)

  5. Update ZAPMxx STC AGMAPARM with new AGMQSUBSYSTEM=NEW1

  6. Restart ZAPMxx

  7. Restart our locally determined subsets of CICS/MQ.

This would give us the flexibility to release a new maint level on a CICS/MQ/ZAPMxx basis, does not rely on a big bang approach & removes the need for potentially disruptive SETSSI DELETE/ADD & SETPROG LNKLST UPDATE actions. It would also allow for a much less disruptive implementation & backout if problems are experienced.

An example of SSN subset updates within an LPAR can we seen with TWS/IWS for example:-

SUBSYS SUBNAME(EQQV) INITRTN(EQQINITx) INITPARM('2816,N')

SUBSYS SUBNAME(EQQW) INITRTN(EQQINITy) INITPARM('2816,N')

Where x/y could be differing maint/release levels of TWS/OPC/IWS. This is evident here:-

Defining subsystems - IBM Documentation IWS 9.3 EQQINITM INITRTN

Defining Subsystems (ibm.com) Earlier TWS release EQQINITF INITRTN

Further info here IBM Docs - IBM Documentation

Idea priority High