Process for refreshing the zAPM Connect env after PTF install that made changes to MQ monitoring subsystem code

Steps

Note:  These instructions are one method.  Check your company's procedures for LNKLST updates.

1. Install the PTF.

2.  Stop IBM MQ QMGR regions that are being monitored by zAPM Connect, use the AGMQ TERM command.  Do this for every MQ Subsystem to clear obsolete subsystems communications table's extension.  

F AGMAPROC,AGMQ TERM agmq

*Replace "agmq" with your MQ subsystem name.
 AGMAPROC is the default Container PROC name.

3.  Bring down the CICS regions involved in zAPM Connect monitoring of CICS/MQ transactions. Alternatively, you can issue the following modify command to stop zAPM Connect transaction monitoring without having to stop the CICS region completely:

F cicsrgn,AGMU,STOP  

* Replace “cicsrgn” with your CICS Region. 

4.  Bring down Container PROC (named AGMAPROC by default).

5.  Verify whether the required modules are in the current LNKLST data set. Issue the following commands to check: 

SETPROG LNKLST,TEST,NAME=CURRENT,MOD=AGMQSSIN
SETPROG LNKLST,TEST,NAME=CURRENT,MOD=AGMQSTBC
SETPROG LNKLST,TEST,NAME=CURRENT,MOD=AGMQSTBX

If the command output indicates that the modules are already in an LNKLST data set, but the data set is not the SMP/E target data set &shilev.SAGMMOD.  You must ensure that the modules are identical to the ones in the SMP/E target data set. If they are not identical, perform the following tasks:

• Replace the modules in the data set that is displayed in the command output of the prior step with the ones in the SMP/E target data set.
• Issue the following command to build a new copy of all the library directory indexes for the complete set of data sets that are currently managed by library lookaside (LLA):    

F LLA,REFRESH

If the updated modules are already in the current LNKLST data set, skip to step 7; otherwise, proceed to step 6.

6. Update the LNKLST data sets with either of the following methods (a or b), depending on your preferences:

a. Copy the required modules (AGMQSSIN, AGMQSTBC, and AGMQSTBX) to a data set in the current LNKLST concatenation. You can use the

D PROG,LNKLST

Command to display the data sets in the current LNKLST.  Issue the following command to build a new copy of all the library directory indexes for the complete set of data sets that are currently managed by library lookaside (LLA):     

F LLA,REFRESH

OR

b. Define a new LNKLST, add the SMP/E target data set &shilev.SAGMMOD to this new data set, and activate the new LNKLST. Issue the following commands to define and activate a new LNKLST:

SETPROG LNKLST,DEFINE,NAME=TEMP,COPYFROM=CURRENT,NOCHECK
SETPROG LNKLST,ADD,NAME=TEMP,DSN=&shilev.SAGMMOD 
SETPROG LNKLST,ACTIVATE,NAME=TEMP

SETPROG LNKLIST,UPDATE,ASID=1

• Which ever method you choose (a or b), use the "SETPROG LNKLST,TEST" commands as described in step 5 to make sure that the three modules can now be referenced through LNKLST concatenation.

7.  If not already done, APF authorize the LNKLST data set. Issue the

D PROG,LNKLST 

Command to verify whether the &shilev.SAGMMOD data set is in the APF list. If not, issue the

SETPROG APF,ADD,DSNAME=&shilev.SAGMMOD,SMS (if the data set is SMS managed) 
or 
SETPROG APF,ADD,DSNAME=&shilev.SAGMMOD,VOLUME=xxxxx (if not SMS managed). 

8. Define a new IBM MQ Monitoring subsystem. By default, AGMQ is the name of the IBM MQ Monitoring subsystem. Issue D SSI command to verify what IBM MQ Monitoring subsystem is already defined. 

SETSSI ADD,SUBNAME=AMQ1,INITRTN=AGMQSSIN 
where AMQ1 is unique (i.e. not listed in the output /D SSI command).

AGMQ3000I Z APM CONNECT MQ MONITORING SUBSYSTEM AMQ1 (HAPM610) V6.1.0 INITIALIZATION SUCCESSFUL

F LLA,REFRESH 

9. Edit the containers PROCLIB’s AGMAPARM DD data set member to use the new SSID defined in step 8A, as such:

• AGMQSUBSYSTEM=AMQ1

10. Start Container PROC.

11. Initialize the IBM MQ QMGR regions using 

F AGMAPROC, AGMQ INIT amq1

*Replace "AMQ1" with your MQ subsystem name.
 AGMAPROC is the default PROC name for the Container.

12. Verify that tracking is active for each IBM MQ QMGR using the new IBM MQ Monitoring subsystem.  Look for these messages in the Container output after the AGMQ INIT mmmm commands are issued:        

• Connected to AGM MQ Monitoring subsystem AMQ1               
• MQ Subsystem mmmm: Tracking activated                      

Also, verify the output of the /F AGMAPROC,AGMQ VER command for the occurrence of the PTF number, in the AGMAPROC output.  This is a sample output (which is shortened): 

AGMZ0004I AGMA - AGMQ VER                                 
AGMA0001I AGMA AGMQINIT ID=UA98829 06.01.00 03/20/19 08.36
AGMA0001I AGMA AGMQTERM ID=UJ07785 06.01.00 02/17/22 14.35
AGMA0001I AGMA AGMQINST ID=UJ08194 06.01.00 03/31/22 09.55
AGMA0001I M92A AGMQAPIX ID=UJ08194 06.01.00 03/31/22 09.55
AGMA0001I M92A AGMQAPID ID=UJ07785 06.01.00 02/17/22 14.35

If you do not see the occurrence of the PTF number in this output, double check the SAGMMOD modules in the LNKLST concatenation (steps 5 - 7).

13. Depending on what you did in step 3, either start the CICS regions, or alternatively, issue this modify commands to update the zAPM Connect code running in the CICS regions:  

F cicsrgn,AGMU,START

*Replace "cicsrgn" with your CICS Region name.

Note: To have these changes persist across an IPL, you need to either update your system PARMLIB concatenation to specify the new IBM MQ Monitoring Subsystem.  Or you will need to change your Container AGMAPARM DD data set member back to use the PARMLIB value before the next IPL.