Updating SYS1.PARMLIB members
For the IBM Z® APM Connect IBM® MQ subsystem to be automatically defined at an IPL, make permanent updates to various members in the SYS1.PARMLIB library.
About this task
- 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
- Verify that the required modules in the
LNKLST data set are the correct level.
If the data set displayed in the command output of step 1 is not the SMP/E target data set &shilev.SAGMMOD, ensure that the modules (AGMQSSIN and AGMQSTBX) are identical in the two data sets. If they are not identical, replace the modules in the data set in the command output of step 1 with the ones in the SMP/E target data set.
When you are finished, proceed to step 4.
- Update the LNKLST data sets.
The load modules (AGMQSSIN and AGMQSTBX) must be placed in a LNKLST data set so that they are available during an IPL. You can choose either of the following methods, depending on your preference:
- Copy the load modules to an exiting data set in the current LNKLST concatenation. This copying process must be repeated every time new maintenance is applied to these modules.
- Add the SMP/E target data set &shilev.SAGMMOD to the LNKLST data set.
The second method requires an update of the PROGxx or LNKLSTxx member in the SYS1.PARMLIB library, depending on how your system is configured.
The following examples assume that you are using PROGxx instead of LNKLSTxx to define the LNKLST concatenation.
Assume that LNKLST00 is the LNKLST defined in the PROGxx member that is activated during an IPL. To add the &shilev.SAGMMOD data set to the LNKLST concatenation, edit the PROGxx member where the LNKLST00 is defined and add the LNKLST statement to the LNKLST00 definition section as follows:
LNKLST ADD NAME(LNKLST00) DSN(&shilev.SAGMMOD)
If the data set is cataloged in a user catalog but not in the system main catalog, you must also specify the volume serial number (VOLSER) of the volume on which the &shilev.SAGMMOD data set resides. Assume that the data set resides on PP0C0P volume, the prior LNKLST statement must be changed as follows:
LNKLST ADD NAME(LNKLST00) DSN(&shilev.SAGMMOD) VOLUME(PP0C0P)For more information about the LNKLST statement in the PROGxx member, see z/OS MVS Initialization and Tuning Reference, SA22-7592.
- APF authorize the LNKLST data set.
The LNKLST data set where the modules (AGMQSSIN and AGMQSTBX) are placed in previous steps must be APF-authorized. If the default LNKAUTH system parameter is taken (LNKAUTH=LNKLST) or is specified in the IEASYSxx member in SYS1.PARMLIB library, you do not have to do anything. The LNKLST data sets are automatically APF-authorized when accessed as part of the LNKLST concatenation if LNKAUTH=LNKLST is used.
If LNKAUTH=APFTAB is specified in the IEASYSxx member in SYS1.PARMLIB, the data set must be explicitly APF-authorized by updating the IEAAPFxx or PROGxx member in the SYS1.PARMLIB library, depending on your system configuration.
The following example assumes that you are defining APF list by using PROGxx instead of IEAAPFxx. Edit the PROGxx member where the APF statements are defined and add an APF statement for the data set as follows:
where dsname is the name of the LNKLST data set that you use in previous steps, 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.
APF ADD DSNAME(dsname) VOLUME(volser)
APF ADD DSNAME(dsname) SMSTip: You can use the D PROG,LNKLST command to check the LNKAUTH setting in your system. For example, the following command output indicates that LNKAUTH=LNKLST is used.
D PROG,LNKLST CSV470I 21.40.36 LNKLST DISPLAY 213 LNKLST SET LNKLST00 LNKAUTH=LNKLST ENTRY APF VOLUME DSNAME 1 A G1C01C SYS1.LINKLIB 2 G1C01C SYS1.MIGLIB 3 G1C01C SYS1.CSSLIB 4 G1C02C SYS1.SIEALNKE 5 G1C01C SYS1.SIEAMIGE 6 A A30091 USER.LINKLIB ……Remember: If LNKAUTH=LNKLST is used and the SMP/E target data set &shilev.SAGMMOD is added to the LNKLST data set, it is not necessary to explicitly APF authorize the data set for defining the IBM Z APM Connect IBM MQ Monitoring subsystem. However, since the dataset will need to be specified through a STEPLIB DD statement in the AGMAPROC, you still must explicitly APF authorize the dataset with an APF ADD statement in the PROGxx member. Even when LNKAUTH=LNKLST is used, if a library is in the LNKLST concatenation, but is not explicitly APF-authorized, referencing this library through a JOBLIB or STEPLIB DD statement will cause the library to be considered unauthorized for the duration of the job or the step.
- Update the IEFSSNxx member of the
The appropriate IEFSSNxx member of the SYS1.PARMLIB library must be updated to identify the IBM Z APM Connect IBM MQ Monitoring subsystem to a z/OS® system.
You can use the D SSI command to display all the subsystems that are defined in the system. Look through the command output to check whether the wanted subsystem is already defined.
If the IBM Z APM Connect IBM MQ monitoring agent subsystem is not defined, code one of the following entries to update the IEFSSNxx member in the SYS1.PARMLIB library, depending on the parameter format:
- Positional format: subname, AGMQSSIN.
- Keyword format: SUBSYS SUBNAME(subname) INITRTN(AGMQSSIN).
For more information about the syntax and rules for coding IEFSSNxx, see z/OS MVS Initialization and Tuning Reference, SA22-7592.
After an IPL is done, the AGMQ3000I message like the following one is written in the SYSLOG, informing you that the subsystem initialization routine completed successfully.
AGMQ3000I Z APM CONNECT MQ MONITORING SUBSTEM AGMQ (UAxxxxx) V6.1.1 INITIALIZATION SUCCESSFUL