IBM i Installation - Product Removal

Owned by
Former user (Deleted)
Last updated: Nov 29, 2022 by
IT Stonebranch
Version comment
5 min read

Currently, IBM i runs Workload Automation 5.1.1.   These pages provide information for that version.

Overview

This page provides processes for the removal of current (5.1.1) and previous (5.1.0 or earlier) releases of Workload Automation for IBM i.

If you remove the currently installed release before installing or re-installing a 5.1.1 release, the removal process deletes the default command reference library, UNVCMDREF, in which the command reference files are located.

If you remove the currently installed release after installing or re-installing a 5.1.1 release, UNVCMDREF is not deleted.

To keep your command reference files from being deleted, rename UNVCMDREF and change the library owner. Release 5.1.1 will let you specify this library - or any library - as your command reference library via the CMD_REFERENCE_DIRECTORY option.

Before removing a 5.1.1 release, check CMD_REFERENCE_DIRECTORY in the Universal Command server member (UCMDS) of the Workload Automation configuration file (UNVCONF) - located in the product library (UNVPRD511); an alternate command reference library previously may have been selected. If it has, manually clear and delete the default command reference library, UNVCMDREF, after removing the 5.1.1 release.


Warning

If the UCHGRLS command was used to rename the 511-tagged names to normal production names (see UCHGRLS (Change Release Tag) Program), you must perform the following steps prior to uninstalling either 5.1.1, 5.1.0, 4.3.0, 4.2.0, 4.1.0, 3.2.0, 3.1.1, or 1.2.1:

Step 1

Run the UCHGRLS command to temporarily rename the 5.1.1 Workload Automation commands in QSYS to the 511-tagged names and the tagged names of the older product to the normal production names. Without this step, Workload Automation may no longer run as expected.

Step 2

After removal of the older product is complete, use the *NEW option with the UCHGRLS command to change the 511-tagged names back to the normal, production names.

Universal Encrypt 1.2.1

Note

Before performing this uninstall, read the Overview.

You must uninstall Universal Encrypt 1.2.1 before uninstalling Universal Command 1.2.1.

The user ID used for uninstalling Universal Encrypt must have authority to delete all Universal Encrypt product-related objects.

To uninstall Universal Encrypt, perform the following steps:

Step 1

To remove the licensed program, execute the following command:
 

Step 2

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UEN121 option *ALL release *ONLY not deleted.
Correct the problem and repeat Step 1.

Universal Command 1.2.1

Note

Before performing this uninstall, read the Overview.

Before uninstalling Universal Command 1.2.1, you must uninstall Universal Encrypt 1.2.1.

The user ID used for uninstalling Universal Command must have *ALLOBJ and *SECADM special authorities.

To uninstall Universal Command, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UBROKER).
On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UCM121 option *ALL release *ONLY not deleted."

Correct the problem and repeat Step 2.

Universal Products 3.1.1

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Universal Products 3.1.1 must have *ALLOBJ and *SECADM special authorities.

To uninstall Universal Products 3.1.1, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UBROKER).
On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV311 option *ALL release *ONLY not deleted.
Correct the problem and repeat Step 2.

Universal Products 3.2.0

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Universal Products 3.2.0 must have *ALLOBJ and *SECADM special authorities.

To uninstall Universal Products 3.2.0, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UNVUBR320).

On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV320 option *ALL release *ONLY not deleted.

Correct the problem and repeat Step 2.

Universal Products 4.1.0

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Universal Products 4.1.0 must have *ALLOBJ and *SECADM special authorities.

To uninstall Universal Products 4.1.0, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UNVUBR410).
On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV410 option *ALL release *ONLY not deleted.
Correct the problem and repeat Step 2.

Stonebranch Solutions 4.2.0

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Stonebranch Solutions 4.2.0 must have *ALLOBJ and *SECADM special authorities.

To uninstall Stonebranch Solutions 4.2.0, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UNVUBR420).

On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV511 option *ALL release *ONLY not deleted.

Correct the problem and repeat Step 2.

Stonebranch Solutions 4.3.0

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Stonebranch Solutions 4.3.0 must have *ALLOBJ and *SECADM special authorities.

To uninstall Stonebranch Solutions 4.3.0, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UNVUBR430).

On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV430 option *ALL release *ONLY not deleted.

Correct the problem and repeat Step 2.

Workload Automation 5.1.0

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Workload Automation 5.1.0 must have *ALLOBJ and *SECADM special authorities.

To uninstall Workload Automation 5.1.0, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UNVUBR510).

On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV511 option *ALL release *ONLY not deleted.

Correct the problem and repeat Step 2.

Workload Automation 5.1.1

Note

Before performing this uninstall, read the Overview.

The user ID used for uninstalling Workload Automation 5.1.1 must have *ALLOBJ and *SECADM special authorities.

To uninstall Workload Automation 5.1.1, perform the following steps:

Step 1

If it is active, end the Universal Broker subsystem (UNVUBR511).

On the IBM i command line, execute the following command:
 

Step 2

To remove the licensed program, execute the following command:
 

Step 3

If the following message displays, use the DSPJOBLOG command to identify the problem:
Objects for product 0UNV511 option *ALL release *ONLY not deleted.

Correct the problem and repeat Step 2.