Patch-ID# 116728-04
Keywords: sunwscmqi
Synopsis: Sun Cluster 3.0/3.1 HA-WMQI 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-WMQI patch

Relevant Architectures: sparc

BugId's fixed with this patch: 4976880 4976885 4979430 4985292 4985294 4992068 4992086 6219059

Changes incorporated in this version: 6219059

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/SUNWscmqi/etc/SUNW.mqi 
/opt/SUNWscmqi/sib/bin/functions 
/opt/SUNWscmqi/sib/bin/sc3get 
/opt/SUNWscmqi/sib/bin/sc3inq 
/opt/SUNWscmqi/sib/bin/sc3put 
/opt/SUNWscmqi/sib/bin/start-broker
/opt/SUNWscmqi/sib/bin/stop-broker
/opt/SUNWscmqi/sib/bin/test-broker
/opt/SUNWscmqi/sib/etc/config
/opt/SUNWscmqi/sib/util/sib_config
/opt/SUNWscmqi/sib/util/sib_register
/opt/SUNWscmqi/siu/bin/functions 
/opt/SUNWscmqi/siu/bin/start-uns
/opt/SUNWscmqi/siu/bin/stop-uns
/opt/SUNWscmqi/siu/bin/test-uns
/opt/SUNWscmqi/siu/etc/config
/opt/SUNWscmqi/siu/util/siu_config
/opt/SUNWscmqi/siu/util/siu_register

Problem Description:

6219059 Dummy RTR file requires #% SERVICE_NAME entry for package upgrade
 
(from 116728-03) 
 
4992086 SC3.1 WebSphere MQI agent - can't start broker
4992068 SC3.1 WebSphere MQI agent - start timeout / start failed
 
(from 116728-02) 
 
4985292 SC3.1 WebSphere MQI agent - probe should make message flow test optional
4985294 SC3.1 WebSphere MQI agent - requires dependency check support for multiple db2 instances
4976880 SC3.1 WebSphere MQ Integrator agent - Support for S9RM when issuing su
4976885 SC3.1 WebSphere MQ Integrator agent - Tolerate manual start of application
4979430 Agent requires a dummy RTR file
 
(from 116728-01) 
 
Revision skipped.

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:
----------------------------- 
 
The following parameters have been added as null values. If you 
need to change the values then you must remove and re-register 
the resource.
 
Note for BugID: 4992086
	After the patch is installed, these parameters can be found in
	/opt/SUNWscmqi/<xxx>/util/<xxx>_config where <xxx>_config is a 
	three-character abbreviation for the various WebSphere MQI components.
 
	New parameters with null values.
 
	START_CMD=
	STOP_CMD=
 
	The parameters above are described below,
 
	START_CMD=      <pathname>/<name> of renamed strmqm program
	STOP_CMD=       <pathname>/<name> of renamed endmqm program 
 
	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.
 
	The Broker startup will first try to start the WebSphere MQ manager 
	and as such if strmqm/endmqm have been renamed, the SC3.1 Agent needs
	to know.
 
 
	Note 1: No changes required
	---------------------------
 
	If you have no need to change the 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 the values to the parameters above, then you
	must remove and re-register the resource, as follows.
	resource, as follows.
 
        1. Save the WebSphere MQI resource definitions.
                scrgadm -pvv -g <resource _group> > <file1>
 
        2. Offline the WebSphere MQI resources using
                scswitch -n -j <resource>
 
        3. Remove the WebSphere MQI resources using
                scrgadm -r -j <resource>
 
        4. Add the patch (On all nodes within the cluster)
 
        5. Edit /opt/SUNWscmqs/sib/util/sib_config 
                and set the parameters as required.
 
        6. Run /opt/SUNWscmqs/sib/util/sib_register 
                to register the WebSphere MQ resource.
 
        7. Repeat for other WebSphere MQI components
                Edit /opt/SUNWscmqs/siu/siu_config
                Run  /opt/SUNWscmqs/siu/siu_register
 
        8. Rerun 1. above to a different file.
                scrgadm -pvv -g <resource _group> > <file2>
 
        9. Check that no resource property values have been reset, 
                i.e. timeout values
 
                diff <file1> <file2>
 
        10. Amend any resource property values that have been reset.
                scrgadm -c -j <resource> -x|y <property>=<value> 
 
        11. Bring Online the resources using
		scswitch -e -j <resource>

README -- Last modified date:  Wednesday, March 30, 2005