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.

Step I — Planning an Authority Broker 4.x Move

Note the following before moving your Authority Broker installation to a different system.

  • Authority Broker 4.x Installation

    Authority Broker must be installed using the software installer so all of the user profiles, authorization lists, and exit programs are created and/or registered. The version installed on the target system must be the same as the version installed on the source system.

  • Alert Methods & Email Server

    Verify the email server is the same on the new system as it is in the system that you are moving Authority Broker from.

    Note: If using a fully qualified name, verify that the fully qualified name is either in the local host table or DNS server.

  • Alert Methods — Message Queue & External Message Queue

    If you are using either User Message Queue or External Message Queue alert methods, both the user profile and the message queue must exist on the new system.

  • Alert Methods — Custom Alert Methods

    If any custom alert methods have been setup within Authority Broker, the library and program must also be moved to the new system.

    User 'Work with Interested Parties' to see what alert methods are used.

  • Exit Points — Custom Exit Points

    If any custom exit points have been setup in Authority Broker, these libraries, files, and programs must also be moved to the new system.

    Use the Work with Product Exits Menu to see whether exit programs are used.

  • System Users & Switch Profiles

    Verify that all of the system user profiles and switch profiles exist on the new system.

  • Event Reporting

    Authority Broker uses the system’s QAUDJRN (IBM system journal). QAUDJRN cannot be moved from the old system so all event reporting will be from the date/time Authority Broker is installed and setup on the new system.

Step II — Install Authority Broker 4.x

To successfully move Authority Broker from one system to another (i.e. a D/R system), you must first install Authority Broker on the destination system using the software installer.

The installer creates the required user profiles and authorization lists, and registers the Authority Broker exit program.

  1. Authority Broker has two user profiles: PLABADM and PLABOWN.
  2. Authority Broker has these authorization lists: POWERABADM, POWERABDTA, POWERABFL, POWERABFO, POWERABPGM and POWERABRPT.

Note 1: If the user profiles or authorization lists exist, the Authority Broker installation will fail. If installation fails, delete these user profiles and/or authorization lists and try the installation again.

Note 2: During the installation process, Authority Broker registers its exit program to its associated exit point – POWERLOCK_AB. Without the exit program registration, Authority Broker profile switches will fail.

Step III – Authority Broker Journal & Replication

If the new system is in an HA environment, please refer to the Authority Broker 4.x Setup in an HA Environment for more information.

Step IV – Authority Broker Files to Move

Below is a list of files that contain the setup and configuration in Authority Broker. In step VI below, you will save these files in the PTABLIB to a savefile then restore them on the new system:

PABEML, PABEXITG, PABEXITSP, PAMALERT, PAMDOW, PAMDOWD, PAMDOWO, PAMEXCL, PAMFCCTL, PAMFCOVR, PAMGRC, PAMGRO, PAMHDR, PAMIP, PAMIPEM, PAMIPRPT, PAMSYS, PAMTMSW and PLUP990       

Note: The files PAMSWPHDR, PAMSWPLOG and PABWSD are the swap history and screen capture files. These files are not included in the move as this history should not be moved from the old system.

Step V – License Objects

Authority Broker version 4 has the ability to enter multiple licenses (press F7 – License List on License Setup screen). This allows you to enter the HA system’s license before the role swap without needing to contact PowerTech technical support for an emergency (temporary) key.   

In the event that you are using multiple licenses and have entered the new system’s license on the current system, you will need to save the PAB9800U user space and move it to the new system. If you are not using the multiple license feature, you can omit this user space and enter the new system’s license key in the product.

Step VI – Move Authority Broker Commands

Create the following save file on both systems (from and to/new):

CRTSAVF FILE(QGPL/MOVABSAVF) TEXT('Move Authority Broker Savefile')

Save command to use if FILES and LICENSE object are to be saved:

SAVOBJ OBJ(PABEML PABEXITG PABEXITSP PAMALERT PAMDOW PAMDOWD PAMDOWO PAMEXCL PAMFCCTL PAMFCOVR PAMGRC PAMGRO PAMHDR PAMIP PAMIPEM PAMIPRPT PAMSYS PAMTMSW PLUP990 PAB9800U) LIB(PTABLIB) DEV(*SAVF) SAVF(QGPL/MOVABSAVF) PVTAUT(*YES)

Note: Target release (TGTRLS) must be determined by the customer.

OR, save command to use if ONLY FILES are to be saved:

SAVOBJ OBJ(PABEML PABEXITG PABEXITSP PAMALERT PAMDOW PAMDOWD PAMDOWO PAMEXCL PAMFCCTL PAMFCOVR PAMGRC PAMGRO PAMHDR PAMIP PAMIPEM PAMIPRPT PAMSYS PAMTMSW PLUP990) LIB(PTABLIB) DEV(*SAVF) SAVF(QGPL/MOVABSAVF) PVTAUT(*YES)

Note: Target release (TGTRLS) must be determined by the customer.

FTP the savefile to the new system, then use the following restore command to restore the files and license object (if saved):

RSTOBJ OBJ(*ALL) SAVLIB(PTABLIB) DEV(*SAVF) SAVF(QGPL/MOVABSAVF) MBROPT(*ALL) ALWOBJDIF(*FILELVL) PVTAUT(*YES)

Step VII – Authorization Lists

Review the following authorization lists and add the users from the old system to the new system:

POWERABADM, POWERABDTA, POWERABFL, POWERABFO, POWERABPGM and POWERABRPT


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: April 08, 2019