Updating from a Previous Release of Irstream or HP OV OS/400 Management - ironstream_for_micro_focus_omi - 7.0

Ironstream for Micro Focus® OMi for IBM i Release Notes

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® OMi
Version
7.0
Language
English
Product name
Ironstream for Micro Focus OMi for IBM i
Title
Ironstream for Micro Focus® OMi for IBM i Release Notes
Copyright
2021
First publish date
2007
ft:lastEdition
2023-08-22
ft:lastPublication
2023-08-23T16:21:59.136387

Version 7.0 requires a new license key if you are upgrading from any prior release. When you are ready to upgrade please notify Precisely Support by visiting https://support.precisely.com/ and request version 7.0 license keys. If you are upgrading from the OV OS/400 management product, you will need to provide the following information about your IBM i systems in order to obtain license keys, if you have not previously provided this information, commands to retrieve the information are shown next to each required item):

System Serial Number: DSPSYSVAL QSRLNBR

Processor Group: WRKLICINF

When upgrading from an existing installation, the files and subdirectories in

/etc/opt/OV/share/conf/vp400 should be backed up. Normal installation will not modify existing configuration files, but these files should be backed up in the event of an unexpected problem occurring during the installation process.

Before running the installation command on the OMU server, stop any existing processes on the server using the commands:

/opt/OV/vp400/bin/vp400sv –stop ovc -stop vp400elli

Before transferring the agent files to the IBM i, stop any running agent subsystem jobs on the IBM i using the command:

ENDSBS EVSBS *IMMED

replaced, and it will be necessary to add re-add IBM i nodes back into this group if this group is being used to assign operator responsibilities.

During the installation process of the version 7.0 IBM i agent on the IBM i, any existing configuration data will be backed up and then restored to the EVIEW library at the end of the installation. A backup of the old EVIEW library will be created in a savefile named EVIEW7SAVE in the QGPL library. You can change the destination library for this savefile by pressing F4 when executing the installation program EVREL70/EVINSTALL. You can also specify “*NONE” as the destination library to skip the creation of this backup savefile.

The default TCP/IP ports connecting the OM server to the IBM i agent have changed in Version 7.0. Prior to Version 7.0, the connection was made using ports 8000 and 8001. Beginning with Version 7.0, ports 9000 and 9001 will be the default ports used, but if you are upgrading from Version 6.X, your existing port configurations will be retained.

IMPORTANT NOTE WHEN UPGRADING FROM VERSION 6.X: The Version 6.X policy templates are defined with “R06 in the policy name, and their associated perl scripts also contain “ R06” in their name. Version 7.0 policies use the OM 9 feature of policy versions, so there is no release numbering in the policy name or the perl script. However, the

Version 7.0 installation will create duplicate versions of the perl scirpts with the “R06” names to ensure that the policies are calling the latest perl scripts. If you have modified any of the Ironstream perl scripts, you must create

IMPORTANT NOTE WHEN UPGRADING FROM HP OV OS/400 MANAGEMENT: The default for original

message text includes fields in the message text that are not present in any version of OS/400 Management product that was obtained from HP. In order to maintain the same original message text format from the HP versions, you must set the node parameter EV400_ADDMSG_FIELDS to a value of NO. Failure to change this parameter will result in message template conditions not matching as expected.