MQA66026 Cumulative Maintenance for V350 OMA for MQSeries

Problem Description:
S1-40719383 : Attempt to view messages fails with incorrect error code 2033
S1-31940933 : Problem producing reports if MQ command server not available
S1-42175226 : Agent not returning data after it failed to open event queues


The following are carried over from previous fixpacks:

D1-38249105 : Agent fails to report data for some queues when a queue is damaged
D1-37785702 : Memory leaks when opening or refreshing the MQSeries Current Events
              report
D1-34491101 : Deleted definitions for cluster, remote, model, and alias queues are
              not removed from Queue Definitions Workspace.
D1-34761203 : Old receiver channel statistics are not always removed from Channel 
              Performance Workspace according to RETAINHIST.   
D1-33432702 : The connection name on a channel is being truncated on the Channel
              Performance report.
D1-33421301 : Duplicate receiver channel entries in Channel Performance Workspace.
D1-29695402 : CNP KMQAGENT abend if drill down to Workspace without specifying the object
              name and if Workspace Administration mode specified for Userid.
D1-27036001 : Queue and Channel Definition Summary Reports' counters, include deleted
              objects for Distributed platforms.
D1-25857601 : MQ Agent crashes when queue name is zero length
D1-22050302 : Allocation problems for large number of rows in reports
D1-23601306 : Queued Messages Summary reporting erroneous queue depth high with MQ5.3
D1-17881013 : QMQ3524 16 buffer pools
D1-17881013 : MQSeries V5.3 toleration
D1-18236113 : MQ5.3 toleration - Multiple Exits
D1-18236118 : Fix blank Resource Name
1-14746201: Tandem performance improvements.
AX433_PORT: Setup RW dir for solaris build.
1-15321668: Fix channel status for SVR, SVRCONN & CLNTCONN.
1-14402101: Accept multiple parameters for QDEFTYPE in mq.cfg file
1-11156307: Change order of thread termination in agent to avoid MQSeries
            Internal Error
1-5GVR2:    MQ350 Agent stops intermittently.
1-5RSBP:    MQ350 Fix dynamic queue delete.
1-543RG:    KMQMI161E kmq_qmq_lh_agent is missing required table index value(s),
 	    message improved.
1-11133501: Cluster Queue Manager and Channel Initiator reports show
            empty. (CMW)
1-5HTRD:    Selecting Open As Reports from a managed object distributed
            to multiple nodes automatically opens the report for the 
            first (or last) node on the distribution list. (CMW)
1-4PQ9L:    MQSeries agents which are connected to remote CMS are not 
            visible in the Summary reports when there are also MQ agents
            connected to the HUB. (CMW)
1-56S04:    When trying to delete a message off of a queue, receiving 
	    unexpected  I/O return code of 1136.
1-5SL11:    MQ 300: HPUX 11 (64 Bit) Agent will not stay up.
1-5SYAT:    MQ350  Slow response for AS/400 MQ/MC Agent to respond.
1-5L6R2:    MQ300 - problem with data that are sent from the MQ agents 
	    to the CMS.
1-4QTGL:    MQ monitoring agent crashes at startup
1-3HRUW:    MQ300 Fatal error after accessing report queue statistic 
            detail report. Solaris 2.7 64 bit systems.
1-4NXKW:    MQ300 Does the AS400 agent have an exclusive hold on 
            SYSTEM.ADMIN.CHANNEL.EVENT and why?
1-16R7A:    MQ300 OMA agent abend (FATAL ERROR)  each time it is stopped
1-4UJ9Q:    MQ350 Problem with situation showing status of rec channel.
1-5AVU6:    MQ300 Agent tries to connect to "Default" as the name of 
            qmgr when the default qmgr was not started
1-3QZHR:    Provide host information so that MQSeries Queue Managers 
            appear under the correct host name and platform in the 
            CandleNet Portal (CNP) Navigator Tree.
1-30CBB:    Added attribute "qmmsg_sum.msgid" (i.e. Message ID) to 
            Take-Action Select-Attributes list for DLQ Summary and 
	    Message Summary reports. 
	    Added attribute "QMMSG_DET.msgid" to Take-Action 
            Select-Attributes list for Message Descriptor Report. (CMW)
1-3HD71:    MQ350 agent goes OFFLINE when Take Action is used.
1-3HDW4:    Multiple time related problems.
1-3BQSX:    Incorrect time char "%x %X" in log messages.
1-16763209: Missing CMW components from MQWS6012
                                                

Keywords:
HIPER


Release Level:
Candle Products - April, 2002 Maintenance (01R2M3)
Candle Products - December, 2000 GA (00R2G3)
Candle Products - December, 2001 GA (01R2G2)
Candle Products - February, 2003 Maintenance (02R2M6)
Candle Products - January, 2001 Maintenance (00R2M1)
Candle Products - July, 2001 GA (00R3G2)
Candle Products - July, 2002 Maintenance (02R1M3)
Candle Products - June, 2003 Maintenance (02R3M4)
Candle Products - March, 2003 GA (02R3G1)
Candle Products - November, 2001 Maintenance (01R1M1)
Candle Products - October, 2002 GA (02R2G3)
Candle Products - September, 2001 GA (01R1G3)
Candle Products - September, 2003 Maintenance (02R3M5)

Corequisite Fixes:
None.

Users Affected:
All users of CCC for MQSeries v350.

Resolution:
Apply the enclosed maintenance.

Operating System Version(s) that Fix Applies to:
AIX 4.3.3 (A6)

Modules Replaced:

New and Replaced Modules:
ax42/mq/bin
19224481 Feb 19 14:08 kmqagent*

ax433/mq/bin
19224481 Feb 19 14:08 kmqagent*

Creation date:
February 20, 2004

Installation Steps:
Note: Binaries installed in aix42 and aix433 are identical.
      aix433 directory will apply to CD images 01r2m3 and later.
      aix42 directory applies to CD images prior to 01r2m3.

1. Stop kmqagent and the Candle Management Server (CMS) if they are
   installed and running.
2. Make a backup copy of the modules listed above by copying them to
   another directory.
3. Transfer MQxx6026.tar.Z in binary mode to a temporary directory
   other than $CANDLEHOME, such as /tmp.
4. From $CANDLEHOME, install by issuing
   uncompress -c /tmp/MQxx6026.tar.Z | tar xvf -
5. Start kmqagent and the CMS if they are installed.

Fix Removal Steps:
1. Shut down the Candle Management Agent
2. Copy the backup files from %CANDLE_HOME%\TEMP to the appropriate
   directories.
3. Restart the CMA to reactivate these modules.
