Platform-Specific Instructions : Installation on VMS

Installation on VMS
This section gives information that is specific to VMS platforms.
Supported Platforms and Installation Packages
TIBCO Enterprise Message Service is available on the VMS platforms listed in Table 7. (For the latest changes, see the README file.)
 
Installing TIBCO Enterprise Message Service on VMS Platforms
Follow these instructions to install TIBCO EMS software on VMS platforms.
Installation on VMS platforms uses the VMSINSTAL utility, which is described in the OpenVMS system management documentation.
 
Task A Log In as SYSTEM
Log in to the SYSTEM account.
Task B Check TCP/IP Services
EMS software will operate properly only if you have installed and started TCP/IP services.
Although you can successfully install the EMS files without running TCP/IP services, the EMS installation verification procedure will fail if TCP/IP services have not been started.
Task C Obtain the Installation Package
The product distribution contains the TIBCO Enterprise Message Service software for VMS platforms, as shown in Supported Platforms and Installation Packages. These files are also available for download from the TIBCO website.
ZIP Files
Installation packages are zipped (compressed) using the VMS free software ZIP utility. To preserve the file attributes, unzip them on a VMS computer (and not on a PC or UNIX computer).
Utilities to decompress zip files are available on the HP OpenVMS Freeware distributions, or at the HP web site:
http://h71000.www7.hp.com/openvms/freeware/index.html?jumpid=/go/openvms/freeware
File Attributes
When copying VMS save sets through a Windows PC or UNIX computer, the resulting files do not retain the proper file attributes. As a result, the VMS BACKUP utility cannot read them to install them.
To rectify this situation, copy the files to a computer running VMS, and use this command to restore the correct file attributes:
$ set file /attr = (RFM:FIX, RAT:NONE, LRL:8192) tibems*.%
Task D Mount the Distribution Media
Insert the EMS distribution into the drive.
The mount command automatically determines that the drive is formatted according to ISO 9660, but you must specify the record format for the backup save sets. For example:
$ mount /override=id/media_format=CDROM -
$_ /undefined=fix:none:8192 CD_device
Task E Install the EMS Product Software
The installation procedure requires your input. The most important items you supply are the target location for the TIBCO Enterprise Message Service files, and the environment to install (development or runtime environment).
The installation procedure takes less than 10 minutes.
Installation Steps
1.
   $ create/directory DKA100:[kits.ems-5-1-0]
2.
Set default to the root directory of the release drive, or transfer the installation package zip file to a disk directory and set default to that directory.
   $ set default DQA0:[000000]
3.
   $ unzip installation_package -d DKA100:[kits.ems-5-1-0]
4.
Retrieve and read the release notes for the VMS distribution, which are in the sys$help directory. For example, to retrieve the release notes without installing EMS software, use these commands as a model:
   $ @sys$update:vmsinstal tibems051 dka100:[kits.ems-5-1-0] -
   $_ options N
The release notes are in the file sys$help:tibems050.release_notes.
5.
   $ @sys$update:vmsinstal tibems051 dka100:[kits.ems-5-1-0]
Task F Verify Installation
We recommend that you verify correct operation of EMS. You can verify installation at any time by invoking the command:
$ @TIBEMS:[COM]QUICK_TEST.COM.
The test procedure verifies that the sample program images used are available, and displays the output seen in a successful test. Finally, it accepts input of the host name and port of a server running on another system, starts a listening program, and sends three messages. The output of the sender and receiver are displayed on the console.
Visually compare the actual results with the sample above it. If they match in all details except for host and port, then EMS software is installed and operating correctly.
Additional Information for VMS Programmers
Compile
On VMS platforms, EMS programmers must define the C-compile command appropriately.
For the Compaq C compiler:
$ CC :== CC/FLOAT=IEEE/IEEE_MODE=UNDERFLOW_TO_ZERO -
/PREFIX=ALL/INCLUDE_DIRECTORY=("/tibems/include",[])
Link
EMS API libraries are multi-threaded, so VMS scheduler upcalls can yield significant performance improvements:
$ LINK/THREADS_ENABLE=UPCALLS
When upgrading from EMS 4.3 to 4.4 or later versions, EMS client executables that were linked with the EMS 4.3 dynamic libraries (shareable images) must be relinked to the new libraries after EMS 4.4 has been installed with its associated third party libraries. The third party libraries are part of the full installation of EMS.