Reverting to the previous maintenance level on AIX

You can revert to a previous maintenance level by using the System Management Interface Tool (SMIT).

Before you begin

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.

About this task

You can back out maintenance updates (fix packs) and restore your system to the previous maintenance or installation level, for any component of IBM MQ for AIX® that is in the APPLIED state.

IBM MQ for AIX uses the following directory trees that are mutually exclusive, which are, for the :

Executable libraries and shared libraries, is /usr/mqm
Data for the queue managers and other configuration files, is var/mqm.

Because the directory trees are mutually exclusive, when you apply or remove maintenance only the files in usr/mqm are affected.

The procedure detailed within this topic removes all the fix packs installed. See Uninstalling a single fix pack on AIX for details on removing a single fix pack from your system.

You can apply and remove maintenance from an 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 you do not have to stop any queue managers, do not do steps 1 to 3 in the following maintenance procedure.

Use the following command to display the current state of the IBM MQ for AIX filesets:


lslpp [ -R usil ] -l "mqm*"

To back out a maintenance update, as the user root, issue the command:


installp [ -R usil ] -r "mqm*"

Otherwise:

Procedure

Log in as a user in group mqm.
Stop all applications using the IBM MQ installation.
If you 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.
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.
  
  The endmqm command informs an application that the queue manager it is connected to is stopping; see Stopping 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: Applying maintenance level updates to multi-instance queue managers on 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.
4. Stop any listeners associated with the queue managers, using the command:
```
endmqlsr -m QMgrName
```
Log in as root, or with sufficient authority to run the following commands.

You can do this by adding sudo before the commands, or by changing to the root user in the shell with the su command. For more information, see Exploring the differences between sudo and su commands in Linux. This information also applies to UNIX systems in general.

Open the appropriate smit panel using this sequence:


Software Installation and Maintenance
Software Maintenance and Utilities
Reject Applied Software Updates (Use Previous Version)

Alternatively, use a fast path command, smit[ty] install_update.

Complete the SOFTWARE name field.

Enter mqm* to restore all applicable file set updates to your installation.

Note: If an option to restore only selected file set updates for IBM MQ for AIX appears, avoid it. The option results in all applicable file set updates for the maintenance update being restored.
Click Enter to reject the current maintenance level and reinstate the previous maintenance or installation level.
1. Accept displayed default values for all other fields
2. Dismiss the confirmation message
The reject process starts. While the command runs, it displays progress messages terminating with an Install Summary table.
1. Check the table to see which components of IBM MQ for AIX have been rejected