CORBA 2.6.1 Readme

NonStop_CORBA_2.6.1_R eadme.txt
7. Follow the Pre-Installation Instructions in Section II below, if
any, before continuing to Step 8.
8. Run IPSetup to place and install (move NonStop Kernel files to the
correct ISVs) this product. If TCP/IP and FTP are unavailable, or
if you have problems with automatic file placement, use the
instructions in the IPSetup User Guide section
"Manual Software Placement Using the IPSetup TACL Program" to
manually place NonStop Kernel files.
This product contains both NonStop Kernel components and workstation
components. You may choose one, two, or three components to place
in one installation.
9. Follow the post-installation instructions in Section III below, if
any, after using IPSetup to place and install this product.
II. Pre-Installation Instructions
NOTE: There are certain installations of CORBA versions which are
incompatible if DSM/SCM is employed during installation time.
Please note the following scenarios:
A. If you install a NonStop CORBA 2.3 using DSM/SCM on a system
where NonStop CORBA 2.6.1 has been installed, the template files
from the latest installation will overwrite the template files
from the earlier NonStop CORBA 2.6.1 installation. Any error
messages introduced in NonStop CORBA 2.6.1 will be lost.
To manually reinstall the EMS template files from NonStop
CORBA 2.6.1, please see Section III Post-Installation
Instructions.
B. You cannot install a NonStop CORBA 2.3,and a NonStop CORBA 2.6.1
product at the same time using DSM/SCM. The installation will
terminate with a message similiar to the following:
ERROR: A duplicate file was found. Product T0539 and
Product T2818 both place file ZDOMC in TSV ZSPIDEF.
These two files have different fingerprints.
Prepare to run IPSetup by performing the following steps:
1. If you have an existing NonStop CORBA 2.3 or NonStop CORBA 2.6
installation, stop all NonStop CORBA applications and subsystems.
Discussion: Eliminates file conflicts with the earlier
NonStop CORBA installations versions.
When updating the ISVs, IPSetup attempts to purge existing
files in the ISV during processing. If a NonStop CORBA
application is running, IPSetup is not able to purge files,
such as NSDSRL, and terminates.
2. Ensure that you (the installation user) are not listed in
$SYSTEM.ZTCPIP.FTPUSERS.
Discussion: If you try to install products using IPSetup and
your user ID is listed in $SYSTEM.ZTCPIP.FTPUSERS, the
installation fails at the point where IPSetup tries to transfer
Page 2