#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
# 
# This file will be sourced in by mgr_register and the parameters
# listed below will be used.
#
# These parameters can be customized in (key=value) form
#
#          RS - name of the resource for the application
#          RG - name of the resource group containing RS
#        QMGR - name of the Queue Manager
#        PORT - name of the Queue Manager port number
#          LH - name of the LogicalHostname SC resource
#      HAS_RS - name of the Queue Manager HAStoragePlus SC resource
#     CLEANUP - Cleanup IPC entries YES or NO (Default CLEANUP=YES)
#      USERID - name of userid to issue strmqm/endmqm commands 
#		(Default USERID=mqm)
#
#	+++ Optional parameters +++
#
# DB2INSTANCE - name of the DB2 Instance name
# ORACLE_HOME - name of the Oracle Home Directory
#  ORACLE_SID - name of the Oracle SID
#   START_CMD - pathname and name of the renamed strmqm program
#    STOP_CMD - pathname and name of the renamed endmqm program
#
# Note 1: Optional parameters
#
#	Null entries for optional parameters are allowed if not used.
#
# Note 2: XAResourceManager processing
#
#	If DB2 will participate in global units of work then set
#	DB2INSTANCE=
#
#	If Oracle will participate in global units of work then set
#	ORACLE_HOME=
#	ORACLE_SID=
#
# Note 3: Renamed strmqm/endmqm programs
#	
#	This is only recommended if WebSphere MQ is deployed onto 
#	Global File Systems for qmgr/log files. You should specify 
#	the full pathname/program, i.e. /opt/mqm/bin/<renamed_strmqm>
#
# Note 4: Cleanup IPC
#
#	Under normal shutdown and startup WebSphere MQ manages it's
#	cleanup of IPC resources with the following fix packs.
#
#	MQSeries v5.2 Fix Pack 07 (CSD07) or later
#	WebSphere MQ v5.3 Fix Pack 04 (CSD04) or later
#
#	Please refer to APAR number IY38428.
#
#	However, while running in a failover environment, the IPC keys
#	that get generated will be different between nodes. As a result
#	after a failover of a Queue Manager, some shared memory segments
#	can remain allocated on the node although not used. 
#
#	Although this does not cause WebSphere MQ a problem when starting
#	or stopping (with the above fix packs applied), it can deplete
#	the available swap space and in extreme situations a node may 
#	run out of swap space. 
#
#	To resolve this issue, setting CLEANUP=YES will ensure that 
#	IPC shared memory segments for WebSphere MQ are removed whenever
#	a Queue Manager is stopped. However IPC shared memory segments 
#	are only removed under strict conditions, namely
#
#	- The shared memory segment(s) are owned by
#		CREATOR=mqm and CGROUP=mqm
#	- The shared memory segment has no attached processes
#	- The CPID and LPID process ids are not running
#	- The shared memory removal is performed by userid mqm
#
#	Setting CLEANUP=NO will not remove any shared memory segments.
#
#	Setting CLEANUP=YES will cleanup shared memory segments under the
#	conditions described above.
#

RS=
RG=
QMGR=
PORT=
LH=
HAS_RS=
CLEANUP=YES
USERID=mqm
DB2INSTANCE=
ORACLE_HOME=
ORACLE_SID=
START_CMD=
STOP_CMD=
