Online Product Support

For more in-depth questions, or any question that is not included in the FAQ’s, please contact your local Safestone support office for assistance.

Installation & Upgrade Questions

  1. I have installed DetectIT but cannot see any options for the modules we have acquired. Why would this be?

    You need to enter a license key to enable the modules. If you have not received this key please contact your DetectIT supplier or Safestone Account Manager.

  2. I am upgrading to a new version of DetectIT. Will I need new keys?

    No, the license keys that have already been supplied will work correctly after the upgrade. To ensure that the license information is copied from one release to another please ensure that the flag ‘Transfer Data’ is set to “Y” during the DetectIT upgrade. If you choose to enter an “N” for this parameter, the license key will need re-applying manually after the upgrade completes.

  3. Can I install the update for the new DetectIT Graphical software on top of my existing Graphical installation?

    Yes, the new release will automatically save your existing configuration and then update the programs as necessary. Do I need to end the DetectIT subsystems in order to install an upgrade?

    Yes, you will need to end the DetectIT subsystems, but note there will be other critical pre-requisites for the upgrade procedure. For full instructions please refer to the sections titled “Upgrading Native Software”, “Upgrading the Graphical Software on System i” and “Installing the DetectIT Graphical Software on the PC” in the Deployment Guide.

  4. How can I find out what releases of DetectIT are compatible with each OS/400 operating system release?

    Please refer to the Version Support page.

  5. Why has the network attribute JOBACN changed from *FILE to *SEARCH during the installation?

    This is so that the DetectIT networking module can function correctly. The table of network job entries will be searched in order to determine the action to be taken for the input stream. DetectIT will ensure that the correct entries are maintained for its own requirements.

    This change is ONLY necessary if you will be using the QSNADS communication methodology within the DetectIT Networking module. If this does not apply to you then please feel free to change the value back.

  6. What is the correct way to install DetectIT on a new System i machine or partition?

    (This as assumes 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 System i. This is not the method recommended by Safestone.

    The only clean way to install DetectIT is from the original Safestone CDs. 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 System 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 System i.

    NOTE: the CHGSYSNAM command is necessary if you intend to ‘re-use’ the settings from the other System 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.

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

  7. Can Safestone provide me with a temporary license key to use during my disaster recovery test?

    We could send a temporary key in advance - but that does not really duplicate a true disaster in the real world - although it would be nice if you got 2 days warning.

    As an alternative you should be aware of a part of DetectIT called ‘contingency key processing’. This is intended for a disaster recovery scenario, specifically where DetectIT is loaded on a 3rd party System i, on a temporary basis.

    Obviously in a DR situation, you need to get up and running as quickly as possible, therefore we provide a key within our standard documentation that you can utilize. This will give you 14 days to use DetectIT on any box, after that you would need to contact Safestone for a further temporary key.

    This contingency key and the process is listed in the DetectIT native manual called ‘General Concepts Guide’ which can be found on the ‘Documentation’ CD.

  8. I am about to upgrade DetectIT and I see libraries @APYDTI and @APYESRS. Can these be deleted?

    You can delete the libraries before the upgrade. Libraries @APYDTI and @APYESRS can be removed safely at any time.

    They are left on the system so that they are available just in case you want to install DetectIT libraries around a network of System i machines, without physically dispatching the CDs.