Important Updates to Cybersecurity Software
HelpSystems is updating the names of our cybersecurity software, including the Powertech product line. Don’t worry—the functionality of your products won’t change.
See the new names here > New, Simpler Names for HelpSystems Security Software.
Please review the following information before upgrading Authority Broker from a previous version. If you are updating Authority Broker 4 from, for example, version 4.05 to 4.10, see Installing or updating Authority Broker 4.
|Previous versions||Authority Broker 4|
To install Powertech Authority Broker on your system, the system values that control object restores must be configured as follows.
Note: The install will work if QALWOBJRST is set to *ALL, but Powertech does not recommend using this value.
The upgrade process needs to process the history records in version 3 in order to convert them into version 4 formatting. If many history records exist, the upgrade process can be very time consuming. If you have Authority Broker history in version 3 that is older than you need, contact HelpSystems Support for assistance purging your history on the system.
As in any upgrade, it’s highly recommended you back up the previous version. Authority Broker 3 was designed as an IBM License Program Product (LPP). The IBM and Powertech recommended method for backing up an LPP type application is to use the SAVLICPGM command to a save file. Should any reason to return to the prior version occur, the save file can be easily restored.
Create a save file with the name of your choosing to be used and save the prior version using something similar to this sample command:
SAVLICPGM LICPGM(3PLAB00) DEV(*SAVF) SAVF(QGPL/yoursavefilename)
Authority Broker 4 requires the following:
Ensure the following servers are available and running prior to upgrading:
Upgrading to Authority Broker 4 is a simple three-step process:
To stop any new users from making swaps while the upgrade process is occurring rename the program PABC1100 found in the PLABROKER library. As a suggestion, rename it to PABC1100X. (Caution: Note the SAVLICPGM command will fail if the PABC1100 program has been renamed first.) It’s generally not a good idea to eject any current users currently swapped since they may be working on critical projects. It would be preferred you send an email or call the system users who have been authorized to use the Authority Broker swaps and request they release their current swaps and also not attempt any new swaps. Should it become necessary to end any current Firecall swaps, access the product main menu and take options 5, 4. Use option 4=End a timed switch. It should be noted you cannot force an end of a non-Firecall swap.
To upgrade Authority Broker, run the installation process to install Authority Broker 4 on your system.
Do the following to perform the installation:
Note 1: Make sure the user profile used for the installation is a member of the user class *SECOFR and has at least the following special authorities: *ALLOBJ, *SECADM, *JOBCTL, *IOSYSCFG, and *AUDIT. The user profile should have Limit capabilities set to *NO.
Note 2: If you are running a version of Authority Broker below 3.1.1, the program objects will be converted to be V6R1 compatible. This conversion is a one-time process on each object. To provide an uninterrupted work environment, all program conversion occurs during the upgrade, which can extend the process as long as 90 minutes or more on some systems.
Note 3: What to do if the installation fails. The installation process runs a prechecker before the actual product install. The prechecker validates the system to see if it has the proper set up installed before it runs the product installation. The installation, whether it completes or fails, will generate a joblog and a prechecker log for your review. To review the prechecker use the WRKSPLF command for the user profile used during the install and look for an object with a name format PTABnnnnnn (where the nnnnnn is the time stamp of the install). If you see an ‘F’ for failure you may attempt to remedy the problem yourself or choose to contact Technical Support for assistance.
Note: The Authority Broker Administrator's Guide can be found at Powertech Product Manuals.
(All these profiles are set to Password = *NONE so that they can’t be used to sign on to the system.)
The installation program installs Authority Broker 4 and also automatically imports prior version setup configuration information. Once the license key has been added, users may begin immediately using the product information.
Version 3, LPP product 3PLAB00, and library PLABROKER remain on the system after the upgrade so that Authority Broker 3 remains available in case the upgrade to version 4 was unsuccessful. After you have verified a successful upgrade, do the following to remove version 3 of the Authority Broker LPP product:
RMVJOBQE PTWRKMGT/PTWRKMGT PLABROKER/PLAUTBKRMN
Still have questions? We can help. Submit a case to Technical Support.