These instructions assume that you have the correct license for the new partition/system. It is important that the correct procedure is followed for a new install; this is because when performed incorrectly, you may see messages about serial numbers and model numbers when starting the DetectIT subsystems.

Issues sometimes arise because a client has loaded DetectIT onto a new partition by restoring from DetectIT libraries saved on another IBM i. This is not the method recommended by Safestone.

The only clean way to install DetectIT is from the original download files. It is recommended you do this for all new installations.

Similarly, it is recommended that you only restore DetectIT from backups that were taken on that same system. An alternative to this is to use the DetectIT Network module which helps you to control multiple IBM i systems from one centralized "console" and distribute DetectIT definitions from one system to another.

If you have restored from backups made on a different system you will need to enter a permanent key and possibly an upgrade key and use the CHGSYSNAM command which will update the old database with the new system name of the IBM i.

Note: the CHGSYSNAM command is necessary if you intend to 're-use' the settings from the other IBM i. In many of the DetectIT files the system name (e.g. SYSTEMA) is used as a major key when accessing / updating the files. Therefore after loading on SYSTEMZ from SYSTEMA's backups you will need to perform the CHGSYSNAM command.

HA (High Availability) products can produce similar key problems, if you journal the Safestone @* libraries


Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case