Setting up the subsystem without an IPL

You can set up an IBM Z® APM Connect IBM® MQ subsystem without the need of an IPL.

1. Verify whether the required modules are in the current LNKLST data sets.

   Use the following commands to check whether the required modules are already in the current LNKLST data sets.

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

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

   1. 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.
   2. 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 modules are already in the current LNKLST data set, skip to step 3; otherwise, proceed to step 2.

2. Update the LNKLST data sets.

   Update the LNKLST data sets with either of the following methods, depending on your preference:

   • Copy the required modules to a data set in the current LNKLST concatenation.
     1. Copy the load modules (AGMQSSIN 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.
     2. 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

   • Define a new LNKLST, add the SMP/E target data set &shilev.SAGMMOD to this new data set, and activate the new LNKLST.
     1. 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

     2. Issue the following command to update the main scheduler address space to use the new LNKLST:

        SETPROG LNKLIST,UPDATE,ASID=1

   Whichever method you choose, use the SETPROG LNKLST,TEST commands as described in step 1 to make sure that the modules can now be referenced through LNKLST concatenation.
3. APF authorize the LNKLST data set.

   If the default LNKAUTH system parameter is taken (LNKAUTH=LNKLST) or is specified in the IEASYSxx member in the SYS1.PARMLIB library, you do not have to explicitly APF authorize a LNKLST data set.

   If LNKAUTH=APFTAB is specified in IEASYSxx member in the SYS1.PARMLIB library, a LNKLST data set must be explicitly APF-authorized. Use the following command to APF authorize the LNKLST data set that is used in previous steps:

   SETPROG APF,ADD,DSNAME=dsname,VOLUME=volser

   where dsname is the name of the LNKST data set that you choose in previous steps (either a data set in the current LNKLST or the SMP/E target data set), and volser is the serial number of the volume where the data set resides. If the data set is SMS-managed, use SMS instead of VOLUME specification.

   SETPROG APF,ADD,DSNAME=dsname,SMS

   You can use the D PROG,APF command to verify whether the data set is now in the APF list.
4. Use the following SETSSI command to define a IBM Z APM Connect IBM MQ Monitoring agent subsystem dynamically.

   SETSSI ADD,SUBNAME=subname,INITRTN=AGMQSSIN

   After the subsystem is defined successfully, the AGMQS3000I message is written in the SYSLOG. You can look for this message to verify whether the subsystem is defined successfully.