+

Search Tips | Advanced Search

Reverting to the previous maintenance level on HP-UX

You revert to a previous maintenance level of IBM MQ by using swremove.


Before you begin

  1. If you are running on a server with multiple IBM MQ installations, you must identify the installation. Make sure that the commands you enter run against the correct installation; see setmqenv.

We can apply and remove maintenance from a IBM MQ MQI client that is not installed on the same server as a queue manager. You do not have to stop any queue managers or logon as administrator. Because we do not have to stop any queue managers, do not do steps 1 to 3 in the following maintenance procedure.


Procedure

  1. Log in as a user in group mqm.
  2. Stop all applications using the IBM MQ installation.

    If we use the Managed File Transfer (MFT) component, ensure that any MFT agents have finished all of the file transfers that they were engaged in. There should be no incomplete transfers associated with the agents, and their SYSTEM.FTE.STATE queues should contain no messages.

  3. End all the activity of queue managers associated with the IBM MQ installation.
    1. Run the dspmq command to list the state of all the queue managers on the system.

      Run either of the following commands from the installation that you are updating: 

      dspmq -o installation -o status
dspmq -a

      dspmq -o installation -o status displays the installation name and status of queue managers associated with all installations of IBM MQ.

      dspmq -a displays the status of active queue managers associated with the installation from which the command is run.

    2. Use the MQSC command DISPLAY LSSTATUS to list the status of listeners associated with a queue manager, as shown in the following example: 
      echo "DISPLAY LSSTATUS(*) STATUS" | runmqsc QmgrName
    3. Run the endmqm command to stop each running queue manager associated with this installation.

      endmqm -c-w-i-p

    5. QmgrName

    9. The endmqm command informs an application that the queue manager it is connected to is stopping; see Stop a queue manager.

      For the maintenance to proceed, applications must respond to an endmqm command by disconnecting from the queue manager and releasing any IBM MQ libraries they have loaded. If they do not, you must find another way to force applications to release IBM MQ resources, such as by stopping the applications.

      You must also stop applications that are using the client libraries that are part of the installation. Client applications might be connected to a different queue manager, running a different installation of IBM MQ. The application is not informed about queue managers in the current installation being shut down.

      Any applications that continue to have IBM MQ shared libraries from the installation loaded prevent you applying IBM MQ maintenance. An application might disconnect from a queue manager, or be forcibly disconnected, but keep an IBM MQ shared library loaded.

      Note: Apply maintenance level updates to multi-instance queue managers on UNIX and Linux describes how to apply maintenance to a multi-instance queue manager. A multi-instance queue manager can continue to run on one server, while maintenance is applied to another server.
    10. Stop any listeners associated with the queue managers, using the command: 
      endmqlsr -m QMgrName
  4. Log in as root, or switch to the superuser using the su command.
  5. Run the swremove command to remove the maintenance package from the system.

    For example, to remove the 7.R.0.1 maintenance level, use the command: 

    swremove MQSERIES,r=7.R.0.1,l= MQ_INSTALLATION_PATH
    where:

    • R is the number of the Release
    • MQ_INSTALLATION_PATH is the installation path for IBM MQ
    Details of the swremove command can be found in the HP-UX Administration Guide or by using the man swremove command.