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, Clearer Names for HelpSystems Security Software.

Step I — Planning a Password Self Help Product Move

Note the following before moving your Password Self Help installation to a different system.

  • Password Self Help installation

    Password Self Help must be installed using the software installer so all of the objects that reside outside the product library, like user profiles, are created.

  • Password Self Help configuration and user profile considerations  

    If you are moving the product to copy setup from one system to another, consider if the configuration on the new system will be similar to the system you are moving from.  If many configuration changes will be needed, and/or if the user profiles to enroll on the new system are different, it may make sense to proceed with a new install of Password Self Help instead of moving the product.

  • Using Password Self Help in an HA environment

    Special consideration is needed if Password Self Help is used in an HA or Mirrored Configuration. For example, you will need to end the replication prior to backing up the library on the original system to ensure that all objects are saved.

  • Licensing

    A new license key will be needed for the system you are moving to. If the new system is replacing the old system, be sure to fill out the Hardware Change Form, or speak to your sales team to get a license key for the new system.

Step II — Install Password Self Help 3.x

On the system you are moving to, install the same version as the one that is installed on the system you are moving from, using the regular install process. See Installing Password Self Help 3.  

The installer creates the required user profiles and other objects for Password Self Help. Password Self Help has two user profiles: ALERTSH and SELFHELP.

Step III – Save Library @MSSH for Password Self Help

On the original system, use the following commands to create a savf and save the library to prepare for the move:

CRTSAVF FILE(QGPL/MOVEPSH) TEXT('Move Password Self Help Savefile')


Step IV – Create the savf and FTP to the new system for Password Self Help

On the system you are moving to, run this command to create the savefile:

CRTSAVF FILE(QGPL/MOVEPSH) TEXT(‘Move Password Self Help Savefile’)

Then FTP the savf from the original system to the new system, in Binary mode.

Step V – Restore Library @MSSH for Password Self Help

If for some reason you were unable to perform Step II to install Password Self Help, you must first SAVSECDTA from the original System and RSTUSRPRF ensure the ALERTSH and SELFHELP profiles exist on the system, then you can restore the library using your savf:


Step VI – System rename command

If your system name on the new system is the same as the old system, skip to step VII. Otherwise,

  1. Sign-on as ALERTSH. 
  2. Take option 60, Command Display Screen, to pull up a command line from within the product. 
  3. Use the command CHGSHPSYS to bring up the Change System Name screen.
  4. Fill in the system name from the original system, and the system name of the new system that you are on now. 
  5. Press Enter to validate the information. 
  6. Press F14 to submit the change.

Step VII – Licensing Password Self Help

  1. Sign on as ALERTSH. 
  2. Take option 70, License Setup.
  3. Enter the license key obtained from your sales team. If you have not already done so, you may request a key by emailing a screen shot of the License Setup screen to [email protected].

Step VIII – Cleaning up unneeded profiles from Password Self Help

If you are running version 3.002 or higher, you can use a command to remove users. The command CLNUPPSHPR has no parameters. It removes unwanted profiles (those not physically existing on the system) from the Password Self Help configuration. Use Option 60 from the ALERTSH menu to bring up a command line to run this command.

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

Last Modified On: October 14, 2019