Patch-ID# 116428-05 Keywords: sunwscmqs Synopsis: Sun Cluster 3.0/3.1 HA-WMQS patch Date: Mar/30/2005 Install Requirements: NA Solaris Release: 8 9 SunOS Release: 5.8 5.9 Unbundled Product: Sun Cluster Unbundled Release: 3.1/3.0 Xref: Topic: Sun Cluster 3.0/3.1 HA-WMQS patch Relevant Architectures: sparc BugId's fixed with this patch: 4886209 4888567 4888572 4964269 4964275 4964277 4979428 4992038 4992041 5040493 6202395 6202554 6203135 6216284 6218994 Changes incorporated in this version: 6216284 6218994 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /opt/SUNWscmqs/chi/bin/functions /opt/SUNWscmqs/chi/bin/start-chi /opt/SUNWscmqs/chi/bin/stop-chi /opt/SUNWscmqs/chi/bin/test-chi /opt/SUNWscmqs/chi/etc/config /opt/SUNWscmqs/chi/util/chi_config /opt/SUNWscmqs/chi/util/chi_register /opt/SUNWscmqs/csv/bin/functions /opt/SUNWscmqs/csv/bin/start-csv /opt/SUNWscmqs/csv/bin/stop-csv /opt/SUNWscmqs/csv/bin/test-csv /opt/SUNWscmqs/csv/etc/config /opt/SUNWscmqs/csv/util/csv_config /opt/SUNWscmqs/csv/util/csv_register /opt/SUNWscmqs/etc/SUNW.mqs /opt/SUNWscmqs/lsr/bin/functions /opt/SUNWscmqs/lsr/bin/start-lsr /opt/SUNWscmqs/lsr/bin/stop-lsr /opt/SUNWscmqs/lsr/bin/test-lsr /opt/SUNWscmqs/lsr/etc/config /opt/SUNWscmqs/lsr/util/lsr_config /opt/SUNWscmqs/lsr/util/lsr_register /opt/SUNWscmqs/mgr/bin/check-start /opt/SUNWscmqs/mgr/bin/create_tdq /opt/SUNWscmqs/mgr/bin/functions /opt/SUNWscmqs/mgr/bin/start-qmgr /opt/SUNWscmqs/mgr/bin/stop-qmgr /opt/SUNWscmqs/mgr/bin/test-qmgr /opt/SUNWscmqs/mgr/etc/config /opt/SUNWscmqs/mgr/util/mgr_config /opt/SUNWscmqs/mgr/util/mgr_register /opt/SUNWscmqs/trm/bin/functions /opt/SUNWscmqs/trm/bin/start-trm /opt/SUNWscmqs/trm/bin/stop-trm /opt/SUNWscmqs/trm/bin/test-trm /opt/SUNWscmqs/trm/etc/config /opt/SUNWscmqs/trm/etc/sample_trm_queues_file /opt/SUNWscmqs/trm/util/trm_config /opt/SUNWscmqs/trm/util/trm_register Problem Description: 6218994 SC3.1 WebSphere MQ Agent - Dummy RTR file requires #% SERVICE_NAME entry for package upgrade 6216284 SC3.1 WebSphere MQ Agent - suppress informational channel FDC files when running endmqm (from 116428-04) 6203135 SC3.1 WebSphere MQ Agent - The stop command failed to stop the application 6202554 SC3.1 WebSphere MQ Agent - Registering the resource using mqr_register assumes values are set 6202395 SC3.1 WebSphere MQ Agent - long pauses or occasional probe timeouts (from 116428-03) 5040493 SC3.1 WebSphere MQ Agent - Bug with cleanup IPC entries (from 116428-02) 4992038 SC3.1 WebSphere MQ agent - Support for XAResourceManager 4992041 SC3.1 WebSphere MQ agent - Allow user defined userid for mq commands (from 116428-01) 4964269 SC3.1 WebSphere MQ agent - Support for S9RM when issuing su 4964275 SC3.1 WebSphere MQ Agent - Cleanup IPC entries for MQ 4964277 SC3.1 WebSphere MQ agent - Tolerate manual start of application 4979428 Agent requires a dummy RTR file 4888572 TRM requires support for multiple process trees 4888567 Check Qmgr dependency not robust enough 4886209 Queue manager probe inefficient Patch Installation Instructions: -------------------------------- There are three (3) possible procedures for installing patches on Sun Cluster 3.0 and 3.1. The proper method to use and any additional instructions, for this patch are specified below in the "Special Install Instructions" section. Refer to the chapter entitled "Patching Sun Cluster Software and Firmware" in the Sun Cluster 3.0/3.1 System Administration Guide for a description of the different install processes and instructions on how to install Sun Cluster 3.x patches. For Solaris 8 release, refer to the man pages for instructions on using 'patchadd' and 'patchrm' scripts provided with Solaris. Special Install Instructions: ----------------------------- For BugIDs 4992038 4992041 Included within this patch are some new enhancements that may require the resource to be removed and re-registered. The following parameters have been added that either have default values or null values. If you need to change either the default values or include values then you must remove and re-register the resource. After the patch is installed, these parameters can be found in /opt/SUNWscmqs//util/_config where _config is a three-character abbreviation for the various WebSphere mq components. Only USERID=mqm is included with the chi, csv, lsr and trm components. The mgr_config contains all the parameters. If you need to change the USERID= parameter, you should change all the _config files for those components you use, then run the _register script as shown in Note 2 below. New parameters with default and null values. CLEANUP=YES USERID=mqm DB2INSTANCE= ORACLE_HOME= ORACLE_SID= START_CMD= STOP_CMD= The parameters above are described below, CLEANUP=YES Deletes unused shared memory segments created by mqm USERID=mqm Userid mqm will be used to issue mq commands DB2INSTANCE= DB2 Instance name for XAResourceManager ORACLE_HOME= Oracle home directory for XAResourcemanager ORACLE_SID= Oracle SID for XAResourceManager START_CMD= / of renamed strmqm program STOP_CMD= / of renamed endmqm program XAResourceManager Processing allows WebSphere MQ to manage global units of work with DB2, Oracle and/or Sybase. If a WebSphere MQ queue manager's qmgr/log files are deployed on a global file system, renaming the strmqm/endmqm programs prevents the queue manager from being manually started on another node. Instead, the cluster framework will manage the startup. However, please refer to the Sun Cluster for WebSphere MQ for Solaris OS documentation on how to do this. Note 1: No changes required --------------------------- If you have no need to change either the default values or include values to the parameters above, then simply apply this patch and follow "How to Apply a Non-Rebooting Sun Cluster Patch" in the Sun Cluster 3.0/3.1 System Administration Guide. Note 2: Changes required ------------------------ If you need to change either the default values or include values to the parameters above, then you must remove and re-register the resource, as follows. 1. Save the WebSphere MQ resource definitions. scrgadm -pvv -g > 2. Offline the WebSphere MQ resources using scswitch -n -j 3. Remove the WebSphere MQ resources using scrgadm -r -j 4. Add the patch (On all nodes within the cluster) 5. Edit /opt/SUNWscmqs/mgr/util/mgr_config and set the parameters as required. 6. Run /opt/SUNWscmqs/mgr/util/mgr_register to register the WebSphere MQ resource. 7. Repeat for other WebSphere MQ components Edit /opt/SUNWscmqs//_config Run /opt/SUNWscmqs//_register 8. Rerun 1. above to a different file. scrgadm -pvv -g > 9. Check that no resource property values have been reset, i.e. timeout values diff 10. Amend any resource property values that have been reset. scrgadm -c -j -x|y = 11. Bring Online the resources using scswitch -e -j README -- Last modified date: Wednesday, March 30, 2005