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.
These instructions are for moving from a very old version of Database Monitor for IBM i to the current version. If your version is R03M01 (3.01) or higher, see Updating Database Monitor for IBM i from 3.01 to 3.x instead.
Database Monitor for IBM i requires that you enter a valid license key. Contact firstname.lastname@example.org if you need to request a new license key.
It is Powertech’s goal not to change system values on customer systems because we recognize that security-conscious organizations have rigorous change control processes in place for even small changes to system values. Therefore, we ask you to make any system value changes that are needed. However, the Database Monitor for IBM i installation process could change a system value to allow the install to proceed if a system value is not set as specified below. If the Installation Wizard changes a system value during install, it changes it back to its original value when the install completes. To install Powertech Database Monitor for IBM i on your system, the following system values that control object restores must be configured as shown.
Database Monitor for IBM i requires that IBM i version 7.2 or higher be installed on your system.
Note: During installation an FTP connection is initiated. The FTP server responds with messages that prompt for FTP login credentials. The standard port reserved to establish an FTP connection to the IBM i is port 21. Consequently, it is required that this port is open and ‘listening’ on the server in order to establish a connection with the Installation Wizard and facilitate a successful installation.
If FTP is not available, you must install the product manually. See Manual Installation of Powertech IBM i Products.
CALL IDT465 PARM('0' '*ALL' ' ') - this will stop all file monitoring
CALL DQVIEW SLAW (look to make sure the queues are empty)
DSPFD DATATHREAD/IDTPRO (‘B’ for bottom - make sure there are no records)
DSPFD DATATHREAD/IDTOVR (‘B’ for bottom - make sure there are no records)
STRDT Option 17, ENDALL
ENDSBS DATATHREAD *IMMED
Use the command WRKSBS and verify the SBS DATATHREAD is not running.
SAVLIB LIB(DATATHREAD) DEV(*SAVF) SAVF(QGPL/DTV3R2_SVF)
The Database Monitor for IBM i installation file is available on the Database Monitor for IBM i download page. (The "Trial" download is the full product, which can be unlocked with a valid License Key).
Ensure the following servers are available and running prior to installation:
Do the following to install Database Monitor for IBM i on your system:
WRKOBJLCK DATATHREAD/IDTSEQ *FILE
WRKOBJLCK DATATHREAD *LIB
There must be NO locks on any files in Database Monitor for IBM i before proceeding – back out of any screens you or others may have up in the Database Monitor for IBM i product.
Enter B for bottom & press Enter.
If the member name is INNPRM instead of INNPRMNEW, rename it as follows:
RNMM FILE(DATATHREAD/INNPRMNEW) MBR(INNPRM) NEWMBR(INNPRMNEW)
Enter B for bottom & press Enter.
If the member name is IDTMSG instead of IDTMSGNEW, rename it as follows:
RNMM FILE(DATATHREAD/IDTMSGNEW) MBR(IDTMSG) NEWMBR(IDTMSGNEW)
Note: Make sure the user profile 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.
Enter license key using Option 18
Database Monitor for IBM i installs the following product libraries, user profiles, and command on your system. It also creates the DATATHREAD subsystem if it doesn’t already exist.
|Installed on System||Description|
DATATHREAD, which has a user class of *USER
The profile is set to Password = *NONE so it can’t be used to sign on to the system.
Check for system specific values (IP address, MAIL-FRM info, etc.) using Option 12.
Verify files specific to your environment are included the list of files using Option 11.
Verify history from your system prior to the upgrade shows in Option 21.
CALL IDT465 PARM('1' '*ALL' ' ')
STRDT, Option 17 then STRMGR
STRDT, Option 17 then DSPALL
Still have questions? We can help. Submit a case to Technical Support.