This hot fix can be downloaded from the SFDC Customer Portal Web UI, using your username and password for support.tibco.com.  Once logged on you can find the hotfix under Download Menu :
AvailableDownloads/BusinessWorks/Plugins/WebSphere_MQ/7.7.0/hotfix-04

Listed below is a summary of updates included. Please refer to the associated read me document for any additional information.

===============================================
Closed Issues in 7.7.0.HF004

    BWMQ-904  When activity pooling is enabled for activities sharing a queue manager 
        connection resource the second activity can return its client to the pool erroneously 
        resulting in a negative residence count.  Can also pollute the pool with activities
        containing closed queue manager connections resulting in HCONN errors.

    BWMQ-903  When multiple get or listen threads connect to a zOS 9.x queue manager an 
            indexing error can result.
            
    BWMQ-900  MQ errors after upgrade to server v9+.  Activities fail trying to access the
            SYSTEM.ADMIN.COMMAND.QUEUE.  This was caused by the fix for BWMQ-847
            which introduced the use of the PCFAgent to get the server platform. 
            
    BWMQ-894 MQ client trace is enabled when turning on BW trace. 
        
    BWMQ-847 Get fails on MQ server version 9.1  The existing for obtaining the server platform
            mechanism has been was deprecated by IBM.  Switch to using the PCFAgent for that. 

    Important correction from the hotfix 1 notes below.  The following setting:
    GenericKeyedObjectPool.Config.maxWait     : default 30 seconds
    refers to a specification in milliseconds.  So the default is coded as:
    GenericKeyedObjectPool.Config.maxWait=30000

Closed Issues in 7.7.0.HF3

    BWMQ-880  Polling listeners not closing destinations when tester stopped.

    BWMQ-879  NPE in process cleanup when using activity pooling after activity has an error.
        Only observed when the connection resource was not mapped.
        
    BWMQ-878
        Delay the startup of listeners so that each instance gets a shared conversation.  To use
        the delay add this parm to bwengine.tra and redeploy the app:
        
        java.property.com.tibco.plugin.bwmq.ListenerInstanceStartupDelay=5000
        
        where 5000 in this case is the number of milliseconds required to ensure
        that the first connection is complete before starting other listener instances.

    BWMQ-877  Add the ability to log the actions of the pool manager with stats.  Add
        the value:
        java.property.com.tibco.mqplugin.DebugConnectionPool=true
        to the application TRA file to turn on detailed connection pool messages.
     
    BWMQ-876  Connection Leakage when high performance app encounters a lot of errors.
    
    BWMQ-873  The activity pooling option introduced in HF1 is not displayed on BWMQ-HF2.
        Activity pooling would, therefore, not work in HF2. 

Closed Issues in 7.7.0.HF2

    BWMQ-848 Plugin uses a deprecated interface and that interface crashes the 9.1 channel  This is
        most apparent in that Get and Listen fail when connected to a version 9.1 server
    
    BWMQ-849  Connection pool max connection can be exceeded.  If multiple threads attempt to
        add connections to the pool at the same time the max can be exceeded.            
    
    BWMQ-786 Connection erroneously shared between instances of a subprocesses called multiple times
        from parent process.
            
Closed Issues in 7.7.0.HF1

    BWMQ-655 - MQ Put activity performance issue.  In circumstances where there is high
        latency between the plug-in platform and the MQ server the API calls to verify a pooled 
        connection, open a destination, put a message, close a destination and return the 
        connection to the pool can slow the execution of a put significantly.  To address that 
        a flag has been placed on all the applicable activities called "Pool Activity".  Use of 
        this feature will result in the a pool of connections being established at the activity level 
        where the destinations used by the activity are kept open.  By default the pool will contain
        a maximum of 30 connections.  The following parameters can be overridden via TRA 
        environment entries:
        GenericKeyedObjectPool.Config.maxTotal     : default 30
        GenericKeyedObjectPool.Config.maxWait     : default 30000  milliseconds
        GenericKeyedObjectPool.Config.maxIdle     : default 10
        
        This feature cannot be used with activities which participate in an XA transaction.
        If the activity uses a connection which is defined to be pooled, the pooling config will be 
        ignored because it is being pooled at a higher level in the activity.
        Using this feature can have impacts on the number of server connections created.  It 
        is recommended to use flow limiting to control connection consumption where necessary.
   
    BWMQ-677  Subscription Name field is not always enabled when Durable subscription is
        selected.   
===============================================