Upgrading the Agent and Extensions

Before you begin

• During these procedures, the following users should be available:
  • Users with authority and permissions to distribute and configure agents.
• If you are updating secured agents on a UNIX system, you must have root access so that you can overwrite the secured files. Delete or rename the secured agent and then distribute the new version of the agent. Re-secure the agent after you have distributed the new version. See Defining-user-access-and-security-settings for more information.
• RACF configuration changes might be required so that QPCFG can use the authentication and authorization API. For more details, see Running-performance-and-availability-monitoring-extensions.
• Refer to the Planning section and determine the installation layout required for each of your agents.

To upgrade the MVMM Extensible Agent and Extensions

If you wish this agent to retain the Flat Directory Layout, refer to the section on Updating-or-upgrading-the-Flat-Directory-Layout-installation.

If you wish this agent to be upgraded to the Default Layout, refer to the section on Upgrading-from-the-Flat-Directory-Layout-to-Default-Layout.

To upgrade the MVMM Extensible Agent and Extensions on z\os platform

Before you begin:

1. Back up your existing agent data sets, including EAAXML.
2. If 90% of objects are to be monitored, consider turning queue manager and object discovery on.

Verify that EAAXML has enough space to hold the definitions for discovered objects. You may choose to double the primary and secondary sizes. If the total number of objects will number in the thousands.

For more information regarding HEAP fine tuning see Tuning the z/OS operating system to optimize MainView Middleware Monitor applications.

Upgrading the MVMM Extensible Agent and the IBM MQ configuration and monitoring extensions on z/OS :

1. FTP the new INSTALL.XMIT and the RECV.JCL files with binary mode, from the new installation files to the agent machine.
2. Run the RECEIVE job (RECV.JCL) , which will take the INSTALL.XMIT file as an input, to create a new INSTALL.CNTL PDS and populate it. Note: you must add storage details to the JCL. For more details see Installing the IBM MQ configuration and monitoring extensions 
3. Run JALLOC to create the new load library.
4. Modify PLINK64, which is the proc for JLINK (the parms in PLINK64 should be mostly identical to those in the previous install).
5. Modify and run JLINK64 to populate the new load library.
6. Stop the agents with the STOP (P) command.
7. Change the loadlib in the QPEA, QPMON, QPCFG procs to point to the new load library.
8. Identify any updated members in the new INSTALL.CNTL PDS, and migrate them to the INSTALL.PDS referenced in the agent and extension started tasks. You must at least update QPCDEF and QPTTAB.
9. Check the CEEOP64 DD and edit the DD to reflect the time zone where the extension is running. For more information about Setting TZ environment variable see Controlling-the-MVMM-Extensible-Agent-on-z-OS-platforms.  
10. Start the agent and all extension STCs, for more information how to run the MVMM Extensible Agent and monitoring extensions as started tasks see Controlling the MVMM Extensible Agent on z/OS platforms.  

To upgrade the IBM IIB/ACE monitoring extension

Before you begin

• Use the source mqsiprofile command to execute the shell you will be working with for the update. 
• Ensure you can run commands such as:
  • mqsiservice -v
  • mqsilistIf these commands do not give you good results, the mqsi profile may not have been sourced properly.
• Distribute the correct pkg_unix_qpwmb.zip from the MVMM  server; you can use the package distribution feature or transfer the file manually from the AGENT_DIST folder that corresponds to your operating system.

For additional information, see Installing-the-IBM-IIB-ACE-monitoring-extension and Running the IBM IIB/ACE monitoring extension.

Updating the extension

1. From <AGENT INSTALL>/qpwmb, run the following commands:
   • ./bin/qpwmb.sh --stop
   • ./bin/qpwmb.sh --status
2. Run the ps -ef | grep java command to see if any stray qpwmb JVMs are still running.
3. Run the following commands from <AGENT INSTALL>.  These commands will back up the existing installation, then create and populate a new install.
   • mv qpwmb qpwmb_backup
   • mkdir qpwmb
   • cd qpwmb
   • mv ../pkg_unix_qpwmb.zip
   • unzip *.zip 
4. Review and restore any JVM parms from the old qpwmb.sh.